WO2012097524A1 - Procédé, dispositif et système de traitement de réinitialisation d'élément de réseau de gestion de mobilité - Google Patents

Procédé, dispositif et système de traitement de réinitialisation d'élément de réseau de gestion de mobilité Download PDF

Info

Publication number
WO2012097524A1
WO2012097524A1 PCT/CN2011/070489 CN2011070489W WO2012097524A1 WO 2012097524 A1 WO2012097524 A1 WO 2012097524A1 CN 2011070489 W CN2011070489 W CN 2011070489W WO 2012097524 A1 WO2012097524 A1 WO 2012097524A1
Authority
WO
WIPO (PCT)
Prior art keywords
user terminal
network element
management network
mobility management
context
Prior art date
Application number
PCT/CN2011/070489
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 华为技术有限公司
Priority to CN2011800004365A priority Critical patent/CN102907126A/zh
Priority to PCT/CN2011/070489 priority patent/WO2012097524A1/fr
Publication of WO2012097524A1 publication Critical patent/WO2012097524A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, device, and system for processing a mobility management network element reset.
  • the user terminal accesses through the local wireless access network
  • the mobile management network element is responsible for the location management, connection management, security authentication, gateway selection, and the like of the user terminal
  • the service gateway is the user terminal.
  • the local access gateway is responsible for access technology related connection management and data forwarding
  • the data gateway is a gateway for the user terminal to access the external data network.
  • the monthly service gateway detects that the mobility management network element is reset and deletes the user context related to the mobility management network element.
  • the user terminal needs to reattach to the network to perform the service, resulting in the redistribution of the Internet Protocol (IP) address of the user terminal and the re-registration of the service domain.
  • IP Internet Protocol
  • the user terminal has to hang up and try again to perform the service normally.
  • the called service of the user terminal there are two processing schemes:
  • the serving gateway triggers the reset mobile management network element to initiate an International Mobile Subscriber Identity (IMSI) or a temporary mobile subscriber identity (S-Temporary Mobile Subscriber Identity, S- TMSI) or Packet Temporary Mobile Subscriber Identity (P-TMSI) paging.
  • IMSI International Mobile Subscriber Identity
  • S-Temporary Mobile Subscriber Identity S- TMSI
  • P-TMSI Packet Temporary Mobile Subscriber Identity
  • the mobility management network element of the service user terminal is reset, the user terminal needs to be reattached to the network to perform the service, and the continuity of the service of the user terminal cannot be guaranteed.
  • the embodiment of the invention provides a processing method, device and system for resetting a mobile management network element,
  • the context of the user terminal is obtained from the service gateway, thereby ensuring the continuity of the service of the user terminal.
  • the technical solution adopted by the embodiment of the present invention is:
  • a method for processing a mobility management network element reset includes:
  • the mobility management network element obtains the context of the user terminal saved by the service gateway from the service gateway of the service user terminal;
  • a mobile management network element including:
  • a context obtaining unit configured to acquire, from a serving gateway of the service user terminal, a context of the user terminal saved by the service gateway;
  • an establishing unit configured to establish, for the user terminal, a signaling connection of the signaling message and/or the service data according to the context of the user terminal.
  • a service gateway including:
  • a saving unit configured to save a context of the user terminal served by the reset mobility management network element after learning that the mobility management network element is reset;
  • a receiving unit configured to receive a context request message related to the user terminal
  • a sending unit configured to send, after the receiving unit receives the context request message, a context of the user terminal saved by the saving unit to a mobile management network element that sends the context request message.
  • a processing system for resetting a mobility management network element comprising: a mobility management network element and a monthly service gateway; the service gateway, configured to save the reset mobility management network element after learning that the mobility management network element is reset Context of the served user terminal, and after receiving the context request message related to the user terminal, sending the saved context of the user terminal to the mobility management network element that sends the context request message; Context, and establishing a transport connection of signaling messages and/or service data for the user terminal according to the context of the user terminal.
  • FIG. 1 is a schematic diagram of a logical architecture of a next generation mobile communication network
  • FIG. 2 is a flowchart of a method for processing a mobility management network element reset according to an embodiment of the present invention
  • FIG. 4 is a flowchart of a method for processing a mobile management network element reset in a user terminal as a called party according to an embodiment of the present invention
  • FIG. 5 is a flowchart of a method for processing a mobile management network element reset according to an embodiment of the present invention when a user terminal is used as a calling party;
  • FIG. 6 is a flow chart of user temporary identification redistribution in an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a mobility management network element according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a service gateway according to an embodiment of the present invention.
  • FIG. 9 is another schematic structural diagram of a service gateway according to an embodiment of the present invention.
  • the next-generation mobile communication network may be an Evolved Packet System (EPS) network, as shown in FIG. 1, where the radio access network may be a universal terrestrial radio access network (Universal Terrestrial) Radio Access Network (UTRAN) I GSM/EDGE Radio Access Network (GERAN) / Evolved Universal Terrestrial Radio Access Network (E-UTRAN), the mobility management network element can be Mobility Management Entity ( Mobility Management Entity (MME) or GPRS Service Support Node (SGSN), the service gateway can be a Serving Gateway (S-GW), and the data gateway can be a Packet Data Network Gateway (PDN). -GW).
  • MME Mobility Management Entity
  • SGSN GPRS Service Support Node
  • S-GW Serving Gateway
  • PDN Packet Data Network Gateway
  • FIG. 2 it is a flowchart of a method for processing a mobility management network element reset according to an embodiment of the present invention, which includes the following steps:
  • Step 201 The mobility management network element acquires, according to a service gateway of the service user terminal, a context of the user terminal saved by the service gateway.
  • Step 202 Establish a transmission connection of the signaling message and/or the service data for the user terminal according to the context of the user terminal.
  • the transmitting connection for establishing signaling messages and/or service data for the user terminal according to the context of the user terminal includes:
  • the mobility management network element establishes a user plane tunnel between the radio access network and the serving gateway according to the acquired context of the user terminal, establishes a control plane tunnel between the mobility management network element and the serving gateway, and establishes a radio access network.
  • the tunnel information and the tunnel information of the mobility management network element are sent to the serving gateway; triggering the establishment of the radio bearer between the user terminal and the radio access network.
  • the mobility management network element is a mobility management network element after reset and restart
  • the user terminal is a service terminal served by the reset mobility management gateway
  • the reset mobility management network element may be the mobile in step 201.
  • the management network element can also be other mobile management network elements in the network. That is, the mobility management network element in step 201 may be a mobility management network element after resetting and restarting, and correspondingly, the user terminal is a user terminal of the month before the mobile management network element is reset; and, in addition, the mobile in step 201
  • the management network element may also be a normally operating mobility management network element, and the user terminal is a user terminal served by other mobile management network elements before resetting.
  • the method for processing the mobility management network element reset in the embodiment of the present invention may be applied to an EPS network, where the mobility management network element may be an S4 SGSN (General Packet Radio Service Support Node) or an MME (Mobility Management Entity, mobility management). Entity), the service gateway can be an SGW (Serving Gateway).
  • S4 SGSN General Packet Radio Service Support Node
  • MME Mobility Management Entity, mobility management. Entity
  • SGW Serving Gateway
  • the service management gateway resets the context information of the user terminal of the reset mobile management network element, so that the mobile management network element can be moved after resetting and restarting.
  • Management network element or other mobile management network that works normally.
  • the service request process of the terminal ensures the operation of the user service.
  • the service gateway needs to be configured. After the service gateway learns that the mobility management network element is reset, the context of the user terminal served by the reset mobility management network element is saved on the service gateway. If the user terminal is in the connected state, the serving gateway needs to release the user plane information of the SGSN, the RNC (Radio Network Controller), or the eNodeB (Evolved Node B) in the context, and retain the user. The remaining context of the terminal.
  • the processing method for resetting the mobility management network element in the embodiment of the present invention may also be directed only to a specific user terminal, which is referred to herein as a user terminal that initiates a reset processing mechanism, that is, to comply with the present invention.
  • the terminal of the processing mechanism of the embodiment of the invention; and for the user terminal that does not initiate the reset processing mechanism, the processing can be performed according to the existing conventional processing manner.
  • the method may further include:
  • the service gateway determines that the user terminal initiates a reset processing mechanism.
  • the service gateway may determine according to any one of the following manners:
  • the service gateway determines that the user terminal initiates a reset processing mechanism. That is to say, if the service gateway saves the user parameter of the user terminal served by a reset mobility management network element, the user terminal initiates a reset processing mechanism by default.
  • the user parameters include: a temporary identifier and a location identifier of the user terminal, and may further include: a security parameter.
  • the temporary identifier of the user terminal may be an S-TMSI, and the location identifier may be a TAI (Tracking Area Identity) list; if the mobility management network element is an S4 SGSN, The temporary identifier of the user terminal may be P-TMSI, and the location identifier may be a routed area identifier (RAI).
  • the security parameter is used for message encryption or integrity protection between the mobility management network element and the user, or for message encryption or integrity protection between the mobility management network element and the eNodeB or RNC. The process of the service gateway acquiring and saving the user parameters of the user terminal will be described in detail later.
  • the serving gateway determines, according to the reset processing mechanism indication information sent by the mobility management network element, that the user terminal initiates a reset processing mechanism.
  • the serving gateway deletes the bearer context in the context of the user terminal that is not allowed to start the reset processing mechanism, and retains the remaining context.
  • the service gateway is notified to store the user parameter of the user terminal, which is described in detail below.
  • FIG. 3 it is a flowchart of storing user parameters on a service gateway in the embodiment of the present invention.
  • the process corresponds to a process of attaching a user terminal or a PDP (Packet Data Protocol) context activation process, and includes the following steps:
  • Step 301 The user terminal sends an attach request/PDP context activation request message to the mobility management network element.
  • Step 302 After receiving the request message, the mobility management network element sends a setup session request message to a service gateway serving the user terminal.
  • Step 303 The service gateway returns a session establishment response message to the mobility management network element.
  • Step 304 After receiving the setup session response message, the mobility management network element sends an attach accept/PDP context activation accept message to the user terminal.
  • Step 305 The mobility management network element sends an update bearer request message to the serving gateway.
  • Step 306 The serving gateway returns an update bearer response message to the mobility management network element.
  • the foregoing process is a process for attaching a user terminal and a PDP context activation process when the mobile management network element works normally in the prior art.
  • the mobility management network element needs to carry the user terminal in the setup session request message or the update bearer request message sent to the serving gateway. User parameters. Accordingly, the service gateway stores the user parameters locally when received.
  • the user parameters of the user terminal are the S-TMSI and the TAI list, and may further include a security parameter, where the security parameter is used by the MME and the user terminal.
  • the parameter used for message encryption or integrity protection or may also be a parameter for message encryption or integrity protection between the MME and the eNodeB, such as the key K EN . DEB .
  • the user parameters of the user terminal are P-TMSI and RAI, and may further include a security parameter, which is used for message encryption or integrity protection between the SGSN and the user terminal.
  • the parameter or it may be a parameter for message encryption or integrity protection between the SGSN and the RNC, such as the key KRN
  • the mobility management network element can obtain multiple sets of security parameters from the HSS (Home Subscriber Server, the home subscriber register), in the above step 303 or step 305, the session request message or the update bearer request message may also be used as needed. It is also possible to include a plurality of sets of security parameters, which are not limited in this embodiment of the present invention.
  • the mobility management network element may directly send the security parameters obtained from the HSS to the serving gateway, or may generate a key from a security algorithm generated by the HSS and send the key to the serving gateway.
  • the mobility management network element sends a message to the serving gateway, where the message includes the latest S-TMSI/P-TMSI/TAI List. /RAI/Security parameters.
  • the message may be an existing tunnel management message or a new message, which is not limited in this embodiment.
  • the S-TMSI/P-TMSI/TAI List/RAI/Security Parameter Change Notification can occur in the mobility management process, the session management process, the user temporary identity redistribution process, the authentication process, or the security process.
  • the user terminal of the mobility management network element Before the mobility management network element is reset, the user terminal of the mobility management network element can use the processing mechanism of the embodiment of the present invention. Or further, the mobility management network element may determine, according to the user subscription data, or the established bearer context parameter, or the operator policy, which users adopt the processing mechanism of the embodiment of the present invention, or which users' contexts are implemented by the present invention.
  • the indication information for example, may be included in step 302 or step 305 of FIG.
  • the indication information may be user granularity or information of the bearer granularity, and is used to indicate that the serving gateway needs to start the processing mechanism of the embodiment of the present invention for the user terminal served by the mobile management network element after the resetting of the mobility management network element, or
  • the bearer context triggered service initiation of the user terminal The processing mechanism of the example.
  • the processing mechanism of the embodiment of the present invention is started for a high-priority user in the network, or the processing mechanism of the embodiment of the present invention is initiated for a user who has an IMS (IP Multimedia Subsystem) call in the network.
  • IMS IP Multimedia Subsystem
  • the manner in which the specific mobility management network element notifies the service gateway of the indication information may be implemented by one of the following:
  • the mobility management network element includes the indication information in the tunnel management message sent to the serving gateway, and indicates that the service gateway cannot be used for the user terminal or a bearer context starting mechanism of the user terminal, and one of them is not limited.
  • the situation may be:
  • the indication information is not included in the tunnel management message.
  • the service gateway is allowed to start the processing mechanism of the embodiment of the present invention by default.
  • the mobility management network element includes the indication information in the tunnel management message sent to the serving gateway, and indicates that the serving gateway initiates the processing mechanism of the embodiment of the present invention for the user terminal or a bearer context of the user terminal.
  • the processing mechanism of the embodiment of the present invention is not activated.
  • One of the cases is: when the tunnel management message received by the serving gateway does not include an indication to start the processing mechanism of the embodiment of the present invention, then the service The gateway cannot initiate the processing mechanism of the embodiment of the present invention for the user terminal or a certain bearer context of the user terminal.
  • the mobility management network element includes the indication information in the tunnel management message sent to the serving gateway, where the indication information is used to indicate that the service gateway starts or does not start the processing mechanism of the embodiment of the present invention.
  • the service request process of the user terminal can be processed normally to ensure the operation of the user service.
  • the user terminal is used as the called party and the calling party as an example, and the processing method of applying the mobile management network element reset in the embodiment of the present invention to the call processing process of the user terminal after the mobility management network element is reset is further described in detail.
  • FIG. 4 it is a flowchart of a method for processing a mobile management network element reset in the embodiment of the present invention when the user terminal is called.
  • the radio access network may be a 3GPP (3rd Generation Partnership Project) access of GERAN/UTRAN/E-UTRAN, respectively corresponding to the BSS.
  • the mobility management network element can be S4 SGSN or MME
  • the service gateway can be SGW
  • the data gateway can be PGW
  • HSS is responsible for attribution Management and maintenance of local user subscription information.
  • the process includes the following steps:
  • Step 401 After the mobility management network element is reset, the serving gateway detects that the mobility management network element is reset. For example, the serving gateway obtains the mobility management network element reset by using the path detection message sent by the mobility management network element or the value of the reset counter included in the tunnel management message, if the value of the reset counter is related to the mobility management network element locally stored by the service gateway. If the value of the reset counter is different, the serving gateway learns that the mobility management network element is reset. There are two scenarios for the mobility management network element reset. The mobility management network element reset has been restarted, or the mobility management network element reset has not been restarted. The service gateway knows that the mobility management network element is reset by knowing that the mobile management network element reset has been restarted.
  • the service gateway can be learned by other methods. For example, when the service gateway does not receive the response message after sending the multiple path detection message, the service gateway learns that the mobility management network element reset is not restarted.
  • the service gateway learns that the mobility management network element is reset, the context of the user terminal served by the reset mobile management network element is retained according to the pre-configuration.
  • the serving gateway releases the user plane information of the SGSN, the RNC or the eNodeB in the context of the user terminal, for example, the IP address and the TEID (Tunnel Endpoint IDentifier), and the remaining context of the user terminal is reserved. .
  • the foregoing operation of the serving gateway may be directed only to the user terminal that starts the reset processing mechanism.
  • the user terminal that starts the service processing mechanism is a user terminal that stores user parameters on the service gateway, and the user parameters include a temporary identifier S-TMSI/P-TMSI and a location identifier TAI List/RAI of the user terminal, and may further include a security parameter.
  • the user terminal that initiates the service processing mechanism is a user terminal that initiates the reset processing mechanism by the mobile management network element through a reset process.
  • the specific indication method has been described in detail above, and is not described herein.
  • the serving gateway may also delete the bearer context that is not allowed to start the reset processing mechanism, and reserve the remaining context of the user terminal.
  • the service gateway can start certain The timer is the node granularity of the reset-based mobility management network element, or is based on the granularity of the user terminal that retains the user context.
  • the user terminal-based timer may be a reset mobile management network element that is notified to the serving gateway through a tunnel management message before resetting, or may be obtained by the serving gateway from other network entities, or may be locally configured on the serving gateway.
  • the serving gateway deletes the relevant user context.
  • Step 402 The serving gateway receives the downlink data packet sent by the data gateway, where the downlink data packet may be a signaling message or a service data packet of the user terminal, where the user terminal is a user terminal served before the mobility management network element is reset.
  • Step 403 The serving gateway sends a message to the mobility management network element, where the message includes the parameter of the user terminal corresponding to the downlink data packet.
  • the mobility management network element is the MME
  • the parameters include IMSI, S-TMSI, TAI List, and may also include security parameters.
  • the mobility management network element is an S4 SGSN
  • the parameters include IMSI, P-TMSI, RAI, and may also include security parameters.
  • the message is a downstream packet notification message or a new message.
  • the parameter of the user terminal is used to instruct the mobility management network element to initiate an S-TMSI/P-TMSI-based paging within the range of the TAI list/RAI, and the security parameter is used in the radio access network and the mobility management network element in the subsequent process. Encryption or integrity protection of messages, or encryption or integrity protection of messages from user terminals and mobility management network elements.
  • the serving gateway selects any mobile management network element serving the location area where the user terminal is located to send a message, and the selected mobility management network element may be the reset mobile management network. If the mobile management network element does not restart after reset, the monthly service gateway selects any mobile service management network element in the location area where the user terminal is located except the reset mobile management network element to send a message.
  • Step 404 After receiving the message sent by the serving gateway, the mobility management network element initiates a paging to the user terminal. If the mobility management network element is the MME, the MME initiates an S-TMSI paging to the user terminal within a plurality of tracking areas identified by the TAI List. If the mobility management network element is the S4 SGSN, the S4 SGSN is in the routing area of the RAI identifier. P-TMSI paging is initiated to the user terminal.
  • Step 405 After receiving the paging message, the user terminal sends a service request message to the mobility management network element.
  • the service request message is sent to the mobility management network element via the radio access network.
  • the radio access network learns the mobility management network element of the monthly service user terminal by using the temporary identifier of the user terminal included in the RRC (Radio Resource Control) message sent by the user terminal. For mobile management network If the radio access network does not find that the mobility management network element corresponding to the temporary identifier is unavailable, the radio access network selects any location area where the user terminal is located, except the non-step 406: Mobile Management Network The element authenticates the user terminal and obtains new security parameters from the HSS.
  • RRC Radio Resource Control
  • Step 407 The mobility management network element registers with the HSS, and acquires subscription data of the user terminal.
  • Step 408 The mobility management network element sends a request message to the serving gateway, where the message is used to request the context of the user terminal reserved on the service gateway.
  • the message includes the IMSI of the user terminal and/or the temporary identifier S-TMSI or P-TMSL of the user terminal. If the mobile management network element selected by the radio access network and the serving gateway is not the same node, the mobile management of the service request message is received.
  • the network element learns the service gateway serving the user terminal through the temporary identifier of the user terminal, and sends a request message to the service gateway. If the mobility management network element selected by the radio access network and the monthly service gateway is the same node, the mobility management network element sends a request message to the serving gateway that sends the message of step 403.
  • Step 409 After receiving the request message of the mobility management network element, the serving gateway sends a response message to the mobility management network element, where the response message includes the context of the user terminal.
  • the context of the user terminal may or may not include the parameters of the user terminal sent in step 403.
  • the request message and the response message of the foregoing steps 408 and 409 may be an existing message or a newly added message, and the message name is not limited.
  • step 408 may be performed in parallel with step 404, or may be performed after step 405.
  • step 406 and step 407 may be performed in parallel with other messages, or may be performed after the service request process, unless the mobile management network element must perform authentication and subscription data acquisition on the user terminal in some cases, and steps 406 and 407 are required in steps.
  • the user terminal moves out of the tracking area registration area, or the user terminal enters a CSG (Closed Subscriber Group) access.
  • CSG Cell Subscriber Group
  • Step 410 Establish a radio bearer between the user terminal and the radio access network, and the mobility management network element establishes a user plane tunnel between the radio access network and the network side.
  • the mobility management network element establishes a tunnel between the radio access network and the serving gateway, such as the serving gateway IP address and the TEID, through the information in the context of the user terminal sent by the serving gateway in step 409.
  • the mobility management network element will also have security parameters such as K EN .
  • the deB or KRNC is sent to the access network, and the security parameter is obtained from the serving gateway or from the HSS through the serving gateway. Get the generated security vector.
  • Step 411-413 The mobility management network element sends the tunnel information of the radio access network and the tunnel information of the mobility management network element to the serving gateway by updating the bearer process, and the monthly service gateway performs bearer update.
  • the serving gateway when the user terminal served by the mobility management network element is used as the called party, the serving gateway sends the parameter of the user terminal to the downlink data packet of the user terminal.
  • the mobile management network element currently serving the user terminal the mobility management network element acquires the context of the user terminal from the service gateway according to the parameter, thereby establishing a transmission connection of the service data of the user terminal according to the context, and ensuring the user service. get on.
  • the mobility management network element can learn the service gateway of the service user terminal by using the temporary identifier of the user: S-TMSI/P-TMSI.
  • the allocation method in which the mobility management network element includes the information of the service gateway of the service user terminal in the temporary identifier is as shown in FIG. 6.
  • FIG. 5 it is a flowchart of a method for processing a mobile management network element reset in the embodiment of the present invention when the user terminal is used as a calling party.
  • the radio access network may be a 3GPP (3rd Generation Partnership Project) access of GERAN/UTRAN/E-UTRAN, corresponding to a BSS (Base Station Subsystem) / RNS (Radio) Network Subsystem, the eNodeB, the mobility management network element may be the S4 SGSN or the MME, the service gateway may be the SGW, the data gateway may be the PGW, and the HSS is responsible for the management and maintenance of the home subscriber subscription information.
  • 3GPP 3rd Generation Partnership Project
  • GERAN/UTRAN/E-UTRAN corresponding to a BSS (Base Station Subsystem) / RNS (Radio) Network Subsystem
  • the eNodeB the mobility management network element may be the S4 SGSN or the MME
  • the service gateway may be the SGW
  • the data gateway may be the PGW
  • the HSS is responsible for the management and maintenance of the home subscriber subscription information.
  • the process includes the following steps:
  • Step 501 The user terminal initiates a service request process, and sends a service request message to the mobility management network element, where the message includes the temporary identifier S-TMSI of the user terminal or the P-TMSL mobility management network element receives the request message, and then passes the message.
  • the included S-TMSI or P-TMSI cannot find the corresponding user context.
  • the service request message is sent to the mobility management network element via the radio access network.
  • the radio access network learns the mobility management network element of the service user terminal by using the temporary identifier of the user terminal carried in the received radio resource management message sent by the user terminal. If the mobile management network element reset does not restart, if the radio access network finds that the mobility management network element corresponding to the temporary identifier is unavailable, the radio access network selects any location area where the user terminal is located, except the unavailable one.
  • Mobile management network The mobility management network element outside the element sends a service request message.
  • Step 502 The mobility management network element authenticates the user terminal, and obtains new security parameters from the HSS.
  • Step 503 The mobility management network element registers with the HSS, and acquires subscription data of the user terminal.
  • Step 504 The mobility management network element learns the service gateway serving the user terminal by using the temporary identifier of the user terminal, and sends a request message to the service gateway, where the message is used to request the context of the user terminal reserved on the service gateway.
  • the message includes the temporary identifier of the user terminal in step 501, S-TMSI or P-TMSL.
  • Step 505 After receiving the request message of the mobility management network element, the serving gateway sends a response message to the mobility management network element, where the response message includes the context of the user terminal.
  • the processing on the service gateway is consistent with the processing of step 401 in the above-mentioned process shown in FIG.
  • request message and the response message in steps 504 and 505 may be existing messages, or may be new messages, and the message names are not limited.
  • step 502 and step 503 may be performed in parallel with other messages, or may be performed after the service request process, unless in some cases the mobility management network element must perform authentication and subscription data acquisition on the user terminal, Step 502 and step 503 are performed after step 501.
  • the user terminal moves out of the tracking area registration area, or the user terminal enters CSG access or the like.
  • Step 506 The user terminal establishes a radio bearer, and a user plane tunnel between the radio access network and the network side.
  • the mobility management network element establishes a tunnel between the access network and the serving gateway, such as the serving gateway IP address and the TEID, through the information in the context of the user terminal sent by the serving gateway in step 505.
  • the mobility management network element will also have security parameters such as K EN .
  • the deB or KRNC is sent to the radio access network, and the security parameter is generated from the security gateway obtained from the serving gateway or obtained from the HSS through the serving gateway.
  • Steps 507-509 The mobility management network element sends the tunnel information of the radio access network and the tunnel information of the mobility management network element to the serving gateway by using the update bearer process, and the service gateway performs bearer update.
  • the mobile management network element when the user terminal served by the mobility management network element acts as the calling party, the mobile management network element currently serving the user terminal receives the service request of the user terminal, according to the When the temporary identifier of the user terminal included in the service request message cannot find the user context corresponding thereto, the context of the user terminal is obtained from the service gateway, and the root The transmission connection of the signaling message and/or the service data of the user terminal is established according to the context of the user terminal, thereby ensuring the progress of the user service.
  • the mobility management network element can obtain the service gateway of the service user terminal by using the temporary identifier of the user: S-TMSI/P-TMSI, and the temporary management identifier of the user can be allocated in multiple ways when the mobile management network element works normally, and
  • the information of the service gateway serving the user terminal is included in the temporary identifier, and the information of the service gateway may be an IP address of the service gateway, a fully Qualified Domain Name (FQDN), or a service gateway number. Etc., for example, below.
  • FIG. 6 it is a flowchart of user temporary identification re-allocation in the embodiment of the present invention, which includes the following steps:
  • Step 601 The mobility management network element initiates a user temporary identity re-allocation process, and sends a temporary identity redistribution request message to the user terminal. This process can be triggered by a variety of reasons, such as changing the service gateway of the service user terminal.
  • the message may be a GUTI (Globally Unique Temporary Identity) message, and the message includes a temporary allocation of the mobility management network element to the user terminal. Identify GUTI.
  • the GUTI includes S-TMSI, and the mobility management network element includes information of the service gateway serving the user terminal in the S-TMSI and is allocated to the user terminal.
  • the message may be a P-TMSI Reallocation Command (P-TMSI Reallocation Command) message, where the message includes a temporary identity P-TMSI assigned by the mobility management network element to the user terminal, and mobility management.
  • P-TMSI Reallocation Command P-TMSI Reallocation Command
  • the network element allocates the information of the monthly service gateway of the user terminal to the user terminal in the P-TMSI.
  • Step 602 The user terminal replies with a GUTI Reallocation Complete or a P-TMSI Reallocation Complete message.
  • the mobility management network element can find the service gateway of the service user terminal according to the service gateway node information included in the S-TMSI or the P-TMSI.
  • the mobility management network element may also allocate the temporary identifier of the user terminal by using an existing mobility management process or a session management process. For example, tracking area updates, routing area updates, or switching processes The temporary identifier of the user terminal can be assigned. In the above manner, the mobility management network element allocates the monthly service gateway node information to the user terminal in the temporary identifier.
  • the embodiment of the present invention further provides a mobility management network element, as shown in FIG. 7, which is a schematic structural diagram of the mobility management network element.
  • the mobility management network element includes:
  • the context obtaining unit 701 is configured to obtain, by using a service gateway of the service user terminal, a context of the user terminal saved by the service gateway;
  • the establishing unit 702 is configured to establish a transmission connection of the signaling message and/or the service data for the user terminal according to the context of the user terminal.
  • the establishing unit 702 is specifically configured to establish a user plane tunnel between the radio access network and the serving gateway according to the context of the user terminal acquired by the context obtaining unit 701, and establish a control plane tunnel between the mobility management network element and the serving gateway. And transmitting the tunnel information of the established radio access network and the tunnel information of the mobility management network element to the serving gateway; triggering establishment of a radio bearer between the user terminal and the radio access network.
  • the mobility management network element further includes:
  • a first receiving unit 703 configured to receive a service request message sent by the user terminal, where the second receiving unit 704 is configured to receive a request message that is sent by the serving gateway and includes a user parameter of the user terminal;
  • the context obtaining unit 701 is specifically configured to: after the first receiving unit 703 receives the service request message sent by the user terminal, according to the temporary identifier of the user terminal included in the service request message, the user context corresponding to the user terminal cannot be found, Obtaining the context of the user terminal from the serving gateway; or obtaining the context of the user terminal from the serving gateway after the second receiving unit 704 receives the request message that is sent by the serving gateway and includes the user parameter of the user terminal.
  • the user parameter includes a temporary identifier of the user terminal.
  • the temporary identifier of the user terminal may include information of the monthly service gateway of the user terminal.
  • the context obtaining unit 701 is further configured to use the user terminal according to the user terminal.
  • the temporary identity is known to serve the service gateway of the user terminal.
  • the mobility management network element further includes: a user parameter notification unit and a user parameter update unit, where:
  • the user parameter notification unit is configured to send the user parameter of the user terminal to the service gateway in an attach procedure or a PDP context activation process of the user terminal;
  • the user parameter update unit is configured to send the latest user parameter to the mobility management process, the session management process, the user temporary identity redistribution process, the authentication process, or the security process after the user parameter changes The service gateway.
  • the mobile management network element of the embodiment of the present invention after resetting and restarting, obtains the context of the user terminal saved by the service gateway from the serving gateway of the service user terminal, and according to the user terminal
  • the context establishes a transmission connection of the signaling message and/or service data of the user terminal, so that the service request process can be processed normally, and the user service is guaranteed.
  • the embodiment of the present invention further provides a service gateway, as shown in FIG. 8, which is a schematic structural diagram of the service gateway.
  • the monthly service gateway includes:
  • a saving unit 801 configured to save a context of the user terminal served by the reset mobile management network element after learning that the mobility management network element is reset;
  • the receiving unit 802 is configured to receive a context request message related to the user terminal
  • the sending unit 803 is configured to send, after the receiving unit 802 receives the context request message, the context of the user terminal saved by the saving unit 801 to the sending The mobility management network element of the context request message.
  • the service gateway of the embodiment of the present invention saves the context of the user terminal of the reset mobile management network element; and after receiving the context request message sent by the mobility management network element, The saved user terminal's context can be sent to the mobility management network element, so that after the mobility management network element is reset, the user terminal's service request flow can be processed normally, and the user service can be guaranteed.
  • the service gateway may further include:
  • a release unit (not shown) is configured to release user plane information of the SGSN, RNC, or eNodeB in the context of the user terminal when the user terminal is in the connected state. In this way, resources can be further optimized to avoid excessive occupation of network resources.
  • the serving gateway may perform the reset processing mechanism described above only for the user terminal that initiated the reset processing mechanism.
  • FIG. 9 is another schematic structural diagram of a service gateway according to an embodiment of the present invention.
  • the service gateway further includes: a determining unit 804, configured to determine that the mobility management network element is reset after the user terminal starts the reset processing mechanism, Saving the context of the user terminal in the saving unit 801
  • the receiving unit 802 is further configured to receive a user parameter of the user terminal that is sent by the mobility management network element.
  • the saving unit 901 is further configured to save the user parameter.
  • the determining unit 804 is specifically configured to: when the saving unit saves the user parameter of the user terminal, determine that the user terminal starts the reset processing mechanism.
  • the receiving unit 802 is further configured to receive the reset processing mechanism indication information sent by the mobility management network element.
  • the determining unit 804 is specifically configured to perform the reset processing according to the The mechanism indication information determines that the user terminal has initiated a reset processing mechanism.
  • the releasing unit is further configured to: when the indication information is the indication information of the bearer granularity, delete the bearer context in the context of the user terminal that is not allowed to start the reset processing mechanism.
  • the receiving unit 802 is further configured to receive a downlink data packet of the user terminal that is sent by the data gateway, where the sending unit 803 is further configured to: after the receiving unit 802 receives the downlink data packet of the user terminal, The user parameter of the user terminal saved by the saving unit 801 is sent to the mobility management network element, so that the mobility management network element initiates paging to the user terminal according to the parameter.
  • the mobility management network element and the monthly service gateway of the embodiment of the present invention can still process the service request process of the user terminal served by the reset mobility management network element after the mobility management network element is reset, and ensure the user service progress. Improve the performance of your network.
  • the mobile management network element and the service gateway may refer to the description in the processing method of the mobility management network element reset in the foregoing embodiment of the present invention.
  • the embodiment of the present invention further provides a processing system for resetting a mobility management network element, where the system includes: a mobility management network element and a service gateway;
  • the service gateway is configured to save a context of the user terminal served by the reset mobility management network element after learning that the mobility management network element is reset, and receive a context related to the user terminal After the request message, the saved context of the user terminal is sent to the mobility management network element that sends the context request message;
  • the mobility management network element is configured to obtain, from the service gateway, a context of the user terminal saved by the service gateway, and establish a transmission connection of the signaling message and/or the service data for the user terminal according to the context of the user terminal.
  • the mobile mobility management network element establishes a user plane tunnel between the radio access network and the serving gateway according to the acquired context of the user terminal, and establishes a control plane tunnel between the mobility management network element and the serving gateway, and the established
  • the tunnel information of the radio access network and the tunnel information of the mobility management network element are sent to the serving gateway; the radio bearer is established between the triggering user terminal and the radio access network.

Landscapes

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

Abstract

L'invention porte sur un procédé, un dispositif et un système de traitement de réinitialisation d'un élément de réseau de gestion de mobilité. Le procédé comprend les étapes suivantes : après la réinitialisation d'un élément de réseau de gestion de mobilité, obtention, en provenance d'une passerelle de desserte desservant un terminal utilisateur, du contexte du terminal utilisateur stocké par la passerelle de desserte, le terminal utilisateur étant le terminal utilisateur desservi par l'élément de réseau de gestion de mobilité avant réinitialisation (201); et établissement de la connexion de transmission de message de signalisation et/ou de données de service pour le terminal utilisateur conformément au contexte du terminal utilisateur (202).
PCT/CN2011/070489 2011-01-21 2011-01-21 Procédé, dispositif et système de traitement de réinitialisation d'élément de réseau de gestion de mobilité WO2012097524A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN2011800004365A CN102907126A (zh) 2011-01-21 2011-01-21 移动管理网元复位的处理方法、设备及系统
PCT/CN2011/070489 WO2012097524A1 (fr) 2011-01-21 2011-01-21 Procédé, dispositif et système de traitement de réinitialisation d'élément de réseau de gestion de mobilité

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/070489 WO2012097524A1 (fr) 2011-01-21 2011-01-21 Procédé, dispositif et système de traitement de réinitialisation d'élément de réseau de gestion de mobilité

Publications (1)

Publication Number Publication Date
WO2012097524A1 true WO2012097524A1 (fr) 2012-07-26

Family

ID=46515102

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/070489 WO2012097524A1 (fr) 2011-01-21 2011-01-21 Procédé, dispositif et système de traitement de réinitialisation d'élément de réseau de gestion de mobilité

Country Status (2)

Country Link
CN (1) CN102907126A (fr)
WO (1) WO2012097524A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101540990A (zh) * 2008-03-19 2009-09-23 华为技术有限公司 实现寻呼处于寻呼盲区的用户的方法及系统
CN101646270A (zh) * 2008-08-06 2010-02-10 华为技术有限公司 保持业务连续的方法、系统、移动性管理实体和存储设备
CN101730124A (zh) * 2008-10-29 2010-06-09 华为技术有限公司 恢复业务的方法、装置和系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101540990A (zh) * 2008-03-19 2009-09-23 华为技术有限公司 实现寻呼处于寻呼盲区的用户的方法及系统
CN101646270A (zh) * 2008-08-06 2010-02-10 华为技术有限公司 保持业务连续的方法、系统、移动性管理实体和存储设备
CN101730124A (zh) * 2008-10-29 2010-06-09 华为技术有限公司 恢复业务的方法、装置和系统

Also Published As

Publication number Publication date
CN102907126A (zh) 2013-01-30

Similar Documents

Publication Publication Date Title
RU2749750C1 (ru) Управление разрывом услуги для беспроводного устройства
WO2009094916A1 (fr) Procédé, système et dispositif de commande pour redémarrage après défaillance dans le domaine circuit
WO2009097818A1 (fr) Procédé, dispositif et système pour fournir un accès d'urgence à un dispositif utilisateur
WO2015062098A1 (fr) Procédé de sélection de réseau et dispositif de réseau central
WO2011157166A2 (fr) Procédé de traitement de restauration de service et élément de réseau de gestion de mobilité
JP2010539758A (ja) Ｌｔｅシステムにおいて、ユーザ静的ｉｐアドレスのアドレッシングをサポートする方法、システムおよび装置
WO2009043209A1 (fr) Procédé permettant d'établir une porteuse vers un terminal utilisateur en mode repos
WO2011098051A1 (fr) Procédé, appareil et système pour le traitement de services prioritaires
WO2010031353A1 (fr) Procédé, dispositif et système de traitement de demande de service
WO2018059401A1 (fr) Procédé, dispositif et système de commutation de réseau, et procédé et dispositif d'accès au réseau
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
WO2013047200A1 (fr) Système, procédé et programme de communication
WO2011023091A1 (fr) Procédé et système de gestion du repli vers une transmission vocale à commutation de circuits dans un réseau
WO2013139235A1 (fr) Procédé et dispositif de radiomessagerie
WO2014166294A1 (fr) Méthode et appareil de sélection de serveur de service de proximité, et méthode et appareil d'inscription d'utilisateur
WO2008138197A1 (fr) Procédé pour vérifier le paramètres qos et dispositif de communication côté réseau
US20240276196A1 (en) Indication information sending method, apparatus and system, and storage medium
JP6446546B2 (ja) データ処理方法、装置、端末、モビリティ管理エンティティ、およびシステム
WO2013104111A1 (fr) Procédé pour le rétablissement d'un service et élément de réseau de gestion de la mobilité
WO2010054544A1 (fr) Procédé de radiomessagerie dans un système évolué de domaine paquet de communication mobile
WO2018045928A1 (fr) Procédé et dispositif de commande d'encombrement de réseau
WO2008154783A1 (fr) Procédé pour établir un tunnel à partir de sgsn vers la passerelle de service
EP3484234B1 (fr) Procédé, dispositif et appareil de gestion de contexte d'équipement d'utilisateur
WO2009149656A1 (fr) Procédé, dispositif et système permettant la mise en œuvre d'un transfert de service
US20150063310A1 (en) Method and Apparatus for Removing Policy and Charging Control Rule from Default Bearer

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180000436.5

Country of ref document: CN

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

Ref document number: 11856193

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

Country of ref document: EP

Kind code of ref document: A1