WO2012028044A1

WO2012028044A1 - Method and system for processing ifom error

Info

Publication number: WO2012028044A1
Application number: PCT/CN2011/077638
Authority: WO
Inventors: 周星月; 周晓云
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-08-30
Filing date: 2011-07-26
Publication date: 2012-03-08
Also published as: CN102387063A; CN102387063B

Abstract

Disclosed are a method and system for processing an IP Flow Mobility (IFOM) error. The method includes: after a User Equipment (UE) and a network side complete routing rules negotiation on flow migration, if a Quality of Service (QoS) resource management related failure occurs on the network side, a Policy and Charging Rules Function (PCRF) informing a Home Agent (HA) of the UE of information about flow migration that failed, and triggering a processing operation for the failure. The present invention solves the problem that in an IFOM process in the prior art, when application for resources for a migrated flow fails, the QoS of the migrated service flow cannot be guaranteed, or even the service is interrupted. Therefore, service continuity is guaranteed, and quality of user experience is guaranteed.

Description

Method and system for processing when error occurs

The present invention relates to an IP flow migration (IFOM) technology in the field of communications, and more particularly to a method and system for processing an IFOM error. Background technique

The Evolved Packet System (EPS) of the 3rd Generation Partnership Project (3GPP) is shown in Figure 1. Figure 1 is an EPS network architecture diagram of a non-roaming scenario. E-UTRAN (Evolved Universal Terrestrial Radio Access Network), Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (P- GW, Packet Data Network Gateway), Home Subscriber Server (HSS), Policy and Charging Rules Function (PCRF) and other supporting nodes.

The application function entity (AF, Application Function) provides access points for service applications. The network resources used by these service applications require dynamic policy control. When performing parameter negotiation on the service side, the AF passes the relevant service information to the PCRF. If the service information is consistent with the policy of the PCRF, the PCRF accepts the negotiation; otherwise, the PCRF rejects the negotiation and simultaneously gives the business parameters acceptable to the PCRF in the feedback. The AF can then return these parameters to the user equipment (UE, User Equipment). The interface between AF and PCRF is the Rx interface.

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, including traffic data flow detection, Gating Control, Quality of Service (QoS) control, and data flow based charging rules. PCRF The policy and charging rules are sent to the Policy and Charging Enforcement Function (PCEF). At the same time, the PCRF also needs to ensure that these rules are consistent with the user's subscription information. The basis for formulating the policy and charging rules by the PCRF includes: obtaining information related to the service from the AF; obtaining the subscription information with the user policy charging control from the SPR (Spread Profile Repository); and obtaining the information related to the bearer related network from the PCEF .

The PCEF is usually located in the gateway (GW, GateWay) and performs the policy and charging rules defined by the PCRF on the bearer plane. The PCEF detects the service data flow according to the service data flow filter in the rule sent by the PCRF, and then executes the policy and charging rules formulated by the PCRF for these service data flows. When the bearer is established, the PCEF performs QoS authorization according to the rules sent by the PCRF, and performs gate control according to the execution of the AF. According to the charging rule sent by the PCRF, the PCEF performs a corresponding service data flow charging operation, and the charging can be either online charging or offline charging. In the case of online charging, PCEF needs to perform credit management together with the Online Charging System (OCS). When offline charging, the relevant accounting information is exchanged between the PCEF and the Offline Charging System (OFCS). The interface between PCEF and PCRF is Gx interface, the interface between OCE and OCS is Gy interface, and the interface between OFCS and OFCS is Gz interface. PCEFs are generally located on the gateway of the network, such as GPRS Gateway Support Node (GGSN) in the General Packet Radio Service (GPRS, General Packet Radio Service), Intelligent Wireless Office i or Network (I-WLAN, Intelligent Packet Data Gateway (PDG) in Wireless Local Area Networks

Similar to the PCC architecture function, the Broadband Forum (BBF) proposes a broadband policy control architecture (BPCF, Centralized Deployment Functional Architecture). The main function of BPCF is to formulate corresponding strategies; Policy enforcement point (PEF, Policy Enforcement Point ) usually resides in fixed network transport equipment, such as: Broadband Access Server (BRAS, Broadband Remote Access Server) / Broadband Network Gateway (BNG, Broadband Network Gateway), executed according to the corresponding policy formulated by BPCF; AAA (Authentication Authorization and Accounting), storing user subscription information. AF develops a strategy for BPCF to provide corresponding business information. At present, the structure of BPCF is relatively rough, and relevant details are still being further developed.

The IFOM (IP Flow Mobility) technology can implement the migration of IP service flows between different access systems. The UE can modify the service flow routing path according to the network congestion status and policies to ensure communication quality and improve user experience. . For example, as shown in FIG. 2, the UE is connected to the same PDN through the 3GPP access system and the I-WLAN access system at the same time, and the service flow through the 3GPP network includes a voice IP stream, a traditional video stream, and a non-traditional video stream. The service flow of the I-WLAN access system includes a network (Web) service flow and a File Transfer Protocol (FTP) flow. When the UE moves to an area where the I-WLAN signal coverage is weak, the quality of the service stream transmitted through the I-WLAN is affected. At this time, the UE initiates an IFOM process of migrating the Web stream from the I-WLAN to the 3GPP to ensure the Web application. Transmission quality. As shown in Figure 3, after a successful migration, the path of the Web stream is changed to be transmitted from the 3GPP network.

In the process of IFOM, the UE and the network side move IPv6 through a double tunnel (DSMIPv6,

The signaling of the dual-Stack Mobile IPv6 is negotiated for the flow migration information. After the signaling negotiation is completed, the UE and the network side modify the corresponding flow migration routing rule information accordingly. At this time, the network side may apply for the network bearer resources for the migrating flow to perform QoS guarantee. If there is a failure to apply for the resource, there is no corresponding solution for how to process the service flow that has been modified by the routing rule. If it is not processed, the QoS of the migrated service flow will not be guaranteed or even the service interruption, which will make the user experience worse. Summary of the invention

In view of the above, the main purpose of the present invention is to provide a method and system for processing an IFOM error, in the process of solving the existing IFOM, in the case that the resource for the migrated stream fails, the traffic flow after the migration is caused. QoS is not guaranteed or even business interruption. In order to achieve the above object, the technical solution of the present invention is achieved as follows:

The present invention provides a method for processing an IFOM error, the method comprising:

After the negotiation between the user equipment (UE) and the network side in the IFOM process to complete the flow migration, if the quality of service (QoS) resource management related fault occurs on the network side, the policy and charging rule function entity (PCRF) will fail. The flow migration information is notified to the home agent (HA) of the UE, triggering a processing operation for the failure.

The faulty flow migration information is: routing rule information of the flow or routing rule identifier of the flow.

After the PCRF notifies the HA of the failed flow migration information to the UE, the method further includes:

The HA sends an acknowledgement message to the PCRF, and notifies the UE of the faulty flow migration information by using the binding release indication message;

The UE sends a binding release message confirmation to the HA.

After the UE sends a binding release message to the HA, the method further includes: the UE sending a binding update message to the HA, and notifying the HA to re-select a routing path for the flow corresponding to the fault;

The HA sends an IP connection access network (IP-CAN) session modification request message to the PCRF, where the routing rule information that needs to be updated is included;

The PCRF sends an IP-CAN session modification response message to the HA;

The HA sends a Binding Update Confirm message to the UE.

The rerouting path is rectified for the flow corresponding to the fault, which is specifically:

The flow corresponding to the fault is returned to the routing path before the flow migration, or a new routing path is selected for the flow corresponding to the fault, or a default path is selected for the flow corresponding to the fault.

The present invention also provides a processing system when the IFOM is in error, and the system includes: a network side, a PCRF, a UE, and a HA of the UE, where The UE and the network side, the routing rule negotiation for completing the flow migration in the IFOM process; the PCRF is configured to perform QoS resource management on the network side after the routing rule negotiation of the flow migration is completed on the UE and the network side In the case of a related fault, the faulty flow migration information is notified to the HA of the UE, and the processing operation for the fault is triggered.

The HA is further configured to: after the PCRF notifies the HA of the UE of the faulty flow migration information, the HA sends an acknowledgement message to the PCRF, and notifies the faulty flow migration information to the UE;

Correspondingly, the UE is further configured to send a binding release message acknowledgement to the HA.

The UE is further configured to: send a binding update message to the HA, and notify the HA to re-select a routing path for the flow corresponding to the fault;

Correspondingly, the HA is further used to send an IP-CAN session modification request message to the PCRF, where the routing rule information that needs to be updated is included;

The PCRF is further configured to send an IP-CAN session modification response message to the HA; the HA is further configured to send a binding update confirmation message to the UE.

The UE is further configured to notify the HA to roll back the flow corresponding to the fault to the routing path before the flow migration, or select a new routing path for the flow corresponding to the fault, or select a default path for the flow corresponding to the fault.

The IFOM error processing method and system provided by the present invention, after the routing rule negotiation of the flow migration is completed between the UE and the network side in the IFOM process, if the QoS resource management related fault occurs on the network side, the PCRF will be faulty. The flow migration information is notified to the HA of the UE, triggering a processing operation for the failure. With the present invention, in the process of solving the existing IFOM, if the resource application for the migrated flow fails, the QoS of the migrated service flow cannot be guaranteed or even the service is interrupted, and the continuity of the service is ensured. The quality of the user experience is guaranteed. DRAWINGS

1 is an EPS network architecture diagram of a non-roaming scenario in the prior art;

2 is a schematic diagram 1 of IP flow migration in the prior art;

3 is a schematic diagram 2 of IP flow migration in the prior art;

4 is a flowchart of a processing method when an IFOM error is performed according to the present invention;

FIG. 5 is a flowchart of a method for processing an IFOM error in a scenario according to Embodiment 1 of the present invention; FIG. 6 is a flowchart of a method for processing an IFOM error in a scenario according to Embodiment 2 of the present invention; Flowchart of processing method when IFOM error occurs in the scene shown. detailed description

The technical solutions of the present invention are further elaborated below in conjunction with the accompanying drawings and specific embodiments. The method for processing an IFOM error provided by the present invention, as shown in FIG. 4, mainly includes the following contents: After the routing rule negotiation (step 401) of the flow migration between the UE and the network side in the IFOM process, if the network The QoS resource management related fault occurs on the side, and the PCRF notifies the home agent (HA, Home Agent) of the faulty flow migration information, and triggers a processing operation for the fault (step 402).

The faulty flow migration information may be: a routing rule information of the flow or a routing rule ID of the flow. The processing of the fault includes: re-selecting the routing path for the flow corresponding to the fault. Specifically, the flow corresponding to the fault may be returned to the routing path before the flow migration, or a new routing path may be selected for the flow corresponding to the fault. Or select the default path for the stream corresponding to the fault.

The processing method of the above IFOM error will be further elaborated below in conjunction with a specific embodiment. The application scenario of the first embodiment of the present invention is: the UE is simultaneously connected to the 3GPP access network and the non-3GPP access network, and multiple binding relationships and multiple IP flow binding association registrations are established for the same home address (Home Address). The UE sends a binding update message to the HA, and the service flow transmitted through the non-3GPP is migrated to the 3GPP network for transmission, and the PCRF applies for the QoS of the migrated service flow. 7 The resource failed. Here, the S-GW and the P-GW in 3GPP use the S5 interface based on the Proxy Mobile IPv6 (Proxy Mobile IPv6) mobility management protocol. As shown in Figure 5, the specific process mainly includes the following steps:

Step 501: The UE currently connects to the 3GPP and the non-3GPP access network at the same time, and establishes a binding association for the service flows that belong to the same PDN connection and through different access networks, and establishes multiple binding relationships and multiple IP flows. Registration.

Step 502: The UE sends a Binding Update message to the HA, where the message carries the home address, the binding identifier, and the flow binding information of the UE. After receiving the binding update message, the HA according to the binding identifier and the flow. The binding information is used to modify the routing rule information of the corresponding service flow, where the routing rule information includes the quintuple information of the IP file and the corresponding route of the IP address.

Step 503: The P-GW (HA) sends an IP-Connectivity Access Network (IP-CAN, IP-Connectivity Access Network) session modification request message to the PCRF, where the request message includes routing rule information to be updated. Among them, P-GW (HA) is a function indicating that the P-GW includes HA, and P-GW and HA are combined.

Step 504: The PCRF sends an IP-CAN session modification response message to the P-GW.

Step 505: The HA returns a Binding Update Acknowledgement message to the UE to confirm the service flow binding operation of the UE, where the message includes a binding lifetime, a home address of the UE, and a binding identifier. , stream binding information.

Step 506: The PCRF sends a gateway control and a QoS providing message to the S-GW, where the message includes information such as a QoS rule and an event trigger.

Step 507: The S-GW sends an Update Bearer Request message to the MME, where the message includes a Process Transaction Id (PTI), an EPS bearer identifier, an EPS bearer QoS information, and a data flow template (TFT, Traffic Flow). Template ), Access Point Name - Aggregate Maximum Bit Rate (APN-AMBR). Step 508: The MME sends a session management request (bearer modification request or session modification request) message to the evolved base station (eNB, evolved NodeB), and sends the PTI, the EPS bearer identifier, the EPS bearer QoS parameter, the TFT, and the APN-AMBR to the eNB for bearer. modify.

Step 509: The eNB fails to coordinate the allocation of the QoS-related bearer resource according to the information in the received session management request message.

Step 510: The eNB sends a bearer modification response message to the MME, to notify the MME that the EPS bearer QoS requested is not allocated.

Step 511: The MME sends an update bearer response message to the S-GW, to notify the EPS bearer that the QoS assignment fails.

Step 512: The S-GW sends a gateway control and QoS rule execution response message to the PCRF, and notifies that the corresponding QoS rule of the PCRF fails to be executed.

Step 513: The PCRF sends a PCC rule providing message to the P-GW (HA) to notify the PCC that the rule execution fails. The message includes information to identify a service flow that cannot allocate the QoS resource, and the information may be a routing rule of the service flow. The rule ) information can also be the routing rule ID (requires the HA to be saved and the routing rule ID consistent on the PCRF).

Step 514, the P-GW (HA) sends an acknowledgement message to the PCRF.

Step 515: The P-GW (HA) notifies the UE of the service flow information that fails the QoS resource application, and the UE may be notified by carrying the flow binding information in the binding release indication message.

Step 516: The UE sends a binding release message confirmation to the P-GW (HA).

Step 517: The UE sends a new binding update message to the P-GW (HA) to roll back the previous service flow to the original routing path. Here, the UE's manipulation depends on the UE's local policy implementation, and the UE may also select a new routing path or select a default route for the service flow.

Step 518: The P-GW (HA) sends an IP-CAN session modification request message to the PCRF, where the request message includes routing rule information to be updated.

In step 519, the PCRF sends an IP-CAN session modification response message to the P-GW. Step 520: The P-GW (HA) sends a binding update confirmation message to the UE.

The application scenario of the second embodiment of the present invention is: the UE is simultaneously connected to the WLAN access system of the 3GPP and the BBF, and multiple binding relationships and multiple IP flow binding association registrations are established for the same home address; the UE sends the binding to the HA. The update message is used to migrate the traffic flow transmitted by the 3GPP to the BBF network, and the BPCF fails to apply for the QoS bearer resource for the migrated service flow. As shown in Figure 6, the specific process mainly includes the following steps:

Step 601: The UE is currently connected to the WLAN access system of the 3GPP and the BBF, and establishes a binding association for the service flows that belong to the same PDN connection and through different access networks, and establishes multiple binding relationships and multiple IP flows. Bind registration.

Step 602: The UE sends a Binding Update message to the HA, where the message carries the home address, the binding identifier, and the flow binding information of the UE. After receiving the binding update message, the HA binds according to the binding identifier and the flow. Determine the information and modify the routing rule information of the corresponding service flow.

Step 603: The P-GW (HA) sends an IP-CAN session modification request to the PCRF, where the request message includes routing rule information to be updated, and the like.

Step 604: The PCRF sends an IP-CAN session modification response message to the P-GW.

Step 605: The HA returns a binding update confirmation message to the UE, to confirm the service flow binding operation of the UE, where the message includes a binding lifetime, a home address, a binding identifier, and a flow binding information of the UE. .

Step 606: The PCRF sends an S9* session request message to the BPCF, where the message includes information such as a QoS rule and an event trigger.

Step 607: The BPCF fails to allocate the QoS-related bearer resource according to the information in the received session management request message in the BBF access system.

Step 608: The BPCF returns an S9* session response message to the PCRF, indicating that the QoS related resource application fails.

Step 609: The PCRF sends a PCC rule providing message to the P-GW (HA) to notify the PCC. The rule fails to be executed. The message contains information to identify the service flow that cannot allocate the QoS resource. The information may be the routing rule information of the service flow, or the routing rule ID (requires the HA to be saved and consistent on the PCRF). Routing rule ID).

Step 610: The P-GW (HA) sends an acknowledgement message to the PCRF.

Step 611: The P-GW (HA) notifies the UE of the service flow information that fails the QoS resource application, and the UE may be notified by carrying the flow binding information in the binding release indication message.

Step 612: The UE sends a binding release message confirmation to the P-GW (HA).

Step 613: The UE sends a new binding update message to the P-GW (HA), and the previous service flow is returned to the original routing path. Here, the UE's manipulation depends on the UE's local policy implementation, and the UE may also select a new routing path or select a default route for the service flow.

Step 614: The P-GW (HA) sends an IP-CAN session modification request message to the PCRF, where the request message includes routing rule information to be updated.

Step 615: The PCRF sends an IP-CAN session modification response message to the P-GW.

Step 616: The P-GW (HA) sends a binding update confirmation message to the UE.

The application scenario of the third embodiment of the present invention is: the UE is simultaneously connected to the 3GPP access network and the non-3GPP access network, and multiple binding relationships and multiple IP flow binding association registrations are established for the same home address; The binding update message is sent, and a new service flow routing rule (establishing a new service flow binding association) is transmitted in the 3GPP network, and the PCRF fails to apply for the QoS bearer resource for the new service flow. Here, the S5 interface based on the PMIPv6 mobility management protocol used by the S-GW and the P-GW in 3GPP. As shown in FIG. 7, the specific process mainly includes the following steps: Step 701: The UE currently connects to the 3GPP and the non-3GPP access network at the same time, and establishes a binding association for the service flows that belong to the same PDN connection and pass through different access networks. Multiple binding relationships and multiple IP flow binding registrations have been established.

Step 702: The UE sends a binding update (Binding Update) message to the HA, where the message carries the home address, the binding identifier, the flow binding information, and the like of the UE. After the HA receives the binding update message, Add a new service flow routing rule according to the binding identifier and the flow binding information, that is, establish a new service flow binding association.

Step 703: The P-GW (HA) sends an IP-CAN session modification request message to the PCRF, where the request message includes the routing rule information to be added.

Step 704: The PCRF sends an IP-CAN session modification response message to the P-GW.

Step 705: The HA returns a Binding Update Acknowledgement message to the UE to confirm the service flow binding operation of the UE, where the message includes a binding lifetime, a home address of the UE, and a binding identifier. , stream binding information.

Step 706: The PCRF sends a gateway control and a QoS providing message to the S-GW, where the message includes information such as a QoS rule and an event trigger.

Step 707: The S-GW sends an Update Bearer Request message to the MME, where the message includes a PTI, an EPS bearer identifier, an EPS bearer QoS information, a TFT, and an APN-AMBR.

Step 708: The MME sends a session management request (bearer modification request or session modification request) message to the eNB, and sends the PTI, the EPS bearer identifier, the EPS bearer QoS parameter, the TFT, and the APN-AMBR to the eNB for bearer modification.

Step 709: The eNB fails to coordinate the allocation of the QoS-related bearer resource according to the information in the received session management request message.

Step 710: The eNB sends a bearer modification response message to the MME, to notify the MME that the EPS bearer QoS requested is not allocated.

Step 711: The MME sends an update bearer response message to the S-GW to notify the EPS bearer that the QoS assignment fails.

Step 712: The S-GW sends a gateway control and QoS rule execution response message to the PCRF, and notifies that the corresponding QoS rule of the PCRF fails to be executed.

Step 713: The PCRF sends a PCC rule providing message to the P-GW or the HA to notify the PCC. The rule fails to be executed. The message contains information to identify the service flow that cannot allocate the QoS resource. The information may be the routing rule information of the service flow, or the routing rule ID (requires the HA to be saved and consistent on the PCRF). Routing rule ID).

Step 714, the P-GW (HA) sends an acknowledgement message to the PCRF.

Step 715: The P-GW (HA) notifies the UE of the service flow information that fails the QoS resource application, and the UE may be notified by carrying the flow binding information in the binding release indication message.

Step 716: The UE sends a binding release message confirmation to the P-GW (HA).

Step 717: The P-GW (HA) sends an IP-CAN session modification request message to the PCRF, where the request message includes routing rule information to be updated.

Step 718: The PCRF sends an IP-CAN session modification response message to the P-GW.

The present invention also provides a processing system for an IFOM error, including: a network side, a PCRF, a UE, and a UE HA. The UE and the network side are used to negotiate the routing rules for the flow migration in the IFOM process. The PCRF is used to notify the HA of the UE of the faulty flow migration information when the QoS resource management related fault occurs on the network side after the routing rule negotiation of the flow migration is performed on the UE and the network side, and triggers the processing of the fault.

Preferably, the HA is further configured to: after the PCRF notifies the HA of the faulty flow migration information to the HA of the UE, the HA sends an acknowledgement message to the PCRF, and notifies the UE of the faulty flow migration information by using the binding release indication message; Correspondingly, the UE is further configured to send a binding release message acknowledgement to the HA.

Preferably, the UE is further configured to: send a binding update message to the HA, and notify the HA to re-select the routing path for the flow corresponding to the fault;

The PCRF is further configured to send an IP-CAN session modification response message to the HA; The HA is also used to send a binding update confirmation message to the UE.

Preferably, the UE is further configured to notify the HA to roll back the flow corresponding to the fault to the routing path before the flow migration, or select a new routing path for the flow corresponding to the fault, or select a default for the flow corresponding to the fault. path.

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

1. A method for processing an IP flow migration (IFOM) error, the method comprising:

2. The method for processing an IFOM error according to claim 1, wherein the faulty flow migration information is: a routing rule information of a flow or a routing rule identifier of a flow.

The method for processing an IFOM error according to claim 1 or 2, wherein after the PCRF notifies the HA of the UE of the failed flow migration information, the method further includes:

The UE sends a binding release message confirmation to the HA.

The IFOM error processing method according to claim 3, wherein after the UE sends a binding release message confirmation to the HA, the method further includes:

Sending, by the UE, a binding update message to the HA, and notifying the HA to re-select a routing path for the flow corresponding to the fault;

The PCRF sends an IP-CAN session modification response message to the HA;

The HA sends a Binding Update Confirm message to the UE.

The IFOM error processing method according to claim 3, wherein the routing path is re-selected for the flow corresponding to the fault, specifically: The flow corresponding to the fault is returned to the routing path before the flow migration, or a new routing path is selected for the flow corresponding to the fault, or a default path is selected for the flow corresponding to the fault.

6. A processing system for an IFOM error, the system comprising: a network side, a PCRF, a UE, and a UE HA, where

The UE and the network side, the routing rule negotiation for completing the flow migration in the IFOM process; the PCRF is configured to perform QoS resource management on the network side after the routing rule negotiation of the flow migration is completed on the UE and the network side In the case of a related fault, the faulty flow migration information is notified to the HA of the UE, and the processing operation for the fault is triggered.

The IFOM error processing system according to claim 6, wherein the faulty flow migration information is: a routing rule information of a flow or a routing rule identifier of a flow.

The IFOM error processing system according to claim 6 or 7, wherein the HA is further configured to send the HA to the PCRF after the PCRF notifies the HA of the failed flow migration information to the UE Acknowledge the message, and notify the UE of the failed flow migration information by using the binding release indication message;

The IFOM error processing system according to claim 8, wherein the UE is further configured to: send a binding update message to the HA, and notify the HA to re-select a routing path for the flow corresponding to the fault;

The IFOM error processing system according to claim 8, wherein the UE is further configured to notify the HA to roll back the flow corresponding to the fault to the routing path before the flow migration, or to the fault. Stream selects a new routing path, or a stream corresponding to the fault 16