WO2023124822A1 - 一种通信协作方法及装置 - Google Patents

一种通信协作方法及装置 Download PDF

Info

Publication number
WO2023124822A1
WO2023124822A1 PCT/CN2022/136835 CN2022136835W WO2023124822A1 WO 2023124822 A1 WO2023124822 A1 WO 2023124822A1 CN 2022136835 W CN2022136835 W CN 2022136835W WO 2023124822 A1 WO2023124822 A1 WO 2023124822A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
terminal device
remote
relay
cell
Prior art date
Application number
PCT/CN2022/136835
Other languages
English (en)
French (fr)
Inventor
潘晓丹
彭文杰
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023124822A1 publication Critical patent/WO2023124822A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data

Definitions

  • the present application relates to the field of wireless communication, and in particular to a communication method, node, device, device, computer-readable storage medium and system suitable for handover.
  • UE User equipment
  • UE-to-Network relay U2N Relay
  • UE-to-Network relay U2N Relay
  • the relay UE and the remote UE communicate through the PC5 interface, and the wireless communication link between the relay UE and the remote UE is called a sidelink (sidelink, SL).
  • Wireless communication is performed through the Uu interface, and the wireless communication link between the relay UE and the network device may be called a Uu link (Uu Link).
  • the embodiment of the present application provides a communication method and its network nodes, terminal equipment, etc., which are used to solve the problem in the prior art that in the U2N Relay scenario, when the Relay UE is in the CHO process, the Remote UE will experience a relatively long period of time The problem of service interruption.
  • a communication method is provided, and the entity executing the communication method may be a first network node, or a functional module applied to the first network node, or a chip or a chip system in the first network node , or a network entity or network device that implements the function of the first network node.
  • the following description is made by taking the execution subject as the first network node as an example.
  • the communication method may include: the first network node sends handover request information to the second network node, where the handover request information includes: first identification information of the relay terminal device and user equipment context information of the relay terminal device, and the remote The first identification information of the terminal device and the user equipment context information of the remote terminal device; wherein, the remote terminal device communicates with the first network node through the relay terminal device, and the handover request The information is used for the relay terminal device to switch from the first network node to the cell of the second network node; the first network node receives switching response information from the second network node, and the switching response The information includes: the second identification information of the relay terminal device, the radio bearer configuration information of the first cell of the second network node configured for the relay terminal device, and the second identification information of the remote terminal device.
  • the source base station can simultaneously request the radio resource configuration in the candidate target cell for the relay terminal equipment Relay UE and the remote relay equipment Remote UE, so that the subsequent Relay UE needs to switch to the candidate target cell, the Remote UE can apply the radio resource configuration of the candidate target cell, and handover to the target cell together with the Relay UE, thereby reducing the service interruption time of the Remote UE.
  • the first identification information of the remote terminal device includes one or more of the following: the remote terminal assigned by the first network node to the remote terminal device The CRNTI of the terminal device, the layer 2 identifier of the remote terminal device, and the temporary identifier of the remote terminal device assigned by the first network node to the remote terminal device.
  • the second identification information of the remote terminal device includes the above-mentioned first identification information of the remote terminal device, or, the first identification information of the remote terminal device
  • the second identification information includes one or more of the following: the CRNTI of the remote terminal device assigned by the second network node to the remote terminal device, the layer 2 identifier of the remote terminal device, and the second The temporary identifier of the remote terminal device assigned by the second network node to the remote terminal device.
  • the handover response information may include: first identification information, first configuration information, and second configuration information of the first cell of the second network node;
  • the first configuration information includes: the radio bearer configuration information of the first cell of the second network node configured for the relay terminal device; the configuration information of the first cell configured for the relay terminal device;
  • the radio bearer configuration information of the first cell of the second network node includes: the radio bearer configuration of the relay terminal device in the first cell of the second network node, and the relay terminal device is
  • the remote terminal device provides the RLC bearer configuration information of the PC5 interface and the RLC bearer configuration information of the Uu interface required by the relay service, wherein the PC5 interface is between the relay terminal device and the remote terminal device A communication interface, the Uu interface is a communication interface between the relay terminal device and the second network node;
  • the second configuration information includes: the first configured for the remote terminal device The radio bearer configuration information of the first cell of the second network node; the radio bearer configuration
  • the first configuration information and the second configuration information are for the convenience of writing, or it can also be understood that the handover response information may directly include the first cell of the second network node.
  • the first network node sends third configuration information to the relay terminal device, where the third configuration information includes: all radio bearer configuration information of the first cell of the second network node, and second identification information of the first cell of the second network node, wherein the first cell of the second network node is a candidate target cell for the relay terminal device to perform handover.
  • the first network node sends fourth configuration information to the remote terminal device, where the fourth configuration information includes: all configuration information configured for the remote terminal device radio bearer configuration information of the first cell of the second network node, and second identification information of the first cell of the second network node, wherein the first cell of the second network node is a candidate target cell for the relay terminal device to perform handover.
  • the second identifier of the first cell of the second network node may be that the first network node is the first cell of the second network node.
  • An identifier assigned by a cell; or, the second identifier of the first cell of the second network node may be a global cell identifier CGI, and the CGI is sent by the second network node to the first cell through the handover response information.
  • the first network node and the second network node are the same network node, that is to say, the method described in the first aspect of this application can be applied to a base station The switching scene between the cells below.
  • a communication method is provided.
  • the entity executing the communication method may be a relay terminal device, or a functional module applied to a relay terminal device, or a chip or a chip system in a relay terminal device , or a network entity or network device that realizes the function of the relay terminal device.
  • the following description will be made by taking the execution subject as a relay terminal device as an example.
  • the communication method may include: the relay terminal device receiving third configuration information sent by the first network node, the third configuration information including: the radio bearer of the first cell of the second network node configured for the relay terminal device configuration information, and second identification information of the first cell of the second network node, wherein the first cell of the second network node is a candidate target cell for the relay terminal device to perform handover;
  • the relay terminal device sends first information to the remote terminal device, where the first information is used to indicate the second identity information of the first cell of the second network node, or the first information is used to indicate the The ordering information of the configuration of the first cell of the second network node.
  • the radio resources of the candidate target cell can be pre-configured for the relay terminal equipment Relay UE and the remote relay equipment Remote UE, so that when the subsequent Relay UE needs to switch to the candidate target cell, the Relay The UE may indicate to the Remote UE which target cell to switch to (such as through the identification information of the cell), or the Relay UE may indicate to the Remote UE which cell's radio resource configuration needs to be applied (such as through the sorting information configured by the cell), so that the Remote The UE can apply the radio resource configuration of the corresponding target cell, and handover to the target cell together with the Relay UE, thereby reducing the service interruption time of the Remote UE.
  • the second identifier of the first cell of the second network node may be that the first network node is the first network node of the second network node.
  • An identifier allocated by a cell such as a cell index.
  • the second identifier of the first cell of the second network node may be a Global Cell Identity (CGI), and the CGI may be provided by the second network node Send to the first network node through handover response information.
  • CGI Global Cell Identity
  • the radio bearer configuration information of the first cell of the second network node configured for the relay terminal device may include: the relay terminal The radio bearer configuration of the device in the first cell of the second network node, and the RLC bearer configuration information and Uu interface of the PC5 interface required by the relay terminal device to provide relay services for the remote terminal device
  • the RLC bearer configuration information, the PC5 interface is the communication interface between the relay terminal equipment and the remote terminal equipment
  • the Uu interface is the communication interface between the relay terminal equipment and the second network node interface.
  • the relay terminal device when the first cell of the second network node satisfies a handover trigger condition, the relay terminal device sends the remote terminal device the first information.
  • a communication method is provided, and the entity executing the communication method may be a remote terminal device, or a functional module applied in a remote terminal device, or a chip or a chip system in a remote terminal device , or a network entity or network device implementing the function of the remote terminal device.
  • the following description is made by taking the execution subject as a remote terminal device as an example.
  • the communication method may include: the remote terminal device receives fourth configuration information sent by the first network node, where the fourth configuration information includes: the radio bearer configuration of the first cell of the second network node configured for the remote terminal device information, and second identification information of the first cell of the second network node, wherein the first cell of the second network node is a candidate target cell for the relay terminal device to perform handover; the The remote terminal device receives the first information sent by the relay terminal device, where the first information is used to indicate the second identification information of the first cell of the second network node, or the first information is used to indicate Sorting information of the configuration of the first cell of the second network node.
  • the second identifier of the first cell of the second network node may be that the first network node is the first network node of the second network node.
  • An identifier allocated by a cell such as a cell index.
  • the second identifier of the first cell of the second network node may be a Global Cell Identity (CGI), and the CGI may be provided by the second network node Send to the first network node through handover response information.
  • CGI Global Cell Identity
  • the radio bearer configuration information of the first cell of the second network node configured for the remote terminal device includes: the remote terminal device in The radio bearer configuration of the first cell of the second network node, and the RLC bearer configuration information of the PC5 interface of the remote device, where the PC5 interface is the remote terminal device and the relay terminal device communication interface between them.
  • the first information is sent by the relay terminal device to the remote terminal equipment.
  • the present application provides a communication device.
  • the communication device may be a first network node or a chip or a chip system in the first network node, and may also be a communication device used in the first network node to implement the first aspect or the first aspect.
  • the communication device may implement the functions/operations performed by the first network node in the above first aspect or its various possible designs, and the functions/operations may be implemented by executing corresponding software through hardware.
  • the hardware or software includes one or more modules corresponding to the above functions/operations.
  • the present application provides a communication device.
  • the communication device may be a relay terminal device or a chip or a chip system in a relay terminal device, or may be a relay terminal device used to implement the second aspect or the first aspect.
  • the communication device can implement the functions/operations performed by the relay terminal device in the second aspect or its possible designs, and the functions/operations can be implemented by executing corresponding software through hardware.
  • the hardware or software includes one or more modules corresponding to the above functions/operations.
  • the present application provides a communication device.
  • the communication device may be a remote terminal device or a chip or a chip system in a remote terminal device, or may be a remote terminal device used to implement the first aspect or the first aspect.
  • the communication device can implement the functions/operations performed by the remote terminal equipment in the above third aspect or its possible designs, and the functions/operations can be implemented by executing corresponding software through hardware.
  • the hardware or software includes one or more modules corresponding to the above functions/operations.
  • a communication device including: a processor and a memory; the memory is used to store computer instructions, and when the communication device is running, the processor executes the computer instructions stored in the memory, so that the communication device Execute the communication method described in any one of the first aspect to the third aspect.
  • a communication device including: a processor; the processor is configured to be coupled with a memory, and after reading instructions in the memory, execute any of the above-mentioned first to third aspects according to the instructions.
  • the communication device further includes a memory; the memory is used to store computer instructions.
  • the communication device further includes a communication interface; the communication interface is used for the communication device to communicate with other devices.
  • the communication interface may be a transceiver, an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, and the like.
  • the communication device may be a chip or a chip system. Wherein, when the communication device is a system-on-a-chip, the communication device may be composed of a chip, or may include a chip and other discrete devices.
  • the above-mentioned communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip or the chip system wait.
  • the aforementioned processor may also be embodied as a processing circuit or a logic circuit.
  • a computer-readable storage medium stores instructions, and when it is run on a computer, the computer can execute any one of the above-mentioned first to third aspects. the communication method described above.
  • a computer program product including computer instructions, which, when run on a computer, enables the computer to execute the communication method described in any one of the above first to third aspects.
  • a communication entity which can implement the functions or operations of the first network node (gNB base station), Relay UE or Remote UE in the first to third aspects above, and the communication entity includes Modules required to perform these operations.
  • a communication system which may include one or more of the foregoing: the first network node, the relay terminal device, the remote terminal device, and the communication entity , the communication device, the computer readable storage medium, and the computer program product.
  • FIG. 1(a) is a schematic diagram of a UE-to-UE direct communication scenario provided by an embodiment of the present application
  • Figure 1(b) is a control plane protocol stack architecture for communication between UE1 and UE2 at the PC5 port provided by the embodiment of the present application
  • FIG. 2 is a schematic diagram of a communication network applicable to a U2N Relay scenario provided by an embodiment of the present application;
  • FIG. 3 is a schematic diagram of a user plane protocol stack of a communication system provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a control plane protocol stack of a communication system provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a communication scenario of group switching based on U2N Relay provided by the embodiment of the present application;
  • FIG. 6 is a schematic flowchart of a communication method for group handover according to an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of another group handover communication method involved in the embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a CHO handover communication method involved in an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of a communication method suitable for CHO handover provided by an embodiment of the present application.
  • FIG. 11 is a schematic flowchart of another communication method suitable for CHO handover provided by the embodiment of the present application.
  • FIG. 12 is a schematic flowchart of another communication method suitable for CHO handover provided by the embodiment of the present application.
  • FIG. 13 is a schematic flowchart of another communication method suitable for CHO handover provided by the embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • data communication between UEs may be performed through a network, or communication between UEs may be directly performed without network equipment.
  • the interface for direct communication between UEs is called PC5 interface
  • the communication link between UEs is called sidelink.
  • a typical application scenario of sidelink communication is the Internet of Vehicles (V2X, Vehicle-to- -everything).
  • V2X Vehicle-to- -everything
  • each car can be a UE, and data transmission between cars can be directly performed through sidelink without going through the network, which can effectively reduce communication delays.
  • the side link may also be called a side link/side link/through link, etc.
  • the PC5 interface may also be called a "side link interface" or a "direct communication interface". Exemplarily, FIG.
  • FIG. 1 is a schematic diagram of a scenario of direct communication between UEs.
  • Fig. 1(a) shows the sidelink communication between UE1 and UE2 through the PC5 interface, and the sidelink communication can be applied to such as device to device (device to device, D2D), machine to machine (machine to machine, M2M) or vehicle to everything (V2X) and other scenarios.
  • Figure 1(b) shows the control plane protocol stack architecture of UE1 and UE2 communicating at the PC5 port. It can be seen that both UE1 and UE2 have a radio resource control (Radio Resource Control, RRC) protocol layer for end-to-end communication. Packet Data Convergence Protocol (PDCP) protocol layer, Radio Link Control (RLC) protocol layer, Media Access Control (MAC) protocol layer and PHY protocol layer.
  • RRC Radio Resource Control
  • the broadcast communication is similar to the broadcast system information of the base station, that is, the UE does not encrypt the broadcast service data, and any other UE within the effective receiving range can receive the broadcast service data if it is interested in the broadcast service.
  • the unicast communication is similar to the data communication performed after the RRC connection is established between the UE and the base station, and a unicast connection needs to be established between the two UEs first.
  • the two UEs can communicate based on the identity determined through negotiation, and the communication can be encrypted or unencrypted.
  • the unicast communication can only be performed between two UEs that have established a unicast connection.
  • a unicast communication on the side link corresponds to a pair of identifiers: source L2 ID (Source Layer-2 Identifier, layer 2 identifier source) and destination layer 2 identifier (Destination Layer-2 Identifier, L2 ID), in each
  • the source L2 ID and the destination L2 ID may be included in the subheader of the sidelink Media Access Control Protocol Data Unit (MAC PDU).
  • MAC PDU Media Access Control Protocol Data Unit
  • Multicast communication refers to communication between all UEs in a communication group, and any UE in the group can send and receive data of the multicast service.
  • the radio bearer is the general term for a series of protocol entities and configurations allocated by the base station to the UE. Generally, it is a service provided by layer 2 (L2) for transmitting user data between the UE and the base station.
  • the radio bearer includes PDCP protocol entities, RLC protocol Entities, MAC protocol entities, and a series of resources allocated by PHY.
  • Radio bearers can be divided into data radio bearers (Data Radio Bearer, DRB) and signaling radio bearers (Signalling Radio Bearer, SRB), the former is used to carry data, and the latter is used to carry signaling messages.
  • the radio bearer is called Sidelink Radio Bearer (Sidelink Radio Bearer, SLRB), including Sidelink Data Radio Bearer SL DRB and Sidelink Signaling Radio Bearer SL SRB.
  • the RLC bearer can refer to the protocol entities and configurations at and below the RLC layer, and can be understood as the lower layer part of the radio bearer, including a series of resources such as RLC protocol entities and logical channels.
  • the embodiment of the present application involves two types of RLC bearers, which are respectively Uu interface RLC (Uu RLC) bearer and PC5 interface RLC (PC5 RLC) bearer.
  • Uu RLC bearer refers to the RLC bearer on the Uu link (or Uu port)
  • PC5 RLC bearer refers to the RLC bearer on the Sidelink (or PC5 port).
  • FIG. 2 is a schematic diagram of a communication network applicable to the U2N Relay scenario, where the base station communicates with the relay UE through the Uu interface, and the relay UE communicates with the remote UE through the PC5 interface/Sidelink .
  • the remote UE can communicate with the base station through the relay UE, and the relay UE provides relay services for the remote UE.
  • the existing U2N Relay technology mainly has two designs: Layer-2 (Layer-2, L2) and Layer-3 (Layer-3, L3).
  • L2 Relay takes L2 Relay as an example to introduce the user plane protocol stack of the communication network shown in Figure 2.
  • FIG 3 it shows Network, 5GC) device communication system user plane protocol stack, wherein, the protocol stack of the remote UE, from top to bottom, includes: the network interconnection protocol (internet protocol, IP) layer for peer-to-peer communication with 5GC, through the Uu interface
  • the service data adaptation protocol service data adaptation protocol, SDAP) (or Uu-SDAP) layer for peer-to-peer communication with gNB
  • the packet data convergence protocol for peer-to-peer communication with gNB through the Uu interface (packet data convergence protocol, PDCP) (or Uu-PDCP) layer, adaptation layer (Adaptation layer, ADAPT), radio link control (radio link control, RLC) (or PC5-RLC) for peer-to-peer communication with the
  • the protocol stack for communicating with the remote UE in the relay UE includes, from top to bottom, an adaptation (Adapt) layer, a PC5-RLC layer, a PC5-MAC layer, and a PC5-PHY layer.
  • the protocol stack for communicating with gNB in the relay UE includes, from top to bottom, the Adapt layer, the Uu-RLC layer for communicating with gNB through the Uu interface, the Uu-MAC layer for communicating with gNB through the Uu interface, and the Uu-MAC layer for communicating with gNB through the Uu interface.
  • Uu-PHY layer to communicate with gNB.
  • the protocol stack for communicating with the remote UE in the gNB includes: the Uu-SDAP layer and the Uu-PDCP layer for communicating with the Remote UE through the Uu interface.
  • the protocol stack in the gNB that communicates with the relay UE includes, from top to bottom: Aapat layer, Uu-RLC layer, Uu-MAC layer and Uu-PHY layer.
  • the protocol stack that communicates with the 5GC through the GPRS Tunneling Protocol-User Plane (GTP-U, GPRS Tunneling Protocol-User Plane) interface includes the N3 protocol stack.
  • the protocol stack for communicating with the remote UE includes the IP layer
  • the protocol stack for communicating with the gNB through GTP-U includes the N3 protocol stack.
  • FIG. 4 shows a control plane protocol stack of a communication system including a remote UE, a relay UE, a gNB and a 5GC device.
  • the protocol stack of the remote UE includes from top to bottom: a non-access stratum (non-access stratum, NAS) for peer-to-peer communication with 5GC, and an RRC layer (or RRC layer) for peer-to-peer communication with gNB through the Uu interface.
  • NAS non-access stratum
  • RRC layer or RRC layer
  • the protocol stack for communicating with the remote UE includes, from top to bottom, an adaptation layer, a PC5-RLC layer, a PC5-MAC layer, and a PC5-PHY layer.
  • the protocol stack for communicating with the gNB includes from top to bottom: adaptation layer, Uu-RLC layer, Uu-MAC layer and Uu-PHY layer.
  • the protocol stack in the gNB for communicating with the remote UE includes the Uu-RRC layer and the Uu-PDCP layer.
  • the protocol stack in the gNB that communicates with the relay UE includes from top to bottom: an adaptation layer, a Uu-RLC layer, a Uu-MAC layer, and a Uu-PHY layer.
  • the protocol stack communicating with the 5GC device through the N2 interface includes the N2 protocol stack.
  • the protocol stack for communicating with the remote UE includes the NAS layer
  • the protocol stack for communicating with the gNB through the N2 interface includes the N2 protocol stack.
  • the data packets of the Remote UE are relayed and forwarded below the PDCP (Packet Data Convergence Protocol) layer of the Relay UE, that is, the Relay UE can only maintain the RLC bearer for relay forwarding, including RLC , MAC and PHY layers. Therefore, there are end-to-end PDCP, SDAP and RRC layers between the Remote UE and the base station, but there is no RLC, MAC and PHY layers for end-to-end communication.
  • PDCP Packet Data Convergence Protocol
  • an adaptation layer may be configured between the RLC layer and the PDCP layer.
  • the main role of the adaptation layer is to multiplex and demultiplex bearers, that is, to support multiplexing of different bearers into one bearer or to split one bearer into different bearers.
  • the adaptation layer in the protocol stack at both ends of the PC5 port (that is, the sidelink) may be called a PC5 adaptation layer
  • the adaptation layer in the protocol stack at both ends of the Uu port may be called a Uu adaptation layer.
  • the name of the protocol layer mentioned in the embodiment of the present application may change during the process of technology or standard evolution, and the specific name is not limited in this application.
  • the adaptation layer (Adaptation layer, ADAPT) may also be called the sidelink relay adaptation protocol (Sidelink Relay Adaptation Protocol, SRAP) layer.
  • the adaptation layer of the gNB can multiplex the data of multiple bearers (for example, the bearers can be SRB or DRB) of one or more Remote UEs to one RLC bearer of the Uu link, that is, the RLC bearer on the Uu link
  • the bearers can be SRB or DRB
  • the RLC bearer can carry data on bearers belonging to one or more Remote UEs, and the specific multiplexing mechanism can depend on the configuration of the base station.
  • the adaptation layer of the base station can add Remote UE ID and DRB ID in the packet header of the data to be sent, when the adaptation layer data packet is sent to the Relay UE, the adaptation layer of the Relay UE can According to the Remote UE ID and DRB ID on the packet header, the data submitted on the Uu RLC bearer is mapped to the PC5 RLC bearer corresponding to different Remote UEs, so as to realize the splitting of multiplexed data.
  • the mapping relationship between the Remote UE ID, the DRB ID and the PC5 RLC bearer may depend on the configuration of the base station.
  • the adaptation layer of the Relay UE can multiplex the data belonging to the radio bearers (DRB or SRB) of one or more Remote UEs to the RLC bearer of a Uu link, thereby realizing bearer multiplexing.
  • DRB radio bearers
  • SRB Radio Bearers
  • the Remote UE local ID can be allocated by the gNB where the Relay UE is located, and the local ID allocated by the gNB can be unique under the gNB or unique under the Relay UE.
  • a possible allocation method is: after the Remote UE and the Relay UE establish a unicast connection, the Relay UE sends an RRC message to the gNB, such as a SidelinkUEInformationNR (SUI) message, and requests the gNB to allocate a local ID for the Remote UE through the RRC message.
  • RRC message such as a SidelinkUEInformationNR (SUI) message
  • FIG. 5 is a schematic diagram of a communication scenario for group handover based on U2N Relay.
  • the Relay UE performs handover from the source base station gNB1 to the target base station gNB2
  • the Remote UE follows the Relay UE from gNB1 to gNB 2 , and the sidelink link between the Remote UE and the Relay UE will always remain connected.
  • the Remote UE and Relay UE can be regarded as a "group (group)".
  • group group
  • the Relay UE switches, the Remote UE in the same group will switch with the Relay UE.
  • the UE context of the Remote UE and The UE context of the Relay UE can be handed over to the target base station together, and the association relationship between the UE contexts of the two UEs will continue to be maintained.
  • the UE context referred to in this embodiment of the present application may refer to the communication link established between functional entities and its configuration information, which is used for information transmission between functional entities; for example, RRC is established between two functional entities, UE and gNB A connection, its communication link and its corresponding configuration information can be understood as the UE context.
  • the UE context can include the mobile phone's network capabilities, authentication information, negotiated security algorithm, bearer information, PDU session information, etc.
  • the group handover referred to in the embodiment of this application can also be applied to the handover scenario from the source cell to the target cell, and is not limited to the handover from the source base station gNB1 to the target base station gNB2.
  • the Relay UE can be a handover from the current serving base station The cell is handed over to another cell of the current base station or to a cell under another base station.
  • the "group" referred to in this embodiment of the application may include the Relay UE and one or more remote UEs that have communication connections with it.
  • One Remote UE that is to say, the Remote UEs in the "group” can be all the Remote UEs connected to the Relay UE or some Remote UEs in all the Remote UEs connected to the Relay UE.
  • FIG. 6 is a schematic flowchart of a communication method for group handover involved in an embodiment of the present application, and the communication method includes:
  • Step 601 the Relay UE sends a measurement report (Measurement report) to the serving base station (Serving eNB);
  • Step 602 The serving base station sends a handover request (handover request) message to the target base station (Target eNB).
  • the serving base station may send handover requests to multiple target base stations or one target base station, there may be multiple corresponding handover requests, and each handover request may correspond to a Relay UE or a remote UE.
  • Step 603 the target base station sends a handover accept (handover accept) message to the serving base station.
  • the serving base station may receive multiple handover acceptance messages from corresponding multiple target base stations or multiple cells.
  • Step 604 The serving base station sends a group handover command (Group HO command) to the Relay UE.
  • the group switching command may include multiple configuration messages, or the group switching command and multiple configuration messages are sent together as one message.
  • the configuration message can be an RRC reconfiguration (RRC Reconfiguration message) message sent by the source base station to the Remote UE and the Relay UE, and the RRC reconfiguration message to the Remote UE and the RRC reconfiguration message to the Relay UE can be used as a message or a transmission .
  • Step 605 the Relay UE sends a configuration message to the Remote UE.
  • the RRC reconfiguration message for the Remote UE is first sent to the Relay UE, and the Relay UE forwards the reconfiguration message of the Remote UE to the corresponding Remote UE.
  • Remote UE can be multiple, and Fig. 6 shows Remote UE1 and Remote UE2, so, as in step 605a, Relay UE sends configuration information (for example, the RRC reconfiguration message of Remote UE1) to Remote UE1, as in step 605b, Relay UE Send configuration information (RRC reconfiguration message of Remote UE2) to Remote UE2.
  • Step 606 The Relay UE switches to the target base station.
  • the Relay UE can switch from the source base station to the target base station according to the configuration message sent by the base station to itself in step 604.
  • Step 607 the Remote UE sends a configuration completion message to the Relay UE.
  • each Remote UE after receiving the RRC reconfiguration message forwarded by the Relay UE, each Remote UE replies a reconfiguration complete message to the Relay UE to indicate that the configuration message is received successfully.
  • Remote UE1 sends a configuration completion message to Relay UE
  • Remote UE2 sends a configuration completion message to Relay UE.
  • the configuration complete message mentioned here may be a reconfiguration complete (Reconfiguration Complete) message.
  • Step 608 the Relay UE sends a handover complete (handover complete) message to the target base station.
  • Step 609 the Relay UE sends a reconfiguration complete (Reconfiguration complete) message to the target base station.
  • the Relay UE After the Relay UE successfully accesses the target base station, it sends a reconfiguration completion message of each Remote UE to the target base station, and completes the access of each Remote UE at the target base station side.
  • 609a indicates that the Relay UE sends the reconfiguration completion message of Remote UE1 to the target base station
  • 609b indicates that the Relay UE sends the reconfiguration completion message of Remote UE2 to the target base station.
  • FIG. 7 is a schematic flowchart of another group handover communication method involved in the embodiment of the present application.
  • the communication method includes:
  • Step 701 Relay UE sends a measurement report (Measurement report) to the serving base station (Serving eNB);
  • Step 702 The serving base station sends a handover request (handover request) message to the target base station (Target eNB).
  • the serving base station can send handover requests to multiple target base stations or one target base station, there can be multiple corresponding handover requests, and each handover request can correspond to a Relay UE or a remote UE.
  • Step 703 the target base station sends a handover accept (handover accept) message to the serving base station.
  • the serving base station may receive multiple handover acceptance messages from corresponding multiple target base stations or multiple cells.
  • Step 704 The serving base station sends a reconfiguration (Reconfiguration) message.
  • the serving base station sends a reconfiguration message to the Relay UE and the Remote UE, and it can be understood that there may be multiple Remote UEs.
  • the serving base station sends a reconfiguration message to Remote UE 1, as shown in 704b, the serving base station sends a reconfiguration message to Remote UE 2, and as shown in 704c, the serving base station sends a reconfiguration message to Relay UE .
  • Step 705 the Remote UE sends a reconfiguration complete (Reconfiguration Complete) message to the Relay UE.
  • Remote UE 1 sends a reconfiguration complete message to Relay UE
  • Remote UE 2 sends a reconfiguration complete message to Relay UE
  • Step 706 The Relay UE switches to the target base station.
  • Step 707 the Relay UE sends a handover complete (handover complete) message to the target base station.
  • the handover complete message may include Relay UE's own reconfiguration complete message and Remote UE1 and Remote UE2's reconfiguration complete message, as a group feedback (Handover complete with group response) during the handover process, as shown in Figure 7 , understandably, this group includes Relay UE, Remote UE1 and Remote UE2.
  • this group includes Relay UE, Remote UE1 and Remote UE2.
  • the source base station sends RRC reconfiguration messages to the Remote UE and the Relay UE respectively.
  • the Relay UE After the Relay UE receives the reconfiguration completion messages of all Remote UEs and successfully accesses the target base station, the Relay UE replies the handover completion message to the target base station with a message.
  • this solution is relatively complex and has a long time delay.
  • 3GPP Release 16 introduced conditional handover (CHO).
  • CHO conditional handover
  • the main idea of CHO is to let the source base station issue a handover command to the UE in advance before the wireless environment between the UE and the source base station further deteriorates, so that the UE knows in advance how to access the target base station, but does not initiate handover immediately. After the candidate target base station satisfies the handover execution condition, the UE decides to initiate the handover process autonomously. Therefore, CHO can reduce the probability of handover failure and improve handover reliability.
  • Candidate target cells can be planned in advance, thereby reducing the probability of UE handover failure.
  • FIG. 8 shows a schematic flow diagram of a communication method for CHO handover.
  • this method there may be uplink data and or downlink data transmission between the Relay UE and the source base station (Source gNB).
  • the method includes :
  • Step 801 The source base station and the relay UE exchange measurement configuration and measurement reports.
  • the source base station sends a measurement configuration to the Relay UE, and based on the measurement configuration, the Relay UE sends a measurement report to the source base station.
  • Step 802 CHO decision.
  • the source base station decides to execute CHO according to the information carried in the measurement report sent by the Relay UE, and selects a cell of a candidate target base station (Target gNB) or selects multiple target cells of multiple candidate target base stations.
  • Target gNB candidate target base station
  • Step 803 the source base station sends a handover request (handover request, HO request) message to the target base station.
  • the source base station can send a handover request message to each candidate target base station, and the handover request message can be sent according to cell granularity, that is, each cell sends a corresponding HO Request message.
  • Step 804 The candidate target base station sends a handover accept (HO accept) message to the source base station.
  • HO accept handover accept
  • the candidate target base station implements an admission control mechanism, and after the Relay UE is admitted, each candidate target base station replies to the source base station with a handover request response (Handover Request ACK).
  • the reply message can also be at the cell granularity, that is, Each cell responds to the received handover request message with a handover request response.
  • the candidate target base station can generate an air interface configuration, reserve radio resources for the UE, and send the corresponding air interface configuration information to the source base station through a Handover Request ACK message, which carries the ID information of the target cell.
  • Step 805 The source base station sends an RRC reconfiguration (RRCReconfiguration) message to the Relay UE.
  • RRC reconfiguration RRCReconfiguration
  • the source base station may send CHO configuration information to the Relay UE through the RRCReconfiguration message, and the CHO configuration may include handover execution conditions and air interface configuration information of each candidate cell.
  • the handover execution condition of each cell may be generated by the source base station, and the air interface resource configuration may be generated by the target base station and sent to the source base station (refer to step 804).
  • the source base station may carry the CHO configuration in the information element IE ConditionalReconfiguration of the RRCReconfiguration message, and its specific content is as follows:
  • Each set of CHO configuration may be as shown in IE CondRecondfigToAddMod, which may include: assigned identifier condReconfigId, handover execution condition conExecutionCond, and wireless air interface resource configuration information condRRCReconfig.
  • the CHO switching execution conditions can include two types: CondEvent A3 and CondEvent A5:
  • -CondEvent A3 The signal quality of the candidate target cell is higher than that of the current serving cell and higher than the configured offset (Conditional reconfiguration candidate becomes amount of offset better than PCell/PSCell).
  • -CondEvent A5 The signal quality of the current serving cell is less than threshold 1, and the signal quality of the candidate target cell is greater than threshold 2 (PCell/PSCell becomes worse than absolute threshold1 AND Conditional reconfiguration candidate becomes better than another absolute threshold2).
  • the specific parameter configuration can refer to the IE CondTriggerConfig in the protocol 38.331, and will not be repeated here.
  • Step 806 Relay UE sends RRC reconfiguration complete (RRCReconfigurationComplete) message to source base station.
  • the Relay UE replies an RRCReconfigurationComplete message to the source base station, which may indicate that the Relay UE has received and saved the corresponding CHO configuration information.
  • the CHO configuration information can support subsequent updates. For example, before the CHO is triggered or the CHO is executed, the configuration information generated by the source base station can be updated, and the source base station or other network side equipment can determine whether to update the CHO configuration.
  • Step 807 Trigger CHO condition judgment.
  • the Relay UE After receiving the CHO configuration, the Relay UE maintains the connection with the source base station, and continuously detects whether there is a candidate target cell that satisfies the handover execution condition.
  • Step 808 Execute switching.
  • the Relay UE detects that a candidate target cell meets the handover execution conditions, the UE disconnects from the source base station, and accesses the target base station according to the radio resource configuration corresponding to the candidate target cell in the CHO configuration.
  • Step 809 the Relay UE sends an RRC reconfiguration complete (RRCReconfigurationComplete) message to the target base station.
  • the Relay UE can reply an RRC reconfiguration complete RRCReconfigurationComplete message to the target base station, which is used to indicate that the Relay UE successfully accesses and applies corresponding configuration.
  • Step 810 the target base station sends a handover success (Handover Success) message to the source base station.
  • the target base station sends a handover success message to the source base station, informing the source base station that the UE has successfully accessed a certain cell under the target base station.
  • Step 811 the source base station sends a handover cancel (Handover Cancel) message to other candidate target base stations.
  • the source base station can send a Handover Cancel message to other configured candidate target cells, instructing them to release the corresponding CHO configuration, so as to release the resources reserved by the candidate target base station for the CHO configuration.
  • the above is the communication method of CHO handover according to the present application.
  • the Relay UE when the Relay UE performs cell handover, the Relay UE may instruct the Remote UE to reselect the Relay UE, and the Relay UE may also trigger the Remote UE to perform RRC re-establishment.
  • the Relay UE when the Relay UE performs CHO handover, the Relay UE will instruct the Remote UE to disconnect from itself and instruct it to perform Relay UE reselection. Therefore, this implementation method cannot support that when the Relay UE performs CHO handover, the Remote UE is handed over to the target cell together with the Relay UE, that is, group handover is performed. Moreover, for the Remote UE, it will take a long time to reselect the Relay UE and perform the re-establishment process.
  • the Remote UE will experience a longer service interruption time, resulting in reduced data transmission efficiency.
  • a design goal of the embodiment of this application is to solve the problem of how to support the Remote UE to handover from the source cell to the target cell together with the Relay UE when the Relay UE performs conditional handover under the L2 U2N relay communication architecture , that is, to solve the problem of how to support group handover when the CHO handover is triggered by the Relay UE.
  • the embodiment of the present application aims at the scenario where the Relay UE performs CHO handover, and designs a set of schemes in which the Remote UE can handover from the source cell to the target cell together with the Relay UE when the CHO handover execution condition of the Relay UE is triggered.
  • the main idea of which includes: during the CHO handover process, the source base station instructs the target base station to provide CHO configurations of multiple candidate target cells to the Relay UE and the Remote UE at the same time.
  • the Relay UE triggers the CHO handover execution condition, the Relay UE instructs the Remote UE to apply the corresponding configuration, so that the Relay UE can access the target cell without disconnecting the connection with the Relay UE.
  • At least one of the following or similar expressions refer to any combination of these items, including any combination of single or plural items.
  • at least one item (piece) of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or, a and b and c, wherein a, b , c can be single or multiple.
  • words such as “first” and "second” are used to distinguish the same or similar items with basically the same function and effect.
  • words such as “first” and “second” do not limit the quantity and execution order, and words such as “first” and “second” do not necessarily limit the difference.
  • words such as “exemplary” or “for example” are used as examples, illustrations or illustrations. Any embodiment or design scheme described as “exemplary” or “for example” in the embodiments of the present application shall not be interpreted as being more preferred or more advantageous than other embodiments or design schemes.
  • the use of words such as “exemplary” or “such as” is intended to present related concepts in a concrete manner for easy understanding.
  • the network architecture and business scenarios described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute limitations on the technical solutions provided by the embodiments of the present application. With the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • the network nodes involved in the embodiments of the present application generally refer to radio access network (radio access network, RAN) equipment in the wireless communication network or a component of the radio access network equipment, the radio access network
  • the equipment can be various types of base stations, such as gNB, LTE eNB, NR gNB or ng-eNB, or the wireless access network equipment is a centralized unit (CU) in the base station, or a distributed unit in the base station (distributed unit, DU).
  • the radio access network equipment is connected to the core network EPC or 5GC.
  • the terminal equipment referred to in the embodiment of the present application is also called user equipment (user equipment, UE), mobile station (mobile station, MS), mobile terminal (mobile terminal, MT), etc.
  • Devices with data connectivity for example, handheld or vehicle-mounted communication devices with wireless connectivity.
  • the terminal device can be: mobile phone (mobile phone), tablet computer, notebook computer, palmtop computer, mobile internet device (mobile internet device, MID), wearable device, virtual reality (virtual reality, VR) device, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, wireless terminals in smart grid Terminals, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, terminal devices can also be roadside units in vehicle networking communication systems (Road Side Unit, RSU), or the communication device or communication chip in the RSU is not limited in this embodiment of the present application.
  • vehicle networking communication systems Road Side Unit, RSU
  • a terminal device especially refers to a device capable of sidelink communication, and the terminal device can be divided into two types: Relay UE, that is, a terminal that can provide relay services for other terminal devices; Remote UE, that is, a terminal that can pass through a relay Terminals that serve access to wireless access network equipment.
  • Relay UE that is, a terminal that can provide relay services for other terminal devices
  • Remote UE that is, a terminal that can pass through a relay Terminals that serve access to wireless access network equipment.
  • Fig. 9 is a schematic structural diagram of a communication device 90 provided in the embodiment of the present application.
  • the communication device 90 can be the first network node or A chip or chip system in the first network node;
  • the communication device 90 may be a relay terminal device or a chip in the relay terminal device Or a chip system;
  • the communication device 90 may be a remote terminal device or a chip or a chip system in the remote terminal device.
  • the implementation of the first network node or the relay terminal device or the remote terminal device in the embodiment of the present application is not limited to the communication device 90, it may also be a Functional logical network entity or node.
  • the communication device 90 may include a processor 901 , a communication line 902 and a communication interface 903 .
  • the communication device 90 may further include a memory 904 .
  • the processor 901 , the memory 904 and the communication interface 903 may be connected through a communication line 902 .
  • the processor 901 may be a central processing unit (central processing unit, CPU), a general-purpose processor, a network processor (network processor, NP), a digital signal processor (digital signal processing, DSP), a microprocessor, a microcontroller , programmable logic device (programmable logic device, PLD) or any combination thereof.
  • the processor 901 may also be other devices with processing functions, such as circuits, devices, or software modules.
  • the communication line 902 is used to transmit information between the components included in the communication device 90 .
  • the communication interface 903 is used to communicate with other devices or other communication networks.
  • the other communication networks may be Ethernet, radio access network (radio access network, RAN), wireless local area networks (wireless local area networks, WLAN), etc.
  • the communication interface 903 may be a radio frequency module or any device capable of realizing wireless communication. This embodiment of the present application is described only by taking the communication interface 903 as an example of a radio frequency module, where the radio frequency module may include an antenna, a radio frequency circuit, and the like, and the radio frequency circuit may include a radio frequency integrated chip, a power amplifier, and the like.
  • the memory 904 is used for storing instructions.
  • the instruction may be a computer program.
  • the memory 904 may be a read-only memory (read-only memory, ROM) or other types of static storage devices capable of storing static information and/or instructions, or may be a random access memory (random access memory, RAM) or may Other types of dynamic storage devices that store information and/or instructions can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD- ROM) or other optical disc storage, optical disc storage, magnetic disk storage media, or other magnetic storage devices, including compact discs, laser discs, compact discs, digital versatile discs, Blu-ray discs, etc.
  • EEPROM electrically erasable programmable read-only memory
  • CD- ROM compact disc read-only memory
  • magnetic disk storage media or other magnetic storage devices, including compact discs, laser discs, compact discs, digital versatile discs, Blu-ray discs, etc.
  • the memory 904 may exist independently of the processor 901 or may be integrated with the processor 901 .
  • the memory 904 can be used to store instructions or program codes or some data, etc.
  • the memory 904 may be located in the communication device 90 or outside the communication device 90 without limitation.
  • the processor 901 is configured to execute instructions stored in the memory 904, so as to implement the communication method provided by the embodiment of the present application or the functions of the involved network entities.
  • the processor 901 may also perform processing-related functions in the communication method provided in the following embodiments of the present application, and the communication interface 903 is responsible for communicating with other devices or communication networks.
  • the embodiment does not specifically limit this.
  • the computer-executed instructions in the embodiments of the present application may also be referred to as application program codes, which is not specifically limited in the embodiments of the present application.
  • the processor 901 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 9 .
  • the communications device 90 may include multiple processors, for example, may further include a processor 907 in addition to the processor 901 in FIG. 8 .
  • the communication apparatus 90 may further include an output device 906 and an input device 907 .
  • the input device 907 is a device such as a keyboard, a mouse, a microphone, or a joystick
  • the output device 906 is a device such as a display screen and a speaker (speaker).
  • composition structure shown in FIG. 9 does not constitute a limitation to the communication device.
  • the communication device may include more or less components than those shown in the illustration, or combine certain components, or a different arrangement of components.
  • system-on-a-chip may be composed of chips, or may include chips and other discrete devices.
  • the network node, the relay terminal device and the remote terminal device in the following embodiments may have components as shown in FIG. 9 or various possible structures.
  • the actions and terms involved in the various embodiments of the present application may refer to each other without limitation.
  • the names of messages exchanged between various devices or the names of parameters in messages are just examples, and other names may also be used in specific implementations, which are not limited.
  • FIG. 10 is a communication method provided by an embodiment of the present application. As shown in FIG. 10, the communication method involves a first network node, a relay terminal device, and a remote terminal device.
  • the communication method may include the following steps:
  • Step 1001 the first network node sends handover request information to the second network node.
  • the handover request information may include: the first identification information of the relay terminal device and the user equipment context information of the relay terminal device, the first identification information of the remote terminal device and the User device context information.
  • the remote terminal device communicates with the first network node through the relay terminal device, and the handover request information is used for the relay terminal device to transfer from the first network node to the second network node Alternatively, it can also be said that the handover request information can be used for the remote terminal device to handover from the first network node to the second network node together with the relay terminal device.
  • the first identification information of the remote terminal device may include at least one of the following: the cell wireless network temporary identifier (cell radio network temporary identifier, CRNTI), the layer 2 identifier of the remote terminal device, and the temporary identifier of the remote terminal device assigned by the first network node to the remote terminal device.
  • the first identification information of the remote terminal device may include: the CRNTI of the remote terminal device allocated by the first network node to the remote terminal device and the layer 2 identifier of the remote terminal device (L2 ID), the L2 ID can be the source L2 ID or the destination L2 ID.
  • the first identification information of the relay terminal device may include at least one of the following: the CRNTI allocated by the first network node to the relay terminal device, the layer 2 identifier of the relay terminal device, and the first network node Temporary identifier assigned to the relay terminal device.
  • the first identification information of the relay terminal device includes the CRNTI of the relay terminal device and the layer 2 identification of the relay terminal device.
  • Step 1002 the first network node receives handover response information from the second network node.
  • the handover response information may include: the second identification information of the relay terminal device and the radio bearer configuration information of the first cell of the second network node configured for the relay terminal device, and, The second identification information of the remote terminal device and the radio bearer configuration information of the first cell of the second network node configured for the remote terminal device.
  • the second identification information of the remote terminal device may be the first identification information of the remote terminal device, that is, the remote The first identification information of the terminal device; or, the second identification information of the remote terminal device may be at least one of the following: the CRNTI of the remote terminal device assigned by the second network node to the remote terminal device , the layer 2 identifier (L2 ID) of the remote terminal device, and the temporary identifier of the remote terminal device assigned by the second network node to the remote terminal device, such as the first
  • the second identification information includes a temporary identification (such as a local ID) and an L2 ID assigned by the second network node to the remote terminal device.
  • the first network node and/or the second network node may each assign a temporary identifier to the remote terminal device according to the Layer 2 identifier of the remote terminal device, and the two are temporary identifiers assigned to the remote terminal device Can be the same or different.
  • the CRNTI of the remote terminal device allocated by the second network node to the remote terminal device may be different from or the same as the CRNTI of the remote terminal device allocated by the first network node.
  • the handover response information may include first configuration information and second configuration information
  • the first configuration information may include: the first configuration information of the second network node configured for the relay terminal device
  • the wireless information of the first cell of the second network node configured for the relay terminal device bearer configuration information including: the RRC bearer configuration information of the relay terminal device in the first cell of the second network node, and the requirements for the relay terminal device to provide the relay service for the remote terminal device
  • the required RLC bearer configuration information of the PC5 interface and the RLC bearer configuration information of the Uu interface the PC5 interface is the communication interface between the relay terminal equipment and the remote terminal equipment, and the Uu interface is the Relying on the communication interface between the terminal device and the second network node
  • the second configuration information may include: radio bearer configuration information of the first cell of the second network node configured for the remote terminal device, and The first identification information of the first cell of the second network node; the radio bearer
  • the first configuration information can generally refer to configuration information related to relay terminal devices
  • the second configuration information can generally refer to Refers to the configuration information related to the remote terminal equipment, and the specific content of the configuration information is not specifically limited in this application.
  • Step 1003 the first network node sends third configuration information to the relay terminal device.
  • the third configuration information may include: radio bearer configuration information of the first cell of the second network node configured for the relay terminal device, and configuration information of the first cell of the second network node The second identification information of the second network node, wherein the first cell of the second network node is a candidate target cell for the relay terminal device to perform handover.
  • Step 1004 The first network node sends fourth configuration information to the remote terminal device.
  • the fourth configuration information includes: the radio bearer configuration information of the first cell of the second network node configured for the remote terminal device, and the configuration information of the first cell of the second network node Second identification information, wherein the first cell of the second network node is a candidate target cell for the relay terminal device to perform handover.
  • the second identification information of the first cell of the second network node may be an identification assigned by the first network node to the first cell of the second network node, such as a cell index index; or
  • the second identity information of the first cell of the second network node may be a global cell identity (CGI), which is sent by the second network node to the first network node through the handover response information in step 1002.
  • CGI global cell identity
  • the first network node configures the cell index for the first cell of the second network node (that is, the candidate target cell of the target base station), or in The CGI of the candidate target cell is provided in the CHO configuration for the Remote UE or the Relay UE, or the ordering information of the configuration of the candidate target cell is provided in the CHO configuration for the Remote UE or the Relay UE, which may exist as an independent implementation mode.
  • the first network node and the second network node may be the same network node, that is to say, the switching of the relay terminal device may be a different network node under the same network node. between districts.
  • Step 1005 the relay terminal device sends the first information to the remote terminal device.
  • this step can be used as an independent embodiment, so that the remote terminal device can apply the determined configuration information of the candidate target cell by sending the first information, thereby accompanying the The relay terminal devices are handed over to the candidate target cell together.
  • the first information sent by the relay terminal device to the remote terminal device can alternatively be understood as a specific implementation manner in which the Relay UE indicates that the Remote UE needs to perform a handover.
  • the premise is that the Remote UE The radio resource configuration of the corresponding candidate target cell has been received from the base station in advance.
  • how the Relay UE instructs the Remote UE to perform handover may be in the manner of sending the first information in this embodiment of the present application.
  • the relay terminal device uses the first information to indicate the remote terminal device: the second identification information of the first cell of the second network node.
  • the first information is used to indicate: the sorting information of the configuration of the first cell of the second network node.
  • the remote terminal device can learn from the first information that the handover target cell of the relay terminal device is the first cell of the second network node described above.
  • the first information is sorting information used to indicate the configuration of the first cell of the second network node, that is, implicitly indicates the radio bearer configuration information corresponding to which cell needs to be applied
  • the second identification information of the first cell of the second network node may also be the physical cell identity (PCI) of the first cell, and the PCI may be considered as the radio bearer corresponding to the cell
  • PCI physical cell identity
  • the content in the configuration information may of course also be other types of identification information, and it is not even necessary to emphasize that there is corresponding identification information. This embodiment of the present application does not limit it.
  • the radio bearer configuration information of the first cell of the second network node configured for the relay terminal device includes: the relay terminal device in the first cell of the second network node RRC bearer configuration information, and the RLC bearer configuration information of the PC5 interface and the RLC bearer configuration information of the Uu interface required by the relay terminal device to provide relay services for the remote terminal device, the PC5 interface is the A communication interface between the relay terminal device and the remote terminal device, the Uu interface is a communication interface between the relay terminal device and the second network node.
  • the relay terminal device sends the first information to the remote terminal device may be replaced by the Relay UE sending indication information to the Remote UE, instructing the Remote UE to apply the CHO configuration.
  • the Relay UE instructs the Remote UE to apply the CHO configuration of the candidate target/alternative cell.
  • the relay terminal device when the first cell of the second network node satisfies a handover trigger condition, the relay terminal device sends the first information to the remote terminal device.
  • the radio bearer configuration information of multiple cells (corresponding to different candidate target cells) received by the remote terminal device or the relay terminal device may respectively correspond to different handover trigger conditions.
  • these handover trigger conditions may be configured by the first network node, and these handover trigger conditions may be that the first network node sends a radio resource control RRC message to the relay terminal device, and the relay terminal device judges whether the handover condition is satisfied .
  • the first network node and the second network node may be a base station gNB, wherein the first network node may be a source base station gNB in a handover procedure, and the second network node may be a target base station gNB in a handover procedure.
  • the relay terminal device may be a Relay UE in the U2N network, and the remote terminal device may be a Remote UE in the U2N network.
  • the Remote UE can perform group handover together with the Relay UE.
  • the source base station carries the handover request information of the Relay UE and the Remote UE in the handover request, instructs the candidate target base station to provide the configuration required for CHO handover for the Relay UE and the Remote UE, and the candidate target base station sends the required configuration configuration through the handover response information
  • the information is sent to the source base station, and then sent to the Relay UE and Remote UE by the source base station.
  • the Relay UE can instruct the Remote UE to enable the corresponding CHO configuration (such as enabling the configuration of a cell of the target base station), so that the Remote UE can handover from the source cell to the target together with the Relay UE
  • the cell can reduce the service interruption time of Remote UE and improve service efficiency.
  • an embodiment of the present application also provides a schematic flowchart of a communication method for CHO handover, the communication method involves a remote terminal Equipment (as shown in the figure: Remote UE1, Remote UE2), relay terminal equipment (Relay UE), source base station (for example: source next generation radio access network equipment, source next generation radio access network NG-RAN), target base station (for example : Target NG-RAN), wherein, in this embodiment, the Relay UE provides relay services for Remote UE1 and Remote UE2 as an example. It can be understood that the Relay UE can also provide relay services for more Remote UEs. For the sake of this embodiment, it is not shown again.
  • a remote terminal Equipment as shown in the figure: Remote UE1, Remote UE2
  • Relay UE relay terminal equipment
  • source base station for example: source next generation radio access network equipment, source next generation radio access network NG-RAN
  • target base station for example : Target NG-RAN
  • the Relay UE provides relay services for Remote UE1 and Remote UE2
  • the Relay UE preparing for CHO handover is generally in the RRC connected state (RRC connected state), may also be in the idle state (Idle state), or in the RRC inactive state (RRC inactive state) ).
  • Remote UE1 and Remote UE2 can access the serving base station of the Relay UE through the Relay UE, that is, the source base station in handover, and perform uplink and/or downlink with the base station respectively For data interaction, uplink or downlink data interaction can also be performed between the Relay UE and the base station.
  • the base station performs CHO configuration for the Relay UE, it simultaneously performs CHO configuration for the Remote UE subordinate to the Relay UE, and when the Relay UE triggers CHO handover, simultaneously triggers
  • the Remote UE refers to the corresponding CHO configuration, so that the Remote UE can handover from the source cell to the target cell together with the Relay UE, and realize that the Remote UE can perform group handover together with the Relay UE.
  • the communication method shown in Figure 11 includes:
  • Step 1101 measurement configuration and measurement reporting.
  • the source base station performs measurement configuration on the Relay UE, and provides measurement-related configuration information to the Relay UE, and then the Relay UE can trigger a measurement action and/or send a measurement report to the base station according to the measurement configuration provided by the source base station.
  • Step 1102 CHO decision.
  • the source base station can decide to execute CHO according to the content of the measurement report reported by the Relay UE, and select multiple candidate target cells.
  • the multiple target cells can belong to different target base stations, or they can belong to the same base station, that is, the target cell There can be one or more base stations. It can be understood that the source base station and the target base station may also be the same, and the handover involved in this case is the handover between different cells under the same base station.
  • Step 1103 the source base station sends a handover request to the target base station.
  • the source base station may send a handover request (handover request, HO request) message to one or more candidate target base stations.
  • a handover request handover request, HO request
  • the handover request message may carry context information of the Relay UE and context information of one or more Remote UEs.
  • UE context information may include: UE security capabilities, access stratum (access stratum, AS) security information, UE protocol data unit (protocol data unit, PDU) session resource information (such as mapping rules from QoS flows to radio bearers), radio One or more of resource control (radio resource control, RRC) radio bearer configuration information and other content.
  • the target base station can perform admission control according to the received UE context information of the Relay UE and/or Remote UE, and allocate transmission resources for the UE.
  • the handover request message may also carry target cell ID information (such as cell global identifier, CGI) and handover indication information to inform the target base station that the source base station requests handover, such as CHO handover.
  • target cell ID information such as cell global identifier, CGI
  • handover indication information to inform the target base station that the source base station requests handover, such as CHO handover.
  • a handover request message may be sent separately for the multiple target cells involved, for requesting handover of the Relay UE to a certain candidate target cell.
  • the handover request message may carry identifier (identifier, ID) information of the Relay UE and the Remote UE to indicate which UEs different UE contexts belong to, for example, the Relay UE identifier information carried in the handover request message may include : the cell radio network temporary identifier (C-RNTI) of the Relay UE, the identification information of the Remote UE carried in the handover request message may include: the C-RNTI of the Remote UE and/or the L2 ID of the Remote UE, Wherein, the L2 ID of the Remote UE may be the destination L2 ID of the Remote UE, or may be the source L2 ID of the Remote UE.
  • C-RNTI cell radio network temporary identifier
  • the ID information of the Relay UE and the ID information of the Remote UE described here are associated with their respective UE contexts.
  • the handover request message sent by the source base station to the target base station can carry the XnAP ID information of the Relay UE (that is, the ID information on the Xn interface allocated by the source base station for the Relay UE), therefore,
  • the handover request message only the UE context of the Remote UE can carry ID information, and use the ID information to indicate that the UE context information corresponds to the Remote UE, for example, the handover request message can carry the C-RNTI of the Remote UE or the Remote UE The L2 ID (source L2 ID or destination L2 ID) or the temporary ID information allocated by the source base station for the Remote UE.
  • the source base station may also separately send a handover request message to the target base station for each UE, that is, each handover request message may only carry information related to the handover request of a certain UE.
  • Step 1104 the source base station receives the handover feedback sent by the target base station.
  • one or more candidate target base stations can reply a handover request feedback (HANDOVER REQUEST ACK) message to the source base station, and each candidate target cell can correspond to a HANDOVER REQUEST ACK message, and the handover request feedback message can be Carrying the ID information of the candidate target cell (such as CGI), the HANDOVER REQUEST ACK message can also include the radio bearer configuration information in the candidate target cell generated by the target base station for the Relay UE and the Remote UE respectively, that is to say, the candidate target base station is the Relay UE
  • the radio resources are reserved for the access of the Remote UE, and the radio bearer configuration information can be configured to the corresponding Relay UE and Remote UE through RRC signaling.
  • the HANDOVER REQUEST ACK message may include a handover command (Handover Command) message
  • the Handover Command message includes radio bearer configuration information generated by the target base station for the Relay UE and the Remote UE respectively in the candidate target cell.
  • the radio bearer configuration information of the candidate target cell can also carry the ID information of the Remote UE to indicate which radio bearer configuration information of the candidate target cell corresponds to Remote UE.
  • the Remote UE ID information may be carried in the radio bearer configuration information configured for the Relay UE and the Remote UE through the RRC message, and the Remote UE ID information may be the local ID information allocated by the target base station for the Remote UE, wherein, for the RelayUE In the configuration information of the Remote UE, the mapping relationship between (local ID, DRB ID) and the Uu RLC channel/PC5 RLC channel of the Remote UE may also be included, wherein the local ID may be the temporary local identifier of the Remote UE configured by the target base station, The DRB ID is the identifier of the data radio bearer of the Remote UE, the Uu RLC channel is the Uu interface radio link control RLC channel between the Relay UE and the source base station/target base station, and
  • the handover request feedback message may carry the Remote UE ID information carried in the previous handover request message, that is, the Remote UE ID information carried in the handover request feedback message may include the C-UE of the Remote UE allocated by the source base station. RNTI, or the Remote UE ID information may include temporary ID information (for example, a local local identifier) allocated by the source base station for the Remote UE and the L2 ID of the Remote UE.
  • the Remote UE ID information can also be the C-RNTI allocated by the candidate target base station for the Remote UE, or, the Remote UE ID information can also be the temporary ID information allocated by the candidate target base station for the Remote UE and the L2 ID of the Remote UE.
  • the candidate target base station may also send a HANDOVER REQUEST ACK message to the source base station separately for each UE.
  • the HANDOVER REQUEST ACK message does not need to carry the above ID information to distinguish different UEs.
  • the target base station can carry one or more of the following in each radio bearer configuration information: the C-RNTI allocated by the source base station for the Remote UE, the L2 ID of the Remote UE, the C-RNTI allocated by the target base station for the Remote UE, And the temporary ID assigned by the target base station to the Remote UE, for the routing of the data of the Remote UE.
  • Step 1105 The source base station sends an RRC reconfiguration message to the Relay UE.
  • the source base station can send the configuration information for CHO to the Relay UE through the RRC Reconfiguration message, and the CHO configuration information can include: the CHO handover execution condition (CHO execution condition) generated by the source base station for the Relay UE, and the candidate target base station The radio bearer configuration information of the candidate target cell generated for the Relay UE.
  • the CHO handover execution condition CHO execution condition
  • the candidate target base station The radio bearer configuration information of the candidate target cell generated for the Relay UE.
  • the radio bearer configuration information generated by the candidate target base station for the Relay UE may include: radio bearer configuration information between the Relay UE and the candidate target base station, and may also include radio bearer configuration information required to provide relay services for the Remote UE
  • the radio bearer configuration information required to provide the relay service for the Remote UE may include: PC5 RLC bearer configuration and Uu RLC bearer configuration, wherein the PC5 RLC bearer refers to the bearer between the Relay UE and the Remote UE, and the Uu RLC bearer configuration Refers to the bearer between the Relay UE and the candidate target base station.
  • the radio bearer configuration information of the Relay UE may also include a mapping relationship between the radio bearer of the Remote UE and the PC5 RLC bearer/Uu RLC bearer.
  • the above mapping relationship includes one or more of the following mapping relationships: the ID information of the Remote UE, the RB ID (DRB ID or SRB ID) of the Remote UE, the PC5 RLC bearer and the Uu RLC bearer.
  • Step 1105a the Relay UE sends an RRC Reconfiguration Complete (RRC Reconfiguration Complete) message to the source base station.
  • the Relay UE can receive and save the above-mentioned CHO configuration information sent by the source base station (such as step 1105), and then the Relay UE can reply the RRC reconfiguration complete message to the source base station to indicate that the source base station has successfully received the CHO configuration.
  • Step 1106 the source base station sends an RRC reconfiguration message to the Remote UE, and the Remote UE replies an RRC reconfiguration complete message to the source base station.
  • the source base station may send the radio bearer configuration information generated by the candidate target base station for the Remote UE in the candidate target cell to the Remote UE1 and the Remote UE2 through the RRC reconfiguration message.
  • the radio bearer configuration information of the Remote UE may include: end-to-end radio bearer configuration between the Remote UE and the candidate target cell and PC5 RLC bearer configuration information.
  • the PC5 RLC bearer configuration information may include: the mapping relationship between the Remote UE's bearer identifier (or the Remote UE's temporary identifier and the bearer identifier) and the PC5 RLC bearer.
  • the source base station may carry the ID information of the candidate target cell in the radio bearer configuration information of each candidate target cell sent to the Relay UE or the Remote UE, and the ID information of the candidate target cell may be CGI, Both the HANDOVER REQUEST message and the HANDOVER REQUEST ACK message can carry the CGI of the candidate target cell; or, the source base station can assign an index identifier to each candidate target cell, and the index identifier information is the same as that configured for the Relay UE/Remote UE respectively.
  • the radio bearer configuration information has an association relationship; or the source base station can encapsulate the radio bearer configurations of multiple target cells in a certain order, and keep the same or corresponding order of the radio bearer configurations sent to the Relay UE and Remote UE through the RRC message.
  • the source base station can send the CHO configuration to the Relay UE and the Remote UE through separate RRC Reconfiguration messages respectively.
  • the source base station can also carry all the configuration information of the Relay UE and the Remote UE in the same RRC message and send it to the Relay UE, and then the Relay UE forwards it to the corresponding Remote UE.
  • Step 1107 Determine whether the handover execution condition is met.
  • the Relay UE After the Relay UE receives the CHO configuration, the Relay UE continues to maintain the connection and transmission with the source base station, and continuously judges whether there is a target cell that meets the handover execution conditions.
  • the Relay UE detects that a candidate target cell meets the handover execution conditions, it can actively perform handover to the candidate target cell that meets the requirements according to the received CHO configuration information, and can disconnect the serving cell of the source base station.
  • the CHO configuration information accesses the candidate target cell.
  • Step 1108 access the target base station.
  • the Relay UE can access the candidate target cell of the target base station through a random access procedure (Random access procedure).
  • Step 1109 RRC reconfiguration complete message.
  • the Relay UE may send an RRC Reconfiguration Complete message to the base station where the candidate target cell is located, indicating that the establishment of the RRC connection is completed.
  • Step 1110 the Relay UE sends indication information to the Remote UE.
  • the Relay UE sends indication information to the Remote UE, and the indication information can be used to notify the Remote UE that the CHO condition of a candidate target cell has been triggered.
  • the Relay UE sends the indication information to Remote UE1 and Remote UE2 respectively, and the Relay UE can also decide which Remote UE needs to be handed over with it as needed To the target cell, the indication information is only sent to the Remote UE that needs to be handed over.
  • the Relay UE can instruct the corresponding Remote UE to apply the radio bearer configuration information configured through the RRC message of the candidate target cell, so that it can access the target cell under the target base station together with the Relay UE. Therefore, in the above indication information, the Relay UE may carry the ID information of the candidate target cell received in step 1105 or the index identification information configured by the source base station for the candidate target cell. The Remote UE can apply radio configuration information corresponding to the ID information or index identification information of the candidate target cell according to the indication information.
  • the Relay UE may also use an implicit indication to trigger the Remote UE to apply the radio bearer configuration information corresponding to the selected candidate target cell.
  • n is a positive integer, corresponding to n candidate target cells
  • Step 1011 the Remote UE sends an RRC reconfiguration complete message to the source base station.
  • the Remote UE can select the wireless configuration of the corresponding candidate target cell according to the instructions of the Relay UE, reset the media access control (Media Access Control, MAC) layer, and perform PC5 communication between the Remote UE and the Relay UE.
  • the RLC bearer is re-established, and then the Remote UE can reply an RRC Reconfiguration Complete message to the target base station through the Relay UE, indicating that the establishment of the RRC connection to the target base station has been completed.
  • the adaptation layer of the Relay UE can add the temporary ID information assigned by the target base station to the Remote UE on the data adaptation layer head, so that the target base station can It can identify which Remote UE the RRC reconfiguration complete message comes from.
  • Step 1112 the target base station sends a handover success (Handover Success) message to the source base station.
  • the target base station after the target base station receives the RRC Reconfiguration Complete message sent by the Relay UE and/or the Remote UE, it can notify the source base station through a HANDOVER SUCCESS message that the Relay UE and/or the Remote UE are successfully handed over from the source cell to the target cell.
  • the HANDOVER SUCCESS message can carry the XnAP ID information of the corresponding UE, that is, one UE corresponds to one HANDOVER SUCCESS message, and the ID information of the corresponding target cell.
  • the source base station may also carry the indication information of the successful handover of the Remote UE in the HANDOVER SUCCESS message of the Relay UE, for example, in the Relay UE
  • the ID information of the Remote UE carried in step 1104 may be carried in the HANDOVER SUCCESS message of the UE, for example, the ID information of the Remote UE may be the C-RNTI of the Remote UE in the source base station or the temporary ID allocated by the source base station for the Remote UE, Or, alternatively, the L2 ID of the Remote UE can be carried in the HANDOVER SUCCESS message of the Relay UE.
  • Step 1113 the source base station sends a HANDOVER CANCEL message to the target base station.
  • the source base station can learn that the relay UE and/or the Remote UE have successfully handed over to the target cell according to the HANDOVER SUCCESS message received in step 1112, then the source base station can send a HANDOVER CANCEL message to the target base stations where the remaining candidate target cells are located, Instruct the candidate target base station to release the pre-configured air interface resources for the Relay UE and Remote UE under the remaining candidate target cells.
  • the Remote UE and the Relay UE are handed over from the source cell to the target cell.
  • the Remote UE can follow the Relay UE to complete the group handover.
  • the embodiment of the present application also proposes the following design.
  • some Remote UEs may be selectively supported to perform group handover, so as to save resource overhead.
  • the Relay UE performs measurement and reports the measurement report.
  • the candidate target base station needs to reserve the air interface resources of the candidate target cell for the Relay UE and the Remote UE subordinate to the Relay UE, so that the subsequent CHO handover execution conditions can be triggered.
  • the Relay UE and the Remote UE can access the candidate target cell.
  • the number of Remote UEs under the Relay UE is large, it means that the candidate target base station needs to reserve a large amount of resources, and when the Remote UE accesses or leaves the Relay UE, it will frequently trigger the CHO configuration update of the candidate target base station side.
  • group handover may be reported to network equipment (such as a base station) as a UE capability, that is, some Remote UEs may support group handover, and some Remote UEs may not support group handover, then Information about whether a certain Remote UE can support group handover can be reported to the base station.
  • the base station can judge whether the HANDOVER REQUEST message in the above step 1103 carries handover request indication information corresponding to the Remote UE according to the capability of the UE.
  • the source base station may select one of the Remote UEs according to the specific conditions of multiple Remote UEs or based on the specific implementation of the base station, and carry the handover request information for the Remote UE in the HANDOVER REQUEST message
  • the base station can judge the link stability between the Relay UE and the Remote UE according to the sidelink link signal quality reported by the Relay UE
  • CHO configuration can be performed on the Remote UE so that the Remote UE performs group handover along with the Relay UE.
  • the remaining Remote UEs that have not been configured with CHO can perform RRC re-establishment procedures with the network side after the Relay UE is handed over.
  • the message may carry:
  • the Relay UE after the Relay UE receives the CHO configuration issued by the source base station, it can know which Remote UEs will perform group handover with itself. Therefore, when the CHO handover execution condition is triggered in step 1107, the Relay The UE may only send CHO handover indication information to these Remote UEs.
  • the embodiment of the present application provides an implementation scheme in which when the Relay UE performs CHO handover, the Remote UE performs group handover together.
  • the source base station may carry the handover request information of the Relay UE and the Remote UE in the CHO handover request sent to the candidate target base station, and instruct the candidate target base station to provide the wireless configuration required for CHO handover for the Relay UE and the Remote UE.
  • the candidate target base station can send the CHO configuration information to the source base station through the HANDOVER REQUEST ACK message, and the source base station sends it to the Relay UE and the Remote UE. Therefore, when the CHO handover execution condition of the Relay UE is triggered, the Remote UE can be instructed to enable the corresponding CHO configuration, so that the Remote UE can handover from the source cell to the target cell together with the Relay UE.
  • the source base station will simultaneously perform handover requests for the Relay UE and the Remote UE, and the candidate target base station can simultaneously perform CHO configuration for the Relay UE and the Remote UE, and reserve corresponding air interface resources.
  • the Relay UE instructs the Remote UE to enable the configuration corresponding to the corresponding handover target cell, so that the Remote UE can handover from the source cell to the target cell together with the Relay UE, and does not need to be disconnected from the Relay UE connection between PC5.
  • the service interruption time of the Remote UE can be reduced.
  • the embodiment of the present application also provides another communication method for CHO, which mainly describes how to The workflow of CHO configuration update, that is, after the candidate target base station sends the configuration information required for CHO handover to the Relay UE or Remote UE, the CHO configuration is not static and can be updated. Before the CHO handover execution condition is triggered, the CHO configuration can be updated as needed. For example, when a new Remote UE accesses the Relay UE or the Remote UE leaves the Relay UE, the source base station or candidate target base station can trigger the update of the CHO configuration .
  • the communication method includes:
  • Step 1201 the Remote UE accesses the source base station through the Relay UE.
  • the Remote UE 3 is connected to the source base station through the Relay UE. It can be understood that the Relay UE may provide relay communication services to other Remote UEs at the same time, which is not shown in the figure.
  • the source base station referred to in the embodiment of the present application can be understood as generally referring to the source-test network equipment involved in the handover process, for example, it may be the source NG-RAN as shown in the accompanying drawing.
  • the target base station which can be understood as generally referring to the target-side network equipment involved in the handover process.
  • Step 1202 CHO configuration update decision.
  • the source base station After the source base station finds that there is a new Remote UE 3 access, it triggers the CHO handover process, so as to configure the CHO configuration information for the Remote UE 3 and update the CHO configuration on the Relay UE side.
  • the source base station can first determine whether the Remote UE supports group handover, or the source base station can according to the link quality between the Remote UE and the Relay UE, or the source base station can according to the service requirements of the Remote UE, to choose whether to configure CHO for Remote UE and update CHO configuration for Relay UE.
  • Step 1203 the source base station sends a handover request message to one or more candidate target base stations.
  • the source base station sends a handover request (HANDOVER REQUEST) message to the candidate target base station
  • the handover request message may carry handover request information for each Remote UE, for example, carry the handover request information of the newly accessed Remote UE3 (including the ID information of the Remote UE3), to instruct the candidate target base station to perform CHO configuration on the newly accessed Remote UE3.
  • the HANDOVER REQUEST message may carry the handover request information of multiple Remote UEs, or may send a HANDOVER REQUEST message separately for each newly accessed Remote UE.
  • step 1103 in the embodiment shown in FIG. 11 , which will not be repeated here.
  • Step 1204 the source base station receives handover request feedback messages sent by one or more candidate target base stations.
  • the candidate target base station after receiving the HANDOVER REQUEST message sent by the source base station, performs CHO configuration for the newly accessed Remote UE3, and reserves air interface resources. Then send the CHO configuration information of Remote UE3 to the source base station through the HANDOVER REQUEST ACK message.
  • the HANDOVER REQUEST ACK message For the manner in which the HANDOVER REQUEST ACK message carries the CHO configuration of the Remote UE3, reference may be made to step 1104 in the embodiment shown in FIG. 11 . It can be understood that if there are multiple Remote UEs, the configuration information of multiple Remote UEs can be carried in one HANDOVER REQUEST ACK message, or the configuration information of each Remote UE can be carried in different separate HANDOVER REQUEST ACK message.
  • the CHO configuration information required by the Remote UE3 may include two parts.
  • the first part is configuration information on the Remote UE side, which may include: the end-to-end radio bearer configuration of the Remote UE in the target cell, and/or, the The PC5 RLC bearer configuration between the Remote UE and the Relay UE
  • the second part is the configuration information on the Relay UE side corresponding to the Remote UE, which can include: the PC5 of the Relay UE required by the Relay UE to provide relay services for the Remote UE Configuration information of RLC bearer and Uu RLC bearer.
  • the CHO configuration of the Remote UE3 may also include the ID information of the Remote UE3. Specifically what is the ID information of the Remote UE3, you can refer to the description about the ID information of the Remote UE in step 1104, and will not repeat them here
  • Step 1205 The source base station sends an RRC reconfiguration message to the Relay UE.
  • the source base station can send the CHO configuration information on the Relay UE side to the Relay UE through the RRC reconfiguration message.
  • Step 1206 The Relay UE feeds back an RRC reconfiguration complete message to the source base station.
  • the Relay UE may indicate to the source base station that the CHO configuration information on the Relay UE side has been received by replying the RRC reconfiguration complete message.
  • Step 1207 The source base station sends an RRC reconfiguration message to the Remote UE3.
  • the source base station can send the CHO configuration information on the Remote UE side to the Remote UE3 through the RRC reconfiguration message, and the CHO configuration can include the identification information of the target cell.
  • the identification information of the target cell can be
  • the CGI may also be cell ID information configured by the source base station for the target cell, such as cell index information.
  • Step 1208 The Remote UE sends an RRC reconfiguration complete message to the source base station.
  • the Remote UE3 can reply the RRC reconfiguration complete message to the source base station, indicating that the source base station Remote UE3 has received the CHO configuration information.
  • the above is an example of the CHO configuration update process in the scenario where a new Remote UE accesses a Relay UE.
  • the following takes the disconnection of the Remote UE and the connection of the Relay UE as an example to continue to introduce another CHO configuration update process.
  • the source base station may send indication information to one or more candidate target base stations, where the indication information is used to indicate that the one or more candidate target base stations are performing
  • the air interface resources reserved for the Remote UE during CHO configuration including release: the end-to-end radio bearer configuration and PC5 RLC bearer configuration in the candidate target cell pre-configured for the Remote UE, and release: providing relay for the Remote UE PC5 RLC bearer and Uu RLC bearer configuration on the Relay UE side required for the service.
  • the indication information may include the ID information of the Remote UE.
  • the ID information of the Remote UE may be the L2 ID of the Remote UE, or the temporary identification local ID allocated by the source station or the target station for the Remote UE, or It may be the CRNTI allocated by the source station or the target station for the Remote UE, or a combination of one or more of the Remote UE ID information mentioned here, which is not limited in this embodiment of the present application.
  • the source base station can also send an RRC reconfiguration message to the Relay UE to update the CHO configuration on the Relay UE side.
  • One purpose of the update is to release the new configuration on the Relay UE side and the remote UE that has left. configuration.
  • the RRC reconfiguration message sent by the source base station to the Relay UE may include the ID information of the departing Remote UE, and the ID information of the Remote UE may be the L2 ID of the Remote UE, or may be the source station or the target The local ID assigned by the station to the Remote UE, or the CRNTI assigned by the source station or the target station to the Remote UE, or one or more of the types of Remote UE ID information mentioned here In combination, this embodiment of the present application does not limit it.
  • the source base station can trigger a new CHO handover process, so that the candidate target base station side, the Relay UE side and the CHO configuration information of other Remote UEs are reconfigured.
  • the reconfiguration process reference may be made to the embodiment process shown in FIG. 11 , which will not be repeated here.
  • the main ideas include: for the handover process, configure the corresponding CHO configuration for the Remote UE and the Relay UE in advance, and when the CHO handover execution condition of the Relay UE is triggered, the Relay UE instructs the Remote UE to execute
  • the corresponding configuration enables the Remote UE to follow the Relay UE to access the target base station without disconnecting the connection with the Relay UE.
  • this method can reduce The length of service interruption of the small Remote UE, thereby improving the efficiency of data transmission.
  • the embodiment of this application also proposes another communication method in which the Relay UE instructs the Remote UE to perform CHO handover.
  • This communication method can be applied to scenarios such as when the Remote UE accesses the source base station through the Relay UE, and the Relay UE generates a Uu interface wireless link radio link failure (RLF), the Relay UE can instruct the Remote UE to perform CHO handover; or when the Remote UE detects PC5 RLF, it can actively trigger the execution of CHO handover.
  • RLF wireless link radio link failure
  • the solution of the embodiment of the present application may include the following parts: 1. How to configure the Remote UE for CHO handover; 2. How to trigger the Remote UE to perform CHO handover.
  • FIG. 13 shows a communication method for CHO handover provided by the embodiment of the present application.
  • the method involves Remote UE, Relay UE, candidate Relay UE (Candidate Relay UE), source Base station Source gNB, target base station Target gNB and candidate target base station (Candidate target gNB), the detailed flow of the communication method may include:
  • Step 1301 The source base station receives the measurement report reported by the Remote UE.
  • the Remote UE performs measurement based on the measurement configuration of the source base station, and reports a measurement report, which may include ID information of multiple surrounding cells of the Remote UE and ID information of surrounding optional Relay UEs.
  • the source base station makes a CHO handover decision based on the measurement report.
  • the source base station may select multiple candidate target cells and/or select candidate Relay UEs under the multiple candidate target cells. It should be noted that the multiple candidate target cells may belong to the same candidate target base station, or may belong to different candidate target base stations.
  • Step 1302 the source base station sends a HANDOVER REQUEST message to one or more candidate target base stations.
  • the HANDOVER REQUEST message can be used to handover the Remote UE to the target cell or the target Relay UE under the target cell.
  • Each target cell can correspond to a HANDOVER REQUEST message.
  • each HANDOVER REQUEST message can carry the ID information (such as CGI) of the target cell, or optionally, the handover request message can carry the ID information of the target cell (such as CGI) and the IDs of one or more candidate target Relay UEs.
  • the ID identifier of the candidate target Relay UE may be the C-RNTI or L2 ID (source L2 ID/destination L2 ID) of the Relay UE.
  • the HANDOVER REQUEST message may also carry context information of the Remote UE.
  • the handover request message may also carry context information of one or more candidate target Relay UEs.
  • each HANDOVER REQUEST message may only carry one candidate target Relay UE, then, the HANDOVER REQUEST message may only carry the context information of this Relay UE.
  • the L2 ID information of the Remote UE may also be carried in the HANDOVER REQUEST message, which is used by the target base station to allocate a temporary identification local ID under the target station for the Remote UE.
  • the HANDOVER REQUEST message can also carry the C-RNTI of the Remote UE under the source station.
  • Step 1303 the source base station receives handover request responses from one or more candidate target base stations.
  • each candidate target cell may correspond to a HANDOVER REQUEST ACK message.
  • the HANDOVER REQUEST ACK message may carry: the ID information (such as CGI) of the candidate target cell and the radio bearer configuration information of the Remote UE; or, the HANDOVER REQUEST ACK message may carry: the ID information of the candidate target cell (such as CGI) and one or more groups: ID information (L2 ID or C-RNTI) of the candidate target Relay UE + radio bearer configuration of the candidate target Relay UE + radio bearer configuration of the Remote UE.
  • ID information such as CGI
  • ID information L2 ID or C-RNTI
  • the Remote UE temporary identification (local ID) and the L2 ID of the Remote UE allocated by the target base station to one or more Remote UEs around the Relay UE can be carried, such that The Relay UE can identify the temporary identifier local ID configured by the target base station for the Remote UE around it based on the Remote UE temporary identifier local ID and the Remote UE's L2 ID.
  • the handover request message and the handover request ACK message exchanged between the source base station and the target base station involved in the embodiment of the present application, as well as the content of the interaction in these two messages can exist as an independent implementation mode to solve the problem of source How the base station and the target base station configure the wireless resources of the candidate target cell for the Relay UE and the Remote UE, and how to provide the Remote UE with the corresponding wireless configuration of the target cell and the wireless configuration of the candidate target Relay UE when RLF occurs in the Relay UE question.
  • each HANDOVER REQUEST ACK message may only carry the configuration information of one candidate target Relay UE, that is, the HANDOVER REQUEST ACK message includes: ID information (such as CGI) of the candidate target cell + ID information of the candidate target Relay UE ( L2 ID or C-RNTI)+the radio bearer configuration (or called CHO configuration) of the candidate target Relay UE+the radio bearer configuration (or called CHO configuration) of the Remote UE.
  • ID information such as CGI
  • ID information of the candidate target cell + ID information of the candidate target Relay UE ( L2 ID or C-RNTI)+the radio bearer configuration (or called CHO configuration) of the candidate target Relay UE+the radio bearer configuration (or called CHO configuration) of the Remote UE.
  • each of the above HANDOVER REQUEST ACK messages may also carry the temporary identifier local ID allocated by the target base station for the Remote UE and the L2 ID of the Remote UE.
  • Step 1304 The source base station sends the configuration of the candidate target Relay UE to the candidate Relay UE through an RRC reconfiguration message.
  • the configuration of the candidate target Relay UE may include one or more of the following: the radio bearer configuration of the candidate target Relay UE in the candidate target cell, ID information of the Remote UE (such as including: L2 ID of the Remote UE+candidate target base station local ID allocated for Remote UE).
  • Step 1305 The candidate Relay UE sends an RRC reconfiguration complete message to the source base station.
  • Step 1306 The source base station sends an RRC reconfiguration message to the Remote UE.
  • the source base station can generate a CHO handover execution condition for each candidate target cell or a candidate Relay UE under each candidate target cell, and then send it to the Remote UE through an RRC reconfiguration message together with the radio bearer configuration information of the Remote UE.
  • the RRC reconfiguration message may include one or more of the following: CHO handover execution conditions, radio bearer configuration of the Remote UE, ID information of the target cell and ID information of the candidate target Relay.
  • the Remote UE can be configured with multiple candidate target Relay UEs, and one relay UE can also correspond to the CHO configuration of multiple Remote UEs. Therefore, the respective configurations of the Remote UE and the Relay UE need to be corresponding.
  • the configuration information received by the Remote UE can include the ID information of the Relay UE, such as the L2 ID of the Relay UE, so that when the CHO handover execution condition of the Remote UE is triggered, it knows which relay UE should be instructed to trigger the surrounding The corresponding CHO configuration.
  • the radio bearer configuration of the Relay UE may include the temporary ID of the Remote UE, or the L2 ID information of the Remote UE may also be carried in the radio bearer configuration of the Relay UE.
  • Step 1307 The Remote UE sends an RRC reconfiguration complete message to the source base station.
  • Step 1308a CHO condition triggers.
  • the Remote UE accesses the target cell or the target Relay UE. If the CHO handover execution condition corresponds to a candidate target Relay UE, the Remote UE can send indication information to the target Relay UE according to the ID information of the Relay UE carried in the CHO configuration, and the Relay UE knows which remote UE triggered the trigger according to the indication information CHO is enabled, then the radio bearer configuration corresponding to the Remote UE is applied.
  • the CHO handover execution condition can be configured as one or more of the following: the Remote UE detects that RLF occurs in PC5, or the Relay UE indicates that the Remote UE has occurred Uu RLF.
  • PC5 is the communication interface between the Remote UE and the Relay UE providing the relay service for the Remote UE
  • Uu is the communication interface between the Relay UE providing the relay service for the Remote UE and the source base station. That is, when one or both of the above two conditions occur, the Remote UE will trigger CHO handover and apply the corresponding CHO configuration.
  • the source base station can only configure the above handover execution conditions in a set of CHO configurations as a backup configuration for the Remote UE.
  • the Remote UE can quickly switch to the target cell and/or the target cell.
  • Target Relay UE can quickly switch to the target cell and/or the target cell.
  • the source base station does not need to configure the above-mentioned CHO handover execution conditions in the CHO configuration, but is stipulated by the protocol.
  • the Remote UE automatically starts from its own set of Alternatively, one of multiple sets of CHO configurations may be selected for execution. For example, the set whose link signal quality configured in the CHO handover execution condition is closest to the threshold may be selected, or a set may be randomly selected. It is also possible that, based on the implementation, the Remote UE selects a set of CHO configurations for switching when the above-mentioned Uu RLF or PC5 RLF occurs.
  • Step 1308 the Relay UE indicates to the Remote UE that RLF occurs.
  • This step is optional, wherein the Relay UE can indicate to the Remote UE that Uu RLF or PC5 RLF occurs.
  • Step 1309 Establish a unicast connection.
  • This step is optional. If there is no unicast connection between the two before, a unicast connection can be established between the Remote UE and the candidate Relay UE.
  • Step 1310 the Remote UE sends a CHO trigger indication to the candidate Relay UE.
  • Step 1311 Send an RRC reconfiguration complete message to the target cell through the Relay UE.
  • the Remote UE may send an RRC configuration completion message to the target cell through the Relay UE after sending the indication information to the Relay UE.
  • Step 1312 Randomly access the target base station.
  • the Remote UE can randomly access the target cell of the target base station according to the corresponding configuration.
  • Step 1313 Send an RRC reconfiguration complete message to the target cell of the target base station.
  • the embodiment of the present application further provides a communication device, and the communication device is used to implement the above-mentioned various methods.
  • the communication device may be the first network node in the above method embodiment, or a device including the above first network node, or a component or computer program that can be used for the first network node. It should be understood that the first network node also It may be a source-side network device in a handover process or a handover preparation process, which is not limited in this embodiment of the present application; or,
  • the communication device may be the second network node in the above method embodiment, or a device including the above second network node, or a component or computer program that can be used for the second network node. It can be understood that the second network node also It may be the target-side network device in the handover process or handover preparation process, which is not limited in this embodiment of the present application; or,
  • the communication device may be the relay terminal device in the above method embodiment, or a device including the above relay terminal device, or a component or computer program that can be used for the relay terminal device. It can be understood that the relay terminal device can It is the Relay UE in the handover process or the handover preparation process, which is not limited in this embodiment of the present application; or,
  • the communication device may be the remote terminal device in the above method embodiment, or a device including the above remote terminal device, or a component or computer program that can be used for the remote terminal device. It can be understood that the remote terminal device can It is the Remote UE in the handover process or the handover preparation process, which is not limited in this embodiment of the present application.
  • the communication device includes hardware structures and/or software modules corresponding to each method/operation/function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software in combination with the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.
  • the embodiment of the present application may divide the functional modules of the communication device according to the above method embodiments.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be realized in the form of hardware, can be realized in the form of software function modules, or can be realized in the form of combining hardware and software. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 14 shows a schematic structural diagram of a communication device 140 .
  • the communication device 140 includes a transceiver module 1401 and a processing module 1402 .
  • the transceiving module 1401 can also be referred to as a transceiving unit to realize the information transceiving function between the communication device and other devices, for example, it can be a transceiving circuit, a transceiver, a transceiver or a communication interface. It should be noted that all relevant content of the steps involved in the above method embodiments can be referred to the function description of the corresponding function module, and will not be repeated here.
  • the communication device 140 is presented in the form of dividing various functional modules in an integrated manner.
  • a “module” here may refer to a specific ASIC, a circuit, a processor and a memory executing one or more software or firmware programs, an integrated logic circuit, and/or other devices that can provide the above-mentioned functions.
  • the communication device 140 may take the form of the communication device 90 shown in FIG. 9 .
  • the processor 901 in the communication device 90 shown in FIG. 9 may invoke the computer-executed instructions stored in the memory 903, so that the communication device 90 executes the communication method in the foregoing method embodiments.
  • the function/implementation process of the transceiver module 1401 and the processing module 1402 in FIG. 14 can be implemented by the processor 901 in the communication device 90 shown in FIG. 9 invoking computer-executed instructions stored in the memory 903 .
  • the function/implementation process of the processing module 1402 in FIG. 14 can be realized by the processor 901 in the communication device 90 shown in FIG. /The implementation process can be implemented through the communication interface 904 in the communication device 90 shown in FIG. 9 .
  • the communication device 140 provided in this embodiment can execute the above-mentioned communication method, the technical effect it can obtain can refer to the above-mentioned method embodiment, and details are not repeated here.
  • sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • a software program it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server, or data center Transmission to another website site, computer, server or data center via wired (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or may be a data storage device including one or more servers, data centers, etc. that can be integrated with the medium.
  • the available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (Solid State Disk, SSD)), etc.
  • a magnetic medium such as a floppy disk, a hard disk, or a magnetic tape
  • an optical medium such as a DVD
  • a semiconductor medium such as a solid state disk (Solid State Disk, SSD)
  • a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer.
  • an application running on a computing device and the computing device can be components.
  • One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers.
  • these components can execute from various computer readable media having various data structures thereon.
  • These components can be communicated via, for example, data based on having one or more packets of data (e.g., data from a component that interacts with another component in a local system, a distributed system, and/or in a signaled network to interact with other systems) to communicate with local and/or remote processes.
  • data e.g., data from a component that interacts with another component in a local system, a distributed system, and/or in a signaled network to interact with other systems
  • the word "exemplary” is used as an example, illustration or description. Any embodiment or design described herein as “example” is not to be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the word example is intended to present concepts in a concrete manner.
  • information information
  • message messages
  • information information
  • message messages
  • “ ⁇ (of)” corresponding (corresponding, relevant)
  • corresponding (corresponding) can sometimes be used interchangeably.
  • System and “network” can sometimes be used interchangeably.
  • communication network also refers to "communication system”.
  • the network architecture and business scenarios described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute limitations on the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了通信方法及其设备，可应用于U2N中继通信，该方法中，源基站向目标基站发送切换请求，其中包括Relay UE的标识及其UE上下文信息，Remote UE的标识及其UE上下文信息；源基站从目标基站接收切换响应，其中包括为该Relay UE配置的候选目标小区的无线承载配置信息，以及为该Remote UE配置的候选目标小区的无线承载配置信息。当发生Relay UE向目标小区切换时，Relay UE可以指示Remote UE应用该目标小区的无线承载配置信息，使得Remote UE能够伴随Relay UE一同切换到目标小区，从而能够减少Remote UE的服务中断的时间。

Description

一种通信协作方法及装置
本申请要求于2021年12月31日提交中国专利局、申请号为202111670280.3、申请名称为“通信方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信领域，尤其涉及适用于切换的通信方法、节点、设备、装置、计算机可读存储介质及系统等。
背景技术
用户设备(user equipment，UE)到网络中继(UE-to-Network relay，U2N Relay)技术，是一种由中继UE(Relay UE)为远端UE(Remote UE)提供中继通信，使得远端UE可以通过中继UE接入到无线接入网设备的通信方法。其中，中继UE和远端UE之间通过PC5接口进行通信，中继UE和远端UE之间的无线通信链路称为侧行链路(sidelink，SL)，中继UE和网络设备之间通过Uu接口进行无线通信，中继UE和网络设备之间无线通信链路可以称为Uu链路(Uu Link)。
在U2N Relay通信架构的基础上，业界进一步提出了U2N组切换(Group Handover)技术，但是当Relay UE处于条件切换(Conditional Handover，CHO)时，现有技术并不能很好的支持Relay UE和Remote UE进行组切换，比如，Remote UE会经历相对较长时间的服务中断。
发明内容
本申请实施例提供了一种通信方法及其网络节点，终端设备等，用于解决现有技术中，在U2N Relay场景下，当Relay UE处于CHO过程中，Remote UE将经历相对较长时间的服务中断的问题。
为解决上述技术问题，示例性的，本申请的实施例采用如下技术方案：
第一方面，提供了一种通信方法，执行该通信方法的实体可以是第一网络节点，也可以是应用于第一网络节点中的功能模块，或者是第一网络节点中的芯片或芯片系统，或者是实现该第一网络节点功能的网络实体或者网络设备。下面以执行主体为第一网络节点为例进行描述。该通信方法可以包括：第一网络节点向第二网络节点发送切换请求信息，该切换请求信息包括：中继终端设备的第一标识信息和所述中继终端设备的用户设备上下文信息，远端终端设备的第一标识信息和所述远端终端设备的用户设备上下文信息；其中，所述远端终端设备通过所述中继终端设备与所述第一网络节点进行通信交互，所述切换请求信息用于所述中继终端设备从所述第一网络节点向所述第二网络节点的小区进行切换；所述第一网络节点从所述第二网络节点接收切换响应信息，所述切换响应信息包括：所述中继终端设备的第二标识信息和为所述中继终端设备配置的所述第二网络节点的第一小区的无线承载配置信息，以及所述远端终端设备的第二标识信息和为所述远端终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息。基于该通信方法，可以 使得在CHO切换中，源基站同时为中继终端设备Relay UE和远端中继设备Remote UE请求在候选目标小区的无线资源配置，这样后续Relay UE需要切换到该候选目标小区时，Remote UE就可以应用该候选目标小区的无线资源配置，伴随该Relay UE一同切换到目标小区，从而可以减少Remote UE的服务中断时间。
结合上述第一方面，在一种可能的实现方式中，该远端终端设备的第一标识信息包括如下中一个或多个：该第一网络节点为该远端终端设备分配的所述远端终端设备的CRNTI，该远端终端设备的层2标识，以及该第一网络节点为该远端终端设备分配的所述远端终端设备的临时标识。
结合上述第一方面，在一种可能的实现方式中，该远端终端设备的第二标识信息包括上述的该远端终端设备的所述第一标识信息，或者，该远端终端设备的第二标识信息包括如下中一个或多个：所述第二网络节点为所述远端终端设备分配的所述远端终端设备的CRNTI，所述远端终端设备的层2标识，以及所述第二网络节点为所述远端终端设备分配的所述远端终端设备的临时标识。
结合上述第一方面，在一种可能的实现方式中，所述切换响应信息中可以包括：该第二网络节点的第一小区的第一标识信息，第一配置信息和第二配置信息；示例性的，该第一配置信息包括：为所述中继终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息；所述为所述中继终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息，包括：所述中继终端设备在所述第二网络节点的所述第一小区的无线承载配置，以及所述中继终端设备为所述远端终端设备提供中继服务所需要的PC5接口的RLC承载配置信息和Uu接口的RLC承载配置信息，其中，该PC5接口是所述中继终端设备和所述远端终端设备之间的通信接口，该Uu接口是所述中继终端设备和所述第二网络节点之间的通信接口；示例性的，该第二配置信息包括：为所述远端终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息；所述为所述远端终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息，包括：所述远端终端设备在所述第二网络节点的所述第一小区的无线承载配置，以及所述远端设备的PC5接口的RLC承载配置信息，所述PC5接口是所述远端终端设备和所述中继终端设备之间的通信接口。
需要说明的是，此处的第一配置信息和第二配置信息是用于行文方便，或者，也可以理解为，所述切换响应信息中可以直接包括该第二网络节点的第一小区的第一标识信息，为所述中继终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息，以及为所述远端终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息。
结合上述第一方面，在一种可能的实现方式中，该第一网络节点向该中继终端设备发送第三配置信息，所述第三配置信息包括：为所述中继终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息，以及所述第二网络节点的所述第一小区的第二标识信息，其中，所述第二网络节点的所述第一小区是所述中继终端设备进行切换的候选目标小区。
结合上述第一方面，在一种可能的实现方式中，该第一网络节点向该远端终端设备发送第四配置信息，所述第四配置信息包括：为所述远端终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息，以及所述第二网络节点的所述第一小区的第二标识信息，其中，所述第二网络节点的所述第一小区是所述中继终端设备进行切换的候选目标小区。
结合上述第一方面，在一种可能的实现方式中，该第二网络节点的所述第一小区的第二标识可以是所述第一网络节点为所述第二网络节点的所述第一小区分配的标识；或者，该第二网络节点的所述第一小区的第二标识可以是全球小区标识CGI，该CGI是由所述第二网络 节点通过所述切换响应信息发送给所述第一网络节点。
结合上述第一方面，在一种可能的实现方式中，该第一网络节点和该第二网络节点为同一个网络节点，也就是说，本申请第一方面所描述的方法可以应用于一个基站下的小区间切换场景。
第二方面，提供了一种通信方法，执行该通信方法的实体可以是中继终端设备，也可以是应用于中继终端设备中的功能模块，或者是中继终端设备中的芯片或芯片系统，或者是实现该中继终端设备功能的网络实体或者网络设备。下面以执行主体为中继终端设备为例进行描述。该通信方法可以包括：该中继终端设备接收第一网络节点发送的第三配置信息，该第三配置信息包括：为所述中继终端设备配置的第二网络节点的第一小区的无线承载配置信息，以及所述第二网络节点的所述第一小区的第二标识信息，其中，所述第二网络节点的所述第一小区是所述中继终端设备进行切换的候选目标小区；该中继终端设备向远端终端设备发送第一信息，该第一信息用于指示该第二网络节点的所述第一小区的所述第二标识信息，或者该第一信息用于指示所述第二网络节点的所述第一小区的配置的排序信息。
基于该通信方法，可以使得在CHO切换中，为中继终端设备Relay UE和远端中继设备Remote UE预先配置候选目标小区的无线资源，这样后续Relay UE需要切换到该候选目标小区时，Relay UE可以向Remote UE指示需要切换至哪一个目标小区(比如通过小区的标识信息)，或者Relay UE可以指示Remote UE需要应用哪个小区的无线资源配置(比如通过小区配置的排序信息)，这样，Remote UE就可以应用相应的目标小区的无线资源配置，伴随该Relay UE一同切换到目标小区，从而可以减少Remote UE的服务中断时间。
结合上述第二方面，在一种可能的实现方式中，该第二网络节点的所述第一小区的所述第二标识可以是该第一网络节点为所述第二网络节点的所述第一小区分配的标识，比如小区索引。
结合上述第二方面，在一种可能的实现方式中，该第二网络节点的所述第一小区的所述第二标识可以是全球小区标识CGI，该CGI可以是由所述第二网络节点通过切换响应信息发送给所述第一网络节点。
结合上述第二方面，在一种可能的实现方式中，为所述中继终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息，可以包括：所述中继终端设备在所述第二网络节点的所述第一小区的无线承载配置，以及所述中继终端设备为所述远端终端设备提供中继服务所需要的PC5接口的RLC承载配置信息和Uu接口的RLC承载配置信息，该PC5接口是所述中继终端设备和所述远端终端设备之间的通信接口，该Uu接口是所述中继终端设备和所述第二网络节点之间的通信接口。
结合上述第二方面，在一种可能的实现方式中，当所述第二网络节点的所述第一小区满足切换触发条件，则所述中继终端设备向所述远端终端设备发送所述第一信息。
第三方面，提供了一种通信方法，执行该通信方法的实体可以是远端终端设备，也可以是应用于远端终端设备中的功能模块，或者是远端终端设备中的芯片或芯片系统，或者是实现该远端终端设备功能的网络实体或者网络设备。下面以执行主体为远端终端设备为例进行描述。该通信方法可以包括：远端终端设备接收第一网络节点发送的第四配置信息，该第四配置信息包括：为所述远端终端设备配置的第二网络节点的第一小区的无线承载配置信息，以及所述第二网络节点的所述第一小区的第二标识信息，其中，所述第二网络节点的所述第 一小区是所述中继终端设备进行切换的候选目标小区；该远端终端设备接收所述中继终端设备发送的第一信息，该第一信息用于指示所述第二网络节点的所述第一小区的第二标识信息，或者该第一信息用于指示所述第二网络节点的所述第一小区的配置的排序信息。
基于该通信方法，可以使得在CHO切换中，为远端中继设备Remote UE和中继终端设备Relay UE预先配置候选目标小区的无线资源，这样后续Relay UE需要切换到该候选目标小区时，通过向Remote UE指示需要切换至哪一个目标小区(比如通过小区的标识信息来指示)，或者需要应用哪个小区的无线资源配置(比如通过小区配置的排序信息来指示)，这样，Remote UE就可以应用相应的目标小区的无线资源配置，伴随该Relay UE一同切换到目标小区，从而可以减少Remote UE的服务中断时间。
结合上述第三方面，在一种可能的实现方式中，该第二网络节点的所述第一小区的所述第二标识可以是该第一网络节点为所述第二网络节点的所述第一小区分配的标识，比如小区索引。
结合上述第三方面，在一种可能的实现方式中，该第二网络节点的所述第一小区的所述第二标识可以是全球小区标识CGI，该CGI可以是由所述第二网络节点通过切换响应信息发送给所述第一网络节点。
结合上述第三方面，在一种可能的实现方式中，为该远端终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息，包括：所述远端终端设备在所述第二网络节点的所述第一小区的无线承载配置，以及所述远端设备的PC5接口的RLC承载配置信息，所述PC5接口是所述远端终端设备和所述中继终端设备之间的通信接口。
结合上述第三方面，在一种可能的实现方式中，当所述第二网络节点的所述第一小区满足切换触发条件，则该第一信息被所述中继终端设备发给所述远端终端设备。
第四方面，本申请提供了一种通信装置，该通信装置可以为第一网络节点或者第一网络节点中的芯片或者芯片系统，还可以是第一网络节点中用于实现第一方面或第一方面的任一可能的设计的功能模块。该通信装置可以实现上述第一方面或其各可能的设计中第一网络节点所执行的功能/操作，所述功能/操作可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能/操作相对应的模块。其中，上述第四方面的技术效果可参考上述第一方面，在此不再赘述。
第五方面，本申请提供了一种通信装置，该通信装置可以为中继终端设备或者中继终端设备中的芯片或者芯片系统，还可以是中继终端设备中用于实现第二方面或第二方面的任一可能的设计的功能模块。该通信装置可以实现上述第二方面或其各可能的设计中的中继终端设备所执行的功能/操作，所述功能/操作可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能/操作相对应的模块。其中，上述第五方面的技术效果可参考上述第二方面，在此不再赘述。
第六方面，本申请提供了一种通信装置，该通信装置可以为远端终端设备或者远端终端设备中的芯片或者芯片系统，还可以是远端终端设备中用于实现第一方面或第一方面的任一可能的设计的功能模块。该通信装置可以实现上述第三方面或其各可能的设计中远端终端设备所执行的功能/操作，所述功能/操作可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能/操作相对应的模块。其中，上述第六方面的技术效果可参考上述第三方面，在此不再赘述。
第七方面，提供了一种通信装置，包括：处理器和存储器；该存储器用于存储计算机指令，当该通信装置运行时，该处理器执行该存储器存储的该计算机指令，以使该通信装置执 行如上述第一方面至第三方面中任一项所述的通信方法。
第八方面，提供了一种通信装置，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述第一方面至第三方面中任一项所述的通信方法。
在一种可能的实现方式中，通信装置还包括存储器；该存储器用于存储计算机指令。
在一种可能的实现方式中，通信装置还包括通信接口；该通信接口用于该通信装置与其它设备进行通信。示例性的，该通信接口可以为收发器、输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。
在一种可能的实现方式中，该通信装置可以是芯片或芯片系统。其中，当该通信装置是芯片系统时，该通信装置可以由芯片构成，也可以包含芯片和其他分立器件。
在一种可能的实现方式中，当通信装置为芯片或芯片系统时，上述通信接口可以是该芯片或芯片系统上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。上述处理器也可以体现为处理电路或逻辑电路。
第九方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第一方面至第三方面中任一项所述的通信方法。
第十方面，提供了一种包含计算机指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面至第三方面中任一项所述的通信方法。
第十一方面，提供了一种通信实体，该通信实体可以实现上述第一至第三方面中的第一网络节点(gNB基站)，Relay UE或者Remote UE的功能或操作，该通信实体包括了用于执行这些操作所需的模块。
第十二方面，提供了一种通信系统，该通信系统可以包括前述中的一个或多个：所述第一网络节点，所述中继终端设备，所述远端终端设备，所述通信实体，所述通信装置，所述计算机可读存储介质，以及所述计算机程序产品。
附图说明
图1(a)为本申请实施例提供的一种UE与UE之间直接通信场景的示意图；
图1(b)为本申请实施例提供的一种UE1和UE2在PC5口通信的控制面协议栈架构
图2为本申请实施例提供的一种可适用于U2N Relay场景的通信网络的示意图；
图3为本申请实施例提供的一种通信系统的用户面协议栈的示意图；
图4为本申请实施例提供的一种通信系统的控制面协议栈的示意图；
图5为本申请实施例提供的一种基于U2N Relay进行组切换的通信场景示意图；
图6为本申请实施例涉及的一种组切换的通信方法的流程示意图；
图7为本申请实施例涉及的又一种组切换的通信方法的流程示意图；
图8为本申请实施例涉及的一种CHO切换的通信方法的流程示意图；
图9为本申请实施例提供的一种通信装置的结构示意图；
图10为本申请实施例提供的一种适用于CHO切换的通信方法的流程示意图；
图11为本申请实施例提供的又一种适用于CHO切换的通信方法的流程示意图；
图12为本申请实施例提供的又一种适用于CHO切换的通信方法的流程示意图；
图13为本申请实施例提供的又一种适用于CHO切换的通信方法的流程示意图；
图14为本申请实施例提供的另一种通信装置的结构示意图。
具体实施方式
在介绍本申请具体实施例之前，对本申请实施例涉及的一些概念或名词进行解释说明。
1、侧行链路/侧行链路通信
在无线通信系统中，UE与UE之间可以通过网络进行数据通信，也可以不借助网络设备，直接进行UE与UE之间的通信。其中，UE与UE之间进行直接通信的接口称为PC5接口，UE与UE之间的通信链路称为侧行链路sidelink，sidelink通信的一个典型应用场景即车联网(V2X，Vehicle-to-everything)。在车联网中，每个车可以是一个UE，车与车之间可以通过sidelink直接进行数据传输，而不需要经过网络，这样可以有效地减少通信时延。侧行链路也可以称为边链路/旁链路/直通链路等，PC5接口也可以称为“侧链接口”或“直接通信接口”等。示例地，图1为一种UE与UE之间进行直接通信场景的示意图。其中，图1(a)示出了UE1与UE2之间通过PC5接口进行侧行链路通信，侧行链路通信可以应用于如设备到设备(device to device，D2D)、机器到机器(machine to machine，M2M)或车联网(vehicle to everything，V2X)等多种场景中。图1(b)示出了UE1和UE2在PC5口通信的控制面协议栈架构，可以看出，UE1和UE2均具有端到端通信的无线资源控制(Radio Resource Control，RRC)协议层，分组数据汇聚层协议(Packet Data Convergence Protocol，PDCP)协议层，无线连路控制(Radio Link Control，RLC)协议层，媒体介入控制(Media Access Control，MAC)协议层以及PHY协议层。
2、侧行链路的广播(broadcast)、单播(unicast)和组播(groupcast)通信
广播通信与基站广播系统信息类似，即UE不做加密对外发送广播业务数据，任何在有效接收范围内的其他UE，如果对该广播业务感兴趣都可以接收该广播业务的数据。
单播通信类似于UE与基站之间建立RRC连接之后进行的数据通信，需要两个UE之间先建立单播连接。在建立单播连接之后，两个UE可以基于协商确定的标识进行通信，该通信可以是加密的，也可以是不加密的。相比于广播，在单播通信中，只能是建立了单播连接的两个UE之间才能进行该单播通信。在单播通信中，UE在发送数据时，可以随数据一起发送源标识和目的标识，其中，源标识可以是由发端UE自己为该单播连接分配的标识，目的标识可以是对端接收UE为该单播连接分配的标识。侧行链路上的一次单播通信对应于一对标识：源L2 ID(Source Layer-2 Identifier，层二标识源)和目的层二标识(Destination Layer-2 Identifier，L2 ID)，在每个侧行链路媒体接入控制层数据协议单元(Media Access Control Protocol Data Unit，MAC PDU)的子头中可以包含该源L2 ID和目的L2 ID。
组播通信是指一个通信组内所有UE之间的通信，组内任一UE都可以收发该组播业务的数据。
3、无线承载(Radio Bearer，RB)
无线承载是基站为UE分配的一系列协议实体及配置的总称，一般是由层2(L2)提供的用于在UE和基站之间传输用户数据的服务，无线承载包括PDCP协议实体、RLC协议实体、MAC协议实体和PHY分配的一系列资源等。无线承载可以分为数据无线承载(Data Radio Bearer，DRB)和信令无线承载(Signalling Radio Bearer,SRB)，前者用于承载数据，后者用于承载信令消息。在Sidelink通信场景中，无线承载称为Sidelink无线承载(Sidelink Radio Bearer，SLRB)，包括Sidelink数据无线承载SL DRB和Sidelink信令无线承载SL SRB。
4、RLC承载(RLC Bearer)
RLC承载可以指RLC层及以下的协议实体及配置，可理解为无线承载的下层部分，包括 RLC协议实体和逻辑信道等一系列资源。本申请实施例涉及两类RLC承载，分别为Uu接口RLC(Uu RLC)承载和PC5接口RLC(PC5 RLC)承载。Uu RLC承载是指在Uu link(或Uu口)上的RLC承载，PC5 RLC承载是指在Sidelink(或PC5口)上的RLC承载。
5、U2N Relay
为了改善网络性能，例如提高网络覆盖范围，提出了UE到网络中继(UE-to-Network Relay，U2N Relay)通信技术，借助中继UE(Relay UE)来辅助远端UE(Remote UE)和网络设备之间进行通信。如图2所示，图2为可适用于U2N Relay场景的通信网络的示意图，其中，基站与中继UE之间通过Uu接口通信，中继UE与远端UE之间通过PC5接口/Sidelink通信。在U2N Relay场景中，远端UE可以通过中继UE与基站进行通信，中继UE为远端UE提供中继服务。
现有的U2N Relay技术主要有层二(Layer-2,L2)和层三(Layer-3,L3)两种设计。以下以L2 Relay为例，对图2所示出的通信网络的用户面协议栈进行介绍，参见图3，其中示出了包含远端UE、中继UE、基站gNB和5G核心网(5G Core Network，5GC)设备的通信系统的用户面协议栈，其中，远端UE的协议栈从上至下，依次包括：与5GC对等通信的网络互联协议(internet protocol，IP)层、通过Uu接口与gNB进行对等通信的服务数据适配协议(service data adaptation protocol，SDAP)(或称Uu-SDAP)层、通过Uu接口与gNB进行对等通信的数据包数据汇聚协议(packet data convergence protocol，PDCP)(或称Uu-PDCP)层、适配层(Adaptation layer，ADAPT)、通过PC5接口与中继UE进行对等通信的无线链路控制(radio link control，RLC)(或称PC5-RLC)层、通过PC5接口与中继UE进行对等通信的媒体访问控制(media access control，MAC)(或称PC5-MAC层)层，以及通过PC5接口与中继UE进行对等通信的物理(physical，PHY)层(或称PC5-PHY层)。中继UE中与远端UE通信的协议栈从上至下，依次包括：适配(Adapt)层、PC5-RLC层、PC5-MAC层和PC5-PHY层。中继UE中与gNB通信的协议栈从上至下，依次包括：Adapt层、通过Uu接口与gNB进行通信的Uu-RLC层、通过Uu接口与gNB进行通信的Uu-MAC层和通过Uu接口与gNB进行通信的Uu-PHY层。gNB中与远端UE通信的协议栈包括：通过Uu接口与Remote UE进行通信的Uu-SDAP层和Uu-PDCP层。gNB中与中继UE通信的协议栈从上至下依次包括：Aapat层、Uu-RLC层、Uu-MAC层和Uu-PHY层。gNB中，通过GPRS隧道协议用户面(GTP-U，GPRS Tunneling Protocol-User Plane)接口与5GC通信的协议栈包括N3协议栈。5GC中，与远端UE通信的协议栈包括IP层，通过GTP-U与gNB通信的协议栈包括N3协议栈。
相应的，图4示出了包含远端UE、中继UE、gNB和5GC设备的通信系统的控制面协议栈。其中，远端UE的协议栈从上至下依次包括：与5GC进行对等通信的非接入层(non-access stratum，NAS)、通过Uu口与gNB进行对等通信的RRC层(或称Uu-RRC层)、通过Uu口与gNB进行对等通信的PDCP层(或称Uu-PDCP层)、适配Adapt层、通过PC5口与中继UE进行对等通信的RLC层(或称PC5-RLC层)、通过PC5口与中继UE进行对等通信的MAC层(或称PC5-MAC层)，以及通过PC5口和中继UE进行对等通信的PHY层(或称PC5-PHY层)。中继UE中，与远端UE通信的协议栈从上至下依次包括：适配层、PC5-RLC层、PC5-MAC层和PC5-PHY层。中继UE中，与gNB通信的协议栈从上至下包括：适配层、Uu-RLC层、Uu-MAC层和Uu-PHY层。gNB中与远端UE通信的协议栈包括Uu-RRC层和Uu-PDCP层。gNB中与中继UE通信的协议栈从上至下包括：适配层、Uu-RLC层、Uu-MAC层和Uu-PHY层。gNB中，通过N2接口与5GC设备通信的协议栈包括N2协议栈。5GC设 备中，与远端UE通信的协议栈包括NAS层，通过N2接口与gNB通信的协议栈包括N2协议栈。
可以看出，Remote UE的数据包在Relay UE的PDCP(Packet Data Convergence Protocol，分组数据汇聚层协议)层以下进行中继转发，即Relay UE可以仅维护用于中继转发的RLC承载，包括RLC、MAC以及PHY层。因此，Remote UE和基站之间有端对端的PDCP，SDAP和RRC层，但没有端对端通信的RLC、MAC和PHY层。
需要说明的是，图3或图4所示出的协议栈架构中，在RLC层和PDCP层之间可以配置有适配层。适配层的主要作用为承载的复用和解复用，即支持不同的承载可以复用到一个承载上或者将一个承载拆分至不同的承载。在PC5口(即sidelink)两端的协议栈中的适配层可称为PC5适配层，在Uu口两端的协议栈中的适配层可称为Uu适配层。
需要说明的是，本申请实施例提到的协议层的名称可能在技术或者标准演进过程中会发生变化，具体名称本申请对此不作限定。比如，适配层(Adaptation layer，ADAPT)也可以叫侧行链路中继适配协议(Sidelink Relay Adaptation Protocol，SRAP)层。
以下行方向为例，gNB的适配层可以将一个或者多个Remote UE的多个承载(举例，承载可以是SRB或DRB)的数据复用至一个Uu link的RLC承载，即Uu link上的一个RLC承载可以承载分别属于一个或者多个Remote UE的承载上的数据，具体的复用机制可以取决于基站的配置。例如，在下行数据发送过程中，基站的适配层可以在待发送的数据的包头中添加Remote UE ID和DRB ID，当适配层数据包发送至Relay UE时，Relay UE的适配层可以根据包头上Remote UE ID和DRB ID，将Uu RLC承载上递交过来的数据映射到不同Remote UE所对应的PC5 RLC承载，从而实现复用数据的拆分。其中，Remote UE ID、DRB ID和PC5 RLC承载之间的映射关系可以取决于基站的配置。上行方向类似，Relay UE的适配层可以将分别属于一个或者多个Remote UE的无线承载(DRB或SRB)的数据复用到一个Uu link的RLC承载上，从而实现承载的复用。
为了区分属于不同Remote UE的数据，需要为每个Remote UE分配一个Remote UE的标识Remote UE ID，该标识可以称之为本地标识(Local ID)，并在数据包路由过程中携带该Local ID，以指示该数据属于哪一个Remote UE。Remote UE local ID可以由Relay UE所在的gNB进行分配，gNB所分配的local ID可以在该gNB下唯一，或者在Relay UE下唯一。一种可能的分配方式是：Remote UE和Relay UE建立单播连接之后，Relay UE向gNB发送RRC消息，例如SidelinkUEInformationNR(SUI)message，通过该RRC消息请求gNB为该Remote UE分配local ID。
6、组切换(Group Handover)
在U2N Relay通信架构中，业界讨论进一步引入组切换技术。图5为一种基于U2N Relay进行组切换的通信场景示意图，如图5所示，当Relay UE进行从源基站gNB1到目标基站gNB2的切换时，Remote UE跟着Relay UE一起从gNB1切换到gNB 2，且Remote UE和Relay UE之间的sidelink链路将一直保持连接。在此场景中，Remote UE和Relay UE可以看成是一个“组(group)”，当Relay UE进行切换时，同一个组内的Remote UE将跟随Relay UE一起切换，该Remote UE的UE上下文和该Relay UE的UE上下文可以一同切换至目标基站，并继续保持这两个UE的UE上下文之间的关联关系。
本申请实施例所称UE上下文，示例性的，可以是指功能实体间建立的通信链路及其配置信息，用于功能实体间的信息传输；比如UE与gNB两个功能实体之间建立RRC连接，它的通信链路及其相应的配置信息可以理解成UE的上下文，比如，UE上下文可以包含手机 的网络能力、鉴权信息、协商的安全算法、承载信息、PDU会话信息等。
本申请实施例所称的组切换，也可应用于从源小区到目标小区的切换场景，并不限定于是源基站gNB1向目标基站gNB2的切换，比如Relay UE可以是从当前服务基站下的一个小区切换到当前基站的其他小区或者切换到其他基站下的小区。
可以理解的是，由于一个Relay UE可以为一个或多个Remote UE提供数据中继服务，那么，本申请实施例所称的“组”中，可以包括Relay UE以及与其存在通信连接的一个或多个Remote UE，也就是说，“组”内的Remote UE可以是所有和Relay UE相连接的Remote UE或者是和Relay UE相连接的所有Remote UE中的部分Remote UE。
如图6所示，图6为本申请实施例涉及的一种组切换的通信方法的流程示意图，该通信方法包括：
步骤601：Relay UE向服务基站(Serving eNB)发送测量报告(Mesasurement report)；
步骤602：服务基站向目标基站(Target eNB)发送切换请求(handover request)消息。
其中，服务基站可以向多个目标基站或者一个目标基站发送切换请求，相应的切换请求可以有多个，每条切换请求可以对应一个Relay UE或者一个remote UE。
步骤603：目标基站向服务基站发送切换接受(handover accept)消息。
如果服务基站向多个目标基站或者一个目标基站的多个小区发送了切换请求，那么，服务基站可以从对应的多个目标基站或者多个小区接收多个切换接受消息。
步骤604：服务基站向Relay UE发送组切换命令(Group HO command)。
在该步骤中，组切换命令可以包括多个配置消息，或者组切换命令和多个配置消息作为一个消息一起发送。该配置消息可以是源基站给Remote UE和Relay UE下发的RRC重配置(RRC Reconfiguration message)消息，给Remote UE的RRC重配置消息和给Relay UE的RRC重配置消息可以作为一条消息或一次传输。
步骤605：Relay UE给Remote UE发送配置消息。
具体的，给Remote UE的RRC重配置消息首先被下发给Relay UE，并由Relay UE将Remote UE的重配置消息转发给相应的Remote UE。Remote UE可以为多个，图6示出了Remote UE1和Remote UE2，那么，如步骤605a，Relay UE给Remote UE1发送配置信息(例如，Remote UE1的RRC重配置消息)，如步骤605b，Relay UE给Remote UE2发送配置信息(Remote UE2的RRC重配置消息)。
步骤606：Relay UE切换到目标基站。
其中，Relay UE可以根据步骤604中基站给自己发的配置消息，从源基站切换至目标基站。
步骤607：Remote UE向Relay UE发送配置完成消息。
其中，每个Remote UE接收到Relay UE转发的RRC重配置消息后，给Relay UE回复重配置完成消息，以指示配置消息接收成功。
如607a所示，Remote UE1向Relay UE发送配置完成消息，以及，如607b所示，Remote UE2向Relay UE发送配置完成消息。此处所称配置完成消息可以是重配置完成(Reconfiguration Complete)消息。
步骤608：Relay UE向目标基站发送切换完成(handover complete)消息。
步骤609：Relay UE向目标基站发送重配置完成(Reconfiguration complete)消息。
其中，Relay UE成功接入目标基站之后，给目标基站发送每个Remote UE的重配置完成消息，完成各个Remote UE在目标基站侧的接入。示例性的，如图6所示，609a表示Relay UE 把Remote UE1的重配置完成消息发送给目标基站，609b表示Relay UE把Remote UE2的重配置完成消息发送给目标基站。
如图7所示，图7为本申请实施例涉及的又一种组切换的通信方法的流程示意图，该通信方法包括：
步骤701：Relay UE向服务基站(Serving eNB)发送测量报告(Mesasurement report)；
步骤702：服务基站向目标基站(Target eNB)发送切换请求(handover request)消息。
服务基站可以向多个目标基站或者一个目标基站发送切换请求，相应的切换请求可以有多个，每条切换请求可以对应一个Relay UE或者一个remote UE。
步骤703：目标基站向服务基站发送切换接受(handover accept)消息。
如果服务基站向多个目标基站或者一个目标基站的多个小区发送了切换请求，那么，服务基站可以从对应的多个目标基站或者多个小区接收多个切换接受消息。
步骤704：服务基站发送重配置(Reconfiguration)消息。
其中，服务基站向Relay UE和Remote UE发送重配置消息，可以理解的是，Remote UE可以有多个。示例性的，如704a所示，服务基站向Remote UE 1发送重配置消息，如704b所示，服务基站向Remote UE 2发送重配置消息，如704c所示，服务基站向Relay UE发送重配置消息。
步骤705：Remote UE向Relay UE发送重配置完成(Reconfiguration Complete)消息。
其中，示例性的，如705a所示，Remote UE 1向Relay UE发送重配置完成消息，如705b所示，Remote UE 2向Relay UE发送重配置完成消息，
步骤706：Relay UE切换到目标基站。
步骤707：Relay UE向目标基站发送切换完成(handover complete)消息。
其中，该切换完成消息中可以包括Relay UE自己的重配置完成消息以及Remote UE1和Remote UE2的重配置完成消息，作为切换过程中的组的反馈(Handover complete with group response)，如图7所示，可以理解的是，该组包括Relay UE，Remote UE1和Remote UE2。在图7所示出的通信方法中，源基站给Remote UE和Relay UE分别下发RRC重配置消息。等到Relay UE接收到所有Remote UE的重配置完成消息，并且自己成功接入目标基站后，Relay UE以一条消息给目标基站回复切换完成消息。但该方案较为复杂且具有较长的时延。
7、条件切换(Conditional Handover)
对于通信频率较高，覆盖范围较小的系统，比如5G或者NR通信系统，当UE移动时可能会遭遇快速的信号恶化，导致切换的可靠性降低。为了减少切换失败的概率，提升切换的可靠性，3GPP Release 16引入了条件切换(conditional handover，CHO)。CHO的主要思想为在UE与源基站间的无线环境进一步恶化之前，让源基站提前下发切换命令给UE，使得UE提前知道如何接入目标基站，但不立即发起切换。待候选目标基站满足切换执行条件后，UE自主决定发起切换过程。因此，CHO可以减少切换失败的概率，提升切换的可靠性。例如，在高铁这类UE移动较快且移动轨迹较明确的场景，无线环境恶化较快，但UE移动轨迹明确，运营商若能够提前知道UE在不同位置上适合接入的最佳小区，则可以提前规划好候选目标小区，从而减小UE切换失败的概率。
如图8所示，图8示出了一种CHO切换的通信方法的流程示意图，该方法中，Relay UE和源基站(Source gNB)之间可以存在上行数据和或下行数据传输，该方法包括：
步骤801：源基站和Relay UE之间交互测量配置和测量报告。
其中，源基站向Relay UE发送测量配置，基于该测量配置，Relay UE向源基站发送测量 报告。
步骤802：CHO决策。
其中，源基站根据Relay UE发送的测量报告所携带的信息，决策执行CHO，并选择一个候选目标基站(Target gNB)的小区或者选择多个候选目标基站的多个目标小区。
步骤803：源基站向目标基站发送切换请求(handover request，HO request)消息。
其中，源基站可以给每个候选目标基站发送切换请求消息，该切换请求消息可以按照小区粒度发送，即每个小区相应发送一条HO Request消息。
步骤804：候选目标基站向源基站发送切换接受(HO accept)消息。
其中，候选目标基站执行准入控制机制，在Relay UE准入后，每个候选目标基站向源基站回复切换请求相应(Handover Request ACK)，该回复消息同样也可以是小区粒度的，也即，每个小区针对收到的切换请求消息，相应的回复切换请求响应。此时，候选目标基站可以生成空口配置，为UE预留好无线资源，并将相应的空口配置信息通过Handover Request ACK消息发送给源基站，该消息中携带目标小区的ID信息。
步骤805：源基站向Relay UE发送RRC重配置(RRCReconfiguration)消息。
其中，源基站可以通过RRCReconfiguration消息给Relay UE发送CHO配置信息，CHO配置可以包括每个候选小区的切换执行条件和空口配置信息。其中，每个小区的切换执行条件可以是源基站生成，空口资源配置则可以是目标基站生成并发送给源基站(参考步骤804)。
示例性的，源基站可以在RRCReconfiguration消息的信元IE ConditionalReconfiguration中携带CHO配置，其具体内容如下所示：
Figure PCTCN2022136835-appb-000001
每一套CHO配置可以如IE CondRecondfigToAddMod所示，其中，可以包括：分配的标识condReconfigId，切换执行条件conExecutionCond以及无线空口资源的配置信息condRRCReconfig。
Figure PCTCN2022136835-appb-000002
其中，CHO切换执行条件可以包括CondEvent A3和CondEvent A5两类：
-CondEvent A3:候选目标小区的信号质量比当前服务小区高，并且高于配置的偏移量(Conditional reconfiguration candidate becomes amount of offset better than PCell/PSCell)。
-CondEvent A5:当前服务小区的信号质量小于阈值1，且候选目标小区的信号质量大于阈值2(PCell/PSCell becomes worse than absolute threshold1 AND Conditional reconfiguration candidate becomes better than another absolute threshold2)。
具体的参数配置可以参考协议38.331中的IE CondTriggerConfig所示，在此不再赘述。
步骤806：Relay UE向源基站发送RRC重配置完成(RRCReconfigurationComplete)消 息。
具体的，Relay UE给源基站回复RRCReconfigurationComplete消息，可以指示Relay UE已接收并保存相应的CHO配置信息。可以理解，该CHO配置信息可以支持后续更新，比如，在CHO触发或者CHO执行之前，源基站生成的配置信息可以更新，可以由源基站或者其他网络侧设备确定是否进行CHO配置的更新。
步骤807：触发CHO条件判断。
具体的，Relay UE接收到CHO配置之后，保持和源基站的连接，持续检测有无候选目标小区满足切换执行条件。
步骤808：执行切换。
具体的，当Relay UE检测到有一个候选目标小区满足切换执行条件时，UE和源基站断开连接，并根据CHO配置中的该候选目标小区对应的无线资源配置接入目标基站。
步骤809：Relay UE向目标基站发送RRC重配置完成(RRCReconfigurationComplete)消息。
具体的，该Relay UE成功接入目标基站后，该Relay UE可以给目标基站回复RRC重配置完成RRCReconfigurationComplete消息，用于指示该Relay UE成功接入并应用相应的配置。
步骤810：目标基站向源基站发送切换成功(Handover Success)消息。
其中，通过目标基站向源基站发送切换成功消息，告知源基站UE已成功接入该目标基站下的某个小区。
步骤811：源基站向其他候选目标基站发送切换取消(Handover Cancel)消息。
其中，源基站可以给其他配置的候选目标小区发送Handover Cancel消息，指示其释放相应的CHO配置，以释放该候选目标基站给CHO配置预留的资源。
以上，为本申请所涉及的CHO切换的通信方法。
在一种实现方式中，当Relay UE进行小区切换时，Relay UE可以指示Remote UE进行重选Relay UE，Relay UE还可以触发Remote UE进行RRC重建立。基于这种实现方式，当Relay UE进行CHO切换时，Relay UE将指示Remote UE与自己断开连接并指示其进行Relay UE的重选。因此，该实现方式并不能支持Relay UE进行CHO切换时，Remote UE跟着Relay UE一起切换到目标小区，即进行组切换。并且，针对Remote UE来说，重选Relay UE以及执行重建立流程，将花费较长的时间。
综上所述，在Relay UE进行CHO切换时，Remote UE将经历较长的服务中断时长，从而导致数据传输效率降低。
有鉴于此，本申请实施例的一个设计目标即是要解决在L2 U2N relay通信架构下，当Relay UE进行条件切换时，如何支持Remote UE随着Relay UE一起从源小区切换至目标小区的问题，也即，要解决在Relay UE触发CHO切换时，如何支持组切换的问题。
因此，本申请实施例针对Relay UE进行CHO切换的场景，设计了一套当Relay UE的CHO切换执行条件触发时，Remote UE可以跟随Relay UE一起从源小区切换至目标小区的方案，示例性的，其主要思想包括：在CHO切换过程中，源基站指示目标基站同时给Relay UE和Remote UE提供多个候选目标小区的CHO配置。当Relay UE触发CHO切换执行条件时，Relay UE指示Remote UE应用相应的配置，从而可以通过Relay UE接入目标小区，而不需要断开和Relay UE之间的连接。
具体的，下面将结合本申请实施例中的附图，对本申请实施例所提供的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关 系，例如，A/B可以表示A或B；本申请中的“和/或”仅用于描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A，B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a和b，a和c，b和c，或，a和b和c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。同时，在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
此外，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请实施例中涉及的网络节点，示例性的，一般是指无线通信网络中的无线接入网(radio access network，RAN)设备或者是无线接入网设备中的组成部分，无线接入网设备可以是各种类型的基站，比如gNB，LTE eNB、NR gNB或者ng-eNB，或者无线接入网设备是基站中的集中式单元(centralized unit，CU)，或者是基站中的分布式单元(distributed unit，DU)。无线接入网设备和核心网EPC或者5GC相连接。
本申请实施例中所称的终端设备，又称为用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等，是一种向用户提供语音/数据连通性的设备，例如，具有无线连接功能的手持式通信设备或车载通信设备等。终端设备具体可以为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备、虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、或智慧家庭(smart home)中的无线终端，终端设备还可以是车辆联网通信系统中的路侧单元(Road Side Unit，RSU)，或者是RSU中的通信装置或通信芯片本申请实施例对此不作限定。在本申请实施例中，终端设备尤指能够进行sidelink通信的设备，终端设备可以分为两种：Relay UE，即能够为其他终端设备提供中继服务的终端；Remote UE，即能够通过中继服务接入无线接入网设备的终端。
图9为本申请实施例提供的一种通信装置90的结构示意图，当该通信装置90具有本申请实施例所述的第一网络节点的功能时，该通信装置90可以为第一网络节点或者第一网络节点中的芯片或者芯片系统；当该通信装置90具有本申请实施例所述的中继终端设备的功能时，该通信装置90可以为中继终端设备或者中继终端设备中的芯片或者芯片系统；当该通信装置90具有本申请实施例所述的远端终端设备的功能时，该通信装置90可以为远端终端设备或者远端终端设备中的芯片或者芯片系统。当然，本申请实施例中第一网络节点或中继终端设 备或远端终端设备的实现方式并不限于通信装置90，也可以是具有第一网络节点或中继终端设备或远端终端设备的功能的逻辑网络实体或节点。
如图9所示，该通信装置90可以包括处理器901，通信线路902以及通信接口903。可选的，该通信装置90还可以包括存储器904。其中，处理器901，存储器904以及通信接口903之间可以通过通信线路902连接。
其中，处理器901可以是中央处理器(central processing unit，CPU)、通用处理器网络处理器(network processor，NP)、数字信号处理器(digital signal processing，DSP)、微处理器、微控制器、可编程逻辑器件(programmable logic device，PLD)或它们的任意组合。处理器901还可以是其它具有处理功能的装置，如电路、器件或软件模块等。
通信线路902，用于在通信装置90所包括的各部件之间传送信息。
通信接口903，用于与其他设备或其它通信网络进行通信，比如，该其它通信网络可以为以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等，该通信接口903可以是射频模块或者任何能够实现无线通信的装置。本申请实施例仅以通信接口903为射频模块为例进行说明，其中，射频模块可以包括天线、射频电路等，射频电路可以包括射频集成芯片、功率放大器等。
存储器904，用于存储指令。其中，指令可以是计算机程序。
其中，存储器904可以是只读存储器(read-only memory，ROM)或可存储静态信息和/或指令的其他类型的静态存储设备，也可以是随机存取存储器(random access memory，RAM)或者可存储信息和/或指令的其他类型的动态存储设备，还可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储、磁盘存储介质或其他磁存储设备，光碟存储包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等。
需要说明的是，存储器904可以独立于处理器901存在，也可以和处理器901集成在一起。存储器904可以用于存储指令或者程序代码或者一些数据等。存储器904可以位于通信装置90内，也可以位于通信装置90外，不予限制。处理器901，用于执行存储器904中存储的指令，以实现本申请实施例所提供的通信方法或者所涉及的网络实体的功能。
或者，可选的，本申请实施例中，也可以是处理器901执行本申请下述实施例提供的通信方法中的处理相关的功能，通信接口903负责与其他设备或通信网络通信，本申请实施例对此不作具体限定。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在一种示例中，处理器901可以包括一个或多个CPU，例如图9中的CPU0和CPU1。
作为一种可选的实现方式，通信装置90可以包括多个处理器，例如，除图8中的处理器901之外，还可以包括处理器907。
作为一种可选的实现方式，通信装置90还可以包括输出设备906和输入设备907。示例性地，输入设备907是键盘、鼠标、麦克风或操作杆等设备，输出设备906是显示屏、扬声器(speaker)等设备。
需要说明的是，图9中示出的组成结构并不构成对该通信装置的限定，除图9所示部件之外，该通信装置可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
下面对本申请实施例提供的通信方法进行描述。其中，下述实施例中的网络节点，中继终端设备和远端终端设备可以具有如图9所示的部件或者各种可能的结构。其中，本申请各实施例之间涉及的动作，术语等均可以相互参考，不予限制。本申请的实施例中各个设备之间交互的消息名称或消息中的参数名称等只是一个示例，具体实现中也可以采用其他的名称，不予限制。
图10为本申请实施例提供的一种通信方法，如图10所示，该通信方法涉及第一网络节点，中继终端设备和远端终端设备，该通信方法可以包括如下步骤：
步骤1001：第一网络节点向第二网络节点发送切换请求信息。
其中，该所述切换请求信息可以包括：中继终端设备的第一标识信息和所述中继终端设备的用户设备上下文信息，远端终端设备的第一标识信息和所述远端终端设备的用户设备上下文信息。其中，该远端终端设备通过该中继终端设备与该第一网络节点进行通信交互，所述切换请求信息用于所述中继终端设备从所述第一网络节点向所述第二网络节点的小区进行切换，或者，也可以说该切换请求信息可以用于远端终端设备跟随该中继终端设备一起从第一网络节点向第二网络节点切换。
示例性的，该远端终端设备的第一标识信息可以包括如下中至少一个：所述第一网络节点为所述远端终端设备分配的所述远端终端设备的小区无线网络临时标识(cell radio network temporary identifier，CRNTI)，所述远端终端设备的层2标识，以及，所述第一网络节点为所述远端终端设备分配的所述远端终端设备的临时标识。具体的，该远端终端设备的第一标识信息可以包括：所述第一网络节点为所述远端终端设备分配的所述远端终端设备的CRNTI和所述远端终端设备的层2标识(L2 ID)，该L2 ID可以是源L2 ID或者目的L2 ID。
示例性的，该中继终端设备的第一标识信息可以包括如下中至少一个：第一网络节点为该中继终端设备分配的CRNTI，该中继终端设备的层2标识，以及第一网络节点为该中继终端设备分配的临时标识。具体的，比如，该中继终端设备的第一标识信息包括该中继终端设备的CRNTI和该中继终端设备的层2标识。
步骤1002：第一网络节点从第二网络节点接收切换响应信息。
其中，该所述切换响应信息可以包括：所述中继终端设备的第二标识信息和为所述中继终端设备配置的所述第二网络节点的第一小区的无线承载配置信息，以及，所述远端终端设备的第二标识信息和为所述远端终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息。
其中，示例性的，该远端终端设备的第二标识信息可以是该远端终端设备的第一标识信息，也即之前第一网络节点通过切换请求信息向第二网络节点发送的该远端终端设备的第一标识信息；或者，该远端终端设备的第二标识信息可以是以下中至少一个：所述第二网络节点为所述远端终端设备分配的所述远端终端设备的CRNTI，所述远端终端设备的层2标识(L2 ID)，以及所述第二网络节点为所述远端终端设备分配的所述远端终端设备的临时标识，比如该远端终端设备的第二标识信息包括第二网络节点为该远端终端设备分配的临时标识(比如local ID)和L2 ID。
示例性的，该第一网络节点和/或该第二网络节点可以根据远端终端设备的层2标识为该远端终端设备各自分配临时标识，两者为远端终端设备所分配的临时标识可以相同，也可以不同。
可以理解的是，第二网络节点为远端终端设备分配的远端终端设备的CRNTI，可以和第一网络节点为远端终端设备分配的远端终端设备的CRNTI不同，也可以相同。
示例性的，该切换响应信息中可以包含第一配置信息和第二配置信息，其中，第一配置信息可以包括：为所述中继终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息以及所述第二网络节点的所述第一小区的第一标识信息；所述为所述中继终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息，包括：所述中继终端设备在所述第二网络节点的所述第一小区的RRC承载配置信息，以及所述中继终端设备为所述远端终端设备提供中继服务所需要的PC5接口的RLC承载配置信息和Uu接口的RLC承载配置信息，所述PC5接口是所述中继终端设备和所述远端终端设备之间的通信接口，所述Uu接口是所述中继终端设备和所述第二网络节点之间的通信接口；该第二配置信息可以包括：为所述远端终端设备配置的所述第二网络节点的第一小区的无线承载配置信息，以及所述第二网络节点的所述第一小区的第一标识信息；所述为所述远端终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息，包括：所述远端终端设备在所述第二网络节点的所述第一小区的无线承载配置，以及所述远端设备的PC5接口的RLC承载配置信息，所述PC5接口是所述中继终端设备和所述远端终端设备之间的通信接口。
可以理解的是，本申请实施例所称第一配置信息和第二配置信息，是开放式的描述，第一配置信息可以泛指和中继终端设备有关的配置信息，第二配置信息可以泛指和远端终端设备有关的配置信息，配置信息中的具体内容构成，本申请不作具体限定。
步骤1003：第一网络节点向中继终端设备发送第三配置信息。
其中，该第三配置信息可以包括：为所述中继终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息，以及所述第二网络节点的所述第一小区的第二标识信息，其中，所述第二网络节点的所述第一小区是所述中继终端设备进行切换的候选目标小区。
步骤1004：所述第一网络节点向所述远端终端设备发送第四配置信息。
其中，该第四配置信息包括：为所述远端终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息，以及所述第二网络节点的所述第一小区的第二标识信息，其中，所述第二网络节点的所述第一小区是所述中继终端设备进行切换的候选目标小区。
示例性的，在步骤1003和1004中，第二网络节点的第一小区的第二标识信息，可以是第一网络节点为第二网络节点的第一小区分配的标识，比如小区索引index；或者，第二网络节点的第一小区的第二标识信息，可以是全球小区标识CGI，该CGI是由该第二网络节点通过步骤1002中的切换响应信息发送给所述第一网络节点的。
可以理解的是，第一网络节点(源基站)在给Remote UE或者Relay UE的CHO配置中，为第二网络节点的第一小区(也即目标基站的候选目标小区)配置小区index，或者在给Remote UE或者Relay UE的CHO配置中提供候选目标小区的CGI，或者在给Remote UE或者Relay UE的CHO配置中提供候选目标小区的配置的排序信息，可以作为独立的实施方式存在。
可以理解的是，本申请实施例中，该第一网络节点和该第二网络节点可以是同一个网络节点，也就是说，中继终端设备的切换可以是发生在同一个网络节点下的不同小区之间。
步骤1005：中继终端设备向远端终端设备发送第一信息。
示例性的，从中继终端设备角度而言，本步骤可以作为独立的实施例方式，以实现通过发送第一信息，使得远端终端设备能够应用所确定的候选目标小区的配置信息，从而伴随该 中继终端设备一起切换到该候选目标小区。
可以理解的是，中继终端设备向远端终端设备发送第一信息，可替换的，可以理解成是该Relay UE指示该Remote UE需要执行切换的一种具体实现方式，其前提是，Remote UE已经提前从基站接收到相应的候选目标小区的无线资源配置。具体Relay UE如何指示该Remote UE需要执行切换，可以是采用本申请实施例中发送第一信息的方式。
其中，中继终端设备通过该第一信息用于指示远端终端设备：第二网络节点的第一小区的第二标识信息。或者，该第一信息用于指示：该第二网络节点的第一小区的配置的排序信息。这样，远端终端设备就可以通过该第一信息了解到中继终端设备的切换目标小区就是前文所描述的第二网络节点的第一小区。
可以理解的是，如果该第一信息是用于指示该第二网络节点的第一小区的配置的排序信息的话，也就是隐式指示需要应用哪一个小区所对应的无线承载配置信息，那么在步骤1003和/或步骤1004中，第二网络节点的第一小区的第二标识信息，也可以是该第一小区的物理小区标识(PCI)，该PCI可以认为是该小区所对应的无线承载配置信息中的内容，当然也可以是其他类型的标识信息，甚至并不需要强调有相应的标识信息。本申请实施例对此不作限定。所述为所述中继终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息，包括：所述中继终端设备在所述第二网络节点的所述第一小区的RRC承载配置信息，以及所述中继终端设备为所述远端终端设备提供中继服务所需要的PC5接口的RLC承载配置信息和Uu接口的RLC承载配置信息，所述PC5接口是所述中继终端设备和所述远端终端设备之间的通信接口，所述Uu接口是所述中继终端设备和所述第二网络节点之间的通信接口。
可以理解的是，本申请实施例中所描述的“中继终端设备向远端终端设备发送第一信息”，可替换为，Relay UE可以给Remote UE发送指示信息，指示Remote UE应用CHO配置。这样，针对只给Remote UE配置了一个用于CHO切换的候选目标/备选小区的话，那么可以简化为Relay UE指示Remote UE应用该候选目标/备选小区的CHO配置即可。
在一种实现方式中，当所述第二网络节点的所述第一小区满足切换触发条件，则所述中继终端设备向所述远端终端设备发送所述第一信息。
需要说明的是，远端终端设备或者中继终端设备收到的多个(对应不同候选目标小区)小区的无线承载配置信息，可以分别对应不同的切换触发条件。具体的，这些切换触发条件可以是第一网络节点配置的，这些切换触发条件可以是第一网络节点通过无线资源控制RRC消息发送给中继终端设备设备，有中继终端设备判断切换条件是否满足。
本申请实施例中，第一网络节点和第二网络节点可以是基站gNB，其中，第一网络节点可以是切换流程中的源基站gNB，第二网络节点可以是切换流程中的目标基站gNB。中继终端设备可以是U2N网络中的Relay UE，远端终端设备可以是U2N网络中的Remote UE。
通过图10所提出的本申请实施例技术方案，可以实现当Relay UE进行小区切换时，RemoteUE可以伴随该Relay UE一起进行组切换。比如，通过源基站在切换请求中携带Relay UE和Remote UE的切换请求信息，指示候选目标基站为Relay UE以及Remote UE提供CHO切换所需配置，候选目标基站通过切换响应信息将所需配置的配置信息发送给源基站，并由源基站发送给Relay UE以及Remote UE。当Relay UE的CHO切换执行条件触发时，Relay UE可以指示Remote UE启用相应的CHO配置(比如启用目标基站的一个小区的配置)，实现Remote UE可以和Relay UE一起，从源小区一起切换至目标小区，从而可以减小Remote UE 的服务中断时间，提高服务效率。
参考图10所示出的通信方法，单独或者在其基础上，如图11所示，本申请实施例还提供了一种用于CHO切换的通信方法的流程示意图，该通信方法涉及远端终端设备(如图：Remote UE1，Remote UE2)，中继终端设备(Relay UE)，源基站(比如：源下一代无线接入网设备，source next generation radio access network NG-RAN)，目标基站(比如：Target NG-RAN)，其中，本实施例以Relay UE为Remote UE1和Remote UE2提供中继服务为例，可以理解的是，Relay UE还可以为更多的Remote UE提供中继服务，为简洁起见本实施例不再示出。需要说明的是，本申请实施例中，准备进行CHO切换的Relay UE，一般处于RRC连接态(RRC connected state)，也可以处于空闲态(Idle state)，或者处于RRC非活动态(RRC inactive state)。
在图11所示出的通信方法及其系统中，Remote UE1和Remote UE2可以通过Relay UE接入Relay UE的服务基站，也即切换中的源基站，并分别和该基站进行上行和/或下行数据交互，Relay UE和基站之间也可以进行上行或者下行数据交互。示例性的，图11所示出的通信方法，其主要思想可以包括：基站给Relay UE进行CHO配置时，同时为Relay UE下属的Remote UE进行CHO配置，当Relay UE触发CHO切换时，同时触发Remote UE引用相应的CHO配置，从而使得Remote UE可以和Relay UE一起从源小区切换至目标小区，实现Remote UE可以跟随Relay UE一起进行组切换。图11所示出的该通信方法包括：
步骤1101：测量配置和测量上报。
其中，源基站对Relay UE进行测量配置，提供测量有关的配置信息给Relay UE，进而Relay UE可以根据源基站提供的测量配置，触发测量动作和/或将测量报告发给基站。
步骤1102：CHO决策。
其中，源基站可以根据Relay UE上报的测量报告的内容，决策执行CHO，选定多个候选的目标小区，该多个目标小区可以属于不同的目标基站，也可以属于同一个基站，也即目标基站可以有一个或多个。可以理解的是，源基站和目标基站也可以是同一个，此时涉及的切换就是同一个基站下的不同小区间的切换。
步骤1103：源基站向目标基站发送切换请求。
该步骤中，源基站可以给候选的一个或者多个候选目标基站发送切换请求(handover request，HO request)消息。
该切换请求消息中可以携带Relay UE的上下文信息以及一个或多个Remote UE的上下文信息。UE上下文信息可以包含：UE安全能力、接入层(access stratum，AS)安全信息、UE的协议数据单元(protocol data unit，PDU)会话资源信息(如QoS流到无线承载的映射规则)、无线资源控制(radio resource control，RRC)无线承载配置信息等内容中的一个或多个。目标基站可以根据收到的Relay UE和/或Remote UE的UE上下文信息进行准入控制，并为UE分配传输资源。该切换请求消息中还可以携带目标小区的ID信息(如全球小区标识cell global identifier，CGI)以及切换指示信息，以告知目标基站源基站请求进行切换，比如进行CHO切换。
其中，可选的，可以针对涉及的多个目标小区分别单独发送一条切换请求消息，用于请求将Relay UE切换至某一个候选目标小区。
可以理解的是，切换请求消息中可以携带Relay UE和Remote UE的标识(identifier，ID)信息来指示不同的UE上下文分别属于哪个UE，例如，切换请求消息中携带的Relay UE的标识信息可以包括：Relay UE的小区无线网络临时标识(cell radio network temporary identifier， C-RNTI)，切换请求消息中携带的Remote UE的标识信息可以包括：Remote UE的C-RNTI和/或Remote UE的L2 ID，其中，Remote UE的L2 ID可以是Remote UE的目的L2 ID，也可以是Remote UE的源L2 ID。可以理解的是，此处所描述的Relay UE的ID信息以及Remote UE的ID信息，和各自的UE上下文之间具有关联关系。在另一种可能的方式中，由于源基站发送给目标基站的切换请求消息可以携带Relay UE的XnAP ID信息(也即，源基站为Relay UE分配的在Xn接口上的ID信息)，因此，在切换请求消息中可以只为Remote UE的UE上下文携带ID信息，使用该ID信息来指示该UE上下文信息是对应于该Remote UE，例如切换请求消息中可以携带Remote UE的C-RNTI或者Remote UE的L2 ID(源L2 ID或者目的L2 ID)或者源基站为Remote UE的分配的临时ID信息。
可选的，源基站也可以单独为每个UE向目标基站发送切换请求消息，即每个切换请求消息可以只携带某一个UE的切换请求相关的信息。
步骤1104：源基站接收目标基站发送的切换反馈。
在经过准入控制机制后，一个或多个候选目标基站可以向源基站回复切换请求反馈(HANDOVER REQUEST ACK)消息，每个候选目标小区可以对应一条HANDOVER REQUEST ACK消息，该切换请求反馈消息中可以携带候选目标小区的ID信息(比如CGI)，HANDOVER REQUEST ACK消息中还可以包含目标基站为Relay UE和Remote UE分别生成的在候选目标小区的无线承载配置信息，也就是说候选目标基站为Relay UE和Remote UE的接入预留好了无线资源，无线承载配置信息可以通过RRC信令配置给相应的Relay UE和Remote UE。比如，在HANDOVER REQUEST ACK消息中可以包含切换命令(Handover Command)消息，该Handover Command消息中包含目标基站为Relay UE和Remote UE分别生成的在候选目标小区的无线承载配置信息。
由于Relay UE可以为多个Remote UE提供中继通信支持，因此候选目标小区的无线承载配置信息中，还可以携带Remote UE的ID信息，以指示该候选目标小区的无线承载配置信息是对应哪一个Remote UE。具体的，通过RRC消息配置给Relay UE和Remote UE的无线承载配置信息中可以携带该Remote UE ID信息，该Remote UE ID信息可以是目标基站为该Remote UE分配的local ID信息，其中，给RelayUE的配置信息中，还可以包括Remote UE的(local ID，DRB ID)和Uu RLC channel/PC5 RLC channel之间的映射关系，其中，local ID可以是目标基站配置的该Remote UE的临时本地标识，DRB ID是该Remote UE的数据无线承载的标识，Uu RLC channel是所述Relay UE和源基站/目标基站之间的Uu接口无线链路控制RLC信道，PC5 RLC channel是所述Relay UE和所述Remote UE之间的PC接口的无线链路控制RLC信道。
在一种实现方式中，切换请求反馈消息中可以携带之前切换请求消息中携带的Remote UE ID信息，即切换请求反馈消息中携带的Remote UE ID信息可以包括源基站分配的该Remote UE的C-RNTI，或者该Remote UE ID信息可以包括源基站为该Remote UE分配的临时ID信息(比如，本地local标识)和该Remote UE的L2 ID。另一种实现方式中，该Remote UE ID信息还可以是候选目标基站为该Remote UE分配的C-RNTI，或者，该Remote UE ID信息还可以是候选目标基站为该Remote UE分配的临时ID信息和该Remote UE的L2 ID。
可选的，候选目标基站也可以针对每个UE单独向源基站发送HANDOVER REQUEST ACK消息，此时HANDOVER REQUEST ACK消息则不需要携带上述ID信息用于区分不同的UE。但目标基站可以在每个无线承载配置信息中携带如下中的一个或多个：源基站为Remote UE分配的C-RNTI，该Remote UE的L2 ID，目标基站为Remote UE分配的C-RNTI， 以及目标基站为该Remote UE分配的临时ID，以用于Remote UE的数据的路由。
步骤1105：源基站向Relay UE发送RRC重配置消息。
该步骤中，源基站可以通过RRC Reconfiguration消息向Relay UE发送用于CHO的配置信息，该CHO配置信息可以包括：源基站为Relay UE生成的CHO切换执行条件(CHO execution condition)，以及候选目标基站为Relay UE生成的候选目标小区的无线承载配置信息。
示例性的，候选目标基站为Relay UE生成的无线承载配置信息可以包括：Relay UE和候选目标基站之间的无线承载配置信息，还可以包括为Remote UE提供中继服务所需要的无线承载配置信息，比如，为Remote UE提供中继服务所需要的无线承载配置信息可以包括：PC5 RLC承载配置和Uu RLC承载配置，其中，PC5 RLC承载是指Relay UE和Remote UE之间的承载，Uu RLC承载是指Relay UE和候选目标基站之间的承载。进一步的，Relay UE的无线承载配置信息中还可以包括该Remote UE的无线承载和PC5 RLC承载/Uu RLC承载之间的映射关系。具体地，上述映射关系包含如下中一个或多个之间的映射关系：Remote UE的ID信息,该Remote UE的RB ID(DRB ID或SRB ID)，该PC5 RLC承载以及该Uu RLC承载。
步骤1105a：Relay UE向源基站发送RRC重配置完成(RRC Reconfiguration Complete)消息。
其中，Relay UE可以接收并保存源基站下发的上述CHO配置信息(如步骤1105)，然后Relay UE可以向源基站回复RRC重配置完成消息，以指示源基站已成功接收CHO配置。
步骤1106：源基站向Remote UE发送RRC重配置消息，Remote UE向源基站回复RRC重配置完成消息。
其中，源基站可以通过RRC重配置消息向Remote UE1和Remonte UE2分别发送候选目标基站为Remote UE生成的在候选目标小区的无线承载配置信息。Remote UE1和Remote UE2收到该RRC配置信息后，可以分别向源基站回复RRC重配置完成消息。Remote UE的无线承载配置信息可以包括：该Remote UE和候选目标小区端对端的无线承载配置以及PC5 RLC承载配置信息。其中，PC5 RLC承载配置信息可以包括：Remote UE的承载标识(或者Remote UE的临时标识和承载标识)和PC5 RLC承载之间的映射关系。
在步骤1105和步骤1106中，源基站可以在向Relay UE或Remote UE发送的每个候选目标小区的无线承载配置信息中携带候选目标小区的ID信息，该候选目标小区的ID信息可以是CGI，在HANDOVER REQUEST消息和HANDOVER REQUEST ACK消息中都可以携带候选目标小区的CGI；或者，源基站可以为每个候选目标小区分配一个索引index标识，该索引标识信息与分别为Relay UE/Remote UE配置的无线承载配置信息具有关联关系；或者源基站可以按照一定的顺序封装多个目标小区的无线承载配置，并保持通过RRC消息发给Relay UE和Remote UE的无线承载配置的顺序相同或者对应。
步骤1105和步骤1106中，源基站可以分别通过单独的RRC Reconfiguration消息，给Relay UE和Remote UE发送CHO配置。源基站也可以将Relay UE和Remote UE的所有配置信息承载在同一个RRC消息中发给Relay UE，再由Relay UE转发给相应的Remote UE。
步骤1107：判断是否满足切换执行条件。
其中，Relay UE收到CHO配置之后，Relay UE继续保持和源基站的连接与传输，并持续判断有无目标小区满足切换执行条件。当Relay UE检测到有一个候选目标小区满足切换执行条件时，可以按照接收到的CHO配置信息主动执行向满足要求的候选目标小区进行切换，并且可以断开和源基站的服务小区的连接，按照CHO配置信息接入该候选目标小区。
步骤1108：接入目标基站。
其中，CHO切换执行条件触发后，Relay UE可以通过随机接入过程(Random access procedure)接入目标基站的候选目标小区。
步骤1109：RRC重配置完成消息。
其中，Relay UE可以给候选目标小区所在的基站发送RRC Reconfiguration Complete消息，指示RRC连接建立完成。
步骤1110：Relay UE向Remote UE发送指示信息。
该步骤中，Relay UE给Remote UE发送指示信息，该指示信息可以用来通知Remote UE某个候选目标小区的CHO条件已触发。Remote UE可以有一个或多个需要随同Relay UE一起切换，如图所示，Relay UE分别向Remote UE1和Remote UE2发送该指示信息，Relay UE也可以根据需要决策哪一个Remote UE需要跟随其一起切换到目标小区，仅给需要伴随切换的Remote UE发送该指示信息。通过该步骤，Relay UE可以指示相应的Remote UE应用候选目标小区的通过RRC消息配置的无线承载配置信息，从而可以和Relay UE一起接入目标基站下的目标小区。因此，在上述指示信息中，Relay UE可以携带步骤1105中收到的候选目标小区的ID信息或者源基站为候选目标小区配置的index标识信息。Remote UE可以根据该指示信息，应用与该候选目标小区的ID信息或者index标识信息相对应的无线配置信息。
可选的，Relay UE还可以用隐式指示的方式来触发Remote UE应用与选定的候选目标小区对应的无线承载配置信息。比如，假设Relay UE和Remote UE均被配置了n套候选目标小区的CHO配置(n为正整数，对应n个候选目标小区)，源基站在步骤1105和步骤1106中下发的配置消息中，可以按照相同的顺序排列候选目标小区的配置信息，Relay UE可以隐式指示第k套配置对应的CHO切换执行条件被触发(k<＝n，k为正整数)，比如，Relay UE可以向Remote UE指示候选目标小区的配置的顺序信息，如k值，Remote UE收到k值后，则相应的应用第k套无线承载配置。
步骤1011：Remote UE向源基站发送RRC重配置完成消息。
其中，Remote UE可以根据Relay UE的指示，选择对应的候选目标小区的无线配置，进行媒体接入控制(Media Access Control，MAC)层的重置，以及进行Remote UE和该Relay UE之间的PC5 RLC承载重建立，然后，Remote UE可以通过Relay UE给目标基站回复RRC Reconfiguration Complete消息，指示目标基站RRC连接建立已完成。
其中，Relay UE中继转发该Remote UE的RRC重配置完成消息时，Relay UE的适配层可以在数据的适配层头上添加目标基站为该Remote UE分配的临时ID信息，以便让目标基站能够识别该RRC重配置完成消息是来自哪个Remote UE。
步骤1112：目标基站向源基站发送切换成功(Handover Success)消息。
其中，目标基站接收到Relay UE和/或Remote UE发送的RRC Reconfiguration Complete消息之后，可以通过HANDOVER SUCCESS消息告知源基站，Relay UE和/或Remote UE成功从源小区切换至目标小区。其中，HANDOVER SUCCESS消息中可以携带对应UE的XnAP ID信息，即一个UE对应一条HANDOVER SUCCESS消息，以及对应的目标小区的ID信息。
可选的，源基站在收到Relay UE和一个或多个Remote UE发送的RRC Reconfiguration Complete消息之后，也可以将Remote UE切换成功的指示信息携带在Relay UE的HANDOVER SUCCESS消息中，比如，在Relay UE的HANDOVER SUCCESS消息中可以携带步骤1104中携带的Remote UE的ID信息，例如该Remote UE的ID信息可以是该Remote UE在源基站的C-RNTI或者源基站为该Remote UE分配的临时ID，或者，可替换的，在Relay  UE的HANDOVER SUCCESS消息中可以携带该Remote UE的L2 ID。
步骤1113：源基站向目标基站发送切换取消(HANDOVER CANCEL)消息。
其中，源基站可以根据步骤1112中收到的HANDOVER SUCCESS消息中获知relay UE/和或Remote UE已成功切换至目标小区，则该源基站可以给其余候选目标小区所在的目标基站发送HANDOVER CANCEL消息，指示候选目标基站可以释放其余候选目标小区下为Relay UE和Remote UE的预配置的空口资源。
至此，可以理解，Remote UE就和Relay UE一起，从源小区切换至目标小区。综上，上述通信过程中，当Relay UE进行CHO切换时，Remote UE能够跟随Relay UE一起完成组切换。进一步的，独立或者在上述过程的基础上，本申请实施例还提出了如下设计。
一种可能的实现方式中，可以选择性的支持部分Remote UE进行组切换，以节省资源开销。
根据上述方案，Relay UE进行测量并上报测量报告，触发CHO切换流程后，候选目标基站需要为Relay UE和该Relay UE下属的Remote UE预留候选目标小区的空口资源，以便后续CHO切换执行条件触发之后，Relay UE和Remote UE可以接入该候选目标小区。当Relay UE下属的Remote UE个数较多时，意味着候选目标基站需要预留大量的资源，并且Remote UE接入或者离开Relay UE时，将频繁触发候选目标基站侧的CHO配置更新，因此，在一种可选设计汇总，可以选择性地只给部分Remote UE进行CHO配置，其余Remote UE可以在Relay UE通过CHO切换接入目标小区之后，将按照现有技术的方式，进行小区或者Relay UE的重选。
在另一种可能的实现方式中，可以将组切换作为一种UE的能力上报给网络设备(比如基站)，也即，有些Remote UE可能支持组切换，有些Remote UE可能不支持组切换，那么某一个Remote UE是否能够支持组切换的信息，可以上报给基站。基站可以根据UE的能力情况，判断在上述步骤1103的HANDOVER REQUEST消息是否携带对应该Remote UE的切换请求指示信息。
在又一种可能的实现方式中，源基站可以根据多个Remote UE的具体情况或者基于基站的具体实现，选择其中某一个Remote UE并将用于该Remote UE的切换请求信息携带在HANDOVER REQUEST消息中，例如，当Relay UE和Remote UE之间链路较稳定时(基站可以根据Relay UE测量上报的sidelink链路信号质量情况来判断Relay UE和Remote UE之间的链路稳定性)，或者，Remote UE的业务中断容忍度比较低或时延要求比较低时，就可以针对这个Remote UE进行CHO配置，使得该Remote UE伴随着Relay UE进行组切换。其余未被执行CHO配置的Remote UE，可以在Relay UE切换之后与网络侧进行RRC重建立流程。
在又一种可能的实现方式中，在源基站接收到其他基站发送的HANDOVER REQUEST ACK消息时，该消息中可以携带：
i.Relay UE的CHO配置，以及，
ii.在源基站给目标基站发送的HANDOVER REQUEST消息中指示的请求要和该Relay UE一起切换的那些Remote UE的在Relay UE处所需要无线承载配置信息，即Relay UE为了能够给这些Remote UE提供中继服务所需要的Uu/PC5接口的RLC承载配置信息，此处Uu接口是Relay UE和目标基站之间的无线通信接口，PC5接口是Relay UE和Remote UE之间的接口。
在一种可能的实现方式中，Relay UE收到源基站下发的CHO配置之后，可以知道哪些Remote UE将跟随自己一起进行组切换，因此，当步骤1107中，CHO切换执行条件触发时， Relay UE可以只给这些Remote UE发送CHO切换的指示信息。
由上可以看出，本申请实施例提供了Relay UE进行CHO切换时，Remote UE一起进行组切换的实现方案。比如，源基站可以在向候选目标基站发送的CHO切换请求中携带Relay UE和Remote UE的切换请求信息，指示候选目标基站为Relay UE以及Remote UE提供CHO切换所需的无线配置。候选目标基站可以通过HANDOVER REQUEST ACK消息将CHO配置信息发送给源基站，并由源基站发送给Relay UE以及Remote UE。因此，当Relay UE的CHO切换执行条件触发时，可以指示Remote UE启用相应的CHO配置，从而Remote UE可以和Relay UE一起，从源小区切换至目标小区。
区别于现有技术，在本实施例中，源基站将同时进行Relay UE和Remote UE的切换请求，候选目标基站可以同时为Relay UE和Remote UE进行CHO配置，并预留相应的空口资源。当Relay UE的CHO条件触发时，Relay UE指示Remote UE启用相应的切换目标小区对应的配置，从而，Remote UE可以和Relay UE一起，从源小区切换至目标小区，并且不需要断开和Relay UE之间的PC5连接。这样，通过上述方案，可以减少Remote UE的服务中断时间。
参考图10和图11所示出的通信方法，单独或者在其基础上，如图12所示，本申请实施例还提供了又一种用于CHO的通信方法，该通信方法主要描述了如何进行CHO配置更新的工作流程，也就是说，候选目标基站给Relay UE或者Remote UE下发用于CHO切换所需的配置信息之后，该CHO配置并不是一成不变的，并且是可以更新的。在CHO切换执行条件被触发之前，可以根据需要进行CHO配置的更新，比如，当有新的Remote UE接入Relay UE或者Remote UE离开Relay UE时，源基站或者候选目标基站可以触发CHO配置的更新。
以下以新的Remote UE接入Relay UE为例，如图12所示，该通信方法包括：
步骤1201：Remote UE通过Relay UE接入源基站。
其中，以Remote UE 3作为新接入的Remote UE为例，该Remote UE 3通过Relay UE接入到源基站。可以理解的是，该Relay UE可以同时在给其他Remote UE提供中继通信服务，图中未示出。
需要说明的是，本申请实施例所称源基站可以理解为泛指切换过程中涉及的源测网络设备，比如，可以是如附图中所示出的source NG-RAN。目标基站同理，可以理解为泛指切换过程中涉及的目标侧网络设备。
步骤1202：CHO配置更新决策。
其中，源基站发现有新的Remote UE 3接入之后，触发CHO切换流程，以便于给Remote UE 3配置CHO配置信息以及更新Relay UE侧的CHO配置。
示例性的，该源基站可以先判断Remote UE是否支持组切换，或者该源基站可以根据Remote UE和Relay UE之间的链路质量情况，或者该源基站可以根据Remote UE的业务需求情况，来选择是否给Remote UE进行CHO配置以及进行Relay UE的CHO配置更新。
步骤1203：源基站向一个或多个候选目标基站发送切换请求消息。
其中，源基站向候选目标基站发送切换请求(HANDOVER REQUEST)消息，该切换请求消息中可以携带针对每个Remote UE的切换请求信息，比如，携带新接入的Remote UE3的切换请求信息(包含该Remote UE3的ID信息)，以指示候选目标基站对新接入的Remote UE3进行CHO配置。当有多个Remote UE新接入时，该HANDOVER REQUEST消息可以承载多个Remote UE的切换请求信息，也可以为每个新接入的Remote UE单独发送HANDOVER REQUEST消息。具体方式也可以参考图11所示实施例中的步骤1103，在此不再赘述。
步骤1204：源基站接收一个或多个候选目标基站发送的切换请求反馈消息。
其中，候选目标基站接收到源基站发送的HANDOVER REQUEST消息后，为该新接入的Remote UE3进行CHO配置，预留空口资源。然后通过HANDOVER REQUEST ACK消息，将Remote UE3的CHO配置信息发送给源基站。该HANDOVER REQUEST ACK消息承载Remote UE3的CHO配置的方式可以参考图11所示实施例中的步骤1104。可以理解的是，如果存在多个Remote UE的话，可以将多个Remote UE的配置信息承载在一条HANDOVER REQUEST ACK消息中，也可以是将每个Remote UE的配置信息承载在不同的单独的HANDOVER REQUEST ACK消息中。
示例性的，该Remote UE3所需的CHO配置信息可以包含两部分，第一部分为Remote UE侧的配置信息，可以包括：该Remote UE在目标小区的端对端的无线承载配置，和/或，该Remote UE和Relay UE之间的PC5 RLC承载配置，第二部分为与该Remote UE对应的Relay UE侧的配置信息，可以包括：Relay UE为该Remote UE提供中继服务所需的Relay UE的PC5 RLC承载和Uu RLC承载的配置信息。该Remote UE3的CHO配置中还可以包括该Remote UE3的ID信息。具体该Remote UE3的ID信息是哪些，可以参考步骤1104中关于Remote UE的ID信息的描述，此处不再赘述
步骤1205：源基站向Relay UE发送RRC重配置消息。
其中，源基站可以通过该RRC重配置消息，将Relay UE侧的CHO配置信息发送给Relay UE。
步骤1206：Relay UE向源基站反馈RRC重配置完成消息。
其中，Relay UE可以通过回复RRC重配置完成消息，向源基站指示已接收到该Relay UE侧的CHO配置信息。
步骤1207：源基站向Remote UE3发送RRC重配置消息。
其中，源基站可以通过该RRC重配置消息，将Remote UE侧的CHO配置信息发送给该Remote UE3，该CHO配置中可以包含目标小区的标识信息，示例性的，该目标小区的标识信息可以是CGI，也可以是源基站为目标小区配置的小区ID信息，比如小区索引信息。
步骤1208：Remote UE向源基站发送RRC重配置完成消息。
其中，Remote UE3可以向源基站回复RRC重配置完成消息，指示源基站Remote UE3已接收到CHO配置信息。
以上是新的Remote UE接入Relay UE场景中CHO配置的更新流程示例。下面以Remote UE断开和Relay UE的连接为例，继续介绍又一种CHO配置更新流程。
示例性的，当有Remote UE离开源基站下的Relay UE时，源基站可以向一个或多个候选目标基站发送指示信息，该指示信息用于指示该一个或多个候选目标基站释放之前在进行CHO配置时为该Remote UE预留的空口资源，包括释放：为该Remote UE预先配置的在候选目标小区的端对端无线承载配置以及PC5 RLC承载配置，以及释放：为该Remote UE提供中继服务所需的Relay UE侧的PC5 RLC承载和Uu RLC承载配置。该指示信息中可以包括该Remote UE的ID信息，该Remote UE的ID信息，可以是该Remote UE的L2 ID，也可以是源站或者目标站为该Remote UE分配的临时标识local ID，或者还可以是源站或者目标站为该Remote UE分配的CRNTI，或者是此处提到的这几种Remote UE ID信息中的一个或多个的结合，本申请实施例对此不作限定。
示例性的，源基站还可以向Relay UE发送RRC重配置消息，对Relay UE侧的CHO配置进行更新，更新的一个目的是释放Relay UE侧的配置新中的和所离开的Remote UE的相关 的配置。其中，源基站发给Relay UE的所述RRC重配置消息中可以包括该离开的Remote UE的ID信息，该Remote UE的ID信息，可以是该Remote UE的L2 ID，也可以是源站或者目标站为该Remote UE分配的临时标识local ID，或者还可以是源站或者目标站为该Remote UE分配的CRNTI，或者是此处提到的这几种Remote UE ID信息中的一个或多个的结合，本申请实施例对此不作限定。在另一种可能的实现方式中，当有Remote UE离开的时候，源基站可以触发一次新的CHO切换流程，使得候选目标基站侧，Relay UE侧以及其余Remote UE的CHO配置信息进行重新配置，重配置的流程可以参考如图11所示出的实施例流程，在此不再赘述。
本申请以上实施例所讨论的方案中，其主要思想包括：针对切换过程，提前为Remote UE和Relay UE配置对应的CHO配置，当Relay UE的CHO切换执行条件触发时，Relay UE指示Remote UE执行相应的配置，使得Remote UE能够跟随Relay UE一起接入目标基站，而不需要断开和Relay UE之间的连接，该方法和现有技术中Remote UE需要进行RRC重建立流程相比，可以减小Remote UE的服务中断时长，从而提高数据传输效率。
本申请实施例还提出了另一种Relay UE指示Remote UE执行CHO切换的通信方法，该通信方法可以应用的场景如，当Remote UE通过Relay UE接入源基站，并且Relay UE发生Uu接口无线链路失败(radio link failure，RLF)，则Relay UE可以指示Remote UE执行CHO切换；或者当Remote UE检测到PC5 RLF时，可以主动触发执行CHO切换。
针对这些场景，本申请实施例方案可以包括以下部分：1、如何对Remote UE进行CHO切换配置；2、如何触发Remote UE进行CHO切换。通过本申请实施例方案，可以解决现有技术中，针对Relay UE发生Uu RLF或PC 5 RLF而导致无法提供中继通信支持时，Remote UE需要重新选择合适的小区和Relay UE，并进行RRC重建立过程，而这将使得Remote UE经历较长的中断时长。
该通信方法可以如图13所示，图13示出了本申请实施例提供的一种用于CHO切换的通信方法，该方法涉及Remote UE，Relay UE，候选Relay UE(Candidate Relay UE)，源基站Source gNB，目标基站Target gNB以及候选目标基站(Candidate target gNB)，该通信方法的详细流程，可以包括：
步骤1301：源基站接收Remote UE上报的测量报告。
其中，该Remote UE基于源基站的测量配置进行测量，并上报测量报告，该测量报告中可以包含该Remote UE的多个周边小区的ID信息以及周边可选Relay UE的ID信息。
源基站基于测量上报，进行CHO切换决策。源基站可以选定多个候选的目标小区和/或选择该多个候选目标小区下的候选Relay UE。需要说明的是，该多个候选目标小区可以属于相同的候选目标基站，也可以属于不同的候选目标基站。
步骤1302：源基站向一个或多个候选目标基站发送切换请求HANDOVER REQUEST消息。
其中，该HANDOVER REQUEST消息可用于将该Remote UE切换至目标小区或者目标小区下的目标Relay UE。每个目标小区可以对应一条HANDOVER REQUEST消息，此时，每条HANDOVER REQUEST消息中可以携带目标小区的ID信息(例如CGI)，或者可选的，该切换请求消息可以携带目标小区的ID信息(例如CGI)以及一个或者多个候选目标Relay UE的ID。其中，候选目标Relay UE的ID标识可以是该Relay UE的C-RNTI或者L2 ID(源L2 ID/目的L2 ID)。该HANDOVER REQUEST消息还可以携带该Remote UE的上下文信息。
示例性的，如果源基站请求将Remote UE切换至目标Relay UE，那么该切换请求消息中 还可以携带一个或者多个候选目标Relay UE的上下文信息。可选的，每个HANDOVER REQUEST消息中也可以只携带一个候选目标Relay UE，那么，该HANDOVER REQUEST消息中也就可以只携带这一个Relay UE的上下文信息。
可选的，HANDOVER REQUEST消息中还可以携带Remote UE的L2 ID信息，以用于目标基站为该Remote UE分配在目标站下面的临时标识local ID。HANDOVER REQUEST消息还可以携带Remote UE在源站下面的C-RNTI。
步骤1303：源基站接收来自一个或多个候选目标基站发送的切换请求响应。
具体的，候选目标基站针对该切换请求准入成功后，向源基站回复切换请求响应HANDOVER REQUEST ACK消息，每个候选目标小区可以对应一条HANDOVER REQUEST ACK消息。
示例性的，该HANDOVER REQUEST ACK消息中可以携带：候选目标小区的ID信息(如CGI)和Remote UE的无线承载配置信息；或者，该HANDOVER REQUEST ACK消息可以携带：候选目标小区的ID信息(如CGI)以及一组或者多组：候选目标Relay UE的ID信息(L2 ID或者C-RNTI)+该候选目标Relay UE的无线承载配置+该Remote UE的无线承载配置。可以理解的是，这一组或者多组信息可以分别对应一个或者多个候选目标Relay UE，也就是说，针对每个候选目标Relay UE，都可以配置这一组信息。
可选的，在上述每一组候选目标Relay UE的配置中，可以携带目标基站为Relay UE周边的一个或多个Remote UE分配的Remote UE临时标识(local ID)和Remote UE的L2 ID，这样该Relay UE就可以基于Remote UE临时标识local ID和Remote UE的L2 ID，识别出目标基站为自己周边的Remote UE配置的临时标识local ID。
可以理解的是，本申请实施例中所涉及的源基站和目标基站之间交互的handover request消息和handover request ACK消息，以及这两个消息中交互的内容，可以作为独立实施方式存在，解决源基站和目标基站如何为Relay UE和Remote UE配置候选目标小区的无线资源，以及可以解决当Relay UE出现RLF时，如何为Remote UE提供相应的目标小区的无线配置和候选目标Relay UE的无线配置的问题。
需要说明的是，本申请实施例中涉及的符号“+”，可以表示“和”的关系，比如A+B，可以理解成A和B。
可选的，每一条HANDOVER REQUEST ACK消息中可以只携带一个候选目标Relay UE的配置信息，即HANDOVER REQUEST ACK消息中包括：候选目标小区的ID信息(如CGI)+候选目标Relay UE的ID信息(L2 ID或者C-RNTI)+该候选目标Relay UE的无线承载配置(或者称为CHO配置)+Remote UE的无线承载配置(或者称为CHO配置)。
示例性的，上述每一条HANDOVER REQUEST ACK消息还可以携带目标基站为Remote UE分配的临时标识local ID和Remote UE的L2 ID。
步骤1304：源基站通过RRC重配置消息，将候选目标Relay UE的配置发送给该候选Relay UE。
其中，该候选目标Relay UE的配置可以包括如下中一个或多个：该候选目标Relay UE的在候选目标小区的无线承载配置，Remote UE的ID信息(比如包括：Remote UE的L2 ID+候选目标基站为Remote UE分配的local ID)。
步骤1305：候选Relay UE向源基站发送RRC重配置完成消息。
步骤1306：源基站向Remote UE发送RRC重配置消息。
其中，源基站可以为每个候选目标小区或者每个候选目标小区下的候选Relay UE生成 CHO切换执行条件，然后和Remote UE的无线承载配置信息一起，通过RRC重配置消息发送给该Remote UE。比如，该RRC重配置消息中可以包括如下中的一个或多个：CHO切换执行条件，该Remote UE的无线承载配置，目标小区的ID信息以及候选目标Relay的ID信息。
可以理解的是，Remote UE可以配置多个候选目标Relay UE，一个relay UE也可以对应多个Remote UE的CHO配置，因此，Remote UE和Relay UE各自的配置需要进行对应。比如，在Remote UE侧，Remote UE收到的配置信息中可以包含Relay UE的ID信息，例如Relay UE的L2 ID，以便于Remote UE的CHO切换执行条件触发时，知道应指示周边哪个relay UE触发相应的CHO配置。在Relay UE侧，Relay UE的无线承载配置中，可以包含Remote UE的临时ID，或者在Relay UE的无线承载配置中，还可以携带Remote UE的L2 ID信息。
步骤1307：Remote UE向源基站发送RRC重配置完成消息。
步骤1308a：CHO条件触发。
示例性的，Remote UE的某个CHO条件触发，则该Remote UE接入目标小区或者目标Relay UE。若CHO切换执行条件对应于某个候选目标Relay UE，则Remote UE可以根据CHO配置中携带的Relay UE的ID信息，给目标Relay UE发送指示信息，Relay UE根据指示信息，知道是哪个remote UE触发了CHO，于是应用对应该Remote UE的无线承载配置。
在一种设计中，源基站在给Remote UE配置CHO切换执行条件时，该CHO切换执行条件可以配置为如下一个或多个：Remote UE检测到PC5发生RLF，或者，Relay UE指示Remote UE发生了Uu RLF。其中，PC5是Remote UE和为该Remote UE提供中继服务的Relay UE之间的通信接口，Uu是为该Remote UE提供中继服务的Relay UE和源基站之间的通信接口。也就是，当上述两个条件之一或者两者都发生时，Remote UE将触发CHO切换，并应用相应的CHO配置。可选的，源基站可以只在一套CHO配置中配置上述切换执行条件，作为Remote UE的备用配置，当发生PC5 RLF或者Uu RLF时，Remote UE可以快速切换至目标小区和或目标小区下的目标Relay UE。
在另一种可能的实现方式中，源基站不需要将上述CHO切换执行条件配置在CHO配置中，而是由协议规定，当上述Uu RLF或者PC5 RLF发生时，Remote UE自行从自己的一套或者多套CHO配置中选择一套执行，比如可以选择CHO切换执行条件中配置的链路信号质量最接近阈值的一套，或者随机选择一套。还可能的方式是，Remote UE基于实现，自行在上述Uu RLF或者PC5 RLF发生时，选择一套CHO配置进行切换。
步骤1308：Relay UE向Remote UE指示发生RLF。
该步骤为可选，其中，Relay UE可以向Remote UE指示发生Uu RLF或者PC5 RLF。
步骤1309：建立单播连接。
该步骤为可选，若先前两者之间没有单播连接，则Remote UE和候选Relay UE之间可以建立单播连接。
步骤1310：Remote UE向候选Relay UE发送CHO触发指示。
步骤1311：通过Relay UE向目标小区发送RRC重配置完成消息。
若触发的CHO切换执行条件对应于一个目标relay UE，则Remote UE在给Relay UE发送指示信息后，可以通过该Relay UE给目标小区发送RRC配置完成消息。
如下可选的，若触发的CHO切换执行条件对应于一个目标小区，则
步骤1312：随机接入目标基站。
其中，Remote UE可以根据相应的配置随机接入目标基站的该目标小区。
步骤1313：向目标基站的目标小区发送RRC重配置完成消息。
上述主要从各个设备之间进行通信交互的角度对本申请实施例提供的方案进行了介绍。相应的，本申请实施例还提供了通信装置，该通信装置用于实现上述各种方法。
该通信装置可以为上述方法实施例中的第一网络节点，或者包含上述第一网络节点的装置，或者为可用于第一网络节点的部件或计算机程序，可以理解的是，第一网络节点也可以是切换过程或切换准备过程中的源侧网络设备，本申请实施例对此不作限定；或者，
该通信装置可以为上述方法实施例中的第二网络节点，或者包含上述第二网络节点的装置，或者为可用于第二网络节点的部件或计算机程序，可以理解的是，第二网络节点也可以是切换过程或切换准备过程中的目标侧网络设备，本申请实施例对此不作限定；或者，
该通信装置可以为上述方法实施例中的中继终端设备，或者包含上述中继终端设备的装置，或者为可用于中继终端设备的部件或计算机程序，可以理解的是，中继终端设备可以是切换过程或切换准备过程中的Relay UE，本申请实施例对此不作限定；或者，
该通信装置可以为上述方法实施例中的远端终端设备，或者包含上述远端终端设备的装置，或者为可用于远端终端设备的部件或计算机程序，可以理解的是，远端终端设备可以是切换过程或切换准备过程中的Remote UE，本申请实施例对此不作限定。
可以理解的是，该通信装置为了实现上述方法/操作/功能，其包含了执行各个方法/操作/功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法实施例中对通信装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，可以采用软件功能模块的形式实现，也可以采用硬件结合软件的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
图14示出了一种通信装置140的结构示意图。该通信装置140包括收发模块1401和处理模块1402。所述收发模块1401，也可以称为收发单元用以实现该通信装置与其他设备之间的信息收发功能，例如可以是收发电路，收发机，收发器或者通信接口。需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该通信装置140以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个实施例中，本领域的技术人员可以想到该通信装置140可以采用图9所示的通信装置90的形式。
比如，图9所示的通信装置90中的处理器901可以通过调用存储器903中存储的计算机执行指令，使得通信装置90执行上述方法实施例中的通信方法。
具体的，图14中的收发模块1401和处理模块1402的功能/实现过程可以通过图9所示的通信装置90中的处理器901调用存储器903中存储的计算机执行指令来实现。或者，图14中的处理模块1402的功能/实现过程可以通过图8所示的通信装置90中的处理器901调用存储器903中存储的计算机执行指令来实现，图14中的收发模块1401的功能/实现过程可以 通过图9中所示的通信装置90中的通信接口904来实现。
由于本实施例提供的通信装置140可执行上述通信方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、设备和方法，可以通过其它的方式实现。例如，以上所描述的设备实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，设备或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
如本申请所使用的，术语“组件”、“模块”、“系统”等等旨在指代计算机相关实体，该计算机相关实体可以是硬件、固件、硬件和软件的结合、软件或者运行中的软件。例如，组件可以是，但不限于是：在处理器上运行的处理、处理器、对象、可执行文件、执行中的线程、程序和/或计算机。作为示例，在计算设备上运行的应用和该计算设备都可以是组件。一个或多个组件可以存在于执行中的过程和/或线程中，并且组件可以位于一个计算机中以及/或者分 布在两个或更多个计算机之间。此外，这些组件能够从在其上具有各种数据结构的各种计算机可读介质中执行。这些组件可以通过诸如根据具有一个或多个数据分组(例如，来自一个组件的数据，该组件与本地系统、分布式系统中的另一个组件进行交互和/或以信号的方式通过诸如互联网之类的网络与其它系统进行交互)的信号，以本地和/或远程过程的方式进行通信。
本申请围绕可包括多个设备、组件、模块等的系统来呈现各个方面、实施例或特征。应当理解和明白的是，各个系统可以包括另外的设备、组件、模块等，并且/或者可以并不包括结合附图讨论的所有设备、组件、模块等。此外，还可以使用这些方案的组合。
另外，在本申请实施例中，“示例的”一词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
本申请实施例中，信息(information)，消息(message)有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是一致的。“的(of)”，“相应的(corresponding，relevant)”和“对应的(corresponding)”有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是一致的。“系统”和“网络”有时可以混用，在不强调其区别时，其所要表达的含义是一致的，比如，“通信网络”也即是指“通信系统”。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (26)

  1. 一种通信方法，应用于第一网络节点，其特征在于，所述方法包括：
    所述第一网络节点向第二网络节点发送切换请求信息，所述切换请求信息包括：中继终端设备的第一标识信息和所述中继终端设备的用户设备上下文信息，远端终端设备的第一标识信息和所述远端终端设备的用户设备上下文信息；其中，所述远端终端设备通过所述中继终端设备与所述第一网络节点进行通信交互，所述切换请求信息用于所述中继终端设备从所述第一网络节点向所述第二网络节点的小区进行切换；
    所述第一网络节点从所述第二网络节点接收切换响应信息，所述切换响应信息包括：所述中继终端设备的第二标识信息和为所述中继终端设备配置的所述第二网络节点的第一小区的无线承载配置信息，以及所述远端终端设备的第二标识信息和为所述远端终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息。
  2. 根据权利要求1所述的方法，其特征在于，所述远端终端设备的第一标识信息包括如下中一个或多个：
    所述第一网络节点为所述远端终端设备分配的所述远端终端设备的CRNTI，所述远端终端设备的层2标识，以及所述第一网络节点为所述远端终端设备分配的所述远端终端设备的临时标识。
  3. 根据权利要求1或2所述的方法，其特征在于：
    所述远端终端设备的第二标识信息包括所述远端终端设备的所述第一标识信息；或者，
    所述远端终端设备的第二标识信息包括如下中一个或多个：所述第二网络节点为所述远端终端设备分配的所述远端终端设备的CRNTI，所述远端终端设备的层2标识，以及所述第二网络节点为所述远端终端设备分配的所述远端终端设备的临时标识。
  4. 根据权利要求1-3任一所述的方法，其特征在于，所述切换响应信息中包括：
    所述第二网络节点的所述第一小区的第一标识信息，第一配置信息和第二配置信息；
    其中，所述第一配置信息包括：所述为所述中继终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息；所述为所述中继终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息，包括：所述中继终端设备在所述第二网络节点的所述第一小区的无线承载配置，以及所述中继终端设备为所述远端终端设备提供中继服务所需要的PC5接口的RLC承载配置信息和Uu接口的RLC承载配置信息，所述PC5接口是所述中继终端设备和所述远端终端设备之间的通信接口，所述Uu接口是所述中继终端设备和所述第二网络节点之间的通信接口；
    其中，所述第二配置信息包括：所述为所述远端终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息；所述为所述远端终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息，包括：所述远端终端设备在所述第二网络节点的所述第一小区的无线承载配置，以及所述远端设备的PC5接口的RLC承载配置信息，所述PC5接口是所述远端终端设备和所述中继终端设备之间的通信接口。
  5. 根据权利要求1-4任一所述的方法，其特征在于，所述方法还包括：
    所述第一网络节点向所述中继终端设备发送第三配置信息，所述第三配置信息包括：为所述中继终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息，以及所述第二网络节点的所述第一小区的第二标识信息；
    其中，所述第二网络节点的所述第一小区是所述中继终端设备进行切换的候选目标 小区。
  6. 根据权利要求1-5任一所述的方法，其特征在于，所述方法还包括：
    所述第一网络节点向所述远端终端设备发送第四配置信息，所述第四配置信息包括：为所述远端终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息，以及所述第二网络节点的所述第一小区的第二标识信息，其中，所述第二网络节点的所述第一小区是所述中继终端设备进行切换的候选目标小区。
  7. 根据权利要求5或6所述的方法，其特征在于：
    所述第二网络节点的所述第一小区的第二标识信息，包括：所述第一网络节点为所述第二网络节点的所述第一小区分配的标识；或者，
    所述第二网络节点的所述第一小区的第二标识信息，包括全球小区标识CGI，所述CGI由所述第二网络节点通过所述切换响应信息发送给所述第一网络节点。
  8. 根据权利要求1-7任一所述的方法，其特征在于，所述第一网络节点和所述第二网络节点为同一个网络节点。
  9. 一种通信方法，应用于中继终端设备，其特征在于，所述方法包括：
    所述中继终端设备接收第一网络节点发送的第三配置信息，所述第三配置信息包括：为所述中继终端设备配置的第二网络节点的第一小区的无线承载配置信息，以及所述第二网络节点的所述第一小区的第二标识信息，其中，所述第二网络节点的所述第一小区是所述中继终端设备进行切换的候选目标小区；
    所述中继终端设备向远端终端设备发送第一信息，所述第一信息用于指示：所述第二网络节点的所述第一小区的所述第二标识信息，或者，所述第一信息用于指示：所述第二网络节点的所述第一小区的配置的排序信息。
  10. 根据权利要求9所述的方法，其特征在于，所述第二网络节点的所述第一小区的所述第二标识信息，包括：所述第一网络节点为所述第二网络节点的所述第一小区分配的标识。
  11. 根据权利要求9所述的方法，其特征在于，所述第二网络节点的所述第一小区的所述第二标识信息包括全球小区标识CGI，所述CGI由所述第二网络节点通过切换响应信息发送给所述第一网络节点。
  12. 根据权利要求9-11中任一所述的方法，其特征在于，所述为所述中继终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息，包括：所述中继终端设备在所述第二网络节点的所述第一小区的无线承载配置，以及所述中继终端设备为所述远端终端设备提供中继服务所需要的PC5接口的RLC承载配置信息和Uu接口的RLC承载配置信息，所述PC5接口是所述中继终端设备和所述远端终端设备之间的通信接口，所述Uu接口是所述中继终端设备和所述第二网络节点之间的通信接口。
  13. 根据权利要求9-12中任一所述的方法，其特征在于，当所述第二网络节点的所述第一小区满足切换触发条件，则所述中继终端设备向所述远端终端设备发送所述第一信息。
  14. 一种通信方法，应用于远端终端设备，其特征在于，所述方法包括：
    所述远端终端设备接收第一网络节点发送的第四配置信息，所述第四配置信息包括：为所述远端终端设备配置的第二网络节点的第一小区的无线承载配置信息，以及所述第 二网络节点的所述第一小区的第二标识信息，其中，所述第二网络节点的所述第一小区是所述中继终端设备进行切换的候选目标小区；
    所述远端终端设备接收所述中继终端设备发送的第一信息，所述第一信息指示：所述第二网络节点的所述第一小区的第二标识信息，或者，所述第一信息指示：所述第二网络节点的所述第一小区的配置的排序信息。
  15. 根据权利要求14所述的方法，其特征在于，所述第二网络节点的所述第一小区的标识信息，包括：所述第一网络节点为所述第二网络节点的所述第一小区分配的标识。
  16. 根据权利要求14所述的方法，其特征在于，所述第二网络节点的所述第一小区的标识信息包括全球小区标识CGI，所述CGI由所述第二网络节点通过切换响应信息发送给所述第一网络节点。
  17. 根据权利要求14-16中任一所述的方法，其特征在于，所述为所述远端终端设备配置的所述第二网络节点的所述第一小区的无线承载配置信息，包括：所述远端终端设备在所述第二网络节点的所述第一小区的无线承载配置，以及所述远端设备的PC5接口的RLC承载配置信息，所述PC5接口是所述远端终端设备和所述中继终端设备之间的通信接口。
  18. 根据权利要求14-17中任一所述的方法，其特征在于，当所述第二网络节点的所述第一小区满足切换触发条件，则所述第一信息被所述中继终端设备发给所述远端终端设备。
  19. 一种第一网络节点，其特征在于，所述第一网络节点包括：处理器和存储器；
    所述存储器用于存储计算机指令，当所述处理器执行所述计算机指令时，使得所述第一网络节点执行如权利要求1-8中任一项所述的方法。
  20. 一种中继终端设备，其特征在于，所述中继终端设备包括：处理器和存储器；
    所述存储器用于存储计算机指令，当所述处理器执行所述计算机指令时，以使所述中继终端设备执行如权利要求9-13中任一项所述的方法。
  21. 一种远端终端设备，其特征在于，所述远端终端设备包括：处理器和存储器；
    所述存储器用于存储计算机指令，当所述处理器执行所述计算机指令时，以使所述远端终端设备执行如权利要求14-18中任一项所述的方法。
  22. 一种通信实体，其特征在于，包括用于执行如权利要求1-18中的任一项所述方法的模块。
  23. 一种通信装置，其特征在于，所述通信装置包括：处理器和接口电路；
    所述接口电路，用于和所述处理器交互计算机指令或数据；
    所述处理器用于执行计算机指令，使得所述通信装置执行如权利要求1-18中任一项所述的方法。
  24. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机指令，当所述计算机指令被计算机执行，使得所述计算机执行权利要求1-18中任一项所述的方法。
  25. 一种包含计算机指令的计算机程序产品，其特征在于，当所述计算机指令在计算机上运行时，使得所述计算机执行权利要求1-18中任一项所述的方法。
  26. 一种通信系统，其特征在于，包括如下中的一个或多个：
    如权利要求19所述的第一网络节点；
    如权利要求20所述的中继终端设备；
    如权利要求21所述的远端终端设备；
    如权利要求22所述的通信实体；
    如权利要求23所述的通信装置；
    如权利要求24所述的计算机可读存储介质；以及，
    如权利要求25所述的计算机程序产品。
PCT/CN2022/136835 2021-12-31 2022-12-06 一种通信协作方法及装置 WO2023124822A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111670280.3 2021-12-31
CN202111670280.3A CN116419339A (zh) 2021-12-31 2021-12-31 通信方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2023124822A1 true WO2023124822A1 (zh) 2023-07-06

Family

ID=86997616

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/136835 WO2023124822A1 (zh) 2021-12-31 2022-12-06 一种通信协作方法及装置

Country Status (2)

Country Link
CN (1) CN116419339A (zh)
WO (1) WO2023124822A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180279188A1 (en) * 2017-03-23 2018-09-27 Futurewei Technologies, Inc. Group Handover Methods and Systems
CN110720238A (zh) * 2017-05-05 2020-01-21 中兴通讯股份有限公司 用于实施群组切换的方法和装置
WO2021254011A1 (zh) * 2020-06-19 2021-12-23 展讯通信（上海）有限公司 通信方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180279188A1 (en) * 2017-03-23 2018-09-27 Futurewei Technologies, Inc. Group Handover Methods and Systems
CN110720238A (zh) * 2017-05-05 2020-01-21 中兴通讯股份有限公司 用于实施群组切换的方法和装置
WO2021254011A1 (zh) * 2020-06-19 2021-12-23 展讯通信（上海）有限公司 通信方法及装置

Also Published As

Publication number Publication date
CN116419339A (zh) 2023-07-11

Similar Documents

Publication Publication Date Title
US11546811B2 (en) Method for establishing a fronthaul interface, method for performing access for a UE, method and apparatus for performing a handover for a UE, data forwarding method, user equipment and base station
CN110351024B (zh) 数据传输方法和装置
US10512009B2 (en) Method for user equipment to switch base station, base station and user equipment
US10412650B2 (en) Data transmission method, apparatus and system
JP6785346B2 (ja) データ・オフロードのためのパスを確立する方法及び装置
JP7135100B2 (ja) パケット伝送方法、装置、およびシステム
US8442007B2 (en) Bearer establishing method and system based on handover
CN108377567B (zh) 一种在5g架构下建立双连接传输数据的方法、装置和系统
EP3637846B1 (en) Method and device for use in configuring novel quality of service architecture in dual connectivity system
WO2018045877A1 (zh) 网络切片控制方法及相关设备
KR20190133031A (ko) 통신 방법 및 장치
US20150312810A1 (en) Radio communication system and communication control method
WO2021238774A1 (zh) 通信方法及装置
WO2020098747A1 (zh) 传输路径的配置方法及装置
WO2022067818A1 (zh) 一种数据传输方法及装置
TWI775009B (zh) 用於行動通訊系統之基地台及其資料傳輸方法
KR102246493B1 (ko) 이동통신 시스템에서 멀티 셀 네트워크 구축 방법 및 장치
EP3852481A1 (en) Mode switching method and data stream distribution method and apparatus
WO2021026706A1 (zh) 一种f1接口管理方法及装置
WO2016187751A1 (zh) 无线承载建立方法和设备
CN105009663B (zh) 一种消息传输方法及设备
WO2023124822A1 (zh) 一种通信协作方法及装置
US8774132B2 (en) Base station device, base station controlling device, mobile terminal, communication system, and method for controlling base station device
CN109803390B (zh) 消息、策略发送方法及装置，存储介质，处理器
WO2022082691A1 (zh) Iab网络的rlf恢复方法、装置以及相关设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22914077

Country of ref document: EP

Kind code of ref document: A1