WO2008022593A1 - Method for obtaining contexts of access system - Google Patents

Abstract

A method for obtaining contexts of access system includes the following features: The user equipment UE accesses to the current access system; The information of preceding access system is provided for the current access system, which obtains contexts from the entity of preceding access system according to the information. The present invention can obtain contexts according to the contexts of preceding access system, therefore can effectively avoid unnecessary context obtaining processes, make the context obtaining process simpler and more efficient, and can further promote the spread of SEA network technology.

Description

 Method for obtaining access system context

 The present application claims priority to Chinese Patent Application No. 200610115654.4, the entire disclosure of which is hereby incorporated by reference in its entirety in its entirety in .

Technical field

 The present invention belongs to the field of communication technologies, and in particular, to a method for obtaining a context of an access system.

 In the current third generation partnership project ( Third Generation Partnership .Project ,

In the 3GPP) communication system, each vendor actively researches System Architecture Evolution (SAE) technology and Long Term Evolution (LTE) technology. The purpose of LTE technology is to provide a method for reducing delay and improving users. Several idle speeds, improved system capacity and coverage of low-cost networks. In this technology, only the PS (Packet Switched) domain service is used, and the bearer network is an IP bearer.

 On this basis, many new network architectures have been derived, and a more popular architecture is shown in Figure 1. Referring to Figure 1, in this architecture, the LXE RAN is a radio access network of an evolved network. The nodes in which we do not do "determinate, have eNodeB, and may also have a control plane server (Ccwitro! Plane Server, CPS). Logically It is used as a Long Term Evolution Radio Access Network Entity (JLTE-RAN Entity). In this architecture, in addition to UTE-RAN Entit, it also has Mobility Management Entity (User Plane Entity, MME/UPE). The function of the MME is to save the mobility management (MM) context of the user equipment (User Equipraeot, UE), such as the user's identity, mobility status, Tracking Area (TA) information, etc., and authenticate the user. The UPE functions to: terminate the downlink data for the UE in the idle state, trigger the paging at the same time, and save the context of the UE, such as the IP address and routing information of the UE, etc. User Plane Anchor is the anchor point of the user plane. Whether the MME/UFE is unchanged during the user's session time is not restricted to the following methods

With the in-depth study of the above network architecture, limiting signaling between different Radio Access Technologies (RATs) has become a very important issue. For example, if the UE moves between different RATs (such as a 2G/3G network and an evolved network), the UE may cause the network registration i due to the change of the network it is currently camping on. · The frequent network registration process generates a large number of registrations. Signaling overhead, which greatly wastes air interface resources. Therefore, it is necessary to study how to control the signaling interaction in the process to avoid waste of air interface resources.

 The following is a description of the above-mentioned frequent network registration process by taking FIG. 2 as an example.

 Referring to Figure 2, RAJ and RA2 are the existing 2G/3G routing areas (Routmg Area). The existing 2G/3G UEs must initiate the RCM (Regular Area Update, RAU) process every time the RA is replaced. Even if the UE does not replace the RA, there is a periodic location update process, which is to make the network know whether the UE is still in the network, so as to prevent the UE from leaving the network but the network is not aware and continuously paging the UE. In the present invention, the case where the UE is periodically updated is not considered. Referring again to Figure 2, TAK TA2, TA3 TA4 is the tracking area of the evolved network, and the read tracking area is similar to the 2G/3G RA. When a multimode UE supporting different access networks moves in these areas, if there is no certain The mechanism will result in frequent network registration procedures. For example, when the UE enters RA1 and is stationed in the 2G./3G access system, it will register with the 2G/3G SGSN. When the UE enters TA1 and camps on the LTE access system, In addition, the UE registers with the MME/UPE of the evolved network. When the UE moves out of the TA1 and enters the RA1, it needs to register with the SGSN of the 2G/3G. Through the above registration, the network can page the UE in the RAT. However, The registration signaling overhead of the above registration process is huge.

 In order to solve the problem of huge registration signaling overhead, various inter-RAT restriction signaling schemes have been proposed to avoid such problems. The general idea is that after the UE attaches, it registers with an access network (2G 3G network or evolved network), and then the UE moves to another access network and then registers with another access network, so that the UE simultaneously Registering to both access systems, the UE then moves in the corresponding registration area (RA or TA) of the two networks without initiating any registration procedure. When the UE changes RA or ΊΑ, a normal RAU procedure is initiated. Among them, it should be noted that the two access systems (the SGSN of 2G/3G or the MME of the evolved network) registered have the context of the UE.

 Since both access systems have the context of the UE, which involves the synchronization of the context, the synchronization schemes of the current context are as follows:

 Solution 1, Master and slave (Skills):

In this scheme, the latest context is always maintained on the M.ME, so that the UE does not have to perform cootext interaction when accessing the MME, when the SGSN (Serving GPRS Support Node > Serving GPRS) Support node) When there is eontexl change, need to push context to MME JPE. The disadvantage of this scheme is: When changing cootext in SGSN, it needs to be pushed to ΜΜΕ/ϋ'ΡΕ.

 There is also a method of changing the i4 scheme, that is, the Master-slave + C.RN (Coiitext Reference Number), when the UE is in the access process, when the related context in the access entity ( Generally, the dynamic ccmtexi common to the MME and the SGSN, such as the MM/SM (Session Management) context, changes, the access entity saves the CRN update itself, and synchronizes the CRN to the UE and the MME, and simultaneously synchronizes the changed context. When the UE accesses the SGSN, it needs to carry the CRN saved by the UE. If the CRN sent by the UE matches the CRN saved by the SGSN, the SGSN does not need to extract the context (ie, pu context;), otherwise the SGSN needs to obtain the context from the MME. So proud of this is to prevent the SGSN from having the latest context, but still need to obtain the context from the MME. For example, if the UE accessed the SGSN last time, then it is not necessary to obtain the context from the MME when accessing the SGSN again. CR's method is to ensure that the context is only obtained when necessary (the following method is the same as λ. However, the disadvantage of this method is that when there is a context change in the SGSN, the context is also pushed to the MME/UPE to ensure that the latest is always stored in the MMEAJPE. Context

 Option 2, Coordination plan:

 In the Coordm ion scheme, each time the UE accesses, the MME/SGSN needs to take the context of the other party, because the entity does not know whether the context in the other entity changes.

 The master siave context synchronization method mainly used in the present invention will be described in detail below with reference to the accompanying drawings. The S-TMSI (SAE Teraportar Mobile Subscriber Identit - SAE Temporary Mobile Subscriber Identity) indicates the temporary mobile subscriber identity of the SAE, UT SI (UM' rS TMSL (TMSI or F-TMSI) represents the temporary mobile subscriber identity of the UMTS (Universal Mobile relcommuiiications System), and the S-RA (SAE Routing Area, SAE) represents the RA of the SAE, ie TA. , U-RA means RA of UMTS

 Referring to Figure 3, in the case where the UE first ai1⁄2d] to SAE and then to 2G/3G, context synchronization includes the following steps:

Step 1: The UE attaches to the S.AE, and sends a request message to the MME; Step 32: The MME registers with the H.SS (Home Sixbscnber Server, Home User Server, ); Step 33: The ME obtains from the HSS After the context, the authentication process is initiated to the UE; Step 34: The UE returns an authentication response to the MME.

 Step 35: If the UE passes the authentication and the UE is successfully registered, the MME allocates the S-TMSi/S-RA. and the default IP (default IP) information to the UJE.

 Step 36: After the UE replaces the RAT to the 2G/3G, the RAU process is sent, and the S-TMS1/S-RA allocated by the MME is carried to the UE.

 Step 37: The SGSN sends an SGSN Context Request message to the MME corresponding to the S-TMSI/S-RA to request the cofltexi of the UE; after receiving the ΐΐ request message, the MME sends the relevant context to the SGSN;

 Step 38: Possible recognition process;

 Step 39: The SGSN notifies the MME of its assigned U~TMSI, U-RA and necessary c xt (such as security parameters);

 Step 310: Establish a user plane of the S TSN to the UPE or the iASA (inter Access System Anchor);

 Step 311: Allocating U-TMSI./U-RA and S-TMS1/S-RA to the UE, and the UE does not need to initiate an update registration message when moving between the U-RA and the S-RA;

 Step 312: RA update confirmation

 The association between the SGSN and the MME is established through the above process, that is, the SGSN stores the address information of the S-TMSI/S-RA or the MME allocated by the MME to the UE; the MME also saves the U-TMSi/U- allocated by the SGSN to the UE. Address information of the RA or SGSN,

In the above method, the SGSN obtains all the required contexts from the MME. Therefore, the UE needs to obtain the context required by the SGSN when registering to the MME. For example, if the UE does not access the SGSN at all times, the MM0E stores too much context and occupies the MM0E. Resource _beta

The process of registering the UE to the 2G/3G and then moving to the SAE is as shown in FIG. 4. When the periodic location update or the normal location update is performed in the 2G/3G, the RAU (Routing Area Update) message is sent and carried. U-TMSI/U-RA and S-TMSI7S-RA, because the context synchronization method is master-slave, therefore, even if the last RAT of the UE is 2G/3G, the latest ccmtext is stored in the SGSN, and the SGSN is still to MME / UPE context request, thereby generating an unnecessary synchronization context _¾

Figure 5 shows the data transmission process in the master-skve mode. When the UE accesses the SGSN, The context needs to be requested from the MME, because the latest context is reserved in the MME. When the UE accesses the MME, it is not necessary to request the context from the SGSN. In contrast, the uplink data transmission process of the Coordination scheme shown in FIG. 6 is compared.

 As can be seen from Figure 6, the UE also requests the SGSN to coiitexi when accessing the .ME. That is, the Coordination mode requires the UE to access the SGSN or the MME, and the accessed entity must 驭context to the other party, even if it is accessed last time. The entity is the same as this one, but in fact no need to 驭context: in this case,

 Figure 7 shows the RAU process of the intei: SGSN (between SGSNs) in the Master-skve mode. In this process, the S-TMSI/S-RA parameters are carried in the Context Request message, and the MME is required. Context,

 As can be seen from the above prior art solutions,

 When the context of the SGSN changes, the master-slave scheme needs to push the relevant context to the MME, and the UE needs to obtain the context from the MME when accessing the SGSN, and adopts the Coordinatkm scheme, each time accessing the SGSN or the MME. To get the context from the other party, therefore, in the UE—staying in an access system such as the SGSN, these methods will bring unnecessary process of acquiring the context.

Summary of the invention

 The present invention provides a method for obtaining an access system context, so as to avoid unnecessary context acquisition process when different RAT technologies are used,

 The present invention provides a method for obtaining an access system context, the method comprising:

 When the user equipment accesses the current access system, the UE accesses the last access system information to the current access system, and the current access system obtains the context from the entity that the UE last accessed the system according to the information.

 By adopting the method provided by the present invention, the context can be obtained according to the context in the system that the UE accesses last time, and therefore, the unnecessary context acquisition process can be effectively avoided, thereby making the context acquisition simple and efficient. 3⁄4 is conducive to the rapid promotion of SAE network technology using the description of the drawings

 Figure ί is a schematic diagram of an evolution architecture in the prior art;

 2 is a schematic diagram of a multi-RAT network structure in the prior art;

3 is a flow chart of an implementation of implementing a context in the prior art; 4 is a flow chart of an embodiment of implementing an acquisition context in the prior art;

 FIG. 5 is a flowchart of an embodiment of implementing an acquisition context in the prior art; FIG.

 6 is a flow chart of an embodiment of implementing an acquisition context in the prior art;

 7 is a flow chart of an embodiment of implementing a context in the prior art;

 Figure 8 is a flowchart of Embodiment 1 of the present invention;

 9 is a flowchart of Embodiment 2 of the present invention;

 10 is a flowchart of Embodiment 3 of the present invention;

 11 is a flowchart of Embodiment 4 of the present invention;

 12 is a flowchart of Embodiment 5 of the present invention;

 Figure 13 is a flow chart of a sixth embodiment of the present invention;

 Figure 14 is a flowchart of Embodiment 7 of the present invention;

 Figure 15 is a flow chart of an eighth embodiment of the present invention;

 16 is a flowchart of Embodiment 9 of the present invention.

detailed description

 In the present invention, since the system accessed by the UE last time must have the latest context (because the UE is accessed, if the context of the entity is not up-to-date, the context operation is to be performed), then the UE can access the last time. The information is brought to the network, and the network obtains the context from the last accessed entity according to the information, so that the captured context is the latest. In addition, in the present invention, according to different types of information accessed last time. , using different methods to get ccmtexL

 The present invention will be described in detail below in conjunction with specific embodiments.

In the embodiment of the present invention, the context is subdivided and decomposed into a static part and a dynamic part. The static part is a context obtained by the SGSN or the MME from the HSS during the attach process, for example, Forwarding information: ListC sends 'information' Column-table), SGSN CAMEL Subscription Info, etc., the dynamic part is the context generated by the static part SGSN or MME according to the UE action, such as MM context! such as RAl), SM context (such as PDF Address, ie grouping) The protocol part is divided into static { SGSN, MME Common) (the unit is ST{S, M, C}), and the dynamic part is also divided into dy amic { SGSN, MME, Common} {S,M, C} ), respectively representing the static part Z or the SGSN-specific context in the dynamic part, the MME-specific coniexi, and the public part. Generally, the static part is obtained through the HSS. Reconstruction or transfer between entities (occurring in SGSlNi/MME changes), the dynamic part is obtained through the context synchronization method (the previously described master-slave and other methods).

 In the present invention,

 ST can be obtained from the HSS reconstruction process, that is, the change of the new entity (SG SN or MME:) must be registered to: HSS, and then take ST information from the HSS, such as ST{C:, S} or ST{ C, M}. In order to keep the context at least, only ST(C, S) and DY{C, S) are reserved in the SGSN, and only ST {C , M} and DY {C , M) are reserved in the MME.

 In the present invention, the so-called context synchronization between the MME and the SGSN is only synchronous D Y (C). The original park is that only this part can be converted between the MME and the SGSN and the SGSN is changed. The new SGSN C new SGSN ) also takes the DY S} from the original SGSN (old S xSN ). Similarly, the new MME ( New MME ) To get DY{M) to the original MME (old MME).

 The process of obtaining a context in the method of the present invention is described in detail below in combination with different specific situations (taking the Coordination synchronization method as an example):

 First, the UE is first attached to the MME.:

 The dynamic context required by the MME is obtained from the HSS in the HSS reconstruction process, that is, the HSS generates ST{C and is sent to the MME; the MME generates DY{M:, C}; then, the MME retains ST C, M:} and: DY (M, C

 2. The UE attaches to the MME first, then moves to the SGSN.

As shown in Figure 8, the SGSN obtains DY{C } from the MME, ST{S, C} _t from the HSS, and DY {S} from the SGSN. The reserved context is: ST{S, C}, DY{S, C }, the latest: DY C} in SGSM: The specific process of this situation is:

 Step 800: The UE was originally attached to the SAE and currently enters the 2G/3G network;

 Step 801: The UE sends a routing update (R.A Update) request to the SGSN in the 2G/3G network, where the request carries the S-TMSI and the S-RA identifier allocated by the last accessed SAE system for the UE;

The S-TMSI indicates the temporary mobile subscriber identity of the SAE, the U-TMSI indicates the temporary mobile subscriber identity of the UMTS, the S-RA indicates the RA of the SAE, that is, the TA, and the U-RA indicates the RA of the UMTS; Step 802 to Step 803 : The SGSN determines the old MME that the UE last accessed according to the S-TMSi and the S-RA, and sends an SGSN context request to the old MME. After receiving the message, the MME returns the DY{C} through the SGSN context response message to implement synchronization between the SGSN and the MME.

 Step 804: The authentication process is completed by using an authentication (Auth.) message between the SGSN and the UE.

 Step 805: The SGSN returns an SGSN context acknowledgment (ACK) message to the o!d MME to confirm that the DY (C} has been correctly synchronized. Then, the SGSN establishes an association with the MME. The execution sequence of step 805 and step 804 is not Affecting the implementation of the present invention;

 Step 806: The SGSN sends a location update (Uixhate Locatkm) message to the HSS to notify the HSS that the current UE has changed its location;

 Step 807 to step 80S: The HSS sends a Cancel location message to the old SGSN, and the HSS sends the STfCSj of the i UE to the SGSN through the Insert Subscriber data message;

 Step 809: The SGSN confirms to the HSS that the current location update is successful.

 Step 806 809 is only changed in the SGSN, that is, when the UE moves to an SGSN that has not been registered, if the UE is currently moving to the SGSN that has been registered last time, step 806 809 may not be performed;

 Step 810: The SGSN allocates a new U-TMSI, U-RA to the UE, and sends the U-TMSK U-RA to the UE. In this step, the original S-TMSI/RA may also be sent to the UE in one step. In the embodiment of the present invention, if the network cannot distinguish between the S-TMSI and the U-TMSI, the step 80] may further carry the RAT type identifier, and indicate the last accessed network by the identifier, in this embodiment, that is, It is indicated that the last accessed network is the SAE, and the SGSN can send the context request message to the MMIE in the SAE according to the far RAT type identifier, and the invention can also be implemented;

 In addition, in the embodiment of the present invention, the CRN C Context Reference Number (Context Reference Number) may be further carried in the RA Update message of step 801, so as to further complete the acquisition of the context by using the CRN, the CRN is used as follows:

Step: The UE accesses the MME or the SGSN, and after updating the context, does not push the context, such as the ccmtext of the access entity (MME or SGSN) changes, updates the CRN (such as CRN CRN+) saved by the entity itself; CRN is a loop Value, reset to the lowest value when the highest value is reached) and send the updated CRN to the UE (in real time or when the connection is released); Step 2: The UE accesses an entity, and sends the CRN to the entity. If the UE-CI3⁄4 reads the entity's CRN (Entity^CRN), it indicates that the entity retains the latest cootexi of the UE (--refers to DY{C) ), you do not need to get the context from other entities (--refers to DY{C}). Otherwise, you may need to obtain the context from other entities, access the entity and update your own CRN=UE ..CR>L and return to step 1.

 Among them, you need to pay attention to: When the security-related context changes, you must push the context to the other party.

 The above process can further simplify the process of obtaining the context: Determine whether the context needs to be obtained according to the value of the CRN, so as to avoid unnecessary process of obtaining the context.

 3. The UE moves from the previous access network to the MME. In this case, the MME to which the UE moves is the MME that the UE has already registered:

 If the MME is the last access to the MME, the identifier carried in the RA Update sent by the UE is the access entity itself, and the entity does not take the context from the SGSN and the HSS. The read scheme is relative to the existing Coordination mode. , saving the process of taking the context;

If the last access of the UE is 2G/3G, the UE sends the read information to the network (for example, sending the identifier of the 2G/3G assigned U-TMSi/U-RA, or sending all the identifiers to the network, but indicating the last connection The incoming network is 2G/3G) „MME takes DY (C} to SGSN, MME's context is DY (C _; M), ST{C,M}; The latest: DY〖C} is in MME,

 The method of combining the master-Slave or the combination mode with the CRN, for example, if the CRN sent by the UE matches the CRN saved by the MME, the context is not required, thereby saving the context step; for example, the UE accessing the MME obtains the latest context, the UE If the SGSN is accessed again, but the context is not changed, the MME is accessed again. The method of using the CRN does not need to 驭context from the SGSN.

 If the UE accesses the 2G/3G last time, as shown in Figure 9, the specific process of obtaining the context includes:

 Step 900: The UE accesses the 2G/3G network last time, and accesses the SAE network this time, and then moves to the MME;

 Step 01: The UE sends an R A Update message to the MME, where:

Only the identifier assigned by the last accessed entity SGSN to the UE is carried in the message. UT SI/U-RA , or,

 Only the identifier of the current access assignment, ie S-TMSI/S-RA, is carried in the message, so that in the subsequent step, the MME is from the saved context (if the MME is a new access entity, the new .ME is from the old The MME obtains the SGSN corresponding to the associated SGSN address information in the eotitext, so as to retrieve the coiitext from the SGSN, or

 Carry all of these identifiers in the message.

 The message may also carry the type of the last accessed entity (ie, type), etc., which can indicate the type of the last access entity, so as to assist the MME in finding the SGSN in a subsequent step (if the access entity cannot distinguish The identifier assigned by the UMTS to the UE and the identifier assigned by the SAE. The following description uses the RAT type as the information for distinguishing the access type;

 Step 902 to step 903: The MME determines the corresponding SGSN according to the content of the RA Update in step 901, and sends an SGSN context request message to the SGSN; the SGSN returns the DY {C) to the MME through the SGSN context response message. , thereby implementing synchronization of DY {C}; Step 904: The authentication process is completed by the MME and the UE through an authentication message interaction;

 Step 905: The MME sends an SGSN context ACK message to the SGSN, confirming that the context synchronization is successful.

 Step 906: The MME allocates a new S-TMSI, S-RA to the UE, and sends the S-TMSI and the S-RA to the UE. In this step, the ME may further send the original U-TMSI/RA to the UE. , does not affect the implementation of this.

 Similarly, in this case, the CRN may be further carried in the RA Update message of step 901, so that the CRN' is used to complete the acquisition of the context, and the CRN is used to complete the manner of the embodiment of the present invention and the CRN that has been described above. The same way of use.

As shown in FIG. 9, the UE carries the U-TMS:/U-RA allocated by the last accessed entity SGSN to the MME, and the MME takes the coirtex from the SGSN according to the identifier, and may also carry the class of the last accessed entity to assist. The MME finds the SGSN (if the access entity cannot distinguish between the identifier assigned by the UMTS to the UE and the identifier assigned by the SAJE), or the UIE carries the identifier S-TMS1/S-RA assigned by the access RAT, and the MME corresponds to the associated SGSN from the saved context. The corresponding SGSN is found in the address information, and the context is obtained from the SGSN. Or, the UE carries the identifiers, and the UE may also carry the CRN. If the CRN carried by the UE matches the CRN saved by the MME, it is not necessary to take ccmtexl from the SGSN. - Γ! - This step 骡 902, 903, 905 is a dotted line)

 4. The UE moves to the SGSISi, where, in this case, the SGSN to which the UE moves is the SGSN that the UE has registered:

 If the last access to the SGSN is SGSN, then it is not necessary to take context*. If the MME was last accessed, its execution mode is similar to the flowchart shown in Figure 9, except that the SGSN and MME are exchanged.

 5. The UE moves to the new SGSN, where the new SGSN refers to: the UE moves to an SGSN that has not been registered last time;

 In the case of reading, it can be divided into two sub-cases:

 Sub-case one:

 If the entity that was last accessed is the SGSN: new SGSN takes DY{C,S) from the dd SGSN, and ST{C, S} from the HSS: establishes association with the MME, see Figure 0, and obtains the context under the circumstance The process can be; f is included as:

For example, the last access to this access is still: G 3G but changed to an SGSN, then new SGS takes the context DY{C, S} to the old SGSN, and then the new SGSN registers the request with the HSS ST{ The context of C, S} is finally associated with the MME (the MME address information is learned from the context retrieved by the SGSN, or the iib information of the MME is obtained by the S-TMSI/S-RA carried by the UE) _;

 The functions of the steps in the specific implementation of FIG. 10 are the same as or similar to those of the corresponding steps in FIG. 8 and FIG. 9, and specifically include:

 Step 1000: The UE accesses the 2G/3G network last time, and moves to the new SGSN.

 Step 1001: The UE sends an RA Update message to the new SGSN, where:

 In the message, only the last accessed entity SGSN is the assigned identifier U-TMSI/U-RA, so as to obtain the context from the last access entity, and further understand the other party RAT entity address information according to the context; Or,

 In the message, the current access RAT is only the assigned identifier, U-TMSIZU-R A, so that in a subsequent step, the new SGSN can obtain the context from the oid SGSN according to the identifier, so as to further understand the MME address information; Or,

 Carry all of these identifiers in the message.

Or, in the 璲 message, the type RA1 of the last accessed entity is also carried, so as to be followed by Step to assist w SGSN to find the last accessed entity

 Step 1002: The new SGSN sends an SGSN coiitext request message to the oki SGSN according to the relevant identifier carried in the A Update, requesting to obtain the context;

 Step 1003: The old SGSN returns the dynamic context DY{C, S} to the new SGSN through the SGSN context response message;

 Step 1004: The new SGSN performs an authentication message interaction with the IJE to complete the authentication process. Step 1005: The new SGSN returns an SGSN context AC message to the old SGSN to confirm that the context update is successful.

 Step 1006: Because the UE moves to the SGSN, the location update process is triggered, and an Update Location message is sent to the HSS.

 Step 1007: The HSS sends a cancel location message to the old SGSN. Step 1008: The HSS performs message interaction with the new SGSN, and the static context ST{C, S} of the UE passes the Insert subscriber data message. Sending to the new SGSN; Step 1009: The new SGSN performs a message exchange with the HSS to inform the HSS that the location update is successful; Step 1010: The new SGSN performs an Associaiicra setup association with the MME to establish a message interaction, and establishes an association between the MME and the new SGSN;

 Step 10: The new SGSN allocates a new U-TMSI, U-RA to the UE, and sends the U-TMSL U-RA to the UE. In this step, the new SGSN may further convert the original S-TMSI/RA. Sending to the UE does not affect the implementation of the present invention:

 Similarly, the CRN may be further carried in the RA Update message of the step 1001, so that the CRN is used to complete the eomexi acquisition, and the manner in which the embodiment of the present invention is implemented by using the CRN is the same as the CRN used in the foregoing.

 Similarly, in the case of the case, the identifier carried in the RA Update message may also include the identifier allocated by the RAJ for the current access to the UE, and the identifier of the last accessed RAT for the UE, indicating that the last access is The identifier of the type of the RAT, or all three of them, where:

If the U-only carries the identifier assigned by the access RAT to the UE, as shown in FIG. 10, the UE carries the U-TMS/J-RA identifier to the network, and obtains the coMexL from the o SGSN according to the identifier. If the UE only carries the identifier assigned by the last accessed RAT to the UE, the UE also carries the U-TMSI/U-RA to the network (because the last access is 2G/3G λ) Sub-case 2:

 For example, the last entity accessed is MME: new SGSN gets DY (C} from MME, new SGS gets DY{S} from d SGSN; since SGSN is the last unregistered SGSN, new SGSN needs to The HSS obtains ST "C, S}. The flow is shown in Figure 1!, wherein the function of the specific message in each step is the same as or similar to the function of the corresponding step in Figure 8 and Figure 9, including:

 Step 1] 00: The UE accesses the S.AE network last time, and this time moves to the new new SGSN;

 Step 1] (H: The UE sends an R A Update message to the new SGSN, where:

 In this embodiment, the RA Update message carries only the identifier of the current access RAT, and the subsequent steps are implemented as follows: The UE accesses the new SGSN, and the new SGSN finds that it has no context of the UE, according to the RA Update message. The carried U-TMS [obtain the oM SGSN address, send a context request to the oM SGSN, request to obtain DY(S}, then register with the HSS, obtain ST{C, S}. Learn about the MME from the context of the 荻-fetch The address information or the S~TMSi/S~RA sent by the UE is used to learn the address information of the MME, and obtain the latest DY{C}; the specific implementation of the process will be described in detail later;

 Step 102: After receiving the RA Update message, the new SGSN finds that it does not have the context of the UE, and then extracts the old SGSN address according to the U-TMSi carried in the RA Update message, and sends an SG SN context request message to the oW SGSN to request acquisition. DY (S) ;

 Step i 103: The old SGSN returns the DY{S to the new SGSN through the SGSN context respons message;

 Step 1104: The new SGSN performs an authentication message exchange with the UE to complete the authentication process. Step 1.05: The new SGSN returns an SGSN context ACK message to the dd SGSN to confirm that the context update is successful.

 Step 106: Since the UE moves to the new SGSN, the location update process is triggered, and an Update Location message is sent to the HSS.

 Steps 107 to 1109 are the same as steps 007 to 1009 described above, and are not described in detail herein;

Step Π Ο: Since the UE last accesses the SAE, the new SGSN learns the MME address information from the obtained context, and sends an SGSN context request message to the MME to request the context; the MME will update the DY C. Returned to the SGSN context response message New SGSN:

 Step illl: new SGSN allocates a new U-TMS1, U-RA to the UE, and sends the U-TMSI, U-RA to the UE; the new SGSN establishes an association with the MME; in the read step, the new SGSN can further The original S-TMS1/RA is sent to the UE without affecting the implementation of the present invention.

 In other embodiments of the present invention, the RA Update of the step 101 may carry other identifiers, and the identifiers carried by the roots are different, and the subsequent steps are correspondingly changed, and the identifiers carried in combination with the different identifiers are different. A general description of the specific implementation obtained:

 If the RA Update message carries only the identifier S-TMSI/S-RA assigned by the last accessed RAT (ie, SAE), the flow shown in Figure H corresponds to: S-TMSi/ sent by the new SGSN through the UE. The S-RA first obtains the context of the MME, such as DY{C〗, and obtains the address information of the old SGSN from the obtained context, obtains the DY{S) from the old SGSN, and obtains the SI^C through the process of registering to the HSS. , S}„

 It can even be:

 If the RA Update message carries only the identifier U~TMS1 U~RA assigned by the currently accessed RAT (ie 2G/3G), the new SGSN sends a context request to the dd SGSN according to the identifier, and then the old SGSN obtains the context request from the MME again. After context DY{C}, send the latest context DY{C,S} to new SGSN.

 Or, if the RA Update message carries only the identifier S-TMSi/S-RA assigned by the last accessed RAT (ie, SAE), the new SGS sends a context request to the MME, and then the MME takes the DY from the od SGSN. S}, send the latest context DY{C,S} to the new SGSN,

 Similar to the manner already described above, the present invention can also be implemented in combination with CR, specifically:

If the accessed entity does not have a context, directly compares the CRN from dd SGS 驭eoDtext, if the subscription (such as the CRN sent by the UIE is the same as the CRN saved by the access entity), it is not necessary to take the context to the MME, only the association is established; or the CRN is Send it to the old SGSN. If the CRN matches the CRN in the old SGSN, send DY { S, C} to the new SGSN. Otherwise, only DY {S} is sent. After the new SGSN is received, it is decided whether to send the CMccmtexi again to the MME. :; or send the CRN to the old SGSN, if the CRN matches, send DY{S, C} to the new SGSN, otherwise the oid SGSN takes DY (C} from the MME, and then sends DY (C, S) to new SGSN. The UE moves to new MME:

 For example, if the last entity accessed is the SGSN, the ne MME takes DY (C} from the SGSN; then takes the DY{M from the old MME; and takes ST{M,C} from the HSS.

If the last accessed entity is the MME, the new MME takes the following from the old MME: DY{C ₅ M; , obtains ST(M , C} > from the HSS and establishes an association with the old SGSN.

 These two cases are similar to the techniques described in the corresponding drawings in the case where the UE moves to the new SGSN, and it is only necessary to exchange the corresponding content of the 2G 3G system with the corresponding content of the SAE system.

 7. The UE first attaches to the SGSN:

 In this case, the UE first attaches to the SGSN, the SGSN registers with the HSS, the SGSN obtains ST{C, S} from the HSS, and the SGSN itself generates DY {C, S}.

 8. The UE first attaches to SGSM and then moves to the MME:

 The UE sends the last access identifier, that is, U~TMSI/U-RA to the MME, and the MM:E obtains the latest context from the SGSN according to the ϋ identifier: DY{C}, and the MME re-registers with the HSS, and obtains the ST from the HSS. C, M}, MME generates its own ST{M:}, and finally the saved context is: ST{M, C}, DY {C, M} where DY {C} changes, then MM:E The saved DY {C) is the latest one, and the implementation of the present invention in this case is similar to the implementation of the present invention in the second case described above, except that the corresponding content of the 2G/3G system and the SAE system are Corresponding content exchange.

 Or, the UE itself is to send the identifier of the current access, but it is not yet registered to the SAE, so the assigned identifier is still sent, that is, U-T3VJSI U-RA,

 The UE may carry the identity of the current access, that is, the S-TMSI/S-RA. If the MME is different from the MME when the UE detaches (de-attach), the MME obtains the 1MS1 of the UE from the old MME, and then registers with the HSS. Obtain the address information that the UE has registered to the SGSN from the context obtained by the HSS, and λΚ^ SGSN obtains the context, :

In the implementation as described above, the description SGSN only retains ST{C, S}, DY{C, S} > MME only retains the scenes of ST "C, M}, DY {C _? M}, and considers that the save mode is Preferably, since it is possible that the UE does not enter another access technology after registering to one access technology, it is not necessary to retain the unnecessary context. However, considering that the UE may access multiple entities when accessing an entity In the case where the entity takes the context, if the UE accesses an entity and obtains all DYs, then there will be no case where the cemtext is taken from both the SGSN and the MME. If the UE accesses the MME, the last time the SGSN was accessed, then SGSN it will DYiC, S} are sent to MME UE then this new SGSN will not have access to the Old SGSN context taken _β

 The specific implementation of the present invention will be separately described below in conjunction with various scenarios including, for example, the above-described preservation of all contexts.

 (―), the UE first accesses ΜΜΕ, then accesses the new SGSN, and the entity retains all dynamic contexts (DY{all}), as shown in Figure 12, specifically including the following steps:

 Step 1200: The UE accesses the MME of the SAE network last time, and moves to the new SGSN. Step 1201: The UE sends an RA Update (Routing Area Update) message to the new SGSN, where the UE carries the message The manner of identification may be in a manner similar to the embodiment described above;

 Step 1202: After receiving the RA Update message, the new SGSN sends an SGSN context request message to the MME according to the identifier carried in the RA Update message. Since all dynamic contexts are saved on the MME, the implementation is compared with FIG. In the example, the new SG SN does not need to request DY{S} from the od SG SN;

 Step 1203: The MME returns DY{C, S, M} to the new SGSN by using an SGSN context response message.

 Step 1204: The new SGSN performs an authentication message interaction with the UE to complete the authentication process. Step 1205: The new SGS returns an SGSN context ACK message to the MME, confirming that the context update is successful; the new SGSN is associated with the MME;

 Step 206 to step 1209 is the same as step genre to step 1109;

 Step: 1210 is the same as step 111.

 In the scheme described in FIG. 2, the UE first accesses the MME and then accesses the new SGSN, and then takes context DY {all } to the MME, and also takes DY {M} for re-accessing the new MME in the UE. At that time, it is only necessary to obtain the context from the SGSN, thereby avoiding obtaining the co.rtiexL from both the o dj MME and the SGSN.

 The embodiment is only for the description of the specific implementation of the present invention in the case that the UE first accesses the MME and then accesses the new SGS. Similarly, for the eight cases that have been described above, the embodiment may be separately adopted. Implemented in a similar way.

(2) The above is that the SGSN and the MME obtain the ST from the HSS, and the SGSN and the MME may also Obtained from the last accessed entity or o d SGS or MME

In the case that the SGSN or the MME takes the ST from other entities (non-HSS), the SGSN and the MME may retain all the eratexts, that is, ST{all}, DY{aM), or may only save their own related contexi, such as the SGSN to save the ST { C> S} , DY{C, S}; MME saves ST{C, M], DY{C, M}. Or, the SGSN retains its own context, that is, ST{C, S}, DY{C, S}; and the MME retains all the coMexts. The scenario is that the application is not registered with the HSS after the replacement of the SGSN, and only the last accessed entity驭Context, and replacing the MME requires registration with _HSS3⁄4

 When the SGSN or MME retains all coMexts, when the UE accesses the SGSN, if the SGSN is accessed last time, the new SGSN takes ST{al) from the old SGSN, and DYia l}, 3⁄4 no need to obtain the ST from the HSS. (C, S); new SGSN is then associated with the MME. In addition, the reason for taking contextfall} is to let the UE move to the nmv MME again, and can directly send and send the MME-related context from the SGSN to the new MME. :

 When the UE accesses the MME last time, the new SGSN takes context {a} from the MME to establish an association with the MME, and the old SGSN context is deleted by the HSS or the MME (the present invention does not limit the deletion of the context). The process is shown in Figure 13:

 See Figure 〖3, which includes the following steps:

 Step 1300: The UE accesses the MME of the SAE network last time, and moves to the new SGSN. Step 1301: The UE sends an RA Updat message to the new SGSN, where the manner of carrying the identifier in the message may be adopted in the foregoing embodiment. a similar way;

 Step 1302: After receiving the RA Update message, the new SGSN sends an SGSN context request message to the MM.E according to the identifier carried in the RA Update message. Since all dynamic and static contexts are saved on the MME, therefore, compared with FIG. 11 And FIG. 12, in this embodiment, the new SGSN does not need to obtain the DY(S) from the old SGSN, and does not need to acquire the ST(C, S) from the HSS;

 Step 1303: The MME returns its saved DY {C, S, M} and ST (C, S, M) to the new SGSN through the SGSN context response message;

 Step 1304: The new SGSN performs an authentication message exchange with the UE to complete the authentication process. Step 1305: The new SGSN returns an SGSN context AC message to the MME, confirming that the context update is successful; the new SGSN is associated with the MME;

Step 306: The MME sends a Caned Location message to the old SGSN; Step 1307: The new SGS allocates a new U-TMS and U-RA to the UE, and sends the U-TMSI and the U-RA to the UE. In this step, the new SGSN may further convert the original S-'IMSI. The /RA is sent to the UE without affecting the implementation of the present invention.

 As shown in Figure 13, the new SGSN no longer needs to obtain static contexi from the HSS and obtain it directly from the MME. In addition, since the new SGSN obtains DY{all) and ST{aJ1} from the MME in step 3303, it is possible to enable the UE to obtain the corresponding context only from the SGSN when re-accessing from the SAE to the new SAE. There is no need to retrieve context from the old MME.

 Alternatively, the newly accessed entity obtains all dynamic conte t from the last accessed entity, and obtains static eoiitext from the HSS (if the new access entity changes, otherwise no static context λ is required to be taken to the HSS)

 Another example is that the SGSN and the MME reserve their own context and do not take a static context from the HSS. With the above process, the UE first accesses the MME and then accesses the new SGSN. 4. The method includes the following steps: Step 1400: The UE accesses the MME of the SAE network last time, and moves to the new SGSN. Step 1401: The UE sends an RA Update message to the new SGSN, and the manner in which the identifier is carried in the ΐϊ message may be adopted as above. The manner in which the embodiments are described;

 Step 1402: After receiving the R A Update message, the new SGSN learns that the MME is the entity that the UE accessed last time, and sends an SGSN context request message to the MME according to the identifier carried in the RA Update message.

 Step 1403: The MME returns DY{C} and ST{C} to the new SGSN by using an SGSN context response message.

 Step 404: The new SGSN performs an authentication message interaction with the UE to complete the authentication process. Step 405: The new SGSN returns an SGSN context ACK message to the MME, confirming that the context update is successful; new SGS establishes association with the MME;

 Step 406: The new SGSN determines the address of the dd SGSN according to the identifier carried in the RA Update message in step 1401, and sends an SGSN context request message to the SGSN to request the context (ST S and DY{S) related to the SGSN. ; Because the SGSN has its own context, it is no longer necessary to obtain it from the HSS.

Step 1407: old SGS returns DY{S} and ST{S} to the new SGSN through the SGSN context response message; Step 1408: The new SGSN returns an SGSN context ACK message to the old SGSN to confirm that the context update is successful. In the embodiment of the present invention, the process of deleting the ecmtexi by the old SGS may be further triggered, which does not affect the implementation of the present invention;

 Step 1409: The ew SGSN allocates a new U-TMS1, U-RA to the UE, and sends the U-TMSI and the U-RA to the UE. In the read step IT, the new SGSN may further convert the original S-TMS!/RA. send to

 As shown in Figure 14, if the SGSN or MME saves its own context, DY(S} and ST{S) cannot be obtained when the context is obtained from the MME. It can only be obtained from the old SGSN. The above process can also be obtained from the old SGSN.驭ST{S, C} without obtaining ST{C} from the MME.

 The foregoing embodiment is only for the description of the specific implementation of the present invention in the case that the UE first accesses the MME and then accesses the new SGSN. Similarly, for the eight cases that have been described above, the embodiment may also be separately adopted. In a similar way to achieve „

 In addition, the parameters of the UE access in the above process may be S-TMSI/S-RA and/or U-TMSI/U-RA. In fact, the UE may carry all the identifiers; or, the IIE only carries the last accessed entity. If the last access of the UE is SAE, the current access carries the S-TM:Si/S-RA, and the context is taken by the entity that accesses the network. Alternatively, the UE can carry only the current access. The identifier of the entity allocation, such that the behavior of the dual-mode UE is the same as that of the single-mode. Only when the UE has not registered to an access system, other identifiers can be carried. As shown in FIG. 15, the ST Context (Static, Static Context) is from HSS acquisition, each entity retains the minimum omtexi, including the following steps:

 Step 1500~Step 1503: The UE is powered on and registered to the 2G/3G network;

 UE mobility, access to SAE from 2G/3G network;

 Step 504: The UE sends a Routing Area Update (RAU) message to the MMIE. Since the current UE has only accessed the 2G 3G network and has not accessed the SAE, the message carries the identifier U- that has been allocated to the UE. TMSi/U-RA;

 Step 505: The MME determines the address of the old SGS according to the U-TMSI/U-RA carried in the routing update message, and sends an SGSN context request message to the old SGSN to request the relevant context.

Step 1506: The old SGSN returns the DY{C} to the MME through the SGSN context response message; Step 1507: The MME obtains the corresponding ST (C, M) from the HSS;

 The UE then moves to the 2G/3G network and accesses the SGSN;

 Step 1508: The UE sends an RA Update message to the new SGSN, where the message carries the identifier U-TMSI, IJ-RA that the system has assigned to the UE.

 Step 1509: The new SGS sends an SGSN fine text reqoesi message to the old SGSN, requesting to obtain a corresponding context;

 Step 1510: The old SGSN returns the address information of the DY{Sj and the MME to the new SGSN through the SGSN context response message.

 Step 15H: The oew SGSN sends an SGSN context request message to the MME, requesting the corresponding context;

 Step 15] 2: The MME returns the DY{C} to the new SGSN through the SGSN context response message (because the last accessed entity is the MME, DY (the Q is the latest at the MME); the new SGSN is associated with the MME;

 Step 15: The new SGSN performs authentication message interaction with the UE to complete the authentication process. Step 1514: The HSS generates ST{C, S}, and sends the STiC, S} to the new by interacting with the Register SGSN message of the new SGSN. SGSN; In the embodiment of the present invention, the oki SGSN may be further triggered to delete the context;

 Step 1515: The new SGS allocates a new U-TMSL U-A to the UE, and sends the U»TMSI > U-RA to the UE. In this step, the new SGSN can further send the original S-TMSI/RA I For the UE, does not affect the implementation of the present invention

 As shown in FIG. 15, the UE accesses the RAU from the attach. When the UE does not assign the corresponding identifier, the UE access carries the assigned identifier. Otherwise, the UE accesses the identifier assigned by the system that carries the access.

 If the UE only carries the identifier of the system that was last accessed, then in the above steps 1508-1514, the new SGS first obtains the address information of the MME by using the identifier carried in the RA Update message, and obtains the context from the MME according to the address information. And get the address information of the old SGSN, and then get DY{S} to the SGSN.

In fact, the UE may also carry the identifier allocated by the access system in the access, as in the above step 504, the UE may carry the SAE assigned identifier (old S-TMS1/S-RA) to access the SAE. The system then registers the MME with the HSS, obtains the SGSN address that the UE has registered from the HSS, and obtains the DY C} from the SGSN. As shown in Figure 16, the following steps are specifically included:

 Step 1600~step according to 1603 is the same as step 1500~step 飨503 above;

 UE mobility, access to SAE from 2G/3G network;

 Step 1604: In this embodiment, the UE always carries the identifier allocated by the local system in the access, and therefore, in the step, the IJE carries the identifier allocated by the SAE, and the SMESI-S-RA accesses the SAE system. Specifically, the UE sends a Routing Area Update (RAU) message to the MME, where the message carries the identifier oM S-TMSi/S-RA allocated by the S. AE network that the UE originally accesses to the UE. The premise that the bearer carries the read old S-TMSI/S-RA is that the UE has the SAE parameter saved in the detach state, and the subsequent steps described in this embodiment are all performed for the MME to change;

 Step 1605a: The oew MME sends a Mentiilcatio Request message to the old MME identified by the old S-TMSI/S-RA, and requests the UE's International Mobile Identity (IMSI) from the old MME.

 Step 1605b: The old MME finds the message corresponding to the UE according to the old S-TMSI, and sends the IMSI to the new MME.

 Step 1606a: The read MME finds the HSS where the UE is located according to the leg ί of the UE, and sends a registration message.

 Step 1606b: The HSS sends the ST{C, M} of the UE and the address information registered by the UE to the new MME.

 Step 1607a: The new MME sends a context request message to the oM SGSN according to the address information of the SGSN registered by the UE.

 Step 1607b: old SGS returns to the new MME 3⁄4 context C DY{C) );

 The UE then moves to the 2G/3G network and accesses the SGSN;

 The dance 608 and the step 1615 are the same as the above steps 1508 to 1515, and the description will not be repeated here.

The method can also be applied to another scenario. In this scenario, after the UE registers with the SAE, the ME registers with the HSS>SGSN to treat the MME as an HSS, and can obtain a static context from the MME (ie, the HSS only registers the MME, the SGSN). Registered to the MME, the UE can register to the MME and the SGSN λ. If the UE accesses the SAE last time, then accesses the 2G/3G, if the accessed node is already registered. SGSISU SGS gets DYfC from MME _? Does not get context from other nodes. If the last access to SAE, then access 2G/3G, if the access node is unregistered SGSN, then new SGSN gets DY from MME {C}, ST{C _; S} (use MME as HSS), get DY{S〗 from old SGSN, and do not take ccmtext to HSS. The post MME is associated with the new SGSN.

 If you access SAE last time, this time you access the new MME node, then! The ww MME obtains DY(C, M}, STIC, S} from the dd MME > obtains ST{M} from the HSS, or obtains all contexts from the old MME. The new MME then associates with the SGSN.

 If the last access to 2G/3G, and then access to the SAE, the accessed MME node is the registered MME, the MME obtains DY{C} from the SGSN, and does not obtain the context from other nodes.

 If the last access to 2G/3G, and then access to the SAE, the accessed MME node is an unregistered MME, the new MME obtains DY (C) from the SGSN, and obtains DY{M}, ST S} from the od MME or ST C, S}, from HSS荻 - take ST (M} or ST (C, M} or all static context. The new MME is then associated with the SGSN.

 If the new SGSN node is accessed after the last access to the 2G/3G, the new SGSN obtains the DY C, S} from the old SGSN, and acquires the ST{C, S} from the MME, and the new SGSN establishes an association with the MME.

 In the above embodiments, it is possible to determine whether the DYiC} is up-to-date according to the CRN to determine whether to obtain the context from other entities. In some cases, such as the user subscription data, the network change mode is changed. Etc., the HSS may need to actively modify the context of the ME and/or the SGSN. In this case, because the HSS records the location information of the two entities of the SGSN and the MME, for example, the HSS actively modifies the data of the UE (it may be considered that the data belongs to Static context), then the two entities are directly sent to modify, and the CRN does not need to be changed, and the UE is not required to be notified. The two entities maintain their respective static contexts.

 In addition, the present invention can also be applied to single registration, that is, after the signaling is activated, the UE is restricted to register in two.

In the RAT entity, but only one RAJ entity (the entity that the UE newly accesses) is registered in the HSS, and another _RAT entity is registered in the entity.

 After the UE registers with the SAE, the ME registers with the HSS, and the SGSN uses the MMIE as its virtual HSS, and the SGSN registers only with the MME; in this case, the method is:

If the last access system is SAE, and the current access system is and the accessed node is a registered SGSN, the method is: The SGSN obtains 驭 〖〖C} from the MME, and does not obtain the context from other nodes;

 If the last access system of the UE is SAE, the current access system is 2G/3G, and the accessed node is an unregistered SGSN, the method is:

The ew SGSN acquires DY "C}, ST{C _; S} from the MME as the virtual HSS, acquires DY{S} from the old SGSN, and does not associate with the HSS, and then the MME associates with the new SGSN; or, ∞ w SGSN acquires all contexts from the MME as a virtual HSS;

 If the last access system is SAE and the new MME node is currently accessed, the method is: oew MME obtains DY(C, M), ST{C, S} from the old MME, and obtains ST{M from the HSS. ), or obtain all the context from the o d MME, after which the new MME is associated with the SGSN;

 If the last access system is 2G/3G, the current access system is SAE, and the accessed MME node is a registered MME, the method is:

 The MME obtains DY{C} from the SGSN, and does not extract context from other nodes;

 If the last access system is 2G/3G, the current access system is SAE, and the accessed MME node is an unregistered MME, the 3⁄4 method is:

 New MME obtains OY{C} from SGSN, DY{M:}, ST{S} or ST{C, S} from old MME, ST{M} or ST{C, M: or all static from HSS Context: 'After the new MME is associated with the SGSN;

 If the last access system is 2G/3G, and the new SGSN' node is currently connected, the new SGSN acquires DY{C, S} from the old SGS, and acquires ST{CS} from the MME, and the new SGSN establishes association with the MME. :

 If the UE is registered to the 2G/3G, the SGSN is registered to the HSS, and the SGSN is used as the virtual HSS of the MME. The MME is only registered to the SGSN, and the same is true.

 In addition, it should be noted that the access procedures of the present invention include, but are not limited to, location area update, service request, paging response, Detach, etc., and the location area update is taken as an example for description.

 While the invention has been described by the embodiments of the present invention, it will be understood that

Claims

 Rights request

 A method for obtaining an access system context, the method includes: when a user equipment UE accesses a current access system, providing information about its last access to the system to the current access system;

 The current access system only obtains the context from the entity that the UE last accessed the system.

 The method according to claim 1, wherein the system is a network architecture evolution SAE system or a 2G 3G system, the method further comprising:

 The context is divided into a static part and a dynamic part in advance, wherein the static part is a context acquired by the SGSN or the MME from the HSS during the power-on attach process, and the dynamic part is a context generated by the static part SGSN or the MME according to the UE action; The static part is divided into ST{S, M, C), which respectively represent the context specific to the SGSN in the static part, the context of the MME-specific context and the common part; the dynamic part is divided into DY S, M, C), respectively indicating dynamic Part of the SGSN-specific context, MME-specific context, and the context of the public part

 The method according to claim 2, wherein the current access system and the last access system are different types of radio access technology RAr systems;

 When the υ'Ε accesses the current access system, the process of providing the information of the last accessed system to the current access system includes:

 Initiating an access request to the access entity in the current access system, and carrying the identifier indicating the last access system in the request, the identifier is: the temporary mobility allocated by the last access system to the UE User identification TMSI and routing area RA identification, or the wireless access technology class of the last access system 3⁄4;

 According to the information, the current access system obtains the context from the entity that the UE last accessed the system.

 The access entity in the current access system determines the old access entity of the last access system of the UE according to the identifier of the last access system, and obtains the public part DY (C} in the dynamic context from the entity. .

4. The method according to claim 3, wherein the method further comprises: the access entity in the current access system assigning a new temporary mobile subscriber identity and routing area to the UE > and the new The temporary mobile subscriber identity and routing area are sent to the UE.

The method according to claim 4, wherein the method further comprises: if the UE currently moves to an unregistered access entity, the access entity is

Before the UE allocates the new temporary mobile subscriber identity and the routing area, the access entity acquires the context specific to the access entity and the context of the public part in the static context of the UE from the HSS through the location update process.

 The method according to claim 3, wherein the last access system is an SAE system, the current access system is a 2GZ3G system, and the access entity in the current access system is an SGSN. The old access entity of the last access system is MME

 The method according to claim 3, wherein the last access system is a 2G 3G system, the current access system is an SAE system, and the access entity in the current access system is ΜΜΕ The old access entity of the last access system is the SGSN.

 The method according to claim 2, wherein the current access system and the last access system are different types of access systems, and the access entity of the current access system to which the UE moves An access entity that has been registered by the UE;

 When the 1JE accesses the current access system, the process of providing the information of the last accessed system to the current access system includes:

 The UE sends an access request to the access entity of the current access system, and carries the identifier indicating the last access system in the request; the identifier is any one or more of the following combinations: The TMSi and RA identifiers allocated by the UE, the type of radio access technology of the last access system, and the TMSi and RA identifiers allocated by the current access system to the UE;

 The process in which the current access system acquires the context from the entity that the UE last accessed the system according to the information includes:

The access entity of the current access system determines the UE's last access to the system according to the identity of the last access system! The access entity of the day, and obtain the public part DY (C} ₀ in the dynamic context of the UE from the entity

 The method according to claim 8, wherein the last access system is a 2G/3G system, the current access system is an SAE system, and the access entity in the current access system is M.E.

The method according to claim 8, wherein the last access system is SAE The current access system is a 2G/3G system, and the access entity in the current access system is an SGSN.

 The method according to claim 2, wherein the current access system and the last access system are the same type of access system, and the current access system to which the UE moves is connected. The incoming entity is a new access entity that the UE has not registered;

 When the I JE accesses the current access system, the process of providing the information of the last accessed system to the current access system includes:

 The UE sends an access request to the new access entity, where the request carries an identifier indicating the last access system, and the identifier is: the TMSI and the RA identifier allocated by the last access system to the UE And/or the type of wireless access technology of the last access system;

 The process of obtaining the context of the current access system root information from the entity that the UE last accessed the system includes:

 The new access entity determines the old access entity of the last access system of the UE according to the identifier of the last access system, and obtains the new connection in the dynamic context of the UE from the entity. Into the entity-specific context and the context of the public part

 The method according to claim 5, wherein the method further comprises: the new access entity acquiring, by the location update process, the context specific to the new access entity in the static context of the UE from the HSS , the context of the public part „

 The method according to claim 2, wherein the last access system and the current access system are 2GZ3G systems, and the new access entity is not registered by the UE.

14. The method of claim 12 fans claim, wherein said last access system and the current system is a SAJE access system, the new access entity is not registered in the UE _ΜΜΕ β

The method according to claim 2, wherein the currently accessed system and the last accessed system are different types of access systems, and the current access system to which the UE moves The access entity is a new access entity that the UE has not registered.

 When the UE accesses the current access system, the process of providing the information of the last accessed system to the current access system includes:

The UE sends an access request to the new access entity in the current access system, where the request carries an identifier indicating the system that was accessed last time, and the identifier is any one or more of the following combinations: Enter The Ts1 and RA identifiers assigned by the system to the UE, the type of radio access technology of the last access system, and the TMSI and RA identifiers allocated by the current access system to the UE;

 The current access system acquires a context from an entity that the UE last accessed the system according to the information. The process includes:

 The new access entity obtains the public part DY {C} in the dynamic context of the UE from the access entity of the last access system according to the identifier of the last access system.

 The method according to claim 5, wherein the method further comprises: the new access entity from the current access system according to the identifier of the last access system The access entity acquires a context specific to the old access entity in the dynamic context of the UE;

 The context of the context, public part unique to the new access entity in the UE static context is obtained from the HSS by the registration procedure

 1.7 The method according to claim 5, wherein the last access system is an SAE system, the current access system is a 2G/3G system, and the new access entity is not registered by the UE. The SGSN passed.

 The method according to claim 15, wherein the last access system is a 2G/3G system, the current access system is an SAE system, and the new access entity is not registered by the UE. Oh,

 The method according to claim 2, wherein the obscured and/or the SC3SN respectively save all dynamic contexts DY{all }, and the entity of the current access system acquires from the entity of the previous access system DY{aj.,

20. The method according to claim 2, wherein the MM.E and/or the SGSN respectively save all dynamic contexts DY{all) and all static contexts S'a), the entities of the current access system Get the ST{all}^ 3⁄4 DY{ail} ₀ from the entity of the previous access system

 The method according to claim 2, wherein the MME and/or the SGSN respectively store respective dynamic contexts and static contexts, and the entity of the current access system contacts the current connection that the UE has accessed. The dynamic context and static context of the UE are obtained in an entity of the access system of the same type.

The method according to the preceding claims, wherein, when the current access system is a different access system from the last access system, and the access device currently moved by the IJE is a new access device, The process of obtaining a context from an entity that accesses the system last time includes:

 The entity of the UE's new current access system acquires the context from the entity of the old current access system of the UE and the entity of the last access system.

 The method according to claim 2, wherein before the obtaining the context, the method further comprises: after the UE registers with the SAE, the MME records the HSS, and the SGSN registers the MME as a virtual HSS>SGSN to the read MME, the UE Register to the MME and SGSN;

 If the last access system of the UE is SAE, the current access system is 2G/3G, and the accessed node is a registered SGSN, the SGSN obtains DY{C) from the MME;

 If the last access system of the UE is SAE, the current access system is 2G/3G, and the accessed node is an unregistered new SGSN, the new SGSN obtains DY from the MME as the virtual HSS. {C ST{C,S} , get DY{S} from the old SGSN;

 If the last access system of the UE is SAE and the new MME node is currently accessed, the new MME obtains DY{C, M}, ST{C, S from the old MME, and obtains ST{M} from: HSS. , or get all contexts from the old MME;

 If the last access system of the UE is 2G/3G, the current access system is SAE, and the accessed MME node is the registered MME, then M E obtains DY{C) from the SGSN;

 If the last access system of the UE is 2G/3G, the current access system is SAE, and the accessed MME node is an unregistered MME, the new MME obtains DY{C) from the SGSN, and obtains DYiM from the old MME. }, ST{S} or ST{C, S}, obtain ST{3VJ} or ST{C, M) or all static upper and lower texts from the HSS;

If the UE accesses the system last time as 2G/3G and accesses the new SGSN node, the new SGSN obtains DY{C, S} from the SGSN of the ! day, and retrieves ST{C, S} _e from the MME.

 24. A method according to any one of claims 1 to 23, characterized in that the reading method further comprises:

 Carrying a context reference number CRN in the access request message;

 The network entity in the current access system determines, according to the CRN, whether the entity stores the latest context;

 If not, decide to get the context from other entities