CN101505471A - Method and system for implementing context synchronization in idle status signaling optimization process - Google Patents
Method and system for implementing context synchronization in idle status signaling optimization process Download PDFInfo
- Publication number
- CN101505471A CN101505471A CNA2008100576646A CN200810057664A CN101505471A CN 101505471 A CN101505471 A CN 101505471A CN A2008100576646 A CNA2008100576646 A CN A2008100576646A CN 200810057664 A CN200810057664 A CN 200810057664A CN 101505471 A CN101505471 A CN 101505471A
- Authority
- CN
- China
- Prior art keywords
- management entity
- mobility control
- user mobility
- context
- isr
- 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
- 238000000034 method Methods 0.000 title claims abstract description 83
- 230000011664 signaling Effects 0.000 title claims abstract description 7
- 238000005457 optimization Methods 0.000 title description 4
- 238000005516 engineering process Methods 0.000 claims abstract description 14
- 230000001360 synchronised effect Effects 0.000 claims description 61
- CSRZQMIRAZTJOY-UHFFFAOYSA-N trimethylsilyl iodide Substances C[Si](C)(C)I CSRZQMIRAZTJOY-UHFFFAOYSA-N 0.000 claims description 52
- 230000003213 activating effect Effects 0.000 claims 1
- 230000004048 modification Effects 0.000 description 6
- 238000012986 modification Methods 0.000 description 6
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000002950 deficient Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method and a system for realizing context synchronization during idle-state signaling reduction (ISR), wherein the method comprises the following steps that: user equipment (UE) judges whether a state indicator of the UE needs ISR synchronization when executing tracking area update (TAU) or routing area update (RAU), and sets an update type as ISR synchronization in a TAU request message or a RAU request message and instructs a latest accessed user mobility control management entity of the UE if the state indicator of the UE needs ISR synchronization; and the UE requests an accessed user mobility control management entity to update the context thereof by the context of the latest accessed user mobility control management entity of the UE. The method and the system can solve the problem of context synchronization between two user mobility control management entities under radio access technology (RAT).
Description
Technical field
The present invention relates to the mobile communication technology field, realize the synchronous method and system of context (Context) in particularly idle state signaling optimization (ISR) process.
Background technology
When subscriber equipment (UE) is attached to evolved packet system (EPS), and after having activated idle state signaling optimization (ISR) function, UE will be registered to respectively on Mobility Management Entity (MME) and the service GPRS service node (SGSN), has two entities (MME and SGSN) to preserve the context (Context) of this UE like this in the EPS system.For making things convenient for the description of back, user mobility control and management entity is meant SGSN under the 2G/3G access technology, is meant MME under evolved universal terrestrial radio access network (E-UTRAN) access technology.When user mobility control and management entity was SGSN, then another user mobility control and management entity was MME; Or when user mobility control and management entity was MME, then another user mobility control and management entity was SGSN.
The UE that defines in TS23.401v8.0.0 when free time (Idle) state carries out the process that ISR activated or carried out the ISR state synchronized when UTRAN moves to E-UTRAN, as shown in Figure 1, Fig. 1 is tracing section updating (TAU) process of UE from UTRAN to E-UTRAN.
If UE does not activate ISR, when UE when UTRAN moves to E-UTRAN, then new MME gets its Context data to SGSN, this process is the step 106,107 and 110 among Fig. 1, if SGSN supports the ISR function, then SGSN ISR parameter on the message band of step 107 indicates SGSN to support the ISR function.After new MME authentication is passed through, and new MME also supports the ISR function, and then new MME gives in the message of SGSN in step 110 and is with the ISR parameter, and the ISR function of indication UE activates on SGSN and new MME.That is to say, the ISR if UE is not activated in advance, when user mobility control and management entity will activate the ISR function of UE, then user mobility control and management entity is when another user mobility control and management entity is got its Context, another user mobility control and management entity hereinafter is with its support of ISR parametric representation ISR function in response (Context Response) message thereon, and user mobility control and management entity confirms to be with ISR parametric representation ISR function to activate in (Context Acknowledge) message for the context of another user mobility control and management entity then.
If UE is the ISR that has been activated, and UE is when moving to a new MME when UTRAN moves back to E-UTRAN, and then new MME gets the Context data to old MME, is that step 104,105 and 109 is finished in Fig. 1.UE also needs to fetch its Context data from SGSN simultaneously, is that step 106,107 and 110 is finished in Fig. 1.This just a problem occurs: when two Context exist, is the Context that provides with which entity (being that SGSN still is old MME) as the Context of new MME, still upgrade the Context of new MME with two Context that entity was provided? if when upgrading the Context of new MME, how to handle with two Context that entity was provided?
The step 111 of TS23.401 definition Fig. 1 points out, is ＂ ISR synchronously during (ISR Synch) ＂ when UE indicates the updating type of its TAU, and then new MME adopts the Context that SGSN provided to upgrade.Otherwise new MME can adopt the old Context that MME or SGSN provided to upgrade.
It is the condition of ＂ ISR Synch ＂: UE is block data protocol context (PDP Context) foundation, modification, a dispose procedure of having carried out 2G/3G that the step 102 of Fig. 1 has provided the updating type that UE is provided with TAU, and with MME without any signaling mutual.
But above-mentioned condition is defective.For example, after UE had activated ISR, UE did not carry out PDP Context foundation, modification, the dispose procedure of 2G/3G; But UE has carried out authentication and key agreement (AKA) process again under 2G/3G, and gets back to idle condition after having used new CK and IK, and after this moment, UE moved to E-UTRAN, according to safe requirement, UE and MME should use based on the new K that CK, IK produced
ASME, this stylish MME still needs to use the Context of SGSN, rather than the Context of old MME.
In addition, after UE has activated ISR, UE does not carry out PDP Context foundation, modification, the dispose procedure of 2G/3G under 2G/3G, but foundation, modification, the dispose procedure of EPS carrying (EPS Bearer) under E-UTRAN, have been carried out, get back to idle condition then, and move to new not belonging in the original tracking area identification list (TAI List) behind the tracking area (TA) and MME, carry out the TAU operation, this stylish MME should use the Context of old MME, rather than uses the Context of SGSN.
In addition, TS23.401 points out after UE activates the ISR function, when the UE that is in idle condition enters the TA that does not belong among the TAI List, will carry out the TAU operation.This condition neither be very abundant.For example, if UE has carried out PDP Context foundation, modification, the dispose procedure of 2G/3G under 2G/3G, when UE gets back to E-UTRAN, all to enter the TAU operation, no matter it is whether entered the TA that does not belong among the TAI List, synchronous with the Context that realizes MME and SGSN as early as possible.
As fully visible, can not solve in the prior art between two user mobility control and management entities under two wireless access technologys (RAT), between old SGSN and the new SGSN and the Context stationary problem between old MME and the new MME.
Summary of the invention
The embodiment of the invention proposes in a kind of ISR process to realize the synchronous method of Context, and this method can solve between two user mobility control and management entity SGSN and MME under the RAT, between old SGSN and the new SGSN and the Context stationary problem between old MME and the new MME.
The embodiment of the invention also proposes in a kind of ISR process to realize the synchronous system of Context, and this system can solve between two user mobility control and management entity SGSN and MME under the RAT, between old SGSN and the new SGSN and the Context stationary problem between old MME and the new MME.
Technical scheme of the present invention is achieved in that
Realize the synchronous method of Context in a kind of ISR process, comprising:
When UE carries out TAU or RAU, whether the status indicator of judging UE is " needing ISR (ISRSynch Needed) synchronously ", if, then updating type is set to " ISR is (ISR Synch) synchronously " in TAU request message or RAU request message, and indicates the second user mobility control and management entity;
The first user mobility control and management entity upgrades its Context with the Context of the described second user mobility control and management entity;
The described first user mobility control and management entity is the user mobility control and management entity that the UE request inserts; The described second user mobility control and management entity is the UE user mobility control and management entity of recent access.
Realize the synchronous system of Context in a kind of ISR process, it is characterized in that described system comprises:
UE, be used for when carrying out TAU or RAU, whether the status indicator of judging UE is " needing ISR (ISR Synch Needed) synchronously ", if, then updating type is set to " ISR is (ISR Synch) synchronously " in TAU request message or RAU request message, and indicates the second user mobility control and management entity;
The first user mobility control and management entity is used for upgrading its Context with the Context of the described second user mobility control and management entity;
The described first user mobility control and management entity is the user mobility control and management entity that the UE request inserts; The described second user mobility control and management entity is the UE user mobility control and management entity of recent access.
A kind of UE, when being used to carry out tracing section updating TAU or routing area updating RAU, judge that the status indicator of UE is whether synchronous for needs ISR, if, then in TAU request message or RAU request message updating type to be set to ISR synchronous, and indicate the second user mobility control and management entity; The described second user mobility control and management entity is the UE user mobility control and management entity of recent access.
A kind of user mobility control and management entity, be used for after receiving the TAU request message or RAU request message that UE sends, upgrade its Context with the Context of the second user mobility control and management entity of indicating in described TAU request message or the RAU request message; The described second user mobility control and management entity is the UE user mobility control and management entity of recent access.
As seen, the method and system that the embodiment of the invention proposes, by a newly-increased parameter " ISR SynchNeeded) ", after the state mark of UE is set to " ISR Synch Needed " by knowledge, UE updating type when carrying out TAU or RAU is set to " (ISR Synch) " and indicates the user mobility control and management entity that UE inserts recently, new user mobility control and management entity is according to upgrading its Context with the indication of UE, thus realize Context synchronously.
Description of drawings
Fig. 1 is the TAU process of UE from UTRAN to E-UTRAN;
Fig. 2 is the synchronous flow chart of Context in the embodiment of the invention one TAU process;
Fig. 3 is the synchronous flow chart of Context in the embodiment of the invention two RAU processes;
The flow chart that Fig. 4 is eliminated for ＂ ISR Synch Needed ＂ sign in the embodiment of the invention three TAU processes.
Embodiment
The embodiment of the invention proposes a kind of Context method for synchronous, propose to have entered connection (ECM_CONNECTED) state from idle (ECM_Idle) state as UE, when getting back to idle condition again, as long as S-TMSI or P-TMSI in the MM Context (MM Context) among the UE, Routing Area Identifier (RAI) or TAI List, parameters such as Key in the fail safe context (Security Context) or KSI change or EPS carries (EPS Bearer) or change has taken place PDP Context, and the status indicator ＂ that UE then is set needs ISR (ISR Synch Needed) ＂ synchronously.Can be 1 to represent to be provided with " ISR Synch Needed " with the value of " ISR Synch Needed ", be 0 to represent cancellation " ISR Synch Needed " with the value of " ISR Synch Needed "; Certainly, this only is a kind of expression mode, and other multiple expression modes can also be arranged.The status indicator ＂ that UE is set as UE needs ISR synchronously (ISR SynchNeeded) ＂ the time, it is the current user mobility control and management entity of UE that UE also writes down nearest access user mobility control and management entity, for simply, with UE the user mobility control and management entity of recent access be designated as the second user mobility control and management entity of UE.If UE is provided with its status indicator ＂ ISRSynch Needed ＂, then the updating type of TAU or RAU is set to " ISR Synch ".When UE carries out TAU or route district (RAU) process, if the updating type of UE indication TAU or RAU is " ISRSynch ", then new MME or SGSN are after obtaining the Context that MME and SGSN provide, enter the nearest access user mobility control and management entity (MME or SGSN) of connection status recently with UE, it is the second user mobility control and management entity of UE, its Context is provided behind the Context that is provided, with nearest access user mobility control and management entity to be other the user mobility control and management entity that UE activates the ISR function, be the 3rd user mobility control and management entity of UE, the Context that is provided upgrades its Context earlier.That is to say, when parameter need be revised, upgrade with the Context content that UE enters the entity (MME or SGSN) of connection status recently and provided, be to guarantee that the MM Context of new user mobility control and management entity and carrying Context are up-to-date like this, and be consistent with UE, realized among UE and EPS network and the ISR two user mobility control and management entities MM Context and carrying Context synchronously.The user mobility control and management entity that enters connection status with UE recently can be to be positioned at same RAT with the present user mobility control and management entity of serving UE, also can be to be positioned at different RAT, promptly the second user mobility control and management entity and the first user mobility control and management entity can be in same RAT, also can be positioned at different RAT, but the 3rd user mobility control and management entity always is positioned at different RAT with the second user mobility control and management entity.Cause second user mobility control and management entity and the 3rd user mobility control and management entity have activated the ISR function of UE, in the Context of the second user mobility control and management entity, record the relevant data of the 3rd user mobility control and management entity, also record the relevant data of the second user mobility control and management entity simultaneously among the Context of the 3rd user mobility control and management entity, from these data, all can obtain the other side's sign.That is to say, according to the sign that can obtain the 3rd user mobility control and management entity among the Context of the second user mobility control and management entity.
Realize in the ISR process that the embodiment of the invention proposes that the synchronous method of Context is specifically as follows: when UE carries out TAU or RAU, whether the status indicator of judging UE is synchronous for needs ISR, if, then in TAU request message or RAU request message updating type to be set to ISR synchronous, and indicate the second user mobility control and management entity;
The first user mobility control and management entity upgrades its Context with the Context of the described second user mobility control and management entity;
The user mobility control and management entity that the described first user mobility control and management entity inserts for the UE current request; The described second user mobility control and management entity is the UE user mobility control and management entity of recent access.
Wherein, the first user mobility control and management entity is specifically as follows with the process that the Context of the described second user mobility control and management entity upgrades its Context:
The first user mobility control and management entity upgrades its Context with the Context of the 3rd user mobility control and management entity earlier, and the Context with the described second user mobility control and management entity upgrades its Context then; Wherein, the 3rd user mobility control and management entity is the user mobility control and management entity that has activated the ISR function with the second user mobility control and management entity in advance for UE.
Below lifting specific embodiment introduces in detail:
Embodiment one: referring to Fig. 2, Fig. 2 is the synchronous flow chart of Context in the embodiment of the invention one TAU process.
The change of P-TMSI or S-TMSI can cause the variation of the MM Context of UE, and present embodiment is with the example of changing into of S-TMSI.
As shown in Figure 2, as the UE ISR that has been activated, the UE of MME paging idle condition, UE responds paging, initiates service request (Service Request).Then, MME (comprises new GUTI by the heavy assignment commands of global unique temporary identity (GUTI Reallocation Command) of the step 201 among Fig. 2, new TAI List) message, for after UE distributed a new GUTI (comprising S-TMSI among the GUTI), UE gets back to idle condition again.At this moment, because being UE, MME distributes new GUTI, change has taken place in the employed S-TMSI of UE, just change has taken place in the MM Context of UE, then this moment, UE was provided with ＂ ISR Synch Needed ＂ sign, write down the user mobility control and management entity that UE inserts recently (the i.e. second user mobility control and management entity simultaneously, can represent with Last Context Location) be current user mobility control and management entity MME, Last Context Location=MME just, after get back to idle condition.
In the step 203, after UE moves to a new TA and new MME (i.e. the first user mobility control and management entity) who does not belong among the original T AI List, UE initiating updating of tracking area request (TAUpdate Request) (comprising: new GUTI, UpdateType=ISR Synch, Last ContextLocation=MME, Last Visited TAI), initiate the TAU process.
By step 204 and 206, new MME obtains the old Context that MME provided; By step 205 and 207, new MME obtains the Context that SGSN (the 3rd user mobility control and management entity just) is provided.After the 8th step subscription authentication is passed through, this stylish MME decides according to LastContext Location=MME and does not use the specified user mobility control and management of Last Context Location entity MME earlier, but elder generation uses the user mobility control and management entity (the 3rd user mobility control and management entity just) of another RAT, the Context that is SGSN upgrades its Context, use then with the specified user mobility control and management entity of Last Context Location (the second user mobility control and management entity just), upgrade its Context behind the Context of promptly old MME.
Same reason, when UE under 2G/3G, because of P-TMSI heavily distributes (P-TMSI Reallocation) process, the P-TMSI of UE has been done change, and do not have foundation, modification or the dispose procedure of PDP Context, this moment, UE was provided with ＂ ISR Synch Needed ", and when UE moves to E-UTRAN; UE initiation TAU process, the updating type of TAU is set to ＂ ISR Synch ＂.
The present embodiment introduction be the example of the variation of the change of P-TMSI or the S-TMSI MM Context that can cause UE.In other embodiments of the invention, UE will produce new CK, an IK, KSI in the AKA of UTRAN process, cause the variation of the MM Context of UE; Equally, UE produces a new K in the AKA of E-UTRAN process
ASME, KSI
ASME, also cause the variation of the MM Context of UE; It is synchronous that employing mode same as described above is carried out Context under these situations, specifically repeats no more.
In addition, in embodiment one, it is MME that UE has indicated its user mobility management entity that inserts recently, i.e. " Last Context Location=MME ", direct mode has been taked in this indication, that is, the value of Last Context Location directly is MME or SGSN.In other embodiments of the invention, UE indicates its user mobility management entity that inserts recently also can adopt indirect mode, as UTRAN/GERAN or E-UTRAN, and perhaps P-TMSI or S-TMSI or the like.UE is in the process of TAU or RAU like this, UE need carry " Last Context Location " in TA Update Request or RA UpdateRequest message, the Context that is used to indicate new user mobility control and management entity (MME or SGSN) to use " Last Context Location " indicated old user mobility control and management entity to be provided upgraded its Context the most afterwards.
Embodiment two: referring to Fig. 3, Fig. 3 is the synchronous flow chart of Context in the embodiment of the invention two RAU processes.
As shown in Figure 3, before step 301, old SGSN (the second user mobility control and management entity) and MME (the 3rd user mobility control and management entity) are for UE has activated the ISR function, and the ＂ ISR Synch Needed ＂ of UE sign is eliminated (promptly can adopt: the value of " ISR Synch Needed " is changed to 0).
Step 301, UE carries out P-TMSI and heavily distributes (P-TMSI Reallocation) function under old SGSN, old SGSN is that UE has distributed a new P-TMSI, and this moment, UE was provided with ＂ ISR SynchNeeded ＂, and it is SGSN that ＂ Last Context Location ＂ is set.
Step 302, when UE moves to new SGSN (the first user mobility control and management entity), UE sends Routing Area Update request (RA Update Request) message to new SGSN, the parameter Update Type=ISR Synch that wherein carries in the message, Last Context Location=SGSN.
By step 303 and 305, new SGSN obtains the Context that old SGSN (the second user mobility control and management entity) is provided; By step 304 and 306, new SGSN obtains the Context that MME (the 3rd user mobility control and management entity) is provided.Because of in the message of step 302, the ＂ Last Context Location ＂ that UE provides is SGSN, new SGSN does not use the specified user mobility control and management entity SGSN of Last ContextLocation earlier, but the Context that uses the user mobility control and management entity MME under another RAT to be provided earlier upgrades its Context content, with the specified user mobility control and management entity of Last Context Location, the promptly old Context that SGSN provided upgrades its Context content then.Just, the Context that at first uses the 3rd user mobility control and management entity MME entity to be provided upgrades its Context content, upgrade its Context content with the old Context that SGSN was provided of the second user mobility control and management entity then, the Context that new like this SGSN obtains is up-to-date, and has kept consistent with the Context state of UE.
Similar with the situation among the embodiment one, UE has indicated its user mobility management entity that inserts recently and also can adopt indirect mode in the step 302, as UTRAN/GERAN or E-UTRAN, and perhaps P-TMSI or S-TMSI or the like.
In addition, the embodiment of the invention also proposes, if UE has been provided with ＂ ISR Synch Needed ＂ sign, UE has entered connection status (as passing through TAU in same RAT, RAU or Service Request process), no matter whether S-TMSI or parameter, EPS Bearer and PDP Context such as Key among P-TMSI, RAI or TAI List, the SecurityContext or KSI among the MM Context of UE variation has taken place, the ＂ ISR Synch Needed ＂ that has been provided with of UE can not remove, and also should remain the state of setting.
For example, in Fig. 3, old SGSN (the second user mobility management entity) and MME (the second user mobility management entity) are for UE has activated the ISR function, and the ＂ ISR Synch Needed ＂ of UE sign is eliminated.In step 301, UE has carried out P-TMSI Reallocation function under old SGSN, and old SGSN is that UE has distributed a new P-TMSI, and this moment, UE was provided with ＂ ISR SynchNeeded ＂, and it is SGSN that ＂ Last Context Location ＂ is set.In step 302, when UE moves to new SGSN (the first user mobility management entity), UE goes up to new SGSN and sends RA UpdateRequest message, the parameter Update Type=ISR Synch that wherein carries in the message, Last ContextLocation=SGSN.Because of Last Context Location is SGSN, new SGSN comes its Context of final updating with the old Context that SGSN was provided.Suppose that new SGSN does not distribute new P-TMSI for UE in the RAU process, do not carry out the AKA process yet, and in step 304,306,309 and 310, new SGSN (the first user mobility management entity) has replaced old SGSN (the second user mobility management entity) and MME (the 3rd user mobility management entity) to activate the ISR function once more; RAU in step 311 accepts in (RAU Accept) message, and new SGSN does not carry new P-TMSI.Because UE is execution under same RAT carrying out RAU on the new SGSN, therefore when UE executes RAU after, UE gets back to the Idle state, and the ＂ ISR Synch Needed ＂ that UE is provided with identifies and be not eliminated.Like this, when UE moves to new MME, when UE carries out TAU, new MME will upgrade its Context earlier with the old Context that MME was provided, and upgrade its Context with the new Context that SGGN was provided then.
Embodiment three: referring to Fig. 4, and the flow chart that Fig. 4 is eliminated for ＂ ISR Synch Needed ＂ sign in the embodiment of the invention three TAU processes.
Opposite with embodiment two, if UE has been provided with ＂ ISR Synch Needed ＂ sign, UE with another different RAT at the indicated user mobility control and management entity place of ＂ LastContext Location ＂ in entered connection status (as passing through TAU, the RAU process) time, after TAU or RAU process are finished, if S-TMSI or P-TMSI among the MM Context of UE, RAI or TAI List, parameters such as Key among the SecurityContext or KSI, EPS Bearer and PDP Context all do not change, and then UE removes its ＂ ISR Synch Needed ＂ state.Show that SGSN and MME have realized synchronously this moment on Context.
As shown in Figure 4, SGSN (the second user mobility management entity) and MME (the 3rd user mobility management entity) are for UE has activated the ISR function, and the ＂ ISR Synch Needed ＂ of UE sign is eliminated.In step 401, UE has carried out P-TMSI Reallocation function under SGSN, SGSN is that UE has distributed a new P-TMSI, UE will be provided with ＂ ISR Synch Needed ＂ sign this moment, and ＂ Last Context Location ＂ is set is SGSN, in step 402, when UE moves back to original MME (the first user mobility management entity, this moment, the first user mobility management entity and the 3rd user mobility management entity were same entity), UE carries out TAU on MME, the ＂ Last ContextLocation ＂ that provides because of UE is SGSN, and the Context that MME is provided with SGSN (the second user mobility management entity) comes the back to upgrade its Context most.MME not for UE distributes new S-TMSI, does not carry out the AKA process yet in the TAU process; TAU Accept message in step 407 is not carried new GUTI.Since UE carry out on the MME TAU be with another different RAT at the indicated user mobility control and management entity place of ＂ Last Context Location ＂ under execution TAU, so after UE executes TAU, UE gets back to the Idle state, and removes the ＂ ISR Synch Needed ＂ sign of UE.UE removes its ＂ ISRSynch Needed ＂ sign, shows that the Context of MME and the Context of SGSN have realized synchronously.
In addition, the embodiment of the invention also proposes, if the sign of the ＂ ISR Synch Needed ＂ among the UE is eliminated, UE has entered connection status (as passing through TAU in same RAT, the RAU process), user mobility control and management entity (SGSN or MME) upgrades its Context with the Context that the user mobility control and management entity (SGSN or MME) under its identical RAT is provided, and promptly this moment, the 3rd user mobility control and management entity was a user mobility control and management entity under its identical RAT; And then with another user mobility control and management entity (being MME or SGSN) of other RAT, the i.e. second user mobility control and management entity, upgrade the ISR function that activates UE, and upgrade its Context with the Context of this second user mobility control and management entity once more.
For example, SGSN (the 3rd user mobility control and management entity) and MME (the second user mobility control and management entity) are for UE has activated the ISR function, and the ＂ ISR Synch Needed ＂ of UE sign is eliminated.UE moves and enters under the new SGSN (the first user mobility control and management entity) and carries out the RAU process, this stylish SGSN upgrades its Context with the Context that the old SGSN (i.e. the 3rd user mobility control and management entity) with RAT is provided, upgrade with MME (i.e. the second user mobility control and management entity) then and activate the ISR function, and upgrade its Context with the Context that MME was provided.
In addition, the problem that the embodiment of the invention can also solve is that after UE activated the ISR function, when the UE of idle condition initiated TAU or RAU operation.Below in two kinds of situation:
After UE was provided with ＂ ISR Synch Needed ＂ sign, if UE enters another RAT from a RAT, even UE still is positioned at the zone that RAI or TAI List are identified, UE also needed to do RAU or TAU.Entered as UE under the access technology of 2G/3G, done the RAU operation; UE enters under the E-UTRAN access technology, does the TAU operation.
After UE was provided with ＂ ISR Synch Needed ＂ sign, if UE is in the zone that RAI in same RAT or TAI List are identified when mobile, UE did not need to do RAU or TAU.Certainly, regardless of ＂ ISR Synch Needed ＂ identification-state as UE, when UE leaves the RAI of present registration and the zone that TAI List is identified, when having entered the band of position of a new RAI who does not belong to current registration or TAI list, UE need make TAU or RAU.
The embodiment of the invention also comprises: after ISR activates, when P-TMSI or GUTI change, or RAI or TAI List are when changing, comprise two TMSI parameters (being P-TMSI and GUTI) and RAI and Last Visited TAI at TAU Request or RAU Request message, and MME or SGSN should resolve and obtain its Context with the location that the TMSI that carries in TAU Request or the RAU Request message and RAI or TAI carry out the second user mobility control and management entity MME or SGSN.
If in TAU Request or RAU Request message, do not include two TMSI parameters and RAI and Last Visited TAI, the then problem that addressing, route may occur or search.For example, in the step 401 of embodiment three, UE carries out the heavily distribution of P-TMSI in SGSN, SGSN has distributed a new P-TMSI to UE, in step 402, if be not with P-TMSI in TAU Request message, then MME can only carry out the analytical capabilities of SGSN according to the old P-TMSI that stores among its Context and RAI, at this moment, also can obtain the IP address of SGSN.In step 403, when MME when SGSN sends ContextRequest message, P-TMSI is old P-TMSI in the Context Request message at this moment, and SGSN has distributed a new P-TMSI to UE again in step 401, this moment, SGSN can not correctly obtain the UE that searched, then in step 404, the Context of UE that SGSN may provide the IMSI of a mistake gives MME, thereby throws into question.Therefore in step 403, MME should carry out the addressing of SGSN with UE was provided in the message in the step 402 P-TMSI and old RAI, and the P-TMSI in the Context Request message of step 403 should be the P-TMSI in the message of step 402.
The embodiment of the invention also proposes to realize the synchronous system of Context in a kind of ISR process, comprising:
UE is used for when carrying out TAU or RAU, judges that the status indicator of UE is whether synchronous for needs ISR, if, then in TAU request message or RAU request message updating type to be set to ISR synchronous, and carry the second user mobility control and management entity identification;
The first user mobility control and management entity is used for upgrading its Context with the Context of the described second user mobility control and management entity;
The described first user mobility control and management entity is the user mobility control and management entity that the UE request inserts; The described second user mobility control and management entity is the UE user mobility control and management entity of recent access.
Above-mentioned UE can be further used for:
Whether MM Context, the EPS Bearer or the PDP Context that judge UE change, if change, it is synchronous that then the status indicator of UE need to be set to ISR, and write down the user mobility control and management entity that the second user mobility control and management entity is the current access of UE.
The status indicator of judging UE is needs ISR when synchronous, if UE has entered connection status in the RAT identical with the wireless access technology RAT at the described second user mobility control and management entity place, then keeps the setting of the synchronous status indicator of the described ISR of needs;
The status indicator of judging UE is needs ISR when synchronous, if UE has entered connection status in the RAT different with the RAT at the described second user mobility control and management entity place, whether MMContext, the EPS Bearer or the PDP Context that then judge UE change under new RAT, if do not change, then remove the synchronous status indicator of the described ISR of needs.
The embodiment of the invention also proposes a kind of UE, when being used to carry out tracing section updating TAU or routing area updating RAU, whether the status indicator of judging UE is synchronous for needs ISR, if, then in TAU request message or RAU request message updating type to be set to ISR synchronous, and indicate the second user mobility control and management entity; The described second user mobility control and management entity is the UE user mobility control and management entity of recent access.
Above-mentioned UE can be further used for: whether MM Context, the EPS Bearer or the PDPContext that judge UE change, if change, it is synchronous that then the status indicator of UE need to be set to ISR, and write down the user mobility control and management entity that the second user mobility control and management entity is the current access of UE.
The status indicator of judging UE is needs ISR when synchronous, if UE has entered connection status in the RAT identical with the wireless access technology RAT at the described second user mobility control and management entity place, then keeps the setting of the synchronous status indicator of the described ISR of needs;
The status indicator of judging UE is needs ISR when synchronous, if UE has entered connection status in the RAT different with the RAT at the described second user mobility control and management entity place, whether MMContext, the EPS Bearer or the PDP Context that then judge UE change under new RAT, if do not change, then remove the synchronous status indicator of the described ISR of needs.
The embodiment of the invention also proposes a kind of user mobility control and management entity, be used for after receiving the TAU request message or RAU request message that UE sends, upgrade its Context with the Context of the second user mobility control and management entity of indicating in described TAU request message or the RAU request message; The described second user mobility control and management entity is the UE user mobility control and management entity of recent access.
Wherein, above-mentioned family mobility control and management entity is after receiving the TAU request message or RAU request message that UE sends, can be earlier upgrade its Context with the Context of the 3rd user mobility control and management entity, the Context with the described second user mobility control and management entity upgrades its Context again; The 3rd user mobility control and management entity is to be the user mobility control and management entity that UE has activated the ISR function with the second user mobility control and management entity before this.
As fully visible, the method and system that the embodiment of the invention proposes, by a newly-increased ＂ ISR SynchNeeded ＂ parameter and defined the method how updating type " ISR Synch " is set up, solved between the user mobility management entity SGSN and MME under two RAT, between old SGSN and the new SGSN and the Context stationary problem between old MME and the new MME.
Claims (21)
1, a kind of idle state signaling is optimized the synchronous method of realization context Context in the ISR process, it is characterized in that described method comprises:
When user equipment (UE) is carried out tracing section updating TAU or routing area updating RAU, whether the status indicator of judging UE is synchronous for needs ISR, if, then in TAU request message or RAU request message updating type to be set to ISR synchronous, and indicate the second user mobility control and management entity;
The first user mobility control and management entity upgrades its Context with the Context of the described second user mobility control and management entity;
The described first user mobility control and management entity is the user mobility control and management entity that the UE request inserts; The described second user mobility control and management entity is the UE user mobility control and management entity of recent access.
2, method according to claim 1 is characterized in that, further comprises before the described method:
Whether mobility context MM Context, the evolved packet system carrying EPS Bearer or the block data protocol context PDP Context that judge UE change, if change, it is synchronous that then the status indicator of UE need to be set to ISR, and write down the user mobility control and management entity that the second user mobility control and management entity is the current access of UE.
3, method according to claim 2 is characterized in that, the MM Context of described UE changes and comprises:
Evolved packet system Temporary Mobile Station Identity S-TMSI, grouping Temporary Mobile Station Identity P-TMSI, Routing Area Identifier RAI, tracking area identification list TAI List or fail safe context Security Context change.
4, method according to claim 1 is characterized in that, the described mode of the second user mobility control and management entity of indicating in TAU request message or RAU request message is:
In TAU request message or RAU request message, carry the title of the second user mobility control and management entity, the title of the second user mobility control and management entity place access technology or the type of the employed TMSI of the second user mobility control and management entity.
5, method according to claim 1 is characterized in that, the described first user mobility control and management entity upgrades its Context with the Context of the second user mobility control and management entity and comprises:
The first user mobility control and management entity upgrades its Context with the Context of the 3rd user mobility control and management entity earlier, and the Context with the described second user mobility control and management entity upgrades its Context again;
Described the 3rd user mobility management entity is the user mobility control and management entity that activates the ISR function with the second user mobility control and management entity for UE.
6, method according to claim 5, the sign of described the 3rd user mobility control and management entity are to obtain from the Context of the described second user mobility control and management entity.
7, method according to claim 2, it is characterized in that, described method further comprises: when the status indicator of UE need to be set to ISR synchronous, if UE has entered connection status in the RAT identical with the wireless access technology RAT at the described second user mobility control and management entity place, then keep the setting of the synchronous status indicator of the described ISR of needs.
8, method according to claim 2, it is characterized in that, described method further comprises: when the status indicator of UE need to be set to ISR synchronous, if UE has entered connection status in the RAT different with the RAT at the described second user mobility control and management entity place, whether MMContext, the EPS Bearer or the PDP Context that then judge UE change under new RAT, if do not change, then remove the synchronous status indicator of the described ISR of needs.
9, method according to claim 2, it is characterized in that, described method further comprises: when UE is not provided with when needing the synchronous status indicator of ISR, if UE has entered connection status in same RAT, then the 3rd user mobility control and management entity is the old user mobility control and management entity under the RAT current with it, the second user mobility control and management entity is the user mobility control and management entity under other RAT, and upgrading the ISR function that activates UE with the second user mobility control and management entity, the Context that is provided with the second user mobility control and management entity upgrades its Context again.
10, method according to claim 2, it is characterized in that, described method further comprises: when UE is provided with when needing the synchronous status indicator of ISR, if UE enters another RAT from a RAT, then UE need carry out TAU or RAU process, and the Context of the first user mobility control and management entity obtains upgrading and be synchronous in TAU or RAU process.
11, method according to claim 2, it is characterized in that, described method further comprises: when UE is provided with when needing the synchronous status indicator of ISR, if move in the zone that RAI or TAIList identified of UE in same RAT, then UE does not carry out general TAU or general RAU.
12, method according to claim 2, it is characterized in that, described method further comprises: after ISR activates, if global unique temporary identity GUTI or TAI List change, then comprise the GUTI and the Last Visited TAI of recent visit, P-TMSI and RAI at TAU or RAU request message; The first user mobility control and management entity obtains its Context with described GUTI and Last Visited TAI to the second user mobility control and management entity MME that is located.
13, method according to claim 2 is characterized in that, described method further comprises: ISR if P-TMSI or RAI change, then comprises P-TMSI and RAI at TAU or RAU request message, GUTI and Last Visited TAI after activating; The first user mobility control and management entity obtains its Context with the second user mobility control and management entity SGSN that described P-TMSI and RAI located.
14, realize the synchronous system of Context in a kind of ISR process, it is characterized in that described system comprises:
UE is used for when carrying out TAU or RAU, judges that the status indicator of UE is whether synchronous for needs ISR, if, then in TAU request message or RAU request message updating type to be set to ISR synchronous, and indicate the second user mobility control and management entity;
The first user mobility control and management entity is used for upgrading its Context with the Context of the described second user mobility control and management entity;
The described first user mobility control and management entity is the user mobility control and management entity that the UE request inserts; The described second user mobility control and management entity is the UE user mobility control and management entity of recent access.
15, system according to claim 14 is characterized in that, described UE is further used for:
Whether MM Context, the EPS Bearer or the PDP Context that judge UE change, if change, it is synchronous that then the status indicator of UE need to be set to ISR, and write down the user mobility control and management entity that the second user mobility control and management entity is the current access of UE.
16, system according to claim 14 is characterized in that, described UE is further used for:
The status indicator of judging UE is needs ISR when synchronous, if UE has entered connection status in the RAT identical with the wireless access technology RAT at the described second user mobility control and management entity place, then keeps the setting of the synchronous status indicator of the described ISR of needs;
The status indicator of judging UE is needs ISR when synchronous, if UE has entered connection status in the RAT different with the RAT at the described second user mobility control and management entity place, whether MMContext, the EPS Bearer or the PDP Context that then judge UE change under new RAT, if do not change, then remove the synchronous status indicator of the described ISR of needs.
17, a kind of user equipment (UE), it is characterized in that, when described UE is used to carry out tracing section updating TAU or routing area updating RAU, whether the status indicator of judging UE is synchronous for needs ISR, if, then in TAU request message or RAU request message updating type to be set to ISR synchronous, and indicate the second user mobility control and management entity; The described second user mobility control and management entity is the UE user mobility control and management entity of recent access.
18, UE according to claim 17, it is characterized in that, described UE is further used for: whether MM Context, the EPS Bearer or the PDP Context that judge UE change, if change, it is synchronous that then the status indicator of UE need to be set to ISR, and write down the user mobility control and management entity that the second user mobility control and management entity is the current access of UE.
19, UE according to claim 17 is characterized in that, described UE is further used for:
The status indicator of judging UE is needs ISR when synchronous, if UE has entered connection status in the RAT identical with the wireless access technology RAT at the described second user mobility control and management entity place, then keeps the setting of the synchronous status indicator of the described ISR of needs;
The status indicator of judging UE is needs ISR when synchronous, if UE has entered connection status in the RAT different with the RAT at the described second user mobility control and management entity place, whether MMContext, the EPS Bearer or the PDP Context that then judge UE change under new RAT, if do not change, then remove the synchronous status indicator of the described ISR of needs.
20, a kind of user mobility control and management entity, it is characterized in that, described user mobility control and management entity is used for after receiving the TAU request message or RAU request message that UE sends, and upgrades its Context with the Context of the second user mobility control and management entity of indicating in described TAU request message or the RAU request message; The described second user mobility control and management entity is the UE user mobility control and management entity of recent access.
21, user mobility control and management entity according to claim 20, it is characterized in that, described user mobility control and management entity is after receiving the TAU request message or RAU request message that UE sends, Context with the 3rd user mobility control and management entity upgrades its Context earlier, and the Context with the described second user mobility control and management entity upgrades its Context again;
Described the 3rd user mobility management entity is the user mobility control and management entity that activates the ISR function with the second user mobility control and management entity for UE.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008100576646A CN101505471B (en) | 2008-02-04 | 2008-02-04 | Method and system for implementing context synchronization in idle status signaling optimization process |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008100576646A CN101505471B (en) | 2008-02-04 | 2008-02-04 | Method and system for implementing context synchronization in idle status signaling optimization process |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101505471A true CN101505471A (en) | 2009-08-12 |
| CN101505471B CN101505471B (en) | 2011-11-23 |
Family
ID=40977487
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008100576646A Active CN101505471B (en) | 2008-02-04 | 2008-02-04 | Method and system for implementing context synchronization in idle status signaling optimization process |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101505471B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101998433A (en) * | 2009-08-14 | 2011-03-30 | 大唐移动通信设备有限公司 | Method and device for indicating UE network support characteristics |
| CN102625271A (en) * | 2011-01-26 | 2012-08-01 | 中兴通讯股份有限公司 | Signaling optimization method and system for MTC devices set together |
| CN103313284A (en) * | 2010-06-18 | 2013-09-18 | 电信科学技术研究院 | ISR (Idle State Signaling Reduction) activation/deactivation method and network side equipment |
| CN106028471A (en) * | 2012-09-28 | 2016-10-12 | 英特尔公司 | Persistent bearer for small data transmission in LTE system |
| CN108271230A (en) * | 2018-02-01 | 2018-07-10 | 北京佰才邦技术有限公司 | A kind of method and device for obtaining mobile management information, computer readable storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1671240A (en) * | 2004-03-19 | 2005-09-21 | 华为技术有限公司 | A method for implementing mobile network access limitation |
| EP1841142A1 (en) * | 2006-03-27 | 2007-10-03 | Matsushita Electric Industries Co., Ltd. | Sleep-state and service initiation for mobile terminal |
| CN101043280A (en) * | 2006-06-24 | 2007-09-26 | 华为技术有限公司 | Method and system for positioning user location |
-
2008
- 2008-02-04 CN CN2008100576646A patent/CN101505471B/en active Active
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101998433A (en) * | 2009-08-14 | 2011-03-30 | 大唐移动通信设备有限公司 | Method and device for indicating UE network support characteristics |
| CN103313284A (en) * | 2010-06-18 | 2013-09-18 | 电信科学技术研究院 | ISR (Idle State Signaling Reduction) activation/deactivation method and network side equipment |
| CN103313284B (en) * | 2010-06-18 | 2016-05-18 | 电信科学技术研究院 | A kind of activation/deactivation ISR optimization method and network equipment |
| CN102625271A (en) * | 2011-01-26 | 2012-08-01 | 中兴通讯股份有限公司 | Signaling optimization method and system for MTC devices set together |
| WO2012100674A1 (en) * | 2011-01-26 | 2012-08-02 | 中兴通讯股份有限公司 | A signaling optimization method and system for machine type communication (mtc) devices setting together |
| CN102625271B (en) * | 2011-01-26 | 2016-09-07 | 中兴通讯股份有限公司 | A kind of signaling optimization method and system setting MTC device altogether |
| CN106028471A (en) * | 2012-09-28 | 2016-10-12 | 英特尔公司 | Persistent bearer for small data transmission in LTE system |
| CN106028471B (en) * | 2012-09-28 | 2019-06-18 | 英特尔公司 | Persistent bearer for small data transmission in LTE system |
| CN108271230A (en) * | 2018-02-01 | 2018-07-10 | 北京佰才邦技术有限公司 | A kind of method and device for obtaining mobile management information, computer readable storage medium |
| CN108271230B (en) * | 2018-02-01 | 2021-09-07 | 北京佰才邦技术股份有限公司 | Method and device for acquiring mobile management information and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101505471B (en) | 2011-11-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101415175B (en) | Method and apparatus for processing dual-registration | |
| CN101577955B (en) | Method and system for determining activation of signaling-saving function in idle mode | |
| EP2159972B1 (en) | A method and device for accessing an original network by using a temporary identifier of an evolution network | |
| CN102098655B (en) | Method and system for controlling activation of ISR (Idle mode Signaling Reduction) and UE (user equipment) | |
| US8805392B2 (en) | Method and system for synchronizing user data | |
| CN101521871B (en) | Method, device and system for updating tracking area | |
| CN100488170C (en) | Update method of route trigger area in the packet wireless system | |
| US9155126B2 (en) | Method and device for processing information given idle-mode signaling reduction | |
| CN101127652B (en) | A method, device and system for identifying access anchor of user terminal to external network | |
| CN101610504A (en) | Insert, obtain the method and apparatus of customer equipment context and customer equipment identification | |
| CN101291535A (en) | Method and system for terminal to switch among different networks | |
| CN102083048A (en) | Method and device for processing paging message under idle condition signaling optimized and activated state | |
| CN101505471B (en) | Method and system for implementing context synchronization in idle status signaling optimization process | |
| CN101483850B (en) | Method and system for network access | |
| EP2272269B1 (en) | Context handling upon moving between access networks | |
| CN101553011B (en) | Method for confirming default bearing and mobile management entity | |
| CN102118733A (en) | Method and equipment for processing request of SMSonly function of user equipment | |
| CN102056251B (en) | Network switching method and system and equipment adopting same | |
| CN102761855B (en) | Access, obtain customer equipment context and the method and apparatus of customer equipment identification | |
| CN102740266A (en) | Context synchronization method and system thereof | |
| CN101505474A (en) | Network side processing method in subscriber handover process, network element equipment and network system | |
| CN102638785A (en) | Double-registration processing method and double-registration processing device | |
| CN101400041B (en) | Method, apparatus and system for distributing, obtaining position region identification information | |
| CN101572878B (en) | Method and device for managing the general packet radio service tunneling protocol for control plane (GTP-C) tunnel | |
| CN101448297B (en) | Routing method of combined network elements |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| ASS | Succession or assignment of patent right |
Owner name: INST OF TELECOMMUNICATION SCIENCE AND TECHNOLGOY Free format text: FORMER OWNER: DATANG MOBILE COMMUNICATION EQUIPMENT CO., LTD. Effective date: 20110620 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 100083 NO. 29, XUEYUAN ROAD, HAIDIAN DISTRICT, BEIJING TO: 100191 NO. 40, XUEYUAN ROAD, HAIDIAN DISTRICT, BEIJING |
|
| TA01 | Transfer of patent application right |
Effective date of registration: 20110620 Address after: 100191 Haidian District, Xueyuan Road, No. 40, Applicant after: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY Address before: 100083 Haidian District, Xueyuan Road, No. 29, Applicant before: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd. |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee after: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20210602 Address after: 100085 1st floor, building 1, yard 5, Shangdi East Road, Haidian District, Beijing Patentee after: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd. Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY |