WO2011029349A1

WO2011029349A1 - Method and system for processing multiple bearer binding and event report functions

Info

Publication number: WO2011029349A1
Application number: PCT/CN2010/075388
Authority: WO
Inventors: 周晓云; 宗在峰
Original assignee: 中兴通讯股份有限公司
Priority date: 2009-09-11
Filing date: 2010-07-22
Publication date: 2011-03-17
Also published as: CN102026296A

Abstract

The present invention discloses a method for processing multiple Bearer Binding and Event Report Functions (BBERFs). The method includes: a Policy and Charging Rules Function (PCRF) receives a gateway control session termination indication message from a BBERF; and when having judged that the type of the BBERF is the primary BBERF, the PCRF initiates a gateway control session termination request to terminate all the non-primary BBERFs. The present invention also discloses a system for processing multiple BBERFs. In the system, a judgment unit is used for receiving a gateway control session termination indication message from a BBERF and judging that the type of the BBERF is a primary BBERF, and a PCRF will initiate a gateway control session termination request to terminate all the non-primary BBERFs. The method and system of the present invention implement the processing for gateway control session termination indication messages transmitted by BBERFs.

Description

Method and system for processing multi-bearer binding and event reporting function

The present invention relates to an IP-Connected Network (IP-Access) network technology, and more particularly to a method and system for processing a multi-bearer binding and event reporting function. Background technique

1 is a schematic diagram of the system architecture of an existing Evolved Packet System (EPS). As shown in FIG. 1, the EPS of the 3rd Generation Partnership Project (3GPP) includes: E-UTRAN (Evolved Universal Terrestrial Radio Access Network), Mobility Management Entity (MME), S-GW (Serving Gateway), Packet Data Network Gateway (P-GW) , Packet Data Network Gateway), Home Subscriber Server (HSS), 3GPP Authentication and Authorization Accounting (AAA) server, Policy and Charging Rules Function (PCRF) and other supporting nodes.

The MME is used for control planes such as mobility management, non-access stratum signaling processing, and user mobility management context management. The S-GW is an access gateway device connected to the E-UTRAN. The E-UTRAN and the P-GW forward data, and are responsible for buffering the paging waiting data; the P-GW is a border gateway of the EPS and the Packet Data Network (PDN), and is used for the PDN access and Forward data and other functions between EPS and PDN.

The EPS supports interworking with non-3GPP networks and implements interworking with non-3GPP networks through the S2a/b/c interface. Non-3GPP networks include trusted non-3GPP networks and untrusted non-3GPP networks. The IP access of the trusted non-3GPP network can be directly connected to the P-GW through S2a; The IP address of the untrusted non-3GPP network needs to be connected to the P-GW by the Evolved Packet Data Gateway (ePDG). The interface between the ePDG and the P-GW is S2b. The user equipment (UE, User Equipment) can also be connected to the P-GW through the S2c interface using the DSMIPv6 protocol.

If the EPS system supports the policy and charging rules of the PCRF of the Policy and Charging Control (PCC), the EPS system is connected to the service network of the operator's Internet Protocol (IP) through the receiving interface Rx. Obtaining the service information; In addition, the EPS system is connected to the gateway device in the network through the Gx/Gxa/Gxc interface, and is responsible for initiating the establishment of the IP bearer, guaranteeing the quality of service (QoS) of the service data, and performing charging. control.

The policy and charging enforcement function (PCEF, Policy and Charging Enforcement Function M is established in the P-GW, and the PCRF and the P-GW exchange information through the Gx interface. When the interface between the P-GW and the S-GW is based on the proxy mobile In the case of IP (PMIP, Proxy Mobile IP), there is a Bearer Binding and Event Report Function (BBERF) in the S-GW, and the S-GW and the PCRF exchange information through the Gxc interface. When the non-3GPP network accesses, the trusted non-3GPP access gateway also has a BBERF, and the trusted non-3GPP network access gateway exchanges information with the PCRF through the Gxa interface. When the UE roams, the home PCRF (hPCRF) and The interface of the visited PCRF (vPCRF) is an S9 interface, and the application function (AF, Application Function) for providing the service to the UE is located in the service network, and the service information for generating the PCC policy is sent to the PCRF through the Rx interface.

In the current technology, the protocol used in the PCC architecture is the Diameter application protocol developed on the basis of the Diameter Base Protocol. Example 3⁄4 port, application protocol applied to Gx interface, application protocol applied to Rx interface, application protocol of Gxx interface (including Gxa and Gxc interface), and application protocol applied to roaming interface S9. Messages, commands, and attribute value pairs (AVP, Attribute Value Pairs) for PCC are defined in these application protocols. Wait. Diameter sessions established with these protocols can be Gx sessions, Gxx sessions, Rx sessions, and S9 sessions, respectively. The PCC functional entities perform policy charging control on the PDN connection established by the UE accessing the network through these sessions. Currently, the PCC architecture has defined the Diameter application protocol used in the non-roaming scenario, for example, an application protocol applied to the Gx interface, an application protocol applied to the Rx interface, and an application protocol of the Gxx interface (including the Gxa and Gxc interfaces). Messages, commands, AVPs, etc. for the PCC are defined in these application protocols.

In the prior art, an IP-CAN session involves multiple network elements. In order to obtain policy control rules for controlling this IP-CAN session or to provide information for formulating policy control rules, each network element will establish a Diameter session with the PCRF. Thus, an IP-CAN session will be associated with multiple Diameter sessions, which are created, maintained, and deleted using the Diameter protocol.

When reselection occurs in the BBERF, for example, when the UE cross-system handover or the UE performs pre-registration across systems, the PCRF needs to control two or more BBERFs located in different systems or network elements simultaneously, one of which is called the primary BBERF (Primary BBERF), the other is called Non-Primary BBERF. The PCRF saves its QoS rules and status for each BBERF at the same time, and the operation of these BBERFs is also different. For example: When the PCRF wants to update the QoS rules, the PCRF will send the updated QoS rules to these BBERFs. If the Primary BBERF fails to install the QoS rules, the Primary BBERF reports the situation to the PCRF. The PCRF will delete the same in Non-Primary. QoS rules, and delete the corresponding PCC rules in the PCEF. If the Non-Primary BBERF fails to install the QoS rules, the Non-Primary BBERF reports the situation to the PCRF. The PCRF only updates the QoS rules and their status saved in the Non-Primary BBERF in the PCRF without performing other operations. Of course, hPCRF has other different operations for Primary BBERF and Non-Primary BBERF, and will not be described here.

2 is a flow chart of establishing an IP-CAN session for accessing an EPS through an E-UTRAN or a trusted non-3GPP access gateway in a non-roaming scenario in the prior art, assuming that When the E-UTRAN is accessed, the PMIPv6 protocol is used between the S-GW and the P-GW. When accessing through the trusted non-3GPP access gateway, the PMIPv6 protocol is used between the access gateway and the P-GW. As shown in Figure 2, the following steps are included:

Step 201: The BBERF receives the establishment of the IP-CAN session request message, and the BBERF obtains the user identifier, such as a Network Access Identity (NAI), a PDN identifier, and access information used to formulate a policy. The access information includes the network identifier of the network where the BBERF is located, the current location information of the UE, the address of the BBERF, and the IP-CAN type or RAT type.

The BBERF can be located in the S-GW or a trusted non-3GPP access gateway.

Step 202: The BBERF sends a gateway control session establishment indication message to the PCRF, where the gateway control session establishment indication message carries the user identifier, the PDN identifier, and the access information used to formulate the policy.

The Gxx session (Gxx session, also called the gateway control session) established by the gateway control session establishment indication message is called Gxx session 1.

Step 203: The PCRF saves the reported access information. According to the user identifier and the PDN identifier, interact with the SPR (Subscription Profile Repository) to obtain the subscription information of the UE, and formulate default PCC rules, QoS rules, and event triggers according to the network policy and the reported access information. . The PCRF sends a gateway control session establishment confirmation message to the BBERF, and the message carries QoS rules and event triggers for the BBERF to install QoS rules and event triggers.

Step 204: The gateway where the BBERF is located sends an IP-CAN session request message to the P-GW, where the message carries the NAI identifier of the UE, the PDN identifier, and the IP-CAN type or RAT type of the access network. The establishment of the IP-CAN session request message is an agent binding update message when implemented.

Here, step 204 can be performed simultaneously with step 202 without waiting for step 203 to return. Message.

Step 205: The P-GW allocates an IP address to the UE, and the PCEF that resides in the P-GW sends an IP-CAN session establishment indication message to the PCRF, where the message carries the user identifier, the IP address assigned to the UE, the PDN identifier, and the Develop policy access information. Here, the access information used to formulate the policy is: the IP-CAN type or the RAT type reported in step 204. The Gx session established by the IP-CAN session setup indication message is called Gx Session 1.

Step 206: The PCRF associates the Gx session 1 with the Gxx session established in step 202 (the Gxx session is also referred to as a gateway control session) according to the user identity. The PCRF sends the previously established PCC rules and event triggers to the PCEF via an IP-CAN session setup confirmation message. Since there is currently only one BBERF, the BBERF can be considered a Primary BBERF. Of course, the PCRF can also determine that the BBERF is Primary BBERF according to the IP-CAN type reported in step 205 and the IP-CAN type reported in step 202.

After receiving the acknowledgment message, the PCEF installs the issued PCC rules and event triggers, and the PCRF can also modify the established PCC rules according to the access information provided by the PCEF for formulating policies. Then, the PCRF sends the modified PCF rules. PCC rules.

Step 207: The P-GW returns an IP-CAN session response to the gateway where the BBERF is located. In implementation, the IP-CAN session response is established as a proxy binding update acknowledgement message. The establishment of the IP-CAN Session Reply message can be initiated without waiting for the acknowledgment message of step 206.

Step 208: The gateway where the BBERF is located returns to establish an IP-CAN session response.

3 is a flow chart of an IP-CAN session modification of an existing UE accessing an EPS through an E-UTRAN or a trusted non-3GPP access gateway. It is assumed that after accessing the EPS to establish an IP-CAN session as shown in FIG. 2, due to BBERF A reselection occurs, such as an IP-CAN session modification caused by a handover of the UE or a cross-system pre-registration by the UE. It is assumed that when accessing through E-UTRAN, the PMIPv6 protocol is used between the S-GW and the P-GW, and when accessing through a trusted non-3GPP access gateway, the PMIPv6 protocol is used between the access gateway and the P-GW. As shown in Figure 3, the following steps are included: Step 301: The new BBERF (New BBERF) receives the setup gateway control session request message, and the new BBERF obtains the user identifier, the PDN identifier, and the access information used to formulate the policy, and the access information includes the network identifier of the New BBERF, and the UE Current location information, IP-CAN type or IP-CAN type and RAT type of the access network.

Step 302: The new BBERF sends a gateway control session establishment indication message to the PCRF, where the gateway control session establishment indication message carries the user identifier, the PDN identifier, and the access information used for formulating the policy, and the access information includes the location of the New BBERF. The network identifier of the network, the current location information of the UE, the New BBERF address, and the IP-CAN type or IP-CAN type and RAT type of the new access network. A Gxx session established by a gateway control session establishment indication message (a Gxx session is also referred to as a gateway control session) is represented as a Gxx session 2.

Step 303: The PCRF associates the Gxx session 2 with the Subsession1 according to the user ID and the PDN identifier. The PCRF sends a Gateway Control Session Establishment Confirmation message to the New BBERF, which carries QoS rules and event triggers. The PCRF re-defines the QoS rules based on the UE's new access information. At this point, the PCRF will determine which BBERF is Primary BBERF and which is Non-primary BBERF. If the new access network IP-CAN type reported by the New BBERF in step 302 is inconsistent with the IP-CAN type of the access network on the PCEF in step 205 of FIG. 2, the PCRF determines that the New BBERF is a Non-Primary BBERF. Old BBERF is still Primary BBERF.

From this point on, the PCRF will perform different operations for Primary BBERF and Non-Primary BBERF. The process of the UE performing cross-system pre-registration ends here, and the process of UE handover continues with the following steps.

Step 304: The gateway where the new BBERF is located sends an IP-CAN session signaling message to the P-GW, where the message carries the user identifier and the PDN identifier. The message is implemented as a proxy binding update message for PMIPv6. The message carries the new access network IP-CAN type or IP-CAN type and RAT type. Step 305: The PCEF in the P-GW determines that the UE has switched according to the information such as the user identifier and the PDN identifier, and finds the context corresponding to the UE before the handover, that is, the PCC rule, the event trigger, and the like, and then passes the Gx session. The IP-CAN session modification indication message is sent to the PCRF, where the message carries the UE-switched access information, including the new access network IP-CAN type or IP-CAN type and RAT type.

Step 306: The PCRF determines, according to the access information reported by the Gx session 1 and the access network information reported by the Gxx session 1 and the Gxx session 2, that the New BBERF is Primary BBERF and the Old BBERF is Non-Primary BBERF. The new access network IP-CAN type on the PCEF in step 306 is the same as the new access network IP-CAN type reported by New BBERF in step 302. Therefore, the PCRF determines that the New BBERF is Primary BBERF, Old BBERF. For Non-Primary BBERF. The PCRF re-forms the PCC rules, QoS rules, and event triggers based on the access information reported by the New BBERF, user subscription data, and network policies. The PCRF returns an IP-CAN Session Modification Confirmation message to the PCEF carrying the updated PCC rules and event triggers.

Step 307: The P-GW returns an IP-CAN session signaling message to the gateway where the New BBERF is located, and the message is implemented as a proxy binding update acknowledgement message.

Step 308: The gateway where the New BBERF is located returns a gateway control session response message.

Step 309: The PCRF passes the updated QoS rule and event trigger through the Gxx session 2, and carries it in the gateway control and QoS rule providing message to the New BBERF.

Step 310: New BBERF installs and executes QoS rules and event triggers, and returns a confirmation message to the PCRF to return the gateway control and QoS rules.

The PCRF also sends updated QoS rules and event triggers to the Old BBERF. The PCRF sends QoS rules and event triggers to the Old BBERF via Gxx Session 1 for the Qos rules and event triggers.

In summary, in the process of BBERF reselection, PCRF controls 2 simultaneously. BBERF, and based on BBERF categories, such as Primary and Non-Primary for policy control. The prior art only discloses a processing flow for establishing a gateway control session request in a scenario where the PCRF simultaneously controls two BBERFs, and the processing flow for the gateway control session termination indication message sent by one of the BBERFs is not disclosed. In particular, in the scenario where the PCRF simultaneously controls more than two BBERFs, after the PCRF receives the gateway control session termination indication message sent by one of the BBERFs, how to deal with it is still an unsolved problem. Summary of the invention

In view of this, the main purpose of the present invention is to provide a processing method and system for multi-bearing binding and event reporting, and implement gateway control for BBERF transmission in a scenario where two or more BBERFs are simultaneously controlled by a PCRF. The processing of the session termination indication message fills the technical gap in this processing area.

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

A method for processing a multi-bearer binding and event reporting function, the method comprising: a policy and charging rule function (PCRF) receiving a bearer binding and event reporting function (BBERF) gateway control session termination indication message, when When the PCRF determines that the category of the BBERF is the primary BBERF, the PCRF will initiate a gateway control session termination request for terminating all non-primary BBERFs.

The method further includes:

The PCRF receives the gateway control session termination indication message of the first BBERF. When the PCRF determines that the first BBERF is the primary BBERF and the second BBERF is the non-primary BBERF, the PCRF initiates a gateway control session termination request for terminating the second BBERF.

After the PCRF initiates a gateway control session termination request to the second BBERF, the method further includes:

The second BBERF deletes its own related policy control information, and sends a gateway control session termination indication message to the PCRF; the PCRF deletes the second BBERF related policy control information.

In the local grooming roaming scenario, the method further includes: The vPCRF receives the gateway control session termination indication message of the first BBERF. When the vPCRF determines that the first BBERF is the primary BBERF and the second BBERF is the non-primary BBERF, the vPCRF initiates a gateway control session termination request for terminating the second BBERF.

After the vPCRF initiates a gateway control session termination request to the second BBERF, the vPCRF further includes:

The second BBERF deletes its own related policy control information, and sends a gateway control session termination indication message to the vPCRF; the vPCRF deletes the second BBERF related policy control information.

In the roaming scenario of the home routing, the method further includes:

The vPCRF receives the gateway control session termination indication message of the first BBERF, and the vPCRF sends an S9 session modification indication message to the hPCRF. When the hPCRF determines that the first BBERF is the primary BBERF and the second BBERF is the non-primary BBERF, the hPCRF will initiate the termination of the second The gateway of the BBERF controls the session termination request message, the S9 subsession or the S9 session corresponding to the initiation of the termination.

The hPCRF further determines that the current S9 sub-session corresponding to the first BBERF or the second BBERF is the last sub-session of the S9 session; the hPCRF initiates a gateway control session termination request message that terminates the second BBERF, and initiates the termination. After the corresponding S9 session, it also includes:

The hPCRF sends an S9 session termination request message to the vPCRF, and carries the session termination indication. After the vPCRF deletes all the policy control information related to the S9 session, the vPCRF sends an S9 session termination indication message to the hPCRF. The hPCRF deletes all the policy control information related to the S9 session.

The vPCRF sends a gateway control session termination request message to the second BBERF; the second BBERF deletes its own associated policy control information, and sends a gateway control session termination indication message to the vPCRF; the vPCRF deletes the second BBERF related policy control information.

When the hPCRF further determines that the current S9 sub-session corresponding to the first BBERF or the second BBERF is not the last sub-session of the S9 session, the hPCRF initiates a gateway control session termination request message for terminating the second BBERF, and initiates termination. After the S9 subsession Includes:

The hPCRF sends an S9 session modification request message to the vPCRF, and carries a session termination indication; the vPCRF deletes all policy control information related to the S9 subsession;

A processing system for multi-bearing binding and event reporting, the system comprising: a determining unit, configured to: the PCRF receives a BBERF gateway control session termination indication message, when the PCRF determines that the BBERF category is a primary BBERF The PCRF will initiate a gateway control session termination request that terminates all non-primary BBERFs.

The determining unit is further configured to: when the PCRF determines that the first BBERF is the primary BBERF and the second BBERF is the non-primary BBERF, the PCRF initiates a gateway control session termination request for terminating the second BBERF.

In the local grooming roaming scenario, the determining unit is further configured to: when the vPCRF determines that the first BBERF is the primary BBERF, and the second BBERF is the non-primary BBERF, the vPCRF initiates the termination of the second BBERF gateway control session. request.

The judging unit is further configured to: when the hPCRF determines that the first BBERF is the primary BBERF and the second BBERF is the non-primary BBERF, the hPCRF initiates the termination of the second BBERF gateway control session. Request a message, initiate a corresponding S9 subsession or an S9 session.

The PCRF of the present invention receives the gateway control session termination indication message of the BBERF. When the PCRF determines that the BBERF class is Primary BBERF, the PCRF will initiate a gateway control session termination request for terminating all other Non-Primary BBERFs.

According to the present invention, in the scenario where the PCRF simultaneously controls two or more BBERFs, the processing of the gateway control session termination indication message sent by the BBERF is implemented, thereby The PCRF is able to respond correctly to any of the BBERF's gateway control session termination indication messages. DRAWINGS

Figure 1 is a schematic diagram showing the composition of a system architecture of an existing EPS;

2 is a flow chart of establishing an IP-CAN session for an existing UE to access an EPS through an E-UTRAN or a trusted non-3GPP access gateway;

3 is a flow chart of tampering of an IP-CAN session in which an existing UE accesses an EPS through an E-UTRAN or a trusted non-3GPP access gateway;

4 is a flow chart of Embodiment 1 of a method for processing a multi-bearing binding and event reporting function according to the present invention;

FIG. 5 is a flowchart of Embodiment 3 of a method for processing a multi-bearer binding and event reporting function. detailed description

The basic idea of the present invention is: When the PCRF responds to any of the BBERF gateways to control the session termination indication message, when the PCRF determines that the BBERF class is Primary BBERF, the PCRF will initiate termination of all other Non-Primary BBERF gateway control sessions. request.

The implementation of the technical solution will be further described in detail below with reference to the accompanying drawings.

A method for processing a multi-bearer binding and event reporting function, the method includes: the PCRF receives a BBERF gateway control session termination indication message, and when the PCRF determines that the BBERF category is a primary BBERF, the PCRF initiates termination of all other non-primary The BBERF gateway controls the session termination request.

Specifically, the PCRF receives the gateway control session termination indication message of any one of the BBERFs of the two or more BBERFs. When the PCRF responds to any of the BBERF gateway control session termination indication messages, the PCRF determines the BBERF. The category is Primary BBERF, and the PCRF will initiate a gateway control session for all other Non-Primary BBERFs. End the request.

Here, the method further includes: after receiving the BBERF gateway control session termination indication message, the PCRF deletes the BBERF related policy control information.

The following describes the specific implementation process of the method of the present invention in different scenarios.

The first scenario: In a non-roaming scenario, one PCRF controls two BBERFs simultaneously.

At this time, there is only one PCRF, and it is not necessary to distinguish between hPCRF and vPCRF as in the following roaming scenario, and the PCRF initiates a gateway to control the session termination request. The method further includes the steps of:

Step 321: After receiving the gateway control session termination indication message of the first BBERF, the PCRF deletes the policy control information related to the first BBERF.

Step 322: When the PCRF determines that the first BBERF is Primary BBERF and the second BBERF is Non-Primary BBERF, the PCRF initiates a gateway control session termination request for terminating the second BBERF.

Here, after the step 322, the method further includes: after the PCRF sends the gateway control session termination request message to the second BBERF, the second BBERF deletes the related policy control information, and sends a gateway control session termination indication message to the PCRF; the PCRF deletes the second BBERF related Policy control information.

The second scenario: The UE controls the two BBERFs simultaneously in the local grooming roaming scenario.

In the local grooming roaming scenario, the vPCRF initiates a gateway to control the session termination request. The method further includes the following steps:

Step 331: After receiving the gateway control session termination indication message of the first BBERF, the vPCRF deletes the policy control information related to the first BBERF.

Step 332: When the vPCRF determines that the first BBERF is Primary BBERF, the second BBERF For Non-Primary BBERF, the vPCRF will initiate a gateway control session termination request that terminates the second BBERF.

Here, after the step 332, the method further includes: after the vPCRF sends the gateway control session termination request message to the second BBERF, the second BBERF deletes the related policy control information, and sends a gateway control session termination indication message to the vPCRF; the vPCRF deletes the second BBERF related Policy control information.

The third scenario: In the roaming scenario of the home route, the two PCRFs control the two BBERFs at the same time.

At this time, the two PCRFs are the hPCRF and the vPCRF respectively. In the roaming scenario of the home route, the hPCRF initiates the gateway to control the session termination request. The method further includes the following steps:

Step 341: After receiving the gateway control session termination indication message of the first BBERF, the vPCRF sends an S9 session modification indication message to the hPCRF. The hPCRF deletes the first BBERF address and the session termination indication carried in the S9 session modification indication message. BBERF related policy control information.

Step 342: When the hPCRF determines that the first BBERF is Primary BBERF and the second BBERF is Non-Primary BBERF, the hPCRF initiates a gateway control session termination request message for terminating the second BBERF, and initiates an S9 subsession or S9 session corresponding to the termination.

Here, when the hPCRF further determines that the current S9 sub-session corresponding to the first BBERF or the second BBERF is the last sub-session of the S9 session, the step 342 further includes:

Step 3421, the hPCRF sends an S9 session termination request message to the vPCRF, and carries the session termination indication. After the vPCRF deletes all the policy control information related to the S9 session, the SPCR session sends the S9 session termination indication message to the hPCRF. The hPCRF deletes all the policy control information related to the S9 session. .

Step 3421b: The vPCRF sends a gateway control session termination request message to the second BBERF. The second BBERF deletes the related policy control information, and sends a gateway control session termination indication message to the vPCRF. The vPCRF deletes the second BBERF related policy control information. Here, when the hPCRF further determines that the current S9 sub-session corresponding to the first BBERF or the second BBERF is not the last sub-session of the S9 session, the step 332 further includes:

Step 3422a: The hPCRF sends an S9 session modification request message to the vPCRF, and carries a session termination indication. The vPCRF deletes all policy control information related to the S9 subsession.

Step 3422b: The vPCRF sends a gateway control session termination request message to the second BBERF. The second BBERF deletes the related policy control information, and sends a gateway control session termination indication message to the vPCRF. The vPCRF deletes the second BBERF related policy control information.

In summary, the present invention mainly includes the following contents:

The PCRF receives the BBERF gateway control session termination indication message and deletes the BBERF related policy control. The PCRF determines the type of the BBERF. If the BBERF is Primary BBERF, the PCRF initiates a gateway control session for terminating all other Non-Primary BBERFs.

The invention is illustrated by way of example below.

Embodiment 1:

4 is a flowchart of a method for processing a multi-bearing binding and event reporting function according to the present invention. In this embodiment, a UE may perform a BBERF reselection process and a UE pre-registration across a system in a non-roaming scenario. It is assumed that the PCRF simultaneously controls two BBERFs, as shown by BBERF 1 and BBERF2 in Figure 4; and assumes that the UE uses the PMIPv6 protocol when accessing the EPS through the access network where BBERF 1 and BBERF2 are located.

As shown in Figure 4, the following steps are included:

Step 401: Upon receiving the trigger, BBERF1 decides to terminate its gateway control session with the PCRF. In this step, the triggering of the gateway control session of terminating BBERF1 and PCRF may come from the UE, or the P-GW, or BBERF1 itself.

Step 402: BBERF 1 sends a gateway control session termination indication message to the PCRF.

Step 403: The PCRF deletes the BBERF1 related policy control information, including the QoS rule, Event triggers, etc.

Step 404: The PCRF returns a gateway control session termination confirmation message to the BBERF1.

Step 405: If the PCRF determines that BBERF1 is Primary BBERF, the PCRF decides to initiate a gateway control session that terminates other Non-Primary BBERFs. Thus, the PCRF sends a PCRF-initiated gateway control session termination request message to BBERF2.

Step 406: After receiving the gateway control session termination request message, the BBERF2 returns an acknowledgement message to the PCRF.

Step 407: After deleting the related policy control information, the BBERF2 sends a gateway control session termination indication message to the PCRF.

Step 408: After the PCRF deletes the BBERF2 related policy control information, the PCR message returns a confirmation message to the BBERF2.

Embodiment 2:

In the local grooming roaming scenario, the BBERF reselection process, the UE cross-system pre-registration process, the multi-bearer binding, and the event reporting function, the gateway control session termination process is similar to the non-roaming scenario, except that the embodiment is First, the PCRF initiates a gateway to control the session termination request. In this embodiment, the vPCRF initiates a gateway to control the session termination request. At this time, the PCRF in FIG. 4 serves as a vPCRF. When the vPCRF receives the gateway control session termination indication message sent by the BBERF1, if the vPCRF determines that the BBERF1 is the Primary BBERF, the vPCRF decides to initiate a gateway control session for terminating the other Non-Primary BBERF. Thus, the vPCRF sends a PCRF initiated gateway control session termination request message to BBERF2.

Embodiment 3:

FIG. 5 is a flowchart of a method for processing a multi-bearing binding and event reporting function according to the present invention. In this embodiment, the UE may perform the BBERF re-selection process and the UE cross-system pre-registration after the home routing roaming scenario. It is assumed that the hPCRF controls two BBERFs simultaneously, such as BBERF1 and BBERF2 in Figure 5; and the UE accesses through the access network where BBERF1 and BBERF2 are located. The EPS is used in the PMIPv6 protocol.

As shown in Figure 5, the following steps are included:

Step 501: The BBERF1 receives the trigger and decides to terminate its gateway control session with the vPCRF. Among them, BEERF 1 is the visited place BBERF.

In this step, the triggering of the gateway control session of terminating BBERF1 and vPCRF may come from

UE, or P-GW, or BBERFl itself.

Step 502: The BBERF1 sends a gateway control session termination indication message to the vPCRF.

Step 503: The vPCRF finds an S9 session corresponding to the gateway control session and a subsession (Subsession1) of the corresponding S9 session. The vPCRF sends an S9 session modification indication message to the hPCRF, and carries the BBERF1 address and the session termination indication in the Subsessinl. The BBERFl address and session termination indication are carried at the S9 subsession level. The session termination indication indicates that the visited gateway control session is terminated.

Step 504: The hPCRF deletes the BBERF1 related policy control information, including the QoS rule, the event trigger, and the like according to the BBERF1 address and the session termination indication.

Step 505: The hPCRF returns an S9 session modification confirmation message to the vPCRF.

Step 506: The vPCRF deletes the BBERF1 related policy control information and returns a gateway control session termination confirmation message to the BBERF1.

Here, if the hPCRF determines that BBERF1 is Primary BBERF, the hPCRFPCRF decides to initiate a gateway control session for terminating other Non-Primary BBERFs and a corresponding S9 subsession or S9 session. If Subsession1 corresponding to BBERF 1 or BBERF2 is the last subsession of the S9 session, go to Step 507 to Step 510. Otherwise, go to Step 511 to Step 512.

Step 507: The hPCRF sends an S9 session termination request initiated by the hPCRF to the vPCRF, and carries a session termination indication at the command level.

Step 508: The vPCRF returns an acknowledgement message to the hPCRF.

Step 509: After the vPCRF deletes all policy control information related to the S9 session, the hPCRF is sent to the hPCRF. Send an S9 session termination indication message.

Step 510: The hPCRF deletes all related policy control information and returns an acknowledgement message. Step 511: The hPCRF sends an S9 session modification request message to the vPCRF, and carries a session termination indication in the Subsession1.

Step 512: After the vPCRF deletes the policy control information related to Subsession1, the vPCRF returns an acknowledgement message to the hPCRF.

Step 513: The vPCRF decides to initiate a gateway control session that terminates other Non-Primary BBERFs. Thus, the vPCRF sends a PCRF initiated gateway control session termination request message to BBERF2.

Step 514: After receiving the request message, the BBERF2 returns a gateway control session termination confirmation message to the vPCRF.

Step 515: After deleting the related policy control information, the BBERF2 sends a gateway control session termination indication message to the vPCRF.

Step 516: After the vPCRF deletes the BBERF2 related policy control information, it returns a confirmation message to BBERF2.

A processing system for multi-bearing binding and event reporting, the system comprising a judging unit, a judging unit, configured to send a BBERF gateway control session termination indication message by the PCRF, and when the PCRF determines that the BBERF category is a Primary BBERF, the PCRF A gateway control session termination request that terminates all other Non-Primary BBERFs will be initiated.

Here, the system further includes a deleting unit, and the deleting unit is configured to receive the BBERF gateway control session termination indication message by the PCRF, and delete the BBERF related policy control information.

In different scenarios, the specific implementation of each unit in the system is different, as explained below. The first scenario: In a non-roaming scenario.

At this time, the deleting unit is further configured to delete the first BBERF-related policy control information after the PCRF receives the gateway control session termination indication message of the first BBERF. The judging unit is further configured to: when the PCRF determines that the first BBERF is a Primary BBERF, and the second BBERF is a Non-Primary BBERF, the PCRF initiates a gateway control session termination request for terminating the second BBERF.

The second scenario: in a localized roaming scenario.

At this time, the deleting unit is further configured to: after the vPCRF receives the gateway control session termination indication message of the first BBERF, delete the first BBERF related policy control information.

The judging unit is further configured to: when the vPCRF determines that the first BBERF is Primary BBERF, and the second BBERF is Non-Primary BBERF, the vPCRF initiates a gateway control session termination request for terminating the second BBERF.

The third scenario: Under the roaming scenario of home routing.

At this time, the deleting unit is further configured to: after the vPCRF receives the gateway control session termination indication message of the first BBERF, the vPCRF sends an S9 session modification indication message to the hPCRF; the hPCRF receives the first BBERF address and the session termination carried in the S9 session modification indication message. Instruct to delete the first BBERF related policy control information.

The judging unit is further configured to: when the hPCRF determines that the first BBERF is a Primary BBERF, and the second BBERF is a Non-Primary BBERF, the hPCRF initiates a gateway control session termination request message for terminating the second BBERF, and initiates an S9 subsession corresponding to the termination or S9. Conversation.

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

Claims

Claim

A method for processing a multi-bearer binding and event reporting function, the method comprising: a policy and a charging rule function (PCRF) receiving a bearer binding and an event reporting function

The (BBERF) gateway controls the session termination indication message. When the PCRF determines that the BBERF class is the primary BBERF, the PCRF will initiate a gateway control session termination request for terminating all non-primary BBERFs.

2. The method according to claim 1, wherein in the non-roaming scenario, the method further comprises:

The method of claim 2, after the PCRF initiates a gateway control session termination request to the second BBERF, the method further includes:

The method according to claim 1, wherein in the local grooming roaming scenario, the method further comprises:

The vPCRF receives the gateway control session termination indication message of the first BBERF. When the vPCRF determines that the first BBERF is the primary BBERF and the second BBERF is the non-primary BBERF, the vPCRF initiates a gateway control session termination request for terminating the second BBERF.

The method according to claim 4, wherein after the vPCRF initiates a gateway control session termination request to the second BBERF, the method further includes:

6. The method according to claim 1, wherein the roaming scene of the home route is Next, the method further comprises:

The method according to claim 6, wherein when the hPCRF further determines that the current S9 sub-session corresponding to the first BBERF or the second BBERF is the last sub-session of the S9 session; the hPCRF will initiate termination After the gateway control session termination request message of the second BBERF and the S9 session corresponding to the initiation of the termination, the method further includes:

The method according to claim 6, wherein when the hPCRF further determines that the current S9 sub-session corresponding to the first BBERF or the second BBERF is not the last sub-session of the S9 session, the hPCRF will initiate termination. After the BBERF gateway controls the session termination request message and initiates the termination of the corresponding S9 sub-session, the method further includes:

9. A processing system for multi-bearing binding and event reporting, characterized in that the system The method includes: a judging unit, configured to send, by the PCRF, a gateway control session termination indication message of the BBERF, when the PCRF determines that the category of the BBERF is a primary BBERF, the PCRF initiates termination of a gateway control session of all non-primary BBERFs. request.

The system according to claim 9, wherein, in the non-roaming scenario, the determining unit is further configured to: when the PCRF determines that the first BBERF is a primary BBERF, and the second BBERF is a non-primary BBERF, the PCRF A gateway control session termination request that terminates the second BBERF will be initiated.

The system according to claim 9, wherein, in the local grooming roaming scenario, the determining unit is further configured to: when the vPCRF determines that the first BBERF is the primary BBERF, and the second BBERF is the non-primary BBERF The vPCRF will initiate a gateway control session termination request that terminates the second BBERF.

The system according to claim 9, wherein, in the roaming scenario of the home routing, the determining unit is further configured to: when the hPCRF determines that the first BBERF is the primary BBERF, and the second BBERF is the non-primary BBERF The hPCRF will initiate a gateway control session termination request message for terminating the second BBERF, and initiate an S9 subsession or S9 session corresponding to the termination.