CN108696363B - Charging method and device - Google Patents

Charging method and device Download PDF

Info

Publication number
CN108696363B
CN108696363B CN201710105127.3A CN201710105127A CN108696363B CN 108696363 B CN108696363 B CN 108696363B CN 201710105127 A CN201710105127 A CN 201710105127A CN 108696363 B CN108696363 B CN 108696363B
Authority
CN
China
Prior art keywords
data packet
successfully
base station
charging
flow
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201710105127.3A
Other languages
Chinese (zh)
Other versions
CN108696363A (en
Inventor
李立
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201710105127.3A priority Critical patent/CN108696363B/en
Priority to PCT/CN2018/073655 priority patent/WO2018153193A1/en
Publication of CN108696363A publication Critical patent/CN108696363A/en
Application granted granted Critical
Publication of CN108696363B publication Critical patent/CN108696363B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1432—Metric aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing

Abstract

The embodiment of the application provides a charging method and a charging device, and the charging method comprises the steps that a Service Gateway (SGW) determines data packets which are not successfully issued to a base station, wherein the data packets which are not successfully issued to the base station comprise at least one of data packets cached in the SGW, data packets discarded by the SGW and data packets which are failed to be issued to the base station by the SGW; the SGW accumulates the flow of the data packets which are not successfully issued to the base station according to a detection rule; and the SGW sends the accumulated flow to a charging system so that the charging system determines the flow of the data packet which is successfully sent according to the accumulated flow. The problem of inaccurate charging caused by deducting the flow of the data packet which is not successfully transmitted to the terminal is solved.

Description

Charging method and device
Technical Field
The present application relates to the field of communications, and in particular, to a charging method and apparatus.
Background
At present, when a network element provides generated charging information to a charging system, it usually counts the number of data packets received and transmitted by the network element. However, before reaching the terminal device, the data packet may also pass through a number of upstream network elements. It may occur that some of the data packets counted by the upstream network element are not actually successfully delivered to the terminal. In this case, if the charging system uses the charging information provided by the upstream network element as the main basis for charging the user, a situation of charging the user more frequently occurs.
For example, in an Evolved Packet Core (EPC), downlink Data sequentially passes through an application layer, a Data Gateway (PGW), a Serving Gateway (SGW), and a radio access Network, and is delivered to a terminal. The PGW has the capability of providing online and offline charging information, and the SGW has the capability of providing offline charging information. The PGW is a main charging information data source for charging the user by the charging system. Because some data packets sent by the PGW to the SGW may not be successfully sent to the terminal, the data volume counted by the PGW when generating the charging information may be greater than the data volume actually received by the user, resulting in erroneous charging.
Disclosure of Invention
The embodiment of the application provides a charging method and a charging device, which solve the problem of inaccurate charging caused by deducting the flow of a data packet which is not successfully issued to a terminal.
In a first aspect, a charging method is provided, including: the service gateway SGW determines data packets which are not successfully issued to the base station, wherein the data packets which are not successfully issued to the base station comprise at least one of data packets cached in the SGW, data packets discarded by the SGW and data packets which are failed to be issued to the base station by the SGW. And the SGW accumulates the flow of the data packets which are not successfully issued to the base station according to the detection rule. And the SGW sends the accumulated flow to the charging system so that the charging system determines the flow of the data packet which is successfully issued according to the accumulated flow.
With reference to the implementation manner of the first aspect, in a first possible implementation manner of the first aspect, the SGW further sends, to the charging system, reception time information of a data packet that is not successfully delivered to the base station.
With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner, the SGW sends the accumulated traffic to the charging system through a policy and charging rules function PCRF.
The modification of the SGW dialogue single format can be avoided by sending the accumulated flow to the charging system through the PCRF.
With reference to the first aspect or any one of the first to second possible implementation manners of the first aspect, in a third possible implementation manner, the SGW sends the accumulated traffic to the charging system through the data gateway PGW.
With reference to the first aspect or any one of the first to third possible implementation manners of the first aspect, in a fourth possible implementation manner, the detecting rule includes a correspondence between five-tuple information and a rate group, and accumulating, according to the detecting rule, traffic of a data packet that is unsuccessfully issued to the base station includes: and determining the rate group corresponding to the data packet which is not successfully transmitted to the base station according to the quintuple information of the data packet, and accumulating the flow of the data packet which is not successfully transmitted to the base station and has the same rate group according to the rate group.
With reference to the first aspect or any one of the first to fourth possible implementation manners of the first aspect, in a fifth possible implementation manner, the SGW sends the accumulated traffic record in a ticket to the charging system.
With reference to the first aspect or any one of the first to fifth possible implementation manners of the first aspect, in a sixth possible implementation manner, the correspondence between the five-tuple information and the tariff group includes a correspondence between the five-tuple information and the tariff group and a service identifier.
With reference to the first aspect or any one of the first to sixth possible implementation manners of the first aspect, in a seventh possible implementation manner, the SGW determines, according to a processing policy, a data packet that is not successfully delivered to the base station, where the processing policy includes determining, according to at least one of a priority of a bearer, a current network congestion state, a current state of a terminal, operator configuration information, and information from other network elements, a data packet that is not successfully delivered to the base station.
In a second aspect, a charging method is provided, where the serving gateway SGW determines data packets that are not successfully delivered to the base station, where the data packets that are not successfully delivered to the base station include at least one of a data packet cached in the SGW, a data packet discarded by the SGW, and a data packet that is failed to be delivered to the base station by the SGW. And the SGW accumulates the flow of the data packets which are not successfully issued to the base station according to the detection rule. And the SGW sends the accumulated flow to the data gateway PGW, so that the PGW determines the flow of the data packet which is successfully sent according to the accumulated flow.
With reference to the implementation manner of the second aspect, in a first possible implementation manner of the second aspect, the detecting rule includes a correspondence between quintuple information and a tariff group, and accumulating traffic of data packets that are not successfully delivered to the base station according to the detecting rule includes: determining a rate group corresponding to a data packet which is not successfully transmitted to a base station according to the quintuple information of the data packet; and accumulating the flow of the data packets which have the same rate group and are not successfully issued to the base station.
With reference to the second aspect or the first possible implementation manner of the second aspect, in a second possible implementation manner, the correspondence between the five-tuple information and the tariff group includes a correspondence between the five-tuple information, the tariff group, and the service identifier.
With reference to the second aspect or any one of the first to second possible implementation manners of the second aspect, in a third possible implementation manner, the SGW determines, according to a processing policy, a data packet that is not successfully delivered to the base station, where the processing policy includes determining, according to at least one of a priority of a bearer, a current network congestion state, a current state of a terminal, operator configuration information, and information from other network elements, a data packet that is not successfully delivered to the base station.
In a third aspect, a charging method is provided, including: the data gateway PGW receives the flow of the data packets which are not successfully sent to the base station from the service gateway SGW, wherein the data packets which are not successfully sent to the base station comprise at least one of the data packets cached in the SGW, the data packets discarded by the SGW and the data packets which are failed to be sent to the base station by the SGW. And when the PGW does not send the charging information of the data packet which is not successfully delivered to the charging system and does not record the flow of the data packet which is not successfully delivered to the base station to the ticket, the PGW determines the flow of the data packet which is successfully delivered according to the flow of the data packet which is not successfully delivered. And the PGW determines the charging information sent to the charging system or determines the charging information recorded to the ticket according to the flow of the data packet successfully issued.
With reference to the implementation manner of the third aspect, in a first possible implementation manner of the third aspect, the PGW further receives a detection rule and receiving time information of a data packet that is not successfully delivered, and the determining, by the PGW, a flow of the data packet that is successfully delivered according to the flow of the data packet that is not successfully delivered includes: and the PGW determines charging information related to the unsuccessfully issued data packet according to the detection rule and the receiving time information. And the PGW determines the flow of the data packet which is successfully delivered according to the charging information related to the data packet which is not successfully delivered and the flow of the data packet which is not successfully delivered.
With reference to the third aspect or the first possible implementation manner of the third aspect, in a second possible implementation manner, the detection rule includes rate group information, the PGW determines, according to the detection rule and the reception time information, charging information related to the unsuccessfully delivered data packet, and the PGW determines, according to the rate group information and the reception time information, charging information related to the unsuccessfully delivered data packet.
With reference to the third aspect or any one of the first to second possible implementation manners of the third aspect, in a third possible implementation manner, the charging information sent to the charging system does not include the flow of the unsuccessfully delivered data packet, and the charging information recorded to the ticket does not include the flow of the unsuccessfully delivered data packet.
In a fourth aspect, a charging method is provided, which includes that a charging system receives traffic of a data packet which is not successfully delivered to a base station, and a detection rule and receiving time information of the data packet. The charging system determines charging information associated with the data packet based on the detection rule and the reception time information. And the charging system determines the flow of the data packet which is successfully issued according to the charging information and the flow of the data packet which is not successfully issued. And the charging system charges according to the flow of the data packet which is successfully issued.
With reference to the implementation manner of the fourth aspect, in a first possible implementation manner of the fourth aspect, the traffic of the data packet that is not successfully delivered to the base station is from one of a serving gateway SGW, a data gateway PGW, and a policy and charging rule function PCRF.
With reference to the fourth aspect or the first possible implementation manner of the fourth aspect, in a second possible implementation manner, the traffic of the data packet that is not successfully delivered to the base station is carried in the charging request or the ticket.
In a fifth aspect, a service gateway is provided, which includes a processing module and a sending module. And the processing module is used for determining the data packets which are not successfully issued to the base station, wherein the data packets which are not successfully issued to the base station comprise at least one of the data packets cached in the SGW, the data packets discarded by the SGW and the data packets which are failed to be issued to the base station by the SGW. And the processing module is also used for accumulating the flow of the data packet which is not successfully transmitted to the base station according to the detection rule. And the sending module is used for sending the accumulated flow to the charging system so that the charging system determines the flow of the data packet which is successfully sent according to the accumulated flow.
With reference to the implementation manner of the fifth aspect, in a first possible implementation manner of the fifth aspect, the sending module is further configured to send, to the charging system, the receiving time information of the data packet that is not successfully delivered to the base station.
With reference to the fifth aspect or the first possible implementation manner of the fifth aspect, in a second possible implementation manner, the sending module is configured to send the accumulated traffic to the charging system through a policy and charging rules function PCRF.
With reference to the fifth aspect or any one of the first to second possible implementation manners of the fifth aspect, in a third possible implementation manner, the sending module is configured to send the accumulated traffic to the charging system through a data gateway PGW.
With reference to the fifth aspect or any one of the first to third possible implementation manners of the fifth aspect, in a fourth possible implementation manner, the detecting rule includes a correspondence between quintuple information and a rate group, and the processing module accumulates, according to the detecting rule, traffic of a data packet that is not successfully delivered to the base station includes: determining a rate group corresponding to a data packet which is not successfully transmitted to a base station according to the quintuple information of the data packet; and accumulating the flow of the data packets which have the same rate group and are not successfully issued to the base station.
With reference to the fifth aspect or any one of the first to fourth possible implementation manners of the fifth aspect, in a fifth possible implementation manner, the sending module is configured to send the accumulated traffic record in a ticket to the charging system.
With reference to the fifth aspect or any one of the first to fifth possible implementation manners of the fifth aspect, in a sixth possible implementation manner, the correspondence between the quintuple information and the tariff includes a correspondence between the quintuple information and the tariff and the service identifier.
With reference to the fifth aspect or any one of the first to sixth possible implementation manners of the fifth aspect, in a seventh possible implementation manner, the processing module is configured to determine, according to a processing policy, a data packet that is not successfully delivered to the base station, where the processing policy includes determining, according to at least one of a priority of a bearer, a current network congestion state, a current state of a terminal, operator configuration information, and information from other network elements, the data packet that is not successfully delivered to the base station.
In a sixth aspect, a service gateway is provided, which includes a processing module and a sending module: and the processing module is used for determining the data packets which are not successfully issued to the base station, wherein the data packets which are not successfully issued to the base station comprise at least one of the data packets cached in the SGW, the data packets discarded by the SGW and the data packets which are failed to be issued to the base station by the SGW. And the processing module is used for accumulating the flow of the data packet which is not successfully issued to the base station according to the detection rule. And the sending module is used for sending the accumulated traffic to the data gateway PGW, so that the PGW determines the traffic of the data packet which is successfully delivered according to the accumulated traffic.
With reference to the implementation manner of the sixth aspect, in a first possible implementation manner of the sixth aspect, the detection rule includes a correspondence between quintuple information and a rate group, and the processing module accumulates traffic of a data packet that is not successfully delivered to the base station according to the detection rule includes: determining a rate group corresponding to a data packet which is not successfully transmitted to a base station according to the quintuple information of the data packet; and accumulating the flow of the data packets which have the same rate group and are not successfully issued to the base station.
With reference to the sixth aspect or the first possible implementation manner of the sixth aspect, in a second possible implementation manner, the correspondence between the five-tuple information and the tariff group includes a correspondence between the five-tuple information, the tariff group, and the service identifier.
With reference to the sixth aspect or any one of the first to second possible implementation manners of the sixth aspect, in a third possible implementation manner, the processing module is configured to determine, according to a processing policy, a data packet that is not successfully delivered to the base station, where the processing policy includes determining, according to at least one of a priority of a bearer, a current network congestion state, a current state of a terminal, operator configuration information, and information from other network elements, the data packet that is not successfully delivered to the base station.
A seventh aspect provides a data gateway, including a receiving module, a processing module, and a sending module: and the receiving module is used for receiving the flow of the data packets which are not successfully sent to the base station from the serving gateway SGW, wherein the data packets which are not successfully sent to the base station comprise at least one of the data packets cached in the SGW, the data packets discarded by the SGW and the data packets which are failed to be sent to the base station by the SGW. And the processing module is used for determining the flow of the data packet which is successfully delivered according to the flow of the data packet which is not successfully delivered when the sending module does not send the charging information of the data packet which is not successfully delivered to the charging system and does not record the flow of the data packet which is not successfully delivered to the base station to the ticket. And the processing module is also used for determining the charging information sent to the charging system or determining the charging information recorded to the ticket according to the flow of the data packet successfully issued.
With reference to the implementation manner of the seventh aspect, in a first possible implementation manner of the seventh aspect, the receiving module is further configured to receive a detection rule and receiving time information of a data packet that is not successfully delivered, and the determining, by the processing module according to the traffic of the data packet that is not successfully delivered, the traffic of the data packet that is successfully delivered includes: and the processing module determines charging information related to the unsuccessfully issued data packet according to the detection rule and the receiving time information. And the processing module determines the flow of the data packet which is successfully issued according to the charging information related to the data packet which is not successfully issued and the flow of the data packet which is not successfully issued.
With reference to the seventh aspect or the first possible implementation manner of the seventh aspect, in a second possible implementation manner, the detection rule includes rate group information, the processing module determines, according to the detection rule and the reception time information, charging information related to the unsuccessfully delivered data packet, and the processing module determines, according to the rate group information and the reception time information, charging information related to the unsuccessfully delivered data packet.
With reference to the seventh aspect or any one of the first to second possible implementation manners of the seventh aspect, in a third possible implementation manner, the charging information sent to the charging system does not include the flow of the unsuccessfully delivered data packet, and the charging information recorded to the ticket does not include the flow of the unsuccessfully delivered data packet.
In an eighth aspect, a charging system is provided, which includes a receiving module and a processing module: and the receiving module is used for receiving the flow of the data packet which is not successfully sent to the base station, the detection rule of the data packet and the receiving time information. And the processing module is used for determining the charging information related to the data packet according to the detection rule and the receiving time information. And the processing module is also used for determining the flow of the data packet which is successfully delivered according to the charging information and the flow of the data packet which is not successfully delivered. And charging according to the flow of the data packet which is successfully issued.
With reference to the implementation manner of the eighth aspect, in a first possible implementation manner of the eighth aspect, the traffic of the data packet that is not successfully delivered to the base station comes from one of the serving gateway SGW, the data gateway PGW, and the policy and charging rule function PCRF.
With reference to the eighth aspect or the first possible implementation manner of the eighth aspect, in a second possible implementation manner, the traffic of the data packet that is not successfully delivered to the base station is carried in the charging request or the ticket.
In a ninth aspect, a computing device is provided that includes: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computing device execution instruction, the processor is connected to the memory through the bus, and when the computing device runs, the processor executes the computer execution instruction stored in the memory, so as to enable the computing device to execute the method according to any one of the possible implementation manners of the first aspect to the fourth aspect and the first aspect to the fourth aspect.
Yet another aspect of the present application provides a computer program product containing instructions which, when run on a computer, cause the computer to perform the method of the above-described aspects.
According to the technical scheme provided by the embodiment of the application, the flow of the data packet which is not successfully issued to the base station is deducted from the charging information, so that the charging accuracy is ensured.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below.
FIG. 1 is a schematic diagram of a network architecture for use with an embodiment of the present application;
FIG. 2 is a diagram illustrating a hardware configuration of a computer device 200 according to an embodiment of the present application;
FIG. 3 is an exemplary flow chart of a charging method 300 according to an embodiment of the present application;
FIG. 4 is an exemplary flow chart of a charging method 400 according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an SGW 500 according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a PGW 600 according to an embodiment of the present application
Fig. 7 is a schematic structural diagram of a charging system 700 according to an embodiment of the present application.
Detailed Description
Fig. 1 is a schematic diagram of a network architecture applied in the embodiment of the present application. The data packet is delivered to the SGW102 via the PGW 101. The PGW 101 generates charging information and sends the charging information to the charging system 103 for charging.
The PGW, SGW and charging system can be realized in the form of computer equipment. Fig. 2 is a hardware structure diagram of a computer device 200 according to an embodiment of the present application. As shown in FIG. 2, computer device 200 includes a processor 202, a memory 204, a communication interface 206, and a bus 208. The processor 202, the memory 204, and the communication interface 206 are communicatively coupled to each other via a bus 208.
The processor 202 may be a general-purpose Central Processing Unit (CPU), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solutions provided in the embodiments of the present Application.
The Memory 204 may be a Read Only Memory (ROM), a static Memory device, a dynamic Memory device, or a Random Access Memory (RAM). The memory 204 may store an operating system 2041 and other application programs 2042. When the technical solution provided by the embodiment of the present application is implemented by software or firmware, program codes for implementing the technical solution provided by the embodiment of the present application are stored in the memory 204 and executed by the processor 202.
The communication interface 206 enables communication with other devices or communication networks using transceiver means such as, but not limited to, a transceiver.
Bus 208 may include a path that transfers information between various components, such as processor 202, memory 204, and communication interface 206.
When the PGW 101 is implemented by the computer device 200, the processor 202 is configured to execute the program code stored in the memory 204 for implementing the technical solution provided by the embodiment of the present application, so as to implement the method shown in the embodiments of fig. 3 to 4.
When the SGW102 is implemented by the computer device 200, the processor 202 is configured to execute the program code stored in the memory 204 for implementing the technical solution provided by the embodiment of the present application, so as to implement the method shown in the embodiments of fig. 3 to 4.
When the billing system 103 is implemented by the computer device 200, the processor 202 is configured to execute the program code stored in the memory 204 for implementing the technical solution provided by the embodiment of the present application, so as to implement the method shown in the embodiments of fig. 3 to 4.
Fig. 3 is an exemplary flow chart of a charging method 300 according to an embodiment of the present application. The charging method 300 may be performed by the SGW102 and the charging system 103 shown in fig. 1.
S301, the SGW determines data packets which are not successfully issued to the base station, wherein the data packets which are not successfully issued to the base station comprise at least one of data packets cached in the SGW, data packets discarded by the SGW and data packets failed to be issued to the base station by the SGW.
And the SGW determines the data packets needing to be buffered and the data packets needing to be discarded according to the processing strategy. And the SGW records the five-tuple of the cached data packet and the discarded five-tuple of the data packet, and determines the data packet which is not successfully sent to the base station according to the five-tuple.
The processing policy may be to determine a data packet that is not successfully delivered to the base station according to at least one of a priority of the bearer, a current network congestion state, a current state of the terminal, operator configuration information, and information from other network elements. The current state of the terminal may be ECM-idle (evolved Packet System Connection Management idle) or ECM-connected (evolved Packet System Connection managed), and the operator configuration information may be an upper limit of a buffer data size. For example, when the terminal is in the ECM-IDLE state and a downstream Mobility Management Entity (MME) is already in a congested state, packets transmitted on a bearer with a low priority are dropped. As another example, the number of buffered packets is discarded when the upper limit is reached. The information from other network elements may be information from a Mobility Management Entity (MME) or information from a Serving GPRS Support Node (SGSN).
S302, the SGW accumulates the flow of the data packet which is not successfully issued to the base station according to the detection rule.
Specifically, the detection rule includes a correspondence between quintuple information and a rate group. And the SGW determines the rate groups corresponding to the data packets which are not successfully transmitted to the base station according to the quintuple information of the data packets, and accumulates the unsuccessfully transmitted data packets with the same rate groups. For example, the quintuple information is source address information, the tariff group is A, B, C, the corresponding relationship is that when the source address information is a, the tariff group a is corresponding, when the source address information is B, the tariff group B is corresponding, and when the source address information is C, the tariff group C is corresponding. The corresponding relation between the quintuple information and the rate group comprises the corresponding relation between the quintuple information and the rate group and the service identifier. For example, the quintuple information is source address information, the rating group is A, B, C, the service identifier is S1, S2, S3, the correspondence is that when the source address information is a, the rating group a and the service identifier S1 are corresponded, when the source address information is B, the rating group B and the service identifier S2 are corresponded, and when the source address information is C, the rating group C and the service identifier S3 are corresponded.
When the detection rule is the corresponding relation between the quintuple information and the rate group and the service identifier, the SGW may accumulate the traffic of the data packet which is not successfully delivered to the base station according to the rate group. For example, the data packets that are not successfully delivered include the data packet with the rate group a and the data packet with the rate group B. And the SGW accumulates the flow of the data packets with the rate group A to obtain the total flow of the data packets which are not successfully issued with the rate group A. And the SGW accumulates the flow of the data packets with the rate group B to obtain the total flow of the data packets which are not successfully issued with the rate group B. The SGW may also accumulate the flow of data packets that have not been successfully delivered to the base station according to the tariff group and the service identifier. For example, the data packets with the rate group a and the service identifier S1 and the data packets with the rate group B and the service identifier S2 exist in the data packets that are not successfully delivered. And the SGW accumulates the flow of the data packets with the rate group A and the service identifier S1 to obtain the total flow of the data packets which are not successfully issued and have the rate group A and the service identifier S1. And the SGW accumulates the flow of the data packets with the rate group B and the service identifier S2 to obtain the total flow of the data packets which are not successfully issued and have the rate group B and the service identifier S2.
S303, the SGW sends the accumulated flow to a charging system, so that the charging system determines the flow of the data packet which is successfully sent according to the accumulated flow.
And the SGW also sends the detection rule and the receiving time information of the data packet which is not successfully sent to the base station to the charging system.
The SGW may directly send the accumulated traffic to the Charging system, may send the accumulated traffic to the Charging system through a Policy and Charging Rules Function (PCRF), and may send the accumulated traffic to the Charging system through the PGW.
When the SGW directly sends the accumulated traffic to the charging system, the SGW may record the information of the data packet that is not successfully delivered to the base station in a ticket and send the ticket to the charging system. The information includes detection rules, receiving time information, traffic, etc. of data packets which are not successfully issued to the base station.
When the SGW sends the accumulated traffic to the charging system through the PCRF or the PGW, the SGW also sends, to the charging system through the PCRF or the PGW, a detection rule, reception time information, and the like of a data packet that is not successfully delivered to the base station. When the SGW sends the accumulated flow to the charging system through the PCRF, the PCRF forwards the information to the charging system after receiving the detection rules, the receiving time information and the flow information of the data packet which is not successfully sent to the base station from the SGW. Therefore, modification of the SGW dialogue single format can be avoided, and the burden of the SGW is relieved.
When the SGW sends the accumulated traffic to the charging system through the PGW, after receiving information (including detection rules, reception time information, and traffic information) of a data packet which is not successfully delivered to the base station from the SGW, the PGW determines that charging information related to the data packet which is not successfully delivered to the base station has been sent to the charging system, or records information of the data packet which is not successfully delivered to the base station to a ticket. The PGW may process information of a data packet that is not successfully delivered to the base station in two ways. First, the PGW generates a charging request according to the information, and sends the charging request to the charging system. The charging request may be sent to the charging system along with other charging information currently generated when a charging event occurs. The charging event may be quota exhaustion or a change in QoS parameters, etc. And secondly, recording the information in a call ticket by the PGW, and sending the call ticket to a charging system.
S304, the charging system receives the flow of the data packet which is not successfully sent to the base station, and the detection rule and the receiving time information of the data packet.
S305, the charging system determines the charging information related to the data packet which is not successfully transmitted to the base station according to the detection rule and the receiving time information, and determines the flow of the data packet which is successfully transmitted according to the charging information and the flow of the data packet which is not successfully transmitted.
S306, the charging system charges according to the flow of the data packet which is successfully issued.
According to the technical scheme provided by the embodiment of the application, the flow of the data packet which is not successfully issued to the base station is deducted from the charging information, so that the charging accuracy is ensured.
Fig. 4 is an exemplary flow chart of a charging method 400 according to an embodiment of the present application. The charging method 400 may be performed by the PGW 101, the SGW102, and the charging system 103 shown in fig. 1. In the embodiment shown in fig. 4, the PGW determines the traffic of the data packet that is successfully delivered according to the traffic of the data packet that is not successfully delivered to the base station from the SGW, and sends the traffic of the data packet that is successfully delivered to the charging system for charging.
S401, the SGW determines data packets which are not successfully issued to the base station, wherein the data packets which are not successfully issued to the base station comprise at least one of data packets cached in the SGW, data packets discarded by the SGW and data packets failed to be issued to the base station by the SGW.
S402, the SGW accumulates the flow of the data packet which is not successfully issued to the base station according to the detection rule.
The specific contents of S401 and S402 can refer to S301 and S302 in the embodiment of fig. 3, and are not described herein again.
And S403, the SGW sends the accumulated traffic to the PGW.
S404, the PGW receives the traffic of the data packet which is not successfully delivered to the base station from the SGW.
S405, when the PGW does not send the charging information of the unsuccessfully delivered data packet to the charging system and does not record the traffic of the data packet unsuccessfully delivered to the base station to the ticket, the PGW determines the traffic of the successfully delivered data packet according to the traffic of the unsuccessfully delivered data packet.
The PGW further receives the detection rule and the reception time information of the unsuccessfully delivered data packet, and the determining, by the PGW, the traffic of the successfully delivered data packet according to the traffic of the unsuccessfully delivered data packet includes:
and the PGW determines charging information related to the unsuccessfully issued data packet according to the detection rule and the receiving time information. And the PGW determines the flow of the data packet which is successfully delivered according to the charging information related to the data packet which is not successfully delivered and the flow of the data packet which is not successfully delivered. The relevant content of the detection rule can refer to the step S302 in the embodiment of fig. 3. And the PGW determines charging information related to the unsuccessfully issued data packet according to the receiving time information and the rate group in the detection rule.
For example, the receiving time information is 15:20-15:30, the PGW determines that the charging information of the rate group a generated in the time period of 15:20-15:30 is the charging information related to the data packet which is not successfully delivered, and the charging information is not sent to the charging system. If the used flow recorded in the charging information is 10M, and the flow of the unsuccessfully delivered data packet is 2M, the PGW determines again that the flow of the successfully delivered data packet is 10M-2M — 8M.
S406, the PGW determines the charging information sent to the charging system or determines the charging information recorded to the ticket according to the flow of the successfully issued data packet.
The charging information sent to the charging system or the charging information recorded to the ticket includes the flow of the data packet successfully delivered and does not include the flow of the data packet unsuccessfully delivered. The charging information may also include a rate group of the unsuccessfully delivered data packet.
S407, the PGW sends the charging information to the charging system, or sends a ticket.
The PGW may send charging information to the charging system through the charging request. The PGW sends the flow of the data packet that is successfully delivered to the charging system by sending the charging information or the ticket to the charging system.
S408, the charging system receives the charging information or the call ticket from the PGW.
And S409, the charging system charges according to the charging information or the call ticket.
According to the technical scheme provided by the embodiment of the application, the flow of the data packet which is not successfully issued to the base station is deducted from the charging information, so that the charging accuracy is ensured.
Fig. 5 is a schematic structural diagram of an SGW 500 according to an embodiment of the present application. SGW 500 includes a processing module 502 and a transmitting module 504. The SGW is the SGW102 of fig. 1, the computer device of fig. 2, and the SGW in the embodiments of fig. 3 and 4. The processing module 502 may be configured to perform S301 and S302 in the embodiment of fig. 3, and S401 and S402 in the embodiment of fig. 4. The sending module 504 may be configured to perform S303 in the embodiment of fig. 3 and S403 in the embodiment of fig. 4.
Fig. 6 is a schematic structural diagram of a PGW 600 according to an embodiment of the present application. PGW 500 includes a receiving module 602, a processing module 604, and a transmitting module 606. The PGW is PGW 101 of fig. 1, the computer device of fig. 2, and the PGW in the embodiments of fig. 3 and 4. The receiving module 602, the processing module 604 and the sending module 606 may be configured to perform the relevant steps in S303 in the embodiment of fig. 3. The receiving module 602 may be used to execute S404 in the embodiment of fig. 4. The processing module 604 may be used to perform S405 and S406 in the embodiment of fig. 4. The sending module 606 may be used to execute S407 in the embodiment of fig. 4.
Fig. 7 is a schematic structural diagram of a charging system 700 according to an embodiment of the present application. The billing system 700 includes a receiving module 702 and a processing module 704. The billing system is not shown in the billing system 103 of fig. 1, the computer device of fig. 2, and the billing system of the embodiments of fig. 3 and 4. The receiving module 702 may be used to execute S304 in the fig. 3 embodiment and S408 in the fig. 4 embodiment. The processing module 704 may be used to execute S305 and S306 in the embodiment of fig. 3, and S409 in the embodiment of fig. 4.
It should be noted that although the general computer architecture 200 shown in fig. 2 only shows the processor 202, the memory 204, the communication interface 206 and the bus 208, in a particular implementation, it should be understood by those skilled in the art that the SGW, PGW and billing system described above also contain other components necessary to achieve proper operation. Meanwhile, according to specific needs, it should be understood by those skilled in the art that the SGW, the PGW and the billing system described above may further include hardware devices for implementing other additional functions. Furthermore, those skilled in the art will appreciate that the SGW, PGW and billing system described above may also contain only those components necessary to implement the embodiments of the present application, and need not contain all of the components shown in fig. 2.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (27)

1. A charging method, comprising the steps of:
the method comprises the steps that a Service Gateway (SGW) determines data packets which are not successfully issued to a base station, wherein the data packets which are not successfully issued to the base station comprise at least one of data packets cached in the SGW, data packets discarded by the SGW and data packets failed to be issued to the base station by the SGW;
the SGW accumulates the flow of the data packets which are not successfully issued to the base station according to a detection rule;
the SGW sends the accumulated flow of the data packet which is not successfully issued to the base station to a data gateway PGW, and when the charging information of the data packet which is not successfully issued is not sent to a charging system through the data gateway PGW and the flow of the data packet which is not successfully issued to the base station is not recorded to a ticket, the flow of the data packet which is not successfully issued to the base station is used for the data gateway PGW to determine the flow of the data packet which is successfully issued so as to determine the charging information sent to the charging system, so that the charging system can charge according to the charging information;
the SGW further sends, to the data gateway PGW, a detection rule and reception time information of the data packet unsuccessfully delivered to the base station, where the detection rule and the reception time information are used to cooperate with the data gateway PGW to determine the charging information, the detection rule is a correspondence between quintuple information and a rate group and a service identifier, and the reception time information and the rate group cooperate to determine charging information related to the unsuccessfully delivered data packet and determine a flow rate of the successfully delivered data packet.
2. The method of claim 1, wherein the SGW sends the accumulated traffic to the charging system via a Policy and Charging Rules Function (PCRF).
3. The method of claim 1, wherein the SGW sends the accumulated traffic to the charging system through a data gateway (PGW).
4. The method according to any one of claims 1 to 3, wherein the accumulating the traffic of the data packets unsuccessfully sent to the base station according to the detection rule comprises:
determining the rate group corresponding to the data packet which is not successfully transmitted to the base station according to the quintuple information of the data packet;
and accumulating the flow of the data packets which have the same rate group and are not successfully issued to the base station.
5. The method according to any of claims 1 to 3, wherein the SGW sends the accumulated traffic record in a ticket to the charging system.
6. The method according to any of claims 1 to 3, wherein the SGW determines the data packets which are not successfully delivered to the base station according to a processing policy, and the processing policy includes determining the data packets which are not successfully delivered to the base station according to at least one of a priority of a bearer, a current network congestion state, a current state of a terminal, operator configuration information, and information from other network elements.
7. A charging method, comprising the steps of:
a data gateway PGW receives the flow of data packets which are not successfully issued to a base station from a service gateway SGW, wherein the data packets which are not successfully issued to the base station comprise at least one of data packets cached in the SGW, data packets discarded by the SGW and data packets which are failed to be issued to the base station by the SGW;
when the PGW does not send the charging information of the data packet which is not successfully delivered to a charging system and does not record the flow of the data packet which is not successfully delivered to the base station to a ticket, the PGW determines the flow of the data packet which is successfully delivered according to the flow of the data packet which is not successfully delivered;
the PGW determines charging information sent to the charging system or determines charging information recorded to a ticket according to the flow of the data packet successfully issued;
the data gateway PGW also receives the detection rule and the receiving time information of the data packet which is sent by the SGW and is not successfully issued to the base station, and records the detection rule and the receiving time information to the ticket, the detection rule and the receiving time information are used for being matched with the data gateway PGW to determine the charging information, the detection rule is a corresponding relation between quintuple information and a rate group and a service identifier, and the receiving time information and the rate group are matched to determine the charging information related to the data packet which is not successfully issued and determine the flow of the data packet which is successfully issued.
8. The method of claim 7, wherein the detection rule includes rate group information, the PGW determines charging information related to the unsuccessfully delivered data packet according to the detection rule and the receiving time information, and the PGW determines charging information related to the unsuccessfully delivered data packet according to the rate group information and the receiving time information.
9. The method according to any one of claims 7 to 8, wherein the charging information sent to the charging system does not include the flow of the unsuccessfully delivered data packet, and the charging information recorded to the ticket does not include the flow of the unsuccessfully delivered data packet.
10. A charging method, comprising the steps of:
the method comprises the steps that a charging system receives flow of a data packet which is not successfully issued to a base station, and a detection rule and receiving time information of the data packet, wherein the flow of the data packet which is not successfully issued to the base station, the detection rule and the receiving time information are sent by a service gateway SGW and are recorded in a dialogue list by a data gateway PGW, and when the charging information of the data packet which is not successfully issued is not sent to the charging system through the data gateway PGW and the flow of the data packet which is not successfully issued to the base station is not recorded in a ticket, the flow of the data packet which is not successfully issued to the base station is used for the data gateway PGW to determine the flow of the data packet which is successfully issued;
the charging system determines charging information related to the data packet according to the detection rule and the receiving time information, wherein the detection rule is a corresponding relation between quintuple information and a rate group and a service identifier, and the receiving time information and the rate group are matched to determine the charging information related to the unsuccessfully issued data packet and determine the flow of the successfully issued data packet;
the charging system determines the flow of the data packet which is successfully issued according to the charging information and the flow of the data packet which is not successfully issued;
and the charging system charges according to the flow of the data packet which is successfully transmitted.
11. The method of claim 10, wherein the flow of the data packets that are not successfully delivered to the base station is also from a Policy and Charging Rules Function (PCRF).
12. The method according to claim 10 or 11, wherein the traffic of the data packets which are not successfully delivered to the base station is carried in the charging request or the ticket.
13. A service gateway, comprising a processing module and a sending module:
the processing module is configured to determine a data packet that is not successfully delivered to a base station, where the data packet that is not successfully delivered to the base station includes at least one of a data packet cached in a serving gateway SGW, a data packet discarded by the SGW, and a data packet that is failed to be delivered to the base station by the SGW;
the processing module is further configured to accumulate the traffic of the data packet that is not successfully delivered to the base station according to the detection rule;
the sending module is configured to send the accumulated flow of the data packet unsuccessfully issued to the base station to a data gateway PGW, when the charging information of the unsuccessfully issued data packet is not sent to a charging system through the data gateway PGW and the flow of the data packet unsuccessfully issued to the base station is not recorded in a ticket, the flow of the data packet unsuccessfully issued to the base station is used for the data gateway PGW to determine the flow of the data packet successfully issued so as to determine the charging information sent to the charging system, so that the charging system performs charging according to the charging information, and also sends a detection rule and receiving time information of the data packet unsuccessfully issued to the base station to the charging system, where the detection rule and the receiving time information are used to determine the charging information in cooperation with the data gateway PGW, and the detection rule is a corresponding relationship between quintuple information and a rate group and a service identifier, and the receiving time information and the rate group are matched to determine charging information related to the data packet which is not successfully transmitted and determine the flow of the data packet which is successfully transmitted.
14. The gateway of claim 13, wherein the sending module is configured to send the accumulated traffic to the charging system through a policy and charging rules function PCRF.
15. The gateway according to any of claims 13 to 14, wherein the processing module accumulating the traffic of the data packets that are not successfully delivered to the base station according to the detection rule comprises:
determining the rate group corresponding to the data packet which is not successfully transmitted to the base station according to the quintuple information of the data packet;
and accumulating the flow of the data packets which have the same rate group and are not successfully issued to the base station.
16. The gateway according to any of claims 13 to 14, wherein the sending module is configured to send the accumulated traffic record in a ticket to the charging system.
17. The gateway according to any of claims 13 to 14, wherein the processing module is configured to determine the data packets that are not successfully delivered to the base station according to a processing policy, where the processing policy includes determining the data packets that are not successfully delivered to the base station according to at least one of a priority of a bearer, a current network congestion state, a current state of a terminal, operator configuration information, and information from other network elements.
18. A data gateway, comprising a receiving module, a processing module and a sending module:
the receiving module is configured to receive traffic of data packets that are not successfully delivered to a base station from a serving gateway SGW, where the data packets that are not successfully delivered to the base station include at least one of a data packet cached in the SGW, a data packet discarded by the SGW, and a data packet that is failed to be delivered to the base station by the SGW;
the processing module is used for determining the flow of the data packet which is successfully delivered according to the flow of the data packet which is not successfully delivered when the sending module does not send the charging information of the data packet which is not successfully delivered to the charging system and does not record the flow of the data packet which is not successfully delivered to the base station to a ticket;
the processing module is further configured to determine charging information sent to the charging system according to the flow of the successfully issued data packet, or determine charging information recorded to a ticket;
the receiving module further receives a detection rule and receiving time information of the data packet which is sent by the SGW and is not successfully sent to the base station, and records the detection rule and the receiving time information to the ticket, the detection rule and the receiving time information are used for being matched with the data gateway PGW to determine the charging information, the detection rule is a corresponding relation between quintuple information and a rate group and a service identifier, and the receiving time information and the rate group are matched to determine the charging information related to the data packet which is not successfully sent and determine the flow of the data packet which is successfully sent.
19. The gateway of claim 18, wherein the detection rule includes rate group information, and the processing module determines charging information associated with the unsuccessfully delivered data packet according to the detection rule and the receiving time information, and includes the processing module determining charging information associated with the unsuccessfully delivered data packet according to the rate group information and the receiving time information.
20. The gateway according to any one of claims 18 to 19, wherein the charging information sent to the charging system does not include the flow of the unsuccessfully delivered data packet, and the charging information recorded to the ticket does not include the flow of the unsuccessfully delivered data packet.
21. A charging system is characterized by comprising a receiving module and a processing module:
the receiving module is configured to receive traffic of a data packet that is not successfully delivered to the base station, and a detection rule and receiving time information of the data packet, where the traffic of the data packet that is not successfully delivered to the base station, the detection rule and the receiving time information are sent by a serving gateway SGW and recorded in a dialog list by a data gateway PGW, and when charging information of the data packet that is not successfully delivered is not sent to a charging system through the data gateway PGW and the traffic of the data packet that is not successfully delivered to the base station is not recorded in a ticket, the traffic of the data packet that is not successfully delivered to the base station is used for the data gateway PGW to determine the traffic of the data packet that is successfully delivered;
the processing module is used for determining charging information related to the data packet according to the detection rule and the receiving time information, the detection rule is a corresponding relation between quintuple information and a rate group and a service identifier, and the receiving time information and the rate group are matched to determine the charging information related to the data packet which is not successfully delivered and determine the flow of the data packet which is successfully delivered;
the processing module is further configured to determine the flow rate of the data packet that is successfully delivered according to the charging information and the flow rate of the data packet that is not successfully delivered; and
and charging according to the flow of the data packet which is successfully issued.
22. The charging system of claim 21, wherein the flow of the data packets that are not successfully delivered to the base station comes from a Policy and Charging Rules Function (PCRF).
23. The charging system according to claim 21 or 22, wherein the traffic of the data packets which are not successfully delivered to the base station is carried in the charging request or the ticket.
24. A computing device, comprising: a processor, a memory, a bus, and a communication interface; the memory is used for storing computing device execution instructions, the processor is connected with the memory through the bus, and when the computing device runs, the processor executes the computing device execution instructions stored in the memory so as to enable the computing device to execute the method of any one of claims 1 to 6.
25. A computing device, comprising: a processor, a memory, a bus, and a communication interface; the memory is used for storing computing device execution instructions, the processor is connected with the memory through the bus, and when the computing device runs, the processor executes the computing device execution instructions stored in the memory to enable the computing device to execute the method of any one of claims 7 to 9.
26. A computing device, comprising: a processor, a memory, a bus, and a communication interface; the memory is used for storing computing device execution instructions, the processor is connected with the memory through the bus, and when the computing device runs, the processor executes the computing device execution instructions stored in the memory to enable the computing device to execute the method of any one of claims 10 to 12.
27. A communications charging system comprising a service gateway as claimed in any of claims 13 to 17, a data gateway as claimed in any of claims 18 to 20 and a charging system as claimed in any of claims 21 to 23.
CN201710105127.3A 2017-02-25 2017-02-25 Charging method and device Active CN108696363B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201710105127.3A CN108696363B (en) 2017-02-25 2017-02-25 Charging method and device
PCT/CN2018/073655 WO2018153193A1 (en) 2017-02-25 2018-01-22 Charging method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710105127.3A CN108696363B (en) 2017-02-25 2017-02-25 Charging method and device

Publications (2)

Publication Number Publication Date
CN108696363A CN108696363A (en) 2018-10-23
CN108696363B true CN108696363B (en) 2022-03-08

Family

ID=63253518

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710105127.3A Active CN108696363B (en) 2017-02-25 2017-02-25 Charging method and device

Country Status (2)

Country Link
CN (1) CN108696363B (en)
WO (1) WO2018153193A1 (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101431423A (en) * 2008-12-24 2009-05-13 华为技术有限公司 Reduction method and apparatus for user service flow accounting
CN101547432A (en) * 2008-03-28 2009-09-30 华为技术有限公司 Information-updating method and server
CN103067903A (en) * 2012-12-31 2013-04-24 华为技术有限公司 Charging method and device and system
CN103718579A (en) * 2013-06-20 2014-04-09 华为技术有限公司 Charge processing method, device and system
WO2014076094A1 (en) * 2012-11-13 2014-05-22 Ntt Docomo, Inc. Method and apparatus for congestion status notification
CN105025457A (en) * 2014-04-28 2015-11-04 中国电信股份有限公司 LTE flow charging system and method, and PGW
CN105472590A (en) * 2014-08-15 2016-04-06 中国电信股份有限公司 Method and system for charging data traffic in enhanced high rate packet data (eHRPD) network

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247238B (en) * 2007-02-14 2011-10-05 华为技术有限公司 Method and system for data flux statistics
EP3567800B1 (en) * 2011-05-06 2022-06-22 Huawei Technologies Co., Ltd. Method, system and gateway for charging for data service
US8856213B2 (en) * 2011-08-11 2014-10-07 Verizon Patent And Licensing Inc. Provisioning a moderated data service using a syndicated radio access network (RAN)
CN103856926A (en) * 2012-11-28 2014-06-11 中兴通讯股份有限公司 Charging method and strategy execution, strategy and charging control function device
WO2015039307A1 (en) * 2013-09-18 2015-03-26 华为技术有限公司 Charging method and device

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101547432A (en) * 2008-03-28 2009-09-30 华为技术有限公司 Information-updating method and server
CN101431423A (en) * 2008-12-24 2009-05-13 华为技术有限公司 Reduction method and apparatus for user service flow accounting
WO2014076094A1 (en) * 2012-11-13 2014-05-22 Ntt Docomo, Inc. Method and apparatus for congestion status notification
CN103067903A (en) * 2012-12-31 2013-04-24 华为技术有限公司 Charging method and device and system
CN103718579A (en) * 2013-06-20 2014-04-09 华为技术有限公司 Charge processing method, device and system
CN105025457A (en) * 2014-04-28 2015-11-04 中国电信股份有限公司 LTE flow charging system and method, and PGW
CN105472590A (en) * 2014-08-15 2016-04-06 中国电信股份有限公司 Method and system for charging data traffic in enhanced high rate packet data (eHRPD) network

Also Published As

Publication number Publication date
WO2018153193A1 (en) 2018-08-30
CN108696363A (en) 2018-10-23

Similar Documents

Publication Publication Date Title
WO2017088501A1 (en) Charging method and device
EP3883180B1 (en) Charging method, apparatus, computer program and system.
EP2505005B1 (en) System and method for providing a sequence numbering mechanism in a network environment
CN108337652B (en) Method and device for detecting flow fraud
US9461829B2 (en) Method and apparatus for controlling charging in a communication network
CN107040674B (en) Charging method, device and system
JP6407170B2 (en) Method, apparatus and system for aggregating billing information
US20150271342A1 (en) Network resource allocation in communication networks
US20220394134A1 (en) Method and Apparatus for Information Exchange in Online Charging
EP2779541A1 (en) Method and apparatus for controlling charging by using volume information of data
CN108696363B (en) Charging method and device
CN108259196B (en) Quota management method and quota management device
EP2705655A2 (en) Systems and/or methods for delivering notifications on a communications network
CN108024222B (en) Traffic ticket generating method and device
CN102421106B (en) A kind of by quantity monitoring method and system
US20170026524A1 (en) Charging method and apparatus
US11108914B2 (en) Method and system for revenue maximization in a communication network
CN110324802B (en) Flow charging method and MME
CN109936829B (en) Method, system and charging system for improving network disconnection precision
CN109995540B (en) Charging method, system, equipment and medium for event value-added service
EP3849232A1 (en) Method and device for processing gx session exception
CN108574579B (en) Processing method and device for telecommunication charging and telecommunication system
CN108270580B (en) Reminding method, device and system for online charging
CN110636518B (en) Performance data statistical method and related equipment
JP6769794B2 (en) Communication data amount management device, communication data amount management method, and communication data amount management program

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant