WO2012126311A1

WO2012126311A1 - Method and system for creating and deleting binding information in diameter routing agent, h-pcrf

Info

Publication number: WO2012126311A1
Application number: PCT/CN2012/071637
Authority: WO
Inventors: 周晓云; 毕以峰
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-03-21
Filing date: 2012-02-24
Publication date: 2012-09-27
Also published as: CN102694841A

Abstract

Disclosed is a method for creating and deleting binding information in a Diameter routing agent (DRA). The method for deleting the DRA binding information comprises: when a first policy server terminates a first policy control session with a second policy server, the first policy server notifies the DRA to delete from the DRA binding the associative relationship with the message of the second policy server, said message having been triggered by the first policy server to establish the first policy control session. The present invention also comprises a system to execute the method for creating and deleting binding information in the DRA, and an H-PCRF. The present invention helps to complement the current protocol, defining creation and deletion mechanisms for policy control sessions, and ensuring that the UE can easily access an EPS via a BBF access network.

Description

Method and system for creating and deleting binding information in a Diameter routing agent,

H-PCRF Technical Field

The invention relates to a technology for creating and deleting binding information in a Diameter Routing Agent (DRA), and particularly relates to a user equipment (UE, User Equipment) accessing a network through a broadband forum (BBF, Broadband Forum). A method and system for creating and deleting binding information in a DRA when accessing a network of an evolved packet system (EPS, Evolved Packet System), H-PCRF. Background technique

FIG. 1 is a schematic structural diagram of an evolved packet system in a non-roaming scenario, as shown in FIG.

The EPS is evolved by the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), the Mobility Management Entity (MME), and the S-GW (Serving Gateway). Packet data network gateway (P-GW or PDN GW, Packet Data Network Gateway), Home Subscriber Server (HSS), Policy and Charging Rules Function (PCRF) and other supporting nodes The PCRF is the core of Policy and Charging Control (PCC) and is responsible for policy decision making and charging rules. The PCRF provides network control rules based on service data flows. The network control includes detection of service data flows, Gating Control, Quality of Service (QoS) control, and data flow based charging. The PCRF sends its policy and charging rules to the Policy Charging Enforcement Function (PCEF), and the PCRF also needs to ensure that these rules are consistent with the user's subscription information. The basis for the PCRF to formulate policies and charging rules includes: From Application Function (AF, Application Function) Obtaining information related to the service; obtaining subscription information with the user policy charging control from the SPR (Spread Profile Repository); obtaining information about the network related to the bearer from the PCEF.

EPS supports interworking with non-3GPP systems. Interworking with non-3GPP systems is implemented through the S2a/S2b/S2c interface, which acts as an anchor between 3GPP and non-3GPP systems. As shown in FIG. 1, where the non-3GPP system is divided into trusted non-3GPP IP access and untrusted non-3GPP IP access, the trusted non-3GPP IP access can be directly connected to the P-GW through the S2a interface; The 3GPP IP access is connected to the P-GW through an Evolved Packet Data Gateway (ePDG). The interface between the ePDG and the P-GW is S2b, and IPSec is used between the UE and the ePDG to perform signaling and data. Encryption protection. S2c provides user plane-related control and mobility support between the user equipment (UE, User Equipment) and the P-GW. The supported mobility management protocol is dual-stack mobile IPv6 (DSMIPv6, Moblie IPv6 support for dual). Stack Hosts and Routers ).

At present, many operators pay attention to Fixed Mobile Convergence (FMC) and conduct research on interconnection between 3GPP and Broadband Forum (BBF). For the user to access the mobile core network through the BBF access network (also known as the Fixed Broadband Access Network), the QoS on the entire transmission path of the data (data will pass through the fixed network and the mobile network) Make a guarantee. Currently, two scenarios of BBF access and 3GPP interoperability are mainly studied.

2 is a schematic diagram of a UE accessing an EPS core network through a wireless local area network (WLAN). As shown in FIG. 2, the BBF access network serves as an untrusted non-3GPP access network, and when the UE accesses the BBF access, After the network, the Broadband Access Server (BRAS)/Broadband Network Access Gateway (BNG, Broadband Network Gateway) will perform 3GPP-based access authentication, while the BPF of the BBF actively initiates the S9* session and the 3GPP PCRF. Interact. Therefore, the PCRF can communicate with the broadband policy when performing QoS authorization. The BPCF (Broadband Policy Control Function) interacts and the BPCF performs resource admission control.

However, in some scenarios, the BBF access network does not always be aware of UE access or the BBF access network does not support 3GPP-based access authentication. In this scenario, BPCF will not be able to initiate the establishment of an S9* session, and thus cannot implement QoS control for UE access. At this point, the session establishment process can only be initiated by the PCRF to BPCF.

FIG. 3 is a schematic diagram of an architecture of a core network in which an H (e)NB accesses an EPS through a BBF access network. As shown in FIG. 3, when a 3GPP UE accesses a 3GPP core network to access a service through a HeNB, the required QoS cannot be More than the QoS that the BBF access network can provide. Since the 3GPP UE is inaccessible to the BBF access network through the H(e)NB access, the session establishment procedure can only be initiated to the BPCF by the H(e)NB Policy Function.

FIG. 4 is a schematic diagram of another architecture of the core network where the H(e)NB accesses the EPS through the BBF access network. As shown in FIG. 4, when the 3GPP UE accesses the 3GPP core network to access the service through the HeNB, the required QoS is required. It cannot exceed the QoS that the BBF access network can provide. Since the 3GPP UE access to the BBF access network through the H(e)NB access is imperceptible, the session establishment procedure can only be initiated by the PCRF to the BPCF.

For the roaming scenario of the two access architectures shown in FIG. 2 and FIG. 4, since the BBF access network cannot perceive the access of the 3GPP UE, the PCRF may be required to be visited by the home PCRF (ie, H-PCRF). (ie, V-PCRF) triggers the establishment of an S9* session, which in turn triggers the establishment of an S9* session by the V-PCRF.

In addition, there are multiple PCRF nodes in a public land mobile phone network (PLMN) of the EPS, and all PCRF nodes belong to one or more Diameter (PCRF) domains, in the same Diameter (PCRF) domain. All PCRFs have the same capabilities. A UE-to-packet data network (PDN, Packet Data Network) connection is called an IP-Connected Access Network (IP-CAN) session. The PCC policy for an IP-CAN session is determined by only one PCRF. 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 logical function module-DRA in each Diameter (PCRF) domain. 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 a network that can uniquely identify this IP-CAN session-related information and the corresponding PCRF identity or IP address, identifying the IP-CAN session with the UE. The access identifier (NAI, Network Access Identifier), the IP address of the UE, and the access point name (APN, Access Point Name) of the UE to access the PDN. When the PCEF, BBERF, and AF of the same IP-CAN session establish this information to the DRA when establishing a Diameter session with the PCRF, the DRA searches for the saved information and selects the same PCRF for it. The information of the Diameter session established by the PCEF, the BBERF, or the AF and the PCRF may be saved in the DRA, such as the session identifier of the established Diameter session. This allows the DRA to know which Diameter session it manages for the IP-CAN session. When the Diameter session established by the PCEF, BBERF or AF and the PCRF is deleted, the PCEF, BBERF or AF informs the DRA to delete the Diameter, and the DRA can delete the information of the Diameter session (such as the session identifier). When the DRA deletes all Diameter sessions managed by an IP-CAN session, the DRA deletes all information for that IP-CAN session. In addition, depending on the configuration, the DRA can also select the same PCRF for one UE.

Similarly, for a BBF access network, there may be multiple BPCF nodes, and all BPCF nodes belong to one or more Diameter (BPCF) domains, and may also introduce DRA and utilize DRA as an IP-CAN session or a UE. Choose a BPCF. Currently, there are three ways to implement DRA. (1) Redirect mode. When the PCEF, BBERF, and AF send a Diameter Session Establishment Request message to the PCRF, the Diameter Session Establishment Request 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. The identity or address of the selected PCRF is returned to the sender. If the IP-CAN session related information already exists in the DAR, the DRA returns the identifier or address of the corresponding PCRF to the sender. After the sender obtains the address or identifier of the PCRF, it sends a Diameter Session Establishment Request message to the selected PCRF. (2) Proxy mode. When the PCEF, BBERF, and AF send a Diameter Session Establishment Request message to the PCRF, the Diameter Session Establishment Request 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 Diameter Session Setup Request message to the selected PCRF. If the IP-CAN session related information already exists in the DAR, the DRA forwards the Diameter session establishment request to the corresponding PCRF. The acknowledgment message of the PCRF is also forwarded to the PCEF, BBERF or AF via the DRA. (3) Deformation of the Proxy mode. Similar to the Proxy mode, the difference is that the DRA sends the PCRF address to the PCEF, BBERF or AF when forwarding the acknowledgment message returned by the PCRF. In this way, in subsequent message interactions, PCEF, BBERF or AF can interact directly with the PCRF without going through the DRA.

For mode (2), whether the message created by the first session or the subsequent message is DRA, when the Diameter session is to be terminated, the DRA can analyze the indication of the terminating session in the message, thereby deleting the session in the DRA. Information. For mode (3), when the Diameter session is to be terminated, the client only needs to send the termination message to the DRA first, and then forward it to the PCEF by the DRA. How to use DRA when the H-PCRF needs to trigger the V-PCRF to establish an S9* session, or the PCRF triggers the BPCF to establish an S9* session, and the H(e)NB PCRF triggers the BPCF to establish an S9* session (for the H-PCRF trigger V-PCRF) Establishing an S9* session scenario, the DRA is located in the VPLMN, and the PCRF/H (e) NB PCRF triggers the BPCF to establish an S9* session. The scenario, the DRA is located in the BBF network) Selecting the same V-PCRF or BPCF for an IP-CAN session or a UE and how to create binding information in the DRA remains to be solved. At the same time, when the IP-CAN session is terminated or the UE is detached, how to delete the binding information in the DRA is still a problem to be solved. Summary of the invention

In view of this, the main purpose of the present invention is to provide a method and system for creating and deleting binding information in a Diameter routing proxy, and an H-PCRF, which is to specify that a PCRF triggers a BPCF establishment when a UE accesses an EPS system through a BBF access network. The policy controls the session and how to delete the binding information about the policy control session in the DRA after deleting the policy control session.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

A method for deleting binding information in a Diameter routing agent, including:

When the first policy server terminates the first policy control session with the second policy server, the first policy server notifies the DRA to delete the DRA binding, and the first policy server triggers the second policy server to establish the The first policy controls the association of messages of the session.

Preferably, after the DRA receives the notification that the association relationship between the DRA binding and the first policy server triggers the second policy server to establish the first policy control session, the method further Includes:

And the DRA deletes an association relationship between the DRA binding and the message that the first policy server triggers the second policy server to establish the first policy control session.

Preferably, after the DRA deletes the association relationship between the DRA binding and the message that the first policy server triggers the second policy server to establish the first policy control session, the method further includes:

If the DRA binding is per IP-CAN session, and all policy control sessions of the IP-CAN session are terminated, the DRA deletes the DRA binding associated with the IP-CAN; or, if the DRA binding is per UE's, and all policy control sessions of the UE are terminated, The DRA deletes the DRA binding associated with the UE.

Preferably, before the first policy server terminates the first policy control session with the second policy server, the method further includes:

The first policy server sends the trigger message to the second policy server, and triggers the second policy server to create a first policy control session.

Preferably, the first policy server sends the trigger message to the second policy server, and the second policy server is triggered to create the first policy control session, specifically:

When the first policy server receives the triggering of the first policy control session between the creation and the second policy server, notifying the DRA that the DRA is saved in the DRA binding and triggering the first policy server Establishing, by the second policy server, an association relationship of the message of the first policy control session;

The first policy server notifies the second policy server to create a first policy control session by using the trigger message;

When the first policy server terminates the first policy control session with the second policy server, the DRA is notified to delete the DRA binding, and the first policy server triggers the second policy server to establish the first The relationship of the policy control session messages is:

Notifying the second policy server to terminate the first policy control session when the first policy server receives the triggering of the first policy control session between the termination and the second policy server;

After the first policy control session is terminated, the first policy server notifies the DRA to delete the message that the first policy control session is established with the second policy server of the first policy server trigger in the DRA binding. Relationship.

Preferably, the first policy server is a policy and charging rule function PCRF, and the second policy server is a broadband policy control function BPCF;

Or the first policy server is an H-PCRF, and the second policy server is a V-PCRF. A method for deleting binding information in a Diameter routing agent, including:

When the H-PCRF and the V-PCRF terminate the S9 session, the H-PCRF notifies the visited Diameter routing agent V-DRA to delete the DRA binding; or,

When the H-PCRF and the V-PCRF terminate all the H-PCRFs in the S9 session requesting the sub-session created by the V-PCRF, the H-PCRF notifies the V-DRA to delete the DRA binding and the H - The PCRF triggers the V-PCRF to establish an association relationship of the messages of the S9 session.

Preferably, the H-PCRF carries the same session identifier and/or the message in the message that the H-PCRF triggers the V-PCRF to establish the S9 session in the message that the V-DRA deletes the DRA binding. Request to establish session identification information; or,

And in the message that the H-PCRF is associated with the message that the H-PCRF triggers the V-PCRF to establish the S9 session, and the H-PCRF is carried in the message that the V-DRA is deleted in the DRA binding. The PCRF triggers the V-PCRF to establish the same session identifier in the message of the S9 session and/or request to establish session identification information.

Preferably, the request to establish the session identification information is location information of the user equipment UE accessing the broadband forum BBF access network, or the uniquely distinguishable identifier allocated by the H-PCRF, or the user identifier, or the The local IP address of the UE, or the user ID and PDN ID.

A system for deleting binding information in a Diameter routing agent is applied to a network that accesses an EPS through a BBF access network, where the system includes a first policy server, a second policy server, and a DRA, where:

a first policy server, configured to: when the first policy server terminates the first policy control session with the second policy server, notify the Diameter routing agent that the DRA deletes the DRA binding and the first policy server triggers the The second policy server establishes an association relationship of messages of the first policy control session.

Preferably, the DRA receives an association relationship between the message in the deleted DRA binding and the message that the first policy server triggers the second policy server to establish the first policy control session. After the notification, the DRA deletes the association relationship between the DRA binding and the message that the first policy server triggers the second policy server to establish the first policy control session.

Preferably, after the DRA deletes the association relationship between the DRA binding and the message that the first policy server triggers the second policy server to establish the first policy control session, the system further includes:

If the DRA binding is per IP-CAN session, and all policy control sessions of the IP-CAN session are terminated, the DRA is further used to delete the DRA binding associated with the IP-CAN; or

If the DRA binding is per UE, and all policy control sessions of the UE are terminated, the DRA is further used to delete the DRA binding associated with the UE.

Preferably, before the first policy server terminates the first policy control session with the second policy server,

The first policy server is further configured to: send the trigger message to the second server, and notify the second policy server to create a first policy control session.

Preferably, the first policy server is further configured to notify the DRA to save in the DRA binding when the first policy control session trigger between the creation and the second policy server is received. The first policy server triggers an association relationship between the message that the second policy server establishes the first policy control session;

After the first policy control session is terminated, the first policy server is further configured to notify the DRA to delete the DRA binding, and the first policy server triggers the second policy server to establish the first policy control. The association of the messages of the session.

Preferably, the first policy server is a PCRF, and the second policy server is a BPCF; or the first policy server is an H-PCRF, and the second policy server is a V-PCRF.

A system for deleting binding information in a Diameter routing agent, applied to access through BBF In the network where the network accesses the EPS, the system includes an H-PCRF and a V-PCRF, where:

An H-PCRF, configured to: when the H-PCRF terminates the S9 session with the V-PCRF,

H-PCRF notification visit Diameter routing agent V-DRA delete DRA binding; or,

When the H-PCRF and the V-PCRF terminate all the H-PCRFs in the S9 session requesting the V-PCRF to create a sub-session, the H-PCRF notifies the V-DRA to delete the

The association relationship between the DRA binding and the message that the H-PCRF triggers the V-PCRF to establish the S9 session.

A method for creating binding information in a Diameter routing agent, including:

The first policy server sends a trigger message to the DRA when receiving the triggering of the first policy control session between the second policy server and the second policy server;

After the DRA creates or updates the DRA binding, the association between the DRA binding and the trigger message is saved in the DRA binding.

After receiving the trigger message, the second policy server sends a request message to the first policy server to request to establish the first policy control session.

Preferably, the trigger message carries a session identifier or carries an indication that the session state is not maintained. An H-PCRF, configured to notify the visited Diameter routing agent V-DRA to delete the DRA binding when the H-PCRF terminates the S9 session with the V-PCRF; or

Used to notify the V-DRA to delete the DRA binding and the H-PCRF when all of the H-PCRFs request the V-PCRF to create a sub-session in the H-PCRF and the V-PCRF-terminating S9 session. The association relationship of the message that triggers the V-PCRF to establish the S9 session.

In the present invention, when the BBF access network cannot perceive the UE access, the PCRF triggers the BPCF to establish a policy control session to implement policy control, and after deleting the policy control session, the related binding of the policy control session needs to be deleted in the DRA. information. The invention realizes a better supplement to the existing protocol, and clarifies the mechanism for creating and deleting the policy control session, and ensures that the UE smoothly accesses the EPS through the BBF access network. DRAWINGS

1 is a schematic structural diagram of an evolved packet system in a non-roaming scenario;

2 is a schematic diagram of a UE accessing an EPS core network through a WLAN;

FIG. 3 is a schematic structural diagram of a core network in which an H ( e ) NB accesses an EPS through a BBF access network;

FIG. 4 is another schematic diagram of the architecture of the H(e)NB accessing the EPS core network through the BBF access network;

FIG. 5 is a flowchart of creating a policy control session based on the architecture of FIG. 1 according to the present invention; FIG.

6 is a flowchart of deleting a policy control session binding information in a DRA according to the architecture of FIG. 1 according to the present invention;

7 is a flowchart of creating a policy control session based on the architecture of FIG. 1 according to the present invention;

8 is a flowchart of deleting a policy control session binding information in a DRA according to the architecture of FIG. 2 according to the present invention;

9 is a flowchart of selecting a visited PCRF by a visited DRA in a process of UE attachment or PDN connection establishment in a roaming scenario according to the present invention; 10 is a flowchart of controlling session binding information based on the deletion policy of FIG. 9 according to the present invention; FIG. 11 is an architecture based on FIG. 2 and FIG. 4 according to the present invention. In a roaming scenario, during UE attaching, V-DRA selects V- Flow chart of PCRF;

FIG. 12 is a flowchart of controlling session binding information based on the deletion policy of FIG. 11 according to the present invention. detailed description

The present invention will be further described in detail below with reference to the accompanying drawings.

Embodiment 1

FIG. 5 is a flowchart of a method for creating a policy control session based on the architecture of FIG. 1 according to the present invention. In the process of establishing a UE or a PDN connection, the DRA selects a BPCF process, where the DRA is a redirected Redirect mode, as shown in FIG. 5, The policy control session specifically includes the following steps: Step 501: The PCRF is triggered, and a policy control session with the BPCF needs to be established. The trigger may be caused by the ePDG or the P-GW sending a policy control session message to the PCRF, where the policy control session message carries indication information that the UE accesses through the WLAN. After receiving the policy control session message, the PCRF determines that a policy control session with the BPCF needs to be established to provide a policy to the BBF access network and request admission control of the BBF access network.

Step 502: The PCRF sends a Diameter session establishment request message to the DRA, where the Diameter session establishment request message carries a user identifier, a PDN identifier, and a request to establish a session indication. The PCRF fills in the domain name of the BBF access network in the Destination-Host AVP of the message. The PCRF allocates a session ID, which is ID1, to the Diameter session established by the request.

Here, the request to establish a session indication is used to notify the BPCF to initiate establishment of a policy control session. The Diameter session establishment request message may further carry a request to establish session identification information for initiating an identifier of the session as a BPCF in the future, so that the PCRF determines whether the session BPCF requested to be established has been initiated. The request to establish session identification information may be location information of the user accessing the BBF access network, or a uniquely distinguishable identifier or user identifier allocated by the PCRF, Or the local IP address of the UE (the address is the IP address obtained by the UE in the BBF network), or the user identifier and the PDN identifier.

Step 503: The DRA determines, according to the user identifier, whether a BPCF has been selected for the UE (if the DRA is configured to select one BPCF for each UE) or determines whether a BPCF has been selected for the IP-CAN session according to the user identifier and the PDN identifier (if DRA) Configure to select one BPCF per PDN for each UE. ₀ At this time, if there is no corresponding DRA binding in the DRA, the DRA selects a PCRF for the UE or the IP-CAN session, and saves the corresponding relationship (user ID, PDN). ID, BPCF ID) or (user ID, BPCF ID) or (user ID, PDN ID, UE local IP address, BPCF ID); create a DRA binding, otherwise the DRA is based on the user ID, PDN ID, and/or UE local IP. The address updates the DRA binding. At the same time, the DRA saves the Diameter session associated with the binding, where ID1 is added to the DRA binding. That is, the relationship between the DRA binding and the ID1-identified session is saved, that is, the DRA binding is saved and the BPCF is triggered to establish an S9* session message (ie, step 502, the message can be established by using the ID1 and/or the request carried in step 502. The association of the identification information unique identifier).

Step 504: The DRA returns a redirect message to the PCRF, where the message carries the identifier of the BPCF selected by the DRA in step 503.

Step 505: The PCRF sends a Diameter session establishment request message to the BPCF according to the BPCF identifier returned in step 504, where the Diameter session establishment request message carries a user identifier, a PDN identifier, and a request to establish a session indication. The PCRF fills in the BPCF identifier in the Destination-Host AVP of the message.

Step 506: After receiving the Diameter session establishment request message, the BPCF returns a Diameter session establishment response message to the PCRF.

The Diameter session established in steps 505 and 506 is referred to as an S9a session in the present invention. Step 507: The BPCF establishes a session indication according to the request in the Diameter session establishment request message, and sends a Diameter session establishment request message to the PCRF to request to establish a policy control conference. Words. The BPCF assigns a session ID to the Diameter session established by the request, and the identifier is ID2.

The Diameter session establishment request message may carry the request establishment session identifier information sent in step 505 to notify the PCRF that the message is used to establish the policy control session requested to be established in step 505.

Step 508: The PCRF sends a Diameter session establishment response message to the BPCF.

The Diameter session established in step 507 and step 508 is referred to as an S9* session in the present invention. After the PCRF can perform the policy delivery by using the policy control session established in step 507 and step 508, the BPCF can also perform the policy execution result through the PCRF. Accept the results of the control and the reporting of the incident.

The policy control session in this embodiment may specifically be a gateway control session.

In this embodiment, the Diameter session request message may adopt a credit control request message. In step 502 and step 505, which are credit control request messages, step 503 and step 506 are credit control response messages.

In this embodiment, the Diameter session request message may also be a re-authorization request message, such as an authorization authentication request (AAR, Authorize Authenticate Request) in steps 502 and 505, and steps 503 and 506 are authorization authentication responses (AAA, Authorize). Authenticate Answer ). Therefore, in this embodiment, the specific form of the Diameter session request message is not limited.

In other embodiments, the message of step 502 and step 505 may also carry an indication that the session state is not maintained (that is, the message carries the Auth-Session-State AVP, and the value is NO_STATE_MAINTAINED), or does not carry the PCRF. The session ID assigned by this Diameter session. That is, step 502 - step 506 does not establish an S9a session (after the end of the message interaction, the relevant session information is not maintained in the PCRF and the BPCF). Therefore, step 502-step 506 is only used to trigger the BPCF to initiate the establishment of the S9* session. In step 503, the DRA determines, according to the user identifier, whether BPCF has been selected for the UE (if the DRA is configured to select one for each UE) BPCF) or judging whether the BPCF has been selected for the IP-CAN session according to the user identifier and the PDN identifier (if the DRA is configured to select one BPCF per PDN per UE) ₀ At this time, if there is no corresponding DRA binding in the DRA ( That is, if the BPCF is not selected for the UE or the IP-CAN session, the DRA selects a PCRF for the UE or the IP-CAN session, and saves the correspondence (user ID, PDN identifier, BPCF identifier) or (user ID, BPCF identifier). Or (UE local address, user identity, PDN identity, BPCF identity), create a DRA binding; otherwise the DRA updates the DRA binding according to the user identity, the PDN identity, and/or the UE local IP address. Whether it is an update or a new one, the association between the DRA binding and the triggering BPCF to establish an S9* session in the DRA binding (ie, the step 502 message, the message may be uniquely identified by the request carried in step 502) relationship.

Embodiment 2

In this embodiment, according to the flow of FIG. 5, after the policy control session is established by the PCRF and the BPCF, the DRA binding process in the DRA is deleted when the IP-CAN session is terminated, and the DRA is in the redirection mode. FIG. 6 is a flowchart of deleting the policy control session binding information in the DRA according to the architecture of FIG. 2, and as shown in FIG. 6, the example deleting the policy control session binding information in the DRA includes the following steps:

Step 601: The PCRF is triggered, and the policy control session between the BPCF and the BPCF needs to be terminated, that is, the S9* session.

The trigger may be caused by the ePDG or the P-GW sending a policy control session termination message to the PCRF, where the policy control session message carries indication information that the UE accesses or disconnects the PDN connection from the WLAN access. After receiving the policy control session termination message, the PCRF determines that the policy control session with the BPCF needs to be terminated.

Step 602: The PCRF sends a request to the BPCF to terminate the Diameter session, where the session carries the request session termination indication. The message is sent through the S9* session, that is, the Session ld carried in the message is ID2. Step 603: The BPCF returns a request to the PCRF to terminate the Diameter session response.

Step 604: The BPCF sends a Diameter session termination request to the PCRF.

Step 605: The PCRF returns a Diameter session termination response to the BPCF.

Step 606: The PCRF sends a Diameter session termination request to the DRA, and the message is sent through the S9a session, where the message carries the Session Id as ID1 and/or requests to establish session identification information.

Step 607: The PCRF sends a Diameter session termination request to the BPCF, where the message carries the Session Id as ID1.

Step 608: The DRA judges that the IP-CAN session has a valid DRA binding according to Session Id = ID1, and marks the end of the Diameter session. That is, the association between the DRA binding and the ID1-identified session in the DRA binding is deleted, that is, the DRA binding in the DRA binding is deleted and the BPCF is triggered to establish an S9* session (ie, step 502, the message can be ID1 and / or request to establish an association relationship with the unique identification of the session identification information.

If the DRA binding is per IP-CAN session (ie, the DRA selects a BPCF for each IP-CAN session) and all of the IP-CAN session-related Diameter sessions are terminated (ie, the DRA binding in the DRA binding) The association relationship of all Diameter sessions related to the IP-CAN session is deleted), then the DRA will delete the DRA binding; if the DRA binding is per UE (ie, the DRA selects one BPCF for each UE session, and the UE is all The Diameter session is terminated (that is, the association between the DRA binding and all Diameter sessions related to the UE in the DRA binding is deleted), then the DRA deletes the DRA binding.

Step 609: The DRA returns a redirect message to the PCRF.

Step 610: The BPCF returns a Diameter session termination response to the PCRF.

In other embodiments, if the S9a session is not established in the flow of Figure 5 (i.e., PCRF and BPCF do not retain S9a session state information), the flow of Figure 6 can be implemented as follows:

In step 606, the PCRF also does not carry the Session id. Instead, the session identification information is established with the request in step 502. In step 608, the DRA establishes session identification information according to the request. The IP-CAN session has a valid DRA binding, and the S9* session message is set up in the DRA binding with the triggering BPCF (ie, step 502, the message can be used to establish the session identification information by using the request carried in step 502). The association of the identity). At this time, if the DRA binding is per IP-CAN session (ie, DRA selects one BPCF for each IP-CAN session) and all the IP-CAN session-related Diameter sessions are terminated (these sessions are in a hold state, all The end of the IP-CAN session-related Diameter session means that the association between the DRA binding and all the Diameter sessions associated with the IP-CAN session is deleted in the DRA binding, and the DRA deletes the DRA binding; The binding is per UE (ie, the DRA selects one BPCF for each UE) and all the Diameter sessions of the UE are terminated (these sessions are in a hold state, and all the Diameter sessions of the UE are terminated, indicating that the DRA is bound with the session identifier) The associated associations are deleted), then the DRA will delete the DRA binding. Further, steps 607 and 610 may not be performed.

Embodiment 3

In this embodiment, the DRA selects a BPCF process in the process of establishing a UE attach or a PDN connection, where the DRA is a redirected proxy mode. FIG. 7 is a flowchart of creating a policy control session based on the architecture of FIG. 2 according to the present invention. As shown in FIG. 7, creating a policy control session specifically includes the following steps: Step 701: The PCRF is triggered, and a policy control session with the BPCF needs to be established. . The trigger may be caused by the ePDG or the P-GW sending a policy control session message to the PCRF, where the policy control session message carries indication information that the UE accesses through the WLAN. After receiving the policy control session message, the PCRF determines that a policy control session with the BPCF needs to be established to provide a policy to the BBF access network and request admission control of the BBF access network.

Step 702: The PCRF sends a Diameter session establishment request message to the DRA, where the Diameter session establishment request message carries a user identifier, a PDN identifier, and a request to establish a session indication. The PCRF fills in the domain name of the BBF access network in the Destination-Host AVP of the message. The PCRF assigns a session ID to the Diameter session established by the request, and the identifier is ID1. Here, the request to establish a session indication is used to notify the BPCF to initiate establishment of a policy control session. The Diameter session establishment request message may further carry a request to establish session identification information for initiating an identifier of the session as a BPCF in the future, so that the PCRF determines whether the session BPCF requested to be established has been initiated. The request establishment session identification information may be location information of the UE accessing the BBF access network, or a uniquely distinguishable identifier allocated by the PCRF, or a user identifier, or a user identifier and a PDN identifier, or a local IP of the UE. address.

Step 703: The DRA determines, according to the user identifier, whether a BPCF has been selected for the UE (if the DRA is configured to select one BPCF for each UE) or determines whether a BPCF has been selected for the IP-CAN session according to the user identifier and the PDN identifier (if DRA) Configure to select one BPCF per PDN for each UE. ₀ At this time, if there is no corresponding DRA binding in the DRA, the DRA selects a BPCF for the UE or the IP-CAN session, and saves the correspondence (user ID, PDN). ID, BPCF ID) or (user ID, BPCF ID) or (user ID, PDN ID, UE local IP address, BPCF ID); create a DRA binding, otherwise the DRA is based on the user ID, PDN ID, and/or UE local IP. The address updates the DRA binding. At the same time, the DRA saves the Diameter session associated with the binding, where ID1 is added to the DRA binding. That is, the association between the DRA binding and the ID1-identified session is saved, that is, the message that the DRA binding and the triggering BPCF establishes the S9* session is saved (ie, step 702, the message may be established by using the ID1 and/or the request carried in step 702). The association of the session identification information uniquely identified).

Step 704: The DRA sends a Diameter session establishment request message to the selected BPCF, where the Diameter session establishment request message carries a user identifier, a PDN identifier, and a request to establish a session indication. The PCRF fills in the BPCF identifier in the Destination-Host AVP of the message.

Step 705: After receiving the Diameter session establishment request message, the BPCF returns a Diameter session establishment response message to the DRA.

Step 706: After receiving the Diameter session setup response message, the DRA returns a Diameter session establishment response message to the PCRF. If the DRA can return the selected BPCF identifier, then The DRA carries the BPCF identifier in the response message.

The Diameter session established in steps 705 through 706 is referred to as an S9a session in the present invention. Step 707: The BPCF establishes a session indication according to the request in the Diameter session establishment request message, and sends a Diameter session establishment request message to the PCRF to request to establish a policy control session. The BPCF allocates a session identifier Session ID to the Diameter session established by the request, and the identifier is

ID2.

The Diameter session establishment request message may carry the request establishment session identifier information sent in step 704 to notify the PCRF that the message is used to establish the policy control session requested to be established in step 704.

Step 708: The PCRF sends a Diameter session establishment response message to the BPCF.

The Diam session established in steps 707 through 708 is referred to as an S9* session in the present invention. Thereafter, the PCRF can issue the policy through the policy control session established in step 707 and step 708. The BPCF can also perform policy execution results, admission control results, and event reporting.

In this embodiment, the Diameter session request message may adopt a credit control request message. As steps 702 and 704 are credit control request messages, steps 705 and 706 are credit control response messages.

In this embodiment, the Diameter session request message may also re-authorize the request message, as in step 702 and step 704, the authorization authentication request, and step 705 and step 706 are the authorization authentication response. Therefore, in this embodiment, the specific form of the Diameter session request message is not limited.

In other embodiments, the message of step 702 and step 704 may also carry an indication that the session state is not maintained (ie, the message carries an Auth-Session-State AVP, and the value is NO_STATE_MAINTAINED), or does not carry the PCRF. The session ID assigned by this Diameter session. That is, step 702 - step 706 interaction does not establish an S9a session (in the message interaction node) After the bundle, the relevant session information will not be maintained in the PCRF and BPCF). Therefore, step 702-step 706 is only used to trigger the BPCF to initiate the establishment of the S9* session. In step 703, the DRA determines, according to the user identifier, whether a BPCF has been selected for the UE (if the DRA is configured to select one BPCF for each UE) or determines whether a BPCF has been selected for the IP-CAN session according to the user identifier and the PDN identifier (if The DRA is configured to select one BPCF per PDN per UE. ₀ At this time, if there is no corresponding DRA binding in the DRA (ie, no BPCF is selected for the UE or IP-CAN session), the DRA is the UE or the IP- Select a PCRF for the CAN session, and save the corresponding relationship (user ID, PDN ID, BPCF ID) or (user ID, BPCF ID) or (UE local address, user ID, PDN ID, BPCF ID) to create a DRA binding; otherwise The DRA updates the DRA binding based on the user identity, the PDN identity, and/or the UE local IP address. Whether it is an update or a new one, the association between the DRA binding and the triggering BPCF to establish an S9* session in the DRA binding (ie, the step 702 message, the message may be uniquely identified by the request carried in step 702) is established. relationship.

Embodiment 4

In this embodiment, according to the flow of FIG. 7, after the policy control session is established by the PCRF and the BPCF, the DRA binding process in the DRA is deleted when the IP-CAN session is terminated, where the DRA is a redirection proxy mode. FIG. 8 is a flowchart of deleting the policy control session binding information in the DRA according to the architecture of FIG. 2, and as shown in FIG. 8, the deleting the policy control session binding information in the DRA in this example includes the following steps:

Step 801: The PCRF is triggered, and the policy control session between the BPCF and the BPCF needs to be terminated, that is, the S9* session.

The trigger may be caused by the ePDG or the P-GW sending a policy control session termination message to the PCRF, where the policy control session message carries indication information that the UE accesses or disconnects the PDN connection from the WLAN. After receiving the policy control session termination message, the PCRF determines that the policy control session with the BPCF needs to be terminated. Step 802: The PCRF sends a request to the BPCF to terminate the Diameter session, where the session carries the request session termination indication. The message is sent through the S9* session, that is, the Session ld carried in the message is ID2.

Step 803: The BPCF returns a request to the PCRF to terminate the Diameter session response.

Step 804: The BPCF sends a Diameter session termination request to the PCRF. The message passed

The S9* session is sent, that is, the Session ld carried in the message is ID2 and/or the request to establish a session identification message. Step 805: The PCRF returns a Diameter session termination response to the BPCF.

Step 806: The PCRF sends a Diameter session termination request to the DRA, where the message carries the Session Id as ID1.

Step 807: The DRA judges that the IP-CAN session has a valid DRA binding according to Session Id = IDl.

Step 808: The DRA sends a Diameter session termination request to the BPCF, where the message carries the Session Id as ID1.

Step 809: BPCF returns a confirmation message to the DRA;

Step 810: The DRA marks the Diameter session summary according to Session Id = IDl. That is, the association between the DRA binding and the ID1-identified session in the DRA binding is deleted, that is, the DRA binding in the DRA binding is deleted and the BPCF is triggered to establish an S9* session (ie, step 702 message, the message can be ID1 and / or request to establish an association relationship with the unique identification of the session identification information.

If the DRA binding is per IP-CAN session, and all of the IP-CAN sessions are related

The Diameter session is terminated (ie, the association between the DRA binding and all Diameter sessions related to the IP-CAN session in the DRA binding is deleted), then the DRA will delete the DRA binding; if the DRA binding is per UE And all the Diameter sessions of the UE are terminated (that is, the association relationship between the DRA binding and all Diameter sessions related to the UE in the DRA binding is deleted), then the DRA deletes the DRA binding. Step 811: The DRA returns a Diameter session termination response to the PCRF.

In other embodiments, if the S9a session is not established in the flow of Figure 7 (i.e., PCRF and BPCF do not retain S9a session state information), the flow of Figure 8 can be implemented as follows:

In step 806, the PCRF does not carry the Session id. Instead, the session identification information is established with the request in step 702. In step 810, the DRA establishes session identification information according to the request to determine that the IP-CAN session has a valid DRA binding, and deletes the D9 binding to establish a S9* session message with the triggering BPCF (ie, step 702 message, the message can be used. The association carried in step 702 establishes an association relationship of the session identification information unique identifier. At this time, if the DRA binding is per IP-CAN session, and all the Diameter sessions related to the IP-CAN session are terminated (these sessions are in a hold state, all the Diameter sessions related to the IP-CAN session are terminated) In the DRA binding, the association relationship between the DRA binding and all Diameter sessions related to the IP-CAN session is deleted, then the DRA will delete the DRA binding; if the DRA binding is per UE and all Diameter sessions of the UE Both ends (these sessions are in the state of being maintained. If all the Diameter sessions of the UE are terminated, the association relationship associated with the session identifier in the DRA binding is deleted), then the DRA deletes the DRA binding. Additionally, steps 808 and 809 may not be performed.

Embodiment 5

FIG. 9 is a flowchart of a DRA (V-DRA) selection of a visited PCRF (V-PCRF) in a UE attaching process in a roaming scenario, where V-DRA is a redirected Redirect mode, as shown in FIG. The method specifically includes the following steps:

Step 901: The H-PCRF is triggered, and a policy control session with the V-PCRF needs to be established, that is, an S9 session. At this time, there is no S9 session established between the V-PCRF and the H-PCRF for the UE.

The trigger may be caused by the P-GW sending a policy control session message (ie, an IP-CAN session establishment indication message) to the H-PCRF, where the policy control session message carries the UE through Instructions for WLAN access. After receiving the policy control session message, the H-PCRF determines that a policy control session (ie, an S9 session) with the V-PCRF needs to be established, so as to provide a policy to the BBF access network through the V-PCRF and request the BBF access network. Admission control.

Step 902: The H-PCRF sends a Diameter session establishment request message to the V-DRA, where the Diameter session establishment request message carries a user identifier, a PDN identifier, and a request to establish a session indication. The H-PCRF fills in the domain name of the visited network in the Destination-Host AVP of the message. The H-PCRF allocates a session ID, which is ID1, to the Diameter session established by the request.

Here, the request to establish a session indication is used to notify the V-PCRF to initiate the establishment of the S9 session.

The request to establish session identification information may be further carried in the Diameter session establishment request message, so that the H-PCRF determines whether the session V-PCRF that is requested to be established has been initiated. The request establishment session identifier information may be location information of the UE accessing the BBF access network, or a uniquely distinguishable identifier allocated by the H-PCRF, or a user identifier, or a user identifier and a PDN identifier, or a UE Local IP address.

Step 903: The V-DRA determines, according to the user identifier, whether the V-PCRF has been selected for the UE (the V-DRA is configured to select one PCRF for each UE). At this time, if there is no corresponding binding information in the V-DRA, the V-DRA is the user, and the corresponding relationship (user ID, PDN identifier, V-PCRF identifier) or (user ID, V-PCRF identifier) is saved. Or (user identity, PDN identity, UE local IP address, V-PCRF identity;), create a DRA binding, otherwise the V-DRA updates the DRA binding according to the user identity, the PDN identity, and/or the UE local IP address. At the same time, the V-DRA saves the Diameter session associated with the binding, where ID1 is added to the DRA binding. That is, the association between the DRA binding and the ID1-identified session is saved, that is, the message that the DRA binding and the triggering V-PCRF establishes the S9 session is saved (ie, step 902, the message may be carried by ID1 and/or the request carried in step 902). Establish an association relationship with the unique identifier of the session identification information.

Step 904: The V-DRA returns a redirect message to the H-PCRF, and the DRA is carried in the message. 903 The identifier of the selected V-PCRF.

Step 905: The H-PCRF sends a Diameter session establishment request message to the sending V-PCRF according to the V-PCRF identifier returned by the 904, where the Diameter session establishment request message carries the user identifier, the PDN identifier, and the request establishment session indication. The PCRF fills in the V-PCRF identifier in the Destination-Host AVP of the Diameter session establishment request message.

Step 906: After receiving the Diameter session establishment request message, the V-PCRF returns a Diameter session establishment response message to the PCRF.

The Diameter session established by step 905 and step 906 is referred to as an S9a session in the present invention. Step 907: The V-PCRF establishes a session indication according to the request in the Diameter session establishment request message, and sends a Diameter session establishment request message to the H-PCRF to request to establish a policy control session (ie, an S9 session). The V-PCRF allocates a session identifier Session ID for the Diameter session established by the request, and the identifier is ID2, and the V-PCRF also requests to establish an S9 sub-session (the PDN connection established by the sub-session).

The Diameter session establishment request message may carry the request establishment session identifier information sent in step 905, and is used to notify the H-PCRF that the message is used to establish the policy control session requested to be established in step 905.

Step 908: The H-PCRF sends a Diameter session establishment response message to the V-PCRF.

Step 909: The DRA and the BPCF in the V-PCRF and the BBF access network are executed according to the process shown in FIG. 5.

Thereafter, the H-PCRF can perform the policy delivery by the policy control session (S9 session) established in step 907 and step 908. The V-PCRF can also perform policy execution results, admission control results, and event reporting.

In this embodiment, the Diameter session request message may adopt a credit control request message. As steps 902 and 905 are credit control request messages, steps 903 and 906 are credit control response messages. In this embodiment, the Diameter session request message may also re-authorize the request message, as in step 902 and step 905, the authorization authentication request, step 903 and step 906 are the authorization authentication response. Therefore, in this embodiment, the specific form of the Diameter session request message is not limited.

In other embodiments, the message of step 902 and step 905 may also carry an indication that the session state is not maintained (that is, the message carries the Auth-Session-State AVP, the value is NO_STATE_MAINTAINED), or does not carry the H- The session ID assigned by the PCRF to the Diameter session. That is, the step 902-step 906 interaction does not establish an S9a session (after the end of the message interaction, the relevant session information is not maintained in the H-PCRF and the V-PCRF). Therefore, step 902-step 906 is only used to trigger the V-PCRF to initiate the establishment of the S9 session. In step 903, the V-DRA determines, according to the user identifier, whether the V-PCRF has been selected for the UE. At this time, if there is no corresponding DRA binding in the V-DRA (that is, no V-PCRF is selected for the UE), the V-DRA selects a V-PCRF for the UE, and saves the corresponding relationship (user identifier, PDN identifier). , V-PCRF identifier) or (user ID, V-PCRF identifier) or (UE local address, user ID, PDN identifier, V-PCRF identifier;), create DRA binding, otherwise V-DRA user ID, PDN identifier And/or the UE local IP address updates the DRA binding. Whether it is an update or a new one, the DRA binding is saved in the DRA binding, and the message that triggers the V-PCRF to establish an S9 session (ie, the step 902 message, the message may be uniquely identified by the request carried in step 902) connection relation.

After performing the above process, the UE may need to establish a new PDN connection.

When the UE initiates a new PDN connection, if the Home Routed scenario (ie, the P-GW is located in the HPLMN), the H-PCRF receives the policy control session message (ie, the IP-CAN session establishment indication message) sent from the P-GW. Then, the H-PCRF modifies the established S9 session, and requests the V-PCRF to establish an S9 sub-session with the H-PCRF (the sub-session corresponds to the newly established PDN connection). After receiving the above request, the V-PCRF sends a request message to the H-PCRF to establish an S9 sub-session; if the Visited Access scenario (that is, the P-GW is located in the VPLMN), the V-PCRF receives To the policy control session message (ie, IP-CAN session establishment indication message) sent from the P-GW, the V-PCRF modifies the established S9 session, and requests to establish another S9 sub-session with the H-PCRF (the sub-session corresponds to the sub-session) Newly established PDN connection).

Since the S9 session is modified, it does not involve establishing a new S9a session or a new message that triggers the V-PCRF to establish an S9 session. In addition, after modifying the S9 session, you may need to perform the process of establishing an S9* session between V-PCRF and BPCF. Therefore, when the UE establishes multiple PDN connections, there is an S9 session between the V-PCRF and the H-PCRF, which includes multiple sub-sessions, some of which are initiated by the V-PCRF, and some are by H. - The PCRF requests the V-PCRF to initiate the establishment. At the same time, there is an S9a session between H-PCRF and V-PCRF. There is an S9* session between the BPCF and the V-PCRF, and the S9* session corresponds to the S9 session.

Embodiment 6

In this embodiment, according to the flow of FIG. 9, after the V-PCRF and the H-PCRF establish a policy control session, the process of deleting the binding information in the V-DRA is performed when the IP-CAN session is terminated, where the V-DRA is a redirect Redirect. the way. FIG. 10 is a flowchart of the binding policy of the deletion policy control session according to the present invention. As shown in FIG. 10, the deletion policy control session binding information in this example specifically includes the following steps:

Step 1001: The H-PCRF is triggered, and the policy control session between the V-PCRF and the V-PCRF needs to be terminated, that is, the S9 session.

The trigger may be caused by the P-GW sending a policy control session termination message to the H-PCRF. The policy control session termination message is an IP-CAN session termination indication message, where the policy control session message carries the UE to detach from the WLAN access. Or disconnect the PDN connection instructions. After receiving the policy control session termination message, the H-PCRF determines that the S9 session with the V-PCRF needs to be terminated.

Step 1002: The H-PCRF sends a request to the V-PCRF to terminate the Diameter session, where the session carries the request session termination indication. The message is sent through the S9 session, that is, the Session Id carried in the message is ID2. Step 1003: The V-PCRF returns a request to the H-PCRF to terminate the Diameter session response. Step 1004: The V-PCRF sends a Diameter session termination request to the H-PCRF.

Step 1005: The H-PCRF returns a Diameter session termination response to the V-PCRF.

Step 1006: The H-PCRF sends a Diameter session termination request to the V-DRA, and the message is sent through the S9a session, and the message carries the Session ld as ID1.

Step 1007: The H-PCRF sends a Diameter session termination request to the V-PCRF, where the message carries the Session Id as ID 1.

Step 1008: The V-DRA judges that the IP-CAN session has a valid DRA binding according to Session Id = ID1, and marks the end of the Diameter session. That is, the association between the DRA binding and the ID-identified session in the DRA binding is deleted, that is, the DRA binding in the DRA binding is deleted, and the V-PCRF is triggered to establish an S9 session (ie, step 902, the message can be used. The association relationship between ID1 and/or request to establish a unique identifier for the session identification information.

If all the Diameter sessions of the UE are terminated, the V-DRA deletes the DRA binding (that is, the association between the DRA binding and all Diameter sessions related to the UE in the DRA binding is deleted).

Step 1009: The DRA returns a redirect message to the H-PCRF.

Step 1010: The V-PCRF returns a Diameter session termination response to the H-PCRF.

Step 1011: The DRA and the BPCF in the V-PCRF and the BBF access network are executed according to the flow of FIG. 6.

If the UE establishes multiple PDN connections (that is, there are more than one S9 sub-session in the S9 session), the H-PCRF may notify the V-DRA to delete the established S9a session in two cases:

(1) When the H-PCRF terminates the S9 session, the H-PCRF terminates the S9a session at the same time. At this time, the H-PCRF notifies the V-DRA S9a session to terminate. At this time, because the S9 session is terminated, the UE is in the V-DRA. The related other Diameter sessions must have been terminated. Therefore, in step 1008, when the V-DRA receives the Diameter session termination request sent by the H-PCRF, the V-DRA deletes the UE. DRA binding. That is, when the H-PCRF terminates the S9 session, the H-PCRF sends a message to the V-DRA, informing the V-DRA to delete the DRA binding of the UE.

(2) When the H-PCRF terminates the S9 sub-session initiated by the V-PCRF, the H-PCRF terminates the S9a session at the same time. The H-PCRF notifies the V-DRA S9a session to terminate. At this time, since the S9 session has not been terminated, the other Diameter sessions related to the UE in the V-DRA are not completely terminated. Therefore, in step 1008, when the V-DRA receives the Diameter session termination request of the H-PCRF, The V-DRA deletes the DRA binding in the DRA binding and triggers the V-PCRF to establish an S9 session. The DRA binding of the UE cannot be deleted.

In other embodiments, if the S9a session is not established in the flow of FIG. 9 (ie, the H-PCRF and the V-PCRF do not retain the S9a session state information), the process of FIG. 10 can be implemented as follows:

In step 1006, the PCRF also does not carry the Session id. Instead, the same request as in step 902 is carried to establish session identification information. In step 1008, the V-DRA establishes session identification information according to the request to determine that the IP-CAN session has a valid DRA binding, and deletes the message in the DRA binding that establishes an S9 session with the triggering V-PCRF (ie, step 902 message, The message may use the request carried in step 902 to establish an association relationship uniquely identified by the session identification information. If all the Diameter sessions of the UE are terminated (these sessions are in the hold state, all the Diameter sessions of the UE are terminated, indicating that the association relationship associated with the session identifier in the DRA binding is deleted) and the V-PCRF is triggered by the H-PCRF. The association of the messages of the S9 session is deleted, and the V-DRA deletes the DRA binding. Further, step 1007 and step 1010 may not be performed.

If the UE establishes multiple PDN connections (ie, there is more than one S9 sub-session in the S9 session), then the H-PCRF may notify the V-DRA to delete the S9 initiated by the V-PCRF requested by the H-PCRF in two cases. Association of session messages:

(1) When the H-PCRF terminates the S9 session, the H-PCRF notifies the V-DRA to delete the association relationship with the message that the H-PCRF triggers the V-PCRF to establish the S9 session; at this time, since the S9 session is terminated, then the V-DRA Other Diameter sessions related to the UE must have been terminated, so In step 1008, when the H-PCRF notifies the V-DRA to delete the association relationship between the message that the H-PCRF triggers the V-PCRF to establish the S9 session, the V-DRA deletes the DRA binding of the UE. That is, when the H-PCRF terminates the S9 session, the H-PCRF sends a message to the V-DRA, informing the V-DRA to delete the DRA binding of the UE.

(2) When the H-PCRF terminates all H-PCRF requests for the S9 sub-session initiated by the V-PCRF, the H-PCRF notifies the V-DRA to delete the association relationship with the message that the H-PCRF triggers the V-PCRF to establish an S9 session. At this time, since the S9 session has not been terminated, the other Diameter sessions related to the UE in the V-DRA are not completely terminated, so in step 1008, when the H-PCRF notifies the V-DRA to delete and the H-PCRF triggers V. - When the PCRF establishes the association relationship between the messages of the S9 session, the V-DRA cannot delete the DRA binding after deleting the DRA binding in the DRA binding and the message triggering the V-PCRF to establish the S9 session.

Example 7

FIG. 11 is a flowchart of the V-DRA selecting a V-PCRF in a UE attaching process according to the architecture of FIG. 2 and FIG. 4, wherein the DRA is a redirected Proxy mode, as shown in FIG. The method specifically includes the following steps:

Step 1101: The H-PCRF is triggered, and a policy control session (S9 session) with the V-PCRF needs to be established. That is, there is no S9 session established between the V-PCRF and the H-PCRF for the UE. .

The trigger may be caused by the P-GW sending a policy control session message to the H-PCRF. The policy control session message is an IP-CAN session establishment indication message, and the policy control session message carries indication information that the UE accesses through the WLAN. After receiving the policy control session message, the H-PCRF determines that a policy control session with the V-PCRF needs to be established to provide a policy to the BBF access network through the V-PCRF and request admission control of the BBF access network.

Step 1102: The H-PCRF sends a Diameter session establishment request message to the V-DRA, where the Diameter session establishment request message carries a user identifier, a PDN identifier, and a request to establish a session indication. The PCRF fills in the domain name of the visited network in the Destination-Host AVP of the message. H-PCRF The session identifier is assigned to the Diameter session established for the request, and is identified as ID1.

The Diameter session establishment request message may further carry a request to establish session identification information, which is used as an identifier for initiating a session in the future as a V-PCRF, so that the H-PCRF determines whether the session V-PCRF requested to be established has been initiated. The request establishment session identification information may be location information of the UE accessing the BBF access network, or a uniquely distinguishable identifier allocated by the H-PCRF, or a user identifier, or a user identifier and a PDN identifier, or a UE Local IP address.

Step 1103: The V-DRA determines, according to the user identifier, whether the V-PCRF has been selected for the UE (the V-DRA is configured to select one V-PCRF for each UE). At this time, if there is no corresponding DRA binding in the V-DRA, the V-DRA selects a V-PCRF for the UE, and saves the correspondence (user ID, PDN identifier, V-PCRF identifier) or (user ID, V-PCRF) or (user identity, PDN identity, UE local IP address, V-PCRF identity), create a DRA binding, otherwise the V-DRA updates the DRA binding according to the user identity, the PDN identity, and/or the UE local IP address. At the same time, the V-DRA saves the Diameter session associated with the binding, where ID1 is added to the DRA binding. That is, the association between the DRA binding and the ID1-identified session is saved, that is, the message that the DRA binding and the triggering V-PCRF establish an S9 session is saved (ie, step 902, the message may be carried by ID1 and/or the request carried in step 902). Establish an association relationship with the unique identifier of the session identification information.

Step 1104: The V-DRA sends a Diameter session establishment request message to the selected V-PCRF, where the Diameter session establishment request message carries a user identifier, a PDN identifier, and a request to establish a session indication. The V-DRA fills in the BPCF identifier in the Destination-Host AVP of the message.

Step 1105: After receiving the Diameter session establishment request message, the V-PCRF returns a Diameter session establishment response message to the V-DRA.

Step 1106: After receiving the Diameter session establishment response message, the V-DRA returns a Diameter session establishment response message to the H-PCRF. If the V-DRA can return the selected V-PCRF identifier, the V-DRA carries the V-PCRF identifier in the response message. Step 1105 - The Diameter session established in step 1106 is referred to as an S9a session in the present invention.

Step 1107: The V-PCRF establishes a session indication according to the request in the Diameter session establishment request message, and sends a Diameter session establishment request message to the H-PCRF to request to establish a policy control session, that is, establish an S9 session. The V-PCRF allocates a session ID for the Diameter session established by the request, and the identifier is ID2. The V-PCRF also requests to establish an S9 sub-session (the PDN connection established by the sub-session).

The Diameter session establishment request message may carry the request establishment session information in step 1104 to notify the H-PCRF that the message is used to establish the policy control session requested in step 1104.

Step 1108: The H-PCRF sends a Diameter session establishment response message to the V-PCRF. Step 1109: The V-PCRF interacts with the DRA and BPCF in the BBF access network to perform the process of FIG. 5 or FIG. 7.

Thereafter, the H-PCRF can perform the policy delivery by using the S9 session established in step 1107 and step 1108. The V-PCRF can also perform policy execution results, admission control results, and event reporting.

In this embodiment, the Diameter session request message may adopt a credit control request message. If the credit control request message is in step 1102 and step 1104, step 1105 and step 1106 are credit control response messages.

In this embodiment, the Diameter Session Request message may also re-authorize the request message, such as the authorization authentication request in steps 1102 and 1104, and the step 1105 and the step 1106 are the authorization authentication response. Therefore, in this embodiment, the specific form of the Diameter session request message is not limited.

In other embodiments, the message of step 1102 and step 1104 may also carry an indication that the session state is not maintained (ie, the message carries an Auth-Session-State AVP, the value is NO STATE MAINTAINED), or does not carry the H-PCRF. The Diameter session The associated session ID. That is, step 1102 - step 1106 does not establish an S9a session (after the end of the message interaction, the relevant session information is not maintained in the H-PCRF and the V-PCRF). Therefore, step 1102 - step 1106 is only used to trigger the V-PCRF to initiate the establishment of the S9 session. In step 1103, the V-DRA determines, according to the user identifier, whether the V-PCRF has been selected for the UE. At this time, if there is no corresponding DRA binding in the V-DRA (that is, no V-PCRF is selected for the UE), the V-DRA selects a PCRF for the UE, and saves the corresponding relationship (user identifier, PDN identifier, V - PCRF identity) or (user identity, V-PCRF identity) or (UE local address, user identity, PDN identity, V-PCRF identity;), otherwise V-DRA user identity, PDN identity and/or UE local IP address Update the DRA binding. Whether it is an update or a new one, the DRA binding is saved in the DRA binding, and the message that triggers the V-PCRF to establish an S9 session (ie, the message of step 1102, the message may be uniquely identified by the request carried in step 1102). connection relation.

When the UE initiates a new PDN connection, if the Home Routed scenario (ie, the P-GW is located in the HPLMN), the H-PCRF receives the policy control session message (ie, the IP-CAN session establishment indication message) sent from the P-GW. Then, the H-PCRF modifies the established S9 session, and requests the V-PCRF to establish an S9 sub-session with the H-PCRF (the sub-session corresponds to the newly established PDN connection). After receiving the above request, the V-PCRF sends a request message to the H-PCRF to establish an S9 sub-session; if the Visited Access scenario (ie, the P-GW is located in the VPLMN), the V-PCRF receives the policy control sent from the P-GW. The session message (ie, the IP-CAN session establishment indication message), the V-PCRF modifies the established S9 session, and requests to establish another S9 subsession with the H-PCRF (the subsession corresponds to the newly established PDN connection).

Since the S9 session is modified, it does not involve establishing a new S9a session or a new message triggering the V-PCRF to establish an S9 session. In addition, after modifying the S9 session, it may be necessary to perform a process of establishing an S9* session between the V-PCRF and the BPCF. Therefore, when the UE establishes multiple PDN connections, there is an S9 session between the V-PCRF and the H-PCRF, which includes multiple sub-sessions, and some of the multiple sub-sessions are V-PCRF initiated the establishment of the V-PCRF, and some were initiated by the H-PCRF request V-PCRF. At the same time, there is an S9a session between H-PCRF and V-PCRF. There is an S9* session between the BPCF and the V-PCRF, and the S9* session corresponds to the S9 session.

Example 8

In this embodiment, according to the flow of FIG. 11, after the S9 is established by the H-PCRF and the V-PCRF, the process of deleting the binding information in the DRA is performed when the IP-CAN session is terminated, where the DRA is a redirected Proxy mode. FIG. 12 is a flowchart of the method for controlling session binding based on the deletion policy of FIG. 11 . As shown in FIG. 12 , the example of deleting the policy control session binding information includes the following steps: Step 1201 : The H-PCRF is triggered, and needs to be performed. Terminate the policy control session with the V-PCRF, ie the S9 session.

The trigger may be caused by the P-GW sending a policy control session termination message to the PCRF. The policy control session termination message is an IP-CAN session termination indication, and the policy control session message carries the UE to attach or disconnect from the WLAN access. Instructions for PDN connections. After receiving the policy control session termination message, the PCRF determines that the policy control session with the V-PCRF needs to be terminated.

Step 1202: The H-PCRF sends a request to the V-PCRF to terminate the Diameter session, where the session carries the request session termination indication. The message is sent through the S9 session, that is, the Session Id carried in the message is ID2.

Step 1203: The V-PCRF returns a request to the H-PCRF to terminate the Diameter session response. Step 1204: The V-PCRF sends a Diameter session termination request to the H-PCRF. The message is sent through the S9 session, that is, the Session Id carried in the message is ID2.

Step 1205: The H-PCRF returns a Diameter session termination response to the V-PCRF.

Step 1206: The H-PCRF sends a Diameter session termination request to the V-DRA, and the message is sent through the S9a session. The message carries the Session ld ID1.

Step 1207: The V-DRA judges that the IP-CAN session has a valid DRA binding according to Session Id = ID1. Step 1208: The V-DRA sends a Diameter session termination request to the V-PCRF, where the message carries the Session Id as ID1.

Step 1209: The V-PCRF returns an acknowledgement message to the V-PCRF.

Step 1210: The V-DRA marks the Diameter session summary according to Session Id = ID1. That is, the association between the DRA binding and the ID1-identified session in the DRA binding is deleted, that is, the DRA binding in the DRA binding is deleted and the V-PCRF is triggered to establish an S9 session (ie, step 1102 message, the message can be ID1) And/or request to establish an association relationship with the session identification information unique identifier). If all the Diameter sessions of the UE are terminated (that is, the association relationship between the DRA binding and all Diameter sessions related to the UE in the DRA binding is deleted), the V-DRA deletes the DRA binding.

Step 1211: The V-DRA returns a Diameter session termination response to the H-PCRF.

Step 1212: The V-PCRF interacts with the DRA and BPCF in the BBF access network to perform the process of FIG. 5 or FIG. 7.

(1) When the H-PCRF terminates the S9 session, the H-PCRF terminates the S9a session at the same time. At this time, the H-PCRF notifies the V-DRA S9a session to terminate. At this time, because the S9 session is terminated, the UE is in the V-DRA. The related other Diameter sessions must have been terminated. Therefore, in step 1210, when the V-DRA receives the Diameter session termination request sent by the H-PCRF, the DRA binding can be deleted. At this time, the Diameter session termination request message sent by the H-PCRF can also be understood as a DRA binding deletion message. That is, when the H-PCRF terminates the S9 session, the H-PCRF sends a message to the V-DRA, informing the V-DRA to delete the DRA binding of the UE.

(2) When the H-PCRF terminates all H-PCRF requests for the S9 sub-session initiated by the V-PCRF, the H-PCRF terminates the S9a session at the same time, and the H-PCRF notifies the V-DRA S9a session to terminate. At this time, since the S9 session has not been terminated, other Diameter related to the UE in the V-DRA is The session is not completely terminated. Therefore, in step 1210, when the V-DRA receives the Diameter session termination request from the H-PCRF, the V-DRA deletes the DRA binding in the DRA binding and triggers the V-PCRF to establish the S9 session. The DRA binding of the UE cannot be deleted yet.

In other embodiments, if the S9a session is not established in the flow of FIG. 11 (ie, the H-PCRF and the V-PCRF do not retain the S9a session state information), the process of FIG. 12 can be implemented as follows: In step 1006, the PCRF is also Do not carry the Session id. Instead, the same request as in step 1102 is carried to establish session identification information. In step 1210, the V-DRA establishes the session identification information according to the request to determine that the IP-CAN session has a valid DRA binding, and deletes the message in the DRA binding that establishes the S9 session with the triggering V-PCRF (ie, step 1102 message, The message may use the request carried in step 1102 to establish an association relationship uniquely identified by the session identification information. If all the Diameter sessions of the UE are terminated (these sessions are in the hold state, all the Diameter sessions of the UE are terminated, indicating that the association relationship associated with the session identifier in the DRA binding is deleted) and the V-PCRF is triggered by the H-PCRF. The association of the messages of the S9 session is deleted, and the V-DRA deletes the DRA binding. Additionally, step 1208 and step 1209 may not be performed.

(1) When the H-PCRF terminates the S9 session, the H-PCRF notifies the V-DRA to delete the association relationship with the message that the H-PCRF triggers the V-PCRF to establish the S9 session; at this time, since the S9 session is terminated, then the V-DRA The other Diameter sessions related to the UE must have been terminated. Therefore, in step 1210, when the H-PCRF notifies the V-DRA to delete the association relationship with the message that the H-PCRF triggers the V-PCRF to establish the S9 session, the V-DRA Delete the DRA binding of the UE. At this time, the notification message sent by the H-PCRF can also be understood as a DRA binding deletion message. That is, when the H-PCRF terminates the S9 session, the H-PCRF sends a message to the V-DRA, informing the V-DRA to delete the DRA of the UE. Set.

(2) When the H-PCRF terminates all H-PCRF requests for the S9 sub-session initiated by the V-PCRF, the H-PCRF notifies the V-DRA to delete the association relationship with the message that the H-PCRF triggers the V-PCRF to establish an S9 session. At this time, since the S9 session has not been terminated, the other Diameter sessions related to the UE in the V-DRA are not completely terminated, so in step 1210, when the H-PCRF notifies the V-DRA to delete and the H-PCRF triggers V. - When the PCRF establishes the association relationship between the messages of the S9 session, the V-DRA cannot delete the DRA binding of the UE after deleting the DRA binding in the DRA binding and the message triggering the V-PCRF to establish the S9 session.

The present invention also describes a system for deleting binding information in a Diameter routing agent, which is applied to a network that accesses an EPS through a BBF access network, where the system includes a first policy server, a second policy server, and a DRA, where:

After the DRA receives the notification of the association relationship between the deleted DRA binding and the message that the first policy server triggers the second policy server to establish the first policy control session, the DRA deletes the DRA binding. And an association relationship between the message that the first policy server triggers the second policy server to establish the first policy control session.

After the foregoing DRA deletes the association relationship between the DRA binding and the message that the first policy server triggers the second policy server to establish the first policy control session, the system further includes:

If the DRA binding is per IP-CAN session, and all policy control sessions of the IP-CAN session are terminated, the DRA is further used to delete the DRA binding associated with the IP-CAN; or If the DRA binding is per UE, and all the policy control sessions of the UE are terminated, the DRA is further used to delete the DRA binding associated with the UE.

Before the first policy server terminates the first policy control session with the second policy server,

The first policy server is further configured to notify the DRA to save the first policy server in the DRA binding when receiving the first policy control session trigger between the creation and the second policy server And triggering an association relationship between the message that the second policy server establishes the first policy control session;

The first policy server is a PCRF, and the second policy server is a BPCF;

Or the first policy server is an H-PCRF, and the second policy server is a V-PCRF.

The present invention also describes another system for deleting the binding information in the Diameter routing agent, which is applied to the network that accesses the EPS through the BBF access network, and the system includes an H-PCRF and a V-PCRF, where:

The H-PCRF is configured to: when the H-PCRF terminates the S9 session with the V-PCRF, the H-PCRF notifies the visited Diameter routing agent that the V-DRA deletes the DRA binding; or

The H-PCRF notifies the V-DRA to delete the DRA when all the H-PCRFs request the V-PCRF to create a sub-session in the H-PCRF and the V-PCRF-terminating S9 session. The association relationship between the binding and the message that the H-PCRF triggers the V-PCRF to establish the S9 session. Further, the H-PCRF carries the same session identifier and/or the message that the H-PCRF triggers the V-PCRF to establish the S9 session in the message that informs the V-DRA to delete the DRA binding. Request to establish session identification information; or,

Further, the request to establish the session identification information is location information of the user equipment UE accessing the broadband forum BBF access network, or the uniquely distinguishable identifier allocated by the H-PCRF, or the user identifier, or the The local IP address of the UE, or the user ID and PDN ID.

The invention also describes a method for creating binding information in a Diameter routing agent, comprising: sending, by the first policy server, a trigger message to the DRA when receiving the triggering of the first policy control session between the second policy server and the second policy server;

Further, the trigger message carries a session identifier or carries an indication that the session state is not maintained. Those skilled in the art should understand that the method for creating binding information in the Diameter routing proxy can be understood by referring to the interaction flow shown in FIG. 5 to FIG. 12 described above.

The present invention also describes an H-PCRF, which is used to notify the visited Diameter routing agent V-DRA to delete the DRA binding when the H-PCRF and the V-PCRF terminate the S9 session; or

When the H-PCRF and the V-PCRF terminate the S9 session, all the H-PCRF requests the V-PCRF to create the sub-session, notify the V-DRA to delete the DRA binding and establish the S9 with the H-PCRF trigger V-PCRF. The association of the messages of the session. Those skilled in the art should understand that the foregoing network structure and network element H-PCRF can be understood by referring to the network structure of the existing protocol and the interaction flow between the network elements shown in FIG. 5 to FIG. The specific implementation structure is not limited as long as the above technical solution of the present invention can be implemented. The functions that can be implemented by the network elements in the system of the present invention can be understood by referring to the interaction process between the network elements shown in FIG. 5 to FIG. 12.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Industrial applicability

When the BBF access network is incapable of sensing the UE access, the PCRF triggers the BPCF to establish a policy control session to implement the policy control, and after deleting the policy control session, the related binding information of the policy control session needs to be deleted in the DRA. The invention achieves a better complement to the existing protocol, and clarifies the mechanism for creating and deleting a policy control session.

Claims

Claim

A method for deleting binding information in a Diameter routing proxy, the method comprising:

When the first policy server terminates the first policy control session with the second policy server, the first policy server triggers the second policy server to establish an association relationship of the message of the first policy control session.

The method according to claim 1, wherein the DRA receives the deleted DRA binding and the first policy server triggers the second policy server to establish the first policy control session. After the notification of the association of the message, the method further includes:

The method according to claim 2, wherein the DRA deletes a message in the DRA binding that is triggered by the first policy server to trigger the second policy server to establish the first policy control session. After the association, the method further includes:

If the DRA binding is an IP-CAN session per IP connection access network, and all policy control sessions of the IP-CAN session are terminated, the DRA deletes the DRA binding associated with the IP-CAN; or

If the DRA binding is per UE and all policy control sessions of the UE are terminated, the DRA deletes the DRA binding associated with the UE.

The method according to claim 1, wherein before the first policy server terminates the first policy control session with the second policy server, the method further includes:

The method according to claim 4, wherein the first policy server is directed to The second policy server sends the trigger message, and the second policy server is triggered to create the first policy control session, specifically:

The method according to any one of claims 1 to 5, wherein the first policy server is a policy and charging rule function PCRF, and the second policy server is a broadband policy control function BPCF;

When the H-PCRF and the V-PCRF terminate the S9 session, the H-PCRF notifies the visited Diameter routing agent V-DRA to delete the DRA binding; or When the H-PCRF and the V-PCRF terminate all the H-PCRFs in the S9 session requesting the sub-session created by the V-PCRF, the H-PCRF notifies the V-DRA to delete the DRA binding and the H - The PCRF triggers the V-PCRF to establish an association relationship of the messages of the S9 session.

8. The method of claim 7 wherein:

The H-PCRF carries the same session identifier and/or requests to establish a session in the message that the V-DRA deletes the DRA binding in the message that the H-PCRF triggers the V-PCRF to establish the S9 session. Identification information; or,

9. The method of claim 8 wherein:

The request to establish the session identification information is the location information of the user equipment UE accessing the broadband forum BBF access network, or the uniquely distinguishable identifier allocated by the H-PCRF, or the user identifier, or the locality of the UE IP address, or user ID and PDN ID.

10. A system for deleting binding information in a Diameter routing agent, which is applied to a network that accesses an EPS through a BBF access network, where the system includes a first policy server, a second policy server, and a DRA, wherein

The system according to claim 10, wherein the DRA receives a message that the first policy server triggers the second policy server to establish the first policy control session in the deleted DRA binding. After the notification of the association relationship, the DRA deletes the DRA An association relationship between the binding and the message that the first policy server triggers the second policy server to establish the first policy control session.

The system according to claim 11, wherein the DRA deletes a message that the first policy server triggers the second policy server to establish the first policy control session in the DRA binding. After the association, the system further includes:

13. The system according to claim 10, wherein before the first policy server terminates the first policy control session with the second policy server,

The system according to claim 13, wherein the first policy server is further configured to: notify the first policy control session trigger between the creation and the second policy server The DRA saves an association relationship between the message that the first policy server triggers the second policy server to establish the first policy control session in the DRA binding; after the first policy control session is terminated, the first policy is The server is further configured to: notify the DRA to delete an association relationship between the DRA binding and the message that the first policy server triggers the second policy server to establish the first policy control session.

The system according to any one of claims 10 to 14, wherein the first policy server is a PCRF, and the second policy server is a BPCF;

A system for deleting binding information in a Diameter routing agent, which is applied to a network that accesses an EPS through a BBF access network, the system comprising an H-PCRF and a V-PCRF, wherein the H-PCRF And, when the H-PCRF terminates the S9 session with the V-PCRF, the H-PCRF notifies the visited Diameter routing agent V-DRA to delete the DRA binding; or, is used in the H-PCRF and When the V-PCRF terminates all the H-PCRFs in the S9 session requesting the V-PCRF to create the sub-session, notifying the V-DRA to delete the DRA binding and the H-PCRF triggering the V-PCRF to establish the V-PCRF The association of messages in the S9 session.

17. The system of claim 16 wherein:

The H-PCRF is configured to carry the same session identifier and/or request in the message that the V-DRA deletes the DRA binding in the message that the H-PCRF triggers the V-PCRF to establish the S9 session. Establish session identification information; or,

And the H-PCRF is configured to carry in the message that the association between the V-DRA and the message that the H-PCRF triggers the V-PCRF to establish the S9 session is deleted in the message that the V-DRA is deleted. The H-PCRF triggers the V-PCRF to establish the same session identifier in the message of the S9 session and/or request to establish session identification information.

18. The system of claim 17 wherein:

The request to establish session identification information is location information of the UE accessing the BBF access network, or a uniquely distinguishable identifier allocated by the H-PCRF, or a user identifier, or a local IP address of the UE, or Is the user ID and PDN ID.

19. A method of creating binding information in a Diameter routing agent, the method comprising:

After the DRA creates or updates the DRA binding, the association between the DRA binding and the trigger message is saved in the DRA binding. After receiving the trigger message, the second policy server sends a request message to the first policy server to request to establish the first policy control session.

The method according to claim 19, wherein the trigger message carries a session identifier or carries an indication that the session state is not maintained.

An H-PCRF, wherein the H-PCRF is configured to notify the visited Diameter routing agent V-DRA to delete the DRA binding when the H-PCRF terminates the S9 session with the V-PCRF. ; or,