CN103220743B

CN103220743B - The processing method of Route Distinguisher, Apparatus and system in via node moving process

Info

Publication number: CN103220743B
Application number: CN201210018009.6A
Authority: CN
Inventors: 杨义; 鲍炜
Original assignee: China Academy of Telecommunications Technology CATT
Current assignee: China Academy of Telecommunications Technology CATT; Datang Mobile Communications Equipment Co Ltd
Priority date: 2012-01-19
Filing date: 2012-01-19
Publication date: 2016-08-17
Anticipated expiration: 2032-01-19
Also published as: CN103220743A; WO2013107260A1

Abstract

The invention discloses the processing method of Route Distinguisher, Apparatus and system in a kind of RN moving process, the method includes: the source MME of UE is when determining that service RN moves to the overlay area in the 2nd MME pond from the overlay area in a MME pond, the Route Distinguisher of described RN and the corresponding relation in MME pond according to arranging determine target MME, wherein, described source MME belongs to a described MME pond, and described target MME belongs to described 2nd MME pond；Described source MME and described target MME carry out the transfer operation of described UE context.Therefore, apply the present invention, need the source MME of UE shifting context that the MME in new MME pond can be found as target MME, thus realize from a MME pond, the context of UE is transferred to another MME pond.

Description

Method, device and system for processing route identifier in relay node moving process

Technical Field

The invention relates to the field of wireless communication, in particular to a method, a device and a system for processing a route identifier in the moving process of a relay node.

Background

In a long term evolution system, in order to increase a network coverage area, a Relay Node (RN) is introduced, and the RN is wirelessly connected with a donor base station. The RN may be applied to a high-speed moving environment such as a railway, and reduce the number of times of handover and the number of times of location update of a User Equipment (UE) through group handover, and improve signal quality. In a high-speed mobile environment, the RN is connected with a network by using the identity of the UE, and the network establishes an Evolved Packet System (EPS) bearer for the RN; the RN accesses an Operation and Maintenance (OAM) system and downloads necessary configuration data. From the UE perspective, the RN is the serving base station for the UE. When the UE accesses the RN, all Data of the UE is mapped to a bearer of the RN, and sent to a next hop node, such as a Serving Gateway (SGW) of the UE, through a Packet Data Domain Gateway (PGW) of the RN.

In a Mobility Management Entity (MME) pool, several MMEs serve in parallel, and the MMEs in the MME pool control UEs in the area according to local roaming restriction rules. The UE and the RN under the RN are relatively stationary to maintain a better propagation path, and therefore, the UE does not reselect or handover to a cell other than the RN in the moving process of the RN. When the RN moves across the MME pool, the UE also enters a new MME pool, and at this time, the context of the UE needs to be transferred from the original MME to the MME in the new MME pool.

Generally, a method of S1 handover is used to transfer the context of a UE, fig. 1 is a schematic flowchart of a UE performing S1 handover in the prior art, and referring to fig. 1, a UE performing S1 handover in the prior art includes the following steps:

step 101: the UE sends a measurement report to the source base station.

Step 102: and the source base station performs switching judgment according to the measurement report, selects a proper target cell and sends a switching request message comprising a target cell identifier to the source MME.

Step 103: and the source MME finds the target MME according to the target cell identification and sends a forward relocation request message to the target MME.

Here, the source MME queries a Domain Name System (DNS) server for Internet Protocol (IP) address information of an MME serving a Tracking Area Identity (TAI) of the target cell based on the TAI. The result returned by the DNS may include multiple MME, and the source MME selects one of the MME as the target MME.

Step 104: and the target MME sends a switching request message to the target base station.

Step 105: the target base station reserves resources for the UE and returns a switching request confirmation message to the target MME.

Step 106: and the target MME returns a forward relocation response message to the source MME.

Step 107: the source MME sends a handover command to the source base station.

Step 108: the source base station transmits a Radio Resource Control (RRC) connection reconfiguration message to the UE.

Step 109: and the UE establishes RRC connection with the target cell and returns an RRC connection reconfiguration completion message to the target base station.

Step 110: and the target base station sends a switching notification message to the target MME, updates the position information of the UE and switches the downlink data transmission path.

Step 111: and the target MME sends a forward relocation completion message to the source MME.

Step 112: and the source MME sends a UE resource release command to the source base station.

When the RN moves across the MME pool, if the transfer of the context of the UE from the original MME to the MME in the new MME pool is implemented by using the S1 handover method shown in fig. 1, since the Uu port TAI remains unchanged during the RN moving process, when the source MME queries in the DNS server according to the TAI of the target cell in the handover request message, the obtained query result is the IP address of the source MME, instead of the IP address of the MME in the new MME pool, and therefore, the source MME cannot find the MME in the new MME pool as the target MME, and when the RN moves across the MME pool, the transfer of the context of the UE from one MME pool to another MME pool cannot be implemented.

Disclosure of Invention

The embodiment of the invention provides a method, a device and a system for processing a routing identifier in a RN moving process, which are used for transferring the context of UE (user equipment) served by an RN from an MME (mobility management entity) pool to another MME pool when the RN moves across the MME pools.

The method for processing the route identifier in the RN moving process, provided by the embodiment of the invention, comprises the following steps:

when a source MME of UE determines that a serving RN moves from a coverage area of a first MME pool to a coverage area of a second MME pool, determining a target MME according to a corresponding relation between a set routing identifier of the RN and the MME pool, wherein the source MME belongs to the first MME pool, and the target MME belongs to the second MME pool;

and the source MME and the target MME carry out the transfer operation of the UE context.

The device for processing the route identifier in the RN moving process provided by the embodiment of the invention comprises:

a first determining module, configured to determine, when it is determined that a serving RN moves from a coverage area of a first MME pool to a coverage area of a second MME pool, a target MME according to a set correspondence between a routing identifier of the RN and the MME pool, where the target MME belongs to the second MME pool;

and the transferring module is used for performing UE context transferring operation with the target MME determined by the first determining module.

The system for processing the route identifier in the RN moving process provided by the embodiment of the invention comprises the following steps:

the RN is used for sending a switching request message to a source MME of the UE served by the RN when the RN moves from the coverage area of the first MME pool to the coverage area of the second MME pool;

and the source MME is used for determining a target MME according to the switching request message sent by the RN and the set corresponding relation between the routing identifier of the RN and an MME pool, and performing the transfer operation of the UE context with the target MME, wherein the target MME belongs to a second MME pool.

An RN apparatus provided in an embodiment of the present invention includes:

a third determining module, configured to determine, according to the obtained identification information of the MME pool, that the RN apparatus moves from the coverage area of the first MME pool to the coverage area of the second MME pool;

a sending module, configured to send a handover request message to a source MME of a UE served by the source MME, where the handover request message is used to instruct the source MME to determine a target MME according to a set correspondence between a routing identifier of the RN device and an MME pool, where the source MME belongs to the first MME pool, and the target MME belongs to the second MME pool.

The DNS provided by the embodiment of the invention comprises:

a receiving module, configured to receive a registration request message sent by an RN;

and the storage module is used for storing the corresponding relation between the corresponding routing identifier of the RN and the MME pool when the receiving module receives the registration request message sent by the RN.

An OAM system provided in an embodiment of the present invention includes:

a fourth determining module, configured to determine correspondence between multiple routing identifiers of the RN and multiple MME pools;

and the second notification module is used for notifying the RN of the routing identifier corresponding to the second MME pool when the RN moves from the first MME pool to the second MME pool, and the RN sends a switching request message containing the routing identifier corresponding to the second MME pool to a source MME of the UE served by the RN.

According to the technical scheme, in the embodiment of the present invention, when determining that a serving RN moves from a coverage area of a first MME pool to a coverage area of a second MME pool, a source MME of a UE determines a target MME according to a set correspondence between a routing identifier of the RN and the MME pool, where the source MME belongs to the first MME pool and the target MME belongs to the second MME pool; and the source MME and the target MME carry out the transfer operation of the UE context. Therefore, in the embodiment of the present invention, the source MME of the UE that needs to transfer the context may find the MME in the new MME pool as the target MME, thereby implementing the transfer of the context of the UE from one MME pool to another MME pool.

Drawings

Fig. 1 is a schematic flowchart illustrating a UE performing S1 handover in the prior art;

FIG. 2 is a schematic flow chart of one embodiment of the method of the present invention;

FIG. 3 is a schematic flow chart of another embodiment of the method of the present invention;

FIG. 4 is a schematic flow chart of another embodiment of the method of the present invention;

FIG. 5 is a schematic flow chart of yet another embodiment of the method of the present invention;

FIG. 6 is a schematic structural diagram of an embodiment of the apparatus of the present invention;

FIG. 7 is a schematic block diagram of an embodiment of the system of the present invention;

FIG. 8 is a schematic structural diagram of an RN apparatus according to the present invention;

FIG. 9 is a schematic diagram of the DNS architecture of the present invention;

fig. 10 is a schematic diagram of the OAM system of the present invention.

Detailed Description

When the RN moves across the MME pool, the context of the UE served by the RN needs to be transferred from the original MME to the MME in the new MME pool, so that the UE served by the RN and the RN are relatively static, and a better propagation path is kept.

The method in the embodiment of the present invention is described in detail below with reference to the accompanying drawings.

FIG. 2 is a schematic flow chart of an embodiment of the method of the present invention.

Referring to fig. 2, a method for processing a route identifier in an RN moving process according to an embodiment of the present invention includes the following steps:

step 201: when determining that a serving RN moves from a coverage area of a first MME pool to a coverage area of a second MME pool, an MME of the UE determines a target MME according to a corresponding relation between a set routing identifier of the RN and the MME pool, wherein the source MME belongs to the first MME pool, and the target MME belongs to the second MME pool.

Here, the source MME determines that the RN moves from the coverage area of the first MME pool to the coverage area of the second MME pool according to a handover request message sent by the serving RN.

The corresponding relation between the routing identifier of the RN and the MME pool comprises the following steps: a corresponding relation between one routing identifier of the RN and a plurality of MME pools; or, the plurality of routing identifiers of the RN and the plurality of MME pools. When one routing identifier of the RN corresponds to a first MME pool and a second MME pool, a source MME determines a target MME according to a switching request message sent by the RN and the corresponding relation between the routing identifier of the RN and the second MME pool, wherein the switching request message comprises the routing identifier of the RN and indicating information used for indicating the source MME to select an MME in the second MME pool as the target MME; and when the first routing identifier of the RN corresponds to a first MME pool and the second routing identifier of the RN corresponds to a second MME pool, the source MME determines a target MME according to a switching request message sent by the RN and the corresponding relation between the second routing identifier of the RN and the second MME pool, wherein the switching request message comprises the second routing identifier of the RN.

And if the corresponding relation between the routing identifier of the RN and the MME pool is stored in the DNS, the source MME acquires the corresponding relation between the routing identifier of the RN and the MME pool by inquiring the DNS.

Preferably, the route identifier includes a TAI and/or a global base station identifier.

Step 202: and the source MME and the target MME carry out the transfer operation of the UE context.

Here, the transfer operation is performed according to the corresponding step in the S1 handover method shown in fig. 1, and will not be described in detail here.

Step 203: and releasing the corresponding relation between the set routing identifier of the RN and the first MME pool.

Here, the RN notifies the DNS to delete the stored correspondence between the routing identifier of the RN and the first MME pool.

FIG. 3 is a schematic flow chart of another embodiment of the method of the present invention.

Referring to fig. 3, a method for processing a route identifier in an RN moving process according to an embodiment of the present invention includes the following steps:

step 301: and after the RN is moved from the first MME pool to the second MME pool, establishing an S1 interface with the MME of the second MME pool.

At this time, the RN is connected to the first MME pool and also connected to the second MME pool.

Step 302: and updating the corresponding relation between the TAI supported by the RN and the MME in the DNS so that the TAI supported by the RN corresponds to two MME pools.

Step 303: the RN sends a switching request message comprising a TAI and indication information to a source MME of the UE needing to transfer the context, wherein the indication information is used for indicating the switching purpose and is used for transferring the context of the UE.

Step 304: and the source MME queries the DNS according to the TAI and selects the MME in the second MME pool as a target MME.

Here, in the query result obtained by the source MME, the TAI points to the first MME pool and the second MME pool, and since the handover request message received by the source MME includes the indication information for indicating that the handover is intended to transfer the UE context, the source MME selects an MME in the second MME pool that does not include the source MME as the target MME.

Step 305: and the source MME and the target MME carry out the transfer operation of the UE context.

Step 306: and judging whether UE needing context transfer exists, if so, returning to the step 303, otherwise, executing the step 307.

Step 307: and the RN releases the S1 connection with the first MME pool, and updates the corresponding relation between the TAI supported by the RN and the MME in the DNS, so that the TAI supported by the RN does not correspond to the first MME pool any more.

FIG. 4 is a schematic flow chart of another embodiment of the method of the present invention.

Referring to fig. 4, a method for processing a route identifier in an RN moving process according to an embodiment of the present invention includes the following steps:

step 401: the RN downloads configuration information including a plurality of available TAIs from the OAM system.

Step 402: when the RN establishes S1 connection with the first MME pool, selecting a part of available TAIs to be associated with the MME in the first MME pool, and storing the corresponding relation in the DNS.

Step 403: and when the RN moves from the first MME pool to the second MME pool, selecting the unused part in the available TAI to be associated with the MME in the second MME pool, and storing the corresponding relation in the DNS.

At this time, the DNS stores the correspondence between different TAIs supported by the same RN and the first MME pool and the second MME pool, respectively.

Step 404: and the RN sends a switching request message comprising a target cell TAI to a source MME of the UE needing context transfer, wherein the target cell TAI is a TAI corresponding to the second MME pool.

Step 405: and the source MME queries the DNS according to the target cell TAI to obtain the MME in the second MME pool as the target MME.

Here, if the obtained MMEs in the second MME pool are multiple MMEs, one of them is selected as a target MME.

Step 406: and the source MME and the target MME carry out the transfer operation of the UE context.

Step 407: and judging whether UE needing context transfer exists, if so, returning to the step 404, otherwise, executing the step 408.

Step 408: and the RN releases the S1 connection with the first MME pool, and updates the corresponding relation between the TAI supported by the RN and the MME in the DNS, so that the TAI supported by the RN does not correspond to the first MME pool any more.

Here, the TAI associated with the first MME pool is already released, and may be continuously used when the RN moves to the next MME pool, thereby increasing the application flexibility of the TAI.

Step 409: and the RN updates the TAI of the air interface at the set time, so that the RN uses the TAI associated with the second MME pool.

FIG. 5 is a schematic flow chart of another embodiment of the method of the present invention.

Referring to fig. 5, a method for processing a route identifier in an RN moving process according to an embodiment of the present invention includes the following steps:

step 501: the OAM system determines the corresponding relation between the TAI allocated to the RN and a plurality of MME pools, and stores the corresponding relation in the DNS.

Here, the TAI and MME pools are in one-to-one correspondence, and this correspondence does not change.

Step 502: when the RN moves from the first MME pool to the second MME pool, the TAI corresponding to the second MME pool is obtained from the OAM system.

Here, the RN sends the setting information of the second MME pool to the OAM system, and then the OAM system finds the TAI corresponding to the second MME pool according to the setting information and sends it to the RN.

Step 503: and the RN establishes an S1 interface with the MME in the second MME pool and informs the obtained TAI corresponding to the second MME pool to the MME in the second MME pool.

Step 504: and the RN sends a switching request message comprising a target cell TAI to a source MME of the UE needing context transfer, wherein the target cell TAI is a TAI corresponding to the second MME pool.

Step 505: and the source MME queries the DNS according to the target cell TAI to obtain the MME in the second MME pool as the target MME.

Step 506: and the source MME and the target MME carry out the transfer operation of the UE context.

Step 507: and judging whether UE needing context transfer exists, if so, returning to the step 504, otherwise, executing the step 508.

Step 508: and the RN releases the S1 connection with the first MME pool.

Step 509: and the RN updates the TAI of the air interface at the set time, so that the RN uses the TAI associated with the second MME pool.

FIG. 6 is a schematic structural diagram of an embodiment of the apparatus of the present invention.

Referring to fig. 6, a device for processing a route identifier in an RN moving process according to an embodiment of the present invention includes:

a first determining module 61, configured to determine, when it is determined that the serving RN moves from a coverage area of a first MME pool to a coverage area of a second MME pool, a target MME according to a set correspondence between a routing identifier of the RN and the MME pool, where the target MME belongs to the second MME pool;

a transferring module 62, configured to perform UE context transfer operation with the target MME determined by the first determining module.

The apparatus still further comprises:

a second determining module, configured to determine, according to a handover request message sent by a serving RN, that the RN moves from a coverage area of a first MME pool to a coverage area of a second MME pool;

and the query module is used for querying the DNS to obtain the corresponding relation between the routing identifier of the RN and the MME pool when the corresponding relation between the routing identifier of the RN and the MME pool is stored in the DNS.

Here, the correspondence between the routing identifier of the RN and the MME pool includes: a corresponding relation between one routing identifier of the RN and a plurality of MME pools; or, the plurality of routing identifiers of the RN and the plurality of MME pools. Preferably, the route identifier includes a TAI and/or a global base station identifier.

If one routing identifier of the RN corresponds to a first MME pool and a second MME pool, the first determining module 61 is configured to determine a target MME according to a handover request message sent by the RN and a correspondence between the routing identifier of the RN and the second MME pool, where the handover request message includes the routing identifier of the RN and indication information used for indicating the source MME to select an MME in the second MME pool as the target MME.

If the first routing identifier of the RN corresponds to a first MME pool and the second routing identifier of the RN corresponds to a second MME pool, the first determining module 62 is configured to determine a target MME according to a handover request message sent by the RN and a correspondence between the second routing identifier of the RN and the second MME pool, where the handover request message includes the second routing identifier of the RN.

FIG. 7 is a schematic diagram of an embodiment of the system of the present invention.

Referring to fig. 7, a device for processing a route identifier in an RN moving process according to an embodiment of the present invention includes:

RN71, configured to send a handover request message to a source MME 72 of a UE served by the RN when moving from a coverage area of a first MME pool to a coverage area of a second MME pool;

and the source MME 72 is configured to determine a target MME according to the handover request message sent by the RN71 and the set correspondence between the routing identifier of the RN71 and an MME pool, and perform the transfer operation of the UE context with the target MME, where the target MME belongs to a second MME pool.

Fig. 8 is a schematic structural diagram of an RN device in the present invention.

Referring to fig. 8, an RN apparatus provided in an embodiment of the present invention includes:

a third determining module 81, configured to determine, according to the obtained identification information of the MME pool, that the RN apparatus moves from the coverage area of the first MME pool to the coverage area of the second MME pool;

a sending module 82, configured to send a handover request message to a source MME of a UE served by the source MME, where the handover request message is used to instruct the source MME to determine a target MME according to a set correspondence between a routing identifier of the RN device and an MME pool, where the source MME belongs to the first MME pool, and the target MME belongs to the second MME pool.

Here, the apparatus further includes:

a setting module, configured to set a correspondence between a routing identifier of the RN apparatus and an MME pool;

and the release module is used for releasing the set corresponding relation between the routing identifier of the RN device and the first MME pool after the source MME determines a target MME and performs UE context transfer operation with the target MME.

The apparatus still further comprises:

and the acquisition module is used for acquiring the corresponding relation between the routing identifier of the RN device and the MME pool from the OAM system.

The corresponding relation between the routing identifier of the RN device and the MME pool comprises the corresponding relation between one routing identifier of the RN device and a plurality of MME pools; or, the plurality of routing identifiers of the RN apparatus correspond to a plurality of MME pools. If one routing identifier of the RN device corresponds to a first MME pool and a second MME pool, the switching request message comprises the routing identifier of the RN device and indicating information used for indicating the source MME to select an MME in the second MME pool as a target MME; and if the first routing identifier of the RN device corresponds to the first MME pool and the second routing identifier of the RN device corresponds to the second MME pool, the switching request message comprises the second routing identifier of the RN device.

The apparatus still further comprises:

a first notification module, configured to notify the DNS to store a correspondence between the routing identifier of the RN device and the MME pool; and the source MME is used for notifying the DNS to delete the stored corresponding relation between the routing identifier of the RN device and the first MME pool after the source MME determines a target MME and performs UE context transfer operation with the target MME.

Preferably, the route identifier in the above embodiment includes a TAI and/or a global base station identifier.

Fig. 9 is a schematic structural diagram of the DNS in the present invention.

Referring to fig. 9, a DNS provided in an embodiment of the present invention includes:

a receiving module 91, configured to receive a registration request message sent by an RN;

a storing module 92, configured to store a corresponding relationship between a corresponding routing identifier of the RN and an MME pool when the receiving module 91 receives a registration request message sent by the RN.

Here, the receiving module 91 is further configured to receive a deregistration request message sent by the RN.

The system still further includes:

a deleting module, configured to delete the corresponding relationship between the corresponding routing identifier of the RN and the MME pool when the receiving module 91 receives a deregistration request message sent by the RN.

Fig. 10 is a schematic diagram of the OAM system of the present invention.

Referring to fig. 10, an OAM system provided in this embodiment of the present invention includes:

a fourth determining module 1001, configured to determine correspondence between multiple routing identifiers of the RN and multiple MME pools;

a second notifying module 1002, configured to notify the RN of the routing identifier corresponding to the second MME pool when the RN moves from the first MME pool to the second MME pool, where the RN sends a handover request message including the routing identifier corresponding to the second MME pool to a source MME of a UE served by the RN.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is intended to include such modifications and variations.

Claims

1. A method for processing route identification in the moving process of a Relay Node (RN) is characterized by comprising the following steps:

when a source mobility management entity MME of user equipment UE determines that a service RN moves from a coverage area of a first MME pool to a coverage area of a second MME pool, determining a target MME according to a set corresponding relation between a routing identifier of the RN and the MME pool, wherein the source MME belongs to the first MME pool, and the target MME belongs to the second MME pool; the route identification comprises a Tracking Area Identification (TAI);

the source MME and the target MME carry out UE context transfer operation;

if the corresponding relation between the routing identifier of the RN and the MME pool is stored in a Domain Name System (DNS), the source MME acquires the corresponding relation between the routing identifier of the RN and the MME pool by inquiring the DNS; after the RN moves from the coverage area of the first MME pool to the coverage area of the second MME pool, updating the corresponding relation between the TAI supported by the RN and the MME in the DNS, so that the TAI supported by the RN corresponds to the two MME pools; or, the DNS stores corresponding relations between different TAIs supported by the same RN and a first MME pool and a second MME pool, respectively, when the RN establishes S1 connection with the first MME pool, a part of available TAIs is associated with an MME in the first MME pool, when the RN moves from a coverage area of the first MME pool to a coverage area of the second MME pool, an unused part of the available TAIs is associated with an MME in the second MME pool, and the association is stored in the DNS; in the correspondence stored in the DNS, the TAI and the MME pool are in one-to-one correspondence, and when the RN moves from the coverage area of the first MME pool to the coverage area of the second MME pool, the RN obtains the TAI corresponding to the second MME pool from the operation and maintenance OAM system.

2. The method of claim 1, wherein the source MME determines that the RN has moved from the coverage area of the first MME pool to the coverage area of the second MME pool from a handover request message sent by the serving RN.

3. The method of claim 1, wherein the correspondence of the routing identity of the RN to the MME pool comprises:

a corresponding relation between one routing identifier of the RN and a plurality of MME pools; or,

and the corresponding relation between the plurality of routing identifiers of the RN and the plurality of MME pools.

4. The method of claim 3, wherein if one routing identifier of the RN corresponds to the first MME pool and the second MME pool, the source MME determining the target MME according to the set correspondence between the routing identifier of the RN and the MME pool, comprises:

and the source MME determines a target MME according to a switching request message sent by the RN and the corresponding relation between the routing identifier of the RN and a second MME pool, wherein the switching request message comprises the routing identifier of the RN and indicating information used for indicating the source MME to select the MME in the second MME pool as the target MME.

5. The method of claim 3, wherein if the first routing identifier of the RN corresponds to a first MME pool and the second routing identifier of the RN corresponds to a second MME pool, the source MME determines a target MME according to the set correspondence between the routing identifier of the RN and the MME pool, and the method comprises the following steps:

and the source MME determines a target MME according to a switching request message sent by the RN and the corresponding relation between the second routing identifier of the RN and a second MME pool, wherein the switching request message comprises the second routing identifier of the RN.

6. The method of claim 1, wherein after the source MME and the target MME perform the UE context transfer operation, the method further comprises:

and the RN informs the DNS to delete the stored corresponding relation between the routing identifier of the RN and the first MME pool.

7. The method of claim 1, wherein after the source MME and the target MME perform the UE context transfer operation, the method further comprises:

and releasing the corresponding relation between the set routing identifier of the RN and the first MME pool.

8. An apparatus for processing a route identifier during a moving procedure of a Relay Node (RN), the apparatus comprising:

a first determining module, configured to determine, when it is determined that a serving RN moves from a coverage area of a first Mobility Management Entity (MME) pool to a coverage area of a second MME pool, a target MME according to a set correspondence between a routing identifier of the RN and the MME pool, where the target MME belongs to the second MME pool; the route identification comprises a Tracking Area Identification (TAI);

a transfer module, configured to perform a transfer operation of a context of a UE with the target MME determined by the first determining module;

wherein the apparatus further comprises: the query module is used for querying a Domain Name System (DNS) to obtain the corresponding relation between the routing identifier of the RN and the MME pool when the corresponding relation between the routing identifier of the RN and the MME pool is stored in the DNS; after the RN moves from the coverage area of the first MME pool to the coverage area of the second MME pool, updating the corresponding relation between the TAI supported by the RN and the MME in the DNS, so that the TAI supported by the RN corresponds to the two MME pools; or, the DNS stores corresponding relations between different TAIs supported by the same RN and a first MME pool and a second MME pool, respectively, when the RN establishes S1 connection with the first MME pool, a part of available TAIs is associated with an MME in the first MME pool, when the RN moves from a coverage area of the first MME pool to a coverage area of the second MME pool, an unused part of the available TAIs is associated with an MME in the second MME pool, and the association is stored in the DNS; in the correspondence stored in the DNS, the TAI and the MME pool are in one-to-one correspondence, and when the RN moves from the coverage area of the first MME pool to the coverage area of the second MME pool, the RN obtains the TAI corresponding to the second MME pool from the operation and maintenance OAM system.

9. The apparatus of claim 8, wherein the apparatus further comprises:

a second determining module, configured to determine, according to a handover request message sent by a serving RN, that the RN moves from a coverage area of a first MME pool to a coverage area of a second MME pool.

10. The apparatus of claim 8, wherein the correspondence of the routing identity of the RN to the MME pool comprises:

11. The apparatus of claim 10, wherein if one routing identity of the RN corresponds to a first MME pool and a second MME pool, then

The first determining module is configured to determine a target MME according to a handover request message sent by the RN and a correspondence between a routing identifier of the RN and a second MME pool, where the handover request message includes the routing identifier of the RN and indication information used for indicating a source MME to select an MME in the second MME pool as the target MME.

12. The apparatus of claim 10, wherein if the first routing identification of the RN corresponds to a first MME pool and the second routing identification of the RN corresponds to a second MME pool, then

The first determining module is configured to determine a target MME according to a handover request message sent by the RN and a correspondence between a second routing identifier of the RN and a second MME pool, where the handover request message includes the second routing identifier of the RN.

13. A system for processing route identification in a moving process of a Relay Node (RN), the system is characterized by comprising:

the RN is used for sending a switching request message to a source MME of User Equipment (UE) served by the RN when the RN moves from the coverage area of a first Mobility Management Entity (MME) pool to the coverage area of a second MME pool;

the source MME is used for determining a target MME according to a switching request message sent by the RN and the set corresponding relation between the routing identifier of the RN and an MME pool, and performing UE context transfer operation with the target MME, wherein the target MME belongs to a second MME pool;

the route identification comprises a Tracking Area Identification (TAI); storing the corresponding relation between the routing identifier of the RN and the MME pool in a Domain Name System (DNS), and then acquiring the corresponding relation between the routing identifier of the RN and the MME pool by a source MME through querying the DNS; after the RN moves from the coverage area of the first MME pool to the coverage area of the second MME pool, updating the corresponding relation between the TAI supported by the RN and the MME in the DNS, so that the TAI supported by the RN corresponds to the two MME pools; or, the DNS stores corresponding relations between different TAIs supported by the same RN and a first MME pool and a second MME pool, respectively, when the RN establishes S1 connection with the first MME pool, a part of available TAIs is associated with an MME in the first MME pool, when the RN moves from a coverage area of the first MME pool to a coverage area of the second MME pool, an unused part of the available TAIs is associated with an MME in the second MME pool, and the association is stored in the DNS; in the correspondence stored in the DNS, the TAI and the MME pool are in one-to-one correspondence, and when the RN moves from the coverage area of the first MME pool to the coverage area of the second MME pool, the RN obtains the TAI corresponding to the second MME pool from the operation and maintenance OAM system.

14. A relay node, RN, apparatus, comprising:

a sending module, configured to send a handover request message to a source MME of a user equipment UE served by the source MME, where the handover request message is used to instruct the source MME to determine a target MME according to a set correspondence between a routing identifier of the RN device and an MME pool, where the source MME belongs to the first MME pool and the target MME belongs to the second MME pool; the route identification comprises a Tracking Area Identification (TAI);

wherein, the device still further includes: a first notification module, configured to notify a domain name system DNS to store a correspondence between a routing identifier of the RN device and an MME pool; after the RN device moves from the coverage area of the first MME pool to the coverage area of the second MME pool, updating the corresponding relation between the TAI supported by the RN device and the MME in the DNS, and enabling the TAI supported by the RN device to correspond to the two MME pools; or, the DNS stores corresponding relations between different TAIs supported by the RN device and a first MME pool and a second MME pool, respectively, when the RN device establishes S1 connection with the first MME pool, a part of available TAIs is associated with MMEs in the first MME pool, and when the RN device moves from a coverage area of the first MME pool to a coverage area of the second MME pool, an unused part of the available TAIs is associated with MMEs in the second MME pool, and the association is stored in the DNS; in the correspondence stored in the DNS, the TAI and MME pools are in one-to-one correspondence, and when the RN apparatus moves from the coverage area of the first MME pool to the coverage area of the second MME pool, the apparatus further includes: and the acquisition module is used for acquiring the corresponding relation between the routing identifier of the RN device and the MME pool from the operation and maintenance OAM system.

15. The apparatus of claim 14, wherein the apparatus further comprises:

and the setting module is used for setting the corresponding relation between the routing identifier of the RN device and the MME pool.

16. The apparatus of claim 15, wherein the apparatus further comprises:

17. The apparatus of claim 14 or 16, wherein the correspondence of the routing identity of the RN apparatus to the MME pool comprises:

a correspondence between a routing identifier of the RN device and a plurality of MME pools; or,

and the corresponding relation between a plurality of routing identifiers of the RN device and a plurality of MME pools.

18. The apparatus of claim 17, wherein the handover request message includes the routing identity of the RN apparatus and indication information for instructing the source MME to select an MME in a second MME pool as a target MME, if one routing identity of the RN apparatus corresponds to a first MME pool and a second MME pool.

19. The apparatus of claim 17, wherein the handover request message comprises a second routing identification of the RN apparatus if the first routing identification of the RN apparatus corresponds to a first MME pool and the second routing identification of the RN apparatus corresponds to a second MME pool.

20. The apparatus of claim 19, wherein the first notification module is further configured to notify the DNS to delete the stored correspondence between the routing identifier of the RN apparatus and the first MME pool after the source MME determines the target MME and performs the UE context transfer operation with the target MME.

21. A domain name system, DNS, the system comprising:

the receiving module is used for receiving a registration request message sent by a Relay Node (RN);

a storage module, configured to store a correspondence between a corresponding routing identifier of the RN and a mobility management entity MME pool when the receiving module receives a registration request message sent by the RN; the corresponding relation between the routing identification of the RN and the MME pool is used for determining a target MME, wherein the source MME belongs to the first MME pool, and the target MME belongs to the second MME pool; the route identification comprises a Tracking Area Identification (TAI); after the RN moves from the coverage area of the first MME pool to the coverage area of the second MME pool, updating the corresponding relation between the TAI supported by the RN and the MME in the DNS, so that the TAI supported by the RN corresponds to the two MME pools; or, the DNS stores corresponding relations between different TAIs supported by the same RN and a first MME pool and a second MME pool, respectively, when the RN establishes S1 connection with the first MME pool, a part of available TAIs is associated with an MME in the first MME pool, and when the RN moves from a coverage area of the first MME pool to a coverage area of the second MME pool, an unused part of available TAIs is associated with an MME in the second MME pool, and the association is stored in the DNS; in the correspondence stored in the DNS, the TAI and the MME pool are in one-to-one correspondence, and when the RN moves from the coverage area of the first MME pool to the coverage area of the second MME pool, the RN obtains the TAI corresponding to the second MME pool from the operation and maintenance OAM system.

22. The system of claim 21, wherein the receiving module is further configured to receive a deregistration request message sent by the RN.

23. The system of claim 21, wherein the system further comprises:

and the deleting module is used for deleting the corresponding relation between the corresponding routing identifier of the RN and the MME pool when the receiving module receives the logout request message sent by the RN.

24. An operation and maintenance, OAM, system, comprising:

a fourth determining module, configured to determine a correspondence between multiple routing identifiers of the relay node RN and multiple mobility management entity MME pools; the corresponding relation between a plurality of routing identifiers of the RN and a plurality of MME pools is used for determining a target MME, wherein a source MME belongs to a first MME pool, and the target MME belongs to a second MME pool; the route identification comprises a Tracking Area Identification (TAI); the TAI and MME pools are in one-to-one correspondence;

and the second notification module is used for notifying the RN of the routing identifier corresponding to the second MME pool when the RN moves from the first MME pool to the second MME pool, and the RN sends a switching request message containing the routing identifier corresponding to the second MME pool to a source MME of User Equipment (UE) served by the RN.