CN101646270B - 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 continuity Download PDFInfo
- Publication number
- CN101646270B CN101646270B CN2008101178504A CN200810117850A CN101646270B CN 101646270 B CN101646270 B CN 101646270B CN 2008101178504 A CN2008101178504 A CN 2008101178504A CN 200810117850 A CN200810117850 A CN 200810117850A CN 101646270 B CN101646270 B CN 101646270B
- Authority
- CN
- China
- Prior art keywords
- identification information
- mobility management
- management entity
- information
- memory device
- 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.)
- Active
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method, a system, a mobility management entity and a memory device for maintaining service continuity, and belongs to the field of wireless communication. The method comprises the following steps of: acquiring first and second identification information when a first mobility management entity has a failure; acquiring first context carrying information of a present session corresponding to user equipment from the memory device corresponding to the first identification information according to the second identification information; and establishing load bearing for the user equipment according to the first context carrying information. The system comprises the memory device and the mobility management entity. The mobility management entity comprises an identification information acquisition module, a context acquisition module and a service continuity maintaining module. The memory device comprises a context backup module and a context transmission module. The method, the system, the mobility management entity and the memory device realize the uninterrupted effect of data service of a user when the mobility management entity has the failure, and greatly improve user experience.
Description
Technical field
The present invention relates to wireless communication field, particularly a kind of business continuous method, system, Mobility Management Entity and memory device of keeping.
Background technology
In order to adapt to development of Communication Technique, 3GPP (3rd Generation Partnership Project, third generation partner program) has organized to set up wireless network evolution plan.The version of current wireless network evolution is the R8 version, i.e. SAE (System Architecture Evolution, System Architecture Evolution).
In order to keep professional continuity, SAE has proposed the scheme of MME POOL (Mobility Management Entity POOL, Mobility Management Entity resource pool).MME POOL is made of the MME of a plurality of function unanimities, and UE (User Equipment, subscriber equipment) does not need the MME of the service of changing in the coverage of MME POOL.MME POOL possesses the characteristic that keeps business continuous, and promptly a MME equipment for user's service breaks down in resource pool, can switch to another MME equipment, continues as this user's service.
Referring to Fig. 1, three control appliances of MME1, MME2 and MME3 are arranged among the MME POOL, E-UTRAN (Evolved UMTS (Universal Mobile Telecommunications System, universal mobile telecommunications system) Territorial Radio Access Network, the UMTS Terrestrial radio access network of evolution), S-GW (Serving Gateway, gateway) and HSS (Home SubscriberServer, home subscriber server) all is connected with all MME in the POOL, wherein, E-UTRAN is responsible for user conversation is distributed to MME.For example, the UE1 that is registered under the MME1 initiates service request, the sign that in service request, can carry MME1, and E-UTRAN identifies according to this, can be routed to MME1 to service request.When the MME1 fault, E-UTRAN is obstructed to the route of MME1, and E-UTRAN can be routed to MME2 or MME3 to service request.Because MME2 and MME3 do not have the user data of UE1, return a failure response to E-UTRAN, eNodeB discharges the radio bearer with UE1, and user service data interrupts.UE1 initiates attachment flow again, is attached to MME2 or MME3 and just can restarts business.
In realizing process of the present invention, the inventor finds that there is following problem at least in prior art:
A certain MME breaks down among the MME POOL, this MME can lose the contextual information with all users of self session, though other MME among the POOL can continue as these user's services, but, these MME do not have user's contextual information, and user's data service is interrupted, and the user must initiate attachment flow again, be attached on other MME, just can restart session.Since during the user's data service disconnection, can make the non-constant of user experience.
Summary of the invention
In order to realize that when the Mobility Management Entity in the resource pool broke down, the data service of subscriber equipment was not interrupted, the embodiment of the invention provides a kind of keep professional continuous method, system, Mobility Management Entity and memory device.Described technical scheme is as follows:
A kind of continuous method of business that keeps, described method comprises:
When first Mobility Management Entity breaks down, obtain first identification information and second identification information, described first identification information is the identification information of memory device, described memory device is used to store the first bearer context information of the described first Mobility Management Entity current sessions, and described second identification information is the identification information by the subscriber equipment that is in connected state of the described first Mobility Management Entity service;
From the memory device of the described first identification information correspondence, obtain the first bearer context information of the current sessions of described subscriber equipment correspondence according to described second identification information;
According to the described first bearer context information, for described subscriber equipment is set up carrying.
A kind of continuous system of business that keeps, described system comprises: memory device and Mobility Management Entity;
Described memory device comprises:
The context backup module is used to back up the first bearer context information of the first Mobility Management Entity current sessions;
The context sending module, be used to receive the recovery context request that described Mobility Management Entity sends, described recovery context request is carried the identification information by the subscriber equipment of described first Mobility Management Entity service, and send the described first bearer context information of described identification information correspondence to described Mobility Management Entity, make described Mobility Management Entity according to the described first bearer context information, for described subscriber equipment is set up carrying;
Described Mobility Management Entity comprises:
The identification information acquisition module, be used for when first Mobility Management Entity breaks down, obtain first identification information and second identification information, described first identification information is the identification information of memory device, and described second identification information is the identification information by the subscriber equipment that is in connected state of the described first Mobility Management Entity service;
The context acquisition module is used for from the memory device of the described first identification information correspondence, obtains the first bearer context information of the current sessions of described subscriber equipment correspondence according to described second identification information;
The professional module that keeps continuously is used for according to the described first bearer context information, for described subscriber equipment is set up carrying.
A kind of Mobility Management Entity, described Mobility Management Entity comprises:
The identification information acquisition module, be used for when first Mobility Management Entity breaks down, obtain first identification information and second identification information, described first identification information is the identification information of memory device, described memory device is used to store the first bearer context information of the described first Mobility Management Entity current sessions, and described second identification information is the identification information by the subscriber equipment that is in connected state of the described first Mobility Management Entity service;
The context acquisition module is used for from the memory device of the described first identification information correspondence, obtains the first bearer context information of the current sessions of described subscriber equipment correspondence according to described second identification information;
The professional module that keeps continuously is used for according to the described first bearer context information, for described subscriber equipment is set up carrying.
A kind of memory device, described memory device comprises:
The context backup module is used to back up the first bearer context information of the first Mobility Management Entity current sessions;
The context sending module, be used to receive the recovery context request that second Mobility Management Entity sends, described recovery context request is carried the identification information by the subscriber equipment of described first Mobility Management Entity service, and send the described first bearer context information of described identification information correspondence to described second Mobility Management Entity, make that described second Mobility Management Entity can be according to the described first bearer context information, for described subscriber equipment is set up carrying.
The embodiment of the invention is by obtaining the bearer context information of the Mobility Management Entity current sessions that breaks down from memory device, according to this bearer context information is that subscriber equipment is set up carrying, realized under the situation of Mobility Management Entity fault, the professional unbroken effect of user's data has improved user experience greatly.
Description of drawings
Fig. 1 is the MME POOL structural representation that prior art provides;
Fig. 2 is the professional continuous method flow diagram of maintenance that the embodiment of the invention 1 provides;
Fig. 3 is the SAE network architecture diagram that prior art provides;
Fig. 4 is the professional continuous signaling process figure of maintenance that the embodiment of the invention 1 provides;
Fig. 5 is the professional continuous system configuration schematic diagram of maintenance that the embodiment of the invention 2 provides;
Fig. 6 is the professional continuous system configuration schematic diagram of maintenance that the embodiment of the invention 2 provides;
Fig. 7 is the Mobility Management Entity structural representation that the embodiment of the invention 3 provides;
Fig. 8 is another structural representation of Mobility Management Entity that the embodiment of the invention 3 provides;
Fig. 9 is the identification information acquisition module structural representation that the embodiment of the invention 3 provides;
Figure 10 is the context acquisition module structural representation that the embodiment of the invention 3 provides;
Figure 11 is that the business relations that the embodiment of the invention 3 provides keeps the modular structure schematic diagram;
Figure 12 is the context construction unit structural representation that the embodiment of the invention 3 provides;
Figure 13 is the memory device structural representation that the embodiment of the invention 4 provides.
Embodiment
For the purpose, technical scheme and the advantage that make the embodiment of the invention is clearer, embodiment of the present invention is described further in detail below in conjunction with accompanying drawing.
Embodiment 1
Referring to Fig. 2, present embodiment provides a kind of professional continuous method that keeps, and comprising:
101: when first Mobility Management Entity breaks down, obtain first identification information and second identification information, this first identification information is the identification information of memory device, this memory device is used to store the first bearer context information of this first Mobility Management Entity current sessions, and this second identification information is the identification information by the subscriber equipment that is in connected state of this first Mobility Management Entity service;
102: from the memory device of this first identification information correspondence, obtain the first bearer context information of the current sessions of this subscriber equipment correspondence according to this second identification information;
103: according to this first bearer context information, for this subscriber equipment is set up carrying.
Present embodiment is by obtaining the bearer context information of the Mobility Management Entity current sessions that breaks down from memory device, according to this bearer context information is that subscriber equipment is set up carrying, realized under the situation of Mobility Management Entity fault, the professional unbroken effect of user's data has improved user experience greatly.
The professional continuous method of maintenance that present embodiment provides can be applied to briefly introduce SAE framework below in the communication system based on the SAE framework.
Referring to Fig. 3, SAE comprises EPC (Evolved Packet Core, the packet-based core networks of evolution) and E-UTRAN;
Wherein, EPC is meant the core network element except inserting side E-UTRAN, comprise: MME, S-GW, P-GW (Packet DataNetwork Gateway, grouped data network gateway), functional entitys such as PCRF (Policy and Charging Rule Function, strategy and charging controlled function) and HSS.
MME is responsible for the mobile management of chain of command, comprises the management of user's context and mobile status, distributing user temporary identity sign etc.;
S-GW is the user's face anchor point between 3GPP (3rd Generation Partnership Project, third generation partner program) access network, stops the interface of E-TURAN, is the functional entity of forwarding face;
P-GW is the user's face anchor point between 3GPP access network and the non-3 GPP access network network, the interface of termination and outside PDN (Packet Data Network, packet data network);
PCRF is used for policy control and flow based charging controlled function;
HSS is used for storing user subscription information.
E-UTRAN is made of eNodeB (Enhanced NodeB strengthens the base station), and eNodeB can connect a plurality of MME, and the MME of a plurality of function unanimities constitutes MME POOL.
More than introduced the SAE framework,, elaborated under the SAE framework, kept professional continuous detailed process below in conjunction with accompanying drawing 4.
At first, to memory device, so that keep continuously professional, under the SAE framework, this memory device is S-GW (gateway) to the MME among the MME POOL, or other memory devices with the bearer context information back-up of current sessions, and concrete steps are as follows:
201:MME initiates to set up (or renewal) carrying request, the bearer context information of carrying current sessions in this request to S-GW at every turn;
Above-mentioned bearer context information is: the bearer context information of removing all outer current sessions of safe context and the existing partial session information of S-GW (as IMSI publicly-owned information such as (International Mobile Subscriber Identification Number, international mobile subscriber identitys)); And this bearer context information is the bearer context information by the current sessions of the one or more subscriber equipment correspondences that are in connected state of MME service.
After 202:S-GW receives foundation (or renewal) the carrying request that MME sends, the bearer context information of the current sessions that carries in this request is all stored with related with it forwarding face user session information; Simultaneously, send (or renewal) carrying request of setting up to P-GW (grouped data network gateway);
Further, when MME when S-GW sends the deleting bearing request, S-GW is with the bearer context information deletion of storage;
203:P-GW receives foundation (or renewal) the carrying request that S-GW sends, and simultaneously, returns foundation (or renewal) carrying response to S-GW;
204:S-GW receives foundation (or renewal) the carrying response that P-GW sends, and returns foundation (or renewal) carrying response to MME;
By above-mentioned steps 201-202, MME with the bearer context information back-up of current sessions to S-GW.
When the above-mentioned MME that has backed up the bearer context information of current sessions broke down, eNodeB (reinforcement base station) can be checked through the MME fault rapidly by fault detection mechanism, kept professional continuous process thereby start, and concrete steps are as follows:
301: the MME1 that supposes to back up the bearer context information of current sessions breaks down, eNodeB is checked through the MME1 fault, search UE by all ECM CONNECTED (connection) attitudes of MME1 service, radio bearer between eNodeB and these UE does not discharge at this moment, and eNodeB sends the MME1 fault notification message to these UE;
Send TAU (tracking area update) message simultaneously for avoiding triggering a large amount of UE, to the impact that network brings, eNodeB can send a notification message to these UE in batches.
After 302:UE receives the MME1 fault notification message of eNodeB transmission, send TAU (Trace Area Update, tracking area update) request to eNodeB;
Only receive the UE of fault notification message, just can send the TAU request to eNodeB.Then, it is the UE service that eNodeB reselects a MME according to the load sharing situation in the MME POOL, and establishing and choosing MME2 is that UE continues service.
303:eNodeB sends the TAU request to MME2, and S-GW sign (S-GW ID) is carried in this request;
After 304:MME2 receives the TAU request of eNodeB transmission, owing to can't obtain the bearer context information of current sessions according to the GUTI of UE from the MME1 of fault, therefore MME2 sends Identity Request (identification request) by eNodeB to UE, with the identification information (IMSI) that obtains UE;
After 305:UE receives above-mentioned Identity Request, return Identity Response (identification response) by eNodeB to MME2, the identification information (IMSI) of UE is carried in this response;
Again trigger AKA (Authentication and Key Agreement between UE and the MME2, authorize and key agreement) process, set up safe context, so MME does not need to send safe context in the step 201, correspondingly, S-GW does not need to back up safe context yet.
After 306:MME2 receives above-mentioned Identity Response, send the recovery context request to the pairing S-GW of S-GW sign (S-GW ID), the identification information (IMSI) of UE is carried in this request;
After 307:S-GW receives above-mentioned recovery context request, find the bearer context information of corresponding MME1 current sessions according to the identification information (IMSI) of UE in the request; Simultaneously, return the recovery context response to MME2, the bearer context information of above-mentioned MME1 current sessions is carried in this response;
308:MME2 rebuilds the bearer context information of MME2 according to the bearer context information of the MME1 current sessions that obtains from S-GW, specifically comprises:
A: the information of sign MME1 in the bearer context information of MME1 current sessions is replaced with the information that identifies MME2, as: GUTI.MME2 redistributes GUTI, and this GUTI carries MME2 identification information (MME2ID), and the GUTI in the MME1 context is updated to the GUTI that MME2 redistributes;
B: will except that the bearer context of other MME1 current sessions the information of sign MME1 directly as the bearer context of MME2;
Through step 301-308, just finished the reconstruction of MME2 bearer context information.
309:MME2 sends more new bearer request to S-GW, and the bearer context information of the MME2 of reconstruction is carried in this request;
After 310:S-GW receives above-mentioned more new bearer request, the forwarding face context of the bearer context information updating self of the MME2 that carries according to this request; S-GW sends the bearer update request to P-GW, and the bearer context information of MME2 is carried in this request;
After 311:P-GW receives above-mentioned bearer update request, the context of the bearer context information updating self of the MME2 that carries according to this request; Return the bearer update response to S-GW;
312:S-GW returns the bearer update response to MME2 after receiving above-mentioned bearer update response;
313:MME2 sends Update Location (renewal position) message to HSS, and this message is carried the identification information (MME2ID) of the identification information of UE: IMSI, MME2 etc.;
314:HSS receives above-mentioned Update Location message, and sends Insert Subscriber Data (insertion user data) message to MME2, and this message is carried the identification information of UE, subscription data;
315:MME2 receives above-mentioned message, is UE structure MM (Mobility Management, mobile management) context, and returns Insert Subcriber Data Ack (inserting the user data response) message to HSS, and this message is carried UE identification information (IMSI);
316:HSS sends Update LocationAck (upgrading the position response) message and gives MME2;
By step 313-316, MME2 has finished according to subscription data and has rebuild the contextual process of MM.This is a prior art, repeats no more.
317:MME2 receives above-mentioned Update LocationAck message, and sends TAU Accpet (TAU acceptance) message to UE, finishes the TAU process.
At this moment, MME2 has finished the contextual processes of chain of command such as rebuilding bearer context and MM context, has realized under the unbroken situation of customer service, and the process from fault MME1 switches to MME2 has kept professional continuous.
Present embodiment is by obtaining the bearer context information of the Mobility Management Entity current sessions that breaks down from memory device, according to this bearer context information is that subscriber equipment is set up carrying, realized under the situation of Mobility Management Entity fault, the professional unbroken effect of user's data has improved user experience greatly.
Embodiment 2
Referring to Fig. 5, present embodiment provides a kind of professional continuous system that keeps, and this system comprises: memory device 41 and Mobility Management Entity 42;
This memory device 41, be used to back up the first bearer context information of the first Mobility Management Entity current sessions, receive the recovery context request that this Mobility Management Entity 42 sends, this recovery context request is carried the identification information by the subscriber equipment of this first Mobility Management Entity service, and sends this first bearer context information of this identification information correspondence to this Mobility Management Entity 42; The above-mentioned first bearer context information is the bearer context information by the current sessions of the one or more subscriber equipment correspondences that are in connected state of MME service.
The detailed process that backs up the first bearer context information is:
This memory device 41 can be gateway or other memory device.
This Mobility Management Entity 42, be used for when first Mobility Management Entity breaks down, obtain first identification information and second identification information, this first identification information is the identification information of memory device 41, and this second identification information is the identification information by the subscriber equipment that is in connected state of this first Mobility Management Entity service; From the memory device 41 of this first identification information correspondence, obtain the first bearer context information of the current sessions of this subscriber equipment correspondence according to this second identification information; According to this first bearer context information, for this subscriber equipment is set up carrying.
Referring to Fig. 6, this system also comprises: strengthen base station 43;
This strengthens base station 43, is used for sending fault notification message to the subscriber equipment that is in connected state by this first Mobility Management Entity service; After receiving the second tracking area update request of this subscriber equipment transmission, selecting second Mobility Management Entity is that this subscriber equipment is set up carrying.This second Mobility Management Entity is used for when first Mobility Management Entity breaks down, obtain first identification information and second identification information, this first identification information is the identification information of memory device, this memory device is used to store the first bearer context information of this first Mobility Management Entity current sessions, and this second identification information is the identification information by the subscriber equipment that is in connected state of this first Mobility Management Entity service; From the memory device of this first identification information correspondence, obtain the first bearer context information of the current sessions of this subscriber equipment correspondence according to this second identification information; According to this first bearer context information, for this subscriber equipment is set up carrying.
The system that present embodiment provides is by obtaining the bearer context information of the Mobility Management Entity current sessions that breaks down from memory device, according to this bearer context information is that subscriber equipment is set up carrying, realized under the situation of Mobility Management Entity fault, the professional unbroken effect of user's data has improved user experience greatly.
Embodiment 3
Referring to Fig. 7, present embodiment provides a kind of Mobility Management Entity 42, comprising: identification information acquisition module 421, context acquisition module 422 and the professional module 423 that keeps continuously; Wherein,
Identification information acquisition module 421, be used for when first Mobility Management Entity breaks down, obtain first identification information and second identification information, this first identification information is the identification information of memory device, this memory device is used to store the first bearer context information of this first Mobility Management Entity current sessions, and this second identification information is the identification information by the subscriber equipment that is in connected state of this first Mobility Management Entity service;
Context acquisition module 422 is used for from the memory device of this first identification information correspondence, obtains the first bearer context information of the current sessions of this subscriber equipment correspondence according to this second identification information;
The professional module 423 that keeps continuously is used for according to this first bearer context information, for this subscriber equipment is set up carrying.
Referring to Fig. 8, Mobility Management Entity 42 also comprises:
Context sending module 424 is used for the 3rd bearer context information to this memory device 41 transmission current sessions, the 3rd bearer context information back-up that this memory device 41 will receive.Like this, when Mobility Management Entity 42 broke down, memory device 41 can be selected another Mobility Management Entity for it in resource pool, continued as the subscriber equipment service by Mobility Management Entity 42 services.
Referring to Fig. 9, identification information acquisition module 421 specifically comprises:
The first identification information obtaining unit 421a is used to receive and strengthens the first tracking area update request that the base station sends, and this first identification information is carried in this first tracking area update request;
The second identification information obtaining unit 421b is used for sending the request of obtaining second identification information to this subscriber equipment, receives the response of obtaining second identification information that this subscriber equipment returns, and this second identification information is carried in this response.
Second identification information of this subscriber equipment can be IMSI (International Mobile Subscriber Identification Number, international mobile subscriber identity).
Referring to Figure 10, context acquisition module 422 specifically comprises:
Request transmitting unit 422a is used for sending the recovery context request to the memory device of the first identification information correspondence, and this recovery context request is carried this second identification information;
Context receiving element 422b is used to receive the first bearer context information of the current sessions of this second identification information correspondence that this memory device sends.
Referring to Figure 11, the professional module 423 that keeps continuously specifically comprises:
Context construction unit 423a is used for making up the second bearer context information according to this first bearer context information;
Business relations holding unit 423b is used for the second bearer context information according to this context construction unit 423a structure, is that this subscriber equipment is set up carrying.
Referring to Figure 12, context construction unit 423a specifically comprises:
Identification information makes up subelement 423a1, the information updating that is used for this first Mobility Management Entity of first bearer context information sign is the information of sign second Mobility Management Entity, this second Mobility Management Entity is used for when first Mobility Management Entity breaks down, obtain first identification information and second identification information, this first identification information is the identification information of memory device, this memory device is used to store the first bearer context information of this first Mobility Management Entity current sessions, and this second identification information is the identification information by the subscriber equipment that is in connected state of this first Mobility Management Entity service; From the memory device of this first identification information correspondence, obtain the first bearer context information of the current sessions of this subscriber equipment correspondence according to this second identification information; According to this first bearer context information, for this subscriber equipment is set up carrying;
Beared information makes up subelement 423a2, is used for other the first bearer context information except that the information of this first Mobility Management Entity of sign as the second bearer context information.
The Mobility Management Entity that present embodiment provides is by obtaining the bearer context information of the Mobility Management Entity current sessions that breaks down from memory device, according to this bearer context information is that subscriber equipment is set up carrying, realized under the situation of Mobility Management Entity fault, the professional unbroken effect of user's data has improved user experience greatly.
Embodiment 4
Referring to Figure 13, present embodiment provides a kind of memory device 41, comprising:
Context backup module 411 is used to back up the first bearer context information of the first Mobility Management Entity current sessions;
Context sending module 412, be used to receive the recovery context request that second Mobility Management Entity sends, this recovery context request is carried the identification information by the subscriber equipment of this first Mobility Management Entity service, and send this first bearer context information of this identification information correspondence to this second Mobility Management Entity, make that this second Mobility Management Entity can be according to this first bearer context information, for this subscriber equipment is set up carrying.
This memory device 41 can be gateway or other memory device.
The memory device that present embodiment provides can back up and send the bearer context information of Mobility Management Entity current sessions, making other Mobility Management Entity can be that subscriber equipment is set up carrying according to this bearer context information, realized under the situation of Mobility Management Entity fault, the professional unbroken effect of user's data has improved user experience greatly.
All or part of content in the technical scheme that above embodiment provides can realize that its software program is stored in the storage medium that can read by software programming, storage medium for example: the hard disk in the computer, the hard disk of equipment veneer and internal memory.
The above only is preferred embodiment of the present invention, and is in order to restriction the present invention, within the spirit and principles in the present invention not all, any modification of being done, is equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (19)
1. one kind keeps professional continuous method, it is characterized in that described method comprises:
When first Mobility Management Entity breaks down, obtain first identification information and second identification information, described first identification information is the identification information of memory device, described memory device is used to store the first bearer context information of the described first Mobility Management Entity current sessions, and described second identification information is the identification information by the subscriber equipment that is in connected state of the described first Mobility Management Entity service;
From the memory device of the described first identification information correspondence, obtain the first bearer context information of the current sessions of described subscriber equipment correspondence according to described second identification information;
According to the described first bearer context information, for described subscriber equipment is set up carrying.
2. as claimed in claim 1ly keep professional continuous method, it is characterized in that, described when first Mobility Management Entity breaks down, obtain first identification information and second identification information comprises:
Receive and strengthen the first tracking area update request that the base station sends, described first identification information is carried in the described first tracking area update request;
Send the request of obtaining second identification information to described subscriber equipment;
Receive the response of obtaining second identification information that described subscriber equipment returns, described second identification information is carried in described response.
3. the continuous method of business that keeps as claimed in claim 1, it is characterized in that, described from the memory device of the described first identification information correspondence, the first bearer context information of obtaining the current sessions of described subscriber equipment correspondence according to described second identification information comprises before:
Described memory device receives the first bearer context information of the current sessions of described first Mobility Management Entity transmission;
Described memory device backs up the described first bearer context information.
4. the continuous method of business that keeps as claimed in claim 1, it is characterized in that, described from the memory device of the described first identification information correspondence, the first bearer context information of obtaining the current sessions of described subscriber equipment correspondence according to described second identification information comprises:
Send the recovery context request to described memory device, described recovery context request is carried described second identification information;
Receive the first bearer context information of the current sessions of the described second identification information correspondence that described memory device sends.
5. the continuous method of business that keeps as claimed in claim 1 is characterized in that, and is described according to the described first bearer context information, sets up carrying for described subscriber equipment and comprises:
According to the described first bearer context information, make up the second bearer context information;
According to the described second bearer context information, for described subscriber equipment is set up carrying.
6. the continuous method of business that keeps as claimed in claim 5 is characterized in that described according to the described first bearer context information, the second bearer context information that makes up comprises:
With the information updating of described first Mobility Management Entity of sign in the described first bearer context information is the information of sign second Mobility Management Entity, described second Mobility Management Entity is used for when first Mobility Management Entity breaks down, for described subscriber equipment is set up carrying;
Will except that the sign described first Mobility Management Entity information other first bearer context information as the second bearer context information.
7. the continuous method of business that keeps as claimed in claim 1 is characterized in that, and is described when first Mobility Management Entity breaks down, and obtains first identification information and second identification information and also comprises before:
Strengthen the base station and send fault notification message to the subscriber equipment that is in connected state by the described first Mobility Management Entity service;
Described reinforcement base station receives the second tracking area update request that described subscriber equipment sends;
Base station selected second Mobility Management Entity of described reinforcement and described subscriber equipment are set up carrying, and described second Mobility Management Entity is used for when first Mobility Management Entity breaks down, for described subscriber equipment is set up carrying.
8. as the described continuous method of business that keeps of arbitrary claim among the claim 1-7, it is characterized in that described memory device is a gateway.
9. one kind keeps professional continuous system, it is characterized in that described system comprises: memory device and Mobility Management Entity;
Described memory device comprises:
The context backup module is used to back up the first bearer context information of the first Mobility Management Entity current sessions;
The context sending module, be used to receive the recovery context request that described Mobility Management Entity sends, described recovery context request is carried the identification information by the subscriber equipment of described first Mobility Management Entity service, and send the described first bearer context information of described identification information correspondence to described Mobility Management Entity, make described Mobility Management Entity according to the described first bearer context information, for described subscriber equipment is set up carrying;
Described Mobility Management Entity comprises:
The identification information acquisition module, be used for when first Mobility Management Entity breaks down, obtain first identification information and second identification information, described first identification information is the identification information of memory device, and described second identification information is the identification information by the subscriber equipment that is in connected state of the described first Mobility Management Entity service;
The context acquisition module is used for from the memory device of the described first identification information correspondence, obtains the first bearer context information of the current sessions of described subscriber equipment correspondence according to described second identification information;
The professional module that keeps continuously is used for according to the described first bearer context information, for described subscriber equipment is set up carrying.
10. the continuous system of business that keeps as claimed in claim 9 is characterized in that described system also comprises: strengthen the base station;
Described reinforcement base station is used for sending fault notification message to the subscriber equipment that is in connected state by the described first Mobility Management Entity service; After receiving the second tracking area update request of described subscriber equipment transmission, selecting described Mobility Management Entity is that described subscriber equipment is set up carrying, described Mobility Management Entity is used for when described first Mobility Management Entity breaks down, for described subscriber equipment is set up carrying.
11., it is characterized in that described memory device is a gateway as the described continuous system of business that keeps of arbitrary claim among the claim 9-10.
12. a Mobility Management Entity is characterized in that, described Mobility Management Entity comprises:
The identification information acquisition module, be used for when first Mobility Management Entity breaks down, obtain first identification information and second identification information, described first identification information is the identification information of memory device, described memory device is used to store the first bearer context information of the described first Mobility Management Entity current sessions, and described second identification information is the identification information by the subscriber equipment that is in connected state of the described first Mobility Management Entity service;
The context acquisition module is used for from the memory device of the described first identification information correspondence, obtains the first bearer context information of the current sessions of described subscriber equipment correspondence according to described second identification information;
The professional module that keeps continuously is used for according to the described first bearer context information, for described subscriber equipment is set up carrying.
13. Mobility Management Entity as claimed in claim 12 is characterized in that, described identification information acquisition module comprises:
First identification information obtaining unit is used to receive and strengthens the first tracking area update request that the base station sends, and described first identification information is carried in the described first tracking area update request;
Second identification information obtaining unit is used for sending the request of obtaining second identification information to described subscriber equipment, receives the response of obtaining second identification information that described subscriber equipment returns, and described second identification information is carried in described response.
14. Mobility Management Entity as claimed in claim 12 is characterized in that, described context acquisition module comprises:
Request transmitting unit is used for sending the recovery context request to the memory device of the first identification information correspondence, and described recovery context request is carried described second identification information;
The context receiving element is used to receive the first bearer context information of the current sessions of the described second identification information correspondence that described memory device sends.
15. Mobility Management Entity as claimed in claim 12 is characterized in that, described business keeps module to comprise continuously:
The context construction unit is used for making up the second bearer context information according to the described first bearer context information;
The business relations holding unit is used for the second bearer context information according to described context construction unit structure, is that described subscriber equipment is set up carrying.
16. Mobility Management Entity as claimed in claim 15 is characterized in that, described context construction unit comprises:
Identification information makes up subelement, the information updating that is used for described first Mobility Management Entity of first bearer context information sign is the information of the described Mobility Management Entity of sign, described Mobility Management Entity is used for when described first Mobility Management Entity breaks down, for described subscriber equipment is set up carrying;
Beared information makes up subelement, is used for other the first bearer context information except that the information of described first Mobility Management Entity of sign as the second bearer context information.
17. Mobility Management Entity as claimed in claim 12 is characterized in that, described Mobility Management Entity also comprises:
The context sending module is used for the 3rd bearer context information to described memory device transmission current sessions, described the 3rd bearer context information back-up that described memory device will receive.
18. a memory device is characterized in that, described memory device comprises:
The context backup module is used to back up the first bearer context information of the first Mobility Management Entity current sessions;
The context sending module, be used to receive the recovery context request that second Mobility Management Entity sends, described recovery context request is carried the identification information by the subscriber equipment of described first Mobility Management Entity service, and send the described first bearer context information of described identification information correspondence to described second Mobility Management Entity, make that described second Mobility Management Entity can be according to the described first bearer context information, for described subscriber equipment is set up carrying.
19. memory device as claimed in claim 18 is characterized in that, described memory device is a gateway.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101178504A CN101646270B (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 |
|---|---|---|---|
| CN2008101178504A CN101646270B (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 |
|---|---|
| CN101646270A CN101646270A (en) | 2010-02-10 |
| CN101646270B true CN101646270B (en) | 2011-12-07 |
Family
ID=41657929
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008101178504A Active CN101646270B (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) |
Families Citing this family (23)
| 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 |
| CN102480464B (en) * | 2010-11-24 | 2016-08-17 | 上海宝信软件股份有限公司 | With service calling system and the method that contextual information is injected in web session decoupling |
| WO2012071695A1 (en) * | 2010-11-29 | 2012-06-07 | 华为技术有限公司 | Node fault processing method, system and related device |
| WO2012097524A1 (en) * | 2011-01-21 | 2012-07-26 | 华为技术有限公司 | Method, device and system for processing reset of mobility management network element |
| WO2011110109A2 (en) * | 2011-03-21 | 2011-09-15 | 华为技术有限公司 | Connection establishing method, fault processing method, communication system and device thereof |
| CN102436405B (en) * | 2011-09-05 | 2016-03-30 | 北京星网锐捷网络技术有限公司 | A kind of process context preservation, altering detecting method and device |
| CN103299692A (en) * | 2012-01-10 | 2013-09-11 | 华为技术有限公司 | Method, node, and system for handling partial failure of mobility management entity |
| CN103517302B (en) * | 2012-06-25 | 2017-11-03 | 中兴通讯股份有限公司 | Microwave transport equipment and its rebooting method and device |
| CN103517303A (en) * | 2012-06-25 | 2014-01-15 | 中兴通讯股份有限公司 | Microwave transmission apparatus, and data processing method and device for the same |
| CN103238345A (en) * | 2012-10-31 | 2013-08-07 | 华为技术有限公司 | Communication method, device and system all based on mobile management entity pool (MME Pool) |
| CN103841545B (en) * | 2012-11-27 | 2017-12-29 | 华为技术有限公司 | The method and device that a kind of MME ponds scene ability information reports |
| EP2993957B1 (en) * | 2013-05-31 | 2017-09-06 | Huawei Technologies Co., Ltd. | User equipment management method, device and computer program product |
| CN104284359B (en) * | 2014-06-17 | 2018-10-02 | 南京邮电大学 | Trans-regional disaster tolerance system and control method under a kind of EPC networks |
| CN105323792B (en) * | 2014-07-31 | 2018-11-13 | 中国电信股份有限公司 | Mobility management entity and its disaster recovery method and disaster tolerance system |
| CN105376768B (en) * | 2014-08-19 | 2019-02-22 | 中国电信股份有限公司 | A kind of mobility management entity pond group disaster recovery method and system |
| CN107006046B (en) * | 2015-07-31 | 2021-08-03 | 华为技术有限公司 | Data transmission method and related equipment and system |
| EP3490280B1 (en) * | 2016-08-23 | 2020-11-04 | Huawei Technologies Co., Ltd. | Session management entity relocation |
| CN108200571B (en) * | 2016-12-08 | 2021-03-05 | 中国移动通信集团四川有限公司 | Tracking area updating method and device and mobile management entity |
| CN108668307B (en) * | 2017-03-29 | 2021-04-27 | 中国移动通信集团上海有限公司 | Called service recovery processing method, mobility management entity and service gateway |
| 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 |
| CN110913437B (en) * | 2018-09-14 | 2021-01-29 | 华为技术有限公司 | Communication method and network element |
| JP7127944B2 (en) * | 2021-01-08 | 2022-08-30 | 日本電気株式会社 | Gateway device and control method |
-
2008
- 2008-08-06 CN CN2008101178504A patent/CN101646270B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN101646270A (en) | 2010-02-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101646270B (en) | Method, system, mobility management entity and memory device for maintaining service continuity | |
| EP3751886B1 (en) | Communication method and device under centralized unit-distributed unit architecture | |
| CN101150838B (en) | A method and system for inter-system switching | |
| CN109151807B (en) | Method and system for binding main card and auxiliary card of dual-card dual-standby mobile terminal | |
| US20160014576A1 (en) | Method and Apparatus for Receiving or Sending Short Message | |
| CN102118721A (en) | Evolved packet system and attachment processing method of emergency call thereof | |
| CN101730124A (en) | Method, device and system for resuming service | |
| US20230098825A1 (en) | Short message service ability updating method, device and apparatus | |
| CN103841545B (en) | The method and device that a kind of MME ponds scene ability information reports | |
| CN101772114A (en) | Method, system and device for realizing processing of paging | |
| CN101720115A (en) | Method and system for reestablishing connection of packet data network | |
| CN101083830A (en) | Method for transferring users among different core network equipments | |
| CN101667936A (en) | Method, device and system for fault treatment of access session control server | |
| CN103238345A (en) | Communication method, device and system all based on mobile management entity pool (MME Pool) | |
| WO2018059401A1 (en) | Network switching method, device and system, and network access method and device | |
| WO2020233688A1 (en) | Voice communication method and device thereof | |
| CN104244189A (en) | Paging method in TD-LTE cluster fail-soft communication system | |
| CN101534566A (en) | Method for paging users, wireless access equipment and terminal | |
| CN102045651B (en) | Cluster call method, MSC, BSC and communication system | |
| CN100455133C (en) | Call recovery method and system during network failure | |
| US9781596B2 (en) | Method, apparatus and system for a mobile virtual number service in a mobile telecommunications system | |
| CN103249096A (en) | Switching processing method, equipment and system | |
| CN103428668A (en) | Tracking area updating method and device | |
| CN101047900B (en) | Recovery method of terminal called service, mobile exchange center and system | |
| CN110351800B (en) | Method and system for redundant joint attachment |
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 |