CN102395120B

CN102395120B - Mobility management method, associated equipment and communication system

Info

Publication number: CN102395120B
Application number: CN201110396065.9A
Authority: CN
Inventors: 银宇
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2008-09-27
Filing date: 2008-09-27
Publication date: 2014-07-09
Anticipated expiration: 2028-09-27
Also published as: CN102395120A

Abstract

Embodiments of the invention provide a mobility management method, associated equipment and a communication system. A mobile agent (MA) apparatus comprises: an authentication request sending unit, which is used to send an authentication request to a network side, wherein the authentication request is used to request the network side to authorize a MA capability; an authentication result reception unit, which is used to receive an authentication result fed back by the network side; a notice sending unit, which is used to send a notification carrying the authentication result so that a terminal can confirm that the MA apparatus possesses the MA capability. By using a technical scheme provided in the embodiments of the invention, a position updating quantity of a whole system can be reduced.

Description

Motion management method, relevant device and communication system

The application is to be the divisional application of the case that September 27, application number in 2008 are 200810161460.7, denomination of invention is " motion management method, relevant device and communication system " applying date.

Technical field

The present invention relates to communication technical field, particularly a kind of motion management method, relevant device and communication system.

Background technology

In mobile communication system, after terminal is attached in network, network side can be given wireless coverage of terminal distribution, is called paging zone.In the time that terminal discharges with being connected of network side, if network need to send signaling or user face data to terminal, can be to terminal transmission beep-page message in the scope of this paging zone; In the time that terminal shifts out from current paging zone, need by initiating a position updating request flow process informing network side, network side can be the paging zone that terminal distribution is new.

Obviously, fast mobile terminal faster, its launch position update request is just more frequent, and people's self translational speed and scope are all limited, want so that speed is mobile on a large scale faster, generally will be by the vehicles, as bus, subway, train and steamer etc., all terminals on the vehicles all move with consistent direction and speed.

Under some occasion, as parade, demonstration, also may there is the situation that the crowd of a large amount of walkings moves together.

Inventor finds realizing in process of the present invention: when in a large number in same position, the terminal moving together with speed with consistent direction is in the time shifting out from current paging zone, can distinguish in a short period of time launch position update request message with informing network, network side is according to the location update request message of terminal, determine the current location of terminal, because network side can be received a lot of location update request message in a short period of time, increase the weight of the processing load of network.

Summary of the invention

The embodiment of the present invention provides a kind of motion management method, relevant device and communication system, can reduce the position of entire system and upgrade quantity.

In view of this, the embodiment of the present invention provides:

A kind of motion management method, comprising:

By mobile agent MA context and terminal context bindings;

Receive the primary importance update request that MA sends;

According to described primary importance update request and MA context and the contextual binding relationship of terminal, determine that described terminal moves together with described MA.

A kind of mobile management device, comprising:

Binding unit, for by MA context and terminal context bindings;

Position updating request receiving element, the primary importance update request sending for receiving MA;

Determine unit, shift position, for after described binding unit is by MA context and terminal context bindings, according to described primary importance update request, determine that described terminal moves together with described MA.

A kind of mobile management device, comprising:

Unit set up in attached MA context, for setting up attached MA context, by the MA context relation on the Mobility Management Entity of described attached MA context and MA registration;

Binding unit, for by terminal context and described attached MA context bindings.

A kind of terminal, comprising:

Binding instruction acquiring unit, for obtaining the binding instruction that represents described terminal and MA binding success;

Control unit for getting after the binding instruction that represents described terminal and MA binding success, is controlled and is not sent position updating request when mobile.

A kind of mobile agent device, comprising:

Authentication request transmitting element, for sending authentication request to network side, described authentication request is used for asking network side mandate mobile agent ability;

Authentication result receiving element, for receiving the authentication result of network side feedback;

Notice transmitting element, for sending the notice message that carries described authentication result, there is mobile agent ability for mobile agent device described in terminal check.

A kind of communication system, comprising: the Mobility Management Entity of endpoint registration, and the Mobility Management Entity of MA registration, wherein,

The Mobility Management Entity of described endpoint registration, for setting up attached MA context, with the MA context relation on the Mobility Management Entity of MA registration, and by terminal context and attached MA context bindings;

The Mobility Management Entity of described MA registration, for setting up MA context, the attached MA context relation with on the Mobility Management Entity of endpoint registration, receives the position updating request that described MA sends; According to described position updating request, determine that described terminal moves together with described MA.

Network side in the embodiment of the present invention passes through MA (Mobile Agent, mobile agent) context and terminal context bindings, receiving after the position updating request of MA transmission, think and also carried out corresponding movement with the terminal of MA binding, therefore, do not need the terminal launch position update request message respectively of binding with MA, can determine the shift position of terminal yet, alleviated the processing load of network.

Terminal in the embodiment of the present invention is getting after the indication information that represents terminal and MA binding success, when mobile, control and do not send position updating request, so that network side can not receive and process a lot of location update request message within very short time, alleviate the processing load of network.

Brief description of the drawings

Fig. 1 is the motion management method flow chart that the embodiment of the present invention one provides;

Fig. 2 is the motion management method signaling diagram that the embodiment of the present invention two provides;

Fig. 3 is the motion management method signaling diagram that the embodiment of the present invention three provides;

Fig. 4 is the motion management method signaling diagram that the embodiment of the present invention four provides

Fig. 5 is the signaling diagram that MA notice binding terminal that the embodiment of the present invention provides is bound again;

Fig. 6 is the flow process signaling diagram that unbinds that the embodiment of the present invention provides;

Fig. 7 is the flow process signaling diagram that unbinds that the embodiment of the present invention provides;

Fig. 8 is the mobile management device structure chart that the embodiment of the present invention five provides;

Fig. 9 is the mobile management device structure chart that the embodiment of the present invention six provides;

Figure 10 is the terminal structure figure that the embodiment of the present invention seven provides;

Figure 11 is the mobile agent device structure chart that the embodiment of the present invention eight provides.

Embodiment

Embodiment mono-:

Consult Fig. 1, the embodiment of the present invention one provides a kind of motion management method, comprising:

Network side is by MA context and terminal context bindings;

Receive the position updating request that described MA sends;

According to described position updating request and MA context and the contextual binding relationship of terminal, determine that described terminal moves together with described MA.

Above-mentioned network side can be Mobility Management Entity, and in EPS (evolved packet system, the grouping system of evolution), this Mobility Management Entity can be MME; This position updating request can be TAU (Tracking Area Update, tracing section updating) request.Embodiment describes the present invention program as an example of EPS system example below.

Wherein, network side can have two kinds of modes to realize MA context and terminal context bindings, single place mode and many places mode, single place mode requires binding terminal and MA to have to register on same MME, if terminal and MA are registered on different MME in the time of binding, the MME being registered by MA obtains terminal context to the MME of endpoint registration, carries out the contextual binding of terminal context and MA; It is upper that many places mode allows binding terminal and MA to be registered to different MME, and the MME registering by MA and the MME of endpoint registration set up context relation indirectly to realize the binding of terminal and MA, and this two kinds of implementations are described in subsequent implementation regular meeting in detail.

Wherein, before network side is by MA context and terminal context bindings, also comprise: network side (can be MA registration Mobility Management Entity) receive that MA sends for asking the authentication request of network side mandate mobile agent ability, MA is authenticated, to MA return authentication result; MA broadcasts notice message, carries described authentication result in described notice message; Terminal, according to described authentication result, confirms that MA obtains network authorization mobile agent can be provided.Its detailed process can have following two kinds of modes to realize, and first kind of way comprises the steps:

S1, MA initiate Attach Request message, and this Attach Request message is as authentication request, and the request of carrying in this Attach Request message oneself is as the information of mobile agent.

S2, MME receive after Attach Request message, from HSS (Home Subscriber Server, home subscriber server) or aaa server (Authentication, Authorization, AccountingServer, authentication, mandate, accounting server) obtain subscription data, MA is authenticated.

S3, MME are after to MA authentication success, return to adhere to MA and accept message, this adheres to accepts to carry in message authentication result, authentication result comprises the security parameter of network authorization, and security parameter comprises: for terminal, MA is carried out to the parameters for authentication of legitimacy certification, the time period that mandate MA provides mobile agent service, the region (the TA list that for example MA can serve) that mandate MA provides mobile agent service, the terminal quantity that mandate MA provides mobile agent service.

In this step, to issue security parameter in accepting message be mainly to consider that not only network will authenticate MA adhering to, follow-up terminal also will authenticate MA, obtain the mandate of network with checking MA, authorized the terminal that its time period at special time, region are specific quantity that mobile agent service is provided.

After S4, MA have registered, in particular range, send notice message by wireless signal, to notice existing of oneself, notice message comprises: the ID of MA, network are that GUTI, MME that MA distributes are the capacity (number of terminals that MA has served, the number of terminals that can also serve, or load percentage) of TA, security parameter and the MA at MA TA List, the current place of MA distributed.

Wherein, it is that MA wishes that the terminal in this particular range can receive notice message that MA sends notice message in particular range, and this particular range is that terminal can be bound mobile scope with MA.

In this step, MA transmission notice message can be to send notice message by frequency range and the form of special planning, also can utilize the frequency range of the existing broadcast of mobile communication system to send notice message, the form of its notice message also can adopt the form of existing broadcast and in message, increase distinctive parameter, as ID of MA etc.

Above-mentioned steps is the verification process that completes MA by attachment flow, also can pass through other flow processs, for example TAU (Tracking Area Update, tracing section updating) flow process completes the verification process of MA, the verification process that yet can complete by newly-increased flow process above-mentioned MA, does not affect realization of the present invention.

S5, terminal enter the signal coverage areas of MA, receive notice message, and confirm in own specific duration always, in the signal coverage areas in this MA, to confirm oneself to stick on MA; Terminal authenticates MA according to the security parameter in notice message, confirms that current MA obtains network authorization the service of mobile agent can be provided.

Because terminal and MA are probably in moving process, may be in very short time in the signal coverage areas of terminal in certain MA in some cases, then just left the signal cover of this MA, for example, when the bus that MA has been installed drives near a terminal, just the terminal that is positioned at bus outside receives the notice message of this MA, because terminal in this case does not need the binding with MA, so need in the specific duration of terminal check oneself always could to judge in the signal coverage areas in this MA and oneself move following this MA.

On some large-scale vehicles, in order to serve a large amount of terminals, multiple MA may be installed.If terminal receives the notice message of multiple MA in specific duration in this step simultaneously, this step also comprises: terminal, according to predetermined strategy, selects a MA to carry out follow-up binding.Wherein, predetermined strategy can be to select according to the signal strength signal intensity of MA, to realize the load sharing between MA; Or, select according to the load percentage in the notice message of MA broadcast the MA that load is light; Or, select the larger MA of weighted value according to the weighted value of each MA (weighted value of MA is corresponding with the terminal quantity of the authorized service of MA, and terminal quantity is few, and weighted value is little, and terminal quantity is many, and weighted value is large); Or random select etc., also can select according to adhesion time span, concrete, such as in the signal coverage areas of a terminal in MA1 2 minutes, in the signal coverage areas in MA2 4 minutes, this terminal can select MA2 to carry out follow-up binding.

The second way comprises the steps:

T1, the pre-configured unsymmetrical key that comprises PKI and private key of network side, the feature of unsymmetrical key is to use the information of encrypted private key to only have corresponding PKI just can open, the information of encrypting that uses public-key only has corresponding private key just can open.The private key that network side is held is underground, PKI is sent to each terminal, can be by the PKI burning of network side in the smart card in terminal, also can terminal adhere to or TAU process in be distributed to terminal by network side, or the broadcast notification terminal sending by base station.

The pre-configured unsymmetrical key that comprises PKI and private key of T2, MA; When MA registers to network side, the PKI that MA is configured offers the MME of MA registration, such as, MA sends authentication request to the MME of its registration, in authentication request, carry the PKI that MA configures, MME confirms that MA can provide after mobile agent service, and the PKI and the MAID that configure with the encrypted private key MA that oneself configures, obtain the first encrypted section as authentication result and send to MA.

T3, MA use the own ID of private key to MA, the current timestamp configuring, and network is encrypted to information such as the mandates of MA, obtains the second encrypted section, and sends notice message, and this notice message comprises: the first encrypted section and the second encrypted section.

T4, terminal utilize the PKI of network side configuration to decipher the first encrypted section, obtain PKI that MA configures and the ID of MA, utilize the PKI that MA configures to decipher the second encrypted section, obtain the ID of MA and current timestamp, whether the ID of the MA in terminal judges the first encrypted section is identical with the ID of the MA in the second encrypted section, if, whether the difference that judges the timestamp in described current time stamp and described notice message exceedes threshold value, if not, confirm that MA obtains network authorization, mobile agent service can be provided.

By legitimacy authentication mode as above, guarantee that counterfeit MA cannot obtain the mandate of network, ensure to only have the mandate that just can obtain network through the MA of legitimacy certification, for terminal provides service.

Network side in the embodiment of the present invention one passes through MA (Mobile Agent, mobile agent) context and terminal context bindings, receiving after the position updating request of MA transmission, think and also carried out corresponding movement with the terminal of MA binding, therefore, do not need the terminal launch position update request message respectively of binding with MA, can determine the shift position of terminal yet, alleviated the processing load of network.

Embodiment bis-:

Consult Fig. 2, the embodiment of the present invention two provides a kind of motion management method, adopts single place mode to realize the binding of terminal and MA in the method, and the method comprises:

L1, terminal send TAU request message, this TAU request message is bind request, terminal can confirming oneself to stick in MA successor, when machine be initiated binding, as an embodiment preferably, the terminal of the embodiment of the present invention is initiated binding (this next one TAU can be the TAU that terminal triggers while shifting out current tracking area list, or in terminal, control cycle triggers the TAU that the timer expiry of TAU request triggers) in confirming oneself to stick in next TAU flow process after MA.The addressing information of the MME of the ID of the MA that in this message, the GUTI of carried terminal, terminal are selected and MA registration and binding instruction.Wherein the addressing information of the MME of MA registration can be the GUTI of MA, it fills in the field for wireless access network route bind-request message in TAU request message, owing to being originally MME Datagram of filling in endpoint registration for the field of wireless access network route bind-request message, the addressing information of the MME of its endpoint registration can be the GUTI of terminal, therefore the GUTI of terminal need to be placed in message in a newly-increased cell, wireless access network can route messages to the MME1 that MA registers according to the MME Code in the GUTI of MA in this TAU request message like this.

L2, MME1 (Mobility Management Entity, Mobility Management Entity) find MA context by the GUTI of MA, check that the mandate whether this MA obtains network provides mobile agent service.MME1 confirms that by the MME Code in the GUTI of terminal current being registered on oneself of terminal is still registered on other MME, if endpoint registration is (such as MME2) on other MME, MME1 obtains terminal context from MME2, be registered in above oneself if terminal is current, MME directly searches according to the GUTI of terminal the terminal context prestoring.(shown in figure, obtaining the contextual situation of terminal for MME1 from MME2)

L3, MME1 by terminal context relation to MA context, after this, MME1 knows that follow-up this binding terminal will move together with MA, and MME1 returns to the indication information of binding success to terminal, the indication information of this binding success can be that TAU accepts message, to indicate binding success.

Wherein, MME1 also can return to terminal the indication information of binding success, and terminal, sending after bind request, judges in specific duration whether receive the response message from MME1, if do not receive the response message of MME1, just thinks binding success.

Terminal is after binding MA success, when terminal moves between TA, to no longer initiate TAU request message, this TAU request message is location update request message, but now terminal can still be initiated TAU flow process periodically and maintain and the binding relationship of MA at network side by periodicity TAU flow process.And terminal can continue to receive the notice message of MA during binding, from notice message, obtaining MME is that the new TA List of MA distribution is as the current TA List of oneself.Certainly, terminal can be also own distribution T A List to MME request again in the time unbinding.

Above step has realized the binding of terminal and MA, and the terminal position that subsequent step is described MA agent binding upgrades.

The broadcast singal that L4, MA base stations detected send, finding oneself to have shifted out MME is that the TA List scope of oneself distributing enters a target following district TA2, MA initiates TAU request message (now TAU request message is primary importance update request); ENodeB receives this TAU request message, and sends add target following district mark TAI2 in this TAU request message after.Suppose that the MME1 that MA registered originally can be still tracking area TA2 service, TAU request message is routed to MME1 by eNodeB.

L5, MME1 receive after TAU request message, search the context of MA, for MA distributes new TA List and is kept in MA context, this new TA List includes but are not limited to: TAI2, MME1 returns to TAU to MA and accepts message, in this message, carry the new GUTI, the TA List that distribute into MA, can also comprise the quantity that has been tied to the terminal on MA, or the information such as percentage of loading.

Wherein, this MME1 can reduce the quantity of TA while being MA distribution T A List, to reduce the size of paging zone.

Due to MA and multiple terminal binding, act on behalf of the position update flow of multiple binding terminals, therefore the quantity of the location update message of terminal reduces in a large number, if the quantity that MME1 is the TA in MA distribution T A List reduces, in the time of call terminal, the broadcast coverage of base station is little, can save Radio Resource.

The embodiment of the present invention two is carried out associated by terminal context with MA context by MME1, terminal and MA are bound, and send the indication information of binding success to terminal, while movement between TA with indicating terminal, do not initiate TAU request, and receive at network side after the position updating request sending with the MA of multiple terminal bindings, think and also carried out corresponding movement with the terminal of MA binding, therefore, do not need the terminal launch position update request message respectively with MA binding, also can determine the shift position of terminal, alleviate the processing load of network.

Embodiment tri-:

Consult Fig. 3, the embodiment of the present invention three provides a kind of motion management method, adopts many places mode to realize the binding of terminal and MA in the method, and the method comprises:

M1, terminal are initiated TAU request message, this TAU request message is bind request, terminal can confirm oneself to stick in MA successor when machine initiate binding, in this message, carry GUTI and the binding instruction of ID, the MA of GUTI that network is terminal distribution, MA that terminal is selected.

In this many places scheme, owing to not needing wireless access network this TAU request message to be routed to the MME1 of MA registration, so fill in the GUTI of oneself in terminal " GUTI of terminal " field in TAU request message, and the GUTI of MA be filled up in other fields of message.

Wireless access network is determined the current MME2 of being registered in of terminal according to the MME Code comprising in the GUTI in " the GUTI field of terminal " in TAU request message, and this TAU request message is routed to MME2.

M2, MME2 find the context of terminal according to the GUTI of the terminal in TAU request message, and judge according to the GUTI of the ID of MA or MA whether oneself is the MME of the current registration of MA, if not, continue to judge oneself whether there is attached MA context, if existed, directly attached MA context and terminal context are set up associatedly, and will in attached MA context, be added 1 for the counter that records binding terminal quantity; If there is no attached MA context, sets up attached MA context, by associated to attached MA context and the foundation of terminal context, and is set to 1 for the counter that records binding terminal quantity in attached MA context.Then the context of determining MA according to the GUTI of MA, on MME1, is set up context relation with MME1.If while judging that obtaining MME2 is the MME of the current registration of MA, directly MA context and terminal context are bound.

Concrete, MME2 and MME1 set up context-sensitive mode: MME2 sends context relation request message to MME1, with notice, MME1 has set up attached MA context on MME2, wherein, attached MA context comprises: address and the contextual mark of corresponding MA of the MME1 of MA registration, wherein, the address of the MME1 of MA registration can be to obtain by inquiry DNS service according to the MME Code comprising in the GUTI of MA, and above-mentioned context relation request message comprises: the contextual mark of corresponding MA and the contextual mark of corresponding attached MA; Wherein, the contextual mark of corresponding MA is searched MA context for MME1, for example, can be the GUTI of MA; MME1 is according to the contextual mark of corresponding MA, find corresponding MA context, the upper MME2 contextual information of attached MA (comprising address and the contextual mark of corresponding attached MA of MME2) is deposited in MA context, and send context relation response to MME2.If there is attached MA context on MME2, illustrate that MME2 has set up context relation with MME1, when MME2 need not have terminal binding at every turn, all send context relation request message to MME1.But in the situation that incidence relation is set up, MME2 can timing send context relation updating message to MME1, this message comprises: the terminal quantity that the contextual state of attached MA (represent on MME2 whether have attached MA context) and/or attached MA context are bound, determine on MME2, whether there is attached MA context for MME1, and/or, know for MME1 the terminal quantity that the upper attached MA context of this MME2 is bound, and then add up the quantity of the terminal of binding on the associated all attached MA context of MA context.

M3, MME2 return to the indication information of binding success to terminal, the indication information of this binding success can be that TAU accepts message, to indicate binding success.

Wherein, MME2 also can return to terminal the indication information of binding success, and terminal is sending after bind request, if do not receive the response message of MME1, just thinks binding success.

Terminal is after binding success, when terminal moves between TA, to no longer initiate TAU request message, this TAU request message is location update request message, but now terminal can still be initiated TAU flow process periodically and maintain and the binding relationship of MA at network side by periodicity TAU flow process.And terminal continues to receive the notice message of MA during binding, from notice message, obtaining MME is that the new TAList of MA distribution is as the current TA List of oneself.Certainly, terminal can be also own distribution T A List to MME request again in the time unbinding.

The broadcast singal that M4, MA base stations detected send, finding oneself to have shifted out MME is that the TA List scope of oneself distributing enters a target following district TA2, MA initiates TAU request message; ENodeB receives this TAU request message, sends after adding target following district mark TAI2 in this TAU request message.Suppose that the MME1 that MA registered originally can be still tracking area TA2 service, TAU request message is routed to MME1 by eNodeB.

M5, MME1 receive after TAU request message, search the context of MA, and for MA distributes new TA List and is kept in MA context, this new TA List includes but are not limited to: TAI2.MME1 confirms to have set up context relation with other MME from MA context, if network configuration is by directly call terminal in TA List of network, from MA context, obtain address and the contextual mark of corresponding attached MA of associated MME, send tracing section updating notification message to this associated MME (such as MME2), in this message, carrying MME1 is the newly assigned TA List of MA and the contextual mark of corresponding attached MA, MME2 receives after this message, search attached MA context according to the attached MA Context identifier of correspondence, new TA List is kept in attached MA context.If not by directly call terminal in TA List of network, but by MA transfer, in this step, notify MME2 to upgrade TA List in attached context not necessarily.

M6, MME2 upgrade response message to MME1 returning tracking district.

M7, MME1 return to TAU to MA and accept message, carry new GUTI, the TA List distributing for MA and be tied to the quantity of the terminal on MA in this message.

In the embodiment of the present invention three, the MME2 of endpoint registration carries out associated by terminal context with attached MA context, and the MME1 of the MME2 of endpoint registration and MA registration sets up context relation, terminal and MA are bound, and send the indication information of binding success to terminal, while movement between TA with indicating terminal, do not initiate TAU request, receive after the position updating request sending with the MA of multiple terminal bindings at network side, think and also carried out corresponding movement with the terminal of MA binding.Therefore, do not need to distinguish launch position update request message with the terminal of MA binding, can determine the shift position of terminal yet, alleviated the processing load of network.In the present embodiment, between two MME, set up incidence relation by directly carrying out interacting message, in actual applications, for example, when the mobile management entity of MA registration and the mobile management entity of endpoint registration are being related to of loose coupling, also can, by transferring and set up this incidence relation in an intermediate NE, no longer describe in detail.

Embodiment tetra-:

Consult Fig. 4, the function to MA in the embodiment of the present invention four further strengthens, and makes MA have the function of mobile base station, and terminal is carried out binding by MA, adopts single place mode to realize the binding of terminal and MA, and the method comprises:

N1, terminal are initiated TAU request to MA, and this TAU request is bind request, the GUTI of carried terminal in this message, and this message can also be carried the relevant information of MA, and the relevant information of MA comprises: the ID of MA, TA, the GUTI of MA etc. at the current place of MA.If the relevant information of not carrying MA in this TAU request, MA can add the relevant information of MA in TAU request.

N2, MA send TAU request message to the MME1 of MA registration.

Wherein, whether this TAU request message still depends on through wireless access network the backhaul scheme that MA selects, if MA selects the wireless link of current mobile radio communication as backhaul, this message need to arrive network side by wireless access network; If MA selects other backhaul scheme, such as satellite, WLAN (WLAN (wireless local area network)), WiMax, do not need through wireless access network.

N3-N6 is identical with L2-L5.

In the embodiment of the present invention four, terminal sends TAU by MA and asks MME1, MME1 carries out associated by terminal context with MA context, realize the binding of terminal and MA, and send the indication information of binding success to terminal, while movement between TA with indicating terminal, do not initiate TAU request, receive at network side after the position updating request sending with the MA of multiple terminal bindings, think and also carried out corresponding movement with the terminal of MA binding, therefore, do not need the independent launch position update request of the terminal message with MA binding, also can determine the shift position of terminal, alleviate the processing load of network.

This embodiment tetra-is in single place mode as basis, describe terminal and carried out the mode of binding by MA, also can be in many places mode as basis, its implementation comprises: terminal sends bind request, MA or cut-in convergent gateway are routed to the bind request of terminal the Mobility Management Entity of endpoint registration, follow-up execution step is identical with M3 and M7, does not repeat them here.

Following several situation is after MA and terminal binding, the signaling between network side paging binding terminal, network side and terminal is connected to binding relationship, MA notice binding terminal after setting up is bound again and the flow process that unbinds is described.

One, network side paging binding terminal

After terminal and MA binding, network side thinks that the current location of MA is exactly the current location of terminal, therefore can be in the current tracking area of MA (being the TA List that MA distributes) when call terminal call terminal.

There are as follows three kinds of paging ways:

1, due to the TA List that in the MA context in MME or attached MA context, always in store MA distributes, so the MME of the current registration of terminal can indicate directly call terminal in the TA of MA List of wireless access network.

Wherein, in order to improve paging success rate, MME can indicate wireless access network except the paging zone in the TAList of MA (the paging zone in the TA List of MA is the current paging zone of MA) sends beep-page message, still send out beep-page message in the adjacent cells of the TA of MA List, to avoid in the time that MA is positioned at paging zone edge, the terminal of binding may be outside paging zone adjacent cells and cause not receiving beep-page message, paging failure.

2,, while adopting single place mode to realize the binding of terminal and MA, carry out call terminal by MA in network.

The MME1 of MA registration determines terminal to initiate paging, and first MME1 sends to MA by beep-page message, broadcast paging messages in the scope that MA covers at oneself; Terminal receives after beep-page message, can notify the MA beep-page message of going off the air, and respond paging by service request information to MME1.

3,, while adopting many places mode to realize the binding of terminal and MA, carry out call terminal by MA in network.

P1, MME2 determine call terminal, find on terminal context relation to attached MA context, obtain the address of the MME1 that MA registers from this attached MA context, send beep-page message to MME1, carry the mark of the terminal that needs paging in this message.

P2, MME1 receive after beep-page message, and beep-page message is sent to MA.

P3, MA be broadcast paging messages in the overlay area of oneself, with call terminal.

P4, terminal receive after beep-page message, can notify the MA beep-page message of going off the air, and sends service request information, with answer page to MME2.

In the time adopting the scheme of passing through MA call terminal, if MA adopts wireless access be connected to network side and discharge with the wireless connections of network side, may need first paging MA and re-establish wireless connections before the beep-page message of terminal is sent to MA; If MA adopts fixing access to be connected to network side, such as MA is placed on the place such as cinema, gymnasium, can directly send to MA to the beep-page message of terminal.

Two, the signaling between network side and terminal is connected the binding relationship after setting up

If when MA does not possess the function of signaling between transfer terminal and network and user face data, if terminal need to be carried out business, or, terminal needs to send the MME (such as MME2) of service request information to the current registration of terminal after receiving beep-page message, MME2 receives after service request information, set up with the signaling of terminal and be connected by wireless access network, to reply the service request information of terminal.And can recover the carrying between terminal and wireless access network according to the request of terminal.In the situation that terminal and network are set up signaling and be connected, terminal the same trigger condition when not binding with MA triggers the flow processs such as switching, TAU.

In the situation that terminal and network side are set up signaling and be connected, there are following two kinds of processing schemes for the binding relationship of terminal and MA:

1, on terminal and MME, all remove the binding relationship of terminal and MA.Terminal can be after signaling Connection Release, transfers that to be again tied to this MA after Idle state upper to, also can select new MA to bind.

Concrete, for single place mode, the MME1 (because this MME1 has obtained terminal context, so this MME1 is also the MME of the current registration of terminal) of MA registration deletes MA context and the contextual binding relationship of terminal.For many places mode, the MME2 of endpoint registration deletes attached MA context and the contextual binding relationship of terminal, and will subtract 1 for the counter that records binding terminal quantity, in the time that Counter Value is 0, from attached MA context, obtain the information of the MME1 of MA registration, send instruction to MME1 and delete context-sensitive notification message, described instruction is deleted context-sensitive notification message and is comprised: the contextual mark of corresponding MA, as used the GUTI of MA; MME1 deletes address and the contextual mark of corresponding attached MA of MME2 from MA context, to delete and the context relation of MME2.

As mentioned above, in the situation that terminal and network side are set up signaling and be connected, the binding relationship of removing terminal and MA, can avoid detecting in terminal the flow process that unbinds triggering after the coverage that oneself has shifted out MA, makes network processes flow process simple.

2, terminal and MME continue to keep binding relationship.In this case, even if terminal and network side have been set up signaling connection, in the time that terminal detects the overlay area of leaving bound MA, the flow process informing network side oneself that also needs to initiate to unbind has been left the overlay area of MA.

Three, MA notice binding terminal is bound again

After terminal and MA binding, save TAU request message quantity thereby no longer initiate TAU flow process while movement between TA.But in the time that the moving range due to MA has to more greatly occur MME switching, because change has occurred the MME of MA registration, under the scheme of single place, all contexts current and terminal that this MA binds all need to move on new MME; Under the scheme of many places, part even all binding terminal may also need to move to new MME upper (the new MME not necessarily moving to MA is identical), and because change has occurred the MME of MA registration, MA context relation relation between new MME and the MME of endpoint registration of MA registration needs to rebuild, in an embodiment of the present invention, network side first discharges the binding relationship of all terminals and MA, then notify MA, and initiate TAU flow process by the terminal of MA notice binding, again to bind, consult Fig. 5, its process specifically comprises:

Q1, MA shift out the tracking area in TA List, enter another TA, initiate TAU request message, and this message is second place update request message.The MME originally registering due to MA can not be new TA service, so wireless access network is selected a new MME (being new MME, the MME6 of MA registration), TAU request message is routed to MME6.

Q2, MME6 send and obtain MA context request to the MME (old MME, the MME5 of MA registration) of the original registration of MA.

Q3, MME5 receive obtaining after context request of MME6 initiation, if MA and terminal are bound in many places mode, from the context of MA, obtain address and the contextual mark of corresponding attached MA of associated MME, send instruction to the related MME of institute and delete context-sensitive notification message, this message comprises: the contextual mark of corresponding attached MA.Associated MME is (such as the old MME of endpoint registration, MME3) receive instruction and delete after MA context-sensitive notification message, search corresponding attached MA context, remove the binding relationship of attached MA context and terminal, and delete attached MA context, reply to MME5.

Q4, (be attached MA context and the removing of terminal context bindings relation that associated MME preserves after on own and the related MME of institute, this MA context is all removed with the contextual binding relationship of terminal, and the address of the associated MME preserving in the MA context on MME5 and corresponding attached MA Context identifier are eliminated), MME5 sends MA context to MME6.

Q5, MME6 oneself are the MME of the current registration of MA to HSS registration.

Q6, MME6 are that MA distributes new GUTI and TA List, return to TAU accept message to MA, carry as the newly assigned GUTI of MA, TA List and heavily binding instruction in this message.

Q7, MA receive that TAU accepts after message, confirm to need terminal again to bind according to heavily binding instruction, send and heavily bind notice message, and in heavily binding notice message, notify all terminals of binding with MA to carry out and again bind flow process.

Q8, terminal are received and are heavily bound after notice message, initiate TAU request message, the GUTI of the ID of the GUTI of carried terminal oneself, MA, MA in this message (MME6 is the newly assigned GUTI of MA) and binding instruction.

Initiate at short notice TAU and heavily bind the impact that network is caused in order to reduce a large amount of binding terminals, each terminal is heavily bound after notice message receiving, can random delay a period of time initiate TAU request message again.

Under the mode of many places, wireless access network is according to the GUTI of the terminal in this message, this TAU request message is routed to the MME (MME3) of the original registration of terminal, if this MME3 can not be the Terminal Service that enters new TA, wireless access network selects one can be the MME (such as MME4 is as the MME of terminal new registration) of TA service, now, this TAU request message is routed to MME4.

Q9, MME4 obtain terminal context from MME3.

Q10, MME4 confirm oneself not to be the MME of the current registration of MA according to the GUTI of the ID of MA or MA, judge oneself whether there is attached MA context, if existed, directly attached MA context are set up associated with terminal context; If there is no attached MA context, sets up attached MA context, and attached MA context is set up associated with terminal context.Then the context of determining MA according to the GUTI of MA, on MME6, is set up context relation with MME6, and the processing of heavily binding flow process is here identical with the processing of initial binding.

Q11, MME4 oneself are the MME of the current registration of terminal to HSS registration.

Q12, MME4 return to TAU to terminal and accept message, and in this message, carrying MME4 is the new GUTI that terminal is divided.

Heavily binding under the mode of many places is more than described, if MA and terminal are bound in single place mode, originally to register the MME (MME3) that MME (MME5) and terminal register be originally same MME to MA, and the MME (MME4) of MA new registration MME (MME6) and terminal new registration is same MME.Now, be with above description difference, in Q2, MME6 sends the instruction of obtaining context request and removing the binding relationship of MA and terminal to MME5, and in Q3, MME5 removes the binding relationship of MA and terminal, removes the contextual incidence relation of MA context and terminal.In Q10, MME4 sets up MA context and the contextual binding relationship of terminal.

As above again bind by MA indicating terminal, can realize and carry out MME while switching as MA, the binding again of MA and terminal, carries out after MME switching ensureing, network side still can move together with also according to the definite terminal binding together with it of the movement of MA.

Four, the flow process that unbinds

1, oneself shifted out after MA coverage when terminal detects, initiated TAU flow process and unbind.Fig. 6 shows the flow process that unbinds that terminal triggers, and specifically comprises:

R1, terminal detect that MA signal strength signal intensity is lower than predetermined threshold value, or require terminal to unbind in MA broadcast, terminal is initiated TAU request message, this TAU request is the request that unbinds, the ID of the GUTI of carried terminal, MA, the instruction that unbinds in this message, this TAU request message is routed to MME2 (MME of the current registration of terminal).

R2 is if single place mode, owing to tying up timing terminal context and be migrated to the MME1 of the current registration of MA, so the MME1 of the MME2 of the now current registration of terminal and the current registration of MA is a MME, delete the contextual binding relationship of MA context and described terminal.If under the mode of many places, the current registration of terminal MME2 confirms that terminal context relation is to attached MA context, and counter is subtracted to 1, in the time that counter values is 0, from attached MA context, obtain the information (address of MME1) of the MME1 of the current registration of MA, send instruction to MME1 and delete context-sensitive notification message; MME1 receives after this notification message, deletes information and the contextual mark of corresponding attached MA of this MME2 from MA context.(shown in figure, being many places mode)

Wherein, in the time that counter values is 0, can not send instruction to MME1 at once and delete context-sensitive notification message, but wait for a period of time, such as waiting for 30 seconds, to confirm whether have new terminal to bind with MA in the MME2 short time, if, do not send instruction and delete context-sensitive notification message, if not, send instruction and delete context-sensitive notification message.

R3, MME2 are that terminal is newly distributed GUTI and TA List, send TAU accept message to terminal, carry as the newly assigned GUTI of terminal and TA List in this message.

After unbinding, terminal enters a new tracking area during moving out the tracking area of TA List, as prior art, initiate TAU flow process informing network position and change.

Terminal described above detects and oneself has shifted out MA coverage, initiatively initiating TAU flow process unbinds, ensure in the time that fast mobile terminal goes out MA coverage, the binding relationship of MA and terminal is removed, so that can continue to trigger TAU flow process when follow-up fast mobile terminal as prior art, instead of determine the movement of this terminal according to the movement of MA, ensure that network side can obtain the shift position that terminal is correct.

2, in some cases, MA may determine to stop mobile agent service, such as the bus that MA has been installed has arrived terminal, or, in the time that MA bearing capacity declines, determine the more current terminals of having bound of batch de binding, Fig. 7 shows the flow process that unbinds that MA triggers, and specifically comprises:

S1, MA initiate TAU request, and the instruction of the current all terminals that unbind is carried in this TAU request.

The current registration of S2, MA MME1 receives this TAU request, if single place mode is removed terminal context and the contextual binding relationship of MA of all bindings.If when MME1 redistributes TA List for MA, the TA List in terminal context is not refreshed at every turn, the TA List in the terminal context of all bindings is arranged to the current TA List of MA also comprising before.If many places mode, MME1 obtains the information (address of MME and the contextual mark of corresponding attached MA) of associated MME from MA context, MME1 sends instruction to associated MME (such as MME2) and deletes context-sensitive notification message, carries the contextual mark of corresponding attached MA in this message.If when MME1 redistributes TA List for MA, all do not notify MME2 at every turn, this instruction is deleted in context-sensitive notification message and is also comprised the TA List that MA is current.MME2 searches attached MA context according to the contextual mark of attached MA, to there is the TA List in the terminal context of binding relationship to be arranged to the current TA List of MA with attached MA context, remove attached MA context and the contextual binding relationship of terminal, delete attached MA context, reply to MME1.(shown in figure, being many places mode)

The current registration of S3, MA MME1 returns to TAU to MA and accepts message instruction MA and unbind successfully, and this message comprises the TA List that MA is current.

S4, MA send and are used to indicate the discharged notice message that unbinds of binding relationship to terminal, and this notice message that unbinds comprises the TA List that MA is current.

When receiving, terminal unbinds after notice message, current MA in notice message TA List is saved as the current TA List of oneself, and remove own preservation and binding state MA, if be follow-up enter a new tracking area during moving out the tracking area of TA List, as prior art, initiate TAU flow process informing network position and change.

Because terminal may have with a certain distance from the MA of binding, under some rare cases, when the terminal of binding receives unbinding after notice message of MA, may find the scope of the tracking area that oneself has moved out the current TAList of MA, also be that TA List in the upper terminal context of preserving of MME2 is inaccurate, now to initiate that TAU flow process reports own accurate location and require to MME2 be own distribution T A List to terminal again.

As above be described as example taking MA all terminals that unbind, MA some terminal that also can unbind, for example under the scheme of many places, MA only asks to unbind and is registered in the binding relationship of the terminal on some MME, and its implementation is similar to foregoing description, does not repeat them here.

The MA of foregoing description triggers and unbinds, can be in the time that MA can not or stop as mobile agent, and the binding relationship of MA and terminal is removed in batches, and do not needed each binding terminal to initiate respectively to unbind flow process, thereby saved the signaling quantity unbinding.

The each embodiment of the invention described above is that terminal is initiatively initiated bind-request message, bind with request and MA, a kind of execution mode that this only provides for technical solution of the present invention, technical solution of the present invention is not limited to this, also can initiatively MA and terminal be bound by network side, such as, after the authentication success (authorizing MA to there is Mobile Agent In Function) of network side to MA, by the terminal of closing on MA position and MA binding, and send binding instruction to terminal after binding, when indicating terminal moves between TA, do not initiate TAU flow process, do not affect realization of the present invention.

Embodiment five:

Consult Fig. 8, the embodiment of the present invention five provides a kind of mobile management device, comprising:

Binding unit 801, for by MA context and terminal context bindings;

Binding success instruction transmitting element 802, for after described binding unit 801 is by MA context and terminal context bindings, to the indication information of terminal transmission binding success, launch position update request not when indicating described terminal to upgrade in position;

Position updating request receiving element 803, the position updating request sending for receiving described MA;

Determine unit, shift position 804, for after described binding unit is by MA context and terminal context bindings, according to described position updating request, revise described MA context, and determine that described terminal moves together with described MA.

Wherein, this mobile management device also can not comprise binding success instruction transmitting element 802, be that terminal is sending after bind request, in specific duration, do not receive response message, think and binding success do not need mobile management device successfully to bind instruction to terminal transmission expression MA and terminal binding.

Wherein, described binding unit 801 comprises:

Judging unit, for receiving after the bind-request message of requesting terminal and MA binding, judges whether described terminal is registered on oneself;

Terminal context acquiring unit, for when the judged result of described judging unit is when being, obtain terminal context from described mobile management device, when the judged result of described judging unit is while being no, from described terminal, current registered MME obtains terminal context;

Unit is set up in association, for terminal context and MA context relation that described terminal context acquiring unit is obtained.

If MA registered MME in the past, there is MME switching in MA, when this mobile management device is the new MME of MA registration, this device also comprises: notice is heavily bound unit, for receiving after the second place update request of MA transmission, obtain MA context and terminal context from the old Mobility Management Entity of MA registration, and indicate the old Mobility Management Entity that described MA registers to remove MA context and the contextual binding relationship of terminal, carry the position renewal of heavily binding instruction to described MA transmission and accept message; Binding unit 801 is for receiving after the bind-request message of requesting terminal and MA binding, by the described MA context and the terminal context bindings that obtain from the old Mobility Management Entity of MA registration.

Described device also comprises:

Paging indicating member 805, in described binding unit by after MA context and terminal context bindings, in the time of needs call terminal, instruction wireless access network call terminal in the current paging zone of MA; Or instruction wireless access network is at the current paging zone of MA and the adjacent cells call terminal of current paging zone; Or, send to MA the beep-page message that carried terminal identifies, to indicate described MA to carry out paging to described terminal.

First unit 806 that unbinds, in described binding unit by after MA context and terminal context bindings, when unbinding when instruction of receiving that MA sends, delete MA context and the contextual binding relationship of all terminals;

And/or,

Second unit 807 that unbinds, for in described binding unit by after MA context and terminal context bindings, when receive terminal send unbind indicate time, or, terminal and network side are deleted context and the contextual binding relationship of MA of described terminal after setting up signaling and being connected.

Can also comprise: bind-request message receiving element, for receiving the bind-request message of requesting terminal and MA binding; Described binding unit 801, for receiving after the bind-request message of requesting terminal and MA binding, by MA context and terminal context bindings.

The binding unit of the mobile management device in the embodiment of the present invention five is MA context and terminal context bindings, and launch position update request not when binding success instruction transmitting element indicating terminal upgrades in position, to reduce the processing load of network side; And receiving after the position updating request that MA sends, think and also carried out corresponding movement with the terminal of MA binding, therefore, do not need and the independent launch position update request of the terminal message of MA binding, also can determine the shift position of terminal.

Embodiment six:

Consult Fig. 9, the embodiment of the present invention six provides a kind of mobile management device, and this mobile management device can be the MME of endpoint registration under the mode of many places, comprising:

Unit 901 set up in attached MA context, for setting up attached MA context, by the MA context relation on the Mobility Management Entity of described attached MA context and MA registration;

Binding unit 902, for by terminal context and described attached MA context bindings.

Binding success instruction transmitting element 903, for setting up attached MA context, and by after terminal context and attached MA context bindings, to the indication information of terminal transmission binding success, launch position update request not when indicating described terminal to upgrade in position.

Wherein, this mobile management device also can not comprise binding success instruction transmitting element 903, be that terminal is sending after bind request, in specific duration, do not receive response message, think and binding success do not need mobile management device successfully to bind instruction to terminal transmission expression MA and terminal binding.

This device also comprises:

Paging zone list receiving element 904, for setting up unit at described attached MA context by after the MA context relation on the Mobility Management Entity of described attached MA context and MA registration, receive the position updating request of carrying new paging zone list of the Mobility Management Entity transmission of MA registration;

The first paging unit 905, for when the needs call terminal, instruction wireless access network call terminal in the listed current paging zone of described new paging zone list; Or, instruction wireless access network call terminal in the listed current paging zone of described new paging zone list and adjacent cells thereof.

Or,

The second paging unit, for binding unit by after terminal context and described attached MA context bindings, in the time of needs call terminal, the Mobility Management Entity of registering by MA sends beep-page message to MA, to indicate MA call terminal.

The first delete cells 906, for binding unit by after terminal context and described attached MA context bindings, receive terminal send unbind indicate after, or, after terminal and network side are set up signaling and be connected, delete context and the contextual binding relationship of attached MA of described terminal.

Counter unit 907, for deleting at the first delete cells after the context and the attached contextual binding relationship of MA of described terminal, will subtract 1 for the counter that records binding terminal quantity;

Context relation notice transmitting element 908 is deleted in instruction, in the time that Counter Value is 0, sends instruction delete context-sensitive notification message to the Mobility Management Entity of described MA registration.

Context notification message receiving element 909 is deleted in instruction, the instruction deletion context-sensitive notification message sending for receiving the Mobility Management Entity of MA registration;

The second delete cells 910, for receiving after described instruction deletion context-sensitive notification message, deletes terminal context and attached MA context bindings, and deletes described attached MA context.

This device can also comprise: bind-request message receiving element, for receiving the bind-request message of requesting terminal and MA binding; Described binding unit, for receiving after the bind-request message of requesting terminal and MA binding, by terminal context and described attached MA context bindings.

Attached MA context in the embodiment of the present invention six in Mobility Management Entity is set up unit and is set up for carrying out the attached MA context of context-sensitive with the MME of MA registration; Context bindings unit is terminal context and attached MA context bindings, to realize the binding of MA and terminal, and indicating terminal launch position update request not while upgrading in position, to reduce the processing load of network side; And receiving after the position updating request that MA sends, think and also carried out corresponding movement with the terminal of MA binding, therefore, do not need and the independent launch position update request of the terminal message of MA binding, also can determine the shift position of terminal.

Embodiment seven:

Consult Figure 10, the embodiment of the present invention seven provides a kind of terminal, and this terminal is mobile terminal, and it comprises:

Binding instruction acquiring unit 1001, for obtaining the indication information that represents terminal and MA binding success;

Control unit 1002 for getting after the indication information that represents terminal and MA binding success, is controlled and is not sent position updating request in the time that idle Idle state is moved.

Concrete, binding instruction acquiring unit 1001, for receiving the described terminal of expression of network side transmission and the indication information of MA binding success.

This terminal can also comprise: bind request transmitting element 1003, and for sending request the bind-request message of terminal and MA binding

This mobile terminal also comprises:

Notice message receiving element 1004, has the notice message of mobile agent ability for receiving the corresponding MA of expression that multiple MA send; Selected cell, for receiving after the notice message of multiple MA at described notice message receiving element, selects described MA and described terminal binding.

Terminal in the embodiment of the present invention seven is getting after the indication information that represents terminal and MA binding success, when mobile, control and do not send position updating request, so that network side can not receive and process a lot of location update request message within very short time, alleviate the processing load of network.

Embodiment eight:

Consult Figure 11, the embodiment of the present invention eight provides a kind of mobile agent device, comprising:

Authentication request transmitting element 1101, for sending authentication request to network side, described authentication request is used for asking network side mandate mobile agent ability;

Authentication result receiving element 1102, for receiving the authentication result of network side feedback;

Notice transmitting element 1103, for sending the notice message that carries described authentication result, there is mobile agent ability for mobile agent device described in terminal check.

This device also comprises:

The instruction transmitting element that unbinds, sends for the Mobility Management Entity to MA place the instruction that unbinds.

Heavily binding instruction receiving element, the heavily binding instruction sending for receiving the new Mobility Management Entity of MA registration;

Heavily bind notice message transmitting element, heavily bind notice message for sending.

Paging unit, for receiving the beep-page message of the carried terminal mark that the Mobility Management Entity of MA registration sends, according to described beep-page message, call terminal.

The mobile agent device that utilizes the embodiment of the present invention eight to provide, can be used as the mobile agent of terminal, the movement of proxy terminal.

Embodiment nine:

The embodiment of the present invention nine provides a kind of communication system, comprising: the MME of endpoint registration, and the MME of MA registration, wherein,

The Mobility Management Entity of endpoint registration, for setting up attached MA context, with the MA context relation on the Mobility Management Entity of MA registration, and by terminal context and attached MA context bindings;

The Mobility Management Entity of MA registration, for setting up MA context, the attached MA context relation with on the Mobility Management Entity of endpoint registration, receives the position updating request that described MA sends; According to described position updating request, determine that described terminal moves together with described MA.

In the embodiment of the present invention nine, pass through MA context and attached MA context relation, and by terminal context and attached MA context bindings, to realize MA context and terminal context bindings, receiving after the position updating request of MA transmission, think and also carried out corresponding movement with the terminal of MA binding, therefore, do not need the terminal launch position update request message respectively with MA binding, also can determine the shift position of terminal, alleviate the processing load of network.

One of ordinary skill in the art will appreciate that all or part of step realizing in above-described embodiment method is can carry out the hardware that instruction is relevant by program to complete, described program can be stored in a kind of computer-readable recording medium, for example, read-only memory, disk or CD etc.

The motion management method, relevant device and the communication system that above the embodiment of the present invention are provided are described in detail, applied specific case herein principle of the present invention and execution mode are set forth, the explanation of above embodiment is just for helping to understand method of the present invention and core concept thereof; , for one of ordinary skill in the art, according to thought of the present invention, all will change in specific embodiments and applications, in sum, this description should not be construed as limitation of the present invention meanwhile.

Claims

1. a mobile agent, is characterized in that, comprising:

Notice transmitting element, for sending the notice message that carries described authentication result, for terminal check mobile agent, MA has mobile agent ability.

2. mobile agent according to claim 1, is characterized in that, this mobile agent also comprises:

The instruction transmitting element that unbinds, sends for the Mobility Management Entity to MA place the instruction that unbinds, described in the instruction that unbinds be used to indicate described Mobility Management Entity deletion MA context and the contextual binding relationship of all terminals.

3. mobile agent according to claim 1, is characterized in that, this mobile agent also comprises:

Heavily binding instruction receiving element, the heavily binding instruction sending for receiving the new Mobility Management Entity of MA registration; Described heavy binding instruction is used to indicate the binding again of terminal and MA;

4. mobile agent according to claim 1, is characterized in that, this mobile agent also comprises:

5. a motion management method, is characterized in that, comprising:

Mobile agent MA sends authentication request to network side, and described authentication request is used for asking network side mandate mobile agent ability;

MA receives the authentication result of network side feedback;

MA sends the notice message that carries described authentication result, has mobile agent ability for MA described in terminal check.

6. method according to claim 5, is characterized in that, described method also comprises:

MA sends to the Mobility Management Entity at MA place the instruction that unbinds; The described instruction that unbinds is used to indicate described Mobility Management Entity and deletes MA context and the contextual binding relationship of all terminals.

7. method according to claim 5, is characterized in that, described method also comprises:

MA receives the heavily binding instruction of the new Mobility Management Entity transmission of MA registration; Described heavy binding instruction is used to indicate the binding again of terminal and MA;

MA sends and heavily binds notice message.

8. method according to claim 5, is characterized in that, described method also comprises:

MA receives the beep-page message of the carried terminal mark of the Mobility Management Entity transmission of MA registration, according to described beep-page message, call terminal.

9. method according to claim 5, is characterized in that,

Described mobile agent MA sends authentication request to network side, comprising:

MA initiates Attach Request message to Mobility Management Entity MME;

Described MA receives the authentication result of network side feedback, comprising:

MA receives and adhering to of MME feedback accepts message, wherein, this adheres to accepts to carry in message authentication result, described authentication result comprises the security parameter of network authorization, and this security parameter comprises: for terminal to MA carry out legitimacy certification parameters for authentication, authorize MA provide mobile agent service time period, authorize MA the region of mobile agent service is provided and authorizes MA that the terminal quantity of mobile agent service is provided.

10. method according to claim 9, is characterised in that,

Described notice message comprises: the ID of MA, network are that global unique temporary identity GUTI, MME that MA distributes are the capacity of tracking area TA, security parameter and the MA at MA tracking area list TA List, the current place of MA distributed.

11. methods according to claim 5, is characterized in that,

MA sends authentication request to the MME of its registration, wherein, carries the PKI that MA configures in this authentication request;

MA receives described MME feedback authentication result, and wherein, this authentication result is confirming that this MA can provide after mobile agent service, the first encrypted section that the PKI configuring with the encrypted private key MA that this MME configures and MAID obtain for MME.

12. methods according to claim 11, are characterised in that,

Described notice message comprises the first encrypted section and the second encrypted section;

Wherein, described the second encrypted section is used the private key of its configuration that the ID of MA, current timestamp and network are encrypted and are obtained to the authorization message of MA by MA.

13. methods according to claim 12, is characterized in that, described method also comprises:

Terminal utilizes the PKI of network side configuration to decipher the first encrypted section, obtain PKI that MA configures and the ID of MA, utilize the PKI that MA configures to decipher the second encrypted section, obtain the ID of MA and current timestamp, whether the ID of the MA in terminal judges the first encrypted section is identical with the ID of the MA in the second encrypted section, if, whether the difference that judges the timestamp in described current time stamp and described notice message exceedes threshold value, if not, confirm that MA obtains network authorization, mobile agent service can be provided.