WO2011020239A1 - Switch processing method, method and device for relocating terminal path - Google Patents

Abstract

A switch processing method and a base station are disclosed. Said method includes: after a mobile node switches to a target base station, the gateway of said mobile node is relocated to said target base station (S31); the target base station provides the gateway function for said mobile node (S32). The above technical solution enables the gateway of the mobile node to be relocated to said target base station and enables the target base station to perform the gateway function, thus benefiting the communication between mobile node and target base station.

Description

 Switching processing method and terminal path changing method and device

 The present invention relates to the field of communications technologies, and in particular, to a handover processing method and a terminal path change method and device.

Background technique

 1 is a schematic diagram of a radio access network, which includes a donor base station (DeNB, Donor eNodeB), a relay node (RN, Relay Node), and three user equipments (UEs) subordinate to the relay node. , User Equipment ). Each of the user equipments is also a terminal, and the three terminals are labeled as UE1, UE2, and UE3, and the interface between the RN and the RN is an Uu interface; the interface between the RN and the DeNB is an Un port. In addition, the interface between the DeNBs is referred to as an X2 interface; the interface between the DeNB and the Mobility Management Entity (MME) or the gateway (GW, Gateway) is an SI interface. With the continuous development of Long Term Evolution (LTE) technology, the functions of base stations are becoming more and more abundant, enabling some base stations to implement the functions of the gateway. For example, a base station may implement the function of the relay gateway, that is, the base station may include some or all functions of an SGW (Serving Gateway) and a PGW (Packet Data Network Gateway) of the RN, or may only include the RN. Part or all of the functionality of the PGW.

In the LTE-A (LTE-Advance, LTE Evolution) system, when a relay node has mobility, the relay node becomes a mobile relay node (MRN, Mobile RN) „ in a system including an MRN, when When the MRN moves, the MRN may need to switch from one DeNB to another as the UE, that is, the MRN is switched. The DeNB that provides the MRN service before the handover is called the source base station, and the DeNB that needs to be handed over is called the target. There are at least the following drawbacks in the prior art: When a base station integrates the relay gateway function, if the MRN switches from the source base station to the target base station, the relay gateway will be at the source base station, and the MRN communicates with the target base station, causing delay. Increase the problem. The same problem may also occur on the UE, for example in the UE The local routing gateway is integrated in the scenario of the local radio access network node (for example, the base station). When the UE switches from the source base station to the target base station, if the local routing gateway function execution point of the UE is still at the source base station, the source base station communication is caused. The delay increases, and even when it is severe, data is blocked.

Summary of the invention

 The embodiment of the invention provides a handover processing method and a terminal path modification method and device, which implements a relay gateway change after the mobile node switches to the target base station, which is beneficial to communication between the mobile node and the target base station; and can facilitate the modification of the terminal path. . The embodiment of the invention provides a handover processing method, including:

 After the mobile node switches to the target base station, the gateway of the mobile node is changed to the target base station;

 The target base station provides a gateway function for the mobile node.

 The embodiment of the invention further provides a base station, including:

 a change module, configured to: after the mobile node switches to the base station, change the gateway of the mobile node to the base station;

 a gateway module, configured to provide a gateway function for the mobile node.

 The embodiment of the invention further provides a method for changing a terminal path, including:

 Receiving a path switch request message, where the path switch request message includes information of at least two terminals, where the at least two terminals belong to a terminal mobility management entity, and the path switch request message is used to request that the terminal move management entity The terminal path is switched to the target base station;

 Switching the terminal path of the terminal mobility management entity to the target base station. The embodiment of the invention further provides a terminal mobility management entity, including:

a second receiving module, configured to receive a path switching request message, where the path switching request message includes information of at least two terminals, where the at least two terminals belong to a terminal mobility management entity, and the path switching request message is used to request The terminal path of the terminal mobility management entity is switched to the target base station; And a first change module, configured to switch a terminal path of the mobility management entity to the target base station.

 The embodiment of the invention further provides a method for changing a terminal path, including:

 Receiving a modify bearer request message, where the modify bearer request message includes information of at least two terminals, the at least two terminals belong to one gateway, and the modify bearer request message is used to notify that the user plane connection is switched to the target base station;

 Switch the user plane connection to the target base station.

 The embodiment of the invention further provides a gateway, including:

 a third receiving module, configured to receive a modify bearer request message, where the modify bearer request message includes information of at least two terminals, where the at least two terminals belong to the gateway, and the modify bearer request message is used to notify the user The face connection is switched to the target base station;

 The second change module is configured to switch the user plane connection to the target base station.

 It can be seen from the foregoing solution that the embodiment of the present invention can change the gateway of the mobile node to the target base station, so that the target base station can provide a gateway function for the mobile node, which is beneficial to communication between the mobile node and the target base station. The above technical solution can also implement path change to multiple terminals through one message.

DRAWINGS

 Figure 1 is a schematic diagram of a radio access network

 2 is a schematic diagram of a handover processing method according to Embodiment 1 of the present invention;

 3 is a flowchart of a handover processing method according to Embodiment 3 of the present invention;

 4 is a schematic diagram of a method for allocating an IP address of an MRN according to Embodiment 4 of the present invention; FIG. 5 is a flowchart of a handover processing method according to Embodiment 5 of the present invention;

 6 is a schematic diagram of a handover processing method according to Embodiment 6 of the present invention;

 7 is a schematic diagram of a handover processing method according to Embodiment 7 of the present invention;

 8 is a schematic diagram of a handover processing method according to Embodiment 8 of the present invention;

FIG. 9 is a schematic diagram of a handover processing method according to Embodiment 9 of the present invention; FIG. 10 is a schematic diagram of a handover processing method according to Embodiment 10 of the present invention; FIG. 11 is a schematic diagram of a handover processing method according to Embodiment 11 of the present invention;

 FIG. 12 is a schematic diagram of a handover processing method according to Embodiment 12 of the present invention; FIG.

 FIG. 13 is a schematic diagram of a method for changing a terminal path according to Embodiment 13 of the present invention; FIG. 14 is a schematic diagram of a method for changing a terminal path according to Embodiment 14 of the present invention; FIG. 16 is a schematic diagram of a handover processing method according to Embodiment 16 of the present invention; FIG.

 17 is a schematic diagram of a base station according to Embodiment 17 of the present invention;

 18 is a schematic diagram of a base station according to Embodiment 18 of the present invention;

 FIG. 19 is a schematic diagram of a base station according to Embodiment 19 of the present invention; FIG.

 FIG. 20 is a schematic diagram of a terminal MME according to Embodiment 20 of the present invention; FIG.

 FIG. 21 is a schematic diagram of a terminal gateway according to Embodiment 21 of the present invention; FIG.

 FIG. 22 is a schematic diagram of a handover processing method according to Embodiment 22 of the present invention; FIG. 23 is a schematic diagram of a handover processing method according to Embodiment 23 of the present invention.

detailed description

 Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that the following embodiments are only a part of the embodiments of the present invention, and not all of them. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The embodiments of the present invention may relate to information interaction between multiple communication entities, and the definitions of each communication entity are briefly described. The UE is a user equipment, that is, a terminal; the eNB is a base station; the MRN is a mobile relay node; it can implement handover between different base stations like a terminal; the relay node may be referred to as a relay hereinafter; the source base station is an MRN switch The MRN serving base station; the target base station is the MRN serving base station after the MRN handover; the relay MME is the mobility management entity of the MRN; the terminal MME is the mobile management entity of the terminal; the terminal gateway is a gateway serving the terminal, and includes the terminal SGW And the PGW function; the relay gateway is the gateway that provides the MRN service; the relay network gateway is the PGW of the MRN, and the relay service gateway is the SGW of the MRN. The UE and the MRN in this embodiment may be collectively referred to as mobile nodes, and they are capable of switching between different base stations as mobile nodes. In the embodiment of the present invention, some or all functions of the MRN relay gateway may be combined in the base station, that is, the function of the relay gateway serving the MRN may be implemented by the base station in whole or in part. The target base station can aggregate the relay gateway function or perform the relay gateway function. The target base station can implement the PGW function of the MRN, or the SGW function, or other gateway functions (such as the home e B gateway), or simultaneously implement the foregoing multiple gateways. Features. In one case, the base station may implement all or part of the functions of the SGW and the PGW of the MRN; in another case, the base station may also implement only all or part of the functions of the PGW of the MRN. When the base station can implement all or part of the functions of the SGW and the PGW of the MRN, the base station is also the SGW and the PGW of the MRN. When the base station can implement all or part of the functions of the PGW of the MRN, the base station is also the PGW of the MRN; at this time, the SGW of the MRN is an independent entity, is not included in the base station, or the SGW of the MRN does not exist. Further, the base station may also include a home eNB (HeNB) gateway function or a function similar to a home eNB (HeNB) gateway. For example, the base station performs the function of the HeNB gateway between the relayable node and the core network (EPC-Evolved Packet Core network). For example, the MME may transmit an S1-AP message to the base station, and after receiving the S1-AP message, the base station modifies the Sl-AP TEIDs at the interface connecting the MME and the interface connecting the relay node, and the other parts remain unchanged. This process corresponds to the S1-AP mechanism and is similar to the HeNB gateway function. The MME appears to be connected to the base station; the relay node appears to be connected to the MME.

 2 is a schematic diagram of a handover processing method according to Embodiment 1 of the present invention. The method includes: S21: After a mobile relay node switches to a target base station, the target base station changes a gateway of the mobile relay node to the a target base station, where the target base station can implement a relay gateway function;

 S22: The target base station provides a gateway function for the mobile relay node.

The method embodiment changes a gateway of the mobile relay node to the target base station, and causes the The target base station provides a gateway function for the mobile relay node, so that the gateway of the MRN switches to the target base station, which facilitates communication between the MRN and the target base station. Changing the gateway of the mobile relay node to the target base station means transferring the original gateway (source base station) function of the mobile relay node to the destination gateway (the gateway function entity in the target base station). In practical applications, the functions of some gateways in the source base station may be transferred to the target base station, or all gateway functions of the source base station may be changed to the target base station. Changing the gateway of the mobile relay node to the target base station includes: setting a gateway destination address of the mobile relay node as an address or identifier of the target base station.

 The method can further include: assigning an IP address to the mobile relay node and providing the IP address to the mobile relay node. It can be understood that the assigned IP address can be the same as or different from the original IP address of the mobile relay node.

 Further, the method includes: receiving gateway information of an MRN provided by a source base station. The target base station provides the gateway function for the mobile relay node, including: the target base station provides the gateway function for the MRN by using the gateway information of the MRN. The gateway information of the MRN is: Information required to provide the gateway function for the MRN.

Further, the method further includes: notifying the relay MME of the MRN to switch the gateway path to the target base station. In this step, the mobility management entity of the mobile node may be notified to change the path between the mobility management entity of the mobile node and the mobile node gateway to the path between the mobility management entity of the mobile node and the new gateway of the mobile node. And notifying the mobility management entity of the mobile node to change a path between the mobile management entity of the mobile node and the source base station to a path between the mobility management entity of the mobile node and the target base station. Specifically, the relay MME may be notified of the change of the relay gateway and the changed serving base station, so that the path between the relay MME and the source relay gateway (within the source base station entity) is changed to the relay MME and the new relay gateway. The path between the (the gateway in the target base station entity), the path between the relay MME and the source base station is changed to the path between the relay MME target base stations. Thereby establishing a control plane connection between the relay MME and the relay serving base station (target base station), and establishing a connection between the relay MME and the relay gateway, and then the MME can be connected to the target base station integrated with the relay gateway function. Information interaction now.

 The target base station can implement the relay gateway function. The target base station can implement the PGW function of the MRN, or the SGW function, or other gateway function, or simultaneously implement the foregoing multiple gateway functions.

 Changing the gateway of the mobile relay node to the target base station means transferring the gateway function of the source base station to the target base station. It can be understood that when a plurality of gateway functions, such as PGW, SGW, HeNB gateway or other gateway functions, are collected in the base station, the source base station can only transfer part of the gateway functions of the plurality of gateway functions to the target base station.

 In one application, the changing the gateway of the mobile relay node to the target base station comprises: changing a relay network gateway and a relay service gateway of the mobile relay node to the target base station. When all and part of the functions of the relay network gateway and the relay service gateway are integrated in the target base station, the relay network gateway and the relay service gateway address can be changed to the target base station.

 In another application, the changing the gateway of the mobile relay node to the target base station comprises: changing a relay network gateway of the mobile relay node to the target base station. Further, the method may further include: notifying the relay service gateway of the mobile relay node that the gateway of the mobile relay node has been changed, so that the relay service gateway switches its gateway path to the target base station. When the target base station integrates all or part of the functions of the relay network gateway, or integrates the relay network gateway and other gateway functions (such as home e B GW), the relay network gateway address and/or other gateways in the base station may be The address is directly notified to the serving gateway (that is, the gateway entity in the base station). The other way is to notify the relay MME first, and then notify the serving gateway by the relay MME to make the path change, which is convenient for implementation. Following the communication and data interaction between the serving gateway and the target base station and the gateway entity within the base station entity.

The second embodiment of the present invention provides a handover processing method, which is applied to the following scenario: The MRN switches to the target base station, and the target base station changes the gateway of the MRN to the target base station. The method includes: providing, to the target base station, gateway information of the MRN, to indicate that the target base station changes the relay gateway to the target base station after learning that the MRN switches to the target base station, where the target base station can implement relaying Gateway function.

In this embodiment, the source base station may provide the target base station with information required by the target base station as the MRN relay gateway, so that the target base station can perform gateway change. The source base station can implement the relay gateway function. The source base station can implement the PGW function of the MRN, or the SGW function, or other gateway function, or simultaneously implement the foregoing multiple gateway functions. The gateway information of the MRN is: Information required to provide the gateway function for the MRN. When the source base station includes the relay gateway function of the MRN, it includes information required for providing the MRN with the gateway function, if the MRN is to be handed over from the source base station to the target base station or the MRN is handing over from the source base station to the target base station or the MRN has been from the source base station Switching to the target base station, the source base station may associate the gateway information of the MRN or all the gateway function information included in the source base station (such as the PGW function of the MRN, or the SGW function, or other gateway function, or simultaneously implement the foregoing various gateway functions) The information is provided to the target base station so that the target base station can make a change of the relay gateway. The target base station needs to perform a change of the relay gateway to provide a gateway function for the MRN. Specifically, after the gateway information provided by the source base station, the gateway address is changed, that is, the gateway function of the MRN in the source base station or the source base station is included. The transfer of all gateway functions is performed by the target base station. After the handover, the relay gateway entity of the MRN is changed from the source base station to the target base station, so the path between the logical MRN relay gateway and the source base station becomes the path between the MRN relay gateway and the target base station, and the MRN The gateway communication destination node address (ie, the target base station address or the target communication node address or the target base station identifier) is no longer the source base station but becomes the target base station. Therefore, it is necessary to perform such a change of address. Of course, another way to perform this change is to directly save the target communication node address of the gateway entity when the gateway information of the source base station and the target base station interacts. After the MRN handover is completed, the gateway function entity is changed and the gateway is changed. The change in the destination address of the entity communication. Another way is to directly default to such an address change. After the relay handover is completed, the destination communication node address of the gateway function is the address or identifier of the target base station, or the address or identifier provided by the target base station. The relay gateway entity is not a real physical entity, but is integrated in the base station as part of the base station function, so that the target base station performs the relay gateway change, that is, the target base station performs the middle. Following the gateway function, it begins to provide gateway functionality for the trunk.

 In a specific application, when some or all functions of the SGW and the PGW of the MRN are combined in the base station, the MRN gateway information provided by the source base station to the target base station may be: information required to provide the SGW and the PGW function for the MRN; The MRN gateway information provided by the source base station to the target base station may be only the information required to provide the PGW function for the MRN, and only some or all of the functions of the PGW of the MRN are combined in the base station. When the base station combines the PGW function of the MRN, or the SGW function, or other gateway function (for example, the HeNB GW function), or simultaneously implements the foregoing multiple gateway functions, the PGW function or the SGW function of the MRN provided by the source base station to the target base station , or other gateway functions, or information required to implement the above various gateway functions simultaneously; when the base station incorporates the PGW function of the MRN, or the SGW function, or other gateway functions (such as the HeNB GW function), or simultaneously implement the above various The gateway function, the PGW function provided by the source base station to the MRN of the target base station, or the SGW function or other gateway function, or the information required for simultaneously implementing the at least two gateway functions;

 In a specific application, the source base station provides the MRN gateway information to the target base station, where the source base station sends the handover request message to the target base station, and carries the MRN gateway information in the handover request message. In another specific application, the source base station may not need to provide the gateway information of the MRN when transmitting the handover request message, but provide the gateway information of the MRN after the handover is completed, for example, providing the gateway information of the MRN according to the gateway change request of the target base station. The purpose of this embodiment is to provide the gateway information of the MRN to the target base station, and the specific gateway information transmission mode is not limited in this embodiment.

When the target base station receives the gateway information of the MRN provided by the source base station, the target base station may acquire the gateway information of the MRN while receiving the handover request message, and may acquire the gateway information of the MRN after the handover is completed, and the target base station may Proactively request the MRN's gateway information from the source base station by sending various messages. Related messages for requesting gateway information of the MRN may include, but are not limited to, a Gateway Change Request (RN_GW_HO_REQ) message or the like. FIG. 3 is a schematic diagram of a handover processing method according to Embodiment 3 of the present invention, where the method includes:

 S31: After the mobile node switches to the target base station, change the gateway of the mobile node to the target base station;

 S32: The target base station provides a gateway function for the mobile node.

 In this embodiment, the mobile node includes a UE and an MRN. After the UE and the MRN are switched, the gateway functions of the UE and the MRN can be transferred to the gateway function entity of the target base station (ie, the target base station itself), which facilitates communication between the mobile node and the target base station after handover.

 Further, the method may further include: allocating an IP address to the mobile node, and providing the IP address to the mobile node.

 The method may further include: receiving gateway information of the mobile node provided by the source base station; providing the gateway function by the target base station to the mobile node comprises: the target base station providing the mobile node with a gateway function by using the gateway information of the mobile node.

 The method can also include notifying the mobility management entity of the mobile node to switch the gateway path of the mobility management entity to the target base station.

 The changing the gateway of the mobile node to the target base station comprises: transferring a portion of the gateway function of the mobile node to the target base station.

 The gateway may include many types, such as PGW, SGW, PGW, and home e B GW. Some gateways may include multiple gateway functions as described above. This method may only transfer part of the gateway functions in the gateway to the target base station.

 In the foregoing embodiment, when the target base station performs the relay gateway change, and provides the gateway function for the relay, in addition to notifying the relay MME and the relay SGW to perform path switching, the MRN may be assigned an IP address. FIG. 4 is a schematic diagram of a method for allocating an IP address of an MRN according to Embodiment 4 of the present invention, where the method includes:

S41: When performing a relay gateway change to provide a gateway function for the relay, the mobile relay section is The point assigns an IP address and provides the IP address to the mobile relay node.

 The relay gateway entity function in the source base station entity is transferred to the relay gateway entity of the target base station, and the relay gateway change is implemented, so that the relay gateway entity (or directly the target base station) in the target base station allocates one to the MRN. IP address, specifically, the base station sends an IP address change message to the MRN. The message contains the IP address assigned to the MRN. The message also includes the TEID assigned to the MRN.

 S42: The MRN receives the assigned IP address and performs IP address change.

 Optionally, the MRN replies to the IP address change reply message and confirms that the IP address is changed.

 In this embodiment, after the MRN is switched, the IP address allocation of the MRN is implemented, that is, the target base station performs the change of the relay gateway, and after providing the gateway function for the relay, the relay gateway function entity (which may also be considered as the target base station) in the target base station may be Assign an IP address to the MRN. Of course, the IP address assigned by the target base station may be the same as or different from the MRN source IP address.

 When the base station can combine all or part of the functions of the SGW and the PGW of the MRN,

 According to different gateway functions, base stations can be classified into several types, which can be:

 a) the base station includes some or all of the functions of the relay PGW;

 b) The base station includes some or all of the functions of the relay PGW and the relay SGW; c) the base station includes some or all of the functions of the relay PGW and the home e B GW; at this time, the SGW may be outside the base station entity.

 d) The base station includes some or all of the functions of the relay PGW and the home eNB GW; at this time, the SGW does not exist in the network architecture.

 e) the base station includes part or all of the functions of the relay PGW, the relay SGW and the home eNB GW;

 f) the base station contains some or all of the functions of the relay PGW and other gateways;

 The fifth embodiment is applicable to the case where the SGW function is included in the base station, or the SGW function cannot exist in the relay architecture.

Embodiment 5 of the present invention provides a handover processing method to implement a change of a relay gateway. Figure 5 is a schematic diagram of a handover processing method according to Embodiment 5 of the present invention, where the method includes:

 S51: The source base station of the MRN sends a handover request message to the target base station, where the handover request message includes gateway information of the MRN.

 The source base station sends a handover request message to the target base station by using the X2 message signaling. The handover request message includes the information of the MRN in addition to the information that the MRN handover should have, and the gateway information of the MRN is the same as the previous description. , as: The information required to perform the gateway function when the source base station integrates the gateway function of the MRN. Further, the handover request message may further include a destination address or an identifier (ie, an address or an identifier of the target base station) of the gateway function entity of the MRN after the MRN is switched, so that the relay gateway communicates with the target base station instead of Source base station. Further, A) the message may further include: context information of the terminal of the MRN, so that the target base station can perform the reloading of the terminal bearer between the target base station and the MRN by using the context information of the terminal in the process of establishing the bearer by the MRN. Mapping. Of course, the content can be brought to the target base station using another message.

 B) The message may further include: a session context, the session context may include some policy information, carrying binding configuration information, charging information, and service layer entity address information. This information can be carried to the target side base station as, for example, a message called Session Redirection.

 Of course, the A) B) content can be brought to the target base station by using another message.

 S52: The target base station returns a handover request acknowledgement message to the source base station.

 It can be understood that the handover request acknowledgement message is also implemented by X2 message signaling, indicating that the target base station agrees to perform handover.

 S53: The source base station notifies the MRN to perform handover.

 S54: After the MRN handover is completed, notify the target base station that the handover has been completed.

After receiving the handover command of the source base station, the MRN performs a synchronization process with the target base station and accesses the target cell. S55a: After the MRN handover is completed and the target base station is successfully accessed, the target base station performs gateway relocation by using the received gateway information of the MRN, and provides a gateway function for the relay. Specifically, the gateway destination address of the MRN may be changed to the address or identifier of the target base station itself, so the gateway data from the MRN will flow to the target base station instead of the source base station.

 In this step, it can be said that the function of the relay gateway entity in the source base station entity is transferred to the relay gateway entity of the target base station, and the relay gateway is changed, thereby the relay gateway entity in the target base station (or directly speaking to the target) The base station) will assign an IP address to the MRN.

 S55b: The relay gateway function entity in the target base station allocates an IP address to the MRN. After the trunk gateway is changed, the new gateway of the MRN can assign a new IP address to the MRN. Specifically, the gateway entity (or the target base station) in the target base station may send the IP address allocated for the MRN to the MRN by the target base station through a specific message (such as a gateway address change message). The message includes the IP address assigned by the relay gateway to the MRN; the message may also include the TEID assigned to the MRN. It can be understood that the relay gateway function entity in the target base station can assign the same IP address to the MRN, or can maintain the existing IP address of the MRN unchanged.

 The MRN receives the IP address change message and changes the IP address. Optionally, the MRN replies to the relay IP address change reply message and confirms that the IP address is changed. Therefore, the MRN establishes a GTP tunnel with the gateway entity in the target base station, and the MRN can remap the bearer of the subordinate terminal to the GTP tunnel through the GTP tunnel. Of course, the gateway entity here is not a separate entity, but is integrated into the base station and is part of the base station function, which is described here as an entity only for ease of understanding. Optionally, step S55b may also be performed after S57 is completed.

S56: The target base station notifies the relay MME to perform a change of the relay path (Path), and the target base station may notify the relay MME of the change and path change of the relay gateway by using the existing Sl-AP: Path switch request message. The message is notified to the MME that the relay has changed the cell and changed the relay gateway. The path between the relay MME and the source base station is changed to a path between the relay MME and the target base station, and the path between the relay MME and the relay source GW is changed to a relay MME and a relay new GW (ie, The path between the gateway functional entities integrated in the target base station, which is actually the target base station). The above two path changes are actually the path change between the relay MME and the base station, which is described here as a change of the two paths, just for the sake of understanding.

 In addition to the content in the prior art (such as the message may include ECGI information of the target cell and unacceptable EPS bearers, etc.),

 The message may include a relay identifier (identity) assigned to the RN by the relay gateway, specifically a relay IP address, and may also include a relay TEID assigned to the relay.

 The message may also include an IP address and/or a TEID of the base station, and the TEID may be one or more. The message may include a relay gateway address and/or a relay gateway identifier (RN GW identity ). A specific representation of the relay identifier is the IP address of the relay gateway. It can also contain the TEID of the trunking gateway. Specifically, the message may include:

 Mode 1) the control plane address (or gateway IP address) of the gateway and/or the control plane TEID of the gateway; mode 3) the control plane address (or gateway IP address) of the gateway and/or the control plane TEID of the gateway, and the user of the gateway The face address (or gateway IP address) and/or the TEID of the user plane of the gateway.

 The message may also include terminal location information, which is represented by User Location Information IE information; the message may also include GRE keys (for PMIP-based S5/S8); the message may also contain context information bearer context(s );

S57: After the relay MME changes the relay path, the path change reply information is sent. Specifically, since the target base station changes the MRN gateway to the target base station after the MRN handover, the relay MME may update related information such as the relay gateway address (or the address of the gateway functional entity included in the target base station, There may be information such as the relevant TEID; or actually the address of the target base station, and may also have information such as the corresponding TEID), and the information of the address and/or TEID of the relay serving base station, that is, the update of the relay attribution. In S56 and S57, the user bearer coordination of the coordinated user plane and the control plane may also be performed between the relay MME and the GW. The process implements changing the path between the relay MME and the source base station to a path between the relay MME and the target base station, and changing the path between the relay MME and the relay source GW to the relay MME-relay new The path between the GW (that is, the gateway functional entity integrated in the target base station, which is actually the target base station).

 In an implementation manner, after receiving the gateway information of the MRN, the relay MME may send an S1-AP: r-Path switch request ack message, that is, a handover request response message, to the target base station, where the message is used to relay the MME. This relay path change request message is confirmed.

 In the above processes S56 and S57, the target base station and the relay MME implement path change notification and acknowledgement between each other through two pieces of signaling. In another implementation manner, the target base station notifying the relay MME to perform the relay path change may be implemented according to a conventional procedure. The target base station may send a Path Switch Request message to the relay MME, and the relay MME returns a User Plane Update Request message to the target base station, and the target base station sends a User Plane Update Response message to the relay port, and the relay MME performs the message. The relay path is changed, and a Path Switch Request ack message is returned to the target base station. The specific process of how to notify the relay MME to change the relay path is not limited in this embodiment.

 S58: Perform a path change process of the terminal between the target base station and the terminal MME and the terminal gateway. The specific terminal path change procedure can be implemented using the prior art, or the method described in the subsequent embodiments (such as Embodiment 16).

 S59: The source base station releases related resources of the MRN. After the target base station completes the gateway change and the switching between the user plane and the control plane, the source base station may release the related resources of the MRN, and the related resources may further include the gateway information of the MRN. The source base station can also release related resources of the terminal of the MRN at the same time.

In this embodiment, when the MRN is switched, the gateway is changed to the MRN, the target base station provides a gateway function for the relay, and the relay MME is notified to perform the relay path change, so that the path between the relay MME and the source base station is changed to The path between the relay MME and the target base station, and the relay The path between the MME and the relay source GW is changed to a path between the relay MME-relay new GW (ie, the gateway function entity integrated in the target base station, which is actually the target base station).

 In practical applications, the order of the different steps of the foregoing method embodiments may be reversed, and such adjustments will not affect the implementation of the present invention. For example, the sequence between S55 and S56 and S57 can be adjusted, that is, the target base station performs gateway change, and the sequence of the relay IP address allocation and the target base station notifying the relay MME to perform the relay path change can be changed.

 FIG. 6 is a schematic diagram of a handover processing method according to Embodiment 6 of the present invention. The overall process of the method is similar to that in Embodiment 5. The implementation process is slightly different, including:

 S61: The source base station of the MRN sends a handover request message to the relay MME of the MRN, where the handover request message includes gateway information of the MRN.

 Different from the fifth embodiment, in this embodiment, the source base station does not use the X2 message signaling, but sends a handover request message to the relay MME by using the S1 message signaling, so that the relay MME forwards the message to the target base station, which is The effect of the fifth embodiment is the same.

 S62: The relay MME forwards the handover request message to the target base station.

 S63: The target base station returns a handover request acknowledgement message to the relay MME.

 It can be understood that the handover request acknowledgement message is also implemented by S1 message signaling.

 S64: The relay MME forwards a handover request acknowledgement message to the source base station.

 The subsequent processes S65 to S611 are the same as the processes S53 to S59 in the fifth embodiment, and are not described here again. This embodiment can also implement the path change, but the source base station needs to pass the relay MME when sending the handover request message to the target base station. Forwarding. It can be understood that the MRN is similar to the terminal, and the RRC (Radio Resource Control) message can be used to implement the transmission of the handover request message, which is not limited in this embodiment.

In the fifth embodiment and the sixth embodiment, the base station aggregates all and part of the functions of the relay gateway. It can be understood that the PGW function of the relay gateway can be only included in the base station, and the SGW function is not included. There will be a slight change FIG. 7 is a schematic diagram of a handover processing method according to Embodiment 7 of the present invention, where the method includes:

 S71 to S74 are the same as the processes S51 to S54 in the fifth embodiment, and are not described herein again.

 S75a: After the MRN successfully accesses the target base station, the target base station performs gateway relocation by using the received gateway information of the MRN, specifically, changing the gateway destination address of the MRN to the target base station's own address or identifier. Therefore, data from the MRN gateway will flow to the target base station instead of the source base station.

 In this step, since the relay gateway function is integrated in the base station, the target base station can change its gateway to the target base station itself by default after the MRN is switched, thereby successfully changing the relay gateway function entity from the source base station to At the target base station, so that the target base station performs the relay gateway function.

 The relay gateway entity function in the source base station entity is transferred to the relay gateway entity of the target base station, and the relay gateway change is implemented, so that the relay gateway entity (or directly the target base station) in the target base station allocates one to the MRN. IP address.

 S75b: After the trunk gateway is changed, the relaying new gateway can assign a new IP address to the MRN. Specifically, the gateway entity in the base station may send the IP address allocated for the RN to the MRN through the target base station, or assign the same IP address to the MRN, or maintain the existing IP address of the MRN.

 The MRN establishes a GTP tunnel with the gateway entity in the target base station, and the MRN can remap the bearer of the subordinate terminal to the GTP tunnel through the GTP tunnel. Of course, the gateway entity here is not a separate entity, but is integrated within the base station and is part of the base station function, which is described here as an entity only for ease of understanding.

 Optionally, step S75b may also be performed after S79 is completed.

S76: The target base station notifies the relay MME to perform a change of the relay path (Path), that is, the target base station notifies the relay MME of the gateway information of the MRN, so that the relay MME changes the relay path. Specifically, the target base station sends a Path switch request message to the relay MME. The MME is notified that the relay has changed the cell, and the message includes the ECGI information of the target cell and the unacceptable EPS bearer.

 The target base station can use the existing Sl-AP: Path switch request message to the relay MME of the MRN to notify the relay MME of its relay gateway change and path change.

 The message further includes a relay gateway assigning/updating a relay identifier (identity) to the RN, specifically a relay IP address. It can also contain a trunk TEID assigned to the trunk. The message may also contain the IP address and/or TEID of the base station.

 Specifically, the path request message includes a relay gateway address and/or a relay gateway identifier (RN GW identity ). A specific representation of the relay identifier is the IP address of the relay gateway. The path request message may also include the TEID of the trunk gateway. Specifically, the path request message may include:

 Mode 1) the control plane address (or gateway IP address) of the gateway and/or the control plane TEID of the gateway; mode 3) the control plane address (or gateway IP address) of the gateway and/or the control plane TEID of the gateway, and the user of the gateway The face address (or gateway IP address) and/or the TEID of the user plane of the gateway.

 S77: The relay MME sends a user plane update request message to the relay SGW. Specifically, the message further includes a relay gateway assigning/updating a relay identifier (identity) to the RN, specifically, a relay IP address, and may further include a relay TEID allocated to the relay. The message may also include the IP address and/or TEID of the base station.

 The message may also include a relay gateway address and/or a relay gateway identifier (RN GW identity ). A specific representation of the relay identifier is the IP address of the relay gateway. The message can also contain the TEID of the trunking gateway. Specifically, the message may include:

 Method 1) The control plane address (or gateway IP address) of the PGW gateway and/or the control plane TEID of the gateway;

Mode 2) Control plane address (or gateway IP address) of the PGW gateway and/or control plane of the gateway The message may also include terminal location information, which is represented by User Location Information IE information;

 The message can also contain GRE keys (for PMIP-based S5/S8);

 The message may also include bearer context information bearer context(s);

 The message Type over S5/S8 can also be used to indicate which protocol communication the SGW uses on the S5/S8 interface.

 Thereby, the path between the relay SGW and the source base station is changed to a path between the relay SGW and the target base station, and the path between the relay SGW and the relay source PGW is changed to a relay MME-relay new PGW (ie, The path between the gateway functional entities integrated in the target base station, which is actually the target base station).

 S78: The relay SGW performs path change, and changes the relay PGW address to a gateway function entity (actually the target base station;) in the target base station, and sends a user plane update request message to the medium Following the MME, the path change indicating that the relay MME relays the SGW has been completed, and the user update response message includes:

 Method 1) The control plane address (or gateway IP address) of the SGW gateway and/or the control plane TEID of the gateway;

 Mode 2) Control plane address (or gateway IP address) of the SGW gateway and/or control plane mode of the gateway 3) User plane address (or gateway IP address) of the SGW gateway and/or TEID of the user plane of the gateway.

S79: After receiving the path change notification in S76, the relay MME updates related information such as the target base station address and the like, and updates information such as the PGW-related address and/or TEID, that is, the relay attribution update. After the update is complete, the relay MME sends a path switch ACK message to the target base station, and the message may include the following message: Method 1) the control plane address (or gateway IP address) of the SGW gateway and/or the control plane TEID of the gateway;

 Mode 2) Control plane address (or gateway IP address) of the SGW gateway and/or control plane mode of the gateway 3) User plane address (or gateway IP address) of the SGW gateway and/or TEID of the user plane of the gateway.

 Steps S76, S77, S78 and S79 may be performed simultaneously with step S75a (or steps S75a and S75b), or may be performed after S74 and before S75a. In summary, steps S76, S77, S78 and S79 can be performed simultaneously with step S75a (or steps S75a and S75b), or sequentially.

 The subsequent processes S710 to S711 are the same as the processes S58 to S59 in the fifth embodiment, and are not described herein again. In this embodiment, the gateway address of the base station in which the relay PGW function is set is changed, and the path of the SGW and the relay MME is changed, thereby completing the gateway change, and preventing the target base station from transmitting the MRN data back to the source base station.

 The source base station in the foregoing seventh embodiment sends the handover request message to the target base station by using the X2 message signaling. However, it can be understood that the source base station can also use the method in the sixth embodiment, that is, by using the S1 message signaling to send the handover request message to the source base station. The relay MME is configured to forward the handover request message to the target base station to implement the transmission of the handover request. The reply of the handover request acknowledgement is similar to the handover request message transmission process, and is not directly transmitted by the source base station and the target base station but is relayed. The MME forwards.

It can be understood that the implementation method of the source base station providing the gateway information of the MRN to the target base station may not be unique. In the foregoing embodiment, the source base station carries the gateway information of the MRN in the handover request message and sends the information to the target base station, so that the target base station can obtain the gateway information of the MRN in the process of the handover request, and prepare for the gateway change after the subsequent MRN handover is completed. . In another implementation manner, the source base station may not transmit the gateway information of the MRN in the handover request message to the target base station, but the target base station performs a gateway change request to the source base station after the MRN handover is completed, requesting to provide the direction itself. Gateway information. FIG. 8 is a schematic diagram of a handover processing method according to Embodiment 8 of the present invention. The method includes: S81 and S82 are the same as processes S53 and S54.

 S83: After the MRN synchronizes with the target base station, after successfully accessing the target cell, the target base station sends a gateway change request message to the source base station of the MRN. The gateway change request message may be implemented by X2 message signaling between base stations, and may include an address and an identifier of the target base station, or an identifier of a target cell. It can be understood that the gateway change request message can be replaced by other messages with similar functions, such as a handover notification message.

 S84: After receiving the gateway change request message, the source base station sends a gateway change reply message to the target base station, where the gateway change reply message includes the gateway information of the MRN. The gateway change reply message can also be implemented by X2 message signaling. Further, the gateway change reply message may further include an address or identifier of the target gateway after the MRN handover (ie, an address or an identifier of the target base station).

 Further, A) the message may further include: context information of the terminal of the MRN, so that the target base station can perform the reloading of the terminal bearer between the target base station and the MRN by using the context information of the terminal in the process of establishing the bearer by the MRN. Mapping. Of course, the content can be brought to the target base station by using another message.

 B) The message may further include: a session context, the session context may include some policy information, carrying binding configuration information, charging information, and service layer entity address information. This information can be carried to the target side base station as, for example, a message called Session Redirection.

 Of course, the A) B) content can be brought to the target base station by using another message.

 Processes S85a through S89 are the same as in the fifth embodiment S55a and S59. In this embodiment, the target base station may send a gateway change request message to the source base station, so that the source base station provides the MRN gateway information to the target base station, so that the target base station implements the gateway change.

S86, S87 can be performed simultaneously with S85a, or before S85a and after S84. In short, S86, S87 can be carried out simultaneously with S85a, or in sequence. S86, S87 can also be performed simultaneously with S85a, S85b, or before S85a and after S84. In short, S86, S87 can be carried out simultaneously with S85a, and S85b, or in sequence.

 It can be understood that the process S83 of transmitting the gateway change request message by the target base station to the source base station of the MRN and the process S84 of receiving the gateway change reply message can be implemented not by using the X2 message signaling but by using the S1 message signaling. When the gateway change request message and the receiving gateway change reply message are implemented by using the S1 message signaling, that is, the information transfer between the target base station and the source base station is to be forwarded by the relay MME, the forwarding process is switched in the sixth embodiment. The request message has been described in the transmission, and no specific expansion is made here. In the eighth embodiment, as in the fifth embodiment, all the functions of the PGW and the SGW in the relay gateway are integrated in the base station. When only the PGW function in the relay gateway is integrated in the base station, the process S85 to S89 may change, and a gateway change method similar to that of the seventh embodiment may be used, that is, similar to the S73 to S711 in the seventh embodiment. process.

 It can be understood that there is no sequence between the process of performing the gateway change by the target base station and the process of notifying the relay MME to perform the relay path change (for example, S85a and S86 in Embodiment 8), and any process may be in another process. Previously, two processes could also be implemented simultaneously. It can be understood that there is no strict order between the different steps of the foregoing embodiments, and those skilled in the art can make certain adjustments to the embodiments according to actual needs, and the change of the execution order of each step will not affect the implementation of the embodiment of the present invention, and the generation thereof The beneficial effects are also expected by those skilled in the art, and thus are also included in the present invention and achieve the desired effects of those skilled in the art.

 FIG. 9 is a schematic diagram of a handover processing method according to Embodiment 9 of the present invention. The method includes: S91 to S94 are the same as the procedures S51 to S54 in Embodiment 5, and details are not described herein again.

S95: After the MRN successfully accesses the target base station, the target base station performs gateway relocation by using the received gateway information of the MRN, specifically, changing the gateway destination address of the MRN to the target base station's own address or identifier. Therefore, data from the MRN gateway will flow to the target base station. Not the source base station.

 S96: After the trunk gateway is changed, the relaying new gateway can assign a new IP address to the relay. Specifically, the gateway entity in the base station may send the IP address allocated for the RN to the relay through the target base station, or assign the same IP address to the relay, or may maintain the existing IP address of the relay unchanged.

 S97: The target base station transmission path change request (GW_path switch REQ) message notifies the relay service gateway (SGW) that the MRN has changed the cell, and the relay PGW has also been changed. Different from the way in which the relay MME in the seventh embodiment causes the relay service gateway to perform the path change, in this embodiment, the target base station sends a path change request to prompt the relay service gateway to perform the path change.

 S98: After receiving the notification, the relay SGW updates its destination address of the relay gateway (actually the address of the target base station), and the information related to the MRN, the address associated with the relay gateway, and/or the TEID, that is, relaying The attribution update, after the update is completed, may send a GW path switch RSP message to the target base station to promote the path change of the network gateway. The relay SGW communicates with the relay gateway through the address of the target base station. In S97 and S98, the MME and the GW can coordinate the user bearer coordination between the user plane and the control plane. At the same time, the related information and identifier between the MME and the gateway in the prior art will remain unchanged.

 S99: The target base station notifies the relay MME by using the existing path switch request message, the relay has changed the cell, and the relay PGW has also been changed. The target base station notifies the relay MME to perform a change of the relay path (Path), that is, the target base station notifies the relay MME of the gateway information of the MRN, so that the relay MME changes the relay path. After the relay MME changes the relay path, the data transmitted by the SGW to the MRN is sent to the target base station instead of the source base station.

 S910: The relay MME may perform path switching of the relay gateway, that is, switch the gateway path of the MRN to the target base station, and send a path switch response message to the target base station.

The subsequent processes S911 to S912 are the same as the processes S58 to S59 in the fifth embodiment, and are not described herein again. In this embodiment, the gateway address of the base station that aggregates the relay PGW function is changed, and the SGW is The path of the relay MME is switched to complete the gateway change. It can be understood that there is no strict sequence between S97, S98 and S99, S910. The target base station may first send a path change request message to the relay service gateway, and then send a path switch request message to the relay MME, or two processes may simultaneously This embodiment does not limit this.

 FIG. 10 is a schematic diagram of a handover processing method according to Embodiment 10 of the present invention, where the method includes:

S101 to S104 are the same as steps S81 to S84 in the eighth embodiment.

 S105 is the same as S86 in the eighth embodiment.

 S106 to S107 are the same as S97 to S98 in the seventh embodiment.

 S108a and SI 08b are the same as the eighth embodiment S85a and S85b.

 S109 to S1011 are the same as the eighth embodiment S87 to S89.

 FIG. 11 is a schematic diagram of a handover processing method according to Embodiment 11 of the present invention, where the method includes:

 Steps S81 and S112 are the same as steps S81 and S82 in the eighth embodiment.

 S113: The target base station sends a gateway change request message to the source base station.

 S114: The source base station sends a gateway change reply message to the target base station, and the gateway change reply message includes the gateway information of the MRN.

 S115: The target base station first sends a relay path change notification to the relay MME.

 S116a: The target base station changes the gateway address. The change process of the previous embodiment is similar to the specific gateway address change.

 S116b: The target base station allocates an IP address to the MRN.

 S117: After the relay MME completes the relay path change, the path change reply information is sent to the target base station.

 Processes S118 and S119 are similar to S88 and S89 in the eighth embodiment and are not developed here.

This embodiment shows that the process in which the target base station performs the relay gateway address update and the notification relay MME change the relay path, and the sequence in which the relay MME changes the relay path can be adapted. Should be adjusted.

 FIG. 12 is a schematic diagram of a handover processing method according to Embodiment 12 of the present invention, where the method includes:

 S121: The MRN receives the IP address change message and performs an IP address change.

 S122: The base station and the MRN perform a GTP tunnel establishment and/or update process, and perform bearer establishment and/or update, and remap the terminal's EPS bearer to the updated radio bearer.

 In this embodiment, the base station and the MRN can implement radio bearer update after handover.

 When the MRN is switched, the MRN subordinate terminal and the core network corresponding to the terminal are not aware of the handover. Therefore, the core network side needs to perform handover of the terminal path, so as to change the path of the original terminal MME to the source base station to the terminal MME to the target. The path of the base station.

 FIG. 13 is a schematic diagram of a method for changing a terminal path according to Embodiment 13 of the present invention, where the method includes:

 S13 la: Send a path switch request message to the terminal MME, where the path switch request message includes information of at least two terminals, the at least two terminals belong to the terminal MME, and the path switch request message It is used to request the terminal MME to switch the terminal path to the target base station. That is, the path switch request message is used to notify the terminal MME that the at least two terminals have changed the cell, and the target node of the downlink GTP tunnel needs to be changed (the user plane connection of the terminal gateway needs to be switched from the source base station to the target base station). The path between the terminal gateway and the source base station is changed to a path between the terminal gateway and the target base station, and the path between the terminal MME and the source base station is changed to a path between the terminal MME and the target base station.

 S132a: Receive a path switch response message sent by the terminal MME.

 After the terminal MME path is switched, a path switch response can be sent to enable the target base station to receive the response. The response may include two cases of successful and unsuccessful path switching, and no expansion is performed here.

In fact, each terminal has its own terminal MME functional entity and its own terminal gateway (PGW/SGW). The MME functional entity of multiple terminals may be in a separate terminal MME Within an entity, it may not be an entity that is physically separate. Similarly, the gateway function entity of multiple terminals of the terminal gateway may be in a physical entity of a separate terminal gateway, or may not be an physically separate entity.

 After the terminal MME physical entity receives the path switch request including the information of the multiple terminals (N, N is greater than or equal to 2), the terminal MME may send a modify bearer request message to each terminal gateway, and send the message to each modify bearer request message. The information of the terminals belonging to the terminal gateway among the plurality of terminals is included, so that each terminal gateway performs terminal path modification on the terminals of the plurality of terminals according to the information. If, among the plurality of terminals (N), the gateways of the partial terminals (K, K is less than or equal to N, and greater than or equal to 2) are within the physical entity of one terminal gateway, the terminal MME may perform the partial terminals (K) The information is sent to the terminal gateway physical entity through a modify bearer request message instead of individually transmitting a corresponding modify bearer request message for each terminal.

 When multiple terminals (M, M is greater than or equal to 2) of the MRN monthly service do not belong to the same terminal MME physical entity, but only some of the terminal MMEs (N, N is greater than or equal to 2, and N is less than or equal to M) are in the same Within the physical entity of the terminal MME, that is, when there are multiple terminal MMEs in different physical entities of the terminal MME, multiple terminals belonging to the physical entity of the same terminal MME may be used as a group, and the target base station may send a path switching request. The message is sent to the terminal MME physical entity of the group of terminals, so that the physical entity of the terminal MME can change the path of the group of terminals. Therefore, the target base station may send multiple path switch request messages to the multiple terminal MME physical entities, but such an implementation process still does not require the target base station to separately send a path switch request message for each terminal, which can still save signaling overhead. .

 FIG. 13b is a schematic diagram of a method for changing a terminal path according to Embodiment 13 of the present invention, where the method includes:

S131b: Receive a path switch request message, where the path switch request message includes information of at least two terminals, where the at least two terminals belong to the local terminal MME, and the path switch request message is used to request to switch the terminal path to the target base station. . Briefly, the path switch request message is used to pass It is known that at least two terminals of the terminal MME have changed the cell, and the terminal MME also needs to notify the terminal gateway to perform the change of the target node of the downlink GTP tunnel (the user plane connection of the terminal gateway needs to be switched from the source base station to the target base station).

 S132b: Send a path switch response message. The terminal MME receives the path switch request message sent by the base station, switches the path to the target base station, and sends a path switch response message to the base station.

 Further, the method may include: the terminal MME sends a modify bearer request message to the terminal gateway of the at least two terminals, where the modify bearer request message includes information of the at least two terminals, to notify the terminal gateway to notify the user The face connection is switched to the target base station (ie, the terminal gateway changes the target node of the at least 2 terminal downlink GTP tunnels to the target base station;); and receives the modified bearer response message sent by the terminal gateway. In this implementation process, the terminal MME may initiate a modify bearer request message to the terminal gateway of the at least two terminals, so that the gateway of the multiple terminals can implement path switching, so that the path between the terminal gateway and the source base station is changed between the terminal gateway and the target base station. path of.

 It can be understood that the at least two terminals belong to the same terminal MME but may belong to different terminal gateways. When the at least two terminals belong to one terminal gateway, the terminal MME may only send a modify bearer request message to the terminal gateway, requesting the terminal gateway to perform path modification on the at least two terminals. When the at least two terminals do not belong to one terminal gateway, that is, the case where multiple terminals correspond to multiple terminal gateways, the terminal MME may determine at least two terminals belonging to the same terminal gateway among the at least two terminals as A terminal group sends a modify bearer request message to the terminal gateway of the group terminal, and the terminal MME may send multiple modify bearer request messages for multiple terminal gateways. In this case, a modified bearer request message can still be used to notify the terminal gateway to change the target node of the at least two terminal downlink GTP tunnels to the target base station, without separately transmitting a modify bearer request message to each terminal, which can save signaling. Overhead. It can be understood that the modification bearer response message of the terminal gateway received by the terminal MME may indicate that the modification bearer succeeds or fails, and is not expanded here.

FIG. 14 is a schematic diagram of a method for changing a terminal path according to Embodiment 14 of the present invention, where the method includes: S141: The gateway receives the modify bearer request message, where the modify bearer request message includes information of at least two terminals, where the at least two terminals belong to the gateway, and the modify bearer request message is used to notify that the user plane connection is switched to Target base station (ie, the terminal gateway changes the target node of the at least two terminal downlink GTP tunnels to the target base station;);

 S142: The gateway switches the user plane connection to the target base station;

 S143: The gateway replies with a change response message.

 The gateway in this embodiment receives a message, modifies at least two of its subordinate terminal paths, saves signaling overhead, and improves efficiency. After the gateway switches the user plane connection to the target base station, the transmission path of the gateway and the at least two terminals passes through the target base station instead of passing through the source base station as before the handover, so that the gateway data flows to the correct base station.

 FIG. 15 is a schematic diagram of a method for changing a terminal path according to Embodiment 15 of the present invention, where the method includes:

 S151: The target base station sends a path switch request message to the terminal MME, and notifies the MME that the base station served by the UE changes. The path switch request message includes information about multiple terminals, and the multiple terminals belong to the terminal MME.

 The message may specifically include information such as the TAI+ECGI of the target cell and the rejected EPS bearers bearer list.

The content in a path switch request message in the prior art is for one terminal. For the case of performing path change for a plurality of terminals, if the base station is capable of distinguishing each bearer of each terminal, the information content of the path switch request message of the plurality of terminals may be summarized. In a path switch request message, in order to display the difference, the summarized path switch request message may also be referred to as an ath switch request-all message. At the same time, the MME function entities of the multiple terminals are all in one MME physical entity, and then the base station can send the path switch request-all message to the function entity. S152: The terminal MME receives the path switch request message, and sends a modify bearer request message to the terminal gateway, and notifies the user plane of the serving gateway that the connection needs to be switched from the source base station to the target base station. The path switching request message includes information of the plurality of terminals (N, 2 or more). Then, the MME receives a path switch handover request message about multiple terminals (N), and the MME needs to notify all terminal gateway function entities of the plurality of terminals (N), and the path change of the terminal concerned. If a plurality of terminals (Q, Q is less than or equal to N, and greater than or equal to 2) of the plurality of terminals (N) are in the same gateway physical entity, then a modify bearer request message is sent to The terminal gateway physical entity is processed by the terminal gateway physical entity for different terminals. If there is no terminal gateway function in the same gateway physical entity, a single terminal is used to send a single modify bearer request message to the respective terminal gateway. In addition, the terminal MME may not use the foregoing optimization, but continue to use the prior art, and the terminal MME may send a modify bearer request message for each terminal, and each modify bearer request message is used to request the terminal gateway to update corresponding to the message. The attribution information of the terminal. A modified bearer request message specifically includes addresses of a common target base station based on multiple terminals, and corresponding TEIDs, and even terminal location information, specifically, multiple terminal location information IEs (User Location Information IEs).

 In this process, the terminal MME performs path switching, that is, the terminal path is switched to the target base station, so that the transmission path of the terminal MME and the plurality of terminals passes through the target base station instead of the source base station. The switched terminal MME, when interacting with the plurality of terminal information, may flow its information to the target base station instead of the original base station of the terminal.

 S153: The terminal gateway performs user plane switching, that is, the terminal path is switched to the target base station, that is, the transmission path of the multiple terminals is changed, so that the transmission path of the terminal gateway and the multiple terminals passes through the target base station instead of the source base station. In this step, the terminal gateway will send data to the target base station in the downlink using the received new address and TEIDs. In fact, the path between the gateway and the source base station is changed to the path between the terminal gateway and the target base station.

S154: After the handover is completed, the terminal gateway sends a modify bearer response message to the terminal MME, where The tampering response message is used to notify the terminal MME that the relay gateway address of the plurality of terminals has been changed. It can be understood that, when the terminal MME sends a modify bearer request message to the terminal gateway for each terminal, the terminal gateway receives multiple modify bearer request messages, and the terminal gateway needs to send a response message for each modify bearer request message. That is, one modification bearer response message is sent to each terminal to the terminal MME.

 SI 55: The terminal MME sends a path switch response message to the target base station to notify the target base station terminal that the path switch is completed. The terminal MME may carry the information of the multiple terminals that have successfully changed the path in the path switch response message to the target base station. The path switch response message may specifically be a Path switch request ACK message.

 In this embodiment, the gateway of the terminal and the MME perform terminal path switching, that is, the path between the terminal gateway and the source base station is changed to a path between the terminal gateway and the target base station, and the path between the terminal MME and the source base station is changed. The path between the terminal MME and the target base station is such that the data of the relay subordinate terminal can be transmitted to the target base station, and then transmitted to the relay by the target base station (now the relay service base station).

 In fact, each terminal has its own terminal MME functional entity and its own terminal gateway.

( PGW/SGW ). The MME functional entities of multiple terminals may be within a single terminal MME physical entity or may not be an physically physically separate entity. It can be understood that the foregoing embodiment fifteenth is directed to the case where a plurality of terminal MME functional entities belong to one terminal MME physical entity.

 Similarly, the gateway function entity of multiple terminals of the terminal gateway may be in a physical entity of a separate terminal gateway, or may not be an physically separate entity.

Other similar modifications and variations to the present embodiments are also considered to be the scope of the present invention. It can be understood that the terminal path modification method described in the foregoing thirteenth embodiment to the fifteenth embodiment can be applied to handover in various scenarios. When the base station integrates or does not have an integrated relay gateway function, the foregoing method can be used. The change of the terminal path. In the above embodiment, the information of the multiple terminals is carried in both the path switching request message and the modified bearer request message. For ease of understanding, this will be exemplified below. If n path information is included in the path switch request message or the modify bearer request message, the n terminals may be respectively represented by UE1, UE2, UEn, and the information of the n terminals is represented by sl and s2 sn respectively. If the path switch request message or the modify bearer request message of a single terminal already includes the identifier of the terminal (for the sender and the receiver to identify the terminal to distinguish it from other terminals), then the n terminals are included. The path switch request message or the modify bearer request message, the receiver and the sender will be able to identify the information of each terminal. If the path switching request message or the modification bearer request message of a single terminal does not include the identifier of the terminal, in order to facilitate the receiving end (terminal MME or terminal gateway) of the information to separate the information of the terminal, the terminal may be added to the information. The identifiers, such as sl, s2 sn, may be 1, 2 n, or other numbers, such as the MME UE SIAP ID of the terminal, the eNB UE SIAP ID, or the IMSI or ME Identity, etc. limited. After receiving the path switch request message or modifying the bearer request message, the receiving end of the information may determine whether the information is the information of the subordinate terminal according to the number of each information. And the subordinates of these subordinates make path changes, that is, switch their transmission paths with these terminals from the original source base station to the target base station. In this way, when the terminal MME or the terminal gateway interacts with its terminal information, the corresponding information will pass through the target base station instead of the original base station. It can be understood that, in this embodiment, the information shared by the multiple terminals may be carried in the path switching request message or the modified bearer request message as an independent information, so that the shared information of multiple terminals does not need to be in each terminal. Repeatedly repeated in the information.

 16 is a schematic diagram of a handover processing method according to Embodiment 16 of the present invention, where the method includes:

 16 is a schematic diagram of a handover processing method according to Embodiment 16 of the present invention, where the method includes:

S161: The MRN sends a measurement report to the source base station.

S162: The source base station of the MRN sends a handover request message to the target base station according to the information of the measurement report, where the handover request message includes the gateway information of the MRN, that is, the source base station integrates the MRN. When the gateway function is used, the information required to perform the gateway function. Further, the handover request message may further include a destination address or an identifier (ie, an address or an identifier of the target base station) of the gateway function entity of the MRN after the MRN is switched, so that the relay gateway communicates with the target base station instead of Source base station.

 further,

 A) the message may further include: context information of the terminal of the MRN, so that the target base station can perform remapping of the terminal bearer between the target base station and the MRN by using the context information of the terminal in the process of establishing the bearer by the MRN. Of course, the content can be brought to the target base station using another message.

 B) The message may further include: a session context, the session context may include some policy information, carrying binding configuration information, charging information, and service layer entity address information. This information can be carried to the target side base station as, for example, a message called Session Redirection.

 Of course, the A) B) content can be brought to the target base station by using another message.

 S163: The target base station returns a handover request acknowledgement message to the source base station.

 S164: The source base station notifies the MRN to perform handover.

 S165: After the MRN handover is completed, notify the target base station that the handover has been completed.

 After receiving the handover command from the source base station, the MRN performs a synchronization process with the target base station and accesses the target cell.

 S166: After the MRN handover is completed and the target base station is successfully accessed, the target base station performs gateway relocation by using the received gateway information of the MRN, and provides a gateway function for the relay. Specifically, the gateway destination address of the MRN may be changed. It is the address or identifier of the target base station itself, so the gateway data from the MRN will flow to the target base station instead of the source base station.

In this step, it can be said that the function of the relay gateway entity in the source base station entity is transferred to the relay gateway entity of the target base station, and the relay gateway is changed, thereby the relay gateway entity in the target base station (or directly speaking to the target) The base station) will assign an IP address to the MRN. S167: The relay gateway function entity in the target base station allocates an IP address to the MRN. After the trunk gateway is changed, the new gateway of the MRN can assign a new IP address to the trunk. Specifically, the gateway entity (or the target base station) in the target base station may send the IP address allocated for the RN to the relay by the target base station through a specific message (such as a gateway address change message). The message includes the IP address assigned by the relay gateway to the relay; it can be understood that the relay gateway function entity in the target base station can assign the same IP address to the relay, or can maintain the existing IP address. The address does not change.

 S 168: The MRN receives the IP address change message and changes the IP address. Therefore, the MRN establishes a GTP tunnel with the gateway function entity ( Functionality) in the target base station, and the MRN can remap the bearer of the subordinate terminal to the GTP tunnel through the GTP tunnel. Of course, the gateway entity here is not a separate entity, but is integrated into the base station and is part of the base station function. It is described here as an entity only for ease of understanding. Optionally, the method further includes: S168, the MRN replies to the relay IP address change reply message, and confirms that the IP address is changed.

 S 169: The target base station notifies the relay MME to perform a change of the relay path (Path), that is, the target base station notifies the relay MME of the gateway information of the MRN, so that the relay MME changes the relay path. Specifically, the target base station sends a Path switch request message to the relay MME, and informs the MME that the relay has changed the cell, and the specific content in the message includes the parameters as described in Embodiment 6, Step S56. S1610: The relay MME sends a path change reply message after changing the relay path.

S1611: Perform radio resource reconfiguration between the target base station and the RN, and map the bearer of the relay subordinate terminal to the RN radio bearer. It can be understood that the relay radio bearer update and terminal bearer remapping process may also be included in the handover processing method of other embodiments.

S1612: Perform a path change process of the terminal between the target base station and the terminal MME and the terminal gateway. S1613: The source base station releases related resources of the MRN. After the target base station completes the gateway change, it uses After the switching between the user plane and the control plane, the source base station may release the related resources of the MRN. The related resource may also include gateway information of the MRN. The source base station can also release related information of the terminal of the MRN at the same time.

 In this embodiment, when the MRN is switched, the gateway is changed to the MRN, the target base station provides a gateway function for the relay, and the relay MME is notified to perform the relay path change, so that the path between the relay MME and the source base station is changed to The path between the relay MME and the target base station, and the path between the relay MME and the relay source GW are changed to the relay MME-relay new GW (ie, the gateway function entity integrated in the target base station, which is actually the target base station) ) between the paths. It can be understood that the above process execution sequence can be adjusted. For example, the relay IP allocation steps S167 and S168 can be performed simultaneously with the path change request steps S169 and S1610, or after S169 and S1610 are completed. In addition, S1611 is executed before S169 or S1610, which does not affect the implementation of this embodiment.

 FIG. 17 is a schematic diagram of a base station according to Embodiment 17 of the present invention, where the base station can implement a relay gateway function, and the base station 170 includes:

 The change module 171 is configured to: after the mobile relay node switches to the base station 170, change the gateway of the mobile relay node to the base station 170;

 The gateway module 172 is configured to provide a gateway function for the mobile relay node.

The base station 170 of this embodiment can implement gateway change after the MRN switches to itself. The base station 170 may further include: an allocation module, configured to allocate an IP address to the mobile relay node, and provide the IP address to the mobile relay node. Further, the base station 170 may include: an information receiving module, configured to receive gateway information of a mobile relay node provided by the source base station; the gateway module 172 is configured to use the gateway information of the mobile relay node as The mobile relay node provides gateway functionality. Further, the base station 170 may further include: a first notification module, configured to notify the relay mobility management entity to switch its gateway path to the base station 170. Further, the base station 170 may further include: a path switching module, configured to send a path switch request message to the terminal mobility management entity, where The path switch request message includes information of at least two terminals, and is used to request the terminal mobility management entity to switch the gateway path to the base station 170, where the at least two terminals belong to the terminal mobility management entity.

 The change module 171 can include: a change unit, configured to change a gateway destination address of the mobile relay node to the base station 170.

 In one application, the base station 170 can implement the relay PGW and SGW functions, and the change module 171 can be configured to: change the relay network gateway and the relay service gateway of the mobile relay node to the base station 170.

 In another application, the base station 170 can implement the relay PGW function, and the SGW function is not integrated in the base station 170, but serves as a separate gateway. Then, the change module 171 can be configured to: The relay network gateway of the relay node is changed to the base station 170; correspondingly, the base station 170 may further include: a second notification unit, configured to notify the relay service gateway of the mobile relay node that the relay service gateway will The gateway path is switched to the base station 170.

 FIG. 18 is a schematic diagram of a base station according to Embodiment 18 of the present invention. The base station 180 includes: a gateway function module 181, configured to provide a gateway function for a mobile relay node;

 The information providing module 182 is configured to provide the target base station with gateway information of the mobile relay node, to indicate that the target base station changes the relay gateway to the target base station after learning that the mobile relay node switches to the target base station.

 The base station 180 of this embodiment can perform the function of the mobile relay node gateway, and can provide the target base station with the gateway information of the mobile relay node, and prompt the target base station to perform the gateway change to implement the gateway function of the base station 180. The information providing module 182 can further include:

 a carrying unit, configured to carry the gateway information of the base station 180 in the handover request message when sending the handover request message to the target base station;

 Alternatively, the response unit is configured to provide gateway information of the mobile relay node 180 to the target base station after receiving the gateway change request of the target base station.

FIG. 19 is a schematic diagram of a base station according to Embodiment 19 of the present invention, where the base station 190 includes: The first sending module 191 is configured to send a path switch request message to the terminal MME, where the path switch request message includes information of at least two terminals, where the at least two terminals belong to the terminal MME, and the path switch request message Used to request the terminal MME to switch its gateway path to the base station 190;

 The first receiving module 192 is configured to receive a path switch response message sent by the terminal MME. The base station can implement path change of at least two terminals belonging to one terminal MME by using a path switch request message.

 FIG. 20 is a schematic diagram of a terminal MME according to Embodiment 20 of the present invention, where the terminal MME 200 includes:

 The second receiving module 201 is configured to receive a path switching request message, where the path switching request message includes information of at least two terminals, where the at least two terminals belong to the local end, and the path switching request message is used to request the local terminal. The MME 200 switches the gateway path to the target base station;

 The first change module 202 is configured to switch the gateway path of the terminal MME 200 to the target base station. Further, the local MME 200 may include: a second sending module 203, configured to send a path switch response message.

 The terminal MME 200 can receive a path switching request message, and can perform path switching on a plurality of terminals of the subordinate. The terminal MME 200 may further include: a determining module, configured to determine at least two terminals belonging to the same terminal gateway of the at least two terminals as a group; and a third sending module, configured to send a modify bearer request message to the group The terminal gateway of the terminal includes the information of the group of terminals in the modify bearer request message, to notify the terminal gateway user plane connection of the group of terminals to switch to the target base station.

 FIG. 21 is a schematic diagram of a terminal gateway according to a twenty-first embodiment of the present invention, where the terminal gateway 210 includes:

The third receiving module 211 is configured to receive a modify bearer request message, where the modify bearer request message includes information of at least two terminals, where the at least two terminals belong to the gateway 210, and the modify bearer request message is used to notify Switching the user plane connection to the target base station; a second change module 212, configured to switch the user plane connection to the target base station;

 The fourth sending module 213 is configured to reply to a modified bearer response message.

 The terminal gateway 210 can modify the bearer request message and change at least two terminal paths of the subordinate gateway to save signaling overhead.

 In the embodiment of the present invention, after the MRN is switched, many network entities need to perform gateway path change, and the target base station (including the relay gateway function or the relay PGW gateway function), the relay MME, the terminal MME, and the terminal gateway can pass various The signaling interaction performs path switching, that is, these network entities can switch the relay gateway address from the source base station to the target base station. Before the handover, the MRN and its subordinate terminals exchange data with the core network through the source base station. After the handover is completed, the MRN and its subordinate terminals can perform data interaction with the core network through the target base station because the relay gateway address has been changed.

 It can be understood that when the mobile node is a UE, the gateway change can also be implemented by a process similar to the previous method embodiment.

 FIG. 22 is a schematic diagram of a handover processing method according to Embodiment 22 of the present invention. The method includes: S221: A UE sends a measurement report to a source radio access network node (in the embodiment, a source base station is used as an example).

 S222: The source base station of the UE sends a handover request message to the target base station according to the information of the measurement report, where the handover request message includes the local route P-GW gateway information of the UE, that is, the source base station integrates the local route P- of the UE. The information required to perform the gateway function when the GW gateway function is enabled. Further, the handover request message may further include a destination address or identifier (ie, an address or identifier of the target base station) of the local route P-GW gateway function entity of the UE after the UE handover.

 S223: The target base station returns a handover request acknowledgement message to the source base station.

 S224: The source base station notifies the UE to perform handover.

After receiving the handover command of the source base station, the UE performs a synchronization process with the target base station and accesses the target cell. S225: After the UE handover is completed, notify the target base station that the handover has been completed.

 S226: After the UE completes the handover and successfully accesses the target base station, the target base station performs the gateway relocation by using the received local routing P-GW gateway information of the UE, and provides the local routing gateway function for the UE. Specifically, The gateway destination address of the UE is changed to the address or identifier of the target base station itself.

 In this step, it can be said that the UE local routing gateway entity function in the source base station entity is transferred to the UE local routing gateway entity of the target base station, and the relay gateway is changed, thereby the UE local routing gateway entity in the target base station (or Directly speaking the target base station) will assign a new IP address to the UE.

 S227: The UE local routing gateway function entity in the target base station allocates an IP address to the UE. Due to the change of the trunking gateway, the UE's new gateway can assign a new IP address to the trunk. Specifically, the gateway entity (or the target base station) in the target base station may send the IP address to the UE by the target base station through a specific message (such as a gateway address change message). The message includes the IP address assigned by the relay gateway to the relay. It can be understood that the relay gateway function entity in the target base station can assign the UE an IP address identical to the original IP address, or can maintain the existing UE. The IP address does not change.

 S228: The UE receives the IP address change message and performs an IP address change. Thereby, the UE can initiate a service (for example, web) to the external network (for example, the Internet) through a local routing gateway function entity ( Functionality) in the target base station. Of course, the gateway entity here is not a separate entity, but is integrated within the base station and is part of the base station function, which is described here as an entity only for ease of understanding. Optionally, the method further includes: S228, the UE replies to the IP address change reply message, and confirms that the IP address is changed.

S229: The target base station notifies the MME of the UE to perform a change of the terminal path (Path), that is, the target base station notifies the MME of the UE of the local routing gateway information of the UE, so that the MME changes the path. Specifically, the target base station sends a Path switch request message to the terminal MME. The MME is notified that the UE has changed the cell, and the specific content in the message includes parameters as described in Embodiment 5 and Step S56.

S2210: The MME of the UE sends a path change reply message after making a change to the terminal path.

S2211: Perform bearer update between the target base station (HeNB) and the UE, and remap the EPS bearer of the terminal to the radio bearer of the UE after the target base station is updated.

 S2212: Policy execution and charging entity of the target base station (HeNB) and the UE MME and the UE

The process of changing the local routing gateway of the UE is performed between (PCRF). That is, the target base station notifies the PCRF to change the UE local routing gateway to the target base station, so that the path of the PCRF switches the target base station, so that the PCRF interacts with the target and the station.

 In this embodiment, when the UE is handed over, the UE implements the gateway change of the local routing gateway, and the target base station provides the local routing gateway function for the UE, and notifies the MME of the UE to perform the terminal path update, so that the UE MME and the source base station are The path is changed to the path between the UE MME and the target base station, and the path between the UE MME and the UE source local routing gateway is changed to the UE MME-local routing new GW (ie, the gateway function entity integrated in the target base station, which is actually the target The path between the base stations). It can be understood that the above process execution order can be adjusted.

 In order to improve the efficiency of the embodiment 22, the embodiment 23 connects the gateway update function message to the handover message. FIG. 23 is a schematic diagram of a handover processing method according to the twenty-third embodiment of the present invention. The method includes:

S231: The UE sends a measurement report to the source radio access network node (taking the source base station as an example).

S232: The source base station of the UE sends a handover request message to the target base station according to the information of the measurement report, where the handover request message includes the local route P-GW gateway information of the UE, that is, the source base station integrates the local route P- of the UE. The information required to perform the gateway function when the GW gateway function is enabled. Further, the handover request message may further include a destination address or identifier (ie, an address or identifier of the target base station) of the local routing P-GW gateway function entity of the UE after the UE is handed over, so as to enable the local route of the UE. The gateway is communicating with the target base station instead of the source base station. S233: The target base station local routing gateway function is that the UE pre-allocates the IP address and the session update information on the target side.

 S234: The target base station sends a handover request acknowledgement message to the source base station, and carries the IP address and session update information allocated by the target side to the UE.

 S235: The source base station notifies the UE to perform handover, and carries the IP address and session update information allocated by the target side to the UE.

 S236: The UE first updates the session context and gateway information saved by itself according to the IP address and session update information allocated by the target side base station.

 S237: The UE notifies the target base station that the handover has been completed by concatenating the session update completion and the gateway update completion message in the UE handover completion message.

 After receiving the handover command of the source base station, the UE performs a synchronization process with the target base station and accesses the target cell.

 S238: After the UE handover is completed and the target station is successfully accessed, the target station confirms that the UE has successfully completed the gateway update, and the target base station uses the received local route P-GW gateway information of the UE to perform gateway relocation to provide the UE with the relocation. The local routing gateway function, in particular, may change the gateway destination address of the UE to the address or identifier of the target base station itself.

 In this step, it can be said that the UE local routing gateway entity function in the source base station entity is transferred to the UE local routing gateway entity of the target base station, and the relay gateway is changed, thereby the UE local routing gateway entity in the target base station (or Directly speaking the target base station) will assign a new IP address to the UE.

 Thereby enabling the UE to pass through the local routing gateway functional entity in the target base station

( Functionality ) initiates a business ( ^ column ^ port web ) on the eve network ( ^ column ^ port Internet ). When, of course, the gateway entity here is not a separate entity, but is integrated within the base station as part of the base station function, which is described here as an entity only for ease of understanding.

S239: The target eNB notifies the MME of the UE to perform a change of the path of the terminal (Path), that is, the target base station notifies the MME of the UE of the local routing gateway information of the UE, so that the MME pairs the path. Make changes. Specifically, the target base station sends a Path switch request message to the MME to notify the MME that the UE has changed the cell, and the specific content in the message is as described in Embodiment 5, Step S56.

S2310: The relay MME sends a path change reply message after the UE path is changed. S2311: Perform bearer update between the target base station (HeNB) and the UE, and remap the EPS bearer of the terminal to the radio bearer of the UE after the target base station is updated.

 S2312: Policy execution and charging entity of the target base station (HeNB) and the UE MME and the UE

The process of changing the local routing gateway of the UE is performed between (PCRF).

 In this embodiment, when the UE is handed over, the UE implements the gateway change of the local routing gateway, and the target base station provides the local routing gateway function for the UE, and notifies the MME of the UE to perform the relay path update, so that the UE MME and the source base station are The path is changed to the path between the UE MME and the target base station, and the path between the UE MME and the UE source local routing gateway is changed to the UE MME-local routing new GW (ie, the gateway functional entity integrated in the target base station, which is actually The path between the target base stations).

 It can be understood that the difference between the embodiment 23 and the embodiment 22 is that there is a process of pre-allocating a target gateway IP address in S233, that is, the target base station can allocate an IP address to the UE at this time. Further, the target base station may also allocate session update information to the UE. It can be understood that the present embodiment is directed to the UE handover, and the method for pre-assigning the IP address may be used in the process of the MRN handover, so that the target base station allocates an IP address to the MRN in advance, which is not limited in this embodiment. In summary, steps 231-2311 also apply to relay switching scenarios.

A person skilled in the art can understand that all or part of the processes in the above method embodiments can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium, and the program is executed. At the time, the flow of the embodiment of each of the above methods may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM). The above is only a preferred embodiment of the present invention, and it should be noted that those skilled in the art can make several improvements and modifications to the above embodiments without departing from the principles of the invention.

Claims

Claim A switching processing method, comprising:  After the mobile node switches to the target base station, the gateway of the mobile node is changed to the target base station;  The target base station provides a gateway function for the mobile node.  2. The method according to claim 1, further comprising:  Assigning an IP address to the mobile node and providing the IP address to the mobile node.  The method according to claim 2, wherein the mobile node is a relay node, and further includes:  Radio resource reconfiguration is performed between the target base station and the relay node, and the bearer of the terminal is mapped to the radio bearer of the relay node.  4. The method according to claim 1, further comprising:  Receiving gateway information of the mobile node provided by the source base station;  The providing, by the target base station, the gateway function for the mobile node includes: the target base station providing the mobile node with a gateway function by using the gateway information of the mobile node.  5. The method according to claim 1, further comprising:  The mobility management entity informing the mobile node switches the gateway path of the mobility management entity to the target base station.  The method according to claim 5, wherein the notifying the mobility management entity of the mobile node to switch the gateway path of the mobility management entity to the target base station comprises:  Notifying the mobility management entity of the mobile node to change a path between the mobility management entity of the mobile node and the mobile node gateway to a path between the mobility management entity of the mobile node and a new gateway of the mobile node; Notifying the mobility management entity of the mobile node to change a path between the mobility management entity of the mobile node and the source base station to be between the mobility management entity of the mobile node and the target base station Path.  The method according to any one of claims 1 to 6, wherein the changing the gateway of the mobile node to the target base station comprises: transferring part of the gateway function of the mobile node to the target base station .  The method according to any one of claims 1 to 6, wherein the mobile node is a terminal, and after the gateway of the terminal is changed to the target base station, the method further includes:  The notification policy and charging entity updates the local routing gateway to the target base station.  9. The method according to claim 1, further comprising: the mobile node being a relay node or a terminal.  10. A base station, comprising:  a change module, configured to: after the mobile node switches to the base station, change the gateway of the mobile node to the base station;  a gateway module, configured to provide a gateway function for the mobile node.  The base station according to claim 10, further comprising: an allocation module, configured to allocate an IP address to the mobile node, and provide the IP address to the mobile node.  The base station according to claim 10 or 11, further comprising: an information receiving module, configured to receive gateway information of the mobile node provided by the source base station;  Accordingly, the gateway module is configured to provide gateway functionality to the mobile node using gateway information of the mobile node.  13. A method for changing a terminal path, which is characterized by comprising:  Receiving a path switch request message, where the path switch request message includes information of at least two terminals, where the at least two terminals belong to a terminal mobility management entity, and the path switch request message is used to request that the terminal move management entity The terminal path is switched to the target base station;  Switching the terminal path of the terminal mobility management entity to the target base station. 14. The method according to claim 13, further comprising: Determining, by the at least two terminals, the at least two terminals belonging to the same terminal gateway as one group;  Sending a modify bearer request message to the terminal gateway of the group terminal, the modify bearer request message includes information of the group of terminals, to notify the terminal gateway to switch the user plane connection to the target base station.  15. A terminal mobility management entity, comprising:  a second receiving module, configured to receive a path switching request message, where the path switching request message includes information of at least two terminals, where the at least two terminals belong to the terminal mobility management entity, and the path switching request message is used by Requesting to switch the terminal path of the terminal mobility management entity to the target base station;  And a first change module, configured to switch a terminal path of the mobility management entity to the target base station.  The terminal mobility management entity according to claim 15, further comprising: a determining module, configured to determine at least two terminals belonging to the same terminal gateway of the at least two terminals as a group;  And a third sending module, configured to send a modify bearer request message to the terminal gateway of the group of terminals, where the modify bearer request message includes information about the group of terminals, to notify the terminal gateway to switch the user plane connection to the target base station.  17. A method for changing a terminal path, comprising:  Receiving a modify bearer request message, where the modify bearer request message includes information of at least two terminals, the at least two terminals belong to one gateway, and the modify bearer request message is used to notify that the user plane connection is switched to the target base station;  Switch the user plane connection to the target base station.  18. A gateway, comprising: a third receiving module, configured to receive a modify bearer request message, where the modify bearer request message includes information of at least two terminals, where the at least two terminals belong to the gateway, and the modify bearer request The message is used to notify that the user plane connection is switched to the target base station; and the second change module is configured to switch the user plane connection to the target base station.