CN101646270A - Method, system, mobility management entity and memory device for maintaining service continuity - Google Patents
Method, system, mobility management entity and memory device for maintaining service continuityDownload PDFInfo
- Publication number
- CN101646270A CN101646270ACN200810117850ACN200810117850ACN101646270ACN 101646270 ACN101646270 ACN 101646270ACN 200810117850 ACN200810117850 ACN 200810117850ACN 200810117850 ACN200810117850 ACN 200810117850ACN 101646270 ACN101646270 ACN 101646270A
- Authority
- CN
- China
- Prior art keywords
- identification information
- mobility management
- management entity
- information
- bearer
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
Translated fromChineseDescription
Translated fromChinese技术领域technical field
本发明涉及无线通信领域，特别涉及一种保持业务连续的方法、系统、移动性管理实体和存储设备。The invention relates to the field of wireless communication, in particular to a method, system, mobility management entity and storage device for maintaining service continuity.
背景技术Background technique
为了适应通信技术的发展，3GPP(3rd Generation Partnership Project，第三代合作伙伴计划)组织制定了无线网络演进计划。当前无线网络演进的版本为R8版本，即SAE(SystemArchitecture Evolution，系统架构演进)。In order to adapt to the development of communication technology, 3GPP (3rd Generation Partnership Project, 3rd Generation Partnership Project) organized a wireless network evolution plan. The current wireless network evolution version is the R8 version, namely SAE (System Architecture Evolution, system architecture evolution).
为了保持业务的连续性，SAE提出了MME POOL(Mobility Management Entity POOL，移动性管理实体资源池)的方案。MME POOL由多个功能一致的MME构成，UE(UserEquipment，用户设备)在MME POOL的服务区域内不需要更换服务的MME。MME POOL具备保持业务连续的特性，即当资源池中为用户服务的一个MME设备出现故障，可以切换到另一MME设备，继续为该用户服务。In order to maintain business continuity, SAE proposed the MME POOL (Mobility Management Entity POOL, mobility management entity resource pool) solution. The MME POOL is composed of multiple MMEs with the same functions, and the UE (User Equipment, user equipment) does not need to replace the serving MME within the service area of the MME POOL. MME POOL has the feature of maintaining business continuity, that is, when an MME device serving a user in the resource pool fails, it can be switched to another MME device to continue serving the user.
参见图1，MME POOL中有MME1、MME2和MME3三个控制设备，E-UTRAN(EvolvedUMTS(Universal Mobile Telecommunications System，通用移动通信系统)Territorial RadioAccess Network，演进的UMTS陆地无线接入网)、S-GW(Serving Gateway，服务网关)和HSS(Home Subscriber Server，归属用户服务器)均与POOL内所有MME连接，其中，E-UTRAN负责将用户会话分发到MME。例如，注册在MME1下的UE1发起业务请求，在业务请求中会携带MME1的标识，E-UTRAN根据这个标识，可以把业务请求路由到MME1。当MME1故障时，E-UTRAN到MME1的路由不通，E-UTRAN可以把业务请求路由到MME2或MME3。由于MME2和MME3没有UE1的用户数据，向E-UTRAN返回一个失败响应，eNodeB释放与UE1的无线承载，用户业务数据中断。UE1重新发起附着流程，附着到MME2或MME3才能重新开始业务。Referring to Figure 1, there are three control devices MME1, MME2 and MME3 in the MME POOL, E-UTRAN (EvolvedUMTS (Universal Mobile Telecommunications System, Universal Mobile Communications System) Territorial RadioAccess Network, evolved UMTS Terrestrial Radio Access Network), S-UTRAN Both GW (Serving Gateway, Service Gateway) and HSS (Home Subscriber Server, Home Subscriber Server) are connected to all MMEs in the POOL, and E-UTRAN is responsible for distributing user sessions to MMEs. For example, when UE1 registered under MME1 initiates a service request, the service request will carry the identifier of MME1, and E-UTRAN can route the service request to MME1 according to the identifier. When MME1 fails, the route from E-UTRAN to MME1 is blocked, and E-UTRAN can route service requests to MME2 or MME3. Since MME2 and MME3 do not have the user data of UE1, they return a failure response to the E-UTRAN, the eNodeB releases the radio bearer with UE1, and the user service data is interrupted. UE1 re-initiates the attach procedure, and only after attaching to MME2 or MME3 can the service be restarted.
在实现本发明的过程中，发明人发现现有技术至少存在以下问题：In the process of realizing the present invention, the inventor finds that there are at least the following problems in the prior art:
MME POOL中某一MME发生故障，该MME会丢失与自身会话的所有用户的上下文信息，虽然POOL中的其他MME可以继续为这些用户服务，但是，这些MME没有用户的上下文信息，会使用户的数据业务中断，用户必须重新发起附着流程，附着到其他MME上，才能重新开始会话。由于期间用户的数据业务中断，会使用户体验非常差。MME If a certain MME in the POOL fails, the MME will lose the context information of all users in conversation with itself. Although other MMEs in the POOL can continue to serve these users, these MMEs do not have user context information, which will make the user’s If the data service is interrupted, the user must re-initiate the attach process to attach to another MME before restarting the session. Since the user's data service is interrupted during this period, the user experience will be very poor.
发明内容Contents of the invention
为了实现当资源池中的移动性管理实体发生故障时，用户设备的数据业务不中断，本发明实施例提供了一种保持业务连续的方法、系统、移动性管理实体和存储设备。所述技术方案如下：In order to realize that when the mobility management entity in the resource pool fails, the data service of the user equipment is not interrupted, the embodiment of the present invention provides a method, system, mobility management entity and storage device for maintaining service continuity. Described technical scheme is as follows:
一种保持业务连续的方法，所述方法包括：A method of maintaining business continuity, the method comprising:
当第一移动性管理实体发生故障时，获取第一标识信息和第二标识信息，所述第一标识信息是存储设备的标识信息，所述存储设备用于存储所述第一移动性管理实体当前会话的第一承载上下文信息，所述第二标识信息是由所述第一移动性管理实体服务的处于连接态的用户设备的标识信息；When the first mobility management entity fails, acquire first identification information and second identification information, where the first identification information is identification information of a storage device, and the storage device is used to store the first mobility management entity First bearer context information of the current session, where the second identification information is identification information of a user equipment in a connected state served by the first mobility management entity;
从所述第一标识信息对应的存储设备中，根据所述第二标识信息获取所述用户设备对应的当前会话的第一承载上下文信息；Obtain, from the storage device corresponding to the first identification information, the first bearer context information of the current session corresponding to the user equipment according to the second identification information;
根据所述第一承载上下文信息，为所述用户设备建立承载。Establish a bearer for the user equipment according to the first bearer context information.
一种保持业务连续的系统，所述系统包括：存储设备和移动性管理实体；A system for maintaining business continuity, the system comprising: a storage device and a mobility management entity;
所述存储设备，用于备份第一移动性管理实体当前会话的第一承载上下文信息，接收所述移动性管理实体发送的恢复上下文请求，所述恢复上下文请求携带由所述第一移动性管理实体服务的用户设备的标识信息，并向所述移动性管理实体发送所述标识信息对应的所述第一承载上下文信息；The storage device is configured to back up the first bearer context information of the current session of the first mobility management entity, and receives a restore context request sent by the mobility management entity, where the restore context request carries the identification information of the user equipment served by the entity, and sending the first bearer context information corresponding to the identification information to the mobility management entity;
所述移动性管理实体，用于当第一移动性管理实体发生故障时，获取第一标识信息和第二标识信息，所述第一标识信息是存储设备的标识信息，所述第二标识信息是由所述第一移动性管理实体服务的处于连接态的用户设备的标识信息；从所述第一标识信息对应的存储设备中，根据所述第二标识信息获取所述用户设备对应的当前会话的第一承载上下文信息；根据所述第一承载上下文信息，为所述用户设备建立承载。The mobility management entity is configured to obtain first identification information and second identification information when the first mobility management entity fails, the first identification information is identification information of a storage device, and the second identification information is the identification information of the user equipment in the connected state served by the first mobility management entity; from the storage device corresponding to the first identification information, obtain the current information corresponding to the user equipment according to the second identification information The first bearer context information of the session; according to the first bearer context information, establish a bearer for the user equipment.
一种移动性管理实体，所述移动性管理实体包括：A mobility management entity, the mobility management entity comprising:
标识信息获取模块，用于当第一移动性管理实体发生故障时，获取第一标识信息和第二标识信息，所述第一标识信息是存储设备的标识信息，所述存储设备用于存储所述第一移动性管理实体当前会话的第一承载上下文信息，所述第二标识信息是由所述第一移动性管理实体服务的处于连接态的用户设备的标识信息；An identification information acquiring module, configured to acquire first identification information and second identification information when the first mobility management entity fails, the first identification information is identification information of a storage device, and the storage device is used to store the The first bearer context information of the current session of the first mobility management entity, the second identification information is identification information of a user equipment in a connected state served by the first mobility management entity;
上下文获取模块，用于从所述第一标识信息对应的存储设备中，根据所述第二标识信息获取所述用户设备对应的当前会话的第一承载上下文信息；A context acquiring module, configured to acquire the first bearer context information of the current session corresponding to the user equipment according to the second identification information from the storage device corresponding to the first identification information;
业务连续保持模块，用于根据所述第一承载上下文信息，为所述用户设备建立承载。A service continuity maintaining module, configured to establish a bearer for the user equipment according to the first bearer context information.
一种存储设备，所述存储设备包括：A storage device, the storage device comprising:
上下文备份模块，用于备份第一移动性管理实体当前会话的第一承载上下文信息；a context backup module, configured to back up the first bearer context information of the current session of the first mobility management entity;
上下文发送模块，用于接收第二移动性管理实体发送的恢复上下文请求，所述恢复上下文请求携带由所述第一移动性管理实体服务的用户设备的标识信息，并向所述第二移动性管理实体发送所述标识信息对应的所述第一承载上下文信息，使得所述第二移动性管理实体能够根据所述第一承载上下文信息，为所述用户设备建立承载。A context sending module, configured to receive a context restoration request sent by a second mobility management entity, where the context restoration request carries identification information of a user equipment served by the first mobility management entity, and sends the request to the second mobility management entity The management entity sends the first bearer context information corresponding to the identification information, so that the second mobility management entity can establish a bearer for the user equipment according to the first bearer context information.
本发明实施例通过从存储设备获取发生故障的移动性管理实体当前会话的承载上下文信息，根据该承载上下文信息为用户设备建立承载，实现了在移动性管理实体故障的情况下，用户的数据业务不中断的效果，大大提高了用户体验。In the embodiment of the present invention, by acquiring the bearer context information of the current session of the failed mobility management entity from the storage device, and establishing a bearer for the user equipment according to the bearer context information, the data service of the user is realized in the case of a failure of the mobility management entity. The uninterrupted effect greatly improves the user experience.
附图说明Description of drawings
图1是现有技术提供的MME POOL结构示意图；Fig. 1 is the MME POOL structural schematic diagram that prior art provides;
图2是本发明实施例1提供的保持业务连续的方法流程图；FIG. 2 is a flowchart of a method for maintaining business continuity provided by Embodiment 1 of the present invention;
图3是现有技术提供的SAE网络架构图；FIG. 3 is a SAE network architecture diagram provided by the prior art;
图4是本发明实施例1提供的保持业务连续的信令流程图；FIG. 4 is a signaling flow chart for maintaining service continuity provided by Embodiment 1 of the present invention;
图5是本发明实施例2提供的保持业务连续的系统结构示意图；FIG. 5 is a schematic structural diagram of a system for maintaining business continuity provided by Embodiment 2 of the present invention;
图6是本发明实施例2提供的保持业务连续的系统结构示意图；FIG. 6 is a schematic structural diagram of a system for maintaining service continuity provided by Embodiment 2 of the present invention;
图7是本发明实施例3提供的移动性管理实体结构示意图；FIG. 7 is a schematic structural diagram of a mobility management entity provided by Embodiment 3 of the present invention;
图8是本发明实施例3提供的移动性管理实体另一结构示意图；FIG. 8 is a schematic diagram of another structure of the mobility management entity provided by Embodiment 3 of the present invention;
图9是本发明实施例3提供的标识信息获取模块结构示意图；FIG. 9 is a schematic structural diagram of an identification information acquisition module provided by Embodiment 3 of the present invention;
图10是本发明实施例3提供的上下文获取模块结构示意图；FIG. 10 is a schematic structural diagram of a context acquisition module provided by Embodiment 3 of the present invention;
图11是本发明实施例3提供的业务联系保持模块结构示意图；Fig. 11 is a schematic structural diagram of a business contact maintenance module provided by Embodiment 3 of the present invention;
图12是本发明实施例3提供的上下文构建单元结构示意图；Fig. 12 is a schematic structural diagram of the context construction unit provided by Embodiment 3 of the present invention;
图13是本发明实施例4提供的存储设备结构示意图。FIG. 13 is a schematic structural diagram of a storage device provided by Embodiment 4 of the present invention.
具体实施方式Detailed ways
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合附图对本发明实施方式作进一步地详细描述。In order to make the purpose, technical solutions and advantages of the embodiments of the present invention more clear, the implementation manners of the present invention will be further described in detail below in conjunction with the accompanying drawings.
实施例1Example 1
参见图2，本实施例提供了一种保持业务连续的方法，包括：Referring to Figure 2, this embodiment provides a method for maintaining business continuity, including:
101：当第一移动性管理实体发生故障时，获取第一标识信息和第二标识信息，该第一标识信息是存储设备的标识信息，该存储设备用于存储该第一移动性管理实体当前会话的第一承载上下文信息，该第二标识信息是由该第一移动性管理实体服务的处于连接态的用户设备的标识信息；101: When the first mobility management entity fails, acquire first identification information and second identification information, where the first identification information is identification information of a storage device, and the storage device is used to store the current status of the first mobility management entity. The first bearer context information of the session, the second identification information is the identification information of the user equipment in the connected state served by the first mobility management entity;
102：从该第一标识信息对应的存储设备中，根据该第二标识信息获取该用户设备对应的当前会话的第一承载上下文信息；102: Acquire, from the storage device corresponding to the first identification information, the first bearer context information of the current session corresponding to the user equipment according to the second identification information;
103：根据该第一承载上下文信息，为该用户设备建立承载。103: Establish a bearer for the user equipment according to the first bearer context information.
本实施例通过从存储设备获取发生故障的移动性管理实体当前会话的承载上下文信息，根据该承载上下文信息为用户设备建立承载，实现了在移动性管理实体故障的情况下，用户的数据业务不中断的效果，大大提高了用户体验。In this embodiment, by acquiring the bearer context information of the current session of the failed mobility management entity from the storage device, and establishing a bearer for the user equipment according to the bearer context information, it is realized that in the case of a failure of the mobility management entity, the user's data service does not The interrupt effect greatly improves the user experience.
本实施例提供的保持业务连续的方法可以应用于基于SAE架构的通信系统中，下面简要介绍一下SAE架构。The method for maintaining service continuity provided in this embodiment can be applied to a communication system based on the SAE architecture. The following briefly introduces the SAE architecture.
参见图3，SAE包括EPC(Evolved Packet Core，演进的分组核心网)和E-UTRAN；Referring to Figure 3, SAE includes EPC (Evolved Packet Core, evolved packet core network) and E-UTRAN;
其中，EPC是指除了接入侧E-UTRAN之外的核心网网元，包括：MME、S-GW、P-GW(Packet Data Network Gateway，分组数据网络网关)、PCRF(Policy and Charging RuleFunction，策略和计费控制功能)和HSS等功能实体。Among them, EPC refers to the core network elements other than the access side E-UTRAN, including: MME, S-GW, P-GW (Packet Data Network Gateway, packet data network gateway), PCRF (Policy and Charging RuleFunction, Policies and charging control functions) and functional entities such as HSS.
MME负责控制面的移动性管理，包括用户上下文和移动状态管理，分配用户临时身份标识等；MME is responsible for the mobility management of the control plane, including user context and mobility state management, assigning user temporary identities, etc.;
S-GW是3GPP(3rd Generation Partnership Project，第三代合作伙伴计划)接入网络间的用户面锚点，终止E-TURAN的接口，是转发面的功能实体；S-GW is the user plane anchor point between 3GPP (3rd Generation Partnership Project, 3rd Generation Partnership Project) access networks, terminates the interface of E-TURAN, and is the functional entity of the forwarding plane;
P-GW是3GPP接入网络和非3GPP接入网络之间的用户面锚点，终止和外部PDN(PacketData Network，分组数据网络)的接口；P-GW is the user plane anchor point between the 3GPP access network and the non-3GPP access network, and terminates the interface with the external PDN (PacketData Network, packet data network);
PCRF用于策略控制和流计费控制功能；PCRF is used for policy control and flow charging control functions;
HSS用于存储用户签约信息。The HSS is used to store user subscription information.
E-UTRAN由eNodeB(Enhanced NodeB，加强基站)构成，eNodeB可连接多个MME，多个功能一致的MME构成MME POOL。E-UTRAN is composed of eNodeB (Enhanced NodeB, enhanced base station). The eNodeB can connect to multiple MMEs, and multiple MMEs with the same functions form the MME POOL.
以上介绍了SAE架构，下面结合附图4，详细阐述在SAE架构下，保持业务连续的具体过程。The SAE architecture has been introduced above, and the specific process of maintaining business continuity under the SAE architecture will be described in detail below with reference to Figure 4.
首先，MME POOL中的MME将当前会话的承载上下文信息备份到存储设备，以便于保持业务连续，在SAE架构下，该存储设备为S-GW(服务网关)，或其他存储设备，具体步骤如下：First, the MME in the MME POOL backs up the bearer context information of the current session to a storage device in order to maintain business continuity. Under the SAE architecture, the storage device is S-GW (serving gateway) or other storage devices. The specific steps are as follows :
201：MME每次向S-GW发起建立(或更新)承载请求，在该请求中携带当前会话的承载上下文信息；201: The MME initiates a bearer establishment (or update) request to the S-GW each time, and the bearer context information of the current session is carried in the request;
上述承载上下文信息为：除安全上下文和S-GW已有的部分会话信息(如IMSI(International Mobile Subscriber Identification Number，国际移动用户识别码)等公有信息)外的所有当前会话的承载上下文信息；并且该承载上下文信息是由MME服务的处于连接态的一个或多个用户设备对应的当前会话的承载上下文信息。The above bearer context information is: bearer context information of all current sessions except the security context and some session information existing in the S-GW (such as public information such as IMSI (International Mobile Subscriber Identification Number, International Mobile Subscriber Identification Number)); and The bearer context information is the bearer context information of the current session corresponding to one or more user equipments in the connected state served by the MME.
202：S-GW接收到MME发送的建立(或更新)承载请求后，将该请求中携带的当前会话的承载上下文信息和与之关联的转发面用户会话信息都存储起来；同时，向P-GW(分组数据网络网关)发送建立(或更新)承载请求；202: After receiving the establishment (or update) bearer request sent by the MME, the S-GW stores the bearer context information of the current session carried in the request and the associated forwarding plane user session information; GW (packet data network gateway) sends a bearer establishment (or update) request;
进一步地，当MME向S-GW发送删除承载请求时，S-GW将存储的承载上下文信息删除；Further, when the MME sends a delete bearer request to the S-GW, the S-GW deletes the stored bearer context information;
203：P-GW接收S-GW发送的建立(或更新)承载请求，同时，向S-GW回建立(或更新)承载响应；203: The P-GW receives the establishment (or update) bearer request sent by the S-GW, and at the same time sends back a establishment (or update) bearer response to the S-GW;
204：S-GW接收P-GW发送的建立(或更新)承载响应，向MME回建立(或更新)承载响应；204: The S-GW receives the establishment (or update) bearer response sent by the P-GW, and returns the establishment (or update) bearer response to the MME;
通过上述步骤201-202，MME将当前会话的承载上下文信息备份到S-GW。Through the above steps 201-202, the MME backs up the bearer context information of the current session to the S-GW.
当上述已备份当前会话的承载上下文信息的MME发生故障时，eNodeB(加强基站)通过故障检测机制可以迅速检查到MME故障，从而启动保持业务连续流程，具体步骤如下：When the above-mentioned MME that has backed up the bearer context information of the current session fails, the eNodeB (enhanced base station) can quickly detect the MME failure through the failure detection mechanism, thereby starting the process of maintaining service continuity. The specific steps are as follows:
301：假设已备份当前会话的承载上下文信息的MME1发生故障，eNodeB检查到MME1故障，查找由MME1服务的所有ECM_CONNECTED(连接)态的UE，此时eNodeB与这些UE之间的无线承载并未释放，eNodeB发送MME1故障通知消息给这些UE；301: Assuming that MME1 that has backed up the bearer context information of the current session fails, the eNodeB detects that MME1 is faulty, and searches for all UEs in the ECM_CONNECTED (connected) state served by MME1. At this time, the radio bearer between the eNodeB and these UEs has not been released. , the eNodeB sends an MME1 failure notification message to these UEs;
为避免触发大量UE同时发送TAU(跟踪区域更新)消息，给网络带来的冲击，eNodeB可以分批发送通知消息给这些UE。In order to avoid the impact on the network caused by triggering a large number of UEs to send TAU (Tracking Area Update) messages at the same time, the eNodeB may send notification messages to these UEs in batches.
302：UE接收到eNodeB发送的MME1故障通知消息后，向eNodeB发送TAU(Trace AreaUpdate，跟踪区域更新)请求；302: After receiving the MME1 failure notification message sent by the eNodeB, the UE sends a TAU (Trace Area Update, tracking area update) request to the eNodeB;
只有接收到故障通知消息的UE，才会向eNodeB发送TAU请求。然后，eNodeB根据MME POOL内的负荷分担情况重新选择一个MME为UE服务，设选中MME2为UE继续服务。Only the UE that has received the fault notification message will send a TAU request to the eNodeB. Then, the eNodeB re-selects an MME to serve the UE according to the load sharing situation in the MME POOL, and it is assumed that the selected MME2 continues to serve the UE.
303：eNodeB向MME2发送TAU请求，该请求携带S-GW标识(S-GW ID)；303: eNodeB sends a TAU request to MME2, and the request carries an S-GW identifier (S-GW ID);
304：MME2接收到eNodeB发送的TAU请求后，由于根据UE的GUTI无法从已故障的MME1上获取当前会话的承载上下文信息，因此MME2通过eNodeB向UE发送IdentityRequest(标识请求)，以获取UE的标识信息(IMSI)；304: After MME2 receives the TAU request sent by the eNodeB, since the bearer context information of the current session cannot be obtained from the failed MME1 according to the GUTI of the UE, MME2 sends an IdentityRequest (identification request) to the UE through the eNodeB to obtain the identity of the UE information (IMSI);
305：UE接收到上述Identity Request后，通过eNodeB向MME2回Identity Response(标识响应)，该响应携带UE的标识信息(IMSI)；305: After receiving the above-mentioned Identity Request, the UE sends an Identity Response (identity response) to MME2 through the eNodeB, and the response carries the identity information (IMSI) of the UE;
UE和MME2之间重新触发AKA(Authentication and Key Agreement，授权和密钥协商)过程，建立安全上下文，因此步骤201中MME不需要发送安全上下文，相应地，S-GW也不需要备份安全上下文。The AKA (Authentication and Key Agreement, authorization and key agreement) process is re-triggered between UE and MME2 to establish a security context. Therefore, in step 201, the MME does not need to send the security context, and accordingly, the S-GW does not need to back up the security context.
306：MME2接收到上述Identity Response后，向S-GW标识(S-GW ID)所对应的S-GW发送恢复上下文请求，该请求携带UE的标识信息(IMSI)；306: After receiving the above-mentioned Identity Response, MME2 sends a recovery context request to the S-GW corresponding to the S-GW identifier (S-GW ID), and the request carries the identification information (IMSI) of the UE;
307：S-GW接收到上述恢复上下文请求后，根据请求中UE的标识信息(IMSI)找到对应的MME1当前会话的承载上下文信息；同时，向MME2返回恢复上下文响应，该响应携带上述MME1当前会话的承载上下文信息；307: After receiving the above context recovery request, the S-GW finds the corresponding bearer context information of the current session of MME1 according to the identification information (IMSI) of the UE in the request; at the same time, returns a context recovery response to MME2, which carries the current session of MME1 bearer context information;
308：MME2根据从S-GW获取的MME1当前会话的承载上下文信息，重建MME2的承载上下文信息，具体包括：308: MME2 reconstructs the bearer context information of MME2 according to the bearer context information of the current session of MME1 obtained from the S-GW, specifically including:
A：将MME1当前会话的承载上下文信息中标识MME1的信息替换为标识MME2的信息，如：GUTI。MME2重新分配GUTI，该GUTI携带MME2标识信息(MME2 ID)，将MME1上下文中的GUTI更新为MME2重新分配的GUTI；A: Replace the information identifying MME1 in the bearer context information of the current session of MME1 with the information identifying MME2, such as GUTI. MME2 redistributes GUTI, which carries MME2 identification information (MME2 ID), and updates the GUTI in the MME1 context to the GUTI redistributed by MME2;
B：将除标识MME1的信息之外的其它MME1当前会话的承载上下文直接作为MME2的承载上下文；B: directly use the bearer context of the current session of MME1 other than the information identifying MME1 as the bearer context of MME2;
经过步骤301-308，就完成了MME2承载上下文信息的重建。After steps 301-308, the reconstruction of MME2 bearer context information is completed.
309：MME2向S-GW发送更新承载请求，该请求携带重建的MME2的承载上下文信息；309: MME2 sends an update bearer request to the S-GW, and the request carries the reconstructed bearer context information of MME2;
310：S-GW接收到上述更新承载请求后，根据该请求携带的MME2的承载上下文信息更新自身的转发面上下文；S-GW向P-GW发送承载更新请求，该请求携带MME2的承载上下文信息；310: After receiving the bearer update request above, the S-GW updates its own forwarding plane context according to the bearer context information of MME2 carried in the request; the S-GW sends a bearer update request to the P-GW, and the request carries the bearer context information of MME2 ;
311：P-GW接收到上述承载更新请求后，根据该请求携带的MME2的承载上下文信息更新自身的上下文；向S-GW返回承载更新响应；311: After receiving the bearer update request, the P-GW updates its own context according to the bearer context information of MME2 carried in the request; returns a bearer update response to the S-GW;
312：S-GW接收到上述承载更新响应后，向MME2返回承载更新响应；312: After receiving the bearer update response, the S-GW returns a bearer update response to MME2;
313：MME2向HSS发送Update Location(更新位置)消息，该消息携带UE的标识信息：IMSI、MME2的标识信息(MME2 ID)等；313: MME2 sends an Update Location (update location) message to the HSS, and the message carries UE identification information: IMSI, MME2 identification information (MME2 ID), etc.;
314：HSS接收上述Update Location消息，并向MME2发送Insert Subscriber Data(插入用户数据)消息，该消息携带UE的标识信息，签约数据；314: The HSS receives the above-mentioned Update Location message, and sends an Insert Subscriber Data (insert subscriber data) message to MME2, which carries the UE's identification information and subscription data;
315：MME2接收上述消息，为UE构造MM(Mobility Management，移动性管理)上下文，并向HSS回Insert Subcriber Data Ack(插入用户数据响应)消息，该消息携带UE标识信息(IMSI)；315: MME2 receives the above message, constructs MM (Mobility Management, mobility management) context for UE, and returns Insert Subscriber Data Ack (insert user data response) message to HSS, and the message carries UE identification information (IMSI);
316：HSS发送Update Location Ack(更新位置响应)消息给MME2；316: HSS sends an Update Location Ack (update location response) message to MME2;
通过步骤313-316，MME2完成了根据签约数据重建MM上下文的过程。此为现有技术，不再赘述。Through steps 313-316, MME2 completes the process of rebuilding the MM context according to the subscription data. This is the prior art and will not be repeated here.
317：MME2接收上述Update Location Ack消息，并向UE发送TAU Accpet(TAU接受)消息，完成TAU过程。317: MME2 receives the above Update Location Ack message, and sends a TAU Accpet (TAU acceptance) message to the UE to complete the TAU process.
此时，MME2完成了重新构建承载上下文和MM上下文等控制面上下文的过程，实现了在用户业务不中断的情况下，从故障MME1切换到MME2的过程，保持了业务连续。At this point, MME2 completes the process of rebuilding control plane contexts such as bearer context and MM context, realizing the process of switching from faulty MME1 to MME2 without interrupting user services, and maintaining service continuity.
本实施例通过从存储设备获取发生故障的移动性管理实体当前会话的承载上下文信息，根据该承载上下文信息为用户设备建立承载，实现了在移动性管理实体故障的情况下，用户的数据业务不中断的效果，大大提高了用户体验。In this embodiment, by acquiring the bearer context information of the current session of the failed mobility management entity from the storage device, and establishing a bearer for the user equipment according to the bearer context information, it is realized that in the case of a failure of the mobility management entity, the user's data service does not The interrupt effect greatly improves the user experience.
实施例2Example 2
参见图5，本实施例提供了一种保持业务连续的系统，该系统包括：存储设备41和移动性管理实体42；Referring to FIG. 5, this embodiment provides a system for maintaining service continuity, which includes: a
该存储设备41，用于备份第一移动性管理实体当前会话的第一承载上下文信息，接收该移动性管理实体42发送的恢复上下文请求，该恢复上下文请求携带由该第一移动性管理实体服务的用户设备的标识信息，并向该移动性管理实体42发送该标识信息对应的该第一承载上下文信息；上述第一承载上下文信息是由MME服务的处于连接态的一个或多个用户设备对应的当前会话的承载上下文信息。The
备份第一承载上下文信息的具体过程为：The specific process of backing up the first bearer context information is as follows:
存储设备41接收第一移动性管理实体发送的建立(或更新)承载请求；将该请求中携带的第一移动性管理实体当前会话的第一承载上下文信息和与之关联的转发面用户会话信息都存储起来，实现备份功能。The
该存储设备41可以是服务网关或其它存储设备。The
该移动性管理实体42，用于当第一移动性管理实体发生故障时，获取第一标识信息和第二标识信息，该第一标识信息是存储设备41的标识信息，该第二标识信息是由该第一移动性管理实体服务的处于连接态的用户设备的标识信息；从该第一标识信息对应的存储设备41中，根据该第二标识信息获取该用户设备对应的当前会话的第一承载上下文信息；根据该第一承载上下文信息，为该用户设备建立承载。The mobility management entity 42 is configured to obtain first identification information and second identification information when the first mobility management entity fails, the first identification information is identification information of the
参见图6，该系统还包括：加强基站43；Referring to Fig. 6, the system also includes: a reinforced base station 43;
该加强基站43，用于向由该第一移动性管理实体服务的处于连接态的用户设备发送故障通知消息；接收到该用户设备发送的第二跟踪区域更新请求后，选择第二移动性管理实体为该用户设备建立承载。该第二移动性管理实体用于当第一移动性管理实体发生故障时，获取第一标识信息和第二标识信息，该第一标识信息是存储设备的标识信息，该存储设备用于存储该第一移动性管理实体当前会话的第一承载上下文信息，该第二标识信息是由该第一移动性管理实体服务的处于连接态的用户设备的标识信息；从该第一标识信息对应的存储设备中，根据该第二标识信息获取该用户设备对应的当前会话的第一承载上下文信息；根据该第一承载上下文信息，为该用户设备建立承载。The enhanced base station 43 is configured to send a failure notification message to the user equipment in the connected state served by the first mobility management entity; after receiving the second tracking area update request sent by the user equipment, select the second mobility management The entity establishes a bearer for the user equipment. The second mobility management entity is used to obtain first identification information and second identification information when the first mobility management entity fails, the first identification information is identification information of a storage device, and the storage device is used to store the The first bearer context information of the current session of the first mobility management entity, the second identification information is the identification information of the user equipment in the connected state served by the first mobility management entity; from the storage corresponding to the first identification information In the device, first bearer context information of the current session corresponding to the user equipment is obtained according to the second identification information; and a bearer is established for the user equipment according to the first bearer context information.
本实施例提供的系统通过从存储设备获取发生故障的移动性管理实体当前会话的承载上下文信息，根据该承载上下文信息为用户设备建立承载，实现了在移动性管理实体故障的情况下，用户的数据业务不中断的效果，大大提高了用户体验。The system provided in this embodiment obtains the bearer context information of the current session of the failed mobility management entity from the storage device, and establishes a bearer for the user equipment according to the bearer context information, so that when the mobility management entity fails, the user's The effect of uninterrupted data services greatly improves user experience.
实施例3Example 3
参见图7，本实施例提供了一种移动性管理实体42，包括：标识信息获取模块421、上下文获取模块422和业务连续保持模块423；其中，Referring to FIG. 7 , this embodiment provides a mobility management entity 42, including: an identification information acquisition module 421, a context acquisition module 422, and a service continuity maintenance module 423; wherein,
标识信息获取模块421，用于当第一移动性管理实体发生故障时，获取第一标识信息和第二标识信息，该第一标识信息是存储设备的标识信息，该存储设备用于存储该第一移动性管理实体当前会话的第一承载上下文信息，该第二标识信息是由该第一移动性管理实体服务的处于连接态的用户设备的标识信息；The identification information acquiring module 421 is configured to acquire first identification information and second identification information when the first mobility management entity fails, the first identification information is identification information of a storage device, and the storage device is used to store the first identification information First bearer context information of a current session of a mobility management entity, where the second identification information is identification information of a user equipment in a connected state served by the first mobility management entity;
上下文获取模块422，用于从该第一标识信息对应的存储设备中，根据该第二标识信息获取该用户设备对应的当前会话的第一承载上下文信息；A context obtaining module 422, configured to obtain, from the storage device corresponding to the first identification information, the first bearer context information of the current session corresponding to the user equipment according to the second identification information;
业务连续保持模块423，用于根据该第一承载上下文信息，为该用户设备建立承载。The service continuity maintaining module 423 is configured to establish a bearer for the user equipment according to the first bearer context information.
参见图8，移动性管理实体42还包括：Referring to Fig. 8, the mobility management entity 42 also includes:
上下文发送模块424，用于向该存储设备41发送当前会话的第三承载上下文信息，该存储设备41将接收到的该第三承载上下文信息备份。这样，当移动性管理实体42发生故障的时候，存储设备41可以在资源池中为其选择另一个移动性管理实体，继续为由移动性管理实体42服务的用户设备服务。The context sending module 424 is configured to send the third bearer context information of the current session to the
参见图9，标识信息获取模块421，具体包括：Referring to FIG. 9, the identification information acquisition module 421 specifically includes:
第一标识信息获取单元421a，用于接收加强基站发送的第一跟踪区域更新请求，该第一跟踪区域更新请求携带该第一标识信息；The first identification information acquiring unit 421a is configured to receive a first tracking area update request sent by the enhanced base station, where the first tracking area update request carries the first identification information;
第二标识信息获取单元421b，用于向该用户设备发送获取第二标识信息的请求，接收该用户设备返回的获取第二标识信息的响应，该响应携带该第二标识信息。The second identification information obtaining unit 421b is configured to send a request for obtaining second identification information to the user equipment, and receive a response for obtaining second identification information returned by the user equipment, where the response carries the second identification information.
该用户设备的第二标识信息可以为IMSI(International Mobile Subscriber IdentificationNumber，国际移动用户识别码)。The second identification information of the user equipment may be IMSI (International Mobile Subscriber Identification Number, International Mobile Subscriber Identification Number).
参见图10，上下文获取模块422，具体包括：Referring to FIG. 10, the context acquisition module 422 specifically includes:
请求发送单元422a，用于向第一标识信息对应的存储设备发送恢复上下文请求，该恢复上下文请求携带该第二标识信息；The request sending unit 422a is configured to send a restore context request to the storage device corresponding to the first identification information, where the restore context request carries the second identification information;
上下文接收单元422b，用于接收该存储设备发送的该第二标识信息对应的当前会话的第一承载上下文信息。The context receiving unit 422b is configured to receive the first bearer context information of the current session corresponding to the second identification information sent by the storage device.
参见图11，业务连续保持模块423，具体包括：Referring to Figure 11, the business continuity maintenance module 423 specifically includes:
上下文构建单元423a，用于根据该第一承载上下文信息，构建第二承载上下文信息；A context construction unit 423a, configured to construct second bearer context information according to the first bearer context information;
业务联系保持单元423b，用于根据该上下文构建单元423a构建的第二承载上下文信息，为该用户设备建立承载。The service connection maintaining unit 423b is configured to establish a bearer for the user equipment according to the second bearer context information constructed by the context constructing unit 423a.
参见图12，上下文构建单元423a，具体包括：Referring to FIG. 12, the context construction unit 423a specifically includes:
标识信息构建子单元423a1，用于将第一承载上下文信息中标识该第一移动性管理实体的信息更新为标识第二移动性管理实体的信息，该第二移动性管理实体用于当第一移动性管理实体发生故障时，获取第一标识信息和第二标识信息，该第一标识信息是存储设备的标识信息，该存储设备用于存储该第一移动性管理实体当前会话的第一承载上下文信息，该第二标识信息是由该第一移动性管理实体服务的处于连接态的用户设备的标识信息；从该第一标识信息对应的存储设备中，根据该第二标识信息获取该用户设备对应的当前会话的第一承载上下文信息；根据该第一承载上下文信息，为该用户设备建立承载；The identification information construction subunit 423a1 is configured to update the information identifying the first mobility management entity in the first bearer context information to information identifying a second mobility management entity, and the second mobility management entity is used when the first When a mobility management entity fails, acquire first identification information and second identification information, where the first identification information is identification information of a storage device, and the storage device is used to store the first bearer of the current session of the first mobility management entity context information, the second identification information is the identification information of the user equipment in the connected state served by the first mobility management entity; from the storage device corresponding to the first identification information, the user equipment is obtained according to the second identification information The first bearer context information of the current session corresponding to the device; according to the first bearer context information, establish a bearer for the user equipment;
承载信息构建子单元423a2，用于将除标识该第一移动性管理实体的信息之外的其它第一承载上下文信息作为第二承载上下文信息。The bearer information constructing subunit 423a2 is configured to use other first bearer context information except the information identifying the first mobility management entity as second bearer context information.
本实施例提供的移动性管理实体通过从存储设备获取发生故障的移动性管理实体当前会话的承载上下文信息，根据该承载上下文信息为用户设备建立承载，实现了在移动性管理实体故障的情况下，用户的数据业务不中断的效果，大大提高了用户体验。The mobility management entity provided in this embodiment obtains the bearer context information of the current session of the failed mobility management entity from the storage device, and establishes a bearer for the user equipment according to the bearer context information, so that in the case of a failure of the mobility management entity, , The user's data service is not interrupted, which greatly improves the user experience.
实施例4Example 4
参见图13，本实施例提供了一种存储设备41，包括：Referring to FIG. 13, this embodiment provides a
上下文备份模块411，用于备份第一移动性管理实体当前会话的第一承载上下文信息；A
上下文发送模块412，用于接收第二移动性管理实体发送的恢复上下文请求，该恢复上下文请求携带由该第一移动性管理实体服务的用户设备的标识信息，并向该第二移动性管理实体发送该标识信息对应的该第一承载上下文信息，使得该第二移动性管理实体能够根据该第一承载上下文信息，为该用户设备建立承载。The context sending module 412 is configured to receive a restore context request sent by the second mobility management entity, where the restore context request carries identification information of the user equipment served by the first mobility management entity, and sends the request to the second mobility management entity Sending the first bearer context information corresponding to the identification information, so that the second mobility management entity can establish a bearer for the user equipment according to the first bearer context information.
该存储设备41可以是服务网关或其它存储设备。The
本实施例提供的存储设备能够备份并发送移动性管理实体当前会话的承载上下文信息，使其它移动性管理实体能够根据该承载上下文信息为用户设备建立承载，实现了在移动性管理实体故障的情况下，用户的数据业务不中断的效果，大大提高了用户体验。The storage device provided in this embodiment can back up and send the bearer context information of the current session of the mobility management entity, so that other mobility management entities can establish a bearer for the user equipment according to the bearer context information, and realize the Under this circumstance, the user's data service is not interrupted, which greatly improves the user experience.
以上实施例提供的技术方案中的全部或部分内容可以通过软件编程实现，其软件程序存储在可读取的存储介质中，存储介质例如：计算机中的硬盘、设备单板的硬盘和内存。All or part of the technical solutions provided by the above embodiments can be realized through software programming, and the software program is stored in a readable storage medium, such as a hard disk in a computer, a hard disk on a device board, and memory.
以上所述仅为本发明的较佳实施例，并不用以限制本发明，凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included in the protection of the present invention. within range.
Claims (18)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101178504ACN101646270B (en) | 2008-08-06 | 2008-08-06 | Method, system, mobility management entity and memory device for maintaining service continuity |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101178504ACN101646270B (en) | 2008-08-06 | 2008-08-06 | Method, system, mobility management entity and memory device for maintaining service continuity |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101646270Atrue CN101646270A (en) | 2010-02-10 |
| CN101646270B CN101646270B (en) | 2011-12-07 |
Family
ID=41657929
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008101178504AExpired - Fee RelatedCN101646270B (en) | 2008-08-06 | 2008-08-06 | Method, system, mobility management entity and memory device for maintaining service continuity |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101646270B (en) |
Cited By (24)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011110013A1 (en)* | 2010-09-03 | 2011-09-15 | 华为技术有限公司 | Method, network device and network system for processing failure of mobility management network element |
| WO2011110109A3 (en)* | 2011-03-21 | 2012-02-16 | 华为技术有限公司 | Connection establishing method, fault processing method, communication system and device thereof |
| CN102436405A (en)* | 2011-09-05 | 2012-05-02 | 北京星网锐捷网络技术有限公司 | Method and device for saving and tampering detection of process context |
| CN102480464A (en)* | 2010-11-24 | 2012-05-30 | 上海宝信软件股份有限公司 | Service calling system and method for injecting context information decoupled from web session |
| WO2012097524A1 (en)* | 2011-01-21 | 2012-07-26 | 华为技术有限公司 | Method, device and system for processing reset of mobility management network element |
| CN102714615A (en)* | 2010-11-29 | 2012-10-03 | 华为技术有限公司 | Node fault handling method, system and related equipment |
| WO2013104114A1 (en)* | 2012-01-10 | 2013-07-18 | 华为技术有限公司 | Method, node, and system for handling partial failure of mobility management entity |
| CN103238345A (en)* | 2012-10-31 | 2013-08-07 | 华为技术有限公司 | Communication method, device and system all based on mobile management entity pool (MME Pool) |
| WO2014000550A1 (en)* | 2012-06-25 | 2014-01-03 | 中兴通讯股份有限公司 | Microwave transmission device, and, method and device therefor for data processing |
| CN103517302A (en)* | 2012-06-25 | 2014-01-15 | 中兴通讯股份有限公司 | Microwave transmission apparatus, and method and device for restarting the same |
| CN103841545A (en)* | 2012-11-27 | 2014-06-04 | 华为技术有限公司 | Capability information reporting method and device in MME pool scene |
| WO2014190553A1 (en)* | 2013-05-31 | 2014-12-04 | 华为技术有限公司 | User equipment management method, device and system |
| CN104284359A (en)* | 2014-06-17 | 2015-01-14 | 南京邮电大学 | A cross-regional disaster recovery system and control method under EPC network |
| CN105323792A (en)* | 2014-07-31 | 2016-02-10 | 中国电信股份有限公司 | Mobility management entity, and disaster tolerant method and disaster tolerant system thereof |
| CN105376768A (en)* | 2014-08-19 | 2016-03-02 | 中国电信股份有限公司 | Pool disaster recovery method and system for mobility management entity |
| WO2017020176A1 (en)* | 2015-07-31 | 2017-02-09 | 华为技术有限公司 | Data transmission method, and related device and system |
| CN107331079A (en)* | 2017-06-06 | 2017-11-07 | 浪潮金融信息技术有限公司 | Method for processing business and device |
| WO2018035722A1 (en)* | 2016-08-23 | 2018-03-01 | 华为技术有限公司 | Session management method and device |
| CN108200571A (en)* | 2016-12-08 | 2018-06-22 | 中国移动通信集团四川有限公司 | A kind of tracing section updating method, apparatus and mobile management entity |
| CN108668307A (en)* | 2017-03-29 | 2018-10-16 | 中国移动通信集团上海有限公司 | Called service recovery processing method, mobility management entity and serving gateway |
| CN109547997A (en)* | 2017-08-04 | 2019-03-29 | 中国移动通信有限公司研究院 | Data sharing method, server, computer readable storage medium and system |
| WO2020052463A1 (en)* | 2018-09-14 | 2020-03-19 | 华为技术有限公司 | Communication method and network element |
| JP2022159415A (en)* | 2021-01-08 | 2022-10-17 | 日本電気株式会社 | Gateway device and control method |
| US12200819B2 (en) | 2016-11-02 | 2025-01-14 | Nec Corporation | Gateway device, mobility management device, base station, communication method, control method, paging method, and computer-readable medium preliminary class |
- 2008
- 2008-08-06CNCN2008101178504Apatent/CN101646270B/ennot_activeExpired - Fee Related
Cited By (45)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102318384A (en)* | 2010-09-03 | 2012-01-11 | 华为技术有限公司 | Handling method for mobility management network element failure, network equipment and network system |
| WO2011110013A1 (en)* | 2010-09-03 | 2011-09-15 | 华为技术有限公司 | Method, network device and network system for processing failure of mobility management network element |
| CN102480464B (en)* | 2010-11-24 | 2016-08-17 | 上海宝信软件股份有限公司 | With service calling system and the method that contextual information is injected in web session decoupling |
| CN102480464A (en)* | 2010-11-24 | 2012-05-30 | 上海宝信软件股份有限公司 | Service calling system and method for injecting context information decoupled from web session |
| CN102714615B (en)* | 2010-11-29 | 2015-05-27 | 华为技术有限公司 | Node fault processing method, system and related device |
| CN102714615A (en)* | 2010-11-29 | 2012-10-03 | 华为技术有限公司 | Node fault handling method, system and related equipment |
| WO2012097524A1 (en)* | 2011-01-21 | 2012-07-26 | 华为技术有限公司 | Method, device and system for processing reset of mobility management network element |
| CN102907126A (en)* | 2011-01-21 | 2013-01-30 | 华为技术有限公司 | Method, device and system for processing reset of mobility management network element |
| WO2011110109A3 (en)* | 2011-03-21 | 2012-02-16 | 华为技术有限公司 | Connection establishing method, fault processing method, communication system and device thereof |
| CN102804910A (en)* | 2011-03-21 | 2012-11-28 | 华为技术有限公司 | Connection establishment method, fault handling method, communication system and related equipment |
| CN102436405A (en)* | 2011-09-05 | 2012-05-02 | 北京星网锐捷网络技术有限公司 | Method and device for saving and tampering detection of process context |
| CN102436405B (en)* | 2011-09-05 | 2016-03-30 | 北京星网锐捷网络技术有限公司 | A kind of process context preservation, altering detecting method and device |
| WO2013104114A1 (en)* | 2012-01-10 | 2013-07-18 | 华为技术有限公司 | Method, node, and system for handling partial failure of mobility management entity |
| WO2014000550A1 (en)* | 2012-06-25 | 2014-01-03 | 中兴通讯股份有限公司 | Microwave transmission device, and, method and device therefor for data processing |
| CN103517302A (en)* | 2012-06-25 | 2014-01-15 | 中兴通讯股份有限公司 | Microwave transmission apparatus, and method and device for restarting the same |
| WO2014067098A1 (en)* | 2012-10-31 | 2014-05-08 | 华为技术有限公司 | Communication method, device and system based on mobility management entity pool (mme pool) |
| CN103238345A (en)* | 2012-10-31 | 2013-08-07 | 华为技术有限公司 | Communication method, device and system all based on mobile management entity pool (MME Pool) |
| WO2014082572A1 (en)* | 2012-11-27 | 2014-06-05 | 华为技术有限公司 | Capability information reporting method and device in mme pool scenario |
| CN103841545B (en)* | 2012-11-27 | 2017-12-29 | 华为技术有限公司 | The method and device that a kind of MME ponds scene ability information reports |
| CN103841545A (en)* | 2012-11-27 | 2014-06-04 | 华为技术有限公司 | Capability information reporting method and device in MME pool scene |
| WO2014190553A1 (en)* | 2013-05-31 | 2014-12-04 | 华为技术有限公司 | User equipment management method, device and system |
| CN104284359A (en)* | 2014-06-17 | 2015-01-14 | 南京邮电大学 | A cross-regional disaster recovery system and control method under EPC network |
| CN104284359B (en)* | 2014-06-17 | 2018-10-02 | 南京邮电大学 | Trans-regional disaster tolerance system and control method under a kind of EPC networks |
| CN105323792A (en)* | 2014-07-31 | 2016-02-10 | 中国电信股份有限公司 | Mobility management entity, and disaster tolerant method and disaster tolerant system thereof |
| CN105323792B (en)* | 2014-07-31 | 2018-11-13 | 中国电信股份有限公司 | Mobility management entity and its disaster recovery method and disaster tolerance system |
| CN105376768A (en)* | 2014-08-19 | 2016-03-02 | 中国电信股份有限公司 | Pool disaster recovery method and system for mobility management entity |
| CN105376768B (en)* | 2014-08-19 | 2019-02-22 | 中国电信股份有限公司 | A kind of mobility management entity pond group disaster recovery method and system |
| US10499443B2 (en) | 2015-07-31 | 2019-12-03 | Huawei Technologies Co., Ltd. | Data transmission method, related device, and system |
| CN107006046A (en)* | 2015-07-31 | 2017-08-01 | 华为技术有限公司 | A data transmission method and related equipment and system |
| CN107006046B (en)* | 2015-07-31 | 2021-08-03 | 华为技术有限公司 | A data transmission method and related equipment and system |
| WO2017020176A1 (en)* | 2015-07-31 | 2017-02-09 | 华为技术有限公司 | Data transmission method, and related device and system |
| US10999881B2 (en) | 2016-08-23 | 2021-05-04 | Huawei Technologies Co., Ltd. | Session management method and device |
| WO2018035722A1 (en)* | 2016-08-23 | 2018-03-01 | 华为技术有限公司 | Session management method and device |
| US12200819B2 (en) | 2016-11-02 | 2025-01-14 | Nec Corporation | Gateway device, mobility management device, base station, communication method, control method, paging method, and computer-readable medium preliminary class |
| CN108200571B (en)* | 2016-12-08 | 2021-03-05 | 中国移动通信集团四川有限公司 | Tracking area updating method and device and mobile management entity |
| CN108200571A (en)* | 2016-12-08 | 2018-06-22 | 中国移动通信集团四川有限公司 | A kind of tracing section updating method, apparatus and mobile management entity |
| CN108668307A (en)* | 2017-03-29 | 2018-10-16 | 中国移动通信集团上海有限公司 | Called service recovery processing method, mobility management entity and serving gateway |
| CN108668307B (en)* | 2017-03-29 | 2021-04-27 | 中国移动通信集团上海有限公司 | Called service recovery processing method, mobility management entity and service gateway |
| CN107331079A (en)* | 2017-06-06 | 2017-11-07 | 浪潮金融信息技术有限公司 | Method for processing business and device |
| CN107331079B (en)* | 2017-06-06 | 2019-11-26 | 浪潮金融信息技术有限公司 | Method for processing business and device |
| CN109547997A (en)* | 2017-08-04 | 2019-03-29 | 中国移动通信有限公司研究院 | Data sharing method, server, computer readable storage medium and system |
| WO2020052463A1 (en)* | 2018-09-14 | 2020-03-19 | 华为技术有限公司 | Communication method and network element |
| CN110913437A (en)* | 2018-09-14 | 2020-03-24 | 华为技术有限公司 | Communication method and network element |
| JP2022159415A (en)* | 2021-01-08 | 2022-10-17 | 日本電気株式会社 | Gateway device and control method |
| JP7376166B2 (en) | 2021-01-08 | 2023-11-08 | 日本電気株式会社 | A first CN node, a method performed at the first CN node, and a method performed at a UE |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101646270B (en) | 2011-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101646270B (en) | Method, system, mobility management entity and memory device for maintaining service continuity | |
| US9420439B2 (en) | Method and apparatus for receiving or sending short message | |
| US10405206B2 (en) | Service redundancy method and related apparatus | |
| WO2015062098A1 (en) | Network selection method and core network device | |
| CN101547168B (en) | Device reset notification method and system, service and packet data gateway and mobile management network element | |
| CN114915614B (en) | Method and device for recovering IMS service | |
| US8837355B2 (en) | Bearer processing method and mobile management device | |
| WO2011116722A2 (en) | Method and device for processing failures of mobility management device in idle mode signaling reduction activated scene | |
| JP2011211710A (en) | Efficient deployment for mobility management entity (mme) with stateful (maintenance of communicating condition) geographical redundancy | |
| CN105072706A (en) | Business processing method and system based on dual-card terminal | |
| WO2018059401A1 (en) | Network switching method, device and system, and network access method and device | |
| CN104244189A (en) | Paging method in TD-LTE cluster fail-soft communication system | |
| CA3080412C (en) | Service activation and deactivation method, device and computer storage medium | |
| CN107295515A (en) | A kind of method and device for supporting that user equipment (UE) context recovers between base station | |
| CN101867986B (en) | CSFB function activating method and system thereof | |
| CN102083112A (en) | Method, network equipment and user equipment for guaranteeing service connection | |
| CN102355743A (en) | Management method and management device for UE (User Equipment) context information | |
| WO2007112683A1 (en) | Method,apparatus and system for call recovery | |
| CN101626566B (en) | Method and equipment for realizing terminal transfer under ISR scene | |
| CN105453617B (en) | Method and apparatus for obtaining authentication information | |
| CN101179815B (en) | Mobile switching center pool fault handling method, device and system | |
| CN101330720A (en) | A processing method for accessing users, a user accessing system and equipment | |
| CN108616913A (en) | A kind of call processing method, apparatus and system | |
| EP3823323A1 (en) | Data transmission method and related apparatus | |
| CN107567091B (en) | Location area updating method and mobile station |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | Granted publication date:20111207 | |
| CF01 | Termination of patent right due to non-payment of annual fee |