WO2013107260A1

WO2013107260A1 - Method, device and system for processing route identifier during movement of relay node

Info

Publication number: WO2013107260A1
Application number: PCT/CN2012/087574
Authority: WO
Inventors: 杨义; 鲍炜
Original assignee: 电信科学技术研究院
Priority date: 2012-01-19
Filing date: 2012-12-26
Publication date: 2013-07-25
Also published as: CN103220743A; CN103220743B

Abstract

Disclosed are a method, a device and a system for processing a route identifier during the movement of an relay node (RN). The method comprises: a source mobility management entity (MME) of a user equipment (UE) determining, 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, according to a set correspondence between a route identifier of the RN and an MME pool, a destination MME, the source MME belonging to the first MME pool, and the destination MME belonging to the second MME pool; and the source MME and the destination MME performing a transfer operation on the context of the UE. Therefore, by applying the present application, a source MME of a UE whose context needs to be transferred is capable of finding an MME in a new MME pool as the destination MME, so as to implement the transfer of the context of the UE from one MME pool to another MME pool.

Description

Method, device and system for processing route identifier during relay node movement process The present application claims to be submitted to the Chinese Patent Office on January 19, 2012, the application number is 201210018009.6, and the invention name is "the processing method of the route identifier in the relay node moving process" The priority of the Chinese Patent Application, the entire disclosure of which is incorporated herein by reference.

Technical field

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

Background technique

In the long term evolution system, in order to increase the network coverage area, a Relay Node (RN) is introduced, and the RN is connected to the donor base station in a wireless manner. The RN can be applied to a high-speed mobile environment such as a railway, and the number of handovers of the user equipment (User Equipment, UE) and the number of location updates are reduced by group switching, and the signal quality is improved. In a high-speed mobile environment, the RN connects to the network as the UE, and the network establishes an Evolved Packet System (EPS) for the RN; and the RN accesses the Operation and Maintenance (OAM) system to download the necessary configuration data. From the perspective of the UE, the RN is the serving base station of the UE. When the UE accesses the RN, all the data of the UE is mapped to the bearer of the RN, and is sent to the next hop node by the Packet Data Domain Gateway (PGW) of the RN, for example, the Serving Gateway (SGW) of the UE. ).

In a Mobility Management Entity (MME) pool, several MMEs are concurrently served, and the MME in the MME pool controls the UEs in the area according to the local roaming restriction rules. The UE and the RN under the RN are relatively stationary to maintain a better propagation path. Therefore, during the RN movement, the UE does not normally reselect or handover to a cell other than the RN. When the RN moves across the MME pool, the UE will also enter the new MME pool. At this time, the context of the UE needs to be transferred from the original MME to the MME in the new MME pool.

The S1 handover method is used to transfer the context of the UE. FIG. 1 is a schematic diagram of a process for the UE to perform the S1 handover in the prior art. As shown in FIG. 1 , the UE performs the S1 handover in the prior art, including the following steps:

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

Step 102: The source base station performs a handover decision according to the measurement report, selects a suitable target cell, and sends a handover request message including the target cell identifier to the source MME.

Step 103: The source MME finds the target MME according to the target cell identifier, and sends a pre-transmission and relocation request message to the target MME.

Here, the source MME queries the Domain Name System (DNS) server for the Internet Protocol (IP) address information of the MME serving the TAI according to the Tracking Area Identity (TAI) of the target cell. The result returned by the DNS may include multiple MMEs, and the source MME selects one of them as the target MME. Step 104: The target MME sends a handover request message to the target base station.

Step 105: The target base station reserves resources for the UE, and returns a handover request acknowledgement message to the target MME.

Step 106: The target MME returns a pre-relocation and 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 sends a Radio Resource Control (RRC) connection reconfiguration message to the UE.

Step 109: The UE establishes an RRC connection with the target cell, and returns an R C connection reconfiguration complete message to the target base station.

Step 110: The target base station sends a handover notification message to the target MME, updates the location information of the UE, and converts the downlink data transmission path.

Step 111: The target MME sends a pre-relocation complete message to the source MME.

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

When the RN moves across the MME pool, if the S1 handover method shown in FIG. 1 is used to implement the transfer of the context of the UE from the original MME to the MME in the new MME pool, since the Uu interface TAI remains unchanged during the RN movement, When the source MME queries the DNS server according to the TAI of the target cell in the handover request message, the obtained query result is its own IP address, instead of the IP address of the MME in the new MME pool. Therefore, the source MME cannot find a new one. The MME in the MME pool serves as the target MME, so that when the RN moves across the MME pool, it is impossible to transfer the context of the UE from one MME pool to another MME pool.

Summary of the invention

The embodiment of the invention provides a method, a device and a system for processing a route identifier in a RN mobile process, which are used to transfer the context of the UE served by the RN from one MME pool to another MME pool when the RN moves across the MME pool.

A method for processing a route identifier in a RN mobile process according to an embodiment of the present invention includes:

Determining, by the source MME of the UE, that the serving RN moves from the coverage area of the first MME pool to the coverage area of the second MME pool, determining the target MME according to the corresponding relationship between the route identifier of the RN and the MME pool. The source MME belongs to the first MME pool, and the target MME belongs to the second MME pool;

The source MME performs a transfer operation of the UE context with the target MME.

The apparatus for processing a route identifier in the RN moving process provided by the embodiment of the present invention includes:

a first determining module, configured to determine a target MME according to the corresponding relationship between the route identifier of the RN and the MME pool, when determining that the serving RN moves from the coverage area of the first MME pool to the coverage area of the second MME pool, where The target MME belongs to the second MME pool;

And a transfer module, configured to perform a UE context transfer operation with the target MME determined by the first determining module. A processing system for routing identifiers in an RN mobile process according to an embodiment of the present invention includes:

The RN is configured to serve when moving from the coverage area of the first MME pool to the coverage area of the second MME pool The source MME of the UE sends a handover request message;

a source MME, configured to determine a target MME according to the handover request message sent by the RN, and the corresponding relationship between the route identifier of the RN and the MME pool, and perform the UE context transfer operation with the target MME, where The target MME belongs to the second MME pool.

An RN device provided by an embodiment of the present invention includes:

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

a sending module, configured to send a handover request message to the source MME of the UE that it serves, where the handover request message is used to indicate that the source MME determines the target MME according to the corresponding relationship between the route identifier of the RN device and the MME pool. The source MME belongs to the first MME pool, and the target MME belongs to the second MME pool.

A DNS provided by an embodiment of the present invention includes:

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

And a storage module, configured to store, when the receiving module receives the registration request message sent by the RN, a corresponding relationship between the corresponding route identifier of the RN and the MME pool.

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

a fourth determining module, configured to determine a correspondence between multiple routing identifiers of the RN and multiple MME pools; a second notification module, configured to: when the RN moves from the first MME pool to the second MME pool, The RN corresponding to the second MME pool is notified to the RN, and the RN sends a handover request message including the route identifier corresponding to the second MME pool to the source MME of the UE it serves.

According to the foregoing technical solution, in the embodiment of the present invention, when determining that the serving RN moves from the coverage area of the first MME pool to the coverage area of the second MME pool, the source MME of the UE is configured according to the route identifier of the RN and the MME pool. The corresponding MME determines the target MME, where the source MME belongs to the first MME pool, and the target MME belongs to the second MME pool; the source MME and the target MME perform the UE context transfer operation. Therefore, in the embodiment of the present invention, the source MME of the UE that needs to transfer the context can 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 of a UE performing an S1 handover in the prior art;

2 is a schematic flow chart of a specific embodiment of a method according to the present invention;

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

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

5 is a schematic flow chart of still another embodiment of the method of the present invention;

Figure 6 is a schematic structural view of an embodiment of the device of the present invention; Figure 7 is a schematic structural view of an embodiment of a system of the present invention;

Figure 8 is a schematic structural view of an RN device in the present invention;

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

Figure 10 is a schematic view showing the structure of an OAM system in 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 stationary to maintain a better propagation path.

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

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

As shown in FIG. 2, the method for processing a route identifier in the R mobility process provided by the embodiment of the present invention includes the following steps:

Step 201: When determining that the serving RN moves from the coverage area of the first MME pool to the coverage area of the second MME pool, the MME determines the target MME according to the corresponding relationship between the route identifier of the RN and the MME pool, where the source MME It 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 the handover request message sent by the serving RN.

The corresponding relationship between the route identifier of the RN and the MME pool includes: a correspondence between a route identifier of the RN and multiple MME pools; or a correspondence between multiple route identifiers of the RN and multiple MME pools. And determining, by the source MME, the target MME according to the handover request message sent by the RN and the correspondence between the route identifier of the RN and the second MME pool, where the handover request message is sent, where the MME sends a route identifier to the first MME pool and the second MME pool. The routing identifier of the RN and the indication information for indicating that the source MME selects the MME in the second MME pool as the target MME; when the first routing identifier of the RN corresponds to the first MME pool, and the second routing identifier of the RN corresponds to the second MME The source MME determines the target MME according to the handover request message sent by the RN and the correspondence between the second route identifier of the RN and the second MME pool, where the handover request message includes the second route identifier of the RN.

If the mapping between the RN and the MME is stored in the DNS, the source MME obtains the mapping between the RN's route identifier and the MME pool by querying the DNS.

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

Step 202: The source MME performs a UE context transfer operation with the target MME.

Here, the transfer operation can be performed according to the corresponding steps in the S1 switching method shown in Fig. 1, and will not be described in detail here.

Step 203: The correspondence between the route identifier of the set RN and the first MME pool is released.

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

3 is a schematic flow chart of another embodiment of the method of the present invention. As shown in FIG. 3, the method for processing a route identifier in a RN moving process provided by the embodiment of the present invention includes the following steps:

Step 301: After the RN moves from the first MME pool to the second MME pool, establish 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 to the second MME pool.

Step 302: Update the correspondence between the TAI and the MME supported by the RN in the DNS, so that the TAI supported by the RN corresponds to two MME pools.

Step 303: The RN sends a handover request message including the TAI and the indication information to the source MME of the UE that needs to transfer the context, where the indication information is used to indicate that the purpose of the handover is to transfer the context of the UE.

Step 304: The source MME queries the DNS according to the TAI, and selects the MME in the second MME pool as the 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 the handover request message received by the source MME includes indication information indicating that the current handover destination is to transfer the UE context, The source MME selects the MME in the second MME pool that does not include itself as the target MME.

Step 305: The source MME performs a transfer operation of the UE context with the target MME.

Step 306: Determine whether there is still a UE that needs to transfer the context. If yes, go back to step 303, otherwise go to step 307.

Step 307: The RN releases the S1 connection with the first MME pool, and updates the correspondence between the TAI and the MME supported by the RN in the DNS, so that the TAI supported by the RN no longer corresponds to the first MME pool.

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

As shown in FIG. 4, the method for processing a route identifier in a RN moving process provided by the embodiment of the present invention includes the following steps:

Step 401: R downloads configuration information including multiple available TAIs from the OAM system.

Step 402: When the RN establishes an S1 connection with the first MME pool, the RN selects a part of the available TAIs to associate with the MME in the first MME pool, and stores the corresponding relationship in the DNS.

Step 403: When the RN moves from the first MME pool to the second MME pool, select the unused portion of the available TAI to associate with the MME in the second MME pool, and store the corresponding relationship in the DNS.

At this time, the correspondence between the different TAIs supported by the same R and the first MME pool and the second MME pool is stored in the DNS.

Step 404: The RN sends a handover request message including a target cell TAI to the source MME of the UE that needs to transfer the context, where the target cell TAI is a TAI corresponding to the second MME pool. Step 405: The source MME performs an inquiry in the DNS according to the target cell TAI, and obtains the MME in the second MME pool as the target MME.

Here, if the obtained MME in the second MME pool is multiple MMEs, one of them is selected as a target. Step 406: The source MME and the target MME perform a transfer operation of the UE context.

Step 407: Determine whether there is still a UE that needs to transfer the context. If yes, go back to step 404, otherwise go to step 408.

Step 408: The RN releases the S1 connection with the first MME pool, and updates the correspondence between the TAI and the MME supported by the RN in the DNS, so that the TAI supported by the RN no longer corresponds to the first MME pool.

Here, the TAI associated with the first MME pool has been released, and can continue to be used when the RN moves to the next MME pool, increasing the application flexibility of the TAI.

Step 409: The RN updates the TAI of the air interface at the set time, so that the RN uses the TAL associated with the second MME pool. FIG. 5 is a schematic flowchart of still another embodiment of the method according to the present invention.

As shown in FIG. 5, the method for processing a route identifier in a RN mobility process according to an embodiment of the present invention includes the following steps:

Step 501: The OAM system determines a correspondence between the TAI allocated to the RN and multiple MME pools, and stores the corresponding relationship in the DNS.

Here, the TAI and the MME pool are corresponding to each other, and the correspondence does not change.

Step 502: When the RN moves from the first MME pool to the second MME pool, obtain the TAL corresponding to the second MME pool 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 searches for the TAI corresponding to the second MME pool according to the setting information, and sends the information to the RN.

Step 503: The RN establishes an S1 interface with the MME in the second MME pool, and notifies the MME corresponding to the second MME pool to the MME in the second MME pool.

Step 504: The RN sends a handover request message including the target cell TAI to the source MME of the UE that needs to transfer the context, where the target cell TAI is the TAI corresponding to the second MME pool.

Step 505: The source MME performs an inquiry in the DNS according to the target cell TAI, and obtains the MME in the second MME pool as the target MME.

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

Step 506: The source MME performs a transfer operation of the UE context with the target MME. Here, the transfer operation may be performed according to the corresponding steps in the S 1 switching method shown in FIG. 1, and will not be described in detail here.

Step 507: Determine whether there is still a UE that needs to transfer the context. If yes, go back to step 504, otherwise go to step 508.

Step 508: R releases the S 1 connection with the first MME pool.

Step 509: The RN updates the TAI of the air interface at the set time, so that the RN uses the TAL associated with the second MME pool. FIG. 6 is a schematic structural diagram of an apparatus embodiment of the present invention.

Referring to FIG. 6, the apparatus for processing a route identifier in a RN mobility process according to an embodiment of the present invention includes: a first determining module 61, configured to: determine, in a serving area, that a serving RN moves from a coverage area of a first MME pool to a second MME pool. When the area is covered, the target MME is determined according to the corresponding relationship between the route identifier of the RN and the MME pool, where the target MME belongs to the second MME pool;

The transferring module 62 is configured to perform a UE context transfer operation with the target MME determined by the first determining module. The device still further includes:

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

The querying module is configured to query the DNS to obtain the correspondence between the routing identifier of the RN and the MME pool when the mapping between the routing identifier of the RN and the MME pool is stored in the DNS.

Here, the correspondence between the route identifier of the RN and the MME pool includes: a correspondence between a route identifier of the RN and multiple MME pools; or a correspondence between multiple route identifiers of the RN and multiple MME pools. Preferably, the route identification includes a TAI and/or a global base station identity.

If the RN of the RN corresponds to the first MME pool and the second MME pool, the first determining module 61 is configured to determine the target MME according to the handover request message sent by the RN and the correspondence between the route identifier of the RN and the second MME pool. The handover request message includes a route identifier of the RN and indication information for indicating that the source MME selects the MME in the second MME pool as the target MME.

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

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

As shown in FIG. 3, the processing apparatus for routing identifiers in the RN mobility process according to the embodiment of the present invention includes: an RN 71, configured to move to a coverage area of a second MME pool when moving from a coverage area of the first MME pool to the MME pool The source MME 72 of the serving UE sends a handover request message;

The source MME 72 is configured to determine a target MME according to the handover request message sent by the RN 71 and the corresponding relationship between the route identifier of the RN 71 and the MME pool, and perform a UE context transfer operation with the target MME, where the target The MME belongs to the second MME pool.

Figure 8 is a schematic view showing the structure of an RN device in the present invention.

As shown in FIG. 8, the RN device provided by the embodiment of the present invention includes:

The third determining module 81 is configured to determine, according to the obtained identifier information of the MME pool, that the RN device moves from the coverage area of the first MME pool to the coverage area of the second MME pool;

The sending module 82 is configured to send, to the source MME of the UE that it serves, a handover request message, where the handover request message is used to indicate that the source MME determines the target MME according to the corresponding relationship between the route identifier of the set RN device and the MME pool, where the source MME It belongs to the first MME pool, and the target MME belongs to the second MME pool.

Here, the device further includes:

a setting module, configured to set a correspondence between a route identifier of the RN device and the MME pool;

And a release module, configured to: after the source MME determines the target MME, and performs a UE context transfer operation with the target MME, the corresponding relationship between the route identifier of the set RN device and the first MME pool is released.

The device still further includes:

The obtaining module is configured to obtain, from the OAM system, a correspondence between a route identifier of the RN device and the MME pool.

Corresponding relationship between the route identifier of the R device and the MME pool includes a correspondence between a route identifier of the RN device and multiple MME pools; or a correspondence between multiple route identifiers of the RN device and multiple MME pools. If the route identifier of the RN device corresponds to the first MME pool and the second MME pool, the handover request message includes a route identifier of the RN device and indication information used to indicate that the source MME selects the MME in the second MME pool as the target MME; 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 handover request message includes the second routing identifier of the RN device.

The device still further includes:

The first notification module is configured to notify the DNS storage RN device of the corresponding relationship between the route identifier and the MME pool; and after the source MME determines the target MME, and performs the UE context transfer operation with the target MME, notifying the DNS to delete the stored RN device Correspondence between the route identifier and the first MME pool.

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 a DNS in the present invention.

Referring to FIG. 9, the DNS provided by the embodiment of the present invention includes:

The receiving module 91 is configured to receive a registration request message sent by the RN.

The storage module 92 is configured to store, when the receiving module 91 receives the registration request message sent by the RN, the correspondence between the corresponding route identifier of the RN and the MME pool.

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

The system further includes:

a deleting module, configured to delete the corresponding RN when the receiving module 91 receives the logout request message sent by the RN Correspondence between the route identifier and the MME pool.

As shown in FIG. 10, the OAM system provided by the embodiment of the present invention includes:

The fourth determining module 1001 is configured to determine a correspondence between multiple routing identifiers of the RN and multiple MME pools. The second notification module 1002 is configured to: when the RN moves from the first MME pool to the second MME pool, The route identifier corresponding to the MME pool is notified to the RN, and the RN sends a handover request message including the route identifier corresponding to the second MME pool to the source MME of the UE it serves.

Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can be embodied in the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.

The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each process and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram. It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and modifications of the invention

Claims

Rights request

A method for processing a route identifier in a process of moving a relay node RN, the method comprising: the source mobility management entity MME of the user terminal UE moves to determine that the serving RN moves from the coverage area of the first MME pool to the first Determining a target MME according to the corresponding relationship between the route 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;

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

The method according to claim 1, wherein the mapping between the route identifier of the RN and the MME pool includes:

Corresponding relationship between a route identifier of the RN and multiple MME pools; or

Corresponding relationship between multiple routing identifiers of the RN and multiple MME pools.

The method according to claim 3, wherein if a route identifier of the RN corresponds to the first MME pool and the second MME pool, the source MME according to the set route identifier of the RN and the MME pool The correspondence determines the target MME, including:

Determining, by the source MME, the target MME according to the handover request message sent by the RN and the correspondence between the route identifier of the RN and the second MME pool, where the handover request message includes a route identifier of the RN and is used to indicate the The source MME selects the MME in the second MME pool as the indication information of the target MME.

The method according to claim 3, wherein if the first routing identifier of the RN corresponds to the first MME pool, and the second routing identifier of the RN corresponds to the second MME pool, the source MME is configured according to the The mapping between the route identifier of the RN and the MME pool determines the target MME, including:

The source MME determines the target MME according to the handover request message sent by the RN and the corresponding relationship between the second route identifier of the RN and the second MME pool, where the handover request message includes the second route identifier of the RN.

6. The method of claim 1, wherein the method further comprises:

The mapping between the routing identifier of the RN and the MME pool is stored in the domain name system DNS, and the source MME obtains the correspondence between the routing identifier of the RN and the MME pool by querying the DNS.

The method according to claim 6, wherein after the source MME and the target MME perform the UE context transfer operation, the method further includes:

The RN notifies the DNS to delete the corresponding relationship between the stored route identifier of the RN and the first MME pool.

The method according to claim 1, wherein after the source MME and the target MME perform the UE context transfer operation, the method further includes:

The corresponding relationship between the route identifier of the RN and the first MME pool is released.

The method according to any one of claims 1 to 8, wherein the route identifier comprises a tracking area identifier TAI and/or a global base station identifier.

A device for processing a route identifier in a process of moving a relay node RN, the device comprising: a first determining module, configured to: after determining that the serving RN moves from a coverage area of the first mobility management entity MME pool to Determining a target MME according to the corresponding relationship between the route identifier of the RN and the MME pool, where the target MME belongs to the second MME pool;

And a transfer module, configured to perform a transfer operation of the user terminal UE context with the target MME determined by the first determining module.

11. The device of claim 10, wherein the device further comprises:

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

The device according to claim 10, wherein if a route identifier of the RN corresponds to the first MME pool and the second MME pool,

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 route identifier of the RN and a second MME pool, where the handover request message includes a route of the RN And the indication information used to indicate that the source MME selects an MME in the second MME pool as a target MME.

The device according to claim 10, wherein, if the first route identifier of the RN corresponds to the first MME pool, and the second route identifier of the RN corresponds to the second MME pool,

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 route identifier of the RN and a second MME pool, where the handover request message includes the RN The second route identifier.

14. The device of claim 10, wherein the device further comprises:

The querying module is configured to query the DNS to obtain the correspondence between the routing identifier of the RN and the MME pool when the mapping between the routing identifier of the RN and the MME pool is stored in the DNS of the domain name system.

A processing system for routing identifiers in a process of moving a relay node RN, the system comprising: an RN, configured to move from a coverage area of a first mobility management entity MME pool to a second MME pool In the case of a region, sending a handover request message to the source MME of the user terminal UE that it serves;

16. A relay node RN device, the device comprising:

a third determining module, configured to determine, according to the obtained identification information of the MME pool of the mobility management entity, that the RN device moves from a coverage area of the first MME pool to a coverage area of the second MME pool; a sending module, configured to send, to the source MME of the user terminal UE that it serves, a handover request message, where the handover request message is used to indicate that the source MME determines the target according to the corresponding relationship between the route identifier of the RN device and the MME pool. The MME, where the source MME belongs to the first MME pool, and the target MME belongs to the second MME pool.

The device of claim 16, wherein the device further comprises:

And a setting module, configured to set a correspondence between the route identifier of the RN device and the MME pool.

The device of claim 17, wherein the device further comprises:

And a release module, configured to: after the source MME determines the target MME, and performs a UE context transfer operation with the target MME, releasing the corresponding relationship between the set route identifier of the RN device and the first MME pool.

The device of claim 16, wherein the device further comprises:

The obtaining module is configured to obtain, from the operation and maintenance OAM system, a correspondence between the route identifier of the RN device and the MME pool.

The device of claim 16, wherein the device further comprises:

The first notification module is configured to notify the domain name system DNS to store the correspondence between the route identifier of the RN device and the MME pool.

The apparatus according to claim 20, wherein the first notification module is further configured to: after the source MME determines the target MME, and after performing the UE context transfer operation with the target MME, notify the DNS Deleting the stored correspondence between the route identifier of the RN device and the first MME pool.

22. A domain name system DNS, characterized in that the system comprises:

a receiving module, configured to receive a registration request message sent by the relay node RN;

And a storage module, configured to store, when the receiving module receives the registration request message sent by the RN, a correspondence between a corresponding route identifier of the RN and a mobility management entity MME pool.

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

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

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

25. An operation and maintenance OAM system, characterized in that the system comprises:

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;

a second notification module, configured to: when the RN moves from the first MME pool to the second MME pool, notify the RN of the route identifier corresponding to the second MME pool, where the RN includes the second MME pool The handover request message of the corresponding route identifier is sent to the source MME of the user terminal UE it serves.