WO2014044117A1

WO2014044117A1 - Gateway relocation method and mobility management entity

Info

Publication number: WO2014044117A1
Application number: PCT/CN2013/082595
Authority: WO
Inventors: 黄莹; 高音; 褚丽; 谢峰
Original assignee: 中兴通讯股份有限公司
Priority date: 2012-09-18
Filing date: 2013-08-29
Publication date: 2014-03-27
Also published as: CN102892155A; CN102892155B

Abstract

A gateway relocation method and a mobility management entity (MME). The method comprises: in a process where a destination master base station (DeNB) is switched for a mobile relay node (MRN), an MME of the MRN receiving gateway relocation determination information, and after receiving the gateway relocation determination information, determining, according to the gateway relocation determination information, whether to relocate a serving gateway for the MRN. Through the embodiments of the present invention, it can be determined whether to execute gateway relocation in a switch process for the MRN, so that route optimization is successfully executed, thereby shortening the delay of UE data and signaling.

Description

Gateway relocation method and mobility management entity

Technical field

The present invention relates to the field of wireless communication technologies, and in particular, to a method for relocation of a gateway and a mobility management entity.

Background technique

In the wireless relay technology of the LTE-Advanced standard introduced by the 3GPP standards organization, a relay node (RN) provides a common eNB (UE) to a UE (user equipment) accessing its cell. Node Β ) similar functions and services, and access to an eNB (referred to as DeNB, host base station) serving it in a manner similar to a normal UE through a wireless interface. As high-speed railways are built and put into operation on a large scale, the demand for communication on trains continues to increase. However, due to the influence of Doppler frequency shift, frequent cell switching and high-speed rail penetration loss, the coverage of existing network base stations is difficult to meet the communication quality requirements of high-speed rail. Therefore, the industry proposes to deploy relay nodes on high-speed rails, which are usually called mobile relay nodes (MRNs). As shown in FIG. 1 and FIG. 2, the mobile relay technology can enable users (UE1 and UE2) in the high-speed train to communicate with relatively stationary mobile relay nodes, and the MRN can be different in the process of moving with the high-speed rail. The switching between the DeNBs avoids the simultaneous handover of a large number of users in the high-speed rail car, ensures the communication quality between the UE and the MRN, and can better solve the high-speed existence by enhancing the backbone connection between the mobile MRN and the DeNB. a series of questions.

When the mobile relay uses the architecture shown in Figure 1 (i.e., the same architecture as the standardized RIO fix relay, commonly referred to as architecture 2), in which the SGW, PGW, and relay for the MRN service are built into the DeNB. GW, where the relay GW in the DeNB provides the S1/X2 proxy function for the user plane data and control plane signaling of the UE. In this architecture, the SGW/PGW/relay GW of the MRN (collectively referred to as GW) is located in the initial DeNB (initial DeNB) that is accessed when it is attached, and when the MRN on the high-speed rail moves farther from the initial DeNB, the UE After the data arrives at the PGW of the MRN, the route will be forwarded through multiple DeNBs to reach the DeNB of the serving MRN, that is, there is a problem that the routing path is too long, and the delay of the UE data is increased. Therefore, a route optimization scheme may be considered. When the MRN moves to a far distance from the initial DeNB, the GW of the MRN is used in the handover process of the MRN. Replace with a gateway built into the DeNB that serves the MRN. As shown in FIG. 2, before the MRN handover, the GW is located on the DeNB1, and the MRN is served by the base station function of the DeNB3. The data of the UE first reaches the GW function of the DeNB1, and then the DeNB2 routes to the base station function of the DeNB3, and the MRN can be in the handover process. The GW is relocated to the GW built in the DeNB4, so that the data of the UE can directly reach the GW in the DeNB4, shortening the path length and reducing the data delay.

The mobile relay system can also use the architecture shown in Figure 3 (commonly referred to as architecture 1). The architecture does not have a relay GW functional entity. The SGW and PGW serving the MRN are located in the core network, and the DeNB uses the user plane data of the UE. The control plane signaling is encapsulated into GTP-U data packets and sent to the SGW and PGW of the MRN through the bearer of the mobile relay, and then routed to the MME or SGW of the UE through the IP. With the high-speed movement of the train, when the GW serving the MRN in the core network is far away from the MRN, the routing path is too long, and the GW of the MRN may be relocated to the current service during the handover of the MRN. SGW/PGW near the DeNB of the MRN.

Therefore, it is not necessary to perform the relocation of the gateway every time the MRN is switched, but only when the routing path is long. Therefore, it is necessary to solve the problem of determining whether to perform the gateway relocation in the handover process of the MRN. Summary of the invention

The technical problem to be solved by the present invention is to provide a method for gateway relocation and a mobility management entity, which can determine whether a mobile relay node relocation service is required when the mobile relay node switches the donor base station.

To solve the above technical problem, a method for gateway relocation according to the present invention includes: receiving, in a process of handover of a donor base station (DeNB) for a mobile relay node (MRN), a mobility management entity (MME) of the MRN The gateway relocation judgment information, after receiving the gateway relocation judgment information, determines whether the gateway is the MRN relocation service according to the gateway relocation judgment information.

Preferably, the gateway relocation judgment information includes a gateway relocation judgment indication identifier, and the gateway relocation judgment indication identifier indicates whether the gateway is the MRN relocation service.

Preferably, the MME of the MRN receives the gateway relocation determination information, and the MME of the MRN receives the gateway relocation determination indication identifier from the target DeNB of the MRN. The gateway relocation judgment indication identifier is sent by the source DeNB of the MRN according to whether the measured cell reported by the MRN is included in the gateway relocation cell list, and whether the target cell of the MRN is included in the gateway relocation cell list, and then sent to the The target DeNB, when the target cell of the MRN is included in the gateway relocation cell list, the gateway relocation determination indication identifier indicates the gateway of the MRN relocation service.

Preferably, the MME of the MRN receives the gateway relocation determination information, and the MME of the MRN receives the gateway relocation determination indication identifier from the target DeNB of the MRN, where the gateway relocation determination indication identifier is determined by the target DeNB. Whether the target cell of the MRN on the MRN includes a gateway that determines whether the gateway relocation determination indication indicator indicates that the MRN relocation service is in the gateway relocation cell list, and sends the message to the MME, where the target cell of the MRN is included. When the gateway relocates the cell list, the gateway relocation judgment indication flag indicates a gateway serving the MRN relocation service.

Preferably, the MME of the MRN receives the gateway relocation determination information, and the MME of the MRN receives the gateway relocation determination indication identifier from the source DeNB of the MRN, where the gateway relocation determination indication identifier is determined by the source DeNB of the MRN. Whether the measured cell reported by the MRN is included in the gateway relocation cell list, determines whether the target cell of the MRN is included in the gateway relocation cell list, and sends the target cell to the MME, where the target cell of the MRN is included in the gateway relocation cell list. In the middle, the gateway relocation judgment indication identifier indicates a gateway that is the MRN relocation service.

Preferably, when the MME needs to be reselected for the MRN, the MME of the MRN includes

a source MME of the MRN and a target MME of the MRN, the source MME receiving a gateway relocation determination indication identifier from the source DeNB, and sending a gateway relocation determination indication identifier to the target MME, indicating whether the target MME is the MRN The gateway for the location service.

Preferably, when the MME needs to be reselected for the MRN, the MME of the MRN includes the source MME of the MRN and the target MME of the MRN, and the target MME receives the gateway relocation determination indication identifier from the target DeNB.

Preferably, the MRN reports, by using the measurement report, whether the measured cell is included in the gateway relocation cell list. Preferably, the MRN reports, by using a radio resource control (RRC) connection reconfiguration message, whether the target cell of the MRN is included in the gateway relocation cell list.

Preferably, the gateway relocation judgment information includes a gateway relocation cell list, and the identifier of the cell of the gateway that needs to be the MRN relocation service when the target cell as the MRN is recorded in the gateway relocation cell list.

Preferably, the MME of the MRN receives the gateway relocation judgment information, and includes: the MME of the MRN receives a gateway relocation cell list from the MRN, a home subscriber server (HSS), or an MME that is served by the MRN last time. The list of gateway relocation cells is stored in the context of the MRN.

Preferably, determining, according to the received gateway relocation judgment information, whether the gateway is the gateway for the MRN relocation service, includes:

After receiving the path transfer request of the target DeNB, the MME of the MRN determines whether the target cell of the MRN is included in the gateway relocation cell list in the context of the MRN, and if yes, determines the gateway of the MRN relocation service. .

Preferably, after receiving the handover request message, the MME of the MRN determines whether the target cell of the MRN is included in the gateway relocation cell list in the context of the MRN, and if yes, determines the gateway of the MRN relocation service. .

Preferably, when the MME needs to be reselected for the MRN, the MME of the MRN includes the source MME of the MRN and the target MME of the MRN, and the source MME receives the gateway relocation from the MRN, the HSS, or the MME that served the MRN last time. After the cell list, the gateway relocation 'J, the zone list is saved in the context of the MRN.

After receiving the handover request message of the source DeNB, the source MME of the MRN determines whether the target cell of the MRN is included in the gateway relocation cell list in the context of the MRN, and sends a gateway relocation cell list and a gateway to the target MME. And a relocation judgment indication identifier indicating whether the target MME is a gateway of the MRN relocation service.

Preferably, determining, according to the received gateway relocation judgment information, whether to reset the MRN Gateway for bit services, including:

After receiving the handover request message of the source DeNB, the source MME of the MRN sends a gateway relocation cell list to the target MME, where the target MME determines whether the target cell of the MRN is included in the gateway relocation cell list, and determines Whether to be the gateway of the MRN relocation service.

Preferably, when the MME of the MRN does not receive the gateway relocation determination information, it determines that the gateway does not serve the MRN relocation.

Preferably, the method further comprises:

After the MME of the MRN determines that the MRN relocates the gateway of the service, the gateway performs a relocation service, and the gateway of the relocation service includes a packet data network gateway (P-GW) serving the MRN relocation service. And a serving gateway (S-GW); or, the gateway of the relocation service includes a P-GW, an S-GW, and a relay GW (relay GW) serving the MRN relocation.

Preferably, the method further comprises:

After the MME of the MRN determines that the gateway of the MRN relocation service is performed, performing relocation, where the relocation includes reselecting a gateway serving the MRN, and transferring the core network bearer and context information of the MRN To the reselected gateway.

Preferably, the MME of the MRN reselects the gateway serving as the MRN according to the address of the gateway sent by the target DeNB of the received MRN.

Preferably, the MME of the MRN receives a list of relocation celles from the MRN or the HSS in the attaching process of the MRN; or

The MME of the MRN receives the gateway relocation cell list from the MME that served the MRN last time during the attachment, tracking area update or handover of the MRN.

Preferably, the identifier of the cell that needs to be the gateway of the MRN relocation service when the target cell in the cell relocation cell list is the at least one of the following: the cell identifier, the physical cell identifier, and the base station identifier of the base station to which the cell belongs .

A mobility management entity, comprising: a receiving unit and a determining unit, wherein:

The receiving unit is configured to: receive a gateway relocation judgment information during a process of switching a donor base station (DeNB) for a mobile relay node (MRN); The determining unit is configured to: after the receiving unit receives the gateway relocation determination information, determine, according to the gateway relocation determination information, whether the gateway is the MRN relocation service.

Preferably, the receiving unit is configured to: receive a gateway relocation determination indication identifier from the target DeNB of the MRN, where the gateway relocation determination indication identifier is determined by the source DeNB of the MRN according to whether the measured cell reported by the MRN is included in the gateway In the locating cell list, determining whether the target cell of the MRN is included in the gateway relocation cell list, and sending the signal to the receiving unit, where the target cell of the MRN is included in the gateway relocation cell list, the gateway relocation judgment indication indicator indication A gateway that serves the MRN relocation service.

Preferably, the receiving unit is configured to: receive a gateway relocation determination indication identifier from the target DeNB of the MRN, where the gateway relocation determination indication identifier is determined by the target DeNB according to whether the target cell of the MRN reported by the MRN is included in the gateway And determining, by the relocation cell list, whether the gateway relocation judgment indication flag indicates that the gateway is the MRN relocation service, and sending the information to the receiving unit, where the target cell of the MRN is included in the gateway relocation cell list, the gateway relocation The judgment indication identifier indicates a gateway of the MRN relocation service.

Preferably, the receiving unit is configured to: receive a gateway relocation determination indication identifier from the source DeNB of the MRN, where the gateway relocation determination indication identifier is determined by the source DeNB of the MRN according to whether the measured cell reported by the MRN is included in the gateway In the locating cell list, after determining whether the target cell of the MRN is included in the gateway relocation cell list, the MME is sent to the MME, and when the target cell of the MRN is included in the gateway relocation cell list, the gateway relocation judgment indication flag indication is The gateway of the MRN relocation service.

Preferably, the receiving unit is configured to: receive a gateway relocation cell list from the MRN, a home subscriber server (HSS), or an MME that served the MRN last time, and relocate the gateway relocation 'J, the zone list is saved in In the context of the MRN.

Preferably, the determining unit is configured to: receive a path transfer request of the target DeNB Then, it is determined whether the target cell of the MRN is included in the gateway relocation cell list in the context of the MRN, and if yes, the gateway of the MRN relocation service is determined.

Preferably, the determining unit is configured to: after receiving the handover request message, determine whether the target cell of the MRN is included in the gateway relocation cell list in the context of the MRN, and if yes, determine that the MRN is relocated The gateway of the service.

In summary, the embodiment of the present invention can solve the problem of determining whether to perform gateway relocation in the MRN handover process, so that route optimization is smoothly performed, thereby shortening delay of UE data and signaling. BRIEF abstract

1 is a schematic diagram of a first architecture of a mobile relay system in a high-speed rail scenario;

2 is a schematic diagram of route optimization in the first architecture of the mobile relay system;

3 is a schematic diagram of a second architecture of a mobile relay system in a high-speed rail scenario;

4 is a schematic flow chart of Embodiment 1 of a method according to the present invention;

5 is a schematic flow chart of Embodiment 2 of a method according to the present invention;

6 is a schematic flow chart of Embodiment 3 of the method according to the present invention;

7 is a schematic flow chart of Embodiment 4 of a method according to the present invention;

8 is a schematic flow chart of Embodiment 5 of a method according to the present invention;

9 is a schematic flow chart of Embodiment 6 of the method according to the present invention;

FIG. 10 is a structural diagram of a mobility management entity according to an embodiment of the present invention. Preferred embodiment of the invention

In the embodiment, in the process of switching the DeNB for the MRN, the MME of the MRN receives the gateway relocation determination information, and after receiving the gateway relocation determination information, determines whether the gateway is the MRN relocation service according to the gateway relocation determination information.

The gateway relocation judgment information includes a gateway relocation judgment indication identifier and a gateway relocation cell list. The gateway relocation judgment indication flag indicates whether it is a gateway of the MRN relocation service. A network that needs to be relocated for the MRN when the target cell of the MRN is recorded in the gateway relocation cell list The identity of the closed cell.

The MME of the MRN performs relocation after determining the gateway of the MRN relocation service, and the gateway of the relocation service includes the P-GW and the S-GW serving the MRN relocation; or the gateway of the relocation service includes relocation for the MRN Serving P-GW, S-GW and trunking gateway.

Relocation includes reselecting the gateway serving the MRN and transferring the core network bearer and context information of the MRN to the reselected gateway. The MME of the MRN reselects the gateway serving as the MRN according to the address of the gateway transmitted by the target DeNB of the received MRN.

When the MME of the MRN does not receive the gateway relocation judgment information, it determines the gateway that does not relocate the service for the MRN.

In order to make the objects, the technical solutions and the advantages of the present invention more clearly, the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments of the present application may be arbitrarily combined with each other.

The following embodiments are applicable to both mobile relay system architectures shown in Figures 1 and 3. In the architecture shown in Figure 1, the S-GW, P-GW, and relay GW serving the MRN are all built in the DeNB. Under the architecture shown in Figure 2, there is no relay GW functional entity, and the S-GW serving the MRN and The P-GW is not built into the DeNB, but is located in the core network.

Embodiment 1:

This embodiment describes a method in which a mobile relay node (MRN) obtains a gateway relocation cell list and indicates whether the source or target DeNB target cell is in the gateway relocation cell list through the air interface, and performs the gateway in the X2 handover process of the MRN. The process of relocation. FIG. 4 illustrates the flow of the embodiment, in which the flow in the architecture shown in FIG. 1 is used, where the source S-GW and the source P-GW of the MRN may be built in the source DeNB, or may not be built in the source DeNB. It is built in the initial DeNB (initial DeNB). In this embodiment, the architecture shown in FIG. 3 can also be used, and the source S-GW and the P-GW of the MRN, the target S-GW and the P-GW are all located in the core network.

method one:

Step 401. The MRN obtains a list of gateway relocation cells. The MRN can obtain a list of gateway relocation cells in the following three ways:

1) by way of pre-configuration;

2) Obtained from the accessed donor base station (DeNB); the DeNB may obtain a list of gateway relocation cells from the network management system OAM of the DeNB.

3) obtained from the OAM of the MRN;

The identifier of the cell of the gateway that needs to be relocated by the MRN when the target cell as the MRN is recorded in the gateway relocation cell list. The gateway relocation cell list includes an identifier of one or more cells, where the identifier includes at least one of the following: a cell identifier, a physical cell identifier, and a base station identifier of the base station to which the cell belongs.

Step 402: The MRN measures that the one or more cells satisfy the trigger condition of the measurement report, and then sends the identifier and the measurement parameter of the cell that meet the condition to the source DeNB serving the same by using the measurement report. The MRN also indicates in the measurement report whether one or more of the cells are included in the gateway relocation list. The MRN may carry the identifier of the cell included in the gateway relocation list (add a list of cells in the list) in the measurement report, or the indication of the cell association in the measurement report indicating whether it is included in the gateway relocation list information.

Step 403. After receiving the measurement report of the MRN, the source DeNB determines that there is an X2 interface between the source and the target DeNB, and after the handover, the MRN does not need to replace the MME, and the source DeNB initiates an X2 handover for the MRN. The source DeNB selects a target cell for the MRN based on the measurement report. The source DeNB sends an X2 interface handover request message to the target DeNB. The handover request message includes a gateway relocation determination indication identifier for indicating whether a gateway relocation is required.

If the target cell is in the gateway relocation cell list, it indicates that gateway relocation is required; otherwise, it indicates that no gateway relocation is required.

Step 404. The target DeNB reserves resources for the MRN and creates context information according to the QoS and other information of the E-RAB (E-UTRAN Radio Access Bearer) to be established in the handover request message, and then replies to the handover request acknowledgement message. . The handover request acknowledgement message includes a handover command message of the transparent air interface.

Step 405: The source DeNB sends an air interface message RRC connection reconfiguration message to the MRN, where the RRC message carries a transparent handover command message sent by the target DeNB to the MRN through the source DeNB. To instruct the MRN to perform the handover.

Step 406. The source DeNB sends an SN state transition message to the target DeNB for transmitting the RLC AM mode radio bearer uplink and downlink PDCP SN receiving and transmitting states.

Step 407. After receiving the handover command, the MRN detaches from the source DeNB cell, synchronizes with the target cell, and initiates a RACH process to access the target cell. After the MRN completes the RRC connection with the target cell, it sends an RRC Connection Reconfiguration Complete message to the target DeNB.

Step 408: After receiving the RRC reconfiguration complete message sent by the MRN, the target DeNB sends a path switch request message to the MME of the MRN to update the S1 user plane and the control plane path of the MRN. The path transfer request message includes a gateway relocation judgment indication identifier, which is used to indicate whether a relocation of the gateway is required.

The gateway relocation judgment indication identifier may be an explicit indication information, and if the relocation of the gateway is required, the path transfer request message further includes an address of the S-GW and the P-GW built in the target DeNB to assist the MRN. The MME relocates the gateway of the MRN to the gateway in the target DeNB. In the mobile relay architecture shown in FIG. 1, the gateway relocation judgment indication identifier may also be implicit information implicitly indicated by a specific cell. The specific cell may be the address information of the S-GW and the P-GW built in the target DeNB. If the relocation of the gateway is required, the message may be carried to the MME by carrying the address information of the GW built in the DeNB.

Step 409. After receiving the path transfer request message, the MME of the MRN determines whether to perform gateway relocation according to the gateway relocation judgment indication flag included in the message. If it is determined that the gateway relocation needs to be performed, the S-GW and the P-GW in the target DeNB received in the path transfer request message are selected as the new gateway serving the MRN.

Step 410: The MME of the MRN sends a Create Session Request message to the target SGW (S-GW built in the target DeNB), which includes the EPS bearer information of the MRN to be created and the address of the target PGW (PGW built in the target DeNB).

Step 411. The target SGW creates a context of the MRN and sends a create session request message to the target PGW.

Step 412: After the target PGW creates the context and the EPS bearer of the MRN, the target PGW replies to the Create Session Response message. The target PGW can assign a new IP address to the MRN. Target S-GW In the case that the P-GW is built in the DeNB, the signaling in step 411 and step 412 is an internal interface message in the target DeNB.

Step 413: The target SGW replies to the MME of the MRN to create a session response message, to confirm that the context of the MRN and the establishment of the EPS 7 are completed.

Step 414: The MME of the MRN sends a path transfer request acknowledgement message to the target DeNB. Then, the MRN or the target DeNB may initiate a path transfer request process for the UE served by the MRN to transfer the downlink S1 path of the UE. In the system architecture shown in FIG. 1, the SI user plane GTP-U tunnel mapping relationship of the new relay GW built in the target DeNB can also be established through the process. The target DeNB then instructs the source DeNB and the built-in source S-GW and the source P-GW to release the resources of the MRN.

Method 2:

The difference from the mode 1 is that the MRN does not indicate whether the measured cell is included in the gateway relocation cell list in the measurement report of step 402, and the X2 interface switching request message of step 403 does not carry the gateway relocation determination indication. Logo. After the MRN is detached from the source DeNB cell and establishes an RRC connection with the target DeNB cell, the RRC connection reconfiguration message sent indicates whether the target DeNB cell is included in the gateway relocation cell list.

Embodiment 2:

This embodiment describes a procedure for performing gateway relocation in the S1 handover process of the MRN under the method that the MRN obtains the gateway relocation cell list and indicates whether the measured cell is in the gateway relocation cell list in the measurement report. FIG. 5 illustrates the flow of the embodiment, in which the flow in the architecture shown in FIG. 1 is used, where the source SGW and the source PGW of the MRN may be built in the source DeNB or may not be built in the source DeNB, but built in the initial DeNB (initial DeNB). In this embodiment, the architecture shown in FIG. 3 can also be used, and the source S-GW and the P-GW of the MRN, the target S-GW and the P-GW are all located in the core network.

method one:

Step 501. The MRN obtains a list of gateway relocation cells. The MRN can obtain a list of gateway relocation cells in the following three ways:

1) by way of pre-configuration;

3) obtained from the OAM of the MRN;

The gateway relocation cell list includes identifier information of one or more cells, and the identifier information includes at least one of the following: a cell identifier, a physical cell identifier, and a base station identifier of the base station to which the cell belongs.

Step 502. The MRN measures that the one or more cells meet the trigger condition of the measurement report, and then sends the identifier and the measurement parameter of the cell that meet the condition to the source DeNB serving the same by using the measurement report. The MRN also indicates in the measurement report whether one or more of the cells are included in the gateway relocation list. The MRN may carry the identifier of the cell included in the gateway relocation list in the measurement report, or the indication information of the cell association in the measurement report indicating whether it is included in the gateway relocation list.

Step 503: After receiving the measurement report of the MRN, the source DeNB determines that there is no X2 interface between the source and the target DeNB, or needs to reselect an MME for the MRN, and then needs to perform an S1 handover for the source DeNB, and the source DeNB selects the MRN according to the measurement report. A target cell. The source DeNB sends an S1 interface handover request message to the source MME of the MRN. The handover request message includes a gateway relocation judgment indication identifier for indicating whether a gateway relocation is required. If the target cell is in the gateway relocation cell list, it indicates that gateway relocation is required; otherwise, it indicates that no gateway relocation is required.

Step 504: The source MME determines, according to the base station identifier or the target TAI of the target DeNB in the received handover request message, whether to select a new MME, and if necessary, selects the target MME according to the two parameters, and sends a forwarding relocation request to the source MME. The message carries information such as a source base station to a target base station transparent transmission container, a target base station identifier, a target location area identifier, and an MRN context information. And if the source MME of the MRN receives the gateway relocation determination indication identifier from the source DeNB, the forwarding relocation request message includes the received gateway relocation determination indication identifier.

Step 505: The target MME of the MRN determines whether to perform gateway relocation according to the received gateway relocation judgment indication identifier.

Step 506: The target MME of the MRN sends an S1 interface handover request message to the target DeNB. Preferably, if the MME of the MRN determines that the gateway relocation is to be performed, the S1 interface switching request message may include indication information for indicating that the gateway relocation is performed, and the indication information may be a gateway relocation determination indication identifier.

Step 507: After the target DeNB creates a context for the MRN and the UE and reserves resources for the bearer of the MRN, the target DeNB sends a handover request acknowledgement message to the target MME of the MRN. If the target DeNB receives the indication information for instructing to perform the gateway relocation, the message includes the IP addresses of the target S-GW and the target P-GW built in the target DeNB to assist the target MME to relocate the gateway of the MRN to A gateway built into the target DeNB.

Step 508: If the target MME of the MRN determines to perform the gateway relocation, the target MME of the MRN reselects the S-GW and the P-GW built in the target DeNB as the new gateway serving the MRN. The target MME of the MRN sends a create session request to the S-GW built in the target DeNB, including the EPS bearer information of the MRN to be created and the address of the target P-GW (P-GW built in the target DeNB).

Step 509. The target S-GW creates a context of the MRN, and sends a create session request message to the target P-GW.

Step 510. After the target P-GW creates the context and EPS bearer of the MRN, it replies to the target S-GW to create a session response message. The target S-GW and the P-GW are built in the DeNB, and the signaling in step 509 and step 510 are internal interface messages in the target DeNB.

Step 511: The target S-GW replies to the target MME of the MRN to create a session response message, to confirm that the context of the MRN and the establishment of the EPS bearer are completed.

Step 512: The target MME of the MRN sends a Forward Relocation Response message to the source MME. It should be noted that if it is not necessary to select a new MME, step 504 and step 512 are skipped, and the behaviors of the source MME and the target MME are the same MME behavior.

Step 513: The source MME of the MRN sends an S1 interface switching command message to the source DeNB. Step 514. The source DeNB sends an air interface message to the MRN, and the RRC message carries a handover command message sent by the target DeNB to the source DeNB through the MME of the MRN to instruct the MRN to perform handover.

Step 515. After receiving the handover command, the MRN detaches from the source DeNB cell and is small with the target. The area is synchronized, and the RACH process is initiated to access the target cell. After completing the RRC connection establishment with the target cell, the MRN sends an RRC connection reconfiguration complete message to the target DeNB.

Step 516. The target DeNB sends an S1 interface handover notification message to the target MME of the MRN. Then the target MME of the MRN completes the subsequent operations.

Then, the MRN or the target DeNB may initiate a path transfer request process for the UE served by the MRN to transfer the downlink S1 path of the UE. In the system architecture shown in FIG. 1, the SI user plane GTP-U tunnel mapping relationship of the new relay GW built in the target DeNB can also be established through the process. Then, the resource release process of the source DeNB and the built-in source S-GW and the source P-GW is performed.

Method 2:

The difference from the mode 1 is that the step 505 is performed before the step 508 after the step 507, and the S1 interface switching request message of the step 506 does not include the indication information for indicating whether to perform the gateway relocation. The handover request acknowledgement message of step 507 carries the IP addresses of the target S-GW and the target P-GW built in the target DeNB to assist the target MME to relocate the gateway of the MRN to the gateway built in the target DeNB.

Embodiment 3:

This embodiment describes a procedure for performing gateway relocation in the S1 handover process of the MRN under the method that the MRN obtains the gateway relocation cell list and indicates whether the target cell is in the gateway relocation cell list by using the RRC message. FIG. 6 illustrates the flow of the embodiment, in which the flow in the architecture shown in FIG. 1 is used, where the source SGW and the source PGW of the MRN may be built in the source DeNB or may not be built in the source DeNB, but built in the initial DeNB (initial DeNB). In this embodiment, the architecture shown in FIG. 3 can also be used, and the source S-GW and the P-GW of the MRN, the target S-GW and the P-GW are all located in the core network.

Step 601. The MRN obtains a list of gateway relocation cells.

The MRN can obtain a list of gateway relocation cells in the following three ways:

1) by way of pre-configuration;

2) obtained from the accessed donor base station (DeNB); the DeNB can be from the network management of the DeNB A list of gateway relocation cells is obtained at the OAM of the system.

3) obtained from the OAM of the MRN;

Step 602: The MRN measures that the one or more cells satisfy the trigger condition of the measurement report, and then sends the identifier and the measurement parameter of the cell that meet the condition to the source DeNB serving the same by using the measurement report.

Step 603: After receiving the measurement report of the MRN, the source DeNB determines that there is no X2 interface between the source and the target DeNB, or needs to reselect an MME for the MRN, and then needs to perform an S1 handover for the source DeNB, and the source DeNB selects a target for the MRN according to the measurement report. Community. The source DeNB sends an S1 interface switching request message to the source MME of the MRN.

Step 604: The source MME determines, according to the base station identifier or the target TAI of the target DeNB in the received handover request message, whether to select a new MME, and if necessary, selects the target MME according to the two parameters, and sends a forwarding relocation request to the source MME. The message carries information such as a source base station to a target base station transparent transmission container, a target base station identifier, a target location area identifier, and an MRN context information.

Step 605: The target MME of the MRN sends an S1 interface handover request message to the target DeNB. Step 606: After the target DeNB creates a context for the MRN and the UE and reserves resources for the bearer of the MRN, the target DeNB sends a handover request acknowledgement message to the target MME of the MRN. Optionally, the message includes an IP address of the target S-GW and the target P-GW built in the target DeNB, to assist the target MME to relocate the gateway of the MRN to the gateway built in the target DeNB.

Step 607: The target MME of the MRN sends a Forward Relocation Response message to the source MME. It should be noted that if it is not necessary to select a new MME, step 604 and step 607 are skipped, and the behaviors of the source MME and the target MME are the same MME behavior.

Step 608: The source MME of the MRN sends an S1 interface switching command message to the source DeNB.

Step 609. The source DeNB sends an air interface message to the MRN, and the RRC message carries the handover command message sent by the target DeNB to the source DeNB through the MME of the MRN to instruct the MRN to perform handover.

Step 610. After receiving the handover command, the MRN detaches from the source DeNB cell and is small with the target. The area is synchronized, and the RACH process is initiated to access the target cell. After completing the RRC connection establishment with the target cell, the MRN sends an RRC connection reconfiguration complete message to the target DeNB. The RRC Connection Reconfiguration Complete message includes indication information indicating whether the target cell is in the gateway relocation cell list.

Step 611. The target DeNB sends an S1 interface handover notification message to the target MME of the MRN. The S1 interface switching notification message includes a gateway relocation judgment indication identifier. If the target cell is in the gateway relocation cell list, the gateway relocation judgment indication flag needs to be relocated by the gateway. Optionally, the IP addresses of the target S-GW and the target P-GW built in the target DeNB may not be carried in the handover request acknowledgement, but are carried in the handover notification message to assist the target MME to relocate the gateway of the MRN to the target DeNB. Built in the gateway.

Step 612: The target MME of the MRN determines whether to perform gateway relocation according to the received gateway relocation judgment indication identifier.

Step 613: If the target MME of the MRN determines to perform the gateway relocation, the target MME of the MRN reselects the S-GW and the P-GW built in the target DeNB as the new gateway serving the MRN. The target MME of the MRN sends a create session request to the S-GW built in the target DeNB, including the EPS bearer information of the MRN to be created and the address of the target P-GW (P-GW built in the target DeNB).

Step 614. The target S-GW creates a context of the MRN and sends a Create Session Request message to the target P-GW. Step 615. After the target P-GW creates the context and the EPS bearer of the MRN, the target P-GW replies to the target S-GW to create a session response message. The target S-GW and the P-GW are built in the DeNB, and the signaling in step 614 and step 615 are internal interface messages in the target DeNB.

Step 616: The target S-GW replies to the target MME of the MRN to create a session response message, to confirm that the context of the MRN and the establishment of the EPS bearer are completed.

Thereafter, the MRN or the target DeNB may initiate a path transfer request procedure for the UE served by the MRN to transfer the downlink S1 path of the UE. In the system architecture shown in FIG. 1, the SI user plane GTP-U tunnel mapping relationship of the new relay GW built in the target DeNB can also be established through the process. Then, the resource release process of the source DeNB and the built-in source S-GW and the source P-GW is performed. Embodiment 4:

This embodiment describes a procedure for performing gateway relocation in the X2 handover process of the MRN, in which the gateway relocation cell list is saved as the context of the MRN in the MME. FIG. 7 is a flowchart of the embodiment, in which the flow in the architecture shown in FIG. 1 is used, where the source SGW and the source PGW of the MRN may be built in the source DeNB, or may not be built in the source DeNB, but built in the initial DeNB (initial DeNB). In this embodiment, the architecture shown in FIG. 3 can also be used, and the source S-GW and the P-GW of the MRN, the target S-GW and the P-GW are all located in the core network.

Step 701a. The MRN obtains a list of gateway relocation cells.

1) by way of pre-configuration;

3) obtained from the OAM of the MRN;

Step 701b. The MRN sends the list of gateway relocation cells to the MME serving it. The MRN may send the list of the relocation cell to the MME through the NAS message in the attaching process, or may send the RRC message to the DeNB through the RRC message, and then send the message to the MME through the S1 interface message.

Step 702. The gateway relocation cell list of the MRN is stored in the HSS as the subscription data of the MRN, and the MME may acquire the subscription data from the HSS in the attaching process, including the gateway relocation cell list.

701 701a and 701b or 702 can be used in either way.

The MRN's MME may also receive a list of gateway relocation cells from the last MME serving the MRN during the MRN handover, attach or tracking area update procedure.

Step 703. After obtaining the list of gateway relocation cells, the MME saves it in the context of the MRN.

Step 704: The MRN measures that the one or more cells satisfy the trigger condition of the measurement report, and then sends the identifier and the measurement parameter of the cell that meet the condition to the source DeNB serving the same by using the measurement report. Step 705: After receiving the measurement report of the MRN, the source DeNB determines that there is an X2 interface between the source and the target DeNB, and after the handover, the MRN does not need to replace the MME, and the source DeNB initiates an X2 handover for the MRN. The source DeNB selects a target cell for the MRN according to the measurement report, and then sends an X2 interface handover request message to the target DeNB.

Step 706. The target DeNB reserves resources for the MRN and creates context information according to the QoS and the like of the E-RAB to be established in the handover request message, and then returns a handover request acknowledgement message. The switch request acknowledgement message includes a transparent command message of the transparent air interface.

Step 707: The source DeNB sends an air interface message to the MRN, and the RRC message carries a transparent handover command message sent by the source DeNB to the MRN by the source DeNB to instruct the MRN to perform handover.

Step 708. The source DeNB sends an SN state transition message to the target DeNB for transmitting the RLC AM mode radio bearer uplink and downlink PDCP SN receiving and transmitting states.

Step 709. After receiving the handover command, the MRN detaches from the source DeNB cell, synchronizes with the target cell, and initiates a RACH process to access the target cell. After the MRN completes the RRC connection with the target cell, it sends an RRC Connection Reconfiguration Complete message to the target DeNB.

Step 710: After receiving the RRC reconfiguration complete message sent by the MRN, the target DeNB sends a path switch request message to the MME of the MRN to update the S1 user plane and the control plane path of the MRN. The path transfer request message further includes an address of the S-GW and the P-GW built in the target DeNB to assist the MME of the MRN to relocate the MRN's gateway to the gateway in the target DeNB.

Step 711: After receiving the path transfer request message, the MME of the MRN determines whether to perform gateway relocation according to the gateway relocation cell list in the context of the MRN. If the target cell is in the cell relocation cell list, it is determined that the gateway relocation needs to be performed, and the MME selects the S-GW and the P-GW in the target DeNB received in the path transfer request message as the new gateway serving the MRN.

Step 712. The MME of the MRN sends a Create Session Request message to the target SGW (S-GW built in the target DeNB), which includes the EPS bearer information of the MRN to be created and the address of the target PGW (PGW built in the target DeNB).

Step 713. The target SGW creates a context of the MRN and sends a create session to the target PGW. Request message.

Step 714. After the target PGW creates the context of the MRN and the EPS bearer, it returns a session response message to the target SGW. The target PGW can assign a new IP address to the MRN. The target S-GW and the P-GW are built in the DeNB, and the signaling in step 713 and step 714 are internal interface messages in the target DeNB.

Step 715: The target SGW replies to the MME of the MRN to create a session response message, to confirm that the context of the MRN and the establishment of the EPS 7 are completed.

Step 716: The MME of the MRN sends a path transfer request acknowledgement message to the target DeNB. Then, the MRN or the target DeNB may initiate a path transfer request process for the UE served by the MRN to transfer the downlink S1 path of the UE. In the system architecture shown in FIG. 1, the SI user plane GTP-U tunnel mapping relationship of the new relay GW built in the target DeNB can also be established through the process. The target DeNB then instructs the source DeNB and the built-in source S-GW and the source P-GW to release the resources of the MRN.

Embodiment 5:

In this embodiment, the gateway relocation cell list is stored in the MME as the context of the MRN, and the target MME of the MRN performs the process of determining the gateway relocation in the S1 handover process of the MRN. FIG. 8 is a flowchart of the embodiment, in which the flow in the architecture shown in FIG. 1 is used, where the source SGW and the source PGW of the MRN may be built in the source DeNB, or may not be built in the source DeNB, but built in the initial DeNB (initial DeNB). In this embodiment, the architecture shown in FIG. 3 can also be used, and the source S-GW and the P-GW of the MRN, the target S-GW and the P-GW are all located in the core network.

Step 801a. The MRN obtains a list of gateway relocation cells.

1) by way of pre-configuration;

3) obtained from the OAM of the MRN; The gateway relocation cell list includes identifier information of one or more cells, where the identifier information includes at least one of the following: a cell identifier, a physical cell identifier, and a base station identifier of the base station to which the cell belongs.

Step 801b. The MRN sends the list of gateway relocation cells to the MME serving it. The MRN may send the list of the relocation cell to the MME through the NAS message in the attaching process, or may send the RRC message to the DeNB through the RRC message, and then send the message to the MME through the S1 interface message.

Step 802. The gateway relocation cell list of the MRN is stored in the HSS as the subscription data of the MRN, and the MME may acquire the subscription data from the HSS in the attaching process, including the gateway relocation cell list.

801 801a and 801b or 802 can be used in either way.

Step 803. After obtaining the gateway relocation cell list, the MME saves it in the context of the MR.

Step 804. The MRN measures that the one or more cells satisfy the trigger condition of the measurement report, and then sends the identifier and the measurement parameter of the cell that meet the condition to the source DeNB serving the same through the measurement report.

Step 805: After receiving the measurement report of the MRN, the source DeNB determines that there is no X2 interface between the source and the target DeNB, or needs to reselect an MME for the MRN, and then needs to perform an S1 handover for the source DeNB, and the source DeNB selects a target for the MRN according to the measurement report. Community. The source DeNB sends an S1 interface switching request message to the source MME of the MRN.

Step 806: The source MME determines, according to the base station identifier or the target TAI of the target DeNB in the received handover request message, whether to select a new MME, and if necessary, selects the target MME according to the two parameters, and sends a forwarding relocation request to the source MME. The message carries information such as a source base station to a target base station transparent transmission container, a target base station identifier, a target location area identifier, and an MRN context information.

Step 807: The target MME of the MRN determines whether to perform gateway relocation according to the gateway relocation cell list in the context of the MRN. If the target cell is in the gateway relocation cell list, it is determined that gateway relocation is required.

Step 808: The target MME of the MRN sends an S1 interface handover request message to the target DeNB. Preferably, if the MME of the MRN determines to perform gateway relocation, the S1 interface switching request message The indication information for indicating that the gateway relocation is performed may be included, and the indication information may be a gateway relocation determination indication identifier.

Step 809: After the target DeNB creates a context for the MRN and the UE and reserves resources for the bearer of the MRN, the target DeNB sends a handover request acknowledgement message to the target MME of the MRN. If the target DeNB receives the indication information for instructing to perform the gateway relocation, the message includes the IP addresses of the target S-GW and the target P-GW built in the target DeNB to assist the target MME to relocate the gateway of the MRN to A gateway built into the target DeNB.

Step 810: If the target MME of the MRN determines that the gateway relocation is to be performed, the target MME of the MRN reselects the S-GW and the P-GW built in the target DeNB as the new gateway serving the MRN. The target MME of the MRN sends a create session request to the S-GW built in the target DeNB, including the EPS bearer information of the MRN to be created and the address of the target P-GW (P-GW built in the target DeNB).

Step 811. The target S-GW creates a context of the MRN and sends a Create Session Request message to the target P-GW. Step 812. After the target P-GW creates the context and EPS bearer of the MRN, it replies to the target S-GW to create a session response message. The target S-GW and the P-GW are built in the DeNB, and the signaling in step 509 and step 510 are internal interface messages in the target DeNB.

Step 813: The target S-GW replies to the target MME of the MRN to create a session response message, to confirm that the context of the MRN and the establishment of the EPS bearer are completed.

Step 814: The target MME of the MRN sends a Forward Relocation Response message to the source MME. It should be noted that if there is no need to select a new MME, then step 806 and step 814 are skipped, and the behavior of both the source MME and the target MME are the same MME behavior.

Step 815: The source MME of the MRN sends an S1 interface handover command message to the source DeNB. Step 816. The source DeNB sends an air interface message to the MRN. The RRC message carries the handover command message sent by the target DeNB to the source DeNB through the MME of the MRN to instruct the MRN to perform handover.

Step 817: After receiving the handover command, the MRN detaches from the source DeNB cell, synchronizes with the target cell, and initiates a RACH process to access the target cell. MRN completes RRC connection with the target cell After the establishment, the RRC connection reconfiguration complete message is sent to the target DeNB.

Step 818. The target DeNB sends an S1 interface handover notification message to the target MME of the MRN. Then the target MME of the MRN completes the subsequent operations.

Method 2:

The difference from the first method is that the step 807 is performed before the step 810 after the step 809, and the S1 interface switching request message of the step 808 does not include the indication information for indicating whether to perform the gateway relocation. The handover request acknowledgement message of step 809 carries the IP addresses of the target S-GW and the target P-GW built in the target DeNB to assist the target MME to relocate the gateway of the MRN to the gateway built in the target DeNB.

Example 6:

In this embodiment, the gateway relocation cell list is stored in the MME as the context of the MRN. In the S1 handover process of the MRN, the source MME of the MRN performs the gateway relocation determination to indicate the flow of the target MME of the MRN. FIG. 9 illustrates the flow of the embodiment, in which the flow under the architecture shown in FIG. 1 is used, where the source SGW and the source PGW of the MRN may be built in the source DeNB or may not be built in the source DeNB, but built in the initial DeNB (initial DeNB). In this embodiment, the architecture shown in FIG. 3 can also be used, and the source S-GW and the P-GW of the MRN, the target S-GW and the P-GW are all located in the core network.

Step 901a. The MRN obtains a list of gateway relocation cells.

1) by way of pre-configuration;

Step 901b. The MRN sends the list of gateway relocation cells to the MME serving it. The MRN may send the list of the relocation cell to the MME through the NAS message in the attaching process, or may send the RRC message to the DeNB through the RRC message, and then send the message to the MME through the S1 interface message.

Step 902. The gateway relocation cell list of the MRN is stored in the HSS as the subscription data of the MRN, and the MME may acquire the subscription data from the HSS in the attaching process, including the gateway relocation cell list.

901 901a and 901b or 902 can be used, and the two methods can be used.

Step 903. After obtaining the list of gateway relocation cells, the MME saves it in the context of the MR.

Step 904. The MRN measures that the one or more cells satisfy the trigger condition of the measurement report, and then sends the identifier and the measurement parameter of the cell that meet the condition to the source DeNB serving the same through the measurement report.

Step 905: After receiving the measurement report of the MRN, the source DeNB determines that there is no X2 interface between the source and the target DeNB, or needs to reselect an MME for the MRN, and then needs to perform an S1 handover for the source DeNB, and the source DeNB selects a target for the MRN according to the measurement report. Community. The source DeNB sends an S1 interface switching request message to the source MME of the MRN.

Step 906. The source MME of the MRN determines whether to perform gateway relocation according to the gateway relocation cell list in the context of the MRN. If the target cell is in the gateway relocation cell list, it is determined that gateway relocation is required.

Step 907. The source MME determines whether to select a new MME according to the base station identifier or the target TAI of the target DeNB in the received handover request message, selects the target MME according to the two parameters, and sends a forwarding relocation request to the source MME if necessary. The message carries information such as a source base station to a target base station transparent transmission container, a target base station identifier, a target location area identifier, and an MRN context information. The context information of the MRN includes a list of gateway relocation cells. The message further includes a gateway relocation judgment indication identifier. If the source MME determines that the gateway relocation needs to be performed, the gateway relocation judgment indication identifier indicates that the gateway relocation is performed. Step 908: The target MME of the MRN determines whether to perform gateway relocation according to the gateway relocation judgment indication identifier. If the gateway relocation judgment indication flag indicates that the gateway relocation is performed, it is determined to perform the gateway relocation.

Step 909: The target MME of the MRN sends an S1 interface handover request message to the target DeNB. Preferably, if the target MME of the MRN determines that the gateway relocation is to be performed, the S1 interface handover request message may include indication information for indicating that the gateway relocation is performed, and the indication information may be a gateway relocation determination indication identifier.

Step 910: After the target DeNB creates a context for the MRN and the UE and reserves resources for the bearer of the MRN, the target DeNB sends a handover request acknowledgement message to the target MME of the MRN. If the target DeNB receives the indication information for instructing to perform the gateway relocation, the message includes the IP addresses of the target S-GW and the target P-GW built in the target DeNB to assist the target MME to relocate the gateway of the MRN to A gateway built into the target DeNB.

Step 911: If the target MME of the MRN determines to perform the gateway relocation, the target MME of the MRN reselects the S-GW and the P-GW built in the target DeNB as the new gateway serving the MRN. The target MME of the MRN sends a create session request to the S-GW built in the target DeNB, including the EPS bearer information of the MRN to be created and the address of the target P-GW (P-GW built in the target DeNB).

Step 912. The target S-GW creates a context of the MRN, and sends a create session request message to the target P-GW. Step 913. After the target P-GW creates the context of the MRN and the EPS bearer, it replies to the target S-GW to create a session response message. The target S-GW and the P-GW are built in the DeNB, and the signaling in step 912 and step 913 are internal interface messages in the target DeNB.

Step 914: The target S-GW replies to the target MME of the MRN to create a session response message, to confirm that the context of the MRN and the establishment of the EPS bearer are completed.

Step 915: The target MME of the MRN sends a Forward Relocation Response message to the source MME. It should be noted that if it is not necessary to select a new MME, step 907 and step 915 are skipped, and the behaviors of the source MME and the target MME are the same MME behavior.

Step 916: The source MME of the MRN sends an S1 interface switching command message to the source DeNB. Step 917. The source DeNB sends an air interface message RRC connection reconfiguration message to the MRN, where the RRC message carries the handover command message sent by the target DeNB to the transparent container of the source DeNB through the MME of the MRN, to instruct the MRN to perform handover.

Step 918. After receiving the handover command, the MRN detaches from the source DeNB cell, synchronizes with the target cell, and initiates a RACH process to access the target cell. After the MRN completes the RRC connection with the target cell, it sends an RRC Connection Reconfiguration Complete message to the target DeNB.

Step 919. The target DeNB sends an S1 interface handover notification message to the target MME of the MRN. Then the target MME of the MRN completes the subsequent operations.

Method 2:

The difference from the first method is that the step 908 is performed before the step 911 after the step 910, and the S1 interface switching request message of the step 909 does not include the indication information for indicating whether to perform the gateway relocation. The handover request acknowledgement message of step 910 carries the IP addresses of the target S-GW and the target P-GW built in the target DeNB to assist the target MME to relocate the gateway of the MRN to the gateway built in the target DeNB.

As shown in FIG. 10, the embodiment further provides a mobility management entity, including: a receiving unit and a determining unit, where: a receiving unit, configured to receive gateway relocation determining information in a process of switching a DeNB for an MRN;

The determining unit is configured to determine, according to the gateway relocation judgment information, whether the gateway is the gateway of the MRN relocation service after receiving the gateway relocation judgment information.

The gateway relocation judgment information includes a gateway relocation judgment indication identifier, and the gateway relocation judgment indication identifier indicates whether the gateway is an MRN relocation service.

The receiving unit is specifically configured to receive a gateway relocation determination indicator from the target DeNB of the MRN. The gateway relocation judgment indication identifier is sent by the source DeNB of the MRN according to whether the measured cell reported by the MRN is included in the gateway relocation cell list, and whether the target cell of the MRN is included in the gateway relocation cell list, and then sent To the receiving unit, when the target cell of the MRN is included in the gateway relocation cell list, the gateway relocation determination indication flag indicates that the MRN relocation service is a gateway.

The receiving unit is configured to receive a gateway relocation determination indication identifier from the target DeNB of the MRN, where the gateway relocation determination indication identifier is determined by the target DeNB according to whether the target cell of the MRN reported by the MRN is included in the gateway relocation cell list. After the relocation judgment indication flag indicates that the gateway is the MRN relocation service, and sends the signal to the receiving unit, when the target cell of the MRN is included in the gateway relocation cell list, the gateway relocation judgment indication flag indicates the gateway of the MRN relocation service. .

The receiving unit is configured to receive, by the source DeNB of the MRN, a gateway relocation determination indication identifier, where the gateway relocation determination indication identifier is determined by the source DeNB of the MRN according to the measured cell reported by the MRN, whether the cell is included in the gateway relocation cell list, After determining whether the target cell of the MRN is included in the gateway relocation cell list, the method is sent to the MME. When the target cell of the MRN is included in the gateway relocation cell list, the gateway relocation judgment indication flag indicates that the MRN relocation service is a gateway.

The gateway relocation judgment information includes a gateway relocation cell list, and the identifier of the cell of the gateway that needs to be the MRN relocation service when the target cell of the MRN is recorded in the gateway relocation cell list.

The receiving unit is specifically configured to receive, by the MRN, the HSS, or the MME that served the MRN last time, the gateway relocation cell list, and save the gateway relocation cell list in the context of the MRN.

The determining unit is specifically configured to: after receiving the path transfer request of the target DeNB, determine whether the target cell of the MRN is included in the gateway relocation cell list in the context of the MRN, and if yes, determine the gateway of the MRN relocation service.

The determining unit is specifically configured to: after receiving the handover request message, determine whether the target cell of the MRN is included in the gateway relocation cell list in the context of the MRN, and if yes, determine the gateway of the MRN relocation service. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection of the present invention. Within the scope.

Industrial applicability

The embodiment of the present invention can solve the problem of determining whether to perform gateway relocation in the MRN handover process, so that the route optimization is smoothly performed, thereby shortening the delay of the UE data and signaling.

Claims

Claim

1. A method for relocation of a gateway, comprising:

In the process of switching the donor base station (DeNB) for the mobile relay node (MRN), the mobility management entity (MME) of the MRN receives the gateway relocation judgment information, and after receiving the gateway relocation judgment information, according to the gateway weight The location determination information determines whether it is a gateway of the MRN relocation service.

2. The method according to claim 1, wherein the gateway relocation determination information includes a gateway relocation determination indication identifier, and the gateway relocation determination indication identifier indicates whether the gateway is the MRN relocation service.

The method of claim 2, wherein the MME of the MRN receives the gateway relocation determination information, including:

The MME of the MRN receives the gateway relocation determination indication identifier from the target DeNB of the MRN, where the gateway relocation determination indication identifier is determined by the source DeNB of the MRN according to whether the measured cell reported by the MRN is included in the gateway relocation cell list. After the target cell of the MRN is included in the gateway relocation cell list, the target cell is sent to the target DeNB. When the target cell of the MRN is included in the gateway relocation cell list, the gateway relocation judgment indication flag indicates that the MRN relocation is performed. The gateway of the service.

The MME of the MRN receives the gateway relocation determination indication identifier from the target DeNB of the MRN, where the gateway relocation determination indication identifier is determined by the target DeNB according to whether the target cell of the MRN on the MRN is included in the gateway relocation cell list. After determining that the gateway relocation determination indication flag indicates that the gateway is the MRN relocation service, the MME is sent to the MME, and when the target cell of the MRN is included in the gateway relocation cell list, the gateway relocation determination indication indicator is The gateway of the MRN relocation service.

The MME of the MRN receives the gateway relocation determination indication identifier from the source DeNB of the MRN, where the gateway relocation determination indication identifier is measured by the source DeNB of the MRN according to the MRN. If the target cell of the MRN is included in the list of gateway relocation cells, and is determined to be included in the list of gateway relocation cells, the target cell of the MRN is sent to the MME, and when the target cell of the MRN is included in the list of gateway relocation cells, The gateway relocation judgment indication identifier indicates a gateway serving the MRN relocation service.

6. The method of claim 5, wherein

When the MME needs to reselect the MME, the MME of the MRN includes the source MME of the MRN and the target MME of the MRN, and the source MME receives the gateway relocation determination indication identifier from the source DeNB, and sends a gateway relocation to the target MME. Determining an indication identifier, indicating whether the target MME is a gateway of the MRN relocation service.

7. The method of claim 4, wherein

When the MME needs to be reselected for the MRN, the MME of the MRN includes the source MME of the MRN and the target MME of the MRN, and the target MME receives the gateway relocation determination indication identifier from the target DeNB.

The method according to claim 3 or 5, wherein the MRN reports whether the measured cell is included in the gateway relocation cell list by using the measurement report.

The method according to claim 4, wherein the MRN reports whether the target cell of the MRN is included in the gateway relocation cell list by using a radio resource control (RRC) connection reconfiguration message.

The method of claim 1, wherein the gateway relocation determination information includes a gateway relocation cell list, and the gateway retargeting cell list needs to be a gateway for MRN relocation service when the target cell of the MRN is recorded. The identity of the cell.

The method of claim 10, wherein the MME of the MRN receives the gateway relocation determination information, including:

The MME of the MRN receives a list of gateway relocation cells from the MRN, the home subscriber server (HSS), or the MME that served the MRN last time, and stores the list of gateway relocation cells in the context of the MRN.

The method of claim 11, wherein determining, according to the received gateway relocation judgment information, whether the gateway is the MRN relocation service, includes: After receiving the path transfer request of the target DeNB, the MME of the MRN determines whether the target cell of the MRN is included in the gateway relocation cell list in the context of the MRN, and if yes, determines the gateway of the MRN relocation service. .

13. The method of claim 11 wherein

After receiving the handover request message, the MME of the MRN determines whether the target cell of the MRN is included in the gateway relocation cell list in the context of the MRN, and if so, determines the gateway of the MRN relocation service.

14. The method of claim 11 wherein

When the MME needs to reselect the MME, the MME of the MRN includes the source MME of the MRN and the target MME of the MRN, and the source MME receives the gateway relocation cell list from the MRN, the HSS, or the MME that served the MRN last time. And saving the list of gateway relocation cells in the context of the MRN.

The method of claim 14, wherein determining, according to the received gateway relocation determination information, is a gateway of the MRN relocation service, including:

The method of claim 14, wherein determining, according to the received gateway relocation judgment information, is a gateway of the MRN relocation service, including:

The method according to claim 1, wherein the MME of the MRN determines, when the gateway relocation determination information is not received, the gateway that does not serve the MRN relocation.

18. The method of claim 1, further comprising:

The MME of the MRN performs re-determination after determining that the MRN relocates the gateway of the service. a gateway of the bit service, the gateway of the relocation service includes a packet data network gateway (P-GW) and a serving gateway (S-GW) serving the MRN relocation; or the gateway of the relocation service is included The P-GW, the S-GW, and the relay GW of the MRN relocation service.

19. The method of claim 1, further comprising:

20. The method of claim 19, wherein

The MME of the MRN reselects the gateway serving as the MRN according to the received address of the gateway sent by the target DeNB of the MRN.

21. The method of claim 11 wherein

The MME of the MRN relocates the cell list from the MRN or HSS receiving gateway in the attaching process of the MRN; or

22. The method of claim 10, wherein

The identifier of the cell that needs to be the gateway of the MRN relocation service, which is recorded in the cell re-locating cell list, includes at least one of the following: a cell identifier, a physical cell identifier, and a base station identifier of the base station to which the cell belongs.

A mobility management entity, comprising: a receiving unit and a determining unit, wherein: the receiving unit is configured to: receive a gateway relocation in a process of switching a donor base station (DeNB) for a mobile relay node (MRN) Judging information;

The determining unit is configured to: after the receiving unit receives the gateway relocation determining information, determine, according to the gateway relocation determining information, whether the gateway is the MRN relocation service.

The mobility management entity according to claim 23, wherein the gateway relocation determination information includes a gateway relocation determination indication identifier, and the gateway relocation determination indication identifier indicates whether the gateway is the MRN relocation service. .

25. The mobility management entity of claim 24, wherein

The receiving unit is configured to: receive a gateway relocation determination indication identifier from the target DeNB of the MRN, where the gateway relocation determination indication identifier is determined by the source DeNB of the MRN according to whether the measured cell reported by the MRN is included in the gateway relocation cell list. And determining, after the target cell of the MRN is included in the gateway relocation cell list, sending the signal to the receiving unit, where the target cell of the MRN is included in the gateway relocation cell list, the gateway relocation determination indication identifier indication is The gateway of the MRN relocation service.

26. The mobility management entity of claim 24, wherein

The receiving unit is configured to: receive a gateway relocation determination indication identifier from the target DeNB of the MRN, where the gateway relocation determination indication identifier is determined by the target DeNB according to whether the target cell of the MRN reported by the MRN is included in the gateway relocation cell Determining, in the list, that the gateway relocation judgment indication identifier indicates that the gateway is the gateway of the MRN relocation service, and sends the signal to the receiving unit. When the target cell of the MRN is included in the gateway relocation cell list, the gateway relocation judgment indication identifier Indicates the gateway serving the MRN relocation service.

27. The mobility management entity of claim 24, wherein

The receiving unit is configured to: receive a gateway relocation judgment indication identifier from the source DeNB of the MRN, where the gateway relocation judgment indication identifier is determined by the source DeNB of the MRN according to whether the measured cell reported by the MRN is included in the gateway relocation cell list. After determining whether the target cell of the MRN is included in the gateway relocation cell list, the MME is sent to the MME, and when the target cell of the MRN is included in the gateway relocation cell list, the gateway relocation determination indication identifier is indicated as the MRN. The gateway for the relocation service.

The mobility management entity according to claim 23, wherein the gateway relocation determination information includes a gateway relocation cell list, and the MRN relocation is required when the target relocation cell list is recorded as a target cell of the MRN. The identity of the cell of the gateway of the month.

29. The mobility management entity of claim 28, wherein

The receiving unit is configured to: receive a gateway relocation cell list from the MRN, a home subscriber server (HSS), or an MME served last time for the MRN, and save the gateway relocation d, the zone list in the MRN In the context.

30. The mobility management entity of claim 29, wherein

The determining unit is configured to: after receiving the path transfer request of the target DeNB, determine whether the target cell of the MRN is included in the gateway relocation cell list in the context of the MRN, and if yes, determine that the MRN is relocated The gateway of the service.

31. The mobility management entity of claim 29, wherein

The determining unit is configured to: after receiving the handover request message, determine whether the target cell of the MRN is included in the gateway relocation cell list in the context of the MRN, and if yes, determine the gateway that is the MRN relocation service .