CN101583114A - Providing method of user equipment (UE) IP address and Diameter routing agent - Google Patents
Providing method of user equipment (UE) IP address and Diameter routing agent Download PDFInfo
- Publication number
- CN101583114A CN101583114A CNA2008101613572A CN200810161357A CN101583114A CN 101583114 A CN101583114 A CN 101583114A CN A2008101613572 A CNA2008101613572 A CN A2008101613572A CN 200810161357 A CN200810161357 A CN 200810161357A CN 101583114 A CN101583114 A CN 101583114A
- Authority
- CN
- China
- Prior art keywords
- address
- message
- session
- dra
- pcrf
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1403—Architecture for metering, charging or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
Abstract
The invention discloses a providing method of UE IP address and a Diameter routing agent. The method is applied to a communication system comprising a policy charging control (PCC) client and the Diameter routing agent (DRA) after UE and a packet data network establish IP connection access network (IP-CAN) session. The method comprises the following step that: the PCC client sends a predetermined message to the DRA and carries the IP address of the UE in the message. Thus, the providing method of UE IP address realizes dynamic policy charging control.
Description
Technical field
The present invention relates to the communications field, provide method, Diameter route agent in particular to a kind of user equipment network agreement (Internet Protocol abbreviates IP as) address.
Background technology
Third generation partner program (3rd Generation Partnership Project, abbreviate 3GPP as) grouping system (the Evolved Packet System of evolution, abbreviate EPS as) by Universal Terrestrial Radio Access Network (the Evolved Universal Terrestrial RadioAccess Network of evolution, abbreviate E-UTRAN as), mobile management unit (MobilityManagement Entity, abbreviate MME as), gateway (Serving Gateway, abbreviate S-GW as), data network gateway (Packet Data Network GateWay, abbreviate P-GW as), home subscriber server (Home Subscriber Server, abbreviate HSS as), 3GPP authentication and authorization charging (Authentication, Authorization andAccounting, abbreviate AAA as) server, "Policy and Charging Rules Function (Policy andCharging Rules Function abbreviates PCRF as) and other support nodes are formed.Wherein, S-GW is the accessing gateway equipment that links to each other with E-UTRAN, transmits data between E-UTRAN and P-GW, and is responsible for pending datas such as paging are carried out buffer memory; P-GW is the borde gateway of EPS and Packet Data Network's (Packet Data Network abbreviates PDN as), is responsible for the access of PDN, transmits data etc. between EPS and PDN; PCRF is by Rx interface and operator's IP operation network interface, obtain business information, PCRF also is connected with gateway device in the network by the Gx/Gxa/Gxc interface, be responsible for initiating the foundation of IP carrying, guarantee service quality (the Quality of Service of business datum, abbreviate QoS as), and the control of chargeing.
EPS supports the intercommunication with non-3GPP network, and realizes that by the S2a/b/c interface P-GW is as 3GPP network and the internetwork anchor point of non-3GPP.Non-3GPP network comprises the non-3GPP network of trusted and trustless non-3GPP network, and wherein, the IP of the non-3GPP network of trusted inserts can be directly by S2a and P-GW interface; The IP of trustless non-3GPP network inserts the data gateway (Evolved Packet DataGateway abbreviates ePDG as) that needs through evolution and links to each other with P-GW, and the interface between ePDG and P-GW is S2b.
In the 3GPP network between EPS, strategy and charge execution function (Policy andcharging enforcement function, abbreviate PCEF as) be present among the P-GW, PCRF by with the control that can finish all functions that is connected of P-GW, between PCRF and the P-GW by Gx interface exchange message.Interface between P-GW and S-GW is based on proxy-mobile IP (Proxy Mobile IP, abbreviate PMIP as) time, there is bearing binding and event reporting function (Bearer Binding and Event Report Function among the S-GW, abbreviate BBERF as), pass through Gxc interface exchange message between S-GW and the PCRF.When the non-3GPP network insertion of trusted, the also resident BBERF in the trusted non-3 GPP access network Central Shanxi Plain, between non-3GPP network access gateway of trusted and the PCRF by Gxa interface exchange message.As subscriber equipment (User Equipment, abbreviate UE as) when roaming, the S9 interface is as the interface of ownership place PCRF and visit ground PCRF, simultaneously, for UE provides professional application function (Application Function, abbreviate AF as) send the business information that is used for generation strategy charging control (Policy and Charging Control abbreviates PCC as) strategy to PCRF by Rx interface.
There are three kinds of roaming frameworks in EPS, first kind is called the local route, and Fig. 1 is the schematic diagram according to the roaming framework of the local route of the EPS of correlation technique, as shown in Figure 1, P-GW is at home network (also claiming belonging area network), and provides IP operation (being that AF is at home network) by home network operator.Second kind is called local break-out and home network operator provides IP operation, Fig. 2 is the schematic diagram that the roaming framework of IP operation is provided according to the local break-out of the EPS of correlation technique and home network operator, as shown in Figure 2, P-GW is at visited network, and provides IP operation (being that AF is at home network) by home network operator.The third local break-out and access zone network operator provide IP operation, Fig. 3 is the schematic diagram that the roaming framework of IP operation is provided according to the local break-out of the EPS of correlation technique and access zone network operator, as shown in Figure 3, P-GW is at visited network, and provides IP operation (being that AF is at visited network) by visited network operator.
To be described in detail Fig. 1, Fig. 2 and Fig. 3 below.In present correlation technique, the agreement that the PCC framework adopts is the Diameter application protocol of development on Diameter basic agreement (Diameter BaseProtocol) basis.At present, the PCC framework has defined the Diameter application protocol that uses under non-roaming scene, for example, is applied to the application protocol of Gx interface, is applied to the application protocol of Rx interface and the application protocol of Gxx (comprising Gxa and Gxc interface) interface etc.The PCC framework adopts these agreements to set up each PCC client and (for example, BBERF) and the Diameter session between the PCRF, and transmits with these Diameter sessions and to be used to formulate the information of PCC strategy and the strategy of formulation etc.
The scheme that realizes S9 roaming interface at present is: all IP of (1) vPCRF termination UE connect Access Network (IP Connectivity Access Network, abbreviating IP-CAN as) the relevant Gx session that is present in access zone network of session (referring to the connection of UE to Packet Data Network) is (promptly, the Diameter session of on the Gx interface, setting up), the Gxx session (promptly, the Diameter session of on Gxa or Gxc interface, setting up), between vPCRF and hPCRF, set up a S9 session (promptly, the Diameter session of on the S9 interface, setting up), transmit the Gx session with the S9 session, the information that the Gxx session transmits.(2) the vPCRF Rx session in the access zone network that do not terminate is just given hPCRF with the forwards of Rx session, and vPCRF is as an agency (Proxy).That is to say that when UE has a plurality of PDN to connect, a S9 session will need to transmit simultaneously a plurality of Gxx sessions relevant with a plurality of IP-CAN sessions of this UE, the information of Gx session.
A public land mobile telephone network (the Public Land MobileNetwork of while EPS, abbreviate PLMN as) in have a plurality of PCRF nodes, and all PCRF nodes belong to one or more Diameter (PCRF) territory, and all PCRF in same Diameter (PCRF) territory have identical ability.The PCC strategy of an IP-CAN session is only by a PCRF decision.All be associated with same PCRF in order to ensure relevant all PCEF of an IP-CAN session or BBERF and for this IP-CAN session provides professional AF, EPS has introduced a logic function module Diameter route agent (Diameter Routing Agent abbreviates DRA as) in each Diameter (PCRF) territory.When UE will be established to the IP-CAN session of a PDN, be that a PCRF is selected in this IP-CAN session by DRA, PCEF, BBERF and the AF relevant with this IP-CAN session are associated with on the selected PCRF by DRA.PCEF, BBERF and AF set up the Diameter session with the PCRF that chooses respectively, and by these Diameter sessions transmission strategies that session is controlled to IP-CAN and business information etc.Correctly PCEF, BBERF and AF are associated with a PCRF in order to ensure DRA, DRA will preserve can this IP-CAN session of unique identification relevant information and corresponding PCRF sign or IP address, and the information of sign IP-CAN session has the IP address of NAI, UE of UE and the APN that UE will insert PDN etc.PCEF, BBERF and AF set up with PCRF in foundation these information are provided in the Diameter conversation message, and DRA searches the information of preservation, just can find corresponding PCRF.
In the prior art, the DRA specific implementation can have three kinds of modes: (1) Redirect (being redirected) mode; When Diameter client (for example: PCEF, BBERF and AF) when PCRF sends the Diameter session and sets up request message, this message at first is sent to DRA.If when DRA did not also have the relevant information of this IP-CAN session or UE, DRA can be that this IP-CAN session or UE select a PCRF, and sign or the address of selected PCRF returned to transmit leg (that is Diameter client).If the relevant information of this IP-CAN session or UE has been arranged among the DAR, then DRA returns to Diameter client with sign or the address of the PCRF of correspondence.Diameter client obtains and sends the Diameter session to selected PCRF again after the address of PCRF or the sign and set up request message.After this Diameter session modification message does not need to send to DRA, only when the Diameter session termination, just need send the relevant information of Diameter session termination request message notice DRA deletion to DRA.(2) Proxy mode (claiming PA1 in the present invention).When Diameter client when PCRF sends the Diameter session and sets up request message, this message at first is sent to DRA.If when DRA did not also have the relevant information of this IP-CAN session, DRA can be that a PCRF is selected in this IP-CAN session, and gives selected PCRF with this forwards.If the relevant information of this IP-CAN session has been arranged among the DAR, then DRA gives corresponding PCRF with this forwards.The affirmation message of PCRF also is transmitted to Diameter client by DRA.(3) Proxy mode (being called PA2 among the present invention).Similar with the PA1 mode, difference is that DRA can also send to Diameter client to the sign of PCRF or address when the affirmation message that forwarding PCRF returns.Like this in interacting message subsequently, Diameter client can be directly and PCRF need alternately and not through DRA.Only when the Diameter session termination, just need send the relevant information of Diameter session termination request message notice DRA deletion to DRA.In sum, for Redirect and two kinds of realizations of PA2 of DRA, have only the Diameter session to set up request message and Diameter session termination request message just can be mutual with DRA, and Diameter session modification message is not mutual with DRA.
In the EPS system, the IP-CAN session of UE can have an IPv4 address and an IPv6 address simultaneously.Under normal conditions, because the IPv4 address space is limited, so be that request according to UE distributes in the address of IPv4.UE can be when setting up the IP-CAN session, and P-GW distributes the address of an IPv6 to UE.When UE needs the IPv4 address, distribute the address of an IPv4 again to the P-GW request.In the prior art, when the IP-CAN session was set up, P-GW can set up Indication message by the IP-CAN session, and the address of IPv6 is sent to DRA and PCRF.IP-CAN session modification Indication message will directly send to PCRF, not send to DRA, so the IPv4 address of UE back request can't be kept at DRA.When the AF of IPv4 provides business information to this IP-CAN session, send the service/application informational message to DRA, and the IPv4 address of carrying UE therein, DRA can't find PCRF according to the IPv4 address right so, thereby AF can't provide business information to be used for the PCRF decision-making to the IP-CAN session, and dynamic strategy is chargeed and controlled and can't realize.In addition, when UE discharged the IPv4 address, prior art also can't be notified the DRA deletion IPv4 address that UE discharges.
UE is under the roaming framework of local break-out, insert packet-based core networks (the Evolved Packet Core Network of evolution by non-3GPP connecting system of trusted or E-UTRAN, abbreviate EPC as), Fig. 4 is the flow chart of setting up according to the IP-CAN session of correlation technique, as shown in Figure 4, when adopting PMIPv6, the flow process of setting up the IP-CAN session is as follows:
Step S401, the S-GW of the resident BBERF of having function or trusted non-3 GPP access network close to receive sets up the IP-CAN conversation request message, and S-GW or trusted non-3 GPP access network close sign NAI, the PDN sign of having obtained UE and the access information that is used to generate strategy etc.;
Step S402, BBERF sends " gateway control session is set up indication " message to visit ground DRA, and carries sign NAI, the PDN sign of UE and the access information that is used to generate strategy etc. therein;
Step S403, vDRA judges do not have to select PCRF for this UE according to NAI; VDRA selects a visit ground PCRF for this UE, and preserves binding relationship (NAI, PDN sign, vPCRF address); VDRA returns to BBERF with selected vPCRF address by redirect message;
Step S404, BBERF obtain the vPCRF address, send " gateway control session is set up indication " message to this vPCRF, and carry sign NAI, the PDN sign of UE, the access information that is used to generate strategy etc. therein;
Step S405, vPCRF judges that according to PDN sign and roaming agreement UE has adopted local break-out; VPCRF this session that terminates, and decision is initiated to set up and hPCRF between new Diameter session; VPCRF sends the S9 session to ownership place DRA and sets up Indication message, and carry NAI therein, PDN sign, the access information that is used to generate strategy etc.;
Step S406, hDRA judges do not have to select PCRF for this UE according to NAI; HDRA selects an ownership place PCRF for this UE, and preserves binding relationship (NAI, PDN sign, hPCRF address); HDRA returns to vPCRF with the address by redirect message;
Step S407, vPCRF obtain the hPCRF address, preserve binding relationship (NAI, PDN sign, hPCRF address), and send the S9 session to hPCRF and set up Indication message, and carry NAI therein, PDN sign, the access information that is used to generate strategy etc.;
Step S408, hPCRF and user document library (the Subscription ProfileRepository that contracts, abbreviate SPR as) mutual, obtain the CAMEL-Subscription-Information of UE, and formulate PCC rule and event trigger, and set up acknowledge message by the S9 session and send to vPCRF according to network strategy and the access information that reports up etc.;
Step S409, vPCRF be from PCC rule extraction QoS rule, and revise QoS rule and event trigger according to local policy, sets up acknowledge message by gateway control session and send to BBERF, and BBERF installs QoS rule and event trigger;
Step S410, S-GW or trusted non-3 GPP access network close to the P-GW transmission and set up the IP-CAN conversation request message, and carry NAI and PDN sign therein; This sets up the IP-CAN conversation request message is the agent binding update request message when realizing; P-GW receives and sets up after the IP-CAN conversation request message, is designated UE distributing IP address according to NAI, PDN, and sets up the banding cache clauses and subclauses;
Wherein, above-mentioned step S410 can carry out simultaneously with step S404;
Step S411, the PCEF that resides in P-GW sends the IP-CAN session to vDRA and sets up Indication message, and carry NAI therein, PDN sign and IP address;
Step S412, vDRA judge for this UE has selected vPCRF according to NAI, and find binding relationship (NAI, PDN identify, vPCRF address) according to NAI and PDN sign, it is updated to (NAI, PDN sign, IP address, vPCRF address); VDRA returns redirect message to PCEF, and carries the vPCRF address that vDRA selects therein;
Step S413, PCEF obtain the vPCRF address, send " indication is set up in the IP-CAN session " message to this vPCRF, and carry sign NAI, PDN sign, the IP address of UE and the access information that is used to generate strategy etc. therein;
Step S414, vPCRF judge for this UE has set up the S9 session according to NAI, and find binding relationship (NAI, PDN identify, hPCRF address) according to NAI, PDN sign, and be updated to (NAI, PDN sign, IP address, hPCRF address).VPCRF sends S9 session modification Indication message to hPCRF, and carries NAI, PDN sign, the IP address of UE and the access information that is used to generate strategy etc. therein;
Step S415, hPCRF may be according to PCC rule and the event triggers before the new information change, and send to vPCRF by S9 session modification acknowledge message;
Step S416, vPCRF judges whether to upgrade according to the S9 session modification acknowledge message that receives, and is under the situation that is in judged result, and vPCRF upgrades PCC rule and event trigger; VPCRF returns the IP-CAN session to PCEF and sets up acknowledge message, and carries PCC rule and event trigger therein; PCEF installs PCC rule and event trigger;
If the QoS that vPCRF extracts from PCC rule rule is different with event trigger with the QoS rule that issues before with event trigger, then vPCRF also can be to QoS rule and the event trigger before BBERF sends information updating;
Step S417, PCEF return to BBERF and set up the IP-CAN session response message; In concrete implementation procedure, this sets up the IP-CAN session response message can be the agent binding update acknowledge message, and this is set up the IP-CAN session that the IP-CAN session response message sends in needn't waiting step S416 and sets up acknowledge message;
Step S418, BBERF return and set up the IP-CAN session response message.
In above-mentioned flow process, there are the following problems: have only to send the Diameter session and (for example set up request message and Diameter session termination request message, gateway control session is set up (termination) indication, (termination) indication is set up in the S9 session, message such as IP-CAN session foundation (termination) indication) Shi Caihui sends a request message to DRA.Because the S9 session will be used for transmitting all Gx of UE, the information of Gxx session.In step S414, vPCRF can not send to hDRA again and set up request message, but directly sends modify request messages to selected hPCRF.Therefore, will there be the IP address properties in the binding relationship of preserving among the hDRA.If provide business information to this IP-CAN session at ownership place AF, it will at first send a request message to hDRA, and might only carrying the IP address of UE, AF identifies, hDRA can't correctly find hPCRF so, thereby AF can't provide business information to be used for the hPCRF decision-making to the IP-CAN session, cause dynamic strategy to be chargeed and control and can't realize.
Similarly, when many PDN of UE insert, also the problems referred to above can appear; For example, UE adopts and has set up first IP-CAN session as the flow process of Fig. 4 when initially adhering to, and when the UE decision inserts a PDN again, adopts the roaming mode of local break-out to set up second IP-CAN session; The S9 session that the Gx session relevant with second IP-CAN session will be adopted to have set up comes transmission information, and the IP address of the UE of second IP-CAN session will can not be saved in hDRA equally, and the AF of ownership place equally also just can not find correct hPCRF.
From foregoing description as can be seen: after the IP-CAN session is set up, when AF when business information is provided, identify to send a request message if AF only carries the IP address of UE to DRA, then can cause DRA can't correctly find PCRF.
Summary of the invention
The IP address of only carrying UE at AF in the correlation technique identifies to send a request message to DRA and can cause DRA correctly to find the problem of PCRF and propose the present invention, for this reason, the present invention aims to provide a kind of user equipment (UE) IP address method, Diameter route agent is provided, to address the above problem.
According to an aspect of the present invention, provide a kind of user equipment (UE) IP address that method is provided.
User equipment (UE) IP address according to the present invention provides method, be applied to comprise the communication system of policy and charging control PCC client, the DRA of Diameter route agent, and being applied to subscriber equipment and Packet Data Network sets up IP and is connected after the Access Network IP-CAN session, said method comprises: the PCC client sends predetermined message to DRA, and carries user device IP address therein.
Preferably, the PCC client comprises one of following: "Policy and Charging Rules Function entity PCEF, "Policy and Charging Rules Function entity PCRF.
Preferably, it is one of following that predetermined message comprises: Diameter session modification request message, be used to transmit the specific messages of IP address and/or IP address function information, wherein, Diameter session modification request message comprises one of following: IP-CAN session modification Indication message, S9 session modification Indication message.
Preferably, Diameter session modification request message comprises the Diameter credit control request information, and wherein, the property value of the credit control request type in the Diameter credit control request information is to being set to " update request ".
Preferably, the PCC client is after DRA sends predetermined message, and said method also comprises: DRA receives predetermined message and therefrom obtains the IP address; DRA upgrades the binding relationship of user terminal or IP-CAN session and PCRF address according to the IP address, and returns the redirect message that carries the PCRF address or to PCRF forwarding predetermined message to the PCC client.
Preferably, also carry indication in the predetermined message binding relationship of user terminal or IP-CAN session and PCRF address is carried out the indication information that adds or delete the IP address function.
Preferably, the PCC client is after DRA sends predetermined message, and said method also comprises: DRA receives predetermined message and therefrom obtains the IP address; DRA according to the IP address and indication information adds the IP address to binding relationship or from binding relationship with IP address deletion, and return redirect message or transmit predetermined message to PCRF to the PCC client.
According to a further aspect in the invention, provide a kind of Diameter route agent.
Comprise according to Diameter of the present invention route agent: receiver module, be used to receive predetermined message from the PCC client, wherein, predetermined message carries the IP address information; Acquisition module is used for obtaining the IP address information from the predetermined message that receiver module receives.
Preferably, Diameter route agent also comprises: update module, and the IP address information that is used for obtaining according to acquisition module is upgraded the binding relationship of user terminal or IP-CAN session and PCRF address; Sending module is used for sending redirect message or transmitting predetermined message to PCRF to the PCC client.
By the present invention, adopt the PCC client to send the method for the predetermined message that carries the IP address to DRA, solved IP address that AF in the correlation technique only carries UE and identified to send a request message and to cause DRA can't correctly find the problem of PCRF, realized the dynamic strategy control of chargeing to DRA.
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, and illustrative examples of the present invention and explanation thereof are used to explain the present invention, do not constitute improper qualification of the present invention.In the accompanying drawings:
Fig. 1 is the schematic diagram according to the roaming framework of the local route of the EPS of correlation technique;
Fig. 2 is the schematic diagram that the roaming framework of IP operation is provided according to the local break-out of the EPS of correlation technique and home network operator;
Fig. 3 is the schematic diagram that the roaming framework of IP operation is provided according to the local break-out of the EPS of correlation technique and access zone network operator;
Fig. 4 is the flow chart of setting up according to the IP-CAN session of correlation technique;
Fig. 5 provides the flow chart of method for the IP address of the UE of the embodiment of the invention one;
Fig. 6 provides the flow chart of method for the IP address of the UE of the embodiment of the invention two;
Fig. 7 provides the flow chart of method for the IP address of the UE of the embodiment of the invention three;
Fig. 8 provides the flow chart of method for the IP address of the UE of the embodiment of the invention four;
Fig. 9 provides the flow chart of method for the IP address of the UE of the embodiment of the invention five;
Figure 10 is the structured flowchart of the Diameter route agent of the embodiment of the invention;
Figure 11 is the preferred structure block diagram of the Diameter route agent of the embodiment of the invention.
Embodiment
Functional overview
The embodiment of the invention provides the IP address of a kind of UE that method and system is provided, set up after IP is connected Access Network IP-CAN session in UE and Packet Data Network, the PCC client sends the method for the predetermined message that carries the IP address to DRA, DRA receives predetermined message and therefrom obtains the IP address, DRA upgrades the binding relationship of user terminal or IP-CAN session and PCRF address according to the IP address, and returns redirect message or to PCRF forwarding predetermined message to the PCC client.Describe the present invention below with reference to the accompanying drawings and in conjunction with the embodiments in detail.
Method embodiment
According to embodiments of the invention, provide the IP address of a kind of UE that method is provided, be applied to comprise the communication system of PCC client, DRA, and being applied to UE and Packet Data Network sets up after the IP-CAN session, this method comprises: the PCC client sends predetermined message to DRA, and carries the IP address of UE therein.
Wherein, the PCC client can comprise one of following: PCEF, PCRF; It is one of following that predetermined message can comprise: Diameter session modification request message, be used to transmit the specific messages of IP address and/or IP address function information, wherein, Diameter session modification request message comprises one of following: IP-CAN session modification Indication message, S9 session modification Indication message.
Preferably, Diameter session modification request message comprises the Diameter credit control request information, and wherein, the property value of the credit control request type in the Diameter credit control request information is to being set to " update request ".
In the PCC client after DRA sends predetermined message, DRA receives predetermined message and therefrom obtains the IP address, DRA upgrades the binding relationship of user terminal or IP-CAN session and PCRF address according to the IP address, and returns redirect message or to PCRF forwarding predetermined message to the PCC client.
And, in predetermined message, can also carry indication the binding relationship of UE or IP-CAN session and PCRF address is carried out the indication information that adds or delete the IP address function, in this case, after DRA sent predetermined message, DRA received predetermined message and therefrom obtains the IP address in the PCC client; DRA is according to the IP address and indication information adds to the IP address in the binding relationship or delete the IP address from binding relationship, and returns redirect message or transmit predetermined message to PCRF to the PCC client.
Pass through the embodiment of the invention, adopt the PCC client to send the method for the predetermined message that carries the IP address to DRA, solved IP address that AF in the correlation technique only carries UE and identified to send a request message and to cause DRA can't correctly find the problem of PCRF, realized the dynamic strategy control of chargeing to DRA.
Below in conjunction with example implementation procedure of the present invention is described in detail.
Embodiment one
Present embodiment is described be UE under non-roaming framework, insert EPC by non-3GPP connecting system of trusted or E-UTRAN, when adopting PMIPv6, set up the flow process of IP-CAN session.Fig. 5 as shown in Figure 5, comprises the steps: for the IP address of the UE of the embodiment of the invention one provides the flow chart of method
Step S501, the S-GW of the resident BBERF of having function or trusted non-3 GPP access network close to receive sets up the IP-CAN conversation request message, and S-GW or trusted non-3 GPP access network close sign NAI, PDN sign, the IPv6 Address requests of having obtained UE and the access information that is used to generate strategy etc.;
Step S502, BBERF, DRA, PCRF carry out gateway control session alternately and set up process, this process specifically comprises: BBERF sends " gateway control session is set up indication " message to DRA, and carries sign NAI, the PDN sign of UE, the access information that is used to generate strategy therein; DRA judges do not have to select PCRF for this UE according to NAI; DRA selects a PCRF for this UE, and preserves binding relationship (NAI, PDN sign, PCRF address); DRA returns to BBERF with selected vPCRF address by redirect message; BBERF obtains the PCRF address, sends " gateway control session is set up indication " message to this PCRF, and carries sign NAI, the PDN sign of UE, the access information that is used to generate strategy etc. therein; Receive at PCRF after " gateway control session is set up indication " message, with signatory document library (the Subscription ProfileRepository of user, abbreviate SPR as) mutual, obtain the CAMEL-Subscription-Information of UE, and formulate QoS rule and event trigger according to network strategy and the access information that reports up etc., and send to BBERF by " gateway control session is set up acknowledge message ", after this, BBERF installs QoS rule and event trigger;
Step S503, S-GW or trusted non-3 GPP access network close to the P-GW transmission sets up the IP-CAN conversation request message, and carrying NAI, PDN sign and IPv6 Address requests therein, this sets up the IP-CAN conversation request message can be the agent binding update request message when realizing; P-GW receive set up the IP-CAN conversation request message after, be UE distributing IP v6 address according to NAI, PDN sign and IPv6 Address requests, and set up the banding cache clauses and subclauses;
Wherein, step S503 can carry out simultaneously with step S502;
Step S504, the PCEF that resides in P-GW sends " indication is set up in the IP-CAN session " message to DRA, and carries NAI, PDN sign and IPv6 address therein;
Step S505, DRA judge for this UE has selected PCRF according to NAI, and find binding relationship (NAI, PDN identify, PCRF address) according to NAI and PDN sign, it is updated to (NAI, PDN sign, IPv6 address, PCRF address); DRA returns redirect message to PCEF, and carries the PCRF address that DRA selects therein;
Step S506, PCEF obtain the PCRF address, send " indication is set up in the IP-CAN session " message to this PCRF, and carry sign NAI, PDN sign, the IPv6 address of UE and the access information that is used to generate strategy etc. therein;
Step S507, PCRF formulates PCC rule and event trigger according to NAI, PDN sign and access information etc., and sets up acknowledge message by the IP-CAN session and send to PCEF; PCEF installs PCC rule and event trigger, is handed down to the QoS rule of BBERF before PCRF may need to upgrade;
Step S508, P-GW closes to return to S-GW or trusted non-3 GPP access network and sets up the IP-CAN session and reply, particularly, setting up the IP-CAN session replys and can be the agent binding update acknowledge message, need to prove that this is set up the IP-CAN session that the IP-CAN session response message needn't waiting step S507 and sets up acknowledge message;
Step S509, BBERF return and set up the IP-CAN session and reply;
Step S510, UE will use the business of IPv4 address, therefore needs the address of an IPv4; UE distributes an IPv4 address to the P-GW request;
Step S511, P-GW are UE distributing IP v4 address, and return acknowledge message to UE;
Step S512, PCEF sends " indication of IP-CAN session modification " message to DRA, and the IPv4 address of carrying UE therein; " indication of IP-CAN session modification " message can be Diameter credit control request (Credit Control Request when realizing, abbreviate CCR as) message, wherein, the CC-Request-Type property value is set to " UPDATE_REQUEST " to (Attribute Value Pair abbreviates AVP as); Carry the IPv4 address in this message, in fact Yin Han indication DRA adds this IPv4 address in binding relationship, certainly carries the clearly indication of adding this IPv4 address;
Step S513, DRA upgrades binding relationship (NAI, PDN sign, IPv4 address, IPv6 address, PCRF address), and returns redirect message to PCEF;
Step S514, PCEF sends " indication of IP-CAN session modification " message to PCRF, and the IPv4 address of carrying UE therein;
Wherein, step S512 and 514 can carry out simultaneously;
Step S515, PCRF formulates the PCC rule according to the IPv4 address, and returns IP-CAN session modification acknowledge message to PCEF;
Step S516, PCRF formulate corresponding QoS rule, and upgrade the QoS rule of BBERF.
From this embodiment as can be seen: when the AF of IPv4 will be when this IP-CAN session provides business information, AF will send application/business information message to DRA, and the IPv4 address of carrying UE therein, DRA finds binding relationship according to the IP address, thereby is returned as the PCRF that this IP-CAN session is selected to AF.Need to prove that PCEF also can adopt the IPv4 address of the particular message notice DRA UE of customization.
In other implementation processes, UE asks the address of distributing IP v4 and IPv6 in step S501, but the address (for example, the address of IPv6 is directly distributed by P-GW, and IPv4 is distributed by external network) of when Indication message is set up in the IP-CAN session of P-GW forwarding step S504, only having distributed IPv6 for UE.Externally network is that UE has distributed after the IPv4 address, and PCEF need send to DRA with the address of IPv4 by step S512.
UE when inserting EPC when adopting GTP to insert EPC by E-UTRAN or by trustless non-3 GPP access network, does not need the mutual of relevant BBERF in the flow process of enforcement under non-roaming framework, other flow processs are similar.When UE inserts EPS by the DISMIPv6 agreement, also can adopt similar method with this embodiment.
UE also can adopt the similar method with this embodiment when roaming; Particularly, under the route roaming scence of local, by " indication of IP-CAN session modification " message the newly assigned IP of UE address is sent to ownership place DRA by PCEF; Under the local break-out roaming scence, by " indication of IP-CAN session modification " message the newly assigned IP of UE address is sent to visit ground DRA by PCEF, PCRF sends to ownership place DRA by " indication of S9 session modification " message with the newly assigned IP of UE address by visit ground.
In the above-described embodiments, it can be Per (whenever) IP-CAN (that is, a PCRF is selected in the IP-CAN session of UE, and the different IP of UE-CAN session can be selected different PCRF) that DRA selects PCRF, (that is, same PCRF is selected in all IP-CAN sessions of UE) that also can Per UE.Therefore, the binding relationship of preserving at DRA is Per IP-CAN or Per UE.
Embodiment two
Present embodiment is described be UE under non-roaming framework, insert EPC by non-3GPP connecting system of trusted or E-UTRAN, adopt PMIPv6, setting up after the IP-CAN session flow process of embodiment one, P-GW initiates to discharge the flow process of IPv4 address.Fig. 6 as shown in Figure 6, comprises the steps: for the IP address of the UE of the embodiment of the invention two provides the flow chart of method
Step S601, when UE discharged IPv4 address or IPv4 address aging, P-GW initiated IPv4 address deletion flow process; PCEF sends " indication of IP-CAN session modification " message to DRA, and carries the information of indication deletion IPv4 address therein, and this information can be clear and definite, also can imply; " indication of IP-CAN session modification " message can be Diameter CCR message in implementation process, wherein, CC-Request-Type AVP is set to " UPDATE_REQUEST ";
Step S602, DRA upgrades binding relationship (NAI, PDN sign, IPv6 address, PCRF address), and returns redirect message to PCEF;
Step S603, PCEF sends " indication of IP-CAN session modification " message to PCRF, should carry the information that the IPv4 address is deleted in indication in " indication of IP-CAN session modification " message;
Wherein, step S601 and step S603 can carry out simultaneously;
Step S604, PCRF is according to indication deletion IPv4 address, and renewal PCC rule, returns IP-CAN session modification acknowledge message to PCEF;
Step S605, PCRF upgrade corresponding QoS rule, and upgrade the QoS rule of BBERF;
Step S606, P-GW closes transmission " request message is recalled in binding " to S-GW or trusted non-3 GPP access network, and this binding is recalled request message and is used for indication deletion IPv4 address;
Step S607, S-GW or trusted non-3 GPP access network close and return acknowledge message.
In other implementation processes, PCEF also can adopt the IPv4 address of the particular message notice DRA deletion UE of customization.
UE when inserting EPC when adopting GTP to insert EPC by E-UTRAN or by trustless non-3 GPP access network, does not need the mutual of relevant BBERF in the flow process of enforcement under non-roaming framework, other flow processs are similar.When UE inserts EPS by the DISMIPv6 agreement, also can adopt similar method with this embodiment.
UE also can adopt the similar method with this embodiment when roaming; Particularly, under the route roaming scence of local, the indication that will delete the IP address by " indication of IP-CAN session modification " message by PCEF sends to ownership place DRA; Under the local break-out roaming scence, the indication that to delete the IP address by " indication of IP-CAN session modification " message by PCEF sends to visit ground DRA, and the indication that will delete the IP address by " indication of S9 session modification " message by visit ground PCRF sends to ownership place DRA.
In the above-described embodiments, DRA select PCRF be Per (whenever) IP-CAN's or Per UE.The binding relationship that DRA preserves is Per IP-CAN or Per UE.
Embodiment three
Present embodiment is described be UE under the roaming framework of local break-out, insert EPC by non-3GPP connecting system of trusted or E-UTRAN, when adopting PMIPv6, set up the flow process of IP-CAN session.Fig. 7 provides the flow chart of method for the IP address of the UE of the embodiment of the invention three; As shown in Figure 7, comprise the steps:
Step S701-step S713 is identical with the step S401-step S413 of Fig. 4, does not repeat them here;
Step S714 after vPCRF receives request message, sends " S9 session modification indication request " message to hDRA, and carries the IP address of NAI, PDN sign and UE therein; S9 session modification indication request message can be DiameterCCR message in implementation process, wherein, CC-Request-Type AVP is set to " UPDATE_REQUEST "; Need to prove that vPCRF also can adopt the IP address of the particular message notice hDRA UE of customization; Wherein, the above-mentioned IP address is IPv4 and/or IPv6 address, carries the IP address in this message, in fact impliedly indicates DRA to add this IP address in binding relationship, certainly adopts and carries the clearly indication of adding this address;
Step S715, hDRA judge for this UE has selected PCRF according to NAI, and find binding relationship (NAI, PDN identify, hPCRF address) and binding relationship is updated to (NAI, PDN sign, IP address, hPCRF address) according to NAI and PDN sign; HDRA returns redirect message to vPCRF, and carries the address of hPCRF therein;
Step S716-step S720 is identical with step S414-step S418 among Fig. 4, does not repeat them here.
Need to prove that step S714 and step S716 can carry out simultaneously, step S714 also can adopt the IP address of other message informings hDRA UE.
Radix Angelicae Sinensis possession AF will be when this IP-CAN session provides business information, hAF will send application/business information message to hDRA, and the IP address of carrying UE therein, hDRA finds binding relationship according to the IP address, thereby is returned as the hPCRF that this IP-CAN session is selected to hAF.HAF sends application/business information message to hPCRF again, sets up the AF session, provides business information by this session.
UE is similar by flow process and this embodiment that trusted non-3 GPP access network employing DSMIPv6 agreement access EPC sets up the IP-CAN session, be with the difference of this embodiment: do not carry the PDN sign among step S701, step S702, step S704, the step S707, close the Care-of Address CoA that distributes for UE but carry the trusted non-3 GPP access network; In the binding relationship of preserving, do not have the PDN sign and CoA is arranged; When searching binding relationship, can search according to NAI and CoA.In step S705, vPCRF is not according to there being the PDN sign, and the S9 session is set up in decision.Step S710 sends to P-GW by UE, and carries the IP address of PDN sign and UE in the message that sends, and after this all will carry PDN sign and IP address in the interactive messages.
In the above-described embodiments, it is Per UE that DRA selects PCRF, and the binding relationship that DRA preserves is Per UE.
Embodiment four
Present embodiment is described UE by after setting up first IP-CAN session as the flow process of embodiment one, and decision inserts a PDN again, sets up the flow process of second IP-CAN session.Still on visit ground, this P-GW might be same P-GW with the P-GW of first IP-CAN session to the P-GW of second IP-CAN session, also may be different P-GW.Fig. 8 as shown in Figure 8, comprises the steps: for the IP address of the UE of the embodiment of the invention four provides the flow chart of method
Step S801, the S-GW of the resident BBERF of having function or trusted non-3 GPP access network close to receive sets up the IP-CAN conversation request message, and S-GW or trusted non-3 GPP access network close sign NAI, the PDN sign of having obtained UE ' and access information of being used to generate strategy etc.;
Step S802, BBERF sends " gateway control session is set up indication " message to visit ground DRA, and carry therein sign NAI, the PDN sign of UE ', the access information that is used to generate strategy;
Step S803, vDRA judge for this UE selects PCRF according to NAI, i.e. the vPCRF that selects among the embodiment one increases a binding relationship (NAI, PDN identify ', vPCRF address); VDRA returns to BBERF with selected vPCRF address by redirect message; This vPCRF is the vPCRF that first IP-CAN session is selected;
Step S804, BBERF obtain the vPCRF address, send " gateway control session is set up indication " message to this vPCRF, and carry therein sign NAI, the PDN sign of UE ', the access information that is used to generate strategy etc.;
Step S805, vPCRF according to PDN sign ' and roaming agreement judge that UE has adopted local break-out; VPCRF judges for this UE has set up a S9 session according to NAI, preserves binding relationship (NAI, PDN identify ', hPCRF); VPCRF this session that terminates, the S9 session of setting up before adopting sends S9 session modification Indication message to hPCRF, and the NAI that carries therein, PDN sign ', the access information that is used to generate strategy;
Step S806, hPCRF and SPR are mutual, obtain the CAMEL-Subscription-Information of UE, and formulate PCC rule and event trigger according to network strategy and the access information that reports up etc., and send to vPCRF by S9 session modification acknowledge message;
Step S807, vPCRF be from PCC rule extraction QoS rule, and revise QoS rule and event trigger according to local policy, sets up acknowledge message by gateway control session and send to BBERF; BBERF installs QoS rule and event trigger;
Step S808, S-GW or trusted non-3 GPP access network close to send to P-GW and set up the IP-CAN conversation request message, and carry therein NAI and PDN sign '; This is set up the IP-CAN conversation request message and be the agent binding update request message in implementation process; After P-GW receives message, according to NAI, PDN identify ' be UE distributing IP address ', and set up the banding cache clauses and subclauses;
Wherein, step S808 can carry out simultaneously with step S802;
Step S809, the PCEF that resides in P-GW sends the IP-CAN session to vDRA and sets up Indication message, carries NAI in the message, the PDN sign ' and the IP address ';
Step S810, vDRA judge for this UE has selected PCRF according to NAI, find binding relationship (NAI, the PDN sign ', the vPCRF address), and be updated to (NAI, PDN identify ', the IP address ', the vPCRF address).VDRA returns redirect message to PCEF, carries the vPCRF address that vDRA selects in the message.This vPCRF is the vPCRF that first IP-CAN session is selected;
Step S811, PCEF obtain the vPCRF address, send " indication is set up in the IP-CAN session " message to this vPCRF, carry in the message sign NAI, the PDN sign of UE ', IP address ' and the access information that is used to generate strategy etc.;
Step S812 after vPCRF receives request message, sends S9 session modification indication request message to hDRA, carry NAI, PDN in the message to identify ' and the IP address '; S9 session modification indication request message can be Diameter CCR message in implementation process, wherein CC-Request-Type AVP is set to " UPDATE_REQUEST "; VPCRF also can adopt the customization particular message be used to notify the IP address of hDRA UE '; Wherein, above-mentioned IP address ' be IPv4 and/or IPv6 address, in this message, carry the IP address ', in fact impliedly indicate DRA in binding relationship, add this IP address ', certainly adopt and carry the clearly indication of adding this address;
Step S813, hDRA judge for this UE has selected PCRF according to NAI, and according to NAI and PDN identify ' find binding relationship (NAI, PDN sign ', hPCRF address) and be updated to (NAI, PDN identify ', the IP address ', the hPCRF address); HDRA returns redirect message to vPCRF, and carries the address of hPCRF therein; This hPCRF is the hPCRF that first IP-CAN session is selected;
Step S814, vPCRF judge for this UE has set up the S9 session according to NAI, and identify ' find binding relationship (NAI, PDN sign ', hPCRF address) according to NAI and PDN, be updated to (NAI, PDN identify ', the IP address ', the hPCRF address).VPCRF sends S9 session modification Indication message to hPCRF, and carries NAI therein, the PDN sign ', IP address ' and the access information that is used to generate strategy etc.;
Wherein, step S814 can be parallel with step S812, sends after also can waiting the message that receives step S813 again;
Step S815, hPCRF may be according to PCC rule and the event triggers before the new information change, and send to vPCRF by S9 session modification acknowledge message;
Step S816, if upgrade, then vPCRF upgrades PCC rule and event trigger; VPCRF returns the IP-CAN session to PCEF and sets up acknowledge message, and carries PCC rule and event trigger therein; PCEF installs PCC rule and event trigger;
Wherein, if QoS rule that vPCRF extracts from the PCC rule and event trigger and the generation that issues before variation, vPCRF also can send information updating QoS rule and event trigger before to BBERF;
Step S817, PCEF return to BBERF and set up the IP-CAN session and reply; In implementation process, set up the IP-CAN session and reply and to be the agent binding update acknowledge message; This message needn't waiting step S816 affirmation message;
Step S818, BBERF return and set up the IP-CAN session and reply.
Need to prove, Radix Angelicae Sinensis possession AF will be when second IP-CAN session provides business information, hAF will send application/business information message to hDRA, carry in this message the IP address of UE ', hDRA is according to IP address ' find binding relationship, thereby is returned as the hPCRF that this IP-CAN session is selected to hAF, and hAF sends application/business information message to hPCRF again, set up the AF session, provide business information by this session.
In the above-described embodiments, it is Per UE that DRA selects PCRF, and the binding relationship that DRA preserves is Per UE.
Embodiment five
After present embodiment was described UE and adopted the DSMIPv6 agreement to insert EPC to set up first IP-CAN session, decision inserted a PDN again, sets up the flow process of second IP-CAN session.Still on visit ground, this P-GW might be same with the P-GW of first IP-CAN session to the P-GW of second IP-CAN session, also may be different.Fig. 9 as shown in Figure 9, comprises the steps: for the IP address of the UE of the embodiment of the invention five provides the flow chart of method
Step S901, UE decision inserts a PDN again, sets up Security Association with selected P-GW, in this process, P-GW will for UE divide the new IP address that is used in the IP-CAN session that will set up '; UE sends to P-GW and sets up the IP-CAN conversation request message subsequently, and carry therein NAI, CoA, IP address ' and PDN sign '; This message can be the Binding Update request message in implementation process; P-GW receives after this message, according to NAI, PDN sign ', CoA and IP address ' for setting up the banding cache clauses and subclauses;
Step S902, the PCEF that resides in P-GW sends the IP-CAN session to vDRA and sets up Indication message, and carries NAI therein, CoA, PDN sign ' and the IP address ';
Step S903, vDRA judge for this UE has selected PCRF according to NAI, again according to the binding relationship in PDN sign ' and IP address ' set up (NAI, CoA, PDN identify ', the IP address ', the vPCRF address); VDRA returns redirect message to PCEF, and carries the vPCRF address that vDRA selects therein; This vPCRF is the vPCRF that first IP-CAN session is selected;
Step S904, PCEF obtain the vPCRF address, send " indication is set up in the IP-CAN session " message to this vPCRF, and carry therein sign NAI, CoA, the PDN sign of UE ', IP address ' and the access information that is used to generate strategy etc.;
Step S905, vPCRF receive after the request message, send S9 session modification indication request message to hDRA, and carry therein NAI, CoA, PDN sign ' and IP address '; S9 session modification indication request message can be DiameterCCR message in implementation process, wherein CC-Request-Type AVP is set to " UPDATE_REQUEST "; Wherein, vPCRF also can adopt the IP address of the particular message notice hDRA UE of customization '; Wherein, above-mentioned IP address ' be IPv4 and/or IPv6 address, in this message, carry the IP address ', in fact Yin Han indication DRA in binding relationship, add this IP address ', certainly adopt and carry the clearly indication of adding this address;
Step S906, hDRA judge for this UE has selected PCRF according to NAI, and according to the IP address ' and PDN identify ' set up a binding relationship for (NAI, CoA, PDN identify ', the IP address ', the hPCRF address); HDRA returns redirect message to vPCRF, and carries the address of hPCRF therein; This hPCRF is the selected hPCRF of first IP-CAN session;
Step S907, vPCRF judges according to NAI and has set up the S9 session for this UE, and according to PDN sign ' and IP address ' set up binding relationship for (NAI, CoA, PDN sign ', the IP address ', the hPCRF address), vPCRF sends S9 session modification Indication message to hPCRF, and wherein carry NAI, CoA, PDN sign ', IP address ' and the access information that is used to generate strategy etc.;
Wherein, step S907 can be parallel with step S905, sends after also can waiting the message that received for 906 steps again;
Step S908, hPCRF may be according to PCC rule and the event triggers before the new information change, and send to vPCRF by S9 session modification acknowledge message;
Step S909, if upgrade, then vPCRF upgrades PCC rule and event trigger; VPCRF returns the IP-CAN session to PCEF and sets up acknowledge message, and carries PCC rule and event trigger therein; PCEF installs PCC rule and event trigger;
Step S910, if QoS rule that vPCRF extracts from the PCC rule and event trigger with the generation that issues before variation, then vPCR sends gateway control and QoS rule renewal QoS rule and the event trigger before that give information to BBERF;
Step S911, BBERF upgrades QoS rule and event trigger, returns acknowledge message;
Step S912, PCEF return to UE and set up the IP-CAN session and reply, and in implementation process, set up the IP-CAN session and reply and can be the Binding Update acknowledge message, and this message is triggered by step S909.
Radix Angelicae Sinensis possession AF will be when second IP-CAN session provides business information, hAF will send application/business information message to hDRA, carry in this message the IP address of UE ', hDRA is according to IP address ' find binding relationship, thereby is returned as the hPCRF that this IP-CAN session is selected to hAF; HAF sends application/business information message to hPCRF again, sets up the AF session, provides business information by this session.
In the above-described embodiments, it is Per UE that DRA selects PCRF, and the binding relationship that DRA preserves is Per UE.
After UE adopts embodiment four or embodiment five to set up two IP-CAN sessions, if the UE decision disconnects one of them, vPCRF also will send Diameter session modification request message or particular message is notified hDRA certain IP-CAN session termination to hDRA so, wherein, carry the IP address and the termination indication of the IP-CAN session that will terminate in the above-mentioned message.
System embodiment
According to embodiments of the invention, provide a kind of Diameter route agent.Figure 10 is the structured flowchart of the Diameter route agent of the embodiment of the invention, and as shown in figure 10, this Diameter route agent comprises: receiver module 102 and acquisition module 104 will be described in detail said structure below.
Figure 11 is the preferred structure block diagram of the Diameter route agent of the embodiment of the invention, and as shown in figure 11, Diameter route agent also comprises:
Update module 112 is connected to acquisition module 104, and the IP address information that is used for obtaining according to acquisition module 104 is upgraded the binding relationship that is used to indicate IP address and PCRF address.
Sending module 114 is connected to update module 112, is used for update module after finishing associative operation, sends redirect message to the PCC client.
The DRA of PA2 implementation and above all embodiment are similar, after difference only is that DRA receives Diameter session modification request message, transmit message to PCRF, and after this, the affirmation message of PCRF also is transmitted to the PCC client through DRA.
Pass through the above embodiment of the present invention, adopt the PCC client to send the method for the predetermined message that carries the IP address to DRA, DRA can obtain the IP address of UE, and the AF of ownership place can correctly find ownership place PCRF, solved IP address that AF in the correlation technique only carries UE and identified to send a request message and to cause DRA can't correctly find the problem of PCRF, realized the dynamic strategy control of chargeing to DRA.
Obviously, those skilled in the art should be understood that, above-mentioned each module of the present invention or each step can realize with the general calculation device, they can concentrate on the single calculation element, perhaps be distributed on the network that a plurality of calculation element forms, alternatively, they can be realized with the executable program code of calculation element, thereby, they can be stored in the storage device and carry out by calculation element, perhaps they are made into each integrated circuit modules respectively, perhaps a plurality of modules in them or step are made into the single integrated circuit module and realize.Like this, the present invention is not restricted to any specific hardware and software combination.
The above is the preferred embodiments of the present invention only, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (9)
1. a user equipment (UE) IP address provides method, be applied to comprise the communication system of policy and charging control PCC client, the DRA of Diameter route agent, and be applied to subscriber equipment and Packet Data Network and set up IP and be connected after the Access Network IP-CAN session, it is characterized in that described method comprises:
Described PCC client sends predetermined message to described DRA, and carries user device IP address therein.
2. method according to claim 1 is characterized in that, it is one of following that described PCC client comprises: "Policy and Charging Rules Function entity PCEF, "Policy and Charging Rules Function entity PCRF.
3. method according to claim 1, it is characterized in that, it is one of following that described predetermined message comprises: Diameter session modification request message, be used to transmit the specific messages of described IP address and/or IP address function information, wherein, described Diameter session modification request message comprises one of following: IP-CAN session modification Indication message, S9 session modification Indication message.
4. method according to claim 3, it is characterized in that, described Diameter session modification request message comprises the Diameter credit control request information, and wherein, the property value of the credit control request type in the described Diameter credit control request information is to being set to " update request ".
5. method according to claim 1 is characterized in that, described PCC client is after described DRA sends predetermined message, and described method also comprises:
Described DRA receives described predetermined message and therefrom obtains described IP address;
Described DRA upgrades the binding relationship of described user terminal or IP-CAN session and PCRF address according to described IP address, and returns redirect message or transmit described predetermined message to PCRF to described PCC client.
6. method according to claim 1 is characterized in that, also carries indication in the described predetermined message binding relationship of user terminal or IP-CAN session and PCRF address is carried out the indication information that adds or delete described IP address function.
7. method according to claim 6 is characterized in that, described PCC client is after described DRA sends predetermined message, and described method also comprises:
Described DRA receives described predetermined message and therefrom obtains described IP address;
Described DRA according to described IP address and described indication information adds described IP address to described binding relationship or from described binding relationship with described IP address deletion, and return redirect message or transmit described predetermined message to PCRF to described PCC client.
8. a Diameter route agent is characterized in that, comprising:
Receiver module is used to receive the predetermined message from the PCC client, and wherein, described predetermined message carries the IP address information;
Acquisition module is used for obtaining described IP address information from the described predetermined message that described receiver module receives.
9. Diameter according to claim 8 route agent is characterized in that, also comprises:
Update module, the described IP address information that is used for obtaining according to described acquisition module is upgraded the binding relationship of user terminal or IP-CAN session and PCRF address;
Sending module is used for sending redirect message or transmitting described predetermined message to PCRF to described PCC client.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101613572A CN101583114B (en) | 2008-09-23 | 2008-09-23 | Providing method of user equipment (UE) IP address and Diameter routing agent |
| PCT/CN2009/071555 WO2010034195A1 (en) | 2008-09-23 | 2009-04-29 | Method for providing ip address of user equipment, diameter routing agent |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101613572A CN101583114B (en) | 2008-09-23 | 2008-09-23 | Providing method of user equipment (UE) IP address and Diameter routing agent |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101583114A true CN101583114A (en) | 2009-11-18 |
| CN101583114B CN101583114B (en) | 2011-09-21 |
Family
ID=41365015
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008101613572A Active CN101583114B (en) | 2008-09-23 | 2008-09-23 | Providing method of user equipment (UE) IP address and Diameter routing agent |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN101583114B (en) |
| WO (1) | WO2010034195A1 (en) |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102143062A (en) * | 2010-12-28 | 2011-08-03 | 华为技术有限公司 | Policy and charging rule function addressing method, device and system |
| CN102238507A (en) * | 2010-04-26 | 2011-11-09 | 中兴通讯股份有限公司 | Method and system for determining policy and charging rules function |
| CN102611586A (en) * | 2011-01-18 | 2012-07-25 | 中兴通讯股份有限公司 | Method and system for realizing application detection and control of dual-stack supporting IP-CAN (Internet protocol-controller area network) session |
| CN102638867A (en) * | 2011-02-14 | 2012-08-15 | 中兴通讯股份有限公司 | Method and system for processing secondary admission control |
| CN102694841A (en) * | 2011-03-21 | 2012-09-26 | 中兴通讯股份有限公司 | Method and system for deleting binding information in Diameter routing agent |
| CN102763365A (en) * | 2010-02-18 | 2012-10-31 | 阿尔卡特朗讯公司 | Method for PCRF to autonomously respond to cell capacity shortage |
| CN102811130A (en) * | 2011-06-03 | 2012-12-05 | 华为软件技术有限公司 | Redirect method and redirect device under PCC (Policy and Charging Control) |
| CN103139762A (en) * | 2011-11-22 | 2013-06-05 | 中兴通讯股份有限公司 | Method and system for selecting policy and charging rule function |
| CN104486841A (en) * | 2014-11-20 | 2015-04-01 | 大唐移动通信设备有限公司 | Strategy control rule function server and message forwarding method thereof |
| CN103731812B (en) * | 2012-10-15 | 2017-09-15 | 中国移动通信集团公司 | Session association method, device, gateway, business side access device and server |
| WO2018085994A1 (en) * | 2016-11-08 | 2018-05-17 | 华为技术有限公司 | Integrated controller selection method, device and system |
| CN112887151A (en) * | 2015-02-03 | 2021-06-01 | 思科技术公司 | System and method for discovering policy charging and rule functions in a network environment |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8548463B2 (en) | 2011-10-18 | 2013-10-01 | Alcatel Lucent | PCRN roaming agreement |
| US8843128B2 (en) | 2011-10-18 | 2014-09-23 | Alcatel Lucent | Roaming session termination triggered by roaming agreement/partner deletion |
| CN107306391B (en) * | 2016-04-18 | 2020-03-03 | 中国移动通信有限公司研究院 | Network address allocation method and device and gateway equipment |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101227352B (en) * | 2007-01-15 | 2011-02-09 | 华为技术有限公司 | System and method for accessing network of subscriber terminal emergently to login IP connection |
| CN101150782B (en) * | 2007-10-17 | 2012-04-18 | 中兴通讯股份有限公司 | A selection method for policy billing control server |
| CN101150418B (en) * | 2007-10-17 | 2011-01-05 | 中兴通讯股份有限公司 | A selection method for policy billing control server |
| CN101217810B (en) * | 2008-01-16 | 2011-11-30 | 中兴通讯股份有限公司 | A selecting method of strategy and charging rule functions |
| CN101198171B (en) * | 2007-12-27 | 2011-09-21 | 中兴通讯股份有限公司 | Routing method for strategy charging control information in roaming scene |
| CN101217383A (en) * | 2008-01-04 | 2008-07-09 | 中兴通讯股份有限公司 | A deletion method of functional association relation of strategy and charging rules |
| CN101227391B (en) * | 2008-01-09 | 2012-01-11 | 中兴通讯股份有限公司 | method for selecting function entity of tactics and charging rules under non-roaming condition |
| CN100579302C (en) * | 2008-01-10 | 2010-01-06 | 中兴通讯股份有限公司 | Selecting method of strategies under non-roaming scenery and the functional server of charging rules |
-
2008
- 2008-09-23 CN CN2008101613572A patent/CN101583114B/en active Active
-
2009
- 2009-04-29 WO PCT/CN2009/071555 patent/WO2010034195A1/en active Application Filing
Cited By (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102763365B (en) * | 2010-02-18 | 2015-08-12 | 阿尔卡特朗讯公司 | For the method for PCRF from dynamic response cell capacity deficiency |
| CN102763365A (en) * | 2010-02-18 | 2012-10-31 | 阿尔卡特朗讯公司 | Method for PCRF to autonomously respond to cell capacity shortage |
| CN102238507A (en) * | 2010-04-26 | 2011-11-09 | 中兴通讯股份有限公司 | Method and system for determining policy and charging rules function |
| CN102238507B (en) * | 2010-04-26 | 2015-08-12 | 中兴通讯股份有限公司 | Determine the method and system of "Policy and Charging Rules Function |
| CN102143062A (en) * | 2010-12-28 | 2011-08-03 | 华为技术有限公司 | Policy and charging rule function addressing method, device and system |
| CN102611586A (en) * | 2011-01-18 | 2012-07-25 | 中兴通讯股份有限公司 | Method and system for realizing application detection and control of dual-stack supporting IP-CAN (Internet protocol-controller area network) session |
| CN102611586B (en) * | 2011-01-18 | 2017-06-13 | 中兴通讯股份有限公司 | Support that the method and system of application detection and control are realized in the IP CAN sessions of double stacks |
| US9565052B2 (en) | 2011-01-18 | 2017-02-07 | Zte Corporation | Method and system for realizing application detection and control in IP-CAN session supporting dual stack |
| CN102638867A (en) * | 2011-02-14 | 2012-08-15 | 中兴通讯股份有限公司 | Method and system for processing secondary admission control |
| CN102638867B (en) * | 2011-02-14 | 2018-01-02 | 中兴通讯股份有限公司 | The processing method and system of secondary call access control |
| WO2012126311A1 (en) * | 2011-03-21 | 2012-09-27 | 中兴通讯股份有限公司 | Method and system for creating and deleting binding information in diameter routing agent, h-pcrf |
| CN102694841A (en) * | 2011-03-21 | 2012-09-26 | 中兴通讯股份有限公司 | Method and system for deleting binding information in Diameter routing agent |
| US9344864B2 (en) | 2011-06-03 | 2016-05-17 | Huawei Technologies Co., Ltd. | Redirection method and redirection apparatus under policy and charging control |
| WO2012163284A1 (en) * | 2011-06-03 | 2012-12-06 | 华为技术有限公司 | Redirection method and redirection apparatus under policy and charging control |
| CN102811130A (en) * | 2011-06-03 | 2012-12-05 | 华为软件技术有限公司 | Redirect method and redirect device under PCC (Policy and Charging Control) |
| CN103139762A (en) * | 2011-11-22 | 2013-06-05 | 中兴通讯股份有限公司 | Method and system for selecting policy and charging rule function |
| CN103731812B (en) * | 2012-10-15 | 2017-09-15 | 中国移动通信集团公司 | Session association method, device, gateway, business side access device and server |
| CN104486841A (en) * | 2014-11-20 | 2015-04-01 | 大唐移动通信设备有限公司 | Strategy control rule function server and message forwarding method thereof |
| CN104486841B (en) * | 2014-11-20 | 2019-08-16 | 大唐移动通信设备有限公司 | A kind of policy control rules function server and its message forwarding method |
| CN112887151A (en) * | 2015-02-03 | 2021-06-01 | 思科技术公司 | System and method for discovering policy charging and rule functions in a network environment |
| CN112887151B (en) * | 2015-02-03 | 2023-12-26 | 思科技术公司 | System and method for discovering policy charging and rules functions in a network environment |
| WO2018085994A1 (en) * | 2016-11-08 | 2018-05-17 | 华为技术有限公司 | Integrated controller selection method, device and system |
| US11039501B2 (en) | 2016-11-08 | 2021-06-15 | Huawei Technologies Co., Ltd. | Converged controller selection method, device, and converged controller selection system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101583114B (en) | 2011-09-21 |
| WO2010034195A1 (en) | 2010-04-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101583114B (en) | Providing method of user equipment (UE) IP address and Diameter routing agent | |
| CN101646149B (en) | Method for deleting session messages in DRA | |
| CN101969673B (en) | Method for reselecting bearing binding and event report function | |
| CN101583112B (en) | Method and device for marking session information | |
| CN101286915B (en) | Access control method of packet data network, system thereof and PCRF entity | |
| CN101277541B (en) | Method for forwarding message of Diameter route entity | |
| CN101959257B (en) | Method for reselecting bear binding and event report function | |
| CN100579302C (en) | Selecting method of strategies under non-roaming scenery and the functional server of charging rules | |
| CN101227391B (en) | method for selecting function entity of tactics and charging rules under non-roaming condition | |
| CN101267319B (en) | A method for distributing control rule of policy billing | |
| CN102075894B (en) | Selection method and system for policy and charging rules function entity | |
| CN101198171B (en) | Routing method for strategy charging control information in roaming scene | |
| CN102148689A (en) | Policy and charging rules function entity selection method, device and system | |
| CN103209401A (en) | Strategy control method and system in convergence network | |
| CN101730192A (en) | Method and device for transmitting access network policy information and interaction system | |
| CN104349297A (en) | Charging policy method of internetwork signing authorization and device thereof | |
| CN101730047A (en) | Method and system for formulating strategy | |
| CN102123035B (en) | Policy and charging rules function (PCRF) entity selection method, device and system | |
| CN101447918B (en) | Notification method of user equipment access protocol and system thereof | |
| CN101998513B (en) | Method and system for controlling policy and charging rules function (PCRF) load balance and redirect diameter routing agent (DRA) | |
| CN101355561B (en) | Session information management method and system for DRA | |
| CN103369502B (en) | The processing method and network element of a kind of policy control session | |
| CN101998515B (en) | The implementation method of control PCRF load balancing and realize system | |
| CN102791042A (en) | Method and system for establishing S9 subsession and policy and charging rules function (PCRF) | |
| CN102264054B (en) | Resource management method and system |
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 |