CN101094096B

CN101094096B - Mobility management method under architecture of talk network

Info

Publication number: CN101094096B
Application number: CN2006100865401A
Authority: CN
Inventors: 张戬; 郭小龙; 朱志明; 胡伟华
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2006-06-20
Filing date: 2006-06-20
Publication date: 2011-07-20
Anticipated expiration: 2026-06-20
Also published as: CN101094096A

Abstract

The present invention discloses a mobility management method under an evolved network architecture. When it is determined that a user equipment needs to perform anchor point migration, the new anchor point to which the user equipment is to migrate provides communication resources for supporting subsequent communication of the user equipment. The communication resource is usually: a user plane and a communication address for supporting subsequent communication of the user equipment. The method of the present invention avoids the waste of network transmission resources and the increase of communication delay in the prior art in the mobility management process, but saves network transmission resources and effectively reduces communication delay, thereby significantly improving Communication quality of user equipment, thereby significantly improving user satisfaction.

Description

Motion management method under a kind of evolution network framework

Technical field

The present invention relates to the communications field, be specifically related to the motion management method under a kind of evolution network framework.

Background technology

Along with development of Communication Technique, evolution network framework is furtherd investigate gradually; Wherein, a kind of widely accepted evolution network framework as shown in Figure 1, Fig. 1 is the evolution network structure figure of prior art.Among Fig. 1, subscriber equipment (UE) 101 can insert mobile management entity (Mobility Management Entity by Long Term Evolution wireless access network (LTE-RAN) 102, MME) 103, user entity (User Plane Entity, UPE) 104, and anchor point (Anchor) 109 communications that are connected with UPE 104; In like manner, UE 101 can also insert MME 107, UPE 108 by LTE-RAN 102, and Anchor 109 communications that are connected with UPE 108.

Along with moving of UE, UE may move to another service area from professional service area is provided for self; In this case, UE might carry out the MME/UPE reuse adoption process.At non-real-time service and real time business, the MME/UPE reuse adoption process that UE carried out may be different, below by Fig. 2, Fig. 3 the MME/UPE reuse adoption process simply introduced.

Referring to Fig. 2, Fig. 2 is at the MME/UPE reuse adoption process of non-real-time service in the prior art.Among Fig. 2, when the UE 201 that accepts non-real-time service from first service area when second service area moves, UE 201 may insert LTE-RAN entity (Entity) 1, LTE-RAN Entity2, LTE-RAN Entity 3, LTE-RAN Entity 4 or LTE-RAN Entity 5 at diverse location.And when being positioned at first service area, UE 201 can insert MME/UPE 202 by LTE-RAN Entity; And when being positioned at second service area, 201 of UE can insert MME/UPE203 by LTE-RAN Entity.But that no matter UE 201 inserts is MME/UPE 202 or MME/UPE 203, and UE 201 will communicate by letter by the fixing Anchor 204 with being UE 201 services originally by the MME/UPE that it inserted, and can not transfer to communicate by letter with other Anchor.

The situation of communicating by letter that UE 201 fixes with Anchor 204, can cause some communication issues inevitably: along with moving of UE 201, Anchor 204 may no longer be the Anchor that helps UE 201 communications most, as: the route of Anchor 204 to UE 201 no longer is a best route etc.; This obviously can cause the waste of network transmission resource, and the communication delay of UE 201 also can make the communication quality of UE 201 significantly reduce, and then seriously reduce user satisfaction because of the route variation obviously increases.

Referring to Fig. 3, Fig. 3 is at the MME/UPE reuse adoption process of real time business in the prior art.Among Fig. 3, when the UE 301 that accepts real time business from first service area when second service area moves, UE 301 may insert LTE-RAN entity (Entity) 1, LTE-RAN Entity 2, LTE-RAN Entity 3, LTE-RAN Entity 4 or LTE-RAN Entity 5 at diverse location.And when described real time business did not finish as yet, UE 301 can insert all the time in MME/UPE 302; And finish and UE 301 when being positioned at second service area at described real time business, 301 of UE can insert the MME/UPE 303 that be positioned at second service area by LTE-RAN Entity.But that no matter UE 301 inserts is MME/UPE 302 or MME/UPE 303, and UE 301 will communicate by letter by the fixing Anchor 304 with being UE 301 services originally by the MME/UPE that it inserted, and can not transfer to communicate by letter with other Anchor.

With identical at problem that Fig. 2 set forth, the UE 301 fixing situations of communicating by letter with Anchor 304 can cause some communication issues inevitably: along with moving of UE 301, Anchor 304 may no longer be the Anchor that helps UE 301 communications most, as: the route of Anchor 304 to UE 301 no longer is a best route etc.; This obviously can cause the waste of network transmission resource, and the communication delay of UE 301 also can make the communication quality of UE 301 significantly reduce, and then seriously reduce user satisfaction because of the route variation obviously increases.

Summary of the invention

In view of this, main purpose of the present invention is to provide the motion management method under a kind of evolution network framework, to improve the communication quality of UE.

For achieving the above object, technical scheme of the present invention is achieved in that

The invention discloses the motion management method under a kind of evolution network framework, this method comprises:

When definite UE need carry out moving anchor point, the new anchor point that will be moved to by UE was provided for supporting the communication resource of UE subsequent communications,

New anchor point provides the method for the described communication resource to be: new anchor point foundation is used to support user's face of UE subsequent communications, also is used in the mailing address of supporting the UE subsequent communications for UE divides,

The method that new anchor point is set up described user's face is: new anchor point is directly or indirectly mutual with current user entity UPE for the UE service, and foundation is used to user's face of supporting that UE communicates by letter between new anchor point and this user entity UPE.

Described UPE is the UPE of UE service always, or because of take place the UE position upgrade new select provide the UPE of service for UE.

The method that new anchor point is set up described user's face is:

Send the active session context request to current UPE for the UE service; New UPE is that UE distributes the transmission channel resource according to the active session context request of receiving, again the parameter that UE sign, the foundation desired QoS of carrying and new UPE are the gap marker that downlink data distributed of the new anchor point of reception that comprises in this transmission channel resource is sent to new anchor point; The parameter of the gap marker that downlink data distributed that the described UE of comprising sign, the foundation desired QoS of carrying and the new UPE that new anchor point basis is received is the new anchor point of reception is carrying distribution (Internet protocol) IP address and a distribute data transmission channel resource of wanting newly-built.

The parameter that the described UE of comprising sign, the foundation desired QoS of carrying and new UPE are the gap marker that downlink data distributed of the new anchor point of reception is carried on to create in the session context request and sends to new anchor point.

Between new anchor point and the described UPE is to realize for UE provides the MME of service by current alternately.

Described MME is the MME that service is provided for UE always, or because of take place the UE position upgrade new select provide the MME of service for UE.

Determine that the method that UE need carry out moving anchor point is:

According to the moving anchor point information that sets in advance with static mode and/or determine UE with the moving anchor point parameter that dynamical fashion obtains whether needs carry out moving anchor point.

According to described moving anchor point information determine UE whether the needs method of carrying out moving anchor point be:

Set in advance the route metric between the webserver (Network Sever) of serving and each anchor point of linking to each other for UE, and judge whether the Anchor with optimum route metric is current anchor point of communicating by letter with UE, if determine that UE does not need to carry out moving anchor point; Otherwise, determine that UE need carry out moving anchor point.

The anchor point that further will have optimum route metric is defined as the anchor point that UE should be moved to.

According to described moving anchor point parameter determine UE whether the needs method of carrying out moving anchor point be:

Be retrieved as UE service each anchor point that the webserver connected comprise the system resource load state, the state parameter of UE linking number and link circuit resource load state, and each anchor point that will obtain comprises the system resource load state, one or more corresponding comparison the in the state parameter of UE linking number and link circuit resource load state comprises the system resource load state to draw, the state parameter of UE linking number and link circuit resource load state maximum anchor point of preponderating, judge again whether this anchor point is exactly current anchor point of communicating by letter with UE, and determine that UE need carry out moving anchor point for not the time in judged result.

The state parameter that further will comprise system resource load state, UE linking number and link circuit resource load state maximum described anchor point of preponderating is defined as the anchor point that UE should be moved to.

Be retrieved as UE service each anchor point that the webserver connected comprise the system resource load state, the UE linking number, route metric between the state parameter of link circuit resource load state and each anchor point and this webserver, and judgement comprises the system resource load state, whether preponderate maximum anchor points and the route metric between the webserver of the state parameter of UE linking number and link circuit resource load state is lower than the route metric lowest limit that sets in advance, further judge whether this anchor point is exactly current anchor point of communicating by letter with UE in judged result for not the time, and be to determine that UE need carry out moving anchor point when denying in judged result.

The anchor point that the state parameter that further will comprise system resource load state, UE linking number and link circuit resource load state is preponderated at most and route metric is not less than the route metric lowest limit is defined as the anchor point that UE should be moved to.

What obtain each anchor point that the webserver connected of serving for UE comprises the system resource load state, route metric between the state parameter of UE linking number and link circuit resource load state and each anchor point and this webserver, judge the route metric optimum anchor point comprise the system resource load state, the lowest limit state parameter whether state parameter of UE linking number and link circuit resource load state is better than setting in advance, in judged result is further to judge whether this anchor point is exactly current anchor point of communicating by letter with UE when being, and determines that UE need carry out moving anchor point in judged result for not the time.

Further that route metric is optimum and anchor point that state parameter that comprise system resource load state, UE linking number and link circuit resource load state is better than lowest limit state parameter is defined as the anchor point that UE should be moved to.

The operation that this method comprised is triggered by the location area updating process that UE initiates.

Further initiate the UE position updating process to HSS.

What trigger operation that this method comprises is in the described location area updating process, by the location area updating request of UE transmission.

Described anchor point is the 3rd Generation Partnership Project anchor point, or intercommunication connecting system anchor point.

Further deletion UE carries out the UE context that moving anchor point is preserved for the anchor point of UE service before.

Before new anchor point provided the described communication resource, this method further comprised: carry out the authentication process at UE.

Further set up the RAB that is used to support subsequent communications for UE.

The described communication resource comprises the IP address as mailing address, further this IP address is sent to UE by the described RAB of setting up for UE.

Described mailing address is the IP address, further this IP address is carried on location area updating and accepts to send in the message UE.

UE further uses described IP address and registers to the upper strata service network.

Described top service network is internet protocol multimedia subsystem, MSN or Web content service network.

Compared with prior art, motion management method under the evolution network framework provided by the present invention, when definite UE need carry out the Anchor migration, the new Anchor that will be moved to by UE is provided for supporting the communication resource of UE subsequent communications, this communication resource normally: the user's face, the mailing address that are used to support the UE subsequent communications.As seen, the inventive method can obviously improve the communication quality of UE, and then significantly improves user satisfaction.

Description of drawings

Fig. 1 is the evolution network structure figure of prior art;

Fig. 2 is at the MME/UPE reuse adoption process of non-real-time service in the prior art;

Fig. 3 is at the MME/UPE reuse adoption process of real time business in the prior art;

Fig. 4 is a mobile management general flow chart of the present invention;

Fig. 5 is another mobile management general flow chart of the present invention;

Fig. 6 is the mobile management flow chart of the embodiment of the invention 1;

Fig. 7 is the mobile management flow chart of the embodiment of the invention 2;

Fig. 8 is the mobile management flow chart of the embodiment of the invention 3;

Fig. 9 is the mobile management flow chart of the embodiment of the invention 4;

Figure 10 is the mobile management flow chart of the embodiment of the invention 5;

Figure 11 is the mobile management flow chart of the embodiment of the invention 6;

Figure 12 is the mobile management flow chart of the embodiment of the invention 7;

Figure 13 is the mobile management flow chart of the embodiment of the invention 8;

Figure 14 is the mobile management flow chart of the embodiment of the invention 9;

Figure 15 is the mobile management flow chart of the embodiment of the invention 10;

Figure 16 is the mobile management flow chart of the embodiment of the invention 11;

Figure 17 is the mobile management flow chart of the embodiment of the invention 12;

Figure 18 is the mobile management flow chart of the embodiment of the invention 13.

Embodiment

Below in conjunction with drawings and the specific embodiments to the detailed description of the invention.

Motion management method under the evolution network framework provided by the present invention, when definite UE need carry out the Anchor migration, the new Anchor that will be moved to by UE is provided for supporting the communication resource of UE subsequent communications, this communication resource normally: the user's face, the mailing address that are used to support the UE subsequent communications.

Referring to Fig. 4, Fig. 4 is a mobile management general flow chart of the present invention, and this flow process may further comprise the steps:

Step 401:UE uses prior art and initiates location area updating; And access network is that UE selects new Network Sever.

Particularly, UE initiates location area updating to send the location area updating request mode to access network usually; Access network then can be used the present Flex principle of using more widely and select new Network Sever as UE.

Step 402: old Network Sever is to the context (Context) of new Network Sever transfer at UE.

Particularly, new Network Sever can be from from obtaining the sign that UE initiates present position district before the location area updating the location area updating request of UE, and find the address that UE initiates the old Network Sever that registered before this location area updating according to this sign.Based on this, new Network Sever is to the Context transfer request of old Network Sever transmission at UE, comprise in this request grouping-Temporary Mobile Subscriber Identity (P-TMSI) of UE, the sign in UE present position district (Track Area Identifier), TLLI (Temporary Logical Link Identity, TLLI), parameter such as new Network Sever address; When old Network Sever receives the Context transfer request of the Network Sever that makes a fresh start, the Context of UE is sent to new Network Sever.

Step 403: new Network Sever determines that by logic determines UE need carry out the Anchor migration.

In actual applications, new Network Sever can determine UE whether needs carry out Anchor to move according to the moving anchor point information that sets in advance with static mode and/or with the moving anchor point parameter that dynamical fashion obtains.

At described static mode, can in new Network Sever, set in advance the route metric between this Network Sever and continuous each Anchor thereof; Like this, newly Network Sever just can determine and the Anchor that self has optimum route metric, and judges whether this Anchor is the current Anchor that communicates by letter with UE, if new Network Sever determines that UE does not need to carry out the Anchor migration; Otherwise new Network Sever determines that UE need carry out the Anchor migration, and the Anchor that will have an optimum route metric is defined as the Anchor that UE should be moved to.

At described dynamical fashion, new Network Sever can real-time or is periodically obtained the state parameter of each Anchor that links to each other with self, as: the system resource load state, the UE linking number, link circuit resource load state etc., and one or more corresponding in each Anchor state parameter that will obtain relatively to draw state parameter maximum Anchor that preponderates, this Anchor is defined as helping most the Anchor of UE communication, judge again whether this Anchor is exactly the current Anchor that communicates by letter with UE, if new Network Sever determines that UE does not need to carry out the Anchor migration; Otherwise new NetworkSever determines that UE need carry out the Anchor migration, and definite state parameter maximum described Anchor that preponderates is the Anchor that UE should be moved to.

Certainly, except above-mentioned Anchor state parameter, new Network Sever also can take the route metric between self and each Anchor that is connected into account, obtain route metric between the state parameter of each Anchor and self and each Anchor as: new Network Sever, judge when drawing the Anchor that state parameter preponderates maximum whether the route metric between this Anchor and the new Network Sever is lower than the route metric lowest limit that sets in advance, and be the Anchor that this Anchor is defined as helping most when being not less than UE communication only in judged result, judge further more whether this Anchor is exactly the current Anchor that communicates by letter with UE, if new Network Sever determines that UE does not need to carry out the Anchor migration; Otherwise new Network Sever determines that UE need carry out the Anchor migration, and the Anchor that definite state parameter is preponderated at most and route metric is not less than the route metric lowest limit is the Anchor that UE should be moved to.

In addition, when new Network Sever obtains route metric between the state parameter of each Anchor and self and each Anchor, can also select the Anchor of route metric optimum and judge the lowest limit state parameter whether state parameter of this Anchor is better than setting in advance, and be the Anchor that this Anchor is defined as helping most when being UE communication only in judged result, judge further more whether this Anchor is exactly the current Anchor that communicates by letter with UE, if new Network Sever determines that UE does not need to carry out the Anchor migration; Otherwise new Network Sever determines that UE need carry out the Anchor migration, and the Anchor that definite route metric optimum and state parameter are better than lowest limit state parameter is the Anchor that UE should be moved to.

In actual applications, described route metric can be pre-configured, also can be that new NetworkSever is accessed by Routing Protocol; And, whether need to carry out the Anchor migration and move in the operation of which Anchor the normally very important parameter of route metric at definite UE.

Can find out obviously that by the above new Network Sever is defined as the new Anchor that UE need be moved to the described Anchor that helps UE communication most usually; Comparatively speaking, the current Anchor that communicates by letter with UE then is considered to old Anchor.

Step 404: after definite UE need carry out Anchor migration, can be further in UE, new Network Sever even more common at present authentication process further and between the home subscriber server (HSS); Do so normally and for security reasons consider, such as: when the key of UE had lost efficacy,, just need carry out described authentication process in order to ensure communication safety.

Certainly, in actual applications, also can not carry out described authentication process, but acquiescence can be for UE provides service, and then directly enter step 405.

Step 405: it is that UE distributes new user's face and operation layer address that new Network Sever asks new Anchor, is that UE distributes new user's face and operation layer address during request that new Anchor receives the Network Sever that makes a fresh start.Described operation layer address is generally Internet protocol (IP) address.

Particularly, new Network Sever sends the user's face request for allocation that comprises UE Context to new Anchor; When new Anchor receives user's face request for allocation of the Network Sever that makes a fresh start, be that UE sets up corresponding user plane information according to the UE Context that comprises in this request, and be UE distribution service layer address.Distribute the operation of described operation layer address to be undertaken by multiple modes such as nslookup resolution system (DNS) servers.

For after UE set up user's surface information, both set up the annexation of communicating by letter between new Network Sever and the new Anchor in order to support UE.

Step 406: new Network Sever asks the old user face of old Anchor deletion at UE.

Particularly, new Network Sever sends the user's face removal request that comprises UE Context to old Anchor; When old Anchor receives user's face removal request of the Network Sever that makes a fresh start, the user plane information that deletion was once set up for UE.Like this, just no longer there has been the annexation of communicating by letter between new Network Sever and the old Anchor in order to support UE.

Step 407: location area updating has taken place in new Network Sever notice HSS UE.

Particularly, new Network Sever sends location update message at UE to HSS, sends canceling position message at UE to old Network Sever when HSS receives this location update message; When old Network Sever receives from the canceling position message of HSS, delete the positional information of the UE that stores and cancel acknowledge message to the HSS home position, the subscription data with UE when HSS receives this canceling position acknowledge message sends to new Network Sever; New Network Sever is that UE creates new Context according to the UE subscription data of receiving, and sends insertion user data acknowledge message to HSS; When HSS receives this insertion user data acknowledge message, upgrade acknowledge message to new Network Sever home position.

Step 408: new Network Sever is the operation layer address notification UE that UE distributed with new Anchor.

Particularly, it is the described operation layer address that UE distributed that new Network Sever obtains new Anchor, and this operation layer address is carried on location area updating accepts to send in the message UE.In practical application, new Network Sever may be also for UE have distributed some new parameters, as: P-TMSI, reposition district identify (TAI) etc.New Network Sever can be carried on described location area updating with these parameters and new IP address and accept to send to UE in the message or in other message format.

After step 409:UE receives the operation layer address of the Network Sever that makes a fresh start, use this operation layer address applications prior art to register to the upper strata service network; So that the top service network is known UE by newly assigned this operation layer address, assurance top service network is follow-up can use this operation layer address and UE proper communication.

In the above flow process, there is not tangible time order and function order between step 405 and the step 406, can first execution in step 405 or step 406, also execution in step 405 and step 406 simultaneously.

As seen from Figure 4, when UE initiates location area updating, might select new NetworkSever to support UE communication for UE; This new Network Sever can determine whether UE needs to carry out the Anchor migration and should move to which Anchor, the new Anchor that can also ask UE to move to is that UE sets up new user's face and is UE distribution service layer address, carry out follow-up operations such as top service network registry so that UE can use newly assigned operation layer address, assurance top service network is follow-up can use this operation layer address and UE proper communication.

Certainly, do not need to carry out the Anchor migration if new Network Sever determines UE, the so follow-up operation that relates to new Anchor just all need not have been carried out, and carries out the location area updating operation of UE and gets final product and just use prior art.

Obviously, flow process shown in Figure 4 can guarantee UE is moved to the current Anchor that helps communicating by letter most as far as possible, problems such as the network transmission resource waste that so not only can not occur in the prior art being taken place, the increase of UE communication delay, network transmission resource can also be obviously saved and the UE communication delay can be effectively reduced, make the communication quality of UE significantly improve, and then obviously improve user satisfaction.

Referring to Fig. 5, Fig. 5 is another mobile management general flow chart of the present invention, and this flow process may further comprise the steps:

Step 501:UE uses prior art and initiates location area updating, but the unpromising UE of access network selects new Network Sever.

Step 502: the current Network Sever that service is provided for UE determines that by logic determines UE need carry out the Anchor migration.

In actual applications, Network Sever can according to the moving anchor point information that sets in advance with static mode and/or with the moving anchor point parameter that dynamical fashion obtains determine UE whether needs carry out the Anchor migration.

At described static mode, can in Network Sever, set in advance the route metric between this NetworkSever and continuous each Anchor thereof; Like this, Network Sever just can determine and the Anchor that self has optimum route metric, and judges whether this Anchor is the current Anchor that communicates by letter with UE, if Network Sever determines that UE does not need to carry out the Anchor migration; Otherwise Network Sever determines that UE need carry out Anchor migration, and the Anchor that will have an optimum route metric is defined as the Anchor that UE should be moved to.

At described dynamical fashion, Network Sever can real-time or is periodically obtained the state parameter of each Anchor that links to each other with self, as: the system resource load state, the UE linking number, link circuit resource load state etc., and one or more corresponding in each Anchor state parameter that will obtain relatively to draw state parameter maximum Anchor that preponderates, this Anchor is defined as helping most the Anchor of UE communication, judge again whether this Anchor is exactly the current Anchor that communicates by letter with UE, if Network Sever determines that UE does not need to carry out the Anchor migration; Otherwise Network Sever determines that UE need carry out Anchor migration, and definite state parameter maximum described Anchor that preponderates is the Anchor that UE should be moved to.

Certainly, except above-mentioned Anchor state parameter, Network Sever also can take the route metric between self and each Anchor that is connected into account, obtain route metric between the state parameter of each Anchor and self and each Anchor as: Network Sever, when drawing the Anchor that state parameter preponderates maximum, judge whether the route metric between this Anchor and the Network Sever is lower than the route metric lowest limit that sets in advance, and be the Anchor that this Anchor is defined as helping most when being not less than UE communication only in judged result, judge further more whether this Anchor is exactly the current Anchor that communicates by letter with UE, if Network Sever determines that UE does not need to carry out the Anchor migration; Otherwise Network Sever determines that UE need carry out Anchor migration, and the Anchor that definite state parameter is preponderated at most and route metric is not less than the route metric lowest limit is the Anchor that UE should be moved to.

In addition, when Network Sever obtains route metric between the state parameter of each Anchor and self and each Anchor, can also select the Anchor of route metric optimum and judge the lowest limit state parameter whether state parameter of this Anchor is better than setting in advance, and be the Anchor that this Anchor is defined as helping most when being UE communication only in judged result, judge further more whether this Anchor is exactly the current Anchor that communicates by letter with UE, if Network Sever determines that UE does not need to carry out the Anchor migration; Otherwise Network Sever determines that UE need carry out Anchor migration, and the Anchor that definite route metric optimum and state parameter are better than lowest limit state parameter is the Anchor that UE should be moved to.

In actual applications, described route metric can be pre-configured, also can be that Network Sever is accessed by Routing Protocol; And, whether need to carry out the Anchor migration and move in the operation of which Anchor the normally very important parameter of route metric at definite UE.

Can find out obviously that by the above Network Sever is defined as the new Anchor that UE need be moved to the described Anchor that helps UE communication most usually; Comparatively speaking, the current Anchor that communicates by letter with UE then is considered to old Anchor.

Step 503: after definite UE need carry out Anchor migration, can be further in UE, Network Sever even more common at present authentication process further and between the HSS.

Certainly, in actual applications, also can not carry out described authentication process, but directly enter step 504.

It is that UE distributes new user's face and operation layer address that step 504:Network Sever asks new Anchor, and new Anchor is that UE distributes new user's face and operation layer address when receiving from the request of Network Sever.The method of operation of this step is identical with the corresponding operating method of step 405.

For after UE set up user's surface information, both set up annexation between Network Sever and the new Anchor in order to support that UE communicates by letter.

Step 505:Network Sever asks the old user face of old Anchor deletion at UE.Concrete delet method is identical with corresponding delet method in the step 406.

After finishing this step, just no longer exist between Network Sever and the old Anchor in order to have supported annexation that UE communicates by letter.

Step 506:Network Sever is the operation layer address notification UE that UE distributed with new Anchor.Concrete Notification Method is identical with corresponding Notification Method in the step 408.

Step 507:UE uses this operation layer address applications prior art to register to the upper strata service network after receiving operation layer address from Network Sever.Concrete register method is identical with corresponding register method in the step 409.

In the above flow process, there is not tangible time order and function order between step 504 and the step 505, can first execution in step 504 or step 505, also execution in step 504 and step 505 simultaneously.

As seen from Figure 5, when UE initiates location area updating, might not select new Network Sever but still continue to use the current Network Sever that serves for UE for UE; This Network Sever can determine whether UE needs to carry out the Anchor migration and should move to which Anchor, the new Anchor that can also ask UE to move to is that UE sets up new user's face and is UE distribution service layer address, carry out follow-up operations such as top service network registry so that UE can use newly assigned operation layer address, assurance top service network is follow-up can use this operation layer address and UE proper communication.

Certainly, do not need to carry out Anchor migration if described Network Sever determines UE, the so follow-up operation that relates to new Anchor just all need not have been carried out, and carries out the location area updating operation of UE and gets final product and just use prior art.

Obviously, flow process shown in Figure 5 can guarantee UE is moved to the current Anchor that helps communicating by letter most as far as possible, problems such as the network transmission resource waste that so not only can not occur in the prior art being taken place, the increase of UE communication delay, network transmission resource can also be obviously saved and the UE communication delay can be effectively reduced, make the communication quality of UE significantly improve, and then obviously improve user satisfaction.

Need to prove that the Network Sever among Fig. 4, Fig. 5 can be the MME/UPE that is combined into a logic entity, also can be to be separated into two MME under the logic entity situation at MME, UPE, or other can provide the communication entity of communication service for UE.Anchor among Fig. 4, Fig. 5 can be 3rd Generation Partnership Project anchor point (3GPP Anchor), also can be intercommunication connecting system anchor point (Inter Access System Anchor, IASA) etc.; And, can also be provided with the UPE entity among the Anchor of Fig. 4, Fig. 5; Have, the internet protocol multimedia subsystem among Fig. 4, Fig. 5 (IMS) is a kind of in the described top service network again, and this top service network also can be MSN or Web content service network etc.

Make a general survey of Fig. 4, Fig. 5 as can be known, the difference of Fig. 4 and flow process shown in Figure 5 only is whether be that the UE that initiates location area updating has selected new Network Sever; Yet, no matter whether be that the UE that initiates location area updating has selected new Network Sever, UE can both be moved to the current Anchor that helps communicating by letter most as far as possible, makes the communication quality of UE significantly improve, and then obviously improves user satisfaction.

Fig. 4, Fig. 5 have just carried out the general description of principle to motion management method of the present invention, in actual applications, because Network Sever can be the MME/UPE that is combined into a logic entity, also can be the MME under MME, UPE separation case, adding in the mobility management process might be for UE selects new Network Sever, that is: gravity treatment MME and or UPE; This can make the mobility management process under the different situations be not quite similar; Therefore, the mobility management process under the different situations is described in detail below by a large amount of embodiment, with as far as possible clear, at large set forth the concrete operations details of motion management method of the present invention.Need to prove, though whether gravity treatment MME and or UPE and MME, UPE whether be combined into a logic entity and can make mobility management process that certain variation takes place, the different communication entity does not have much variations usually at the identical operation that message structure carried out.

Embodiment 1:MME and UPE are combined into a logic entity MME/UPE, and gravity treatment MME/UPE;

Referring to Fig. 6, Fig. 6 is the mobile management flow chart of the embodiment of the invention 1, and this flow process may further comprise the steps:

Step 601: the new MME/UPE of UE in the lane place at its place that carry out location area updating sends location area updating request (TAU Request), comprises in this update request that P-TMSI, UE initiate location area updating sign (old TAI), the updating type parameters such as (Update Type) of residing lane place before.

Usually, UE can carry out location area updating because of having entered a new lane place, also can be periodically to carry out location area updating.

Step 602: new MME/UPE is according to the old TAI among the TAU Request that receives, inquires the address that UE initiates the old MME that registered before the location area updating, and sends context request (Context request) at UE according to this address to old MME.Comprise some necessary information among the described Context request, as: P-TMSI, oldTAI, TLLI, new MME address etc.

Step 603: old MME/UPE is carried on the Context of UE in the context response (Context response) and sends to new MME/UPE.

Step 604: new MME/UPE determines that by logic determines UE need carry out the Anchor migration.

Step 605: after definite UE need carry out Anchor migration, new MME/UPE can be further and UE even and HSS between at the more common at present authentication process of UE.

Certainly, in actual applications, also can not carry out described authentication process, but directly enter step 606.

Step 606: new MME/UPE can further return context transfer acknowledge message (context Acknowledge) to old MME/UPE after receiving Context response from old MME/UPE.In practical application, also can not carry out the operation of this step, but directly enter step 607.

Step 607: the new Anchor that new MME/UPE will be moved to UE sends and carries the user's face of the setting up context request (Create context request) of UEContext, and to ask new Anchor be that UE distributes new IP address.

Step 608: when new Anchor receives the Create context request of the MME/UPE that makes a fresh start, be that UE sets up corresponding user plane information, and distribute new IP address for UE according to the UE Context that comprises in this request; Afterwards, the user plane information that also will set up for UE and the described IP address of distribution send to new MME/UPE.Described user plane information and IP address all can be carried on to set up in user's face context response (Create context response) and send to new MME/UPE.

Step 609: new MME/UPE is to the deletion user's context request (Delete PDP context request) of old MME/UPE transmission at UE.

Step 610: make a fresh start the in the future Delete PDP context request of MME/UPE of old MME/UPE sends to UE and initiates the old Anchor that communicates by letter with UE before the location area updating.

Step 611: the UE Context of deletion storage when old Anchor receives the Delete PDP context request that old MME/UPE transmits, and return deletion user's context response (Delete PDP context response) to old MME/UPE.

Step 612: old MME/UPE will send to new MME/UPE from the Delete PDP context response of old Anchor.

Step 613: new MME/UPE sends the position to HSS and upgrades (Update location) message, may comprise the international mobile subscriber identity (IMSI), cancellation type (Cancellation Type) of UE etc. in this message.

Step 614:HSS sends at the canceling position (Cancel location) of UE to old MME/UPE and asks.

Step 615: the UE positional information that deletion was stored when old MME/UPE received from the Cancel location request of HSS, and to HSS home position cancellation affirmation (Cancellocation Ack).

Step 616 is carried on the subscription data of UE to insert in user data (the Insert Subscriber Data) request to step 618:HSS and sends to new MME/UPE; New MME/UPE confirms that UE has been positioned at new lane place when receiving from the Insert Subscriber Data request of HSS, and for UE creates new context, also returns the insertion user data to HSS and confirm (Insert Subscriber Data Ack) message; After HSS receives the Insert Subscriber Data Ack message of the MME/UPE that makes a fresh start, upgrade affirmation (Update location Ack) message to new MME/UPE home position.

Step 619: new MME/UPE is that user plane information and the IP address allocated that UE sets up sends UE with new Anchor.Described user plane information and IP address can be carried on location area updating and accept to send to UE in (TA update accept) message, and described user plane information may comprise the new P-TMSI at UE, new TAI etc.

After step 620:UE received the IP address of the MME/UPE that makes a fresh start, (TA update Complete) message was finished in renewal to new MME/UPE home position district.

The described user plane information that step 621:UE basis is received and the IP aspect relevant parameter of IP address configuration self, and use described IP address applications prior art to top service network registries such as IMS.

Embodiment 2:MME and UPE are combined into a logic entity MME/UPE, and gravity treatment MME/UPE not;

Referring to Fig. 7, Fig. 7 is the mobile management flow chart of the embodiment of the invention 2, and this flow process may further comprise the steps:

Step 701: the UE that carry out location area updating is the MME/UPE transmission TAU Request of its service to always.

Step 702:MME/UPE determines that by logic determines UE need carry out the Anchor migration.

Step 703: after definite UE need carry out Anchor migration, MME/UPE can be further and UE even and HSS between at the more common at present authentication process of UE.

Certainly, in actual applications, also can not carry out described authentication process, but directly enter step 704.

The new Anchor that step 704:MME/UPE will be moved to UE sends Create context request, and to ask new Anchor be that UE distributes new IP address.

Step 705: new Anchor is that UE sets up corresponding user plane information when receiving from the Create context request of MME/UPE, and distributes new IP address for UE; Afterwards, the user plane information that also will set up for UE and the described IP address of distribution send to MME/UPE.Described user plane information and IP address all can be carried among the Create context response and send to MME/UPE.

Step 706:MME/UPE is to the Delete PDP context request of old Anchor transmission at UE.

Step 707: delete the UE Context of storage when old Anchor receives from the Delete PDP context request of MME/UPE, and return Delete PDP context response to MME/UPE.

Step 708:MME/UPE is that user plane information and the IP address allocated that UE sets up sends UE with new Anchor.Described user plane information and IP address can be carried in the TA update accept message and send to UE.

Step 709:UE returns TAupdate Complete message to MME/UPE after receiving IP address from MME/UPE.

The described user plane information that step 710:UE basis is received and the IP aspect relevant parameter of IP address configuration self, and use described IP address applications prior art to top service network registries such as IMS.

Embodiment 3:MME, UPE are separated into two logic entities, and UPE and Anchor are combined into a logic entity UPE/Anchor; And, gravity treatment MME;

Referring to Fig. 8, Fig. 8 is the mobile management flow chart of the embodiment of the invention 3, and this flow process may further comprise the steps:

Step 801: the new MME of UE in the lane place at its place that carry out location area updating sends TAU Request.

Step 802: the TAU Request that new MME basis is received is to the Context request of old MME transmission at UE.

Step 803: old MME is carried on the Context of UE and sends to new MME among the Context response.

Step 804: new MME determines that by logic determines UE need carry out the Anchor migration.

Step 805: after definite UE need carry out Anchor migration, new MME can be further and UE even and HSS between at the more common at present authentication process of UE.

Certainly, in actual applications, also can not carry out described authentication process, but directly enter step 806.

Step 806: new MME can further return context Acknowledge to old MME after receiving Context response from old MME.In practical application, also can not carry out the operation of this step, but directly enter step 807.

Step 807: the new UPE/Anchor that new MME will be moved to UE sends Create context request, and to ask new UPE/Anchor be that UE distributes new IP address.

Step 808: new UPE/Anchor is that UE sets up corresponding user plane information when receiving the Create context request of the MME that makes a fresh start, and distributes new IP address for UE; Afterwards, the user plane information that also will set up for UE and the described IP address of distribution send to new MME.Described user plane information and IP address all can be carried among the Create context response and send to new MME.

Step 809: new MME notifies old UPE/Anchor deletion UE Context.

Concrete deletion action is generally: new MME is to the Delete PDP context request of old MME transmission at UE; Make a fresh start the in the future Delete PDP context request of MME of old MME sends to old UPE/Anchor; The UE Context of deletion storage when old UPE/Anchor receives the Delete PDP context request that old MME transmits, and return Delete PDP context response to old MME; Old MME will send to new MME from the Delete PDP context response of old UPE/Anchor.

Step 810: new MME sends Update location message to HSS.

Step 811:HSS asks to the Cancellocation that old MME sends at UE.

Step 812: old MME deletes the UE positional information of being stored when receiving from the Cancellocation request of HSS, and returns Cancel location Ack to HSS.

Step 813 is carried on the subscription data of UE in the Insert Subscriber Data request to step 815:HSS and sends to new MME; New MME confirms that UE has been positioned at new lane place when receiving from the Insert Subscriber Data request of HSS, and for UE creates new context, also returns Insert Subscriber Data Ack message to HSS; HS S returns Update location Ack message to new MME after receiving the Insert Subscriber Data Ack message of the MME that makes a fresh start.

Step 816: new MME is that user plane information and the IP address allocated that UE sets up sends UE with new UPE/Anchor.Described user plane information and IP address can be carried in the TA update accept message and send to UE.

After step 817:UE receives the IP address of the MME that makes a fresh start, return TA update Complete message to new MME.

The described user plane information that step 818:UE basis is received and the IP aspect relevant parameter of IP address configuration self, and use described IP address applications prior art to top service network registries such as IMS.

Embodiment 4:MME, UPE are separated into two logic entities, and UPE and Anchor are combined into a logic entity UPE/Anchor; And, gravity treatment MME not;

Referring to Fig. 9, Fig. 9 is the mobile management flow chart of the embodiment of the invention 4, and this flow process may further comprise the steps:

Step 901: the UE that carry out location area updating is the MME transmission TAURequest of its service to always.

Step 902:MME determines that by logic determines UE need carry out the Anchor migration.

Step 903: after definite UE need carry out Anchor migration, MME can be further and UE even and HSS between at the more common at present authentication process of UE.

Certainly, in actual applications, also can not carry out described authentication process, but directly enter step 904.

The new UPE/Anchor that step 904:MME will be moved to UE sends Create context request, and to ask new UPE/Anchor be that UE distributes new IP address.

Step 905: new UPE/Anchor is that UE sets up corresponding user plane information when receiving from the Create context request of MME, and distributes new IP address for UE; Afterwards, the user plane information that also will set up for UE and the described IP address of distribution send to MME.Described user plane information and IP address all can be carried among the Create context response and send to MME.

Step 906:MME is to the Delete PDP context request of old UPE/Anchor transmission at UE.

Step 907: delete the UE Context of storage when old UPE/Anchor receives from the Delete PDP context request of MME, and return Delete PDP context response to MME.

Step 908:MME is that user plane information and the IP address allocated that UE sets up sends UE with new UPE/Anchor.Described user plane information and IP address can be carried in the TA update accept message and send to UE.

Step 909:UE returns TA update Complete message to MME after receiving IP address from MME.

The described user plane information that step 910:UE basis is received and the IP aspect relevant parameter of IP address configuration self, and use described IP address applications prior art to top service network registries such as IMS.

Embodiment 5:MME, UPE, Anchor are separated into three logic entities respectively, and gravity treatment MME;

Referring to Figure 10, Figure 10 is the mobile management flow chart of the embodiment of the invention 5, and this flow process may further comprise the steps:

Step 1001: the new MME of UE in the lane place at its place that carry out location area updating sends TAU Request.

Step 1002: the TAU Request that new MME basis is received is to the Context request of old MME transmission at UE.

Step 1003: old MME is carried on the Context of UE and sends to new MME among the Context response.

Step 1004: new MME determines that by logic determines UE need carry out the Anchor migration.

Step 1005: after definite UE need carry out Anchor migration, new MME can be further and UE even and HSS between at the more common at present authentication process of UE.

Certainly, in actual applications, also can not carry out described authentication process, but directly enter step 1006.

Step 1006: new MME can further return context Acknowledge to old MME after receiving Context response from old MME.In practical application, also can not carry out the operation of this step, but directly enter step 1007.

Step 1007: the new Anchor that new MME and UE will be moved to is mutual, is that UE sets up new user's face and distributes new IP address by new Anchor.

Concrete operations are: new MME sends Create context request to new Anchor, and to ask new Anchor be that UE distributes new IP address; New Anchor is that UE sets up corresponding user plane information when receiving the Create context request of the MME that makes a fresh start, and for UE distributes new IP address, and also the user plane information that will set up for UE and the described IP address of distribution send to new MME.Described user plane information and IP address all can be carried among the Create context response and send to new MME.

Step 1008: new MME notifies old Anchor deletion UE Context.

Concrete deletion action is generally: new MME is to the Delete PDP context request of old MME transmission at UE; Make a fresh start the in the future Delete PDP context request of MME of old MME sends to old Anchor; The UE Context of deletion storage when old Anchor receives the Delete PDP context request that old MME transmits, and return Delete PDP context response to old MME; Old MME will send to new MME from the Delete PDP context response of old Anchor.

Step 1009: new MME sends Update location message to HSS.

Step 1010:HSS asks to the Cancel location that old MME sends at UE.

Step 1011: old MME deletes the UE positional information of being stored when receiving from the Cancel location request of HSS, and returns Cancel location Ack to HSS.

Step 1012 is carried on the subscription data of UE in the Insert Subscriber Data request to step 1014:HSS and sends to new MME; New MME confirms that UE has been positioned at new lane place when receiving from the Insert Subscriber Data request of HSS, and for UE creates new context, also returns Insert Subscriber Data Ack message to HSS; HSS returns Update location Ack message to new MME after receiving the Insert Subscriber Data Ack message of the MME that makes a fresh start.

Step 1015: new MME is that user plane information and the IP address allocated that UE sets up sends UE with new Anchor.Described user plane information and IP address can be carried in the TA update accept message and send to UE.

After step 1016:UE receives the IP address of the MME that makes a fresh start, return TA update Complete message to new MME.

The described user plane information that step 1017:UE basis is received and the IP aspect relevant parameter of IP address configuration self, and use described IP address applications prior art to top service network registries such as IMS.

Embodiment 6:MME, UPE, Anchor are separated into three logic entities respectively, and not gravity treatment MME, UPE;

Referring to Figure 11, Figure 11 is the mobile management flow chart of the embodiment of the invention 6, and this flow process may further comprise the steps:

Step 1101: the UE that carry out location area updating is the MME transmission TAURequest of its service to always.

Step 1102:MME determines that by logic determines UE need carry out the Anchor migration.

Step 1103: after definite UE need carry out Anchor migration, MME can be further and UE even and HSS between at the more common at present authentication process of UE.

Certainly, in actual applications, also can not carry out described authentication process, but directly enter step 1104.

The new Anchor that step 1104:MME and UE will be moved to is mutual, is that UE sets up new user's face and distributes new IP address by new Anchor.

Concrete operations are: MME sends Create context request to new Anchor, and to ask new Anchor be that UE distributes new IP address; New Anchor is that UE sets up corresponding user plane information when receiving from the Create context request of MME, and for UE distributes new IP address, and also the user plane information that will set up for UE and the described IP address of distribution send to MME.Described user plane information and IP address all can be carried among the Create context response and send to MME.

Step 1105:MME notifies old Anchor deletion UE Context.

Concrete deletion action is generally: MME is to the Delete PDP context request of old Anchor transmission at UE; Delete the UE Context of storage when old Anchor receives from the Delete PDP context request of MME, and return Delete PDP context response to MME.

Step 1106:MME is that user plane information and the IP address allocated that UE sets up sends UE with new Anchor.Described user plane information and IP address can be carried in the TA update accept message and send to UE.

Step 1107:UE returns TA update Complete message to MME after receiving IP address from MME.

The described user plane information that step 1108:UE basis is received and the IP aspect relevant parameter of IP address configuration self, and use described IP address applications prior art to top service network registries such as IMS.

Embodiment 7:MME, UPE, Anchor are separated into three logic entities respectively; Gravity treatment MME and generation UPE migration;

Referring to Figure 12, Figure 12 is the mobile management flow chart of the embodiment of the invention 7, and this flow process may further comprise the steps:

Step 1201: the new MME of UE in the lane place at its place that carry out location area updating sends TAU Request.

Step 1202: the TAU Request that new MME basis is received is to the Context request of old MME transmission at UE.

Step 1203: old MME is carried on the Context of UE and sends to new MME among the Context response.

Step 1204: new MME determines that by logic determines UE need carry out the Anchor migration.

Step 1205: after definite UE need carry out Anchor migration, new MME can be further and UE even and HSS between at the more common at present authentication process of UE.

Certainly, in actual applications, also can not carry out described authentication process, but directly enter step 1206.

Step 1206: new MME can further return context Acknowledge to old MME after receiving Context response from old MME.In practical application, also can not carry out the operation of this step, but directly enter step 1207.

Step 1207: it will be the new UPE of UE service that new MME selects, and the new Anchor that will move to UE is mutual, is that UE sets up new user's face and distributes new IP address by new Anchor.Particularly, it is multiple that new MME selects the method for described new UPE to have, as: the load that new MME obtains each UPE, and the lightest UPE of definite load will be the new UPE of UE service; Perhaps, new MME obtains the route metric between each UPE and the UE, and according to the route metric of obtaining determine and UE between the UPE of route optimum be will be the new UPE of UE service.

Certainly, new MME also can take all factors into consideration described UPE load and route metric, as: new MME obtains the load of each UPE and selects the lightest UPE of load, obtain the route metric between this UPE and the UE again and judge whether the route metric obtain is lower than the route metric lowest limit that sets in advance, and be to determine that this UPE is will be the new UPE of UE service when being not less than only in judged result; Perhaps, new MME obtain between each UPE and the UE route metric and according to the route metric of obtaining select and UE between the UPE of route optimum, obtain the load of this UPE again and judge whether the load of obtaining is higher than the load upper limit that sets in advance, and only will be the new UPE of UE service for determining this UPE when not being higher than in judged result.

Step 1208: new MME notifies old Anchor deletion UE Context.The operation of this step is identical with the operation of step 1008.

Step 1209: new MME sends Update location message to HSS.

Step 1210:HSS asks to the Cancel location that old UPE sends at UE.

Step 1211: old UPE deletes the UE positional information of being stored when receiving from the Cancel location request of HSS, and returns Cancel location Ack to HSS.

Step 1212 is carried on the subscription data of UE in the Insert Subscriber Data request to step 1214:HSS and sends to new MME; New MME confirms that UE has been positioned at new lane place when receiving from the Insert Subscriber Data request of HSS, and for UE creates new context, also returns Insert Subscriber Data Ack message to HSS; HSS returns Update location Ack message to new MME after receiving the Insert Subscriber Data Ack message of the MME that makes a fresh start.

Step 1215: new MME is that user plane information and the IP address allocated that UE sets up sends UE with new Anchor.Described user plane information and IP address can be carried in the TA update accept message and send to UE.

After step 1216:UE receives the IP address of the MME that makes a fresh start, return TA update Complete message to new MME.

The described user plane information that step 1217:UE basis is received and the IP aspect relevant parameter of IP address configuration self, and use described IP address applications prior art to top service network registries such as IMS.

The method of the new UPE of selection described in Figure 12 also can be applied in other flow chart, as long as there is operation to relate to the new UPE that service will be provided for UE in this flow chart.

Embodiment 8:MME, UPE, Anchor are separated into three logic entities respectively; Not gravity treatment MME and generation UPE migration;

Referring to Figure 13, Figure 13 is the mobile management flow chart of the embodiment of the invention 8, and this flow process may further comprise the steps:

Step 1301: the UE that carry out location area updating is the MME transmission TAU Request of its service to always.

Step 1302:MME determines that by logic determines UE need carry out the Anchor migration.

Step 1303: after definite UE need carry out Anchor migration, MME can be further and UE even and HSS between at the more common at present authentication process of UE.

Certainly, in actual applications, also can not carry out described authentication process, but directly enter step 1304.

It will be the new UPE of UE service that step 1304:MME selects, and the new Anchor that will move to UE is mutual, is that UE sets up new user's face and distributes new IP address by new Anchor.

Step 1305:MME notifies old Anchor deletion UE Context.

Step 1306:MME is that user plane information and the IP address allocated that UE sets up sends UE with new Anchor.Described user plane information and IP address can be carried in the TA update accept message and send to UE.

Step 1307:UE returns TA update Complete message to MME after receiving IP address from MME.

The described user plane information that step 1308:UE basis is received and the IP aspect relevant parameter of IP address configuration self, and use described IP address applications prior art to top service network registries such as IMS.

In above-mentioned Fig. 6 to Figure 13, when the situation of gravity treatment MME, UPE occurring, no matter whether MME is combined into a logic entity with UPE, can further delete the UE Context that is preserved by old MME, old UPE in the flow process that relates to new Anchor deletion UE Context.

Have, it is the operation that UE sets up user's face and distributing IP address that MME makes new Anchor alternately with new Anchor, is normally undertaken by UPE again; This UPE is the UPE that always serves for UE, or that selection will be the new UPE of UE service.Particularly, it is that UE sets up user's face and distributing IP address that MME need ask new Anchor by described UPE, described user's face typically refers to this UPE and user's face of newly communicating by letter in order to support UE between the Anchor, and setting up this user's face needs UPE and new Anchor to communicate mutual and negotiation usually; And, send to and send to UE again after the user plane information of UE and IP address generally also are transmitted to MME by UPE.

In actual applications, when MME, UPE, Anchor are separated into three logic entities respectively, can also carry out Figure 14 to flow process shown in Figure 180.

Particularly, might occur among Figure 14 to Figure 18 gravity treatment MME and or the situation of UPE, this makes the mobility management process under the different situations be not quite similar, even the situation that the different communication entity all can carry out logical operation at identical message structure occurs; But need to prove that the different communication entity does not have much variations usually at the identical operation that message structure carried out.

Embodiment 9: the UPE migration takes place but gravity treatment MME not;

Referring to Figure 14, Figure 14 is the mobile management flow chart of the embodiment of the invention 9, and this flow process may further comprise the steps:

Step 1401:UE sends TAU Request to LTE-RAN, and LTE-RAN sends to the MME that always serves for UE increase the Location Area Identification at the current place of UE in the message header of this TAURequest after.

The safety certification process that step 1402:MME and UE are more common at present, described safety certification process be with described authentication process is similar before, all is in order to determine whether qualified acceptance service of UE.

Certainly, in actual applications, also can not carry out described safety certification process, but acquiescence can be for UE provides service, and then directly enter step 1403.

Step 1403:MME determines that UE need carry out the Anchor migration, and then sends the deletion session context request (Delete Session Context Request) that carries the UE sign to old Anchor by logic determines.

Step 1404: when old Anchor receives from the Delete Session Context Request of MME, discharge the resource that UE takies according to the UE sign that is wherein comprised, send deletion session context response (Delete Session Context Response) to MME afterwards.The described resource that UE takies generally includes IP address and data channel resource etc.

Step 1405:MME selects to be the new UPE of UE service, and sends the deexcitation session context request (Deactivate Session Context Request) that carries the UE sign to old UPE.

Step 1406: when old UPE receives from the Deactivate Session Context Request of MME, be released to user's face resource that UE distributes according to the UE sign that is wherein comprised, and return deexcitation session context response (Deactivate Session Context Response) to MME.

Step 1407:MME sends active session context request (Activate Session Context Request) to new UPE, comprises UE sign, service quality (QoS), UE ability, encryption key etc. in this request.

Step 1408: when new UPE receives from the Activate Session Context Request of MME, select the cryptographic algorithm that to use according to the UE ability that is wherein comprised and the cryptographic algorithm self supported, and be that UE distributes the transmission channel resource according to the QoS that Activate Session Context Request is comprised, the parameters such as described cryptographic algorithm of this transmission channel resource and selection are carried in the active session context response (Activate Session Context Response) send to MME again.

With general packet radio service tunnel agreement (GTP) tunnel is example, employed IP address, port and tunnel end sign (TEID) when the described transmission channel resource of distributing for UE generally includes new UPE and receives the downlink data of the Anchor that makes a fresh start also comprise employed IP address, port and TEID when new UPE receives upstream data from LTE-RAN.

Step 1409:MME preserves the parameter that is comprised among the Activate Session Context Response, and sends the session context request (Create Session Context Request) of creating to new Anchor; Usually carry UE sign in this request, set up the desired QoS of carrying, new UPE is the parameters such as gap marker that downlink data distributed of the new Anchor of reception.

With the GTP tunnel is example, and entrained parameter comprises among the Create Session Context Request: employed IP address, port and TEID when new UPE receives the downlink data of new Anchor.

Step 1410: new Anchor is to want newly-built carrying distributing IP address when receiving from the Create Session Context Request of MME, and according to the QoS distribute data transmission channel resource among the Create Session Context Request, the described IP address that will distribute again and data transmission channel resource are carried on to create in the session context response (Create Session Context Response) and send to MME.Usually comprise the QoS that the described IP of distribution, new Anchor can allow and the described data transmission channel resource of distribution etc. among the Create Session Context Response.

With the GTP tunnel is example, and entrained parameter comprises among the Create Session Context Response: new Anchor receives the employed IP of upstream data address, port and the TEID of the UPE that makes a fresh start by newly-built described carrying.

Step 1411:MME preserves the parameter that is comprised among the Create Session Context Response of the Anchor that makes a fresh start, using prior art and set up process to LTE-RAN initiation RAB, is QoS that receives and new UPE that reception is notified to LTE-RAN from the data channel resource identification that the LTE-RAN upstream data is distributed.

With the GTP tunnel is example, the new UPE data channel resource identification that to be reception distributed from the LTE-RAN upstream data normally: new UPE is employed IP address, port and TEID during from the upstream data of LTE-RAN by newly-built described carrying reception.

LTE-RAN uses prior art according to the QoS from MME and UE consults, and finishes empty port load-supporting and sets up; And for receiving the downlink data distribute data channel resource of the UPE that makes a fresh start, the described downlink data channel resource identification that also will consult successful QoS and distribution returns to MME.

With the GTP tunnel is example, and described downlink data channel resource identification is generally: LTE-RAN is for receiving the employed IP of downlink data address, port and the TEID of the UPE that makes a fresh start.

The QoS of the negotiation success that step 1412:MME preservation LTE-RAN returns and the information such as described downlink data channel resource identification of distribution, and QoS, the LTE-RAN that will finally determine be that the make a fresh start described data channel resource identification that downlink data distributed of UPE of reception is carried on and upgrades in session context (the Update Session Context) message, again this message sent to new UPE.

With the GTP tunnel is example, and LTE-RAN is that the make a fresh start described data channel resource identification that downlink data distributed of UPE of reception is generally: LTE-RAN is for receiving the employed IP of downlink data address, port and the TEID of the UPE that makes a fresh start.

In certain step of aforesaid operations, new Anchor also will be used in the new IP address of carrying out subsequent communications for UE divides, and gives MME with this IP address notification.

Step 1413:MME sends TA Update Accept message to UE, and it is the UE IP address allocated that this message comprises new Anchor, be the DEA of the terminal use of the pairing IP of the carrying address of supporting UE communication to set up, new UPE appointment, new customer temporary identity sign etc.

Step 1414:UE returns TA Update Complete message to MME, and notice MME has received parameters such as newly assigned IP address and user identity temporary mark.

UE receives to after its IP address allocated, uses this IP address applications prior art initialization IP link layer.So far, UE just can successfully communicate by letter with new Anchor.

Certainly, UE can further use prior art and carries out registration process in top service networks such as IMS.

As seen, among the embodiment 9, the operation of creating or deleting the IP carrying does not relate to the Signalling exchange of creating the IP carrying all by MME control between UPE and the Anchor.

In actual applications, also can be as embodiment 10, by between UPE and the Anchor finish the foundation or the release of IP carrying alternately.

Referring to Figure 15, Figure 15 is the mobile management flow chart of the embodiment of the invention 10, and this flow process may further comprise the steps:

Step 1501:UE sends TAU Request by LTE-RAN to the MME that serves for UE always.

The safety certification process that step 1502:MME and UE are more common at present.Certainly, in actual applications, also can not carry out described safety certification process, but directly enter step 1503.

Step 1503:MME determines that by logic determines UE need carry out the Anchor migration; MME also selects to be the new UPE of UE service, and sends Deactivate Session Context Request to old UPE.

Step 1504: old UPE is released to user's face resource that UE distributes when receiving from the Deactivate Session Context Request of MME, also sends Delete Session Context Request to old Anchor.

Step 1505: discharge the resource that UE takies when old Anchor receives from the Delete Session Context Request of old UPE, send Delete Session Context Response to old UPE afterwards.

Step 1506: send Deactivate Session Context Response to MME when old UPE receives from the Deactivate Session Context Request of old Anchor.

When step 1507:MME receives from the Deactivate Session Context Response of old UPE, send Activate Session Context Request to new UPE.

Step 1508: new UPE is that UE distributes the transmission channel resource and carries out operation such as cryptographic algorithm selection when receiving from the Activate Session Context Request of MME; And new UPE sends Create Session Context Request to new Anchor.

Step 1509: when new Anchor receives the Create Session Context Request of the UPE that makes a fresh start, for wanting newly-built carrying distributing IP address and distribute data transmission channel resource, the described IP address that will distribute again and data transmission channel resource are carried among the Create Session Context Response and send to new UPE.

Step 1510: new UPE preserves the parameter that wherein comprises when receiving the Create Session Context Response of the Anchor that makes a fresh start, and will be once sends to MME for parameters such as the described transmission channel resource of UE distribution, cryptographic algorithm are carried among the Activate Session Context Response.

Step 1511:MME preserves the parameter that is comprised among the Activate Session Context Response of the UPE that makes a fresh start, and uses prior art and set up process to LTE-RAN initiation RAB.

Step 1512:MME preserves to set up with LTE-RAN and carries relevant parameter, and these parameters are carried in the Update Session Context message send to new UPE.

Step 1513:MME sends the TA Update Accept message that comprises newly assigned IP address at least to UE.

Step 1514:UE returns TA Update Complete message to MME, and notice MME has received parameters such as newly assigned IP address.

By the above as seen, just to be to create the method for IP carrying different for the key difference of Figure 14 and Figure 15.

In actual applications, the time sequencing of creating and deleting between the IP carrying can be distinguished to some extent with the respective sequence among Figure 14, Figure 15, shown in embodiment 11.

Referring to Figure 16, Figure 16 is the mobile management flow chart of the embodiment of the invention 11, and this flow process may further comprise the steps:

Step 1601:UE sends TAU Request by LTE-RAN to the MME that serves for UE always.

The safety certification process that step 1602:MME and UE are more common at present.Certainly, in actual applications, also can not carry out described safety certification process, but directly enter step 1603.

Step 1603:MME determines that by logic determines UE need carry out the Anchor migration; MME also selects to be the new UPE of UE service, and sends Activate Session Context Request to new UPE.

Step 1604: new UPE selects the cryptographic algorithm that will use and is UE distribution transmission channel resource when receiving from the Activate Session Context Request of MME, the parameters such as described cryptographic algorithm of this transmission channel resource and selection is carried among the Activate Session Context Response sends to MME again.

Step 1605:MME preserves the parameter that is comprised among the Activate Session Context Response, and sends Create Session Context Request to new Anchor.

Step 1606: for wanting newly-built carrying distributing IP address and distribute data transmission channel resource, the described IP address that will distribute again and data transmission channel resource were carried among the Create Session Context Response and send to MME when new Anchor received from the Create Session Context Request of MME.

Step 1607:MME preserves the parameter that is comprised among the Create Session Context Response of the Anchor that makes a fresh start, and uses prior art and set up process to LTE-RAN initiation RAB.

Step 1608:MME preserves to set up with LTE-RAN and carries relevant parameter, and these parameters are carried in the Update Session Context message send to new UPE.

Step 1609:MME sends Delete Session Context Request to old Anchor.

Step 1610: discharge the resource that UE takies when old Anchor receives from the Delete Session Context Request of MME, send Delete Session Context Response to MME afterwards.

Step 1611:MME sends Deactivate Session Context Request to old UPE.

Step 1612: old UPE is released to user's face resource that UE distributes when receiving from the Deactivate Session Context Request of MME, and returns Deactivate Session Context Response to MME.

Step 1613:MME sends the TA Update Accept message that comprises newly assigned IP address at least to UE.

Step 1614:UE returns TA Update Complete message to MME, and notice MME has received parameters such as newly assigned IP address.

Embodiment 12: UPE migration and gravity treatment MME take place;

Figure 17 is the mobile management flow chart of the embodiment of the invention 12, and this flow process may further comprise the steps:

Step 1701:UE sends TAU Request to LTE-RAN, and it will be the new MME of UE service that LTE-RAN selects, and sends to new MME increase the Location Area Identification at the current place of UE in the message header of the TAU Request that receives after.

Step 1702: new MME is according to the Location Area Identification among the TAU Request that receives, inquires the address that UE initiates the old MME that registered before the location area updating, and sends Context request at UE according to this address to old MME.And new MME determines that by logic determines UE need carry out the Anchor migration, and new MME also selects to be the new UPE of UE service.

Step 1703: old MME is carried on the Context of UE and sends to new MME among the Context response.

Step 1704: new MME and the more common at present safety certification process of UE.Certainly, in actual applications, also can not carry out described safety certification process, but directly enter step 1705.

Step 1705: new MME carries out position updating process at UE and HSS application prior art.

Concrete operations are generally: new MME is to the Update location message of HSS transmission at UE; HSS asks to the Cancellocation that old MME sends at UE; Old MME deletes the UE positional information of being stored when receiving from the Cancel location request of HSS, and returns Cancel location Ack to HSS; Afterwards, HSS is carried on the subscription data of UE in the Insert Subscriber Data request and sends to new MME; New MME confirms that UE has been positioned at new lane place when receiving from the Insert Subscriber Data request of HSS, and for UE creates new context, also returns Insert Subscriber Data Ack message to HSS; HSS returns Update location Ack message to new MME after receiving the Insert Subscriber Data Ack message of the MME that makes a fresh start.

In Figure 14 to Figure 16, new MME also can carry out above-mentioned position updating process at UE and HSS.

Step 1706: old MME was the old UPE transmission Deactivate Session Context Request of UE service before UE initiates location area updating when receiving from the Cancellocation of HSS request.

Step 1707: old UPE is released to user's face resource that UE distributes when receiving from the Deactivate Session Context Request of old MME, and returns Deactivate Session Context Response to old MME.

Step 1708: the old Anchor that new MME is initiating to communicate by letter with UE before the location area updating to UE sends Delete Session Context Request.

Step 1709: discharge the resource that UE takies when old Anchor receives from the Delete Session Context Request of MME, newly send Delete Session Context Response to MME afterwards.

Step 1710: new MME sends Activate Session Context Request to new UPE.

Step 1711: new UPE selects the cryptographic algorithm that will use and is UE distribution transmission channel resource when receiving the Activate Session Context Request of the MME that makes a fresh start, the parameters such as described cryptographic algorithm of this transmission channel resource and selection is carried among the Activate Session Context Response sends to new MME again.

Step 1712: new MME preserves the parameter that is comprised among the Activate Session Context Response, and sends Create Session Context Request to new Anchor.

Step 1713: for wanting newly-built carrying distributing IP address and distribute data transmission channel resource, the described IP address that will distribute again and data transmission channel resource were carried among the Create Session Context Response and send to new MME when new Anchor received the Create Session Context Request of the MME that makes a fresh start.

Step 1714: new MME preserves the parameter that is comprised among the Create Session Context Response of the Anchor that makes a fresh start, and uses prior art and set up process to LTE-RAN initiation RAB.

Step 1715: new MME preserves to set up with LTE-RAN and carries relevant parameter, and these parameters are carried in the Update Session Context message send to new UPE.

In certain step of aforesaid operations, new Anchor also will be used in the new IP address of carrying out subsequent communications for UE divides, and gives new MME with this IP address notification.

Step 1716: new MME sends the TA Update Accept message that comprises newly assigned IP address at least to UE.

Step 1717:UE returns TA Update Complete message to new MME, notifies new MME to receive parameters such as newly assigned IP address.

Embodiment 13:UPE does not move and gravity treatment MME not;

Referring to Figure 18, Figure 18 is the mobile management flow chart of the embodiment of the invention 13, and this flow process may further comprise the steps:

Step 1801:UE sends TAU Request by LTE-RAN to the MME that serves for UE always.

The safety certification process that step 1802:MME and UE are more common at present.Certainly, in actual applications, also can not carry out described safety certification process, but directly enter step 1803.

Step 1803:MME determines that by logic determines UE need carry out the Anchor migration, and the old Anchor that communicated by letter with UE before UE initiates location area updating sends Delete Session Context Request.

Step 1804: discharge the resource that UE takies when old Anchor receives from the Delete Session Context Request of MME, send Delete Session Context Response to MME afterwards.

Step 1805:MME sends Deactivate Session Context Request to UPE.

Step 1806:UPE is released to user's face resource that UE distributes when receiving from the Deactivate Session Context Request of MME, and returns Deactivate Session Context Response to MME.

Step 1807:MME sends Activate Session Context Request to UPE.

Select the cryptographic algorithm that to use when step 1808:UPE receives from the Activate Session Context Request of MME and be UE distribution transmission channel resource, again the parameters such as described cryptographic algorithm of this transmission channel resource and selection are carried among the Activate Session Context Response and send to MME, can support UE to upgrade the normal course of communications of being carried out behind the lane place to guarantee described transmission channel resource and described cryptographic algorithm.

Step 1809:MME preserves the parameter that is comprised among the Activate Session Context Response, and sends Create Session Context Request to new Anchor.

Step 1810: for wanting newly-built carrying distributing IP address and distribute data transmission channel resource, the described IP address that will distribute again and data transmission channel resource were carried among the Create Session Context Response and send to MME when new Anchor received from the Create Session Context Request of MME.

Step 1811:MME preserves the parameter that is comprised among the Create Session Context Response of the Anchor that makes a fresh start, and uses prior art and set up process to LTE-RAN initiation RAB.

Step 1812:MME preserves to set up with LTE-RAN and carries relevant parameter, and these parameters are carried in the Update Session Context message send to UPE.

Step 1813:MME sends the TA Update Accept message that comprises newly assigned IP address at least to UE.

Step 1814:UE returns TA Update Complete message to MME, and notice MME has received parameters such as newly assigned IP address.

Among Figure 18, MME can also carry out position updating process at UE and HSS application prior art.

In fact, in Fig. 6 to Figure 13, to carry out the RAB shown in Figure 14 to Figure 18 equally and set up process; Do not indicate among Fig. 6 to Figure 13 that this RAB sets up process, for no other reason than that this process is not the key component that Fig. 6 to Figure 13 will describe.In actual applications, also can when setting up process and finish, described RAB will send to UE by this RAB of setting up for the described IP address that UE distributes.

Can know by above-described Fig. 4, the concise and to the point flow process of mobile management shown in Figure 5 and each embodiment of Fig. 6 to Figure 18, whether no matter whether gravity treatment MME, at least two communication entities whether moving among UPE and MME, UPE, the Anchor are combined into a logic entity, and motion management method of the present invention can be selected the Anchor that helps communicating by letter most for UE; This guarantees that UE is follow-up can not occur situations such as network transmission resource waste of the prior art, communication delay increase when communicating by letter with this Anchor, but make that network transmission resource obtains saving, communication delay is effectively reduced, thereby can obviously improve the communication quality of UE, and then significantly improve user satisfaction.

Need to prove: the operation of the Anchor that selection described above helps communicating by letter most all is that the location area updating of being initiated by UE is operated and triggered; In actual applications, also can periodic triggers or trigger because of the state of activation of UE and the conversion between the idle condition.

By the above as can be seen, the motion management method under the evolution network framework provided by the present invention can obviously improve the communication quality of UE, and then significantly improve user satisfaction.

Claims

1. A mobility management method under an evolved network architecture, characterized in that the method comprises:

When it is determined that the user equipment UE needs to perform anchor point migration, the new anchor point to which the UE is to migrate provides communication resources for supporting subsequent communication of the UE,

The method for the new anchor point to provide the communication resource is: the new anchor point establishes a user plane for supporting the UE's subsequent communication, and allocates a communication address for the UE to support the UE's subsequent communication,

The method for the new anchor to establish the user plane is as follows: the new anchor directly or indirectly interacts with the user plane entity UPE currently serving the UE, and establishes a user interface for supporting UE communication between the new anchor and the user plane entity UPE. noodle.

2 . The method according to claim 1 , wherein the UPE is a UPE that has been serving the UE, or a UPE that is newly selected to serve the UE due to a location update of the UE.

3. The method according to claim 1, wherein the method for establishing the user plane by a new anchor point is:

Send an activation session context request to the UPE currently serving the UE; the new UPE allocates transmission channel resources for the UE according to the received activation session context request, and then the transmission channel resources include the UE identity, the QoS required to establish the bearer, and the new The parameters of the channel identification allocated by the UPE for receiving the downlink data of the new anchor point are sent to the new anchor point; the new anchor point is based on the received UE identification, the QoS required for establishing the bearer, and the new UPE for receiving the new anchor point. The parameter of the channel identifier assigned to the downlink data allocates an Internet Protocol IP address and allocates data transmission channel resources for the bearer to be created.

4. The method according to claim 3, wherein the parameters including the UE identity, the QoS required to establish the bearer, and the channel identity allocated by the new UPE for receiving the downlink data of the new anchor point are carried in the creation Sent to the new anchor in the session context request.

5. The method according to claim 1, wherein the interaction between the new anchor point and the UPE is realized through a mobility management entity (MME) currently serving the UE.

6. The method according to claim 5, wherein the MME is an MME that has been serving the UE, or a newly selected MME that is serving the UE due to UE location update.

7. The method according to any one of claims 1 to 5, wherein the method for determining that the UE needs to perform anchor migration is:

Whether the UE needs to perform anchor relocation is determined according to statically preset anchor relocation information and/or dynamically acquired anchor relocation parameters.

8. The method according to claim 7, wherein the method for determining whether the UE needs to perform anchor migration according to the anchor migration information is as follows:

Preset the routing metrics between the network server serving the UE and the connected anchors, and judge whether the anchor with the optimal routing metrics is the current anchor communicating with the UE, and if so, determine that the UE does not need to perform anchoring relocation; otherwise, it is determined that the UE needs to perform anchor point relocation.

9. The method according to claim 8, further determining the anchor point with the optimal routing metric as the anchor point to which the UE should migrate.

10. The method according to claim 7, wherein the method for determining whether the UE needs to perform anchor migration according to the anchor migration parameter is as follows:

Obtain the status parameters of each anchor point connected to the network server serving the UE, including system resource load status, UE connection number and link resource load status, and obtain each anchor point including system resource load status, UE connection number and link resource load status. One or more corresponding comparisons among the status parameters of the link resource load status to obtain the anchor point with the most dominant status parameters including the system resource load status, the number of UE connections, and the link resource load status, and then determine whether the anchor point It is the anchor point currently communicating with the UE, and when the judgment result is negative, it is determined that the UE needs to perform anchor point migration.

11. The method according to claim 10, characterized in that, further determining the anchor point with the most dominant state parameters including system resource load status, UE connection number, and link resource load status as the UE should migrate to anchor.

12. The method according to claim 7, wherein the method for determining whether the UE needs to perform anchor migration according to the anchor migration parameters is as follows:

Obtain the status parameters of each anchor point connected to the network server serving the UE, including the system resource load status, the number of UE connections, and the link resource load status, as well as the routing metrics between each anchor point and the network server, and determine the network server that includes the system. Resource load status, UE connection number and status parameters of link resource load status dominate whether the routing metric between the anchor point and the network server is lower than the preset routing metric bottom limit, and further judge this when the judgment result is no. Whether the anchor point is the anchor point currently communicating with the UE, and if the judgment result is no, it is determined that the UE needs to perform anchor point migration.

13. The method according to claim 12, characterized in that further, the state parameters including the system resource load status, the number of UE connections and the link resource load status are dominant, and the anchor whose routing metric is not lower than the lower limit of the routing metric The point is determined as the anchor point to which the UE should migrate.

14. The method according to claim 7, wherein the method for determining whether the UE needs to perform anchor migration according to the anchor migration parameters is as follows:

Obtain the status parameters of each anchor point connected to the network server serving the UE, including the system resource load status, the number of UE connections and the link resource load status, and the routing metrics between each anchor point and the network server, and determine the best routing metrics Whether the status parameters of the optimal anchor point including the system resource load status, the number of UE connections and the link resource load status are better than the preset bottom limit status parameters, and if the judgment result is yes, it is further judged whether the anchor point is currently connected to the UE An anchor point for communication, and when the determination result is negative, it is determined that the UE needs to perform anchor point relocation.

15. The method according to claim 14, wherein the routing metric is further optimized and the state parameters including the system resource load condition, the number of UE connections and the link resource load condition are better than the anchor point of the bottom limit state parameter. is the anchor point to which the UE should migrate.

16. The method according to claim 1, wherein the operations included in the method are triggered by a location area update process initiated by the UE.

17. The method according to claim 16, further initiating a UE location update procedure to a Home Subscriber Server (HSS).

18. The method according to claim 17, wherein what triggers the operations included in the method is a location area update request sent by the UE during the location area update process.

19. The method according to claim 1, 2, 3, 4, 5, 16 or 17, wherein the anchor point is a 3GPP Anchor, or an Interworking Access System anchor point IASA.

20. The method according to claim 1, 2, 3, 4, 5, 16 or 17, characterized in that the UE Context saved by the anchor serving the UE before the UE performs anchor migration is further deleted.

21. The method according to claim 1, 2, 3, 4, 5, 16 or 17, characterized in that before the new anchor point provides the communication resources, the method further comprises: performing an authentication and authentication process for the UE .

22. The method according to claim 1, 2, 3, 4, 5, 16 or 17, further establishing a radio access bearer for supporting subsequent communication for the UE.

23. The method according to claim 22, wherein the communication resource includes an IP address as a communication address, and the IP address is further sent to the UE through the radio access bearer established for the UE.

24. The method according to claim 1, 3, 4, 5, 16 or 17, wherein the communication address is an IP address, and the IP address is further carried in the location area update accepting TA updateaccept message and sent to UE.

25. The method according to claim 24, wherein the UE further uses the IP address to register with an upper layer service network.

26. The method according to claim 25, wherein the upper-layer service network is an Internet Protocol Multimedia Subsystem (IMS), MSN or a network content service network.