CN101453338B - Charging proxy entity, charging method and system - Google Patents
Charging proxy entity, charging method and system Download PDFInfo
- Publication number
- CN101453338B CN101453338B CN200710032297XA CN200710032297A CN101453338B CN 101453338 B CN101453338 B CN 101453338B CN 200710032297X A CN200710032297X A CN 200710032297XA CN 200710032297 A CN200710032297 A CN 200710032297A CN 101453338 B CN101453338 B CN 101453338B
- Authority
- CN
- China
- Prior art keywords
- charging
- entity
- message
- server
- authentication
- 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
Images
Abstract
The embodiment of the invention discloses a charging method under a charging entity separation architecture, which comprises: a charging proxy entity collects charging information from a data path functional entity; the charging proxy entity constructs charging messages when the charging information meets triggering conditions of the charging messages; and the charging proxy entity transmits the charging messages to an authentication and authorization charging server of a home location, and the charging messages are used for charging control. The embodiment of the invention also discloses the charging proxy entity and a charging system under the charging entity separation architecture. The invention solves the charging problem under a charging entity separation scene in an NWG protocol after transfer of an authentication device or an R3.
Description
Technical field
The present invention relates to the micro-wave access to global intercommunication technology, relate in particular to a kind of charging proxy entity and the charging method under the charging separation architecture.
Background technology
It is a kind of wireless metropolitan area network technology based on IEEE 802.16 standards that microwave interworking technology (WIMAX, Worldwide Interoperability for MicrowaveAccess) is inserted in the whole world.The WIMAX network mainly is made up of three parts, and is as shown in Figure 1:
Client, i.e. mobile subscriber station/subscriber station (MSS/SS, Mobile SubscriberStation/Subscriber Station);
Access service network (ASN; Access Service Network) comprises Authentication Authorization and charging proxy (AAA Proxy; Authentication Authorization Accounting Proxy), Authentication Authorization and Accounting Client (AAA Client; Authentication Authorization Accounting Client), charging proxy entity, prepayment client (Prepaid Client) and hot line equipment (HLD, Hot-Line Device); , accessing business network gate (ASN-GW, Access Service Network-Gateway);
Interconnect service network (CSN; Connectivity Service Network) comprises prepaid server (PPS; Prepaid Server), Authentication Authorization and accounting server (AAA Server; AuthenticationAuthorization Accounting Server), Authentication Authorization and Accounting Client, charging proxy entity, prepayment client, hot line equipment and home agent logic entities such as (HA, Home Agent).WIMAX network wireless side is based on the wireless MAN access technology of IEEE 802.16d/e standard.
The collection entity of definition charge information is charging proxy entity (AA, Accounting Agent) in the NWG Stage3 Release 1.1.0 version, and charging proxy entity and Accounting Client entity relationship are as shown in Figure 2:
Charging proxy entity can be positioned at base station (BS; Base Station), grappling data path functions entity (Anchor DPF; Anchor Data Path Function) or in the services data path functional entity (ServingDPF, Serving Anchor Data Path Function).
The entity that reports of charge information is Accounting Client entity (Accounting Client); Accounting Client entity and grappling data path functions entity are arranged in anchoring authentication device (Anchor Authenticator); Also can be arranged in HA; The Accounting Client entity is preserved charge information with the form of user data record (UDR, Usage Data Record), and charge information comprises flow, duration etc.
The charge information of paying in the back is produced by charging proxy entity, and charging proxy entity is collected unpressed up-downgoing flow information.
Authentication device (Authenticator) migration or R3 relocation (Relocation) all can cause the Accounting Client entity to separate with charging proxy entity; As shown in Figure 3: grappling data function entity/external agent (FA; Foreign Agent) and charging proxy entity; And authentication device, Accounting Client entity all be positioned on the gateway of access service network before separated migrates, and after the migration; Grappling data function entity/external agent and charging proxy entity are positioned on the gateway of same access service network, and authentication device, Accounting Client entity then are positioned on the gateway of another access service network.
The authentication device migration is meant authentication device and Accounting Client entity migration to new gateway, and grappling data path functions entity/external agent and charging proxy entity are on original gateway;
And R3 relocation, former grappling data path functions entity/external agent and charging proxy entity are moved on the new gateway, become new target data path functional entity/external agent, and authentication device and Accounting Client entity are positioned on the original gateway.
At this, gateway is a physical concept, grappling data function entity/external agent and charging proxy entity, and authentication device, Accounting Client entity then are the entities of dividing according to the function of said gateway.
The inventor finds that there is following shortcoming in prior art in embodiment of the present invention embodiment:
When authentication device migration or R3 relocation, can cause charging proxy entity and Accounting Client entity separation; But the NWG agreement does not define the charging flow after charging entity is separated; In order to guarantee the precision of chargeing; Can only and report the Accounting Client entity by the charging proxy entity collecting charging information, Accounting Client entity maintaining UDR record and generation charging message are issued aaa server.Can cause between them the charging Signalling exchange frequent like this, lack fail safe and stability.
Summary of the invention
The embodiment of the invention provides a kind of charging proxy entity; And charging method under the charging entity separation architecture and system, through charging proxy entity collecting charging information from the data path functions entity, and generate charging message; And charging message is sent to aaa server; Avoid frequent Signalling exchange, can solve under the charging entity separation scene, the charging problem behind authentication device migration or the R3 relocation.Described charging entity is separated, and is meant that Accounting Client entity and charging proxy entity functional entity are separated from each other in authentication device migration or R3 relocation process.
For addressing the above problem, the embodiment of the invention provides the charging method under a kind of charging entity separation architecture, comprising:
Charging proxy entity is collecting charging information from the data path functions entity;
When said charge information satisfies the charging message trigger condition, charging proxy entity structure charging message;
Charging proxy entity sends to the authentication authorized charging server of ownership place with said charging message, is used for the control of chargeing.
The embodiment of the invention also provides a kind of charging proxy entity, comprising:
The information gathering module is used for from data path functions entity collecting charging information;
The message constructing module is used for when said charge information satisfies the charging message trigger condition, according to said charge information structure charging message;
Message transmission module is used for said charging message is sent to the authentication authorized charging server of ownership place.
Correspondingly, the embodiment of the invention also provides the charge system under a kind of charging entity separation architecture, comprising:
The data path functions entity is used to charging proxy entity and offers charge information;
Charging proxy entity is collected said charge information from said data path functions entity, when said charge information satisfied the charging message trigger condition, the structure charging message also was sent to the authentication authorized charging server of ownership place;
The authentication authorized charging server of ownership place is used to receive the charging message that said charging proxy entity sends, and according to the control of chargeing of said charging message.
Embodiment of the present invention has following beneficial effect:
Charging proxy entity is collecting charging information from the data path functions entity, and constructs corresponding charging message according to said charge information and be sent to authentication authorized charging server; Said authentication authorized charging server is according to said charging message, the control of chargeing accordingly.Because said data path functions entity and charging proxy entity be in the authentication device migration perhaps behind the R3 relocation, also on same physical gateway, the Signalling exchange that charging proxy entity need not be frequent; Can construct charging message from collecting charging information on the data path functions entity, offer the authentication authorized charging server control of chargeing; And do not need again charge information to be sent to the Accounting Client entity; Construct charging message by the Accounting Client entity, avoided frequent Signalling exchange, improved stability and fail safe; Thereby solved in the NWG agreement under the charging entity separation scene charging problem behind authentication device migration or the R3 relocation.
Description of drawings
Fig. 1 is the configuration diagram of charging network in the prior art;
Fig. 2 be in the prior art charging proxy entity and Accounting Client entity concern sketch map;
Fig. 3 is the sketch map that authentication device migration/R3 relocation causes charging proxy entity and Accounting Client entity separation in the prior art;
Fig. 4 is the schematic flow sheet of first embodiment of the charging method under the charging entity separation architecture that provides of the embodiment of the invention;
Fig. 5 is the schematic flow sheet of second embodiment of the charging method under the charging entity separation architecture that provides of the embodiment of the invention;
Fig. 6 is the schematic flow sheet of the 3rd embodiment of the charging method under the charging entity separation architecture that provides of the embodiment of the invention;
Fig. 7 is the schematic flow sheet of the 4th embodiment of the charging method under the charging entity separation architecture that provides of the embodiment of the invention;
Fig. 8 is the schematic flow sheet of the 5th embodiment of the charging method under the charging entity separation architecture that provides of the embodiment of the invention.
Fig. 9 is the composition sketch map of first embodiment of the charge system under the charging entity separation architecture that provides of the embodiment of the invention;
Figure 10 is the composition sketch map of second embodiment of the charge system under the charging entity separation architecture that provides of the embodiment of the invention;
Figure 11 is the structural representation of charging proxy entity first embodiment that provides of the embodiment of the invention;
Figure 12 is the structural representation of charging proxy entity second embodiment that provides of the embodiment of the invention;
Figure 13 is the composition sketch map of the message constructing module of the charging proxy entity that provides of the embodiment of the invention;
Figure 14 is the composition sketch map of visit ground authentication authorized charging server in the charge system as shown in Figure 9 that provides of the embodiment of the invention;
Figure 15 is the composition sketch map of charging clients entities in the charge system shown in figure 10 that provides of the embodiment of the invention;
Embodiment
The embodiment of the invention provides a kind of charging proxy entity, and charging method under the charging entity separation architecture and system, has solved under the charging entity separation scene charging problem behind authentication device migration or the R3 relocation.
Referring to Fig. 4, be the schematic flow sheet of first embodiment of the charging method under the charging entity separation architecture that provides of the embodiment of the invention;
Charging method under the said charging entity separation architecture comprises following flow process:
At step S100, charging proxy entity is collecting charging information from the data path functions entity;
At step S101, when said charge information satisfies the charging message trigger condition, with the charging proxy entity of said data path functions entity on same gateway according to said charge information, the structure charging message; Said charging message trigger condition comprises the beginning message trigger condition of chargeing, chargeing stops the message trigger condition; Pre-payment message trigger condition; Back paying message trigger condition etc., correspondingly, the charging message that generates according to said charging message trigger condition comprises the beginning message of chargeing, chargeing stops message; Pre-payment message, back paying message or the like;
At step S102, said charging message is sent to the authentication authorized charging server of ownership place;
Need to prove; When remote authentication dial-in user service message (Radius is passed through in configuration; RemoteAuthentication Dial In User Service) when chargeing, sends it to the ownership place authentication authorized charging server through visit ground authentication authorized charging server; When configuration was chargeed through R4 message, back paying scene structure R4 charging message was issued the Accounting Client entity of authentication device place gateway, sends to the ownership place authentication authorized charging server through the Accounting Client entity; The online quota updating message of pre-payment scene structure R4 is issued the pre-payment agent entity of authentication device place gateway, sends to the ownership place authentication authorized charging server through the prepayment client entity.
At step S103, said ownership place authentication authorized charging server is according to the control of chargeing accordingly of said charging message, and said charging message comprises the beginning message of chargeing, chargeing stops message; Pre-payment message; Back paying message or the like, corresponding charging are controlled to be and begin to charge, and stop to charge; Pre-payment funds, postpaid accounting etc. charge and control.
The charging method that the embodiment of the invention provides, charging proxy entity is collecting charging information from the data path functions entity, and constructs corresponding charging message according to said charge information and be sent to authentication authorized charging server; Said authentication authorized charging server is according to said charging message, the control of chargeing accordingly.Because said data path functions entity and charging proxy entity be in the authentication device migration perhaps behind the R3 relocation, also on same physical gateway, the Signalling exchange that charging proxy entity need not be frequent; Can construct charging message from collecting charging information on the data path functions entity, offer the authentication authorized charging server control of chargeing; And do not need again charge information to be sent to the Accounting Client entity; Construct charging message by the Accounting Client entity, avoided frequent Signalling exchange, improved stability and fail safe; Thereby solved in the NWG agreement under the charging entity separation scene charging problem behind authentication device migration or the R3 relocation.
Fig. 5 is the schematic flow sheet of second embodiment of the charging method under the charging entity separation architecture that provides of the embodiment of the invention;
The prerequisite of the embodiment of the invention is: authentication device did not move when R3 relocation took place; Migration back grappling data path functions entity/external agent/charging proxy entity takes place to be positioned on the intended gateway; Authentication device/Accounting Client entity is positioned on the anchor ASN-GW, on intended gateway, disposes and charges through the R4 charging message.
Back paying flow process after the embodiment of the invention is separated with charging entity is the flow process that example is explained the charging method that the embodiment of the invention provides:
At step S201-S204; No matter be the R3 relocation that anchor ASN-GW or intended gateway are initiated; Anchor ASN-GW is confirming that R4 directly connects triggering (Achor DPF HO Req) message initiation R3 relocation process through send grappling data path functions entity to intended gateway after switching completion; This message of protocol definition is carried information such as authentication device ID, grappling external agent's Care-of Address, mobile network protocol (MIP, Mobile Internet Protocol) association key, DHCP (DHCP, Dynamic Host Configuration Protocol) lease; For supporting billing function, can also carry following information as required in the message:
Acct-Multi-Session-Id (the unified charging identifier of all sessions of user)
PDF ID (service bearer stream identification)
SDF ID (service application stream identification)
AF-Charging-Id (the application layer charging identifier in the PCC framework)
User Priority (user gradation)
Acct-Interim-Interval (sending the time interval of interim UDR)
At step S205-S213, after R3 relocation was accomplished, intended gateway was accomplished through the direct connection response of grappling data path functions entity (Achor DPF HO Rsp) message informing anchor ASN-GW R3 relocation;
At step S214, on anchor ASN-GW, after grappling data path functions entity was received the Achor DPFHO Rsp message of success, notice FA discharged and is connected with the R3 of HA, notified charging proxy entity to stop to charge simultaneously;
At step S215, receive the Radius that sends from the Accounting Client entity charge stop request message after, the AAA accounting server sends to charge to the Accounting Client entity and stops response message;
At step S216, the data path functions entity sends the beginning request message that charges to charging proxy entity/pre-payment agency;
At step S217-S220; On intended gateway; The data path functions entity is through Achor DPF HORsp message informing anchor ASN-GW R3 relocation successful the time; Notify the charging proxy entity of this gateway to create the UDR record; And the charge information that passes in the R3 relocation process write UDR, and charging proxy entity charges the charge information structure R4 in the UDR record and begins request (Acct Req Start) message and issue the Accounting Client entity on the Anchor GW, and the Accounting Client entity is according to charge beginning request message and issue the AAA accounting server of R4 Acct Req Start message constructing Radius.
At step S221-S224; On intended gateway; When satisfying the trigger condition of charging updating message; Charging proxy entity is issued the Accounting Client entity on the anchor ASN-GW with charge information structure R4 Acct Req (Interim-update) message in the UDR record, and the Accounting Client entity is according to R4 Acct Req message constructing Radius charging update inquiry information and issue the AAA accounting server.
At step S225-S228; On intended gateway; When satisfied charging stops the message trigger condition; Charging proxy entity is issued the Accounting Client entity on the anchor ASN-GW with charge information structure R4 Acct Req (Stop) message in the UDR record, and the Accounting Client entity charges according to R4 Acct Req (Stop) message constructing Radius and stops request message and issue the AAA accounting server.
Fig. 6 is the schematic flow sheet of the 3rd embodiment of the charging method under the charging entity separation architecture that provides of the embodiment of the invention;
The prerequisite of the embodiment of the invention is equally: authentication device did not move when R3 relocation took place; Migration back grappling data path functions entity/external agent/charging proxy entity takes place to be positioned on the intended gateway; Authentication device/Accounting Client is positioned on the anchor ASN-GW, on intended gateway, disposes and charges through the R4 charging message.
Pre-payment flow process after the embodiment of the invention is separated with charging entity is the flow process that example is explained the charging method that the embodiment of the invention provides:
At step S301-S304; No matter be the R3 relocation that anchor ASN-GW or intended gateway are initiated; Anchor ASN-GW is confirming that R4 initiates the R3 relocation process through send Anchor DPF HO Req message to intended gateway after switching completion; This message of protocol definition is carried information such as authentication device ID, grappling external agent's Care-of Address, MIP association key, DHCP lease, is to support billing function, can also carry following information as required in the message:
Prepaid accounting sign (QID, Quota Identity) in the prepaid accounting quota (PPAQ, Prepaid Accounting Quota);
Pre-payment Server IP address (the IP address of prepaid server)
At step S305-S310, after R3 relocation was accomplished, intended gateway was accomplished through Achor DPF HO Rsp message informing anchor ASN-GW R3 relocation;
At step S311, on anchor ASN-GW, the data path functions entity receives Achor DPF HO Rsp message;
Carry step S312, data path functions entity notice FA discharges and is connected with the R3 of HA;
At step S313, data path functions entity notice prepayment client stops to charge;
At step S314, Accounting Client/prepayment client sends online authentication to aaa server/prepaid server and inserts request (Online-Access Request) message;
At step S315, aaa server/prepaid server is sent response message to Accounting Client/prepayment client and is returned unspent quota;
At step S316, the data path functions entity sends the beginning request message that charges to charging proxy/pre-payment agency;
At step S317-S320; On intended gateway; The data path functions entity is through Achor DPF HORsp message informing anchor ASN-GW R3 relocation successful the time, notifies the beginning of chargeing of the prepayment client of this gateway, prepayment client according to the configuration decision to the prepayment client entity transmission R4Online-Access of anchor ASN-GW Request message request quota; Carry the QID and the certificate server IP address that obtain from anchor ASN-GW in the message; The prepayment client entity of anchor ASN-GW is received the quota updating message, according to the certificate server IP address in the message, online authentication is inserted request (Online-Access Request) issue on the aaa server with prepaid server function of appointment; Aaa server continues as this user's allocated quotas according to QID; And issue the prepayment client of anchor ASN-GW through Online-Access Accept message, and the prepayment client entity of anchor ASN-GW is issued the pre-payment agent entity of intended gateway again through R4 Online-Access Accept message, and the beginning user data was transmitted after intended gateway obtained quota; Also can transmit data earlier, deduct the quota of using in advance here again.
At step S321-S324; On intended gateway; When the pre-payment quota reaches or the user moves back when net; Prepayment client sends R4 Online-Access Request message request renewal quota or returns quota to the prepayment client entity of anchor ASN-GW; Carry the QID and the certificate server IP address that obtain from anchor ASN-GW in the message, the prepayment client entity of anchor ASN-GW is received online quota updating message, according to the certificate server IP address in the message; Online-Access Request is issued on the aaa server with PPS function of appointment; Aaa server continues as these user's allocated quotas or returns quota according to QID, and issues the prepayment client of anchor ASN-GW through Online-Access Accept message, and the prepayment client entity of anchor ASN-GW is issued the pre-payment agent entity of intended gateway again through R4 Online-Access Accept message.
Fig. 7 is the schematic flow sheet of the 4th embodiment of the charging method under the charging entity separation architecture that provides of the embodiment of the invention;
The prerequisite of the embodiment of the invention is: data path functions entity/external agent did not move when the authentication device migration took place; Migration back grappling data path functions entity/external agent/charging proxy entity takes place to be positioned on the original gateway; Authentication device/Accounting Client entity is positioned on the new gateway, on former gateway, disposes and charges through Radius message.
Back paying flow process after the embodiment of the invention is separated with charging entity is the flow process that example is explained the charging method that the embodiment of the invention provides:
At step S401-S402, new authentication gateway sends announcing removal message to former authentication gateway, and former authentication gateway gets into " discrimination weight locking " state, replys the announcing removal response message to new authentication gateway then;
At step S403, new authentication gateway begins the discrimination weight process of user through new authentication gateway after receiving response message;
At step S404-S406; New authentication gateway is accomplished request message through migration and is notified former authentication gateway user to accomplish through the discrimination weight process of new authentication gateway; Former authentication gateway finishes " discrimination weight locking " state; Delete user's authentication record, and reply migration to new authentication gateway and accomplish response message, new authentication gateway is confirmed through accomplishing acknowledge message to former authentication gateway transmission migration after receiving response message;
At step S407, on former authentication gateway, the authentication device functional entity notifies the charging proxy entity on the same gateway to stop the charging through former authentication device after receiving that acknowledge message is accomplished in migration, changes into through new authentication device and chargeing;
At step S408-S413; Charging proxy entity is received that structure Radius charges behind the notification message of authentication device and is stopped request message and send to authentication authorized charging server; Notify structure R4 to charge and begin the Accounting Client entity that request message also sends to new authentication device place gateway, the Accounting Client entity is according to R4 charging beginning request message structure Radius charging beginning request message and issue the AAA accounting server.
At step S414-S417; On the gateway of former authentication device place; When satisfying the trigger condition of charging updating message; Charging proxy entity is collected the charge information structure R4 charging update inquiry information that writes down in the data path functions entity of former authentication device place gateway and is issued the Accounting Client entity on the gateway of new authentication device place, and the Accounting Client entity is according to R4 charging update inquiry information structure Radius charging update inquiry information and issue the AAA accounting server.
At step S418-S421; On the gateway of former authentication device place; When satisfied charging stops the trigger condition of message; Charging proxy entity is collected charge information structure R4 charging the stopping request message that writes down in the data path functions entity of former authentication device place gateway and is issued the Accounting Client entity on the gateway of new authentication device place, and the Accounting Client entity charges according to R4 charging stopping request message structure Radius and stops request message and issue the AAA accounting server.
Fig. 8 is the schematic flow sheet of the 5th embodiment of the charging method under the charging entity separation architecture that provides of the embodiment of the invention.
The prerequisite of the embodiment of the invention is equally: data path functions entity/external agent did not move when the authentication device migration took place; Migration back grappling data path functions entity/external agent/charging proxy entity takes place to be positioned on the original gateway; Authentication device/Accounting Client entity is positioned on the new gateway, on former gateway, disposes and charges through R4 message.
Pre-payment flow process after the embodiment of the invention is separated with charging entity is the flow process that example is explained the charging method that the embodiment of the invention provides:
At step S501-S502, new authentication gateway sends announcing removal message to former authentication gateway, and former authentication gateway gets into " discrimination weight locking " state, replys the announcing removal response message to new authentication gateway then;
At step S503, new authentication gateway begins the discrimination weight process of user through new authentication gateway after receiving response message;
At step S504-S506; New authentication gateway is accomplished request message through migration and is notified former authentication gateway user to accomplish through the discrimination weight process of new authentication gateway; Former authentication gateway finishes " discrimination weight locking " state; Delete user's authentication record, and reply migration to new authentication gateway and accomplish response message, new authentication gateway is confirmed through accomplishing acknowledge message to former authentication gateway transmission migration after receiving response message;
At step S507, on former authentication gateway, the authentication device functional entity notifies the pre-payment agent entity on the same gateway to stop the pre-payment through former authentication device after receiving that acknowledge message is accomplished in migration, changes into through new authentication device pre-payment;
At step S508-S513; On former authentication gateway; The pre-payment agent entity is received behind the above-mentioned notification message of authentication device the structure online authentication request message of Radius and is sent to the authentication authorized charging server with prepaid server function; In this message, return quota through former authentication server application; The pre-payment agency structure online authentication request message of R4 also sends to the prepayment client entity that new authentication device belongs to gateway; Carry the IP address information of QID and prepaid server in the message; Prepayment client entity on the gateway of new authentication device place is according to the online authentication request message of Radius of the online authentication request message structure of R4 standard, and the online authentication request message of Radius issued the authentication authorized charging server with pre paid functionality of appointment according to the prepaid server IP address information in the online authentication request message of R4.Authentication authorized charging server continues as this user's allocated quotas according to QID; And accept message through online authentication and issue the prepayment client that new authentication device belongs to gateway; The prepayment client entity is accepted the pre-payment agent entity that message is issued former authentication device place gateway through the online authentication of R4 again; The beginning user data was transmitted after former authentication device gateway obtained quota, also can transmit data earlier, deducted the quota of using in advance here again.
At step S521-S524; On former authentication gateway; When the pre-payment quota reaches or the user moves back when net; The pre-payment agency sends the online authentication request message request renewal quota of R4 or returns quota to the prepayment client entity of new authentication device place gateway; Carry the IP address of QID and prepaid server in the message, the prepayment client entity of new authentication device place gateway is received online quota updating message, according to the certificate server IP address in the message; Online authentication request message is issued on the aaa server with PPS function of appointment; Aaa server continues as these user's allocated quotas or returns quota according to QID, and accepts the prepayment client that message is issued new authentication device place gateway through online authentication, and the prepayment client entity of new authentication device place gateway is accepted the pre-payment agent entity that message is issued former authentication device place gateway through the online authentication of R4 again.
The charging method that the embodiment of the invention provides; Through the charge information that in the R3 relocation process, carries; Charging proxy entity is collected the charge information that writes down in the data path functions entity of also safeguarding former authentication device place gateway, and constructs corresponding charging message according to said charge information and be sent to authentication authorized charging server; Said authentication authorized charging server is according to said charging message, and the control of chargeing has accordingly solved in the NWG agreement under the charging entity separation scene charging problem behind authentication device migration or the R3 relocation.
Referring to Fig. 9, be the composition sketch map of first embodiment of the charge system under the charging entity separation architecture that provides of the embodiment of the invention;
At first explanation is; When authentication device moves; Authentication device and Accounting Client entity migration are to new gateway; Grappling data path functions entity/external agent and charging proxy entity are on original gateway, and therefore being kept at the last charge information of grappling data path functions entity/external agent does not migrate to new gateway, can directly offer charging proxy entity structure charging message; Said charging proxy entity sends to the authentication authorized charging server of ownership place with the charging message of its structure, thereby realizes the control of chargeing; And when R3 relocation; Former grappling data path functions entity/external agent and charging proxy entity are moved on the new gateway; Become new target data path functional entity/external agent; Authentication device and Accounting Client entity are positioned on the original gateway, therefore then need be in R3 relocation message, and target data path functional entity/external agent that the last charge information of grappling data path functions entity/external agent is sent on the new gateway was last with being kept at originally; Carry charge information, be sent to the charging proxy entity on the new gateway; Said charging proxy entity sends to the authentication authorized charging server of ownership place with the charging message of its structure, thereby realizes the control of chargeing.It is thus clear that authentication device migration offers the charging proxy entity except needn't be in transition process charge information being carried in the migration message, its follow-up processing is identical with R3 relocation.
Here only be that the charge system that provides in the example explanation embodiment of the invention comprises with the R3 relocation:
Grappling data path functions entity 10, in the R3 relocation process, the anchor ASN-GW 1 through its place sends the migration message to the target data path functional entity 20 of intended gateway 2; Carry charge information in the said migration message;
Target data path functional entity 20 is used to receive the said migration message that carries charge information, and to said grappling data path functions entity 10 remigration response messages;
Charging proxy entity 21; Be used for creating the user data record according to the indication of said target data path functional entity 20; And according to the charge information that carries in the migration message; Structure Radius charging message is sent to ownership place authentication authorized charging server 3 through visit ground authentication authorized charging server 4;
Ownership place authentication authorized charging server 3 is used for according to said Radius charging message the control of chargeing accordingly.
Need to prove; Above-mentioned anchor ASN-GW 1 is two gateway entities that separate with intended gateway 2; Comprise a plurality of functional entitys in each gateway entity; Like data path functional entity, direct connection device (HomeOn), act on behalf of mobile network protocol client (PMIP Client, Proxy Mobile Internet Protocol), charging proxy entity or the like.
After charging proxy entity and the Accounting Client entity separation; Charging proxy entity is created the UDR record according to the indication that it separates the data path functions entity of place, back gateway; In the present embodiment, charging proxy entity 21 is created the UDR record according to the indication of the target data path functional entity 20 in the intended gateway 2 at its place, the charge information of collection and maintenance customer or Business Stream; After satisfying the charging message formation condition; Construct the Radius charging message, issue ownership place authentication authorized charging server 3, said Radius charging message can be issued ownership place authentication authorized charging server 3 through following path:
Intended gateway 2 through the charging proxy entity place is sent to visit ground authentication authorized charging server 4 with said Radius charging message;
Visit ground authentication authorized charging server 4 between intended gateway 2 and the ownership place authentication authorized charging server 3 is acted on behalf of according to the domain name in charging or the authentication message, and said Radius charging message is sent to ownership place authentication authorized charging server 3.
The benefit in said path is to need not to increase R4 charging message reciprocal process, and Radius charging flow and agency (Proxy) flow process of utilizing standard is delivered to user's charging related news on visit ground authentication authorized charging server 4 and the ownership place authentication authorized charging server 3.
Referring to Figure 10, be the composition sketch map of second embodiment of the charge system under the charging entity separation architecture that provides of the embodiment of the invention;
Identical with above-mentioned charge system first embodiment, only be the charge system that provides in the example explanation embodiment of the invention here with the R3 relocation, comprising:
Grappling data path functions entity 10, in the R3 relocation process, the anchor ASN-GW 1 through its place sends the migration message to the target data path functional entity 20 of intended gateway 2; Carry charge information in the said migration message;
Target data path functional entity 20 is used to receive the said migration message that carries charge information, and to said grappling data path functions entity 10 remigration response messages;
Charging proxy entity 21; Be used for creating the user data record according to the indication of said target data path functional entity 20; And according to the charge information that carries in the migration message, structure R4 charging message is sent to ownership place authentication authorized charging server 3 through authentication gateway 5;
Ownership place authentication authorized charging server 3 is used for according to said Radius charging message the control of chargeing accordingly.
Need to prove that above-mentioned anchor ASN-GW 1 is meant two gateway entities that separate with intended gateway 2, comprises a plurality of functional entitys in each gateway entity, like data path functional entity, HO, PMIP Client, charging proxy entity etc.
At first, charging proxy entity 21 is sent to the said R4 charging message of its structure the authentication gateway 5 at Accounting Client entity 50 (or authentication device 51) place;
The advantage in said path is in charging flow, to add the controlled function of separating network element, realizes above-mentioned specific function.
Specify the charging proxy entity 21 in the charge system that provides like Fig. 9 or embodiment shown in Figure 10 below in conjunction with Figure 11.
Said charging proxy entity 21 comprises:
Need to prove; Behind R3 relocation, data path functions entity and said charging proxy entity migrate in the intended gateway, and said data path functions entity is called the target data path functional entity; Data path functions entity before the migration is called grappling data path functions entity; In the R3 relocation process, grappling data path functions entity is used for sending migration message to said target data path functional entity, carries charge information in the said migration message.
Referring to Figure 12, said charging proxy entity 21 is except comprising: information gathering module 211, message constructing module 212, the message transmission module 213, also comprise:
User data logging modle 210 is used to preserve said charge information, and said user data logging modle 210 is created according to the indication of data path functions entity behind R3 relocation.
Figure 13 is the composition sketch map of the message constructing module of the charging proxy entity 21 that provides of the embodiment of the invention;
Said message constructing module 212 specifically comprises:
R4 charging message structural unit 2120 is used for when the charge information that the user data that said charging proxy entity 21 is created writes down satisfies the charging message trigger condition, according to said charge information structure R4 charging message; Said charging message trigger condition comprises the beginning message trigger condition of chargeing, chargeing stops the message trigger condition; Pre-payment message trigger condition; Back paying message trigger condition etc., correspondingly, the R4 charging message that generates according to said charging message trigger condition comprises that R4 charging beginning message, R4 charge and stop message; R4 pre-payment message, paying message or the like behind the R4;
Radius charging message structural unit 2121 is used for when the charge information that the user data that said charging proxy entity 21 is created writes down satisfies the charging message trigger condition, according to said charge information structure Radius charging message.Said charging message trigger condition comprises the beginning message trigger condition of chargeing, chargeing stops the message trigger condition; Pre-payment message trigger condition; Back paying message trigger condition etc., correspondingly, the Radius charging message that generates according to said charging message trigger condition comprises that Radius charging beginning message, Radius charge and stop message; Radius pre-payment message, paying message or the like behind the Radius;
Need to prove that the form of R4 charging message is following:
| Message?Name | Function Type | Messa ge Type | ||||
| R4?Accounting?Request/Response | Wait to apply for | Wait to apply for | ||||
| IE?Name | Type | Length | Value | IE describes | M/O | |
| MS? |
21 | Variable | Form by its sub-TLV IE | The information of relevant MS is described | M | |
| Sub-IE | MS?ID | 200 | 6 | Binary | The MAC address of MS belongs to the field of MS Info | M |
| The Radius charging message | Wait to apply for | Variable | The Radius charging message comprises the IP/UDP head | Please refer to RFC2866 | M | |
Figure 14 is the composition sketch map of visit ground authentication authorized charging server 4 in the charge system as shown in Figure 9 that provides of the embodiment of the invention;
Said visit ground authentication authorized charging server 4 comprises:
Information sending module 41 is used for said Radius charging message is sent to the authentication authorized charging server 3 of ownership place.
Figure 15 is the composition sketch map of charging clients entities in the charge system shown in figure 10 that provides of the embodiment of the invention;
Said Accounting Client entity 5 comprises:
Information sending module 52 is used for said standardized Radius charging message is sent to the authentication authorized charging server 3 of ownership place.
Specifically; After the information receiving module 50 of Accounting Client entity 5 is received the R4 charging message of charging proxy entity 21 transmissions; Information standardization module 51 is converted into the Radius charging message with R4 charging message (R4 Accoumting Request), and information sending module 52 sends it to AAA accounting server 3.
The online quota updating message of R4 form is following:
| Message?Name | Function?Type | Messa ?ge |
| Type | ||||||
| R4?Online-Access?Request/Accept/Reject | Wait to apply for | Wait to apply for | ||||
| IE?Name | Type | Length | Value | IE describes | M/O | |
| MS? |
21 | Variable | Form by its sub-TLV IE | The information of relevant MS is described | M | |
| Sub-IE | MS?ID | 200 | 6 | Binary | The MAC Address of MS belongs to the field of MS Info | M |
| PPS?IP | Wait to apply for | 4 | The IP address of prepaid server | The IP address of prepaid server | O | |
| Radius Online-Access Request/Accept/ Reject message | Wait to apply for | Variable | Radius Online-Access Request/Accept/Reject message comprises the IP/UDP head | Please refer to RFC2865 | M | |
Need to prove; When receiving said R4 charging message when being the online quota updating message of above-mentioned R4; Prepayment client is the Radius form with this message conversion, this message is issued the prepaid server of appointment according to the prepaid server IP address in the online quota updating message of R4 then.
In like manner charge or message that prepaid server is returned also is forwarded on the charging proxy entity/pre-payment agent entity of grappling data path functions entity place gateway through the Accounting Client entity/prepayment client entity of authentication device place gateway.
Charging proxy entity/prepaid server the entity of grappling data path functions entity place gateway carries out the control and the charging information collecting of back paying and pre-payment; Trigger when satisfying charging message trigger condition or quota threshold value and reaching and charge or online quota updating message, and transmit through authentication device place gateway.
The charging proxy entity of embodiment of the present invention embodiment, charging method and system have following beneficial effect:
Charging proxy entity is collecting charging information from the data path functions entity, and constructs corresponding charging message according to said charge information and be sent to authentication authorized charging server; Said authentication authorized charging server is according to said charging message, the control of chargeing accordingly.Because said data path functions entity and charging proxy entity be in the authentication device migration perhaps behind the R3 relocation, also on same physical gateway, the Signalling exchange that charging proxy entity need not be frequent; Can construct charging message from collecting charging information on the data path functions entity, offer the authentication authorized charging server control of chargeing; And do not need again charge information to be sent to the Accounting Client entity; Construct charging message by the Accounting Client entity, avoided frequent Signalling exchange, improved stability and fail safe; Thereby solved in the NWG agreement under the charging entity separation scene charging problem behind authentication device migration or the R3 relocation.
Above disclosedly be merely a kind of preferred embodiment of the present invention, can not limit the present invention's interest field certainly with this, the equivalent variations of therefore doing according to claim of the present invention still belongs to the scope that the present invention is contained.
Claims (18)
1. the charging method under the charging entity separation architecture, this charging entity separation architecture is the framework that Accounting Client entity and charging proxy entity functional entity are separated from each other in authentication device migration or R3 relocation process, it is characterized in that, comprising:
Charging proxy entity is collecting charging information from the data path functions entity;
When said charge information satisfies the charging message trigger condition, charging proxy entity structure charging message;
Charging proxy entity sends to the authentication authorized charging server of ownership place with said charging message, is used for the control of chargeing.
2. the charging method under the charging entity separation architecture as claimed in claim 1 is characterized in that, the step of said charging proxy entity collecting charging information from the data path functions entity comprises:
In the R3 relocation process, the target data path functional entity receives the migration message of sending from grappling data path functions entity; Carry charge information in the said migration message;
Target data path functional entity indication charging proxy entity is created the user data record;
Charging proxy entity is created the user data record according to the indication of said target data path functional entity, collects the charge information that carries in the said migration message, and is kept in the said user data record.
3. the charging method under the charging entity separation architecture as claimed in claim 1 is characterized in that, the step of said charging proxy entity collecting charging information from the data path functions entity comprises:
In the authentication device transition process, charging proxy entity is collecting charging information from grappling data path functions entity.
4. like the charging method under claim 2 or the 3 described charging entity separation architectures, it is characterized in that the charging message of said charging proxy entity structure comprises R4 charging message or remote authentication dial-in user service Radius charging message.
5. the charging method under the charging entity separation architecture as claimed in claim 4; It is characterized in that; When said charging proxy entity constructed the R4 charging message, charging proxy entity comprised the step that said charging message sends to the authentication authorized charging server of ownership place:
Charging proxy entity is sent to the Accounting Client entity with said R4 charging message;
Said Accounting Client entity is standardized as the Radius charging message with the R4 charging message;
Accounting Client is sent to said Radius charging message the authentication authorized charging server of ownership place.
6. the charging method under the charging entity separation architecture as claimed in claim 5; It is characterized in that; Said R4 charging message comprises that R4 charging beginning request message, R4 charging update inquiry information, R4 charge and stop request message; Said authentication authorized charging server is according to said R4 charging message, the control of chargeing accordingly.
7. the charging method under the charging entity separation architecture as claimed in claim 4; It is characterized in that; When said charging proxy entity constructed the Radius charging message, charging proxy entity comprised the step that said charging message sends to the authentication authorized charging server of ownership place:
Charging proxy entity is sent to authentication authorized charging server with said Radius charging message;
Said authentication authorized charging server is sent to said Radius charging message the authentication authorized charging server of ownership place.
8. the charging method under the charging entity separation architecture as claimed in claim 7; It is characterized in that; Said Radius charging message comprises that Radius charging beginning request message, Radius charging update inquiry information, Radius charge and stop request message; Said authentication authorized charging server is according to said Radius charging message, the control of chargeing accordingly.
9. the charging method under the charging entity separation architecture described in claim 2; It is characterized in that the charge information that carries in the said migration message comprises: the IP address of session identification, service application stream identification, service bearer stream identification, application layer charging identifier, user gradation, the time interval, prepaid accounting quota sign, prepaid server.
10. the charging proxy entity under the charging entity separation architecture, this charging entity separation architecture is the framework that Accounting Client entity and charging proxy entity functional entity are separated from each other in authentication device migration or R3 relocation process, it is characterized in that, comprising:
The information gathering module is used for from data path functions entity collecting charging information;
The message constructing module is used for when said charge information satisfies the charging message trigger condition, according to said charge information structure charging message;
Message transmission module is used for said charging message is sent to the authentication authorized charging server of ownership place.
11. charging proxy entity as claimed in claim 10 is characterized in that, said message constructing module comprises:
R4 charging message structural unit is used for according to the charging message trigger condition, structure R4 charging message;
Remote authentication dial-in user service Radius charging message structural unit is used for according to the charging message trigger condition, structure Radius charging message.
12., it is characterized in that said charging proxy entity also comprises like claim 10 or 11 described charging proxy entities:
The user data logging modle is used to preserve said charge information, and said user data logging modle is created according to the indication of data path functions entity behind R3 relocation.
13. the charge system under the charging entity separation architecture, this charging entity separation architecture are the frameworks that Accounting Client entity and charging proxy entity functional entity are separated from each other in authentication device migration or R3 relocation process, it is characterized in that, comprising:
The data path functions entity is used to charging proxy entity charge information is provided;
Charging proxy entity is collected said charge information from said data path functions entity, when said charge information satisfied the charging message trigger condition, the structure charging message also was sent to the authentication authorized charging server of ownership place;
The authentication authorized charging server of ownership place is used to receive the charging message that said charging proxy entity sends, and according to the control of chargeing of said charging message.
14. the charge system under the charging entity separation architecture as claimed in claim 13 is characterized in that,
When R3 relocation took place, said data path functions entity and said charging proxy entity migrated in the intended gateway, and said data path functions entity is called the target data path functional entity, and then said system also comprises:
Grappling data path functions entity in the R3 relocation process, is used for sending migration message to said target data path functional entity, carries charge information in the said migration message.
15. the charge system under the charging entity separation architecture as claimed in claim 13 is characterized in that, said system also comprises:
The Accounting Client entity is used to receive said charging proxy entity to the R4 of its transmission charging message, and it is standardized as the authentication authorized charging server that the Radius charging message is sent to ownership place.
16. the charge system under the charging entity separation architecture as claimed in claim 15 is characterized in that, said Accounting Client entity comprises:
Information receiving module is used to receive said charging proxy entity to the R4 of its transmission charging message;
The information standardization module is used for said R4 charging message is standardized as the Radius charging message;
Information sending module is used for said standardized Radius charging message is sent to the authentication authorized charging server of ownership place.
17. the charge system under the charging entity separation architecture as claimed in claim 13 is characterized in that, said system also comprises:
Visit ground authentication authorized charging server is used to receive the Radius charging message that sends from said charging proxy entity, and said Radius charging message is sent to the authentication authorized charging server of ownership place.
18. the charge system under the charging entity separation architecture as claimed in claim 17 is characterized in that, said visit ground authentication authorized charging server comprises:
Information receiving module is used to receive said charging proxy entity to the Radius of its transmission charging message;
Information sending module is used for said Radius charging message is sent to the authentication authorized charging server of ownership place.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200710032297XA CN101453338B (en) | 2007-12-07 | 2007-12-07 | Charging proxy entity, charging method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200710032297XA CN101453338B (en) | 2007-12-07 | 2007-12-07 | Charging proxy entity, charging method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101453338A CN101453338A (en) | 2009-06-10 |
| CN101453338B true CN101453338B (en) | 2012-07-04 |
Family
ID=40735376
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200710032297XA Expired - Fee Related CN101453338B (en) | 2007-12-07 | 2007-12-07 | Charging proxy entity, charging method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101453338B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101938730A (en) * | 2009-07-02 | 2011-01-05 | 中兴通讯股份有限公司 | Method and system for triggering start of billing |
| CN111858291B (en) * | 2019-04-30 | 2022-04-22 | 华为技术有限公司 | Root cause determination method, equipment and system for data abnormity in charging system migration test |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1848898A (en) * | 2005-11-03 | 2006-10-18 | 华为技术有限公司 | Method for realizing prepayment |
| CN101022349A (en) * | 2007-02-09 | 2007-08-22 | 华为技术有限公司 | Charge mode providing method and charge method and charge control system |
-
2007
- 2007-12-07 CN CN200710032297XA patent/CN101453338B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1848898A (en) * | 2005-11-03 | 2006-10-18 | 华为技术有限公司 | Method for realizing prepayment |
| CN101022349A (en) * | 2007-02-09 | 2007-08-22 | 华为技术有限公司 | Charge mode providing method and charge method and charge control system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101453338A (en) | 2009-06-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101090351B (en) | Transport method for function entity in WiMAX network | |
| CN1695367B (en) | Method, system and telecommunication node for alternative prepaid support | |
| CN101047709B (en) | Method for implementing terminal denetwork at customer terminal mobile network protocol | |
| CN101232385B (en) | System and method for charging for microwave to switch in global intercommunication system | |
| WO2011003348A1 (en) | Method, device and communication system for group charging | |
| US20150373205A1 (en) | Method, apparatus and system for aggregating charging information | |
| CN101163020B (en) | Charging correlation method, device and system | |
| CN101923533A (en) | Method, device and system for processing prepaid service access | |
| CN101026664B (en) | Prepaid business charging method and system | |
| JP5930438B2 (en) | Access method, mobility management device, and user equipment | |
| CN101047710B (en) | Method for implementing terminal denetwork at agent mobile network protocol | |
| CN100426777C (en) | System and method for accessing 3GPP deductive network by non-3GPP technology | |
| CN101453338B (en) | Charging proxy entity, charging method and system | |
| CN102404798B (en) | Method, equipment and system for position information acquisition and service control | |
| CN101442417B (en) | Method, apparatus and system for implementing pre-payment in network | |
| CN101090332B (en) | Network-off method for terminal at normal mode | |
| CN101369901B (en) | Method, apparatus and system for associating policy and charging execution function entity | |
| CN105307141B (en) | The method, device and equipment of policy control and charging | |
| WO2019042218A1 (en) | Charging realisation system, charging realisation method and charging management functional entity | |
| CN101009744B (en) | A method for providing charging information in the wireless access network system | |
| CN101771989A (en) | Charging method, device and system | |
| CN101600155A (en) | Realize the methods, devices and systems of general service charging | |
| CN101227300B (en) | Post-paying charge rate switch method and access service network gateway | |
| CN101227702B (en) | Equipment, system and method for terminal to terminate business under vacant mode | |
| CN105472590B (en) | The method and system of charging is carried out in eHRPD network to data traffic |
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: 20120704 Termination date: 20171207 |