Patent Description:
Examples of the present disclosure relate to the communications field, and in particular, to a handover method, a terminal device, a computer readable storage medium and a computer program product.

Two connection modes may exist between user equipment (User Equipment, UE) and a network device. In a first connection mode, the UE is directly connected to the network device to perform data communication. This is a direct communication mode. In a second connection mode, first UE is connected to the network device by using second UE, to perform data communication. This is an indirect communication mode. In this case, the first UE may be referred to as remote UE, and the second UE may be referred to as relay UE.

In Rel-<NUM> in a long term evolution (Long Term Evolution, LTE) system, the 3rd generation partnership project (3rd Generation Partnership Project, 3GPP) studies and standardizes a function of relay UE. In Rel-<NUM>, the relay UE forwards communication data between remote UE and a network device through an IP layer (layer <NUM>).

However, when the communication data between the remote UE and the network device is forwarded through the Internet protocol (Internet Protocol, IP) layer of the relay UE, the following problems arise. A first problem is about data security. A packet data convergence protocol (Packet Data Convergence Protocol, PDCP) layer of the relay UE can obtain data of the remote UE through decompression, and therefore security of the data of the remote UE cannot be ensured on the relay UE. A second problem is about service continuity. When the remote UE switches a path, service continuity cannot be ensured. A third problem is that the network device cannot differentiate between data of the remote UE and data of the relay UE.

To resolve the foregoing problems, the relay UE may forward data by using a layer <NUM>. The layer <NUM> is a layer above a radio link control (Radio Link Control, RLC) layer and below the PDCP layer. This is also a current research topic in LTE Rel-<NUM>. In this case, the remote UE may be referred to as evolved remote UE, and the relay UE may be referred to as evolved relay UE (or referred to as an evolved UE-to-network relay).

When being connected to the network device by using the evolved relay UE, the evolved remote UE moves together with the evolved relay UE. When the evolved remote UE and the evolved relay UE move from one cell to another cell, inter-cell handover needs to be performed at the same time.

<FIG> is a schematic flowchart showing that evolved remote UE and evolved relay UE are handed over from a source base station to a target base station in the prior art. The evolved remote UE needs to be first disconnected from the evolved relay UE, to be specific, switches a path from a trunk link to a cellular link, and then performs an inter-cell handover process. After handover is completed, the evolved remote UE performs a process of path switching from the cellular link to the trunk link again.

In the foregoing process, the evolved remote UE needs to perform two path switching processes and one handover process, resulting in high signaling overheads, and high power consumption in the handover process.

Document <CIT> relates to a method and an apparatus for transmitting an indication in a wireless communication system, wherein a source donor DeNB A transmits a first handover request message for a mobile relay node to a target DeNB B and transmits a second handover request message for several user equipments, UEs, which is attached to the mobile relay node, to a target eNB C. The source donor DeNB A transmits an indication including information on lists of UEs, which can be handed over to the target DeNB B or eNB C, to the mobile relay node and the mobile relay node transmits a radio resource control connection reconfiguration message indicating a UE to handover to the target DeNB B or eNB C. According to this document, the source donor DeNB A transmits an indication including information on lists of UEs which can be handed over to the target eNB C. The lists of UEs which can be handed over to the target eNB C may be lists of UEs which are allowed to be handed over to the target eNB C by the second handover request ACK message. Alternatively, the lists of UEs which can be handed over to the target eNB C may be lists of UEs which are decided to be hand over to the target eNB C by the source DeNB A after receiving the second handover request ACK message.

The present invention provides a handover method according to independent claim <NUM> to resolve a problem of high signaling overheads and high power consumption when evolved remote UE and evolved relay UE are handed over. Furthermore, a computer readable storage medium, a terminal device configured to perform the method and a computer program product according to independent claims <NUM>-<NUM>, respectively, are provided. The scope of the invention is provided by the appended set of claims. In particular, embodiments of the invention is provided by the dependent claims. In the following, parts of the description and drawings referring to examples or implementations which are not covered by the claims are not presented as embodiments of the invention, but as examples useful for understanding the invention.

To make the objectives, technical solutions, and advantages of the present disclosure clearer, the following further describes the present disclosure in detail with reference to the accompanying drawings. Apparently, the described examples are merely some rather than all of the examples of the present disclosure.

In the specification, claims, and accompanying drawings of this disclosure, the terms "first", "second", and so on are intended to distinguish between different objects but do not indicate a particular order. In addition, the terms "including" and "having" and any other variants thereof are intended to cover a non-exclusive inclusion. For example, a process, a method, a system, a product, or a device that includes a series of steps or units is not limited to the listed steps or units, but optionally further includes an unlisted step or unit, or optionally further includes another inherent step or unit of the process, the method, the product, or the device.

A handover method in an example of the present disclosure is applicable to a plurality of system architectures. <FIG> is a schematic diagram of a system architecture to which an example of the present disclosure is applicable. As shown in <FIG>, the system architecture includes a network device <NUM> and one or more terminals, such as a first terminal <NUM>, a second terminal <NUM>, and a third terminal <NUM> shown in <FIG>. The first terminal is a relay terminal. The second terminal <NUM> and the third terminal <NUM> may transmit information with the network device <NUM> by using the network device <NUM>. Further, the first terminal <NUM>, the second terminal <NUM>, and the third terminal <NUM> may transmit information to each other.

In this example of the present disclosure, the network device includes but is not limited to a NodeB NodeB, an evolved NodeB eNodeB, a base station in a 5th-generation (the 5th-generation, <NUM>) communications system, a base station in a future communications system, an access node in a Wi-Fi system, a wireless relay node, a wireless backhaul node, and UE. The base station is an apparatus deployed in a radio access network to provide a wireless communication function. For example, a device that provides a base station function in a <NUM> network includes a base transceiver station (base transceiver station, BTS) and a base station controller (base station controller, BSC). A device that provides a base station function in a <NUM> network includes a NodeB (NodeB) and a radio network controller (radio network controller, RNC). A device that provides a base station function in a <NUM> network includes an evolved NodeB (evolved NodeB, eNB). A device that provides a base station function in a <NUM> network includes a new radio NodeB (New Radio NodeB, gNB), a centralized unit (Centralized Unit, CU), a distributed unit (Distributed Unit), and a new radio controller. In a WLAN, a device that provides a base station function is an access point (Access Point, AP).

The terminal may be a device (device) providing voice and/or data connectivity for a user, and may include a wireless terminal and a wired terminal. The wireless terminal may be a handheld device having a wireless connection function, or another processing device connected to a wireless modem. The terminal communicates with one or more core networks through a radio access network (radio access network, RAN), or may access a distributed network in a self-organizing manner or a grant free manner, or may access a wireless network in another manner to perform communication. Alternatively, the terminal may directly perform wireless communication with another terminal, or the terminal may directly perform wireless communication with another terminal. For example, the terminal may be a mobile phone, a computer, a tablet computer, a personal digital assistant (Personal Digital Assistant, PDA), a mobile Internet device (Mobile Internet Device, MID), a wearable device, an e-book reader (e-book reader), or the like. For another example, the wireless terminal may be a portable, pocket-sized, handheld, computer built-in, or in-vehicle mobile device. For still another example, the wireless terminal may be a mobile station (Mobile Station), an access point (Access Point), or a part of UE.

A communications system to which the foregoing system architecture is applicable includes but is not limited to a code division multiple access (Code Division Multiple Access, CDMA) IS-<NUM> system, a code division multiple access (Code Division Multiple Access, CDMA) <NUM> system, a time division-synchronous code division multiple access (Time Division-Synchronous Code Division Multiple Access, TD-SCDMA) system, a wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, a time division duplexing-long term evolution (Time Division Duplexing-Long Term Evolution, TDD LTE) system, a frequency division duplexing-long term evolution (Frequency Division Duplexing-Long Term Evolution, FDD LTE) system, a long term evolution advanced (Long Term Evolution Advanced, LTE-Advanced) system, and various future evolved wireless communications systems (such as a <NUM> system).

Based on the foregoing system architecture, in an application scenario of this example of the present disclosure, a first network device is the network device <NUM>, first UE is the first terminal <NUM>, and second UE is any one or a combination of the second terminal <NUM> and the third terminal <NUM>.

When the first network device, the first UE, and the second UE communicate with each other, a control plane protocol stack is shown in <FIG> and <FIG>, and a user plane protocol stack is shown in <FIG> and <FIG>.

The first UE and the second UE in this example of this disclosure may be deployed on land, for example, may be indoor, outdoor, handheld, or in-vehicle, or may be deployed on water, or may be deployed on an airplane, a balloon, and a satellite in the sky. The UE in this example of this disclosure may be a mobile phone, a tablet computer (Pad), a computer with a wireless receive/transmit function, a virtual reality (Virtual Reality, VR) terminal device, an augmented reality (Augmented Reality, AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in telemedicine (remote medical), a wireless terminal in a smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in a smart city (smart city), a wireless terminal in a smart home (smart home), or the like. The application scenario is not limited in this example of this disclosure.

The following uses examples to describe a process in which the first UE and the second UE are handed over from the first network device to a second network device or a third network device. <FIG> and <FIG> are a schematic diagram of a control plane protocol stack when the first network device, the first UE, and the second UE communicate with each other, and <FIG> and <FIG> are a schematic diagram of a user plane protocol stack when the first network device, the first UE, and the second UE communicate with each other.

<FIG> is a schematic flowchart of a handover method according to an example of the present disclosure. As shown in <FIG>, the handover method <NUM> includes the following steps:.

When the first UE needs to be handed over, the second UEs in the RRC connected mode that keep a short-distance communication connection to the first UE may be classified into the following two types.

A first type of second UE is still connected to the second network device by using the first UE after the first UE is handed over.

A second type of second UE is no longer connected to the second network device by using the first UE after the first UE is handed over. In this case, for example, the second UE may be connected to the second network device or the third network device over a direct link.

When the first UE is handed over, if there are still several second UEs connected to the second network device by using the first UE, when the first UE is handed over, there are four cases:.

With reference to <FIG> and <FIG>, the following further describes <FIG> by using interaction among the first UE, the second UE, the first network device, and the second network device as an example. <FIG> and <FIG> are a diagram of interaction among the first UE, the second UE, the first network device, and the second network device according to an example of the present disclosure. Second UE <NUM> is the second type of second UE, and second UE <NUM> is the first type of second UE.

Step <NUM>: The first UE sends a measurement report to the first network device.

When the second UE communicates with the first network device by using the first UE, the first UE reports a Uu link (uplink or downlink) measurement result to the first network device. The measurement result may include information about a neighboring cell, and the information about the neighboring cell may include signal strength of the neighboring cell, signal quality of the neighboring cell, or the like.

Step <NUM>: The first network device sends a handover request message to the second network device.

The first network device determines the second network device based on the measurement result. For example, the first network device may determine, based on the signal quality of the neighboring cell, a target cell in which the second network device is located, and determine the second network device in the target cell based on information such as a priority, a capacity, and load of a base station in the target cell.

After determining the second network device, the first network device sends the handover request message to the second network device, and the handover request message includes context information of the first UE and the second UE, for example, first identifier information, a key, and the like of the first UE, and first identifier information, a key, and the like of the second UE. There may be one or more handover request messages. When there are a plurality of handover request messages, each handover request message corresponds to one UE.

Step <NUM>: The second network device sends a handover response message to the first network device.

The first network device receives the handover response message sent by the second network device. The handover response message may include at least one of a device identifier of the first UE, identifier information of second UE accepted by the second network device, and a device identifier of second UE that is not accepted by the second network device. The device identifier of the first UE is different from the first identifier information. There may be one or more handover response messages. When there are a plurality of handover response messages, each handover acknowledgement message corresponds to one UE.

Step <NUM>: The first UE receives a first radio resource reconfiguration message and M second radio resource reconfiguration messages, where the first radio resource reconfiguration message and the M second radio resource reconfiguration messages are sent by the first network device.

The first radio resource reconfiguration message includes a first handover command, the first handover command is used to instruct to hand over the first UE from the first network device to the second network device, the second radio resource reconfiguration message includes a second handover command, the second handover command is used to instruct to hand over the second UE from the first network device to a third network device, M is a quantity of second UEs in an RRC connected mode that are connected to the first UE, and the second network device is the same as or different from the third network device.

Further, the first radio resource reconfiguration message includes first information, and the first information includes at least one of first indication information and second indication information.

The first indication information is used to indicate second UE connected to the second network device by using the first UE after the first UE is handed over to the second network device, a quantity of second UEs connected to the second network device by using the first UE is X, and X is an integer that is not greater than M.

The second indication information is used to indicate second UE that is connected to the second network device not by using the first UE after the first UE is handed over to the second network device, and a quantity of second UEs that are connected to the second network device not by using the first UE is M-X.

The first indication information or the second indication information is specifically a device identifier of the second UE. For example, the device identifier is UE*, where * is a number of the second UE. When M is <NUM>, if the first information includes only the first indication information, for example, (UE2, UE3, and UE4), it indicates that all second UEs are connected to the second network device by using the first UE, in other words, X is <NUM>. If the first information includes only the second indication information, for example, (UE2, UE3, and UE4), it indicates that all second UEs are connected to the second network device not by using the first UE, in other words, X is <NUM>. If the first information includes the first indication information (UE2) and the second indication information (UE3 and UE4), it indicates that the UE2 is connected to the second network device by using the first UE, in other words, X is <NUM>, and the UE3 and the UE4 are connected to the second network device not by using the first UE.

Further, when a short-distance communication link between the first UE and the second UE is connected over a sidelink, the first radio resource reconfiguration message includes second information, and the second information includes a configuration of a resource or a resource pool used to send the second radio resource configuration message over the sidelink.

Further, before step <NUM>, the method includes a step of generating, by the first network device, the first radio resource reconfiguration message and the second radio resource reconfiguration messages. A first RLC service data unit (Service Data Unit, SDU) and a second RLC SDU are generated by different protocol entities in the first network device. Therefore, the first radio resource reconfiguration message is included in the first RLC SDU, and the second radio resource reconfiguration messages are included in second RLC SDUs. The first RLC SDU and at least one of the M second RLC SDUs are included in one RLC protocol data unit (Protocol Data Unit, PDU).

The following describes a process about how protocol entities in the first network device generate the RLC PDU, the first RLC SDU, and the second RLC SDU.

<FIG> is a schematic diagram showing that the first network device generates the RLC PDU, the first RLC SDU, and the second RLC SDU. As shown in <FIG>, after receiving the handover response message sent by the second network device, an RRC layer of the first network device separately generates the first handover command sent to the first UE and the second handover command sent to the second UE. Then, the RRC layer sends the first handover command to a PDCP entity that is configured to transmit a signaling radio bearer (Signaling Radio Bearer, SRB) of the first UE and that is to process the first handover command, and the RRC layer sends the second handover command to a PDCP entity that is configured to transmit an SRB of the second UE and that is to process the second handover command. The processing herein is mainly performing header compression on protocols of convergence protocols in the first handover command and the second handover command, to separately generate PDCP protocol data units (Protocol Data Unit, PDU). Subsequently, each PDCP entity sends a generated PDCP PDU to an adaptation (Adaptation) layer for processing. In this case, the processing is performing encryption by adding second identifier information. After the processing, the adaptation layer sends each encrypted PDCP PDU to a common RLC entity. Then, the RLC entity encapsulates an RLC SDU corresponding to the PDCP PDU into an RLC PDU. Finally, the first network device sends the RLC PDU to the first UE.

After the RLC PDU is received, an RLC entity that is of the first UE and that is configured to receive an SRB <NUM> sends the first RLC SDU and the second RLC SDU in the RLC PDU to the adaptation layer. The adaptation layer respectively submits a PDCP PDU corresponding to the first RLC SDU and a PDCP PDU corresponding to the second RLC SDU to corresponding protocol layers based on a device identifier of the first RLC SDU and a device identifier of the second RLC SDU. To be specific, the PDCP PDU corresponding to the first RLC SDU is sent to a PDCP entity of the first UE, and the PDCP PDU corresponding to the second RLC SDU is sent to an uppermost protocol layer used to process data of the second UE over a short-distance link.

When the first UE and the second UE are connected over the short-distance link by using a PC5 technology/sidelink technology, the uppermost protocol layer is correspondingly an RLC layer of the second UE, as shown in <FIG>.

When the first UE and the second UE are connected over the short-distance link by using a non-3GPP technology, the uppermost protocol layer is correspondingly an adaptation layer of the second UE, as shown in <FIG>.

Before the first UE is handed over from the first network device to the second network device, the method further includes step <NUM> and step <NUM>.

Step <NUM>: The first UE sends the second radio resource reconfiguration message to the second UE.

Step 550a: The first UE sends a second radio resource reconfiguration message to the second type of second UE. Step 550b: The first UE sends a second radio resource reconfiguration message to the first type of second UE. Optionally, after step <NUM>, the method further includes:.

In this example, the first UE may be handed over after the first UE sends the second radio resource reconfiguration message to the second UE. In a next example, referring to <FIG> and <FIG>, the first UE may be alternatively handed over before the first UE sends the second radio resource reconfiguration message to the second UE.

For a specific time when the first UE is handed over from the first network device to the second network device, there are two cases.

In a first case, the first UE sends the second radio resource reconfiguration message to the second UE; and the first UE is handed over from the first network device to the second network device after the first UE completes sending the M second radio resource reconfiguration messages.

After an uppermost protocol layer used to process data of each second UE over a short-distance link sends a PDCP PDU that corresponds to a second radio resource reconfiguration message and that needs to be forwarded to the second UE, the uppermost protocol feeds back indication information to an RRC layer of the first UE, based on processing manners in <FIG> and <FIG>. In other words, after an uppermost protocol layer used to process data of each second UE over a short-distance link sends a PDCP PDU corresponding to a second RLC SDU including a second radio resource reconfiguration message, the uppermost protocol feeds back indication information to an RRC layer of the first UE.

After the RRC layer of the first UE determines that sending all PDCP PDUs corresponding to the M second radio resource reconfiguration messages is completed, the RRC layer of the first UE initiates a process of handover to the second network device. <FIG> is a first schematic diagram showing that an entity in second UE processes a second radio resource reconfiguration message.

Further, after the first UE sends the second radio resource reconfiguration message to the second UE, the first UE suspends transmission and reception of data on a radio bearer over the short-distance communication link between the first UE and the second UE.

When the first UE and the second UE are connected over the short-distance link by using a sidelink technology, the first UE suspends processing on an RLC entity on the radio bearer over the short-distance communication link between the first UE and the second UE, and suspends transmission and reception of bottom-layer data. When the first UE and the second UE are connected over the short-distance link by using a non-3GPP technology, the first UE suspends processing on an adaptation layer on the radio bearer over the short-distance communication link between the first UE and the second UE, and suspends transmission and reception of bottom-layer data.

In a second case, the first UE sends the second radio resource reconfiguration message to the second UE; the first UE receives the indication information that is fed back by the second UE and that indicates that the second radio resource reconfiguration message is successfully received; and after the first UE receives M pieces of indication information, the first UE is handed over from the first network device to the second network device.

An uppermost protocol layer used to process data of each second UE over a short-distance link sends a PDCP PDU corresponding to a second radio resource reconfiguration message to the corresponding second UE, based on processing manners in FIG. 6a and FIG. In other words, an uppermost protocol layer used to process data of each second UE over a short-distance link first sends a PDCP PDU corresponding to a second RLC SDU unit including a second radio resource reconfiguration message. Then the uppermost protocol layer receives indication information that is fed back by the second UE and that indicates that the second radio resource reconfiguration message is successfully received. In other words, the uppermost protocol layer receives indication information that is fed back by the second UE and that indicates that the second RLC SDU including the second radio resource reconfiguration message is successfully received. Finally, the uppermost protocol layer feeds back an indication to an RRC layer of the first UE.

After the RRC layer of the first UE determines that M pieces of indication information that are fed back by the second UE and that indicate that the second radio resource reconfiguration messages are successfully received are received, the first UE starts to be handed over from the first network device to the second network device. <FIG> is a second schematic diagram showing that an entity in second UE processes a second radio resource reconfiguration message.

Step <NUM>: The first UE sends a random access preamble sequence.

Step <NUM>: The first UE receives a random access response message sent by the second network device.

Step <NUM>: The first UE sends an RRC connection reconfiguration complete (Connection Reconfiguration Complete, CRC) message to the second network device.

Further, after the first UE receives the indication information that is fed back by the second UE and that indicates that the second radio resource reconfiguration message is successfully received, the first UE suspends transmission and reception of data on a radio bearer over the short-distance communication link between the first UE and the second UE.

When the first UE and the second UE are connected over the short-distance link by using a sidelink technology, the first UE suspends processing on an RLC entity on the radio bearer over the short-distance communication link between the first UE and the second UE, and suspends transmission and reception of bottom-layer data.

When the first UE and the second UE are connected over the short-distance link by using a non-3GPP technology, the first UE suspends processing on an adaptation layer on the radio bearer over the short-distance communication link between the first UE and the second UE, and suspends transmission and reception of bottom-layer data.

The following describes processing on a protocol stack when the first UE is being handed over.

When the first UE is handed over from the first network device to the second network device, the first UE needs to reset a media access control (Media Access Control, MAC) layer, and re-establish RLC entities and PDCP entities of radio bearers over all Uu links. In addition, the first UE further needs to process a protocol stack over the short-distance communication link between the first UE and the second UE. Specifically:.

When the first UE and the second UE are connected over the short-distance link by using a sidelink technology, the first UE re-establishes a radio link control entity corresponding to each second UE over the sidelink. Specific processing includes: discarding all RLC SDUs and/or RLC PDUs buffered on all RLC entity sending sides, discarding all RLC PDUs that have been received on all RLC entity receiving sides, stopping and resetting all timers, and resetting all status variables.

When the first UE and the second UE are connected over the short-distance link by using a non-3GPP technology, the first UE re-establishes an adaptation layer entity corresponding to each second UE over the non-3GPP link. Specific processing includes: clearing an SDU and/or a PDU buffered by the adaptation layer entity, stopping and resetting all timers if existent, and resetting all status variables if existent.

The following describes a processing process after the second UE receives the second radio resource reconfiguration messages.

When the second UE is of the second type, to be specific, when the second UE is no longer connected to the second network device by using the first UE after the first UE is handed over, the second UE is handed over to the second network device or the third network device by using the prior art. The second UE processes a short-distance link connection in two implementations.

In a first implementation, after receiving the second radio resource reconfiguration message, the second UE immediately disconnects the short-distance link between the second UE and the first UE. The second UE may disconnect the short-distance link between the second UE and the first UE by sending a short-distance link connection release message to the first UE.

In a second implementation, after handover of the second UE to the second network device or the third network device is completed, the second UE disconnects the short-distance link between the second UE and the first UE. When the second UE is of the first type, to be specific, when there is second UE connected to the second network device by using the first UE after the first UE is handed over, the second UE processes a short-distance link connection in two implementations.

In a first implementation, after receiving the second radio resource reconfiguration message, the second UE suspends transmission and reception of the data on the radio bearer over the short-distance communication link between the second UE and the first UE.

After the second UE receives a first message, namely, a short-distance link communication restoration instruction message, sent by the first UE, the second UE re-establishes a radio bearer over the short-distance communication link between the second UE and the first UE, and resumes transmission and reception of data on the radio bearer over the short-distance communication link between the second UE and the first UE.

That the second UE re-establishes a radio bearer over the short-distance communication link between the second UE and the first UE specifically includes:.

In a second implementation, after the second UE receives the second radio resource reconfiguration message, the second UE re-establishes a radio bearer over the short-distance communication link between the second UE and the first UE, and suspends transmission and reception of the data on the radio bearer over the short-distance communication link between the second UE and the first UE. After the second UE receives a first message, namely, a short-distance link communication restoration instruction message, sent by the first UE, the second UE resumes transmission and reception of data on the radio bearer over the short-distance communication link between the second UE and the first UE. A manner in which the second UE re-establishes the radio bearer over the short-distance communication link between the second UE and the first UE is the same as a manner used by the first type of second UE in the first implementation, and details are not described herein again.

Step <NUM> is performed after step <NUM>.

Step <NUM>: The first UE sends a short-distance link communication restoration instruction message to the second UE.

The first UE performs the following process:
The first UE sends the short-distance link communication restoration instruction message to the first type of second UE, and the short-distance link communication restoration instruction message is used to instruct the second UE to resume transmission and reception of the data on the radio bearer over the short-distance link between the second UE and the first UE.

When the first UE and the second UE are connected over the short-distance link by using a sidelink technology, the short-distance link communication restoration instruction message is a message generated by a PC5-S protocol layer. When the first UE and the second UE are connected over the short-distance link by using a non-3GPP access technology, the short-distance link communication restoration instruction message is a message generated by a PC5-S protocol layer, a message generated by an adaptation layer, or a message generated by an RRC layer.

The second UE performs the following process:
After receiving the short-distance link communication restoration instruction message, the first type of second UE resumes transmission and reception of the data on the radio bearer over the short-distance link between the second UE and the first UE. For specific processing, refer to processing performed by the second UE after the second UE receives the second radio resource reconfiguration message in step 550a/550b.

Step <NUM>: The second UE sends an RRC CRC message to the second network device.

Step 5110a: The second type of second UE sends an RRC CRC message to the second network device.

When the third network device exists, the second type of second UE sends the RRC CRC message to the third network device at the same time.

Step <NUM>110b: The first type of second UE sends an RRC CRC message to the second network device.

The first type of second UE sends the RRC CRC message to the second network device by using the first UE. When the second UE and the first UE are connected over the short-distance link by using a sidelink technology, a resource used by the first UE to send the RRC CRC message over the sidelink may be added by the second network device to the second radio resource reconfiguration message sent to the second UE.

With reference to <FIG> and <FIG>, the following further describes <FIG> by using interaction among the first UE, the second UE, the first network device, and the second network device as an example. <FIG> and <FIG> are a diagram of interaction among the first UE, the second UE, the first network device, and the second network device according to Example <NUM> of the present disclosure. Second UE <NUM> is the second type of second UE, and second UE <NUM> is the first type of second UE.

Specific processes of step <NUM> to step <NUM> are the same as those of step <NUM> to step <NUM>, and details are not described herein again.

Step <NUM>: The first UE sends a short-distance link communication suspension instruction message to the second UE.

Step 950a: The first UE sends the short-distance link communication suspension instruction message to the second type of second UE.

Step 950b: The first UE sends the short-distance link communication suspension instruction message to the first type of second UE.

The first UE performs the following process:
After the first UE receives the radio resource reconfiguration message and the second radio resource reconfiguration messages, regardless of whether the second radio resource reconfiguration message is a radio resource reconfiguration message sent to the first type of second UE or a radio resource reconfiguration message sent to the second type of second UE, the first UE is first handed over from the first network device to the second network device. After the handover is completed, the first UE sends the M second radio resource reconfiguration messages to M second UEs. For the first type of second UE and the second type of second UE, there are specifically the following two optional implementations.

For the first type of second UE, details are as follows:
Implementation <NUM>: The first UE is handed over from the first network device to the first network device. After the handover is completed, the first UE sends a second radio resource reconfiguration message bound for the first type of second UE to the corresponding second UE. Further, the first UE re-establishes a radio bearer over a short-distance link between the first UE and the second UE. The re-establishment operation specifically includes the following steps:
When the first UE and the second UE are connected over the short-distance link by using a sidelink technology, the first UE re-establishes a radio link control entity corresponding to each second UE over the sidelink. Specific processing includes: discarding all RLC SDUs and/or RLC PDUs buffered on all RLC entity sending sides, discarding all RLC PDUs that have been received on all RLC entity receiving sides, stopping and resetting all timers, and resetting all status variables.

When the first UE and the second UE are connected over the short-distance link by using a sidelink technology, the first UE re-establishes an adaptation layer entity corresponding to each second UE over the non-3GPP link. Specific processing includes: clearing an SDU and/or a PDU buffered by the adaptation layer entity, stopping and resetting all timers if existent, and resetting all status variables if existent.

Implementation <NUM>: Before the first UE is handed over from the first network device to the second network device, the first UE sends a second message, namely, the short-distance link communication suspension instruction message to each second UE. The second message is used to instruct the second UE to suspend transmission and reception of data on a radio bearer over a short-distance link between the second UE and the first UE. The first UE also suspends transmission and reception of the data on the radio bearer over the short-distance link between the first UE and the second UE. Then, the first UE is handed over from the first network device to the second network device. After the handover is completed, the first UE sends a third message to each second UE. The third message is used to instruct the second UE to resume transmission and reception of the data on the radio bearer over the short-distance link between the second UE and the first UE. The first UE also suspends transmission and reception of the data on the radio bearer over the short-distance link between the first UE and the second UE. Subsequently, the first UE sends a second radio resource reconfiguration message bound for the first type of second UE to the corresponding second UE. Further, the first UE re-establishes a radio bearer over a short-distance link between the first UE and the second UE. The re-establishment operation is consistent with that in <FIG> and <FIG>. When the first UE and the second UE are connected over the short-distance link by using a sidelink technology, the short-distance link communication restoration instruction message is a message generated by a PC5-S protocol layer. When the first UE and the second UE are connected over the short-distance link by using a non-3GPP access technology, the short-distance link communication restoration instruction message is a message generated by a PC5-S protocol layer, a message generated by an adaptation layer, or a message generated by an RRC layer.

For the second type of remote UE, details are as follows:
Implementation <NUM>: The first UE is handed over from the first network device to the second network device. After the handover is completed, the first UE sends a second radio resource reconfiguration message bound for the second type of second UE to the corresponding second UE.

Implementation <NUM>: Before the first UE is handed over from the first network device to the second network device, the first UE sends a second message to each second UE. The second message is used to instruct the second UE to suspend transmission and reception of data on a radio bearer over a short-distance link between the second UE and the first UE. The first UE also suspends transmission and reception of the data on the radio bearer over the short-distance link between the first UE and the second UE. Then, the first UE is handed over from the first network device to the second network device. After the handover is completed, the first UE sends a third message to each second UE. The third message is used to instruct the second UE to resume transmission and reception of the data on the radio bearer over the short-distance link between the second UE and the first UE. The first UE also resumes transmission and reception of the data on the radio bearer over the short-distance link between the first UE and the second UE. Subsequently, the first UE sends a second radio resource reconfiguration message bound for the first type of second UE to the corresponding second UE. Then, the first UE releases a short-distance link connection to the second type of second UE. When the first UE and the second UE are connected over the short-distance link by using a sidelink technology, the second message and the third message are messages generated by a PC5-S protocol layer. When the first UE and the second UE are connected over the short-distance link by using a non-3GPP access technology, the second message and the third message are messages generated by a PC5-S protocol layer, messages generated by an adaptation layer, or messages generated by an RRC layer.

For Implementation <NUM>, optionally, after the first UE sends the second radio resource reconfiguration message bound for the first type of second UE to the corresponding second UE, and the first UE receives a short-distance link connection release message sent by the second UE, the first UE releases the short-distance link connection to the second type of second UE.

Correspondingly, the second UE performs the following process:
The first type of second UE:
Implementation <NUM>: In a case in which step 950a/950b and step 990a/990b are not included, the second UE receives a second radio resource reconfiguration message sent by the first UE. Further, the second UE re-establishes a radio bearer over a short-distance link between the second UE and the first UE. The re-establishment operation specifically includes the following steps:
The second UE re-establishes transmission and reception of data on the radio bearer over the short-distance communication link between the second UE and the first UE. Specifically, the second UE re-establishes PDCP entities of all radio bearers, re-establishes RLC entities of all the radio bearers, and resets a MAC entity.

When the second UE and the first UE are connected over the short-distance link by using a non-3GPP technology, the PDCP entities of all the radio bearers are re-established.

Implementation <NUM>: The second UE receives a second message sent by the first UE. The second message is used to instruct the second UE to suspend transmission and reception of data on a radio bearer over a short-distance link between the second UE and the first UE. The second UE suspends transmission and reception of the data on the radio bearer over the short-distance link between the second UE and the first UE. Then, the second UE receives a third message sent by the first UE. The third message is used to instruct the second UE to resume transmission and reception of the data on the radio bearer over the short-distance link between the second UE and the first UE. The second UE resumes transmission and reception of the data on the radio bearer over the short-distance link between the second UE and the first UE. Subsequently, the second UE receives a second radio resource reconfiguration message sent by the first UE. Further, the second UE re-establishes a radio bearer over the short-distance link between the second UE and the first UE. The re-establishment operation is the same as that in step <NUM> and step <NUM> in <FIG> and <FIG>, and details are not described herein again. When the first UE and the second UE are connected over the short-distance link by using a sidelink technology, the second message and the third message are messages generated by a PC5-S protocol layer. When the first UE and the second UE are connected over the short-distance link by using a non-3GPP access technology, the second message and the third message are messages generated by a PC5-S protocol layer, messages generated by an adaptation layer, or messages generated by an RRC layer.

Step 990a: The first UE sends the short-distance link communication restoration instruction message to the second type of second UE.

Step 990b: The first UE sends the short-distance link communication restoration instruction message to the first type of second UE.

A processing process on a first UE side is as follows:
After handover of the first UE is completed, in other words, after an RRC CRC is sent to the second UE, the first UE sends the third message, namely, the short-distance link communication restoration instruction message, to the second UE. For specific processing by the first UE, refer to description in Implementation <NUM> in step 950a/950b.

A processing process on a second UE side is as follows:
After receiving the short-distance link communication restoration instruction message sent by the first UE, the second UE resumes transmission and reception of the data on the radio bearer over the short-distance link between the second UE and the second UE. For specific processing, refer to description in Implementation <NUM> in step 950a/950b.

Step <NUM>: The first UE sends the second radio resource control reconfiguration message to the second UE.

The first UE sends a second radio resource control reconfiguration message to the second type of second UE. The first UE sends a second radio resource control reconfiguration message to the first type of second UE.

The first UE performs the following processing process:
The first UE sends the second radio resource reconfiguration message to second UE. For specific processing by the second UE, refer to step 550a and step 550b.

The second UE performs the following processing process:
The second UE receives the second radio resource reconfiguration message sent by the first UE. For specific processing by the second UE, refer to description in the two implementations in step 550a/550b.

Step 9110a: The second type of second UE sends an RRC CRC message to the second network device.

Step 9110b: The first type of second UE sends an RRC CRC message to the second network device.

The first type of second UE sends the RRC CRC message to the second network device by using the first UE. When the second UE and the first UE are connected over the short-distance link by using a sidelink technology, a resource used by the second UE to send the RRC CRC message over the sidelink may be added by the second network device to the second radio resource reconfiguration message sent to the second UE.

The second type of second UE sends the RRC CRC message to the second network device or the third network device.

After the first UE receives the first radio resource reconfiguration message and the second radio resource reconfiguration messages, if there is both the first type of second UE and the second type of first UE, for the first type of second UE, the first UE performs operations in a manner in <FIG> and <FIG>, and for the second type of second UE, the first UE performs operations in a manner in <FIG> and <FIG>.

Step <NUM> and step <NUM> have same implementations as step <NUM> to step <NUM>, and details are not described herein again.

Step 1050a: The first UE sends a second radio resource reconfiguration message to the second type of second UE.

Step 1050b: The first UE sends a short-distance link communication suspension instruction message to the first type of second UE.

Step <NUM> to step <NUM> have same implementations as step <NUM> and step <NUM>, and details are not described herein again.

Step <NUM>: The first UE sends short-distance link communication restoration instruction information to the first type of second UE.

Step <NUM>: The first UE sends a second radio resource reconfiguration message to the first type of second UE.

Step <NUM>: The second type of second UE sends an RRC CRC message to the second network device.

Step <NUM>: The first type of second UE sends an RRC CRC message to the second network device.

Through application of the handover method provided in this example of the present disclosure, the first UE receives the first radio resource reconfiguration message and the M second radio resource reconfiguration messages, where the first radio resource reconfiguration message and the M second radio resource reconfiguration messages are sent by the first network device. The first radio resource reconfiguration message includes the first handover command, the first handover command is used to instruct to hand over the first UE from the first network device to the second network device, the second radio resource reconfiguration message includes the second handover command, the second handover command is used to instruct to hand over the second UE from the first network device to the third network device, M is the quantity of second UEs in the RRC connected mode that are connected to the first UE, M is an integer greater than or equal to <NUM>, and the second network device is the same as or different from the third network device. The first UE is handed over from the first network device to the second network device according to the first handover command. This resolves a problem of high signaling overheads and high power consumption when evolved remote UE and evolved relay UE are handed over from the first network device to the second network device at the same time.

<FIG> is a schematic diagram of a handover apparatus according to Example <NUM> of the present disclosure. The handover apparatus <NUM> is configured to perform a method procedure performed by the first UE. As shown in <FIG>, the handover apparatus <NUM> includes a receiver <NUM>, a processor <NUM>, a transmitter <NUM>, a memory <NUM>, and a bus system <NUM>.

The memory <NUM> is configured to store a program. Only one memory is shown in <FIG>. Certainly, a plurality of memories may be disposed as required. The memory <NUM> may be a memory in the processor <NUM>.

The memory <NUM> stores the following elements: an executable module or a data structure, a subset thereof, or an extended set thereof;.

The processor <NUM> controls operations of the handover apparatus <NUM>, and the processor <NUM> may also be referred to as a CPU. In specific application, all components of the handover apparatus <NUM> are coupled together by using the bus system <NUM>. The bus system <NUM> may include a power supply bus, a control bus, a status signal bus, and the like in addition to a data bus. However, for clear description, various types of buses in the figure are marked as the bus system <NUM>. For ease of illustration, <FIG> shows merely an example of the bus system <NUM>.

The method disclosed in the foregoing examples of this disclosure may be applied to the processor <NUM>, or may be implemented by the processor <NUM>. The processor <NUM> may be an integrated circuit chip and has a signal processing capability. In an implementation process, steps in the foregoing method may be implemented by using a hardware integrated logical circuit in the processor <NUM>, or by using instructions in a form of software. The processor <NUM> may be a general-purpose processor, a DSP, an ASIC, an FPGA or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The processor <NUM> may implement or perform the methods, the steps, and logical block diagrams that are disclosed in the examples of this disclosure. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor or the like. Steps of the methods disclosed with reference to the examples of this disclosure may be directly performed and accomplished by a hardware decoding processor, or may be performed and accomplished by using a combination of hardware and software modules in the decoding processor. A software module may be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, or the like. The storage medium is located in the memory <NUM>. The processor <NUM> reads information from the memory <NUM>, and performs the following steps in combination with hardware of the processor <NUM>.

The receiver <NUM> is configured to receive a first radio resource reconfiguration message and M second radio resource reconfiguration messages, where the first radio resource reconfiguration message and the M second radio resource reconfiguration messages are sent by a first network device, the first radio resource reconfiguration message includes a first handover command, the first handover command is used to instruct to hand over the handover apparatus <NUM> from the first network device to a second network device, the second radio resource reconfiguration message includes a second handover command, the second handover command is used to instruct to hand over second UE from the first network device to a third network device, M is a quantity of second UEs in an RRC connected mode that are connected to the handover apparatus <NUM>, and the second network device is the same as or different from the third network device.

The processor <NUM> is configured to hand over the handover apparatus <NUM> from the first network device to the second network device according to the first handover command.

Further, the first radio resource reconfiguration message includes first information, and the first information includes at least one of first indication information and second indication information. The first indication information is used to indicate second UE connected to the second network device by using the handover apparatus <NUM> after the handover apparatus <NUM> is handed over to the second network device, a quantity of second UEs connected to the second network device by using the handover apparatus <NUM> is X, and X is an integer that is not greater than M. The second indication information is used to indicate second UE that is connected to the second network device not by using the handover apparatus <NUM> after the handover apparatus <NUM> is handed over to the second network device, and a quantity of second UEs that are connected to the second network device not by using the handover apparatus <NUM> is M-X.

Further, the first indication information or the second indication information is specifically a device identifier of the second UE.

Further, the first radio resource reconfiguration message includes second information, and the second information includes a configuration of a resource or a resource pool used to send the second radio resource configuration message over a sidelink.

Further, the first radio resource reconfiguration message is included in a first RLC SDU, the second radio resource reconfiguration messages are included in second RLC SDUs, and the first RLC SDU and at least one of the M second RLC SDUs are included in one RLC PDU.

Further, the transmitter <NUM> is configured to send the second radio resource reconfiguration message to the second UE.

The processor <NUM> is further configured to hand over the handover apparatus <NUM> from the first network device to the second network device after sending the M second radio resource reconfiguration messages is completed.

The receiver <NUM> is further configured to receive indication information that is fed back by the second UE and that indicates that the second radio resource reconfiguration message is successfully received.

The processor <NUM> is further configured to hand over the handover apparatus <NUM> from the first network device to the second network device after the handover apparatus <NUM> receives M pieces of indication information.

Further, the processor <NUM> is configured to suspend transmission and reception of data on a radio bearer over a link between the handover apparatus <NUM> and the second UE.

Further, the processor <NUM> is configured to: when handing over the handover apparatus <NUM> from the first network device to the second network device according to the first handover command, if there is second UE connected to the second network device by using the handover apparatus <NUM>, re-establish a radio bearer over a link between the handover apparatus <NUM> and the second UE.

Further, the processor <NUM> is configured to: when handing over the handover apparatus <NUM> from the first network device to the second network device according to the first handover command, if there is no second UE connected to the second network device by using the handover apparatus <NUM>, release the radio bearer over the link between the handover apparatus <NUM> and the second UE.

Further, the processor <NUM> is configured to: if there is the second UE connected to the second network device by using the handover apparatus <NUM>, resume transmission and reception of data on the radio bearer over the link between the handover apparatus <NUM> and the second UE.

Further, the transmitter <NUM> is configured to send a first message to the second UE, where the first message is used to instruct the second UE to resume transmission and reception of the data on the radio bearer over the link between the second UE and the handover apparatus <NUM>.

Further, the transmitter <NUM> is configured to: if there is no second UE connected to the second network device by using the handover apparatus <NUM>, send the second radio resource reconfiguration message to the second UE.

Further, the transmitter <NUM> is configured to: if there is no second UE connected to the second network device by using the handover apparatus <NUM>, send a second message to the second UE before the handover apparatus <NUM> is handed over from the first network device to the second network device, where the second message is used to instruct the second UE to suspend transmission and reception of data on a radio bearer over a link between the second UE and the handover apparatus <NUM>.

The processor <NUM> is further configured to suspend transmission and reception of the data on the radio bearer over the link between the handover apparatus <NUM> and the second UE.

The transmitter <NUM> is further configured to send the second message to the second UE after the handover apparatus <NUM> is handed over from the first network device to the second network device, where the second message is used to instruct the second UE to resume transmission and reception of the data on the radio bearer over the link between the second UE and the handover apparatus <NUM>.

The processor <NUM> is further configured to resume transmission and reception of the data on the radio bearer over the link between the handover apparatus <NUM> and the handover apparatus <NUM>.

The transmitter <NUM> is further configured to send the second radio resource reconfiguration message to the second UE.

Further, the processor <NUM> is configured to: if there is no second UE connected to the second network device by using the handover apparatus <NUM>, release a connection of the link between the handover apparatus <NUM> and the second UE.

Further, the transmitter <NUM> is configured to: if there is second UE connected to the second network device by using the handover apparatus <NUM>, send the second radio resource reconfiguration message to the second UE.

The processor <NUM> is further configured to re-establish a radio bearer over a link between the handover apparatus <NUM> and the second UE.

Further, the transmitter <NUM> is configured to: if there is second UE connected to the second network device by using the handover apparatus <NUM>, send a second message to the second UE before the handover apparatus <NUM> is handed over from the first network device to the second network device, where the second message is used to instruct the second UE to suspend transmission and reception of data on a radio bearer over a link between the second UE and the handover apparatus <NUM>.

The transmitter <NUM> is further configured to send a third message to the second UE after the handover apparatus <NUM> is handed over from the first network device to the second network device, where the third message is used to instruct the second UE to resume transmission and reception of the data on the radio bearer over the link between the second UE and the handover apparatus <NUM>.

The processor <NUM> is further configured to re-establish a radio bearer over the link between the handover apparatus <NUM> and the second UE.

Through application of the handover apparatus <NUM> provided in this example of the present disclosure, the receiving unit receiver <NUM> receives the first radio resource reconfiguration message and the M second radio resource reconfiguration messages, where the first radio resource reconfiguration message and the M second radio resource reconfiguration messages are sent by the first network device. The first radio resource reconfiguration message includes the first handover command, the first handover command is used to instruct to hand over the handover apparatus <NUM> from the first network device to the second network device, the second radio resource reconfiguration message includes the second handover command, the second handover command is used to instruct to hand over the second UE from the first network device to the third network device, M is the quantity of second UEs in the RRC connected mode that are connected to the handover apparatus <NUM>, M is an integer greater than or equal to <NUM>, and the second network device is the same as or different from the third network device. The handover unit processor <NUM> hands over the handover apparatus <NUM> from the first network device to the second network device according to the first handover command. This resolves a problem of high signaling overheads and high power consumption when the first UE and the second UE are handed over.

The method steps in the examples of this disclosure may be implemented in a hardware form, or may be implemented by a processor by executing a software instruction. The software instruction may include a corresponding software module. The software module may be stored in a random access memory (Random Access Memory, RAM), a flash memory, a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), a register, a hard disk, a removable hard disk, a CD-ROM, or any other form of storage medium known in the art. For example, a storage medium is coupled to a processor, so that the processor can read information from the storage medium or write information into the storage medium. Certainly, the storage medium may be a component of the processor. The processor and the storage medium may be located in an ASIC. In addition, the ASIC may be located in a sending device or a receiving device. Certainly, the processor and the storage medium may exist in the sending device or the receiving device as discrete components.

All or some of the foregoing examples may be implemented by using software, hardware, firmware, or any combination thereof. When software is used to implement the examples, the examples may be implemented completely or partially in a form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedure or functions according to the examples of the present disclosure are all or partially generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable apparatuses. The computer instructions may be stored in a computer-readable storage medium, or transmitted by using the computer-readable storage medium. The computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, a fiber, or a digital subscriber line (DSL)) or wireless (for example, infrared, wireless, or a microwave) manner. The computer-readable storage medium may be any usable medium accessible by a computer, or a data storage device, such as a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a DVD), a semiconductor medium (for example, a solid state disk Solid State Disk, (SSD)), or the like.

It may be understood that various numerical symbols related to the examples of this disclosure are differentiated merely for ease of description, but are not used to limit the scope of the examples of this disclosure.

Claim 1:
A handover method, wherein the method comprises:
receiving, by first user equipment (<NUM>), UE, from a first network device (<NUM>), a first radio resource reconfiguration message and M second radio resource reconfiguration messages, wherein the first radio resource reconfiguration message and the M second radio resource reconfiguration messages are sent by a first network device (<NUM>), the first radio resource reconfiguration message comprises a first handover command, the first handover command is used to instruct to hand over the first UE (<NUM>) from the first network device (<NUM>) to a second network device, the second radio resource reconfiguration message comprises a second handover command, the second handover command is used to instruct to hand over second UE (<NUM>) from the first network device (<NUM>) to a third network device, the M is a quantity of second UEs (<NUM>) in a radio resource control, RRC, connected mode that are connected to the first UE (<NUM>), the M is an integer greater than or equal to <NUM>, and the second network device is the same as or different from the third network device; and
handing over, by the first UE (<NUM>), from the first network device (<NUM>) to the second network device according to the first handover command, wherein when the first UE (<NUM>) is handed over, the first UE (<NUM>) resets a media access control, MAC, layer and re-establishes radio link control, RLC, entities and packet data convergence protocol, PDCP, entities of radio bearers over all uplinks or downlinks, wherein the first UE (<NUM>) processes a protocol stack over short-distance communication link between the first UE (<NUM>) and the second UE (<NUM>), and wherein:
if there is second UE (<NUM>) connected to the second network device by using the first UE (<NUM>), re-establishing, by the first UE (<NUM>), a radio bearer over a short-distance link between the first UE (<NUM>) and the second UE (<NUM>); and
if there is no second UE (<NUM>) connected to the second network device by using the first UE (<NUM>), releasing, by the first UE (<NUM>), a radio bearer over a short-distance link between the first UE (<NUM>) and the second UE (<NUM>).