CN101128030A

CN101128030A - Context negotiation method

Info

Publication number: CN101128030A
Application number: CNA2006101114043A
Authority: CN
Inventors: 郭小龙; 孙颖
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2006-08-16
Filing date: 2006-08-16
Publication date: 2008-02-20
Anticipated expiration: 2026-08-16
Also published as: CN101128030B; WO2008019632A1

Abstract

The utility model relates to a mobile communication access technical field, disclosing a context negotiating method, a subscriber equipment UE and a wireless access body are used to store the context value CRN of the UE. The utility model comprises following steps: A. The subscriber equipment sends access request with CRN to a first RAT body; B. The first RAT body judge whether the received CRN is matched with the CRN corresponding to the UE stored in the RAT body; if not, C process is executed, or the flow is exited; C. The first RAT body gets the context of UE from a second RAT body, and the first body RAT and UE update the UE and CRN stored locally. The utility model also discloses another context negotiating method. The utility model avoids unnecessary context synchronous process.

Description

The method of context negotiation

Technical field

The present invention relates to mobile communication access technology field, particularly the method for context negotiation.

Background technology

At present at third generation partner program (Three Generation Partnership Project, 3GPP), each manufacturer's active research System Architecture Evolution (System Architecture Evolution, SAE), Long Term Evolution (Long Term Evolution, LTE) project.The purpose of SAE or LTE provides a kind of network cheaply that can reduce time delay, raising user data rate, improved power system capacity and covering, and (bearer network all is the IP carrying for Packet Switching, PS) territory business only to use packet switching.

Occurred at present a lot of new network architectures and can reach foregoing purpose, wherein a kind of network architecture of commonplace acceptance mainly comprises as shown in Figure 1 as the lower part:

The wireless access network of evolvement network (LTE RAN) is used to realize the access of subscriber equipment (UE), and here as a functional entity, concrete node does not wherein limit;

Mobile management entity/user entity (Mobility Management Entity/User PlaneEntity, MME/UPE), the function of MME is to preserve mobile management (MM) context of UE, as user's sign, mobility status, TA information etc., and the user authenticated; The function of UPE is the entity of the UE termination downlink data of idle (idle) state, triggers paging simultaneously and preserves the context of UE, as the IP address of UE and routing iinformation etc.; It is unrestricted whether MME/UPE separates following method, below as do not add specified otherwise, MME is the abbreviation of MME/UPE;

User's face anchor point (User Plane Anchor, UPA) and home subscriber server (HomeSubscriber Server HSS) is respectively applied for and carries out routing update and register information and upgrade.

(Radio Access Technology moves between RAT), and UE can change and quarters at different networks and cause the table tennis registration process if UE is in different wireless access technologys.The network configuration that 2G/3G network combines with evolvement network as shown in Figure 2, RA1 and RA2 are route district (the Routing Area of existing 2G/3G, RA), the UE of existing 2G/3G will initiate Routing Area Update (Routing Area Update, RAU) process at RA of every replacing.TA1, TA2, TA3, TA4 be evolvement network tracking area (Tracking Area, TA).Mobile as a multimode UE like this in these zones, if there is not certain mechanism, can cause frequent network registration process.UE script Serving GPRS Support Node (SGSN) to 2G/3G in RA1 is registered; When entering 1 of TA, registers to the MME/UPE of evolvement network again UE; When UE move out again TA1 enter RA1 will be to the SGSN of 2G/3G registration; UE moves to TA2 from RA1 again and registers to MME/UPE again ... the purpose of registration is to make network paging still to bring a large amount of register command expenses to UE in certain RAT.

Because two kinds of connecting systems being registered to of UE, the i.e. MME of the SGSN of 2G/3G or evolvement network) context (context) of UE all arranged.Context comprises the distinctive context of this RAT and two kinds of contexts that RAT is general, when the context changes of a kind of RAT, may have influence on the context of another kind of RAT, so this wherein relates to contextual stationary problem.

Present contextual synchronization scenario mainly contains following two kinds:

1, principal and subordinate (Master-Slave) mode: always keep up-to-date context at MME, inserting MME like this, needn't to carry out context mutual; When SGSN has change in context, need notify MME with contextual situation of change;

Can not notify the opposing party when 2, the context of collaborative (Coordination) mode: UE changes under any access technology, have only when UE inserts certain technology once more, whether MME or SGSN obtain the other side's context, do not change at another entity because this entity is known the context of UE.

These two kinds of methods all can cause unnecessary context synchronizing process.In master-slave mode, even UE does not insert MME all the time, do not need MME to have under the situation of latest content, also will be with change in context advisory MME; UE is when inserting SGSN, and the context among the SGSN might be a latest content, and SGSN still will be to the MME request contexts in this case, and this there is no need fully.In cooperative mode, UE every access SGSN or MME will remove to obtain context to the other side's entity (being MME or SGSN), and when UE one waits until at certain access technology net such as 2G/3G network, so this method is brought unnecessary context synchronizing process.

Summary of the invention

In view of this, the objective of the invention is to, propose the method for context negotiation, can avoid unnecessary context synchronizing process.

The context negotiation method that the present invention proposes is divided three classes according to its execution mode, and in the first kind scheme, user equipment (UE) and wireless access technology RAT entity are preserved the context record value CRN about UE respectively, and comprise the steps:

A1, user equipment (UE) send the access request of carrying CRN to a RAT entity;

Whether the CRN that the CRN that B1, RAT entity judgement are received is corresponding with the described UE that the entity of this RAT is preserved mates, if do not match then execution in step C, otherwise withdraws from flow process of the present invention;

C1, a RAT entity obtain the context of described UE to the 2nd RAT entity.

A described RAT entity is Serving GPRS Support Node SGSN, and the 2nd RAT entity is mobile management entity or user entity MME/UPE;

Perhaps, a described RAT entity is MME/UPE, and the 2nd RAT entity is SGSN.

Further comprise before the steps A 1:

UE is registered to the 2nd RAT entity, and described the 2nd RAT entity has been created the context about described UE.

Further comprise after the step C1: a RAT entity changes the context of UE, upgrades the CRN of the described UE that this entity preserves, and notifies described UE to upgrade the CRN of its preservation.

The CRN that described notice UE upgrades its preservation comprises following any one situation:

Send dedicated signaling or the existing signaling of the CRN after carrying renewal to UE;

Perhaps, the CRN after will upgrading in the access dispose procedure of UE sends to UE.

Further comprise after the step C1: a described RAT entity is set up related with described the 2nd RAT entity.

Described UE did not change RAT and does not change and insert entity before steps A, then the entity of described RAT of step B1 is a RAT entity.

Before steps A 1, described UE moves to a new RAT entity from a RAT entity at original place, and a then described RAT entity is a new RAT entity, and step B1 further comprises:

B111, a new RAT entity send context request to a RAT entity at the original place of UE;

The one RAT entity at B112, the original place of UE is sent to a new RAT entity with context and the corresponding CRN of described UE;

Whether B113, a new RAT entity judge CRN that UE reports and mate from the CRN of the RAT entity at the original place of UE, if not execution in step C1 then, if then withdraw from flow process of the present invention.

Before steps A 1, described UE moves to a new RAT entity from a RAT entity at original place, and then steps A 1 a described RAT entity is new RAT entity;

Step B1 further comprises:

B121, a new RAT entity send the context request of carrying the CRN that UE reports to the RAT entity at the original place of UE;

The one RAT entity at B122, the original place of UE judges whether the CRN CRN corresponding with the described UE of local preservation that is received mates, if not execution in step C1 then, if then withdraw from flow process of the present invention;

Described step C1 is: a RAT entity at the original place of UE obtains the context of described UE to the 2nd RAT entity;

Further comprise after the step C1: a RAT entity at the original place of UE is sent to a new RAT entity with the UE context that obtained and corresponding CRN and the local UE context of preserving.

In the second class embodiment, a RAT entity is not only preserved the CRN of this RAT about UE, also preserves the CRN of the 2nd RAT about UE, and comprises the steps:

A2, UE send the request of access to a RAT entity;

B2, a RAT entity are sent to the 2nd RAT entity with the CRN about UE of the 2nd RAT that the entity of this RAT is preserved;

C2, the 2nd RAT entity judge whether the CRN of CRN that is received and the 2nd RAT that self preserves mates, if execution in step D2 then, otherwise execution in step E2;

D2, the 2nd RAT entity send prompting message to a RAT entity, and the UE context that a RAT entity is preserved the entity of this RAT is as the up-to-date context of UE, and finish flow process of the present invention;

E2, the 2nd RAT entity are sent to a RAT entity with the UE context of self preserving, and a RAT entity generates the up-to-date context of UE according to the UE context of being received.

Perhaps, a described RAT entity is MME/UPE, and the 2nd RAT entity is SGSN.

Preferably, this method further comprises: the context changes of UE in the RAT entity, a RAT entity upgrades the CRN of the UE of this RAT that self preserves.

Described UE did not change RAT and does not change and insert entity before steps A 2, then the entity of described RAT of step B2 is a RAT entity.

Before steps A 2, described UE moves to a new RAT entity from a RAT entity at original place, and a then described RAT entity is a new RAT entity, and step B2 further comprises:

B211, a new RAT entity send context request to a RAT entity at the original place of UE;

The one RAT entity at B212, the original place of UE sends the context response information of the CRN of the UE that carries the UE context self preserved and the 2nd RAT to a new RAT entity;

B213, a new RAT entity send the CRN that carries from the UE of the 2nd RAT of the RAT entity at the original place of UE to the 2nd RAT entity.

Before steps A 2, described UE moves to a new RAT entity from a RAT entity at original place, and then steps A 3 described RAT entities are a new RAT entity;

Step B2 further comprises:

B221, a new RAT entity send context request to a RAT entity at the original place of UE;

The one RAT entity at B222, the original place of UE sends the context request of the CRN of the UE that carries the 2nd RAT that self preserves;

Described step D2 is: the 2nd RAT entity sends prompting message to a RAT entity at the original place of UE, the CRN of UE context that the one RAT entity at the original place of UE is preserved self and the UE of the 2nd RAT is sent to a new RAT entity, and a RAT entity is preserved the CRN of the UE of the UE context received and the 2nd RAT;

Described step e 2 is: the CRN of UE context that the 2nd RAT entity is preserved self and the UE of the 2nd RAT is sent to a RAT entity at the original place of UE; The one RAT entity at the original place of UE is sent to a new RAT entity with the context of the CRN of the UE of the UE context from the 2nd RAT entity received, the 2nd RAT and the UE that self preserves; A new RAT entity generates the up-to-date context of UE according to the UE context of being received, and preserves the CRN of the UE of the 2nd RAT that is received.

In the 3rd class execution mode, the RAT entity is preserved the CRN of UE, and comprises the steps:

A3, UE send the request of access to a RAT entity;

B3, a RAT entity are sent to the 2nd RAT entity with the CRN of the described UE that this entity is preserved

C3, the 2nd RAT entity judge whether the CRN that self preserves upgrades than the CRN that is received, if execution in step E3 then, otherwise execution in step D3;

D3, the 2nd RAT entity send prompting message to a RAT entity, and the UE context that a RAT entity is preserved the entity of this RAT is as the up-to-date context of UE, and finish flow process of the present invention;

E3, the 2nd RAT entity are sent to a RAT entity with the UE context of self preserving, and a RAT entity generates the up-to-date context of UE according to the UE context of being received.

Wherein, a RAT entity adopts identical algorithm to upgrade the CRN that self preserves with the 2nd RAT entity.

Preferably, this method further comprises: the CRN that a RAT entity or the 2nd RAT entity are preserved carries out initialization, then notifies the CRN of the 2nd RAT entity or its preservation of RAT entity synchronous initiation.

A described RAT entity is SGSN, and the 2nd RAT entity is MME/UPE;

Perhaps, a described RAT entity is MME/UPE, and the 2nd RAT entity is SGSN.

This method further comprises: the context changes of UE in the RAT entity, a RAT entity upgrades the CRN of the described UE that self preserves.

Described UE did not change RAT and does not change and insert entity before steps A 3, then the entity of described RAT of step B3 is a RAT entity.

Before steps A 3, described UE moves to a new RAT entity from a RAT entity at original place, and a then described RAT entity is a new RAT entity, and step B3 further comprises:

B311, a new RAT entity send context request to a RAT entity at the original place of UE;

The one RAT entity at B312, the original place of UE sends to a new RAT entity and carries the UE context self preserved and the context response information of CRN;

B313, a new RAT entity send the CRN of the UE that the RAT entity that carries the original place of UE preserved to the 2nd RAT entity.

Before steps A 3, described UE moves to a new RAT entity from a RAT entity at original place, and then steps A 3 described RAT entities are a new RAT entity;

Step B3 further comprises:

B321, a new RAT entity send context request to a RAT entity at the original place of UE;

The one RAT entity at B322, the original place of UE sends the context request of the CRN that carries the UE that self preserves;

Described step D3 is: the 2nd RAT entity sends prompting message to a RAT entity at the original place of UE, the one RAT entity at the original place of UE is sent to a new RAT entity with UE context and the CRN that self preserves, and a RAT entity is preserved UE context and the CRN that is received;

Described step e 3 is: the RAT entity that UE context that the 2nd RAT entity is preserved self and CRN are sent to the original place of UE; The one RAT entity at the original place of UE is sent to a new RAT entity with the context of the CRN of the UE context from the 2nd RAT entity received, UE and the UE that self preserves; A new RAT entity generates the up-to-date context of UE according to the UE context of being received, and preserves the CRN of the UE that is received.

As can be seen from the above technical solutions, the CRN value of the CRN that RAT entity comparison UE reports and self storage illustrates that the local UE of preservation context is up-to-date if both are consistent, need not to carry out the context synchronizing process; If the local UE context of preserving of both inconsistent then explanations is not up-to-date, need obtain up-to-date context by the context synchronizing process, so just can avoid meaningless context synchronizing process, saved interface-free resources.

Description of drawings

Fig. 1 is the configuration diagram of evolvement network;

The network configuration example figure that Fig. 2 combines with evolvement network for the 2G/3G network;

Fig. 3 is the flow chart of the embodiment of the invention one;

Fig. 4 is the flow chart of the embodiment of the invention two;

Fig. 5 a and Fig. 5 b are the flow chart of the embodiment of the invention three;

Fig. 6 a and Fig. 6 b are the flow chart of 4 first kinds of execution modes of the embodiment of the invention;

Fig. 7 a and Fig. 7 b are the flow chart of 4 second kinds of execution modes of the embodiment of the invention;

Fig. 8 a and Fig. 8 b are the flow chart of the embodiment of the invention five;

Fig. 9 a and Fig. 9 b are the flow chart of 6 first kinds of execution modes of the embodiment of the invention;

Figure 10 a and Figure 10 b are the flow chart of 6 second kinds of execution modes of the embodiment of the invention;

Figure 11 is the present invention's first sets of plan Signalling exchange flow chart;

Figure 12 is the present invention's second sets of plan Signalling exchange flow chart;

Figure 13 is the flow chart of the embodiment of the invention seven;

Figure 14 is the flow chart of the embodiment of the invention eight;

Figure 15 is the flow chart of 9 first kinds of execution modes of the embodiment of the invention;

Figure 16 is the flow chart of 9 second kinds of execution modes of the embodiment of the invention;

Figure 17 is the flow chart of ten first kinds of execution modes of the embodiment of the invention;

Figure 18 is the flow chart of ten second kinds of execution modes of the embodiment of the invention;

Figure 19 is the flow chart of the embodiment of the invention 11;

Figure 20 is the flow chart of the embodiment of the invention 12;

Figure 21 is the flow chart of the embodiment of the invention 13 the first execution modes;

Figure 22 is the flow chart of the embodiment of the invention 13 the second execution modes;

Figure 23 is the flow chart of the embodiment of the invention 14 the first execution modes;

Figure 24 is the flow chart of the embodiment of the invention 14 the second execution modes.

Embodiment

For making the purpose, technical solutions and advantages of the present invention clearer,, and the present invention is divided into three class embodiments to setting forth below in conjunction with accompanying drawing.

First kind embodiment of the present invention is a kind of context record value (Context RecordNumber, cooperative mode CRN) of having.Specifically, UE inserts MME or SGSN, upgrade context after, if the context changes of the RAT entity of this access (MME or SGSN) then changes the value of CRN according to the CRN update algorithm, and CRN is synchronized to UE; As long as it is all different after described CRN update algorithm changes each CRN with value before the change, the present invention of its concrete form does not do any qualification, lifts simple example, and the CRN update algorithm can be that CRN is progressively increased 1, CRN is a cycle values, reaches the highest and then puts minimum or CRN successively decreases;

UE inserts another RAT entity (SGSN or MME), and the CRN of UE this locality is sent to this entity, if the CRN coupling that the entity of the CRN that UE carries and access keeps does not then need the past RAT entity (MME or SGSN) to obtain context; Otherwise the entity of access wants the past RAT entity to obtain context, and upgrades the CRN of oneself, as the CRN value on the RAT entity before equaling, or equals the CRN value on the UE; When context changes once more, change CRN according to the CRN update algorithm, and send to UE and carry out synchronously.

In addition, when some important special context changes, during context changes that for example safety is relevant, may notify another entity change in context situation at once.

Below by specific embodiment the inventive method is further elaborated.

Embodiment one: UE initially inserts the 2G/3G network.

The flow process of present embodiment comprises the steps: as shown in Figure 3

Step 301:UE start inserts the 2G/3G network and reports local CRN value to SGSN, is referred to as UE_CRN, supposes that initial CRN is set to 0;

Create about the context of described UE among the step 302:SGSN and preserve the CRN that UE reports; Below all the CRN that preserves among the SGSN is referred to as SGSN_CRN, be 0 this moment; After UE succeeds in registration, according to the CRN update algorithm, UE_CRN and SGSN_CRN are all progressively increased 1, then UE_CRN and SGSN_CRN all become 1;

Step 303:UE enters evolvement network and reports local CRN to MME;

Create among the step 304:MME about the related context of described UE in evolvement network; Detailed process is as follows: MME is the CRN of the CRN that reports of UE and the local described UE that has stored at first relatively, the CRN value that UE reports is 1, below all the CRN that preserves among the MME is referred to as MME_CRN, this fashion does not have the MME_CRN about this UE, then MME asks for context and the corresponding CRN of UE in SGSN to SGSN, and it is identical that MME_CRN is changed to the CRN or the SGSN_CRN that send up with UE, and the value that is about to MME_CRN is changed to 1; If after MME upgraded to some extent to context, MME_CRN progressively increased 1 once more, and the notice of the CRN after will changing UE, then UE_CRN and MME_CRN all become 2; CRN behind described will change notice UE can be the dedicated signaling from the CRN after carrying renewal to UE or the existing signaling that send; Perhaps, the CRN after will upgrading in the access dispose procedure of UE sends to UE.

Step 305: when UE inserts the 2G/3G network once more, SGSN_CRN value (current is 1) among UE_CRN that UE reports (current is 2) and the SGSN is not inconsistent, then SGSN gets the context of described UE in the MME, and it is identical that SGSN_CRN is changed to the CRN or the MME_CRN that send up with UE, is about to SGSN_CRN and is set to 2.

If insert in the 2G/3G network development process at this UE, the context of UE does not change, the CRN of UE does not need to upgrade (still being 2) so, UE inserts 2G/3G or SAE once more so, then the entity of Jie Ruing does not need to get context from the opposing party, because MME_CRN and SGSN_CRN are 2, the CRN that reports with UE is identical.

In the process that above CRN changes,, then CRN is changed to minimum if CRN has reached maximum.

Embodiment two: UE initially inserts the SAE/LTE network.

The flow process of present embodiment comprises the steps: as shown in Figure 4

Step 401:UE start access network also reports local CRN value to MME, and the local CRN that stores of UE is referred to as UE_CRN, supposes that initial CRN is set to 0;

Create about the context of described UE among the step 402:MME and preserve the CRN that UE reports; The CRN that preserves among the MME is referred to as MME_CRN, and be 0 this moment; After UE succeeds in registration, according to the CRN update algorithm, UE_CRN and MME_CRN are all progressively increased 1, then UE_CRN and MME_CRN all become 1;

Step 403:UE enters the 2G/3G network and reports local CRN to MME;

Create among the step 404:SGSN about the related context of described UE in the 2G/3G network; Detailed process is as follows: SGSN is the CRN of the CRN that reports of UE and the local described UE that has stored at first relatively, the CRN value that UE reports is 1, the CRN that preserves among the SGSN is referred to as SGSN_CRN, this fashion does not have the SGSN_CRN about this UE, then SGSN asks for context and the corresponding CRN of UE in MME to MME, and it is identical that SGSN_CRN is changed to the CRN or the MME_CRN that send up with UE, and the value that is about to SGSN_CRN is changed to 1; If after SGSN upgraded to some extent to context, SGSN_CRN progressively increased 1 once more, and the notice of the CRN after will changing UE, then UE_CRN and SGSN_CRN all become 2; CRN behind described will change notice UE can be the dedicated signaling from the CRN after carrying renewal to UE or the existing signaling that send; Perhaps, the CRN after will upgrading in the access dispose procedure of UE sends to UE.

Step 405: as UE once more during cut-in evolution network, MME_CRN (value is 1) among UE_CRN that UE reports (value is 2) and the MME is not inconsistent, then SGSN gets the context of described UE in the MME, and the MME_CRN of corresponding described UE is changed to identical with SGSN_CRN or UE_CRN.

In the process of superincumbent UE cut-in evolution network, if the context of UE does not change, UE_CRN does not upgrade so, and when UE inserts 2G/3G or evolvement network once more, then the entity of Jie Ruing does not need to get context from the opposing party.

Embodiment three: under the constant situation of SGSN, and the RAU process that UE initiates at the 2G/3G network.

UE is after SGSN sends the RAU request, and SGSN can judge that whether the CRN value that UE reports and the CRN value of self storage inside mate, and just need not initiate to ask for contextual flow process to MME if mate SGSN; Otherwise then will ask for related context to MME, detailed process is seen shown in Fig. 5 a or Fig. 5 b, is comprised the steps:

Step 501:UE sends the RAU request of carrying UE_CRN to SGSN; Also comprise old U-TMSI, old U-RA and/or S-TMSI, S-RA among the RAU, these contents and the present invention are irrelevant;

Step 502:SGSN judges whether the UE_CRN that is received mates with the local SGSN_CRN that stores, if coupling does not then need to ask among the MME context, carries out normal RAU flow process, otherwise execution in step 503;

Step 503:SGSN sends context request to MME;

Step 504:MME is sent to SGSN with the context of described UE; The context that the SGSN storage is received, and SGSN_CRN is changed to identical with UE_CRN or MME_CRN;

Step 505: carry out other processes among the RAU, upgrade as the PDP Context between SGSN and MME, described other processes are all irrelevant with content of the present invention;

Step 506: if SGSN goes up some context of UE renewal is arranged, then will upgrade CRN and be synchronized to UE; The described UE of being synchronized to can be the dedicated signaling from the CRN after carrying renewal to UE or the existing signaling that send; Perhaps, the CRN after will upgrading in the access dispose procedure of UE sends to UE; SGSN sends RAU to UE and accepts to reply.

Embodiment four: under the situation that SGSN changes, and the RAU process that UE initiates at the 2G/3G network.

UE is after new SGSN initiates the RAU request, and new SGSN can arrive the context of getting UE among the old SGSN at the original place of UE.New SGSN or old SGSN can judge whether the SGSN_CRN that stores among UE_CRN that UE reports and the oldSGSN mates, if do not match, illustrate that variation has taken place the context of user in evolvement network, SGSN will be triggered to MME and get contextual flow process, otherwise just needn't trigger this process.Detailed process comprises the steps: shown in Fig. 6 a or Fig. 6 b

Step 601:UE sends the RAU request of carrying UE_CRN to SGSN;

Step 602:SGSN sends context request to the old at the original place of UE SGSN;

Step 603:old SGSN is sent to SGSN with context and the corresponding SGSN_CRN of described UE;

Step 604:SGSN judges from the UE_CRN of UE with from the SGSN_CRN of old SGSN whether mate, if coupling is then carried out normal RAU flow process, do not need to ask for context among the MME, otherwise execution in step 605;

Step 605:SGSN sends context request to MME;

Step 606:MME is sent to SGSN with the context of described UE, the context that the SGSN storage is received, and SGSN_CRN is set to identical with UE_CRN or MME_CRN;

Step 607: carry out other correlated processes of RAU, as position renewal, PDP Context renewal etc.; These processes are not contents of the present invention, but the RAU process is necessary; It is related that MME and SGSN also will set up, and promptly MME and SGSN write down the other side's address information respectively;

Step 608:SGSN sends RAU to UE and replys, if some context of UE has renewal on new SGSN, then will upgrade CRN and be synchronized to UE.The described UE of being synchronized to can be the dedicated signaling from the CRN after carrying renewal to UE or the existing signaling that send; Perhaps, the CRN after will upgrading in the access dispose procedure of UE sends to UE.

Present embodiment also can adopt as flow process as shown in Figure 7a or 7b:

Step 701:UE sends the RAU request of carrying UE_CRN to SGSN;

Step 702:SGSN sends context request to the old at the original place of UE SGSN, in this request, carries the UE_CRN that UE reports;

Whether the SGSN_CRN of the UE_CRN that step 703:old SGSN judgement is received and the described UE correspondence of local storage mates, and carries out normal RAU flow process if mate, otherwise execution in step 704;

Step 704:old SGSN sends context request to MME;

Step 705:MME is sent to old SGSN with the context of described UE;

The context of the UE that step 706:old SGSN preserves self and be sent to the SGSN at the present place of UE from the UE context that MME obtains;

Step 707: carry out other correlated processes of RAU, as position renewal, PDP Context renewal etc.; It is related that MME and SGSN also will set up, and promptly MME and SGSN write down the other side's address information respectively;

Step 708:SGSN sends RAU to UE and replys.If some context of UE has renewal on new SGSN, then to upgrade CRN and be synchronized to UE.The described UE of being synchronized to can be the dedicated signaling from the CRN after carrying renewal to UE or the existing signaling that send; Perhaps, the CRN after will upgrading in the access dispose procedure of UE sends to UE.

Embodiment five: under the constant situation of MME, and the RAU process that UE initiates at evolvement network.

UE is after MME sends the RAU request, and MME can judge that whether the CRN value that UE reports and the CRN value of self storage inside mate, and just need not initiate to ask for contextual flow process to SGSN if mate MME; Otherwise then will ask for related context to SGSN, detailed process is seen shown in Fig. 8 a or Fig. 8 b, is comprised the steps:

Step 801:UE sends the RAU request of carrying UE_CRN to MME; Also comprise old U-TMSI, old U-RA or S-TMSI, S-RA among the RAU, these contents and the present invention are irrelevant;

Step 802:MME judges whether the UE_CRN that is received mates with the local MME_CRN that stores, if coupling is carried out normal RAU flow process, otherwise execution in step 803;

Step 803:MME sends context request to SGSN;

Step 804:SGSN is sent to MME with the context of described UE; The context that the MME storage is received, and MME_CRN is changed to identical with UE_CRN or SGSN_CRN;

Step 805: carry out other processes among the RAU, upgrade as the PDP Context between MME and SGSN, described other processes are all irrelevant with content of the present invention; It is related that MME and SGSN also will set up, and promptly MME and SGSN write down the other side's address information respectively;

Step 806:MME sends RAU to UE and replys.If some context of UE has renewal on MME, then to upgrade CRN and be synchronized to UE.The described UE of being synchronized to can be the dedicated signaling from the CRN after carrying renewal to UE or the existing signaling that send; Perhaps, the CRN after will upgrading in the access dispose procedure of UE sends to UE.

Embodiment six: under the situation that MME changes, and the RAU process that UE initiates at evolvement network.

UE is after new MME initiates the RAU request, and new MME can arrive the context of getting UE among the old MME at the original place of UE.New MME or old MME can judge whether the MME_CRN that stores among UE_CRN that UE reports and the oldMME mates, if do not match, illustrate that variation has taken place the context of user in 2G/3G, MME will be triggered to SGSN and get contextual flow process, otherwise just needn't trigger this process.Detailed process comprises the steps: shown in Fig. 9 a or Fig. 9 b

Step 901:UE sends the RAU request of carrying UE_CRN to MME;

Step 902:MME sends context request to the old at the original place of UE MME;

Step 903:old MME is sent to MME with context and the corresponding MME_CRN of described UE;

Step 904:MME judges from the UE_CRN of UE with from the MME_CRN of old MME whether mate, if coupling is carried out normal RAU flow process, otherwise execution in step 905;

Step 905:MME sends context request to SGSN;

Step 906:SGSN is sent to MME with the context of described UE; The context that the MME storage is received, and MME_CRN is changed to identical with UE_CRN or SGSN_CRN;

Step 907: carry out other correlated processes of RAU, as position renewal, PDP Context renewal etc.; It is related that MME and SGSN also will set up, and promptly MME and SGSN write down the other side's address information respectively;

Step 908: the back MME that finishes sends RAU to UE and replys.If some context of UE has renewal on MME, then to upgrade CRN and be synchronized to UE.The described UE of being synchronized to can be the dedicated signaling from the CRN after carrying renewal to UE or the existing signaling that send; Perhaps, the CRN after will upgrading in the access dispose procedure of UE sends to UE.

Present embodiment also can adopt flow process as shown in figure 10:

Step 1001:UE sends the RAU request of carrying UE_CRN to MME;

Step 1002:MME sends context request to the old at the original place of UE MME, in this request, carries the UE_CRN that UE reports;

Step 1003:old MME judges whether the UE_CRN and the local CRN that stores that are received mate, if coupling is then carried out normal RAU flow process, otherwise execution in step 1004;

Step 1004:old MME sends context request to SGSN;

Step 1005:SGSN is sent to old MME with the context of described UE;

Step 1006:old MME sends to MME together with context of self preserving and the context that obtains from SGSN;

Step 1007: carry out other correlated processes of RAU, as position renewal, PDP Context renewal etc.; It is related that MME and SGSN also will set up, and promptly MME and SGSN write down the other side's address information respectively;

Step 1008:MME sends RAU to UE and replys; If some context of UE has renewal on new MME, then to upgrade CRN and be synchronized to UE.The described UE of being synchronized to can be the dedicated signaling from the CRN after carrying renewal to UE or the existing signaling that send; Perhaps, the CRN after will upgrading in the access dispose procedure of UE sends to UE.

More than each embodiment mainly be to be that example describes with the RAU process, in fact the method for the invention is applicable to the various processes that UE inserts.Below the flow process of the above embodiment of the inventive method is once summed up, wherein represent to adopt the access entity of first kind of RAT with a RAT entity, the 2nd RAT entity represents to adopt the access entity of second kind of RAT, RAT can be SAE or 2G/3G, and then a RAT entity or the 2nd RAT entity are represented SGSN or MME respectively.Figure 11 is the Signalling exchange flow chart of the inventive method, comprises the steps:

Step 1101:UE sends the request of access to a RAT entity, carries UE_CRN in this request;

Step 1102: a RAT entity judges whether the CRN of the described UE that the entity of the UE_CRN received and this RAT is preserved mates, if then carry out other operation, if not execution in step 1103 then;

Step 1103: a RAT entity to the 2nd RAT entity and or a former RAT entity send context request, require to obtain the context of described UE;

Step 1104: the 2nd RAT entity is sent to a RAT entity with the context of described UE; Perhaps the 2nd RAT entity is sent to the RAT entity at the original place of UE with the context of described UE, and the RAT entity by the original place of UE is sent to a RAT entity with context again;

Step 1105: other correlated processes of carrying out this access process;

Step 1106: a RAT entity returns to insert to UE and accepts to reply.If contextual some part changes then the CRN value is carried out corresponding change and is synchronized to UE in the RAT entity.

The second class embodiment of the present invention is: two kinds of RAT entities are not only preserved the CRN of UE among this RAT, also preserve the CRN of UE among the another kind of RAT, and its basic interaction flow comprises the steps: as shown in figure 12

Step 1201:UE sends the request of access to a RAT entity;

Step 1202: a RAT entity sends context request to the 2nd RAT entity, carries the CRN of the 2nd RAT entity of preserving in the RAT entity in this request;

Step 1203: the 2nd RAT entity judges whether the CRN that self preserves and CRN from a RAT entity mate, if coupling is then returned and is not comprised the contextual information of UE, CRN or other guide that this information can be sent for null response, a RAT; Otherwise return the context of UE;

Step 1204: a RAT entity is judged the content received, if receive described information, then with the UE context self preserved as the up-to-date context of UE; If receive the context of UE, then with the UE context received as the up-to-date context of UE, and upgrade the CRN that self preserves;

Step 1205: other correlated processes of carrying out this access process;

Step 1206: a RAT entity returns to insert to UE and accepts to reply.If contextual some part changes then upgrades the CRN value in the RAT entity.

With specific embodiment this embodiment is described in detail below.

Embodiment seven: UE adopts second sets of plan to initiate to insert request at the 2G/3G network and does not change SGSN.

The flow process of present embodiment comprises the steps: as shown in figure 13

Step 1301:UE sends the request of access to SGSN, and this request can be RAU request, register requirement, page response etc.;

Step 1302:SGSN sends the context request message of carrying MME_CRN to MME; Here MME_CRN is the CRN of UE in the evolvement network of preserving among the SGSN, owing to from the MME_CRN among the MME, therefore might as well also it be referred to as MME_CRN;

Whether MME_CRN that step 1303:MME is relatively received and the MME_CRN that self preserves mate, if both do not match, then execution in step 1304; If both couplings then go to step 1305;

UE context and MME_CRN that step 1304:MME preserves this locality are sent to SGSN, and the UE context that SGSN preserves this locality according to the content of being received upgrades, and preserve the MME_CRN that is received; And go to step 1306;

Step 1305:MME returns one to SGSN and does not comprise the contextual information of UE, this information can for: in the SGSN context response information, return a null message, perhaps MME_CRN is returned to SGSN again, perhaps other predetermined content etc., the present invention is not further qualified the particular content and the form of described information;

Step 1306: carry out other flow process, as authentication, flow processs such as information updating.

If the context of UE in SGSN upgrades to some extent, then SGSN upgrades the SGSN_CRN that self preserves, and the MME_CRN that SGSN preserves then remains unchanged.

Embodiment eight: UE adopts second sets of plan to initiate to insert request at evolvement network and does not change MME.

The flow process of present embodiment comprises the steps: as shown in figure 14

Step 1401:UE sends the request of access to MME, and this request can be RAU request, register requirement, page response etc.;

Step 1402:MME sends the context request message of carrying SGSN_CRN to SGSN; Here SGSN_CRN is the CRN of UE in the 2G/3G network of preserving among the MME, owing to from the SGSN_CRN among the SGSN, therefore might as well also it be referred to as SGSN_CRN;

Whether SGSN_CRN that step 1403:SGSN is relatively received and the SGSN_CRN that self preserves mate, if both do not match, then execution in step 1404; If both couplings then go to step 1405;

UE context and SGSN_CRN that step 1404:SGSN preserves this locality are sent to MME, and the UE context that MME preserves this locality according to the content of being received upgrades, and preserve the SGSN_MME that is received; And go to step 1406;

Step 1405:SGSN returns one to MME and does not comprise the contextual information of UE, this information can for: in the MME context response information, return a null message, perhaps SGSN_CRN is returned to MME again, perhaps other predetermined content etc., the present invention is not further qualified the particular content and the form of described information;

Step 1406: carry out other flow process, as authentication, flow processs such as information updating.

If the context of UE in MME upgrades to some extent, then MME upgrades the MME_CRN that self preserves, and the SGSN_CRN that MME preserves then remains unchanged.

Embodiment nine: UE adopts second sets of plan to initiate to insert request and change SGSN at the 2G/3G network.

The present embodiment flow process comprises the steps: as shown in figure 15

Step 1501:UE sends the request of access to the new SGSN at the present place of UE, and this request can be RAU request, register requirement, page response etc.;

Step 1502: new SGSN sends the SGSN context request to the old at the original place of UE SGSN;

Step 1503:old SGSN sends the SGSN context request carry the MME_CRN that old SGSN preserved to MME;

Step 1504:MME judges whether MME_CRN that self preserves and the MME_CRN that is received mate, if both do not match, then execution in step 1505; If both couplings then execution in step 1506;

UE context and MME_CRN that step 1505:MME preserves this locality are sent to oldSGSN, and old SGSN will be from context and the MME_CRN of MME, and the context that self preserves is sent to new SGSN; New SGSN is according to the UE context of the updating context this locality of being received, and preserves the MME_CRN that is received;

Step 1506:MME returns one to old SGSN and does not comprise the contextual information of UE, and old SGSN is sent to new SGSN with context and the MME_CRN that self preserves; New SGSN preserves context and the MME_CRN that is received; Described information can for: in the SGSN context response information, return a null message, perhaps the MME_CRN that old SGSN is sent is returned to old SGSN again, perhaps other predetermined content etc., the present invention is not further qualified the particular content and the form of described information.

Step 1507: carry out other flow process, as authentication, flow processs such as information updating.

If the context of UE in new SGSN upgrades to some extent, then new SGSN upgrades the SGSN_CRN that self preserves, and the MME_CRN that new SGSN preserves then remains unchanged.

Present embodiment can also adopt flow process as shown in figure 16, comprises the steps:

Step 1601:UE sends the request of access to the new SGSN at the present place of UE, and this request can be RAU request, register requirement, page response etc.;

Step 1602: new SGSN sends the SGSN context request to the old at the original place of UE SGSN;

Step 1603:old SGSN sends to new SGSN and carries the UE context self preserved and the SGSN context response information of MME_CRN;

Step 1604: new SGSN sends context request to MME, also carries the MME_CRN from old SGSN in this context request;

Step 1605:MME judges whether MME_CRN that is received and the MME_CRN that self preserves mate, if then execution in step 1606; Otherwise execution in step 1607;

Step 1606:MME returns to new SGSN and does not comprise the contextual information of UE; New SGSN will be from the context of old SGSN as the UE latest content, and preserves MME_CRN, goes to step 1608;

Step 1607:MME is sent to new SGSN with UE context and the MME_CRN that self preserves; New SGSN will integrate the up-to-date context as UE from the context of old SGSN with from the context of MME, and preserve MME_CRN;

Step 1608: carry out other flow process, as authentication, flow processs such as information updating.

Embodiment ten: UE adopts second sets of plan to initiate to insert request and change MME at evolvement network.

The present embodiment flow process comprises the steps: as shown in figure 17

Step 1701:UE sends the request of access to the new MME at the present place of UE, and this request can be RAU request, register requirement, page response etc.;

Step 1702: new MME sends context request to the old at the original place of UE MME;

Step 1703:old MME sends the context request carry the SGSN_CRN that old MME preserved to SGSN;

Step 1704:SGSN judges whether SGSN_CRN that self preserves and the SGSN_CRN that is received mate, if both do not match, then execution in step 1705; If both couplings then execution in step 1706;

UE context and SGSN_CRN that step 1705:SGSN preserves this locality are sent to oldMME, and old MME will be from context and the SGSN_CRN of SGSN, and the context that self preserves is sent to new MME; New MME is according to the UE context of the updating context this locality of being received, and preserves the SGSN_CRN that is received;

Step 1706:SGSN returns one to old MME and does not comprise the contextual information of UE, and old MME is sent to new MME with context and the SGSN_CRN that self preserves; New MME preserves context and the SGSN_CRN that is received; Described information can for: in context response information, return a null message, perhaps the SGSN_CRN that old MME is sent is returned to old MME again, perhaps other predetermined content etc., the present invention is not further qualified the particular content and the form of described information.

Step 1707: carry out other flow process, as authentication, flow processs such as information updating.

If the context of UE in new MME upgrades to some extent, then new MME upgrades the MME_CRN that self preserves, and the SGSN_CRN that new MME preserves then remains unchanged.

Present embodiment can also adopt flow process as shown in figure 18, comprises the steps:

Step 1801:UE sends the request of access to the new MME at the present place of UE, and this request can be RAU request, register requirement, page response etc.;

Step 1802: new MME sends context request to the old at the original place of UE MME;

Step 1803:old MME sends to new MME and carries the UE context self preserved and the context response information of SGSN_CRN;

Step 1804: new MME sends context request to SGSN, also carries the SGSN_CRN from old MME in this context request;

Step 1805:SGSN judges whether SGSN_CRN that is received and the SGSN_CRN that self preserves mate, if then execution in step 1806; Otherwise execution in step 1807;

Step 1806:SGSN returns to new MME and does not comprise the contextual information of UE; New MME will be from the context of old MME as the UE latest content, and preserves SGSN_CRN, goes to step 1808;

Step 1807:SGSN is sent to new MME with UE context and the SGSN_CRN that self preserves; New MME will integrate the up-to-date context as UE from the context of old MME with from the context of SGSN, and preserve SGSN_CRN;

Step 1808: carry out other flow process, as authentication, flow processs such as information updating.

If the context of UE in new MME upgrades to some extent, then new MME upgrades the MME_CRN that self preserves.

The 3rd class embodiment of the present invention is: the CRN value of only preserving the UE of this RAT in the RAT entity.After UE inserts a RAT, when the 2nd RAT entity obtains context, carry the CRN that a RAT entity is preserved; The 2nd RAT entity is judged the own CRN that preserves and from which is up-to-date CRN among the CRN of a RAT entity, if the CRN value that oneself is preserved is up-to-date, the CRN that then returns context and self preserve, a RAT entity is accepted context and is preserved the CRN value that the other side sends over; Otherwise the 2nd RAT entity returns null response to a RAT entity.If after UE inserted, the context of UE changed, then a RAT entity changes the CRN that self stores.

It is consistent that this method requires a RAT entity and the 2nd RAT entity to upgrade the algorithm of CRN value, and for example the two all adopts and adds up 1 or 1 the method for successively decreasing at every turn.If the CRN that a RAT entity or the 2nd RAT entity are preserved carries out initialization, then notify the CRN of the 2nd RAT entity or its preservation of RAT entity synchronous initiation.Described initialization is generally that CRN adds up or when being decremented to limiting value, it is become initial value.

Below illustrate realization principle of the present invention.For example the two all uses the method for ascending order:

UE inserts 2G/3G, SGSN carries CRN (supposing CRN=5 among the SGSN) when MME obtains context, MME receives relatively CRN value of request back, if the CRN value of preserving among the MME is 6, MME judges the CRN value (5) that the CRN value (6) of self sends over greater than SGSN, the CRN value that shows self is up-to-date, and MME returns the CRN (6) of context and self reservation so, and the CRN value (6) that SGSN sends over MME is upgraded the CRN value (5) of self;

If SGSN carries CRN (supposing CRN=5 among the SGSN) when MME obtains context), MME receives relatively CRN value of request back, if the CRN value of preserving among the MME is 5, MME judges the CRN value (6) that the CRN value (5) of self sends over less than SGSN, show that the CRN that SGSN sends over is up-to-date, return null response so.

And in above-mentioned second kind of scheme, then need not require the algorithm of renewal CRN value of a RAT entity and the 2nd RAT entity consistent.

With specific embodiment this embodiment is described in detail below.

Embodiment 11: UE adopts the 3rd sets of plan to initiate to insert request and do not change SGSN at the 2G/3G network.

The flow process of present embodiment comprises the steps: as shown in figure 19

Step 1901:UE sends the request of access to SGSN, and this request can be RAU request, register requirement, page response etc.;

Step 1902:SGSN sends the context request message of carrying SGSN_CRN to MME;

Step 1903:MME judges which is up-to-date CRN in SGSN_CRN that is received and the MME_CRN that self preserves, if the MME_CRN that self preserves is up-to-date, then execution in step 1904; Otherwise, then go to step 1905;

UE context and MME_CRN that step 1904:MME preserves this locality are sent to SGSN, and the UE context that SGSN preserves this locality according to the content of being received upgrades, and the MME_CRN that preservation is received is as the SGSN_CRN after upgrading; And go to step 1906;

Step 1905:MME returns one to SGSN and does not comprise the contextual information of UE, this information can for: in the SGSN context response information, return a null message, perhaps MME_CRN is returned to SGSN again, perhaps other predetermined content etc., the present invention is not further qualified the particular content and the form of described information;

Step 1906: carry out other flow process, as authentication, flow processs such as information updating.

If the context of UE in SGSN upgrades to some extent, then SGSN upgrades the SGSN_CRN that self preserves.

Embodiment 12: UE adopts the 3rd sets of plan to initiate to insert request at evolvement network and does not change MME.

The flow process of present embodiment comprises the steps: as shown in figure 20

Step 2001:UE sends the request of access to MME, and this request can be RAU request, register requirement, page response etc.;

Step 2002:MME sends the context request message of carrying MME_CRN to SGSN;

Step 2003:SGSN judges which is up-to-date CRN in MME_CRN that is received and the SGSN_CRN that self preserves, if the SGSN_CRN that self preserves is up-to-date, then execution in step 2004; Otherwise, then go to step 2005;

UE context and SGSN_CRN that step 2004:SGSN preserves this locality are sent to MME, and the UE context that MME preserves this locality according to the content of being received upgrades, and the SGSN_MME that preservation is received is the MME_CRN after upgrading; And go to step 2006;

Step 2005:SGSN returns one to MME and does not comprise the contextual information of UE, this information can for: in the MME context response information, return a null message, perhaps SGSN_CRN is returned to MME again, perhaps other predetermined content etc., the present invention is not further qualified the particular content and the form of described information;

Step 2006: carry out other flow process, as authentication, flow processs such as information updating.

If the context of UE in MME upgrades to some extent, then MME upgrades the MME_CRN that self preserves.

Embodiment 13: UE adopts the 3rd sets of plan to initiate to insert request and change SGSN at the 2G/3G network.

The present embodiment flow process comprises the steps: as shown in figure 21

Step 2101:UE sends the request of access to the new SGSN at the present place of UE, and this request can be RAU request, register requirement, page response etc.;

Step 2102: new SGSN sends the SGSN context request to the old at the original place of UE SGSN;

Step 2103:old SGSN sends the SGSN context request carry the SGSN_CRN that old SGSN preserved to MME;

Step 2104:MME judges whether the MME_CRN that self preserves upgrades than the SGSN_CRN that is received, if then execution in step 2105; Otherwise then execution in step 2106;

UE context and MME_CRN that step 2105:MME preserves this locality are sent to oldSGSN, and old SGSN will be from context and the MME_CRN of MME, and the context that self preserves is sent to new SGSN; New SGSN is according to the UE context of the updating context this locality of being received, and the MME_CRN that preservation is received is the SGSN_CRN after upgrading;

Step 2106:MME returns one to old SGSN and does not comprise the contextual information of UE, and old SGSN is sent to new SGSN with context and the SGSN_CRN that self preserves; New SGSN preserves context and the SGSN_CRN that is received; Described information can for: in the SGSN context response information, return a null message, perhaps the MME_CRN that old SGSN is sent is returned to old SGSN again, perhaps other predetermined content etc., the present invention is not further qualified the particular content and the form of described information.

Step 2107: carry out other flow process, as authentication, flow processs such as information updating.

If the context of UE in new SGSN upgrades to some extent, then new SGSN upgrades the SGSN_CRN. that self preserves

Present embodiment can also adopt flow process as shown in figure 22, comprises the steps:

Step 2201:UE sends the request of access to the new SGSN at the present place of UE, and this request can be RAU request, register requirement, page response etc.;

Step 2202: new SGSN sends the SGSN context request to the old at the original place of UE SGSN;

Step 2203:old SGSN sends to new SGSN and carries the UE context self preserved and the SGSN context response information of SGSN_CRN;

Step 2204: new SGSN sends context request to MME, also carries the SGSN_CRN from old SGSN in this context request;

Step 2205:MME judges which is up-to-date CRN for SGSN_CRN that is received and the MME_CRN that self preserves, if the MME_CRN that self preserves is up-to-date, then execution in step 2207; If the SGSN_CRN that is received is up-to-date, then execution in step 2206;

Step 2206:MME returns to new SGSN and does not comprise the contextual information of UE; New SGSN will be from the context of old SGSN as the UE latest content, and preserves the SGSN_CRN from old SGSN, goes to step 2208;

Step 2207:MME is sent to new SGSN with UE context and the MME_CRN that self preserves; New SGSN will integrate the up-to-date context as UE from the context of old SGSN with from the context of MME, and preserve MME_CRN as the SGSN_CRN after upgrading;

Step 2208: carry out other flow process, as authentication, flow processs such as information updating.

Embodiment 14: UE adopts the 3rd sets of plan to initiate to insert request and change MME at evolvement network.

The present embodiment flow process comprises the steps: as shown in figure 23

Step 2301:UE sends the request of access to the new MME at the present place of UE, and this request can be RAU request, register requirement, page response etc.;

Step 2302: new MME sends context request to the old at the original place of UE MME;

Step 2303:old MME sends the context request carry the MME_CRN that old MME preserved to SGSN;

Step 2304:SGSN judges which is up-to-date CRN for SGSN_CRN that self preserves and the MME_CRN that is received, if the SGSN_CRN that self preserves is up-to-date, then execution in step 2305; Execution in step 2306 if MME_CRN is up-to-date;

UE context and SGSN_CRN that step 2305:SGSN preserves this locality are sent to oldMME, and old MME will be from context and the SGSN_CRN of SGSN, and the context that self preserves is sent to new MME; New MME is according to the UE context of the updating context this locality of being received, and the SGSN_CRN that preservation is received is the MME_CRN after upgrading;

Step 2306:SGSN returns one to old MME and does not comprise the contextual information of UE, and old MME is sent to new MME with context and the MME_CRN that self preserves; New MME preserves context and the MME_CRN that is received; Described information can for: in context response information, return a null message, perhaps the MME_CRN that old MME is sent is returned to old MME again, perhaps other predetermined content etc., the present invention is not further qualified the particular content and the form of described information.

Step 2307: carry out other flow process, as authentication, flow processs such as information updating.

Present embodiment can also adopt flow process as shown in figure 24, comprises the steps:

Step 2401:UE sends the request of access to the new MME at the present place of UE, and this request can be RAU request, register requirement, page response etc.;

Step 2402: new MME sends context request to the old at the original place of UE MME;

Step 2403:old MME sends to new MME and carries the UE context self preserved and the context response information of MME_CRN;

Step 2404: new MME sends context request to SGSN, also carries the MME_CRN from old MME in this context request;

Step 2405:SGSN judges which is up-to-date CRN for MME_CRN that is received and the SGSN_CRN that self preserves, if the SGSN_CRN that self preserves is up-to-date, then execution in step 2407; If the MME_CRN that is received is up-to-date, then execution in step 2406;

Step 2406:SGSN returns to new MME and does not comprise the contextual information of UE; New MME will be from the context of old MME as the UE latest content, and preserves the MME_CRN from old MME, goes to step 2408;

Step 2407:SGSN is sent to new MME with UE context and the SGSN_CRN that self preserves; New MME will integrate the up-to-date context as UE from the context of old MME with from the context of SGSN, and preserve SGSN_CRN as the MME_CRN after upgrading;

Step 2408: carry out other flow process, as authentication, flow processs such as information updating.

In some cases, as user contracting data change, the change of network insertion pattern etc., HSS may need initiatively to revise the context of MME and/or SGSN, in this case, because the positional information of HSS record SGSN and two entities of MME if HSS initiatively revises the data of UE, so directly sends to these two entities and all makes amendment, CRN does not need to change simultaneously, needn't notify UE. yet

The present invention can be used under the various frameworks such as MME/UPE unification or MME/UPE separation.If MME/UPE separates and session management is positioned at UPE, so when the session management context changes is arranged on the UPE, will notify MME so that can preserve user's up-to-date mobile management and session management context in native system among the MME, just can realize the inventive method then according to above any one flow process.Between described MME and the UPE is known technology alternately.

In the flow process of the inventive method, when only in the RAT that the up-to-date context of needs and UE insert at present, not having up-to-date context, just can obtain context, and MME and the SGSN contextual process of push each other needn't occur in the prior art to the entity of another kind of RAT.

The above only is preferred embodiment of the present invention, not in order to restriction the present invention, all any modifications of being done within the spirit and principles in the present invention, is equal to and replaces and improvement etc., all should be included within protection scope of the present invention.

Claims

1. the method for a context negotiation is characterized in that, user equipment (UE) and wireless access technology RAT entity are preserved the context record value CRN about UE respectively, and this method comprises the steps:

C1, a RAT entity obtain the context of described UE to the 2nd RAT entity.

2. method according to claim 1 is characterized in that, a described RAT entity is Serving GPRS Support Node SGSN, and the 2nd RAT entity is mobile management entity or user entity MME/UPE;

Perhaps, a described RAT entity is MME/UPE, and the 2nd RAT entity is SGSN.

3. method according to claim 1 is characterized in that, further comprises before the steps A 1:

4. method according to claim 1 is characterized in that, further comprises after the step C1: a RAT entity changes the context of UE, upgrades the CRN of the described UE that this entity preserves, and notifies described UE to upgrade the CRN of its preservation.

5. method according to claim 4 is characterized in that, the CRN that described notice UE upgrades its preservation comprises following any one situation:

6. method according to claim 1 is characterized in that, further comprises after the step C1: a described RAT entity is set up related with described the 2nd RAT entity.

7. according to each described method of claim 1 to 6, it is characterized in that described UE did not change RAT and do not change and insert entity before steps A, then the entity of described RAT of step B1 is a RAT entity.

8. according to each described method of claim 1 to 6, it is characterized in that before steps A 1, described UE moves to a new RAT entity from a RAT entity at original place, a then described RAT entity is a new RAT entity, and step B1 further comprises:

9. according to each described method of claim 1 to 6, it is characterized in that before steps A 1, described UE moves to a new RAT entity from a RAT entity at original place, then steps A 1 a described RAT entity is new RAT entity;

Step B1 further comprises:

10. the method for a context negotiation is characterized in that, a RAT entity is not only preserved the CRN of this RAT about UE, also preserves the CRN of the 2nd RAT about UE, and this method comprises the steps:

A2, UE send the request of access to a RAT entity;

11. method according to claim 10 is characterized in that, a described RAT entity is Serving GPRS Support Node SGSN, and the 2nd RAT entity is mobile management entity or user entity MME/UPE;

Perhaps, a described RAT entity is MME/UPE, and the 2nd RAT entity is SGSN.

12. method according to claim 10 is characterized in that, this method further comprises: the context changes of UE in the RAT entity, a RAT entity upgrades the CRN of the UE of this RAT that self preserves.

13., it is characterized in that described UE did not change RAT and do not change and insert entity according to claim 10,11 or 12 described methods before steps A 2, then the entity of described RAT of step B2 is a RAT entity.

14. according to claim 10,11 or 12 described methods, it is characterized in that before steps A 2, described UE moves to a new RAT entity from a RAT entity at original place, a then described RAT entity is a new RAT entity, and step B2 further comprises:

15., it is characterized in that before steps A 2, described UE moves to a new RAT entity from a RAT entity at original place according to claim 10,11 or 12 described methods, then steps A 3 described RAT entities are a new RAT entity;

Step B2 further comprises:

16. the method for a context negotiation is characterized in that, the RAT entity is preserved the CRN of UE, and this method comprises the steps:

A3, UE send the request of access to a RAT entity;

17. method according to claim 16 is characterized in that, a RAT entity adopts identical algorithm to upgrade the CRN that self preserves with the 2nd RAT entity.

18. method according to claim 17 is characterized in that, this method further comprises: the CRN that a RAT entity or the 2nd RAT entity are preserved carries out initialization, then notifies the CRN of the 2nd RAT entity or its preservation of RAT entity synchronous initiation.

19. method according to claim 16 is characterized in that, a described RAT entity is SGSN, and the 2nd RAT entity is MME/UPE;

Perhaps, a described RAT entity is MME/UPE, and the 2nd RAT entity is SGSN.

20. method according to claim 16 is characterized in that, this method further comprises: the context changes of UE in the RAT entity, a RAT entity upgrades the CRN of the described UE that self preserves.

21., it is characterized in that described UE did not change RAT and do not change and insert entity according to each described method of claim 16 to 20 before steps A 3, then the entity of described RAT of step B3 is a RAT entity.

22. according to each described method of claim 16 to 20, it is characterized in that before steps A 3, described UE moves to a new RAT entity from a RAT entity at original place, a then described RAT entity is a new RAT entity, and step B3 further comprises:

23., it is characterized in that before steps A 3, described UE moves to a new RAT entity from a RAT entity at original place according to each described method of claim 16 to 20, then steps A 3 described RAT entities are a new RAT entity;

Step B3 further comprises: