WO2010034195A1 - Method for providing ip address of user equipment, diameter routing agent - Google Patents

Method for providing ip address of user equipment, diameter routing agent Download PDF

Info

Publication number
WO2010034195A1
WO2010034195A1 PCT/CN2009/071555 CN2009071555W WO2010034195A1 WO 2010034195 A1 WO2010034195 A1 WO 2010034195A1 CN 2009071555 W CN2009071555 W CN 2009071555W WO 2010034195 A1 WO2010034195 A1 WO 2010034195A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
message
session
dra
pcrf
Prior art date
Application number
PCT/CN2009/071555
Other languages
French (fr)
Chinese (zh)
Inventor
周晓云
宗在峰
Original Assignee
刘建
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 刘建 filed Critical 刘建
Publication of WO2010034195A1 publication Critical patent/WO2010034195A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403Architecture for metering, charging or billing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24Accounting or billing

Definitions

  • Diameter routing agent User equipment IP address providing method, Diameter routing agent
  • the present invention relates to the field of communications, and in particular to a user equipment network protocol (Internet Protocol, IP address) address providing method, and a Diameter routing agent.
  • the Evolved Packet System (Evolved Packet System) of the 3rd Generation Partnership Project (3GPP) includes: Evolved Universal Terrestrial Radio Access (Evolved Universal Terrestrial Radio Access) Network, the tube is called E-UTRAN, Mobility Management Entity (MME), Monthly Serving Gateway (S-GW), Data Network Gateway (Packet Data Network Gate Way) Called P-GW), Home Subscriber Server (HSS), 3GPP+Authorized Accounting (Authentication, Authorization and Accounting, AAA), Policy and Billing
  • MME Mobility Management Entity
  • S-GW Monthly Serving Gateway
  • S-GW Data Network Gateway
  • Packet Data Network Gate Way Called P-GW
  • HSS Home Subscriber Server
  • 3GPP+Authorized Accounting Authentication, Authorization and Accounting, AAA
  • PCRF Policy and Charging Rules Function
  • the S-GW is an access gateway device connected to the E-UTRAN, and forwards data between the E-UTRAN and the P-GW, and is responsible for buffering paging waiting data;
  • the P-GW is an EPS and a packet data network ( Packet Data Network, the border gateway of the PDN, is responsible for accessing the PDN, forwarding data between the EPS and the PDN, etc.
  • the PCRF interfaces with the operator's IP service network through the Rx interface to obtain service information.
  • the PCRF passes the Gx/Gxa/ The Gxc interface is connected to the gateway device in the network, and is responsible for initiating the establishment of the IP bearer, ensuring the quality of service (Quality of Service, called QoS), and performing charging control.
  • QoS Quality of Service
  • EPS supports interworking with non-3GPP networks and is implemented through the S2a/b/c interface, which acts as a 4 seed point between the 3GPP network and the non-3GPP network.
  • the non-3GPP network includes: a trusted non-3GPP network and an untrusted non-3GPP network, wherein IP access of the trusted non-3GPP network can directly interface with the P-GW through S2a; IP access of the untrusted non-3GPP network needs to be evolved
  • the data gateway (Evolved Packet Data Gateway, called ePDG) is connected to the P-GW, and the interface between the ePDG and the P-GW is S2b.
  • ePDG Evolved Packet Data Gateway
  • the Policy and charging enforcement function exists in the P-GW, and the PCRF passes through the P-GW.
  • the connection can complete the control of all functions, and the PCRF exchanges information with the P-GW through the Gx interface.
  • the interface between the P-GW and the S-GW is based on Proxy Mobile IP (proxy Mobile IP)
  • the S-GW has a Bearer Binding and Event Report Function (Bearer Binding and Event Report Function).
  • BBERF Bearer Binding and Event Report Function
  • the trusted non-3GPP access gateway When the trusted non-3GPP network accesses, the trusted non-3GPP access gateway also resides in the BBERF, and the trusted non-3GPP network access gateway exchanges information with the PCRF through the Gxa interface.
  • the S9 interface serves as an interface between the home PCRF (hereinafter referred to as hPCRF) and the visited PCRF (hereinafter referred to as vPCRF), and at the same time, provides the application function of the service for the UE ( The Application Function, called AF), sends service information for generating a Policy and Charging Control (PCC) policy to the PCRF through the Rx interface.
  • hPCRF home PCRF
  • vPCRF visited PCRF
  • AF The Application Function
  • FIG. 1 is a schematic diagram of the roaming architecture of the home routing of EPS according to the related art.
  • the P-GW is the home network (also called the home network). ), IP services provided by the home network operator (ie AF home network).
  • the second type is called local grooming and IP service is provided by the home network operator.
  • FIG. 2 is a schematic diagram of the roaming architecture of the local grooming of the related technology and the IP service provided by the home network operator, as shown in FIG. P-GW is visiting the network and providing IP services (ie AF home network) by the home network operator.
  • the third type is called local grooming and is provided by the visited network operator.
  • FIG. 1 is a schematic diagram of the roaming architecture of the home routing of EPS according to the related art.
  • the P-GW is the home network (also called the home network). ), IP services provided by the home network operator (ie AF home network).
  • the second type is called local grooming and IP service is provided by the home network operator.
  • FIG. 3 is a schematic diagram of the roaming architecture of the local network of the EPS and the visited network operator providing the IP service according to the related art, as shown in FIG.
  • the P-GW is visiting the network, and the IP service is provided by the visiting network operator (ie, the AF is on the visited network).
  • the ten-party protocol adopted by the PCC architecture is the Diameter application protocol developed on the basis of Diameter's Diameter Base Protocol.
  • the PCC architecture has defined a 10-meter application for Diameter applications used in non-roaming scenarios.
  • the PCC architecture uses these ten protocols to establish Diameter sessions between each PCC client (BBERF) and the PCRF, and uses these Diameter sessions to transmit information and policies for developing PCC policies.
  • the current implementation of the S9 roaming interface is as follows: (1) The vPCRF terminates all IP connection access networks of the UE (IP Connectivity Access Network, referred to as IP-CAN).
  • the session refers to the connection of the UE to the packet data network
  • Visit the Gx session of the local network ie, build on the Gx interface
  • a Diameter session ie, a Diameter session established on a Gxa or Gxc interface
  • establishing an S9 session between the vPCRF and the hPCRF ie, a Diameter session established on the S9 interface
  • S9 session Transmitting the Gx session, the information transmitted by the Gxx session
  • the vPCRF does not terminate the Rx session in the visited network, but only forwards the message of the Rx session to the hPCRF, and the vPCRF acts as a proxy (Proxy).
  • PCRF public Land Mobile Network
  • PCRF Diameter
  • PCRF Diameter
  • the EPS introduces a Dialogic function module Diameter in each Diameter (PCRF) i or The routing agent (Diameter Routing Agent) is called DRA.
  • PCRF Diameter Routing Agent
  • DRA Dialogic function module Diameter in each Diameter
  • the DRA selects a PCRF for this IP-CAN session, and the PCEF, BBERF and AF associated with this IP-CAN session are associated by the DRA to the selected PCRF.
  • PCEF, BBERF, and AF respectively establish Diameter sessions with selected PCRFs, and transmit policies and service information for controlling IP-CAN sessions through these Diameter sessions.
  • the DRA In order to ensure that the DRA correctly associates the PCEF, BBERF and AF to a PCRF, the DRA maintains information that uniquely identifies the IP-CAN session and the corresponding PCRF identity or IP address.
  • the information identifying the IP-CAN session is the NAI of the UE.
  • PCEF, BBERF, and AF provide this information in establishing a Diameter session message with the PCRF.
  • the DRA looks up the saved information and can find the corresponding PCRF.
  • the DRA implementation can be implemented in three ways: (1) Redirect mode, when the Diameter client (eg, 3:4: PCEF, BBERF, and AF) sends a Diameter session establishment request message to the PCRF, The message is first sent to the DRA. If the DRA does not yet have this IP-CAN session or UE-related information, the DRA will select a PCRF for the IP-CAN session or UE and ⁇ ) retrieve the identity or address of the selected PCRF to the sender (ie, Diameter) Client). If there is already this IP-CAN session or UE related information in the DAR, the Bay' J DRA returns the corresponding PCRF's target or address to the Diameter client.
  • the Diameter client eg, 3:4: PCEF, BBERF, and AF
  • the Diameter client After obtaining the address or identifier of the PCRF, the Diameter client sends a Diameter session establishment request message to the selected PCRF. After jt ⁇ , Diameter session tampering message ⁇ P does not need to be sent to DRA, only in Diameter session At the end of the process, it is necessary to send a Diameter session termination request message to the DRA to notify the DRA to delete the related information.
  • (2) Proxy mode (referred to as PA1 in the present invention), when the Diameter client sends a Diameter session establishment request message to the PCRF, the message is first sent to the DRA. If the DRA does not yet have this IP-CAN session related information, the DRA will select a PCRF for this IP-CAN session and forward the message to the selected PCRF.
  • the DRA forwards the message to the corresponding PCRF.
  • the acknowledgment message of the PCRF is also forwarded to the Diameter client through the DRA.
  • (3) Proxy mode (referred to as PA2 in the present invention). Similar to the PA1 mode, the difference is that the DRA sends the IDF of the PCRF to the Diameter client when forwarding the acknowledgment message returned by the PCRF. In this way, in the subsequent message interaction, the Diameter client can directly interact with the PCRF without going through the DRA. Only when the Diameter session is terminated, it is necessary to send a Diameter session termination request message to the DRA to notify the DRA to delete related information.
  • an IP-CAN session of a UE can have both an IPv4 address and an IPv6 address. Under normal circumstances, since the IPv4 address space is limited, the address in IPv4 is allocated according to the request of the UE. The UE may allocate an IPv6 address to the UE when establishing an IP-CAN session. When the UE needs an IPv4 address, it requests the P-GW to allocate an IPv4 address.
  • the P-GW may send an IPv6 address to the DRA and the PCRF through an IP-CAN session establishment indication message.
  • the IP-CAN session 4 tampering message will be sent directly to the PCRF and will not be sent to the DRA, so the IPv4 address requested by the UE cannot be saved in the DRA.
  • the IPv4 AF provides service information to the IP-CAN session, and sends a service/application information message to the DRA, and carries the IPv4 address of the UE therein, the DRA cannot correctly find the PCRF according to the IPv4 address, so the AF will not be able to
  • the IP-CAN session provides service information for PCRF decision making, and dynamic policy charging control cannot be implemented.
  • the UE releases the IPv4 address the prior art cannot notify the DRA to delete the IPv4 address released by the UE.
  • the UE accesses an evolved packet core network (Evolved Packet Core Network, EPC) through a trusted non-3GPP access system or E-UTRAN under a local grooming roaming architecture
  • FIG. 4 is an IP-CAN according to the related art.
  • the identifier NAI of the UE, the PDN identifier, and the access information for formulating the policy are taken.
  • Step S402 The BBERF sends a "Gateway Control Session Establishment Indication" message to the visited DRA, and carries the identifier of the UE, the NAI, and the PDN identifier. And the access information for formulating the policy, etc.; Step S403, the vDRA determines that the PCRF is not selected for the UE according to the NAI, and the Bay' J vDRA selects a visited PCRF for the UE, and saves the binding relationship (NAI, The VDNF address is returned to the BBERF by the redirect message.
  • Step S404 the BBERF obtains the vPCRF address, sends a "Gateway Control Session Establishment Indication" message to the vPCRF, and carries the UE in the message. Identifying the NAI, the PDN identifier, the access information used to formulate the policy, and the like; Step S405, the vPCRF determines that the UE adopts local grooming according to the PDN identifier and the roaming protocol; the vPCRF terminates the session, and decides to initiate a new relationship with the hPCRF.
  • the VPCRF sends an S9 session establishment indication message to the home DRA, and carries the NAI, the PDN identifier, the access information for formulating the policy, and the like; Step S406, hDRA determines that the PCRF has not been selected for the UE according to the NAI.
  • the Bay' J hDRA selects a home PCRF for the UE, and saves the binding relationship (NAI, PDN identifier, hPCRF address); hDRA returns the address through the redirect message.
  • the vPCRF obtains the hPCRF address, saves the binding relationship (NAI, PDN identifier, hPCRF address), and sends an S9 session establishment indication message to the hPCRF, and carries the NAI, the PDN identifier, and the policy for the connection. Entering information and the like;
  • Step S408 the hPCRF interacts with the subscription profile repository (SPR) to obtain the subscription information of the UE, and formulates the PCC rule according to the network policy and the access information obtained from the above.
  • SPR subscription profile repository
  • Step S409 the vPCRF extracts the QoS rule from the PCC rule, and then modifies the QoS rule and the event trigger according to the local policy, and sends a confirmation message to the gateway establishment session through the gateway control session BBERF, BBERF installs QoS rules and event triggers;
  • Step S410 S-GW or trusted non-3GPP access gateway sends an IP-CAN to the P-GW Request message, which carries the NAI and the PDN identifier, and; the IP-CAN session establishment request message when implemented as a proxy binding update request message; P-GW receives the IP-CAN session establishment request After the message is obtained, the IP address is allocated to the UE according to the NAI and the PDN identity, and a binding cache bar is established.
  • step S410 can be performed simultaneously with the step S404.
  • Step S411 the PCEF residing on the P-GW to the vDRA Sending an IP-CAN session establishment indication message, and carrying the NAI, the PDN identifier, and the IP address therein;
  • Step S412 the vDRA determines that the vPCRF has been selected for the UE according to the NAI, and finds the binding relationship according to the NAI and the PDN identifier.
  • NAI, PDN identifier, vPCRF address (NAI, PDN identifier, vPCRF address), ⁇ ) update it to (NAI, PDN identity, IP address, vPCRF address);
  • vDRA returns a redirect message to the PCEF, and carries the vPCRF address selected by the vDRA;
  • the PCEF obtains the vPCRF address, and sends a ' ⁇ -CAN session setup message' to the vPCRF, and carries the identifier of the UE, the PDN identifier, the IP address, and the access information for formulating the policy, etc.;
  • Step S414 vPCRF According to the NAI, the S9 session has been established for the UE, and the binding relationship (NAI, PDN identifier, hPCRF address) is found according to the NAI and PDN identifiers, and updated to (NAI, PDN identifier, IP address, hPCRF).
  • the vPCRF sends an S9 session tampering indication message to the hPCRF, and carries the NAI, the PDN identifier, the IP address of the UE, and the access information used to formulate the policy, etc.; Step S415, the hPCRF may change according to the new information.
  • the previous PCC rule and the event trigger are sent to the vPCRF through the S9 session modification confirmation message.
  • the vPCRF determines whether the update occurs according to the received S9 session modification confirmation message. If the determination result is yes, the vPCRF is updated.
  • the vPCRF returns an IP-CAN session establishment confirmation message to the PCEF and carries the PCC rules and event triggers therein; the PCEF installs the PCC rules and event triggers; if the vPCRF extracts the QoS rules from the PCC rules and The event trigger is different from the previously issued QoS rule and event trigger, and the vPCRF also sends a QoS rule and an event trigger before the message update to the BBERF; in step S417, the PCEF returns an IP-CAN session response message to the BBERF;
  • the establishing an IP-CAN session response message may be an agent binding update confirmation message, and the establishing an IP-CAN session response Information without waiting for the IP-CAN session in step S416 of the transmission A confirmation message is established; in step S418, the BBERF returns to establish an IP-CAN session response message.
  • the Diameter session establishment request message and the Diameter session termination request message are sent (for example, the gateway control session establishment (terminating) indication, the S9 session establishment (terminating) indication, the IP-CAN session establishment (terminating)
  • the request message is sent to the DRA only when the message is indicated. Since the S9 session will be used to transmit information about all Gx, Gxx sessions of the UE.
  • the vPCRF does not send a setup request message to the hDRA, but sends a modification request message directly to the selected hPCRF. Therefore, there will be no IP address attribute in the binding relationship saved in hDRA.
  • the home AF If the home AF provides service information to the IP-CAN session, it will first send a request message to the hDRA, and the AF may only carry the IP address of the UE to identify, so hDRA will not find the hPCRF correctly, so the AF will not be able to
  • the IP-CAN session provides service information for hPCRF decision making, which results in dynamic policy charging control not being implemented.
  • the UE accesses the PDN multiple times, the above problem may also occur; for example, when the UE initially attaches, the first IP-CAN session is established by using the process of FIG. 4, when the UE decides to access another PDN.
  • a second IP-CAN session is established; the Gx session associated with the second IP-CAN session will use the established S9 session to transmit information, and the second IP-CAN session of the UE
  • the IP address will not be saved to hDRA, and the AF of the home location will not find the correct hPCRF. It can be seen from the above description that after the IP-CAN session is established, when the AF provides the service information, if the AF only carries the IP address of the UE for identification, it sends a request message to the DRA, which may cause the DRA to fail to find the PCRF correctly.
  • the present invention has been made in view of the problem that the AF in the related art only carries the IP address of the UE to transmit a request message to the DRA, and the DRA cannot correctly find the PCRF. Therefore, the present invention aims to provide a user equipment IP.
  • the address providing method and the Diameter routing agent are used to solve the above problem.
  • a user equipment IP address providing method is provided.
  • User equipment IP address providing method which is applied to include policy charging control
  • the communication system of the PCC client and the Diameter routing agent DRA and after the user equipment establishes an IP connection access network IP-CAN session with the packet data network, the foregoing method includes: the PCC client sends a predetermined message to the DRA, and carries therein IP address of the user device.
  • the PCC client comprises one of the following: Policy and Charging Rules Function Entity PCEF, Policy and Charging Rules Function Entity PCRF.
  • the predetermined message comprises one of: a Diameter session modification request message, a dedicated message for transmitting an IP address and/or an IP address operation information, wherein the Diameter session 4 tampering request message comprises one of the following: an IP-CAN session Modify the indication message, S9 session modification indication message.
  • the Diameter Session Tamper Request message includes a Diameter Credit Control Request message, wherein the attribute value pair of the credit control request type in the Diameter Credit Control Request message is set to "Update Request".
  • the method further includes: the DRA receiving the predetermined message and obtaining the IP address from the DRA; and the DRA updating the binding relationship between the user terminal or the IP-CAN session and the PCRF address according to the IP address, And returning a redirect message carrying the PCRF address to the PCC client or forwarding the predetermined message to the PCRF.
  • the predetermined message further carries indication information indicating that the user terminal or the binding relationship between the IP-CAN session and the PCRF address is performed to perform an add or delete IP address operation.
  • the method further includes: the DRA receiving the predetermined message and obtaining an IP address from the DRA; and the DRA adds the IP address to the binding relationship or the binding relationship according to the IP address and the indication information.
  • the intermediate IP address is deleted, and a redirect message is returned to the PCC client or a predetermined message is forwarded to the PCRF.
  • a Diameter routing agent is provided.
  • the Diameter routing agent includes: a receiving module, configured to receive a predetermined message from a PCC client, wherein the predetermined message carries IP address information; and an obtaining module, configured to obtain an IP address from a predetermined message received by the receiving module information.
  • the Diameter routing agent further includes: an update module, configured to update a binding relationship between the user terminal or the IP-CAN session and the PCRF address according to the IP address information acquired by the obtaining module; and a sending module, configured to send a redirect to the PCC client The message or forward the scheduled message to the PCRF.
  • FIG. 1 is a schematic diagram of a roaming architecture of a home route of an EPS according to the related art
  • FIG. 2 is a schematic diagram of a roaming architecture for providing IP services by a local network operator of an EPS according to the related art
  • FIG. FIG. 4 is a flowchart of an IP-CAN session establishment according to the related art
  • FIG. 5 is a schematic diagram of a UE for a localization of an EPS and a visited network operator providing IP services
  • FIG. FIG. 6 is a flowchart of a method for providing an IP address of a UE according to Embodiment 2 of the present invention
  • FIG. 7 is a flowchart of a method for providing an IP address of a UE according to Embodiment 3 of the present invention
  • FIG. 9 is a flowchart of a method for providing an IP address of a UE according to Embodiment 5 of the present invention
  • FIG. 10 is a schematic diagram of a structure of a Diameter routing proxy according to an embodiment of the present invention
  • Figure 11 is a diagram showing a preferred structure 411 of a Diameter routing agent according to an embodiment of the present invention.
  • the present invention provides a method and system for providing an IP address of a UE.
  • the PCC client sends a predetermined message carrying the IP address to the DRA.
  • the DRA receives the predetermined message and obtains the IP address from the DRA, and the DRA updates the binding relationship between the user terminal or the IP-CAN session and the PCRF address according to the IP address, and returns a redirect message to the PCC client or forwards the predetermined message to the PCRF.
  • a method for providing an IP address of a UE is provided, which is applied to a communication system including a PCC client and a DRA, and is applied to an UE after establishing an IP-CAN session with a packet data network.
  • the method includes: the PCC client sends a predetermined message to the DRA, and carries the IP address of the UE therein.
  • the PCC client may include one of the following: PCEF, PCRF; the predetermined message may include one of the following: a Diameter session tampering request message, a dedicated message for transmitting an IP address and/or an IP address operation information, where the Diameter session 4 tampering request message includes one of the following: IP-CAN session repair _? Zhang instructions message, S9 session repair _? Zhang instructions message.
  • the Diameter Session Tamper Request message includes a Diameter Credit Control Request message, wherein the attribute value pair of the credit control request type in the Diameter Credit Control Request message is set to "Update Request".
  • the DRA After the PCC client sends the predetermined message to the DRA, the DRA receives the predetermined message and obtains the IP address therefrom, and the DRA updates the binding relationship between the user terminal or the IP-CAN session and the PCRF address according to the IP address, and returns the weight to the PCC client. Direct the message or forward the scheduled message to the PCRF.
  • the predetermined message may further carry indication information indicating that the UE or the IP-CAN session and the PCRF address are bound to perform an operation of adding or deleting an IP address, in which case, the PCC client sends a reservation to the DRA.
  • the DRA receives the predetermined message and obtains the IP address from it; the DRA adds the IP address to the binding relationship or deletes the IP address from the binding relationship according to the IP address and the indication information, and returns a redirect message to the PCC client. Or forward the predetermined message to the PCRF.
  • the method for transmitting a predetermined message carrying an IP address to the DRA by using the PCC client solves the problem that the AF only carries the IP address of the UE to identify the IP address and sends a request message to the DRA, which may cause the DRA to fail to find the PCRF correctly. , realize dynamic policy charging control.
  • the implementation process of the present invention will be described in detail below with reference to examples.
  • FIG. 5 is a flowchart of a method for providing an IP address of a UE according to Embodiment 1 of the present invention. As shown in FIG. 5, the method includes the following steps: Step S501: receiving an S-GW with a BBERF function or a trusted non-3GPP access gateway.
  • Step S502 BBERF, The DRA and the PCRF perform the gateway control session establishment process, and the process includes: the BBERF sends a "Gateway Control Session Establishment Indication" message to the DRA, and carries the identifier of the UE, the PDN identifier, and the access information used to formulate the policy.
  • the DRA determines that the PCRF has not been selected for the UE according to the NAI; the DRA selects a PCRF for the UE, and saves the binding relationship (NAI, PDN identifier, PCRF address); the DRA retrieves the selected vPCRF address and returns it through the redirect message. BBERF; BBERF obtains the PCRF address, sends a "Gateway Control Session Establishment Indication" message to the PCRF, and carries the identifier of the UE, the PDN identifier, the access information used to formulate the policy, etc.
  • the PCRF After receiving the "Gateway Control Session Establishment Indication" message, the PCRF interacts with the User Profile (Repository Profile Repository) to obtain the subscription information of the UE, and according to the network policy and the reported access information. Develop QoS rules and event triggers, and send them to BBERF through "Gateway Control Session Establishment Confirmation Message".
  • the User Profile Repository Profile Repository
  • Step S503, S-GW or trusted non-3GPP access gateways The P-GW sends an IP-CAN session request message, and carries the NAI, PDN identifier and IPv6 address request therein, and the establishment IP-CAN session request message can be a proxy binding update request message when implemented; receiving at the P-GW After the IP-CAN session request message is established, please refer to the NAI, PDN identifier and IPv6 address.
  • step S503 can be performed simultaneously with step S502; and step S504, the PCEF residing at the P-GW sends a message of " ⁇ -CAN session establishment indication" to the DRA, and Carrying the NAI, the PDN identifier, and the IPv6 address therein; in step S505, the DRA determines that the PCRF has been selected for the UE according to the NAI, and finds the binding relationship (NAI, PDN identifier, PCRF address) according to the NAI and the PDN identifier.
  • the update is (NAI, PDN identity, IPv6 address, PCRF address); the DRA returns a redirect message to the PCEF, and carries the PCRF address selected by the DRA therein; Step S506, the PCEF acquires the PCRF address, and sends the PCRF to the PCRF.
  • ⁇ -CAN session establishment indication message and carrying therein the identifier of the UE, the NDN, the PDN identifier, the IPv6 address, and the access information for formulating the policy, etc.;
  • Step S507 the PCRF identifies the NAI, the PDN identifier, and the access information.
  • the PCC rules and event triggers are set up and sent to the PCEF through the IP-CAN session establishment confirmation message; the PCEF installs the PCC rules and event triggers, and the PCRF may need to update the QoS rules previously sent to the BBERF; Step S50 8:
  • the P-GW returns an IP-CAN session response to the S-GW or the trusted non-3GPP access gateway.
  • the establishment of the IP-CAN session response may be an agent binding update confirmation message. It should be noted that the establishment is performed.
  • the IP-CAN session response message does not have to wait for the IP-CAN session establishment confirmation message of step S507; in step S509, the BBERF returns to establish an IP-CAN session response; in step S510, the UE needs to use the IPv4 address service, and therefore needs an IPv4 address;
  • the UE requests the P-GW to allocate an IPv4 address; Step S511, the P-GW allocates an IPv4 address to the UE, and returns an acknowledgement message to the UE; Step S512, the PCEF sends a ' ⁇ -CAN Session Modification Indication" message to the DRA, and in which Carrying the IPv4 address of the UE; the "IP-CAN Session 4 Tampering Indication" message can be implemented as a Diameter Credit Control Request (Cell Control Request, CCR) message, where the CC-Request-Type attribute value pair ( Attribute Value Pair, the tube is called AVP. It is set to "UPDATE-REQUEST". The message carries the IPv4 address.
  • CCR Diameter Credit Control Request
  • the implicit indication is that the DRA adds force to the binding relationship.
  • the IPv4 address can of course carry the IPv4 address.
  • step S514 the PCEF sends an "IP-CAN session modification indication" message to the PCRF, and Carrying the IPv4 address of the UE therein; wherein, steps S512 and 514 can be performed simultaneously; Step S515, the PCRF determines the PCC rule according to the IPv4 address, and returns an IP-CAN session modification confirmation message to the PCEF; Step S516, the PCRF formulates the corresponding QoS rules, and update the BBERF QoS rules. It can be seen from this embodiment that when the IPv4 AF is to provide service information to the IP-CAN session, the AF will send an application/service information message to the DRA, and carry the IPv4 address of the UE therein, and the DRA will only use the IP address.
  • the PCEF may also notify the DRA UE's IPv4 address by using a customized specific message.
  • the UE requests to allocate IPv4 and IPv6 addresses in step S501, but only assigns an IPv6 address to the UE when the P-GW sends the IP-CAN session establishment indication message of step S504 (for example, an IPv6 address) Directly assigned by the P-GW, and IPv4 is assigned by the external network).
  • the PCEF needs to send the address to the DRA through the IPv4 address in step S512.
  • the implementation of the BBERF does not need to be performed in the implementation of the UE.
  • the other processes are similar.
  • the UE accesses the EPS through the DISMIPv6 protocol, a method similar to this embodiment can also be employed.
  • the PCEF sends the newly assigned IP address of the UE to the home location through the "IP-CAN Session Modification Indication" message.
  • DRA In the local grooming roaming scenario, the PCEF sends the newly assigned IP address of the UE to the visited DRA through the 'IP-CAN Session 4 Tampering Indication' message, and the visited PCRF passes the "S9 Session 4 Tampering Indication" The message sends the newly assigned IP address of the UE to the home DRA.
  • the DRA selection PCRF may be Per (per) IP-CAN (ie, One IP-CAN session of the UE selects one PCRF, different IP-CAN sessions of the UE may select different PCRFs, or Per UE (ie, all IP-CAN sessions of the UE select the same PCRF). Because jt ⁇ , the binding relationship saved in DRA is Per IP-CAN or Per UE.
  • the second embodiment describes that the UE accesses the EPC through the trusted non-3GPP access system or the E-UTRAN in the non-roaming architecture, and adopts PMIPv6. After the IP-CAN session is established in the first embodiment, P- The GW initiates the release of the IPv4 address.
  • Step S601 When the UE releases an IPv4 address or an IPv4 address expires, the P-GW initiates an IPv4 address deletion.
  • the PCEF sends a ' ⁇ -CAN session 4 tampering indication, message to the DRA, and carries therein information indicating the deletion of the IPv4 address, which may be explicit or implicit; "IP-CAN session The abbreviated indication "message may be a Diameter CCR message during implementation, wherein the CC-Request-Type AVP is set to "UPDATE_REQUEST"; in step S602, the DRA updates the binding relationship (NAI, PDN identity, IPv6 address, PCRF address) And returning a redirect message to the PCEF; step S603, the PCEF sends a message of the ' ⁇ -CAN session modification indication' to the PCRF, where the message 'IP-CAN session modification indication' carries information indicating that the IPv4 address is deleted; Step S601 and step S603 can be performed simultaneously; Step S604, the PCRF deletes the IPv4 address according to the indication, and updates the PCC rule, and returns an IP-CAN session 4 tampering confirmation message to the
  • the PCEF sends an indication of deleting the IP address to the home by using a ' ⁇ -CAN session ⁇ •instruction indication message” DRA;
  • the PCEF sends an indication of the deleted IP address to the visited DRA via the 'IP-CAN Session Modification Indication' message, and the IP address is deleted by the visited PCRF through the "S9 Session Modification Indication" message.
  • the indication of the address is sent to the home DRA.
  • the DRA selection PCRF is Per (per) IP-CAN or Per UE.
  • the binding relationship saved by the DRA is Per IP-CAN or Per UE.
  • Embodiment 3 This embodiment describes a procedure for establishing an IP-CAN session when the UE adopts PMIPv6 under the roaming architecture of the local grooming, accessing the EPC through the trusted non-3GPP access system or the E-UTRAN.
  • FIG. 7 is a flowchart of a method for providing an IP address of a UE according to Embodiment 3 of the present invention; as shown in FIG. 7, the method includes the following steps: Step S701 - Step S713 is the same as Step S401 - Step S413 of FIG. 4, and details are not described herein again.
  • Step S714 after the vPCRF receives the request message, sends an "S9 Session Modification Indication Request" message to the hDRA, and carries the NAI, the PDN identifier, and the IP address of the UE;
  • the S9 session modification indication request message may be The Diameter CCR message, where the CC-Request-Type AVP is set to "UPDATE_REQUEST"; it should be noted that the vPCRF may also notify the IP address of the hDRA UE by using a customized specific message; wherein the above IP address is IPv4 and/or An IPv6 address, which carries an IP address in the message, in fact implicitly indicates that the DRA adds the IP address in the binding relationship.
  • step S715 the hDRA determines that the The UE selects the PCRF, and finds the binding relationship (NAI, PDN identifier, hPCRF address) according to the NAI and PDN identifiers, and updates the binding relationship to (NAI, PDN, IP address, hPC). RF address); hDRA returns a redirect message to the vPCRF, and carries the address of the hPCRF therein; Steps S716 to S720 are the same as steps S414 to S418 in FIG. 4, and details are not described herein again.
  • step S714 and step S716 can be performed simultaneously, and step S714 can also use other messages to notify the IP address of the hDRA UE.
  • the home AF is to provide service information to the IP-CAN session
  • the hAF sends an application/service information message to the hDRA, and carries the IP address of the UE, and the hDRA finds the binding relationship according to the IP address, thereby Returns the hPCRF selected for this IP-CAN session.
  • the hAF then sends an application/service information message to the hPCRF to establish an AF session, and the service information is provided through the session.
  • Step S701 The procedure for the UE to establish an IP-CAN session by using the DSMIPv6 protocol to access the EPC through the trusted non-3GPP access network is similar to the embodiment.
  • the difference from the embodiment is as follows: Step S701, Step S702, Step S704, and Step S707 are not carried.
  • the PDN identifier but carries the care-of address CoA assigned by the trusted non-3GPP access gateway to the UE; there is no PDN identifier in the saved binding relationship but there is CoA; when searching for the binding relationship, the NAI and CoA can be searched. .
  • step S705 the vPCRF decides to establish an S9 session according to the absence of the PDN identifier.
  • Step S710 is sent by the UE to the P-GW, and carries the PDN identifier and the IP address of the UE in the sent message, and then the M message carries the PDN identifier and the IP address.
  • the DRA selection PCRF is Per UE
  • the binding relationship saved by the DRA is Per UE.
  • Embodiment 4 This embodiment describes that after establishing the first IP-CAN session by the procedure as in Embodiment 1, the UE decides to access another PDN and establish a third IP-CAN session. The P-GW of the second IP-CAN session is still in the visited place, and the P-GW may be the same P-GW as the P-GW of the first IP-CAN session, or may be a different P-GW.
  • Step S801 An S-GW or a trusted non-3GPP connected to a BBERF function
  • the ingress gateway receives the establishment of an IP-CAN session request message, and the S-GW or the trusted non-3GPP access gateway acquires the identifier NAI of the UE, the PDN identifier 'and the access information used to formulate the policy, etc.
  • the visited DRA sends a "Gateway Control Session Establishment Indication" message, and carries the identification of the UE, the NAI, the PDN identifier, and the access information used to formulate the policy
  • Step S803 the vDRA determines that the PCRF has been selected for the UE according to the NAI, that is, the vPCRF selected in the first embodiment, and the boosting force.
  • Step S804 BBERF acquires the vPCRF Address, sending a "Gateway Control Session Establishment Indication" message to the vPCRF, and carrying therein the identifier NAI of the UE, the PDN identifier ', the access information used to formulate the policy, etc.; Step S805, the vPCRF is based on the PDN identifier 'and The roaming protocol determines that the UE adopts local grooming; the vPCRF establishes an S9 session for the UE according to the NAI, and saves the binding relationship (NAI, PDN identifier ', hPCRF); the vPCRF terminates the session, and uses the previously established S9 session, The hPCRF sends an S9 session modification
  • Step S806 the hPCRF interacts with the SPR to obtain the subscription information of the UE, and according to the network policy and the uplink report. Enrolling information, etc., formulating a PCC rule and an event trigger, and transmitting the confirmation message to the vPCRF through the S9 session modification; Step S807, the vPCRF extracts the QoS rule from the PCC rule, and then Modifying QoS rules and event triggers according to the local policy, sending a confirmation message to the BBERF through the gateway control session establishment; BBERF installing QoS rules and event triggers; Step S808, S-GW or trusted non-3GPP access gateway sending to the P-GW Establishing an IP-CAN session request message, and carrying the NAI and PDN identifiers therein; the setup IP-CAN session request message is a proxy binding update request message during implementation; after the P-GW receives the message, according to the NAI, The PDN identifies 'assigning an IP address to the UE' and establishes a
  • the vDRA returns a redirect message to the PCEF, where the message carries the vPCRF address selected by the vDRA.
  • This vPCRF is the vPCRF selected for the first IP-CAN session; Step S811, the PCEF obtains the vPCRF address, and sends an "IP-CAN Session Establishment Indication" message to the vPCRF, where the message carries the identifier of the UE, the PDN identifier, the IP address, and the access information used to formulate the policy.
  • the vPCRF after receiving the request message, the vPCRF sends an S9 session modification indication request message to the hDRA, where the message carries the NAI, the PDN identifier 'and the IP address';
  • the S9 session modification indication request message may be a Diameter CCR message in the implementation process, where the CC - The Request-Type AVP is set to "UPDATE_REQUEST";
  • the vPCRF may also use a custom specific message to notify the hDRA UE of the IP address '; wherein the above IP address 'is an IPv4 and/or IPv6 address, carrying the IP in the message
  • the address ' in fact implicitly indicating that the DRA adds the IP address in the binding relationship', may of course adopt an explicit indication carrying the additional force p; in step S813, hDRA determines that the PCRF has been selected for the UE according to the NAI.
  • NAI binding relationship
  • PDN identifier hPCRF address
  • update NAI, PDN identifier ', IP address', hPCRF address
  • hDRA returns a redirect message to the vPCRF And carrying the address of the hPCRF
  • the hPCRF is the hPCRF selected by the first IP-CAN session
  • step S814 the vPCRF determines that the S9 session has been established for the UE according to the NAI, and then finds the NII and PDN identifiers.
  • the binding relationship (NAI, PDN identifier ', hPCRF address) is updated to (NAI, PDN identifier ', IP address', hPCRF address).
  • the vPCRF sends an S9 session tampering indication message to the hPCRF, and carries the NAI, the PDN identifies the ', the IP address', and the access information for formulating the policy, etc., wherein the step S814 may be in parallel with the step S812, or may be received.
  • step S813 The message of step S813 is sent again; in step S815, the hPCRF may change the previous PCC rule and the event trigger according to the new information, and send the confirmation message to the vPCRF through the S9 session modification; Step S816, if an update occurs, the vPCRF is updated.
  • PCC rules and event triggers vPCRF returns IP-CAN session establishment confirmation message to PCEF, and carries PCC rules and event triggers therein; PCEF installs PCC rules and event triggers; wherein, if vPCRF extracts QoS from PCC rules The rule and event triggers have changed with the previous delivery, and the vPCRF also sends the QoS rules and event triggers before the message update to the BBERF.
  • Step S817 the PCEF returns an IP-CAN session response to the BBERF.
  • establishing an IP-CAN session response may be an agent binding update confirmation message; the message does not have to wait for the confirmation message of step S816; Step S818, BBERF returns to establish IP-CAN session response.
  • the home AF is to provide service information to the second IP-CAN session
  • the hAF will send an application/service information message to the hDRA, where the message carries the IP address of the UE, and the hDRA is based on the IP address. The address 'find the binding relationship, and returns the hPCRF selected for the IP-CAN session to the hAF.
  • the hAF then sends an application/service information message to the hPCRF to establish an AF session, and the service information is provided through the session.
  • the DRA selection PCRF is Per UE
  • the binding relationship saved by the DRA is Per UE.
  • Embodiment 5 This embodiment describes a procedure in which the UE uses the DSMHV6 protocol to access the EPC to establish a first IP-CAN session, and then decides to access another PDN and establish a second IP-CAN session. The P-GW of the second IP-CAN session is still in the visited place, and the P-GW may be the same or different from the P-GW of the first IP-CAN session.
  • Step S901 The UE determines to access another PDN, and establishes security with the selected P-GW.
  • the P-GW will allocate a new IP address for the UE to establish an IP-CAN session; then the UE sends an IP-CAN session request message to the P-GW and carries the NAI in it.
  • the message may be a binding update request message during implementation; after receiving the message, the P-GW establishes the NAI, PDN identifier ', CoA and IP address' Binding the cache entry; Step S902, the PCEF residing at the P-GW sends an IP-CAN session establishment indication message to the vDRA, and carries the NAI, CoA, PDN identifier 'and IP address'therein; Step S903, vDRA The NAI judges that the PCRF has been selected for the UE, and then establishes a binding relationship (NAI, CoA, PDN identifier ', IP address', vPCRF address) according to the PDN identifier 'and IP address'; vDRA returns a redirect message to the PCEF And carrying the vPCRF address selected by vDRA; the vPCRF is the first IP-CAN Word selected vPCRF; Step S904, the PCEF acquires a vPCR
  • Step S905 after receiving the request message, the vPCRF sends an S9 session modification indication request message to the hDRA, and carries the NAI, CoA, PDN identifier 'and IP address'therein; the S9 session repair_revision request message is implemented.
  • the process may be a Diameter CCR message, where the CC-Request-Type AVP is set to "UPDATE_REQUEST"; wherein the vPCRF may also notify the hDRA UE's IP address by using a customized specific message; wherein the above IP address 'is IPv4 and And the IPv6 address, in the message carrying the IP address ', in fact implicitly indicating that the DRA adds the IP address in the binding relationship', of course, an explicit indication carrying the address can be used; step S906, hDRA has selected the PCRF for the UE according to the NAI judgment, and establishes a binding relationship according to the IP address 'and the PDN identifier' (NAI, CoA, PDN identifier ', IP address', hPCRF address); hDRA direction vPCRF Returning the redirect message, and carrying the address of the hPCRF; the hPCRF is the hPCRF selected by the first IP-CAN session; Step S907, the
  • the PDN identifier 'and the IP address' establishes a binding relationship (NAI, CoA, PDN identifier, IP address, and hPCRF address), and the vPCRF sends an S9 session 4 tampering indication message to the hPCRF, and carries the NAI, CoA, and PDN identifiers.
  • step S907 may be in parallel with step S905, or may be sent after receiving the message of step 906; step S908, hPCRF may only report the new information
  • the previous PCC rules and event triggers are changed, and sent to the vPCRF through the S9 session modification confirmation message; Step S909, if an update occurs, the vPCRF updates the PCC rules and event triggers; the vPCRF returns an IP-CAN session establishment confirmation message to the PCEF, And carrying the PCC rules and event triggers therein; PCEF installs the PCC rules and event triggers; Step S910, if the QoS rules and event triggers extracted by the vPCRF from the PCC rules are changed with the previous delivery, the Bay 1 J vPCR Sending a gateway control and QoS rule to the BBERF to provide a QoS rule and an event trigger before the message is updated; Step S911, the BBERF updates the QoS rule and the event
  • the establishment of the IP-CAN session response may be a binding update confirmation message, and the message is triggered by step S909.
  • the hAF sends an application/service information message to the hDRA, where the message carries the IP address of the UE, and the hDRA is located at the IP address to find the binding relationship.
  • the hPCRF selected for the IP-CAN session is returned to the hAF; the hAF then sends an application/service information message to the hPCRF to establish an AF session, and the service information is provided through the session.
  • the DRA selection PCRF is Per UE
  • the binding relationship saved by the DRA is Per UE.
  • a Diameter routing agent is provided, preferably,
  • FIG. 10 is a schematic diagram of a structure of a Diameter routing proxy according to an embodiment of the present invention.
  • the Diameter routing proxy includes: a receiving module 102 and an obtaining module 104.
  • the receiving module 102 is configured to receive a predetermined message from the PCC client, where the predetermined message carries the IP address information.
  • the obtaining module 104 is connected to the receiving module 102, and is configured to obtain IP address information from a predetermined message received by the receiving module 102.
  • FIG. 11 is a schematic diagram of a preferred structure of a Diameter routing agent according to an embodiment of the present invention.
  • the Diameter routing agent further includes: an update module 112, connected to the obtaining module 104, configured to obtain an IP address according to the obtaining module 104.
  • the information update is used to indicate the binding relationship between the IP address and the PCRF address.
  • the sending module 114 is connected to the update module 112, and is used to update the module to complete related operations. After that, a redirect message is sent to the PCC client.
  • the DRA of the PA2 implementation is similar to all the above embodiments. The only difference is that after receiving the Diameter session tampering request message, the DRA forwards the message to the PCRF. After jt ⁇ , the PCRF acknowledgment message is also forwarded to the PCC client via the DRA.
  • the method for sending a predetermined message carrying an IP address to the DRA by using the PCC client the DRA can obtain the IP address of the UE, and the AF of the home location can correctly find the home PCRF, which solves the related art.
  • the AF only carries the IP address of the UE for identification to send a request message to the DRA, and the DRA cannot correctly find the PCRF, and implements dynamic policy charging control.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or they may be Multiple modules or steps are made into a single integrated circuit module.
  • the invention is not limited to any particular combination of hardware and software.
  • the above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Abstract

A method for providing the IP address of user equipment (UE) is disclosed. A Diameter routing agent (DRA) is also disclosed. The above method is applied to the communication system including a policy and charging control (PCC) client and a DRA and applied after establishing an IP connectivity access network (IP-CAN) session between the UE and a packet data network (PDN). The above method includes that the PCC client sends a predetermined message, which carries the UE’s IP address, to the DRA. The above method and the DRA enable dynamic policy and charging control.

Description

用户设备 IP地址提供方法、 Diameter路由代理  User equipment IP address providing method, Diameter routing agent
技术领域 本发明涉及通信领域, 具体而言 , 涉及一种用户设备网络协议( Internet Protocol , 筒称为 IP ) 地址提供方法、 Diameter路由代理。 背景技术 第三代合作伙伴计划( 3rd Generation Partnership Project, 筒称为 3GPP ) 的演进的分组系统(Evolved Packet System, 筒称为 EPS ) 包括: 演进的通用 地面无线接入网 ( Evolved Universal Terrestrial Radio Access Network , 筒称为 E-UTRAN )、 移动管理单元 (Mobility Management Entity, 筒称为 MME )、 月 务网关 (Serving Gateway, 筒称为 S-GW )、 数据网络网关 (Packet Data Network Gate Way,筒称为 P-GW )、归属用户月 务器( Home Subscriber Server, 筒称为 HSS )、 3 GPP 认证 4受权计费 ( Authentication、 Authorization and Accounting ,筒称为 AAA )月 务器、策略和计费规则功能( Policy and Charging Rules Function, 筒称为 PCRF )及其他支撑节点。其中 , S-GW是与 E-UTRAN 相连的接入网关设备, 在 E-UTRAN和 P-GW之间转发数据, 并且负责对寻 呼等待数据进行緩存; P-GW是 EPS与分组数据网 ( Packet Data Network, 筒称为 PDN ) 的边界网关, 负责 PDN的接入、 在 EPS与 PDN间转发数据 等; PCRF通过 Rx接口与运营商 IP业务网络接口, 获取业务信息, PCRF 通过 Gx/Gxa/Gxc接口与网络中的网关设备相连接,负责发起 IP承载的建立, 保证业务数据的服务质量 (Quality of Service, 筒称为 QoS ), 并进行计费控 制。 The present invention relates to the field of communications, and in particular to a user equipment network protocol (Internet Protocol, IP address) address providing method, and a Diameter routing agent. BACKGROUND OF THE INVENTION The Evolved Packet System (Evolved Packet System) of the 3rd Generation Partnership Project (3GPP) includes: Evolved Universal Terrestrial Radio Access (Evolved Universal Terrestrial Radio Access) Network, the tube is called E-UTRAN, Mobility Management Entity (MME), Monthly Serving Gateway (S-GW), Data Network Gateway (Packet Data Network Gate Way) Called P-GW), Home Subscriber Server (HSS), 3GPP+Authorized Accounting (Authentication, Authorization and Accounting, AAA), Policy and Billing The Policy and Charging Rules Function (called the PCRF) and other supporting nodes. The S-GW is an access gateway device connected to the E-UTRAN, and forwards data between the E-UTRAN and the P-GW, and is responsible for buffering paging waiting data; the P-GW is an EPS and a packet data network ( Packet Data Network, the border gateway of the PDN, is responsible for accessing the PDN, forwarding data between the EPS and the PDN, etc. The PCRF interfaces with the operator's IP service network through the Rx interface to obtain service information. The PCRF passes the Gx/Gxa/ The Gxc interface is connected to the gateway device in the network, and is responsible for initiating the establishment of the IP bearer, ensuring the quality of service (Quality of Service, called QoS), and performing charging control.
EPS支持与非 3GPP网络的互通, 并通过 S2a/b/c接口实现, P-GW作 为 3GPP网络与非 3GPP网络间的 4苗点。 非 3GPP网络包括: 可信任非 3GPP 网络和不可信任非 3GPP网络, 其中, 可信任非 3GPP网络的 IP接入可直接 通过 S2a与 P-GW接口; 不可信任非 3GPP网络的 IP接入需要经过演进的数 据网关(Evolved Packet Data Gateway, 筒称为 ePDG )与 P-GW相连, ePDG 与 P-GW间的接口为 S2b。 在 EPS之间的 3GPP网络中, 策略和计费执行功能( Policy and charging enforcement function, 筒称为 PCEF )存在于 P-GW中, PCRF通过与 P-GW 的连接可以完成所有功能的控制, PCRF与 P-GW之间通过 Gx接口交换信 息。 当 P-GW与 S-GW之间的接口基于代理移动 IP ( Proxy Mobile IP , 筒称 为 ΡΜΙΡ ) 时, S-GW中存在 载绑定和事件 4艮告功能 (Bearer Binding and Event Report Function , 筒称为 BBERF ) , S-GW与 PCRF之间通过 Gxc接口 交换信息。 当可信任非 3GPP网络接入时, 可信任非 3GPP接入网关中也驻 留 BBERF ,可信任非 3GPP网络接入网关与 PCRF之间通过 Gxa接口交换信 息。 当用户设备 ( User Equipment, 筒称为 UE )漫游时 , S9接口作为归属地 PCRF (以下称为 hPCRF ) 和拜访地 PCRF (以下称为 vPCRF ) 的接口, 同 时, 为 UE提供业务的应用功能 (Application Function, 筒称为 AF ), 通过 Rx接口向 PCRF发送用于生成策略计费控制 ( Policy and Charging Control , 筒称为 PCC ) 策略的业务信息。 EPS supports interworking with non-3GPP networks and is implemented through the S2a/b/c interface, which acts as a 4 seed point between the 3GPP network and the non-3GPP network. The non-3GPP network includes: a trusted non-3GPP network and an untrusted non-3GPP network, wherein IP access of the trusted non-3GPP network can directly interface with the P-GW through S2a; IP access of the untrusted non-3GPP network needs to be evolved The data gateway (Evolved Packet Data Gateway, called ePDG) is connected to the P-GW, and the interface between the ePDG and the P-GW is S2b. In the 3GPP network between EPSs, the Policy and charging enforcement function (PCEF) exists in the P-GW, and the PCRF passes through the P-GW. The connection can complete the control of all functions, and the PCRF exchanges information with the P-GW through the Gx interface. When the interface between the P-GW and the S-GW is based on Proxy Mobile IP (proxy Mobile IP), the S-GW has a Bearer Binding and Event Report Function (Bearer Binding and Event Report Function). The cartridge is called BBERF), and the information is exchanged between the S-GW and the PCRF through the Gxc interface. When the trusted non-3GPP network accesses, the trusted non-3GPP access gateway also resides in the BBERF, and the trusted non-3GPP network access gateway exchanges information with the PCRF through the Gxa interface. When the user equipment (User Equipment, called UE) roams, the S9 interface serves as an interface between the home PCRF (hereinafter referred to as hPCRF) and the visited PCRF (hereinafter referred to as vPCRF), and at the same time, provides the application function of the service for the UE ( The Application Function, called AF), sends service information for generating a Policy and Charging Control (PCC) policy to the PCRF through the Rx interface.
EPS存在三种漫游架构, 第一种称为家乡路由, 图 1是根据相关技术的 EPS的家乡路由的漫游架构的示意图, 如图 1所示, P-GW在家乡网络(也 称归属地网络), 由家乡网络运营商提供 IP业务(即 AF在家乡网络)。 第二 种称为本地疏导并由家乡网络运营商提供 IP业务, 图 2是才艮据相关技术的 EPS的本地疏导并由家乡网络运营商提供 IP业务的漫游架构的示意图,如图 2所示, P-GW在拜访网络, 并由家乡网络运营商提供 IP业务(即 AF在家 乡网络)。 第三种称为本地疏导并由拜访地网络运营商提供 IP业务, 图 3是 根据相关技术的 EPS的本地疏导并拜访地网络运营商提供 IP业务的漫游架 构的示意图, 如图 3所示, P-GW在拜访网络, 并由拜访网络运营商提供 IP 业务(即 AF在拜访网络)。 下面将对图 1、 图 2和图 3进行详细描述。 在目前的相关技术中, PCC 架构采用的十办议是在 Diameter基础十办议 ( Diameter Base Protocol )基础上发 展的 Diameter应用协议。 目前, PCC架构已经定义了在非漫游场景下使用的 Diameter应用十办议, 例 。, 应用于 Gx接口的应用十办议, 应用于 Rx接口的应 用协议以及 Gxx (包括 Gxa和 Gxc接口)接口的应用协议等。 PCC架构采用 这些十办议建立各 PCC客户端 (例 口, BBERF ) 与 PCRF之间的 Diameter会 话, 并用这些 Diameter会话来传送用于制定 PCC策略的信息以及制定的策 略等。 目前实现 S9漫游接口的方案为: ( 1 ) vPCRF终结 UE的所有 IP连接接 入网 ( IP Connectivity Access Network, 筒称为 IP-CAN ) 会话 (指 UE到分 组数据网的连接)相关的存在于拜访地网络的 Gx会话(即, 在 Gx接口上建 立的 Diameter会话)、 Gx 会话 (即, 在 Gxa或 Gxc接口上建立的 Diameter 会话 ), 在 vPCRF和 hPCRF之间建立一个 S9会话 (即, 在 S9接口上建立 的 Diameter会话), 用 S9会话来传送 Gx会话、 Gxx会话传送的信息; (2 ) vPCRF 不终结拜访地网络中的 Rx 会话, 只是将 Rx 会话的消息转发给 hPCRF, vPCRF作为一个代理(Proxy )。 也就是说, 当 UE有多个 PDN连接 时 , 一个 S9会话将需要同时传送与这个 UE的多个 IP-CAN会话相关的多个 Gxx会话、 Gx会话的信息。 同时 EPS的一个公共陆地移动电话网( Public Land Mobile Network, 筒 称为 PLMN ) 中存在多个 PCRF节点, 并且所有的 PCRF节点属于一个或多 个 Diameter ( PCRF ) i或, 同一个 Diameter ( PCRF ) i或中的所有 PCRF具有 相同的能力。 一个 IP-CAN会话的 PCC策略只由一个 PCRF决定。 为了确保 一个 IP-CAN会话相关的所有 PCEF或 BBERF以及为这个 IP-CAN会话提供 业务的 AF都关联到同一个 PCRF, EPS在每个 Diameter ( PCRF ) i或中引入 了一个還辑功能模块 Diameter路由代理 ( Diameter Routing Agent, 筒称为 DRA )。当 UE要建立到一个 PDN的 IP-CAN会话时,由 DRA为这个 IP-CAN 会话选择一个 PCRF, 与这个 IP-CAN会话相关的 PCEF、 BBERF和 AF由 DRA来关联到所选择的 PCRF上。 PCEF、 BBERF和 AF分别与选中的 PCRF 建立 Diameter会话,并通过这些 Diameter会话传送对 IP-CAN会话进行控制 的策略和业务信息等。 为了确保 DRA正确地将 PCEF、 BBERF和 AF关联到 一个 PCRF, DRA要保存能够唯一标识这个 IP-CAN会话相关的信息和对应 的 PCRF标识或者 IP地址, 标识 IP-CAN会话的信息有 UE的 NAI、 UE的 IP地址以及 UE要接入 PDN的 APN等。 PCEF、 BBERF和 AF在建立与 PCRF 建立 Diameter会话消息中提供这些信息, DRA查找保存的信息, 就可以找 到对应的 PCRF。 在现有技术中 , DRA具体实现可以有三种方式: ( 1 ) Redirect (重定向) 方式,当 Diameter客户端(例 ¾口: PCEF、 BBERF和 AF )向 PCRF发送 Diameter 会话建立请求消息时, 该消息首先被发送给 DRA。 若 DRA 还没有这个 IP-CAN会话或 UE相关的信息时, DRA会为这个 IP-CAN会话或 UE选择 一个 PCRF , 并^)夺所选择的 PCRF的标识或地址返回给发送方(即, Diameter 客户端)。 若 DAR中已经有这个 IP-CAN会话或 UE相关的信息, 贝' J DRA将 对应的 PCRF 的标只或地址返回给 Diameter客户端。 Diameter客户端获取 PCRF的地址或标识后再向所选择的 PCRF发送 Diameter会话建立请求消息。 jt匕后, Diameter会话爹改消息啫 P不需要发送给 DRA, 只有在 Diameter会话 终结时,才需要向 DRA发送 Diameter会话终结请求消息通知 DRA删除相关 的信息。( 2 ) Proxy方式(在本发明中称为 PA1 ), 当 Diameter客户端向 PCRF 发送 Diameter会话建立请求消息时 , 该消息首先被发送给 DRA。 若 DRA还 没有这个 IP-CAN会话相关的信息时 , DRA会为这个 IP-CAN会话选择一个 PCRF , 并将该消息转发给所选择的 PCRF。 若 DAR 中已经有这个 IP-CAN 会话相关的信息 , 则 DRA将该消息转发给对应的 PCRF。 PCRF的确认消息 也通过 DRA转发给 Diameter客户端。 ( 3 ) Proxy方式(本发明中称为 PA2 )。 与 PA1 方式类似, 不同点在于 DRA在转发 PCRF返回的确认消息时会 PCRF的标识或地址也发送给 Diameter客户端。 这样在随后的消息交互中, Diameter客户端可以直接与 PCRF交互而不需要经过 DRA。只有在 Diameter 会话终结时,才需要向 DRA发送 Diameter会话终结请求消息通知 DRA删除 相关的信息。综上所述,对于 DRA的 Redirect和 PA2两种实现,只有 Diameter 会话建立请求消息和 Diameter 会话终结请求消息才会与 DRA 交互, 而 Diameter会话爹改消息不与 DRA交互。 在 EPS系统中, UE的一个 IP-CAN会话可以同时拥有一个 IPv4地址和 一个 IPv6地址。 在通常情况下, 由于 IPv4地址空间有限, 因此在 IPv4的地 址是才艮据 UE的请求分配的。 UE可以在建立 IP-CAN会话时, P-GW给 UE 分配一个 IPv6的地址。 当 UE需要 IPv4地址的时, 再向 P-GW请求分配一 个 IPv4的地址。在现有技术中, IP-CAN会话建立时, P-GW可以通过 IP-CAN 会话建立指示消息, 将 IPv6的地址发送给 DRA和 PCRF。 IP-CAN会话 4爹改 才旨示消息将直接发送给 PCRF,不发送给 DRA,因此 UE后面请求的 IPv4地址 无法保存在 DRA。 当 IPv4的 AF向该 IP-CAN会话提供业务信息, 向 DRA 发送业务 /应用信息消息, 并在其中携带 UE的 IPv4地址, 那么 DRA将无法 才艮据 IPv4地址正确找到 PCRF, 从而 AF将无法向 IP-CAN会话提供业务信 息用于 PCRF决策, 动态策略计费控制无法实现。 此外, 当 UE释放 IPv4地 址时, 现有技术也无法通知 DRA删除 UE释放的 IPv4地址。 There are three roaming architectures for EPS. The first one is called home routing. Figure 1 is a schematic diagram of the roaming architecture of the home routing of EPS according to the related art. As shown in Figure 1, the P-GW is the home network (also called the home network). ), IP services provided by the home network operator (ie AF home network). The second type is called local grooming and IP service is provided by the home network operator. FIG. 2 is a schematic diagram of the roaming architecture of the local grooming of the related technology and the IP service provided by the home network operator, as shown in FIG. P-GW is visiting the network and providing IP services (ie AF home network) by the home network operator. The third type is called local grooming and is provided by the visited network operator. FIG. 3 is a schematic diagram of the roaming architecture of the local network of the EPS and the visited network operator providing the IP service according to the related art, as shown in FIG. The P-GW is visiting the network, and the IP service is provided by the visiting network operator (ie, the AF is on the visited network). 1 , 2 and 3 will be described in detail below. In the current related technology, the ten-party protocol adopted by the PCC architecture is the Diameter application protocol developed on the basis of Diameter's Diameter Base Protocol. Currently, the PCC architecture has defined a 10-meter application for Diameter applications used in non-roaming scenarios. Application for Gx interface, application protocol for Rx interface and application protocol for Gxx (including Gxa and Gxc interface) interfaces. The PCC architecture uses these ten protocols to establish Diameter sessions between each PCC client (BBERF) and the PCRF, and uses these Diameter sessions to transmit information and policies for developing PCC policies. The current implementation of the S9 roaming interface is as follows: (1) The vPCRF terminates all IP connection access networks of the UE (IP Connectivity Access Network, referred to as IP-CAN). The session (refers to the connection of the UE to the packet data network) is related to Visit the Gx session of the local network (ie, build on the Gx interface) a Diameter session, a Gx session (ie, a Diameter session established on a Gxa or Gxc interface), establishing an S9 session between the vPCRF and the hPCRF (ie, a Diameter session established on the S9 interface), using an S9 session Transmitting the Gx session, the information transmitted by the Gxx session; (2) The vPCRF does not terminate the Rx session in the visited network, but only forwards the message of the Rx session to the hPCRF, and the vPCRF acts as a proxy (Proxy). That is, when the UE has multiple PDN connections, one S9 session will need to simultaneously transmit information of multiple Gxx sessions, Gx sessions related to multiple IP-CAN sessions of this UE. At the same time, there are multiple PCRF nodes in a public Land Mobile Network (PLMN) of EPS, and all PCRF nodes belong to one or more Diameter (PCRF) i or the same Diameter (PCRF) All PCRFs in i or have the same capabilities. The PCC policy for an IP-CAN session is determined by only one PCRF. In order to ensure that all PCEFs or BBERFs associated with an IP-CAN session and AFs serving this IP-CAN session are associated with the same PCRF, the EPS introduces a Dialogic function module Diameter in each Diameter (PCRF) i or The routing agent (Diameter Routing Agent) is called DRA. When the UE wants to establish an IP-CAN session to a PDN, the DRA selects a PCRF for this IP-CAN session, and the PCEF, BBERF and AF associated with this IP-CAN session are associated by the DRA to the selected PCRF. PCEF, BBERF, and AF respectively establish Diameter sessions with selected PCRFs, and transmit policies and service information for controlling IP-CAN sessions through these Diameter sessions. In order to ensure that the DRA correctly associates the PCEF, BBERF and AF to a PCRF, the DRA maintains information that uniquely identifies the IP-CAN session and the corresponding PCRF identity or IP address. The information identifying the IP-CAN session is the NAI of the UE. The IP address of the UE and the APN to which the UE accesses the PDN. PCEF, BBERF, and AF provide this information in establishing a Diameter session message with the PCRF. The DRA looks up the saved information and can find the corresponding PCRF. In the prior art, the DRA implementation can be implemented in three ways: (1) Redirect mode, when the Diameter client (eg, 3:4: PCEF, BBERF, and AF) sends a Diameter session establishment request message to the PCRF, The message is first sent to the DRA. If the DRA does not yet have this IP-CAN session or UE-related information, the DRA will select a PCRF for the IP-CAN session or UE and ^) retrieve the identity or address of the selected PCRF to the sender (ie, Diameter) Client). If there is already this IP-CAN session or UE related information in the DAR, the Bay' J DRA returns the corresponding PCRF's target or address to the Diameter client. After obtaining the address or identifier of the PCRF, the Diameter client sends a Diameter session establishment request message to the selected PCRF. After jt匕, Diameter session tampering message 啫P does not need to be sent to DRA, only in Diameter session At the end of the process, it is necessary to send a Diameter session termination request message to the DRA to notify the DRA to delete the related information. (2) Proxy mode (referred to as PA1 in the present invention), when the Diameter client sends a Diameter session establishment request message to the PCRF, the message is first sent to the DRA. If the DRA does not yet have this IP-CAN session related information, the DRA will select a PCRF for this IP-CAN session and forward the message to the selected PCRF. If there is already information related to this IP-CAN session in the DAR, the DRA forwards the message to the corresponding PCRF. The acknowledgment message of the PCRF is also forwarded to the Diameter client through the DRA. (3) Proxy mode (referred to as PA2 in the present invention). Similar to the PA1 mode, the difference is that the DRA sends the IDF of the PCRF to the Diameter client when forwarding the acknowledgment message returned by the PCRF. In this way, in the subsequent message interaction, the Diameter client can directly interact with the PCRF without going through the DRA. Only when the Diameter session is terminated, it is necessary to send a Diameter session termination request message to the DRA to notify the DRA to delete related information. In summary, for the Redirect and PA2 implementations of the DRA, only the Diameter session establishment request message and the Diameter session termination request message will interact with the DRA, and the Diameter session tampering message does not interact with the DRA. In an EPS system, an IP-CAN session of a UE can have both an IPv4 address and an IPv6 address. Under normal circumstances, since the IPv4 address space is limited, the address in IPv4 is allocated according to the request of the UE. The UE may allocate an IPv6 address to the UE when establishing an IP-CAN session. When the UE needs an IPv4 address, it requests the P-GW to allocate an IPv4 address. In the prior art, when an IP-CAN session is established, the P-GW may send an IPv6 address to the DRA and the PCRF through an IP-CAN session establishment indication message. The IP-CAN session 4 tampering message will be sent directly to the PCRF and will not be sent to the DRA, so the IPv4 address requested by the UE cannot be saved in the DRA. When the IPv4 AF provides service information to the IP-CAN session, and sends a service/application information message to the DRA, and carries the IPv4 address of the UE therein, the DRA cannot correctly find the PCRF according to the IPv4 address, so the AF will not be able to The IP-CAN session provides service information for PCRF decision making, and dynamic policy charging control cannot be implemented. In addition, when the UE releases the IPv4 address, the prior art cannot notify the DRA to delete the IPv4 address released by the UE.
UE 在本地疏导的漫游架构下, 通过可信任非 3GPP 接入系统或 E-UTRAN接入演进的分组核心网 (Evolved Packet Core Network, 筒称为 EPC ), 图 4是根据相关技术的 IP-CAN会话建立的流程图, 如图 4所示, 采 用 PMIPv6时, 建立 IP-CAN会话的流程如下: 步骤 S401 ,驻留有 BBERF功能的 S-GW或可信任非 3GPP接入网关接 收到建立 IP-CAN会话请求消息, 并且 S-GW或可信任非 3GPP接入网关获 取了 UE的标识 NAI、 PDN标识、 以及用于制定策略的接入信息等; 步骤 S402, BBERF向拜访地 DRA发送"网关控制会话建立指示 "消息 , 并在其中携带 UE的标识 NAI、 PDN标识、以及用于制定策略的接入信息等; 步骤 S403 , vDRA才艮据 NAI判断没有为该 UE选择过 PCRF , 贝' J vDRA 为该 UE选择一个拜访地 PCRF, 并保存绑定关系 (NAI、 PDN标识、 vPCRF 地址); vDRA 夺所选择的 vPCRF地址通过重定向消息返回给 BBERF; 步骤 S404, BBERF获取 vPCRF地址, 向该 vPCRF发送"网关控制会 话建立指示"消息, 并在其中携带有 UE的标识 NAI、 PDN标识、 用于制定 策略的接入信息等; 步骤 S405 , vPCRF才艮据 PDN标识以及漫游协议判断 UE采用了本地疏 导; vPCRF终结该会话, 并决定发起建立与 hPCRF之间新的 Diameter会话; vPCRF向归属地 DRA发送 S9会话建立指示消息 , 并在其中携带 NAI、 PDN 标识、 用于制定策略的接入信息等; 步骤 S406, hDRA才艮据 NAI判断没有为该 UE选择过 PCRF, 贝' J hDRA 为该 UE选择一个归属地 PCRF, 并保存绑定关系 (NAI、 PDN标识、 hPCRF 地址); hDRA将地址通过重定向消息返回给 vPCRF; 步骤 S407, vPCRF获取 hPCRF地址,保存绑定关系(NAI、 PDN标识、 hPCRF地址) ,并向 hPCRF发送 S9会话建立指示消息, 并在其中携带 NAI、 PDN标识、 用于制定策略的接入信息等; 步骤 S408 , hPCRF与用户签约文档库( Subscription Profile Repository , 筒称为 SPR ) 交互, 获取 UE的签约信息, 并才艮据网络策略以及上 4艮上来的 接入信息等制定 PCC规则和事件触发器, 并通过 S9会话建立确认消息发送 给 vPCRF; 步骤 S409, vPCRF从 PCC规则抽取 QoS规则 , 并才艮据本地策略修改 QoS 规则和事件触发器, 通过网关控制会话建立确认消息发送给 BBERF, BBERF安装 QoS规则和事件触发器; 步骤 S410, S-GW或可信任非 3GPP接入网关向 P-GW发送建立 IP-CAN 会话请求消息, 并在其中携带 NAI和 PDN标识; 该建立 IP-CAN会话请求 消息在实现时为代理绑定更新请求消息; P-GW接收到建立 IP-CAN会话请 求消息之后, 才艮据 NAI、 PDN标识为 UE分配 IP地址, 并建立绑定緩存条 ; 其中 , 上述的步骤 S410可以和步骤 S404同时进行; 步骤 S411 , 驻留在 P-GW的 PCEF向 vDRA发送 IP-CAN会话建立指 示消息, 并在其中携带 NAI、 PDN标识和 IP地址; 步骤 S412 , vDRA才艮据 NAI判断已经为该 UE选择了 vPCRF , 并才艮据 NAI和 PDN标识找到绑定关系 (NAI、 PDN标识、 vPCRF地址), ^)夺其更新 为 (NAI、 PDN标识、 IP地址、 vPCRF地址); vDRA向 PCEF返回重定向 消息, 并在其中携带 vDRA选择的 vPCRF地址; 步骤 S413 , PCEF获取 vPCRF地址, 向该 vPCRF发送' ΊΡ-CAN会话建 立才旨示"消息, 并在其中携带 UE的标识 NAI、 PDN标识、 IP地址和用于制 定策略的接入信息等; 步骤 S414, vPCRF才艮据 NAI判断已经为该 UE建立了 S9会话, 并才艮 据 NAI、 PDN标识找到绑定关系 (NAI、 PDN标识、 hPCRF地址), 并更新 为 (NAI、 PDN标识、 IP地址、 hPCRF地址), vPCRF向 hPCRF发送 S9会 话爹改指示消息, 并在其中携带 NAI、 PDN标识、 UE的 IP地址和用于制定 策略的接入信息等; 步骤 S415 , hPCRF可能才艮据新的信息更改之前的 PCC规则和事件触发 器 , 并通过 S9会话修改确认消息发送给 vPCRF; 步骤 S416, vPCRF才艮据接收的 S9会话修改确认消息判断是否发生更新, 在判断结果为是的情况下, vPCRF更新 PCC规则和事件触发器; vPCRF向 PCEF返回 IP-CAN会话建立确认消息 , 并在其中携带 PCC规则和事件触发 器; PCEF安装 PCC规则和事件触发器; 如果 vPCRF从 PCC规则中抽取的 QoS规则和事件触发器与之前下发 的 QoS规则和事件触发器不同 ,则 vPCRF还会向 BBERF发送消息更新之前 的 QoS规则和事件触发器; 步骤 S417, PCEF向 BBERF返回建立 IP-CAN会话应答消息; 在具体 的实现过程中,该建立 IP-CAN会话应答消息可以为代理绑定更新确认消息, 并且该建立 IP-CAN会话应答消息不必等待步骤 S416中发送的 IP-CAN会话 建立确认消息; 步骤 S418 , BBERF返回建立 IP-CAN会话应答消息。 在上述的流程中, 存在如下问题: 只有发送 Diameter会话建立请求消 息和 Diameter会话终结请求消息 (例如 , 网关控制会话建立 (终结) 指示, S9会话建立 (终结) 指示, IP-CAN会话建立 (终结) 指示等消息) 时才会 向 DRA发送请求消息。 由于 S9会话将用来传送 UE的所有 Gx、 Gxx会话的 信息。 在步骤 S414中, vPCRF不会再向 hDRA发送建立请求消息, 而是直 接向所选择的 hPCRF发送修改请求消息。 因此, hDRA中保存的绑定关系中 将没有 IP地址属性。 若在归属地 AF向该 IP-CAN会话提供业务信息 , 它将 首先向 hDRA发送请求消息, 而 AF有可能只携带 UE的 IP地址来标识, 那 么 hDRA将无法正确找到 hPCRF , 从而 AF将无法向 IP-CAN会话提供业务 信息用于 hPCRF决策, 导致动态策略计费控制无法实现。 同样地 , 当 UE多次 PDN接入时, 也会出现上述问题; 例如, UE在初 始附着时, 采用如图 4的流程建立了第一个 IP-CAN会话, 当 UE决定再接 入一个 PDN时, 采用本地疏导的漫游方式建立第二个 IP-CAN会话; 与第二 个 IP-CAN会话相关的 Gx会话将采用已建立的 S9会话来传送信息, 第二个 IP-CAN会话的 UE的 IP地址将同样不会保存到 hDRA,归属地的 AF同样也 就不能找到正确的 hPCRF。 从上述描述可以看出: 在 IP-CAN会话建立之后, 当 AF在提供业务信 息时, 如果 AF只携带 UE的 IP地址进行标识来向 DRA发送请求消息, 这 样会导致 DRA无法正确找到 PCRF。 The UE accesses an evolved packet core network (Evolved Packet Core Network, EPC) through a trusted non-3GPP access system or E-UTRAN under a local grooming roaming architecture, and FIG. 4 is an IP-CAN according to the related art. Flowchart of session establishment, as shown in FIG. 4, when PMIPv6 is adopted, the process of establishing an IP-CAN session is as follows: Step S401, an S-GW residing with a BBERF function or a trusted non-3GPP access gateway receives an establishment IP- CAN session request message, and S-GW or trusted non-3GPP access gateway obtained The identifier NAI of the UE, the PDN identifier, and the access information for formulating the policy are taken. Step S402: The BBERF sends a "Gateway Control Session Establishment Indication" message to the visited DRA, and carries the identifier of the UE, the NAI, and the PDN identifier. And the access information for formulating the policy, etc.; Step S403, the vDRA determines that the PCRF is not selected for the UE according to the NAI, and the Bay' J vDRA selects a visited PCRF for the UE, and saves the binding relationship (NAI, The VDNF address is returned to the BBERF by the redirect message. Step S404, the BBERF obtains the vPCRF address, sends a "Gateway Control Session Establishment Indication" message to the vPCRF, and carries the UE in the message. Identifying the NAI, the PDN identifier, the access information used to formulate the policy, and the like; Step S405, the vPCRF determines that the UE adopts local grooming according to the PDN identifier and the roaming protocol; the vPCRF terminates the session, and decides to initiate a new relationship with the hPCRF. The VPCRF sends an S9 session establishment indication message to the home DRA, and carries the NAI, the PDN identifier, the access information for formulating the policy, and the like; Step S406, hDRA determines that the PCRF has not been selected for the UE according to the NAI. The Bay' J hDRA selects a home PCRF for the UE, and saves the binding relationship (NAI, PDN identifier, hPCRF address); hDRA returns the address through the redirect message. In the step S407, the vPCRF obtains the hPCRF address, saves the binding relationship (NAI, PDN identifier, hPCRF address), and sends an S9 session establishment indication message to the hPCRF, and carries the NAI, the PDN identifier, and the policy for the connection. Entering information and the like; Step S408, the hPCRF interacts with the subscription profile repository (SPR) to obtain the subscription information of the UE, and formulates the PCC rule according to the network policy and the access information obtained from the above. And the event trigger, and sent to the vPCRF through the S9 session establishment confirmation message; Step S409, the vPCRF extracts the QoS rule from the PCC rule, and then modifies the QoS rule and the event trigger according to the local policy, and sends a confirmation message to the gateway establishment session through the gateway control session BBERF, BBERF installs QoS rules and event triggers; Step S410, S-GW or trusted non-3GPP access gateway sends an IP-CAN to the P-GW Request message, which carries the NAI and the PDN identifier, and; the IP-CAN session establishment request message when implemented as a proxy binding update request message; P-GW receives the IP-CAN session establishment request After the message is obtained, the IP address is allocated to the UE according to the NAI and the PDN identity, and a binding cache bar is established. The foregoing step S410 can be performed simultaneously with the step S404. Step S411, the PCEF residing on the P-GW to the vDRA Sending an IP-CAN session establishment indication message, and carrying the NAI, the PDN identifier, and the IP address therein; Step S412, the vDRA determines that the vPCRF has been selected for the UE according to the NAI, and finds the binding relationship according to the NAI and the PDN identifier. (NAI, PDN identifier, vPCRF address), ^) update it to (NAI, PDN identity, IP address, vPCRF address); vDRA returns a redirect message to the PCEF, and carries the vPCRF address selected by the vDRA; step S413, The PCEF obtains the vPCRF address, and sends a 'ΊΡ-CAN session setup message' to the vPCRF, and carries the identifier of the UE, the PDN identifier, the IP address, and the access information for formulating the policy, etc.; Step S414, vPCRF According to the NAI, the S9 session has been established for the UE, and the binding relationship (NAI, PDN identifier, hPCRF address) is found according to the NAI and PDN identifiers, and updated to (NAI, PDN identifier, IP address, hPCRF). The vPCRF sends an S9 session tampering indication message to the hPCRF, and carries the NAI, the PDN identifier, the IP address of the UE, and the access information used to formulate the policy, etc.; Step S415, the hPCRF may change according to the new information. The previous PCC rule and the event trigger are sent to the vPCRF through the S9 session modification confirmation message. In step S416, the vPCRF determines whether the update occurs according to the received S9 session modification confirmation message. If the determination result is yes, the vPCRF is updated. PCC rules and event triggers; the vPCRF returns an IP-CAN session establishment confirmation message to the PCEF and carries the PCC rules and event triggers therein; the PCEF installs the PCC rules and event triggers; if the vPCRF extracts the QoS rules from the PCC rules and The event trigger is different from the previously issued QoS rule and event trigger, and the vPCRF also sends a QoS rule and an event trigger before the message update to the BBERF; in step S417, the PCEF returns an IP-CAN session response message to the BBERF; In a specific implementation process, the establishing an IP-CAN session response message may be an agent binding update confirmation message, and the establishing an IP-CAN session response Information without waiting for the IP-CAN session in step S416 of the transmission A confirmation message is established; in step S418, the BBERF returns to establish an IP-CAN session response message. In the above process, there are the following problems: Only the Diameter session establishment request message and the Diameter session termination request message are sent (for example, the gateway control session establishment (terminating) indication, the S9 session establishment (terminating) indication, the IP-CAN session establishment (terminating) The request message is sent to the DRA only when the message is indicated. Since the S9 session will be used to transmit information about all Gx, Gxx sessions of the UE. In step S414, the vPCRF does not send a setup request message to the hDRA, but sends a modification request message directly to the selected hPCRF. Therefore, there will be no IP address attribute in the binding relationship saved in hDRA. If the home AF provides service information to the IP-CAN session, it will first send a request message to the hDRA, and the AF may only carry the IP address of the UE to identify, so hDRA will not find the hPCRF correctly, so the AF will not be able to The IP-CAN session provides service information for hPCRF decision making, which results in dynamic policy charging control not being implemented. Similarly, when the UE accesses the PDN multiple times, the above problem may also occur; for example, when the UE initially attaches, the first IP-CAN session is established by using the process of FIG. 4, when the UE decides to access another PDN. When the local IP-CAN session is established, a second IP-CAN session is established; the Gx session associated with the second IP-CAN session will use the established S9 session to transmit information, and the second IP-CAN session of the UE The IP address will not be saved to hDRA, and the AF of the home location will not find the correct hPCRF. It can be seen from the above description that after the IP-CAN session is established, when the AF provides the service information, if the AF only carries the IP address of the UE for identification, it sends a request message to the DRA, which may cause the DRA to fail to find the PCRF correctly.
发明内容 针对相关技术中的 AF只携带 UE的 IP地址进行标识来向 DRA发送请 求消息而导致的 DRA无法正确找到 PCRF的问题而提出本发明, 为此, 本 发明旨在提供一种用户设备 IP地址提供方法、 Diameter路由代理, 以解决上 述问题。 为了实现上述目的, 才艮据本发明的一个方面, 提供了一种用户设备 IP 地址提供方法。 根据本发明的用户设备 IP 地址提供方法, 应用于包括策略计费控制 PCC客户端、 Diameter路由代理 DRA的通信系统, 且应用于用户设备与分 组数据网建立 IP连接接入网 IP-CAN会话之后 , 上述方法包括: PCC客户端 向 DRA发送预定消息, 并在其中携带用户设备的 IP地址。 优选地, PCC客户端包括以下之一: 策略和计费规则功能实体 PCEF、 策略和计费规则功能实体 PCRF。 优选地, 预定消息包括以下之一: Diameter会话修改请求消息、 用于传 输 IP地址和 /或 IP地址操作信息的专用消息, 其中, Diameter会话 4爹改请求 消息包括以下之一: IP-CAN会话修改指示消息、 S9会话修改指示消息。 优选地 , Diameter会话爹改请求消息包括 Diameter信用控制请求消息, 其中, Diameter信用控制请求消息中的信用控制请求类型的属性值对设置为 "更新请求"。 优选地, PCC客户端向 DRA发送预定消息之后,上述方法还包括: DRA 接收预定消息并从中获取 IP地址; DRA才艮据 IP地址更新用户终端或 IP-CAN 会话与 PCRF地址的绑定关系,并向 PCC客户端返回携带有 PCRF地址的重 定向消息或向 PCRF转发预定消息。 优选地, 预定消息中还携带有指示对用户终端或 IP-CAN会话与 PCRF 地址的绑定关系执行添加或删除 IP地址操作的指示信息。 优选地, PCC客户端向 DRA发送预定消息之后,上述方法还包括: DRA 接收预定消息并从中获取 IP地址; DRA才艮据 IP地址和指示信息将 IP地址 添加到绑定关系或从绑定关系中将 IP地址删除, 并向 PCC客户端返回重定 向消息或向 PCRF转发预定消息。 为了实现上述目的, 根据本发明的另一方面, 提供了一种 Diameter路 由代理。 才艮据本发明的 Diameter路由代理包括: 接收模块, 用于接收来自 PCC 客户端的预定消息, 其中, 预定消息携带有 IP地址信息; 获取模块, 用于从 接收模块接收的预定消息中获取 IP地址信息。 优选地, Diameter路由代理还包括: 更新模块, 用于根据获取模块获取 的 IP地址信息更新用户终端或 IP-CAN会话与 PCRF地址的绑定关系; 发送 模块, 用于向 PCC客户端发送重定向消息或向 PCRF转发预定消息。 通过本发明, 采用 PCC客户端向 DRA发送携带有 IP地址的预定消息 的方法, 解决了相关技术中 AF只携带 UE的 IP地址进行标识来向 DRA发 送请求消息会导致 DRA无法正确找到 PCRF的问题, 实现了动态策略计费 控制。 附图说明 此处所说明的附图用来提供对本发明的进一步理解 ,构成本申请的一部 分, 本发明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的 不当限定。 在附图中: 图 1是根据相关技术的 EPS的家乡路由的漫游架构的示意图; 图 2是根据相关技术的 EPS的本地疏导并家乡网络运营商提供 IP业务 的漫游架构的示意图; 图 3是根据相关技术的 EPS的本地疏导并拜访地网络运营商提供 IP业 务的漫游架构的示意图; 图 4是根据相关技术的 IP-CAN会话建立的流程图; 图 5为本发明实施例一的 UE的 IP地址提供方法的流程图; 图 6为本发明实施例二的 UE的 IP地址提供方法的流程图; 图 7为本发明实施例三的 UE的 IP地址提供方法的流程图; 图 8为本发明实施例四的 UE的 IP地址提供方法的¾¾程图; 图 9为本发明实施例五的 UE的 IP地址提供方法的流程图; 图 10为本发明实施例的 Diameter路由代理的结构^ I图; 图 11为本发明实施例的 Diameter路由代理的优选结构 411图。 具体实施方式 功能相克述 如上所述, 由于在 IP-CAN会话建立之后, 当 AF在提供业务信息时 , 如果 AF只携带 UE的 IP地址进行标识来向 DRA发送请求消息, 这样会导 致 DRA无法正确找到 PCRF。 基于此, 本发明提供了一种 UE的 IP地址提 供方法和系统, 在 UE与分组数据网建立 IP连接接入网 IP-CAN会话之后 , PCC客户端向 DRA发送携带有 IP地址的预定消息的方法, DRA接收预定 消息并从中获取 IP地址, DRA才艮据 IP地址更新用户终端或 IP-CAN会话与 PCRF地址的绑定关系 , 并向 PCC客户端返回重定向消息或向 PCRF转发预 定消息。 下面将参考附图并结合实施例来详细说明本发明。 需要说明的是, 如果 不冲突, 本申请中的实施例以及实施例中的特征可以相互组合。 方法实施例 根据本发明的实施例, 提供了一种 UE的 IP地址提供方法, 应用于包 括 PCC客户端、 DRA的通信系统 , 且应用于 UE与分组数据网建立 IP-CAN 会话之后, 该方法包括: PCC客户端向 DRA发送预定消息, 并在其中携带 UE的 IP地址。 其中, PCC客户端可以包括以下之一: PCEF、 PCRF; 预定消息可以包 括以下之一: Diameter会话爹改请求消息、 用于传输 IP地址和 /或 IP地址操 作信息的专用消息,其中, Diameter会话 4爹改请求消息包括以下之一: IP-CAN 会话修 _?丈指示消息、 S9会话修 _?丈指示消息。 优选地 , Diameter会话爹改请求消息包括 Diameter信用控制请求消息, 其中, Diameter信用控制请求消息中的信用控制请求类型的属性值对设置为 "更新请求"。 在 PCC客户端向 DRA发送预定消息之后 , DRA接收预定消息并从中 获取 IP地址, DRA才艮据 IP地址更新用户终端或 IP-CAN会话与 PCRF地址 的绑定关系 , 并向 PCC客户端返回重定向消息或向 PCRF转发预定消息。 并且, 在预定消息中还可以携带有指示对 UE或 IP-CAN会话与 PCRF 地址的绑定关系执行添加或删除 IP地址操作的指示信息, 在这种情况下, 在 PCC客户端向 DRA发送预定消息之后, DRA接收预定消息并从中获取 IP 地址; DRA才艮据 IP地址和指示信息将 IP地址添加到绑定关系中或从绑定关 系中删除 IP地址, 并向 PCC客户端返回重定向消息或向 PCRF转发预定消 息。 通过本发明 , 采用 PCC客户端向 DRA发送携带有 IP地址的预定消息 的方法, 解决了相关技术中 AF只携带 UE的 IP地址进行标识来向 DRA发 送请求消息会导致 DRA无法正确找到 PCRF的问题, 实现了动态策略计费 控制。 下面将结合实例对本发明的实现过程进行详细描述。 实施例一 本实施例描述的是 UE在非漫游架构下, 通过可信任非 3GPP接入系统 或 E-UTRAN接入 EPC, 采用 PMIPv6时, 建立 IP-CAN会话的:^程。 图 5 为本发明实施例一的 UE的 IP地址提供方法的流程图, 如图 5所示, 包括如 下步骤: 步骤 S501 ,驻留有 BBERF功能的 S-GW或可信任非 3GPP接入网关接 收到建立 IP-CAN会话请求消息, 并且 S-GW或可信任非 3GPP接入网关获 取了 UE的标识 NAI、 PDN标识、 IPv6地址请求以及用于制定策略的接入信 息等; 步骤 S502, BBERF、 DRA、 PCRF进行交互执行网关控制会话建立过 程, 该过程具体包括: BBERF向 DRA发送"网关控制会话建立指示 "消息, 并在其中携带 UE的标识 NAI、 PDN标识、 用于制定策略的接入信息; DRA 才艮据 NAI判断没有为该 UE选择过 PCRF; DRA为该 UE选择一个 PCRF, 并保存绑定关系 (NAI、 PDN标识、 PCRF地址); DRA 夺所选择的 vPCRF 地址通过重定向消息返回给 BBERF; BBERF获取 PCRF地址, 向该 PCRF 发送"网关控制会话建立指示 "消息, 并在其中携带 UE的标识 NAI、 PDN标 识、 用于制定策略的接入信息等; 在 PCRF接收到 "网关控制会话建立指示" 消息之后 , 与用户签约文档库( Subscription Profile Repository, 筒称为 SPR ) 交互, 获取 UE的签约信息, 并根据网络策略以及上报上来的接入信息等制 定 QoS 规则和事件触发器, 并通过 "网关控制会话建立确认消息"发送给 BBERF, jt匕后, BBERF安装 QoS规则和事件触发器; 步骤 S503 , S-GW或可信任非 3GPP接入网关向 P-GW发送建立 IP-CAN 会话请求消息, 并在其中携带 NAI、 PDN 标识和 IPv6 地址请求, 该建立 IP-CAN会话请求消息在实现时可以为代理绑定更新请求消息; 在 P-GW接 收到建立 IP-CAN会话请求消息之后, 才艮据 NAI、 PDN标识和 IPv6地址请 求为 UE分配 IPv6地址, 并建立绑定緩存条目; 其中, 步骤 S503可以和步骤 S502同时进行; 步骤 S504,驻留在 P-GW的 PCEF向 DRA发送' ΊΡ-CAN会话建立指示" 消息, 并在其中携带 NAI、 PDN标识和 IPv6地址; 步骤 S505 , DRA才艮据 NAI判断已经为该 UE选择了 PCRF ,并才艮据 NAI 和 PDN标识找到绑定关系( NAI、 PDN标识、 PCRF地址), ^)夺其更新为( NAI、 PDN标识、 IPv6地址、 PCRF地址); DRA向 PCEF返回重定向消息, 并在 其中携带 DRA选择的 PCRF地址; 步骤 S506, PCEF获取 PCRF地址, 向该 PCRF发送' ΊΡ-CAN会话建立 指示"消息, 并在其中携带有 UE的标识 NAI、 PDN标识、 IPv6地址和用于 制定策略的接入信息等; 步骤 S507, PCRF才艮据 NAI、 PDN标识及接入信息等制定 PCC规则和 事件触发器 ,并通过 IP-CAN会话建立确认消息发送给 PCEF; PCEF安装 PCC 规则和事件触发器 , PCRF可能需要更新之前下发给 BBERF的 QoS规则; 步骤 S508 , P-GW向 S-GW或可信任非 3GPP接入网关返回建立 IP-CAN 会话应答, 具体地, 建立 IP-CAN会话应答可以为代理绑定更新确认消息, 需要说明的是, 该建立 IP-CAN会话应答消息不必等待步骤 S507的 IP-CAN 会话建立确认消息; 步骤 S509, BBERF返回建立 IP-CAN会话应答; 步骤 S510, UE要使用 IPv4地址的业务, 因此需要一个 IPv4的地址;SUMMARY OF THE INVENTION The present invention has been made in view of the problem that the AF in the related art only carries the IP address of the UE to transmit a request message to the DRA, and the DRA cannot correctly find the PCRF. Therefore, the present invention aims to provide a user equipment IP. The address providing method and the Diameter routing agent are used to solve the above problem. In order to achieve the above object, according to an aspect of the present invention, a user equipment IP address providing method is provided. User equipment IP address providing method according to the present invention, which is applied to include policy charging control The communication system of the PCC client and the Diameter routing agent DRA, and after the user equipment establishes an IP connection access network IP-CAN session with the packet data network, the foregoing method includes: the PCC client sends a predetermined message to the DRA, and carries therein IP address of the user device. Preferably, the PCC client comprises one of the following: Policy and Charging Rules Function Entity PCEF, Policy and Charging Rules Function Entity PCRF. Preferably, the predetermined message comprises one of: a Diameter session modification request message, a dedicated message for transmitting an IP address and/or an IP address operation information, wherein the Diameter session 4 tampering request message comprises one of the following: an IP-CAN session Modify the indication message, S9 session modification indication message. Preferably, the Diameter Session Tamper Request message includes a Diameter Credit Control Request message, wherein the attribute value pair of the credit control request type in the Diameter Credit Control Request message is set to "Update Request". Preferably, after the PCC client sends the predetermined message to the DRA, the method further includes: the DRA receiving the predetermined message and obtaining the IP address from the DRA; and the DRA updating the binding relationship between the user terminal or the IP-CAN session and the PCRF address according to the IP address, And returning a redirect message carrying the PCRF address to the PCC client or forwarding the predetermined message to the PCRF. Preferably, the predetermined message further carries indication information indicating that the user terminal or the binding relationship between the IP-CAN session and the PCRF address is performed to perform an add or delete IP address operation. Preferably, after the PCC client sends the predetermined message to the DRA, the method further includes: the DRA receiving the predetermined message and obtaining an IP address from the DRA; and the DRA adds the IP address to the binding relationship or the binding relationship according to the IP address and the indication information. The intermediate IP address is deleted, and a redirect message is returned to the PCC client or a predetermined message is forwarded to the PCRF. In order to achieve the above object, according to another aspect of the present invention, a Diameter routing agent is provided. The Diameter routing agent according to the present invention includes: a receiving module, configured to receive a predetermined message from a PCC client, wherein the predetermined message carries IP address information; and an obtaining module, configured to obtain an IP address from a predetermined message received by the receiving module information. Preferably, the Diameter routing agent further includes: an update module, configured to update a binding relationship between the user terminal or the IP-CAN session and the PCRF address according to the IP address information acquired by the obtaining module; and a sending module, configured to send a redirect to the PCC client The message or forward the scheduled message to the PCRF. The method for transmitting a predetermined message carrying an IP address to the DRA by using the PCC client solves the problem that the AF only carries the IP address of the UE to identify the IP address and sends a request message to the DRA, which may cause the DRA to fail to find the PCRF correctly. , realize dynamic policy charging control. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawings: FIG. 1 is a schematic diagram of a roaming architecture of a home route of an EPS according to the related art; FIG. 2 is a schematic diagram of a roaming architecture for providing IP services by a local network operator of an EPS according to the related art; FIG. FIG. 4 is a flowchart of an IP-CAN session establishment according to the related art; FIG. 5 is a schematic diagram of a UE for a localization of an EPS and a visited network operator providing IP services; FIG. FIG. 6 is a flowchart of a method for providing an IP address of a UE according to Embodiment 2 of the present invention; FIG. 7 is a flowchart of a method for providing an IP address of a UE according to Embodiment 3 of the present invention; FIG. 9 is a flowchart of a method for providing an IP address of a UE according to Embodiment 5 of the present invention; FIG. 10 is a schematic diagram of a structure of a Diameter routing proxy according to an embodiment of the present invention; Figure 11 is a diagram showing a preferred structure 411 of a Diameter routing agent according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS As described above, since the AF is providing service information after the IP-CAN session is established, If the AF only carries the IP address of the UE for identification to send a request message to the DRA, this will cause the DRA to fail to find the PCRF correctly. Based on this, the present invention provides a method and system for providing an IP address of a UE. After the UE establishes an IP connection access network IP-CAN session with the packet data network, the PCC client sends a predetermined message carrying the IP address to the DRA. In the method, the DRA receives the predetermined message and obtains the IP address from the DRA, and the DRA updates the binding relationship between the user terminal or the IP-CAN session and the PCRF address according to the IP address, and returns a redirect message to the PCC client or forwards the predetermined message to the PCRF. The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other if they do not conflict. Method Embodiments According to an embodiment of the present invention, a method for providing an IP address of a UE is provided, which is applied to a communication system including a PCC client and a DRA, and is applied to an UE after establishing an IP-CAN session with a packet data network. The method includes: the PCC client sends a predetermined message to the DRA, and carries the IP address of the UE therein. The PCC client may include one of the following: PCEF, PCRF; the predetermined message may include one of the following: a Diameter session tampering request message, a dedicated message for transmitting an IP address and/or an IP address operation information, where the Diameter session 4 tampering request message includes one of the following: IP-CAN session repair _? Zhang instructions message, S9 session repair _? Zhang instructions message. Preferably, the Diameter Session Tamper Request message includes a Diameter Credit Control Request message, wherein the attribute value pair of the credit control request type in the Diameter Credit Control Request message is set to "Update Request". After the PCC client sends the predetermined message to the DRA, the DRA receives the predetermined message and obtains the IP address therefrom, and the DRA updates the binding relationship between the user terminal or the IP-CAN session and the PCRF address according to the IP address, and returns the weight to the PCC client. Direct the message or forward the scheduled message to the PCRF. And, the predetermined message may further carry indication information indicating that the UE or the IP-CAN session and the PCRF address are bound to perform an operation of adding or deleting an IP address, in which case, the PCC client sends a reservation to the DRA. After the message, the DRA receives the predetermined message and obtains the IP address from it; the DRA adds the IP address to the binding relationship or deletes the IP address from the binding relationship according to the IP address and the indication information, and returns a redirect message to the PCC client. Or forward the predetermined message to the PCRF. The method for transmitting a predetermined message carrying an IP address to the DRA by using the PCC client solves the problem that the AF only carries the IP address of the UE to identify the IP address and sends a request message to the DRA, which may cause the DRA to fail to find the PCRF correctly. , realize dynamic policy charging control. The implementation process of the present invention will be described in detail below with reference to examples. The first embodiment describes that the UE accesses the EPC through the trusted non-3GPP access system or the E-UTRAN under the non-roaming architecture, and establishes the IP-CAN session when using the PMIPv6. FIG. 5 is a flowchart of a method for providing an IP address of a UE according to Embodiment 1 of the present invention. As shown in FIG. 5, the method includes the following steps: Step S501: receiving an S-GW with a BBERF function or a trusted non-3GPP access gateway. To establish an IP-CAN session request message, and the S-GW or the trusted non-3GPP access gateway acquires the identifier NAI of the UE, the PDN identifier, the IPv6 address request, and the access information for formulating the policy, etc.; Step S502, BBERF, The DRA and the PCRF perform the gateway control session establishment process, and the process includes: the BBERF sends a "Gateway Control Session Establishment Indication" message to the DRA, and carries the identifier of the UE, the PDN identifier, and the access information used to formulate the policy. The DRA determines that the PCRF has not been selected for the UE according to the NAI; the DRA selects a PCRF for the UE, and saves the binding relationship (NAI, PDN identifier, PCRF address); the DRA retrieves the selected vPCRF address and returns it through the redirect message. BBERF; BBERF obtains the PCRF address, sends a "Gateway Control Session Establishment Indication" message to the PCRF, and carries the identifier of the UE, the PDN identifier, the access information used to formulate the policy, etc. After receiving the "Gateway Control Session Establishment Indication" message, the PCRF interacts with the User Profile (Repository Profile Repository) to obtain the subscription information of the UE, and according to the network policy and the reported access information. Develop QoS rules and event triggers, and send them to BBERF through "Gateway Control Session Establishment Confirmation Message". After jt匕, BBERF installs QoS rules and event triggers; Step S503, S-GW or trusted non-3GPP access gateways The P-GW sends an IP-CAN session request message, and carries the NAI, PDN identifier and IPv6 address request therein, and the establishment IP-CAN session request message can be a proxy binding update request message when implemented; receiving at the P-GW After the IP-CAN session request message is established, please refer to the NAI, PDN identifier and IPv6 address. Obtaining an IPv6 address for the UE, and establishing a binding cache entry; wherein, step S503 can be performed simultaneously with step S502; and step S504, the PCEF residing at the P-GW sends a message of "ΊΡ-CAN session establishment indication" to the DRA, and Carrying the NAI, the PDN identifier, and the IPv6 address therein; in step S505, the DRA determines that the PCRF has been selected for the UE according to the NAI, and finds the binding relationship (NAI, PDN identifier, PCRF address) according to the NAI and the PDN identifier. ^) The update is (NAI, PDN identity, IPv6 address, PCRF address); the DRA returns a redirect message to the PCEF, and carries the PCRF address selected by the DRA therein; Step S506, the PCEF acquires the PCRF address, and sends the PCRF to the PCRF. ΊΡ-CAN session establishment indication message, and carrying therein the identifier of the UE, the NDN, the PDN identifier, the IPv6 address, and the access information for formulating the policy, etc.; Step S507, the PCRF identifies the NAI, the PDN identifier, and the access information. The PCC rules and event triggers are set up and sent to the PCEF through the IP-CAN session establishment confirmation message; the PCEF installs the PCC rules and event triggers, and the PCRF may need to update the QoS rules previously sent to the BBERF; Step S50 8: The P-GW returns an IP-CAN session response to the S-GW or the trusted non-3GPP access gateway. Specifically, the establishment of the IP-CAN session response may be an agent binding update confirmation message. It should be noted that the establishment is performed. The IP-CAN session response message does not have to wait for the IP-CAN session establishment confirmation message of step S507; in step S509, the BBERF returns to establish an IP-CAN session response; in step S510, the UE needs to use the IPv4 address service, and therefore needs an IPv4 address;
UE向 P-GW请求分配一个 IPv4地址; 步骤 S511 , P-GW为 UE分配 IPv4地址, 并向 UE返回确认消息; 步骤 S512, PCEF向 DRA发送' ΊΡ-CAN会话修改指示 "消息, 并在其中 携带 UE的 IPv4地址; "IP-CAN会话 4爹改指示"消息实现时可以为 Diameter 信用控制请求 ( Credit Control Request , 筒称为 CCR ) 消息, 其中, CC-Request-Type 属性值对 ( Attribute Value Pair , 筒称为 AVP ) 设置为 "UPDATE— REQUEST"; 在该消息中携带 IPv4地址, 事实上隐含的指示 DRA 在绑定关系中添力。该 IPv4地址, 当然可以携带添加该 IPv4地址的明确指示; 步骤 S513 , DRA 更新绑定关系 (NAI、 PDN标识、 IPv4地址、 IPv6 地址、 PCRF地址), 并向 PCEF返回重定向消息; 步骤 S514, PCEF向 PCRF发送" IP-CAN会话修改指示 "消息, 并在其 中携带 UE的 IPv4地址; 其中, 步骤 S512和 514可以同时进行; 步骤 S515 , PCRF才艮据 IPv4地址制定 PCC规则,并向 PCEF返回 IP-CAN 会话修改确认消息; 步骤 S516, PCRF制定相应的 QoS规则 , 并更新 BBERF的 QoS规则。 从该实施例可以看出:当 IPv4的 AF要向该 IP-CAN会话提供业务信息 时, AF将向 DRA发送应用 /业务信息消息, 并在其中携带 UE的 IPv4地址, DRA才艮据 IP地址找到绑定关系, 从而向 AF返回为该 IP-CAN会话选择的 PCRF。需要说明的是 , PCEF也可以采用定制的特定消息通知 DRA UE的 IPv4 地址。 在其他实施过程中, UE在步骤 S501中请求分配 IPv4和 IPv6的地址, 但在 P-GW发送步骤 S504的 IP-CAN会话建立指示消息时只为 UE分配了 IPv6的地址 (例如, IPv6的地址由 P-GW直接分配, 而 IPv4由外部网络分 配)。 在外部网络为 UE分配了 IPv4地址之后, PCEF需要通过步骤 S512 IPv4的地址发送给 DRA。 The UE requests the P-GW to allocate an IPv4 address; Step S511, the P-GW allocates an IPv4 address to the UE, and returns an acknowledgement message to the UE; Step S512, the PCEF sends a 'ΊΡ-CAN Session Modification Indication" message to the DRA, and in which Carrying the IPv4 address of the UE; the "IP-CAN Session 4 Tampering Indication" message can be implemented as a Diameter Credit Control Request (Cell Control Request, CCR) message, where the CC-Request-Type attribute value pair ( Attribute Value Pair, the tube is called AVP. It is set to "UPDATE-REQUEST". The message carries the IPv4 address. In fact, the implicit indication is that the DRA adds force to the binding relationship. The IPv4 address can of course carry the IPv4 address. Clear instructions; Step S513, the DRA updates the binding relationship (NAI, PDN identifier, IPv4 address, IPv6 address, PCRF address), and returns a redirect message to the PCEF. In step S514, the PCEF sends an "IP-CAN session modification indication" message to the PCRF, and Carrying the IPv4 address of the UE therein; wherein, steps S512 and 514 can be performed simultaneously; Step S515, the PCRF determines the PCC rule according to the IPv4 address, and returns an IP-CAN session modification confirmation message to the PCEF; Step S516, the PCRF formulates the corresponding QoS rules, and update the BBERF QoS rules. It can be seen from this embodiment that when the IPv4 AF is to provide service information to the IP-CAN session, the AF will send an application/service information message to the DRA, and carry the IPv4 address of the UE therein, and the DRA will only use the IP address. The binding relationship is found, thereby returning to the AF the PCRF selected for the IP-CAN session. It should be noted that the PCEF may also notify the DRA UE's IPv4 address by using a customized specific message. In other implementations, the UE requests to allocate IPv4 and IPv6 addresses in step S501, but only assigns an IPv6 address to the UE when the P-GW sends the IP-CAN session establishment indication message of step S504 (for example, an IPv6 address) Directly assigned by the P-GW, and IPv4 is assigned by the external network). After the external network allocates an IPv4 address to the UE, the PCEF needs to send the address to the DRA through the IPv4 address in step S512.
UE在非漫游架构下, 通过 E-UTRAN采用 GTP接入 EPC时或通过不 可信任非 3GPP接入网接入 EPC时, 实施的¾¾程中不需要有关 BBERF的交 互, 其他流程类似。 当 UE通过 DISMIPv6协议接入 EPS时, 也可采用与该 实施例相类似的方法。 When the UE accesses the EPC through G-TP through the E-UTRAN or when the EPC is accessed through the untrusted non-3GPP access network, the implementation of the BBERF does not need to be performed in the implementation of the UE. The other processes are similar. When the UE accesses the EPS through the DISMIPv6 protocol, a method similar to this embodiment can also be employed.
UE在漫游时, 也可以采用与该实施例相类似的方法; 具体地, 在家乡 路由漫游场景下 , 由 PCEF通过" IP-CAN会话修改指示 "消息将 UE新分配的 IP地址发送给归属地 DRA; 在本地疏导漫游场景下, 由 PCEF通过' 'IP-CAN 会话 4爹改指示"消息将 UE新分配的 IP地址发送给拜访地 DRA, 由拜访地 PCRF 通过" S9 会话 4爹改指示"消息将 UE 新分配的 IP 地址发送给归属地 DRA。 在上述实施例中 , DRA选择 PCRF可以是 Per (每) IP-CAN的 (即, UE的一个 IP-CAN会话选择一个 PCRF , UE的不同 IP-CAN会话可以选择 不同的 PCRF ), 也可以 Per UE的 (即, UE的所有 IP-CAN会话选择同一个 PCRF )。 因 jt匕, 在 DRA保存的绑定关系是 Per IP-CAN或 Per UE的。 实施例二 本实施例描述的是 UE在非漫游架构下, 通过可信任非 3GPP接入系统 或 E-UTRAN接入 EPC, 采用 PMIPv6, 在实施例一的建立 IP-CAN会话流程 之后, P-GW发起释放 IPv4地址的¾¾程。 图 6为本发明实施例二的 UE的 IP 地址提供方法的流程图, 如图 6所示, 包括如下步骤: 步骤 S601 , 当 UE释放 IPv4地址或 IPv4地址过期时, P-GW发起 IPv4 地址删除流程; PCEF向 DRA发送' ΊΡ-CAN会话 4爹改指示,,消息, 并在其中 携带有指示删除 IPv4地址的信息 , 该信息可以是明确的 , 也可以是隐含的; "IP-CAN会话爹丈指示 "消息在实施过程中可以为 Diameter CCR消息,其中, CC-Request-Type AVP设置为 "UPDATE— REQUEST"; 步骤 S602, DRA更新绑定关系 (NAI、 PDN标识、 IPv6地址、 PCRF 地址), 并向 PCEF返回重定向消息; 步骤 S603 , PCEF向 PCRF发送' ΊΡ-CAN会话修改指示 "消息 ,该' 'IP-CAN 会话修改指示 "消息中携带有指示删除 IPv4地址的信息; 其中, 步骤 S601和步骤 S603可以同时进行; 步骤 S604, PCRF才艮据指示删除 IPv4地址,并更新 PCC规则 , 向 PCEF 返回 IP-CAN会话 4爹改确认消息; 步骤 S605 , PCRF更新相应的 QoS规则 , 并更新 BBERF的 QoS规则; 步骤 S606, P-GW向 S-GW或可信任非 3GPP接入网关发送 "绑定 ¾t回 请求消息", 该绑定 回请求消息用于指示删除 IPv4地址; 步骤 S607, S-GW或可信任非 3GPP接入网关返回确认消息。 在其他实施过程中, PCEF也可以采用定制的特定消息通知 DRA删除 UE的 IPv4地址。 When the UE roams, a method similar to this embodiment may also be adopted; specifically, in the home routing roaming scenario, the PCEF sends the newly assigned IP address of the UE to the home location through the "IP-CAN Session Modification Indication" message. DRA; In the local grooming roaming scenario, the PCEF sends the newly assigned IP address of the UE to the visited DRA through the 'IP-CAN Session 4 Tampering Indication' message, and the visited PCRF passes the "S9 Session 4 Tampering Indication" The message sends the newly assigned IP address of the UE to the home DRA. In the above embodiment, the DRA selection PCRF may be Per (per) IP-CAN (ie, One IP-CAN session of the UE selects one PCRF, different IP-CAN sessions of the UE may select different PCRFs, or Per UE (ie, all IP-CAN sessions of the UE select the same PCRF). Because jt匕, the binding relationship saved in DRA is Per IP-CAN or Per UE. The second embodiment describes that the UE accesses the EPC through the trusted non-3GPP access system or the E-UTRAN in the non-roaming architecture, and adopts PMIPv6. After the IP-CAN session is established in the first embodiment, P- The GW initiates the release of the IPv4 address. FIG. 6 is a flowchart of a method for providing an IP address of a UE according to Embodiment 2 of the present invention. As shown in FIG. 6, the method includes the following steps: Step S601: When the UE releases an IPv4 address or an IPv4 address expires, the P-GW initiates an IPv4 address deletion. The PCEF sends a 'ΊΡ-CAN session 4 tampering indication, message to the DRA, and carries therein information indicating the deletion of the IPv4 address, which may be explicit or implicit; "IP-CAN session The abbreviated indication "message may be a Diameter CCR message during implementation, wherein the CC-Request-Type AVP is set to "UPDATE_REQUEST"; in step S602, the DRA updates the binding relationship (NAI, PDN identity, IPv6 address, PCRF address) And returning a redirect message to the PCEF; step S603, the PCEF sends a message of the 'ΊΡ-CAN session modification indication' to the PCRF, where the message 'IP-CAN session modification indication' carries information indicating that the IPv4 address is deleted; Step S601 and step S603 can be performed simultaneously; Step S604, the PCRF deletes the IPv4 address according to the indication, and updates the PCC rule, and returns an IP-CAN session 4 tampering confirmation message to the PCEF; Step S605, the PCRF updates the corresponding QoS Rules, and update the QoS rule of the BBERF; Step S606, the P-GW sends a "Binding Back Request Message" to the S-GW or the trusted non-3GPP access gateway, where the binding back request message is used to indicate that the IPv4 address is deleted; Step S607, the S-GW or the trusted non-3GPP access gateway returns an acknowledgement message. In other implementations, the PCEF may also use a customized specific message to notify the DRA to delete the IPv4 address of the UE.
UE在非漫游架构下, 通过 E-UTRAN采用 GTP接入 EPC时或通过不 可信任非 3GPP接入网接入 EPC时, 实施的¾¾程中不需要有关 BBERF的交 互, 其他流程类似。 当 UE通过 DISMIPv6协议接入 EPS时, 也可采用与该 实施例相类似的方法。 When the UE uses the GTP to access the EPC through the E-UTRAN in the non-roaming architecture, When a trusted non-3GPP access network accesses the EPC, there is no need for BBERF interaction in the implementation of the 3⁄4⁄4 process, and other processes are similar. When the UE accesses the EPS through the DISMIPv6 protocol, a method similar to this embodiment can also be employed.
UE在漫游时, 也可以采用与该实施例相类似的方法; 具体地, 在家乡 路由漫游场景下, 由 PCEF通过' ΊΡ-CAN会话^ ·改指示 "消息将删除 IP地址 的指示发送给归属地 DRA; 在本地疏导漫游场景下, 由 PCEF通过' 'IP-CAN 会话修改指示 "消息将删除 IP地址的指示发送给拜访地 DRA,由拜访地 PCRF 通过" S9会话修改指示 "消息将删除 IP地址的指示发送给归属地 DRA。 在上述实施例中, DRA选择 PCRF是 Per (每) IP-CAN的或 Per UE的。 DRA保存的绑定关系是 Per IP-CAN或 Per UE的。 实施例三 本实施例描述的是 UE在本地疏导的漫游架构下, 通过可信任非 3GPP 接入系统或 E-UTRAN接入 EPC, 采用 PMIPv6时, 建立 IP-CAN会话的流 程。图 7为本发明实施例三的 UE的 IP地址提供方法的流程图;如图 7所示, 包括如下步骤: 步骤 S701-步骤 S713与图 4的步骤 S401 -步骤 S413相同, 在此不再 赘述; 步骤 S714 , 在 vPCRF接收到请求消息之后 , 向 hDRA发送" S9会话修 改指示请求"消息 , 并在其中携带 NAI、 PDN标识和 UE的 IP地址; S9会话 修改指示请求消息在实施过程中可以为 Diameter CCR 消息, 其 中, CC-Request-Type AVP 设置为 "UPDATE— REQUEST"; 需要说明的是, vPCRF也可以采用定制的特定消息通知 hDRA UE的 IP地址; 其中, 上述 IP 地址为 IPv4和 /或 IPv6地址, 在该消息中携带 IP地址 , 事实上隐含地指示 DRA在绑定关系中添加该 IP地址, 当然可以采用携带添加该地址的明确指 示; 步骤 S715 , hDRA才艮据 NAI判断已经为该 UE选择了 PCRF, 并才艮据 NAI和 PDN标识找到绑定关系 (NAI、 PDN标识、 hPCRF地址) 并^)夺绑定 关系更新为 (NAI、 PDN标只、 IP地址、 hPCRF地址); hDRA向 vPCRF返 回重定向消息, 并在其中携带 hPCRF的地址; 步骤 S716-步骤 S720与图 4中的步骤 S414-步骤 S418相同, 在此不再 赘述。 需要说明的是, 步骤 S714与步骤 S716可以同时进行, 步骤 S714也可 以采用其他消息通知 hDRA UE的 IP地址。 当归属地 AF要向该 IP-CAN会话提供业务信息时 , hAF将向 hDRA发 送应用 /业务信息消息 , 并在其中携带 UE的 IP地址 , hDRA才艮据 IP地址找 到绑定关系, 从而向 hAF返回为该 IP-CAN会话选择的 hPCRF。 hAF再向 hPCRF发送应用 /业务信息消息, 建立 AF会话, 通过该会话提供业务信息。 When the UE roams, a method similar to the embodiment may also be adopted; specifically, in the home routing roaming scenario, the PCEF sends an indication of deleting the IP address to the home by using a 'ΊΡ-CAN session^•instruction indication message” DRA; In the local grooming roaming scenario, the PCEF sends an indication of the deleted IP address to the visited DRA via the 'IP-CAN Session Modification Indication' message, and the IP address is deleted by the visited PCRF through the "S9 Session Modification Indication" message. The indication of the address is sent to the home DRA. In the above embodiment, the DRA selection PCRF is Per (per) IP-CAN or Per UE. The binding relationship saved by the DRA is Per IP-CAN or Per UE. Embodiment 3 This embodiment describes a procedure for establishing an IP-CAN session when the UE adopts PMIPv6 under the roaming architecture of the local grooming, accessing the EPC through the trusted non-3GPP access system or the E-UTRAN. FIG. 7 is a flowchart of a method for providing an IP address of a UE according to Embodiment 3 of the present invention; as shown in FIG. 7, the method includes the following steps: Step S701 - Step S713 is the same as Step S401 - Step S413 of FIG. 4, and details are not described herein again. Step S714, after the vPCRF receives the request message, sends an "S9 Session Modification Indication Request" message to the hDRA, and carries the NAI, the PDN identifier, and the IP address of the UE; the S9 session modification indication request message may be The Diameter CCR message, where the CC-Request-Type AVP is set to "UPDATE_REQUEST"; it should be noted that the vPCRF may also notify the IP address of the hDRA UE by using a customized specific message; wherein the above IP address is IPv4 and/or An IPv6 address, which carries an IP address in the message, in fact implicitly indicates that the DRA adds the IP address in the binding relationship. Of course, an explicit indication that the address is added may be used. In step S715, the hDRA determines that the The UE selects the PCRF, and finds the binding relationship (NAI, PDN identifier, hPCRF address) according to the NAI and PDN identifiers, and updates the binding relationship to (NAI, PDN, IP address, hPC). RF address); hDRA returns a redirect message to the vPCRF, and carries the address of the hPCRF therein; Steps S716 to S720 are the same as steps S414 to S418 in FIG. 4, and details are not described herein again. It should be noted that step S714 and step S716 can be performed simultaneously, and step S714 can also use other messages to notify the IP address of the hDRA UE. When the home AF is to provide service information to the IP-CAN session, the hAF sends an application/service information message to the hDRA, and carries the IP address of the UE, and the hDRA finds the binding relationship according to the IP address, thereby Returns the hPCRF selected for this IP-CAN session. The hAF then sends an application/service information message to the hPCRF to establish an AF session, and the service information is provided through the session.
UE 通过可信任非 3GPP 接入网采用 DSMIPv6 协议接入 EPC 建立 IP-CAN会话的流程与该实施例类似 , 与该实施例的区别在于: 步骤 S701、 步骤 S702、 步骤 S704、 步骤 S707中不携带 PDN标识, 而是携带可信任非 3GPP接入网关为 UE分配的转交地址 CoA; 在保存的绑定关系中没有 PDN 标识而有 CoA; 在查找绑定关系时可以才艮据 NAI和 CoA进行查找。 在步骤 S705中 , vPCRF才艮据没有 PDN标识, 决定建立 S9会话。 步骤 S710由 UE 发送给 P-GW, 并在发送的消息中携带 PDN标识和 UE的 IP地址, 此后交 互的消息中 M夺携带 PDN标识和 IP地址。 在上述实施例中, DRA选择 PCRF是 Per UE的, DRA保存的绑定关 系是 Per UE的。 实施例四 本实施例描述 UE通过如实施例一的流程建立第一个 IP-CAN会话后, 决定再接入一个 PDN, 建立第二个 IP-CAN会话的¾¾程。 第二个 IP-CAN会 话的 P-GW仍然在拜访地, 该 P-GW有可能与第一个 IP-CAN会话的 P-GW 是同一个 P-GW, 也可能是不同的 P-GW。 图 8为才艮据本发明实施例四的 UE 的 IP地址提供方法的流程图, 如图 8所示, 包括如下步骤: 步骤 S801 ,驻留有 BBERF功能的 S-GW或可信任非 3GPP接入网关接 收到建立 IP-CAN会话请求消息, 并且 S-GW或可信任非 3GPP接入网关获 取了 UE的标识 NAI、 PDN标识'以及用于制定策略的接入信息等; 步骤 S802, BBERF向拜访地 DRA发送"网关控制会话建立指示 "消息 , 并在其中携带 UE的标识 NAI、 PDN标识'、 用于制定策略的接入信息; 步骤 S803 , vDRA才艮据 NAI判断已经为该 UE选择 PCRF , 即实施例一 中选择的 vPCRF ,增力。一个绑定关系( NAI、 PDN标识'、 vPCRF地址); vDRA 将所选择的 vPCRF地址通过重定向消息返回给 BBERF;该 vPCRF为第一个 IP-CAN会话选择的 vPCRF; 步骤 S804, BBERF获取 vPCRF地址, 向该 vPCRF发送"网关控制会 话建立指示"消息, 并在其中携带有 UE的标识 NAI、 PDN标识'、 用于制定 策略的接入信息等; 步骤 S805 , vPCRF才艮据 PDN标识'以及漫游协议判断 UE采用了本地疏 导; vPCRF根据 NAI判断已经为该 UE建立了一个 S9会话 , 保存绑定关系 ( NAI、 PDN标识'、 hPCRF ); vPCRF终结该会话, 采用之前建立的 S9会 话, 向 hPCRF发送 S9会话修改指示消息 , 并在其中携带 NAI、 PDN标识'、 用于制定策略的接入信息; 步骤 S806 , hPCRF与 SPR交互, 获取 UE的签约信息, 并根据网络策 略以及上报上来的接入信息等制定 PCC规则和事件触发器, 并通过 S9会话 修改确认消息发送给 vPCRF; 步骤 S807, vPCRF从 PCC规则抽取 QoS规则 , 并才艮据本地策略修改 QoS 规则和事件触发器, 通过网关控制会话建立确认消息发送给 BBERF; BBERF安装 QoS规则和事件触发器; 步骤 S808 , S-GW或可信任非 3GPP接入网关向 P-GW发送建立 IP-CAN 会话请求消息 , 并在其中携带 NAI和 PDN标识'; 该建立 IP-CAN会话请求 消息在实施过程中为代理绑定更新请求消息; 在 P-GW接收到消息之后, 根 据 NAI、 PDN标识'为 UE分配 IP地址', 并建立绑定緩存条目; 其中, 步骤 S808可以和步骤 S802同时进行; 步骤 S809 , 驻留在 P-GW的 PCEF向 vDRA发送 IP-CAN会话建立指 示消息, 消息中携带 NAI, PDN标识'和 IP地址'; 步骤 S810 , vDRA才艮据 NAI判断已为该 UE选择了 PCRF , 找到绑定关 系 (NAI, PDN标识', vPCRF地址), 并更新为 (NAI,PDN标识', IP地址', vPCRF地址)。 vDRA向 PCEF返回重定向消息, 消息中携带 vDRA选择的 vPCRF地址。 这个 vPCRF为第一个 IP-CAN会话选择的 vPCRF; 步骤 S811 , PCEF获取 vPCRF地址 , 向该 vPCRF发送 "IP-CAN会话建 立指示 "消息 , 消息中携带有 UE的标识 NAI、 PDN标识'、 IP地址'和用于制 定策略的接入信息等; 步骤 S812, vPCRF收到请求消息后, 向 hDRA发送 S9会话修改指示 请求消息, 消息中携带 NAI、 PDN标识'和 IP地址'; S9会话修改指示请求消 息在实施过程中可以为 Diameter CCR消息,其中 CC-Request-Type AVP设置 为" UPDATE— REQUEST"; vPCRF也可以采用定制特定消息用于通知 hDRA UE的 IP地址'; 其中, 上述 IP地址'为 IPv4和 /或 IPv6地址, 在该消息中携 带 IP地址', 事实上隐含地指示 DRA在绑定关系中添加该 IP地址', 当然可 以采用携带添力 p该地址的明确指示; 步骤 S813 , hDRA才艮据 NAI判断已经为该 UE选择了 PCRF, 并才艮据 NAI和 PDN标识'找到绑定关系 ( NAI、 PDN标识'、 hPCRF地址)并更新为 ( NAI、 PDN标识'、 IP地址'、 hPCRF地址); hDRA向 vPCRF返回重定向 消息, 并在其中携带 hPCRF的地址; 该 hPCRF为第一个 IP-CAN会话选择 的 hPCRF; 步骤 S814, vPCRF才艮据 NAI判断已为该 UE建立了 S9会话, 并才艮据 NAI和 PDN标识'找到绑定关系 (NAI、 PDN标识'、 hPCRF地址), 更新为 ( NAI、 PDN标识'、 IP地址'、 hPCRF地址)。 vPCRF向 hPCRF发送 S9会 话爹改指示消息, 并在其中携带 NAI, PDN标识'、 IP地址'和用于制定策略 的接入信息等; 其中, 步骤 S814可以和步骤 S812并行, 也可以等接收到步骤 S813的 消息后再发送; 步骤 S815 , hPCRF可能才艮据新的信息更改之前的 PCC规则和事件触发 器 , 并通过 S9会话修改确认消息发送给 vPCRF; 步骤 S816 ,若发生更新 ,则 vPCRF更新 PCC规则和事件触发器; vPCRF 向 PCEF返回 IP-CAN会话建立确认消息, 并在其中携带 PCC规则和事件触 发器; PCEF安装 PCC规则和事件触发器; 其中, 若 vPCRF从 PCC规则中抽取的 QoS规则和事件触发器与之前 下发的发生了变化, vPCRF还会向 BBERF发送消息更新之前的 QoS规则和 事件触发器; 步骤 S817, PCEF向 BBERF返回建立 IP-CAN会话应答; 在实施过程 中, 建立 IP-CAN会话应答可以为代理绑定更新确认消息; 该消息不必等待 步骤 S816的确认消息; 步骤 S818 , BBERF返回建立 IP-CAN会话应答。 需要说明的是,当归属地 AF要向第二个 IP-CAN会话提供业务信息时, hAF将向 hDRA发送应用 /业务信息消息, 该消息中携带有 UE的 IP地址', hDRA才艮据 IP地址'找到绑定关系, 从而向 hAF返回为该 IP-CAN会话选择 的 hPCRF , hAF再向 hPCRF发送应用 /业务信息消息, 建立 AF会话 , 通过 该会话提供业务信息。 在上述实施例中, DRA选择 PCRF是 Per UE的, DRA保存的绑定关 系是 Per UE的。 实施例五 本实施例描述 UE采用 DSMHV6协议接入 EPC建立第一个 IP-CAN会 话后 ,决定再接入一个 PDN,建立第二个 IP-CAN会话的流程。第二个 IP-CAN 会话的 P-GW仍然在拜访地,该 P-GW有可能与第一个 IP-CAN会话的 P-GW 是同一个, 也可能是不同的。 图 9为根据本发明实施例五的 UE的 IP地址提 供方法的流程图, 如图 9所示, 包括如下步骤: 步骤 S901 , UE决定再接入一个 PDN, 与所选择的 P-GW建立安全联 盟, 在该过程中 , P-GW将为 UE分配用于要建立的 IP-CAN会话的新的 IP 地址';随后 UE向 P-GW发送建立 IP-CAN会话请求消息,并在其中携带 NAI、 CoA、 IP地址'和 PDN标识'; 该消息在实施过程中可以为绑定更新请求消息; P-GW接收到该消息之后, 才艮据 NAI、 PDN标识'、 CoA和 IP地址'为建立绑 定緩存条目; 步骤 S902 , 驻留在 P-GW的 PCEF向 vDRA发送 IP-CAN会话建立指 示消息, 并在其中携带 NAI, CoA、 PDN标识'和 IP地址'; 步骤 S903 , vDRA才艮据 NAI判断已为该 UE选择了 PCRF ,又才艮据 PDN 标识'和 IP地址'建立一个绑定关系(NAI、 CoA、 PDN标识'、 IP地址'、 vPCRF 地址); vDRA向 PCEF返回重定向消息,并在其中携带 vDRA选择的 vPCRF 地址; 该 vPCRF为第一个 IP-CAN会话选择的 vPCRF; 步骤 S904, PCEF获取 vPCRF地址, 向该 vPCRF发送' ΊΡ-CAN会话建 立指示 "消息, 并在其中携带有 UE的标识 NAI、 CoA、 PDN标识'、 IP地址' 和用于制定策略的接入信息等; 步骤 S905 , vPCRF接收到请求消息之后, 向 hDRA发送 S9会话修改 指示请求消息, 并在其中携带 NAI、 CoA、 PDN标识'和 IP地址'; S9会话修 _ 改才旨示请求消息在实施过程中可以为 Diameter CCR 消息, 其中 CC-Request-Type AVP设置为 "UPDATE— REQUEST"; 其中, vPCRF也可以 采用定制的特定消息通知 hDRA UE的 IP地址'; 其中, 上述 IP地址'为 IPv4 和 /或 IPv6地址 , 在该消息中携带 IP地址', 事实上隐含的指示 DRA在绑定 关系中添力口该 IP地址', 当然可以采用携带添力口该地址的明确指示; 步骤 S906, hDRA才艮据 NAI判断已经为该 UE选择了 PCRF, 并才艮据 IP地址'和 PDN标识'建立一个绑定关系为 ( NAI、 CoA、 PDN标识'、 IP地址 '、 hPCRF地址); hDRA向 vPCRF返回重定向消息, 并在其中携带 hPCRF 的地址; 该 hPCRF为第一个 IP-CAN会话所选择的 hPCRF; 步骤 S907, vPCRF才艮据 NAI判断已为该 UE建立了 S9会话, 并才艮据The procedure for the UE to establish an IP-CAN session by using the DSMIPv6 protocol to access the EPC through the trusted non-3GPP access network is similar to the embodiment. The difference from the embodiment is as follows: Step S701, Step S702, Step S704, and Step S707 are not carried. The PDN identifier, but carries the care-of address CoA assigned by the trusted non-3GPP access gateway to the UE; there is no PDN identifier in the saved binding relationship but there is CoA; when searching for the binding relationship, the NAI and CoA can be searched. . In step S705, the vPCRF decides to establish an S9 session according to the absence of the PDN identifier. Step S710 is sent by the UE to the P-GW, and carries the PDN identifier and the IP address of the UE in the sent message, and then the M message carries the PDN identifier and the IP address. In the above embodiment, the DRA selection PCRF is Per UE, and the binding relationship saved by the DRA is Per UE. Embodiment 4 This embodiment describes that after establishing the first IP-CAN session by the procedure as in Embodiment 1, the UE decides to access another PDN and establish a third IP-CAN session. The P-GW of the second IP-CAN session is still in the visited place, and the P-GW may be the same P-GW as the P-GW of the first IP-CAN session, or may be a different P-GW. FIG. 8 is a flowchart of a method for providing an IP address of a UE according to Embodiment 4 of the present invention. As shown in FIG. 8, the method includes the following steps: Step S801: An S-GW or a trusted non-3GPP connected to a BBERF function The ingress gateway receives the establishment of an IP-CAN session request message, and the S-GW or the trusted non-3GPP access gateway acquires the identifier NAI of the UE, the PDN identifier 'and the access information used to formulate the policy, etc.; Step S802, BBERF The visited DRA sends a "Gateway Control Session Establishment Indication" message, and carries the identification of the UE, the NAI, the PDN identifier, and the access information used to formulate the policy; Step S803, the vDRA determines that the PCRF has been selected for the UE according to the NAI, that is, the vPCRF selected in the first embodiment, and the boosting force. a binding relationship (NAI, PDN identifier ', vPCRF address); vDRA returns the selected vPCRF address to the BBERF through a redirect message; the vPCRF is the vPCRF selected for the first IP-CAN session; Step S804, BBERF acquires the vPCRF Address, sending a "Gateway Control Session Establishment Indication" message to the vPCRF, and carrying therein the identifier NAI of the UE, the PDN identifier ', the access information used to formulate the policy, etc.; Step S805, the vPCRF is based on the PDN identifier 'and The roaming protocol determines that the UE adopts local grooming; the vPCRF establishes an S9 session for the UE according to the NAI, and saves the binding relationship (NAI, PDN identifier ', hPCRF); the vPCRF terminates the session, and uses the previously established S9 session, The hPCRF sends an S9 session modification indication message, and carries the NAI, the PDN identifier, and the access information used to formulate the policy. Step S806, the hPCRF interacts with the SPR to obtain the subscription information of the UE, and according to the network policy and the uplink report. Enrolling information, etc., formulating a PCC rule and an event trigger, and transmitting the confirmation message to the vPCRF through the S9 session modification; Step S807, the vPCRF extracts the QoS rule from the PCC rule, and then Modifying QoS rules and event triggers according to the local policy, sending a confirmation message to the BBERF through the gateway control session establishment; BBERF installing QoS rules and event triggers; Step S808, S-GW or trusted non-3GPP access gateway sending to the P-GW Establishing an IP-CAN session request message, and carrying the NAI and PDN identifiers therein; the setup IP-CAN session request message is a proxy binding update request message during implementation; after the P-GW receives the message, according to the NAI, The PDN identifies 'assigning an IP address to the UE' and establishes a binding cache entry; wherein, step S808 can be performed simultaneously with step S802; step S809, the PCEF residing at the P-GW sends an IP-CAN session establishment indication message to the vDRA, The message carries the NAI, the PDN identifies 'and the IP address'; Step S810, the vDRA determines that the PCRF has been selected for the UE according to the NAI, finds the binding relationship (NAI, PDN identifier ', vPCRF address), and updates to (NAI) , PDN identifier ', IP address', vPCRF address). The vDRA returns a redirect message to the PCEF, where the message carries the vPCRF address selected by the vDRA. This vPCRF is the vPCRF selected for the first IP-CAN session; Step S811, the PCEF obtains the vPCRF address, and sends an "IP-CAN Session Establishment Indication" message to the vPCRF, where the message carries the identifier of the UE, the PDN identifier, the IP address, and the access information used to formulate the policy. S812, after receiving the request message, the vPCRF sends an S9 session modification indication request message to the hDRA, where the message carries the NAI, the PDN identifier 'and the IP address'; the S9 session modification indication request message may be a Diameter CCR message in the implementation process, where the CC - The Request-Type AVP is set to "UPDATE_REQUEST"; the vPCRF may also use a custom specific message to notify the hDRA UE of the IP address '; wherein the above IP address 'is an IPv4 and/or IPv6 address, carrying the IP in the message The address ', in fact implicitly indicating that the DRA adds the IP address in the binding relationship', may of course adopt an explicit indication carrying the additional force p; in step S813, hDRA determines that the PCRF has been selected for the UE according to the NAI. And find the binding relationship (NAI, PDN identifier, hPCRF address) and update to (NAI, PDN identifier ', IP address', hPCRF address) according to the NAI and PDN identifiers; hDRA returns a redirect message to the vPCRF And carrying the address of the hPCRF; the hPCRF is the hPCRF selected by the first IP-CAN session; step S814, the vPCRF determines that the S9 session has been established for the UE according to the NAI, and then finds the NII and PDN identifiers. The binding relationship (NAI, PDN identifier ', hPCRF address) is updated to (NAI, PDN identifier ', IP address', hPCRF address). The vPCRF sends an S9 session tampering indication message to the hPCRF, and carries the NAI, the PDN identifies the ', the IP address', and the access information for formulating the policy, etc., wherein the step S814 may be in parallel with the step S812, or may be received. The message of step S813 is sent again; in step S815, the hPCRF may change the previous PCC rule and the event trigger according to the new information, and send the confirmation message to the vPCRF through the S9 session modification; Step S816, if an update occurs, the vPCRF is updated. PCC rules and event triggers; vPCRF returns IP-CAN session establishment confirmation message to PCEF, and carries PCC rules and event triggers therein; PCEF installs PCC rules and event triggers; wherein, if vPCRF extracts QoS from PCC rules The rule and event triggers have changed with the previous delivery, and the vPCRF also sends the QoS rules and event triggers before the message update to the BBERF. Step S817, the PCEF returns an IP-CAN session response to the BBERF. In the implementation process, establishing an IP-CAN session response may be an agent binding update confirmation message; the message does not have to wait for the confirmation message of step S816; Step S818, BBERF returns to establish IP-CAN session response. It should be noted that when the home AF is to provide service information to the second IP-CAN session, the hAF will send an application/service information message to the hDRA, where the message carries the IP address of the UE, and the hDRA is based on the IP address. The address 'find the binding relationship, and returns the hPCRF selected for the IP-CAN session to the hAF. The hAF then sends an application/service information message to the hPCRF to establish an AF session, and the service information is provided through the session. In the above embodiment, the DRA selection PCRF is Per UE, and the binding relationship saved by the DRA is Per UE. Embodiment 5 This embodiment describes a procedure in which the UE uses the DSMHV6 protocol to access the EPC to establish a first IP-CAN session, and then decides to access another PDN and establish a second IP-CAN session. The P-GW of the second IP-CAN session is still in the visited place, and the P-GW may be the same or different from the P-GW of the first IP-CAN session. FIG. 9 is a flowchart of a method for providing an IP address of a UE according to Embodiment 5 of the present invention. As shown in FIG. 9, the method includes the following steps: Step S901: The UE determines to access another PDN, and establishes security with the selected P-GW. In the process, the P-GW will allocate a new IP address for the UE to establish an IP-CAN session; then the UE sends an IP-CAN session request message to the P-GW and carries the NAI in it. , CoA, IP address 'and PDN identifier'; the message may be a binding update request message during implementation; after receiving the message, the P-GW establishes the NAI, PDN identifier ', CoA and IP address' Binding the cache entry; Step S902, the PCEF residing at the P-GW sends an IP-CAN session establishment indication message to the vDRA, and carries the NAI, CoA, PDN identifier 'and IP address'therein; Step S903, vDRA The NAI judges that the PCRF has been selected for the UE, and then establishes a binding relationship (NAI, CoA, PDN identifier ', IP address', vPCRF address) according to the PDN identifier 'and IP address'; vDRA returns a redirect message to the PCEF And carrying the vPCRF address selected by vDRA; the vPCRF is the first IP-CAN Word selected vPCRF; Step S904, the PCEF acquires a vPCRF address, and sends a 'ΊΡ-CAN Session Establishment Indication" message to the vPCRF, and carries therein the identifier of the UE, the CoA, the PDN identifier ', the IP address', and the access information used to formulate the policy. Step S905, after receiving the request message, the vPCRF sends an S9 session modification indication request message to the hDRA, and carries the NAI, CoA, PDN identifier 'and IP address'therein; the S9 session repair_revision request message is implemented. The process may be a Diameter CCR message, where the CC-Request-Type AVP is set to "UPDATE_REQUEST"; wherein the vPCRF may also notify the hDRA UE's IP address by using a customized specific message; wherein the above IP address 'is IPv4 and And the IPv6 address, in the message carrying the IP address ', in fact implicitly indicating that the DRA adds the IP address in the binding relationship', of course, an explicit indication carrying the address can be used; step S906, hDRA has selected the PCRF for the UE according to the NAI judgment, and establishes a binding relationship according to the IP address 'and the PDN identifier' (NAI, CoA, PDN identifier ', IP address', hPCRF address); hDRA direction vPCRF Returning the redirect message, and carrying the address of the hPCRF; the hPCRF is the hPCRF selected by the first IP-CAN session; Step S907, the vPCRF determines that the S9 session has been established for the UE according to the NAI, and then
PDN标识'和 IP地址'建立绑定关系为 (NAI、 CoA、 PDN标识'、 IP地址'、 hPCRF地址), vPCRF向 hPCRF发送 S9会话 4爹改指示消息,并其中携带 NAI、 CoA、 PDN标识'、 IP地址'和用于制定策略的接入信息等; 其中, 步骤 S907可以和步骤 S905并行, 也可以等接收到 906步的消 息后再发送; 步骤 S908 , hPCRF可能才艮据新的信息更改之前的 PCC规则和事件触发 器 , 并通过 S9会话修改确认消息发送给 vPCRF; 步骤 S909,若发生更新,则 vPCRF更新 PCC规则和事件触发器; vPCRF 向 PCEF返回 IP-CAN会话建立确认消息, 并在其中携带 PCC规则和事件触 发器; PCEF安装 PCC规则和事件触发器; 步骤 S910 , 若 vPCRF从 PCC规则中抽取的 QoS规则和事件触发器与 之前下发的发生了变化, 贝1 J vPCR向 BBERF发送网关控制和 QoS规则提供 消息更新之前的 QoS规则和事件触发器; 步骤 S911 , BBERF更新 QoS规则和事件触发器, 返回确认消息; 步骤 S912, PCEF向 UE返回建立 IP-CAN会话应答, 在实施过程中 , 建立 IP-CAN会话应答可以为绑定更新确认消息, 该消息由步骤 S909触发。 当归属地 AF要向第二个 IP-CAN会话提供业务信息时 , hAF将向 hDRA 发送应用 /业务信息消息, 该消息中携带有 UE的 IP地址 ' , hDRA 居 IP地 址'找到绑定关系, 从而向 hAF返回为该 IP-CAN会话选择的 hPCRF; hAF 再向 hPCRF发送应用 /业务信息消息, 建立 AF会话, 通过该会话提供业务 信息。 在上述实施例中, DRA选择 PCRF是 Per UE的, DRA保存的绑定关 系是 Per UE的。 当 UE采用实施例四或实施例五建立两个 IP-CAN会话后, 若 UE决定 断开其中的一个, 那么 vPCRF也要向 hDRA发送 Diameter会话爹改请求消 息或特定消息来通知 hDRA某个 IP-CAN会话终结, 其中, 上述消息中携带 有要终结 IP-CAN会话的 IP地址和终结指示。 系统实施例 才艮据本发明的实施例, 提供了一种 Diameter 路由代理, 优选地, 该The PDN identifier 'and the IP address' establishes a binding relationship (NAI, CoA, PDN identifier, IP address, and hPCRF address), and the vPCRF sends an S9 session 4 tampering indication message to the hPCRF, and carries the NAI, CoA, and PDN identifiers. ', IP address' and the access information for formulating the policy, etc.; wherein, step S907 may be in parallel with step S905, or may be sent after receiving the message of step 906; step S908, hPCRF may only report the new information The previous PCC rules and event triggers are changed, and sent to the vPCRF through the S9 session modification confirmation message; Step S909, if an update occurs, the vPCRF updates the PCC rules and event triggers; the vPCRF returns an IP-CAN session establishment confirmation message to the PCEF, And carrying the PCC rules and event triggers therein; PCEF installs the PCC rules and event triggers; Step S910, if the QoS rules and event triggers extracted by the vPCRF from the PCC rules are changed with the previous delivery, the Bay 1 J vPCR Sending a gateway control and QoS rule to the BBERF to provide a QoS rule and an event trigger before the message is updated; Step S911, the BBERF updates the QoS rule and the event trigger, and returns an acknowledgement message; Step S912, the PCEF returns an IP-CAN session response to the UE. In the implementation process, the establishment of the IP-CAN session response may be a binding update confirmation message, and the message is triggered by step S909. When the home AF is to provide service information to the second IP-CAN session, the hAF sends an application/service information message to the hDRA, where the message carries the IP address of the UE, and the hDRA is located at the IP address to find the binding relationship. The hPCRF selected for the IP-CAN session is returned to the hAF; the hAF then sends an application/service information message to the hPCRF to establish an AF session, and the service information is provided through the session. In the above embodiment, the DRA selection PCRF is Per UE, and the binding relationship saved by the DRA is Per UE. After the UE establishes two IP-CAN sessions by using the fourth embodiment or the fifth embodiment, if the UE decides to disconnect one of the UEs, the vPCRF also sends a Diameter session tampering request message or a specific message to the hDRA to notify the hDRA of an IP address. - CAN session termination, where the above message carries an IP address and a termination indication to terminate the IP-CAN session. System Embodiments According to an embodiment of the present invention, a Diameter routing agent is provided, preferably,
Diameter路由代理用于实现上述方法实施例中的 Diameter路由代理的功能。 图 10为本发明实施例的 Diameter路由代理的结构^ I图, 如图 10所示, 该 Diameter路由代理包括: 接收模块 102和获取模块 104 , 下面将对上述结构 进行详细描述。 接收模块 102, 用于接收来自 PCC客户端的预定消息, 其中, 预定消 息携带有 IP地址信息。 获取模块 104, 连接至接收模块 102 , 用于从接收模块 102接收的预定 消息中获取 IP地址信息。 图 11 为本发明实施例的 Diameter路由代理的优选结构才11图, 如图 11 所示, Diameter路由代理还包括: 更新模块 112, 连接至获取模块 104, 用于根据获取模块 104获取的 IP 地址信息更新用于指示 IP地址与 PCRF地址的绑定关系。 发送模块 114 , 连接至更新模块 112 , 用于更新模块在完成相关操作之 后, 向 PCC客户端发送重定向消息。 以上各模块的执行功能, 可以参考上述方法实施例中的相关描述, 这里 不再赘述。 The Diameter routing agent is used to implement the function of the Diameter routing agent in the foregoing method embodiment. FIG. 10 is a schematic diagram of a structure of a Diameter routing proxy according to an embodiment of the present invention. As shown in FIG. 10, the Diameter routing proxy includes: a receiving module 102 and an obtaining module 104. The foregoing structure will be described in detail below. The receiving module 102 is configured to receive a predetermined message from the PCC client, where the predetermined message carries the IP address information. The obtaining module 104 is connected to the receiving module 102, and is configured to obtain IP address information from a predetermined message received by the receiving module 102. FIG. 11 is a schematic diagram of a preferred structure of a Diameter routing agent according to an embodiment of the present invention. As shown in FIG. 11, the Diameter routing agent further includes: an update module 112, connected to the obtaining module 104, configured to obtain an IP address according to the obtaining module 104. The information update is used to indicate the binding relationship between the IP address and the PCRF address. The sending module 114 is connected to the update module 112, and is used to update the module to complete related operations. After that, a redirect message is sent to the PCC client. For the execution functions of the above modules, refer to the related description in the foregoing method embodiments, and details are not described herein again.
PA2 实现方式的 DRA与以上所有实施例类似, 不同之处仅在于 DRA 接收到 Diameter会话爹改请求消息后, 向 PCRF转发消息, jt匕后, PCRF的 确认消息也经 DRA转发给 PCC客户端。 通过本发明的上述实施例, 采用 PCC客户端向 DRA发送携带有 IP地 址的预定消息的方法, DRA可以获取 UE的 IP地址, 并且归属地的 AF可以 正确找到归属地 PCRF , 解决了相关技术中 AF只携带 UE的 IP地址进行标 识来向 DRA发送请求消息而导致的 DRA无法正确找到 PCRF的问题, 实现 了动态策略计费控制。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布 在多个计算装置所组成的网络上, 可选地, 它们可以用计算装置可执行的程 序代码来实现, 从而, 可以将它们存储在存储装置中由计算装置来执行, 或 者将它们分别制作成各个集成电路模块, 或者将它们中的多个模块或步骤制 作成单个集成电路模块来实现。 这样, 本发明不限制于任何特定的硬件和软 件结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本 领域的技术人员来说, 本发明可以有各种更改和变化。 凡在本发明的 4青申和 原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护 范围之内。 The DRA of the PA2 implementation is similar to all the above embodiments. The only difference is that after receiving the Diameter session tampering request message, the DRA forwards the message to the PCRF. After jt匕, the PCRF acknowledgment message is also forwarded to the PCC client via the DRA. With the foregoing embodiment of the present invention, the method for sending a predetermined message carrying an IP address to the DRA by using the PCC client, the DRA can obtain the IP address of the UE, and the AF of the home location can correctly find the home PCRF, which solves the related art. The AF only carries the IP address of the UE for identification to send a request message to the DRA, and the DRA cannot correctly find the PCRF, and implements dynamic policy charging control. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or they may be Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any particular combination of hardware and software. The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Claims

权 利 要 求 书 Claim
1. 一种用户设备 IP地址提供方法, 应用于包括策略计费控制 PCC客户端、 Diameter路由代理 DRA的通信系统,且应用于用户设备与分组数据网建 立 IP连接接入网 IP-CAN会话之后 , 其特征在于 , 所述方法包括: A user equipment IP address providing method, which is applied to a communication system including a policy charging control PCC client and a Diameter routing agent DRA, and is applied after the user equipment establishes an IP connection access network IP-CAN session with the packet data network. The method includes:
所述 PCC客户端向所述 DRA发送预定消息,并在其中携带用户设 备的 IP地址。  The PCC client sends a predetermined message to the DRA and carries the IP address of the user equipment therein.
2. 根据权利要求 1所述的方法, 其特征在于, 所述 PCC客户端包括以下之 一: 策略和计费规则功能实体 PCEF、 策略和计费规则功能实体 PCRF。 The method according to claim 1, wherein the PCC client comprises one of the following: a policy and charging rule function entity PCEF, a policy and a charging rule function entity PCRF.
3. 根据权利要求 1所述的方法, 其特征在于, 所述预定消息包括以下之一: Diameter会话 4爹丈请求消息、 用于传输所述 IP地址和 /或 IP地址操作信 息的专用消息, 其中, 所述 Diameter会话修改请求消息包括以下之一: IP-CAN会话 4爹改指示消息、 S9会话修 _?丈指示消息。 3. The method according to claim 1, wherein the predetermined message comprises one of: a Diameter session, a request message, a dedicated message for transmitting the IP address and/or IP address operation information, The Diameter session modification request message includes one of the following: an IP-CAN session 4 tampering indication message, and an S9 session repairing_? Zhang instructions message.
4. 才艮据权利要求 3所述的方法, 其特征在于, 所述 Diameter会话 4爹改请求 消息包括 Diameter信用控制请求消息, 其中, 所述 Diameter信用控制请 求消息中的信用控制请求类型的属性值对设置为"更新请求"。 4. The method according to claim 3, wherein the Diameter Session 4 tampering request message comprises a Diameter Credit Control Request message, wherein an attribute of the credit control request type in the Diameter Credit Control Request message The value pair is set to "Update Request".
5. 才艮据权利要求 1所述的方法 ,其特征在于,所述 PCC客户端向所述 DRA 发送预定消息之后, 所述方法还包括: The method according to claim 1, wherein after the PCC client sends the predetermined message to the DRA, the method further includes:
所述 DRA接收所述预定消息并从中获取所述 IP地址; 所述 DRA才艮据所述 IP地址更新所述用户终端或 IP-CAN会话与 PCRF地址的绑定关系,并向所述 PCC客户端返回重定向消息或向 PCRF 转发所述预定消息。  Receiving, by the DRA, the predetermined message and obtaining the IP address from the network address; the DRA updates the binding relationship between the user terminal or the IP-CAN session and the PCRF address according to the IP address, and sends the binding relationship to the PCRF address to the PCC client. The terminal returns a redirect message or forwards the predetermined message to the PCRF.
6. 根据权利要求 1所述的方法, 其特征在于, 所述预定消息中还携带有指 示对用户终端或 IP-CAN会话与 PCRF地址的绑定关系执行添加或删除 所述 IP地址操作的指示信息。 The method according to claim 1, wherein the predetermined message further carries an indication that the binding of the user terminal or the IP-CAN session and the PCRF address is performed to perform an operation of adding or deleting the IP address. information.
7. 根据权利要求 6所述的方法,其特征在于,所述 PCC客户端向所述 DRA 发送预定消息之后, 所述方法还包括: The method according to claim 6, wherein after the PCC client sends a predetermined message to the DRA, the method further includes:
所述 DRA接收所述预定消息并从中获取所述 IP地址; 所述 DRA才艮据所述 IP地址和所述指示信息将所述 IP地址添力口到 所述绑定关系或从所述绑定关系中将所述 IP地址删除, 并向所述 PCC 客户端返回重定向消息或向 PCRF转发所述预定消息。 Receiving, by the DRA, the predetermined message and obtaining the IP address therefrom; And the DRA adds the IP address to the binding relationship according to the IP address and the indication information, or deletes the IP address from the binding relationship, and sends the IP address to the PCC client. The terminal returns a redirect message or forwards the predetermined message to the PCRF.
8. 一种 Diameter路由代理, 其特征在于, 包括: 8. A Diameter routing agent, comprising:
接收模块, 用于接收来自 PCC客户端的预定消息, 其中, 所述预 定消息携带有 IP地址信息;  a receiving module, configured to receive a predetermined message from a PCC client, where the predetermined message carries IP address information;
获取模块,用于从所述接收模块接收的所述预定消息中获取所述 IP 地址信息。  And an obtaining module, configured to obtain the IP address information from the predetermined message received by the receiving module.
9. 才艮据权利要求 8所述的 Diameter路由代理, 其特征在于, 还包括: 9. The Diameter routing agent according to claim 8, further comprising:
更新模块, 用于才艮据所述获取模块获取的所述 IP地址信息更新用 户终端或 IP-CAN会话与 PCRF地址的绑定关系;  And an update module, configured to update a binding relationship between the user terminal or the IP-CAN session and the PCRF address according to the IP address information obtained by the obtaining module;
发送模块 , 用于向所述 PCC客户端发送重定向消息或向 PCRF转 发所述预定消息。  And a sending module, configured to send a redirect message to the PCC client or forward the predetermined message to the PCRF.
PCT/CN2009/071555 2008-09-23 2009-04-29 Method for providing ip address of user equipment, diameter routing agent WO2010034195A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810161357.2 2008-09-23
CN2008101613572A CN101583114B (en) 2008-09-23 2008-09-23 Providing method of user equipment (UE) IP address and Diameter routing agent

Publications (1)

Publication Number Publication Date
WO2010034195A1 true WO2010034195A1 (en) 2010-04-01

Family

ID=41365015

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/071555 WO2010034195A1 (en) 2008-09-23 2009-04-29 Method for providing ip address of user equipment, diameter routing agent

Country Status (2)

Country Link
CN (1) CN101583114B (en)
WO (1) WO2010034195A1 (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013056368A1 (en) * 2011-10-18 2013-04-25 Alcatel Lucent Pcrn roaming agreement
WO2013056369A1 (en) * 2011-10-18 2013-04-25 Alcatel Lucent Roaming session termination triggered by roaming agreement/partner deletion
CN107306391A (en) * 2016-04-18 2017-10-31 中国移动通信有限公司研究院 A kind of network address assignment method, device and gateway device
CN107409067A (en) * 2015-02-03 2017-11-28 思科技术公司 The system and method for discovery strategy charging and rule functional (PCRF) in a network environment

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8305922B2 (en) * 2010-02-18 2012-11-06 Alcatel Lucent Method for PCRF to autonomously respond to cell capacity shortage
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
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
CN102638867B (en) * 2011-02-14 2018-01-02 中兴通讯股份有限公司 The processing method and system of secondary call access control
CN102694841A (en) * 2011-03-21 2012-09-26 中兴通讯股份有限公司 Method and system for deleting binding information in Diameter routing agent
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
CN104486841B (en) * 2014-11-20 2019-08-16 大唐移动通信设备有限公司 A kind of policy control rules function server and its message forwarding method
WO2018085994A1 (en) 2016-11-08 2018-05-17 华为技术有限公司 Integrated controller selection method, device and system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217383A (en) * 2008-01-04 2008-07-09 中兴通讯股份有限公司 A deletion method of functional association relation of strategy and charging rules
CN101217810A (en) * 2008-01-16 2008-07-09 中兴通讯股份有限公司 A selecting method of strategy and charging rule functions
CN101227352A (en) * 2007-01-15 2008-07-23 华为技术有限公司 System and method for accessing network of subscriber terminal emergently to login IP connection

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101150418B (en) * 2007-10-17 2011-01-05 中兴通讯股份有限公司 A selection method for policy billing control server
CN101150782B (en) * 2007-10-17 2012-04-18 中兴通讯股份有限公司 A selection method for policy billing control server
CN101198171B (en) * 2007-12-27 2011-09-21 中兴通讯股份有限公司 Routing method for strategy charging control information in roaming scene
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

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101227352A (en) * 2007-01-15 2008-07-23 华为技术有限公司 System and method for accessing network of subscriber terminal emergently to login IP connection
CN101217383A (en) * 2008-01-04 2008-07-09 中兴通讯股份有限公司 A deletion method of functional association relation of strategy and charging rules
CN101217810A (en) * 2008-01-16 2008-07-09 中兴通讯股份有限公司 A selecting method of strategy and charging rule functions

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Policy and Charging Control signalling flows and QoS; parameter mapping (Release 8) 3GPP TS 29.213 V8.2.0.", 3RD GENERATION PARTNERSHIP PROJECT; TECHNICAL SPECIFICATION GROUP CORE NETWORK AND TERMINALS, December 2008 (2008-12-01) *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013056368A1 (en) * 2011-10-18 2013-04-25 Alcatel Lucent Pcrn roaming agreement
WO2013056369A1 (en) * 2011-10-18 2013-04-25 Alcatel Lucent Roaming session termination triggered by roaming agreement/partner deletion
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
EP2769581A4 (en) * 2011-10-18 2015-06-10 Alcatel Lucent Roaming session termination triggered by roaming agreement/partner deletion
CN107409067A (en) * 2015-02-03 2017-11-28 思科技术公司 The system and method for discovery strategy charging and rule functional (PCRF) in a network environment
CN107306391A (en) * 2016-04-18 2017-10-31 中国移动通信有限公司研究院 A kind of network address assignment method, device and gateway device

Also Published As

Publication number Publication date
CN101583114A (en) 2009-11-18
CN101583114B (en) 2011-09-21

Similar Documents

Publication Publication Date Title
WO2010034195A1 (en) Method for providing ip address of user equipment, diameter routing agent
EP2458913B1 (en) Reselection system for bearer binding and event reporting function and method thereof
US9137652B2 (en) Method for implementing policy and charging control in a roaming scene
US8799440B2 (en) Policy and charging control method and system for multi-PDN connections of single APN
JP5499170B2 (en) Billing system and billing method
US9351325B2 (en) Policy control method and system for converged network
US8326263B2 (en) Method for selecting policy and charging rules function
US8793396B2 (en) Method for deleting session information in DRA
US8943165B2 (en) Method for reselecting bearer binding and event report function
US20110161504A1 (en) Method and apparatus for identifying session information
US20110099604A1 (en) Access control method and system for packet data network, pcrf entity
US8463889B2 (en) Method for provisioning and installing event triggers
WO2011029289A1 (en) Method and system for transmitting a bearer control mode in roaming scenarios
WO2016201999A1 (en) Third-party application charging method and apparatus, and application function device
WO2011018020A1 (en) Method and system for controlling load balance of pcrf, and redirect dra
CN102791042B (en) Method and system for establishing S9 subsession and policy and charging rules function (PCRF)
WO2013178183A1 (en) Quality of service update processing method and device
WO2013113263A1 (en) Method and system for identifying application detection control function mode
WO2011134315A1 (en) Method, device and system for service authorization
WO2011029349A1 (en) Method and system for processing multiple bearer binding and event report functions
EP2323340B1 (en) Method and apparatus for identifying session information
WO2013020451A1 (en) Session establishment method and system
WO2017084603A1 (en) Method and device for processing pcc rule
WO2011035644A1 (en) Method and system for acquiring serving general packet radio service support node address

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09815565

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09815565

Country of ref document: EP

Kind code of ref document: A1