WO2023066041A1 - 通信方法、装置及系统 - Google Patents

通信方法、装置及系统 Download PDF

Info

Publication number
WO2023066041A1
WO2023066041A1 PCT/CN2022/124044 CN2022124044W WO2023066041A1 WO 2023066041 A1 WO2023066041 A1 WO 2023066041A1 CN 2022124044 W CN2022124044 W CN 2022124044W WO 2023066041 A1 WO2023066041 A1 WO 2023066041A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
information
terminal device
remote terminal
rlc
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2022/124044
Other languages
English (en)
French (fr)
Inventor
潘晓丹
彭文杰
王瑞
史玉龙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to KR1020247016387A priority Critical patent/KR20240076847A/ko
Priority to JP2024523682A priority patent/JP7835855B2/ja
Priority to EP22882651.7A priority patent/EP4408116A4/en
Publication of WO2023066041A1 publication Critical patent/WO2023066041A1/zh
Priority to US18/640,752 priority patent/US20240267826A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/246—Connectivity information discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/248—Connectivity information update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/14—Mobility data transfer between corresponding nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • the present application relates to the field of wireless communication, and in particular to a communication method, node, device, computer-readable storage medium and wireless access network equipment.
  • UE User equipment
  • UE-to-Network relay U2N Relay
  • relay UE provides relay communication for remote UE (Remote UE)
  • the remote UE accesses the radio access network device through the relay UE.
  • 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.
  • the data packets of the Remote UE are relayed and forwarded below the Packet Data Convergence Protocol (PDCP) layer of the Relay UE, that is, the Relay UE Maintain the radio link control (Radio Link Control, RLC) bearer used for relaying.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • the relay RLC bearer includes the RLC protocol layer, the media access control (Media Access Control, MAC) protocol layer, and the physical layer (Physical Layer, PHY) ; There are PDCP protocol layer for end-to-end communication between the Remote UE and the gNB base station, the Service Data Adaptation Protocol (Service Data Adaptation Protocol, SDAP) protocol layer and the radio resource control (radio resource control, RRC) protocol layer, but there is no RLC, MAC and PHY layers for end-to-end communication.
  • an adaptation layer (Adaptation layer, ADAPT) is added between the RLC layer and the PDCP layer.
  • the main functions of this adaptation layer include bearer multiplexing and demultiplexing, for example, supporting different Bearers are multiplexed into one bearer or a bearer is split into multiple different bearers.
  • the gNB base station adopts the CU-DU separation architecture, that is to say, a gNB base station is logically divided into a centralized unit (Central Unit, CU) and The two parts of the distributed unit (Distributed Unit, DU) communicate through the F1 interface between gNB-CU and gNB-DU, but the existing communication process of the F1 interface between gNB-CU and gNB-DU cannot support L2 U2N Relay communication.
  • CU Central Unit
  • DU distributed Unit
  • Embodiments of the present application provide communication methods, network nodes, devices, computer-readable storage media, and wireless access network equipment to solve the problem that the F1 interface between gNB-CU and gNB-DU cannot support existing The problem of L2 U2N Relay communication.
  • 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 first information to a second network node, the first information is used to trigger the second network node to assign a local identifier to a remote terminal device, and the first network node A network node receives second information from the second network node, where the second information includes a local identifier assigned by the second network node to the remote terminal device; or, the first network node sends the The second network node sends first information, where the first information includes the local identifier assigned by the first network node to the remote terminal device; wherein, the first network node or the second network node passes The relay terminal device communicates with the remote terminal device.
  • the first network node may assign a local identifier to the remote terminal device and notify the second network node, or the first network node may instruct the second network node to assign a local identifier to the remote terminal device, so that
  • the communication between the first network node (taking gNB-CU as an example) and the second network node (taking gNB-DU as an example) can support the existing Layer 2 U2N Relay communication.
  • the first network node receives third information sent by the second network node; the third information includes The identification information of the remote terminal device assigned by the terminal device on the first interface, or the third information includes the remote terminal device assigned by the second network node to the remote terminal device at the first interface Identification information of an interface and identification information of the relay terminal device on the first interface allocated by the second network node to the relay terminal device; wherein the first interface is the first network A communication interface between a node and said second network node.
  • the second network node (take gNB-DU as an example) allocates the identification information of the terminal device on the first interface to the remote terminal device, and may let the first network node (take gNB-DU -CU as an example) knows the relay terminal device to which the remote terminal device is connected, and can successfully send the configuration information required by the relay service to the relay terminal device.
  • Operation 1 The first network node sends fourth information to the second network node, where the fourth information includes the data radio bearer identifier DRB ID information of the remote terminal device and the first radio link control RLC bearer There is a corresponding relationship between the DRB ID information of the remote terminal device and the identification information carried by the first RLC; the first network node receives the fifth information sent by the second network node, and the The fifth information includes configuration information of the first RLC bearer generated by the second network node; wherein the first RLC bearer is a bearer between the remote terminal device and the relay terminal device, There is a corresponding relationship between the DRB ID information of the remote terminal equipment and the identification information carried by the first RLC;
  • the first network node receives the fifth information generated by the second network node, the fifth information includes: the data radio bearer identification DRB ID information of the remote terminal equipment, the first RLC bearer identification information, and configuration information of the first RLC bearer, wherein the first RLC bearer is a bearer between the remote terminal device and the relay terminal device, and the DRB of the remote terminal device There is a corresponding relationship between the ID information and the identification information carried by the first RLC;
  • operation three the first network node sends fourth information to the second network node, where the fourth information includes the data radio bearer identifier DRB ID information of the remote terminal device, and the remote terminal device The local identification of the second RLC bearer, and the identification information of the second RLC bearer; the first network node receives fifth information generated by the second network node, and the fifth information includes configuration information of the second RLC bearer; wherein, The second RLC bearer is a bearer between the second network node and the relay terminal device; the DRB ID information of the remote terminal device, the local identifier of the remote terminal device, and the second There is a corresponding relationship between the identification information carried by the RLC;
  • operation four the first network node receives fifth information generated by the second network node, where the fifth information includes at least one of the following: DRB ID information of the remote terminal device, The local identifier of the remote terminal device, the identification information of the second RLC bearer, and the configuration information of the second RLC bearer; wherein, the second RLC bearer is the second network node and the relay terminal There is a corresponding relationship between the bearer between devices, the DRB ID information of the remote terminal device, the local identifier of the remote terminal device, and the identification information carried by the second RLC.
  • the method may further include: the first network node sending fourth information to the second network node , the fourth information includes identification information of the remote device.
  • the fourth information further includes identification information of an uplink transmission tunnel, and the identification information of the uplink transmission tunnel corresponds to at least one of the following: Relationship: the DRB ID information of the remote terminal device, the local identifier of the remote terminal device, the identification information of the remote terminal device, and the identification information carried by the second RLC; wherein, the uplink transmission The tunnel is used for the first network node to receive data from the second network node on the first interface; and/or, the fifth information further includes identification information of a downlink transmission tunnel, and the downlink transmission tunnel
  • the identification information of the remote terminal device has a corresponding relationship with at least one of the following: the DRB ID information of the remote terminal device, the local identification of the remote terminal device, the identification information of the remote terminal device, and the second RLC bearer identification information; wherein, the downlink transmission tunnel is used for sending data from the first network node to the second network node on the first interface.
  • the second network node taking gNB-DU as an example
  • the first network node taking gNB-CU as an example
  • can configure the required remote terminal for the remote terminal device The bearer configuration of the device and the bearer configuration of the relay terminal device, and enable the relay terminal device to provide a relay service for data transmission between the remote terminal device and the network node.
  • the first network node receives first indication information from the relay terminal device, where the first indication information includes the Identification information, where the first indication information is used to request allocation of a local identifier for the remote terminal device, and the local identifier of the remote terminal device is used to uniquely identify the remote terminal device within the scope of control of the first network node
  • the terminal device, or the local identifier of the remote terminal device is used to uniquely identify the remote terminal device within the control range of the relay terminal device.
  • the first information is a user equipment context modification request UE CONTEXT MODIFICATION REQUEST message of the relay terminal device
  • the second information is the The user equipment context modification response UE CONTEXT MODIFICATION RESPONSE message of the device
  • the fourth information is the user equipment context establishment request UE CONTEXT SETUP REQUEST message of the remote terminal device
  • the fifth information is the remote terminal
  • the user equipment context establishment of the device responds to a UE CONTEXT SETUP RESPONSE message
  • the third information is an Initial UL RRC Message Transfer message for an initial uplink RRC message transfer of the remote terminal device.
  • the first network node includes: a radio resource control RRC protocol layer, a service data adaptation protocol SDAP protocol layer, and a packet data convergence layer protocol PDCP protocol layer;
  • the second network node includes: a radio link control RLC protocol layer, a medium access control MAC protocol layer, and a physical PHY protocol layer, and the first network node and the second network node belong to the same base station gNB.
  • the second network node is the The target node
  • the third network node is the source node in the handover process
  • the first network node controls the second network node and the third network node, and conforms to any of the following: the first The first information is a UE CONTEXT SETUP REQUEST message of the remote terminal device's user equipment context establishment request, and the second information is a UE CONTEXT SETUP RESPONSE message of the remote terminal device's user equipment context establishment response; or, the first The fourth information is the UE CONTEXT SETUP REQUEST message of the remote terminal device's user equipment context establishment request, and the fifth information is the UE CONTEXT SETUP RESPONSE message of the remote terminal device's user equipment context establishment response.
  • the third network node includes: a radio link control RLC protocol layer, a media access control MAC protocol layer, and a physical PHY protocol layer, and the first network node , the second network node, and the third network node are included in one base station gNB.
  • the method may further include: the fourth information or the fifth information further includes the first identifier, the The first identifier is used to indicate that the relay terminal device corresponds to the first RLC bearer.
  • the first identifier is an identifier of the relay terminal or a serving cell identifier of the relay terminal or an identifier assigned to the relay terminal by the first network node or an identifier assigned to the relay terminal by the second network node.
  • a communication method is provided, and the entity executing the communication method may be a second network node, or a functional module applied in the second network node, or a chip or a chip system in the second network node , or a network entity or network device that implements the function of the second network node.
  • the communication method may include: the second network node receives first information from the first network node, the first information is used to trigger the second network node to allocate a local identifier for the remote terminal device, and the The second network node sends second information to the first network node, where the second information includes the local identifier assigned by the second network node to the remote terminal device; or, the second network node receives First information from a first network node, where the first information includes a local identifier assigned by the first network node to the remote terminal device; wherein, the first network node or the second network node Communicate with the remote terminal device through the relay terminal device.
  • the first network node may assign a local identifier to the remote terminal device and notify the second network node, or the first network node may instruct the second network node to assign a local identifier to the remote terminal device, and the second network
  • the node notifies the first network node of the assigned local identifier of the remote terminal equipment, so that the communication between the first network node (take gNB-CU as an example) and the second network node (take gNB-DU as an example) Communication, it can support the existing Layer 2 U2N Relay communication.
  • the second network node sends third information to the first network node;
  • the third information includes that the second network node is the remote The identification information of the remote terminal device on the first interface allocated by the terminal device, or the third information includes the identification information of the remote terminal device allocated by the second network node on the first interface The identification information of the interface and the identification information of the relay terminal device on the first interface allocated by the second network node to the relay terminal device; wherein, the first interface is the second network node and a communication interface between the first network node.
  • the method may include any of the following operations:
  • the second network node receives fourth information sent by the first network node, where the fourth information includes the data radio bearer identifier DRB ID information of the remote terminal device and the first radio link Controlling the identification information carried by RLC, there is a corresponding relationship between the DRB ID information of the remote terminal equipment and the identification information carried by the first RLC;
  • the second network node sends fifth information to the first network node , the fifth information includes configuration information of the first RLC bearer generated by the second network node; wherein the first RLC bearer is a communication between the remote terminal device and the relay terminal device bearer, there is a correspondence between the DRB ID information of the remote terminal device and the identification information carried by the first RLC;
  • optional operation 2 the second network node sends fifth information to the first network node, where the fifth information includes: the data radio bearer identifier DRB ID information of the remote terminal device, the first RLC identification information of the bearer, and configuration information of the first RLC bearer, wherein the first RLC bearer is a bearer between the remote terminal device and the relay terminal device, and the remote terminal device's There is a correspondence between the DRB ID information and the identification information carried by the first RLC;
  • the second network node receives fourth information sent by the first network node, where the fourth information includes the data radio bearer identifier DRB ID information of the remote terminal device, and the remote a local identifier of the end-terminal device, and identification information of the second RLC bearer; the second network node sends fifth information to the first network node, and the fifth information includes configuration information of the second RLC bearer;
  • the second RLC bearer is a bearer between the second network node and the relay terminal device; the DRB ID information of the remote terminal device, the local identifier of the remote terminal device, and the There is a corresponding relationship between the identification information carried by the second RLC;
  • the second network node sends fifth information to the first network node, where the fifth information includes: the data radio bearer identifier DRB ID information of the remote terminal device, and the remote The local identifier of the end terminal device, and the identification information of the second RLC bearer; wherein, the second RLC bearer is a bearer between the second network node and the relay terminal device, and the remote terminal device's There is a correspondence between the DRB ID information, the local identifier of the remote terminal device, and the identifier information carried by the second RLC.
  • the method may further include: the second network node receiving the fourth network node sent by the first network node information, where the fourth information includes identification information of the remote device.
  • the fourth information further includes identification information of an uplink transmission tunnel, and the identification information of the uplink transmission tunnel corresponds to at least one of the following: Relationship: the DRB ID information of the remote terminal device, the local identifier of the remote terminal device, the identification information of the remote terminal device, and the identification information carried by the second RLC; wherein, the uplink transmission The tunnel is used for the first network node to receive data from the second network node on the first interface; and/or, the fifth information further includes identification information of a downlink transmission tunnel, and the downlink transmission tunnel
  • the identification information of the remote terminal device has a corresponding relationship with at least one of the following: the DRB ID information of the remote terminal device, the local identification of the remote terminal device, the identification information of the remote terminal device, and the second RLC bearer identification information; wherein, the downlink transmission tunnel is used for sending data from the first network node to the second network node on the first interface.
  • the first information is a user equipment context modification request UE CONTEXT MODIFICATION REQUEST message of the relay terminal device
  • the second information is the The user equipment context modification response UE CONTEXT MODIFICATION RESPONSE message of the device
  • the fourth information is the user equipment context establishment request UE CONTEXT SETUP REQUEST message of the remote terminal device
  • the fifth information is the remote terminal
  • the user equipment context establishment of the device responds to a UE CONTEXT SETUP RESPONSE message
  • the third information is an Initial UL RRC Message Transfer message for an initial uplink RRC message transfer of the remote terminal device.
  • the first network node includes: a radio resource control RRC protocol layer, a service data adaptation protocol SDAP protocol layer, and a packet data convergence layer protocol PDCP protocol layer;
  • the second network node includes: a radio link control RLC protocol layer, a media access control MAC protocol layer, and a physical PHY protocol layer; the first network node and the second network node are included in a base station gNB.
  • the second network node is the The target node
  • the third network node is the source node in the handover process
  • the second network node and the third network node are controlled by the first network node, and conform to any of the following:
  • the first information is the UE CONTEXT SETUP REQUEST message of the user equipment context establishment request of the remote terminal device
  • the second information is the UE CONTEXT SETUP RESPONSE message of the user equipment context establishment response of the remote terminal device
  • the The fourth information is a UE CONTEXT SETUP REQUEST message of the remote terminal device's user equipment context establishment request
  • the fifth information is a UE CONTEXT SETUP RESPONSE message of the remote terminal device's user equipment context establishment response.
  • the third network node includes: a radio link control RLC protocol layer, a media access control MAC protocol layer, and a physical PHY protocol layer, and the first network node , the second network node, and the third network node are included in a base station.
  • the method may further include: the fourth information or the fifth information further includes the first identifier, the The first identifier is used to indicate that the relay terminal device corresponds to the first RLC bearer.
  • the first identifier is an identifier of the relay terminal or a serving cell identifier of the relay terminal or an identifier assigned to the relay terminal by the first network node or an identifier assigned to the relay terminal by the second network node.
  • 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 sixth information to the second network node, the sixth information includes second indication information, and the second indication information instructs the second network node to establish the first
  • the second radio link control RLC bearer between the second network node and the relay terminal equipment, the second RLC bearer is used to bear the first data, and the first data is between the remote terminal equipment and the second network node Or data exchanged between the first network nodes; the first network node receives seventh information sent by the second network node DU, where the seventh information includes configuration information of the second RLC bearer.
  • the radio link control RLC bearer referred to in this embodiment has the function of an RLC channel, so it can also be called an RLC channel.
  • the second indication information includes information about a signaling radio bearer (SRB) that needs to be established for the remote device; or, the second indication information includes the Relay service authorization information of the relay terminal device.
  • SRB signaling radio bearer
  • the first data is data carried by the signaling radio bearer SRB0, signaling radio bearer SRB1, or signaling radio bearer SRB2 of the remote terminal device.
  • the data of SRB0, SRB1 and SRB2 of the remote terminal device may be multiplexed on one RLC bearer for transmission.
  • the sixth information is a UE CONTEXT SETUP REQUEST message for a user equipment context setup request
  • the seventh information is a UE CONTEXT SETUP RESPONSE message for a user equipment context setup response.
  • the sixth information is a UE CONTEXT MODIFICATION REQUEST message
  • the seventh information is a UE CONTEXT MODIFICATION RESPONSE message.
  • the first network node includes: a radio resource control RRC protocol layer, a service data adaptation protocol SDAP protocol layer, and a packet data convergence layer protocol PDCP protocol layer;
  • the second network node includes: a radio link control RLC protocol layer, a media access control MAC protocol layer, and a physical PHY protocol layer; the first network node and the second network node are included in a base station gNB.
  • a communication method is provided, and the entity executing the communication method may be a second network node, or a functional module applied to the second network node, or a chip or a chip system in the second network node , or a network entity or network device that implements the function of the second network node.
  • the following description is made by taking the execution subject as an example of the second network node.
  • the communication method may include: the second network node receiving sixth information sent by the first network node, the sixth information including second indication information, the second indication information instructing the second network node to establish the The second radio link between the second network node and the relay terminal device controls the RLC bearer, where the second RLC bearer is used to bear the first data, and the first data is between the remote terminal device and the second network Data exchanged between nodes or the first network node; the second network node sends seventh information to the first network node DU, where the seventh information includes configuration information of the second RLC bearer.
  • the second indication information includes information about a signaling radio bearer (SRB) that needs to be established for the remote device; or, the second indication information includes the Relay service authorization information of the relay terminal device.
  • SRB signaling radio bearer
  • the first data is data carried by the signaling radio bearer SRB0, signaling radio bearer SRB1, or signaling radio bearer SRB2 of the remote terminal device.
  • the data of SRB0, SRB1 and SRB2 of the remote terminal device may be multiplexed on one RLC bearer for transmission.
  • the sixth information is a UE CONTEXT SETUP REQUEST message
  • the seventh information is a UE CONTEXT SETUP RESPONSE message.
  • the sixth information is a UE CONTEXT MODIFICATION REQUEST message
  • the seventh information is a UE CONTEXT MODIFICATION RESPONSE message.
  • the first network node includes: a radio resource control RRC protocol layer, a service data adaptation protocol SDAP protocol layer, and a packet data convergence layer protocol PDCP protocol layer;
  • the second network node includes: a radio link control RLC protocol layer, a media access control MAC protocol layer, and a physical PHY protocol layer; the first network node and the second network node are included in one base station.
  • 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 Any possible design of the functional modules of the described method.
  • the communication device can realize the above aspects or the functions executed by the first network node in each possible design, and the functions can be realized by executing corresponding software through hardware.
  • the hardware or software includes one or more modules with corresponding functions above.
  • the present application provides a communication device.
  • the communication device may be a second network node or a chip or a chip system in the second network node, and may also be used in the second network node to implement the second aspect or the second Any possible design of the functional modules of the described method.
  • the communication device can realize the above aspects or the functions executed by the second network node in each possible design, and the functions can be realized by executing corresponding software through hardware.
  • the hardware or software includes one or more modules with corresponding functions above.
  • the communication device may include: a transceiver module and a processing module.
  • a communication device including: a processor and a memory; the memory is used to store computer-executable instructions, and when the communication device is running, the processor executes the computer-executable instructions stored in the memory, so that the The communication device executes the communication method described in any one of the above first aspect to the fourth 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 fourth 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 is provided, and instructions are stored in the computer-readable storage medium.
  • the computer-readable storage medium When the computer-readable storage medium is run on a computer, the computer can execute any one of the above-mentioned first to fourth aspects. the communication method described above.
  • a computer program product including instructions, which, when run on a computer, enable the computer to execute the communication method described in any one of the first aspect to the fourth aspect.
  • a radio access network device may be a gNB base station, and the radio access network device includes at least one of the following: performing any of the above-mentioned first and third aspects A first network node for a communication method, and a second network node for executing the communication method described in any one of the second and fourth aspects above.
  • the technical effect brought by any design method in the fifth aspect to the eleventh aspect can refer to the technical effect brought by different design methods in the first aspect to the fourth aspect, and will not be repeated here.
  • 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 5G communication system provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a gNB architecture with CU-DU separation provided in an embodiment of the present application.
  • Figure 7(a) is a schematic diagram of a communication system under the CU-DU separation architecture applicable to L2 U2N Relay provided by the embodiment of the present application;
  • FIG. 7(b) is a schematic diagram of the control plane protocol stack architecture when the adaptation layer is set in the DU provided by the embodiment of the present application;
  • FIG. 7(c) is a schematic diagram of the user plane protocol stack architecture when the adaptation layer is set in the DU provided by the embodiment of the present application;
  • FIG. 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a communication method provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of another communication method provided by the embodiment of the present application.
  • FIG. 11 is a schematic diagram of another communication method provided by the embodiment of the present application.
  • FIG. 12 is a schematic diagram of another communication method provided by the embodiment of the present application.
  • FIG. 13 is a schematic diagram of another communication method 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.
  • UEs can communicate with each other through a wireless network, and data signals between UEs are relayed through access network equipment.
  • the cellular network centered on traditional access network equipment (such as traditional base stations) has certain limitations in terms of data transmission quality and service scope.
  • Proximity Service (ProSe) communication emerges as the times require, and UEs can also communicate directly without access network equipment. This method can effectively reduce the communication time between UEs. delay.
  • 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.
  • FIG. 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 perform data communication based on the negotiated identity, and the data can be encrypted or unencrypted.
  • the unicast communication can only be performed between two UEs that have established a unicast connection.
  • a UE In unicast communication, when a UE sends data, it can send a source ID and a destination ID along with the data, where the source ID can be the ID assigned by the sending UE itself for the unicast connection, and the destination ID can be the peer receiving UE The ID assigned for this unicast connection.
  • the embodiment of the present application relates to a unicast communication process.
  • a unicast communication on the side link corresponds to a pair: source L2 ID (Source Layer-2 Identifier, layer 2 identifier source) and destination layer 2 identifier (Destination Layer-2 Identifier, L2ID).
  • the source L2 ID and destination L2 ID can be included in the subheader of each sidelink Media Access Control Protocol Data Unit (MAC PDU), so that the data can be transmitted to the correct receiving end.
  • 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. It is generally a service provided by layer 2 for transmitting user data between the UE and the base station.
  • the radio bearer includes PDCP protocol entities, RLC protocol entities, MAC A series of resources allocated by the protocol entity and PHY, etc.
  • the radio bearer is divided into a data radio bearer (Data Radio Bearer, DRB) and a signaling radio bearer (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.
  • RLC bearer can refer to protocol entities and configurations at and below the RLC layer, 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).
  • a relay UE is proposed to assist the communication between a remote UE (Remote UE) and a network device.
  • Figure 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 establish a communication connection with the base station through the relay UE.
  • 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).
  • Layer-2 Layer-2
  • Layer-3 Layer-3
  • FIG. 3 taking L2Relay as an example, the user plane protocol stack of the communication network shown in FIG. 2 is introduced.
  • Figure 3 shows the user plane protocol stack of a communication system including a remote UE, a relay UE, a base station gNB, and a 5G Core Network (5G Core Network, 5GC) device, wherein the protocol stack of the remote UE is from top to bottom It includes the protocol (internet protocol, IP) layer for interconnection between networks, the service data adaptation protocol (service data adaptation protocol, SDAP) (or Uu-SDAP) layer for peer-to-peer communication with gNB through the Uu interface, and the communication with gNB through the Uu interface.
  • IP internet protocol
  • SDAP service data adaptation protocol
  • Uu-SDAP Uu-SDAP
  • Packet data convergence protocol (PDCP) (or Uu-PDCP) layer of gNB peer-to-peer communication, adaptation layer (Adaptation layer, ADAPT), wireless link for peer-to-peer communication with relay UE through PC5 interface
  • the radio link control (RLC) or PC5-RLC) layer
  • the media access control media access control, MAC
  • PC5-MAC layer for peer-to-peer communication with the relay UE through the PC5 interface
  • a physical (physical, PHY) layer (or PC5-PHY layer) in which the relay UE performs peer-to-peer communication.
  • the protocol stack of the relay UE communicating with the remote UE includes an adaptation layer, a PC5-RLC layer, a PC5-MAC layer and a PC5-PHY layer from top to bottom.
  • the protocol stack for communicating with gNB in relay UE includes ADAPT layer, Uu-RLC layer, Uu-MAC layer and Uu-PHY layer from top to bottom.
  • the protocol stack in the gNB for communicating with the remote UE includes the Uu-SDAP layer and the Uu-PDCP layer from top to bottom.
  • the protocol stack in the gNB that communicates with the relay UE includes the ADAPT layer, Uu-RLC layer, Uu-MAC layer and Uu-PHY layer from top to bottom.
  • 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 a non-access stratum (non-access stratum, NAS) for peer-to-peer communication with 5GC, an RRC layer (or Uu-RRC layer) for peer-to-peer communication with gNB through the Uu interface, PDCP layer (or Uu-PDCP layer), ADAPT layer for peer-to-peer communication with gNB through Uu port, RLC layer (or PC5-RLC layer) for peer-to-peer communication with relay UE through PC5 port, peer-to-peer relay UE through PC5 port Communication MAC layer (or PC5-MAC layer) and PHY layer (or PC5-PHY layer).
  • NAS non-access stratum
  • RRC layer or Uu-RRC layer
  • PDCP layer or Uu-PDCP layer
  • ADAPT layer for
  • the protocol stack for communicating with the remote UE includes ADAPT layer, PC5-RLC layer, PC5-MAC layer and PC5-PHY layer from top to bottom.
  • the protocol stack communicating with gNB includes ADAPT layer, Uu-RLC layer, Uu-MAC layer and Uu-PHY layer from top to bottom.
  • the protocol stack in the gNB for communicating with the remote UE includes the Uu-RRC layer and the Uu-PDCP layer from top to bottom.
  • the protocol stack in the gNB that communicates with the relay UE includes the ADAPT layer, Uu-RLC layer, Uu-MAC layer and Uu-PHY layer from top to bottom.
  • 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 in the 5GC device includes the NAS layer.
  • the protocol stack that communicates 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 end-to-end RLC, MAC and PHY layers.
  • PDCP Packet Data Convergence Protocol
  • the adaptation layer 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 adaptation layer of the gNB can multiplex the data on multiple bearers of one or more Remote UEs to one Uu RLC bearer, that is, one RLC bearer on the Uu link may carry one or more Remote UEs. Data on multiple bearers of the UE. On the Sidelink of each Remote UE, the data on one or more bearers of the Remote UE can be mapped to a PC5 RLC bearer. Similar to the uplink direction, the adaptation layer of the Remote UE can map data on multiple bearers of the Remote UE to a PC5 RLC bearer. The adaptation layer of the Relay UE can multiplex the data on different RLC bearers of one or more Remote UEs to the RLC bearer of a Uu link, thereby realizing bearer multiplexing.
  • 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 5G communication system, in which the Next Generation Radio Access Network (NG-RAN) consists of one or more base stations gNB connected to the 5G core network 5GC constitute.
  • the gNB and 5GC are connected by an NG interface, and the gNBs are connected by an Xn interface.
  • the CU-DU separation architecture is to divide a gNB into a centralized unit (Central unit, CU) and one or more distributed units (Distributed Unit, DU).
  • the gNB-CU and gNB-DU are connected through the F1 interface.
  • one gNB-DU can only be connected to one gNB-CU.
  • gNB-CU can be responsible for RRC, SDAP and PDCP protocol layers, that is to say, gNB-CU has the functions of RRC, SDAP and PDCP protocol layers, and gNB-DU can be responsible for RLC, MAC and PHY protocol layers , that is to say, gNB-DU has the functions of RLC, MAC and PHY protocol layers.
  • Figure 6 is a schematic diagram of a gNB architecture with CU-DU separation, where the gNB-CU is further divided into a user plane (user plane, UP) and a control plane (control plane, CP), That is, gNB-CU can be divided into two parts including gNB-CU-CP and gNB-CU-UP.
  • user plane user plane
  • control plane control plane
  • gNB-CU-CP and gNB-CU-UP are connected through E1 interface; gNB-CU-CP is connected with AMF through NG control plane (NG-C) interface, and gNB-CU-CP is connected through Xn control plane (Xn-C) interface To connect with other gNBs, gNB-CU-CP is connected to gNB-DU through the F1 control plane (F1-C) interface; gNB-CU-UP is connected to gNB-DU through the F1 user plane (F1-U) interface.
  • F1-C F1 control plane
  • F1-U F1 user plane
  • one gNB-CU-UP can only be connected to one gNB-CU-CP, one gNB-DU can be connected to multiple gNB-CU-UP managed by one gNB-CU-CP, one gNB-CU-UP can be connected to Multiple gNB-DUs managed by one gNB-CU-CP.
  • gNB-CU-CP is responsible for the PDCP entity (or PDCP-C) corresponding to RRC and SRB, that is, gNB-CU-CP has the function of the RRC protocol layer entity and the function of the PDCP entity (PDCP-C) corresponding to the SRB;
  • gNB-CU-UP is responsible for the SDAP and the PDCP entity (or PDCP-U) corresponding to the DRB , that is to say, the gNB-CU-UP has the function of the SDAP protocol layer and the function of the PDCP entity (PDCP-U) corresponding to the DRB.
  • the Uu interface adaptation layer suitable for L2 U2N Relay communication is not configured in the gNB CU or gNB DU, which makes the existing F1 interface process unable to support L2 U2N Relay communication.
  • the UE in the background technology communicates directly with the gNB-DU according to the configuration of the Uu port, while in the L2 U2N Relay architecture, a Uu adaptation layer is newly added between the base station and the Relay UE, and the base station needs to communicate with the Remote UE and the Relay UE Configure to support the Remote UE to communicate with the base station through the Relay UE's relay. Therefore, the existing F1 interface process is no longer applicable to the L2 U2N relay.
  • the embodiment of the present application relates to how to solve the problem that the existing CU-DU separation architecture and the F1 interface process are not applicable to the L2 U2N Relay.
  • L2 U2N relay is applied to CU-DU architecture, one or more of the following problems need to be solved:
  • Inter-gNB-DU inter-DU handover
  • 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-b, a-c, b-c, or a-b-c, where 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 number 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. Rather, 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 node involved in the embodiment of the present application is a radio access network (radio access network, RAN) device in a wireless communication network or a component of an access network device.
  • the first network node involved in the embodiment may be is a CU in the gNB, and the second network node may be a DU in the gNB.
  • 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
  • Figure 7(a) is a schematic diagram of a communication system of L2 U2N Relay applicable to the embodiment of the present application under the CU-DU separation architecture, wherein the gNB base station consists of the first network node CU and the second network node DU Composed of two parts, the first network node CU and the second network node DU communicate through the F1 interface, and the Relay UE and the DU of the base station communicate through the Uu interface.
  • Remote UE and Relay UE communicate through sidelink, and the interface between Remote UE and Relay UE is PC5 port.
  • the Relay UE may be located within the cell coverage of the gNB.
  • the Remote UE may be located within the coverage area of the gNB cell, or may move outside the coverage area of the gNB cell.
  • the data of the Remote UE can be relayed and forwarded through the Relay UE to realize the remote UE and
  • the base station performs interaction between the user plane and the signaling plane.
  • Figure 7(b) shows a schematic diagram of the control plane protocol stack architecture where the adaptation layer is set in the DU, where the CU has an RRC layer and a PDCP layer, and the DU has an adaptation layer ADAPT, an RLC layer, a MAC layer, and a PHY layer, where, Schematically, two RRC+PDCP entities are configured in the CU, corresponding to different SRBs.
  • Figure 7(c) shows a schematic diagram of the user plane protocol stack architecture where the adaptation layer is set in the DU, where the CU has an SDAP layer and a PDCP layer, and the DU has an adaptation layer ADAPT, an RLC layer, a MAC layer, and a PHY layer, where, Schematically, two SDAP+PDCP entities are configured in the CU, corresponding to unused DRBs.
  • FIG. 8 is a schematic structural diagram of a communication device 80 provided in the embodiment of the present application.
  • the communication device 80 may be a first network node or a chip or a chip system in the first network node; when the communication device 80 has the function of the second network node described in the embodiment of this application, the communication device 80 may be a second network node A chip or system-on-a-chip in a node or a second network node.
  • the first network node or an implementation manner of the first network node is not limited to the communication device 80, and may also be a first network node or a logical network entity having a function of the first network node.
  • the communication device 80 may include a processor 801 , a communication line 802 and a communication interface 803 .
  • the communication device 80 may further include a memory 804 .
  • the processor 801 , the memory 804 and the communication interface 803 may be connected through a communication line 802 .
  • the processor 801 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 801 may also be other devices with processing functions, such as circuits, devices, or software modules.
  • the communication line 802 is used to transmit information between the components included in the communication device 80 .
  • the communication interface 803 is used for communicating with other devices or other communication networks.
  • the other communication network may be an Ethernet, a radio access network (radio access network, RAN), a wireless local area network (wireless local area networks, WLAN), and the like.
  • the communication interface 803 may be a radio frequency module or any device capable of realizing communication. This embodiment of the present application is described only by taking the communication interface 803 as an example of a radio frequency module, where the radio frequency module may include an antenna, a radio frequency circuit, etc., and the radio frequency circuit may include a radio frequency integrated chip, a power amplifier, and the like.
  • the memory 804 is used for storing instructions.
  • the instruction may be a computer program.
  • the memory 804 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 804 may exist independently of the processor 801 or may be integrated with the processor 801 .
  • the memory 804 can be used to store instructions or program codes or some data, etc.
  • the memory 804 may be located in the communication device 80 or outside the communication device 80, without limitation.
  • the processor 801 is configured to execute instructions stored in the memory 804, so as to implement the communication method provided by the following embodiments of the present application.
  • the processor 801 may also perform processing-related functions in the communication method provided in the following embodiments of the present application, and the communication interface 803 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 801 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 8 .
  • the communication device 80 may include multiple processors, for example, in addition to the processor 801 in FIG. 8 , it may further include a processor 807 .
  • the communication apparatus 80 may further include an output device 806 and an input device 807 .
  • the input device 807 is a device such as a keyboard, a mouse, a microphone, or a joystick
  • the output device 806 is a device such as a display screen and a speaker (speaker).
  • composition structure shown in FIG. 8 does not constitute a limitation to the communication device. Except for the components shown in FIG. 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 nodes in the following embodiments may have components or structures as shown in FIG. 8 .
  • 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.
  • the new F1 interface signaling process that supports Remote UE communication can enable L2 U2N Relay communication under the CU-DU architecture.
  • the adaptation layer can be configured in the CU or in the DU.
  • the following embodiments take the configuration of the adaptation layer in the DU as an example to provide the initial access process of the Remote UE under the CU-DU separation architecture, Inter-DU switching process and UE context release process.
  • FIG. 9 is a communication method provided by an embodiment of the present application.
  • the method involves a first network node (for example, CU) and a second network node (for example, DU), the method may comprise the steps of:
  • S901 The first network node sends first information to the second network node.
  • the first information is used to trigger the second network node to allocate a local identifier for the remote terminal device. It can be understood that S901 is an optional step.
  • the first network node or the second network node communicates with the remote terminal device through a relay terminal device.
  • the second network node sends second information to the first network node, where the second information includes the local identifier allocated by the second network node to the remote terminal device.
  • S903 The second network node sends third information to the first network node.
  • the third information includes the identification information of the remote terminal device on the first interface assigned by the second network node to the remote terminal device, or the third information includes The identification information of the remote terminal equipment on the first interface allocated by the remote terminal equipment and the identification information of the relay terminal equipment on the first interface allocated by the second network node to the relay terminal equipment information; wherein, the first interface is a communication interface between the first network node and the second network node.
  • S904 The first network node sends fourth information to the second network node. It can be understood that S904 is an optional step.
  • S905 The second network node sends fifth information to the first network node.
  • Optional operation one including:
  • the first network node sends fourth information to the second network node, where the fourth information includes the data radio bearer identifier DRB ID information of the remote terminal device and the identification information of the first radio link control RLC bearer, the remote terminal equipment There is a corresponding relationship between the DRB ID information of the terminal device and the identification information carried by the first RLC; the first network node receives fifth information sent by the second network node, and the fifth information includes the first Configuration information of the first RLC bearer generated by a network node; wherein, the first RLC bearer is a bearer between the remote terminal device and the relay terminal device, and the DRB of the remote terminal device There is a corresponding relationship between the ID information and the identification information carried by the first RLC.
  • Optional operation two including:
  • the first network node receives the fifth information generated by the second network node, where the fifth information includes: the data radio bearer identifier DRB ID information of the remote terminal device, the identification information of the first RLC bearer, and the first Configuration information of the RLC bearer, wherein the first RLC bearer is a bearer between the remote terminal device and the relay terminal device, and the DRB ID information of the remote terminal device and the first RLC bearer There is a corresponding relationship between the identification information of .
  • Optional operation three including:
  • the first network node sends fourth information to the second network node, where the fourth information includes the data radio bearer identifier DRB ID information of the remote terminal device, the local identifier of the remote terminal device, and Identification information carried by the second RLC; the first network node receives fifth information generated by the second network node, where the fifth information includes configuration information carried by the second RLC; wherein the second RLC
  • the bearer is the bearer between the second network node and the relay terminal device; the DRB ID information of the remote terminal device, the local identifier of the remote terminal device, and the identification information of the second RLC bearer There is a corresponding relationship between them.
  • Optional operation four including:
  • the first network node receives fifth information generated by the second network node, where the fifth information includes at least one of the following: DRB ID information of the remote terminal device, and the remote terminal The local identifier of the device, the identification information of the second RLC bearer, and the configuration information of the second RLC bearer; wherein, the second RLC bearer is a bearer between the second network node and the relay terminal device , there is a correspondence between the DRB ID information of the remote terminal device, the local identifier of the remote terminal device, and the identification information carried by the second RLC.
  • the method may also include a step: the first network node sends fourth information to the second network node, the fourth information includes the Identification information of the remote device.
  • the fourth information also includes identification information of the uplink transmission tunnel, and the identification information of the uplink transmission tunnel has a corresponding relationship with at least one of the following: the DRB ID information of the remote terminal device, the The local identifier of the remote terminal equipment, the identification information of the remote terminal equipment, and the identification information carried by the second RLC; wherein, the uplink transmission tunnel is used on the first interface, and the second A network node receives data from the second network node; and/or, the fifth information further includes identification information of a downlink transmission tunnel, and the identification information of the downlink transmission tunnel has a corresponding relationship with at least one of the following: the remote The DRB ID information of the end terminal device, the local identifier of the remote terminal device, the identification information of the remote terminal device, and the identification information carried by the second RLC; wherein, the downlink transmission tunnel is used in the On the first interface, the first network node sends data to the second network node.
  • the first network node may also receive first indication information from the relay terminal device, where the first indication information includes identification information of the remote terminal device, and the first indication information includes The indication information is used to request allocation of a local identifier for the remote terminal device, where the local identifier of the remote terminal device is used to uniquely identify the remote terminal device within the control range of the first network node, or, the The local identifier of the remote terminal device is used to uniquely identify the remote terminal device within the control range of the relay terminal device.
  • the fourth information further includes first identification information, where the first identification is used to indicate that the relay terminal device corresponds to the first RLC bearer.
  • the first identification information may be a layer 2 identification of the relay terminal, which is used to indicate that the first RLC bearer is an RLC bearer between the remote terminal and the relay terminal indicated by the layer 2 identification.
  • the indication information may be used to distinguish the relay terminal device corresponding to the first RLC bearer.
  • the first identity may also indicate the identity of the serving cell of the relay terminal, for example, in a scenario where multiple relay terminals must be in different serving cells.
  • the first identifier may also be the identifier information assigned by the first network node to the relay terminal. For example, in the case where the remote terminal is connected to three relay terminals, the first network node may assign 0, 1 and 2 are identified, and together with the identification information carried by the first RLC, the second network node is indicated through the fourth information.
  • the fifth information further includes first identification information, where the first identification is used to indicate that the relay terminal device corresponds to the first RLC bearer.
  • the first identification information may be a layer 2 identification of the relay terminal, which is used to indicate that the first RLC bearer is an RLC bearer between the remote terminal and the relay terminal indicated by the layer 2 identification.
  • the indication information may be used to distinguish the relay terminal device corresponding to the first RLC bearer.
  • the first identity may also indicate the identity of the serving cell of the relay terminal, for example, in a scenario where multiple relay terminals must be in different serving cells.
  • the first identifier may also be the identifier information assigned by the second network node to the relay terminal. For example, in the case where the remote terminal is connected to three relay terminals, the second network node may assign 0, 1 and 2' are identified, and together with the identification information carried by the first RLC, the fifth information is used to indicate the first network node.
  • the first information may be the user equipment context modification request UE CONTEXT MODIFICATION REQUEST message of the relay terminal device, and the second information may be the user equipment context modification response of the relay terminal device UE CONTEXT MODIFICATION RESPONSE message; or, the first information may be the UE CONTEXT SETUP REQUEST message of the user equipment context modification request of the relay terminal device, and the second information may be the user equipment context modification of the relay terminal device Responding to a UE CONTEXT SETUP RESPONSE message; or, the fourth information may be a user equipment context establishment request UE CONTEXT SETUP REQUEST message of the remote terminal device, and the fifth information may be the user equipment context of the remote terminal device Create a response UE CONTEXT SETUP RESPONSE message; or, the third information may be an Initial UL RRC Message Transfer message for the initial uplink RRC message transfer of the remote terminal device.
  • the first network node may include: a radio resource control RRC protocol layer, a service data adaptation protocol SDAP protocol layer, and a packet data convergence layer protocol PDCP protocol layer;
  • the second network node may include: a wireless Link control RLC protocol layer, media access control MAC protocol layer, and physical PHY protocol layer.
  • the first network node and the second network node may be included in one base station.
  • the second network node is the target node in the handover process
  • the third network node is the The source node in the handover process
  • the first network node controls the second network node and the third network node
  • the third network node includes: a radio link control RLC protocol layer, a medium access control MAC protocol layer , and a physical PHY protocol layer, the first network node, the second network node, and the third network node are included in a base station.
  • the first information is a user equipment context establishment request UE CONTEXT SETUP REQUEST message of the remote terminal device
  • the second information is a user equipment context establishment response UE CONTEXT SETUP RESPONSE message
  • the fourth information is a user equipment context establishment request UE CONTEXT SETUP REQUEST message of the remote terminal device
  • the fifth information is a user equipment context establishment response UE CONTEXT SETUP RESPONSE message.
  • another communication method provided by the embodiment of the present application involves a first network node (for example, CU) and a second network node (for example, DU).
  • the method may include the following step:
  • S901' The first network node sends sixth information to the second network node.
  • the sixth information includes second indication information, and the second indication information instructs the second network node to establish a second radio link control RLC bearer between the second network node and the relay terminal device,
  • the second RLC bearer is used to bear first data, and the first data is data exchanged between the remote terminal device and the second network node or the first network node.
  • the second RLC bearer may also be called an RLC channel.
  • the second indication information includes information of a signaling radio bearer (SRB) that needs to be established for the remote device; or, the second indication information includes relay service authorization information of the relay terminal device.
  • SRB signaling radio bearer
  • the first data is data carried by the signaling radio bearer SRB0, signaling radio bearer SRB1, or signaling radio bearer SRB2 of the remote terminal device. It should be noted that the data carried by the signaling radio bearer SRB0, signaling radio bearer SRB1 or signaling radio bearer SRB2 of the remote terminal device can be multiplexed on the same Uu RLC bearer.
  • S902' The second network node sends seventh information to the first network node.
  • the sixth information is a user equipment context establishment request UE CONTEXT SETUP REQUEST message
  • the seventh information is a user equipment context establishment response UE CONTEXT SETUP RESPONSE message.
  • the above-mentioned first network node includes: a radio resource control RRC protocol layer, a service data adaptation protocol SDAP protocol layer, and a packet data convergence layer protocol PDCP protocol layer; and the above-mentioned second network node includes: a radio link control RLC A protocol layer, a medium access control MAC protocol layer, and a physical PHY protocol layer; the first network node and the second network node may be included in a radio access network device, such as a base station gNB.
  • a radio access network device such as a base station gNB.
  • the embodiment of the present application provides the UE initial access process of the Remote UE. Specifically, compared In the existing technology where the UE directly communicates with the base station through the Uu link, before the Remote UE performs initial access, the Relay UE needs to do the following two preparations:
  • the RLC bearer used to carry the SRB signaling of the Remote UE is established between the Relay UE and the DU (that is, on the Uu link).
  • the RLC bearer between the Relay UE and the DU is collectively referred to as the Uu RLC bearer.
  • the base station assigns a local ID to the Remote UE and informs the Relay UE.
  • the Relay UE needs to add the local ID before forwarding, so that the base station can identify the Remote UE to which the received SRB0 signaling belongs.
  • the base station can pre-establish a Uu RLC bearer (or RLC channel) between the DU and the Relay UE during the initial context establishment process of the Relay UE, for carrying the SRB signaling of the Remote UE.
  • a Uu RLC bearer or RLC channel
  • FIG. 10 is a schematic diagram of another communication method provided by the embodiment of the present application. The method may include the following steps:
  • S1001 The CU sends a UE CONTEXT SETUP REQUEST message to the DU.
  • the UE CONTEXT SETUP REQUEST message is used to request the DU to establish a Uu RLC bearer, and the RLC bearer is used to bear the SRB0/1/2 signaling of the Remote UE.
  • the DU sends a UE CONTEXT SETUP RESPONSE message to the CU.
  • the UE CONTEXT SETUP RESPONSE message carries the configuration information of the Uu RLC bearer established by the DU.
  • the CU configures the correspondence between the Uu RLC bearer and the SRB0/1/2 of the Remote UE,
  • the CU instructs the DU to establish a Uu RLC bearer and at the same time instructs the DU Uu
  • the initial context establishment process of the Relay UE remains unchanged, and the base station can establish a Uu RLC bearer for carrying the SRB signaling of the Remote UE through the context update process, which can be initiated by the CU (such as step S1001a and S1002a); or, it may also be initiated by the DU (such as steps S1001b and S1002b).
  • the method may include:
  • the CU sends a UE CONTEXT MODIFICATION REQUEST message to the DU.
  • the UE CONTEXT MODIFICATION REQUEST message can be used to instruct the DU to establish a Uu RLC bearer for carrying the SRB0/1/2 of the Remote UE.
  • the DU sends a UE context modification response UE CONTEXT MODIFICATION RESPONSE message to the CU, and the UE CONTEXT MODIFICATION RESPONSE message carries the configuration information of the Uu RLC bearer generated by the DU.
  • the CU configures the correspondence between the Uu RLC bearer and the SRB0/1/2 of the Remote UE, and instructs the DU to establish the Uu RLC bearer.
  • the CU instructs the DU to establish a Uu RLC bearer, and at the same time instructs the DU to generate the correspondence between the Uu RLC bearer and the SRB0/1/2 of the Remote UE.
  • the method may include:
  • the DU sends a UE CONTEXT MODIFICATION REQUIRED message to the CU.
  • the configuration information of the Uu RLC bearer generated by the DU is sent to the CU.
  • the Uu RLC bearer configured by the DU can also indicate the correspondence between the Uu RLC bearer and the SRB0/1/2 of the Remote UE.
  • S1002b The CU sends a UE CONTEXT MODIFICATION CONFIRM message to the DU. Through the UE CONTEXT MODIFICATION CONFIRM message, the CU confirms to the DU the RLC bearer successfully established by the DU.
  • the user equipment context update process involved in the above S1001, S1002, S1001a, S1002a, S1001b, and S1002b may be initiated based on capability and authorization.
  • the authorization information of the Relay UE-related relay service can be carried.
  • the CU or DU can use the authorization The information triggers the context update process described above.
  • the Relay UE may notify the base station of the UE capability information of the Relay UE itself through the UECapabilityInformation message, if the UE capability information includes that the UE can support relay communication information, the base station can trigger the above context update process accordingly.
  • the above user equipment context update procedure may also be initiated when the first Remote UE accesses.
  • the Relay UE will send SUI information to the base station to inform the base station that there will be sidelink communication between the Remote UE and the Relay UE, and request the base station to allocate corresponding transmission resources.
  • the base station After receiving the SUI information, the base station triggers the context update process, and pre-establishes the Uu RLC bearer for the subsequent SRB signaling of the Remote UE.
  • FIG. 11 is a schematic diagram of another communication method provided by an embodiment of the present application. The method may include the following steps:
  • S1101 Establish a unicast connection between the Remote UE and the Relay UE.
  • the Relay UE sends a SUI message to the DU.
  • the Relay UE is triggered to send sidelink UEInformation (SUI) to the base station (via gNB-DU), and the SUI message can be used to request for the The Remote UE assigns a local ID.
  • SAI sidelink UEInformation
  • Optional operation S1101a After the Remote UE sends SRB0 signaling (for example, MSG3 message or RRCSetupRequest message) to the Relay UE, it triggers the Relay UE to send a SUI message to the base station.
  • SRB0 signaling for example, MSG3 message or RRCSetupRequest message
  • the DU sends an uplink RRC message to the CU to transfer a UL RRC MESSAGE TRANSFER message.
  • the UL RRC MESSAGE TRANSFER message includes the above SUI message sent by the Relay UE to the gNB-DU, that is, the DU transparently transmits the SUI message to the CU, and the SUI message can be parsed at the RRC layer of the CU.
  • UEs that establish a unicast connection with a Relay UE and attempt sidelink communication: Remote UEs that obtain relay services from the Relay UE, and UEs that communicate directly with the Relay UE through sidelinks.
  • the Relay UE When a UE accesses the Relay UE and tries to communicate with the Relay UE through the sidelink, the Relay UE can be triggered to send a SUI message to the base station, through which the SUI message indicates the Destination L2 ID of the Remote UE, and requests the sidelink to transmit resources, such as The Destination L2 ID of the Remote UE can be carried in the SUI message, and the base station can allocate sidelink transmission resources for the Remote UE after receiving the Destination L2 ID of the Remote UE.
  • the base station also needs to assign a local ID to the Remote UE. Therefore, the base station needs to be able to distinguish whether the Destination L2 ID reported in the SUI is a Remote UE. Specifically, the following optional methods can be included:
  • the base station can determine the need to allocate a local ID for the Remote UE through the newly defined uplink RRC message.
  • a new IE is introduced to indicate the L2 ID of the Remote UE, so that the base station determines that a local ID needs to be allocated to the Remote UE according to the indicated L2 ID of the Remote UE.
  • S1104 The CU sends a UE CONTEXT MODIFICATION REQUEST message to the DU.
  • the DU Through the UE CONTEXT MODIFICATION REQUEST message, instruct the DU to allocate a local ID for the Remote UE, for example, directly forward the SUI message to the DU, or define special instruction information, and carry it in the UE CONTEXT MODIFICATION REQUEST message.
  • the CU can also carry the local ID of the Remote UE allocated by itself in the UE CONTEXT MODIFICATION REQUEST message and send it to the DU.
  • what the gNB-CU receives from the SUI message may be the L2 ID of the Remote UE, so the base station can generate the corresponding local ID of the Remote UE for each L2 ID of the Remote UE, and the base station can maintain the remote UE's local ID at the same time. Correspondence between the L2 ID and the local ID of the Remote UE.
  • the SUI message sent by the Relay UE can carry the system architecture evolution temporary mobile station identifier (S-TMSI) of the Remote UE, and the Relay UE can transmit
  • S-TMSI system architecture evolution temporary mobile station identifier
  • the Relay UE can transmit
  • the S-TMSI is obtained from the Remote UE during the connection establishment process, so that the base station can allocate a corresponding local ID for each S-TMSI, and maintain the correspondence between the S-TMSI and the local ID.
  • S1105 The DU sends a UE CONTEXT MODIFICATION RESPONSE message to the CU.
  • the DU sends the allocated Remote UE local ID to the CU. Or, for the case where the CU sends the local ID of the Remote UE assigned by the CU to the DU in the UE CONTEXT MODIFICATION REQUEST message, the DU can confirm the local ID of the Remote UE sent by the CU to the DU through the UE CONTEXT MODIFICATION RESPONSE message.
  • S1106 The CU sends a downlink RRC transfer DL RRC TRANSFER message to the DU, which carries the local ID of the Remote UE.
  • the CU can carry the local ID of the allocated Remote UE in the RRC message, such as the RRC reconfiguration RRCReconfiguration message, and send it to the DU through the DL RRC TRANSFER message, and the DL RRC TRANSFER message can carry the RRCReconfiguration message.
  • the DU sends the RRC reconfiguration RRCReconfiguration message generated by the CU to the Relay UE, and the RRCReconfiguration message carries the local ID allocated for the Remote UE.
  • Figure 12 is a schematic diagram of another communication method provided by the embodiment of the present application, and proposes a method for providing initial access for Remote UEs A method of communication, the method comprising:
  • the Remote UE sends an RRC setup request RRCSetupRequest message to the DU.
  • the Remote UE can send an RRCsetupRequest message to the DU through the relay function of the Relay UE, which is used to request the establishment of the RRC connection between the Remote UE and the gNB.
  • the Relay UE can add the local ID of the Remote UE to the packet header of the SRB0 data packet (such as the adaptation layer PDU) of the Remote UE.
  • the Relay UE can forward the SRBO data according to the Uu RLC bearer configuration configured in various configuration methods in the embodiment shown in FIG. 10 .
  • the DU sends an initial uplink RRC message to the CU to transfer an INITIAL UL RRC MESSAGE TRANSFER message.
  • the DU After the DU receives the SRB0 data packet of the Remote UE carrying the local ID of the Remote UE, the DU assigns the user equipment F1 interface UE F1AP ID to the Remote UE, and can associate the Remote UE local ID with the DU UE of the Remote UE F1AP ID. Then the DU sends an INITIAL UL RRC MESSAGE TRANSFER message to the CU, and the message carries the DU UE F1AP ID of the Remote UE allocated by the DU.
  • the CU needs to perceive which Relay UE the Remote UE is connected to, so the INITIAL UL RRC MESSAGE TRANSFER message can carry the DU UE F1AP ID of the Relay UE allocated by the DU to the Relay UE.
  • INITIAL UL RRC MESSAGE TRANSFER can carry the local ID of the Remote UE, then the CU can also determine the Remote UE according to the local ID Which Relay UE to connect with.
  • S1203 The CU sends a downlink RRC message to the DU to transfer a DL RRC MESSAGE TRANSFER message.
  • the CU allocates the CU side UE F1AP ID of the Remote UE on the F1 port for the Remote UE, and generates an RRC setup RRCSetup message sent to the Remote UE, and sends the RRCSetup message to the DU in a DL RRC MESSAGE TRANSFER message.
  • the DU sends an RRC Setup message to the Remote UE.
  • the DU can send the RRCSetup message to the Remote UE through the relay function of the Relay UE.
  • the adaptation layer carries the local ID of the Remote UE on the adaptation layer header when constructing the adaptation layer PDU.
  • S1205 The Remote UE sends an RRC Setup Complete RRCSetupComplete message to the DU.
  • the Remote UE can send the RRCSetupComplete message to the DU through the relay function of the Relay UE.
  • the DU sends an uplink RRC message to the CU to transfer a UL RRC MESSAGE TRANSFER message.
  • the DU can carry the RRCSetupComplete message through the UL RRC MESSAGE TRANSFER message, and forward the RRCSetupComplete message sent by the Remote UE to the CU.
  • S1207 The CU sends a UE CONTEXT SETUP REQUEST message to the DU.
  • the CU sends the UE CONTEXT SETUP REQUEST of the Remote UE to the DU, which can be used to instruct the DU to establish the UE context of the Remote UE.
  • S1208&S1210 The Relay UE and the DU exchange security command mode (SecurityModeCommand, SMC) messages. Wherein, the process of exchanging SMC messages between the Relay UE and the DU can be used to activate the security mode on the access stratum (AS) side.
  • AS access stratum
  • the DU returns a UE CONTEXT SETUP RESPONSE message to the CU, which is used to indicate that the UE context of the Remote UE is successfully established in the DU.
  • gNB configures the context content of the Remote UE, such as cell configuration and ID information of the Remote UE, bearer configuration information of the SRB/DRB of the Remote UE, and gNB sends an RRC message to the Remote UE (such as the SMC message of S1208), etc.
  • the gNB can also configure the adaptation layer configuration information of the Relay UE and the Remote UE respectively.
  • the adaptation layer configuration information of Relay UE and Remote UE can be configured by gNB-DU or gNB-CU, and the different optional configuration methods are described below.
  • the adaptation layer configuration of the Remote UE is determined by the CU
  • the configuration content of the Remote UE adaptation layer may include: the DRB ID information of the Remote UE and the PC5 RLC bearer information, and there is a mapping relationship between the DRB ID information of the Remote UE and the PC5 RLC bearer information.
  • the CU configures the above information of the adaptation layer, it can send the above configuration content of the Remote UE adaptation layer to the DU through the UE CONTEXT SETUP REQUEST message in step S1207. Further, the DU can establish the configuration of the corresponding PC5 RLC bearer according to the instruction of the CU, and send the configuration information of the PC5 RLC bearer to the CU through the UE CONTEXT SETUP RESPONSE message in step 1209.
  • the configuration content of the Remote UE adaptation layer may also include the identification information of the relay UE, which is used to indicate that the PC5 RLC bearer is a PC5 RLC bearer between the remote UE and the indicated relay UE.
  • the identity information of the relay UE may be the layer 2 identity of the relay UE, or the identity information allocated by the CU for the relay UE, or the identity of the serving cell of the relay UE.
  • the adaptation layer configuration of the Remote UE is determined by the DU
  • the CU may instruct the DU to configure the configuration information of the adaptation layer for the Remote UE through the UE CONTEXT SETUP REQUEST message in step S1207. Then, the DU sends the configuration content of the adaptation layer of the Remote UE configured by itself and the configuration information of the corresponding PC5 RLC bearer to the CU through the UE CONTEXT SETUP REPONSE message.
  • the configuration content of the Remote UE adaptation layer may include: the DRB ID information of the Remote UE and the PC5 RLC bearer information, and there is a mapping relationship between the DRB ID information of the Remote UE and the PC5 RLC bearer information.
  • the CU does not need to carry additional indication information in the UE CONTEXT SETUP REQUEST message in step S1207, because the DU can know that this is a Remtoe UE according to the uploaded RRC message, so it can determine through its own internal implementation
  • the configuration content of the adaptation layer of the Remote UE and the configuration information of the corresponding PC5 RLC bearer is not required.
  • the configuration content of the Remote UE adaptation layer may also include the identification information of the relay UE, which is used to indicate that the PC5 RLC bearer is a PC5 RLC bearer between the remote UE and the indicated relay UE.
  • the identity information of the relay UE may be the layer 2 identity of the relay UE, or the identity information allocated by the CU for the relay UE, or the identity of the serving cell of the relay UE.
  • the adaptation layer configuration of the Relay UE is determined by the CU
  • the CU can determine to create a new Uu RLC bearer of the Relay UE or reuse the existing Uu RLC bearer of the Relay UE to bear the data of the Remote UE.
  • the Uu RLC bearer referred to herein may refer to the RLC bearer on the Uu link between the DU and the Relay UE.
  • the UE CONTEXT SETUP REQUEST message sent by the CU to the DU may carry the ID information of the requested new or modified Uu RLC bearer, and may also carry the Remote UE DRB ID information corresponding to the Uu RLC bearer, and may also carry the Uu RLC bearer ID information.
  • QoS requirements The adaptation layer of the Relay UE needs to configure the mapping relationship between the Uu RLC bearer and the DRB ID of the Remote UE, and the QoS requirement information of the RLC bearer can be used as a reference for DU generation and RLC bearer configuration.
  • the UE CONTEXT SETUP REQUEST message can also include uplink tunnel information.
  • the uplink tunnel is the tunnel required for the DU to send data to the CU.
  • Each tunnel corresponds to a Remote UE DRB ID, and a tunnel address can be assigned to each uplink tunnel. to identify the uplink tunnel.
  • the uplink data is submitted from the adaptation layer to the tunnel on the F1 interface (for example, F1-U GTP tunnel), and the adaptation layer needs to submit the data multiplexed on the Uu RLC bearer to the corresponding Tunnel, so the CU also needs to configure the Remote UE ID, DRB ID and tunnel address and the mapping relationship between the three, and notify the Remote UE ID, DRB ID and tunnel address (including the mapping relationship between the three) to Du.
  • the DU After the DU receives the content of the CU configuration (Remote UE ID, DRB ID and tunnel address), it can generate the configuration information of the Uu RLC bearer that needs to be newly created or modified according to the instructions of the CU, and pass the UE CONTEXT SETUP RESPONSE message in step S1209 Carry the configuration information of the Uu RLC bearer that needs to be created or modified, and send it to the CU.
  • the configuration information of the Uu RLC bearer can be sent in the form of a separate RRC container (container) in the UE CONTEXT SETUP RESPONSE message.
  • the UE CONTEXT SETUP RESPONSE message can also include the configuration information of the downlink tunnel (that is, the CU sends to the DU direction), each downlink tunnel can correspond to a DRB ID of the Remote UE, and a tunnel address can also be assigned to each downlink tunnel , used to identify the downlink tunnel.
  • each tunnel may correspond to one adaptation layer or one Uu RLC bearer, or therefore, corresponding to different DRB IDs of Remote UEs, the same tunnel address may be allocated. All tunnels are assigned an address, or an address is assigned according to the granularity carried by Uu RLC. That is, the tunnels corresponding to the multiplexed DRBs on the Uu RLC bearer are assigned the same address.
  • the adaptation layer configuration of the Relay UE is determined by the DU
  • the UE CONTEXT SETUP REQUEST message sent by the CU to the DU may be used to request the DU to configure the adaptation layer configuration of the Relay UE for the Remote UE.
  • the UE CONTEXT SETUP REQUEST message can carry the QoS information carried by the Remote UE and the uplink tunnel information.
  • the DU can decide whether to create a new Uu RLC bearer to carry the data of the Remote UE, and configure the Remote UE DRB ID corresponding to different Uu RLC bearers, as well as downlink tunnel information, Uu RLC bearer information, Remote UE DRB ID There is a corresponding relationship between the information and the downlink tunnel information, and the distribution method is the same as above.
  • the DU sends the above configuration to the CU through the UE CONTEXT SETUP RESPONSE message.
  • the configuration of the adaptation layer of the Remote UE and the Relay UE is generated during the context establishment of the Remote UE.
  • the Remote UE context establishment process only generates the configuration of the Remote UE's adaptation layer, while the Relay UE's adaptation layer configuration is generated through the UE context modification process of the Relay UE's UE context.
  • the adaptation layer configuration of the Relay UE can also be initiated by the DU or by the CU, similar to the above steps S1207 and S1209, the difference is that the signaling interaction between the DU and the CU is through the The F1 interface signaling associated with the Relay UE.
  • the following uses the CU as an example to configure the configuration information of the adaptation layer for illustration.
  • Step Sb1 CU sends UE CONTEXT MODIFICATION REQUEST message to DU.
  • the CU can decide to establish a new Uu RLC bearer for Remote UE data, so the CU sends a UE CONTEXT MODIFICATION REQUEST message to the DU, and indicates the ID of the newly created Uu RLC bearer through the information element in the message, and indicates each Uu RLC bears the corresponding Remote UE DRB ID information.
  • the UE CONTEXT MODIFICATION REQUEST message may include the DRB ID and the QoS information of the Uu RLC bearer to be newly created, and may also include uplink tunnel information.
  • Step Sb2 DU sends UE CONTEXT MODIFICATION RESPONSE message to CU.
  • the DU can determine the configuration information of the Uu RLC bearer according to the instruction of the CU, and send the configuration information of the Uu RLC bearer between the Relay UE and the DU to the CU through the UE CONTEXT MODIFICATION RESPONSE message.
  • the DU sends an uplink RRC message to the CU to transfer a UL RRC MESSAGE TRANSFER message.
  • the DU can carry the SMC message replied by the Relay UE through the UL RRC MESSAGE TRANSFER message, and forward the SMC message replied by the Relay UE to the CU.
  • S1212 The CU sends a downlink RRC message to the DU to transfer a DL RRC MESSAGE TRANSFER message.
  • the CU may generate an RRC reconfiguration RRCReconfiguration message, and the RRC reconfiguration RRCReconfiguration message includes the mapping relationship configuration information of the Remote UE.
  • the mapping relationship configuration information of the Remote UE may include one or more of the following information and the relationship between them The mapping relationship: Remote UE ID information, Remote DRB ID information, tunnel address information, Uu RLC bearer identification information, PC5 RLC bearer identification information, and the corresponding identification information of the relay terminal, and are sent to the DU through the DL RRC MESSAGE TRANSFER message.
  • the identifier corresponding to the relay terminal may include one or more of the following: the layer 2 identifier/C-RNTI/F1AP ID of the relay terminal, the temporary identifier assigned by the CU to the relay terminal device, and the serving cell where the relay terminal is located logo.
  • the DU sends the RRCReconfiguration message to the Remote UE.
  • the RRCReconfiguration message may include the mapping relationship between the Remote UE ID and the PC5 RLC bearer.
  • S1214 The Remote UE sends an RRCReconfigurationComplete message to the DU, indicating that the RRC connection configuration is completed.
  • the DU sends a UL RRC MESSAGE TRANSFER message to the CU, and the UL RRC MESSAGE TRANSFER message carries the RRCReconfigurationComplete message sent by the Remote UE to the DU, thereby forwarding the RRC message sent by the Remote UE to the CU.
  • the CU can also deliver the adaptation layer configuration to the Relay UE, including the following steps:
  • Step Sa1.CU sends DL RRC MESSAGE TRANSFER message to DU.
  • the CU can generate an RRCReconfiguration message, which contains the configuration information of the adaptation layer of the Relay UE, and sends it to the DU through the DL RRC MESSAGE TRANSFER message.
  • Step Sa2.DU sends the RRCReconfiguration message to the Relay UE.
  • the RRCReconfiguration message may include one or more of information such as local ID information of the Remote UE, DRB ID information of the Remote UE, Uu RLC bearer, PC5 RLC bearer, and identification information corresponding to the relay terminal, and the information between these information have a mapping relationship.
  • Step Sa3 The Remote UE sends a RRCReconfigurationComplete message to the DU, indicating that the RRC connection configuration is completed.
  • Step Sa4 The DU forwards the RRC message sent by the Relay UE to the CU through the UL RRC MESSAGE TRANSFER message.
  • step S1207 and step S1209 the gNB configures a new Uu RLC bearer for the data of the Remote UE or changes the original Uu RLC bearer, then the gNB-CU sends it to the Relay UE
  • the RRC message of the Uu RLC may carry the configuration information carried by the Uu RLC.
  • the embodiment of the present application introduces an adaptation layer in the gNB-DU to support the L2 U2N relay protocol architecture.
  • the Relay UE is also introduced to establish a Uu RLC bearer for the Remote UE SRB signaling, and the process of the base station assigning a local ID to the Remote UE, and DU or CU to determine the adaptation Layer configuration process.
  • the embodiment of the present application designs the initial access process of the Remote UE for the case where the adaptation layer is placed on the gNB-DU, so that the Remote UE can successfully access the base station and establish a UE context.
  • FIG. 12 is a schematic diagram of another communication method provided by the embodiment of the present application.
  • a The inter-DU switching process of the Remote UE is the Relay UE where the Remote UE is switched from the source DU (Source DU) to the target DU (Target DU), and the source DU and the target DU are under the control of the same CU.
  • the method shown in Figure 13 includes:
  • the Remote UE performs measurement reporting and sends a MeasurementReport message to the source DU.
  • the measurement report content includes the ID of the Relay UE and the Cell ID information.
  • the source DU sends a UL RRC MESSAGE TRANSFER message to the CU.
  • the source DU sends the MeasurementReport message to the CU through the F1 interface signaling UL RRC MESSAGE TRANSFER.
  • the CU can decide to switch the Remote UE to the Relay UE under the access target DU (Target DU) according to the measurement report content of the Remote UE.
  • the CU sends a UE CONTEXT SETUP REQUEST message to the target DU.
  • the CU instructs the target DU to establish the UE context of the Remote UE by sending the UE CONTEXT SETUP REQUEST to the target DU.
  • the target DU replies a UE CONTEXT SETUP RESPONSE message to the CU.
  • the UE CONTEXT SETUP RESPONSE message can be used to indicate that the UE context is successfully established in the gNB-DU.
  • the above steps S1303 and S1304 involve the F1 interface signaling related to the Remote UE. Therefore, during the signaling process of the gNB-CU and the gNB-DU, the gNB-CU and the gNB-DU will assign the CU F1AP ID to the Remote UE respectively. And the DU F1AP ID, and carry the assigned F1AP ID of the Remote UE in the signaling. At the same time, in this process, the DU or CU can also allocate the local ID of the Remote UE, and associate the local ID with the F1AP ID. If the local ID is allocated by the CU, the CU will send the local ID assigned by the CU to the DU through the UE CONETEXT SETUP REQUEST message in step S1303.
  • CU requests DU to allocate a local ID through UE CONETEXT SETUP REQUEST message in step S1303, and DU sends the allocated local ID to CU through UE CONETEXT SETUP RESPONSE message in step S1304; or, DU can be based on internal implementation , independently decide to allocate the local ID, and send the allocated local ID to the CU through the UE CONETEXT SETUP RESPONSE message in step S1304, that is, in the UE CONETEXT SETUP RESPONSE message in step S1304, there is no need to carry the local ID for requesting UD allocation instructions for the .
  • step S1303 and step S1304 the adaptation layer configuration of the Remote UE and the adaptation layer configuration of the Relay UE can also be generated, and there are two schemes of DU generation configuration and CU generation configuration.
  • the adaptation layer configuration of the Remote UE may be generated in steps S1303 and S1304, and the adaptation layer configuration of the Relay UE is generated through the UE Context Modification process of the Relay UE shown in step S1307-2, Similar to step Sb1 and step Sb2 in the embodiment shown in FIG. 12 , details are not repeated here.
  • the CU sends a UE CONTEXT MODIFICATION REQUEST message to the source DU, including the RRCReconfiguration message sent by the CU to the Remote UE.
  • the RRCReconfiguration message may also include Remote UE adaptation layer configuration information (such as the Remote UE's DRB ID information and PC5 RLC bearer information, and the mapping relationship between the two ) and the local ID assigned to the Remote UE.
  • the source DU replies a UE CONTEXT MODIFICATION RESPONSE message to the CU.
  • the source DU sends the RRCReconfiguration message generated by the CU to the Remote UE.
  • the CU and the target DU can generate the Uu RLC configuration of the Relay UE through the UE Context Modification process of the Relay UE, including: the adaptation layer configuration of the Relay UE (ie Remote UE local ID, DRB ID, Uu RCL and PC5 RLC bearer mapping relationship), and the required RLC bearer configuration.
  • the adaptation layer configuration of the Relay UE ie Remote UE local ID, DRB ID, Uu RCL and PC5 RLC bearer mapping relationship
  • the required RLC bearer configuration ie Remote UE local ID, DRB ID, Uu RCL and PC5 RLC bearer mapping relationship
  • S1308 The CU sends a DL RRC MESSAGE TRANSFER message to the target DU.
  • the CU generates the RRCReconfiguration message, carries the configuration information of the Relay UE, and sends it to the target DU through the DL RRC MESSAGE TRANSFER message.
  • the target DU sends the RRCReconfiguration message to the Relay UE.
  • the target DU forwards the RRC message of the Relay UE to the CU through the UL RRC MESSAGE TRANSFER message.
  • the Remote UE needs to establish a unicast connection with the Relay UE first, and the Relay UE matches the connected Remote UE with the configuration issued by the base station through the local ID.
  • the Remote UE forwards the RRCReconfigurationComplete message to the target DU through the Relay UE.
  • the Remote UE sends the RRCReconfigurationComplete message of the unicast connection through the Relay UE.
  • the Relay UE identifies the Remote UE, and adds a local ID to the adaptation layer PDU carrying the RRCReconfigurationComplete message during the forwarding process, so that the adaptation layer of the target DU can identify that the message belongs to the Remote UE and forward it correctly.
  • the target DU sends a UL RRC MESSAGE TRANSFER message to the CU.
  • the target DU carries the RRCReconfigurationComplete message of the Remote UE in the UL RRC MESSAGE TRANSFER message and sends it to the CU.
  • the inter-DU switching process of the Remote UE is proposed when the adaptation layer is placed on the DU under the CU-DU separation architecture, so as to enable the Remote UE to successfully access the Relay UE under the target DU.
  • the UE context of the Remote UE needs to be established, and related configuration of the Relay UE also needs to be performed.
  • the base station needs to allocate a local ID during the UE context establishment process, and associate the local ID with the F1AP ID of the Remote UE, so that in the subsequent process, it can identify which Remote UE forwards the RRC message through the Relay UE.
  • the embodiment of the present application also provides a communication method, wherein a UE context release process of the Remote UE is given.
  • a UE context release process of the Remote UE is given.
  • the base station needs to release the UE context of the Remote UE.
  • it may also need to update/release the UE context of the connected Relay UE, including:
  • Step 1 The CU sends the UE CONTEXT RELEASE COMMAND message to the DU, instructing the DU to release the UE context information of the Remote UE. At the same time, the message carries the RRCRelease message delivered to the UE.
  • Step 2 The DU sends the RRCRelease message generated by the CU to the Remote UE, instructing the Remote UE to release the RRC connection.
  • Step 3 The DU replies the UE CONTEXT RELEASE COMPLETE message to the CU to confirm that the UE context of the Remote UE is successfully released.
  • the UE context release or change of the Relay UE also needs to be considered.
  • the DU will further judge whether to release the Uu RLC bearer of the Relay UE or whether to release the Relay UE. For example, with the release of the Remote UE, the Uu RLC bearer does not need to carry data, and the corresponding Uu RLC bearer can be released; or after the release of the Remote UE, the Relay UE has no relay data or its own data, then the Relay UE can be carried out release.
  • Step 4a After the DU judges that the Uu RLC bearer can be released, it sends a UE CONTEXT MODIFICATION REQUIRED message to the CU, indicating the ID information of the released Uu RLC bearer.
  • Step 5a The CU replies the UE CONTEXT MODIFICATION CONFIRM message to the DU, carrying the generated RRCReconfiguration message, which contains the updated configuration information of the Relay UE.
  • Step 6a DU sends RRCReconfiguration message to Relay UE.
  • Step 4b After the DU judges that the Relay UE can be released, it sends a UE CONTEXT RELEASE REQUEST message to the CU, indicating to release the Relay UE.
  • Step 5b CU generates RRCRelease message of Relay UE, and sends it to DU through DL RRC MESSAGE TRANSFER message.
  • Step 6b The DU sends an RRCRelease message to the Relay UE, instructing the Relay UE to release the RRC connection with the base station.
  • the method provided by this embodiment needs to judge whether to update or release the context of the Relay UE after the context release of the Remote UE. After the DU is judged, the context update or release process of the Relay UE is carried out accordingly.
  • the embodiment of the present application also provides a communication method, in which the initial access procedure of the Remote UE is given under the condition that the Uu adaptation layer is placed in the CU. Similarly, when the Uu adaptation layer is placed on the CU, before starting the initial access process, it is necessary to: 1. Establish an RLC bearer for carrying the SRB signaling of the Remote UE between the Relay UE and the DU; The UE allocates a local ID and informs the Relay UE.
  • the method includes the following:
  • Step 1 The signaling interacted between the DU and the CU is the F1 interface signaling related to the Relay UE, that is, the signaling of the Remote UE is carried in the signaling of the Relay UE in the form of a container. Since there is no adaptation layer on the DU, the DU has no way to identify whether the data/signaling uploaded by the Relay UE is the data/signaling of the Remote UE. Only when the data/signaling is submitted to the adaptation layer of the CU, the base station can identify that the data/signaling belongs to the Remote UE according to the local ID on the header of the adaptation layer, and submit it to the upper protocol layer of the Remote UE.
  • Step 2 Generate the configuration of the adaptation layer by the CU.
  • the adaptation layer is located in the CU, so it is more natural for the CU to determine the mapping relationship configuration of the adaptation layer, and at the same time request the DU to establish the corresponding Uu RLC bearer.
  • Step 3 On the data plane, data of different bearers can be multiplexed on the F1 interface tunnel.
  • the F1 interface is connected to the adaptation layer of the CU and the RLC layer of the DU.
  • the data of different bearers is multiplexed on the adaptation layer.
  • the RLC layer In the uplink direction, the RLC layer directly submits the data multiplexed on the Uu RLC bearer to the adapter through a tunnel. With layers, the down direction is similar.
  • the above tunnel should be the F1-U GTP tunnel configured by the CU and DU for the Relay UE.
  • the CU configures the uplink tunnel, it needs to configure the mapping relationship between the adaptation layer entity and the tunnel address; when the DU configures the downlink tunnel, it should configure the corresponding relationship between the Uu RLC bearer ID and the tunnel address.
  • an adaptation layer is introduced in the CU unit to support the L2 U2N relay protocol architecture.
  • the signaling of the Remote UE is carried in the F1 interface signaling of the Relay UE, between the DU and the UE Interaction between CUs; 2.
  • the data of the Remote UE is exchanged between the DU and the CU through the F1 interface tunnel of the Relay UE. Only when the data or signaling is submitted to the adaptation layer of the CU can it be identified that the data or signaling belongs to the Remote UE.
  • data of one bearer corresponds to one F1 interface tunnel, and in this solution, data of different bearers can be multiplexed on one F1 interface tunnel.
  • the actions of the first network node CU or the second network node DU in the above method embodiment can be executed by the processor 801 in the communication device 80 shown in FIG. 8 calling the application code stored in the memory 802 to instruct the The first terminal device executes; this embodiment does not impose any limitation on this.
  • the methods and/or steps implemented by the first network node CU may also be implemented by components (such as chips or circuits) that can be used for the first network node CU;
  • the methods and/or steps implemented by the DU may also be implemented by components (such as chips or circuits) available to the second network node DU.
  • 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 CU in the above method embodiment, or a device including the first network node CU, or a component or computer program that can be used for the first network node CU; or, the communication device may be
  • the second network node DU in the above method embodiment is either an apparatus including the above second network node DU, or a component or computer program that can be used for the second network node DU.
  • the communication device includes hardware structures and/or software modules corresponding to each 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. Those skilled in the art 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 implemented in the form of hardware or in the form of software function modules. 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 transceiver module 1401 may also be referred to as a transceiver unit to implement a transceiver function, for example, it may be a transceiver 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 functions described above.
  • the communication device 140 can take the form of the communication device 80 shown in FIG. 8 .
  • the processor 801 in the communication device 80 shown in FIG. 8 may call the computer-executed instructions stored in the memory 803, so that the communication device 80 executes the communication method in the foregoing method embodiments.
  • the functions/implementation process of the transceiver module 1401 and the processing module 1402 in FIG. 14 can be implemented by the processor 801 in the communication device 80 shown in FIG. 8 invoking computer-executed instructions stored in the memory 803 .
  • the function/implementation process of the processing module 1402 in FIG. 14 can be realized by the processor 801 in the communication device 80 shown in FIG. /The implementation process can be implemented through the communication interface 804 in the communication device 80 shown in FIG. 8 .
  • 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 through, for example, according to 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 the form of network to interact with other systems) to communicate with local and/or remote processes.
  • packets of data e.g., data from a component that interacts with another component in a local system, a distributed system, and/or in the form of 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, signal, message, and channel may sometimes be used interchangeably.
  • “ ⁇ (of)”, “corresponding (corresponding, relevant)” and “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)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供了一种通信方法及其网络节点。该通信方法可应用于UE到网络中继U2N通信，在该通信方法中，第一网络节点gNB-CU向第二网络节点gNB-DU发送第一信息，触发该第二网络节点为Remote UE分配本地标识，该第一网络节点从所述第二网络节点接收第二信息，该第二信息包括该第二网络节点为该Remote UE分配的本地标识；或者，该第一网络节点向所述第二网络节点发送第一信息，该第一信息包括所述第一网络节点为该Remote UE分配的本地标识，其中，该第一网络节点或者第二网络节点通过Relay UE与该Remote UE通信。通过该方法，可以使得gNB-CU和gNB-DU之间的通信能够支持现有的层二U2N Relay通信。

Description

通信方法、装置及系统
本申请要求于2021年10月21日提交中国专利局、申请号为202111229637.4、申请名称为“通信方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信领域，尤其涉及通信方法、节点、装置、计算机可读存储介质及无线接入网设备。
背景技术
用户设备(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接口进行无线通信。
在层二(Layer-2，L2)U2N Relay的协议栈架构中，Remote UE的数据包在Relay UE的分组数据汇聚层协议(Packet Data Convergence Protocol，PDCP)层以下进行中继转发，即Relay UE维护用于中继的无线连路控制(Radio Link Control，RLC)承载，该中继RLC承载包括RLC协议层、媒体介入控制(Media Access Control，MAC)协议层以及物理层(Physical Layer，PHY)；在Remote UE和gNB基站之间具有端对端通信的PDCP协议层，业务数据适配协议(Service Data Adaptation Protocol，SDAP)协议层和无线资源控制(radio resource control，RRC)协议层，但没有端对端通信的RLC、MAC和PHY层。此外，在L2 U2N Relay协议架构中，RLC层与PDCP层之间增加了适配层(Adaptation layer，ADAPT)，该适配层的主要作用包括承载的复用和解复用，比如，支持不同的承载复用到一个承载上或者将一个承载拆分为多个不同的承载。
在下一代无线接入网(Next Generation Radio Access Network，NG-RAN)中，gNB基站采用了CU-DU分离架构，也就是说，一个gNB基站逻辑上划分为集中单元(Central Unit，CU)和分布单元(Distributed Unit，DU)这两部分，gNB-CU和gNB-DU之间通过F1接口通信，但现有的gNB-CU和gNB-DU之间的F1接口的通信流程，无法支持L2 U2N Relay通信。
发明内容
本申请实施例提供通信方法、网络节点、装置、计算机可读存储介质及无线接入网设备，用于解决在U2N Relay场景下，gNB-CU和gNB-DU之间的F1接口无法支持现有的L2 U2N Relay通信的问题。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，提供了一种通信方法，执行该通信方法的实体可以是第一网络节点，也可以是应用于第一网络节点中的功能模块，或者是第一网络节点中的芯片或芯片系统，或者是实 现该第一网络节点功能的网络实体或者网络设备。下面以执行主体为第一网络节点为例进行描述。该通信方法可以包括：所述第一网络节点向第二网络节点发送第一信息，所述第一信息用于触发所述第二网络节点为远端终端设备分配本地标识，以及，所述第一网络节点从所述第二网络节点接收第二信息，所述第二信息包括所述第二网络节点为所述远端终端设备分配的本地标识；或者，所述第一网络节点向所述第二网络节点发送第一信息，所述第一信息包括所述第一网络节点为所述远端终端设备分配的本地标识；其中，所述第一网络节点或者所述第二网络节点通过中继终端设备与所述远端终端设备通信。基于该通信方法，第一网络节点可以为所述远端终端设备分配本地标识并通知第二网络节点，或者第一网络节点可以指示第二网络节点为远端终端设备分配本地标识，从而可以使得第一网络节点(以gNB-CU为例)和第二网络节点(以gNB-DU为例)之间的通信，能够支持现有的层二U2N Relay通信。
结合上述第一方面，在一种可能的实现方式中，所述第一网络节点接收所述第二网络节点发送的第三信息；所述第三信息包括所述第二网络节点为所述远端终端设备分配的所述远端终端设备在第一接口的标识信息，或者，所述第三信息包括所述第二网络节点为所述远端终端设备分配的所述远端终端设备在第一接口的标识信息以及所述第二网络节点为所述中继终端设备分配的所述中继终端设备在所述第一接口的标识信息；其中，所述第一接口为所述第一网络节点和所述第二网络节点之间的通信接口。示例性的，通过上述过程，第二网络节点(以gNB-DU为例)为所述远端终端设备分配该终端设备在第一接口上的标识信息，并且可以让第一网络节点(以gNB-CU为例)知道所述远端终端设备所连接的中继终端设备，并可以成功地给中继终端设备发送中继服务所需的配置信息。
结合上述第一方面，在一种可能的实现方式中，还包括如下可选操作：
操作一：所述第一网络节点向所述第二网络节点发送第四信息，所述第四信息包括所述远端终端设备的数据无线承载标识DRB ID信息以及第一无线链路控制RLC承载的标识信息，所述远端终端设备的DRB ID信息和所述第一RLC承载的标识信息之间具有对应关系；所述第一网络节点接收所述第二网络节点发送的第五信息，所述第五信息包括所述第二网络节点生成的所述第一RLC承载的配置信息；其中，所述第一RLC承载为所述远端终端设备和所述中继终端设备之间的承载，所述远端终端设备的DRB ID信息和所述第一RLC承载的标识信息之间具有对应关系；
或者，操作二：所述第一网络节点接收所述第二网络节点生成的第五信息，所述第五信息包括：所述远端终端设备的数据无线承载标识DRB ID信息，第一RLC承载的标识信息，以及所述第一RLC承载的配置信息，其中，所述第一RLC承载为所述远端终端设备和所述中继终端设备之间的承载，所述远端终端设备的DRB ID信息和所述第一RLC承载的标识信息之间具有对应关系；
或者，操作三：所述第一网络节点向所述第二网络节点发送第四信息，所述第四信息包括所述远端终端设备的数据无线承载标识DRB ID信息，所述远端终端设备的本地标识，以及第二RLC承载的标识信息；所述第一网络节点接收所述第二网络节点生成的第五信息，所述第五信息包括所述第二RLC承载的配置信息；其中，所述第二RLC承载为所述第二网络节点和所述中继终端设备之间的承载；所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识以及所述第二RLC承载的标识信息之间具有对应关系；
或者，操作四：所述第一网络节点接收所述第二网络节点生成的第五信息，所述第五信息包括如下中至少一个：所述远端终端设备的数据无线承载标识DRB ID信息，所述远端终 端设备的本地标识，第二RLC承载的标识信息，以及所述第二RLC承载的配置信息；其中，所述第二RLC承载为所述第二网络节点和所述中继终端设备之间的承载，所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识以及所述第二RLC承载的标识信息之间具有对应关系。
结合上述第一方面，在一种可能的实现方式中，在上述操作二或所述操作四中，所述方法还可以包括：所述第一网络节点向所述第二网络节点发送第四信息，所述第四信息包括所述远端设备的标识信息。
结合上述第一方面，在一种可能的实现方式中，符合以下中任一：所述第四信息还包括上行传输隧道的标识信息，所述上行传输隧道的标识信息与如下中至少一个具有对应关系：所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识，所述远端终端设备的标识信息，以及所述第二RLC承载的标识信息；其中，所述上行传输隧道用于在所述第一接口上，所述第一网络节点从所述第二网络节点接收数据；和/或，所述第五信息还包括下行传输隧道的标识信息，所述下行传输隧道的标识信息与如下中至少一个具有对应关系：所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识，所述远端终端设备的标识信息，以及所述第二RLC承载的标识信息；其中，所述下行传输隧道用于在所述第一接口上，所述第一网络节点向所述第二网络节点发送数据。
示例性的，通过上述过程，第二网络节点(以gNB-DU为例)和第一网络节点(以gNB-CU为例)可以为所述远端终端设备配置所需要的所述远端终端设备的承载配置和所述中继终端设备的承载配置，并使能中继终端设备为远端终端设备和网络节点之间的数据传输提供中继服务。
结合上述第一方面，在一种可能的实现方式中，所述第一网络节点接收来自于所述中继终端设备的第一指示信息，所述第一指示信息包括所述远端终端设备的标识信息，所述第一指示信息用于请求为所述远端终端设备分配本地标识，所述远端终端设备的本地标识用于在所述第一网络节点控制范围内唯一标识所述远端终端设备，或者，所述远端终端设备的本地标识用于在所述中继终端设备控制范围内唯一标识所述远端终端设备。
结合上述第一方面，在一种可能的实现方式中，所述第一信息为所述中继终端设备的用户设备上下文修改请求UE CONTEXT MODIFICATION REQUEST消息，所述第二信息为所述中继终端设备的用户设备上下文修改响应UE CONTEXT MODIFICATION RESPONSE消息；或者，所述第四信息为所述远端终端设备的用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息，所述第五信息为所述远端终端设备的用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息；或者，所述第三信息为所述远端终端设备的初始上行RRC消息转移Initial UL RRC Message Transfer消息。
结合上述第一方面，在一种可能的实现方式中，所述第一网络节点包括：无线资源控制RRC协议层，服务数据适配协议SDAP协议层，以及分组数据汇聚层协议PDCP协议层；所述第二网络节点包括：无线链路控制RLC协议层，媒体访问控制MAC协议层，以及物理PHY协议层，所述第一网络节点和所述第二网络节点属于同一个基站gNB。
结合上述第一方面，在一种可能的实现方式中，在所述远端终端设备从第三网络节点向所述第二网络节点切换的过程中，所述第二网络节点为切换过程中的目标节点，所述第三网络节点为所述切换过程中的源节点，所述第一网络节点控制所述第二网络节点和所述第三网络节点，并且符合如下中任一：所述第一信息为所述远端终端设备的用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息，所述第二信息为所述远端终端设备的用户设备上 下文建立响应UE CONTEXT SETUP RESPONSE消息；或者，所述第四信息为所述远端终端设备的用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息，所述第五信息为所述远端终端设备的用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息。
结合上述第一方面，在一种可能的实现方式中，所述第三网络节点包括：无线链路控制RLC协议层，媒体访问控制MAC协议层，以及物理PHY协议层，所述第一网络节点，所述第二网络节点，以及所述第三网络节点包括在一个基站gNB中。
结合上述第一方面，在一种可能的实现方式中，在上述操作一或所述操作二中，所述方法还可以包括：所述第四信息或者第五信息还包括第一标识，所述第一标识用于指示与所述第一RLC承载对应所述中继终端设备。
所述第一标识为所述中继终端的标识或所述中继终端的服务小区标识或第一网络节点为中继终端分配的标识或第二网络节点为中继终端分配的标识。
第二方面，提供了一种通信方法，执行该通信方法的实体可以是第二网络节点，也可以是应用于第二网络节点中的功能模块，或者是第二网络节点中的芯片或芯片系统，或者是实现该第二网络节点功能的网络实体或者网络设备。该通信方法可以包括：所述第二网络节点接收来自于第一网络节点的第一信息，所述第一信息用于触发所述第二网络节点为远端终端设备分配本地标识，以及，所述第二网络节点向所述第一网络节点发送第二信息，所述第二信息包括所述第二网络节点为所述远端终端设备分配的本地标识；或者，所述第二网络节点接收来自于第一网络节点的第一信息，所述第一信息包括所述第一网络节点为所述远端终端设备分配的本地标识；其中，所述第一网络节点或者所述第二网络节点通过中继终端设备与所述远端终端设备通信。基于该通信方法，第一网络节点可以为所述远端终端设备分配本地标识并通知第二网络节点，或者第一网络节点可以指示第二网络节点为远端终端设备分配本地标识，第二网络节点将分配的所述远端终端设备的本地标识通知第一网络节点，从而可以使得第一网络节点(以gNB-CU为例)和第二网络节点(以gNB-DU为例)之间的通信，能够支持现有的层二U2N Relay通信。
结合上述第二方面，在一种可能的实现方式中，所述第二网络节点向所述第一网络节点发送第三信息；所述第三信息包括所述第二网络节点为所述远端终端设备分配的所述远端终端设备在第一接口的标识信息，或者，所述第三信息包括所述第二网络节点为所述远端终端设备分配的所述远端终端设备在第一接口的标识信息以及所述第二网络节点为所述中继终端设备分配的所述中继终端设备在所述第一接口的标识信息；其中，所述第一接口为所述第二网络节点和所述第一网络节点之间的通信接口。
结合上述第二方面，在一种可能的实现方式中，所述方法可以包括如下任一操作：
可选操作一：所述第二网络节点接收所述第一网络节点发送的第四信息，所述第四信息包括所述远端终端设备的数据无线承载标识DRB ID信息以及第一无线链路控制RLC承载的标识信息，所述远端终端设备的DRB ID信息和所述第一RLC承载的标识信息之间具有对应关系；所述第二网络节点向所述第一网络节点发送第五信息，所述第五信息包括所述第二网络节点生成的所述第一RLC承载的配置信息；其中，所述第一RLC承载为所述远端终端设备和所述中继终端设备之间的承载，所述远端终端设备的DRB ID信息和所述第一RLC承载的标识信息之间具有对应关系；
或者，可选操作二：所述第二网络节点向所述第一网络节点发送第五信息，所述第五信息包括：所述远端终端设备的数据无线承载标识DRB ID信息，第一RLC承载的标识信息，以及所述第一RLC承载的配置信息，其中，所述第一RLC承载为所述远端终端设备和所述 中继终端设备之间的承载，所述远端终端设备的DRB ID信息和所述第一RLC承载的标识信息之间具有对应关系；
或者，可选操作三：所述第二网络节点接收所述第一网络节点发送的第四信息，所述第四信息包括所述远端终端设备的数据无线承载标识DRB ID信息，所述远端终端设备的本地标识，以及第二RLC承载的标识信息；所述第二网络节点向所述第一网络节点发送第五信息，所述第五信息包括所述第二RLC承载的配置信息；其中，所述第二RLC承载为所述第二网络节点和所述中继终端设备之间的承载；所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识以及所述第二RLC承载的标识信息之间具有对应关系；
或者，可选操作四：所述第二网络节点向所述第一网络节点发送第五信息，所述第五信息包括：所述远端终端设备的数据无线承载标识DRB ID信息，所述远端终端设备的本地标识，以及第二RLC承载的标识信息；其中，所述第二RLC承载为所述第二网络节点和所述中继终端设备之间的承载，所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识以及所述第二RLC承载的标识信息之间具有对应关系。
结合上述第二方面，在一种可能的实现方式中，在上述操作二或所述操作四中，所述方法还可以包括：所述第二网络节点接收所述第一网络节点发送的第四信息，所述第四信息包括所述远端设备的标识信息。
结合上述第二方面，在一种可能的实现方式中，符合以下中任一：所述第四信息还包括上行传输隧道的标识信息，所述上行传输隧道的标识信息与如下中至少一个具有对应关系：所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识，所述远端终端设备的标识信息，以及所述第二RLC承载的标识信息；其中，所述上行传输隧道用于在所述第一接口上，所述第一网络节点从所述第二网络节点接收数据；和/或，所述第五信息还包括下行传输隧道的标识信息，所述下行传输隧道的标识信息与如下中至少一个具有对应关系：所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识，所述远端终端设备的标识信息，以及所述第二RLC承载的标识信息；其中，所述下行传输隧道用于在所述第一接口上，所述第一网络节点向所述第二网络节点发送数据。
结合上述第二方面，在一种可能的实现方式中，所述第一信息为所述中继终端设备的用户设备上下文修改请求UE CONTEXT MODIFICATION REQUEST消息，所述第二信息为所述中继终端设备的用户设备上下文修改响应UE CONTEXT MODIFICATION RESPONSE消息；或者，所述第四信息为所述远端终端设备的用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息，所述第五信息为所述远端终端设备的用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息；或者，所述第三信息为所述远端终端设备的初始上行RRC消息转移Initial UL RRC Message Transfer消息。
结合上述第二方面，在一种可能的实现方式中，所述第一网络节点包括：无线资源控制RRC协议层，服务数据适配协议SDAP协议层，以及分组数据汇聚层协议PDCP协议层；所述第二网络节点包括：无线链路控制RLC协议层，媒体访问控制MAC协议层，以及物理PHY协议层；所述第一网络节点和所述第二网络节点包括在一个基站gNB中。
结合上述第二方面，在一种可能的实现方式中，在所述远端终端设备从第三网络节点向所述第二网络节点切换的过程中，所述第二网络节点为切换过程中的目标节点，所述第三网络节点为所述切换过程中的源节点，所述第二网络节点和所述第三网络节点由所述第一网络节点控制，并且符合如下中任一：所述第一信息为所述远端终端设备的用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息，所述第二信息为所述远端终端设备的用户设备 上下文建立响应UE CONTEXT SETUP RESPONSE消息；或者，所述第四信息为所述远端终端设备的用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息，所述第五信息为所述远端终端设备的用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息。
结合上述第二方面，在一种可能的实现方式中，所述第三网络节点包括：无线链路控制RLC协议层，媒体访问控制MAC协议层，以及物理PHY协议层，所述第一网络节点，所述第二网络节点，以及所述第三网络节点包括在一个基站中。
结合上述第二方面，在一种可能的实现方式中，在上述操作一或所述操作二中，所述方法还可以包括：所述第四信息或者第五信息还包括第一标识，所述第一标识用于指示与所述第一RLC承载对应所述中继终端设备。
所述第一标识为所述中继终端的标识或所述中继终端的服务小区标识或第一网络节点为中继终端分配的标识或第二网络节点为中继终端分配的标识。
第三方面，提供了一种通信方法，执行该通信方法的实体可以是第一网络节点，也可以是应用于第一网络节点中的功能模块，或者是第一网络节点中的芯片或芯片系统，或者是实现该第一网络节点功能的网络实体或者网络设备。下面以执行主体为第一网络节点为例进行描述。该通信方法可以包括：所述第一网络节点向第二网络节点发送第六信息，所述第六信息包含第二指示信息，所述第二指示信息指示所述第二网络节点建立所述第二网络节点和中继终端设备之间的第二无线链路控制RLC承载，所述第二RLC承载用于承载第一数据，所述第一数据为远端终端设备与所述第二网络节点或所述第一网络节点之间交互的数据；所述第一网络节点接收所述第二网络节点DU发送的第七信息，所述第七信息包括所述第二RLC承载的配置信息。本实施例所称的无线链路控制RLC承载，具有RLC通道的功能，因此也可以称为RLC channel。通过本实施例方法，
结合上述第三方面，在一种可能的实现方式中，所述第二指示信息包括需要为所述远端设备建立的信令无线承载SRB的信息；或者，所述第二指示信息包括所述中继终端设备的中继服务授权信息。
结合上述第三方面，在一种可能的实现方式中，所述第一数据为所述远端终端设备的信令无线承载SRB0或信令无线承载SRB1或信令无线承载SRB2所承载的数据。示例性的，远端终端设备的SRB0，SRB1和SRB2的数据，可以复用在一个RLC承载进行传输。
结合上述第三方面，在一种可能的实现方式中，所述第六信息为用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息，所述第七信息为用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息。
结合上述第三方面，在一种可能的实现方式中，所述第六信息为用户设备上下文建立请求UE CONTEXT MODIFICATION REQUEST消息，所述第七信息为用户设备上下文建立响应UE CONTEXT MODIFICATION RESPONSE消息。
结合上述第三方面，在一种可能的实现方式中，所述第一网络节点包括：无线资源控制RRC协议层，服务数据适配协议SDAP协议层，以及分组数据汇聚层协议PDCP协议层；所述第二网络节点包括：无线链路控制RLC协议层，媒体访问控制MAC协议层，以及物理PHY协议层；所述第一网络节点和所述第二网络节点包括在一个基站gNB中。
第四方面，提供了一种通信方法，执行该通信方法的实体可以是第二网络节点，也可以是应用于第二网络节点中的功能模块，或者是第二网络节点中的芯片或芯片系统，或者是实现该第二网络节点功能的网络实体或者网络设备。下面以执行主体为第二网络节点为例进行描述。该通信方法可以包括：所述第二网络节点接收第一网络节点发送的第六信息，所述 第六信息包含第二指示信息，所述第二指示信息指示所述第二网络节点建立所述第二网络节点和中继终端设备之间的第二无线链路控制RLC承载，所述第二RLC承载用于承载第一数据，所述第一数据为远端终端设备与所述第二网络节点或所述第一网络节点之间交互的数据；所述第二网络节点向所述第一网络节点DU发送第七信息，所述第七信息包括所述第二RLC承载的配置信息。
结合上述第四方面，在一种可能的实现方式中，所述第二指示信息包括需要为所述远端设备建立的信令无线承载SRB的信息；或者，所述第二指示信息包括所述中继终端设备的中继服务授权信息。
结合上述第四方面，在一种可能的实现方式中，所述第一数据为所述远端终端设备的信令无线承载SRB0或信令无线承载SRB1或信令无线承载SRB2所承载的数据。示例性的，远端终端设备的SRB0，SRB1和SRB2的数据，可以复用在一个RLC承载进行传输。
结合上述第四方面，在一种可能的实现方式中，所述第六信息为用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息，所述第七信息为用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息。
结合上述第四方面，在一种可能的实现方式中，所述第六信息为用户设备上下文建立请求UE CONTEXT MODIFICATION REQUEST消息，所述第七信息为用户设备上下文建立响应UE CONTEXT MODIFICATION RESPONSE消息。
结合上述第四方面，在一种可能的实现方式中，所述第一网络节点包括：无线资源控制RRC协议层，服务数据适配协议SDAP协议层，以及分组数据汇聚层协议PDCP协议层；所述第二网络节点包括：无线链路控制RLC协议层，媒体访问控制MAC协议层，以及物理PHY协议层；所述第一网络节点和所述第二网络节点包括在一个基站中。
第五方面，本申请提供一种通信装置，该通信装置可以为第一网络节点或者第一网络节点中的芯片或者芯片系统，还可以为第一网络节点中用于实现第一方面或第一方面的任一可能的设计所述的方法的功能模块。该通信装置可以实现上述各方面或者各可能的设计中第一网络节点所执行的功能，所述功能可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
其中，上述第五方面的技术效果可参考上述第一、三方面，在此不再赘述。
第六方面，本申请提供一种通信装置，该通信装置可以为第二网络节点或者第二网络节点中的芯片或者芯片系统，还可以为第二网络节点中用于实现第二方面或第二方面的任一可能的设计所述的方法的功能模块。该通信装置可以实现上述各方面或者各可能的设计中第二网络节点所执行的功能，所述功能可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。如：该通信装置可以包括：收发模块和处理模块。
其中，上述第六方面的技术效果可参考上述第二、四方面，在此不再赘述。
第七方面，提供了一种通信装置，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该通信装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该通信装置执行如上述第一方面至第四方面中任一项所述的通信方法。
第八方面，提供了一种通信装置，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述第一方面至第四方面中任一项所述的通信方法。
在一种可能的实现方式中，通信装置还包括存储器；该存储器用于存储计算机指令。
在一种可能的实现方式中，通信装置还包括通信接口；该通信接口用于该通信装置与其 它设备进行通信。示例性的，该通信接口可以为收发器、输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。
在一种可能的实现方式中，该通信装置可以是芯片或芯片系统。其中，当该通信装置是芯片系统时，该通信装置可以由芯片构成，也可以包含芯片和其他分立器件。
在一种可能的实现方式中，当通信装置为芯片或芯片系统时，上述通信接口可以是该芯片或芯片系统上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。上述处理器也可以体现为处理电路或逻辑电路。
第九方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第一方面至第四方面中任一项所述的通信方法。
第十方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面至第四方面中任一项所述的通信方法。
第十一方面，提供一种无线接入网设备，比如，该无线接入网设备可以为gNB基站，该无线接入网设备包括如下中至少一个：执行上述第一、三方面所述的任一通信方法的第一网络节点，以及执行上述第二、四方面任一所述的通信方法的第二网络节点。
其中，第五方面至第十一方面中任一种设计方式所带来的技术效果可参见第一方面至第四方面中不同设计方式所带来的技术效果，此处不再赘述。
附图说明
图1(a)为本申请实施例提供的一种UE与UE之间直接通信场景的示意图；
图1(b)为本申请实施例提供的一种UE1和UE2在PC5口通信的控制面协议栈架构
图2为本申请实施例提供的一种可适用于U2N Relay场景的通信网络的示意图；
图3为本申请实施例提供的一种通信系统的用户面协议栈的示意图；
图4为本申请实施例提供的一种通信系统的控制面协议栈的示意图；
图5为本申请实施例提供的一种5G通信系统的示意图；
图6为本申请实施例提供的一种CU-DU分离的gNB架构示意图；
图7(a)为本申请实施例提供的一种适用于L2 U2N Relay的CU-DU分离架构下的通信系统的示意图；
图7(b)为本申请实施例提供的一种适配层设置在DU时的控制面协议栈架构示意图；
图7(c)为本申请实施例提供的一种适配层设置在DU时的用户面协议栈架构示意图；
图8为本申请实施例提供的一种通信装置的结构示意图；
图9为本申请实施例提供的一种通信方法的示意图；
图10为本申请实施例提供的又一种通信方法的示意图；
图11为本申请实施例提供的又一种通信方法的示意图；
图12为本申请实施例提供的又一种通信方法的示意图；
图13为本申请实施例提供的又一种通信方法的示意图；
图14为本申请实施例提供的另一种通信装置的结构示意图。
具体实施方式
介绍本申请实施例之前，对本申请实施例涉及的一些名词进行解释说明。需要说明的是，下述解释说明是为了让本申请实施例更容易被理解，而不应该视为对本申请实施例所要求的 保护范围的限定。
1、侧行链路
在传统无线通信系统中，UE与UE之间可以通过无线网络进行通信，UE与UE之间的数据信号通过接入网设备中转。但是，传统接入网设备(例如传统基站)为中心的蜂窝网络在数据传输质量及服务范围方面均有一定的局限性。在此需求下，邻近服务(proximity service，ProSe)通信应运而生，UE与UE之间也可以不借助接入网设备，直接进行通信，该方法可以有效减小UE与UE之间的通信时延。其中，UE与UE直接通信的链路可以称为侧行链路，侧行链路对应的UE和UE之间的通信接口为PC5接口，侧行链路也可以称为边链路/旁链路/直通链路等，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、侧行链路的广播、单播和组播通信
广播通信与基站广播系统信息类似，即UE不做加密对外发送广播业务数据，任何在有效接收范围内的其他UE，如果对该广播业务感兴趣都可以接收该广播业务的数据。
单播通信类似于UE与基站之间建立RRC连接之后进行的数据通信，需要两个UE之间先建立单播连接。在建立单播连接之后，两个UE可以基于协商的标识进行数据通信，该数据可以是加密的，也可以是不加密的。相比于广播，在单播通信中，只能是建立了单播连接的两个UE之间才能进行该单播通信。在单播通信中，UE在发送数据时，可以随数据一起发送源标识和目的标识，其中，源标识可以是由发端UE自己为该单播连接分配的标识，目的标识可以是对端接收UE为该单播连接分配的标识。
本申请实施例涉及单播通信过程。侧行链路上的一次单播通信对应于一对：源L2 ID(Source Layer-2 Identifier，层二标识源)和目的层二标识(Destination Layer-2 Identifier，L2ID)。每个侧行链路媒体接入控制层数据协议单元(Media Access Control Protocol Data Unit，MAC PDU)的子头中可以包含该源L2 ID和目的L2 ID，以使得数据传输至正确的接收端。
组播通信是指一个通信组内所有UE之间的通信，组内任一UE都可以收发该组播业务的数据。
3、无线承载(Radio Bearer，RB)
无线承载是基站为UE分配的一系列协议实体及配置的总称，一般是由层2提供的用于在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(Relay UE)来辅助远端UE(Remote UE)和网络设备之间的通信。如图2所示，图2为可适用于U2N Relay场景的通信网络的示意图，其中，基站与中继UE之间通过Uu接口通信，中继UE与远端UE之间通过PC5接口/Sidelink通信。远端UE可以通过中继UE与基站建立通信连接，在U2N Relay场景中，中继UE为远端UE提供中继服务。
现有的U2N Relay技术主要有层二(Layer-2,L2)和层三(Layer-3,L3)两种设计。参见图3，以L2Relay为例，对图2所示出的通信网络的用户面协议栈进行介绍。图3中示出了包含远端UE、中继UE、基站gNB和5G核心网(5G Core Network，5GC)设备的通信系统的用户面协议栈，其中，远端UE的协议栈中从上至下包括网络之间互联的协议(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层)层，以及与中继UE进行对等通信的物理(physical，PHY)层(或PC5-PHY层)。中继UE中与远端UE通信的协议栈从上至下包括适配层、PC5-RLC层、PC5-MAC层和PC5-PHY层。中继UE中与gNB通信的协议栈从上至下包括ADAPT层、Uu-RLC层、Uu-MAC层和Uu-PHY层。gNB中与远端UE通信的协议栈从上至下包括Uu-SDAP层和Uu-PDCP层。gNB中与中继UE通信的协议栈从上至下包括ADAPT层、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，图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层)和PHY层(或PC5-PHY层)。中继UE中，与远端UE通信的协议栈从上至下包括ADAPT层、PC5-RLC层、PC5-MAC层和PC5-PHY层。中继UE中，与gNB通信的协议栈从上至下包括ADAPT层、Uu-RLC层、Uu-MAC层和Uu-PHY层。gNB中与远端UE通信的协议栈从上至下包括Uu-RRC层和Uu-PDCP层。gNB中与中继UE通信的协议栈从上至下包括ADAPT层、Uu-RLC层、Uu-MAC层和Uu-PHY层。gNB中，通过N2接口与5GC设备通信的协议栈包括N2协议栈。5GC设备中与远端UE通信的协议栈包括NAS层。5GC设备中，通过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适配层。
以下行方向为例，gNB的适配层可以将一个或者多个Remote UE的多个承载上的数据复用至一个Uu RLC承载，即Uu link上的一个RLC承载可能会承载一个或者多个Remote UE的多个承载上的数据。在每个Remote UE的Sidelink上，该Remote UE的一个或者多个承载上的数据可以映射在一个PC5 RLC承载。上行方向类似，Remote UE的适配层可以将该Remote UE的多个承载上的数据映射至一个PC5 RLC承载。Relay UE的适配层则可以将一个或者多个Remote UE的不同RLC承载上的数据复用到一个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、CU-DU架构
如图5所示，图5为一种5G通信系统的示意图，其中，下一代无线接入网(Next Generation Radio Access Network，NG-RAN)由一个或多个连接至5G核心网5GC的基站gNB构成。gNB和5GC之间以NG接口连接，gNB之间以Xn接口连接。简言之，CU-DU分离架构是将一个gNB划分为集中单元(Central unit，CU)以及一个或多个分布单元(Distributed Unit，DU)。gNB-CU和gNB-DU之间通过F1接口连接，一个gNB-DU一般只能连接到一个gNB-CU。
在CU-DU分离架构下，gNB-CU可以负责RRC，SDAP以及PDCP协议层，也就是说gNB-CU具有RRC，SDAP以及PDCP协议层的功能，gNB-DU可以负责RLC，MAC以及PHY协议层，也就是说gNB-DU具有RLC，MAC以及PHY协议层的功能。
结合图5，如图6所示，图6为一种CU-DU分离的gNB架构示意图，其中，gNB-CU进一步划分为用户面(user plane，UP)和控制面(control plane，CP)，即，gNB-CU可以划分为包含gNB-CU-CP和gNB-CU-UP两部分。gNB-CU-CP和gNB-CU-UP通过E1接口连接；gNB-CU-CP通过NG控制面(NG-C)接口和AMF连接，gNB-CU-CP通过Xn控制面(Xn-C)接口和其他gNB连接，gNB-CU-CP通过F1控制面(F1-C)接口和gNB-DU连接；gNB-CU-UP通过F1用户面(F1-U)接口和gNB-DU连接。通常一个gNB-CU-UP只能连接到一个gNB-CU-CP，一个gNB-DU可以连接到一个gNB-CU-CP管理的多个gNB-CU-UP,一个gNB-CU-UP可以连接到一个gNB-CU-CP管理的多个gNB-DU。
在gNB-CU分离为gNB-CU-CP和gNB-CU-UP的架构下，对于控制面，gNB-CU-CP负责RRC以及SRB对应的PDCP实体(或称PDCP-C)，也就是说，gNB-CU-CP具有RRC协议层实体的功能以及SRB对应的PDCP实体(PDCP-C)的功能；对于用户面，gNB-CU-UP负责SDAP以及DRB对应的PDCP实体(或称PDCP-U)，也就是说，gNB-CU-UP具有SDAP协议层功能以及DRB对应的PDCP实体(PDCP-U)的功能。
由上可以看出，在现有的gNB CU-DU分离架构下，gNB CU或者gNB DU中并没有配置适用于L2 U2N Relay通信的Uu口适配层，从而导致现有的F1接口流程无法支持L2 U2N Relay通信。比如，背景技术中的UE根据Uu口的配置和gNB-DU直接通信，而在L2 U2N Relay架构中，基站和Relay UE之间新增加了Uu适配层，且基站需要对Remote UE和Relay UE进行配置，以支持Remote UE通过Relay UE的中继和基站进行通信，因此，现有的F1接口流程不再适用于L2 U2N relay。
有鉴于此，本申请实施例涉及如何解决现有CU-DU分离架构以及F1接口流程不适用于L2 U2N Relay的问题。比如，在L2 U2N relay应用于CU-DU架构时，需要解决以下中一个或多个问题：
·Remote UE的local ID如何生成，并告知Relay UE？
·gNB中的Uu适配层放置在CU还是DU？
·适配层的配置如何生成？
·设计新的UE初始接入流程，以支持Remote UE成功接入？
·设计新的同一个CU管理下的DU间切换(Inter-gNB-DU)流程，以支持Remote 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中的CU，第二网络节点可以是gNB中的DU。
本申请实施例中所称的终端设备，又称为用户设备(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中的通信装置或通信芯片本申请实施例对此不作限定。
如图7所示，图7(a)为本申请实施例适用的L2 U2N Relay在CU-DU分离架构下的通信系统的示意图，其中，gNB基站由第一网络节点CU和第二网络节点DU两部分构成，第一网络节点CU和第二网络节点DU之间通过F1接口通信，Relay UE和基站的DU通过Uu接口进行通信。Remote UE和Relay UE通过sidelink通信，Remote UE和Relay UE之间的接口为PC5口。Relay UE可能位于gNB的小区覆盖范围内。Remote UE可能位于gNB小区覆盖范围内，也可能移动至gNB小区覆盖范围以外，对于Remote UE移动到gNB小区覆盖范围以外的情况，Remote UE的数据可以通过Relay UE进行中继转发以实现Remote UE和基站进行用户面和信令面的交互。图7(b)示出了适配层设置在DU的控制面协议栈架构示意图，其中，CU具有RRC层和PDCP层，DU具有适配层ADAPT，RLC层，MAC层以及PHY层，其中，示意性的，CU中配置了两个RRC+PDCP实体，对应不同的SRB。图7(c)示出了适配层设置在DU的用户面协议栈架构示意图，其中，CU具有SDAP层和PDCP层，DU具有适配层ADAPT，RLC层，MAC层以及PHY层，其中，示意性的，CU中配置了两个SDAP+PDCP实体，对应了不用的DRB。
基于图7所提出的通信系统，图8为本申请实施例提供的一种通信装置80的结构示意图，当该通信装置80具有本申请实施例所述的第一网络节点的功能时，该通信装置80可以为第一网络节点或者第一网络节点中的芯片或者芯片系统；当该通信装置80具有本申请实施例所述的第二网络节点的功能时，该通信装置80可以为第二网络节点或者第二网络节点中的芯片或者芯片系统。当然，第一网络节点或第一网络节点的实现方式并不限于通信装置80，还可以是具有第一网络节点或第一网络节点功能的逻辑网络实体。
如图8所示，该通信装置80可以包括处理器801，通信线路802以及通信接口803。可选的，该通信装置80还可以包括存储器804。其中，处理器801，存储器804以及通信接口803之间可以通过通信线路802连接。
其中，处理器801可以是中央处理器(central processing unit，CPU)、通用处理器网络处理器(network processor，NP)、数字信号处理器(digital signal processing，DSP)、微处理器、微控制器、可编程逻辑器件(programmable logic device，PLD)或它们的任意组合。处理器801还可以是其它具有处理功能的装置，如电路、器件或软件模块等。
通信线路802，用于在通信装置80所包括的各部件之间传送信息。
通信接口803，用于与其他设备或其它通信网络进行通信。该其它通信网络可以为以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。通信接口803可以是射频模块或者任何能够实现通信的装置。本申请实施例仅以通信接口803为射频模块为例进行说明，其中，射频模块可以包括天线、射频电路等，射频电路可以包括射频集成芯片、功率放大器等。
存储器804，用于存储指令。其中，指令可以是计算机程序。
其中，存储器804可以是只读存储器(read-only memory，ROM)或可存储静态信息和/ 或指令的其他类型的静态存储设备，也可以是随机存取存储器(random access memory，RAM)或者可存储信息和/或指令的其他类型的动态存储设备，还可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储、磁盘存储介质或其他磁存储设备，光碟存储包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等。
需要说明的是，存储器804可以独立于处理器801存在，也可以和处理器801集成在一起。存储器804可以用于存储指令或者程序代码或者一些数据等。存储器804可以位于通信装置80内，也可以位于通信装置80外，不予限制。处理器801，用于执行存储器804中存储的指令，以实现本申请下述实施例提供的通信方法。
或者，可选的，本申请实施例中，也可以是处理器801执行本申请下述实施例提供的通信方法中的处理相关的功能，通信接口803负责与其他设备或通信网络通信，本申请实施例对此不作具体限定。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在一种示例中，处理器801可以包括一个或多个CPU，例如图8中的CPU0和CPU1。
作为一种可选的实现方式，通信装置80可以包括多个处理器，例如，除图8中的处理器801之外，还可以包括处理器807。
作为一种可选的实现方式，通信装置80还可以包括输出设备806和输入设备807。示例性地，输入设备807是键盘、鼠标、麦克风或操作杆等设备，输出设备806是显示屏、扬声器(speaker)等设备。
需要说明的是，图8中示出的组成结构并不构成对该通信装置的限定，除图8所示部件之外，该通信装置可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
下面结合图7所示通信系统，对本申请实施例提供的通信方法进行描述。其中，下述实施例中的网络节点可以具有图8所示部件或者结构。其中，本申请各实施例之间涉及的动作，术语等均可以相互参考，不予限制。本申请的实施例中各个设备之间交互的消息名称或消息中的参数名称等只是一个示例，具体实现中也可以采用其他的名称，不予限制。
本申请实施例提供的新的支持Remote UE通信的F1接口信令流程，可以使能CU-DU架构下进行L2 U2N Relay通信。在本申请实施例中，适配层可以配置在CU，也可以配置在DU，以下实施例以适配层配置在DU为例，提供了CU-DU分离架构下Remote UE的初始接入流程、Inter-DU切换流程和UE上下文释放流程。
结合图7所示出的通信系统，图9为本申请实施例提供的一种通信方法，如图9(a)所示，该方法涉及第一网络节点(比如，CU)和第二网络节点(比如，DU)，该方法可以包括如下步骤：
S901：第一网络节点向第二网络节点发送第一信息。
示例性的，该第一信息用于触发所述第二网络节点为远端终端设备分配本地标识。可以理解的是，S901为可选步骤。
其中，所述第一网络节点或者所述第二网络节点通过中继终端设备与远端终端设备通信。
S902：第二网络节点向第一网络节点发送第二信息，所述第二信息包括所述第二网络节 点为所述远端终端设备分配的本地标识。
S903：第二网络节点向第一网络节点发送第三信息。
其中，该第三信息包括该第二网络节点为所述远端终端设备分配的所述远端终端设备在第一接口的标识信息，或者，该第三信息包括所述第二网络节点为所述远端终端设备分配的所述远端终端设备在第一接口的标识信息以及所述第二网络节点为所述中继终端设备分配的所述中继终端设备在所述第一接口的标识信息；其中，所述第一接口为所述第一网络节点和所述第二网络节点之间的通信接口。
S904：第一网络节点向第二网络节点发送第四信息。可以理解的是，S904为可选步骤。
S905：第二网络节点向第一网络节点发送第五信息。
对于S904和S905，有如下可选操作：
可选操作一，包括：
第一网络节点向第二网络节点发送第四信息，该第四信息包括所述远端终端设备的数据无线承载标识DRB ID信息以及第一无线链路控制RLC承载的标识信息，所述远端终端设备的DRB ID信息和所述第一RLC承载的标识信息之间具有对应关系；所述第一网络节点接收所述第二网络节点发送的第五信息，所述第五信息包括所述第二网络节点生成的所述第一RLC承载的配置信息；其中，所述第一RLC承载为所述远端终端设备和所述中继终端设备之间的承载，所述远端终端设备的DRB ID信息和所述第一RLC承载的标识信息之间具有对应关系。
可选操作二，包括：
第一网络节点接收第二网络节点生成的第五信息，所述第五信息包括：所述远端终端设备的数据无线承载标识DRB ID信息，第一RLC承载的标识信息，以及所述第一RLC承载的配置信息，其中，所述第一RLC承载为所述远端终端设备和所述中继终端设备之间的承载，所述远端终端设备的DRB ID信息和所述第一RLC承载的标识信息之间具有对应关系。
可选操作三，包括：
所述第一网络节点向所述第二网络节点发送第四信息，所述第四信息包括所述远端终端设备的数据无线承载标识DRB ID信息，所述远端终端设备的本地标识，以及第二RLC承载的标识信息；所述第一网络节点接收所述第二网络节点生成的第五信息，所述第五信息包括所述第二RLC承载的配置信息；其中，所述第二RLC承载为所述第二网络节点和所述中继终端设备之间的承载；所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识以及所述第二RLC承载的标识信息之间具有对应关系。
可选操作四，包括：
所述第一网络节点接收所述第二网络节点生成的第五信息，所述第五信息包括如下中至少一个：所述远端终端设备的数据无线承载标识DRB ID信息，所述远端终端设备的本地标识，第二RLC承载的标识信息，以及所述第二RLC承载的配置信息；其中，所述第二RLC承载为所述第二网络节点和所述中继终端设备之间的承载，所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识以及所述第二RLC承载的标识信息之间具有对应关系。
可以理解的是，在上述操作二或所述操作四中，所述方法也可以包括步骤：所述第一网络节点向所述第二网络节点发送第四信息，所述第四信息包括所述远端设备的标识信息。
在一种可选设计中，该第四信息还包括上行传输隧道的标识信息，所述上行传输隧道的标识信息与如下中至少一个具有对应关系：所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识，所述远端终端设备的标识信息，以及所述第二RLC承载的标识信息；其 中，所述上行传输隧道用于在所述第一接口上，所述第一网络节点从所述第二网络节点接收数据；和/或，该第五信息还包括下行传输隧道的标识信息，所述下行传输隧道的标识信息与如下中至少一个具有对应关系：所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识，所述远端终端设备的标识信息，以及所述第二RLC承载的标识信息；其中，所述下行传输隧道用于在所述第一接口上，所述第一网络节点向所述第二网络节点发送数据。
在一种可选设计中，该第一网络节点还可以接收来自于所述中继终端设备的第一指示信息，所述第一指示信息包括所述远端终端设备的标识信息，所述第一指示信息用于请求为所述远端终端设备分配本地标识，所述远端终端设备的本地标识用于在所述第一网络节点控制范围内唯一标识所述远端终端设备，或者，所述远端终端设备的本地标识用于在所述中继终端设备控制范围内唯一标识所述远端终端设备。
在一种可选设计中，该第四信息还包括第一标识信息，所述第一标识用于指示与所述第一RLC承载对应所述中继终端设备。例如，第一标识信息可以是中继终端的层2标识，用于指示第一RLC承载为所述远端终端和所述层2标识所指示的中继终端之间的RLC承载。当远端终端通过多个中继终端和第二网络节点进行通信时，该指示信息可用于区分第一RLC承载对应的中继终端设备。
可选择地，第一标识还可以指示中继终端的服务小区标识，例如在限定多个中继终端必须处于不同的服务小区的场景中。此外，第一标识还可以是第一网络节点为中继终端分配的标识信息，例如，对于远端终端连接于三个中继终端的情况，第一网络节点可以分别为三个中继终端分配标识0,1和2，并和第一RLC承载的标识信息一起，通过第四信息指示第二网络节点。
在一种可选设计中，该第五信息还包括第一标识信息，所述第一标识用于指示与所述第一RLC承载对应所述中继终端设备。例如，第一标识信息可以是中继终端的层2标识，用于指示第一RLC承载为所述远端终端和所述层2标识所指示的中继终端之间的RLC承载。当远端终端通过多个中继终端和第二网络节点进行通信时，该指示信息可用于区分第一RLC承载对应的中继终端设备。
可选择地，第一标识还可以指示中继终端的服务小区标识，例如在限定多个中继终端必须处于不同的服务小区的场景中。此外，第一标识还可以是第二网络节点为中继终端分配的标识信息，例如，对于远端终端连接于三个中继终端的情况，第二网络节点可以分别为三个中继终端分配标识0,1和2，，并和第一RLC承载的标识信息一起，通过第五信息指示第一网络节点。
本实施例中，如上，该第一信息可以为所述中继终端设备的用户设备上下文修改请求UE CONTEXT MODIFICATION REQUEST消息，所述第二信息可以为所述中继终端设备的用户设备上下文修改响应UE CONTEXT MODIFICATION RESPONSE消息；或者，该第一信息可以为所述中继终端设备的用户设备上下文修改请求UE CONTEXT SETUP REQUEST消息，所述第二信息可以为所述中继终端设备的用户设备上下文修改响应UE CONTEXT SETUP RESPONSE消息；或者，该第四信息可以为所述远端终端设备的用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息，所述第五信息可以为所述远端终端设备的用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息；或者，该第三信息可以为所述远端终端设备的初始上行RRC消息转移Initial UL RRC Message Transfer消息。
本实施例中，所述第一网络节点可以包括：无线资源控制RRC协议层，服务数据适配协议SDAP协议层，以及分组数据汇聚层协议PDCP协议层；所述第二网络节点可以包括：无 线链路控制RLC协议层，媒体访问控制MAC协议层，以及物理PHY协议层。所述第一网络节点和所述第二网络节点可以包括在一个基站中。
对于切换场景，在所述远端终端设备从第三网络节点向所述第二网络节点切换的过程中，所述第二网络节点为切换过程中的目标节点，所述第三网络节点为所述切换过程中的源节点，所述第一网络节点控制所述第二网络节点和所述第三网络节点，该第三网络节点包括：无线链路控制RLC协议层，媒体访问控制MAC协议层，以及物理PHY协议层，所述第一网络节点，所述第二网络节点，以及所述第三网络节点包括在一个基站中。并且，符合如下中任一：所述第一信息为所述远端终端设备的用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息，所述第二信息为用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息；或者，所述第四信息为所述远端终端设备的用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息，所述第五信息为用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息。
如图9(b)所示，为本申请实施例提供的又一种通信方法，该方法涉及第一网络节点(比如，CU)和第二网络节点(比如，DU)，该方法可以包括如下步骤：
S901’：第一网络节点向第二网络节点发送第六信息。
其中，所述第六信息包含第二指示信息，所述第二指示信息指示所述第二网络节点建立所述第二网络节点和中继终端设备之间的第二无线链路控制RLC承载，所述第二RLC承载用于承载第一数据，所述第一数据为远端终端设备与所述第二网络节点或所述第一网络节点之间交互的数据。其中，该第二RLC承载也可以称之为RLC channel。
示例性的，该第二指示信息包括需要为所述远端设备建立的信令无线承载SRB的信息；或者，所述第二指示信息包括所述中继终端设备的中继服务授权信息。
示例性的，该第一数据为所述远端终端设备的信令无线承载SRB0或信令无线承载SRB1或信令无线承载SRB2所承载的数据。需要说明的是，所述远端终端设备的信令无线承载SRB0或信令无线承载SRB1或信令无线承载SRB2所承载的数据，可以复用在同一个Uu RLC承载上。
S902’：第二网络节点向第一网络节点发送第七信息。
其中，所述第六信息为用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息，所述第七信息为用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息。
可以理解的是，在S901’和S902’中，并不限定配置该第二RLC承载是在Remote UE随机接入之前，还是在Remote UE随机接入过程中。
示例性的，上述第一网络节点包括：无线资源控制RRC协议层，服务数据适配协议SDAP协议层，以及分组数据汇聚层协议PDCP协议层；以及上述第二网络节点包括：无线链路控制RLC协议层，媒体访问控制MAC协议层，以及物理PHY协议层；该第一网络节点和该第二网络节点可以包括在一个无线接入网设备中，比如基站gNB。
参考图7所示出的通信系统以及图9所示出的通信方法，以Uu适配层设置于DU为例，本申请实施例提供了Remote UE的UE初始接入流程，具体的，相比较于现有技术中UE直接通过Uu link和基站通信的场景，在Remote UE进行初始接入之前，Relay UE还需要做以下两方面的准备工作：
·Relay UE和DU之间(即在Uu link上)建立用于承载Remote UE的SRB信令的RLC承载，为便于描述，下文统一称Relay UE和DU之间的RLC承载为Uu RLC承载。
·基站给Remote UE分配本地标识local ID，并告知Relay UE。后续的数据交互过程中， Relay UE在接收到Remote UE的SRB0信令后，转发前需添加该local ID，以使得基站能够识别接收到的SRB0信令所属的Remote UE。
由此，基站可以在Relay UE的初始上下文建立过程中，预先建立DU和Relay UE之间的Uu RLC承载(或RLC channel)，用于承载Remote UE的SRB信令。
针对用于承载Remote UE的SRB信令的Uu RLC承载的建立过程，如图10所示，图10为本申请实施例提供的又一种通信方法的示意图，该方法可以包括如下步骤：
S1001：CU向DU发送用户设备下文建立请求UE CONTEXT SETUP REQUEST消息。
该UE CONTEXT SETUP REQUEST消息用于请求DU建立Uu RLC承载，该RLC承载用于承载Remote UE的SRB0/1/2信令。
S1002：DU向CU发送用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息。
该UE CONTEXT SETUP RESPONSE消息中携带DU建立的Uu RLC承载的配置信息。
一种可能的方式中，CU配置了Uu RLC承载和Remote UE的SRB0/1/2之间的对应关系，
并指示DU建立Uu RLC承载。或者，CU指示DU建立Uu RLC承载，同时指示DU Uu
RLC承载和Remote UE的SRB0/1/2之间的对应关系。
在另一种可选方式中，Relay UE的初始上下文建立过程不变，基站可以通过上下文更新流程，建立用于承载Remote UE的SRB信令的Uu RLC承载，该流程可以由CU发起(如步骤S1001a和S1002a)；或者，也可以由DU发起(如步骤S1001b和S1002b)。具体的，该方法可以包括：
S1001a：CU向DU发送UE上下文修改请求UE CONTEXT MODIFICATION REQUEST消息。该UE CONTEXT MODIFICATION REQUEST消息可用于指示DU建立Uu RLC承载，以用于承载Remote UE的SRB0/1/2。
S1002a：DU向CU发送UE上下文修改响应UE CONTEXT MODIFICATION RESPONSE消息，该UE CONTEXT MODIFICATION RESPONSE消息中携带DU生成的Uu RLC承载的配置信息。
一种可能的方式中，CU配置了Uu RLC承载和Remote UE的SRB0/1/2之间的对应关系，并指示DU建立Uu RLC承载。或者，CU指示DU建立Uu RLC承载，同时指示DU生成Uu RLC承载和Remote UE的SRB0/1/2之间的对应关系。
或者可选的，该方法可以包括：
S1001b：DU给CU发送用户设备上下文修改要求UE CONTEXT MODIFICATION REQUIRED消息。通过该UE CONTEXT MODIFICATION REQUIRED消息，将DU生成的Uu RLC承载的配置信息发送给CU。可以理解的是，DU配置的Uu RLC承载还可以指示Uu RLC承载和Remote UE的SRB0/1/2之间的对应关系。
S1002b：CU向DU发送用户设备上下文修改确认UE CONTEXT MODIFICATION CONFIRM消息。通过该UE CONTEXT MODIFICATION CONFIRM消息，CU向DU确认DU成功建立的RLC承载。
可选的，上述S1001，S1002，S1001a，S1002a，S1001b，S1002b涉及的用户设备上下文更新流程，可以基于能力和授权发起。例如，在CU给DU发送的F1接口信令中(如UE CONTEXT SETUP REQUEST消息或UE CONTEXT MODIFICATION REQUEST消息)，可以携带Relay UE相关的中继服务的授权信息，此时CU或者DU可以根据该授权信息触发上述上下文更新流程。或者，也可以在UE能力查询过程中，Relay UE接收到基站发送的UECapabilityEnquiry消息后，将Relay UE自己的UE能力信息通过UECapabilityInformation 消息告知基站，若该UE能力信息中包含该UE能够支持中继通信的信息，则基站可以据此触发上述上下文更新流程。
可以理解的是，上述用户设备上下文更新流程也可以在第一个Remote UE接入时发起。如下文所述，Remote UE接入Relay UE之后，Relay UE将给基站发送SUI信息，以告知基站Remote UE和Relay UE之间将进行sidelink通信，并请求基站分配相应的传输资源。基站接收到SUI信息后，触发上下文更新流程，为后续Remote UE的SRB信令预先建立Uu RLC承载。
针对为Remote UE分配本地标识local ID的过程，如图11所示，图11为本申请实施例提供的又一种通信方法的示意图，该方法可以包括如下步骤：
S1101：Remote UE和Relay UE之间建立单播连接。
S1102：Relay UE向DU发送SUI消息。
示例性的，Remote UE和Relay UE之间建立单播连接后，触发Relay UE给基站(通过gNB-DU)发送侧行链路用户设备信息(SidelinkUEInformation，SUI)，该SUI消息可用于请求为该Remote UE分配local ID。
可选操作S1101a：Remote UE给Relay UE发送SRB0信令(比如，MSG3消息或RRCSetupRequest消息)后，触发Relay UE向基站发送SUI消息。
S1103：DU向CU发送上行RRC消息转移UL RRC MESSAGE TRANSFER消息。
其中，该UL RRC MESSAGE TRANSFER消息包含Relay UE给gNB-DU发送的上述SUI消息，也即DU将SUI消息透传给CU，该SUI消息可以在CU的RRC层进行解析。
通常，和Relay UE建立单播连接并尝试进行sidelink通信的UE可以包括两种：从Relay UE处获取中继服务的Remote UE，以及通过sidelink和Relay UE进行直接通信的UE。当有UE接入Relay UE并尝试通过sidelink和该Relay UE进行通信时，均可以触发Relay UE向基站发送SUI消息，通过该SUI消息指示该Remote UE的Destination L2 ID，并请求sidelink传输资源，比如可以在该SUI消息中携带该Remote UE的Destination L2 ID，基站收到该Remote UE的Destination L2 ID后，可以为Remote UE分配sidelink传输资源。但是，对于本申请实施例，基站还需要给Remote UE分配local ID，因此，基站需要能够区分SUI中上报的Destination L2 ID是否为Remote UE，具体可以包括以下几种可选方式：
·定义新的上行RRC消息，区别于现有的SUI消息，用于请求Remote UE的local ID，基站可以通过该新定义的上行RRC消息，确定需要为该Remote UE分配local ID。
·在现有的SUI消息中，引入一个新的IE，用于指示Remote UE的L2 ID，基站从而根据所指示的Remote UE的L2 ID，确定需要为该Remote UE分配local ID。
·在现有的SUI消息中，引入1-bit指示信息，用于指示该UE是否为Remote UE。例如，利用现有SUI消息中的IE sl-casttype中的预留位spare1，标识该UE是否是Remote UE，比如该bit取值为1，则表示该UE是Remote UE，或者也可以该bit取值为0表示该UE是Remote UE。
S1104：CU向DU发送用户设备上下文修改请求UE CONTEXT MODIFICATION REQUEST消息。
通过该UE CONTEXT MODIFICATION REQUEST消息，指示DU为Remote UE分配local ID，例如，直接将SUI消息转发给DU，或者通过定义专门的指示信息，承载在UE CONTEXT MODIFICATION REQUEST消息。或者，CU也可以将自己分配的该Remote UE的local ID，携带在该UE CONTEXT MODIFICATION REQUEST消息中发送给DU。
在上述步骤中，gNB-CU从SUI消息中接收到的可以是Remote UE的L2 ID，因此基站可以为每个Remote UE的L2 ID生成对应的Remote UE的local ID，基站可以同时维护Remote UE的L2 ID和Remote UE的local ID之间的对应关系。在另一种可选方式中，Relay UE在发送的SUI消息中可以携带Remote UE的系统架构演进临时移动台标识符(system architecture evolution temporary mobile station identifier，S-TMSI)，Relay UE可以在单播连接建立过程中从Remote UE获得该S-TMSI，基站从而可以为每个S-TMSI分配对应的local ID，并维护S-TMSI和local ID之间的对应关系。
S1105：DU向CU发送用户设备上下文修改响应UE CONTEXT MODIFICATION RESPONSE消息。
通过UE CONTEXT MODIFICATION RESPONSE消息，DU将分配好的Remote UE的local ID发送给CU。或者，对于CU将CU分配的Remote UE的local ID，携带在UE CONTEXT MODIFICATION REQUEST消息中发送给DU的情况，DU可以通过UE CONTEXT MODIFICATION RESPONSE消息，确认CU给DU发送的Remote UE的local ID。
S1106：CU向DU发送下行RRC转移DL RRC TRANSFER消息，其中携带Remote UE的local ID。
其中，CU可以将分配的Remote UE的local ID承载在RRC消息中，如RRC重配置RRCReconfiguration消息中，通过DL RRC TRANSFER消息发送给DU，该DL RRC TRANSFER消息中可以携带RRCReconfiguration消息。
S1107：DU将CU生成的RRC重配置RRCReconfiguration消息发送给Relay UE，该RRCReconfiguration消息携带为Remote UE分配的local ID。
参考上述图7-11所示出的本申请实施例，如图12所示，图12为本申请实施例提供的又一种通信方法的示意图，提出了一种为Remote UE提供初始接入的通信方法，该方法包括：
S1201：Remote UE向DU发送RRC建立请求RRCSetupRequest消息。
其中，Remote UE可以通过Relay UE的中继功能，给DU发送RRCsetupRequest消息，用于请求建立Remote UE和gNB之间的RRC连接。在Relay UE转发RRCsetupRequest消息的过程中，Relay UE可以在Remote UE的SRB0数据包(比如适配层PDU)的包头上添加Remote UE的local ID。可选的，Relay UE可以根据图10所示出的实施例中的各种配置方法中配置的Uu RLC承载配置，进行SRB0数据的转发。
S1202：DU向CU发送初始上行RRC消息转移INITIAL UL RRC MESSAGE TRANSFER消息。
其中，DU在接收到携带Remote UE的local ID标识的Remote UE的SRB0数据包后，DU给该Remote UE分配用户设备F1接口UE F1AP ID，并可以关联Remote UE local ID和该Remote UE的DU UE F1AP ID。然后DU发送INITIAL UL RRC MESSAGE TRANSFER消息给CU，消息中携带DU分配的该Remote UE的DU UE F1AP ID。
可以理解的是，CU需要感知该Remote UE和哪个Relay UE相连接，因此INITIAL UL RRC MESSAGE TRANSFER消息中可以携带DU给该Relay UE分配的Relay UE的DU UE F1AP ID。
若gNB分配的local ID在gNB控制范围内唯一，则在另一种可选的实现方式中，INITIAL UL RRC MESSAGE TRANSFER可以携带Remote UE的local ID，那么CU也可以根据该local ID确定该Remote UE和哪个Relay UE连接。
S1203：CU向DU发送下行RRC消息转移DL RRC MESSAGE TRANSFER消息。
其中，CU为该Remote UE分配了该Remote UE在F1口的CU侧UE F1AP ID，并生成发送给Remote UE的RRC建立RRCSetup消息，将该RRCSetup消息携带在DL RRC MESSAGE TRANSFER消息发送给DU。
S1204：DU向Remote UE发送RRC Setup消息。
其中，DU可以通过Relay UE的中继功能向Remote UE发送该RRCSetup消息。为了让Relay UE知道该RRC消息属于哪个Remote UE，适配层在构造适配层PDU时，在适配层头上携带Remote UE的local ID。
S1205：Remote UE向DU发送RRC建立完成RRCSetupComplete消息。
其中，Remote UE可以通过Relay UE的中继功能向DU发送该RRCSetupComplete消息。
S1206：DU向CU发送上行RRC消息转移UL RRC MESSAGE TRANSFER消息。
其中，DU可以通过该UL RRC MESSAGE TRANSFER消息携带该RRCSetupComplete消息，向CU转发Remote UE发送的RRCSetupComplete消息。
S1207：CU向DU发送用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息。
其中，CU给DU发送Remote UE的UE CONTEXT SETUP REQUEST，可以用于指示DU建立Remote UE的UE上下文。
S1208&S1210：Relay UE和DU之间交互安全命令模式(SecurityModeCommand，SMC)消息。其中，Relay UE和DU之间交互SMC消息的过程，可以用于接入(access stratum，AS)侧的安全模式激活。
S1209：DU向CU回复用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息，用于指示Remote UE的UE上下文在DU建立成功。
在一种实现方式中，通过步骤S1207和S1209，gNB除了配置Remote UE的上下文内容，如小区配置和Remote UE的ID信息、Remote UE的SRB/DRB的承载配置信息、gNB向Remote UE发送RRC消息(如S1208的SMC消息)等，gNB还可以分别配置Relay UE和Remote UE的适配层配置信息。Relay UE和Remote UE的适配层配置信息可以由gNB-DU或者gNB-CU进行配置，以下对不同的可选配置方式进行描述。
1.Remote UE的适配层配置由CU确定
Remote UE适配层的配置内容可以包括：Remote UE的DRB ID信息和PC5 RLC承载信息，Remote UE的DRB ID信息和PC5 RLC承载信息这两者之间具有映射关系。CU配置好适配层的上述信息后，可以通过步骤S1207中的UE CONTEXT SETUP REQUEST消息将Remote UE适配层的上述配置内容发送给DU。进一步的，DU可以根据CU的指示建立相应的PC5 RLC承载的配置，并通过步骤1209的UE CONTEXT SETUP RESPONSE消息将该PC5RLC承载的配置信息发送给CU。
此外，Remote UE适配层的配置内容还可以包括relay UE的标识信息，用于指示该PC5RLC承载为remote UE和所指示的relay UE之间的PC5 RLC承载。relay UE的标识信息可以是relay UE的层2标识，或者CU为relay UE分配的标识信息，或者relay UE的服务小区标识。
2.Remote UE的适配层配置由DU确定
CU可以通过步骤S1207中的UE CONTEXT SETUP REQUEST消息，指示DU为Remote UE配置适配层的配置信息。然后，DU将自己配置好的Remote UE的适配层的配置内容以及相应的PC5 RLC承载的配置信息，通过UE CONTEXT SETUP REPONSE消息发送给CU。Remote UE适配层的配置内容可以包括：Remote UE的DRB ID信息和PC5 RLC承载信息， Remote UE的DRB ID信息和PC5 RLC承载信息这两者之间具有映射关系。可选择地，CU可以不需要在步骤S1207中的UE CONTEXT SETUP REQUEST消息中携带额外的指示信息，因为DU根据上传的RRC消息，可以知道这是一个Remtoe UE，因此可以通过自己的内部实现，确定Remote UE的适配层的配置内容以及相应的PC5 RLC承载的配置信息。
此外，Remote UE适配层的配置内容还可以包括relay UE的标识信息，用于指示该PC5RLC承载为remote UE和所指示的relay UE之间的PC5 RLC承载。relay UE的标识信息可以是relay UE的层2标识，或者CU为relay UE分配的标识信息，或者relay UE的服务小区标识。
3.Relay UE的适配层配置由CU确定
其中，CU可以确定新建Relay UE的Uu RLC承载或者重用Relay UE的现有的Uu RLC承载来承载Remote UE的数据。此处所称的Uu RLC承载可指DU和Relay UE之间的Uu link上的RLC承载。
步骤S1207中，CU向DU发送的UE CONTEXT SETUP REQUEST消息可以携带请求新建或者修改的Uu RLC承载的ID信息，还可以携带与Uu RLC承载对应的Remote UE DRB ID信息，还可以携带Uu RLC承载的QoS要求。Relay UE的适配层需要配置Uu RLC承载和Remote UE的DRB ID之间的映射关系，RLC承载的QoS要求信息则可以作为DU生成RLC承载配置的参考依据。此外，UE CONTEXT SETUP REQUEST消息还可以包含上行隧道信息，上行隧道即DU给CU发送数据所需要的隧道，每个隧道对应一个Remote UE DRB ID，并且可以为每个上行隧道分配一个隧道地址，用于标识该上行隧道。如图7(c)所示，上行数据从适配层递交给F1接口上的隧道(比如，F1-U GTP tunnel)，适配层需要将复用在Uu RLC承载上的数据递交给对应的隧道，因此CU还需要配置Remote UE ID、DRB ID和隧道地址以及这三者之间的映射关系，并将Remote UE ID、DRB ID和隧道地址(含这三者之间的映射关系)通知给DU。
DU接收到CU配置的内容(Remote UE ID、DRB ID和隧道地址)后，可以根据CU的指示生成需新建或者需修改的Uu RLC承载的配置信息，并通过步骤S1209中的UE CONTEXT SETUP RESPONSE消息携带需新建或者需修改的Uu RLC承载的配置信息，发送给CU，比如，该Uu RLC承载的配置信息可以在UE CONTEXT SETUP RESPONSE消息以单独的RRC容器(container)的形式发送。此外，该UE CONTEXT SETUP RESPONSE消息中还可以包含下行隧道的配置信息(即CU发送给DU方向)，每个下行隧道可以对应一个Remote UE的DRB ID，还可以为每个下行隧道分配一个隧道地址，用于标识该下行隧道。可以理解的是，由于DU这一侧，可能是多个隧道对应到一个适配层或者一个Uu RLC承载，或因此，对应于不同的Remote UE的DRB ID，可能分配相同的隧道地址。所有隧道分配一个地址，或者按照Uu RLC承载的粒度分配地址。即在该Uu RLC承载上复用的DRB所对应的隧道分配相同的地址。
在隧道的收发过程中，DU侧的地址虽然相同，但可以通过CU侧的地址来区分不同的隧道。
4.Relay UE的适配层配置由DU确定
在步骤S1207中，CU向DU发送的UE CONTEXT SETUP REQUEST消息，可以用来请求DU为Remote UE配置Relay UE的适配层配置。UE CONTEXT SETUP REQUEST消息可以携带Remote UE承载的QoS信息，以及上行隧道信息。在这种情况下，DU可以自行决定是否新建Uu RLC承载用于承载Remote UE的数据，并配置不同Uu RLC承载对应的Remote  UE DRB ID，以及下行隧道信息，Uu RLC承载信息，Remote UE DRB ID信息以及下行隧道信息这三者之间具有对应关系，分配方式同上。在步骤S1209中，DU通过UE CONTEXT SETUP RESPONSE消息，将上述配置发送给CU。
以上方法中，Remote UE和Relay UE的适配层配置均是在Remote UE的上下文建立过程中生成。另一种可选的实现方式是Remote UE上下文建立过程仅生成Remote UE的适配层的配置，而Relay UE的适配层配置则通过Relay UE的UE上下文修改UE context modification过程生成。类似的，在该过程中，Relay UE的适配层配置同样可以是DU发起或者CU发起，和上述步骤S1207和步骤S1209类似，不同之处在于，DU和CU之间的信令交互是通过与Relay UE相关联的F1接口信令。下面以CU来配置适配层的配置信息为例，进行举例说明。
如图12，
步骤Sb1：CU向DU发送用户设备上下文修改请求UE CONTEXT MODIFICATION REQUEST消息。
其中，CU可以决定建立新的Uu RLC承载用于Remote UE的数据，于是CU给DU发送UE CONTEXT MODIFICATION REQUEST消息，通过该消息中的信元，指示新建的Uu RLC承载的ID，并指示每个Uu RLC承载对应的Remote UE DRB ID信息。该UE CONTEXT MODIFICATION REQUEST消息中可以包括DRB ID和需新建的Uu RLC承载的QoS信息，还可以包括上行隧道信息。
步骤Sb2：DU向CU发送用户设备上下文修改响应UE CONTEXT MODIFICATION RESPONSE消息。
其中，DU可以根据CU的指示，确定该Uu RLC承载的配置信息，并通过UE CONTEXT MODIFICATION RESPONSE消息将Relay UE和DU之间的Uu RLC承载的配置信息发送给CU。
S1211：DU向CU发送上行RRC消息转移UL RRC MESSAGE TRANSFER消息。
具体的，DU可以通过UL RRC MESSAGE TRANSFER消息携带Relay UE回复的SMC消息，将该Relay UE回复的SMC消息转发给CU。
S1212：CU向DU发送下行RRC消息转移DL RRC MESSAGE TRANSFER消息。
具体的，CU可以生成RRC重配置RRCReconfiguration消息，该RRC重配置RRCReconfiguration消息包含Remote UE的映射关系配置信息，比如，Remote UE的映射关系配置信息可以包括如下中的一个或多个信息及其之间的映射关系：Remote UE ID信息、Remote DRB ID信息，隧道地址信息，Uu RLC承载标识信息，PC5 RLC承载标识信息，以及中继终端对应的标识信息，并通过DL RRC MESSAGE TRANSFER消息发送给DU。所述中继终端对应的标识可以包括以下一项或者多项：中继终端的层2标识/C-RNTI/F1AP ID，CU给中继终端设备分配的临时标识，中继终端所在的服务小区的标识。
S1213：DU将RRCReconfiguration消息发送给Remote UE。
示例性的，RRCReconfiguration消息中可以包括Remote UE ID和PC5 RLC承载之间的映射关系。
S1214：Remote UE给DU发送RRCReconfigurationComplete消息，指示RRC连接配置完成。
S1215.DU向CU发送UL RRC MESSAGE TRANSFER消息，UL RRC MESSAGE TRANSFER消息携带Remote UE给DU发送的RRCReconfigurationComplete消息，从而将Remote UE发送的RRC消息转发给CU。
此外，CU还可以给Relay UE下发适配层配置，包括如下步骤：
步骤Sa1.CU向DU发送DL RRC MESSAGE TRANSFER消息。
其中，CU可以生成RRCReconfiguration消息，该RRCReconfiguration消息包含Relay UE的适配层配置信息，并通过DL RRC MESSAGE TRANSFER消息发送给DU。
步骤Sa2.DU将该RRCReconfiguration消息发送给Relay UE。其中，该RRCReconfiguration消息可以包括Remote UE的local ID信息，Remote UE的DRB ID信息，Uu RLC承载，PC5 RLC承载，中继终端对应的标识信息等信息中的一个或多个，并且这些信息之间具有映射关系。
步骤Sa3.Remote UE给DU发送RRCReconfigurationComplete消息，指示RRC连接配置完成。
步骤Sa4.DU通过UL RRC MESSAGE TRANSFER消息，将Relay UE发送的RRC消息转发给CU。
若上述步骤S1207和步骤S1209中(或者步骤Sb1和步骤Sb2中)，gNB为Remote UE的数据配置了新的Uu RLC承载或者更改了原有的Uu RLC承载，则gNB-CU在发给Relay UE的RRC消息中，可以携带该Uu RLC承载的配置信息。
为了在CU-DU分离架构下支持L2 U2N relay，和现有技术相比，本申请实施例在gNB-DU中引入了适配层以支持L2 U2N relay协议架构。在Remote UE进行初始接入之前，本申请实施例中，还引入Relay UE建立用于Remote UE SRB信令的Uu RLC承载，以及基站为Remote UE分配local ID的流程，以及DU或者CU确定适配层配置的流程。进一步的，本申请实施例针对适配层放置于gNB-DU的情况，设计了Remote UE的初始接入流程，使得Remote UE能够成功接入基站，并建立UE上下文。
结合前述实施例，如图13所示，图12为本申请实施例提供又一种通信方法的示意图，在该方法中，在Uu适配层设置在gNB-DU的情况下，提出了一种Remote UE的inter-DU切换流程，即Remote UE从源DU(Source DU)切换至目标DU(Target DU)的Relay UE，并且源DU和目标DU从属于同一个CU的控制。具体的，图13所示出的方法，包括：
S1301：Remote U)向源DU发送测量报告MeasurementReport。
其中，Remote UE进行测量上报，发送MeasurementReport消息给源DU。其中，测量上报内容中包含Relay UE的ID以及Cell ID信息。
S1302-1：源DU向CU发送UL RRC MESSAGE TRANSFER消息。
其中，源DU将MeasurementReport消息通过F1接口信令UL RRC MESSAGE TRANSFER发送给CU。
S1302-2：切换决策。
其中，CU可以根据Remote UE的测量上报内容，决策将Remote UE切换至接入目标DU(Target DU)下面的Relay UE。
S1303：CU向目标DU发送UE CONTEXT SETUP REQUEST消息。
其中，CU通过给目标DU发送UE CONTEXT SETUP REQUEST，指示目标DU建立该Remote UE的UE上下文。
S1304：目标DU向CU回复UE CONTEXT SETUP RESPONSE消息。该UE CONTEXT SETUP RESPONSE消息可用于指示UE上下文在gNB-DU建立成功。
上述步骤S1303和步骤S1304涉及与Remote UE相关的F1接口信令，因此，在gNB-CU和gNB-DU发送信令的过程中，gNB-CU和gNB-DU将分别为Remote UE分配CU F1AP ID 以及DU F1AP ID，并在信令中携带分配的Remote UE的F1AP ID。同时，在该过程中，DU或者CU也可以分配Remote UE的local ID，并将local ID和F1AP ID进行关联。若由CU分配local ID，则CU将通过步骤S1303的UE CONETEXT SETUP REQUEST消息将CU分好的local ID发送给DU。若由DU分配，则CU通过步骤S1303的UE CONETEXT SETUP REQUEST消息，请求DU分配local ID，DU再通过步骤S1304的UE CONETEXT SETUP RESPONSE消息将分配的local ID发送给CU；或者，DU可以基于内部实现，自主决策进行local ID的分配，并通过步骤S1304的UE CONETEXT SETUP RESPONSE消息将分配的local ID发送给CU，即在步骤S1304的UE CONETEXT SETUP RESPONSE消息中，不需要携带用于请求UD分配local ID的指示信息。
上述步骤S1303和步骤S1304中，还可以生成Remote UE的适配层配置和Relay UE的适配层配置，并且有DU生成配置和CU生成配置两种方案，具体不同配置过程可以参考上述图12所示出的实施例(比如S1209所提出的各种配置方式)。另一种可能的实现方式中，步骤S1303和步骤S1304中可以仅生成Remote UE的适配层配置，Relay UE的适配层配置通过步骤S1307-2所示的Relay UE的UE Context Modification过程生成，类似于图12所示出的实施例中的步骤Sb1和步骤Sb2，在此不再赘述。
S1305：CU向源DU发送UE CONTEXT MODIFICATION REQUEST消息，其中包括CU发送给Remote UE的RRCReconfiguration消息。示例性的，除了现有技术包含的配置信息，RRCReconfiguration消息中还可以包含Remote UE的适配层配置信息(比如Remote UE的DRB ID信息和PC5 RLC承载信息，及其两者之间的映射关系)以及给Remote UE分配的local ID。
S1306：源DU给CU回复UE CONTEXT MODIFICATION RESPONSE消息。
S1307-1：源DU给Remote UE下发CU生成的RRCReconfiguration消息。
S1307-2：可选择地，CU和目标DU可以通过Relay UE的UE Context Modification流程，生成Relay UE的Uu RLC的配置，包括：Relay UE的适配层配置(即Remote UE local ID，DRB ID，Uu RCL以及PC5 RLC承载之间的映射关系)，以及需要的RLC承载配置。
S1308:CU向目标DU发送DL RRC MESSAGE TRANSFER消息。
其中，CU生成RRCReconfiguration消息，承载Relay UE的配置信息，并通过DL RRC MESSAGE TRANSFER消息发送给目标DU。
S1309:目标DU将RRCReconfiguration消息发送给Relay UE。
S1310:Relay UE给目标DU回复RRCReconfigurationComplete消息。
S1311.目标DU通过UL RRC MESSAGE TRANSFER消息转发Relay UE的RRC消息给CU。
S1312.单播连接建立。
其中，若Remote UE和Relay UE之间先前没有单播连接，则Remote UE还需先和Relay UE建立单播连接，Relay UE通过local ID将接上来的Remote UE和基站下发的配置进行匹配。
S1313.Remote UE通过Relay UE的转发RRCReconfigurationComplete消息给目标DU。
其中，Remote UE通过Relay UE发送单播连接的RRCReconfigurationComplete消息。Relay UE识别该Remote UE，并在转发过程中，在承载RRCReconfigurationComplete消息的适配层PDU中，添加local ID，以便让目标DU的适配层能够识别该消息属于Remote UE，并进行正确转发。
S1314.目标DU向CU发送UL RRC MESSAGE TRANSFER消息。
目标DU将Remote UE的RRCReconfigurationComplete消息承载在UL RRC MESSAGE TRANSFER消息中，发送给CU。
S1315.CU指示源DU释放Remote UE的UE上下文。
通过本实施例方法，提出了在CU-DU分离架构下，适配层放置于DU时，Remote UE的inter-DU切换流程，从而使能Remote UE成功接入目标DU下面的Relay UE。和现有的Remote UE执行inter-DU切换流程相比，本实施例中，需要建立Remote UE的UE上下文，还需要进行Relay UE的相关配置。并且，基站在UE上下文建立过程中需分配local ID，并将local ID和Remote UE的F1AP ID进行关联，从而在后续流程中可以识别是哪个Remote UE通过Relay UE转发的RRC消息。
本申请实施例还提供了一种通信方法，其中，给出了Remote UE的UE上下文释放流程。当Remote UE进入RRC IDLE/INACTIVE状态，或者Remote UE离开该Relay UE时，基站需要释放Remote UE的UE上下文，此外，还可能需要更新/释放所连接Relay UE的UE上下文，具体包括：
步骤1：CU给DU发送UE CONTEXT RELEASE COMMAND信息，指示DU释放Remote UE的UE上下文信息。同时，该消息中携带下发给UE的RRCRelease消息。
步骤2：DU将CU生成的RRCRelease消息发送给Remote UE，指示Remote UE释放RRC连接。
步骤3：DU给CU回复UE CONTEXT RELEASE COMPLETE信息，确认Remote UE的UE上下文释放成功。
不同于现有技术，Remote UE释放的同时，还需要考虑Relay UE的UE上下文释放或者更改。在Remote UE的上下文释放后，DU将进一步判断是否需要释放Relay UE的Uu RLC承载或者是否需要释放Relay UE。例如，随着Remote UE的释放，Uu RLC承载无需承载数据，则可以将相应的Uu RLC承载释放；或者Remote UE的释放后，Relay UE没有中继数据也没有自己的数据，则可以进行Relay UE的释放。
若DU判断进行Uu RLC承载的释放，则执行步骤4a～步骤6a的流程；若判断进行Relay UE的释放，则进行步骤步骤4b～步骤6b的流程。
步骤4a：DU判断可以释放Uu RLC承载后，给CU发送UE CONTEXT MODIFICATION REQUIRED消息，指示释放的Uu RLC承载的ID信息。
步骤5a：CU给DU回复UE CONTEXT MODIFICATION CONFIRM消息，携带生成的RRCReconfiguration消息，RRCReconfiguration消息中包含更新后的Relay UE的配置信息。
步骤6a：DU将RRCReconfiguration消息发送给Relay UE。
步骤4b：DU判断可释放Relay UE后，给CU发送UE CONTEXT RELEASE REQUEST消息，指示释放Relay UE。
步骤5b：CU生成Relay UE的RRCRelease消息，并通过DL RRC MESSAGE TRANSFER消息发送给DU。
步骤6b：DU给Relay UE发送RRCRelease消息，指示Relay UE释放和基站的RRC连接。
由上，本实施例所提供的方法，和现有UE上下文释放流程相比，在Remote UE的上下文释放之后，DU还需要判断是否需要对Relay UE进行上下文的更新或者释放。DU判断之后，相应地进行Relay UE的上下文更新或者释放流程。
本申请实施例还提供了一种通信方法，其中，给出了在Uu适配层放置于CU的情况下，Remote UE的初始接入流程。类似地，Uu适配层放置于CU时，在开始初始接入流程之前，还需要：1.Relay UE和DU之间建立用于承载Remote UE的SRB信令的RLC承载；2.基站给Remote UE分配local ID，并告知Relay UE。该方法包括如下：
步骤1.DU和CU之间交互的信令为Relay UE相关的F1接口信令，即Remote UE的信令以container的形式承载在Relay UE的信令中。由于DU上面没有适配层，因此，DU没有办法识别Relay UE上传的数据/信令是否为Remote UE的数据/信令。只有当数据/信令递交到CU的适配层时，基站才可以根据适配层头上的local ID标识识别该数据/信令属于Remote UE，并递交至Remote UE的上层协议层。
步骤2.由CU生成适配层的配置。适配层位于CU，因此比较自然的方式是由CU确定适配层的映射关系配置，同时请求DU建立对应的Uu RLC承载。
步骤3.在数据面，不同承载的数据可以在F1接口隧道上进行复用。F1接口连接CU的适配层和DU的RLC层，适配层上面为复用了不同承载的数据，在上行方向，RLC层直接将复用在Uu RLC承载上的数据通过一个隧道递交给适配层，下行方向类似。特别地，上述隧道应为CU和DU为Relay UE配置的F1-U GTP tunnel。因此，在上下文建立过程中，CU配置上行隧道时，需配置适配层实体和隧道地址之间的映射关系；DU配置下行隧道时，应配置Uu RLC承载ID和隧道地址之间的对应关系。
在该方法中，为了在CU-DU分离架构下支持L2 U2N relay，在CU单元中引入适配层以支持L2 U2N relay协议架构。和图12所示出的实施例相比，由于DU没有办法识别Remote UE的数据，本方案中：1.Remote UE的信令通过承载在Relay UE的F1接口信令中的方式，在DU和CU之间交互；2.Remote UE的数据通过Relay UE的F1接口隧道在DU和CU之间交互。只有当数据或者信令递交到CU的适配层时，才能够识别该数据或者信令属于Remote UE。此外，现有技术中一个承载的数据对应于一个F1接口隧道，该方案中不同承载的数据可以在一个F1接口隧道上复用。
需要说明的是，上述方法实施例中第一网络节点CU或第二网络节点DU的动作可以由图8所示的通信装置80中的处理器801调用存储器802中存储的应用程序代码以指令该第一终端设备执行；本实施例对此不作任何限制。
可以理解的是，以上各个实施例中，由第一网络节点CU实现的方法和/或步骤，也可以由可用于第一网络节点CU的部件(例如芯片或者电路)实现；由第二网络节点DU实现的方法和/或步骤，也可以由可用于第二网络节点DU的部件(例如芯片或者电路)实现。
上述主要从各个设备之间交互的角度对本申请实施例提供的方案进行了介绍。相应的，本申请实施例还提供了通信装置，该通信装置用于实现上述各种方法。该通信装置可以为上述方法实施例中的第一网络节点CU，或者包含上述第一网络节点CU的装置，或者为可用于第一网络节点CU的部件或计算机程序；或者，该通信装置可以为上述方法实施例中的第二网络节点DU，或者包含上述第二网络节点DU的装置，或者为可用于第二网络节点DU的部件或计算机程序。可以理解的是，该通信装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法实施例中对通信装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
图14示出了一种通信装置140的结构示意图。该通信装置140包括收发模块1401和处理模块1402。所述收发模块1401，也可以称为收发单元用以实现收发功能，例如可以是收发电路，收发机，收发器或者通信接口。需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该通信装置140以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该通信装置140可以采用图8所示的通信装置80的形式。
比如，图8所示的通信装置80中的处理器801可以通过调用存储器803中存储的计算机执行指令，使得通信装置80执行上述方法实施例中的通信方法。
具体的，图14中的收发模块1401和处理模块1402的功能/实现过程可以通过图8所示的通信装置80中的处理器801调用存储器803中存储的计算机执行指令来实现。或者，图14中的处理模块1402的功能/实现过程可以通过图8所示的通信装置80中的处理器801调用存储器803中存储的计算机执行指令来实现，图14中的收发模块1401的功能/实现过程可以通过图8中所示的通信装置80中的通信接口804来实现。
由于本实施例提供的通信装置140可执行上述通信方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、设备和方法，可以通过其它的方式实现。例如，以上所描述的设备实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，设备或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
如本申请所使用的，术语“组件”、“模块”、“系统”等等旨在指代计算机相关实体，该计算机相关实体可以是硬件、固件、硬件和软件的结合、软件或者运行中的软件。例如，组件可以是，但不限于是：在处理器上运行的处理、处理器、对象、可执行文件、执行中的线程、程序和/或计算机。作为示例，在计算设备上运行的应用和该计算设备都可以是组件。一个或多个组件可以存在于执行中的过程和/或线程中，并且组件可以位于一个计算机中以及/或者分布在两个或更多个计算机之间。此外，这些组件能够从在其上具有各种数据结构的各种计算机可读介质中执行。这些组件可以通过诸如根据具有一个或多个数据分组(例如，来自一个组件的数据，该组件与本地系统、分布式系统中的另一个组件进行交互和/或以信号的方式通过诸如互联网之类的网络与其它系统进行交互)的信号，以本地和/或远程过程的方式进行通信。
本申请围绕可包括多个设备、组件、模块等的系统来呈现各个方面、实施例或特征。应当理解和明白的是，各个系统可以包括另外的设备、组件、模块等，并且/或者可以并不包括结合附图讨论的所有设备、组件、模块等。此外，还可以使用这些方案的组合。
另外，在本申请实施例中，“示例的”一词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
本申请实施例中，信息(information)，信号(signal)，消息(message)，信道(channel)有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是一致的。“的(of)”，“相应的(corresponding，relevant)”和“对应的(corresponding)”有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是一致的。“系统”和“网络”有时可以混用，在不强调其区别时，其所要表达的含义是一致的，比如，“通信网络”也即是指“通信系统”。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (39)

  1. 一种通信方法，应用于第一网络节点，其特征在于，所述方法包括：
    所述第一网络节点向第二网络节点发送第一信息，所述第一信息用于触发所述第二网络节点为远端终端设备分配本地标识，以及，所述第一网络节点从所述第二网络节点接收第二信息，所述第二信息包括所述第二网络节点为所述远端终端设备分配的本地标识；
    或者，
    所述第一网络节点向所述第二网络节点发送第一信息，所述第一信息包括所述第一网络节点为所述远端终端设备分配的本地标识；
    其中，所述第一网络节点或者所述第二网络节点通过中继终端设备与所述远端终端设备通信。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一网络节点接收所述第二网络节点发送的第三信息；
    所述第三信息包括所述第二网络节点为所述远端终端设备分配的所述远端终端设备在第一接口的标识信息，
    或者，
    所述第三信息包括所述第二网络节点为所述远端终端设备分配的所述远端终端设备在第一接口的标识信息以及所述第二网络节点为所述中继终端设备分配的所述中继终端设备在所述第一接口的标识信息；
    其中，所述第一接口为所述第一网络节点和所述第二网络节点之间的通信接口。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括如下任一操作：
    操作一：
    所述第一网络节点向所述第二网络节点发送第四信息，所述第四信息包括所述远端终端设备的数据无线承载标识DRB ID信息以及第一无线链路控制RLC承载的标识信息，所述远端终端设备的DRB ID信息和所述第一RLC承载的标识信息之间具有对应关系；
    所述第一网络节点接收所述第二网络节点发送的第五信息，所述第五信息包括所述第二网络节点生成的所述第一RLC承载的配置信息；
    其中，所述第一RLC承载为所述远端终端设备和所述中继终端设备之间的承载，所述远端终端设备的DRB ID信息和所述第一RLC承载的标识信息之间具有对应关系；
    或者，
    操作二：
    所述第一网络节点接收所述第二网络节点生成的第五信息，所述第五信息包括：所述远端终端设备的数据无线承载标识DRB ID信息，第一RLC承载的标识信息，以及所述第一RLC承载的配置信息，其中，所述第一RLC承载为所述远端终端设备和所述中继终端设备之间的承载，所述远端终端设备的DRB ID信息和所述第一RLC承载的标识信息之间具有对应关系；
    或者，
    操作三：
    所述第一网络节点向所述第二网络节点发送第四信息，所述第四信息包括所述远端终端设备的数据无线承载标识DRB ID信息，所述远端终端设备的本地标识，以及第二RLC承载的标识信息；
    所述第一网络节点接收所述第二网络节点生成的第五信息，所述第五信息包括所述第二RLC承载的配置信息；
    其中，所述第二RLC承载为所述第二网络节点和所述中继终端设备之间的承载；所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识以及所述第二RLC承载的标识信息之间具有对应关系；
    或者，
    操作四：
    所述第一网络节点接收所述第二网络节点生成的第五信息，所述第五信息包括如下中至少一个：所述远端终端设备的数据无线承载标识DRB ID信息，所述远端终端设备的本地标识，第二RLC承载的标识信息，以及所述第二RLC承载的配置信息；
    其中，所述第二RLC承载为所述第二网络节点和所述中继终端设备之间的承载，所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识以及所述第二RLC承载的标识信息之间具有对应关系。
  4. 根据权利要求3所述的方法，其特征在于，在所述操作二或所述操作四中，所述方法还包括：
    所述第一网络节点向所述第二网络节点发送第四信息，所述第四信息包括所述远端设备的标识信息。
  5. 根据权利要求3或4所述的方法，其特征在于，符合以下中任一：
    所述第四信息还包括上行传输隧道的标识信息，所述上行传输隧道的标识信息与如下中至少一个具有对应关系：所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识，所述远端终端设备的标识信息，以及所述第二RLC承载的标识信息；其中，所述上行传输隧道用于在所述第一接口上，所述第一网络节点从所述第二网络节点接收数据；
    和/或，
    所述第五信息还包括下行传输隧道的标识信息，所述下行传输隧道的标识信息与如下中至少一个具有对应关系：所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识，所述远端终端设备的标识信息，以及所述第二RLC承载的标识信息；其中，所述下行传输隧道用于在所述第一接口上，所述第一网络节点向所述第二网络节点发送数据。
  6. 根据权利要求1-5中任一所述的方法，其特征在于，所述方法还包括：
    所述第一网络节点接收来自于所述中继终端设备的第一指示信息，所述第一指示信息包括所述远端终端设备的标识信息，所述第一指示信息用于请求为所述远端终端设备分配本地标识，所述远端终端设备的本地标识用于在所述第一网络节点控制范围内唯一标识所述远端终端设备，或者，所述远端终端设备的本地标识用于在所述中继终端设备控制范围内唯一标识所述远端终端设备。
  7. 根据权利要求1-6中任一所述的方法，其特征在于，符合如下任一：
    所述第一信息为所述中继终端设备的用户设备上下文修改请求UE CONTEXT MODIFICATION REQUEST消息，所述第二信息为所述中继终端设备的用户设备上下文修改响应UE CONTEXT MODIFICATION RESPONSE消息；
    或者，
    所述第四信息为所述远端终端设备的用户设备上下文建立请求UE CONTEXT  SETUP REQUEST消息，所述第五信息为所述远端终端设备的用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息；
    或者，
    所述第三信息为所述远端终端设备的初始上行RRC消息转移Initial UL RRC Message Transfer消息。
  8. 根据权利要求1-7中任一所述的方法，其特征在于：
    所述第一网络节点包括：无线资源控制RRC协议层，服务数据适配协议SDAP协议层，以及分组数据汇聚层协议PDCP协议层；
    所述第二网络节点包括：无线链路控制RLC协议层，媒体访问控制MAC协议层，以及物理PHY协议层；
    所述第一网络节点和所述第二网络节点包括在一个基站中。
  9. 根据权利要求1，3-6，8中任一所述的方法，其特征在于：在所述远端终端设备从第三网络节点向所述第二网络节点切换的过程中，所述第二网络节点为切换过程中的目标节点，所述第三网络节点为所述切换过程中的源节点，所述第一网络节点控制所述第二网络节点和所述第三网络节点，并且符合如下中任一：
    所述第一信息为所述远端终端设备的用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息，所述第二信息为所述远端终端设备的用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息；
    或者，
    所述第四信息为所述远端终端设备的用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息，所述第五信息为所述远端终端设备的用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息。
  10. 根据权利要求9所述的方法，其特征在于，所述第三网络节点包括：无线链路控制RLC协议层，媒体访问控制MAC协议层，以及物理PHY协议层，所述第一网络节点，所述第二网络节点，以及所述第三网络节点包括在一个基站中。
  11. 根据权利要求3-10中任一所述的方法，所述第四信息或者第五信息还包括第一标识，所述第一标识用于指示与所述第一RLC承载对应所述中继终端设备。
  12. 根据权利要求11所述的方法，所述第一标识为所述中继终端的标识或所述中继终端的服务小区标识或第一网络节点为中继终端分配的标识或第二网络节点为中继终端分配的标识。
  13. 一种通信方法，应用于第二网络节点，其特征在于，所述方法包括：
    所述第二网络节点接收来自于第一网络节点的第一信息，所述第一信息用于触发所述第二网络节点为远端终端设备分配本地标识，以及，所述第二网络节点向所述第一网络节点发送第二信息，所述第二信息包括所述第二网络节点为所述远端终端设备分配的本地标识；
    或者，
    所述第二网络节点接收来自于第一网络节点的第一信息，所述第一信息包括所述第一网络节点为所述远端终端设备分配的本地标识；
    其中，所述第一网络节点或者所述第二网络节点通过中继终端设备与所述远端终端设备通信。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    所述第二网络节点向所述第一网络节点发送第三信息；
    所述第三信息包括所述第二网络节点为所述远端终端设备分配的所述远端终端设备在第一接口的标识信息，
    或者，
    所述第三信息包括所述第二网络节点为所述远端终端设备分配的所述远端终端设备在第一接口的标识信息以及所述第二网络节点为所述中继终端设备分配的所述中继终端设备在所述第一接口的标识信息；
    其中，所述第一接口为所述第二网络节点和所述第一网络节点之间的通信接口。
  15. 根据权利要求113或14所述的方法，其特征在于，所述方法还包括如下任一操作：
    操作一：
    所述第二网络节点接收所述第一网络节点发送的第四信息，所述第四信息包括所述远端终端设备的数据无线承载标识DRB ID信息以及第一无线链路控制RLC承载的标识信息，所述远端终端设备的DRB ID信息和所述第一RLC承载的标识信息之间具有对应关系；
    所述第二网络节点向所述第一网络节点发送第五信息，所述第五信息包括所述第二网络节点生成的所述第一RLC承载的配置信息；
    其中，所述第一RLC承载为所述远端终端设备和所述中继终端设备之间的承载，所述远端终端设备的DRB ID信息和所述第一RLC承载的标识信息之间具有对应关系；
    或者，
    操作二：
    所述第二网络节点向所述第一网络节点发送第五信息，所述第五信息包括：所述远端终端设备的数据无线承载标识DRB ID信息，第一RLC承载的标识信息，以及所述第一RLC承载的配置信息，其中，所述第一RLC承载为所述远端终端设备和所述中继终端设备之间的承载，所述远端终端设备的DRB ID信息和所述第一RLC承载的标识信息之间具有对应关系；
    或者，
    操作三：
    所述第二网络节点接收所述第一网络节点发送的第四信息，所述第四信息包括所述远端终端设备的数据无线承载标识DRB ID信息，所述远端终端设备的本地标识，以及第二RLC承载的标识信息；
    所述第二网络节点向所述第一网络节点发送第五信息，所述第五信息包括所述第二RLC承载的配置信息；
    其中，所述第二RLC承载为所述第二网络节点和所述中继终端设备之间的承载；所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识以及所述第二RLC承载的标识信息之间具有对应关系；
    或者，
    操作四：
    所述第二网络节点向所述第一网络节点发送第五信息，所述第五信息包括：所述远端终端设备的数据无线承载标识DRB ID信息，所述远端终端设备的本地标识，以及第二RLC承载的标识信息；
    其中，所述第二RLC承载为所述第二网络节点和所述中继终端设备之间的承载，所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识以及所述第二RLC承载的标识信息之间具有对应关系。
  16. 根据权利要求15所述的方法，其特征在于，在所述操作二或所述操作四中，所述方法还包括：
    所述第二网络节点接收所述第一网络节点发送的第四信息，所述第四信息包括所述远端设备的标识信息。
  17. 根据权利要求15或16所述的方法，其特征在于，符合以下中任一：
    所述第四信息还包括上行传输隧道的标识信息，所述上行传输隧道的标识信息与如下中至少一个具有对应关系：所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识，所述远端终端设备的标识信息，以及所述第二RLC承载的标识信息；其中，所述上行传输隧道用于在所述第一接口上，所述第一网络节点从所述第二网络节点接收数据；
    和/或，
    所述第五信息还包括下行传输隧道的标识信息，所述下行传输隧道的标识信息与如下中至少一个具有对应关系：所述远端终端设备的DRB ID信息，所述远端终端设备的本地标识，所述远端终端设备的标识信息，以及所述第二RLC承载的标识信息；其中，所述下行传输隧道用于在所述第一接口上，所述第一网络节点向所述第二网络节点发送数据。
  18. 根据权利要求13-17中任一所述的方法，其特征在于符合如下任一：
    所述第一信息为所述中继终端设备的用户设备上下文修改请求UE CONTEXT MODIFICATION REQUEST消息，所述第二信息为所述中继终端设备的用户设备上下文修改响应UE CONTEXT MODIFICATION RESPONSE消息；
    或者，
    所述第四信息为所述远端终端设备的用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息，所述第五信息为所述远端终端设备的用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息；
    或者，
    所述第三信息为所述远端终端设备的初始上行RRC消息转移Initial UL RRC Message Transfer消息。
  19. 根据权利要求13-18中任一所述的方法，其特征在于：
    所述第一网络节点包括：无线资源控制RRC协议层，服务数据适配协议SDAP协议层，以及分组数据汇聚层协议PDCP协议层；
    所述第二网络节点包括：无线链路控制RLC协议层，媒体访问控制MAC协议层，以及物理PHY协议层；
    所述第一网络节点和所述第二网络节点包括在一个基站中。
  20. 根据权利要求13，15-17，19中任一所述的方法，其特征在于：在所述远端终端设备从第三网络节点向所述第二网络节点切换的过程中，所述第二网络节点为切换过程中的目标节点，所述第三网络节点为所述切换过程中的源节点，所述第二网络节点和所述第三网络节点由所述第一网络节点控制，并且符合如下中任一：
    所述第一信息为所述远端终端设备的用户设备上下文建立请求UE CONTEXT  SETUP REQUEST消息，所述第二信息为所述远端终端设备的用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息；
    或者，
    所述第四信息为所述远端终端设备的用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息，所述第五信息为所述远端终端设备的用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息。
  21. 根据权利要求20所述的方法，其特征在于，所述第三网络节点包括：无线链路控制RLC协议层，媒体访问控制MAC协议层，以及物理PHY协议层，所述第一网络节点，所述第二网络节点，以及所述第三网络节点包括在一个基站中。
  22. 根据权利要求15-21中任一所述的方法，所述第四信息或者第五信息还包括第一标识，所述第一标识用于指示与所述第一RLC承载对应所述中继终端设备。
  23. 根据权利要求22所述的方法，所述第一标识为所述中继终端的标识或所述中继终端的服务小区标识或第一网络节点为中继终端分配的标识或第二网络节点为中继终端分配的标识。
  24. 一种通信方法，应用于第一网络节点，其特征在于，所述方法包括：
    所述第一网络节点向第二网络节点发送第六信息，所述第六信息包含第二指示信息，所述第二指示信息指示所述第二网络节点建立所述第二网络节点和中继终端设备之间的第二无线链路控制RLC承载，所述第二RLC承载用于承载第一数据，所述第一数据为远端终端设备与所述第二网络节点或所述第一网络节点之间交互的数据；
    所述第一网络节点接收所述第二网络节点发送的第七信息，所述第七信息包括所述第二RLC承载的配置信息。
  25. 根据权利要求24所述的方法，其特征在于，
    所述第二指示信息包括需要为所述远端设备建立的信令无线承载SRB的信息；
    或者，
    所述第二指示信息包括所述中继终端设备的中继服务授权信息。
  26. 根据权利要求24或25所述的方法，其特征在于，所述第一数据为所述远端终端设备的信令无线承载SRB0或信令无线承载SRB1或信令无线承载SRB2所承载的数据。
  27. 根据权利要求24-26中任一所述的方法，其特征在于：
    所述第六信息为用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息，所述第七信息为用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息；
    或者，
    所述第六信息为用户设备上下文建立请求UE CONTEXT MODIFICATION REQUEST消息，所述第七信息为用户设备上下文建立响应UE CONTEXT MODIFICATION RESPONSE消息。
  28. 根据权利要求24-27中任一所述的方法，其特征在于：
    所述第一网络节点包括：无线资源控制RRC协议层，服务数据适配协议SDAP协议层，以及分组数据汇聚层协议PDCP协议层；
    所述第二网络节点包括：无线链路控制RLC协议层，媒体访问控制MAC协议层，以及物理PHY协议层；
    所述第一网络节点和所述第二网络节点包括在一个基站中。
  29. 一种通信方法，应用于第二网络节点，其特征在于，所述方法包括：
    所述第二网络节点接收第一网络节点发送的第六信息，所述第六信息包含第二指示信息，所述第二指示信息指示所述第二网络节点建立所述第二网络节点和中继终端设备之间的第二无线链路控制RLC承载，所述第二RLC承载用于承载第一数据，所述第一数据为远端终端设备与所述第二网络节点或所述第一网络节点之间交互的数据；
    所述第二网络节点向所述第一网络节点DU发送第七信息，所述第七信息包括所述第二RLC承载的配置信息。
  30. 根据权利要求29所述的方法，其特征在于，
    所述第二指示信息包括需要为所述远端设备建立的信令无线承载SRB的信息；
    或者，
    所述第二指示信息包括所述中继终端设备的中继服务授权信息。
  31. 根据权利要求29或30所述的方法，其特征在于，所述第一数据为所述远端终端设备的信令无线承载SRB0或信令无线承载SRB1或信令无线承载SRB2所承载的数据。
  32. 根据权利要求29-31中任一所述的方法，其特征在于：
    所述第六信息为用户设备上下文建立请求UE CONTEXT SETUP REQUEST消息，所述第七信息为用户设备上下文建立响应UE CONTEXT SETUP RESPONSE消息；
    或者，
    所述第六信息为用户设备上下文建立请求UE CONTEXT MODIFICATION REQUEST消息，所述第七信息为用户设备上下文建立响应UE CONTEXT MODIFICATION RESPONSE消息。
  33. 根据权利要求29-32中任一所述的方法，其特征在于：
    所述第一网络节点包括：无线资源控制RRC协议层，服务数据适配协议SDAP协议层，以及分组数据汇聚层协议PDCP协议层；
    所述第二网络节点包括：无线链路控制RLC协议层，媒体访问控制MAC协议层，以及物理PHY协议层；
    所述第一网络节点和所述第二网络节点包括在一个基站中。
  34. 一种第一网络节点，其特征在于，所述第一网络节点包括：处理器和存储器；
    所述存储器用于存储计算机执行指令，当所述处理器执行所述计算机执行指令时，以使所述通信装置执行如权利要求1-12，24-28中任一项所述的方法。
  35. 一种第二网络节点，其特征在于，所述第二网络节点包括：处理器和存储器；
    所述存储器用于存储计算机执行指令，当所述处理器执行所述计算机执行指令时，以使所述通信装置执行如权利要求13-23，29-33中任一项所述的方法。
  36. 一种网络节点，其特征在于，包括用于执行如权利要求1-12，24-28中的任一项所述方法的模块；或包括用于执行如权利要求13-23，29-33中的任一项所述方法的模块。
  37. 一种通信装置，其特征在于，所述通信装置包括：处理器和接口电路；
    所述接口电路，用于接收计算机执行指令并传输至所述处理器；
    所述处理器用于执行所述计算机执行指令，以使所述通信装置执行如权利要求1-33中任一项所述的方法。
  38. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机程序，当所述计算机程序被计算机执行时使得所述计算机执行权利要求1-33中任一项所述的方法。
  39. 一种无线接入网设备，其特征在于，包括：如权利要求34所述的第一网络节点， 以及，如权利要求35所述的第二网络节点。
PCT/CN2022/124044 2021-10-21 2022-10-09 通信方法、装置及系统 Ceased WO2023066041A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020247016387A KR20240076847A (ko) 2021-10-21 2022-10-09 통신 방법, 장치 및 시스템
JP2024523682A JP7835855B2 (ja) 2021-10-21 2022-10-09 通信方法、装置、及びシステム
EP22882651.7A EP4408116A4 (en) 2021-10-21 2022-10-09 Communication method, device, and system
US18/640,752 US20240267826A1 (en) 2021-10-21 2024-04-19 Communication method, apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111229637 2021-10-21
CN202111229637.4 2021-10-21

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/640,752 Continuation US20240267826A1 (en) 2021-10-21 2024-04-19 Communication method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2023066041A1 true WO2023066041A1 (zh) 2023-04-27

Family

ID=86028622

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/124044 Ceased WO2023066041A1 (zh) 2021-10-21 2022-10-09 通信方法、装置及系统

Country Status (6)

Country Link
US (1) US20240267826A1 (zh)
EP (1) EP4408116A4 (zh)
JP (1) JP7835855B2 (zh)
KR (1) KR20240076847A (zh)
CN (1) CN116017393A (zh)
WO (1) WO2023066041A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025110905A1 (en) * 2023-11-22 2025-05-30 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for relay communication in wireless communication system
WO2025206693A1 (ko) * 2024-03-25 2025-10-02 엘지전자 주식회사 무선 통신 시스템에서 릴레이 통신을 수행하는 방법 및 이를 위한 장치

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230199877A1 (en) * 2021-12-20 2023-06-22 Electronics And Telecommunications Research Institute Operation method of sidelink relay, and sidelink relay therefor
CN119450806A (zh) * 2023-08-04 2025-02-14 维沃移动通信有限公司 Sl多路径建立方法、终端、网络侧设备、芯片及介质
US20250081046A1 (en) * 2023-08-31 2025-03-06 Qualcomm Incorporated Cellular connection over non-cellular access via gateway
CN119562246A (zh) * 2023-09-01 2025-03-04 大唐移动通信设备有限公司 分配本地标识的方法、装置及存储介质
CN119729418A (zh) * 2023-09-27 2025-03-28 大唐移动通信设备有限公司 信息传输方法、装置及终端
CN120456298A (zh) * 2024-02-07 2025-08-08 大唐移动通信设备有限公司 数据传输方法、装置、终端、网络侧设备及存储介质
WO2025178198A1 (ko) * 2024-02-19 2025-08-28 엘지전자 주식회사 릴레이 통신 지원
WO2026029531A1 (ko) * 2024-07-31 2026-02-05 엘지전자 주식회사 릴레이에 기초한 통신

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018027820A1 (zh) * 2016-08-11 2018-02-15 华为技术有限公司 一种链接建立方法及相关设备
CN109792595A (zh) * 2016-09-29 2019-05-21 华为技术有限公司 用于使用中继接入网络的系统和方法
US20190166486A1 (en) * 2016-06-03 2019-05-30 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method and device for relay transmission
CN111526559A (zh) * 2019-02-02 2020-08-11 华为技术有限公司 一种通信方法及装置
CN113498193A (zh) * 2020-04-07 2021-10-12 华为技术有限公司 一种通信方法及设备

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018176416A1 (zh) * 2017-03-31 2018-10-04 华为技术有限公司 中继通信方法、装置和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190166486A1 (en) * 2016-06-03 2019-05-30 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method and device for relay transmission
WO2018027820A1 (zh) * 2016-08-11 2018-02-15 华为技术有限公司 一种链接建立方法及相关设备
CN109792595A (zh) * 2016-09-29 2019-05-21 华为技术有限公司 用于使用中继接入网络的系统和方法
CN111526559A (zh) * 2019-02-02 2020-08-11 华为技术有限公司 一种通信方法及装置
CN113498193A (zh) * 2020-04-07 2021-10-12 华为技术有限公司 一种通信方法及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4408116A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025110905A1 (en) * 2023-11-22 2025-05-30 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for relay communication in wireless communication system
WO2025206693A1 (ko) * 2024-03-25 2025-10-02 엘지전자 주식회사 무선 통신 시스템에서 릴레이 통신을 수행하는 방법 및 이를 위한 장치

Also Published As

Publication number Publication date
US20240267826A1 (en) 2024-08-08
EP4408116A4 (en) 2025-01-15
CN116017393A (zh) 2023-04-25
JP7835855B2 (ja) 2026-03-25
KR20240076847A (ko) 2024-05-30
JP2024539159A (ja) 2024-10-28
EP4408116A1 (en) 2024-07-31

Similar Documents

Publication Publication Date Title
WO2023066041A1 (zh) 通信方法、装置及系统
EP3911019B1 (en) Communication method and apparatus
RU2749847C2 (ru) Способ и система для управления информацией пользователя
US12563616B2 (en) Packet forwarding method, apparatus, and system
CN106162512A (zh) 一种中继承载控制方法和装置
CN116210250A (zh) 一种数据传输方法及装置
WO2017113409A1 (zh) 用户设备接入网络的方法、核心网实体、基站及第一ue
KR20180125450A (ko) 중계 전송 방법과 장치, 및 중계 단말 장비
CN116419339A (zh) 通信方法、装置及系统
WO2016173078A1 (zh) 一种数据中转传输方法、系统和具备中继功能的ue
CN115278603A (zh) 一种通信方法、装置及系统
WO2017118191A1 (zh) 一种控制面信息的传输方法及装置
WO2022037363A1 (zh) 一种计算承载的应用方法及装置
KR20190103382A (ko) 라우팅 방법 및 장치
CN104618849A (zh) 终端的本地交换方法及系统
CN116508356A (zh) 密钥生成方法及装置
WO2021204270A1 (zh) 通信方法及装置
CN113873585B (zh) 用于切换的数据传输的方法和装置
CN115996108A (zh) 一种数据传输方法及相关装置
WO2021213014A1 (zh) 一种通信方法及装置
US20260032752A1 (en) Communication method and communication apparatus
US20250227729A1 (en) Communication method and apparatus
WO2026012039A1 (zh) 一种通信方法、通信装置和通信系统
WO2025167697A1 (zh) 一种通信方法及装置
WO2025139601A1 (zh) 通信方法、装置及系统

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: 22882651

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2024523682

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 202437033790

Country of ref document: IN

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112024007744

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2022882651

Country of ref document: EP

Effective date: 20240425

ENP Entry into the national phase

Ref document number: 20247016387

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112024007744

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20240419