CN102036220A

CN102036220A - Mobile management method and device

Info

Publication number: CN102036220A
Application number: CN2009101782363A
Authority: CN
Inventors: 张伟; 彭程晖; 李波杰; 陈育华; 李宏
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2009-09-25
Filing date: 2009-09-25
Publication date: 2011-04-27

Abstract

The embodiment of the invention discloses a mobile management method and device, which relate to the technical field of mobile communication and are invented for solving the problem that the mobile management of a mobile management system framework based on user identity in the prior art can not be carried out when user positions are changed. The mobile management method provided by the embodiment of the invention comprises the following steps of: receiving a request message sent by first domain routing equipment by first equipment, wherein user identification and the address of the first domain routing equipment are carried in the request message; and updating the address of the domain routing equipment corresponding to the user identification stored in the local into the address of the first domain routing equipment carried in the request message by the first equipment according to the user identification. The embodiment of the invention realizes the mobile management for the mobile management system framework based on the user identity.

Description

A kind of motion management method and device

Technical field

The present invention relates to the mobile communication technology field, relate in particular to a kind of motion management method and device.

Background technology

The dual semanteme that the IP address of the middle use of internet (Internet) at present has topology location (Locator) and sign (Identifier).Wherein, from the angle of network topology, the IP address has described Locator semanteme, and a topology location when promptly certain main frame access network is represented in the IP address when main frame moves, needs the IP address to change thereupon; From application point of view, the IP address has described sign (Identifier) semanteme, it is the identity that main frame has been represented in the IP address, when inter-host communication, the IP address is as a sign (Identifier) of the mutual identification of communicating pair, using under the state that connects not disconnection, need the IP address to remain unchanged as far as possible for a long time.At the beginning of the Internet design, this simple design of the dual semanteme in IP address meets network demand at that time, be today the Internet obtain one of key factor of immense success.But, along with the develop rapidly of the increasing of Internet user, wireless network and people expansion to ubiquitous communication requirement, the way of this locator in IP address and Identifier coupling has caused some problems, wherein bad to ambulant support is one of subject matter, and promptly when main frame moved, variation had taken place in the position that it is linked into network, corresponding change need be made in the IP address, but this moment, the identity of main frame did not change, and the IP address should not change, and had therefore produced contradiction.

On the other hand, mobile communication and Internet obtain huge development respectively, impel the user constantly to enlarge by the demand that mobile device obtains the Internet service.When communicating by letter between the user, where less relevance the other side is positioned at, and has used what equipment, whom is and mainly pay close attention to the other side, and the therefore following network must be the center with the user rather than with the main frame.But the present Internet network architecture is to be center rather than customer-centric with the main frame, causes the user can not get access to the Internet service whenever and wherever possible easily.

Like this, get access to the required information and the needs of service from Internet whenever and wherever possible in order to satisfy more and more users, proposed a kind of mobile management system framework, thereby solved the dual semanteme of described IP address and the network architecture problem of customer-centric based on user identity.

In realizing process of the present invention, the inventor finds to have following problem in the prior art at least: the mobile management system framework based on user identity of described proposition, when customer location changes, can't carry out mobile management.

Summary of the invention

The embodiment of the invention provides a kind of motion management method and device, to realize the mobile management based on the mobile management system framework of user identity.

For achieving the above object, embodiments of the invention adopt following technical scheme:

On the one hand, the embodiment of the invention provides a kind of motion management method, and described motion management method comprises:

First equipment receives the request message that the first territory routing device sends, the address of carrying user ID and the described first territory routing device in the described request message;

First equipment is according to described user ID, the address of the territory routing device of the described user ID correspondence of this locality storage is updated to the address of the described first territory routing device that carries in the described request message.

On the other hand, the embodiment of the invention also provides a kind of motion management method, and described motion management method comprises:

Receive to insert the request message that entity sends, carry the described user's that user ID and described access entity obtain station location marker in the described request message;

According to the user ID of carrying in the described request message, the station location marker of the described user ID correspondence of this locality storage is updated to the described user's that described access entity obtains station location marker.

On the one hand, the embodiment of the invention also provides a kind of signatory location server again, and this server comprises:

Receiving element is used to receive the request message that the first territory routing device sends, the address of carrying user ID and the described first territory routing device in the described request message;

Updating block is used for according to described user ID, the address of the territory routing device of the described user ID correspondence of this locality storage is updated to the address of the described first territory routing device that carries in the described request message.

On the one hand, the embodiment of the invention also provides a kind of territory routing device again, and this territory routing device comprises:

Receiving element is used to receive and inserts the request message that entity sends, and carries the described user's that user ID and described access entity obtain station location marker in the described request message;

Updating block is used for the user ID of carrying according to described request message, the station location marker of the described user ID correspondence of this locality storage is updated to the described user's that described access entity obtains station location marker.

On the one hand, the embodiment of the invention also provides a kind of access entity again, and this access entity comprises:

Acquiring unit is used to obtain described user's station location marker, and described station location marker is a station location marker of described access entity itself, is a station location marker of described user's independent allocation for described access entity or other network side entities perhaps;

Transmitting element is used to send the station location marker update inquiry information, carries the described user's that user ID and described access entity obtain station location marker in the described station location marker update inquiry information.

Again on the one hand, the embodiment of the invention also provides a kind of overall situation location server of contract, and this overall situation location server of contracting comprises:

Receiving element is used to receive the signatory location server query requests in the territory, local that carries user ID that signatory location server sends;

Query unit is used for according to described user ID, searches described user's signatory location server address, territory, local;

Return the unit, be used for the signatory location server address information in the described described user's who inquires territory, local is sent to the signatory location server that sends query requests.

A kind of motion management method and device that the embodiment of the invention provides by receiving the request message that the first territory routing device sends, carry the address of the user ID and the first territory routing device in the described request message; And, the address of the territory routing device of described user ID correspondence is updated to the address of the described first territory routing device according to the user ID of carrying in the described request message.A kind of motion management method and device that the embodiment of the invention provides also by receive inserting the request message that entity sends, carry the described user's that user ID and described access entity obtain station location marker in the described request message; According to the user ID of carrying in the described request message, the station location marker of the described user ID correspondence of this locality storage is updated to the described user's that described access entity obtains station location marker.Thereby realized under the mobile management system framework based on user identity the mobile management when customer location changes.

Description of drawings

A kind of mobile management system structure chart that Fig. 1 provides for the embodiment of the invention based on user identity;

A kind of motion management method flow chart that Fig. 2 provides for the embodiment of the invention one;

A kind of motion management method flow chart that Fig. 3 provides for the embodiment of the invention two;

Access domain Visited SLS carries out Home SLS and upgrades flow chart in a kind of motion management method that Fig. 4 provides for the embodiment of the invention to Home Domain territory;

The routing optimality flow chart that territory routing device and Correspondent Node carry out in a kind of motion management method that Fig. 5 provides for the embodiment of the invention;

Trigger SLS by the network side decision-making in a kind of motion management method that Fig. 6 provides for the embodiment of the invention and upgrade flow chart;

A kind of signatory location server structural representation that Fig. 7 provides for the embodiment of the invention;

A kind of territory routing device structural representation that Fig. 8 provides for the embodiment of the invention;

A kind of access entity structure schematic diagram that Fig. 9 provides for the embodiment of the invention;

The signatory location server structural representation of a kind of overall situation that Figure 10 provides for the embodiment of the invention.

Embodiment

Below in conjunction with accompanying drawing a kind of motion management method and the device that the embodiment of the invention provides is described in detail.

In order more clearly to describe described motion management method and device, at first described mobile management system framework based on user identity is simply introduced.As shown in Figure 1, solid line is a data flow in this accompanying drawing; Dotted line is a signaling flow.Wherein, described mobile management system based on user identity is divided into a plurality of territories with whole network, and wherein said territory can be divided for foundation according to the topology information of network, operation strategy, geographical location information etc.; At least comprise in each territory: signatory location server (Subscriber Location Server, SLS), at least one territory routing device (Domain Router, DR) and at least one insert entity.In described mobile management system, can also comprise a signatory location server (Global SLS) of the overall situation that is independent of each territory based on user identity.

Wherein, storage other territory, local of level, territory Home Domain information among the signatory location server Global SLS of the described overall situation.Can comprise the indication of user Home Domain in the user ID, Global SLS can inquire about corresponding Home Domain information according to the indication of the user Home Domain that comprises in the user ID, and then obtains this user's Home SLS.

Mapping relations among the described signatory location server SLS between storage its contracted user's CAMEL-Subscription-Information and described contracted user's user ID and the DR that this user is currently connected to, can also store other territories user's who roams into this territory relevant information among the SLS, such as current DR of this roamer etc., whether store these roamers' information among the SLS, depend on contracting between network strategy and the operator; Described SLS is the chain of command entity, does not participate in data forwarding, only is used for processing signaling.Wherein, described user's CAMEL-Subscription-Information comprises user ID, user's context, files on each of customers (profile) or the like.The territory, local (Home Domain) that should signatory territory be called this user, when the user moves out the territory, local, when arriving another territory, then this another territory is called this user's access domain (Visited Domain).In addition, described SLS also is used to the user who inserts in its territory to distribute DR.

Store the mapping relations of the current local topology position (local locator) of user ID and user among the described territory routing device DR; Described DR is the data surface entity, is used for the relevant signaling of deal with data, is responsible for the inside and outside data forwarding in territory simultaneously, and DR is the first order convergence point in extraneous packet turnover territory.In addition, when user's mobile needs carried out DR switching renewal, the DR after then switching arrived SLS with user's DR update notification.

Described access entity, be used to access subscriber equipment wherein to obtain local locator, can be directly with himself local locator as the local locator that inserts subscriber equipment wherein, can be local locator of described subscriber equipment independent allocation also by described access entity or other network side entities; Described access entity also need with insert wherein user ID with and the corresponding local locator territory routing device DR that notifies it to be belonged to.The access entity of subscriber equipment is the second level convergence point of transfer of data in the territory.In IP network, described access entity can for insert routing device (access router, AR); In wireless network, described access entity can for gateway (Gateway, GW); Long Term Evolution (Long Term Evolution, LTE) in the system, described access entity can for gateway (Serving Gateway, S-GW).

Storage user's ID in the subscriber equipment, the user can select to preserve or do not preserve current access entity and be its local locator that obtains, if do not preserve its local locator in the subscriber equipment, then inserting entity need preserve for the user, and whether subscriber equipment preserves local locator, can be by consulting to determine with the access entity.

It should be noted that, described mobile management system based on user identity needs to distribute the unique user ID of the overall situation for each user in advance, for example in user and operator when signatory, operator is user's distributing user ID, this ID can also can pass through certain algorithmic transformation directly as this user ID when user-network access, such as the hash functional transformation, generate the user ID of set form.Described user ID is used for the user ID layer of communication protocol stack, and is used for the user identity identification of data transmission procedure, can be used as one of foundation of packet route.Wherein, described user ID layer can be realized in network layer or between network layer and transport layer, concrete: when the user ID layer is positioned at the network layer of communication protocol stack, user ID can be the part of network layer address, so has just comprised the user ID of source user and purpose user's user ID in the network layer packet header; And when the user ID layer in communication protocol stack between network layer and the transport layer time, need in communication protocol stack, increase one deck newly, accordingly, all packets will have a new user ID layer packet header, will comprise the user ID of source user and purpose user's user ID in the user ID layer packet header.Need to prove that the above communication protocol stack can be the ICP/IP protocol stack, or meet the protocol stack of OSI seven layer network reference models, or communication network existing protocol stack etc.

It is also to be noted that the station location marker of a kind of local of being called locator of employing is realized the route of packet in each territory, local locator does not require that the overall situation is unique, only requires in the territory unique.But, belonging between the network entity of same area not and communicate by letter, or when network entity is communicated by letter with the network entity on the Internet in the territory, need to use a kind of station location marker that is called overall topology location Global locator, Global locator requires the overall situation unique.Like this, just require first order convergence point DR should have a Global locator at least.In real network, local locator and Global locator can show as the IP address, and the former can be a private IP address, but the latter must be a public ip address.

When the user moves, take place in the same DR span into the switching of entity the time, user's local locator will change, then the mapping relations of the current local locator of user ID of storing among the DR and user need to upgrade; When the user is moved further the switching of striding DR, need to set up in the new DR after moving or upgrade the mapping relations of the current local locator of user ID and user, the mapping relations between the current DR of user ID of storing among the SLS and user also need to upgrade; If cross-domain switching has taken place the user, then need to carry out on the SLS in the user Home Domain territory renewal of the mapping relations of user ID and the current DR of user.Therefore, by specific embodiment motion management method of the present invention and device are described in detail below.Following examples are that GW is an example to insert entity all, and establishing GW1 is that the i.e. first access entity of entity is inserted in the source, and GW2 is that purpose access entity promptly second inserts entity; DR1 is the i.e. second territory routing device of territory, source routing device, and DR2 purpose territory routing device i.e. the first territory routing device.

As shown in Figure 2, be a kind of motion management method that the embodiment of the invention one provides, when this method is switched for stride GW in DR as the user, the more new technological process of described DR; The specific implementation process of this flow process is as follows:

200: the source is inserted between entity GW1 and the purpose access entity GW2 and is carried out handover negotiation optimization, so that GW1 judges whether to send handoff request message to GW2, promptly whether carry out step 201.Wherein, the GW1 decision can comprise to the trigger condition that GW2 sends handoff request message: GW2 finds that the user moves under the coverage of oneself, then send the handover trigger request message, carry this mobile subscriber's user ID and the address of GW2 in this message to GW1; Perhaps GW1 receives user's indication, indicates this user to move under the scope of GW2.More than one of two kinds of trigger conditions take place or two kinds all take place all passable.

It should be noted that GW1 receives any handover triggering condition, and after determining carry out step 201, just can directly ignore another trigger condition.

201:GW1 inserts entity GW2 to purpose and sends handoff request message, carries mobile subscriber's user ID in this handoff request message, and switches relevant context between user GW.

202: purpose inserts entity GW2 and receives the handoff request message that GW1 sends, and described GW2 obtains a new station location marker local locator for the user.

In order to obtain described new local locator, purpose inserts the local locator of can be an own local locator of entity GW2 as described user own, perhaps GW2 also can be new local locator of described user's independent allocation, can also be that described user distributes a new local locator perhaps, get access to by sending modes such as request by GW2 by other entities of network side.

203: purpose inserts entity GW2 and sends station location marker update inquiry information (locator update Request) to the territory of current connection routing device DR, and the user ID and the described GW2 that carry the mobile subscriber in this message are the local locator that described mobile subscriber newly obtains.

204:DR receives purpose and inserts the station location marker update inquiry information (locator update Request) that entity GW2 sends, and the station location marker in the binding relationship of the described mobile subscriber's of oneself storage user ID and its station location marker is updated to the station location marker that carries among the described locator update Request, it is that described mobile subscriber newly gets access to that this station location marker is purpose access entity GW2.

205:DR sends the position to GW2 and upgrades acknowledge message.

206:GW2 sends switch acknowledgment message to GW1 after receiving described position renewal acknowledge message.

It should be noted that, when the user carries out in the handoff procedure at described source access entity GW1 and purpose access entity GW2, for the upstream data bag, GW1 directly sends to DR, and for downlink data packet, entity GW1 is inserted in the source needs buffer memory DR to be handed down to described user's downlink data packet, so as to switch finish after, GW1 is transmitted to purpose with described packet and inserts entity GW2, is handed down to the user by GW2; Thereby can guarantee that described packet do not lose, and then guarantee the continuity of user and Correspondent Node.

It is also to be noted that if the user need perceive Locator, then GW2 issues locator setting up in the process of carrying with the user, and the new bearer between GW2 and the user sets up process, can occur in any time after the step 201.

It is also to be noted that when subscriber equipment itself detects it when moving to GW2, described subscriber equipment can directly send to GW2 and switch message, and then finishes DR and upgrade; More new technological process is similar for its handling process and above-mentioned DR, and its difference only is, described user directly sends switches message to GW2, and need not other entity triggers user and send switching message.

A kind of motion management method that the embodiment of the invention one provides, the territory routing device inserts the station location marker update inquiry information that entity sends by receiving purpose, and insert entity according to the user ID of carrying in the described station location marker update inquiry information and described purpose and be its station location marker that obtains, station location marker in the binding relationship of described user ID and its station location marker is updated to purpose access entity is its station location marker that obtains, realized in the mobile management system framework based on user identity, because entity is inserted in user's source and purpose inserts inter-entity switching, the more new management of the territory routing device that is carried out.

As shown in Figure 3, be a kind of motion management method that the embodiment of the invention two provides, this method is when striding the DR switching in the same territory, the more new technological process of SLS.When switching, corresponding GW also switches at the described DR that strides, but the renewal operation at GW DR place when switching is identical with the described embodiment of Fig. 2 with flow process, so detailed description no longer in the present embodiment.In the present embodiment, SLS is first equipment, and purpose territory routing device DR2 is the first territory routing device, and territory, source routing device DR1 is the second territory routing device; GW1 is the first access entity, and GW2 is the second access entity; The more new technological process of the first equipment SLS is as follows in the present embodiment:

300: carry out handover negotiation optimization between territory, source routing device DR1 and the purpose territory routing device DR2,, promptly whether carry out step 301 so that DR1 judges whether to send territory routing device handoff request message to DR2.

Wherein, the DR1 decision can comprise following scene to the trigger condition that DR2 sends territory routing device handoff request message: scene one, GW2 finds that the user moves under the coverage of oneself, then send the handover trigger request message to DR2, DR2 continues to send territory routing device handover trigger request message to DR1 again, all carries address and this mobile user identification of GW2 in described handover trigger request message and the territory routing device handover trigger request message; Scene two, GW1 receives user's indication, indicates this user to move under the scope of GW2, then GW1 sends the handover trigger request message to DR1, wherein, carries address and this mobile user identification of GW2 in the described handover trigger request message; Scene three, can direct communication if belong between GW1 under the different DR and the GW2, then GW2 can directly send the handover trigger request message to GW1, send the handover trigger request message by GW1 to DR1 then, perhaps GW2 directly sends the handover trigger request message to DR1, carries address and this mobile user identification of GW2 in the described handover trigger request message.

It should be noted that one of above trigger condition or its combination in any, can take place simultaneously that DR1 receives any trigger request, and after determining carry out step 301, can directly ignore other trigger request.

301: territory, source routing device DR1 sends territory routing device handoff request message to purpose territory routing device DR2, carries user ID, purpose in the described handoff request message and inserts the context that switches between the address of entity GW2 and user domain routing device.

302:DR2 receives described territory routing device handoff request message, and according to the user ID of wherein carrying, judge whether its this locality stores this user's relevant information, if DR2 judges its this locality and does not store this user profile, perhaps Cun Chu this user profile is out of date, then carries out following steps.

303:DR2 sends territory routing device update request (DR update Request) to signatory location server SLS, carry address and the user ID of purpose territory routing device DR2 in the described update request, so that described signatory location server SLS finishes the renewal of the binding relationship between the user ID of its storage and the DR that the user is currently connected to.

304: after described signatory location server SLS receives described DR update Request, the DR address is updated to the address of carrying in the DR update Request message, the i.e. address of purpose territory routing device DR2 in the binding relationship between the DR that the user ID and the user of its storage is currently connected to.

305: after described signatory location server SLS upgrades and finishes, described signatory location server SLS sends the territory routing device to described purpose territory routing device DR2 and upgrades acknowledge message, carries the described user-dependent contextual information of storage in the described signatory location server in the described renewal acknowledge message; Wherein said contextual information comprises: safe key, QoS parameter and files on each of customers etc.Described signatory location server SLS can obtain described user-dependent contextual information by user ID, sends to described purpose territory routing device DR2 thereby upgrade acknowledge message by described territory routing device.

306: described purpose territory routing device DR2 according to the GW2 address that obtains in the step 301, carries out the station location marker renewal process with GW2 after receiving the territory routing device renewal acknowledge message of SLS transmission.Described position updating process is specific as follows: DR2 sends the position to GW2 and upgrades and trigger message, after GW2 receives, carries out the step 202-203 in embodiment illustrated in fig. 2, and after step 307 is finished, proceeds step 205.In the described position updating process, can also comprise the loading establishing process that inserts entity GW2 with purpose.

307: described purpose territory routing device DR2 sets up the binding relationship of user ID and station location marker, and in this locality this binding relationship is stored.This step corresponds among the embodiment shown in Figure 2, is similar to step 204, and difference is in this step it is to rebulid a binding relationship, and is to upgrade in the step 204.

308: after described purpose territory routing device DR2 finishes the establishment of binding relationship and foundation and purpose and inserts the carrying of entity GW2, send the territory routing device to territory, source routing device DR1 and switch and finish acknowledge message;

309: territory, described source routing device DR1 receives after described switching finishes acknowledge message, will discharge the described user-dependent binding relationship of its storage, and the carrying between release and the GW1.Wherein, described DR1 stored binding relationship, and the release of DR1 and GW1 carrying can be triggered by described purpose territory routing device DR2 or SLS or GW1; For example: can send the release buffered message to territory, described source routing device DR1 by described purpose territory routing device DR2, perhaps, send the release buffered message to territory, described source routing device DR1 by SLS, perhaps insert entity GW1 and send the release buffered message to territory, described source routing device DR1 by the source.

It should be noted that for example: GW1 can discharge the user ID corresponding cache as long as GW1 receives that after the described switch acknowledgment message, the buffer memory of described GW1 can discharge.

It is also to be noted that, the trigger condition that the above buffer memory discharges all is optional, can also be with the release of mode controls buffer memory such as the lifetime (lifetime) is expired, promptly in GW and DR, timer is set, when timer then, GW and DR also do not receive update request, and then GW and DR discharge the corresponding cache record voluntarily, and described caching record is exactly the binding relationship of user ID and its correspondence position sign the GW middle finger; Described caching record is exactly the binding relationship of user ID and its corresponding domain routing device address described DR middle finger.

A kind of motion management method that the embodiment of the invention two provides, territory routing device update inquiry information by the described first signatory location server SLS reception sources territory routing device transmission, and according to the address of user ID of carrying in the routing device update inquiry information of described territory and purpose territory routing device, current DR address in the binding relationship between the address of the DR that the user ID and the user of its storage is currently connected to, be updated to the address of purpose territory equipment DR2, realized in the mobile management system framework based on user identity, since user's territory, source routing device and the switching between the routing device of purpose territory, the more new management of the signatory location server that is carried out.

The above same territory can be meant mobile subscriber's Home Domain, also can be user's Visited Domain.When the territory that the described DR of striding switches is Visited Domain, dispose CAMEL-Subscription-Information between situation and two territories according to real network, the Visited SLS that can be chosen in the Visited Domain upgrades, Home SLS renewal is carried out in the Home Domain territory that perhaps is chosen in the mobile subscriber place, perhaps can also be chosen in described access domain Visited SLS upgrades, also need to carry out Home SLS simultaneously and upgrade, wherein need to carry out process that HomeSLS upgrades as shown in Figure 4 to Home Domain territory to the Home Domain territory at described mobile subscriber place.Among the embodiment shown in Figure 4, the signatory location server Visited SLS of described user's access domain is first equipment, and this Visited SLS can be the SLS described in the embodiment as shown in Figure 3, and the specific implementation process of this embodiment is as follows:

The territory routing device update inquiry information (DR update Request) that 401:Visited SLS acceptance domain routing device DR2 sends, carry address and the user ID of purpose territory routing device DR2 in the routing device update inquiry information of described territory, this step corresponds to embodiment shown in Figure 3 and is step 303.

402: according to the user ID in the routing device update inquiry information of described territory, described Visited SLS finds that described user is the roamer, be that Visited SLS finds the not information such as context of this user's correspondence of buffer memory of its this locality, find that perhaps this user belongs to another territory, i.e. this user another one territory of having contracted, then continue to judge whether to find in this locality the address information of this user's Home SLS, promptly judge local address information of whether having stored described roamer's Home SLS, if can not find, execution in step 403, if can find the Home SLS address information of this user's correspondence, then execution in step 404;

403: described Visited SLS initiates the process of inquiring user local territory SLS to the signatory location server Global SLS of the overall situation.

This process is specific as follows: Visited SLS sends territory, local SLS query requests (the query home SLS) message that carries user ID and gives the overall situation signatory location server Global SLS; Carry Home Domain indication in the described user ID, Global SLS can be according to the Home Domain information of this user's correspondence of Home Domain indication inquiry that comprises in the user ID, and then obtain this user's Home SLS address information, and this user's that will inquire Home SLS address information is notified to Visited SLS.Then, continue to carry out following steps again.

404: according to the territory routing device update inquiry information described in the step 401, described Visited SLS sends the signatory location server Home SLS of territory routing device update request to described user's territory, local, so that the binding relationship between the DR address that user ID in the signatory location server Home SLS renewal local cache in territory, described local and user are currently connected to.

405: the DR address is updated to the address of carrying in the routing device update inquiry information of territory, the i.e. address of DR2 in the binding relationship between the DR address that the signatory location server Home SLS in territory, described local is currently connected to described user ID and user.

406: the signatory location server Home SLS in territory, local sends the territory routing device to Visited SLS and upgrades acknowledge message (DR update response), carry described user's contextual information in the described renewal acknowledge message, this information comprises: a kind of or its combination in any among safe key, QoS parameter, the user profile.

407: after finishing above-mentioned Home SLS renewal, if described Visited SLS can proceed the user ID of himself and the renewal of the binding relationship between its DR address that is currently connected to, then VisitedSLS is updated to the DR address that is currently connected to of user ID correspondence the address of DR2; Perhaps, if described Visited SLS can set up the binding relationship between user ID and its DR address that is currently connected in this locality, then Visited SLS sets up this binding relationship, and stores in this locality.Afterwards, the operation of Visited SLS such as the step 305 among Fig. 3 repeat no more to step 309 herein.

It should be noted that described Visited SLS need carry out the user ID of himself and the renewal of the binding relationship between its DR address that is currently connected to or the foundation of binding relationship and also can finish in step 402.

What deserves to be explained is that among above-described all embodiment, the user when mobile cross-domain switching may take place, before and after promptly moving two DR of process belong to different territories.Because between the DR, between DR and the SLS, and between the SLS, all be to communicate by letter by IP, the communication between them is not subjected to the restriction in territory, and therefore the flow process of switching between DR in switching and the territory between cross-domain DR is similar.Move the different in kind in former and later two territories according to the user, switching is divided into three kinds of scenes between cross-domain DR:

Scene one: the user moves to purpose Visited Domain by source Visited Domain;

Under this scene, the more new technological process of SLS in the Visited Domain territory and described embodiment flow process shown in Figure 3 are basic identical, the difference part is the SLS among Fig. 3, in this scene, refer to the SLS in the purpose Visited Domain, and operation corresponding to SLS in the step 304 of Fig. 3, SLS in the purpose Visited Domain in this scene also can inquire about the record that whether has this user ID correspondence in the local cache earlier, if there is respective record, then only needs to upgrade original record and get final product; If there was not the record of described user ID correspondence before among the SLS in the described purpose Visited Domain, SLS in the then described purpose Visited Domain can newly set up a record in this locality, the binding relationship between storage user ID and the current purpose DR of this user.

And under this kind scene, according to the signatory agreement between the territory, purpose Visited SLS can also initiate the more new technological process to user Home SLS, and more the flow process among new technological process and the embodiment shown in Figure 4 is identical for this, repeats no more herein.

Scene two: the user moves to Visited Domain by Home Domain

Handling process under this kind scene and scene one handling process are basic identical, just correspond to the SLS among described Fig. 3 embodiment equally, refer to the SLS in the Visited Domain under this scene.

And under this kind scene, according to the signatory agreement between the territory, purpose Visited SLS can also be to user Home SLS initiation more new technological process as shown in Figure 4.

Scene three: the user moves to Home Domain by Visited Domain

Handling process under this kind scene and scene one handling process are basic identical, just correspond to the SLS among described Fig. 3 embodiment equally, refer to the SLS in the Home Domain under this scene, owing to necessarily preserved the binding relationship between user ID and the user DR among the Home SLS, therefore, Home SLS only needs directly relative recording to be updated to new DR and gets final product the flow process that also no longer exists home SLS to upgrade.

In a kind of motion management method that the embodiment of the invention provides, the signatory location server Home SLS in territory, local is by receiving the territory routing device update inquiry information that Visited SLS sends, and according to the address of user ID of carrying in the routing device update inquiry information of described territory and purpose territory routing device, current DR address in the binding relationship between the address of the DR that the user ID and the user of its storage is currently connected to, be updated to the address of purpose territory equipment DR2, realized in the mobile management system framework based on user identity, because the user is at Visited domain or cross-domain territory, source routing device during with the switching between the routing device of purpose territory, contract the more new management of location server of local of being carried out and/or access domain.

As shown in Figure 5, a kind of motion management method that provides for the embodiment of the invention, this method is for after described purpose territory routing device DR2 and territory, source routing device DR1 finish switching, the routing optimality flow process of carrying out with Correspondent Node, this flow performing main body can be DR1, promptly the second territory routing device also can be DR2, i.e. the first territory routing device.This flow process specifically comprises:

501a: the described first territory routing device DR2 acceptance domain routing device upgrades acknowledge message; Described territory routing device upgrades acknowledge message and corresponds to Fig. 3, is the territory routing device described in Fig. 3 step 305 and upgrades acknowledge message;

Perhaps,

501b, the described second territory routing device DR1 acceptance domain routing device switch finishes acknowledge message; The routing device switching of described territory is finished acknowledge message and is corresponded to Fig. 3, is the territory routing device switch acknowledgment message described in Fig. 3 step 308;

502: according to described acknowledge message, described first territory routing device DR2 and Correspondent Node CN carry out routing optimality to be upgraded, so that described Correspondent Node is updated to routing device address, described first territory with the routing device address, territory of user ID correspondence; Perhaps, finish acknowledge message according to described switching, described second territory routing device DR1 and Correspondent Node CN carry out routing optimality to be upgraded, so that described Correspondent Node is updated to routing device address, described first territory with the routing device address, territory of user ID correspondence.

503: after described routing optimality renewal was finished, Correspondent Node CN just can be by the purpose territory routing device address transmission data bag after upgrading.Described packet carries described user's user ID and the address of purpose territory routing device DR2.

A kind of motion management method that the embodiment of the invention provides upgrades acknowledge message by the acceptance domain routing device; And according to described acknowledge message, carry out routing optimality with Correspondent Node and upgrade, so that described Correspondent Node is updated to routing device address, purpose territory with the routing device address, territory of user ID correspondence.Thereby realized mobile management system framework based on user identity, after the switching of user's territory, source routing device and purpose territory routing device, the routing optimization managing that described source territory routing device or described purpose territory routing device and described Correspondent Node carry out.

As shown in Figure 6, a kind of motion management method that provides for the embodiment of the invention, this method triggers SLS by the network side decision-making and upgrades, described network side decision-making triggers the SLS renewal and is meant that network side entity switches according to the DR under its decision-making needs SLS, or described SLS is according to its down load state, multi-homing etc. of each DR of link, the switching of decision DR; This switching flow specifically comprises:

601:SLS receives the territory routing device update inquiry information that other network side entities send, for some users or certain user make the decision-making that DR switches; Perhaps SLS is according to its following situation such as load state, multi-homing of each DR of link, from making the decision-making that DR switches as some users or certain user.Here suppose that source routing equipment is DR1, i.e. the second territory routing device, the purpose routing device is DR2, i.e. the second territory routing device.

Wherein, other network side entities refer to the network side entity except that the first territory routing device, as other routers, server or the like.

602:SLS sends the request of DR handover trigger to DR1, and perhaps SLS sends the request of DR handover trigger to DR2, sends the request of DR handover trigger by DR2 to DR1 again.

After 603:DR1 receives the DR handover trigger request described in the step 602, finish the territory routing device with DR2 and switch, wherein comprise the switching that active access entity GW1 and purpose insert entity GW2.

Need to prove, step 301-309 is basic identical among the territory routing device switching flow of described DR1 and DR2 and Fig. 3 embodiment, the difference part only is: in present embodiment, if in the step 602, SLS directly sends the request of DR handover trigger to DR1, and then corresponding to Fig. 3 need need to increase an operation between step 302 and step 303, and promptly DR2 is that described user distributes a purpose to insert entity, be GW2, so that the new technological process more of the station location marker in carry out step 306; If in the step 602, be to have sent the request of DR handover trigger to DR2 earlier by SLS, send the request of DR handover trigger by DR2 to DR1 again, then DR2 is that operation that described user specifies purpose to insert entity GW2 can occur in DR2 and receives that the DR handover trigger request of SLS is to any moment between the step 303.

In addition, what deserves to be explained is that among the described embodiment of above Fig. 6, the described SLS of step 601-step 603 can be described user's territory, local SLS, also can be described user's access domain SLS.If the described SLS of step 601-step 603 is described user's territory, local SLS, handling process just as shown in Figure 6; If the described SLS of step 601-step 603 is described user's access domain SLS, after then access domain SLS receives the triggering message of other network side entities, may search less than described user's user information corresponding, then access domain SLS will at first find the address of described user's territory, local SLS, and trigger request is transmitted to this territory, local SLS, sending trigger request by this territory, local SLS to DR1 or DR2, wherein access domain SLS may also need the signatory location server of the inquiry overall situation in order to obtain the address of territory, local SLS.A kind of motion management method that the embodiment of the invention provides, signatory location server SLS is by receiving the territory routing device updating message that network side entity sends, perhaps according to self decision-making, directly or indirectly send the handover trigger request message, so that described source routing equipment is finished switching to the purpose routing device to territory, source routing device.Thereby realized in the mobile management system framework based on user identity the renewal operation of the signatory location server that triggers by network side decision-making.

As shown in Figure 7, be a kind of signatory location server that the embodiment of the invention provides, this server is concrete, comprising:

Receiving element 701 is used to receive the request message that the first territory routing device sends, the address of carrying user ID and the described first territory routing device in the described request message;

Updating block 702 is used for according to described user ID, the address of the territory routing device of the described user ID correspondence of this locality storage is updated to the address of the described first territory routing device that carries in the described request message.

Further, described server also comprises:

Transmitting element is used for sending acknowledge message to the described first territory routing device, carries described user's contextual information in the described acknowledge message.

Wherein, described user ID is positioned at the user ID layer in communication protocol stack, and described user ID layer is arranged in the network layer of communication protocol stack, perhaps between network layer and the transport layer.

Further, when described request message was territory routing device update inquiry information, this server also comprised:

Described transmitting element, also be used for territory routing device update inquiry information according to the described first territory routing device transmission, signatory location server sends territory routing device update inquiry information to described roamer's territory, local, carry described roamer's user ID and routing device address, described first territory in the routing device update inquiry information of described territory, so that the signatory location server in territory, described local upgrades the address of the territory routing device of user ID correspondence described in the local cache;

Described receiving element also is used to receive the territory routing device that described user's the signatory location server in territory, local sends and upgrades acknowledge message, carries described user's contextual information in the described renewal acknowledge message.

It should be noted that described signatory location server also comprises:

Described transmitting element also is used for sending query requests to the signatory location server of the overall situation, comprises described roamer's user ID in the described query requests, so that obtain the signatory location server address information in territory, described user local;

Described receiving element also is used to receive the acknowledgment of your inquiry that the signatory location server of the described overall situation returns, and carries the address information of user's the signatory location server in territory, described local in the described acknowledgment of your inquiry.

It is also to be noted that described signatory location server also comprises:

Described receiving element also is used to receive the territory routing device handover trigger request message that network side entity sends, and carries the address of user ID and this territory routing device in the described message;

Described transmitting element, also be used for according to the territory routing device handover trigger request message of the network side entity transmission that receives or according to self decision-making, send territory routing device handover trigger request message to the territory routing device, so that finish switching between the routing device of territory.

As shown in Figure 8, be a kind of territory routing device that the embodiment of the invention provides, this equipment comprises:

Receiving element 801 is used to receive and inserts the request message that entity sends, and carries the described user's that user ID and described access entity obtain station location marker in the described request message;

Updating block 802 is used for the user ID of carrying according to described request message, the station location marker of the described user ID correspondence of this locality storage is updated to the described user's that described access entity obtains station location marker.

Further, when described access entity be second to insert entity; Described request message is the station location marker update inquiry information; This territory routing device also comprises:

Transmitting element is used to send station location marker and upgrades acknowledge message.

It should be noted that described territory routing device also comprises:

Described transmitting element also is used to send the handover trigger request message to other territory routing devices, carries the address of user ID and this territory routing device in the described message;

Described receiving element also is used to receive the handover trigger request message that other territory routing devices send, and carries the address of user ID and this territory routing device in the described message.

It should be noted that described territory routing device also comprises:

Described transmitting element also is used to send a request message, and carries the address of user ID and this territory routing device in the described request message;

Described receiving element also is used to receive the affirmation message that signatory location server sends, and carries described user's contextual information in the described acknowledge message.

It should be noted that described territory routing device also comprises:

Described transmitting element also is used for sending territory routing device request message to other territory routing devices, carries the address that described user ID and described user's second inserts entity in the routing device request message of described territory;

Described receiving element also is used to receive territory routing device that other territory routing devices send and switches and finish acknowledge message.

It should be noted that described territory routing device also comprises:

Described transmitting element also is used for sending the release buffered message to other territory routing devices.

It should be noted that described territory routing device also comprises:

Described receiving element, also be used for the acceptance domain routing device and upgrade acknowledge message or territory routing device and switch and finish acknowledge message, described territory routing device upgrades acknowledge message and described territory routing device and switches and finishes address and the user ID that carries the territory routing device that sends described message in the acknowledge message;

Optimize the unit, be used for finishing acknowledge message according to described acknowledge message or the switching of described territory routing device, the Correspondent Node corresponding with described user carries out routing optimality to be upgraded, so that described Correspondent Node upgrades the routing device address, territory of described user ID correspondence.

It should be noted that described territory routing device also comprises:

Packet receives buffer unit, be used for when the user is switched between the second territory routing device and the first territory routing device, the described user's that the described second territory routing device will receive downlink data packet buffer memory, and after finishing switching, be transmitted to the described first territory routing device.

As shown in Figure 9, be a kind of access entity that the embodiment of the invention provides, this access entity comprises:

Acquiring unit 901 is used to obtain described user's station location marker, and described station location marker is a station location marker of described access entity itself, is a station location marker of described user's independent allocation for described access entity or other network side entities perhaps;

Transmitting element 902 is used to send the station location marker update inquiry information, carries the described user's that user ID and described access entity obtain station location marker in the described station location marker update inquiry information.

It should be noted that described access entity also comprises:

Buffer unit is used for when the user is switched between the first access entity and the described second access entity, the described user's that the described first access entity will receive downlink data packet buffer memory, and after finishing switching, be transmitted to described second and insert entity.

As shown in figure 10, be the signatory location server of a kind of overall situation that the embodiment of the invention provides, this server comprises:

Receiving element 1001 is used to receive the signatory location server query requests in the territory, local that carries user ID that signatory location server sends;

Query unit 1002 is used for according to described user ID, searches described user's signatory location server address, territory, local;

Return unit 1003, be used for the signatory location server address information in the described described user's who inquires territory, local is sent to the signatory location server that sends query requests.

It should be noted that the described equipment of Fig. 7 to Figure 10 can be used as specific installation and exists, also can be used as a functional entity,, be integrated in other network equipments and exist perhaps as a kind of device.

What deserves to be explained is that also mentioned message can realize by constructing new message structure during the above was all implemented, and can also carry the information of carrying in the described message by the message in the existing procedure and realize.

Also need to prove, more than whole Home SLS address informations described in the embodiment, it is the signatory location server address information in territory, local, it can be the global position sign of the signatory location server in territory, described local, as global ip address, or the domain-name information of the signatory location server in territory, described local, other signatory location servers can obtain the global position sign of the signatory location server in territory, described local according to this dns query message, perhaps, can also be other any information that can reflect the global position sign of the signatory location server in territory, described local.

It is also to be noted that, more than whole described embodiment, carry out DR switch to upgrade finish before, all from Correspondent Node receive data carry out buffer memory by source routing equipment DR1, after the switching renewal is finished, be transmitted to DR2 by described DR1, thereby can guarantee the continuity of user and Correspondent Node.

It should be noted that the invention process adopts branch territory layer mode by the query mappings between user ID and customer location mechanism, make the search efficiency height, expense is little; (Domain NameServer, DNS) system does not have special demands, as long as data surface separates with signaling plane to name server.Handover decisions can be made by network side entity, and the network decision-making power is bigger, upgrades the operation major part and carries out at network side, and is little to terminal requirements, and then reduced the empty overhead in the wireless system.

The embodiment of the invention has realized the mobile management system framework based on user identity by above-described motion management method and device, because entity is inserted in user's source and purpose inserts entity switching, the more new management of the territory routing device that is carried out; Since user's territory, the source routing device and the switching of purpose territory routing device, the more new management of the signatory location server that is carried out; Since user's territory, the source routing device and the switching of purpose territory routing device, the more new management of the signatory location server in the territory, local of being carried out; After the switching of user's territory, source routing device and purpose territory routing device, routing optimization managing that described source territory routing device or described purpose territory routing device and described Correspondent Node carry out and the territory routing device handoff trigger message that is sent by network side entities such as signatory location servers trigger source routing equipment and switch renewal to the purpose routing device.

Need to prove that the present invention can implement easily in wireless communication system (as LTE, WiMAX, WCDMA etc.).In the LTE system, be embodied as example with the present invention, SLS can be used as subscribed services device (HSS in local in a functional entity and the LTE system, Home Subscriber Server) integrates DR and also can be used as grouped data network gateway (PDN-GW in functional entity and the LTE system, Packet Data Network Gateway) integrates, and GW just refers to the gateway (S-GW, Serving Gateway) in the LTE system.In addition, the wireless communication system that execution mode disclosed in this invention is not limited only to provide among the embodiment, suitable equally for wired communication system.In wired communication system, the GW in the embodiment of the invention shows as cable access router.

Through the above description of the embodiments, one of ordinary skill in the art will appreciate that: realize that all or part of step in the foregoing description method is to instruct relevant hardware to finish by program, described program can be stored in the computer read/write memory medium, this program is when carrying out, comprise step as above-mentioned method embodiment, described storage medium, as: ROM/RAM, magnetic disc, CD etc.

The above; only be the specific embodiment of the present invention, but protection scope of the present invention is not limited thereto, anyly is familiar with those skilled in the art in the technical scope that the present invention discloses; can expect easily changing or replacing, all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claim.

Claims

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

2. motion management method according to claim 1 is characterized in that, this method also comprises:

Described first equipment sends acknowledge message to the described first territory routing device, carries described user's contextual information in the described acknowledge message.

3. motion management method according to claim 2 is characterized in that,

Described contextual information comprises a kind of or its combination in any in safe key, QoS parameter, the files on each of customers.

4. according to any described motion management method in the claim 1 to 3, it is characterized in that:

Described first equipment receives before the step of request message, also comprises:

The described first territory routing device receives the territory routing device request message that the second territory routing device sends, and carries the address that described user ID and described user's second inserts entity in the routing device request message of described territory;

The described first territory routing device is according to the user ID of carrying in the routing device request message of described territory, judge this locality and do not store described user ID user information corresponding, the described user ID user information corresponding of perhaps judging local storage is expired;

The described first territory routing device sends a request message to described first equipment.

5. motion management method according to claim 4 is characterized in that, the described first territory routing device receives before the step of territory routing device request message of the second territory routing device, also comprises:

Described second inserts entity judges that the user moves in the scope that self covers, and then sends the handover trigger request message to the described first territory routing device;

The described first territory routing device sends territory routing device handover trigger request message to the described second territory routing device, initiates territory routing device request message so that trigger the described second territory routing device;

All carry described second in described handover trigger request message and the described territory routing device handover trigger request message and insert the address of entity and described user's user ID;

Perhaps,

First inserts entity receives user's indication;

Described first inserts entity sends the handover trigger request message to the described second territory routing device, initiates territory routing device request message so that trigger the described second territory routing device;

All carry described second in described handover trigger request message and the described user indication and insert the address of entity and described user's user ID;

Perhaps,

Described second inserts entity inserts entity transmission handover trigger request message to described first;

Carry described second in the described handover trigger request message and insert the address of entity and described user's user ID;

Perhaps,

Described second inserts entity sends the handover trigger request message to the described second territory routing device, initiates territory routing device request message so that trigger the described second territory routing device;

Carry described second in the described handover trigger request message and insert the address of entity and described user's user ID.

6. motion management method according to claim 4 is characterized in that, the described first territory routing device receives before the step of the territory routing device request message that the second territory routing device sends, and also comprises:

Described first equipment receives the territory routing device handover trigger request message that other network side entities send, and perhaps described first equipment self is made the decision-making that the territory routing device switches;

Described first equipment sends territory routing device handover trigger request message to the described first territory routing device, perhaps described first equipment sends territory routing device handover trigger request message to the described second territory routing device, so that the described second territory routing device continues to send territory routing device handover trigger request message to the described first territory routing device;

The described first territory routing device receives after the routing device handover trigger request message of described territory that for described user's intended target inserts entity, it is the described second access entity that described target inserts entity.

7. motion management method according to claim 2 is characterized in that,

When described first equipment after the first territory routing device sends the step of acknowledge message, also comprise:

The described first territory routing device confirmation of receipt message;

The described first territory routing device is set up described user's the user ID and the binding relationship of station location marker, and in this locality this binding relationship is stored;

The described first territory routing device sends territory routing device switching to the second territory routing device and finishes acknowledge message.

8. motion management method according to claim 7 is characterized in that, also comprises:

After the described first territory routing device receives described acknowledge message, the Correspondent Node that the described first territory routing device is corresponding with described user carries out routing optimality to be upgraded, so that described Correspondent Node is updated to the routing device address, territory of described user's correspondence the address of the described first territory routing device; Perhaps,

When the described second territory routing device receive described territory routing device switch finish acknowledge message after, the Correspondent Node that the described second territory routing device is corresponding with described user carries out routing optimality to be upgraded, so that described Correspondent Node is updated to the routing device address, territory of described user's correspondence the address of the described first territory routing device.

9. motion management method according to claim 7 is characterized in that, this method also comprises:

The described second territory routing device switches according to described territory routing device finishes acknowledge message, discharges the described user's of storage binding relationship.

10. motion management method according to claim 4 is characterized in that, also comprises:

When the user is switched between described first territory routing device and the described second territory routing device, the described user's data bag buffer memory that the described second territory routing device will receive, and after finishing switching, be transmitted to the described first territory routing device.

11. motion management method according to claim 1 is characterized in that,

When first equipment is the signatory location server of described user's access domain, also comprise:

Described first equipment receives after the request message of the described first territory routing device transmission, and the described user of described first device discovery is the roamer;

Described first equipment sends territory routing device update inquiry information to the signatory location server in described roamer's territory, local, carries described roamer's user ID and routing device address, described first territory in the routing device update inquiry information of described territory;

Described first equipment receives the territory routing device renewal acknowledge message that the signatory location server in territory, described local sends.

12. motion management method according to claim 11 is characterized in that, also comprises:

When described roamer's the address information of the signatory location server in territory, local is not stored in described first equipment this locality, described first equipment sends query requests to the signatory location server of the overall situation, comprises described roamer's user ID in the described query requests;

The signatory location server of the described overall situation receives described query requests, inquire the address information of the signatory location server in territory, local of described user ID correspondence, send acknowledgment of your inquiry to described first equipment, carry the address information of the signatory location server in territory, described local in the described acknowledgment of your inquiry;

Described first equipment receives described acknowledgment of your inquiry.

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

The signatory location server in territory, described local receives the territory routing device update inquiry information that described first equipment sends;

The signatory location server in territory, described local is according to the user ID of carrying in the routing device update inquiry information of described territory, the address of the territory routing device of the described user ID correspondence of this locality storage is updated to the address of the territory routing device that carries in the routing device update inquiry information of described territory;

The signatory location server in territory, described local sends the territory routing device to described first equipment and upgrades acknowledge message.

14. motion management method according to claim 13 is characterized in that, also comprises:

After described first equipment receives the territory routing device renewal acknowledge message of the signatory location server transmission in territory, described local,

Described first equipment is set up the binding relationship between the routing device address, first territory of carrying in described roamer's user ID and the described territory routing device update inquiry information, and in this locality this binding relationship is stored;

Perhaps, described first equipment is updated to the routing device address, first territory of carrying in the routing device update inquiry information of described territory with the routing device address, territory of described roamer's user ID correspondence.

15. motion management method according to claim 1 is characterized in that:

Described user ID is positioned at the user ID layer in communication protocol stack, described user ID layer is arranged in the network layer of communication protocol stack, perhaps between network layer and the transport layer.

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

17. motion management method according to claim 16 is characterized in that, also comprises:

Described access entity is the second access entity;

When the user is switched between the first access entity and the described second access entity, the described user's that the described first access entity will receive downlink data packet buffer memory, and after finishing switching, be transmitted to described second and insert entity.

18., it is characterized in that according to claim 16 or 17 described motion management methods:

19. a signatory location server is characterized in that, comprising:

20. signatory location server according to claim 19 is characterized in that, this server also comprises:

21. signatory location server according to claim 19 is characterized in that, when described request message was territory routing device update inquiry information, this server also comprised:

22. signatory location server according to claim 21 is characterized in that, this server also comprises:

Described receiving element also is used to receive the acknowledgment of your inquiry that the signatory location server of the described overall situation returns, and carries the address information of user's the signatory location-based service in territory, described local in the described acknowledgment of your inquiry.

23., it is characterized in that this server also comprises according to any described signatory location server in the claim 19 to 22:

24. a territory routing device is characterized in that, comprising:

25. territory according to claim 24 routing device is characterized in that, described access entity is the second access entity; Described request message is the station location marker update inquiry information; This territory routing device also comprises:

26. territory according to claim 24 routing device is characterized in that, this territory routing device also comprises:

27. territory according to claim 24 routing device is characterized in that, this territory routing device also comprises:

28. territory according to claim 24 routing device is characterized in that, this territory routing device also comprises:

29. territory according to claim 24 routing device is characterized in that, this territory routing device also comprises:

30. territory according to claim 24 routing device is characterized in that, this territory routing device also comprises:

31. territory according to claim 24 routing device is characterized in that, this territory routing device also comprises:

32. one kind is inserted entity, it is characterized in that this access entity comprises:

33. access entity according to claim 32 is characterized in that, this access entity comprises:

34. the signatory location server of the overall situation is characterized in that this server comprises:

Query unit is used for according to described user ID, searches described user's the signatory location server address of local domain;