WO2011054270A1 - 一种实现位置区域更新的方法及系统 - Google Patents

一种实现位置区域更新的方法及系统 Download PDF

Info

Publication number
WO2011054270A1
WO2011054270A1 PCT/CN2010/078212 CN2010078212W WO2011054270A1 WO 2011054270 A1 WO2011054270 A1 WO 2011054270A1 CN 2010078212 W CN2010078212 W CN 2010078212W WO 2011054270 A1 WO2011054270 A1 WO 2011054270A1
Authority
WO
WIPO (PCT)
Prior art keywords
sgsn
mme
emergency service
user
new mme
Prior art date
Application number
PCT/CN2010/078212
Other languages
English (en)
French (fr)
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 WO2011054270A1 publication Critical patent/WO2011054270A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity
    • H04W12/106—Packet or message integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/63—Location-dependent; Proximity-dependent
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/26—Resource reservation
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/24—Interfaces between hierarchically similar devices between backbone network devices

Definitions

  • the present invention relates to an IP Multimedia Core Subsystem (IMS) technology, and more particularly to a method and system for implementing location area update.
  • IMS IP Multimedia Core Subsystem
  • the IP Multimedia Core Subsystem is the core of the new generation of communication networks.
  • the IMS uses the Session Initiation Protocol (SIP) system.
  • SIP Session Initiation Protocol
  • SIP is independent of access, and has the ability to separate media service control functions from bearer separation, call and session separation, application and service separation, service and network separation, and convergence of mobile and Internet services.
  • IMS is independent of access
  • EMC Emergency Call
  • S AE System Architecture Evolution
  • UMTS Universal Mobile Telecommunications System
  • SAE can also be called Evolved Packet System (EPS).
  • EMC Emergency Call
  • EPS Evolved Packet System
  • FIG. 1 is a schematic structural diagram of a main network element involved in an emergency call of a user equipment (UE, User Equipment) through a UMTS and an IMS station to access an IMS through a SAE and a mobile station (MS, Mobile Station).
  • UE User Equipment
  • MS Mobile Station
  • the main network elements involved in the emergency call of the UE to the IMS through the SAE include: the network element of the SAE/UMTS network part and the network element of the IMS emergency service part.
  • the network element of the SAE network part is used to provide the underlying bearer management and mobility management.
  • the network elements of the SAE network part include: an enhanced radio base station (eNodeB), a mobility management entity (MME, Mobility Management Entity), and a user plane data routing processing gateway (SAE GW).
  • the SAE GW includes a Packet Data Network Gateway (P-GW) and a Serving GW (S-GW, Serving GW); the Policy and Charging Rules Function (PCRF) is an important function of the PCC architecture.
  • Entity used to control the acquisition, assembly, and delivery of Internet Protocol-IP-Connectivity Access Network (IP-CAN, IP-Connectivity Access Network) policies and charging rules.
  • IP-CAN can be a collection of devices and interfaces in EPS.
  • the MME is responsible for managing and storing the UE's context (eg, UE identity/user identity, mobility management state, user security parameters, etc.), assigning a temporary identity to the user, and authenticating the UE when the UE is camped in the tracking area or network.
  • the home subscriber server (HSS) is used to store user data.
  • the P-GW is a mobility anchor point in the SAE system. It is a border gateway between the SAE and the Packet Data Network (PDN). It is responsible for PDN access and forwarding data between the SAE and the PDN.
  • PDN Packet Data Network
  • the Global Terrestrial Radio Access (UTRAN) and Enhanced Data Rate for Global System for Mobile Communications Evolution Radio Access Network (GERAN) are UMTS wireless Access to the network.
  • the Service General Packet Radio Service Support Node (SGSN, ERVICE GPRS SUPPORT NODE) and the Gateway General Packet Radio Service Support Node (GGSN) are the core network elements of the UMTS network.
  • the SGSN has an MME control plane function and a user plane function
  • the GGSN has a P-GW-like gateway function.
  • the network element of the IMS emergency service part is used to control and process the session of the emergency call.
  • the network element of the IMS emergency service part includes: a Call Session Control Function (CSCF), the CSCF is a core network element that controls the session process, and the CSCF includes a proxy call session control function module (P-CSCF, Proxy- CSCF), query call session control function module (I-CSCF, Interrogating-CSCF), service call session control function module (S-CSCF, Serving-CSCF), E-CSCF.
  • the E-CSCF is the session control center of the emergency call, which determines which PSAP the emergency call should be routed to.
  • FIG. 2 is a flow chart of performing a location area update by accessing a new MME/SGSN (new MME/SGSN) from an old MME/SGSN (old MME/SGSN), where the UE moves, where it is tracked when moving to a new MME.
  • Area Update TAU, Tracking Area Update
  • RAU Router Area Update
  • Step 200 The UE initiates a location area update request to the new MME/SGSN, where the request is sent by the eNodeB (when sent to the MME) /UTRAN or GERAN (when sent to the SGSN), and the location area update request carries the user identity.
  • the user identity is a temporary identity previously assigned at the old MME/SGSN.
  • Step 201 The new MME/SGSN finds the old MME/SGSN that the user has previously accessed according to the temporary identity sent by the UE, sends a context request to the old MME/SGSN, and carries the received location area update request in the context request.
  • Steps 202 to 203 The old MME/SGSN performs a security function on the received context request message, for example, performs verification (integrity check, etc.).
  • the security function fails (for example, the integrity check fails)
  • the old MME/SGSN is new.
  • the MME/SGSN returns a context reply, it carries a suitable error reason.
  • the security function cannot be performed on the user, for example, performing user identity authentication and/or verifying integrity protection of the data sent by the user, and the old MME/SGSN is required to the user. Perform security functions.
  • Step 204 to step 205 After the new MME/SGSN receives the above error reason, it initiates a security function for the user, which may be identity authentication for the user.
  • the reason may be that the user equipment is faulty, or the HSS and/or the MME/SGSN is faulty, and the new MME/SGSN sends a reject location update request to the user equipment, so that if the user is There is an emergency service under the old MME/SGSN.
  • Existing methods for implementing location area update will result in users not being able to access under the new MME/SGSN. Conduct emergency business.
  • the main object of the present invention is to provide a method for realizing location area update, which can ensure that the user equipment successfully performs emergency services after the location area is updated.
  • Another object of the present invention is to provide a system for realizing location area update, which can ensure that the user equipment successfully performs emergency services after the location area is updated.
  • the method further includes: the old MME/SGSN notifying the new MME/SGSN of the information that the user equipment has an emergency service; and the new MME/SGSN retains the emergency service after failing to perform the security function on the user.
  • the information that the old MME/SGSN notifies the user equipment of the emergency service to the new MME/SGSN includes: if the old MME/SGSN detects that the user equipment that initiates the location area update has an emergency service, the old The MME/SGSN indicates a security failure in the context response and carries an emergency service bearer context; and the old MME/SGSN starts a timer for deactivating non-emergency services.
  • the old MME/SGSN further carries a non-emergency service indication for indicating that the user has a non-emergency service in the context response.
  • the method further includes: the new MME/SGSN requesting the context of the non-emergency service from the old MME/SGSN according to the non-emergency service indication. , continue the follow-up process of the location area update.
  • the information that the old MME/SGSN notifies the user equipment of the emergency service to the new MME/SGSN includes: if the old MME/SGSN detects that the user equipment that initiates the location area update has an emergency service, the old The MME/SGSN indicates a security failure in the context response and carries an emergency service indication indicating that the user has an emergency service; and the old MME/SGSN starts a timer for deactivating the non-emergency service.
  • the retaining the emergency service after the new MME/SGSN fails to perform the security function on the user includes: the new MME/SGSN requests the context from the old ME/SGSN according to the received emergency service indication, and in the request Carrying a security failure indication, the old MME/SGSN returns the emergency service bearer context to the new MME/SGSN; and continues to perform the subsequent process of the location area update.
  • the retaining the emergency service after the new MME/SGSN fails to perform the security function on the user includes: the new MME/SGSN requests the context from the old ME/SGSN according to the received emergency service indication, and in the request Carrying the security success indication, the old MME/SGSN returns the emergency service bearer context and the non-emergency service bearer context to the new MME/SGSN, and deletes the timer for deactivating the non-emergency service; the new MME/SGSN is deactivated Non-emergency business, continue the follow-up process of location area update.
  • the method further includes: the new MME/SGSN requesting the context from the old MME/SGSN, and obtaining the emergency service bearer context and the non-user of the user Emergency business bearer context; Continue the subsequent process of location area update.
  • the information that the old MME/SGSN notifies the user equipment of the emergency service to the new MME/SGSN includes: if the old MME/SGSN detects the originating location area update The user equipment has an emergency service, and the old MME/SGSN indicates a security failure in the context response and carries the bearer context.
  • the bearer context includes an emergency service bearer context and an existing non-emergency service bearer context.
  • the retaining the emergency service after the new MME/SGSN fails to perform the security function on the user includes: the new MME/SGSN deactivates the non-emergency service, and continues to perform the location area update process.
  • the method further includes: the new MME/SGSN continuing to perform the location area update procedure.
  • a system for implementing location area update which mainly includes a user equipment, an old MME/SGSN, and a new MME/SGSN, where
  • a user equipment configured to initiate a location area update request to the new MME/SGSN when the old MME/SGSN accesses the new MME/SGSN, and receive the location area i or the update response from the new MME/SGSN;
  • a new MME/SGSN configured to receive a location area update request from the user equipment, requesting a context from the old MME/SGSN; after receiving the notification from the old MME/SGSN, the new MME/SGSN retains the security function after failing to perform the security function on the user The user's emergency service, continuing the location area update and returning the location area update response to the user equipment;
  • the old MME/SGSN is configured to receive a context request from the new MME/SGSN, and notify the new MME/SGSN of the information that the user equipment has an emergency service when the security function is failed for the user.
  • the new MME/SGSN is further configured to acquire the non-emergency service of the user equipment from the old MME/SGSN after performing the security function successfully for the user.
  • the new MME/SGSN requests the context from the old MME/SGSN, the old MME/SGSN.
  • the old MME/SGSN notifies the new MME/SGSN of the emergency service of the user equipment, and the new MME/SGSN retains the emergency service after failing to perform the security function on the user.
  • FIG. 1 is a schematic structural diagram of a main network element involved in an emergency call in which a UE/MS accesses an IMS through an EPS/UMTS in the prior art;
  • FIG. 2 is a flow chart showing that an existing UE moves, accesses a new MME/SGSN from an old MME/SGSN, and performs location area update;
  • FIG. 3 is a flowchart of a method for implementing location area update according to the present invention.
  • FIG. 4 is a schematic structural diagram of a system for realizing location area update according to the present invention.
  • FIG. 5 is a schematic flowchart of a first embodiment of a location area update according to the present invention
  • FIG. 6 is a schematic flowchart of a second embodiment of implementing a location area update according to the present invention
  • FIG. 8 is a schematic flowchart of a fourth embodiment of the present invention for implementing location area update
  • FIG. 9 is a schematic flowchart of a fifth embodiment of implementing location area update according to the present invention
  • FIG. 11 is a schematic flowchart of a seventh embodiment of implementing location area update according to the present invention.
  • FIG. 3 is a flowchart of a method for implementing location area update according to the present invention.
  • the method includes: Step 300: In a process of performing location area update by a user equipment, a new MME/SGSN When the old MME/SGSN requests the context, the old MME/SGSN fails to perform the security function for the user.
  • the new MME/SGSN requests the context from the old MME/SGSN through a context request, and the specific implementation is a technical means that is well known to those skilled in the art, and details are not described herein again.
  • Step 301 The old MME/SGSN notifies the new MME/SGSN of the information about the emergency service of the user equipment, and the new MME/SGSN reserves the emergency service after failing to perform the security function on the user.
  • Method 1 If the old MME/SGSN detects that the user equipment that initiates the location area update has an emergency service, indicates a security failure in the context response, carries the emergency service bearer context, and indicates that the user has non-emergency services. Non-emergency service indication; at the same time, the old MME/SGSN starts a timer for deactivating non-emergency services;
  • the new MME/SGSN performs a security function on the user. If successful, requests the context of the non-emergency service from the old MME/SGSN to continue the subsequent process of the location area update, and the emergency service and non-emergency service of the user equipment may be in the new MME/SGSN. If the failure occurs, the subsequent process of the location area update is continued, that is, only the emergency service of the user equipment is available in the new MME/SGSN, and the old MME/SGSN deactivates the non-emergency service according to the timer.
  • Method 2 If the old MME/SGSN detects that the user equipment that initiates the location area update has an emergency service, indicates a security failure in the context response, and an emergency service indication indicating that the user has an emergency service; and the old MME/SGSN is started for a timer to deactivate non-emergency services;
  • the new MME/SGSN performs a security function on the user. If successful, requests the context from the old MME/SGSN, and obtains the user bearer context (including the user's emergency service bearer context and non-emergency service bearer context); continues to perform the location area update follow-up The process, the emergency service and the non-emergency service of the user equipment may continue to be executed in the new MME/SGSN;
  • the old MME/SGSN If the security function of the new MME/SGSN fails, according to the urgent service indication received, the old The ME/SGSN requests the context and carries the security failure indication (in the specific implementation, it may not carry the user verified indication). At this time, the old MME/SGSN only returns the emergency service bearer context to the new MME/SGSN; the new MME/SGSN The subsequent process of the location area update is continued, that is, only the emergency service of the user equipment is available in the new MME/SGSN, and the old MME/SGSN deactivates the non-emergency service according to the timer.
  • Method 3 If the old MME/SGSN detects that the user equipment that initiates the location area update has an emergency service, indicates a security failure in the context response, and an emergency service indication indicating that the user has an emergency service; and the old MME/SGSN is started for a timer to deactivate non-emergency services;
  • the new MME/SGSN performs a security function on the user. If successful, requests the context from the old MME/SGSN, and obtains the user bearer context (including the user's emergency service bearer context and non-emergency service bearer context); continues to perform the location area update follow-up The process, the emergency service and the non-emergency service of the user equipment may continue to be executed in the new MME/SGSN;
  • the context is requested from the old MME/SGSN according to the received emergency service indication, and carries a security success indication (which may be a user equipment verified indication), at this time, the old MME/SGSN Returning the emergency service bearer context and the non-emergency service bearer context to the new MME/SGSN, and deleting the timer for deactivating the non-emergency service; the new MME/SGSN deactivates the non-emergency service, and only retains the emergency service of the user; /SGSN continues the subsequent process of location area update, that is, only the emergency service of the user equipment in the new MME/SGSN.
  • a security success indication which may be a user equipment verified indication
  • Method 4 If the old MME/SGSN detects that the user equipment that initiates the location area update has emergency service and non-emergency service, indicating a security failure in the context response (may be a suitable error indication that the integrity check failed; ), and carry the emergency service bearer context and non-emergency services ⁇ 2 context;
  • the new MME/SGSN performs security functions on the user. If successful, the location area continues to be executed.
  • the new process, the emergency service and the non-emergency service of the user equipment can continue to be executed in the new MME/SGSN; if it fails, the new MME/SGSN deactivates the non-emergency service, retains only the emergency service, and continues to perform the location area update process.
  • FIG. 4 is a schematic structural diagram of a system for implementing location area update according to the present invention. As shown in FIG. 4, the method mainly includes user equipment, old MME/SGSN, and new MME. /SGSN, where,
  • the user equipment is configured to initiate a location area update request to the new MME/SGSN when the old MME/SGSN accesses the new MME/SGSN, and receive the location area i or the update response from the new MME/SGSN.
  • a new MME/SGSN configured to receive a location area update request from the user equipment, requesting a context from the old MME/SGSN; after receiving the notification from the old MME/SGSN, the new MME/SGSN retains the security function after failing to perform the security function on the user The user's emergency service, continues the location area update and returns a location area update response to the user device.
  • the old MME/SGSN is configured to receive a context request from the new MME/SGSN, and notify the new MME/SGSN of the information that the user equipment has an emergency service when the security function is failed for the user.
  • the new MME/SGSN is further configured to acquire the non-emergency service of the user equipment from the old MME/SGSN after the security function is successfully performed on the user.
  • FIG. 5 is a schematic flowchart of the first embodiment of the present invention, where the user equipment of the emergency service moves from the old MME/SGSN to the new MME/SGSN, and initiates a location update process, as shown in FIG. 5, including:
  • Step 500 The user equipment initiates a location area update request to the new MME/SGSN, the request is sent by the eNodeB (when sent to the MME), or the request is sent by the UTRAN/GERAN (when sent to the SGSN), and the location area update request is sent.
  • the user identity is the temporary identity previously assigned to the old MME/SGSN.
  • Step 501 The new MME/SGSN finds the old MME/SGSN accessed by the user according to the temporary identity from the user equipment, sends a context request to the old MME/SGSN, and carries the received location area update request in the context request.
  • Step 502 to step 503 The old MME/SGSN performs a security function on the received context request message, for example, performs verification (integrity check, etc.).
  • the security function fails (if the integrity check fails)
  • the old MME/SGSN detects The user equipment has an emergency service.
  • the context reply carries a security failure indication and an emergency service bearer context.
  • the security failure indication may be an integrity check failure of a location update message sent by the user, such as a suitable error value.
  • the old MME/SGSN starts a timer after sending the context reply, and the old MME/SGSN will time out the timer to deactivate the non-emergency service of the user equipment.
  • Step 504 to step 505 The new MME/SGSN performs a security function on the user. If it fails, it continues to perform the subsequent process of the location area update, and sends an accept location update request to the user equipment.
  • the user equipment has only emergency services in the new MME/SGSN.
  • FIG. 6 is a schematic flowchart of a second embodiment of the present invention for implementing location area update.
  • the user equipment with emergency services moves from the old MME/SGSN to the new MME/SGSN, and initiates a location update process.
  • the following includes the following: Steps:
  • Steps 600 to 601 are identical to steps 500 to 501, and are not described here.
  • the old MME/SGSN performs a security function on the received context request message, for example, performs verification (integrity check, etc.).
  • the security function fails (such as an integrity check failure)
  • the old MME/SGSN detects The user equipment has an emergency service.
  • the context reply carries a security failure indication, and an emergency service bearer context and a non-emergency service indication.
  • the security failure indication may be an integrity check failure of a location update message sent by the user, such as a suitable error value.
  • old The MME/SGSN starts a timer after sending a context reply, and the old MME/SGSN will time out the timer to deactivate the non-emergency service of the user equipment.
  • Step 604 to step 605 The new MME/SGSN performs a security function on the user, and when the security function is successfully executed, sends a context request to the old MME/SGSN, where the user equipment has been verified.
  • Step 606 The old MME/SGSN sends a context reply to the new MME/SGSN, where the user bearer context is carried, including the non-emergency service bearer context of the user. At the same time, the old MME/SGSN deletes the timers set in steps 602 to 603.
  • Step 607 The new MME/SGSN sends an accept location update request to the UE, and the emergency service and the non-emergency service of the user may continue to be executed in the new MME/SGSN.
  • FIG. 7 is a schematic flowchart of a third embodiment of implementing location area update according to the present invention.
  • the user equipment with emergency service moves from the old MME/SGSN to the new MME/SGSN, and initiates a location update process. As shown in FIG. 7, the following includes the following steps. Steps:
  • Steps 700 to 701 are completely identical to steps 500 to 501, and are not described here.
  • the old MME/SGSN performs a security function on the received context request message, for example, performs verification (integrity check, etc.), and when the security function fails (if the integrity check fails), the old MME/SGSN detects The user equipment has an emergency service.
  • the context reply carries a security failure indication and an emergency service indication.
  • the security failure indication may be a failure to check the integrity of the location update message sent by the user, such as a suitable error value.
  • the old MME/SGSN starts a timer after sending a context reply, and the old MME/SGSN will time out the timer to deactivate the non-emergency service of the user equipment.
  • Step 704 to step 705 The new MME/SGSN performs a security function on the user. If the user fails, according to the received emergency service indication, the context request is sent to the old MME/SGSN, and the security request indication is carried in the context request. When it is implemented, it can be carried without carrying the user.
  • the certificate indicates that if the user request has not been carried in the context request, it means that the security function is not performed on the user, or the new MME/SGSN can directly carry a security failure indication in the context request.
  • Step 706 The old MME/SGSN sends a context reply to the new MME/SGSN, which carries the emergency service bearer context of the user.
  • Step 707 The new MME/SGSN sends an accept location update request to the user equipment, and the user equipment has only emergency services in the new MME/SGSN.
  • FIG. 8 is a schematic flowchart of a fourth embodiment of implementing the location area update according to the present invention.
  • the user equipment with emergency services moves from the old MME/SGSN to the new MME/SGSN, and initiates a location update process.
  • the following includes the following: Steps:
  • Steps 800 to 801 are identical to steps 500 to 501, and are not described here.
  • the old MME/SGSN performs a security function on the received context request message, for example, performs verification (integrity check, etc.).
  • the security function fails (if the integrity check fails)
  • the old MME/SGSN detects The user equipment has an emergency service.
  • the context reply carries a security failure indication and an emergency service indication.
  • the security failure indication may be a failure to check the integrity of the location update message sent by the user, such as a suitable error value.
  • the old MME/SGSN starts a timer after sending a context reply, and the old MME/SGSN will time out the timer to deactivate the non-emergency service of the user equipment.
  • Step 804 to step 805 The new MME/SGSN performs a security function on the user. If successful, according to the received emergency service indication, the user sends a context request to the old MME/SGSN, and carries the user verified indication in the context request.
  • Step 806 The old MME/SGSN sends a context reply to the new MME/SGSN, where the bearer context of the user is carried, including the emergency service bearer context. When the user has non-emergency services, the non-emergency service bearer context is also carried.
  • Step 807 The new MME/SGSN sends an accept location update request to the user equipment, and the bearer of the user equipment in the original MME/SGSN is migrated to the new MME/SGSN.
  • FIG. 9 is a schematic flowchart of a fifth embodiment of implementing the location area update according to the present invention.
  • the user equipment with emergency services moves from the old MME/SGSN to the new MME/SGSN, and initiates a location update process.
  • the following includes the following: Steps:
  • Steps 900 to 901 are identical to steps 500 to 501, and are not described here.
  • the old MME/SGSN performs a security function on the received context request message, for example, performs verification (integrity check, etc.), and when the security function fails (such as an integrity check failure), the old MME/SGSN detects The user equipment has an emergency service.
  • the context reply carries a security failure indication and an emergency service indication.
  • the security failure indication may be a failure to check the integrity of the location update message sent by the user, such as a suitable error value.
  • the old MME/SGSN starts a timer after sending a context reply, and the old MME/SGSN will time out the timer to deactivate the non-emergency service of the user equipment.
  • Step 904 to step 905 The new MME/SGSN performs a security function on the user. If the user fails to receive an emergency service indication, the context request is sent to the old MME/SGSN, and the context request carries a security success indication, such as Can be the user has verified the indication.
  • a security success indication such as Can be the user has verified the indication.
  • Step 906 The old MME/SGSN sends a context reply to the new MME/SGSN, where the bearer context of the user is carried, including the emergency service bearer context and the non-emergency service bearer context that may exist.
  • the old MME/SGSN deletes the settings in steps 902 to 903. Timer.
  • Step 907 to step 908 The new MME/SGSN sends an accept location update request to the user equipment, and the new MME/SGSN deactivates the non-emergency service of the UE.
  • the user equipment has only emergency services in the new MME/SGSN.
  • FIG. 10 is a schematic flowchart of a sixth embodiment of implementing location area update according to the present invention.
  • a user equipment with an emergency service moves from an old MME/SGSN to a new MME/SGSN, and initiates a location update.
  • the process, as shown in Figure 10, includes the following steps:
  • Steps 1000 to 1001 are completely identical to steps 500 to 501, and are not described here.
  • the old MME/SGSN performs a security function on the received context request message, for example, performs verification (integrity check, etc.), and when the security function fails (such as an integrity check failure), the old MME/SGSN detects The user equipment has an emergency service.
  • the context reply carries a security failure indication, and an emergency service bearer context and an existing non-emergency service bearer context.
  • the security failure indication may be an integrity check failure of a location update message sent by the user, such as a suitable error value.
  • Step 1004 to step 1006 The new MME/SGSN performs a security function on the user. If it fails, only the emergency service is reserved, and the new MME/SGSN sends a request for receiving the location update to the user equipment, and initiates the non-emergency service of the deactivated user. Location update process.
  • FIG. 11 is a schematic flowchart of a seventh embodiment of the present invention, in which a UE with an emergency service moves from an old MME/SGSN to a new MME/SGSN, and initiates a location update process. As shown in FIG. 9, the following steps are included. :
  • Steps 1100 to 1101 are completely identical to steps 500 to 501, and are not described here.
  • Step 1102 to step 1103 The old MME/SGSN performs a security function on the received context request message, for example, performs verification (integrity check, etc.), and when the security function fails (such as an integrity check failure), the old MME/SGSN detects The user equipment has an emergency service.
  • the context reply carries a security failure indication, and an emergency service bearer context and an existing non-emergency service bearer context.
  • the security failure indication may be an integrity check failure of a location update message sent by the user, such as a suitable error value.
  • Step 1104 to step 1105 The new MME/SGSN performs a security function on the user, and if successful, sends an accept location update request to the user equipment to complete the location update procedure, the user equipment The bearer in the old MME/SGSN is migrated to the new MME/SGSN.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

一种实现位置区域更新的方法及系统 技术领域
本发明涉及 IP 多媒体子系统 （IMS , IP Multimedia Core Network Subsystem )技术， 尤指一种实现位置区域更新的方法及系统。 背景技术
IP多媒体子系统（ IMS , IP Multimedia Core Network Subsystem )是新 一代通信网络的核心， IMS 釆用会话发起协议 ( SIP , Session Initiation Protocol )体系。 SIP 与接入无关， 并具备媒体业务控制功能与承载分离、 呼叫与会话分离、 应用与服务分离、 业务与网络分离、 以及移动网与因特 网业务融合等多种能力。
由于 IMS和接入无关，所以 IMS下的紧急业务（ EMC, Emergency Call ) 可以建设在系统长期演进（ S AE , System Architecture Evolution ) 网络和通 用移动通信系统 ( UMTS, Universal Mobile Telecommunications System )上。 其中 SAE也可以称为演进的分组系统（ EPS , Evolved Packet System ) 。
图 1所示为用户设备（ UE, User Equipment )通过 SAE以及移动台（ MS , Mobile Station )通过 UMTS接入 IMS的紧急呼叫所涉及的主要网元组成的 架构示意图。 其中， UE与 MS不做特别区分。 UE通过 SAE接入 IMS的紧 急呼叫所涉及的主要网元包括： SAE/UMTS网络部分的网元以及 IMS紧急 业务部分的网元。
其中， SAE网络部分的网元， 用于提供底层的承载管理和移动性管理。 SAE网络部分的网元包括： 增强的无线基站（eNodeB ) 、 移动性管理实体 ( MME, Mobility Management Entity )、以及用户面数据路由处理网关（ SAE GW ) 。 SAE GW包括分组数据网网关（ P-GW, Packet Data Network Gateway ) 和服务网关（S-GW, Serving GW ) ； 策略和计费规则功能（PCRF, Policy and Charging Rules Function )是 PCC架构的重要功能实体， 用于控制因特 网协议 -连接接入网（IP-CAN, IP-Connectivity Access Network )策略和计费 规则的获取、 装配和下发等。 其中， IP-CAN可以是 EPS中的设备和接口的 集合。 MME负责管理和存储 UE的上下文（例如， UE标识 /用户标识、 移 动性管理状态、 用户安全参数等）， 为用户分配临时标识， 当 UE驻扎在跟 踪区域或者网络时， 负责对 UE 进行鉴权。 归属用户服务器（HSS , home subscriber server )用于保存用户数据。
P-GW是 SAE系统内的移动锚点，是 SAE与分组数据网络（ PDN, Packet Data Network ) 的边界网关， 负责 PDN的接入、 在 SAE与 PDN间转发数 据等功能。
全球陆上无线接入 ( UTRAN, Universal Terrestrial Radio Access )和增 强型数据速率演进的全球移动通讯系统无线接入网络（GERAN, enhanced Data Rate for Global System for Mobile Communications Evolution Radio Access Network )是 UMTS的无线接入网络。服务通用分组无线服务支持节 点（ SGSN, ERVICE GPRS SUPPORT NODE )和网关通用分组无线服务支 持节点（ GGSN )是 UMTS网络的核心网网元。 其中， SGSN具有 MME控 制面功能和用户面功能， GGSN具有类似 P-GW的网关功能。
IMS紧急业务部分的网元，用于控制和处理紧急呼叫的会话。其中， IMS 紧急业务部分的网元包括： 呼叫会话控制功能模块（CSCF, Call Session Control Function ) , CSCF是控制会话过程的核心网元， CSCF包括代理呼 叫会话控制功能模块（P-CSCF, Proxy-CSCF ) 、 查询呼叫会话控制功能模 块（I-CSCF, Interrogating-CSCF )、 服务呼叫会话控制功能模块（ S-CSCF, Serving-CSCF ) 、 E-CSCF。 其中， E-CSCF是紧急呼叫的会话控制中心， 决定紧急呼叫应该路由到哪个 PSAP。 图 2 为 UE发生移动， 从旧 MME/SGSN ( old MME/SGSN )接入新 MME/SGSN ( new MME/SGSN ) , 执行位置区域更新的流程图， 这里， 当 移动到新 MME时， 为跟踪区更新（TAU, Tracking Area Update ) , 当移动 到新 SGSN时， 为路由区更新（RAU, Router Area Update )。 如图 2所示， 具体包括：
步骤 200: UE向新 MME/SGSN发起位置区域更新请求， 该请求通过 eNodeB (当向 MME发送时） /UTRAN或 GERAN (当向 SGSN发送时）发 送， 在位置区域更新请求中携带有用户身份， 该用户身份为之前在旧 MME/SGSN分配的临时身份。
步骤 201： 新 MME/SGSN根据 UE发来的临时身份， 找到用户之前接 入的旧 MME/SGSN, 向旧 MME/SGSN发送上下文请求， 在上下文请求中 携带接收到的位置区域更新请求。
步骤 202〜步骤 203: 旧 MME/SGSN对接收到的上下文请求消息执行安 全功能， 例如进行验证（完整性检查等） ， 当安全功能失败（如完整性检 查失败） 时， 旧 MME/SGSN向新 MME/SGSN返回上下文回复时， 携带一 个适合的错误原因。
本步骤中， 由于新 MME/SGSN中没有该用户的安全信息， 因此无法对 用户执行安全功能， 例如进行用户身份认证和 /或验证用户发送数据的完整 性保护等， 需要旧 MME/SGSN对用户执行安全功能。
步骤 204〜步骤 205： 当新 MME/SGSN收到上述错误原因后，发起对用 户执行安全功能， 可以是对用户进行身份认证。
本步骤中， 当安全功能对用户认证失败时， 原因可以是用户设备出错、 或者 HSS和 /或 MME/SGSN出错等， 新 MME/SGSN将发送拒绝位置更新 请求给用户设备， 这样， 如果用户在旧 MME/SGSN下存在紧急业务， 现有 实现位置区域更新的方法将会导致用户无法在新 MME/SGSN 下接入以及 进行紧急业务。
从上述流程可以看出， 当有紧急业务的用户移动到新 MME/SGSN下进 行位置区域更新过程中 , 由于新 MME/SGSN不知道用户在旧 MME/SGSN 中有紧急业务， 以及新 MME/SGSN或旧 MME/SGSN中安全功能的执行， 在现有技术中， 可能导致用户无法在新 MME/SGSN 下接入以实现紧急业 务。 发明内容
有鉴于此， 本发明的主要目的在于提供一种实现位置区域更新的方法， 能够保证用户设备在位置区域更新后， 成功进行紧急业务。
本发明的另一目的在于提供一种实现位置区域更新的系统， 能够保证 用户设备在位置区域更新后， 成功进行紧急业务。
为达到上述目的， 本发明的技术方案是这样实现的：
一种实现位置区域更新的方法， 在用户设备执行位置区域更新的过程 中， 新移动性管理实体 /服务通用分组无线服务支持节点 MME/SGSN向旧 MME/SGSN请求上下文时， 旧 MME/SGSN对用户执行安全功能失败， 该 方法还包括：所述旧 MME/SGSN将用户设备存在紧急业务的信息通知给新 MME/SGSN; 所述新 MME/SGSN在对用户执行安全功能失败后保留紧急 业务。
在上述方案中， 所述旧 MME/SGSN将用户设备存在紧急业务的信息通 知给新 MME/SGSN包括： 如果所述旧 MME/SGSN检测到发起位置区域更新 的用户设备存在紧急业务， 所述旧 MME/SGSN在上下文响应中指示安全失 败， 并携带紧急业务承载上下文； 同时所述旧 MME/SGSN启动用于去活非 紧急业务的定时器。
在上述方案中， 所述旧 MME/SGSN在上下文响应中还携带有用于表明 用户存在非紧急业务的非紧急业务指示。 在上述方案中， 如果所述新 MME/SGSN对该用户执行安全功能成功， 该方法还包括： 所述新 MME/SGSN根据所述非紧急业务指示， 向旧 MME/SGSN请求非紧急业务的上下文，继续执行位置区域更新的后续流程。
在上述方案中， 所述旧 MME/SGSN将用户设备存在紧急业务的信息通 知给新 MME/SGSN包括： 如果所述旧 MME/SGSN检测到发起位置区域更新 的用户设备存在紧急业务， 所述旧 MME/SGSN在上下文响应中指示安全失 败， 并携带用于表明用户存在紧急业务的紧急业务指示； 同时所述旧 MME/SGSN启动用于去活非紧急业务的定时器。
在上述方案中， 所述新 MME/SGSN在对用户执行安全功能失败后保留 紧急业务包括： 所述新 MME/SGSN根据收到的紧急业务指示， 向旧 ME/SGSN请求上下文， 并在请求中携带安全失败指示， 所述旧 MME/SGSN 将紧急业务承载上下文返回给新 MME/SGSN; 继续执行位置区域更新的后 续流程。
在上述方案中， 所述新 MME/SGSN在对用户执行安全功能失败后保留 紧急业务包括： 所述新 MME/SGSN根据收到的紧急业务指示， 向旧 ME/SGSN请求上下文， 并在请求中携带安全成功指示， 所述旧 MME/SGSN 将紧急业务承载上下文和非紧急业务承载上下文返回给新 MME/SGSN, 同 时删除用于去活非紧急业务的定时器；所述新 MME/SGSN去活非紧急业务， 继续执行位置区域更新的后续流程。
在上述方案中， 如果所述新 MME/SGSN对该用户执行安全功能成功， 该方法还包括： 所述新 MME/SGSN向旧 MME/SGSN请求上下文， 并获得该 用户的紧急业务承载上下文和非紧急业务承载上下文； 继续执行位置区域 更新的后续流程。
在上述方案中， 所述旧 MME/SGSN将用户设备存在紧急业务的信息通 知给新 MME/SGSN包括： 如果所述旧 MME/SGSN检测到发起位置区域更新 的用户设备存在紧急业务， 所述旧 MME/SGSN在上下文响应中指示安全失 败， 并携带承载上下文。
在上述方案中， 所述承载上下文包括紧急业务承载上下文和存在的非 紧急业务承载上下文。
在上述方案中， 所述新 MME/SGSN在对用户执行安全功能失败后保留 紧急业务包括： 所述新 MME/SGSN去活非紧急业务， 继续执行位置区域更 新流程。
在上述方案中， 如果所述新 MME/SGSN对该用户执行安全功能成功， 该方法还包括： 所述新 MME/SGSN继续执行位置区域更新流程。
一种实现位置区域更新的系统， 主要包括用户设备、 旧 MME/SGSN、 新 MME/SGSN, 其中，
用户设备，用于在发生移动，从旧 MME/SGSN接入新 MME/SGSN时， 向新 MME/SGSN发起位置区域更新请求； 接收来自新 MME/SGSN的位置 区 i或更新响应；
新 MME/SGSN, 用于接收来自用户设备的位置区域更新请求， 向旧 MME/SGSN请求上下文； 新 MME/SGSN接收到来自旧 MME/SGSN的通 知后， 在对用户执行安全功能失败后保留该用户的紧急业务， 继续位置区 域更新并向用户设备返回位置区域更新响应；
旧 MME/SGSN, 用于接收来自新 MME/SGSN的上下文请求， 在对用户 执行安全功能失败时， 将用户设备存在紧急业务的信息通知给新 MME/SGSN。
在上述方案中， 所述新 MME/SGSN还用于， 在对用户执行安全功能成 功后， 从旧 MME/SGSN获取所述用户设备的非紧急业务。
从上述本发明提供的技术方案可以看出， 在用户设备执行位置区域更 新的过程中，新 MME/SGSN向旧 MME/SGSN请求上下文， 旧 MME/SGSN 对用户执行安全功能失败时，旧 MME/SGSN将用户设备存在紧急业务的信 息通知给新 MME/SGSN, 新 MME/SGSN在对用户执行安全功能失败后保 留紧急业务。 通过本发明方法， 当有紧急业务的用户移动到新 MME/SGSN 下进行位置区域更新过程中， 由于新 MME/SGSN 获知了用户在旧 MME/SGSN中存在紧急业务， 即使在新 MME/SGSN安全功能执行失败， 用户也能在新 MME/SGSN下接入以实现紧急业务，有效地保证了用户设备 在位置区域更新后， 成功进行紧急业务。 附图说明
图 1为现有技术中 UE/MS通过 EPS/UMTS接入 IMS的紧急呼叫所涉 及的主要网元的组成架构示意图；
图 2为现有 UE发生移动， 从旧 MME/SGSN接入新 MME/SGSN, 执 行位置区域更新的流程图；
图 3为本发明实现位置区域更新的方法的流程图；
图 4为本发明实现位置区域更新的系统的组成结构示意图；
图 5为本发明实现位置区域更新的第一实施例的流程示意图； 图 6为本发明实现位置区域更新的第二实施例的流程示意图； 图 7为本发明实现位置区域更新的第三实施例的流程示意图； 图 8为本发明实现位置区域更新的第四实施例的流程示意图； 图 9为本发明实现位置区域更新的第五实施例的流程示意图； 图 10为本发明实现位置区域更新的第六实施例的流程示意图； 图 11为本发明实现位置区域更新的第七实施例的流程示意图。 具体实施方式
图 3为本发明实现位置区域更新的方法的流程图， 如图 3所示， 包括： 步骤 300: 在用户设备执行位置区域更新的过程中， 新 MME/SGSN向 旧 MME/SGSN请求上下文时， 旧 MME/SGSN对用户执行安全功能失败。 本步骤中， 新 MME/SGSN 通过上下文请求 （context request ) 向旧 MME/SGSN请求上下文， 具体实现属于本领域技术人员惯用技术手段， 这 里不再赘述。
步骤 301 : 旧 MME/SGSN将用户设备存在紧急业务的信息通知给新 MME/SGSN, 新 MME/SGSN在对用户执行安全功能失败后保留紧急业务。
本步骤的实现可以有以下几种方法：
方法一：如果旧 MME/SGSN检测到发起位置区域更新的用户设备存在 紧急业务， 在上下文响应（ context response )中指示安全失败， 并携带紧急 业务承载上下文， 以及用于表明用户存在非紧急业务的非紧急业务指示； 同时旧 MME/SGSN启动用于去活非紧急业务的定时器；
新 MME/SGSN对该用户执行安全功能， 如果成功， 向旧 MME/SGSN 请求非紧急业务的上下文， 继续执行位置区域更新的后续流程， 用户设备 的紧急业务和非紧急业务可以在新 MME/SGSN继续执行； 如果失败， 继续 执行位置区域更新的后续流程，也就是在新 MME/SGSN只有该用户设备的 紧急业务， 这时由旧 MME/SGSN才艮据定时器去活非紧急业务。
方法二：如果旧 MME/SGSN检测到发起位置区域更新的用户设备存在 紧急业务， 在 context response中指示安全失败， 以及用于表明用户存在紧 急业务的紧急业务指示； 同时旧 MME/SGSN启动用于去活非紧急业务的定 时器；
新 MME/SGSN对该用户执行安全功能， 如果成功， 向旧 MME/SGSN 请求上下文， 并获得用户承载上下文（包括用户的紧急业务承载上下文和 非紧急业务承载上下文） ； 继续执行位置区域更新的后续流程， 用户设备 的紧急业务和非紧急业务可以在新 MME/SGSN继续执行；
如果新 MME/SGSN的安全功能失败， 才艮据收到的紧急业务指示， 向旧 ME/SGSN请求上下文， 并且携带安全失败指示（具体实现时， 可以是不携 带用户已验证指示 ) , 此时， 旧 MME/SGSN只将紧急业务承载上下文返回 给新 MME/SGSN; 新 MME/SGSN继续执行位置区域更新的后续流程， 也 就是在新 MME/SGSN只有该用户设备的紧急业务， 这时由旧 MME/SGSN 才艮据定时器去活非紧急业务。
方法三：如果旧 MME/SGSN检测到发起位置区域更新的用户设备存在 紧急业务， 在 context response中指示安全失败， 以及用于表明用户存在紧 急业务的紧急业务指示； 同时旧 MME/SGSN启动用于去活非紧急业务的定 时器；
新 MME/SGSN对该用户执行安全功能， 如果成功， 向旧 MME/SGSN 请求上下文， 并获得用户承载上下文（包括用户的紧急业务承载上下文和 非紧急业务承载上下文） ； 继续执行位置区域更新的后续流程， 用户设备 的紧急业务和非紧急业务可以在新 MME/SGSN继续执行；
如果新 MME/SGSN的安全功能失败， 才艮据收到的紧急业务指示， 向旧 MME/SGSN请求上下文， 并且携带安全成功指示（可以是用户设备已验证 指示）， 此时， 旧 MME/SGSN将紧急业务承载上下文和非紧急业务承载上 下文返回给新 MME/SGSN, 同时删除用于去活非紧急业务的定时器； 新 MME/SGSN去活非紧急业务， 仅保留用户的紧急业务； 新 MME/SGSN继 续执行位置区域更新的后续流程，也就是在新 MME/SGSN只有该用户设备 的紧急业务。
方法四：如果旧 MME/SGSN检测到发起位置区域更新的用户设备存在 紧急业务和非紧急业务， 在上下文响应（ context response )中指示安全失败 (可以是完整性检查失败的一个合适的错误指示；)， 并携带紧急业务承载上 下文和非紧急业务^^载上下文；
新 MME/SGSN对用户执行安全功能， 如果成功， 继续执行位置区域更 新流程， 用户设备的紧急业务和非紧急业务可以在新 MME/SGSN 继续执 行； 如果失败， 新 MME/SGSN去活非紧急业务， 只保留紧急业务， 继续执 行位置区域更新流程。
针对本发明方法， 还提供一种实现位置区域更新的系统， 图 4为本发 明实现位置区域更新的系统的组成结构示意图， 如图 4所示， 主要包括用 户设备、 旧 MME/SGSN、 新 MME/SGSN, 其中，
用户设备，用于在发生移动，从旧 MME/SGSN接入新 MME/SGSN时， 向新 MME/SGSN发起位置区域更新请求； 接收来自新 MME/SGSN的位置 区 i或更新响应。
新 MME/SGSN, 用于接收来自用户设备的位置区域更新请求， 向旧 MME/SGSN请求上下文； 新 MME/SGSN接收到来自旧 MME/SGSN的通 知后， 在对用户执行安全功能失败后保留该用户的紧急业务， 继续位置区 域更新并向用户设备返回位置区域更新响应。
旧 MME/SGSN, 用于接收来自新 MME/SGSN的上下文请求， 在对用 户执行安全功能失败时， 将用户设备存在紧急业务的信息通知给新 MME/SGSN。
所述新 MME/SGSN还用于， 在对用户执行安全功能成功后， 从旧 MME/SGSN获取所述用户设备的非紧急业务。
下面结合实施例对本发明方法进行详细描述。
图 5 为本发明实现位置区域更新的第一实施例的流程示意图， 有紧急 业务的用户设备从旧 MME/SGSN移动到新 MME/SGSN, 发起位置更新的 流程， 如图 5所示， 包括：
步骤 500: 用户设备向新 MME/SGSN发起位置区域更新请求， 该请求 通过 eNodeB (当向 MME发送时）发送， 或者该请求通过 UTRAN/GERAN (当向 SGSN发送时）发送， 在位置区域更新请求中携带有用户身份， 该 用户身份为之前在旧 MME/SGSN分配的临时身份。
步骤 501 : 新 MME/SGSN根据来自用户设备的临时身份， 找到用户之 前接入的旧 MME/SGSN, 向旧 MME/SGSN发送上下文请求， 在上下文请 求中携带接收到的位置区域更新请求。
步骤 502〜步骤 503:旧 MME/SGSN对接收到的上下文请求消息执行安 全功能， 例如进行验证（完整性检查等） ， 当安全功能失败（如完整性检 查失败）时，旧 MME/SGSN检测到该用户设备存在紧急业务，旧 MME/SGSN 向新 MME/SGSN返回上下文回复时， 在上下文回复中携带安全失败指示， 以及紧急业务承载上下文。 安全失败指示可以是对用户发送的位置更新消 息的完整性检查失败， 比如一个合适的错误值。 旧 MME/SGSN在发送上下 文回复后启动一个定时器， 旧 MME/SGSN将在该定时器超时， 去活该用户 设备的非紧急业务。
步骤 504〜步骤 505:新 MME/SGSN对该用户执行安全功能，如果失败， 继续执行位置区域更新的后续流程， 向用户设备发送接受位置更新请求， 该用户设备在新 MME/SGSN只有紧急业务。
图 6为本发明实现位置区域更新的第二实施例的流程示意图， 有紧急 业务的用户设备从旧 MME/SGSN移动到新 MME/SGSN, 发起位置更新的 流程， 如图 6所示， 包括以下步骤：
步骤 600〜步骤 601与步骤 500〜步骤 501完全一致， 这里不再赘述。 步骤 602〜步骤 603:旧 MME/SGSN对接收到的上下文请求消息执行安 全功能， 例如进行验证（完整性检查等） ， 当安全功能失败（如完整性检 查失败）时，旧 MME/SGSN检测到该用户设备存在紧急业务，旧 MME/SGSN 向新 MME/SGSN返回上下文回复时， 在上下文回复中携带安全失败指示、 以及紧急业务承载上下文和非紧急业务指示。 安全失败指示可以是对用户 发送的位置更新消息的完整性检查失败， 比如一个合适的错误值。 旧 MME/SGSN在发送上下文回复后启动一个定时器， 旧 MME/SGSN将在该 定时器超时， 去活该用户设备的非紧急业务。
步骤 604〜步骤 605： 新 MME/SGSN对该用户执行安全功能， 当安全功 能执行成功时， 向旧 MME/SGSN发送上下文请求， 其中携带该用户设备已 验证指示。
步骤 606: 旧 MME/SGSN向新 MME/SGSN发送上下文回复， 其中携 带用户承载上下文， 包括用户的非紧急业务承载上下文。 同时， 旧 MME/SGSN删除步骤 602〜步骤 603中设置的定时器。
步骤 607: 新 MME/SGSN向 UE发送接受位置更新请求， 用户的紧急 业务和非紧急业务可以在新 MME/SGSN继续执行。
图 7为本发明实现位置区域更新的第三实施例的流程示意图， 有紧急 业务的用户设备从旧 MME/SGSN移动到新 MME/SGSN, 发起位置更新的 流程， 如图 7所示， 包括以下步骤：
步骤 700〜步骤 701与步骤 500〜步骤 501完全一致， 这里不再赘述。 步骤 702〜步骤 703:旧 MME/SGSN对接收到的上下文请求消息执行安 全功能， 例如进行验证（完整性检查等） ， 当安全功能失败（如完整性检 查失败）时，旧 MME/SGSN检测到该用户设备存在紧急业务，旧 MME/SGSN 向新 MME/SGSN返回上下文回复时， 在上下文回复中携带安全失败指示、 以及紧急业务指示。 安全失败指示可以是对用户发送的位置更新消息的完 整性检查失败， 比如一个合适的错误值。 旧 MME/SGSN在发送上下文回复 后启动一个定时器， 旧 MME/SGSN将在该定时器超时， 去活该用户设备的 非紧急业务。
步骤 704〜步骤 705:新 MME/SGSN对该用户执行安全功能，如果失败， 根据收到的该用户有紧急业务指示， 向旧 MME/SGSN发送上下文请求， 在 上下文请求重中携带安全失败指示。 具体实现时， 可以是不携带用户已验 证指示， 也就是说如果上下文请求中未携带用户已验证指示， 意味着对该 用户执行安全功能失败，或者新 MME/SGSN可以直接在上下文请求中携带 一个安全失败指示。
步骤 706: 旧 MME/SGSN向新 MME/SGSN发送上下文回复， 其中携 带用户的紧急业务承载上下文。
步骤 707: 新 MME/SGSN向用户设备发送接受位置更新请求， 该用户 设备在新 MME/SGSN只有紧急业务。
图 8为本发明实现位置区域更新的第四实施例的流程示意图， 有紧急 业务的用户设备从旧 MME/SGSN移动到新 MME/SGSN, 发起位置更新的 流程， 如图 8所示， 包括以下步骤：
步骤 800〜步骤 801与步骤 500〜步骤 501完全一致， 这里不再赘述。 步骤 802〜步骤 803:旧 MME/SGSN对接收到的上下文请求消息执行安 全功能， 例如进行验证（完整性检查等） ， 当安全功能失败（如完整性检 查失败）时，旧 MME/SGSN检测到该用户设备存在紧急业务，旧 MME/SGSN 向新 MME/SGSN返回上下文回复时， 在上下文回复中携带安全失败指示、 以及紧急业务指示。 安全失败指示可以是对用户发送的位置更新消息的完 整性检查失败， 比如一个合适的错误值。 旧 MME/SGSN在发送上下文回复 后启动一个定时器， 旧 MME/SGSN将在该定时器超时， 去活该用户设备的 非紧急业务。
步骤 804〜步骤 805:新 MME/SGSN对该用户执行安全功能，如果成功， 根据收到的该用户有紧急业务指示， 向旧 MME/SGSN发送上下文请求， 在 上下文请求中携带用户已验证指示。
步骤 806: 旧 MME/SGSN向新 MME/SGSN发送上下文回复， 其中携 带用户的承载上下文， 包括紧急业务承载上下文， 当用户还有非紧急业务 时， 还携带有非紧急业务承载上下文。 步骤 807: 新 MME/SGSN向用户设备发送接受位置更新请求， 该用户 设备在原 MME/SGSN中的承载迁移到新 MME/SGSN。
图 9为本发明实现位置区域更新的第五实施例的流程示意图， 有紧急 业务的用户设备从旧 MME/SGSN移动到新 MME/SGSN, 发起位置更新的 流程， 如图 9所示， 包括以下步骤：
步骤 900〜步骤 901与步骤 500〜步骤 501完全一致， 这里不再赘述。 步骤 902〜步骤 903:旧 MME/SGSN对接收到的上下文请求消息执行安 全功能， 例如进行验证（完整性检查等） ， 当安全功能失败（如完整性检 查失败）时，旧 MME/SGSN检测到该用户设备存在紧急业务，旧 MME/SGSN 向新 MME/SGSN返回上下文回复时， 在上下文回复中携带安全失败指示、 以及紧急业务指示。 安全失败指示可以是对用户发送的位置更新消息的完 整性检查失败， 比如一个合适的错误值。 旧 MME/SGSN在发送上下文回复 后启动一个定时器， 旧 MME/SGSN将在该定时器超时， 去活该用户设备的 非紧急业务。
步骤 904〜步骤 905:新 MME/SGSN对该用户执行安全功能，如果失败， 根据收到的该用户有紧急业务指示， 向旧 MME/SGSN发送上下文请求， 在 上下文请求中携带安全成功指示， 比如可以是用户已验证指示。
步骤 906: 旧 MME/SGSN向新 MME/SGSN发送上下文回复， 其中携 带用户的承载上下文， 包括紧急业务承载上下文和可能存在的非紧急业务 承载上下文； 旧 MME/SGSN删除步骤 902〜步骤 903中设置的定时器。
步骤 907〜步骤 908:新 MME/SGSN向用户设备发送接受位置更新请求， 同时新 MME/SGSN去活 UE的非紧急业务。 该用户设备在新 MME/SGSN 只有紧急业务。
图 10为本发明实现位置区域更新的第六实施例的流程示意图， 有紧急 业务的用户设备从旧 MME/SGSN移动到新 MME/SGSN, 发起位置更新的 流程， 如图 10所示， 包括以下步骤：
步骤 1000〜步骤 1001与步骤 500〜步骤 501完全一致， 这里不再赘述。 步骤 1002〜步骤 1003: 旧 MME/SGSN对接收到的上下文请求消息执行 安全功能， 例如进行验证（完整性检查等） ， 当安全功能失败（如完整性 检查失败） 时， 旧 MME/SGSN 检测到该用户设备存在紧急业务， 旧 MME/SGSN向新 MME/SGSN返回上下文回复时， 在上下文回复中携带安 全失败指示、 以及紧急业务承载上下文和存在的非紧急业务承载上下文。 安全失败指示可以是对用户发送的位置更新消息的完整性检查失败， 比如 一个合适的错误值。
步骤 1004〜步骤 1006: 新 MME/SGSN对该用户执行安全功能，如果失 败， 则只保留紧急业务， 同时新 MME/SGSN向用户设备发送接受位置更新 请求， 发起去活用户的非紧急业务， 完成位置更新流程。
图 11为本发明实现位置区域更新的第七实施例的流程示意图， 有紧急 业务的 UE从旧 MME/SGSN移动到新 MME/SGSN, 发起位置更新的流程， 如图 9所示， 包括以下步骤：
步骤 1100〜步骤 1101与步骤 500〜步骤 501完全一致， 这里不再赘述。 步骤 1102〜步骤 1103: 旧 MME/SGSN对接收到的上下文请求消息执行 安全功能， 例如进行验证（完整性检查等） ， 当安全功能失败（如完整性 检查失败） 时， 旧 MME/SGSN 检测到该用户设备存在紧急业务， 旧 MME/SGSN向新 MME/SGSN返回上下文回复时， 在上下文回复中携带安 全失败指示、 以及紧急业务承载上下文和存在的非紧急业务承载上下文。 安全失败指示可以是对用户发送的位置更新消息的完整性检查失败， 比如 一个合适的错误值。
步骤 1104〜步骤 1105: 新 MME/SGSN对该用户执行安全功能， 如果成 功， 向用户设备发送接受位置更新请求， 完成位置更新流程， 该用户设备 在旧 MME/SGSN中的承载迁移到新 MME/SGSN。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围， 凡在本发明的精神和原则之内所作的任何修改、 等同替换和改进 等， 均应包含在本发明的保护范围之内。

Claims

权利要求书
1、 一种实现位置区域更新的方法， 在用户设备执行位置区域更新的过 程中， 新移动性管理实体 /服务通用分组无线服务支持节点 MME/SGSN向 旧 MME/SGSN请求上下文时， 旧 MME/SGSN对用户执行安全功能失败， 其特征在于， 该方法还包括：
所述旧 MME/SGSN 将用户设备存在紧急业务的信息通知给新 MME/SGSN;
所述新 MME/SGSN在对用户执行安全功能失败后保留紧急业务。
2、 根据权利要求 1所述的方法， 其特征在于， 所述旧 MME/SGSN将用 户设备存在紧急业务的信息通知给新 MME/SGSN包括：
如果所述旧 MME/SGSN检测到发起位置区域更新的用户设备存在紧急 业务， 所述旧 MME/SGSN在上下文响应中指示安全失败， 并携带紧急业务 承载上下文； 同时所述旧 MME/SGSN启动用于去活非紧急业务的定时器。
3、 根据权利要求 2所述的方法， 其特征在于， 所述旧 MME/SGSN在上 下文响应中还携带有用于表明用户存在非紧急业务的非紧急业务指示。
4、 根据权利要求 3所述的方法， 其特征在于， 如果所述新 MME/SGSN 对该用户执行安全功能成功， 该方法还包括：
所述新 MME/SGSN根据所述非紧急业务指示， 向旧 MME/SGSN请求非 紧急业务的上下文， 继续执行位置区域更新的后续流程。
5、 根据权利要求 1所述的方法， 其特征在于， 所述旧 MME/SGSN将用 户设备存在紧急业务的信息通知给新 MME/SGSN包括：
如果所述旧 MME/SGSN检测到发起位置区域更新的用户设备存在紧急 业务， 所述旧 MME/SGSN在上下文响应中指示安全失败， 并携带用于表明 用户存在紧急业务的紧急业务指示； 同时所述旧 MME/SGSN启动用于去活 非紧急业务的定时器。
6、 根据权利要求 5所述的方法， 其特征在于， 所述新 MME/SGSN在对 用户执行安全功能失败后保留紧急业务包括：
所述新 MME/SGSN根据收到的紧急业务指示， 向旧 MME/SGSN请求上 下文， 并在请求中携带安全失败指示， 所述旧 MME/SGSN将紧急业务承载 上下文返回给新 MME/SGSN; 继续执行位置区域更新的后续流程。
7、 根据权利要求 5所述的方法， 其特征在于， 所述新 MME/SGSN在对 用户执行安全功能失败后保留紧急业务包括：
所述新 MME/SGSN根据收到的紧急业务指示， 向旧 MME/SGSN请求上 下文， 并在请求中携带安全成功指示， 所述旧 MME/SGSN将紧急业务承载 上下文和非紧急业务承载上下文返回给新 MME/SGSN, 同时删除用于去活 非紧急业务的定时器； 所述新 MME/SGSN去活非紧急业务， 继续执行位置 区域更新的后续流程。
8、 根据权利要求 5至 7任一项所述的方法， 其特征在于， 如果所述新 MME/SGSN对该用户执行安全功能成功， 该方法还包括：
所述新 MME/SGSN向旧 MME/SGSN请求上下文， 并获得该用户的紧急 业务承载上下文和非紧急业务承载上下文； 继续执行位置区域更新的后续 流程。
9、 根据权利要求 1所述的方法， 其特征在于， 所述旧 MME/SGSN将用 户设备存在紧急业务的信息通知给新 MME/SGSN包括：
如果所述旧 MME/SGSN检测到发起位置区域更新的用户设备存在紧急 业务， 所述旧 MME/SGSN在上下文响应中指示安全失败， 并携带承载上下 文。
10、 根据权利要求 9所述的方法， 其特征在于， 所述承载上下文包括紧 急业务承载上下文和存在的非紧急业务承载上下文。
11、 根据权利要求 9所述的方法， 其特征在于， 所述新 MME/SGSN在对 用户执行安全功能失败后保留紧急业务包括：
所述新 MME/SGSN去活非紧急业务， 继续执行位置区域更新流程。
12、 根据权利要求 9、 10或 11所述的方法， 其特征在于， 如果所述新 MME/SGSN对该用户执行安全功能成功， 该方法还包括： 所述新 MME/SGSN继续执行位置区域更新流程。
13、 一种实现位置区域更新的系统， 其特征在于， 主要包括用户设备、 旧 MME/SGSN、 新 MME/SGSN, 其中 ,
用户设备，用于在发生移动，从旧 MME/SGSN接入新 MME/SGSN时， 向新 MME/SGSN发起位置区域更新请求； 接收来自新 MME/SGSN的位置 区 i或更新响应；
新 MME/SGSN, 用于接收来自用户设备的位置区域更新请求， 向旧 MME/SGSN请求上下文； 新 MME/SGSN接收到来自旧 MME/SGSN的通 知后， 在对用户执行安全功能失败后保留该用户的紧急业务， 继续位置区 域更新并向用户设备返回位置区域更新响应；
旧 MME/SGSN, 用于接收来自新 MME/SGSN的上下文请求， 在对用户 执行安全功能失败时， 将用户设备存在紧急业务的信息通知给新 MME/SGSN。
14、 根据权利要求 13所述的系统， 其特征在于， 所述新 MME/SGSN还 用于， 在对用户执行安全功能成功后， 从旧 MME/SGSN获取所述用户设备 的非紧急业务。
PCT/CN2010/078212 2009-11-09 2010-10-28 一种实现位置区域更新的方法及系统 WO2011054270A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910237281.1 2009-11-09
CN200910237281.1A CN102056114B (zh) 2009-11-09 2009-11-09 一种实现位置区域更新的方法及系统

Publications (1)

Publication Number Publication Date
WO2011054270A1 true WO2011054270A1 (zh) 2011-05-12

Family

ID=43959945

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/078212 WO2011054270A1 (zh) 2009-11-09 2010-10-28 一种实现位置区域更新的方法及系统

Country Status (2)

Country Link
CN (1) CN102056114B (zh)
WO (1) WO2011054270A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112312380B (zh) * 2019-07-29 2022-04-01 大唐移动通信设备有限公司 一种位置上下文的管理方法及网络侧设备
CN113225723B (zh) * 2021-04-02 2023-03-17 上海微波技术研究所（中国电子科技集团公司第五十研究所） 一种加快5g终端紧急业务建立的方法、系统及介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000054537A2 (en) * 1999-03-09 2000-09-14 Nokia Networks Oy Camping in an exclusive cell
CN101123822A (zh) * 2007-08-01 2008-02-13 中兴通讯股份有限公司 Ip多媒体子系统集中业务中紧急呼叫业务的实现方法
CN101335993A (zh) * 2007-06-25 2008-12-31 华为技术有限公司 接入处理方法、装置及用户设备

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101557573B (zh) * 2008-04-07 2012-06-20 电信科学技术研究院 紧急服务信息的获取方法及通信设备
CN101557589A (zh) * 2009-05-04 2009-10-14 中兴通讯股份有限公司 防止空完整性保护算法用于正常通信的方法和系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000054537A2 (en) * 1999-03-09 2000-09-14 Nokia Networks Oy Camping in an exclusive cell
CN101335993A (zh) * 2007-06-25 2008-12-31 华为技术有限公司 接入处理方法、装置及用户设备
CN101123822A (zh) * 2007-08-01 2008-02-13 中兴通讯股份有限公司 Ip多媒体子系统集中业务中紧急呼叫业务的实现方法

Also Published As

Publication number Publication date
CN102056114A (zh) 2011-05-11
CN102056114B (zh) 2014-02-05

Similar Documents

Publication Publication Date Title
US11405258B2 (en) Methods and apparatuses for facilitating P-CSCF restoration when a P-CSCF failure has occurred
US11178714B2 (en) Proxy call session control function failure recovering method, apparatus and system
JP4994449B2 (ja) ネットワークにアクセスする方法、システムおよびデバイス
EP3185596B1 (en) Method, apparatus and system for processing priority services
US8315589B2 (en) Emergency calls for internet protocol multimedia subsystem (IMS) over packet switched code division multiple access (CDMA) networks
WO2010075689A1 (zh) 网络容灾方法、终端和呼叫会话控制功能实体
WO2011035647A1 (zh) 实现紧急定位的方法及系统
WO2010075747A1 (zh) Ip多媒体子系统集中业务的注销方法及系统
US20130142120A1 (en) Mobile communication method and call session control server device
WO2017036227A1 (zh) 一种实现终端被叫业务恢复的方法及装置
US8885608B2 (en) Mobile communication method
US20150365980A1 (en) Method and Device for Sending Identifier Information or Call Transfer Request
CN105592486A (zh) 一种容灾方法及网元、服务器
WO2010105462A1 (zh) 用户设备附着的处理方法、移动性管理实体以及用户设备
WO2012041026A1 (zh) 电路交换域业务切换到分组交换域的方法及系统
CN107404715B (zh) 位置信息提供方法及装置
WO2008116373A1 (fr) Procédé de traitement de service d'urgence
WO2011020273A1 (zh) 一种紧急业务的处理方法和系统
WO2007112621A1 (fr) Procédé destiné à assurer le maintien de la cohérence d'un désenregistrement d'adresses ip de domaine ps et de domaine ims
WO2011054270A1 (zh) 一种实现位置区域更新的方法及系统
WO2011020368A1 (zh) 紧急附着的处理方法、装置和系统
WO2010127530A1 (zh) 一种ip多媒体子系统业务的建立方法及系统
WO2010127529A1 (zh) 一种ip多媒体子系统业务的建立方法及系统
WO2012022226A2 (zh) 一种实现高优先级业务的方法和系统
WO2010037287A1 (zh) 用户设备活动信息通知方法、系统及网元设备、服务器

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: 10827884

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: 10827884

Country of ref document: EP

Kind code of ref document: A1