CN101483845A

CN101483845A - Bearing updating method, core network mobility management element, user plane entity and system

Info

Publication number: CN101483845A
Application number: CNA2008100003875A
Authority: CN
Inventors: 胡伟华
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2008-01-09
Filing date: 2008-01-09
Publication date: 2009-07-15

Abstract

The invention discloses a bearer update method, which comprises the steps: after a terminal moves to a second access area that does not support conservation signaling ISR, the network in the second access area acquires the latest user plane bearer context from the first access area network that support ISR where UE is accessed last time and then updates. The invention further discloses a corresponding core network mobile management network element, a user plane entity and a system. When the UE moves to the second access area that does not support ISR, the method ensures the user plane bearer context information updating in the second access area network to be the latest.

Description

Bearing updating method and core network mobility management element, user entity, system

Technical field

The present invention relates to the mobile communication network technology field, particularly a kind of bearing updating method and core network mobility management element, user entity, system.

Background technology

3GPP is in order to strengthen the competitiveness of future network, studying a kind of brand-new evolvement network, its system architecture diagram as shown in Figure 1, UMTS Terrestrial radio access network (the E-UTRAN that comprises evolution, Evolved UMTS Terrestrial Radio Access Network), be used to realize all and the wireless function associated of evolvement network; Mobile management network element (MME, Mobility Management Entity) is responsible for the mobile management of chain of command, comprises the management of user's context and mobile status, distributing user temporary identity sign etc.; Service gateway entity (Serving GW, Serving Gateway) is the user's face anchor point between different access networks in the 3GPP, the interface of the inner different access networks of shielding 3GPP; Grouped data network gateway entity (PDN GW, Packet Data Network Gateway) is the user's face anchor point between 3GPP access network and the non-3 GPP access network network and the interface of external packet data network (PDN, Packet Data Network)."Policy and Charging Rules Function entity (PCRF, Policy and Charging Rule Function) is used for policy control decision and flow based charging controlled function.Home network server (HSS, Home SubscriberServer) is used for storing user subscription information.

UMTS Terrestrial radio access network (UTRAN, UMTS Terrestrial Radio AccessNetwork), GSM EDGE Radio Access Network (GERAN, GSM/EDGE Radio AccessNetwork), be used for realizing all and the wireless function associated of existing GPRS/UMTS network.Service universal grouping wireless business supporting node (SGSN, Serving GPRS Supporting Node) is used for realizing functions such as GPRS/UMTS network routing forwarding, mobile management, session management and user profile storage.

Non-3GPP IP access network (Non-3GPP IPAccess), it mainly is the access network of some non-3GPP tissue definition, as WLAN (wireless local area network) (WLAN, Wireless Local Area Network), micro-wave access global inter communication (Wimax, Worldwide Interoperability for Microwave Access), code division multiple access inserts networks such as (CDMA, Code Division Multiple Access).

Need to prove that above-mentioned framework does not also mean that final SAE system architecture, final framework may with this framework difference to some extent, do not limit here.

In the overlapping or adjacent areas of different 3GPP inserting technology networks, portable terminal (UserEquipment, UE) change connecting system at every turn, such as from GERAN/UTRAN (2G/3G overlay area) to EUTRAN (LTE overlay area), perhaps from EUTRAN to GERAN/UTRAN, all need to initiate more new technological process of position.Position more new technological process can be given core net and eat dishes without rice or wine to bring certain load.For reduce even avoid above-mentioned signaling traffic load as far as possible, and the mobility management mechanism between the optimization 3GPP different access systems, 3GPP has proposed ISR characteristic (Idle mode signalling reduction, saving signaling or limitation signaling, its main purpose are to reduce the mobile management flow process of UE between different access networks).Its main thought is: after UE is registered in SGSN and MME successively, if successfully enabled ISR, route district RA (the Routing Area at place when as long as terminal is not left its registration SGSN and MME, the several that zone under the SGSN administration is divided into is by the district) and tracking area TA (Tracing Area, be some tracking areas that the zone under the MME administration is divided into), and the change of user plane bearer does not take place, just do not need to initiate more new technological process of any position, even UE constantly changes like this, can not bring any signaling traffic load between 2G/3G and LTE sub-district yet.Even the RA at UE place or TA change, only otherwise change SGSN and MME, do not need to set up new registration procedure SGSN or MME to HSS yet.

UE has enabled ISR mechanism under idle condition after, even enter into activated state in certain connecting system A (among above-mentioned GERAN/UTRAN and the EUTRAN a kind of), ISR mechanism did not lose efficacy.If the user is during activated state, under the A connecting system, increase/delete/revised user plane bearer, do not need its user's bearer context in non-current access system B (another kind among above-mentioned GERAN/UTRAN and the EUTRAN) of real-time update yet, when having only the user to change connecting system to B next time, target access system B need be up-to-date with user's bearer context information updating.

Fig. 2 shows the flow chart of above-mentioned mechanism.

As figure, UE successfully adhere to (Attach Procedure) on MME1 after, if be linked into SGSN1, and current system supports will start the ISR activation process, for clear under the situation of ISR mechanism, add before the step with the ISR activation process that A with sign, specifically comprises:

Steps A 1:UE initiates routing update request (Routing Area UpdatingRequest) to SGSN1, carries the S-TMSI that MME1 distributes in this routing update request message.

Steps A 2a:SGSN1 sends context request (Context Request) message and gives MME1, requires to obtain the context that UE preserves on MME1.

Steps A 2b:MME1 returns context response (Context Response) message and gives SGSN1, carries the ability information that MME1 supports ISR in the message.

Steps A 2c:SGSN1 sends context and confirms (Context Acknowledge) message to MME1, and indication ISR enables information in the message.

Steps A 3a:SGSN1 sends more new bearer request (Update Bearer Request) message and gives Serving GW.

Steps A 3b:Serving GW upgrades bearer context, returns more new bearer response (Update BearerResponse) and gives SGSN1.

Steps A 4:SGSN1 and HSS are mutual, completing place registration and subscription data acquisition process (UpdateLocation Procedure).

Steps A 5:SGSN1 issues routing update and accepts (Routing Area Updating Accept) message to UE, comprises the information that newly assigned temporary identity sign P-TMSI of SGSN1 and indication ISR activate in the message.

Steps A 6:UE sends routing update and finishes (Routing Area Updating Complete) message to SGSN1.

UE is in the GERAN/UTRAN system, promptly be linked in the SGSN1, if carrying foundation/modification/deletion has taken place, then the bearer context on UE, SGSN1, Serving GW, the PDN GW (not shown) can be finished corresponding renewal, and the intrasystem MME1 of EUTRAN goes up the bearer context of preserving that does not still still have variation.At this moment, the state that UE can revise S-TMSI is to upgrade, and need initiate bearer update with record when being linked into MME1 following time.

When UE is linked into MME1,, will start the bearer update flow process according to the state of aforementioned S-TMSI.Step in the bearer update flow process is designated the beginning with B, and then the bearer update process comprises as shown in FIG.:

Step B1:UE sends the tracing section updating request message to MME1, carries S-TMSI and P-TMSI in the message, and indication needs more new bearer.

Step B2a:MME1 is according to the indication of UE, and finding needs more new bearer, then sends context request message to SGSN1, the context that acquisition request UE preserves on SGSN1.

Step B2b:SGSN1 returns context response information and gives MME1, carries ability information and bearer context information that SGSN1 supports ISR in the message.

Step B2c:MME1 sends context acknowledgement message to SGSN1, and indication ISR enables information in the message.

Step B3:MME1 issues routing update and accepts message to UE, the information that indication ISR activates.

In research and practice process to prior art, the inventor finds to exist in the prior art following problem:

ISR is not the essential function of 3GPP Rel8 at present, and Rel8 before network do not support ISR, like this, just may have the network of supporting ISR in the future network and not support the network of ISR and the situation of depositing.

If variation has taken place at the bearer context of SGSN1 in UE, the foundation/modification/deletion of carrying has promptly taken place, according to the analysis of front, MME1 can not upgrade in real time synchronously, but is just starting the bearer update flow process when UE is linked into MME1.But UE is before being linked into MME1, when promptly also not being linked into MME1, if UE moves on the MME2 that does not support ISR, because MME2 does not support ISR, MME2 can't discern the synchronous indication in the tracing section updating request message of UE, can tell MME2 to obtain up-to-date bearer context information to the SGSN1 of different access technologies system in the described synchronous indication, MME2 just can not remove to obtain bearer context yet to SGSN1; P-TMSI and Routing Area Identifier (the Routing Area Indentity that provides also can't be provided simultaneously MME2, RAI), sign or the address of the SGSN1 of registration before described RAI can be used to derive, MME2 also just can not learn that SGSN1 obtains bearer context information from the P-TMSI and the RAI that can't discern.And if MME2 obtains bearer context from MME1, then because MME1 does not also upgrade bearer context from SGSN1 this moment, then the bearer context obtained from MME1 of MME2 neither be up-to-date, can cause inconsistent on user plane bearer context on the MME2 and UE, Serving GW, the PDN GW like this, thereby produce unknowable gross error.

For understanding conveniently, the flow chart of above-mentioned situation has been shown among Fig. 3:

Foundation/modification/deletion has taken place in UE under SGSN1, UE revises S-TMSI for upgrading, and writes down when being linked into MME1 following time and need initiate bearer update.

Step 301:UE moves under the MME2, sends the tracing section updating request message to MME2, carry S-TMSI and P-TMSI in the message, and indication needs more new bearer.

Step 302a:MME2 ignores described mobile phone indication because do not support ISR, and the concurrent request message of serving is hereinafter given the MME1 of identical access technology, requires to obtain the context that the user preserves on MME1.

Step 302b:MME1 returns context response information and gives MME2, carries ability information and bearer context information that MME1 supports ISR in the message.The bearer context information here is not the up-to-date bearer context information of UE on SGSN1.

Step 302c:MME2 sends context acknowledgement message to MME1, does not contain indication ISR in the message and enables information.

Step 303:MME2 sends more new bearer request to Serving GW, is not with the ISR indication information, and Serving GW returns and upgrades bearing response message to MME2.

Step 304:Serving GW finds that the more new bearer request of receiving does not contain ISR information, judges the ISR deexcitation, notice SGSN1 ISR deexcitation, and deleting bearing (Delete Bearer), and discharge related resource.

Step 305:MME2 issues routing update and accepts message to UE, and message does not contain the information of indicating ISR.

As seen, among the step 302b, because what MME1 preserved is not up-to-date bearer context information, promptly different with current up-to-date bearer context information on UE and Serving GW, the PDN GW, then MME1 will not be after up-to-date bearer context information returns to MME2, up-to-date bearer context information on MME2 and UE, Serving GW, the PDN GW is inconsistent, thereby will produce unknowable gross error.

Similarly, if UE at the bearer context of MME1 variation has taken place, the foundation/modification/deletion of carrying has taken place promptly, according to the analysis of front, SGSN1 can not upgrade in real time synchronously yet, but is just starting the bearer update flow process when UE is linked into SGSN1.But UE is before being linked into SGSN1, when promptly also not being linked into SGSN1, if UE moves on the SGSN2 that does not support ISR, because SGSN2 does not support ISR, SGSN2 can't discern the synchronous indication in the Routing Area Update request message of UE, tell SGSN2 to obtain up-to-date bearer context information to the MME1 of different access technologies in the described synchronous indication, like this, SGSN2 just can not go to obtain bearer context information yet to MME1; S-TMSI and tracking area identification (the Tracing Area Indentity that provides also can't be provided simultaneously SGSN2, TAI), sign or the address of the MME1 of registration before described TAI can be used to derive, SGSN2 also just can not learn that MME1 obtains bearer context information from the S-TMSI and the TAI that can't discern.And if SGSN2 obtains bearer context from SGSN1, then because SGSN1 does not also upgrade bearer context from MME1 this moment, then the bearer context obtained from SGSN1 of SGSN2 neither be up-to-date, can cause inconsistent on user plane bearer context on the SGSN2 and UE, Serving GW, the PDN GW like this, thereby produce unknowable gross error.Flow chart and Fig. 3 of this situation are similar, no longer repeat at this.

Two kinds of situations to sum up, can obtain, mode according to prior art, move to the network of not supporting ISR for UE from the network of supporting ISR, if this does not support that the network of ISR is different access technology systems with up-to-date bearer context place system, then the situation of bearer context information inconsistency can occur, and then cause occurring unknowable gross error.

Summary of the invention

The purpose of the embodiment of the invention provides a kind of bearing updating method and core network mobility management element, user entity, system, moves to from the network of supporting ISR to guarantee UE that the carrying contextual information is up-to-date behind the network of not supporting ISR.

For solving the problems of the technologies described above, the embodiment of the invention provides a kind of bearing updating method and core network mobility management element, user entity, system to be achieved in that

A kind of bearing updating method comprises:

After terminal moved to and do not support that second of saving signaling ISR inserts the zone, the described second access Local Area Network obtained up-to-date user plane bearer context and renewal from the first access Local Area Network of the support ISR that UE last time inserted.

A kind of bearing updating method comprises:

After terminal moved to and do not support that second of ISR inserts the zone, user entity upgraded the user plane bearer context of the described second access Local Area Network.

A kind of source core network mobility management element of realizing bearer update, this source core network mobility management element comprises the core network mobility management element of the support ISR that UE last time inserted, comprises the request receiving element, the bearer context acquiring unit, the bearer context transmitting element, wherein

The request receiving element is used for the acquisition request bearer context information that receiving target side core network mobility management element is sent; Described target side core network mobility management element comprises the core network mobility management element of not supporting ISR that inserts after the terminal UE;

The bearer context acquiring unit is used for obtaining bearer context information from gateway, or by the inquiry service gateway, the core network mobility management element from the source different access technologies obtains bearer context information then; Described source core network mobility management element comprises core network mobility management element that UE last time inserted and support ISR;

The bearer context transmitting element is used to send described bearer context information to the target side core network mobility management element.

The request receiving element is used for the acquisition request bearer context information that receiving target side core network mobility management element is sent; Described target side core network mobility management element comprises the core network mobility management element of not supporting ISR that inserts after the UE;

The bearer context acquiring unit is used for obtaining bearer context information from the core network mobility management element of different access technologies;

A kind of gateway of realizing bearer update comprises the request receiving element, updating block, wherein,

The request receiving element is used for the request of the renewal bearer context chain of command information that receiving target side core network mobility management element sends;

Updating block is used for the bearer context on the target side core network mobility management element is updated to up-to-date bearer context.

A kind of system that realizes bearer update comprises the source core network mobility management element, the target side core network mobility management element, wherein,

The target side core network mobility management element is not supported ISR, and is used to provide terminal to insert; Also be used for obtaining up-to-date user plane bearer context from the source core network mobility management element;

The source core network mobility management element is used to send the up-to-date user plane bearer context of preservation to the target side core network mobility management element.

A kind of system that realizes bearer update comprises target side core network mobility management element and user entity, wherein,

The target side core network mobility management element is not supported ISR, and is used to provide terminal to insert;

User entity is used to upgrade the user plane bearer context of described target side core network mobility management element.

The technical scheme that is provided by the above embodiment of the invention as seen, after UE moves to and does not support that second of ISR inserts the zone, described second access network last time inserted from UE and first access zone support ISR obtains the user plane bearer context and upgrades, thereby can keep the bearer context information on each network element of terminal and network consistent, all be up-to-date.

Description of drawings

Fig. 1 is the system architecture diagram of a kind of evolvement network in the prior art;

Fig. 2 is the flow chart of ISR mechanism in the prior art;

Fig. 3 is for causing the signaling time-sequence figure of the inconsistent a kind of situation of bearer context in the prior art;

Fig. 4 is the flow chart of the inventive method first embodiment;

Fig. 5 is the signaling time-sequence figure of the inventive method first embodiment;

Fig. 6 is the flow chart of the inventive method second embodiment;

Fig. 7 is the signaling time-sequence figure of the inventive method second embodiment;

Fig. 8 is the flow chart of the inventive method the 3rd embodiment;

Fig. 9 is the signaling time-sequence figure of the inventive method the 3rd embodiment;

Figure 10 is the flow chart of the inventive method the 4th embodiment;

Figure 11 is the signaling time-sequence figure of the inventive method the 4th embodiment;

Figure 12 is the signaling time-sequence figure of the inventive method the 4th another situation of embodiment;

Figure 13 is the flow chart of the inventive method the 5th embodiment;

Figure 14 is the signaling time-sequence figure of the inventive method the 5th embodiment;

Figure 15 is the signaling time-sequence figure of the inventive method the 5th another situation of embodiment;

Figure 16 is the flow chart of the inventive method the 6th embodiment;

Figure 17 is the signaling time-sequence figure of the inventive method the 6th embodiment;

Figure 18 is the signaling time-sequence figure of the inventive method the 6th another situation of embodiment;

Figure 19 is the block diagram of the source MME embodiment of the inventive method first embodiment correspondence;

Figure 20 is the block diagram of the source MME embodiment of the inventive method the 3rd embodiment correspondence;

Figure 21 is the block diagram of the source SGSN embodiment of the inventive method first and the 3rd embodiment correspondence;

Figure 22 is the block diagram of the source SGSN embodiment of the inventive method the 4th embodiment correspondence;

Figure 23 is the block diagram of the source SGSN embodiment of the inventive method the 6th embodiment correspondence;

Figure 24 is the block diagram of the source MME embodiment of the inventive method the 4th and the 6th embodiment correspondence;

Figure 25 is the block diagram of the source SGSN embodiment of the inventive method second and the 5th embodiment correspondence.

Embodiment

The embodiment of the invention provides a kind of bearing updating method and core network mobility management element, user entity, system.

In order to make those skilled in the art person understand the present invention program better, the embodiment of the invention is described in further detail below in conjunction with drawings and embodiments.

Below introduce first embodiment of the inventive method.

Fig. 4 shows the flow chart of the inventive method first embodiment, as figure, comprising:

After step 401:UE is registered in a MME and a SGSN who supports ISR, activate ISR, and the foundation/deletion/modification of carrying takes place in UE on a SGSN.

The one MME and a SGSN are responsible for the core network mobility management, but administer the Access Network of different access technologies respectively, are called first core network mobility management element here.Correspondingly, the 2nd MME, the 2nd SGSN are called second core network mobility management element.Below also similar.

Step 402:UE moves on the 2nd MME that does not support ISR, to the 2nd MME initiating updating of tracking area request.

This step 501 in can corresponding following signaling time-sequence figure.

Step 403: the 2nd MME sends acquisition request bearer context information to the MME.

This step 502 in can corresponding following signaling time-sequence figure.

Step 404: a MME obtains bearer context information from Serving GW, or by inquiry Serving GW, obtains bearer context information from a SGSN then, and described bearer context information is returned the 2nd MME.

This step 503～506 in can corresponding following signaling time-sequence figure.

Afterwards, can also comprise step 405: the 2nd MME and Serving GW are alternately to upgrade bearer context information.

This step 507 in can corresponding following signaling time-sequence figure.

Afterwards, can also comprise step 406: the 2nd MME and HSS are alternately to carry out position updating process.

This step 508 in can corresponding following signaling time-sequence figure.

Can also comprise that Serving GW notifies a SGSN to discharge resource.

This step 509～510 in can corresponding following signaling time-sequence figure.

Fig. 5 shows the signaling time-sequence figure of the inventive method first embodiment, as figure, comprising:

After UE is registered in the MME1 (MME above corresponding) and SGSN1 (SGSN above corresponding) that supports ISR, activate ISR, and the foundation/deletion/modification of carrying has taken place in UE under SGSN1, and UE revises S-TMSI for not upgrading, and remembers and need upgrade.

501:UE moves under the MME2 (the 2nd MME above corresponding), sends the tracing section updating request message to MME2, carry S-TMSI and P-TMSI in the message, and indication needs more new bearer.

502:MME2 sends context request message to MME1, requires to obtain the context that the user preserves on MME1.

503a: there are two kinds of possible modes in this step:

I) context request message sent according to the MME2 that receives of MME1 judges that MME2 does not support ISR, sends bearer context and obtains request to Serving GW.

Here the method for Pan Duaning comprises:

A) GPRS Tunnel Protocol (the GPRS Tunnel Protocol that uses of the context request message of not supporting the core network mobility management element SGSN/MME of ISR to send, GTP) version is different with the context request message that the core network mobility management element SGSN/MME that supports ISR sends, and is older such as version;

B) context request message of supporting the core network mobility management element SGSN/MME of ISR to send need comprise cell and indicates it to support ISR, if therefore context request message does not comprise this indication, the recipient just can think that the transmission requesting party does not support ISR;

C) increase essential cell in the context request message and be used to indicate transmit leg whether to support ISR, the recipient judges according to the value of this cell whether transmit leg supports ISR.

II) MME1 does not judge whether MME2 supports ISR, directly sends bearer context to Serving GW and obtains request message.

503b:Serving GW returns bearer context and obtains response message to MME1, also has two kinds of possible implementations here:

I) comprise the information that to indicate MME1 need remove to upgrade up-to-date bearer context in the message.

II) directly return up-to-date bearer context information in the message.

504a: if Serving GW returns in 503 is the indication of upgrading bearer context, and then MME1 sends bearer context request to SGSN1; Otherwise directly enter step 505.

504b:SGSN1 returns the bearer context response message, comprises user's bearer context information.

Here it should be noted that MME1 obtains the concrete steps that SGSN1 goes up bearer context and also can adopt 3 steps of similar context request, response, affirmation mutual, describe this embodiment here no longer separately.

505:MME1 returns to MME2 with up-to-date bearer context by context response information.

506:MME2 returns context and confirms to reply this MME1.

507a:MME2 is the bearer context Resources allocation that receives, and sends more new bearer request to Serving GW, upgrades bearer context information.

507b:Serving GW preserves the bearer context update content that MME2 sends, and returns more new bearer response.

508:MME2 is initiated to the renewal position process of HSS, and MME2 is registered to HSS, obtains user's subscription data simultaneously.

After 509:Serving GW learnt ISR deexcitation, notice SGSN1 discharged resource.

510:MME2 issues tracing section updating and accepts message to UE, comprises the temporary identity sign S-TMSI of distribution in the message.

Below introduce second embodiment of the inventive method, flow process as shown in Figure 6 comprises:

Step 601,602 is identical with abovementioned steps 401,402 respectively, no longer repeats.Step 602 701 in can corresponding following signaling time-sequence figure wherein.

Step 603: the 2nd MME upgrades in the bearer context information process to Serving GW, and ServingGW returns the indication of user's bearer context of removing the 2nd MME preservation.

Can also comprise between the described step 603 and 602:

The 2nd MME obtains user's bearer context that a MME preserves, and the bearer context Resources allocation for obtaining.

Can also comprise:

Serving GW does not comprise ISR by the renewal loading context information that receives and activates the indication information that comprises indication ISR deexcitation in indication or the message, learns user ISR deexcitation;

The renewal bearing request message content that user's bearer context that Serving GW contrast self is preserved and the 2nd MME send judges that current the 2nd MME goes up whether user's bearer context of preserving is up-to-date and difference, or, judge whether the user's bearer context on current the 2nd MME is up-to-date according to system's classification of the up-to-date bearer context of preserving;

When being up-to-date, carry out the normal process flow process; When not being up-to-date, then, return response according to the difference of up-to-date bearer context and the last bearer context of the 2nd MME, indication MME2 upgrades successfully, perhaps indicates the 2nd MME to remove its local user's bearer context of preserving.

The bearer context that step 604:Serving GW upgrades on the 2nd MME synchronously is up-to-date bearer context.

Afterwards, can also comprise step 605: the 2nd MME and HSS are alternately to carry out position updating process.

This step 706 in can corresponding following signaling time-sequence figure.

Can also comprise that Serving GW notifies a SGSN to discharge resource.

Fig. 7 shows the complete signaling time-sequence figure of the inventive method second embodiment, as figure, comprising:

701:UE moves under the MME2 (the 2nd MME above corresponding), sends the tracing section updating request message to MME2, carry S-TMSI and P-TMSI in the message, and indication needs more new bearer.

702a:MME2 sends context request message to MME1, requires to obtain the context that the user preserves on MME1.

702b:MME1 returns context response information and gives MME2.

702c:MME2 returns context and confirms to reply.

703a:MME2 is the bearer context Resources allocation that receives, and sends more new bearer request to Serving GW, upgrades bearer context information, and does not comprise the information that ISR activates indication or comprises indication ISR deexcitation in this request.

703b:Serving GW does not comprise ISR by the renewal loading context information that receives and activates the indication information that comprises indication ISR deexcitation in indication or the message, then knows user ISR deexcitation.There are two kinds of possible methods in subsequent step:

I) go up consistent respectively user's bearer context if Serving GW has preserved before this with SGSN1 with MME1, can contrast the renewal bearing request message content that MME2 sends, judge whether the user's bearer context on the current MME2 is up-to-date.If up-to-date, normal process then, the information updating of sending according to MME2 is carried hereinafter corresponding information and is returned success response; If not up-to-date, then, return response according to the difference of up-to-date bearer context and the last bearer context of MME2, indication MME2 upgrades successfully, perhaps indicates MME2 to remove its local user's bearer context of preserving.

Such as using cause value, the bearer context that indication MME2 will upgrade does not exist on Serving GW, can these corresponding bearer contexts of deletion after MME2 receives like this.

II) Serving GW has preserved system's classification of up-to-date bearer context before this, judge in view of the above whether the user's bearer context on the current MME2 is up-to-date, if up-to-date, normal process then, the information updating of sending according to MME2 is carried hereinafter corresponding information and is returned success response; If not up-to-date, directly return response, indication MME2 removes its local user's bearer context of preserving.

Do not exist on Serving GW such as the bearer context that can use Reason For Denial value indication MME2 to upgrade, can these corresponding bearer contexts of deletion after then MME2 receives.

704:Serving GW initiates to upgrade synchronously the process of the bearer context on the MME2, the bearer context on the MME2 is updated to up-to-date bearer context, with consistent on Serving GW and the PDN GW.

Here, Serving GW and PDN GW have been the user entity effects.

Here, if among the step 703b before this, that Serving GW carries out is I), then Serving GW can initiate corresponding load creating or modification process; If among the step 703b, that Serving GW carries out is II before this), then Serving GW all initiates the load creating flow process.

705:MME2 is initiated to the renewal position process of HSS, and MME2 is registered to HSS, obtains user's subscription data simultaneously.

After 706:Serving GW learnt ISR deexcitation, notice SGSN1 discharged resource

707:MME2 issues tracing section updating and accepts message to UE, comprises the temporary identity sign S-TMSI of distribution in the message.

Below introduce the 3rd embodiment of the inventive method, flow process as shown in Figure 8 comprises:

After step 801:UE is registered in a MME and a SGSN who supports ISR, activate ISR, and the foundation/deletion/modification of carrying takes place in UE on a SGSN.

Step 802:UE moves on the 2nd MME that does not support ISR, to the 2nd MME initiating updating of tracking area request.

This step 901 in can corresponding following signaling time-sequence figure.

Step 803: the 2nd MME sends acquisition request bearer context information to the MME.

This step 902 in can corresponding following signaling time-sequence figure.

Step 804: a MME obtains bearer context information from a SGSN, and described bearer context information is returned to the 2nd MME.

This step 903～905 in can corresponding following signaling time-sequence figure.

Afterwards, can also comprise step 805: the 2nd MME and Serving GW are alternately to upgrade bearer context information.

This step 906 in can corresponding following signaling time-sequence figure.

Afterwards, can also comprise step 806: the 2nd MME and HSS are alternately to carry out position updating process.

This step 907 in can corresponding following signaling time-sequence figure.

Can also comprise that Serving GW notifies a SGSN to discharge resource.

This step 908～909 in can corresponding following signaling time-sequence figure.

Fig. 9 shows the signaling time-sequence figure of the inventive method the 3rd embodiment, as figure, comprising:

901:UE moves under the MME2 (the 2nd MME above corresponding), sends the tracing section updating request message to MME2, carry S-TMSI and P-TMSI in the message, and indication needs more new bearer.

902:MME2 sends context request message to MME1, requires to obtain the context that the user preserves on MME1.

The context request message that 903a:MME1 sends according to the MME2 that receives judges that MME2 can not support ISR, and the user's of own preservation bearer context may not be up-to-date, then sends bearer context and obtains request to SGSN1, otherwise enter 904.

Here judge that MME2 does not support the method for ISR to comprise:

A) context request message of the GTP version that uses of the context request message of not supporting the core network mobility management element SGSN/MME of ISR to send and the core network mobility management element SGSN/MME transmission of supporting ISR is different, and is older such as version;

903b:SGSN1 returns bearer context and obtains response message to MME1

904:MME1 returns to MME2 with up-to-date bearer context by context response information.

905:MME2 returns context and confirms to reply.

906a:MME2 is the bearer context Resources allocation that receives, and sends more new bearer request to Serving GW, upgrades bearer context information.

906b:Serving GW preserves the bearer context update content that MME2 sends, and returns more new bearer response.

907:MME2 is initiated to the renewal position process of HSS, and MME2 is registered to HSS, obtains user's subscription data simultaneously.

After 908:Serving GW learnt ISR deexcitation, notice SGSN1 discharged resource.

909:MME2 issues tracing section updating and accepts message to UE, comprises the temporary identity sign S-TMSI of distribution in the message.

Said method first to the 3rd embodiment is after UE is registered in a MME and a SGSN who supports ISR, activate ISR, and the foundation/deletion/modification of carrying takes place in UE on a SGSN, UE moves on the 2nd MME that does not support ISR afterwards, to the situation of the 2nd MME initiating updating of tracking area request.

Below introduce fourth embodiment of the invention.

Figure 10 shows the flow chart of the inventive method the 4th embodiment, as figure, comprising:

After step 1001:UE is registered in a MME and a SGSN who supports ISR, activate ISR, and the foundation/deletion/modification of carrying takes place in UE on a MME.

Step 1002:UE moves on the 2nd SGSN that does not support ISR, initiates the Routing Area Update request to the 2nd SGSN.

This step 1101 in can corresponding following signaling time-sequence figure.

Step 1003: the 2nd SGSN sends acquisition request bearer context information to the SGSN.

This step 1102 in can corresponding following signaling time-sequence figure.

Step 1004: a SGSN obtains bearer context information from Serving GW, or by inquiry Serving GW, obtains bearer context information from a MME then, and described bearer context information is returned the 2nd SGSN.

This step 1103～1106 in can corresponding following signaling time-sequence figure.

Afterwards, can also comprise step 1005: the 2nd SGSN and Serving GW are alternately to upgrade bearer context information.

This step 1107 in can corresponding following signaling time-sequence figure.

Afterwards, can also comprise step 1006: the 2nd SGSN and HSS are alternately to carry out position updating process.

This step 1108 in can corresponding following signaling time-sequence figure.

Can also comprise that Serving GW notifies a MME to discharge resource.

This step 1109～1110 in can corresponding following signaling time-sequence figure.

Figure 11 shows the signaling time-sequence figure of the inventive method the 4th embodiment, as figure, comprising:

After UE is registered in the SGSN1 (SGSN above corresponding) and MME1 (MME above corresponding) that supports ISR, activate ISR, and the foundation/deletion/modification of carrying has taken place in UE under MME1, and UE revises P-TMSI for not upgrading, and remembers and need upgrade.

UE is registered in SGSN1 and MME1, enables ISR.

1101:UE moves under the SGSN2 (the 2nd SGSN above corresponding), sends the Routing Area Update request message to SGSN2, carry S-TMSI and P-TMSI in the message, and indication needs more new bearer.

1102:SGSN2 sends context request message to SGSN1, requires to obtain the context that the user preserves on SGSN1.

1103a: there are two kinds of possible methods in this step:

I) context request message sent according to the SGSN2 that receives of SGSN1 judges that SGSN2 can not support ISR, sends bearer context and obtains request to Serving GW.

Here the method for Pan Duaning comprises:

II) SGSN1 does not judge whether SGSN2 supports ISR, directly sends bearer context to Serving GW and obtains request message;

1103b:Serving GW returns bearer context and obtains response message to SGSN1, also has two kinds of possible implementation methods here:

I) comprise the information that to indicate SGSN1 need remove to upgrade up-to-date bearer context in the message

II) directly return up-to-date bearer context information in the message

1104a: if in 1103, what Serving GW returned is the indication of upgrading bearer context, and then SGSN1 sends bearer context request to MME1, otherwise directly enters step 1105.

1104b:MME1 returns the bearer context response message, comprises user's bearer context information.

Here it should be noted that SGSN1 obtains the concrete steps that MME1 goes up bearer context and also can adopt 3 steps of similar context request, response, affirmation mutual.

1105:SGSN1 returns to SGSN2 with up-to-date bearer context by context response information.

1106:SGSN2 returns context and confirms to reply.

1107a:SGSN2 is the bearer context Resources allocation that receives, and sends more new bearer request to Serving GW.

1107b:Serving GW preserves the bearer context update content that SGSN2 sends, and returns more new bearer response.

1108:SGSN2 is initiated to the renewal position process of HSS, and SGSN2 is registered to HSS, obtains user's subscription data simultaneously.

After 1109:Serving GW learnt ISR deexcitation, notice MME1 discharged resource

1110:SGSN2 issues Routing Area Update and accepts message to UE, comprises the temporary identity sign P-TMSI of distribution in the message.

Need to prove,, be compatible Rel8 Previous System according to current standard, during SGSN2 before UE moves to Rel8, in 1105, SGSN1 returns to that all relate to the corresponding information of Serving GW in the bearer context of SGSN2, can all replace with PDN GW information.Like this under this scene, after this 1107 in the reciprocal process of SGSN2 and Serving GW, actual is the reciprocal process of SGSN2 and PDN GW.

As shown in figure 12, among the 1207a, SGSN2 is the bearer context Resources allocation that receives, and sends more new bearer request to PDNGW, upgrades bearer context information.

Among the 1207b, PDN GW preserves the bearer context update content that SGSN2 sends, and returns more new bearer response.

Similar among other signaling and Figure 11.

Below introduce the 5th embodiment of the inventive method, flow process as shown in figure 13 comprises:

Step

1301,1302 is identical with

abovementioned steps

1001,1002 respectively, no longer repeats.Step 1302 1401 in can corresponding following signaling time-sequence figure wherein.

Step 1303: the 2nd SGSN upgrades in the bearer context information process to Serving GW, and ServingGW returns the indication of user's bearer context of removing the 2nd SGSN preservation.

Can also comprise between the described step 1303 and 1302:

The 2nd SGSN obtains user's bearer context that a SGSN preserves, and the bearer context Resources allocation for obtaining.

Can also comprise:

The renewal bearing request message content that user's bearer context that Serving GW contrast self is preserved and the 2nd SGSN send judges that current the 2nd SGSN goes up whether user's bearer context of preserving is up-to-date and difference, or, judge whether the user's bearer context on current the 2nd SGSN is up-to-date according to system's classification of the up-to-date bearer context of preserving;

When being up-to-date, carry out the normal process flow process; When not being up-to-date, then, return response according to the difference of up-to-date bearer context and the last bearer context of the 2nd MME, indication MME2 upgrades successfully, perhaps indicates the 2nd SGSN to remove its local user's bearer context of preserving.

The bearer context that step 1304:Serving GW upgrades on the 2nd SGSN synchronously is up-to-date bearer context.

Afterwards, can also comprise step 1305: the 2nd SGSN and HSS are alternately to carry out position updating process.

This step 1406 in can corresponding following signaling time-sequence figure.

Can also comprise that Serving GW notifies a MME to discharge resource.

Figure 14 shows the complete signaling time-sequence figure of the inventive method the 5th embodiment, as figure, comprising:

After UE is registered in the MME1 (MME above corresponding) and SGSN1 (SGSN above corresponding) that supports ISR, activate ISR, and the foundation/deletion/modification of carrying has taken place in UE under MME1, and UE revises P-TMSI for not upgrading, and remembers and need upgrade.

1401:UE moves under the SGSN2 (the 2nd SGSN above corresponding), sends the Routing Area Update request message to SGSN2, carry S-TMSI and P-TMSI in the message, and indication needs more new bearer.

1402a:SGSN2 sends context request message to SGSN1, requires to obtain the context that the user preserves on SGSN1.

1402b:SGSN1 returns context response information and gives SGSN2, comprising the user plane bearer context of SGSN1 preservation.

1402c:SGSN2 returns context and confirms to reply.

1403a:SGSN2 is the bearer context Resources allocation that receives, and sends more new bearer request to Serving GW, upgrades bearer context information, and does not comprise the information that ISR activates indication or comprises indication ISR deexcitation in this request.

1403b:Serving GW does not comprise ISR by the renewal loading context information that receives and activates the indication information that comprises indication ISR deexcitation in indication or the message, then knows user ISR deexcitation.There are two kinds of possible methods in subsequent step:

I) go up consistent respectively user's bearer context if Serving GW has preserved before this with MME1 with SGSN1, can contrast the renewal bearing request message content that SGSN2 sends, judge whether the user's bearer context on the current SGSN2 is up-to-date.If up-to-date, normal process then, the information updating of sending according to SGSN2 is carried hereinafter corresponding information and is returned response; If not up-to-date, then, return response according to the difference of up-to-date bearer context and the last bearer context of SGSN2, indication SGSN2 upgrades successfully, perhaps indicates SGSN2 to remove its local user's bearer context of preserving.

Such as using cause value, the bearer context that indication SGSN2 will upgrade does not exist on Serving GW, can these corresponding bearer contexts of deletion after SGSN2 receives like this.

II) Serving GW has preserved system's classification of up-to-date bearer context before this, judge in view of the above whether the user's bearer context on the current SGSN2 is up-to-date, if up-to-date, normal process then, the information updating of sending according to SGSN2 is carried hereinafter corresponding information and is returned success response; If not up-to-date, directly return response, indication SGSN2 removes its local user's bearer context of preserving.

Do not exist on Serving GW such as the bearer context that can use Reason For Denial value indication SGSN2 to upgrade, can these corresponding bearer contexts of deletion after then SGSN2 receives.

1404:Serving GW initiates to upgrade synchronously the process of the bearer context on the SGSN2, the bearer context on the SGSN2 is updated to up-to-date bearer context, with consistent on Serving GW and the PDN GW.

Here, if among the step 1403b before this, that Serving GW carries out is I), then Serving GW can initiate corresponding load creating or modification process; If among the step 1403b, that Serving GW carries out is II before this), then Serving GW all initiates the load creating flow process.

1405:SGSN2 is initiated to the renewal position process of HSS, and SGSN2 is registered to HSS, obtains user's subscription data simultaneously.

After 1406:Serving GW learnt ISR deexcitation, notice MME1 discharged resource

1407:SGSN2 issues Routing Area Update and accepts message to UE, comprises the temporary identity sign P-TMSI of distribution in the message.

Need to prove,, be compatible Rel8 Previous System according to current standard, during SGSN2 before UE moves to Rel8,1402b, SGSN1 return to that all relate to the corresponding information of Serving GW in the bearer context of SGSN2, can all replace with PDN GW information.Like this under this scene, after this reciprocal process of SGSN2 and Serving GW in 1403 and 1404 in the step, actual is the reciprocal process of SGSN2 and PDN GW, certainly in such cases, PDN GW also needs the ISR that preserves the user whether to enable information, and can be by the renewal loading context information of receiving, judge user's whether deexcitation of ISR.

As shown in figure 15:

1503a:SGSN2 is the bearer context Resources allocation that receives, and sends more new bearer request to PDN GW, upgrades bearer context information.

1503b:PDN GW does not comprise ISR by the renewal loading context information that receives and activates the indication information that comprises indication ISR deexcitation in indication or the message, then knows user ISR deexcitation.There are two kinds of possible methods in subsequent step:

I) go up consistent respectively user's bearer context if PDN GW has preserved before this with SGSN1 with MME1, can contrast the renewal bearing request message content that SGSN2 sends, judge whether the user's bearer context on the current SGSN2 is up-to-date.If up-to-date, then normal process is carried hereinafter corresponding information according to the information updating that SGSN2 sends; If not up-to-date, then, return response according to the difference of up-to-date bearer context and the last bearer context of SGSN2, indication SGSN2 upgrades successfully, perhaps indicates SGSN2 to remove its local user's bearer context of preserving.(such as using cause value, the bearer context that indication SGSN2 will upgrade does not exist on PDN GW, and SGSN2 will delete these corresponding bearer contexts naturally like this.)

II) PDN GW has preserved system's classification of up-to-date bearer context before this, judge in view of the above whether the user's bearer context on the current SGSN2 is up-to-date, if up-to-date, normal process then, the information updating of sending according to SGSN2 is carried hereinafter corresponding information and is returned success response; If not up-to-date, directly return response, indication SGSN2 removes its local user's bearer context of preserving.(do not exist on PDN GW such as the bearer context that uses Reason For Denial value indication SGSN2 to upgrade, then SGSN2 can delete these corresponding bearer contexts naturally.)

1504:PDN GW initiates to upgrade synchronously the process of the bearer context on the SGSN2, the bearer context on the SGSN2 is updated to up-to-date bearer context, with consistent on the PDN GW.Here, if before this among the step 3b, that PDN GW carries out is I), then PDN GW can initiate corresponding load creating or modification process; If among the step 1503b, that PDN GW carries out is II before this), then PDN GW all initiates the load creating flow process.

Similar among other signaling and Figure 14.

Below introduce the 6th embodiment of the inventive method, flow process as shown in figure 16 comprises:

After step 1601:UE is registered in a MME and a SGSN who supports ISR, activate ISR, and the foundation/deletion/modification of carrying takes place in UE on a MME.

Step 1602:UE moves on the 2nd SGSN that does not support ISR, initiates the Routing Area Update request to the 2nd SGSN.

This step 1701 in can corresponding following signaling time-sequence figure.

Step 1603: the 2nd SGSN sends acquisition request bearer context information to the SGSN.

This step 1702 in can corresponding following signaling time-sequence figure.

Step 1604: a SGSN obtains bearer context information from a MME, and described bearer context information is returned to the 2nd SGSN.

This step 1703～1705 in can corresponding following signaling time-sequence figure.

Afterwards, can also comprise step 1605: the 2nd SGSN and Serving GW are alternately to upgrade bearer context information.

This step 1706 in can corresponding following signaling time-sequence figure.

Afterwards, can also comprise step 1606: the 2nd MME and HSS are alternately to carry out position updating process.

This step 1707 in can corresponding following signaling time-sequence figure.

Can also comprise that Serving GW notifies a SGSN to discharge resource.

This step 1708～1709 in can corresponding following signaling time-sequence figure.

Figure 17 shows the signaling time-sequence figure of the inventive method the 6th embodiment, as figure, comprising:

1701:UE moves under the SGSN2, sends the Routing Area Update request message to SGSN2, carry S-TMSI and P-TMSI in the message, and indication needs more new bearer.

1702:SGSN2 sends context request message to SGSN1, requires to obtain the context that the user preserves on SGSN1.

The context request message that 1703a:SGSN1 sends according to the SGSN2 that receives judges that SGSN2 can not support ISR, and the user's of own preservation bearer context may not be up-to-date, then sends bearer context and obtains request to MME1, otherwise enter step 4.

Here judge that target SGSN 2 do not support the method for ISR to comprise:

1703b:MME1 returns bearer context and obtains response message to SGSN1, also has two kinds of possible implementation methods here:

Here it should be noted that SGSN1 obtains the concrete steps that MME1 goes up bearer context and also can adopt 3 steps of similar context request, response, affirmation mutual, describe this embodiment here no longer separately.

1704:SGSN1 returns to SGSN2 with up-to-date bearer context by context response information.

1705:SGSN2 returns context and confirms to reply.

1706a:SGSN2 is the bearer context Resources allocation that receives, and sends more new bearer request to Serving GW, upgrades bearer context information.

1706b:Serving GW preserves the bearer context update content that SGSN2 sends, and returns more new bearer response.

1707:SGSN2 is initiated to the renewal position process of HSS, and SGSN2 is registered to HSS, obtains user's subscription data simultaneously.

After 1708:ServingGW learnt ISR deexcitation, notice MME1 discharged resource

1709:SGSN2 issues Routing Area Update and accepts message to UE, comprises the temporary identity sign P-TMSI of distribution in the message.

Need to prove,, be compatible Rel8 Previous System according to current standard, during SGSN2 before UE moves to Rel8, step 4, SGSN1 returns to that all relate to the corresponding information of Serving GW in the bearer context of SGSN2, can all replace with PDN GW information.Like this under this scene, the reciprocal process of 6SGSN2 and Serving GW in the step after this, actual is the reciprocal process of SGSN2 and PDN GW.

As shown in figure 18, among the 1806a, SGSN2 is the bearer context Resources allocation that receives, and sends more new bearer request to PDNGW, upgrades bearer context information.

Among the 1806b, PDN GW preserves the bearer context update content that SGSN2 sends, and returns more new bearer response.

Below introduce the source MME embodiment of the inventive method first embodiment correspondence, Figure 19 shows the block diagram of this embodiment, as scheming:

A kind of source MME that realizes bearer update, this source MME comprise MME that UE last time inserted and support ISR, comprise request receiving element 191, bearer context acquiring unit 192, and bearer context transmitting element 193, wherein,

Request receiving element 191 is used for the acquisition request bearer context information that receiving target side MME sends; Described target side MME comprises the MME that does not support ISR that inserts after the UE;

Bearer context acquiring unit 192 is used for obtaining bearer context information from gateway, or by the inquiry service gateway, obtains bearer context information from source SGSN then; Described source SGSN comprises SGSN that UE last time inserted and support ISR;

Bearer context transmitting element 193 is used to send described bearer context information to target side MME.

The context request message that the described request receiving element also is used for sending according to the target side MME that receives judges that target side MME does not support ISR.

Below introduce the source MME embodiment of the inventive method the 3rd embodiment correspondence, Figure 20 shows the block diagram of this embodiment, as scheming:

A kind of source MME that realizes bearer update, this source MME comprise MME that UE last time inserted and support ISR, comprise request receiving element 201, bearer context acquiring unit 202, and bearer context transmitting element 203, wherein,

Request receiving element 201 is used for the acquisition request bearer context information that receiving target side MME sends; Described target side MME comprises the MME that does not support ISR that inserts after the UE;

Bearer context acquiring unit 202 is used for obtaining bearer context information from the SGSN of source;

Bearer context transmitting element 203 is used to send described bearer context information to target side MME.

Below introduce the source SGSN embodiment of the inventive method first and the 3rd embodiment correspondence, Figure 21 shows the block diagram of this embodiment, as scheming:

A kind of source SGSN that realizes bearer update, this source SGSN comprise SGSN that UE last time inserted and support ISR, comprise request receiving element 211, bearer context transmitting element 212, wherein,

Request receiving element 211 is used to receive the request of obtaining bearer context;

Bearer context transmitting element 212 is used for sending bearer context according to the request of sending.

Below introduce the source SGSN embodiment of the inventive method the 4th embodiment correspondence, Figure 22 shows the block diagram of this embodiment, as scheming:

A kind of source SGSN that realizes bearer update, this source SGSN comprise SGSN that UE last time inserted and support ISR, comprise request receiving element 221, bearer context acquiring unit 222, and bearer context transmitting element 223, wherein,

Request receiving element 221 is used for the acquisition request bearer context information that receiving target side SGSN sends; Described target side SGSN comprises the SGSN that does not support ISR that inserts after the UE;

Bearer context acquiring unit 222 is used for obtaining bearer context information from gateway, or by the inquiry service gateway, obtains bearer context information from source MME then; Described source MME comprises MME that UE last time inserted and support ISR;

Bearer context transmitting element 223 is used to send described bearer context information to target side MME.

The context request message that the described request receiving element also is used for sending according to the target side SGSN that receives judges that target side SGSN does not support ISR.

Below introduce the source SGSN embodiment of the inventive method the 6th embodiment correspondence, Figure 23 shows the block diagram of this embodiment, as scheming:

A kind of source SGSN that realizes bearer update, this source SGSN comprise SGSN that UE last time inserted and support ISR, comprise request receiving element 231, bearer context acquiring unit 232, and bearer context transmitting element 233, wherein,

Request receiving element 231 is used for the acquisition request bearer context information that receiving target side SGSN sends; Described target side SGSN comprises the SGSN that does not support ISR that inserts after the UE;

Bearer context acquiring unit 232 is used for obtaining bearer context information from the MME of source;

Bearer context transmitting element 233 is used to send described bearer context information to target side SGSN.

Below introduce the source MME embodiment of the inventive method the 4th and the 6th embodiment correspondence, Figure 24 shows the block diagram of this embodiment, as scheming:

A kind of source MME that realizes bearer update, this source MME comprise MME that UE last time inserted and support ISR, comprise request receiving element 241, bearer context transmitting element 242, wherein,

Request receiving element 241 is used to receive the request of obtaining bearer context;

Bearer context transmitting element 242 is used for sending bearer context according to the request of sending.

Below introduce the source SGSN embodiment of the inventive method second and the 5th embodiment correspondence, Figure 25 shows the block diagram of this embodiment, as scheming:

A kind of gateway of realizing bearer update comprises request receiving element 251, updating block 252, wherein,

Request receiving element 251 is used for the request of the renewal bearer context information that receiving target side MME or SGSN send;

Updating block 252 is used for the bearer context on target side MME or the SGSN is updated to up-to-date bearer context.

Described gateway also comprises request-response unit 253, is used to indicate target side MME or SGSN to remove its local user's bearer context of preserving.

Below introduce system embodiment of the present invention.

As previously mentioned, core network mobility management element comprises MME and/or SGSN, and user entity comprises SGW and/or PGW.

By above embodiment as seen, after UE moves to and does not support that second of ISR inserts the zone, the described second first access Local Area Network that inserts that Local Area Network last time inserted from UE and support ISR obtains the user plane bearer context and upgrades, thereby can keep the bearer context information on each network element of terminal and network consistent.

Though described the embodiment of the invention by embodiment, those of ordinary skills know, the present invention has many distortion and variation and do not break away from spirit of the present invention, wish that appended claim comprises these distortion and variation and do not break away from spirit of the present invention.

Claims

1, a kind of bearing updating method is characterized in that, comprising:

2, the method for claim 1 is characterized in that, described terminal moves to does not support the second access zone of saving signaling ISR to comprise:

Described terminal moves to the zone of second core network mobility management element covering of not supporting ISR;

Correspondingly, described second insert first of support ISR that Local Area Network last time inserted from terminal and insert Local Area Network and obtain the user plane bearer context and upgrade and comprise:

Second core network mobility management element last time inserted from terminal and first core network mobility management element support ISR obtains up-to-date user plane bearer context and upgrades.

3, method as claimed in claim 2 is characterized in that, described second core network mobility management element last time inserted from terminal and first access Local Area Network support ISR obtains the user plane bearer context and upgrades and comprises:

The acquisition request bearer context information to the first that sends second core network mobility management element inserts first core network mobility management element in the Local Area Network;

First core network mobility management element obtains bearer context information from gateway, or by the inquiry service gateway, after obtaining bearer context information from first core network mobility management element of different access technologies then, described bearer context information is returned second core network mobility management element.

4, method as claimed in claim 2 is characterized in that, described second core network mobility management element last time inserted from terminal and first access Local Area Network support ISR obtains the user plane bearer context and upgrades and comprises:

First core network mobility management element obtains bearer context information from first core network mobility management element of different access technologies, and described bearer context information is returned to second core network mobility management element.

5, method as claimed in claim 4, it is characterized in that, the acquisition request bearer context information to the first that sends described second core network mobility management element inserts after first core network mobility management element in the Local Area Network, and first core network mobility management element also comprised before first core network mobility management element of different access technologies obtains bearer context information:

The context request message that first core network mobility management element is sent according to second core network mobility management element received judges that second core network mobility management element do not support ISR.

6, method as claimed in claim 3 is characterized in that, described first core network mobility management element obtains bearer context information from gateway and comprises:

The context request message that first core network mobility management element is sent according to second core network mobility management element received judges that second core network mobility management element do not support ISR, sends bearer context and obtains request to gateway; Or first core network mobility management element do not judge whether second core network mobility management element supports ISR, directly send bearer context and obtain request message to user entity;

User entity returns up-to-date bearer context information and gives first core network mobility management element.

7, method as claimed in claim 3 is characterized in that, described first core network mobility management element is by the inquiry service gateway, obtains bearer context information from first core network mobility management element of different access technologies then and comprises:

The user entity return messages are given first core network mobility management element, the message content that first core network mobility management element returns according to user entity, and judgement need go to upgrade up-to-date bearer context information;

First core network mobility management element sends first core network mobility management element of bearer context request to different access technologies, first core network mobility management element of different access technologies returns the bearer context response message, comprises user's bearer context information in this message.

8, as each described method in the claim 5 to 7, it is characterized in that the context request message that described first core network mobility management element is sent according to second core network mobility management element of receiving judges that second core network mobility management element do not support that ISR comprises:

According to GPRS Tunnel Protocol version difference, or do not support ISR according to different MME of judgement of context request message or the SGSN that SGSN or MME send; Or,

The context request message that sends according to SGSN or MME does not comprise the cell judgement of supporting ISR and does not support ISR; Or,

Increase is used to indicate transmit leg whether to support the essential cell of ISR in the context request message, judges according to the value of this cell whether source supports ISR.

9, as each described method in the claim 2 to 7, it is characterized in that, described core network mobility management element comprises Mobility Management Entity MME or Serving GPRS Support Node SGSN, and described user entity comprises gateway and/or packet data gateway.

10, a kind of bearing updating method is characterized in that, comprising:

11, method as claimed in claim 10 is characterized in that, described terminal moves to does not support second of ISR to insert after the zone, and user entity upgrades the described second user's bearer context that inserts Local Area Network and also comprises before:

Second second core network mobility management element that inserts Local Area Network upgrades bearer context information to user entity, and in described renewal bearer context information process, described user entity returns the indication of user's bearer context of removing the preservation of second core network mobility management element.

12, method as claimed in claim 11 is characterized in that, described second core network mobility management element also comprises after user entity upgrades bearer context information:

User entity judges that the bearer context that described second core network mobility management element is preserved is not up-to-date.

13, method as claimed in claim 12 is characterized in that, described user entity judges that the bearer context that described second core network mobility management element is preserved is not up-to-date comprising:

The renewal bearing request message content that the user's bearer context that the user entity contrast self is preserved and second core network mobility management element send judges that user's bearer context of preserving on current second core network mobility management element is not up-to-date, or, judge that the bearer context on current second core network mobility management element is not up-to-date according to system's classification of the up-to-date bearer context of preserving.

14, method as claimed in claim 11 is characterized in that, the indication that described user entity returns user's bearer context of removing the preservation of second core network mobility management element comprises:

User entity indicates second core network mobility management element to remove its local user's bearer context of preserving according to the bearer context of self preserving and the difference of the bearer context on second core network mobility management element; Or,

User entity directly returns response, indicates second core network mobility management element to remove user's bearer context of preserving.

15, as each described method in the claim 10 to 14, it is characterized in that, described second core network mobility management element comprises mobile management network element MME or Serving GPRS Support Node SGSN, and described user entity comprises gateway and/or packet data gateway.

16, a kind of source core network mobility management element of realizing bearer update, this source core network mobility management element comprises the core network mobility management element of the support ISR that UE last time inserted, it is characterized in that, comprise the request receiving element, the bearer context acquiring unit, the bearer context transmitting element, wherein

17, a kind of source core network mobility management element of realizing bearer update, this source core network mobility management element comprises the core network mobility management element of the support ISR that UE last time inserted, it is characterized in that, comprise the request receiving element, the bearer context acquiring unit, the bearer context transmitting element, wherein

18, a kind of gateway of realizing bearer update is characterized in that, comprises the request receiving element, updating block, wherein,

The request receiving element is used for the request of the renewal bearer context that receiving target side core network mobility management element sends;

19, a kind of system that realizes bearer update is characterized in that, comprises the source core network mobility management element, the target side core network mobility management element, wherein,

20, a kind of system that realizes bearer update is characterized in that, comprises target side core network mobility management element and user entity, wherein,