CN102202281B - Ticket processing method and system - Google Patents
Ticket processing method and system Download PDFInfo
- Publication number
- CN102202281B CN102202281B CN201010140149.1A CN201010140149A CN102202281B CN 102202281 B CN102202281 B CN 102202281B CN 201010140149 A CN201010140149 A CN 201010140149A CN 102202281 B CN102202281 B CN 102202281B
- Authority
- CN
- China
- Prior art keywords
- ticket
- packet data
- gateway
- data network
- carrying
- 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.)
- Expired - Fee Related
Links
Landscapes
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
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, referred to as 3GPP) grouping system (the Evolved Packet System of the evolution of the R8 of definition in wireless communication standard tissue, referred to as EPS) in, basic granularity is carrying (Bearer).Fig. 1 is Packet Data Network (the Packet Data Network of prior art, referred to as PDN) connect each schematic diagram carried of business duration of existence, as shown in Figure 1, in PDN, PDN connection business duration of existence can remain sets up a carrying, Internet protocol (the Internet Protocol of " always online " is provided to UE, referred to as IP) connect, this carrying is called default bearing, there is service quality (the Quality of Service initially provided, referred to as QoS) class letter (QCI), distribute and keep priority (Allocation andRetention Priority, referred to as ARP).When the service needed different QoS of user ensures, network can create other EPS and carry in identical PDN connects, and is called dedicated bearing.That is, multiple carrying may be had in a PDN connects.
Gateway (Serving Gateway, referred to as S-GW) and packet data network gateway (PDN Gateway, referred to as P-GW) network element can collect the charge information of each carrying, and be that each carrying exports ticket (SGW-CDR and PGW-CDR).According to time or traffic threshold, a carrying can produce multiple partial CDR, and because carrying is identified by a unique mark Charging ID, therefore, the Charging ID of these partial CDRs is identical.Such PDN connection can produce a lot of partial CDR.
Fig. 2 is charging gateway of the prior art (Charging Gateway Function, referred to as CGF) process the schematic diagram of ticket, CGF collects SGW-CDR and PGW-CDR ticket from S-GW and P-GW network element, carries out merging treatment, and the ticket after process is sent to charging center.SGW-CDR and PGW-CDR partial CDR identical for Charging ID can be combined by existing merging treatment, i.e. the partial CDR of same carrying can be combined, and decreases the quantity of ticket.But, a lot of may be had with carrying of same PDN join dependency, and, inventor finds, due to the ticket that these tickets are same users, there is much identical information, in ticket transmission and preservation process, there is information redundancy, waste unnecessary transfer resource and storage resources, and too increase the burden of charging center process ticket.
Summary of the invention
Main purpose of the present invention is to provide a kind of ticket processing scheme, at least to solve the problem.
According to an aspect of the present invention, provide a kind of call bill processing method, the method comprises the following steps: packet data network gateway and/or gateway arrange indication information in ticket, and ticket is sent to charging gateway, and the Packet Data Network that indication information is used to indicate belonging to ticket connects; And the ticket belonging to the connection of same Packet Data Network merges according to the indication information carried in the ticket received by charging gateway.
Further, charging gateway carries out merging comprise according to by belonging to the ticket that same Packet Data Network connects: the ticket that same Packet Data Network is connected that belongs to from gateway and packet data network gateway merges by charging gateway respectively.
Further, after the ticket belonging to the connection of same Packet Data Network merges by charging gateway, 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, by the quantity of the carrying after statistics compared with the quantity of the carrying of carrying in default bearing ticket, if the same the ticket after merging is sent to charging center, otherwise, continue to receive ticket and also merge.
Further, the carrying quantity of all establishments, after default bearing terminates, is filled in the carrying amount field of default bearing ticket by gateway or packet data network gateway.
Further, can unique identification packet data network gateway information with can the information that is connected of the unique identification Packet Data Network under same packet data network gateway be combined to indicate the Packet Data Network belonging to ticket to connect.
Further, can the information of unique identification packet data network gateway be the address of packet data gateway.
According to a further aspect in the invention, additionally provide a kind of ticket treatment system, comprise: packet data network gateway, gateway and charging gateway, this packet data network gateway and gateway comprise: arrange module, for arranging indication information in ticket, the Packet Data Network that indication information is used to indicate belonging to ticket connects; Sending module, for sending to charging gateway by ticket; Charging gateway comprises: receiver module, for receiving the ticket from packet data network gateway and/or gateway; Merge module, for being merged by the ticket belonging to the connection of same Packet Data Network according to the indication information carried in the ticket received.
Further, merge module and comprise: first merges module, for the ticket belonging to the connection of same Packet Data Network from gateway is merged; Second merges module, for being merged by the ticket belonging to the connection of same Packet Data Network from packet data network gateway.
Further, charging gateway also comprises: statistical module, for the quantity according to the bearing identification statistics carrying in the ticket after merging; Sending module, for sending to charging center by the ticket after merging; And, calling module, for by the quantity of carrying after statistics with the quantity of the carrying of carrying in default bearing ticket compared with, if the same call sending module and the ticket after merging sent to charging center, otherwise, call receiver module and merge module and continue receive ticket and merge.
Further, module is set also for after default bearing terminates, the carrying quantity of all establishments is filled in the carrying amount field of default bearing ticket.
Further, arrange module can unique identification packet data network gateway information with the information that is connected of the unique identification Packet Data Network under same packet data network gateway can be set to indication information.
Further, arranging that the address of packet data gateway is set to by module can the information of unique identification packet data network gateway.
By the present invention, adopt packet data network gateway and/or gateway to arrange indication information in ticket, and ticket is sent to charging gateway, the Packet Data Network that this indication information is used to indicate belonging to ticket connects; The ticket belonging to the connection of same Packet Data Network merges according to the indication information carried in the ticket received by charging gateway, to solve in correlation technique according to carrying Consolidate CDR ticket information redundancy after the merging that causes, and then cause wasting transfer resource and storage resources and the problem affecting charging center treatment effeciency, save transfer resource and storage resources, improve the treatment effeciency of charging center.
Accompanying drawing explanation
Accompanying drawing described herein is used to provide a further understanding of the present invention, and form a application's part, schematic description and description of the present invention, for explaining the present invention, does not form inappropriate limitation of the present invention.In the accompanying drawings:
Fig. 1 is that the PDN of prior art connects each schematic diagram carried of business duration of existence;
Fig. 2 is the schematic diagram of CGF process ticket of the prior art;
Fig. 3 is the structured flowchart of the ticket treatment system according to the embodiment of the present invention;
Fig. 4 is according to the preferred structured flowchart one of the ticket treatment system of the embodiment of the present invention;
Fig. 5 is according to the preferred structured flowchart two of the ticket treatment system of the embodiment of the present invention;
Fig. 6 is the flow chart of the call bill processing method according to the embodiment of the present invention; And,
Fig. 7 is to the schematic diagram of same PDN join dependency ticket merging treatment according to the CGF of the embodiment of the present invention.
Embodiment
Hereinafter also describe the present invention in detail with reference to accompanying drawing in conjunction with the embodiments.It should be noted that, when not conflicting, the embodiment in the application and the feature in embodiment can combine mutually.
In the examples below, CGF is for receiving the ticket of P-GW or S-GW transmission and carrying out merging treatment, and P-GW and S-GW generates ticket, and ticket is sent to CGF.
Fig. 3 is the structured flowchart of the ticket treatment system according to the embodiment of the present invention, and as shown in Figure 3, this system comprises: P-GW, S-GW and CGF.Wherein, P-GW and S-GW includes: arrange module 32, sending module 34, CGF comprises: receiver module 36, merging module 38.Be explained below.
Arrange module 32, for arranging indication information in ticket, the Packet Data Network that indication information is used to indicate belonging to ticket connects; Sending module 34 is coupled to and arranges module 32, and this module is used for ticket to send to CGF; Receiver module 36, for receiving the ticket from P-GW and/or S-GW; Merge module 38 and be coupled to receiver module 36, this module is used for being merged by the ticket belonging to the connection of same Packet Data Network according to the indication information carried in the ticket received.
Pass through said system, can realize merging ticket in units of PDN connects, merge relative to the ticket being carried as unit, the redundant information in ticket can be reduced further, improve the utilance of transfer resource and storage resources, further, the quantity of the ticket of charging center process decreases, and can provide the treatment effeciency of charging center.
Fig. 4 is according to the preferred structured flowchart one of the ticket treatment system of the embodiment of the present invention, as shown in Figure 4, merges module 38 and comprises: first merges module 382, for being merged by the ticket belonging to the connection of same Packet Data Network from S-GW; Second merges module 384, for being merged by the ticket belonging to the connection of same Packet Data Network from P-GW.
By the system shown in Fig. 4, can the ticket coming from S-GW and P-GW be merged respectively.
After merging module 38 pairs of tickets merge, whether CGF can also complete all to merge to ticket judges, Fig. 5 is according to the preferred structured flowchart two of the ticket treatment system of the embodiment of the present invention, as shown in Figure 5, CGF also comprises: statistical module 52, sending module 54, calling module 58, be described respectively to this below.
Statistical module 52 is coupled to and merges module 38, for the quantity according to the bearing identification statistics carrying in the ticket after merging; Calling module 56 is coupled to statistical module 52, for by the quantity of carrying after statistics compared with the quantity of the carrying of carrying in default bearing ticket, if the same call sending module 54 and the ticket after merging is sent to charging center, otherwise, call receiver module 36 and merge module 38 and continue receive ticket and merge; Sending module 54, for sending to charging center by the ticket after merging.
Preferably, module 32 is set also for after default bearing terminates, the carrying quantity of all establishments is filled in the carrying amount field of described default bearing ticket.
By the system shown in Fig. 5; CGF can judge whether the merging of ticket all completes further; to guarantee to send to charging center by merging the ticket all completed; the minimum number of the ticket handled by charging center can be guaranteed like this, and can guarantee that ticket takies minimum transfer resource and storage resources.
Arrange module 32 can by can unique identification P-GW information with the information that is connected of the unique identification Packet Data Network under same P-GW can be set to indication information.This module also can arrange a unique identification in the overall situation for same Packet Data Network connects.Certainly, because Packet Data Network's establishment of connection completes with P-GW, use can unique identification P-GW information and can the information that is connected of the unique identification Packet Data Network under same P-GW easier as the indication information realization of ticket.Wherein, can the information of unique identification P-GW can be the address of this P-GW.Below this is illustrated.
Such as, in SGW-CDR and PGW-CDR ticket, define " PDN connection identifier (PDN Connection ID) " field, be used for identifying the different tickets belonging to same PDN and connect; This field uniquely identifies that a PDN connects together with " P-GW address (P-GW Address used) " field.That is, several tickets of same PDN join dependency, its " PDN Connection ID ", " P-GW Address used " are the same.Therefore multiple tickets of a PDN join dependency can be combined accordingly.
Fig. 6 is the flow chart of the call bill processing method according to the embodiment of the present invention, and this flow process comprises the following steps:
Step S602, P-GW and/or S-GW arrange indication information in ticket, and will carry ticket and send to CGF, and the Packet Data Network that this indication information is used to indicate belonging to ticket connects; And,
The ticket belonging to the connection of same Packet Data Network merges according to the indication information carried in the ticket received by step S604, CGF.
Preferably, the ticket that same Packet Data Network is connected that belongs to from S-GW with P-GW can merge by CGF respectively.
After step S604, after the ticket belonging to the connection of same Packet Data Network merges by CGF, CGF is according to the quantity of the bearing identification statistics carrying in the ticket after merging; And by the quantity of the carrying after statistics compared with the quantity of the carrying of carrying in default bearing ticket, if the same the ticket after merging is sent to charging center, otherwise, continue to receive ticket and also merge.
Preferably, the carrying quantity of all establishments, after default bearing terminates, is filled in the carrying amount field of default bearing ticket by S-GW or P-GW.
Preferably, can unique identification packet data network gateway information with can the information that is connected of the unique identification Packet Data Network under same packet data network gateway be combined to indicate the Packet Data Network belonging to ticket to connect, wherein, can the information of unique identification P-GW be the address of packet data gateway.
Fig. 7 is according to the CGF of the embodiment of the present invention to the schematic diagram of same PDN join dependency ticket merging treatment, uniquely identifies that a PDN is connected and Fig. 7 is described together below in conjunction with " PDN connection identifier " field defined in SGW-CDR with PGW-CDR ticket and " P-GW address " field.
Step S701, SGW-CDR and the PGW-CDR ticket of all carryings is all sent to CGF by S-GW, P-GW network element, CGF according to " PDN Connection ID "+" P-GW Address used "+" record type (Record Type) " by SGW-CDR and PGW-CDR bill classification, wherein, Record Type is used to indicate this ticket is from S-GW or from P-GW;
Step S702, by " PDN Connection ID "+" P-GW Address used "+" Record Type " if identical, then line up (certainly by writing time (Record Opening Time) field, also can arrange according to other fields), each field in these tickets is merged in a new ticket, wherein, the value of some field in different tickets is the same, such as, record type (Record Type), the international mobile subscriber identity (Served IMSI) of user, the international mobile equipment identification number of user and software version number (Served IMEISV), the ISDN number (Served MSISDN) of user, the P-GW address (P-GW Address Used) used, the serving node address (Serving node Address) used, the serving node address (Serving node Type) used, 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) used, dynamic address mark (Dynamic Address Flag), charging characteristic (Charging Characteristics), the service node PLMN identifier (Serving node PLMN Identifier) used, diagnostic message (Diagnostics), charging characteristic preference pattern (Charging Characteristicsselection mode), nodename (Node Id), radio access technologies type (RAT Type) etc., these fields only need reservation one to add new ticket when merging.The value of some field in different tickets is not identical, these fields simply can be combined or select one of them to insert.Such as, record opening time (Record Opening Time) the field time can got the earliest inserts new ticket, duration (Duration) field accumulation gets up to insert new ticket, charging identifier (Charging ID) field is different before merging carries different values, the new ticket merged needs the Charging ID recording all carryings, a list can be formed, traffic data flow list (List of Traffic Data Volumes), business datum list (List of Service Data) field is the list of data traffic before merging, be exactly each list is concatenated insert new ticket etc. after merging,
Step S703, check whether the ticket of all carryings that this PDN connects all is combined, in view of the carrying not having information can record this PDN join dependency in existing SGW-CDR and PGW-CDR ticket is how many, in this step, S-GW with P-GW of EPS can be connected at PDN the quantity (comprising default bearing and dedicated bearing) that business duration of existence adds up the carrying of all establishments, when PDN connects service ending, " the Bearer Number " the carrying quantity of all establishments filled in the ticket (SGW-CDR and PGW-CDR) of default bearing carries amount field.If the carrying quantity of " Bearer Number " field record is consistent with the quantity of the Charging ID recorded in step S702, show that the ticket of all carryings has merged all, by the newspeak single transmit that merged to charging center.If inconsistent, show not merged, also have the ticket of other carryings not deliver to CGF, continue again to merge after needing to wait for arrival.
By above step, the ticket of multiple carryings of same PDN join dependency is merged into a new ticket, comprises information in need in this ticket, and there is no redundant information, decrease the data traffic and memory space that are transferred to charging center, decrease the processing load of charging center.
Be described respectively with regard to S-GW and P-GW two kinds of situations respectively below.
Situation one, S-GW
In S-GW, a PDN connects business duration of existence and creates a default bearing and two dedicated bearings.At the end of PDN connects, namely default bearing terminates, and S-GW network element produces SGW-CDR ticket, and comprise " Bearer Number " field in ticket, owing to creating a default bearing and two dedicated bearings, the value of " Bearer Number " field is 3.
The SGW-CDR ticket of all carryings is all sent to CGF by step S801, S-GW network element; CGF according to " PDN Connection ID "+" P-GW Address used "+" Record Type " by SGW-CDR bill classification;
Step S802, ticket identical for " PDN Connection ID "+" P-GW Address used "+" Record Type " is lined up by Record Opening Time field, each field in these tickets is merged in a new ticket, merging treatment is identical with the process in step S602, does not repeat them here.
Step S803, check whether the ticket of all carryings that this PDN connects all is combined, if the quantity of Charging ID is identical with the quantity in " Bearer Number " field in " Charging ID " list, show that the ticket of all carryings has merged all, the new SGW-CDR ticket merged can be sent to charging center, otherwise wait for that continuation merges.
Situation two, P-GW
In P-GW, a PDN connects business duration of existence and creates a default bearing and two dedicated bearings.At the end of PDN connects, namely default bearing terminates, and P-GW network element produces PGW-CDR ticket, and comprise " Bearer Number " field in ticket, owing to creating a default bearing and two dedicated bearings, the value of " Bearer Number " field is 3.
The PGW-CDR ticket of all carryings is all sent to CGF by step S901, P-GW network element; CGF according to " PDN Connection ID "+" P-GW Address used "+" Record Type " by PGW-CDR bill classification;
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 a new ticket, merging treatment is identical with the process in step S602, does not repeat them here.
Step S903, check whether the ticket of all carryings that this PDN connects all is combined, if the quantity of Charging ID is identical with the quantity in " Bearer Number " field in " Charging ID " list, show that the ticket of all carryings has merged all, the new PGW-CDR ticket merged can be sent to charging center, otherwise wait for that continuation merges.
In sum, pass through above-described embodiment, to solve in correlation technique according to carrying Consolidate CDR ticket information redundancy after the merging that causes, and then cause wasting transfer resource and storage resources and the problem affecting charging center treatment effeciency, save transfer resource and storage resources, improve the treatment effeciency of charging center.
Obviously, those skilled in the art should be understood that, above-mentioned of the present invention each module or each step can realize with general calculation element, they can concentrate on single calculation element, or be distributed on network that multiple calculation element forms, alternatively, they can realize with the executable program code of calculation element, thus, they can be stored and be performed by calculation element in the storage device, and in some cases, step shown or described by can performing with the order be different from herein, or they are made into each integrated circuit modules respectively, or the multiple module in them or step are made into single integrated circuit module to realize.Like this, the present invention is not restricted to any specific hardware and software combination.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (8)
1. a call bill processing method, is characterized in that comprising the following steps:
Packet data network gateway and/or gateway arrange indication information in ticket, and described ticket is sent to charging gateway, and the Packet Data Network that described indication information is used to indicate belonging to described ticket connects; And,
The ticket that same Packet Data Network is connected that belongs to from described gateway and described packet data network gateway will merge according to the indication information carried in the ticket received by described charging gateway respectively;
Described charging gateway is according to the quantity of the bearing identification statistics carrying in the ticket after merging; And,
By the quantity of the carrying after statistics compared with the quantity of the carrying of carrying in default bearing ticket, if the same the ticket after merging is sent to charging center, otherwise, continue to receive ticket and also merge.
2. method according to claim 1, is characterized in that, the carrying quantity of all establishments, after default bearing terminates, is filled in the carrying amount field of described default bearing ticket by described gateway or described packet data network gateway.
3. method according to claim 1, it is characterized in that, can unique identification packet data network gateway information with can the information that is connected of the unique identification Packet Data Network under same packet data network gateway be combined to indicate the Packet Data Network belonging to ticket to connect.
4. method according to claim 3, is characterized in that, described can the information of unique identification packet data network gateway be the address of described packet data gateway.
5. a ticket treatment system, comprising: packet data network gateway, gateway and charging gateway, is characterized in that,
Described packet data network gateway and described gateway comprise:
Arrange module, for arranging indication information in ticket, the Packet Data Network that described indication information is used to indicate belonging to described ticket connects;
Sending module, for sending to charging gateway by described ticket;
Described charging gateway comprises:
Receiver module, for receiving the ticket from described packet data network gateway and/or described gateway;
Merge module, for being merged by the ticket that same Packet Data Network is connected that belongs to from described gateway and described packet data network gateway respectively according to the indication information carried in the ticket that receives;
Statistical module, for the quantity according to the bearing identification statistics carrying in the ticket after merging;
Sending module, for sending to charging center by the ticket after merging; And,
Calling module, for by the quantity of carrying after statistics compared with the quantity of the carrying of carrying in default bearing ticket, if the same call described sending module and the ticket after merging is sent to charging center, otherwise, call described receiver module and described merging module and continue receive ticket and merge.
6. system according to claim 5, is characterized in that, describedly arranges module also for after default bearing terminates, and the carrying quantity of all establishments is filled in the carrying amount field of described default bearing ticket.
7. system according to claim 5, it is characterized in that, described arrange module can unique identification packet data network gateway information with the information that is connected of the unique identification Packet Data Network under same packet data network gateway can be set to described indication information.
8. system according to claim 7, is characterized in that, described arrange module the address of described packet data gateway is set to described can the information of unique identification packet data network 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 CN102202281A (en) | 2011-09-28 |
| CN102202281B true 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) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014015465A1 (en) * | 2012-07-23 | 2014-01-30 | 华为技术有限公司 | Charging information processing method, apparatus, and system |
| CN103384202B (en) * | 2013-07-17 | 2017-06-13 | 大唐移动通信设备有限公司 | The transmission method and equipment of a kind of flow report message |
| 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 |
| CN106332033A (en) * | 2015-06-17 | 2017-01-11 | 中兴通讯股份有限公司 | Method and device for generating telephone bill and packet data network 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 |
| CN108833724B (en) * | 2018-07-23 | 2021-03-19 | 北京邮电大学 | CDR synthesis method and device |
| CN110532294A (en) * | 2019-09-03 | 2019-12-03 | 中国联合网络通信集团有限公司 | Ticket merging method, device, equipment and computer readable 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102202281A (en) | 2011-09-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102202281B (en) | Ticket processing method and system | |
| CN101667920B (en) | Charging method and system and ticket generating device | |
| CN102075894B (en) | Selection method and system for policy and charging rules function entity | |
| CN101959252B (en) | Quality of service (QoS) control and strategy configuration method and device | |
| US9100816B2 (en) | Charging method, device, and system | |
| EP2642815A1 (en) | Method for establishing and using public path and m2m communication method and system | |
| US20130044646A1 (en) | Policy application method for machine type communication, and policy and charging enforcement function | |
| CN102763366A (en) | Diverse source message association | |
| CN103685582A (en) | PCRF addressing method, as well as system, terminal, server, PA equipment and DRA equipment corresponding to same | |
| CN102238517A (en) | Method, device and system for reporting machine type communication (MTC) events | |
| CN101998347B (en) | Methods and system for acquiring charging information of local internet protocol (IP) access | |
| KR101530501B1 (en) | Supported feature override | |
| CN104168553A (en) | Sending and charging method and device for service messages | |
| CN105208598A (en) | Network access method and apparatus | |
| CN101610496A (en) | Method, network entity and network system that a kind of route is handled | |
| CN105580425B (en) | Data connection for UE to 3GPP data access net provides the method and apparatus of on-demand QoS | |
| CN100397820C (en) | Charging method in communication system | |
| US8385361B2 (en) | Multicast transmission to a radio access network | |
| CN102413457A (en) | Uplink data message sending method and device | |
| WO2019042218A1 (en) | Charging realisation system, charging realisation method and charging management functional entity | |
| EP3057356A1 (en) | Capability negotiation method, system and apparatus | |
| CN101729265B (en) | Method, device and system for charging in evolved packet system (EPS) | |
| CN101316176B (en) | Service quality policy based charging method and resource admission control subsystem | |
| CN105188043A (en) | Method, device and system for charging based on PDN connection | |
| CN104735645A (en) | Method and interworking function device for converting routing parameters |
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 |