WO2011006395A1 - Procédé de synchronisation et système de gestion de défaut partiel - Google Patents

Procédé de synchronisation et système de gestion de défaut partiel Download PDF

Info

Publication number
WO2011006395A1
WO2011006395A1 PCT/CN2010/073062 CN2010073062W WO2011006395A1 WO 2011006395 A1 WO2011006395 A1 WO 2011006395A1 CN 2010073062 W CN2010073062 W CN 2010073062W WO 2011006395 A1 WO2011006395 A1 WO 2011006395A1
Authority
WO
WIPO (PCT)
Prior art keywords
mme
pfh
bearer
new
pdn connection
Prior art date
Application number
PCT/CN2010/073062
Other languages
English (en)
Chinese (zh)
Inventor
卢飞
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2011006395A1 publication Critical patent/WO2011006395A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information

Definitions

  • the present invention relates to fault handling techniques in the field of communications, and more particularly to a method and system for synchronizing partial faults. Background technique
  • the architecture of the current SAE is as shown in FIG. 1.
  • the network element included in the evolved radio access network is an evolved Node B (eNodeB, Evolved NodeB), which is used for user connection.
  • eNodeB Evolved NodeB
  • Incoming to provide wireless resources Packet Data Network (PDN) is a network that provides services for users;
  • EPC provides lower latency and allows more wireless access systems to access, including the following network elements:
  • Mobility Management Entity Control plane functional entity, A server that temporarily stores user data, and is responsible for managing and storing the context of the user equipment (UE, User Equipment) (such as UE/user identity, mobility management state, user security parameters, etc.), and assigning a temporary identifier to the user, when the UE is camped on the UE When tracking the area or the network, it is responsible for authenticating the user; processing all non-access stratum messages between the MME and the UE; triggering paging at the SAE.
  • the MME is a mobility management entity of the SAE system. In the Universal Mobile Telecommunications System (UMTS), the mobility management entity is a GPRS (General Packet Radio Service) support node (SGSN, Serving GPRS Support Node). ).
  • GPRS General Packet Radio Service
  • the Serving Gateway is a user plane entity responsible for user plane data routing processing and terminating downlink data of UEs in idle (ECM_IDLE) state. Manage and store the SAE bearer context of the UE, such as IP bearer service parameters and intranet routing information.
  • the S-GW is the anchor point of the internal user plane of the 3GPP system. A user can only have one S-GW at a time.
  • the packet data network gateway (P-GW, PDN Gateway) is the gateway responsible for the UE accessing the PDN, assigns the user IP address, and is also the mobility anchor of the 3GPP and non-3GPP access systems.
  • the function of the P-GW also includes the policy implementation. , billing support. Users can access multiple P-GWs at the same time.
  • the Policy and Charging Enforcement Function (PCEF) is also located in the P-GW.
  • the Policy and Charging Rules Function (PCRF) is responsible for providing policy control and charging rules to the PCEF.
  • the home subscriber server permanently stores the user subscription data.
  • the content stored in the HSS includes the UE's International Mobile Subscriber Identification (IMSI) and the IP address of the P-GW.
  • IMSI International Mobile Subscriber Identification
  • the S-GW and the P-GW may be unified.
  • the EPC system user plane network element includes an S-GW and a P-GW.
  • the current EPS system introduces the function of Partial Failure Handling (PFH).
  • the partial fault handling is the PDN that the MME and S-GW need to create for the UE when the UE initially attaches or performs mobility management.
  • the connection is associated with the respective associated Full PDN Connection Set ID (FQ-CSID, Fully Qualified PDN Connection Set Identity), and the respective associated FQ-CISD is sent to the P-GW.
  • FQ-CSID Full PDN Connection Set ID
  • FQ-CSID Fully Qualified PDN Connection Set Identity
  • Step 201 The UE sends an Attach request to the MME, requesting registration in the E-UTRAN network, where the request message carries the IMSI of the UE or the Globally Unique Temporary Identity (GUTI).
  • GUI Globally Unique Temporary Identity
  • Step 202 The MME sends a location update request message to the HSS, where the request message carries
  • Step 203 The HSS sends a location update acknowledgement message to the MME, where the acknowledgement message carries user data of the UE.
  • Step 204 After obtaining the user data of the UE, the MME sends a setup session request message to the S-GW, requesting to establish a default bearer, where the request message carries the control plane address of the P-GW, and the quality of service (QoS, Quality of Service) of the default bearer. If the MME supports the PFH function, you need to associate the bearer ID of the default bearer with the MME-FQ-CSID. And pass the MME-FQ-CSID to the S-GW.
  • QoS Quality of Service
  • Step 205 The S-GW sends a setup session request message to the P-GW, where the request message carries
  • TEID User plane address and user plane tunnel endpoint identifier
  • control plane address of the P-GW control plane address of the P-GW
  • QoS of the default bearer APN-AMBR
  • Bearer ID If the S-GW supports the PFH function, The bearer ID of the default bearer needs to be associated with the S-GW-FQ-CSID and sent to the P-GW from the received MME-FQ-CSID.
  • Step 206 The P-GW sends a session establishment response message to the S-GW, where the response message carries The TEID of the P-GW control plane, the user plane address of the P-GW, and the TEID, Bearer ID, and the traffic flow template (TFT, Traffic Flow Template). If the P-GW supports the PFH function, the bearer ID of the default bearer needs to be associated. To the P-GW-FQ-CSID, and send the associated P-GW-FQ-CSID to the S-GW.
  • TFT Traffic Flow Template
  • Step 207 The S-GW sends a session establishment response message to the MME, where the response message carries the TEID of the S-GW control plane, the user plane address of the S-GW, the TEID, the Bearer ID, the uplink TFT, and the S-GW-FQ-CSID. P-GW-FQ-CSID.
  • Step 208 The MME sends an Attach Accept message to the eNodeB, where the message carries a GUTI, a Tracking Area List (TA list, Tracking Area list), a Bearer ID, and a session management configuration information unit.
  • the session management configuration information element includes an uplink TFT and a bearer QoS. .
  • Step 209 The eNodeB sends an RRC connection reconfiguration message to the UE, where the message carries the radio bearer ID, and the eNodeB sends the Attach accept message to the UE together.
  • Step 210 The UE sends an RRC connection reconfiguration complete message to the eNodeB, where the message carries the bearer ID.
  • Step 211 The eNodeB sends an Attach Complete message to the MME.
  • Step 212 The MME sends an update bearer request message to the S-GW, where the request message carries the user plane address and the TEID of the eNodeB.
  • Step 213 The S-GW sends an update bearer response message to the MME.
  • the UE When the coverage area of the UE changes, and the device is found to be in an unregistered TA list area by listening to the broadcast channel, the UE initiates an operation of Tracking Area Update (TAU), as shown in FIG. 3 (assuming the UE)
  • TAU Tracking Area Update
  • MME, S-GW, and P-GW All support the PFH function.
  • Step 301 The UE moves to the new TA list area, and sends a tracking area update request to the new MME, requesting to register in the new area, and the request message carries the GUTI allocated by the old MME for the UE.
  • Step 302 The new MME finds the old MME according to the GUTI identifier, and sends a context request signaling to perform a context acquisition process.
  • Step 303 The old MME sends the mobility management and the seven-load information of the user to the new MME, that is, performs a context response.
  • Step 304 After receiving the context response message, the new MME confirms the context, that is, the context confirmation.
  • Step 305 The new MME initiates an update bearer request to the S-GW, where the request message carries the source general wireless packet service tunneling protocol control (GTP-C, GPRS Tunnel Protocol-Control Plane) tunnel identifier and the destination GTP-C tunnel identifier, S-
  • the GW updates the binding relationship; if the new MME supports the PFH function, the Bearer ID of the default bearer needs to be associated with the MME-FQ-CSID and sent to the S-GW.
  • GTP-C general wireless packet service tunneling protocol control
  • Step 306 The S-GW sends an update bearer request to the P-GW, and sends the S-GW address information, the tunnel identifier information, and the location information of the UE to the P-GW.
  • the S-GW needs to acquire the new associated MME.
  • - FQ-CSID is sent to the P-GW.
  • Step 307 The P-GW updates its own context and returns update bearer response information to the S-GW.
  • the S-GW also needs to send its stored S-GW-FQ-CSID, P-GW-FQ-CSID to the new MME.
  • Step 309 the new MME notifies the HSS of the change of the registration location by the location update message.
  • Step 310 The HSS sends location cancellation signaling to the old MME to maintain only the registration of the new MME.
  • Step 311 The old MME returns a location cancellation response to the HSS.
  • Step 312 the HSS confirms the location update of the new MME.
  • Step 313 If the new MME confirms that the UE is valid in the current tracking area, send a tracking area update accept message to the UE.
  • Step 314 If the new MME allocates a new GUTI identifier to the UE through the TAU procedure, the UE returns a tracking area update complete message to confirm to the new MME.
  • the S-GW updates the MME-FQ-CSID through the update bearer request in step 305, and the S-GW sends the new MME-FQ-CSID to the P-GW in step 306.
  • the original MME-CSID needs to be replaced with the new MME-FQ-CSID to prevent the resources from being correctly released when a partial fault occurs.
  • the new MME/SGSN does not support the PFH function, the S-GW or the P-GW cannot update the corresponding associated FQ-CSID, which may result in the S-GW or the P-GW failing to correctly release the PDN connection corresponding to the corresponding FQ-CSID.
  • the main purpose of the present invention is to provide a method and system for synchronizing partial faults, so as to correctly release the corresponding PDN connection resources of the S-GW or the P-GW when the new MME does not support the PFH function. .
  • the present invention provides a synchronization method for partial fault processing, the method comprising:
  • the new MME When the user terminal (UE) moves to the new mobility management entity (MME), the new MME sends its partial fault processing (PFH) capability information to the old MME during context transfer;
  • PHF partial fault processing
  • the old MME initiates an association synchronization operation of the PFH to the serving gateway (S-GW) and the packet data network gateway (P-GW) when determining that the new MME does not support the PFH function according to the received PFH capability information.
  • the association synchronization operation of the PFH is specifically:
  • the old MME deletes the bearer ID (Bearer ID) of the default bearer of the packet data network (PDN) connection to be released from the MME-FQ-CSID stored by itself, and sends a release PDN connection set to the S-GW. Requesting a message to perform PFH synchronization, where the request message carries the The default 7-bearing Bearer ID of the PDN connection to be released;
  • the S-GW deletes the Bearer ID of the default bearer of the PDN connection to be released from the MME-FQ-CSID and the S-GW-FQ-CSID stored by the S-GW, and sends a release PDN connection set to the P-GW.
  • the request message performs PFH synchronization, where the request message carries the default 7-bearing Bearer ID of the PDN connection to be released;
  • the P-GW deletes the Bearer ID of the default bearer of the PDN connection to be released from the MME-FQ-CSID, S-GW-FQ-CSID, and P-GW-FQ-CSID stored by the P-GW, and passes the S- The GW returns a release PDN connection set request response message to the old MME.
  • the method further includes: sending, by the new MME, the PFH capability information of the MME to the old MME by using the context confirmation message.
  • the method further includes: sending, by the new MME, the PFH capability information of the new MME to the old MME by using the context request signaling.
  • the method further includes: sending, by the new MME, the PFH capability information of the new MME to the old MME by using the node re-allocation response message.
  • the method further includes: the old MME transmitting its own PFH capability information to the new MME in the process of performing context transfer; the new MME determining, according to the PFH capability information of the old MME, whether to send the PFH capability information of the new MME to the The old MME is described.
  • the present invention also provides a synchronization system for partial fault processing, the system comprising: a new MME and an old MME, an S-GW, and a P-GW, where
  • the new MME is configured to send its PFH capability information to the old MME during the context transfer process when the UE moves to the new MME;
  • the old MME is configured to initiate, according to the received PFH capability information, an association synchronization operation of the PFH to the S-GW and the P-GW when determining that the new MME does not support the PFH function; the S-GW and the P - GW is used to perform the association synchronization operation of the PFH.
  • the old MME is further configured to: the default bearer of the PDN connection to be released
  • the ID is deleted from the MME-FQ-CSID that is stored in the MME-FQ-CSID, and sends a PDN connection set request message to the S-GW to perform PFH synchronization.
  • the request message carries the default 7-load of the PDN connection to be released. Bearer ID;
  • the S-GW is further configured to delete the Bearer ID of the default bearer of the PDN connection to be released from the MME-FQ-CSID and the S-GW-FQ-CSID stored by the S-GW, and to the P - GW sends a release PDN connection set request message to perform PFH synchronization, and the request message carries a Bearer ID of the default bearer of the PDN connection to be released;
  • the P-GW is further configured to delete the Bearer ID of the default bearer of the PDN connection to be released from the MME-FQ-CSID, the S-GW-FQ-CSID, and the P-GW-FQ-CSID stored by the P-GW. And returning the release PDN connection set request response message to the old MME through the S-GW.
  • the new MME is further configured to send, by using a context acknowledgement message, or a context request signaling, or a node reassignment response message, its own PFH capability information to the old MME during context transfer.
  • the old MME is further configured to send its own PFH capability information to the new MME during context transfer;
  • the new MME is further configured to: determine, according to the PFH capability information of the old MME, whether to send the PFH capability information of the new MME to the old MME.
  • the method and the system for synchronizing the partial faults provided by the present invention, when the UE moves to the new MME, the new MME sends its own PFH capability information to the old MME during the context transfer process;
  • the PFH capability information when determining that the new MME does not support the PFH function, initiates an association synchronization operation of the PFH to the S-GW and the P-GW.
  • the S-GW or the P-GW can synchronize the PDN connection associated with the FQ-CSID, so that the corresponding PDN connection resources of the S-GW or the P-GW can be correctly released.
  • 1 is a schematic structural diagram of a SAE in the prior art
  • 2 is a flow chart of partial fault processing in the prior art
  • FIG. 4 is a flowchart of a method for synchronizing partial fault processing according to the present invention.
  • FIG. 5 is a flowchart of a method for synchronizing partial fault processing according to Embodiment 1 of the present invention
  • FIG. 6 is a flowchart of a method for synchronizing partial fault processing according to Embodiment 2 of the present invention
  • FIG. 7 is a partial fault processing method according to Embodiment 3 of the present invention
  • FIG. 8 is a flowchart of a method for synchronizing partial fault processing according to Embodiment 4 of the present invention
  • FIG. 9 is a schematic structural diagram of a synchronization system for partial fault processing according to the present invention.
  • the present invention provides a synchronization method for partial fault processing.
  • the new MME transmits its own PFH capability to the old MME during context transfer; if the old MME learns the new MME If the PFH function is not supported, the old MME initiates the association operation of the PFH to the S-GW and the P-GW.
  • Step 401 The UE moves to the coverage area of the new MME, and the new MME needs to perform a context acquisition process with the old MME, in the process, the new The MME notifies the old MME of its own PFH capability (whether or not the PFH function is supported).
  • the S-GW sends a release PDN connection set request message for PFH synchronization; the request message includes the IMSI of the UE, and the PDN connection to be released The default bearer ID of the bearer.
  • Step 404 The S-GW deletes the Bearer ID of the default bearer of the PDN connection to be released from the MME-FQ-CSID and the S-GW-FQ-CSID stored by the S-GW, and sends a request for releasing the PDN connection set to the P-GW.
  • the message is PFH-synchronized; the request message includes an IMSI, and a Bearer ID of the default bearer of the PDN connection to be released.
  • Step 405 The P-GW deletes the Bearer ID of the default bearer of the PDN connection to be released from the MME-FQ-CSID, the S-GW-FQ-CSID, and the P-GW-FQ-CSID stored by the P-GW, and sends the S - GW returns a release PDN connection set request response message.
  • Step 406 The S-GW returns a release PDN connection set request response message to the old MME.
  • Step 406 it mainly includes the following steps:
  • Step 501 The UE moves to a new TA list area, and sends a tracking area update request to the new MME, requesting to register in a new area, where the request message carries the GUTL allocated by the old MME for the UE.
  • Step 502 The new MME finds the old MME according to the GUTI identifier, and sends a context request signal to perform a context acquisition process.
  • Step 503 The old MME sends the user's mobility management and the data to the new MME, and carries the PFH capability (whether the PFH function is supported) information in the returned context response message.
  • Step 504 After receiving the context response message, the new MME confirms the context, that is, the context confirmation.
  • the new MME carries its own PFH capability (whether the PFH function is supported) information in the context confirmation message.
  • the old MME sends its own PFH capability information to the new MME, and the new MME can control the transmission of the PFH capability information of the new MME according to the PFH capability information of the old MME, that is, if it is determined that the old MME supports the PFH function, The new MME needs to be itself
  • the PFH capability information is sent to the old MME for use by the old MME to perform subsequent PFH association synchronization operations. If it is determined that the old MME does not support the PFH function, then there is no subsequent PFH association synchronization operation, so that the new MME does not need to Its own PFH capability information is sent to the old MME.
  • Step 505 The new MME initiates an update bearer request to the S-GW, where the request message carries the source GTP-C tunnel identifier and the destination GTP-C tunnel identifier, and the S-GW updates the bearer binding relationship; if the new MME supports the PFH function, The Bearer ID of the default bearer needs to be associated with the MME-FQ-CSID and sent to the S-GW.
  • Step 506 The S-GW sends an update bearer request to the P-GW, and sends the S-GW address information, the tunnel identifier information, and the location information of the UE to the P-GW.
  • the S-GW needs to obtain the new associated MME.
  • - FQ-CSID is sent to the P-GW.
  • Step 507 The P-GW updates its own context and returns an update bearer response information to the S-GW.
  • the S-GW also needs to send its stored S-GW-FQ-CSID, P-GW-FQ-CSID to the new MME.
  • Step 509 The new MME notifies the HSS of the change of the registration location by using the location update message.
  • the old MME returns a location cancellation response to the HSS.
  • Step 512 the HSS confirms the location update of the new MME.
  • Step 513 If the new MME confirms that the UE is valid in the current tracking area, send a tracking area update accept message to the UE.
  • Step 514 If the new MME allocates a new GUTI identifier to the UE through the TAU procedure, the UE returns a tracking area update complete message to confirm to the new MME.
  • Step 515 if the new MME does not support the PFH function, the old MME needs to be associated with the S-GW,
  • the P-GW performs a PFH association synchronization process.
  • the PFH association synchronization process is shown in Figure 4 and will not be described here.
  • the new MME sends its own PFH capability information to the old MME through the context confirmation message in the case of determining that the old MME supports the PFH function.
  • Figure 6 shows the second embodiment of the synchronization method for partial fault processing applied to the actual TAU process, which mainly includes the following steps:
  • Step 601 The UE moves to a new TA list area, and sends a tracking area update request to the new MME, requesting to register in a new area, where the request message carries the GUTL allocated by the old MME for the UE.
  • Step 602 The new MME finds the old MME according to the GUTI identifier, sends a context request signal to perform a context acquisition process, and carries the PFH capability of the new MME (whether the PFH function is supported) information in the context request signaling.
  • the new MME does not need to confirm whether the old MME supports the PFH function, and directly sends its own PFH capability information to the old MME, and hands over the initiative of the PFH association synchronization operation to the old MME, that is, if the old MME supports the PFH function, Then, when determining that the new MME does not support the PFH function according to the PFH capability information of the new MME, the PFH association synchronization operation needs to be performed; if the old MME does not support the PFH function, the old MME does not need to perform the PFH association synchronization operation, thereby eliminating the need for the new MME.
  • the transmitted PFH capability information is processed.
  • Step 603 The old MME sends the mobility management and the 7-load information of the user to the new MME.
  • steps 605-614 are similar to the operations of steps 505-514 in FIG. 5, and are not described here.
  • Step 615 If the new MME does not support the PFH function, the old MME needs to perform a PFH association synchronization process with the S-GW and the P-GW.
  • the PFH association synchronization process is shown in Figure 4, and is no longer here.
  • the new MME sends the PFH capability information of the new MME to the old MME through the context request signaling, whether the old MME supports the PFH function.
  • the embodiment mainly includes the following steps:
  • Step 701 The original eNodeB decides to initiate a handover between the eNodeB and the core network node to the new eNodeB.
  • Step 702 The original eNodeB sends a handover request message to the old MME.
  • Step 703 The old MME selects a new MME according to the MME selection function, and sends a node re-allocation request message to the new MME, where the message includes the address of the P-GW and the uplink TEID, the address of the S-GW, and the uplink TEID, and the old MME is
  • the redistribution request message carries its own PFH capability (whether the PFH function is supported).
  • Step 704 The new MME sends a handover request message to the new eNodeB, requesting to establish a UE context in the new eNodeB.
  • Step 705 The new eNodeB sends a handover request acknowledgement message to the new MME.
  • Step 706 The new MME sends a node reassignment response message to the old MME, and carries the PFH capability (whether or not the PFH function is supported) information in the response message.
  • Step 707 The old MME sends a handover indication message to the original eNodeB.
  • Step 708 The original eNodeB forwards the handover indication message to the UE.
  • Step 709 After performing cell synchronization with the new eNodeB, the UE sends a handover confirmation message to the new eNodeB.
  • Step 710 The new eNodeB sends a handover notification message to the new MME.
  • Step 711 The new MME sends a message that the node re-allocation is completed to the old MME.
  • Step 712 The old MME returns a confirmation message that the node re-allocation is completed to the new MME.
  • the request message carries the source GTP-C tunnel identifier and the destination GTP-C tunnel identifier, and the S-GW updates the bearer binding relationship. If the new MME supports the PFH function, The Bearer ID of the default bearer needs to be associated with the MME-FQ-CSID and sent to the S-GW.
  • Step 714 The S-GW sends an update bearer request to the P-GW, and sends parameters such as the address information of the S-GW, the tunnel identifier information, and the location information of the UE to the P-GW.
  • the S-GW needs to acquire the new associated MME.
  • - FQ-CSID is sent to the P-GW.
  • Step 715 The P-GW updates its own context and returns an update bearer response message to the S-GW.
  • Step 716 The S-GW returns an update bearer response message to the new MME, and brings the destination GTP-C tunnel identifier specified by the S-GW, its own address, and the address and tunnel information of the P-GW to the new MME.
  • the S-GW also needs to send its stored S-GW-FQ-CSID, P-GW-FQ-CSID to the new MME.
  • Step 717 If the new MME does not support the PFH function, the old MME needs to perform a PFH association synchronization process with the S-GW and the P-GW.
  • the PFH association synchronization process is shown in Figure 4 and will not be described here.
  • the old MME sends its own PFH capability information to the new MME in the re-allocation request message.
  • the old MME may not carry its own PFH capability information, as shown in FIG. Show.
  • the operation of the embodiment shown in FIG. 8 is similar to the example shown in FIG. 7, and is not described here. The only difference is that the old MME does not carry the PFH capability information of the old MME itself in the re-allocation request message.
  • the PFH capability information may occupy a message unit in the message, that is, when the message unit takes a value of "1", it indicates that the MME supports the PFH function, when the message unit takes If the value is "0", it means that the MME does not support the PFH function; or, when the value of the message unit is "0", it indicates that the MME supports the PFH function. When the value of the message unit is "1", it indicates that the MME does not support PFH function.
  • the present invention also provides a synchronization system for partial fault processing. As shown in FIG.
  • the system includes: a new MME 10, an old MME 20, an S-GW 30, and a P-GW. 40.
  • the new MME 10 is configured to send its own PFH capability information to the old MME 20 during the context transfer process when the UE moves to the new MME 10.
  • the old MME 20 is configured to initiate an association synchronization operation of the PFH to the S-GW 30 and the P-GW 40 when determining that the new MME 10 does not support the PFH function according to the received PFH capability information.
  • the S-GW 30 and the P-GW 40 are configured to perform an association synchronization operation of the PFH.
  • the old MME 20 is further configured to delete the default Bearer ID of the PDN connection to be released from the MME-FQ-CSID stored by itself, and send a release PDN connection set request message to the S-GW 30.
  • the request message carries the Bearer ID of the default bearer of the PDN connection to be released;
  • the S-GW 30 is further configured to: the Bearer ID of the default bearer of the PDN connection to be released from the MME stored by itself Deleting the FQ-CSID and the S-GW-FQ-CSID, and sending a release PDN connection set request message to the P-GW 40 for PFH synchronization, where the request message carries the Bearer ID of the default bearer of the PDN connection to be released;
  • P- The GW 40 is further configured to: delete the default Bearer ID of the PDN connection to be released from the MME-FQ-CSID, the S-GW-FQ-CSID, and the P-GW-FQ-CSID
  • the new MME 10 is further configured to send, by the context acknowledgement message, or the context request signaling, or the node reassignment response message, its own PFH capability information to the old MME 20 during context transfer.
  • the old MME 20 is further configured to: send the PFH capability information of the new MME 10 to the new MME 10 during the context transfer process; correspondingly, the new MME 10 is further configured to determine, according to the PFH capability information of the old MME 20, whether the PFH capability of the new MME 10 is to be used. The information is sent to the old MME 20.
  • the S-GW or the P-GW can synchronize the PDN connection associated with the FQ-CSID, so that the correct release operation can be performed on the corresponding PDN connection resource.

Abstract

L'invention porte sur un procédé de synchronisation pour une gestion de défaut partiel (PFH), comprenant les étapes suivantes : lorsqu'un équipement utilisateur (UE) se déplace vers une nouvelle entité de gestion de mobilité (MME), la nouvelle MME adresse des informations de sa capacité de PFH à la MME initiale dans la procédure de délivrance de contexte ; lorsque la MME initiale détermine, selon les informations de capacité de PFH reçues, que la nouvelle MME n'accepte pas la fonction PFH, elle initie une opération d'association et de synchronisation pour la PFH à la passerelle de desserte (S-GW) et à la passerelle de réseau de données par paquets (P-GW). La présente invention porte également sur un système de synchronisation pour PFH, permettant à la S-GW ou à la P-GW de synchroniser la connexion de réseau de données par paquets (PDN) associée à l'identité d'ensemble de connexion PDN complètement qualifiée (FQ-CSID), permettant ainsi une libération correcte des ressources de connexion PDN correspondant à la S-GW ou à la P-GW.
PCT/CN2010/073062 2009-07-16 2010-05-21 Procédé de synchronisation et système de gestion de défaut partiel WO2011006395A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910089396.0A CN101959209B (zh) 2009-07-16 2009-07-16 一种部分故障处理的同步方法和系统
CN200910089396.0 2009-07-16

Publications (1)

Publication Number Publication Date
WO2011006395A1 true WO2011006395A1 (fr) 2011-01-20

Family

ID=43448921

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/073062 WO2011006395A1 (fr) 2009-07-16 2010-05-21 Procédé de synchronisation et système de gestion de défaut partiel

Country Status (2)

Country Link
CN (1) CN101959209B (fr)
WO (1) WO2011006395A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103702353A (zh) * 2012-09-28 2014-04-02 中国电信股份有限公司 故障定位方法和系统，以及接入点和网管设备

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102740268B (zh) * 2011-04-07 2017-04-12 中兴通讯股份有限公司 分组数据网络网关及终端移动性管理的系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101365159A (zh) * 2007-08-08 2009-02-11 华为技术有限公司 承载标识处理方法及设备
CN101388828A (zh) * 2007-09-10 2009-03-18 大唐移动通信设备有限公司 演进分组交换系统承载激活的方法及装置
WO2009078508A1 (fr) * 2007-12-14 2009-06-25 Electronics And Telecommunications Research Institute Procédé de commande et de gestion de support dans un réseau de communication mobile ip évolué

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101365159A (zh) * 2007-08-08 2009-02-11 华为技术有限公司 承载标识处理方法及设备
CN101388828A (zh) * 2007-09-10 2009-03-18 大唐移动通信设备有限公司 演进分组交换系统承载激活的方法及装置
WO2009078508A1 (fr) * 2007-12-14 2009-06-25 Electronics And Telecommunications Research Institute Procédé de commande et de gestion de support dans un réseau de communication mobile ip évolué

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103702353A (zh) * 2012-09-28 2014-04-02 中国电信股份有限公司 故障定位方法和系统，以及接入点和网管设备

Also Published As

Publication number Publication date
CN101959209A (zh) 2011-01-26
CN101959209B (zh) 2014-06-11

Similar Documents

Publication Publication Date Title
US9320075B2 (en) Method, system and transmission distribution network element for indicating data-distribution
EP2471307B1 (fr) Relocalisation d'ancre de mobilité pour des abonnés nomades
US8855045B2 (en) Method and system for controlling establishment of local IP access
WO2013010415A1 (fr) Procédé, système et sgw pour réaliser une notification d'attributs d'adresse ip
EP2259657B1 (fr) Procédé pour indiquer la gestion de support de la passerelle de desserte
WO2011153750A1 (fr) Procédé et système de synchronisation de données d'utilisateur
WO2010130094A1 (fr) Procédé, dispositif et système destinés à rechercher un équipement d'utilisateur
WO2008019631A1 (fr) Procédé et système de transfert de matériel d'utilisateur dans un système de communication mobile
WO2009043209A1 (fr) Procédé permettant d'établir une porteuse vers un terminal utilisateur en mode repos
US20110182244A1 (en) Method for supporting context management by home node-b
WO2009094871A1 (fr) Procédé pour purger des données de la mémoire tampon d'une passerelle de desserte
EP2482567B1 (fr) Procede et appareil pour la transition de statut
WO2008113235A1 (fr) Procédé pour éviter la libération erronée de ressources pendant une mise à jour de zone de suivi ou un transfert intercellulaire
WO2011026392A1 (fr) Procédé et système d'acquisition de stratégies d’itinéraire
WO2010124551A1 (fr) Procédé et système pour préserver un identifiant de passerelle de réseau par paquets dans un scénario d'accès multiples
WO2011026407A1 (fr) Procédé et système de prise en charge de mobilité de connexion d'accès par protocole internet local
WO2014209016A1 (fr) Procédé et appareil de délestage de trafic de données dans un système de communication sans fil
WO2012062183A1 (fr) Procédé et système pour contrôler une qualité de service et une politique de facturation de flux de données
WO2011006404A1 (fr) Procédé et système d'établissement d'une connexion d'accès ip local
WO2012130018A1 (fr) Procédé et système pour la prise en charge de mobilité de connexion de déchargement ip
WO2008154783A1 (fr) Procédé pour établir un tunnel à partir de sgsn vers la passerelle de service
WO2011017979A1 (fr) Procede et dispositif de gestion de ressources dans un systeme de communication soutenant le shuntage ip
WO2011026391A1 (fr) Procédé de réattribution de charge pour passerelle de desserte, système et passerelle de desserte
WO2012126319A1 (fr) Procédé et système pour le transfert intercellulaire d'un service d'accès local
WO2011050663A1 (fr) Procédé et système de mise à jour de tunnel dans un système de communication prenant en charge un accès sous protocole internet (ip) local

Legal Events

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

Ref document number: 10799393

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10799393

Country of ref document: EP

Kind code of ref document: A1