CN102202281A - Ticket processing method and system - Google Patents
Ticket processing method and system Download PDFInfo
- Publication number
- CN102202281A CN102202281A CN2010101401491A CN201010140149A CN102202281A CN 102202281 A CN102202281 A CN 102202281A CN 2010101401491 A CN2010101401491 A CN 2010101401491A CN 201010140149 A CN201010140149 A CN 201010140149A CN 102202281 A CN102202281 A CN 102202281A
- Authority
- CN
- China
- Prior art keywords
- ticket
- packet data
- gateway
- data network
- module
- 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.)
- Granted
Links
Images
Abstract
The invention discloses a ticket processing method and a ticket processing system. The method comprises the following steps that: a packet data network gateway and/or a serving gateway set/sets indication information in tickets, and transmit/transmits the tickets to a charging gateway, wherein the indication information is used for indicating packet data network connection with the tickets; and the charging gateway combines the tickets belonging to the same packet data network connection according to the indication information in the received tickets. By the method and the system, transmission resources and storage resources are saved, and the processing efficiency of a charging center is improved.
Description
Technical field
The present invention relates to the communications field, in particular to a kind of call bill processing method and system.
Background technology
Current third generation partner program (3rd Generation Partnership Project, abbreviate 3GPP as) grouping system (the Evolved Packet System of the evolution of the R8 of definition in the wireless communication standard tissue, abbreviate EPS as) in, basic granularity is carrying (Bearer).Fig. 1 is (the Packet Data Network of Packet Data Network of prior art, abbreviate PDN as) connect the schematic diagram of professional each carrying of duration of existence, as shown in Figure 1, in PDN, PDN connects professional duration of existence and can remain and set up a carrying, come to provide Internet protocol (the Internet Protocol of " always online " to UE, abbreviate IP as) connect, this carrying is called default bearing, service quality (the Quality of Service that initially provides is provided, abbreviate QoS as) class letter (QCI), distribute and maintenance priority (Allocation andRetention Priority abbreviates ARP as).When user's service needed different QoS ensured, network can be created other EPS carryings in identical PDN connects, be called dedicated bearing.That is, in connecting, a PDN may have a plurality of carryings.
Gateway (Serving Gateway abbreviates S-GW as) and packet data network gateway (PDN Gateway abbreviates P-GW as) network element can be collected the charge information of each carrying, and are each carrying output ticket (SGW-CDR and PGW-CDR).According to time or traffic threshold, a carrying can produce a plurality of partial CDRs, because carrying is discerned by a unique sign Charging ID, therefore, the Charging ID of these partial CDRs is identical.Such PDN connects can produce a lot of partial CDRs.
Fig. 2 is charging gateway of the prior art (Charging Gateway Function, abbreviate CGF as) handle the schematic diagram of ticket, CGF collects SGW-CDR and PGW-CDR ticket from S-GW and P-GW network element, merges processing, and the ticket after handling is sent to the charging center.Existing merging handle can Charging ID is identical SGW-CDR and PGW-CDR partial CDR merge, i.e. the partial CDR of same carrying can merge, and has reduced the quantity of ticket.But, have a lot of with carrying of same PDN join dependency, and, the inventor finds, because these tickets are tickets of same user, have a lot of identical information, in ticket transmission and preservation process, there is information redundancy, waste unnecessary transfer resource and storage resources, and increased the burden of charging center processing ticket.
Summary of the invention
Main purpose of the present invention is to provide a kind of ticket processing scheme, to address the above problem at least.
According to an aspect of the present invention, a kind of call bill processing method is provided, this method may further comprise the steps: packet data network gateway and/or gateway are provided with indication information in ticket, and ticket is sent to charging gateway, and indication information is used to indicate the affiliated Packet Data Network of ticket to connect; And charging gateway merges according to the ticket that the indication information that carries in the ticket that receives will belong to the connection of same Packet Data Network.
Further, charging gateway merges and comprises according to belonging to ticket that same Packet Data Network connects: charging gateway will merge from the ticket that same Packet Data Network is connected that belongs to of gateway and packet data network gateway respectively.
Further, charging gateway will belong to after ticket that same Packet Data Network connects merges, and said method is further comprising the steps of: charging gateway is according to the quantity of the bearing identification statistics carrying in the ticket after merging; And the quantity of the carrying of carrying in quantity and the default bearing ticket with the carrying after the statistics is compared, if ticket identical then after will merging sends to the charging center, otherwise continuation reception ticket also merges.
Further, gateway or packet data network gateway fill in the carrying quantity of all establishments the carrying amount field of default bearing ticket after default bearing finishes.
Further, information that can the unique identification packet data network gateway connects with the Packet Data Network under the indication ticket with the information that can be connected in the unique identification Packet Data Network under the same packet data network gateway is linked together.
Further, information that can the unique identification packet data network gateway is the address of packet data gateway.
According to a further aspect in the invention, a kind of ticket treatment system also is provided, comprise: packet data network gateway, gateway and charging gateway, this packet data network gateway and gateway comprise: module is set, be used at ticket indication information being set, indication information is used to indicate the affiliated Packet Data Network of ticket to connect; Sending module is used for ticket is sent to charging gateway; Charging gateway comprises: receiver module is used to receive the ticket from packet data network gateway and/or gateway; Merge module, be used for to belong to the ticket that same Packet Data Network connects and merge according to the indication information that the ticket that receives carries.
Further, merge module and comprise: first merges module, is used for the ticket that same Packet Data Network connects from belonging to of gateway is merged; Second merges module, is used for the ticket that same Packet Data Network connects from belonging to of packet data network gateway is merged.
Further, charging gateway also comprises: statistical module is used for the quantity according to the bearing identification statistics carrying of the ticket after merging; Sending module is used for the ticket after merging is sent to the charging center; And, calling module, the quantity that is used for the carrying that quantity and default bearing ticket with the carrying after the statistics carry is compared, if ticket identical then that call after sending module will merge sends to the charging center, otherwise, call receiver module and merge module and continue to receive ticket and merge.
Further, module being set also is used for the carrying quantity of all establishments being filled in the carrying amount field of default bearing ticket after default bearing finishes.
Further, the information that module can the unique identification packet data network gateway being set is indication information with the information setting that can be connected in the unique identification Packet Data Network under the same packet data network gateway.
Further, module is set the address setting of packet data gateway is information that can the unique identification packet data network gateway.
By the present invention, adopt packet data network gateway and/or gateway that indication information is set in ticket, and ticket is sent to charging gateway, this indication information is used to indicate the affiliated Packet Data Network of ticket to connect; Charging gateway merges according to the ticket that the indication information that carries in the ticket that receives will belong to the connection of same Packet Data Network, solved ticket information redundancy after the merging that causes according to the carrying Consolidate CDR in the correlation technique, and then the problem that causes wasting transfer resource and storage resources and influence the charging center treatment effeciency, save transfer resource and storage resources, improved the treatment effeciency of charging center.
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, and illustrative examples of the present invention and explanation thereof are used to explain the present invention, do not constitute improper qualification of the present invention.In the accompanying drawings:
Fig. 1 is the schematic diagram that the PDN of prior art connects professional each carrying of duration of existence;
Fig. 2 is the schematic diagram that CGF of the prior art handles ticket;
Fig. 3 is the structured flowchart according to the ticket treatment system of the embodiment of the invention;
Fig. 4 is the ticket treatment system preferred construction block diagram one according to the embodiment of the invention;
Fig. 5 is the ticket treatment system preferred construction block diagram two according to the embodiment of the invention;
Fig. 6 is the flow chart according to the call bill processing method of the embodiment of the invention; And,
Fig. 7 is the schematic diagram that same PDN join dependency ticket is merged processing according to the CGF of the embodiment of the invention.
Embodiment
Hereinafter will describe the present invention with reference to the accompanying drawings and in conjunction with the embodiments in detail.Need to prove that under the situation of not conflicting, embodiment and the feature among the embodiment among the application can make up mutually.
In following examples, CGF is used to receive the ticket of P-GW or S-GW transmission and merge processing, and P-GW and S-GW generate ticket, and ticket is sent to CGF.
Fig. 3 is the structured flowchart according to the ticket treatment system of the embodiment of the invention, and as shown in Figure 3, this system comprises: P-GW, S-GW and CGF.Wherein, P-GW and S-GW include: module 32, sending module 34 are set, and CGF comprises: receiver module 36, merging module 38.Be explained below.
Module 32 is set, is used at ticket indication information being set, indication information is used to indicate the affiliated Packet Data Network of ticket to connect; Sending module 34 is coupled to module 32 is set, and this module is used for ticket is sent to CGF; Receiver module 36 is used to receive the ticket from P-GW and/or S-GW; Merge module 38 and be coupled to receiver module 36, this module is used for will belonging to the ticket that same Packet Data Network connects according to the indication information that the ticket that receives carries and merges.
Pass through said system, can realize ticket being merged with the PDN unit of being connected to, merge with respect to ticket with the unit of being carried as, can further reduce the redundant information in the ticket, improve the utilance of transfer resource and storage resources, and the quantity of the ticket that handle the charging center has also reduced, and the treatment effeciency of charging center can be provided.
Fig. 4 is the ticket treatment system preferred construction block diagram one according to the embodiment of the invention, and as shown in Figure 4, merge module 38 and comprise: first merges module 382, is used for the ticket that same Packet Data Network connects from belonging to of S-GW is merged; Second merges module 384, is used for the ticket that same Packet Data Network connects from belonging to of P-GW is merged.
By the system shown in Fig. 4, can the ticket that come from S-GW and P-GW be merged respectively.
After 38 pairs of tickets of merging module merge, whether CGF can also finish whole merging to ticket is judged, Fig. 5 is the ticket treatment system preferred construction block diagram two according to the embodiment of the invention, as shown in Figure 5, CGF also comprises: statistical module 52, sending module 54, calling module 58 describe respectively this below.
Statistical module 52 is coupled to and merges module 38, is used for the quantity according to the bearing identification statistics carrying of the ticket after merging; Calling module 56 is coupled to statistical module 52, the quantity that is used for the carrying that quantity and default bearing ticket with the carrying after the statistics carry is compared, if ticket identical then that call after sending module 54 will merge sends to the charging center, otherwise, call receiver module 36 and merge module 38 and continue to receive ticket and merge; Sending module 54 is used for the ticket after merging is sent to the charging center.
Preferably, module 32 being set also is used for the carrying quantity of all establishments being filled in the carrying amount field of described default bearing ticket after default bearing finishes.
By the system shown in Fig. 5; CGF can judge further whether the merging of ticket is all finished; to guarantee sending to the charging center with merging the ticket of all finishing; can guarantee the minimum number of the handled ticket in charging center like this, and can guarantee that ticket takies minimum transfer resource and storage resources.
It can be indication information with the information setting that can be connected in the unique identification Packet Data Network under the same P-GW with information that can unique identification P-GW that module 32 is set.This module also can be provided with a unique identification in the overall situation for same Packet Data Network connects.Certainly, because Packet Data Network's establishment of connection finishes with P-GW, information and the information that can be connected in the unique identification Packet Data Network under the same P-GW that use can unique identification P-GW are easier as the indication information realization of ticket.Wherein, information that can unique identification P-GW can be the address of this P-GW.Below this is illustrated.
For example, definition " PDN connection identifier (PDN Connection ID) " field in SGW-CDR and the PGW-CDR ticket is used for discerning the different tickets that belong to same PDN connection; This field connects with PDN of " P-GW address (P-GW Address used) " unique identification of field.That is, several tickets of same PDN join dependency, its " PDN Connection ID ", " P-GW Address used " they are the same.Therefore can combine a plurality of tickets of a PDN join dependency in view of the above.
Fig. 6 is the flow chart according to the call bill processing method of the embodiment of the invention, and this flow process may further comprise the steps:
Step S602, P-GW and/or S-GW are provided with indication information in ticket, and will carry ticket and send to CGF, and this indication information is used to indicate the Packet Data Network under the ticket to connect; And,
Step S604, CGF merges according to the ticket that the indication information that carries in the ticket that receives will belong to the connection of same Packet Data Network.
Preferably, CGF can be respectively merges the ticket that same Packet Data Network is connected that belongs to from S-GW and P-GW.
After step S604, CGF will belong to after ticket that same Packet Data Network connects merges, and CGF is according to the quantity of the bearing identification statistics carrying in the ticket after merging; And the quantity of the carrying of carrying in the quantity of the carrying after will adding up and the default bearing ticket compares, if ticket identical then after will merging sends to the charging center, otherwise, continue to receive ticket and also merge.
Preferably, S-GW or P-GW fill in the carrying quantity of all establishments the carrying amount field of default bearing ticket after default bearing finishes.
Preferably, information that can the unique identification packet data network gateway connects with the Packet Data Network under the indication ticket with the information that can be connected in the unique identification Packet Data Network under the same packet data network gateway is linked together, wherein, information that can unique identification P-GW is the address of packet data gateway.
Fig. 7 merges the schematic diagram of handling according to the CGF of the embodiment of the invention to same PDN join dependency ticket, is connected and Fig. 7 describes below in conjunction with the PDN of " PDN connection identifier " field and the unique together identification of " P-GW address " field that defines in SGW-CDR and the PGW-CDR ticket.
Step S701, S-GW, P-GW network element all send to CGF with the SGW-CDR and the PGW-CDR ticket of all carryings, CGF classifies SGW-CDR and PGW-CDR ticket according to " PDN Connection ID "+" P-GW Address used "+" record type (Record Type) ", wherein, to be used to indicate this ticket be from S-GW or from P-GW to Record Type;
Step S702, with " PDN Connection ID "+" P-GW Address used "+" Record Type " if identical, then by writing time (Record Opening Time) field line up (certainly, also can arrange) according to other fields, each field in these tickets is merged in the new ticket, wherein, the value of some field in different tickets is the same, for example, record type (Record Type), user's international mobile subscriber identity (Served IMSI), user's international mobile equipment identification number and software version number (Served IMEISV), user's ISDN number (Served MSISDN), the P-GW address (P-GW Address Used) of using, the service node address (Serving node Address) of using, the service node address (Serving node Type) of using, APN network identity (Access Point Name Network Identifier), APN preference pattern (APN Selection Mode), PDP/PDN type (PDP/PDN Type), the PDP/PDN address (Served PDP/PDN Address) of using, dynamic address mark (Dynamic Address Flag), charging characteristic (Charging Characteristics), the service node PLMN identifier (Serving node PLMN Identifier) that uses, diagnostic message (Diagnostics), charging characteristic preference pattern (Charging Characteristicsselection mode), nodename (Node Id), radio access technologies types (RAT Type) etc., these fields only need keep one and add new ticket when merging.The value of some field in different tickets is inequality, these fields simply can be united or selects one of them to insert.For example, record is opened the time time that (Record Opening Time) field can get the earliest and is inserted new ticket, duration (Duration) field accumulation gets up to insert new ticket, charging identifier (Charging ID) field is different before merging to carry different values, the new ticket that merges need write down the Charging ID of all carryings, can form a tabulation, traffic data flow tabulation (List of Traffic Data Volumes), business datum tabulation (List of Service Data) field is the tabulation of data traffic before merging, and merging the back is exactly that each tabulation polyphone is got up to insert new ticket etc.;
Step S703, whether the ticket of checking all carryings that this PDN connects all merges, in view of how many carryings that does not have information can write down this PDN join dependency in existing SGW-CDR and the PGW-CDR ticket is, in this step, the S-GW of EPS can be connected professional duration of existence with P-GW at PDN and add up the quantity of the carrying of all establishments (comprising default bearing and dedicated bearing), when PDN connects service ending, the carrying quantity of all establishments is filled in " Bearer Number " carrying amount field in the ticket (SGW-CDR and PGW-CDR) of default bearing.If the quantity of the Charging ID that writes down among the carrying quantity of " Bearer Number " field record and the step S702 is consistent, the ticket that shows all carryings has all merged to be finished, and gives the charging center with the newspeak single transmit that merging is finished.If inconsistent, show not merge and finish to also have the ticket of other carryings not deliver to CGF, need to continue again to merge after the wait arrival.
By above step, the ticket of a plurality of carryings of same PDN join dependency is merged into a new ticket, comprises the information of all needs in this ticket, and do not have redundant information, reduce the data traffic and the memory space that are transferred to the charging center, reduced the processing load of charging center.
Describe respectively with regard to S-GW and two kinds of situations of P-GW respectively below.
Situation one, S-GW
In S-GW, a PDN connects professional duration of existence and has created a default bearing and two dedicated bearings.When PDN connected end, promptly default bearing finished, and the S-GW network element produces the SGW-CDR ticket, comprises " Bearer Number " field in the ticket, owing to created a default bearing and two dedicated bearings, the value of " Bearer Number " field is 3.
Step S801, the S-GW network element all sends to CGF with the SGW-CDR ticket of all carryings; CGF classifies the SGW-CDR ticket according to " PDN Connection ID "+" P-GW Address used "+" Record Type ";
Step S802, the ticket that " PDN Connection ID "+" P-GW Address used "+" Record Type " is identical is lined up by Record Opening Time field, each field in these tickets is merged in the new ticket, it is identical with the processing among the step S602 to merge processing, does not repeat them here.
Step S803, whether the ticket of checking all carryings that this PDN connects all merges, if the quantity of Charging ID is identical with quantity in " Bearer Number " field in " Charging ID " tabulation, the ticket that shows all carryings has all merged to be finished, the new SGW-CDR ticket that merging can be finished sends to the charging center, otherwise waits for and continue to merge.
Situation two, P-GW
In P-GW, a PDN connects professional duration of existence and has created a default bearing and two dedicated bearings.When PDN connected end, promptly default bearing finished, and the P-GW network element produces the PGW-CDR ticket, comprises " Bearer Number " field in the ticket, owing to created a default bearing and two dedicated bearings, the value of " Bearer Number " field is 3.
Step S901, the P-GW network element all sends to CGF with the PGW-CDR ticket of all carryings; CGF classifies the PGW-CDR ticket according to " PDN Connection ID "+" P-GW Address used "+" Record Type ";
Step S902, the ticket that " PDN Connection ID "+" P-GW Address used "+" Record Type " is the same is lined up by Record Opening Time field, each field in these tickets is merged in the new ticket, it is identical with the processing among the step S602 to merge processing, does not repeat them here.
Step S903, whether the ticket of checking all carryings that this PDN connects all merges, if the quantity of Charging ID is identical with quantity in " Bearer Number " field in " Charging ID " tabulation, the ticket that shows all carryings has all merged to be finished, the new PGW-CDR ticket that merging can be finished sends to the charging center, otherwise waits for and continue to merge.
In sum, pass through the foregoing description, solved ticket information redundancy after the merging that causes according to the carrying Consolidate CDR in the correlation technique, and then the problem that causes wasting transfer resource and storage resources and influence the charging center treatment effeciency, save transfer resource and storage resources, improved the treatment effeciency of charging center.
Obviously, those skilled in the art should be understood that, above-mentioned each module of the present invention or each step can realize with the general calculation device, they can concentrate on the single calculation element, perhaps be distributed on the network that a plurality of calculation element forms, alternatively, they can be realized with the executable program code of calculation element, thereby, they can be stored in the storage device and carry out by calculation element, and in some cases, can carry out step shown or that describe with the order that is different from herein, perhaps they are made into each integrated circuit modules respectively, perhaps a plurality of modules in them or step are made into the single integrated circuit module and realize.Like this, the present invention is not restricted to any specific hardware and software combination.
The above is the preferred embodiments of the present invention only, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (12)
1. call bill processing method is characterized in that may further comprise the steps:
Packet data network gateway and/or gateway are provided with indication information in ticket, and described ticket is sent to charging gateway, and described indication information is used to indicate the affiliated Packet Data Network of described ticket to connect; And,
Described charging gateway merges according to the ticket that the indication information that carries in the ticket that receives will belong to the connection of same Packet Data Network.
2. method according to claim 1, it is characterized in that described charging gateway merges and comprises according to belonging to ticket that same Packet Data Network connects: described charging gateway will merge from the ticket that same Packet Data Network is connected that belongs to of described gateway and described packet data network gateway respectively.
3. method according to claim 1 and 2 is characterized in that, described charging gateway will belong to after ticket that same Packet Data Network connects merges, and described method is further comprising the steps of:
Described charging gateway is according to the quantity of the bearing identification statistics carrying in the ticket after merging; And,
The quantity of the carrying of carrying in quantity and the default bearing ticket with the carrying after the statistics is compared, if ticket identical then after will merging sends to the charging center, otherwise continuation reception ticket also merges.
4. method according to claim 3 is characterized in that, described gateway or described packet data network gateway fill in the carrying quantity of all establishments the carrying amount field of described default bearing ticket after default bearing finishes.
5. method according to claim 1 and 2, it is characterized in that information that can the unique identification packet data network gateway connects with the Packet Data Network under the indication ticket with the information that can be connected in the unique identification Packet Data Network under the same packet data network gateway is linked together.
6. method according to claim 5 is characterized in that, described information that can the unique identification packet data network gateway is the address of described packet data gateway.
7. ticket treatment system comprises: packet data network gateway, gateway and charging gateway, it is characterized in that,
Described packet data network gateway and described gateway comprise:
Module is set, is used at ticket indication information being set, described indication information is used to indicate the affiliated Packet Data Network of described ticket to connect;
Sending module is used for described ticket is sent to charging gateway;
Described charging gateway comprises:
Receiver module is used to receive the ticket from described packet data network gateway and/or described gateway;
Merge module, be used for to belong to the ticket that same Packet Data Network connects and merge according to the indication information that the ticket that receives carries.
8. system according to claim 7 is characterized in that, described merging module comprises: first merges module, is used for the ticket that same Packet Data Network connects from belonging to of described gateway is merged; Described second merges module, is used for the ticket that same Packet Data Network connects from belonging to of described packet data network gateway is merged.
9. according to claim 7 or 8 described systems, it is characterized in that described charging gateway also comprises:
Statistical module is used for the quantity according to the bearing identification statistics carrying of the ticket after merging;
Sending module is used for the ticket after merging is sent to the charging center; And,
Calling module, the quantity that is used for the carrying that quantity and default bearing ticket with the carrying after the statistics carry is compared, if ticket identical then that call after described sending module will merge sends to the charging center, otherwise, call described receiver module and described merging module and continue to receive ticket and merge.
10. system according to claim 9 is characterized in that, the described module that is provided with also is used for the carrying quantity of all establishments being filled in the carrying amount field of described default bearing ticket after default bearing finishes.
11. according to claim 7 or 8 described systems, it is characterized in that described the information that module can the unique identification packet data network gateway is set is described indication information with the information setting that can be connected in the unique identification Packet Data Network under the same packet data network gateway.
12. system according to claim 11 is characterized in that, the described module that is provided with is described information that can the unique identification packet data network gateway with the address setting of described packet data gateway.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010140149.1A CN102202281B (en) | 2010-03-24 | 2010-03-24 | Ticket processing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010140149.1A CN102202281B (en) | 2010-03-24 | 2010-03-24 | Ticket processing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102202281A true CN102202281A (en) | 2011-09-28 |
| CN102202281B CN102202281B (en) | 2015-05-13 |
Family
ID=44662602
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010140149.1A Expired - Fee Related CN102202281B (en) | 2010-03-24 | 2010-03-24 | Ticket processing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102202281B (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103384202A (en) * | 2013-07-17 | 2013-11-06 | 大唐移动通信设备有限公司 | Flow report message transmission method and device |
| CN104137580A (en) * | 2012-07-23 | 2014-11-05 | 华为技术有限公司 | Charging information processing method, apparatus, and system |
| CN104506371A (en) * | 2015-01-04 | 2015-04-08 | 华为技术有限公司 | Method and device for management of application programming interface (API) call records |
| CN105188043A (en) * | 2014-06-19 | 2015-12-23 | 阿尔卡特朗讯 | Method, device and system for charging based on PDN connection |
| CN106332033A (en) * | 2015-06-17 | 2017-01-11 | 中兴通讯股份有限公司 | Method and device for generating telephone bill and packet data network gateway |
| CN108111320A (en) * | 2016-11-24 | 2018-06-01 | 大唐移动通信设备有限公司 | A kind of local service charging method, server and charging gateway |
| CN108632900A (en) * | 2017-03-21 | 2018-10-09 | 中国移动通信集团山西有限公司 | For the flow processing method of the network integration, device, base station and gateway |
| CN108833724A (en) * | 2018-07-23 | 2018-11-16 | 北京邮电大学 | A kind of CDR synthetic method and device |
| CN110532294A (en) * | 2019-09-03 | 2019-12-03 | 中国联合网络通信集团有限公司 | Ticket merging method, device, equipment and computer readable storage medium |
| CN114629734A (en) * | 2022-03-14 | 2022-06-14 | 阿里巴巴（中国）有限公司 | Call bill processing method, device, system and storage medium |
| CN114629734B (en) * | 2022-03-14 | 2024-04-26 | 阿里巴巴（中国）有限公司 | Method, device, system and storage medium for processing ticket |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007093099A1 (en) * | 2006-02-18 | 2007-08-23 | Huawei Technologies Co., Ltd | Method and system for associating and distinguishing the account bill in the fork scene |
| CN101583113A (en) * | 2008-07-07 | 2009-11-18 | 中兴通讯股份有限公司 | Charging method and system for distinguishing user charging rules |
-
2010
- 2010-03-24 CN CN201010140149.1A patent/CN102202281B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007093099A1 (en) * | 2006-02-18 | 2007-08-23 | Huawei Technologies Co., Ltd | Method and system for associating and distinguishing the account bill in the fork scene |
| CN101583113A (en) * | 2008-07-07 | 2009-11-18 | 中兴通讯股份有限公司 | Charging method and system for distinguishing user charging rules |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108650102A (en) * | 2012-07-23 | 2018-10-12 | 华为技术有限公司 | Billing information processing method, apparatus and system |
| CN104137580A (en) * | 2012-07-23 | 2014-11-05 | 华为技术有限公司 | Charging information processing method, apparatus, and system |
| CN108650102B (en) * | 2012-07-23 | 2021-06-01 | 华为技术有限公司 | Charging information processing method, device and system |
| CN103384202A (en) * | 2013-07-17 | 2013-11-06 | 大唐移动通信设备有限公司 | Flow report message transmission method and device |
| CN105188043A (en) * | 2014-06-19 | 2015-12-23 | 阿尔卡特朗讯 | Method, device and system for charging based on PDN connection |
| CN104506371A (en) * | 2015-01-04 | 2015-04-08 | 华为技术有限公司 | Method and device for management of application programming interface (API) call records |
| WO2016107510A1 (en) * | 2015-01-04 | 2016-07-07 | 华为技术有限公司 | Management method and apparatus for application programming interface (api) calling record |
| CN106332033A (en) * | 2015-06-17 | 2017-01-11 | 中兴通讯股份有限公司 | Method and device for generating telephone bill and packet data network gateway |
| CN108111320A (en) * | 2016-11-24 | 2018-06-01 | 大唐移动通信设备有限公司 | A kind of local service charging method, server and charging gateway |
| CN108111320B (en) * | 2016-11-24 | 2020-12-04 | 大唐移动通信设备有限公司 | Local service charging method, server and charging gateway |
| CN108632900A (en) * | 2017-03-21 | 2018-10-09 | 中国移动通信集团山西有限公司 | For the flow processing method of the network integration, device, base station and gateway |
| CN108833724A (en) * | 2018-07-23 | 2018-11-16 | 北京邮电大学 | A kind of CDR synthetic method and device |
| CN110532294A (en) * | 2019-09-03 | 2019-12-03 | 中国联合网络通信集团有限公司 | Ticket merging method, device, equipment and computer readable storage medium |
| CN114629734A (en) * | 2022-03-14 | 2022-06-14 | 阿里巴巴（中国）有限公司 | Call bill processing method, device, system and storage medium |
| CN114629734B (en) * | 2022-03-14 | 2024-04-26 | 阿里巴巴（中国）有限公司 | Method, device, system and storage medium for processing ticket |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102202281B (en) | 2015-05-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102202281B (en) | Ticket processing method and system | |
| CN106817686B (en) | Charging method and device | |
| CN101325592B (en) | Method, apparatus and system for establishing load-bearing connection | |
| CN101227714B (en) | System, apparatus and method for sharing network resource | |
| CN102075894B (en) | Selection method and system for policy and charging rules function entity | |
| CN101409951B (en) | Method for establishing load bearing and relevant apparatus | |
| CN101720119B (en) | Method and system for realizing PDN connecting selection | |
| CN103125142B (en) | For the group of mobile entity implements common service quality | |
| WO2021156771A1 (en) | EXTENSION OF Npcf_EventExposure WITH USAGE MONITORING EVENT | |
| CN102148689A (en) | Policy and charging rules function entity selection method, device and system | |
| CN101227391A (en) | Tactics under non-roaming condition and method for selecting charging regulation function entity | |
| CN102763366A (en) | Diverse source message association | |
| CN103404102A (en) | Bearing creating method, device and system | |
| CN102238517A (en) | Method, device and system for reporting machine type communication (MTC) events | |
| CN103517245A (en) | D2D communication charging method and system | |
| CN102340842B (en) | Resource control method and device and base station | |
| CN102098348A (en) | Selection method of packet data network gateway and mobility management network element | |
| CN105208598A (en) | Network access method and apparatus | |
| CN101360097B (en) | Method, network and network element for forwarding packet | |
| CN109428734B (en) | Charging realizing system, charging realizing method and charging management function entity | |
| CN105580425B (en) | Data connection for UE to 3GPP data access net provides the method and apparatus of on-demand QoS | |
| US11051150B2 (en) | Machine-to-machine network optimization and online charging | |
| CN103384279A (en) | Address allocation method and device | |
| CN102948219A (en) | Method for allocating a network entity | |
| CN105188043A (en) | Method, device and system for charging based on PDN connection |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20150513 Termination date: 20200324 |