WO2019105483A1 - 一种传输方法和中继节点 - Google Patents

一种传输方法和中继节点 Download PDF

Info

Publication number
WO2019105483A1
WO2019105483A1 PCT/CN2018/118925 CN2018118925W WO2019105483A1 WO 2019105483 A1 WO2019105483 A1 WO 2019105483A1 CN 2018118925 W CN2018118925 W CN 2018118925W WO 2019105483 A1 WO2019105483 A1 WO 2019105483A1
Authority
WO
WIPO (PCT)
Prior art keywords
relay node
data
information
message
layer
Prior art date
Application number
PCT/CN2018/118925
Other languages
English (en)
French (fr)
Inventor
王瑞
刘菁
戴明增
石小丽
朱元萍
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2019105483A1 publication Critical patent/WO2019105483A1/zh

Links

Images

Classifications

    • 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/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • 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

Definitions

  • the present application relates to the field of communications and, more particularly, to a transmission method and relay node.
  • LTE R10 Long Term Evolution Release 10
  • the Relay node has wireless self-backhaul, it saves the trenching and embedding when the traditional base station deploys the wired backhaul link. Cost, while increasing the flexibility of deployment, especially for the initial deployment of 5G and evolving communication systems.
  • the existing R10 Relay can only support relatively simple deployment scenarios, such as a single-hop single-homed base station.
  • R10 Relay Multi-hop scenarios have become an urgent problem to be solved in order to meet the needs of more diverse networks in the future.
  • the present application provides a transmission method and a relay node, which can support a multi-hop scenario in the R10 Relay, thereby meeting the needs of a more diverse network in the future.
  • a transmission method includes: the first relay node sends the first data to a network device by using a first wireless interface according to the attribute information of the first data and the first mapping relationship, a first radio interface is a radio interface that performs data transmission between the first relay node and the network device, where the first mapping relationship is attribute information of the first data and the first data is sent The correspondence between the radio bearers used.
  • the first relay node receives the first data sent by a second relay node by using a second wireless interface, where the second wireless interface a wireless interface that performs data transmission between the first relay node and the second relay node; the first relay node acquires attribute information of the first data, and attribute information of the first data And including at least one of the following information: session connection information, data flow information, information of a radio bearer of the first radio interface, information of a radio bearer of the second radio interface, a message type, and a Node information.
  • the first relay node when the message type of the first data is the first user plane data, receives the The first data sent by the second relay node, where the first data is processed by a PHY protocol layer, a MAC protocol layer, an RLC protocol layer, and a PDCP protocol layer that are peered with the second relay node; Transmitting, by the first relay node, the first data to the network device by using the first wireless interface, where the first data passes through a PDCP protocol layer, an RLC protocol layer, a MAC protocol layer, and the like
  • the PHY protocol layer processes; the first user plane data is data of a terminal device connected to the second relay node.
  • the first data is further processed by an adaptive function, and an adaptive identifier is added, where the adaptive identifier is used by the first relay node to acquire attribute information of the data.
  • the relay node does not need to parse the GTP-U data when receiving, and does not need to perform GTP-U encapsulation when transmitting, which helps to simplify the behavior of the relay node, save processing and processing overhead, and speed up data forwarding.
  • the first relay node when the first data is the first user plane data, receives the second by using the second radio interface.
  • the first data sent by the relay node the first data is processed by a PHY protocol layer, a MAC protocol layer, an RLC protocol layer, a PDCP protocol layer, and a GTP-U protocol layer that are peered with the second relay node.
  • the protocol layer, the MAC protocol layer and the PHY protocol layer process; the first user plane data is data of a terminal device connected to the second relay node.
  • the relay node does not need to perform different processing on different user plane data, and the existing mechanism is used, and the standard work is less changed, and the relay node can learn the user plane data of each terminal device. information.
  • the first relay node when the first data is the first control plane data, the first relay node receives the The first data sent by the second relay node, the first data is processed by a PHY protocol layer, a MAC protocol layer, an RLC protocol layer, and a PDCP protocol layer that are peered with the second relay node;
  • the relay node sends the first data to the network device by using the first wireless interface, the first data passes through a PDCP protocol layer, an RLC protocol layer, a MAC protocol layer, and a PHY protocol that are peered with the network device.
  • Layer processing; the first control plane data is control plane information related to a terminal device accessing the second relay node.
  • the first data is further processed by an adaptive function, and an adaptive identifier is added, where the adaptive identifier is used by the first relay node to acquire attribute information of the data.
  • the transmission method of the embodiment of the present application replaces the GTP-U encapsulation by the function of the adaptation layer, which helps to save the overhead of data encapsulation and decapsulation of the relay node.
  • the first relay node when the first relay node receives the first data sent by the second relay node by using the second wireless interface, The first data is also processed by the NGAP protocol layer that is peered with the second relay node; when the first relay node sends the first data to the network device by using the first wireless interface, The first data is also processed by an NGAP protocol layer that is peered with the network device.
  • control plane information related to the terminal device can be obtained through the processing of the NGAP layer, which helps to simplify the behavior of the relay node, save processing and processing overhead, and speed up data forwarding.
  • the first relay node when the first relay node receives the first data sent by the second relay node by using the second wireless interface, The first data is also processed by the RRC protocol layer that is peered with the second relay node; when the first relay node sends the first data to the network device by using the first wireless interface, The first data is also processed by the RRC protocol layer peering with the network device.
  • the transmission method of the embodiment of the present application is performed by using the RRC layer instead of the NGAP layer, which reduces the process of the relay node parsing and reorganizing the NGAP message, and carries the NGAP message on the SRB for transmission, which helps distinguish the control plane data type.
  • the first relay node receives the first data sent by the terminal device by using a third wireless interface, where the third wireless interface is the first a wireless interface that the relay node communicates with the terminal device; the first relay node acquires attribute information of the first data, and the attribute information of the first data includes at least one of the following information: session connection information And data stream information, information of the radio bearer of the first radio interface, information of a radio bearer of the third radio interface, a message type, and information of the terminal device.
  • the first relay node when the message type of the first data is the second user plane data, the first relay node sends the Transmitting, by the network device, the first data, where the first data is processed by a GTP-U protocol layer, a PDCP protocol layer, an RLC protocol layer, a MAC protocol layer, and a PHY protocol layer, which are peered with the network device;
  • the two user plane data is data of the terminal device.
  • the relay node serves the terminal device and the plurality of relay nodes at the same time, and can distinguish two types of data, and perform more appropriate processing for each data type.
  • the first relay node when the first data is the second control plane data, the first relay node sends the network device to the network device by using the first wireless interface Transmitting the first data, where the first data is processed by an NGAP protocol layer, a PDCP protocol layer, an RLC protocol layer, a MAC protocol layer, and a PHY protocol layer that are peered with the network device; and the second control plane data is The control plane information related to the terminal device.
  • the first mapping relationship is determined by the first relay node; or the first mapping relationship is configured by the network device or the operating and management entity OAM Or the first data carries information for acquiring the first mapping relationship when the first relay node receives the first data received by the first radio interface.
  • the second aspect provides a transmission method, where the method includes: receiving, by the second relay node, second data sent by the terminal device; and the second relay node, according to the attribute information of the second data, and the second mapping relationship Transmitting, by the second wireless interface, the second data to the first relay node, where the second wireless interface is a wireless interface for performing data transmission between the first relay node and the second relay node;
  • the second mapping relationship is a correspondence between the attribute information of the second data and the radio bearer used to send the second data;
  • the attribute information of the second data includes at least one of the following information: session connection information, data Flow information, information of a radio bearer of the second radio interface, a message type, and information of the terminal device.
  • the second relay node when the message type of the second data is the first user plane data, the second relay node sends the information through the second wireless interface
  • the first relay node sends the second data, and the second data passes through a GTP-U protocol layer peered with the network device, a PDCP protocol layer peered with the first relay node, an RLC protocol layer, and a MAC protocol. Layer and PHY protocol layer processing; the first user plane data is data of the terminal device.
  • the relay node does not need to parse the GTP-U data, which helps simplify the behavior of the relay node, saves processing overhead, and speeds up data forwarding.
  • the second relay node when the message type of the second data is the first user plane data, the second relay node sends the information through the second wireless interface
  • the first relay node sends the second data, and the second data is processed by a GTP-U protocol layer, a PDCP protocol layer, an RLC protocol layer, a MAC protocol layer, and a PHY protocol layer, which are peered with the first relay node.
  • the first user plane data is data of the terminal device.
  • the transmission method of the embodiment of the present application carries relevant information through the GTP-U protocol layer, which helps the relay node to forward data.
  • the second relay node when the message type of the second data is the first user plane data, the second relay node sends the information through the second wireless interface Transmitting, by the first relay node, the second data, where the second data is processed by a PDCP protocol layer, an RLC protocol layer, a MAC protocol layer, and a PHY protocol layer, which are peered with the first relay node;
  • the face data is data of the terminal device.
  • the first data is further processed by an adaptive function, and an adaptive identifier is added, where the adaptive identifier is used by the first relay node to acquire attribute information of the data.
  • the relay node does not perform GTP-U encapsulation, but is carried by the adaptive layer identifier, which helps to save the process of data processing by the relay node.
  • a transmission method includes: a second relay node generates first control plane data; and a second relay node sends the first relay node to a first relay node by using a radio bearer of the second radio interface a control plane data, the second radio interface is a radio interface for performing data transmission between the first relay node and the second relay node; and the second relay node is located at the second radio interface
  • the first relay node sends the first control plane data the first control plane data passes through an NGAP protocol layer that is peered with the network device, and the PDCP protocol layer that is equivalent to the first relay node, and the RLC protocol layer. Processing by the MAC protocol layer and the PHY protocol layer; the first control plane data is control plane information related to the terminal device.
  • the second mapping relationship is determined by the second relay node; or the first mapping relationship is performed by the network The device or the operation and management entity OAM configuration; or the first mapping relationship is configured by the first relay node; or the second relay node acquires the first mapping relationship carried by the second data.
  • the network device is a host base station or a third relay node, where the network device is directly or indirectly connected to the first relay node.
  • a relay node for performing the method of the first aspect or any possible implementation of the first aspect.
  • the network device comprises means for performing the method of any of the above-described first or first possible implementations of the first aspect.
  • a relay node for performing the method of any of the possible implementations of the second aspect or the second aspect.
  • the relay node comprises means for performing the method of any of the possible implementations of the second aspect or the second aspect described above.
  • a relay node for performing the method in any of the possible implementations of the third aspect or the third aspect.
  • the relay node comprises means for performing the method of any of the possible implementations of the third aspect or the third aspect described above.
  • another relay node comprising: a transceiver, a memory, and a processor.
  • the transceiver, the memory and the processor are in communication with each other via an internal connection path for storing instructions for executing instructions stored in the memory to control the receiver to receive signals and to control the transmitter to transmit signals
  • the processor executes the instructions stored by the memory, the executing causes the processor to perform the method of the first aspect or any of the possible implementations of the first aspect.
  • another relay node comprising: a transceiver, a memory, and a processor.
  • the transceiver, the memory and the processor are in communication with each other via an internal connection path for storing instructions for executing instructions stored in the memory to control the receiver to receive signals and to control the transmitter to transmit signals
  • the processor executes the instructions stored by the memory, the executing causes the processor to perform the method of any of the possible implementations of the second aspect or the second aspect.
  • another relay node comprising: a transceiver, a memory, and a processor.
  • the transceiver, the memory and the processor are in communication with each other via an internal connection path for storing instructions for executing instructions stored in the memory to control the receiver to receive signals and to control the transmitter to transmit signals
  • the processor executes the instructions stored by the memory, the executing causes the processor to perform the method of any of the possible implementations of the third aspect or the third aspect.
  • a tenth aspect a communication system is provided, the system comprising the relay node in any one of the possible implementations of the fourth aspect or the fourth aspect, and the fifth aspect or the fifth aspect, in any possible implementation manner Relay node; or
  • the system includes the relay node in any one of the possible implementations of the fourth aspect or the fourth aspect, and the relay node in any one of the possible implementations of the sixth aspect or the sixth aspect; or
  • the system includes the relay node in any one of the possible implementations of the seventh aspect or the seventh aspect, and the relay node in any one of the possible implementations of the eighth aspect or the eighth aspect; or
  • the system includes the relay node in any one of the possible implementations of the seventh aspect or the seventh aspect, and the relay node in any of the possible implementations of the ninth aspect or the ninth aspect.
  • a computer program product comprising: computer program code, when the computer program code is executed by a computer, causing the computer to perform any of the first aspect or the first aspect described above A possible implementation.
  • a computer program product comprising: computer program code, when the computer program code is executed by a computer, causing the computer to perform any of the second aspect or the second aspect A possible implementation.
  • a computer program product comprising: computer program code, when the computer program code is executed by a computer, causing the computer to perform any of the third aspect or the third aspect described above A possible implementation.
  • a fourteenth aspect a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • a fifteenth aspect a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of any of the second aspect or the second aspect of the second aspect.
  • a computer readable medium for storing a computer program comprising instructions for performing the method of any of the third aspect or any of the possible implementations of the third aspect.
  • a chip system for use in a relay node, the chip system comprising: one or more processors, one or more memories, and interface circuits, the interface circuit being responsible for the chip system and External information exchange, the one or more memories, the interface circuit and the one or more processors being interconnected by a line, the one or more memories storing instructions; the instructions being by the one or A plurality of processors are executed to perform the operations of the first relay node in the method of the above aspects.
  • a chip system for use in a relay node, the chip system comprising: one or more processors, one or more memories and interface circuits, the interface circuit being responsible for the chip system and External information exchange, the one or more memories, the interface circuit and the one or more processors being interconnected by a line, the one or more memories storing instructions; the instructions being by the one or A plurality of processors are executed to perform the operations of the second relay node in the method of the various aspects described above.
  • Figure 1 shows the control plane protocol stack architecture of the LTE R10 Relay.
  • Figure 2 shows the user plane protocol stack architecture of the LTE R10 Relay.
  • FIG. 3 is a schematic flowchart of a method for accessing a relay node in an LTE R10 Relay.
  • FIG. 4 is a schematic flowchart of a two-hop RN network access method according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of an L3 protocol stack control plane architecture 1-A according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of an L3 protocol stack control plane architecture 1-B according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of an L3 protocol stack control plane architecture 2 according to an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a three-hop RN network access method according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of an L3 protocol stack control plane architecture 1-A-A according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of an L3 protocol stack control plane architecture 1-B-A according to an embodiment of the present application.
  • FIG. 11 is another schematic diagram of the L3 protocol stack control plane architecture 2 in the embodiment of the present application.
  • FIG. 12 is a schematic diagram of an L3 protocol stack control plane architecture 1-A-B according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of an L3 protocol stack control plane architecture 1-B-B according to an embodiment of the present application.
  • FIG. 14 is another schematic diagram of the L3 protocol stack control plane architecture 1-A-A according to the embodiment of the present application.
  • FIG. 15 is another schematic diagram of the L3 protocol stack control plane architecture 1-B-A according to the embodiment of the present application.
  • FIG. 16 is still another schematic diagram of the L3 protocol stack control plane architecture 2 in the embodiment of the present application.
  • FIG. 17 is another schematic diagram of the L3 protocol stack control plane architecture 1-A-B according to the embodiment of the present application.
  • FIG. 18 is another schematic diagram of the L3 protocol stack control plane architecture 1-B-B according to the embodiment of the present application.
  • FIG. 19 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 20 is another schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 21 is a schematic flowchart of a method for a session establishment by a two-hop RN/terminal device through a control plane according to an embodiment of the present application.
  • FIG. 22 is a schematic flowchart of a method for a three-hop RN/terminal device to establish a session through a control plane.
  • FIG. 23 is a schematic flowchart of a method for establishing a session through a control plane by a three-hop RN/terminal device based on the control plane protocol stacks 1-A-B and 1-B-B according to an embodiment of the present application.
  • FIG. 24 is a schematic diagram of the L3 protocol stack user plane architecture 1 in the embodiment of the present application.
  • 25 is a schematic diagram of a data transmission process of an Un1 wireless interface.
  • Figure 26 is a schematic diagram of the RN1 mapping process during data transmission.
  • FIG. 27 is a schematic diagram of the L3 protocol stack user plane architecture 2 in the embodiment of the present application.
  • FIG. 28 is a schematic diagram of the L3 protocol stack user plane architecture 1-A of the embodiment of the present application.
  • 29 is a schematic diagram of a data transmission process of an Un1 wireless interface.
  • FIG. 30 is a schematic diagram of an RN1 mapping process in a data transmission process.
  • FIG. 31 is another schematic diagram of the L3 protocol stack user plane architecture 2 in the embodiment of the present application.
  • FIG. 32 is another schematic diagram of the L3 protocol stack user plane architecture 1-B of the embodiment of the present application.
  • Figure 33 is a schematic diagram of the RN1 mapping process during data transmission.
  • FIG. 34 is a schematic diagram of a protocol stack combination in accordance with an embodiment of the present application.
  • FIG. 35 is a schematic diagram of the flow of a control plane message of the UE 2 accessing the RN 2 according to the embodiment of the present application.
  • FIG. 36 is a schematic diagram of the flow of user plane data of the UE 2 accessing the RN2 according to the embodiment of the present application.
  • FIG. 37 is a schematic flow chart of a control plane message of the UE1 accessing the RN1 according to the embodiment of the present application.
  • FIG. 38 is a schematic diagram of a flow of a user plane message of the UE1 accessing the RN1 according to the embodiment of the present application.
  • FIG. 39 is a schematic block diagram of a relay node according to an embodiment of the present application.
  • FIG. 40 is another schematic block diagram of a relay node according to an embodiment of the present application.
  • FIG. 41 is still another schematic block diagram of a relay node according to an embodiment of the present application.
  • FIG. 42 is still another schematic block diagram of a relay node according to an embodiment of the present application.
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • 5G future 5th Generation
  • NR New Radio
  • the terminal device in the embodiment of the present application may refer to a user equipment, an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or User device.
  • the terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), with wireless communication.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the network device in the embodiment of the present application may be a device for communicating with the terminal device, where the network device may be a base station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) system, or
  • the LTE system is an evolved base station (eNB or eNodeB), and may be a wireless controller in a cloud radio access network (CRAN) scenario, or the network device may be a relay station or an access device.
  • the embodiments of the present application are not limited in terms of a point, an in-vehicle device, a wearable device, and a network device in a future 5G network or a network device in a future evolved PLMN network.
  • FIG. 1 shows the control plane protocol stack architecture of the LTE R10 Relay.
  • the control plane includes a user equipment (User Equipment, UE), a relay node (RN), a donor base station (DeNB), and a Mobility Management Entity (MME) serving the UE (hereinafter referred to as MME- UE), the UE's protocol stack includes a Non-Access Stratum (NAS), a Radio Resource Control (RRC) layer, and a Packet Data Convergence Protocol (PDCP) from top to bottom.
  • NAS Non-Access Stratum
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • the RRC layer, the PDCP layer, the RLC layer, the MAC layer, and the PHY layer, and the protocol stack that communicates with the host base station includes an S1 Application Protocol (S1-AP) layer and a Stream Control Transmission (S1 Application Protocol, Stream Control Transmission).
  • S1-AP S1 Application Protocol
  • S1 Application Protocol, Stream Control Transmission S1 Application Protocol, Stream Control Transmission
  • the base station and the RN communicate with the RN from top to bottom including S1-AP Layer, SCTP layer, IP
  • the protocol stack that communicates with the MME-UE includes an S1-AP layer, an SCTP layer, an IP layer, and a data link layer (also referred to as an L2 layer) from top to bottom.
  • the protocol stack of the MME-UE includes the NAS, the S1-AP layer, the SCTP layer, the IP layer, the L2 layer, and the L1 layer from top to bottom.
  • the R10 relay control plane has a complete protocol stack.
  • the RRC message of the UE is terminated in the RN, and the RN provides a proxy for the S1/X2 message for the UE.
  • the S1 interface is an interface between the host base station and the CN control plane entity.
  • the X2 interface can be an interface between the donor base station and the RN (or RN and RN).
  • FIG. 2 shows the user plane protocol stack architecture of the LTE R10 Relay.
  • the user plane includes a UE, an RN, a donor base station, and a Serving Gateway (SGW)/Public Data Network Gateway (PGW) (hereinafter referred to as SGW-UE/PGW-UE) serving the UE.
  • SGW Serving Gateway
  • PGW Public Data Network Gateway
  • the protocol stack of the UE includes an IP layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from top to bottom; the protocol stack in which the RN communicates with the UE includes a PDCP layer, an RLC layer, a MAC layer, and a PHY from top to bottom.
  • the protocol stack that communicates with the host base station includes a General Packet Radio Service Tunneling Protocol (User Plane (GTP-U) layer and a User Datagram Protocol (UDP) from top to bottom.
  • GTP-U General Packet Radio Service Tunneling Protocol
  • UDP User Datagram Protocol
  • the layer and PHY layer, the protocol stack for communication with the SGW-UE/PGW-UE includes the GTP-U layer, the UDP layer, the IP layer, the L2 layer, and the L1 layer from top to bottom; and the SGW-UE/PGW-UE
  • the IP layer, the GTP-U layer, the UDP layer, the IP layer, the L2 layer, and the L1 layer are included.
  • the R10 Relay user plane also has a complete protocol stack, which can provide the radio data radio bearer (DRB) transmission service for the UE, and can aggregate data of multiple UEs and forward them to the host through the backhaul link. Base station.
  • DRB radio data radio bearer
  • FIG. 3 is a schematic flowchart of a method 100 for a relay node in the LTE R10 Relay. As shown in FIG. 3, the method 100 includes:
  • the relay node turns on the UE mode access donor base station (DeNB), establishes a control plane and a data plane connection, and the purpose is to obtain a DeNB cell list from an operation and management entity (OAM);
  • OAM operation and management entity
  • the RN selects one DeNB cell from the DeNB cell list to access in the relay mode, and the OAM configures the evolved universal mobile communication system LTE cell Terrestrial Radio Access Network Cell Global Identifier (ECGI)
  • ECGI evolved universal mobile communication system LTE cell Terrestrial Radio Access Network Cell Global Identifier
  • the Relay node Because the Relay node has wireless self-backhaul, it saves the cost of laying a wired backhaul link when deploying a traditional base station, and increases the flexibility of deployment, especially for the initial deployment of 5G and evolved communication systems.
  • R10 Relay can only support simple deployment scenarios, such as single-hop single-homed base stations. In order to provide better performance and meet the needs of future networks, it is necessary to study Relays that support multi-hop scenarios.
  • the embodiment of the present application provides a basic protocol stack architecture, and introduces a network access process of a multi-hop relay, a network access process of the UE, and a quality of service (QoS) mapping mechanism and a configuration method based on various protocol stack architectures.
  • QoS quality of service
  • the difference from the R10 Relay is that the UE's data packets pass through multiple RN nodes.
  • the behavior of each node needs to be clear. It can be analyzed from the control plane and the user plane:
  • the wireless interface control plane connection refers to a wireless interface connection between two directly connected nodes for transmitting control plane messages, for example, a radio interface control plane connection between the UE and the RN accessed by the UE.
  • the radio interface control plane connection is called the radio resource control RRC connection.
  • RRC connection For ease of description, only the RRC connection is used as an example of the radio interface control plane connection, and the establishment and message transmission of the radio interface control plane connection. The process is described, but the above process is not limited to the 4G system, nor is it limited to the establishment and management of the RRC connection, and can be applied to the evolved network of 5G and later.
  • the control plane connection between the interface between the access network (RAN) and the core network (CN) is between the directly connected RAN node and the CN node. Interface for transmitting control plane messages.
  • the interface between the RAN and the core network is called an NG interface, which carries the NG Application Protocol (AP), and manages the interface and manages the UE of the access network by transmitting NGAP messages.
  • NG interface which carries the NG Application Protocol (AP)
  • AP NG Application Protocol
  • NGAP NG Application Protocol
  • only the NG interface and the NGAP message are used as an example of the interface and interface message between the RAN and the CN, and the process of establishing the interface between the RAN and the CN and the process of message delivery are described, but the above process is not limited.
  • the access network After the RRC connection establishment of the wireless interface is completed, the access network notifies the core network that a new UE has accessed through the Initial UE message in the NGAP message, and then the core network and the access network perform authentication and/or security activation for the UE, and The context and data transmission resources are subsequently configured for the UE.
  • the RN/UE For the L3 multi-hop RN involved in the embodiment of the present application, after the next hop RN/UE establishes an initial RRC connection with the RN, how does the RN notify the Donor that a new RN/UE accesses the network, and may pass the RRC message or the NGAP.
  • the Initial UE message can be carried in a Signaling Radio Bearer (SRB) or carried in a Data Radio Bearer (DRB) of the RN, if the NGAP message is used.
  • SRB Signaling Radio Bearer
  • DRB Data Radio Bearer
  • the problem of the user plane is how the intermediate node forwards the data packet. For example, for the uplink, it is necessary to distinguish whether the data of the RN or the data of the UE performs different forwarding behaviors, and how to determine the radio bearer of the radio bearer of the data bearer (Radio Bearer, RB) For example, for the downlink, how does the RN distinguish between its own data or the data of the next RN. It refers to the forwarding strategy of the packet, including the identification of the packet, to distinguish the source/destination of the packet as needed; and an overall QoS mapping framework.
  • Radio Bearer Radio Bearer
  • FIG. 4 is a schematic flowchart of a two-hop RN network access method 200 according to an embodiment of the present application. As shown in FIG. 4, the method 200 includes:
  • the second relay node acquires access information, where the access information is used by the second relay node to acquire information required for accessing the first relay node, such as a random access resource.
  • the access assistance information may include any one of the following information or a combination of any one of the following: an access indication, a hop count information, and an RN-specific random access resource.
  • the permission indication is used by the second relay node to determine whether the first relay node can be accessed; the hop count information is used by the second relay node to determine the hop count of the first relay node after accessing the first relay node;
  • the RN-dedicated random access resource is used to indicate the RN-dedicated random access resource provided by the first relay node, and the RN-dedicated random access resource is used only when the RN performs random access, and the ordinary UE cannot use the RN.
  • Dedicated random access resources is used by the second relay node to determine whether the first relay node can be accessed.
  • the first relay node sends a broadcast message to the second relay node, where the access assistance information is carried.
  • the broadcast message is System Information.
  • the second relay node establishes a control plane connection of the second wireless interface.
  • the second wireless interface is a wireless interface that the second relay node communicates with the first relay node.
  • the control plane is connected as an RRC connection.
  • control plane connection establishment process includes the following S2021-S2023.
  • the second relay node sends a random access request message to the first relay node, where the first relay node sends a random access request response to the second relay node.
  • the second relay node sends a connection establishment request message to the first relay node, where the first relay node sends a connection establishment response message to the second relay node.
  • connection setup request message may be an RRC Connection Setup Request message
  • connection setup message may be an RRC Connection Setup message
  • the second relay node sends a connection establishment complete message to the first relay node.
  • connection setup complete message may be an RRC Connection Setup Complete message.
  • the second relay node sends a first uplink NAS message (first NAS message) to the first relay node.
  • the first NAS message is used to indicate a registration request of the second relay node to the core network.
  • the first NAS message may be carried in a message that the control plane connection establishment is complete, such as an RRC connection setup complete message.
  • the first relay node sends a first message to the network device on the first radio interface, where the first message is the first uplink information related to the second relay node on the first radio interface (RN2 associated message) And optionally, the first message carries the first uplink NAS message of the second relay node.
  • the first wireless interface is a wireless interface that the first relay node communicates with the network device.
  • the first message needs to carry the first identifier of the second relay node, where the first relay node and the donor base station identify the second relay node on the first wireless interface.
  • the first identity may be added by an adaptive function (eg, the first identity is present in the adaptation layer header).
  • the first identifier may include any one of the following information or a combination of any one of the following: RN1 RN/UE NGAP ID-Un1 (the first relay node is the device corresponding to the identifier on the first wireless interface.
  • the ID of the NG connection assigned by the bearer the second identifier (other forms of ID, which can be used to identify the device corresponding to the identifier), the SRB identifier/DRB identifier, and the logical channel identifier.
  • the first relay node is on the first radio interface.
  • the first identifier may be different from the UE or the RN, that is, the RN and the UE use the same identifier format; or the identifier distinguishes the UE and the RN, and when the device is the UE, the identifier format of the UE is used, when the device is In the case of the RN, the identity format of the RN is adopted; in addition, if the UE ID in the existing NGAP is applied, the RN1 RN/UE NGAP ID-Un1 is equivalent to the RAN UE NGAP ID.
  • the foregoing second identifier may be any one of the following identifiers or a combination of any one of the following: the device corresponding to the identifier accesses cell identification information (for example, a physical cell identifier PCI or a global cell identifier ECGI), and the identifier Corresponding device identification information (for example, a cell-level radio network temporary identifier C-RNTI), where the identifier corresponds to the identifier information of the RN accessed by the device (optionally, the RN identifier is carried therein, indicating that the accessed base station is the RN
  • the hop count information of the RN to which the device corresponds to the identifier, the identifier assigned by the core network control plane node to the device corresponding to the identifier eg, S-TMSI, GUTI
  • the core network control plane node identifier eg, AMF ID, AMF pointer, AMF group ID, AMF global identifier.
  • the foregoing second identifier may not distinguish between the UE and the RN, that is, the RN uses the same ID format as the UE; in another case, the identifier distinguishes between the UE and the RN, when the device is the UE, The identity format of the UE is adopted. When the device is an RN, the identifier format of the RN is adopted.
  • the host base station is an example of the network device.
  • the description of the implementation manner is performed by using the host base station instead of the network device.
  • the first message may be a message that carries an NG interface application protocol (NGAP) transmitted on the first radio interface, such as an initial UE message.
  • NGAP NG interface application protocol
  • the foregoing NGAP message may be carried on the DRB of the first radio interface or transmitted on the SRB.
  • the first message may be an RRC message.
  • the first message carries the first uplink NAS message sent by the second relay node to the core network, and the host base station sends the first uplink NAS message of the second relay node to the relay service.
  • the core network control plane node is the core network control plane node.
  • the host base station identifies the second relay node based on the first identifier in the first message, and allocates the first terminal identifier, such as the RAN UE NGAP ID, on the NG-C interface to the second relay node.
  • the first terminal identifier such as the RAN UE NGAP ID
  • the host base station saves a correspondence between the first identifier of the second relay node and the first terminal identifier.
  • the first terminal identifier is used by the host base station and/or the core network control plane node to identify the relay node on the NG-C interface.
  • the host base station receives the first message.
  • the RN1 RN NGAP ID-Un1 needs to be replaced with the identifier that the host base station allocates to the second relay node that can identify the second relay node on the NG-C interface, such as the RAN RN NGAP ID.
  • the donor base station stores the mapping relationship between the RN1 RN NGAP ID-Un1 of the second relay node and the RAN RN NGAP ID.
  • the host base station receives a response message of the core network control plane node.
  • the step specifically includes steps S206-208.
  • the host base station learns that the second relay node accesses the network by using the first relay node, and the host base station generates a first NGAP message according to the first message and sends the message to the control node of the core network serving the relay.
  • CN CP_RN such as AMF
  • the first NGAP message carries the first uplink NAS message of the second relay node.
  • the NGAP message is an initial UE message.
  • the core network authenticates and secures the second relay node. After the success, the second relay node is allowed to register. If the failure occurs, the second relay node is denied to register in the network.
  • the core network node sends a second NGAP message to the host base station.
  • the second NAPA message carries a response message of the core network to the first uplink NAS message of the second relay node.
  • the NAS response message is a NAS message indicating that the registration is successful or rejected.
  • the NGAP message is an initial context configuration request.
  • the NGAP message includes an identifier allocated by the core network node for the RN2 to identify the RN2 on the NG-C, for example, an AMF RN NGAP ID.
  • the host base station receives the NGAP message, identifies the RN2 based on the RAN RN NGAP ID included therein, and saves the correspondence between the AMF RN NGAP ID and the RN2.
  • the host base station sends a second message to the first relay node on the first radio interface.
  • the second message carries the first uplink NAS response message of the second relay node.
  • the second message includes at least a portion of the initial context configuration request.
  • the response message received by the host base station on the NG-C includes a second terminal identifier that is allocated by the core network control plane node to the second relay node, for example, an AMF RN NGAP ID, when the host base station is based on the response message.
  • the second message is sent on the first radio interface, the third identifier of the second relay node needs to be carried in the second message, where the first relay node identifies the second relay node.
  • the third identifier may include any one of the following information or a combination of any one of the following: a Donor RN/UE NGAP ID (the host base station allocates an NG connection carried by the device corresponding to the identifier on the first radio interface. ID), a second identifier (other type of ID, which can be used to identify the device corresponding to the identifier), an SRB identifier/DRB identifier, a logical channel identifier, and the first relay node is the device corresponding to the identifier on the first radio interface
  • the third identifier may be different from the UE or the RN, that is, the RN and the UE use the same identifier format; or the identifier distinguishes the UE and the RN, and when the device is the UE, the identifier format of the UE is used, when the device is In the case of the RN, the identity format of the RN is adopted; in addition, if the UE ID in the existing NGAP is applied, the Donor RN/UE NGAP ID is equivalent to the AMF UE NGAP ID. It can be understood that the third identifier can be the same identifier as the first identifier.
  • the host base station replaces the foregoing second terminal identifier with a third identifier of the second relay node.
  • the second message further carries the first identifier of the second relay node.
  • the host base station maintains a mapping relationship between the second terminal identifier and the third identifier and/or the first identifier of the second relay node.
  • the second terminal identifier is used by the host base station and/or the core network control plane node to identify the relay node on the NG-C interface.
  • the second message may be an NGAP message transmitted by the first wireless interface, such as an Initial Context Setup Request, or an RRC message.
  • the foregoing NGAP message may be carried on the DRB of the first radio interface or transmitted on the SRB.
  • the second message may be an RRC message.
  • the first relay node sends an RRC reconfiguration message to the second relay node on the second radio interface.
  • the first relay node sends another RRC message (for example, an RRC message defined by the RN) to the second relay node.
  • another RRC message for example, an RRC message defined by the RN
  • the first relay node may also send other control plane messages related to the second relay node to the host base station, and vice versa. Similar to the processing of the first message in S205, S20z, and S209, the first relay node needs to send a control plane message related to the second relay node to the host base station when the first radio interface sends the message to the host node.
  • the first message is similar, that is, exemplary, and may be an NGAP message or an RRC message; after receiving the control plane message, the host base station may further process the generated NGAP message and send the message to the core network through the NG-C interface.
  • the host base station identifies the RN based on the first identifier in the message received on the first radio interface, and adds a RAN UE NGAP corresponding to the RN in the corresponding NGAP message sent on the NG-C interface. ID.
  • the host base station receives the response message of the NGAP message on the NG-C interface, and generates a response message to the control plane message sent by the first radio interface to the first relay node, where the format of the response message is similar to the second message, that is, For example, it may be an NGAP message or an RRC message.
  • the host base station identifies the RN based on the AMF UE NGAP ID and/or the RAN UE NGAP ID in the response message received on the NG-C interface, and adds the response message sent on the corresponding first radio interface.
  • the first identifier corresponding to the RN is a registered trademark of Cisco Systems, Inc.
  • the core network sends an NGAP message related to the second relay node to the host base station, and the format of the control plane message that triggers the host base station to send the second relay node on the first radio interface is similar to the second message.
  • the host base station identifies the RN based on the AMF UE NGAP ID and/or the RAN UE NGAP ID in the NGAP message received on the NG-C interface, and sends a corresponding control plane message on the first radio interface.
  • a third identifier corresponding to the RN is added.
  • the host base station if the second relay node needs to respond to the control plane message, the format of the response message is similar to the first message; the host base station generates an NG-C interface based on the control plane response message received by the first radio interface. NGAP message.
  • the host base station identifies the RN based on the first identifier in the message received on the first radio interface, and adds a RAN UE NGAP corresponding to the RN in the corresponding NGAP message sent on the NG-C interface. ID.
  • the network access procedure of the two-hop RN is described above with reference to FIG. 4, and the control plane architecture of the second relay node, the first relay node, the network device, and the core network node will be described in detail below.
  • the second relay node is denoted as RN2, the first relay node is denoted as RN1, the network device is denoted as a donor base station (Donor), and the core network node is denoted as CN CP_RN.
  • FIG. 5 shows a schematic diagram of an L3 protocol stack control plane architecture 1-A in accordance with an embodiment of the present application.
  • the L3 protocol stack control plane includes the second relay node (RN2), the first relay node (RN1), the donor base station (Donor), and the core network node (CN-CP_RN, the core network control plane function served by the RN) ).
  • RN2 is a 2-hop RN and RN1 is a 1-hop RN.
  • the radio interface in which RN2 communicates with RN1 is denoted as Un2
  • the radio interface in which RN1 communicates with the donor base station is denoted as Un1
  • the terrestrial interface in which the donor base station communicates with CN-CP_RN is denoted as NG-C.
  • Un2 port The protocol stack in which RN2 communicates with RN1 includes an RRC layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from top to bottom.
  • RRC layer there is a NAS layer above the RRC layer, and the NAS layer is responsible for the corresponding process negotiated with the core network. Therefore, the NAS message is transparently transmitted to the CN-CP_RN through the RAN hop nodes (for example, the RN1 and the donor base station), and is performed by the CN-CP_RN. Parsing and processing.
  • the functions of the PDCP layer include transmission of user data/RRC messages, encryption and decryption, in-order delivery, and the like.
  • the functions of the RLC layer include transmission of upper protocol data unit (PDU), RLC re-establishment, cascading/segmentation and reassembly of RLC SDU (this function is available in LTE, but the future evolved RAT may cancel the function, or The function is moved to other protocol layers) and so on.
  • the functions of the MAC layer include data scheduling (such as priority processing and scheduling of data of different UEs, or priority processing of different logical channels (LC) of the same UE and scheduling of data), belonging to one or more LCs. Multiplexing/demultiplexing of MAC SDU.
  • the PHY is responsible for transmitting the upper layer data through the wireless resources.
  • the RRC message is carried on the SRB of the radio interface, and each SRB has a dedicated PDCP entity, an RLC entity, and a corresponding MAC layer logical channel.
  • Un2 port The protocol stack in which RN1 communicates with RN2 is peered with the protocol stack of RN2, and includes the RRC layer, the PDCP layer, the RLC layer, the MAC layer, and the PHY layer from top to bottom. The functions of each layer are similar to those of RN1.
  • the RN1 interprets the RRC message received on the Un2 port, and performs processing (for example, reading the RRC information content), and may trigger the generation of the corresponding NGAP message, and the DRB that is carried in the Un1 port is sent to the host base station. If the RRC message received by the Un2 port includes the NAS PDU, the RN2 encapsulates the NAS PDU in the NGAP message and sends the host base station through the Un1 port.
  • the RN1 For the downlink DL, the RN1 generates an RRC message that is sent to the RN2, and is sent to the RN2 through the Un2 interface after being processed by the lower layer protocol stack. If the NGAP message received by the Un1 port includes the NAS message, the RN1 passes the Un2 port. The RRC message is sent to RN2.
  • Un1 port The protocol stack of RN1 and host communication includes the NGAP layer, the SCTP layer (optionally), the IP layer (optionally), and the Service Data Adaptation Protocol (SDAP) layer from top to bottom. Alternatively, it can be configured as a transparent transmission, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer.
  • the generated NGAP message (which may include the NAS message), optionally further processed by the SCTP layer and/or the IP layer (optionally), carried in the DRB packet through the Un1 port Send to the host base station.
  • the RN1 receives the data packet sent by the host base station on the Un1 interface, and obtains the NGAP message carried in the data packet, and transmits the NGAP message to the upper layer NGAP protocol layer for processing (optionally, the SCTP layer processing and/or IP layer processing).
  • the processed NGAP message content (which may include the NAS message) is sent to the protocol layer of the Un2 port.
  • the NAS message carried in the NGAP message received by the Un1 port is sent to the RRC layer of the Un2 port.
  • the DRB of the RN1 on the Un1 port may carry any one of the following types of data or a combination of any of the following: data of the RN1, data of the UE served by the RN1, data of the RN2, data of the UE served by the RN2, and data of other RNs.
  • the data of the UE served by the other RN, the NGAP message generated by the RN1 for the UE it serves, the GTP-U packet encapsulated by the RN1 for the UE it serves, and the NGAP message generated by the RN2 for the UE it serves (part of the message)
  • the RN2 may be modified and/or replaced by the RN1, and the RN2 encapsulates the GTP-U data packet encapsulated by the UE (the part of the message may be modified and/or replaced by the RN1), and the other RN generates the UE for the UE it serves.
  • NGAP message (part of the message may be modified and/or replaced by RN1), and the other RN encapsulates the GTP-U packet encapsulated by the UE (the part of the message may be modified and/or replaced by RN1),
  • the RN1/substitute base station may need to perform the distinguishing process. Therefore, it is necessary to be able to identify the different types of data packets, which may be implemented by any one of the following methods or a combination of any of the following. :
  • the first adaptive identifier may include any one of the following information or a combination of any multiple: two-hop RN identifier and/or hop count information (for identifying RN2), and second UE identifier (for Identifying the RN2 served UE), one hop RN identity and/or hop count information (for identifying RN1), first UE identity (for identifying the UE served by RN1), three hop RN identity and/or hop count information (using For the three-hop, four-hop or even n-hop RNs that transmit data through RN2 and RN1, the third UE identifier (for identifying the multi-hop RN service), the NGAP message type, the XnAP message type, and the GTP-U message type (belongs to NG-U or Xn-U), and user plane packet type.
  • two-hop RN identifier and/or hop count information for identifying RN2
  • second UE identifier for Identifying the RN2 served UE
  • the process of adding an adaptive identity to an upstream packet and parsing the identity of the downstream packet is referred to as an adaptive function.
  • the adaptive function may be included in an existing protocol layer, such as an SDAP layer/PDCP layer/RLC layer/MAC layer/PHY layer; or the adaptive function may be separately deployed in a protocol layer, for example, referred to as adaptive (Adaptation, referred to as Adapt) layer.
  • the adaptation layer may be deployed between the NGAP layer and the PDCP layer, or between the PDCP layer and the RLC layer, or between the RLC layer and the MAC layer, or between the MAC and PHY layers.
  • Un1 port The protocol stack of the host base station communicating with RN1 is peered with RN1, including the NGAP layer, the SCTP layer (optionally), the IP layer (optionally), and the SDAP layer from top to bottom (optionally, configurable For transparent transmission, PDCP layer, RLC layer, MAC layer and PHY layer. It should be noted that since the RN1 and the host base station are used for the protocol stack peering on the Un1 port, if the adaptive function needs to be presented, the presentation manner is the same, and the description of the RN1 is referred to.
  • the host base station receives the data packet sent by the RN1 on the Un1 interface, and performs processing (for example, acquiring the DRB identifier corresponding to the data packet by using the adaptive layer function, or the LC identifier, or any one of the following identifiers or Any combination of multiple: RN2 identifier, NGAP message type, and hop count information of RN2, etc., after which the NGAP message is obtained and passed to the upper NGAP protocol layer for processing (optionally, the SCTP layer is processed and/or IP layer processing).
  • the processed NGAP message content is sent to the NGAP layer of the NG-C interface. If the NGAP message received by the Un1 port contains the NAS PDU, the host eNB encapsulates the NAS PDU in an NGAP message and sends it to the CN-CP_RN through the NG-C interface.
  • the eNB sends the NGAP message to the RN2, and further passes the SCTP layer processing and/or the IP layer processing (optionally), and performs adaptive layer processing (for example, adding the RN2 identifier, adding the NGAP message type). , or add other information content, and further encapsulation, etc., carried in the DRB data packet, processed by the lower layer protocol stack, and sent to the RN1 through the Un1 port.
  • the RN2 associated NGAP message sent by the core network received on the NG-C interface may be converted into an NGAP message sent to the RN1 on the Un1 radio interface.
  • the host base station converts the RN2 message related to the RN2 received on the Un1 radio interface into an NGAP message on the NG-C, and then sends the message to the core network.
  • the processing of the host base station may be similar to the R10 Relay technology.
  • the content of the NGAP message is kept unchanged, and the NGAP ID identifying the RN2 in the NGAP message is replaced.
  • the RAN RN NGAP ID is allocated to the RN1
  • the AMF UE NGAP ID is allocated to the host base station.
  • the host base station sends a message corresponding to the NGAP message on the NG-C port, the RAN UE NGAP ID is used.
  • the RN1 can generate an XnAP message associated with the RN2, and the RN1 sends or receives an XnAP message sent by the host base station to the host base station on the Un1 interface, and the host base station is on the Xn-C interface.
  • the XnAP message related to the RN2 is sent or received to other base stations, or the host base station sends or receives an XnAP message related to the RN2 sent by other RNs to other RNs on other radio interfaces.
  • the processing of the XnAP message related to the RN2 by the donor base station is similar to the processing of the NGAP message, for example, the replacement of the UE XnAP ID, and possibly the replacement of the content carried on the IP header/SCTP header of the IP address, port number, and the like. .
  • the first message and the second message of the Un1 interface are in the form of an NGAP message, and the NGAP message is carried in a data packet carried on the DRB.
  • FIG. 6 shows a schematic diagram of an L3 protocol stack control plane architecture 1-B in accordance with an embodiment of the present application.
  • the L3 protocol stack control plane includes the second relay node (RN2), the first relay node (RN1), the donor base station (Donor), and the core network node (CN-CP_RN, the core network control plane function served by the RN) ).
  • RN2 is a 2-hop RN and RN1 is a 1-hop RN.
  • the radio interface in which RN2 communicates with RN1 is denoted as Un2, the radio interface in which RN1 communicates with Donor is denoted as Un1, the terrestrial interface in which Donor communicates with CN-CP_RN is denoted as NG, and the control plane thereof is denoted as NG-C.
  • Un2 port The protocol stack in which RN2 communicates with RN1 includes an RRC layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from top to bottom.
  • RRC layer there is a NAS layer above the RRC layer, and the NAS layer is responsible for the corresponding process of negotiating with the core network. Therefore, the NAS message is transparently transmitted to the core network node CN-CP_RN through the RAN hop nodes (for example, RN1 and the donor base station). -CP_RN parsing and processing.
  • Un2 port The protocol stack in which RN1 communicates with RN2 is peered with the protocol stack of RN2, and includes the RRC layer, the PDCP layer, the RLC layer, the MAC layer, and the PHY layer from top to bottom. The functions of each layer are similar to those of RN1.
  • the RRC layer of the RN1 interprets the RRC message received by the Un2 port, and after processing (for example, reading the RRC information content), the corresponding NGAP message may be triggered, and the SRB carried in the Un1 port is sent to Host base station. If the RRC message received by the Un2 port includes the NAS PDU, the RN2 encapsulates the NAS PDU in the NGAP message and sends the host base station through the Un1 port.
  • the RN1 For the downlink DL, the RN1 generates an RRC message that is sent to the RN2, and is sent to the RN2 through the Un2 interface after being processed by the lower layer protocol stack. If the NGAP message received by the Un1 port includes the NAS message, the RN1 passes the Un2 port. The RRC message is sent to RN2.
  • the protocol stack in which RN1 communicates with the host includes an NGAP layer, an SCTP layer (optionally), an IP layer (optionally), an RRC layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from top to bottom.
  • the RRC layer may have an adaptive function; or the adaptive function may be included in an existing protocol layer, such as a PDCP layer/RLC layer/MAC layer/PHY layer; or the adaptive function is deployed in a separate protocol layer.
  • the location of the protocol layer may be between the RRC layer and the PDCP layer, or between the PDCP and RLC layers, or between the RLC layer and the MAC layer, or between the MAC layer and the PHY layer.
  • the PDCP layer/RLC layer/MAC layer/PHY layer is a protocol layer shared by the RAN control plane and the user plane, if the adaptive function is deployed in these protocol layers, a unified adaptive function scheme is adopted for the control plane and the user plane. Provided the possibility.
  • the generated NGAP message (which may include the NAS message) is processed by the SCTP layer and/or processed by the IP layer (optionally), and the bearer is sent to the host base station through the Un1 port in the RRC message.
  • the RN1 receives the RRC message sent by the host base station on the Un1 port, performs processing, and obtains the NGAP message part thereof, and transmits the NGAP message part to the upper layer NGAP protocol layer for processing (optionally, the SCTP layer processing and/or Or IP layer processing).
  • the processed NGAP message content (which may include the NAS message) is sent to the NGAP layer of the Un2 port.
  • the SRB of RN1 on the Un1 interface may carry any one of the following information/messages or a combination of any of the following: RRC message of RN1, NG1 message generated by RN1 for the UE it serves, and RN2 generated by the UE it serves NGAP message (part of the content of the message may be modified and/or replaced by RN1), and the other RN generates an NGAP message for the UE it serves (part of the message may be modified and/or replaced by RN1), and RN1 is The XnAP message generated by the serving UE, the XnAP message generated by the RN2 for the UE it serves (the part of the message may be modified and/or replaced by RN1), and the XnAP message generated by the UE served by the other RN (the message) Some of the content can be modified and/or replaced by RN1). After receiving the RRC message of the different types on the RN1, the RN1 and the eNB may need to perform the distinguishing process. Therefore, the
  • the second adaptive identifier may include any one of the following information or a combination of any multiple: two-hop RN identifier and/or hop count information (for identifying RN2), and second UE identifier (for Identifying the RN2 served UE), one hop RN identity and/or hop count information (for identifying RN1), first UE identity (for identifying the UE served by RN1), three hop RN identity and/or hop count information (using The third UE identifier (the UE for identifying the three-hop RN service), the NGAP message type, the XnAP message type, and the RRC message type are used to identify three-hop, four-hop, or even n-hop RNs that transmit data through RN2 and RN1.
  • the process of adding an adaptive identity to the uplink RRC message and parsing the identity of the downlink RRC message is referred to as an adaptive function.
  • the adaptive function may be included in an existing protocol layer, such as an RRC layer/PDCP layer/RLC layer/MAC layer/PHY layer; or the adaptive function may be separately deployed in a protocol layer, for example, referred to as adaptive (Adaptation, referred to as Adapt) layer.
  • the adaptation layer may be deployed between the NG layer and the RRC layer, or between the RRC layer and the PDCP layer, or between the PDCP layer and the RLC layer, or between the RLC layer and the MAC layer. Or deployed between the MAC and PHY layers.
  • Un1 port The protocol stack of the host base station communicating with RN1 is peered with RN1, including the NGAP layer, the SCTP layer (optionally), the IP layer (optionally), the RRC layer, the PDCP layer, the RLC layer, and the MAC from top to bottom. Layer and PHY layer. It should be noted that since the RN1 and the host base station are used for the protocol stack peering on the Un1 port, if the adaptive function needs to be presented, the presentation manner is the same, and the description of the RN1 is referred to.
  • the host base station receives the RRC message sent by the RN1 on the Un1 port, and performs processing (for example, acquiring the RN2 identifier, acquiring the RRC message type, obtaining the SRB identifier, or acquiring other information content, and further decapsulating, etc.)
  • the NGAP message part is obtained and passed to the upper NGAP protocol layer for processing (optionally, through SCTP layer processing and/or IP layer processing).
  • the processed NGAP message content is sent to the NGAP layer of the NG-C interface. If the NGAP message received by the Un1 port contains the NAS PDU, the host base station encapsulates the NAS PDU in the NGAP message and sends it to the CN-CP_RN through the NG-C interface.
  • the eNB sends the NGAP message to the RN2, and further passes the SCTP layer processing and/or the IP layer processing (optionally), and carries the RRC message through the RRC layer processing (for example, adding the RN2 identifier, adding The SRB identifier, the RRC message type is added, or other information content, and further encapsulation are added.
  • the SRB is sent to the RN1 through the Un1 port.
  • RN2 associated NGAP/XnAP message (RN2 associated NGAP/XnAP message) that may be received on the NG-C/Xn-C interface may be converted to the RN1 on the Un1 radio interface.
  • the NGAP/XnAP message, the processing of the donor base station is similar to the processing under the 1-A architecture, with reference to the description of the 1-A architecture.
  • the first message and the second message of the Un1 port are in the form of an NGAP message carried in the RRC message.
  • FIG. 7 shows a schematic diagram of an L3 protocol stack control plane architecture 2 in accordance with an embodiment of the present application.
  • the L3 protocol stack control plane includes the second relay node (RN2), the first relay node (RN1), the donor base station (Donor), and the core network node (CN-CP_RN, the core network control plane function served by the RN) ).
  • RN2 is a 2-hop RN and RN1 is a 1-hop RN.
  • the radio interface in which RN2 communicates with RN1 is denoted as Un2
  • the radio interface in which RN1 communicates with Donor is denoted as Un1
  • the terrestrial interface in which Donor communicates with CN-CP_RN is denoted as NG-C.
  • Un2 port The protocol stack in which RN2 communicates with RN1 includes an RRC layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from top to bottom.
  • RRC layer there is a NAS layer above the RRC layer, and the NAS layer is responsible for the corresponding process negotiated with the core network. Therefore, the NAS message is transparently transmitted to the core network control plane node serving the RN through the RAN hop nodes (for example, the RN1 and the donor base station).
  • CN-CP_RN is parsed and processed by CN-CP_RN.
  • the functions of the RRC layer include RRC connection control, receiving system messages, mobility management, NAS message transmission, and the like.
  • Un2 port The protocol stack in which RN1 communicates with RN2 is peered with the protocol stack of RN2, and includes the RRC layer, the PDCP layer, the RLC layer, the MAC layer, and the PHY layer from top to bottom. The functions of each layer are similar to those of RN1.
  • the RRC layer of the RN1 interprets the RRC message received at the Un2 port, and performs processing (for example, extracting some information, or adding some information content, or further encapsulating) and transmitting the protocol to the Un1 port. Stack processing. If the RRC message received by the Un2 port includes the NAS PDU, the RN1 transparently transmits the NAS PDU to the RRC layer protocol stack of the Un1 port of the RN2, and the RN2 transparently transmits the NAS PDU to the host base station at the Un1 port.
  • the RN1 generates an RRC message sent to the RN2 based on the RN2 associated message RRC message received by the Un1 port, sends the RRC message to the RN2, and sends the RRC message to the RN2 through the Un2 port.
  • the protocol stack in which RN1 communicates with the host includes the RRC layer, the PDCP layer, the RLC layer, the MAC layer, and the PHY layer from top to bottom.
  • the RRC layer may have an adaptive layer function; or the adaptive function may be included in an existing protocol layer, such as a PDCP layer/RLC layer/MAC layer/PHY layer; or the adaptive function is deployed in a separate protocol layer.
  • the location of the protocol layer may be between the RRC layer and the PDCP layer, or between the PDCP and RLC layers, or between the RLC layer and the MAC layer, or between the MAC layer and the PHY layer.
  • the PDCP layer/RLC layer/MAC layer/PHY layer is a protocol layer shared by the RAN control plane and the user plane, if the adaptive function is deployed in these protocol layers, a unified adaptive function scheme is adopted for the control plane and the user plane. Provided the possibility.
  • the RRC layer protocol stack of the Un1 interface receives the RRC information transmitted by the Un2 port protocol stack, and performs processing (for example, adding an RN2 identifier, adding an RRC message type, adding an SRB identifier, or adding other information content, and Further encapsulation, etc.) is passed to the underlying protocol stack.
  • processing for example, adding an RN2 identifier, adding an RRC message type, adding an SRB identifier, or adding other information content, and Further encapsulation, etc.
  • the RN1 receives the RRC message sent by the host base station on the Un1 port, and performs processing (for example, acquiring the RN2 identifier, acquiring the RRC message type, obtaining the SRB identifier, or acquiring other information content, and further decapsulating, etc.) , passed to the protocol stack of RN1 at the Un2 port.
  • processing for example, acquiring the RN2 identifier, acquiring the RRC message type, obtaining the SRB identifier, or acquiring other information content, and further decapsulating, etc.
  • the RRC layer adaptive layer function may include adding/acquiring RN2 identifier, adding/acquiring RRC message type, adding/acquiring SRB identifier, or adding/acquiring other information content, and further encapsulating/decapsulating.
  • the above adaptive layer function can also be implemented by defining a separate adaptation layer independent of the RRC layer.
  • the SRB of the RN1 on the Un1 interface may carry any one or any combination of the following types of information: RRC message of RN1, UE related RRC message served by RN1 (RN1 generation), RRC message related to RN2 (RN1 generation) RN2-related UE-related RRC message (RN2 generation, possibly through RN1 modification) data, other RN-related RRC messages (RN1 generation), and other RN-served UE-related RRC messages (other RN generation may pass Changes to RN1).
  • the RN1/substitute base station may need to perform the distinguishing process. Therefore, it is necessary to be able to identify the different types of data packets, which may be in any one of the following ways or a combination of any of the following. achieve:
  • the third adaptive identifier may include any one of the following information or a combination of any multiple: two-hop RN identifier and/or hop count information (for identifying RN2), and the first UE identifier (for Identifying the RN2 served UE), one hop RN identification and/or hop count information (for identifying RN1), second UE identity (for identifying the RN1 served UE), multi-hop RN identification and/or hop count information (using The third UE identifier (the UE used to identify the multi-hop RN service) and the RRC message type are used to identify the three-hop, four-, and n-hop RNs that pass data through RN2 and RN1.
  • the process of adding an identity to an uplink RRC message and resolving the identity of the downlink RRC message is referred to as an adaptive function.
  • the adaptive function may be included in an existing protocol layer, such as an RRC layer/PDCP layer/RLC layer/MAC layer/PHY layer; or the adaptive function may be separately deployed in a protocol layer, for example, referred to as adaptive (Adaptation, referred to as Adapt) layer.
  • the adaptation layer may be deployed between the RRC layer and the PDCP layer, or between the PDCP layer and the RLC layer, or between the RLC layer and the MAC layer, or between the MAC and PHY layers.
  • Un1 port The protocol stack in which the host base station communicates with RN1 is peered with RN1, and includes an RRC layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from top to bottom. It should be noted that since the RN1 and the host base station are used for the protocol stack peering on the Un1 port, if the adaptive function needs to be presented, the presentation manner is the same, and the description of the RN1 is referred to.
  • the RRC layer protocol stack of the host base station receives the RRC information sent by the RN1, and performs processing (for example, acquiring the RN2 identifier, acquiring the RRC message type, obtaining the SRB identifier, or acquiring other information content, and further decapsulating After the NG-C interface is sent to the CN-CP_RN. If the RRC message received by the Un1 port contains the NAS PDU, the host eNB encapsulates the NAS PDU in an NGAP message and sends it to the CN-CP_RN through the NG-C interface.
  • the eNB sends the RRC message sent to the RN2 to the RRC layer (for example, adding the RN2 identifier, adding the SRB identifier, adding the RRC message type, or adding other information content, and further encapsulating, etc.) to the lower layer protocol stack. After processing, it is sent to RN1 through the Un1 port.
  • the RRC layer for example, adding the RN2 identifier, adding the SRB identifier, adding the RRC message type, or adding other information content, and further encapsulating, etc.
  • the first message and the second message of the Un1 port are in the form of an RRC message.
  • FIG. 8 shows a schematic flowchart of a three-hop RN network access method 300 according to an embodiment of the present application. As shown in FIG. 8, the method 300 includes:
  • the third relay node acquires access assistance information, where the access assistance information is used by the third relay node to acquire information required to access the second relay node, such as a random access resource.
  • the content of the access assistance information refers to the description in S201.
  • the third relay node establishes a control plane connection of the third wireless interface.
  • the third wireless interface is a wireless interface that the third relay node communicates with the second relay node.
  • the control plane is connected as an RRC connection. Specifically, the step is similar to S202, and details are not described herein again.
  • the third relay node sends a first uplink NAS message (second NAS message) to the second relay node.
  • the second NAS message is used to indicate a registration request of the third relay node to the core network.
  • the second NAS message may be carried in the last uplink message established by the control plane connection, for example, an RRC connection setup complete message.
  • the second relay node sends a third message to the first relay node, where the third message is an uplink first message related to the third relay node (RN3 associated message).
  • the third message is used to indicate that the third relay node accesses the network.
  • the third message carries the first uplink NAS message of the third relay node.
  • the third message needs to carry a fourth identifier of the third relay node, where the second relay node and/or the first relay node identify the third relay node on the second radio interface.
  • the fourth identifier may be added by an adaptive function (eg, the fourth identifier is present in the adaptive layer header).
  • the fourth identifier may include any one of the following information or a combination of any one of the following: RN2 RN/UE NGAP ID-Un2 (the second relay node is the device corresponding to the identifier on the second wireless interface.
  • For the content of the second identifier refer to the description in S205.
  • the fourth identifier may be different from the UE or the RN, that is, the RN and the UE use the same identifier format; or the identifier distinguishes the UE and the RN, and when the device is the UE, the identifier format of the UE is adopted, when the device is In the case of the RN, the identity format of the RN is adopted; in addition, if the UE ID in the existing NGAP is applied, the RN2 RN/UE NGAP ID-Un2 is equivalent to the RAN UE NGAP ID.
  • the third message may be an RRC message and is carried on the SRB of the second radio interface (the second relay node).
  • the third message may be an NGAP message carried on the second radio interface, such as an initial UE message Initial UE message.
  • the foregoing NGAP message may be carried on the DRB of the second radio interface or transmitted on the SRB.
  • a possible process is: parsing part or all information of the third message, and learning the third relay node (ie, a new RN) Accessing the network by the second relay node, the first relay node sends a fourth message to the network device according to the third message, where the fourth message is used to indicate that the third relay node accesses the network;
  • a possible processing the third message is not parsed, and the third message is transparently transmitted to the network device as a fourth message, which is simply referred to as a transparent transmission.
  • the fourth message carries the first uplink NAS message of the third relay node.
  • the fourth message needs to carry a first identifier of the third relay node, where the first relay node and/or the host base station identifies the third relay node on the first wireless interface.
  • the first identity may be added by an adaptive function (eg, the first identity is present in the adaptation layer header).
  • the first relay node identifies the third relay node based on the fourth identifier in the third message, and allocates, by the third relay node, the third relay node on the first wireless interface.
  • a logo identifies the third relay node based on the fourth identifier in the third message, and allocates, by the third relay node, the third relay node on the first wireless interface.
  • the first relay node saves a correspondence between the fourth identifier of the third relay node and the first identifier.
  • the first identifier refer to S205, and details are not described herein again.
  • the third message is an NGAP message carried in the second radio interface
  • the RN2 RN/UE NGAP ID-Un2 carried in the second relay node is a unique identifier in the second relay node
  • the first relay node receives After the third message, the RN2 RN/UE NGAP ID-Un2 needs to be replaced with the identifier of the third relay node that can be identified by the first relay node for the third relay node.
  • RN1 RN/UE NGAP ID-Un1 The first relay node stores the mapping relationship between the RN2 RN/UE NGAP ID-Un2 of the third relay node and the RN 1 RN/UE NGAP ID-Un1.
  • the information carried by the first identifier cannot distinguish the hop count information of the RN corresponding to the identifier, and the host base station cannot know that the relay node of the access network is a 2-hop RN based on the first identifier.
  • the second relay node the 3-hop RN (for example, the third relay node), or the RN with the hop count greater than 3, therefore, if the host base station needs to know the topology of the network (for example, the third relay node accesses the second The relay node, which in turn transmits signaling and/or data through the first relay node, needs to send the fourth message to the first relay node, and further prompts that the fourth message is also related to the second relay node.
  • One possible way is to further carry the first identifier of the second relay node in the fourth message; another possible manner is that the first relay node and the base base station transmit information related to the second relay node Using the second relay node dedicated resource (eg, the SRB/DRB and/or logical channel of the first radio interface configured specifically for the second relay node), when the host base station receives the fourth message on the dedicated resource, it can be known that the fourth message indicates that the accessed RN is accessed through the second relay node, instead of being directly accessed by the first relay node.
  • the dedicated resource is configured by the host base station to the first relay node after the second relay node accesses the first relay node.
  • the fourth message is an RRC message and is carried on the SRB of the first radio interface (the first relay node).
  • the fourth message is an NGAP message, for example, an Initial UE message.
  • the host base station learns that the third relay node accesses the network by using the second relay node and/or the first relay node, and generates a corresponding third NGAP message and sends the message to the relay service.
  • Core network control plane node After receiving the fourth message, the host base station learns that the third relay node accesses the network by using the second relay node and/or the first relay node, and generates a corresponding third NGAP message and sends the message to the relay service.
  • Core network control plane node After receiving the fourth message, the host base station learns that the third relay node accesses the network by using the second relay node and/or the first relay node, and generates a corresponding third NGAP message and sends the message to the relay service.
  • Core network control plane node After receiving the fourth message, the host base station learns that the third relay node accesses the network by using the second relay node and/or the first relay node, and generates a corresponding third NGAP message and send
  • the fourth message carries the first uplink NAS message sent by the third relay node to the core network, and the host base station sends the first uplink NAS message of the third relay node to the relay service.
  • Core network control plane node Core network control plane node.
  • the host base station identifies the third relay node as the third, based on the first identifier/third identifier in the fourth message (transmission condition, the fourth message does not include the first identifier, including the fourth identifier)
  • the relay node allocates a first terminal identity on the NG-C interface, such as a RAN UE NGAP ID.
  • the host base station saves a correspondence between the first identifier/fourth identifier of the third relay node and the first terminal identifier.
  • the NGAP message is an initial UE message of the third relay node.
  • the fourth message is an NGAP message carried in the first radio interface, and the carried RN1RN/UE NGAP ID-Un1 (in the case of transparent transmission, the fourth message does not include the RN1 RN/UE NGAP ID-Un1 Including the RN2 RN/UE NGAP ID-Un2)
  • the host base station needs to replace the RN1 RN/UE NGAP ID-Un1/RN2 RN/UE NGAP ID-Un2 with the host base station as the third medium.
  • the first terminal identifier of the third relay node such as the RAN RN NGAP ID, can be identified on the NG-C interface following the node assignment.
  • the host base station maintains a mapping relationship between the RN1 RN/UE NGAP ID-Un1/RN2 RN/UE NGAP ID-Un2 of the third relay node and the RAN RN/UE NGAP ID.
  • the host base station receives a response message of the core network control plane node.
  • the step specifically includes steps S3051-3052.
  • the core network performs authentication and security configuration for the third relay node.
  • the fourth NGAP message may be an Attach Accept message.
  • the core network notifies the network device to establish the necessary context for the third relay node by using the fourth NGAP message.
  • the fourth NAGAN message carries the foregoing NAS message.
  • the fourth NGAP message is an Initial Context Setup Request message.
  • the fourth NGAP message includes second terminal device identification information that is allocated by the core network control plane entity (for example, AMF) to the third relay node, for example, an AMF UE/RN NGAP ID, and the second terminal device identifier.
  • the information is used to identify the third relay node on the NG-C interface.
  • the network device receives the fourth NGAP message from the core network, and generates a fifth message according to the fourth NGAP message and sends the message to the first relay node.
  • the fifth message includes NAS information indicating that the third relay node is successfully registered.
  • the fifth message is an RRC message, and is carried on the SRB of the first radio interface (the first relay node).
  • the fifth message is an NGAP message, such as an Initial Context Setup message.
  • the foregoing fifth message may be sent on the DRB or the SRB.
  • the response message received by the network device on the NG-C includes a second terminal identifier that is allocated by the core network control plane node to the third relay node, for example, an AMF UE NGAP ID, when the network device is based on the response message.
  • the network device When the fifth message is sent on the first radio interface, the network device carries the third identifier of the third relay node in the fifth message, where the network device identifies the third relay node in the first radio interface.
  • a possible process is: the fifth message further carries a first identifier of the third relay node, where the first relay node identifies the third relay node; another possible processing is: Corresponding to the transparent transmission in S303, the first relay node does not parse the fifth message, and the fifth message is transparently transmitted to the network device as the sixth message, and the fifth message further carries the third relay node.
  • the fourth identifier is used by the second relay node to identify the third relay node.
  • the network device when the network device generates the fifth message based on the foregoing NGAP message, the second terminal identifier in the NGAP message is replaced with the third identifier of the third relay node.
  • the network device saves an association relationship between at least two of the following information of the third relay node: a second terminal identifier, a first terminal identifier, a third identifier, a fourth identifier, and a first identifier.
  • the AMF UE NGAP ID, the RAN UE NGAP ID, the Donor RN/UE NGAP ID-Un1, the RN1 RN/UE NGAP ID-Un1, or the RN2 RN/UE NGAP ID-Un2 correspond to the same relay node (RN3).
  • the first relay node generates, according to the fifth message, a sixth message sent to the second relay node on the second radio interface.
  • One possible processing is: the first relay node parses part or all of the information of the fifth message; another possible processing: does not parse the fifth message, and transparently transmits the fifth message as the sixth message to the second Relay node, that is, transparent transmission.
  • the sixth message includes a NAS message that the core network notifies the UE that the registration is successful.
  • the sixth message is an RRC message and is carried on the SRB of the second radio interface (Un2 port).
  • the sixth message is an NGAP message, for example, an Intial Context Setup Request message.
  • the sixth message is carried on the second radio interface (Un2 port) on the SRB/DRB of the second relay node, for example, using the same SRB/DRB as the first message.
  • the fifth message received by the first relay node on the first radio interface includes a third identifier of the third relay node, for example, Donor UE/RN NGAP ID-Un1, and the host base station is based on the fifth message.
  • the sixth message sent by the second radio interface is generated, the fifth identifier of the third relay node needs to be carried in the sixth message, and is used to identify the third relay node on the second radio interface.
  • the fifth identifier may be added by an adaptive function (eg, the fifth identifier is present in the adaptive layer header).
  • the fifth identifier may include any one of the following information or a combination of any one of the following: RN1 RN/UE NGAP ID-Un2 (the first relay node is the device corresponding to the identifier on the second wireless interface.
  • the ID of the NG connection assigned by the bearer the second identifier (other type of ID, which can be used to identify the device corresponding to the identifier), the SRB identifier/DRB identifier, the logical channel identifier, and the second relay node on the second radio interface
  • the fourth identifier may be different from the UE or the RN, that is, the RN and the UE use the same identifier format; or the identifier distinguishes the UE and the RN, and when the device is the UE, the identifier format of the UE is adopted, when the device is In the case of the RN, the identity format of the RN is adopted; in addition, if the UE ID in the existing NGAP is applied, the RN1 RN/UE NGAP ID-Un2 is equivalent to the AMF UE NGAP ID.
  • the fifth identifier can be the same identifier as the fourth identifier.
  • the sixth message further carries a fourth identifier of the third relay node.
  • the first relay node stores an association relationship between at least two of the following information of the third relay node: a first identifier, a third identifier, a fourth identifier, and a fifth identifier.
  • a first identifier a third identifier
  • a fourth identifier a fifth identifier.
  • Donor RN/UE NGAP ID-Un1, RN1 RN/UE NGAP ID-Un1, RN1 RN/UE NGAP ID-Un2, RN2 RN/UE NGAP ID-Un2 correspond to the same relay node (RN3).
  • the second relay node receives the sixth message, where the sixth message includes a third NAS message.
  • the second relay node sends the second NAS message carried in the sixth message to the third relay node, where the third NAS message is used to indicate that the third relay node registers the result in the core network.
  • the foregoing third NAS message is sent in an RRCConnectionReconfiguration message.
  • the second relay node stores an association relationship between at least two of the following information of the third relay point: a fifth identifier, a fourth identifier, and the second relay node is the third The identification information (for example, C-RNTI-Un3 port) assigned by the relay node on the third interface.
  • the identification information for example, C-RNTI-Un3 port assigned by the relay node on the third interface.
  • C-RNTI-Un3 correspond to the same relay node (RN3).
  • the second relay node may also send other control plane messages related to the third relay node to the first relay node, and vice versa. Similar to the processing of the third message in this embodiment, the second relay node needs to send the control plane message related to the third relay node to the first relay node when the second wireless interface sends the control plane message.
  • the third message is similar, that is, exemplary, and may be an NGAP message or an RRC message.
  • the first relay node may further process the control plane message of the first radio interface, and the format of the message is Similar to the foregoing fourth message, that is, exemplary, it may be an NGAP message or an RRC message, and is sent to the network device through the first wireless interface.
  • the first relay node identifies the RN based on the fourth identifier in the message received on the second radio interface, and adds a corresponding to the RN in the corresponding control plane message sent on the first radio interface.
  • the first logo Similarly, the host base station sends a control plane message related to the third relay node to the first relay node on the first wireless interface, the format of the message is similar to the fifth message, thereby triggering the first relay node to be in the second wireless
  • the interface sends a control plane message related to the third relay node to the second relay node, the format of the message being similar to the sixth message.
  • the first relay node identifies the RN based on the third identifier in the control plane message received on the first radio interface, and adds and is associated with the corresponding control plane message sent on the second radio interface.
  • the fifth identifier corresponding to the RN.
  • the host base station is an example of the network device.
  • the description of the implementation manner is performed by using the host base station instead of the network device.
  • FIG. 9 shows a schematic diagram of an L3 protocol stack control plane architecture 1-A-A in accordance with an embodiment of the present application.
  • the L3 protocol stack control plane includes the third relay node (RN3), the second relay node (RN2), the first relay node (RN1), the donor base station (Donor), and the core network node (CN-CP_RN) , the core network control plane function for the RN).
  • RN3 is a 3-hop RN
  • RN2 is a 2-hop RN
  • RN1 is a 1-hop RN.
  • the radio interface in which RN3 communicates with RN2 is denoted as Un3, the radio interface in which RN2 communicates with RN1 is denoted as Un2, the radio interface in which RN1 communicates with Donor is denoted as Un1, and the terrestrial interface in which Donor communicates with CN-CP_RN is denoted as NG-C.
  • FIG. 10 shows a schematic diagram of an L3 protocol stack control plane architecture 1-B-A in accordance with an embodiment of the present application.
  • the L3 protocol stack control plane includes the third relay node (RN3), the second relay node (RN2), the first relay node (RN1), the donor base station (Donor), and the core network node (CN-CP_RN) , the core network control plane function for the RN).
  • RN3 is a 3-hop RN
  • RN2 is a 2-hop RN
  • RN1 is a 1-hop RN.
  • the radio interface in which RN3 communicates with RN2 is denoted as Un3, the radio interface in which RN2 communicates with RN1 is denoted as Un2, the radio interface in which RN1 communicates with Donor is denoted as Un1, and the terrestrial interface in which Donor communicates with CN-CP_RN is denoted as NG-C.
  • each node is described below by taking the protocol stack architecture shown in FIG. 10 as an example. It should be understood that the action of RN2 in the protocol stack architecture shown in FIG. 9 is similar to the action of RN2 in the protocol stack architecture shown in FIG. 10, except that RN2 and RN1 are on the Un2 port in the protocol stack architecture shown in FIG.
  • the protocol stack of the communication includes the RRC layer, that is, the NGAP message is carried in the SRB on the Un2 port; in the protocol stack architecture shown in FIG. 9, the protocol stack in which the RN2 and the RN1 communicate on the Un2 port does not include the RRC layer, that is, the NGAP message at the Un2 port. Hosted in the DRB. In the two protocol stack architectures, RN1 needs to have an NGAP layer, and the NGAP message is parsed at the NGAP layer, and the newly generated NGAP message is sent out through the Un1 port.
  • the protocol stack in which the RN3 communicates with the RN2 includes an RRC layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from top to bottom.
  • the NAS layer is responsible for the corresponding process negotiated with the core network. Therefore, the NAS message is transparently transmitted to the core network node CN-CP_RN through the RAN hop nodes (for example, RN2, RN1, and the donor base station). It is parsed and processed by CN-CP_RN.
  • Un3 port The protocol stack in which RN2 communicates with RN3 is peered with the protocol stack of RN3, and includes the RRC layer, the PDCP layer, the RLC layer, the MAC layer, and the PHY layer from top to bottom.
  • the RN2 interprets the RRC message received on the Un3 interface, and after processing (for example, reading the RRC information content), may generate a corresponding NGAP message, and the SRB carried in the Un2 port is sent to the host base station.
  • the NGAP message is to be part of the content or content of the RRC message. If the RRC message received by the Un3 port includes the NAS PDU, the RN2 encapsulates the NAS PDU in the NGAP message and sends it to the RN1 through the Un2 port.
  • the RN2 For the downlink DL, the RN2 generates an RRC message that is sent to the RN3, and is sent to the RN3 through the Un3 interface after being processed by the lower layer protocol stack. If the NGAP message received by the Un2 interface includes the NAS message, the MPLS message is transmitted through the Un3 port. The RRC message is sent to RN3.
  • Un2 port The protocol stack in which RN2 communicates with RN1 includes an NGAP layer, an SCTP layer (optionally), an IP layer (optionally), and an RRC layer from top to bottom (optionally, when there is no RRC layer, the protocol Stack 1-BA is the same as 1-AA), PDCP layer, RLC layer, MAC layer, and PHY layer.
  • the generated NGAP message (which may include the NAS message) is further processed by the SCTP layer and/or the IP layer (optionally), and then carried in the RRC message (when the RRC layer is not present, The bearer is sent to RN1 through the Un2 port in the DRB packet.
  • the foregoing NGAP message is processed by an adaptive function, for example, including adding an RN3 identifier, adding an RN2 identifier, increasing an RRC message type, adding an SRB identifier, adding an NGAP message type, or adding other information content, and then transmitting the information to the lower layer protocol stack. .
  • the RN2 receives the RRC message sent by the RN1 on the Un2 interface (when the RRC layer is not present, receives the DRB data packet), and performs processing (for example, acquiring the RN2 identifier, acquiring the RN3 identifier, acquiring the RRC message type, After obtaining the NGAP message type, obtaining the SRB identifier, or acquiring other information content, etc., the NGAP message part is obtained and passed to the upper NGAP protocol layer for processing (optionally, the SCTP layer processing and/or the IP layer processing).
  • processing for example, acquiring the RN2 identifier, acquiring the RN3 identifier, acquiring the RRC message type, After obtaining the NGAP message type, obtaining the SRB identifier, or acquiring other information content, etc.
  • the NGAP message part is obtained and passed to the upper NGAP protocol layer for processing (optionally, the SCTP layer processing and/or the IP layer processing).
  • the processed NGAP message content (which may include the NAS message) is sent to the protocol layer of the Un3 port.
  • the NAS message carried in the NGAP message received by the Un2 port is sent to the RRC layer of the Un3 port.
  • the SRB of the RN2 on the Un2 interface may carry any one of the following information/messages or a combination of any of the following: an RRC message of the RN2, an NGAP message generated by the RN2 for the UE it serves, and an RN3 generated by the UE served by the RN3.
  • the NGAP message (part of the content of the message may be modified and/or replaced by the RN2), the NGAP message generated by the other RN for the UE it serves (the part of the message may be modified and/or replaced by the RN2), and the RN2 is The XnAP message generated by the serving UE, the XnAP message generated by the RN3 for the UE it serves (the part of the message may be modified and/or replaced by the RN2), and the XnAP message generated by the UE served by the other RN (the message) Some of the content can be modified and/or replaced by RN1). After the RN2/RN1 receives the RRC message of the different types, the RN2/RN1 may need to perform the distinguishing process. Therefore, it is necessary to be able to identify the different types of RRC messages, which can be implemented by any one of the following modes or a combination of any of the following. :
  • the fourth adaptive identifier may include any one of the following information or a combination of any multiple: three-hop RN identifier and/or hop count information (for identifying RN3), and third UE identifier (for Identifying the RN3 served UE), the two-hop RN identity and/or hop count information (for identifying the RN2), the second UE identity (for identifying the UE served by the RN2), the multi-hop RN identity and/or the hop count information (using The fourth UE identifier (the UE for identifying the four-hop or even the n-hop RN service), the NGAP message type, the XnAP message type, and the RRC message type are used to identify the four-hop or even n-hop RN that transmits data through RN3 and RN2.
  • the process of adding an adaptive identity to the uplink RRC message and parsing the identity of the downlink RRC message is referred to as an adaptive function.
  • the adaptive function may be included in an existing protocol layer, such as an RRC layer/PDCP layer/RLC layer/MAC layer/PHY layer; or the adaptive function may be separately deployed in a protocol layer, for example, referred to as adaptive (Adaptation, referred to as Adapt) layer.
  • the adaptation layer may be deployed between the NG layer and the RRC layer, or between the RRC layer and the PDCP layer, or between the PDCP layer and the RLC layer, or between the RLC layer and the MAC layer. Or deployed between the MAC and PHY layers.
  • the DRB of the RN2 on the Un2 port may carry any one of the following types of data or a combination of any one of the following: data of the RN2, data of the UE served by the RN2, data of the RN3, data of the UE served by the RN3, and data of other RNs.
  • the data of the UE served by the other RN, the NGAP message generated by the RN2 for the UE it serves, the GTP-U packet encapsulated by the RN2 for the UE it serves, and the NGAP message generated by the RN3 for the UE it serves (part of the message)
  • the RN3 may modify and/or replace the RN2, and the RN3 encapsulates the GTP-U data packet encapsulated by the UE (the part of the message may be modified and/or replaced by the RN2), and the other RN generates the UE for the UE it serves.
  • NGAP message (part of the content of the message may be modified and/or replaced by RN2), and other RN encapsulates the GTP-U data packet encapsulated by the UE (the part of the message may be modified and/or replaced by RN2),
  • the RN2/RN1 may need to perform the distinguishing process. Therefore, it is necessary to be able to identify the different types of data packets, which may be implemented by any one of the following methods or a combination of any of the following:
  • the fifth adaptive identifier may include any one of the following information or a combination of any multiple: three-hop RN identifier and/or hop count information (for identifying RN3), and third UE identifier (for Identifying the RN3 served UE), the two-hop RN identity and/or hop count information (for identifying the RN2), the second UE identity (for identifying the UE served by the RN2), the multi-hop RN identity and/or the hop count information (using For identifying four-hop or even n-hop RNs that pass data through RN3 and RN2, fourth UE identity (for identifying multi-hop RN service UE), NGAP message type, XnAP message type, GTP-U message type (belonging to NG) -U or Xn-U), as well as the user plane packet type.
  • the process of adding an adaptive identity to an upstream packet and parsing the identity of the downstream packet is referred to as an adaptive function.
  • the adaptive function may be included in an existing protocol layer, such as an SDAP layer/PDCP layer/RLC layer/MAC layer/PHY layer; or the adaptive function may be separately deployed in a protocol layer, for example, referred to as adaptive (Adaptation, referred to as Adapt) layer.
  • the adaptation layer may be deployed between the NGAP layer and the PDCP layer, or between the PDCP layer and the RLC layer, or between the RLC layer and the MAC layer, or between the MAC and PHY layers.
  • Un2 port The protocol stack in which RN1 communicates with RN2 is peered with the protocol stack of RN2, including NGAP, SCTP (optionally), IP (optionally), RRC layer (optionally), PDCP layer, from top to bottom. RLC layer, MAC layer, and PHY layer. The functions of each layer are similar to those of RN2.
  • the RRC layer of the RN1 interprets the RRC message received at the Un2 port, and performs processing (for example, reading the RRC information content, obtaining the RN3 identifier, and acquiring the message type), and then extracting the NGAP message therein. It is sent to the upper NGAP layer to generate an NGAP message for the Un1 port.
  • the Un1 port based on the NGAP message received by the Un1 port, generate an NGAP message sent to the RN2 on the Un2 port (for example, mapping the NGAP ID of the RN3 of the Un1 port to the NGAP ID of the RN3 of the Un2 port), after the RRC After layer processing (including, for example, adding RN3, adding RN2 identifier, increasing RRC message type, adding SRB identifier, adding NGAP message type, or adding other information content, and further encapsulating, etc.), after passing through the lower layer protocol stack, passing through Un2 port The SRB is sent to RN2.
  • layer processing including, for example, adding RN3, adding RN2 identifier, increasing RRC message type, adding SRB identifier, adding NGAP message type, or adding other information content, and further encapsulating, etc.
  • Un1 port The protocol stack in which RN1 communicates with the host includes NGAP, SCTP (optionally), IP (optionally), RRC layer (optionally), PDCP layer, RLC layer, MAC layer, and PHY layer from top to bottom. .
  • RRC layer is optional: if there is an RRC layer, the NGAP message is carried on the SRB of the Un1 port, which is the same as the Un1 port in the protocol stack 1-B; if there is no RRC layer, The NGAP message is carried on the DRB of the Un1 interface. This is the same as the Un1 port in the protocol stack 1-A.
  • the behavior of RN1 is similar to that of protocol stack 1-B or RN1 on Un1 port in protocol stack 1-A. For example, the method of distinguishing various data types on Un1 port, and the deployment mode of adaptive function, etc., refer to the above two types. A description of the behavior of RN1 in the protocol stack. Only a simple packet processing flow is described here.
  • the NGAP message (which may include the NAS message) received by the Un2 port is processed to generate an NGAP message (for example, mapping the NGAP ID of the RN3 of the Un2 port to the NGAP ID of the RN3 of the Un1 port), Further sent to the lower layer protocol stack, optionally after processing (for example, including adding RN3, adding RN2 identifier, increasing RRC message type, adding SRB identifier, adding NGAP message type, or adding other information content, and further encapsulating, etc.)
  • the Un1 port is sent to the host base station.
  • the RN1 receives the bearer NGAP message sent by the host base station on the Un1 port, and performs processing (for example, acquiring the RN1 identifier, acquiring the RN2 identifier, acquiring the RN3 identifier, acquiring the RRC message type, obtaining the NGAP message type, and acquiring the SRB.
  • the NGAP message part is obtained and passed to the upper NGAP layer for processing (for example, mapping the NGAP ID of the RN3 of the Un1 port to the NGAP of the RN3 of the Un2 port) ID), generates an NGAP message sent on the Un2 port.
  • the protocol stack of the donor base station is peered with RN1, including the NGAP layer, the SCTP layer (optionally), the IP layer (optionally), the RRC layer (optionally), the PDCP layer, and the RLC from top to bottom. Layer, MAC layer, and PHY layer.
  • RN1 including the NGAP layer, the SCTP layer (optionally), the IP layer (optionally), the RRC layer (optionally), the PDCP layer, and the RLC from top to bottom. Layer, MAC layer, and PHY layer.
  • the host base station receives the RRC message or the DRB data packet sent by the RN1 on the Un1 interface, and performs processing (for example, acquiring the RN2 identifier, acquiring the RN3 identifier, acquiring the RRC message type, acquiring the SRB identifier, acquiring the NGAP message type, After obtaining other information content, etc., the NGAP message part is obtained and passed to the upper NGAP protocol layer for processing (optionally, through SCTP layer processing and/or IP layer processing).
  • the content of the processed NGAP message is sent to the NGAP layer of the NG-C interface (for example, the NGAP ID of the RN3 of the Un1 port is mapped to the NGAP ID of the RN3 of the NG-C port). If the NGAP message received by the Un1 port contains the NAS PDU, the host eNB encapsulates the NAS PDU in an NGAP message and sends it to the CN-CP_RN through the NG-C interface.
  • the host base station sends the NGAP message to the RN3, further processed by the SCTP layer and/or the IP layer (optionally), and is processed and carried in the RRC message or the DRB packet (for example, adding The RN2 identifier, the RN3 identifier is added, the NGAP message type is added, the SRB identifier is added, the RRC message type is added, or other information content is added, and further encapsulation is performed.
  • the RN2 is sent to the RN1 through the Un1 interface.
  • FIG. 11 shows another schematic diagram of the L3 protocol stack control plane architecture 2 according to an embodiment of the present application.
  • the L3 protocol stack control plane includes the third relay node (RN3), the second relay node (RN2), the first relay node (RN1), the donor base station (Donor), and the core network node (CN-CP_RN) , the core network control plane function for the RN).
  • RN3 is a 3-hop RN
  • RN2 is a 2-hop RN
  • RN1 is a 1-hop RN.
  • the radio interface in which RN3 communicates with RN2 is denoted as Un3, the radio interface in which RN2 communicates with RN1 is denoted as Un2, the radio interface in which RN1 communicates with Donor is denoted as Un1, and the terrestrial interface in which Donor communicates with CN-CP_RN is denoted as NG-C.
  • RN2 in FIG. 11 is similar to the action of RN1 in the protocol stack architecture 2 in FIG. 7. For brevity, no further details are provided herein.
  • FIG. 12 shows a schematic diagram of an L3 protocol stack control plane architecture 1-A-B in accordance with an embodiment of the present application.
  • the L3 protocol stack control plane includes the third relay node (RN3), the second relay node (RN2), the first relay node (RN1), the donor base station (Donor), and the core network node (CN-CP_RN) , the core network control plane function for the RN).
  • RN3 is a 3-hop RN
  • RN2 is a 2-hop RN
  • RN1 is a 1-hop RN.
  • the radio interface in which RN3 communicates with RN2 is denoted as Un3, the radio interface in which RN2 communicates with RN1 is denoted as Un2, the radio interface in which RN1 communicates with Donor is denoted as Un1, and the terrestrial interface in which Donor communicates with CN-CP_RN is denoted as NG-C.
  • the RN1 of the L3 protocol stack control plane architecture 1-AB does not parse the content of the NGAP message sent by the RN2, that is, the data type of the DRB that carries the NGAP message is not distinguished, and the PDCP SDU of the DRB of the RN2 of the Un2 interface is carried. It is sent to the host base station on the DRB of RN1 on the Un1 port.
  • FIG. 13 shows a schematic diagram of an L3 protocol stack control plane architecture 1-B-B in accordance with an embodiment of the present application.
  • the L3 protocol stack control plane includes the third relay node (RN3), the second relay node (RN2), the first relay node (RN1), the donor base station (Donor), and the core network node (CN-CP_RN) , the core network control plane function for the RN).
  • RN3 is a 3-hop RN
  • RN2 is a 2-hop RN
  • RN1 is a 1-hop RN.
  • the radio interface in which RN3 communicates with RN2 is denoted as Un3, the radio interface in which RN2 communicates with RN1 is denoted as Un2, the radio interface in which RN1 communicates with Donor is denoted as Un1, and the terrestrial interface in which Donor communicates with CN-CP_RN is denoted as NG-C.
  • the RRC message of the RN2 and the NGAP message generated by the RN2 are carried on different SRB/LCs, and the RN1 does not parse the NGAP message sent by the RN2, and the SRB that carries the NGAP message.
  • the RRC message content on the /LC is carried on the SRB or DRB of the RN1 on the Un1 interface and sent to the host base station.
  • Un3 port The protocol stack in which RN3 communicates with RN2 includes an RRC layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from top to bottom.
  • RRC layer there is a NAS layer above the RRC layer, and the NAS layer is responsible for the corresponding process negotiated with the core network. Therefore, the NAS message is transparently transmitted to the core network node CN-CP_RN through the RAN hop nodes (for example, RN2, RN1, and the donor base station). It is parsed and processed by CN-CP_RN.
  • Un3 port The protocol stack in which RN2 communicates with RN3 is peered with the protocol stack of RN3, and includes the RRC layer, the PDCP layer, the RLC layer, the MAC layer, and the PHY layer from top to bottom. The functions of each layer are similar to those of RN3.
  • the RN2 interprets the RRC message received on the Un3 interface, and after processing (for example, reading the RRC information content), may generate a corresponding NGAP message, and the SRB carried in the Un2 port is sent to the host base station.
  • the NGAP message is to be part of the content or content of the RRC message. If the RRC message received by the Un3 port includes the NAS PDU, the RN2 encapsulates the NAS PDU in the NGAP message and sends it to the RN1 through the Un2 port.
  • the RN2 For the downlink DL, the RN2 generates an RRC message that is sent to the RN3, and is sent to the RN3 through the Un3 interface after being processed by the lower layer protocol stack. If the NGAP message received by the Un2 interface includes the NAS message, the MPLS message is transmitted through the Un3 port. The RRC message is sent to RN3.
  • the protocol stack in which RN2 communicates with RN1 includes the RRC layer from top to bottom (optionally, when there is no RRC layer, the protocol stack 1-BB is the same as 1-AB), PDCP layer, RLC layer, MAC layer And the PHY layer. It should be noted that the foregoing protocol layer is peer-to-peer with RN1. Above these protocol layers, there is also an NGAP layer, an SCTP layer (optionally), and an IP layer (optionally) that are equivalent to the host base station.
  • the behavior of RN2 on the Un2 port is similar to the behavior of RN2 on the Un2 port in the protocol stack architecture shown in Figure 10. Referring to the detailed description in Figure 10, for example, the method of distinguishing data types and the deployment of adaptive functions on the Un2 port Here, only a simple packet processing flow is described.
  • the generated NGAP message (which may include the NAS message) is further processed by the SCTP layer and/or the IP layer (optionally), and then carried in the RRC message (when the RRC layer is not present, The bearer is sent to RN1 through the Un2 port in the DRB packet.
  • the foregoing NGAP message is processed by an adaptive function, for example, including adding an RN3 identifier, adding an RN2 identifier, increasing an RRC message type, adding an SRB identifier, adding an NGAP message type, or adding other information content, and then transmitting the information to the lower layer protocol stack. .
  • the RN2 receives the RRC message sent by the RN1 on the Un2 port (when the RRC layer is not present, receives the DRB data packet), and performs processing (for example, acquiring the RN2 identifier, acquiring the RN3 identifier, acquiring the RRC message type, After obtaining the NGAP message type, obtaining the SRB identifier, or acquiring other information content, etc., the NGAP message part is obtained and passed to the upper NGAP protocol layer for processing (optionally, the SCTP layer processing and/or the IP layer processing).
  • processing for example, acquiring the RN2 identifier, acquiring the RN3 identifier, acquiring the RRC message type, After obtaining the NGAP message type, obtaining the SRB identifier, or acquiring other information content, etc.
  • the NGAP message part is obtained and passed to the upper NGAP protocol layer for processing (optionally, the SCTP layer processing and/or the IP layer processing).
  • the processed NGAP message content (which may include the NAS message) is sent to the protocol layer of the Un3 port.
  • the NAS message carried in the NGAP message received by the Un2 port is sent to the RRC layer of the Un3 port.
  • Un2 port The protocol stack in which RN1 communicates with RN2 is peered with the protocol stack of RN2 from RRC, and includes the RRC layer (optionally), the PDCP layer, the RLC layer, the MAC layer, and the PHY layer from top to bottom.
  • RRC radio resource control
  • the RN1 receives the RRC message of the SRB that is carried on the interface of the Un2, and performs processing (for example, obtaining the RN3 identifier and obtaining the message type), and then extracting the NGAP message and sending it to the host base station through the Un1 port. .
  • the RN1 distinguishes whether the RRC message is an RRC message of the RN2 by using the SRB identifier or the logical channel identifier where the RRC message is located. If yes, it is submitted to the RRC layer on the Un2 port for analysis; if not, it is not submitted to the RRC layer of the Un2 port, and is directly forwarded to the protocol stack of the Un1 port.
  • the foregoing NGAP message may be sent to the host base station by being carried on the SRB or DRB of the Un1 port.
  • the RN1 receives the DRB data packet that is carried in the Un2 interface, and performs processing (for example, obtaining the RN3 identifier and acquiring the message type), extracting the NGAP message and sending it to the host base station through the Un1 interface. .
  • the RN1 distinguishes the data packet from the RNAP message generated by the RN2 to the RN3 by using the DRB identifier or the logical channel identifier of the data packet, and directly forwards the PDCP SDU of the data packet to the protocol stack of the Un1 port.
  • the foregoing NGAP message may be sent to the host base station by being carried on the SRB or DRB of the Un1 port.
  • the RRC message/DRB data packet sent by the Un1 port is generated, and after processing, the RRC message/DRB data packet sent to the RN2 is processed, for example, including adding the RN3, adding the RN2 identifier, and increasing the RRC message type.
  • the SRB ID is added, the NGAP message type is added, or other information content is added.
  • the device After being processed by the lower layer protocol stack, the device sends the message to the RN2 through the Un2 port.
  • the protocol stack in which RN1 communicates with the host includes the RRC layer (optionally), the PDCP layer, the RLC layer, the MAC layer, and the PHY layer from top to bottom.
  • the RRC layer is optional: if there is an RRC layer, the NGAP message is carried on the SRB of the Un1 port, which is the same as the Un1 port in the protocol stack 1-B; if there is no RRC layer, The NGAP message is carried on the DRB of the Un1 interface. This is the same as the Un1 port in the protocol stack 1-A.
  • the behavior of RN1 is similar to that of protocol stack 1-B or RN1 on Un1 port in protocol stack 1-A.
  • the method of distinguishing various data types on Un1 port, and the deployment mode of adaptive function, etc. refer to the above two types.
  • the description of the behavior of RN1 in the protocol stack is different from the above two protocol stacks, and RN1 does not need to be interpreted. Only a simple packet processing flow is described here.
  • the NGAP message (which may include the NAS message) received by the Un2 interface is processed by the RRC layer (including, for example, adding the RN3, adding the RN2 identifier, increasing the RRC message type, adding the SRB identifier, and adding the NGAP message.
  • the type, or other information content, and further encapsulation, etc., are carried in the RRC message and sent to the host base station through the Un1 port.
  • the RN1 receives the RRC message sent by the host base station on the Un1 interface, and performs processing (for example, acquiring the RN1 identifier, acquiring the RN2 identifier, acquiring the RN3 identifier, acquiring the RRC message type, obtaining the NGAP message type, and acquiring the SRB identifier, After obtaining other information content, and further decapsulating, etc., the NGAP message part is obtained and passed to the RRC layer processing of the Un2 port.
  • processing for example, acquiring the RN1 identifier, acquiring the RN2 identifier, acquiring the RN3 identifier, acquiring the RRC message type, obtaining the NGAP message type, and acquiring the SRB identifier.
  • the protocol stack below the RRC layer of the donor base station is peered with RN1
  • the NGAP layer above the RRC layer is peered with RN2
  • the NGAP layer including the NGAP layer, the SCTP layer (optionally), and the IP layer from top to bottom (optionally ), RRC layer, PDCP layer, RLC layer, MAC layer, and PHY layer.
  • the RRC layer may have an adaptive layer function.
  • the host base station receives the RRC message sent by the RN1 on the Un1 port, and performs processing (for example, acquiring the RN2 identifier, acquiring the RN3 identifier, acquiring the RRC message type, acquiring the SRB identifier, acquiring the NGAP message type, or acquiring other information content, and After further decapsulation, etc., the NGAP message part is obtained and passed to the upper layer NGAP protocol layer processing (optionally, through SCTP layer processing and/or IP layer processing). The processed NGAP message content is sent to the NGAP layer of the NG-C interface. If the NGAP message received by the Un1 port contains the NAS PDU, the host eNB encapsulates the NAS PDU in an NGAP message and sends it to the CN-CP_RN through the NG-C interface.
  • processing for example, acquiring the RN2 identifier, acquiring the RN3 identifier, acquiring the RRC message type, acquiring the SRB identifier,
  • the eNB sends the NGAP message to the RN3, and further passes the SCTP layer processing and/or the IP layer processing (optionally), and carries the RRC message through the RRC layer (for example, adding the RN2 identifier and adding the RN3 identifier).
  • the NGAP message type is added, the SRB identifier is added, the RRC message type is added, or other information content is added, and further encapsulation is performed.
  • the packet After being processed by the lower layer protocol stack, the packet is sent to the RN1 through the Un1 port.
  • the method for the terminal device to access the network through the two-hop RN is similar to the method 300, and the difference lies in:
  • the third interface that the terminal device communicates with the second relay node is a Uu port, and the third relay node communicates with the second relay node as an Un3 port.
  • the wireless interface mechanism of the Uu port and the Un3 port may be different.
  • the different wireless interface mechanisms refer to physical layer transmission technologies being different or partially different; or the physical layer transmission technologies are the same but the physical layer is different from the protocol stack; or the protocol stack structure and the protocol layer functions are mostly the same, The wireless transmission resources are different. It can be seen in the embodiment of the present application that the Uu is the same as the Un3 protocol stack, and the physical layer transmission technology and the used wireless transmission resources may be different;
  • the UE identifier needs to be added at the adaptation layer of each node, and the network device can recognize that this is a terminal device-related control plane message, so that when the NGAP message is sent to the core network node for the terminal device, the NGAP is used.
  • the message is routed to the core network node (CN-CP for UE) serving the terminal device.
  • FIG. 14 is another schematic diagram of an L3 protocol stack control plane architecture 1-AA according to an embodiment of the present application. It should be understood that FIG. 14 corresponds to FIG. 9 , except that the UE accesses the network through two hops, for brevity. I will not repeat them here.
  • FIG. 15 is another schematic diagram of an L3 protocol stack control plane architecture 1-BA according to an embodiment of the present application. It should be understood that FIG. 15 corresponds to FIG. 10, except that the UE accesses the network through two hops, for brevity. I will not repeat them here.
  • FIG. 16 shows still another schematic diagram of the L3 protocol stack control plane architecture 2 according to the embodiment of the present application. It should be understood that FIG. 16 corresponds to FIG. 11 , except that the UE accesses the network through two hops, for the sake of brevity. No longer.
  • FIG. 17 is another schematic diagram of an L3 protocol stack control plane architecture 1-AB according to an embodiment of the present application. It should be understood that FIG. 17 corresponds to FIG. 12, except that the UE accesses the network through two hops, for brevity. I will not repeat them here.
  • FIG. 18 is another schematic diagram of the L3 protocol stack control plane architecture 1-BB according to the embodiment of the present application. It should be understood that FIG. 18 corresponds to FIG. 13 , except that the UE accesses the network through two hops, for brevity. I will not repeat them here.
  • the network access process of the two-hop and three-hop RN or the terminal device and the control plane protocol stack architecture are introduced.
  • the data transmission process of the user plane and the protocol stack of the data plane are introduced below with reference to FIG. 19 to FIG. Architecture.
  • FIG. 19 shows a schematic flowchart of a transmission method 400 according to an embodiment of the present application. As shown in FIG. 19, the method 400 includes:
  • the first relay node determines a first mapping relationship, where the first mapping relationship is used to determine a correspondence between the attribute information of the first data packet and the radio bearer used by the first data packet.
  • the relay node communicates with the network device through the first wireless interface; the first relay node communicates with the first device through the second wireless interface.
  • the network device may be a host base station or an RN; the first device may be a UE or an RN (for example, a second relay node).
  • the first data packet is a data packet of a terminal device that belongs to a certain second relay node, and at this time, the information of the terminal device may include the terminal device.
  • the first data packet belongs to a data packet of a terminal device of a multi-hop RN service, and the information of the terminal device may include an identifier of the terminal device, and between each terminal device and the second relay node.
  • the identification information of the multi-hop RN of the data packet is forwarded for the terminal device.
  • the attribute information of the first data packet may include a combination of any one or more of the following information: information of the first device, information of the terminal device, session connection information, and data flow information, where the data packet is Information about the radio bearer of the data when the second radio interface is transmitted, the information of the logical channel used by the first data packet when transmitting on the second radio interface, and the radio bearer of the data when the first data packet is transmitted by the first radio interface Information, the information of the logical channel used by the first data packet when transmitting on the first wireless interface.
  • the information of the terminal device is used to identify the terminal device served by the second relay node to which the first data packet belongs.
  • the session connection is a protocol data unit session or a PDU session (PDU session) or a PDU session resource.
  • the data stream is a quality of service flow (QoS flow).
  • QoS flow quality of service flow
  • the information of the radio bearer and/or the information of the logical channel includes the information of the radio bearer and/or the information of the node to which the logical channel belongs on the transmitted radio interface, that is, the information and/or logical channel through the radio bearer.
  • Information can identify the node to which it belongs on the transmitted wireless interface.
  • the radio bearer includes a data radio bearer and a signaling radio bearer, and the information of the radio bearer includes an identifier of the radio bearer.
  • the first mapping relationship includes a first uplink mapping relationship and/or a first downlink mapping relationship.
  • the first uplink mapping relationship may be any one of the following modes:
  • the mode (1) has the finest granularity and can be a mapping of QFI to DRB in a PDU session of one UE/RN; the granularity of mode 2 is the coarsest, and the DRB of the second radio interface is the DRB of the first radio interface.
  • the mapping (3) is a compromise between the first two modes, and the dimension of the UE/RN is added on the basis of the mode (2), that is, the data belonging to a certain UE/RN in the DRB of the second radio interface reaches the A mapping of the DRB of a wireless interface.
  • the candidate mode of the first downlink mapping relationship is similar to the uplink mode, and may be any of the following modes:
  • the second wireless interface sends a correspondence between the information of the radio bearer used by the first data packet and the information of the logical channel.
  • the manner in which the first relay node acquires the foregoing first mapping relationship may be any one of the following modes or a combination of any multiple:
  • the first relay node decides by itself
  • the obtaining, by the information carried in the first data packet includes acquiring the first downlink mapping relationship.
  • the first relay node receives the first data packet on the first wireless interface, and acquires any one or any combination of the following information carried in the first data packet: session connection information, data flow information, And transmitting, by the second wireless interface, the information of the radio bearer used by the first data packet and/or the information of the logical channel, the information of the first device, and the information of the terminal device; thereby acquiring the first downlink mapping relationship.
  • the method (3) further includes acquiring the first uplink mapping relationship.
  • the first relay node receives the first data packet on the second wireless interface, and acquires any one or any combination of the following information carried in the first data packet: session connection information, data flow information, And transmitting, by the first wireless interface, the information of the data radio bearer used by the first data packet and/or the information of the logical channel, the information of the first device, and the information of the terminal device; thereby acquiring the first uplink mapping relationship.
  • the first uplink mapping relationship is obtained by using the downlink sending manner of the first data packet, where the first relay node acquires any one of the following information of the first data packet or any of the following information.
  • session connection information data stream information, information of the radio bearer used by the first data packet and/or information of the logical channel on the second radio interface, used by the first radio interface to send the first data packet Information of the radio bearer and/or information of the logical channel, and information of the first device and/or the terminal device to which the first data packet belongs; thereby acquiring any one of the following mapping relationships as the first uplink mapping relationship: session connection Correspondence of information and/or data stream information to information of radio bearers and/or logical channels of the first radio interface, information of radio bearers and/or logical channels of the first radio interface and radio bearers of the second radio interface and/or Or the correspondence of the information of the logical channel, the information of the radio bearer and/or the logical channel of the first radio interface, and the
  • the first relay node determines, and the first relay node acquires any one or any of the following information: QoS information of the session connection of the first data packet, The QoS information of the data stream of the data packet, the data radio bearer information used by the first data packet and/or the QoS information of the logical channel used by the first radio interface, and the first data packet sent by the second radio interface
  • the data carries the information of the radio and/or the QoS information of the logical channel.
  • the QoS information may include QoS parameters, or scheduling requirements (e.g., scheduling priorities of logical channels, etc.), or QoS classification levels (QCI), and the like.
  • the first relay node determines the first mapping relationship based on the QoS related information.
  • the first relay node receives, by using the second wireless interface, a first data packet sent by a second relay node, where the second wireless interface is the first relay node and the second relay A wireless interface for data transmission between nodes.
  • the first relay node determines attribute information of the first data packet.
  • the manner in which the first relay node determines the attribute information of the first data packet may be any one of the following modes or a combination of any multiple:
  • the first relay node sends the first data packet to the network device by using the first wireless interface according to the attribute information of the first data packet and the first mapping relationship, where the first wireless The interface is a wireless interface for performing data transmission between the first relay node and the network device.
  • FIG. 20 shows a schematic flowchart of a transmission method 500 according to an embodiment of the present application. As shown in FIG. 20, the method 500 includes:
  • the second relay node determines a second mapping relationship, where the second mapping relationship is a correspondence between attribute information of the second data packet and a radio bearer used to send the second data packet.
  • the second relay node communicates with the first relay node through the second wireless interface; the second relay node communicates with the first device through the third wireless interface.
  • the first device may be a UE or an RN (for example, a third relay node).
  • the attribute information of the second data packet may include a combination of any one or more of the following information: information of the second device, session connection information, data flow information, and the data packet is transmitted on the third wireless interface.
  • the information of the radio bearer in which the second data packet is transmitted on the third radio interface, the information of the radio bearer in which the second data packet is transmitted on the second radio interface, and the second data The information of the logical channel used when transmitting the second wireless interface.
  • the session connection is a PDU session or a PDU session resource.
  • the data stream is a QoS flow.
  • the second mapping relationship includes a second uplink mapping relationship and/or a second downlink mapping relationship.
  • the second uplink mapping relationship may be any one of the following modes:
  • the mode (1) has the finest granularity and can be a mapping of QFI to DRB in a PDU session of one UE/RN;
  • the mode (2) has the coarsest granularity, and is the DRB of the third radio interface to the second radio interface.
  • the mapping of the DRB; the method 3 is a compromise between the first two modes, and the dimension of the UE/RN is added on the basis of the mode (2), that is, the data belonging to a certain UE/RN in the DRB of the third radio interface reaches the The mapping of the DRB of the second wireless interface.
  • the candidate mode of the second downlink mapping relationship is similar to the uplink mode, and may be any of the following modes:
  • the manner in which the second relay node obtains the foregoing second mapping relationship may be any one of the following modes or a combination of any multiple:
  • the second relay node receives the second data packet on the second wireless interface, and acquires any one or any combination of the following information carried in the second data packet: session connection information, data flow information, And transmitting, by the third wireless interface, information of the radio bearer used by the second data packet and/or information of the logical channel, and information of the second device; thereby acquiring a second downlink mapping relationship.
  • the method 3 further includes acquiring the second uplink mapping relationship.
  • the second relay node receives the second data packet on the third wireless interface, and acquires any one or any combination of the following information carried in the second data packet: session connection information, data flow information, And transmitting, by the second wireless interface, information of the radio bearer used by the second data packet and/or information of the logical channel, and information of the second device; thereby acquiring a second uplink mapping relationship.
  • the second uplink mapping relationship is obtained by using the downlink sending manner of the second data packet, where the second relay node acquires any one of the following information of the second data packet or any of the following information.
  • the second relay node determines, and the second relay node acquires any one or any of the following information: QoS information of the session connection of the second data packet, The QoS information of the data stream of the second data packet, the information of the data radio bearer used by the second data packet and/or the QoS information of the logical channel used by the second radio interface, and the second radio interface transmitting the second data packet
  • the data carries the information of the radio and/or the QoS information of the logical channel.
  • the QoS information may include QoS parameters, or scheduling requirements (such as scheduling priorities of logical channels, etc.), or QoS classification levels (QCI), and the like.
  • the second relay node determines the first mapping relationship based on the QoS related information.
  • the second relay node receives, by using the third wireless interface, a second data packet sent by the terminal device.
  • the second relay node determines attribute information of the second data packet.
  • the manner in which the second relay node determines the attribute information of the second data packet may be any one of the following manners or a combination of any multiple:
  • the second relay node sends the second data packet to the first relay node by using the second wireless interface according to the attribute information of the second data packet and the second mapping relationship.
  • FIG. 21 is a schematic flowchart of a method 600 for a session establishment by a two-hop RN/terminal device through a control plane according to an embodiment of the present application.
  • the host base station configures a first mapping relationship for the first relay node.
  • the method 600 includes:
  • the first device accesses the first relay node by using the second wireless interface, and then transmits signaling and data to the core network by using the first wireless interface between the first relay node and the host base station.
  • the first device may be a terminal device or an RN, such as a second relay node.
  • the second wireless interface is the Uu port; when the first device is the RN, the second wireless interface is the Un2 port.
  • the core network control plane node (for example, AMF) sends a first control plane request message to the host base station by using the NG interface, and the host base station receives the first control plane request message by using the NG interface, where the first control plane request message is used to request the host base station. Allocating resources for the session connection to the first device.
  • AMF core network control plane node
  • the first control plane request message includes any one of the following information related to the first device or a combination of any multiple: a first terminal identifier, a second terminal identifier, session connection identifier information, and a first transmission Layer information, slice related information, QoS parameters for session connections, data flow identification information, QoS parameters for data flows, and NAS messages related to session connection establishment.
  • the first transport layer information is NG-U tunnel establishment information corresponding to the session connection, for example, a GTP TEID and/or a transport layer address including a core network user plane node, for uplink data transmission.
  • the first terminal identifier and/or the second terminal identifier are used to identify the first device; the slice related information is used by the relay node to identify information such as a slice type corresponding to the session connection, and can be used for performing differentiated scheduling of different slices. Wait for the operation.
  • the first control plane request message is an NGAP message, such as PDU SESSION RESOURCE SETUP REQUEST, or PDU SESSION RESOURCE MODIFY REQUEST, or INITIAL CONTEXT SETUP REQUEST.
  • the session connection is a PDU session or a PDU session resource.
  • the data stream is a QoS flow.
  • the slice related information is a slice type or S-NSSAI.
  • the host base station sends a second control plane request message to the first relay node on the first radio interface, where the first relay node receives the second control plane request message sent by the host base station on the first radio interface, where the The second control plane request message is used to request the first relay node to allocate resources for the session connection of the first device.
  • the second control plane request message includes any one of the following information of the first device or a combination of any multiple: a first identifier, a third identifier, session connection identifier information, second transport layer information, and slice correlation Information, QoS parameters for session connections, data flow identification information, QoS parameters for data flows, and NAS messages related to session connection establishment.
  • the second transport layer information is information corresponding to the session connection that distinguishes different GTP tunnels on the first radio interface, such as a GTP TEID and/or a transport layer address, for uplink data transmission.
  • the second transport layer information may be the same as the first transport layer information, that is, the host base station does not change the information and directly sends the information to the first relay node; or the second transport layer information is different from the first transport layer information, that is, the host The base station allocates transport layer information (for example, GTP TEID) to the session connection, and replaces the first transport layer information as the second transport layer information, and sends the information to the first relay node.
  • transport layer information for example, GTP TEID
  • the host base station sends the first radio bearer configuration information to the first relay node on the first radio interface, for adding, modifying, and releasing the radio bearer on the first radio interface.
  • the first radio bearer configuration information includes any one of the following information or a combination of any one of the following: first relay node identifier information, radio bearer identifier information, configuration information of the SDAP, configuration information of the PDCP, and RLC Configuration information, configuration information of the logical channel, identification information of the first device, session connection identification information, and data flow identification information.
  • the radio bearer identification information may be a DRB identifier.
  • the first radio bearer configuration information is carried in an RRC message of the first relay node on the first radio interface (for example, an RRC reconfiguration value message), and is sent separately from the second control plane request message; or the first a radio bearer configuration information is included in the second control plane request message as a container (for example, an RRC container); or the second control plane request message is used as a container (for example, an NGAP message container) together with the first bearer configuration information, Contained in the same RRC message (for example, RRC reconfiguration value message).
  • the first relay node may identify, according to the inclusion relationship of the container and the message/information, the association relationship between the wireless bearer of the first relay node and the session connection (and the data flow) of the first device.
  • the first relay node may obtain the correspondence between the session connection identifier information and/or the data stream identifier information of the first device and the radio bearer identifier information of the first radio interface by using the foregoing first radio bearer configuration information.
  • the control plane protocol stack has multiple options, the format and information content of the second control plane request message are different under different protocol stack architectures.
  • the second control plane request message is an NGAP message, and is carried in the DRB of the first relay node of the first radio interface, where the message carries the first The identifier and/or the third identifier are used to identify the first device; in the case of the control plane protocol stack architecture 1-B, the second control plane request message is an NGAP message, and is carried by the first relay node of the first wireless interface. In the SRB, the message carries the first identifier and/or the third identifier, which is used to identify the first device.
  • the second control plane request message is an RRC message, which is carried in the And transmitting, by the first relay node of the wireless interface, the first identifier and/or the third identifier, where the first identifier and the third identifier are not used as the NGAP ID.
  • the first relay node receives the second control plane request message at the first wireless interface.
  • the first relay node acquires, according to the first radio bearer configuration information, a mapping relationship between the session connection and/or the data flow of the uplink first device and the DRB of the first relay node on the first radio interface. Since the user plane protocol stack has multiple candidate modes, the specific process of the first relay node transmitting the uplink data packet of the first device on the first wireless interface is also slightly different. Exemplarily, in a case where the first relay node and the host base station have a GTP-U protocol layer on the first radio interface (as shown in FIG. 21), the first relay node receives the first device on the second radio interface.
  • An uplink data packet generating a GTP-U data packet based on the session connection identification information and/or the data flow identification information corresponding thereto (adding transport layer information, such as a GTP TEID, in the GTP-U data packet header according to the second transport layer information);
  • the data stream identification information is added to the GTP-U data packet; and the GTP-U data packet is carried on the DRB of the first wireless interface according to the first radio bearer configuration information.
  • the first relay node receives the uplink data packet of the first device on the second radio interface;
  • Corresponding session connection identification information and/or data flow identification information adding an adaptive identifier, configured to identify the first device and the session connection and/or the data flow corresponding to the first device on the first wireless interface, and generate the first
  • the wireless interface data packet is configured to transmit the first wireless interface data packet on the DRB of the first wireless interface according to the first radio bearer configuration information.
  • the first relay node if the first relay node does not establish a radio bearer corresponding to the radio bearer identification information indicated in the first radio bearer configuration information, the first relay node establishes and configures the radio based on the first radio bearer configuration information. Hosted.
  • the first radio node sends, by the second radio interface, the second radio bearer configuration information to the first device, where the second radio bearer configuration information is used to add, modify, and release the radio bearer on the second radio interface.
  • the second radio bearer configuration information includes any one of the following information or a combination of any one of the following: first device identifier information, radio bearer identifier information, configuration information of the SDAP, session connection identifier information, and data stream identifier information. , PDCP configuration information, RLC configuration information, and logical channel configuration information.
  • the radio bearer identification information may be a DRB identifier.
  • the first device acquires, by using the foregoing second radio bearer configuration information, the correspondence between the session connection identifier information and/or the data stream identifier information of the first device and the radio bearer identifier information of the second radio interface.
  • the first relay node receives the uplink data packet of the first device on the second radio interface, and learns, according to the radio bearer and/or the logical channel that carries the data packet, the session connection to which the uplink data packet belongs. / or data stream.
  • the first relay node sends the NAS message of the first device to the first device on the second wireless interface, and receives the NAS response message.
  • the first relay node sends a second control plane response message to the host base station on the first radio interface, and is configured to respond to the second control plane request message.
  • the second control plane response message includes any one of the following information related to the first device or a combination of any one of the following: a first identifier, a third identifier, session connection identifier information, and third transport layer information, Slice related information, data flow identification information, and NAS response messages related to session connection establishment.
  • the third transport layer information is information corresponding to the session connection that distinguishes different GTP tunnels on the first radio interface, such as a GTP TEID and/or a transport layer address, for downlink data transmission.
  • the third transport layer information is allocated by the first relay node.
  • the first relay node sends the first radio bearer configuration completion information to the first relay node on the first radio interface, to indicate that the radio bearer on the first radio interface is configured.
  • the first radio bearer configuration completion information is carried in an RRC message of the first relay node on the first radio interface (for example, an RRC reconfiguration value completion message), and is sent and sent separately from the second control plane response message.
  • the first radio bearer configuration completion information is included in the second control plane response message as a container (for example, an RRC container); or the second control plane response message is used as a container (for example, an NGAP message container) Together with the first bearer configuration completion information described above, it is included in the same RRC message (eg, RRC reconfiguration value completion message).
  • the format and information content of the second control plane response message are similar to the second control plane request message, and are not described here.
  • the host base station receives, on the first wireless interface, a second control plane response message sent by the first relay node.
  • the host base station sends a first control plane response message to the core network control plane node (for example, AMF) through the NG interface, and is configured to respond to the first control plane request message.
  • AMF core network control plane node
  • the first control plane response message includes any one of the following information related to the first device or a combination of any multiple: a first terminal identifier, a second terminal identifier, session connection identifier information, and a fourth transmission Layer information, slice related information, data flow identification information, and NAS response messages related to session connection establishment.
  • the fourth transport layer information is NG-U tunnel establishment information corresponding to the session connection, for example, a GTP TEID and/or a transport layer address of the donor base station, for downlink data transmission.
  • the fourth transport layer information may be different from the third transport layer information, that is, the host base station allocates transport layer information (for example, GTP TEID) for the session connection, and replaces the third transport layer information as the fourth transport layer information, and sends the information.
  • the first control plane response message is an NGAP message, such as PDU SESSION RESOURCE SETUP RESPONSE, or PDU SESSION RESOURCE MODIFY RESPONSE, or INITIAL CONTEXT SETUP RESPONSE.
  • the host base station when the host base station transmits the downlink data of the session connection of the first device on the first wireless interface, generate a GTP-U data packet based on the third transmission information, for example, adding a third transmission to the GTP-U data packet.
  • FIG. 22 shows a schematic flow chart of a method 700 for a three-hop RN/terminal device to establish a session through a control plane.
  • the host base station configures a first mapping relationship for the first relay node.
  • the first relay node configures a second mapping relationship for the second relay node.
  • the method 700 includes:
  • the second device accesses the second relay node by using the third wireless interface, and further, the second wireless interface between the second relay node and the first relay node, and the first relay node and the host base station.
  • the first wireless interface transmits signaling and data to the core network.
  • the second device may be a terminal device or an RN, such as a third relay node.
  • the first wireless interface is the Un1 port; the second wireless interface is the Un2 port; when the second device is the terminal device, the third wireless interface is the Uu port; when the second device is the RN, the third wireless interface is the Un3 port. .
  • the core network control plane node (for example, AMF) sends a first control plane request message to the host base station by using the NG interface, and the host base station receives the first control plane request message sent by the core network control plane node by using the NG interface, where the A control plane request message is used to request the host base station to allocate resources for the session connection to the second device.
  • AMF core network control plane node
  • the first control plane request message includes any one of the following information related to the second device or a combination of any one of the following: the first terminal identifier, the second terminal identifier, the session connection identifier information, and the first transmission Layer information, slice related information, QoS parameters for session connections, data flow identification information, QoS parameters for data flows, and NAS messages related to session connection establishment.
  • the first transport layer information is NG-U tunnel establishment information corresponding to the session connection, for example, a GTP TEID and/or a transport layer address including a core network user plane node, for uplink data transmission.
  • the first terminal identifier and/or the second terminal identifier are used to identify the second device.
  • the first control plane request message is an NGAP message, such as PDU SESSION RESOURCE SETUP REQUEST, or PDU SESSION RESOURCE MODIFY REQUEST, or INITIAL CONTEXT SETUP REQUEST.
  • the session connection is a PDU session or a PDU session resource.
  • the data stream is a QoS flow.
  • the slice related information is a slice type or S-NSSAI.
  • the host base station sends a second control plane request message to the first relay node to the first relay node, where the first relay node receives the second control sent by the host base station on the first wireless interface.
  • the second request plane request message is used to request the first relay node to allocate resources for the session connection of the second device.
  • the second control plane request message includes any one of the following information of the second device or a combination of any multiple: a first identifier, a third identifier, session connection identifier information, second transport layer information, and slice correlation Information, QoS parameters for session connections, data flow identification information, QoS parameters for data flows, and NAS messages related to session connection establishment.
  • the second transport layer information is information corresponding to the session connection that distinguishes different GTP tunnels on the first radio interface, such as a GTP TEID and/or a transport layer address, for uplink data transmission.
  • the second transport layer information may be the same as the first transport layer information, that is, the host base station does not change the information and directly sends the information to the first relay node; or the second transport layer information is different from the first transport layer information, that is, the host The base station allocates transport layer information (for example, GTP TEID) to the session connection, and replaces the first transport layer information as the second transport layer information, and sends the information to the first relay node.
  • transport layer information for example, GTP TEID
  • the host base station sends the first radio bearer configuration information to the first relay node on the first radio interface, for adding, modifying, and releasing the radio bearer on the first radio interface.
  • the first radio bearer configuration information includes any one of the following information or a combination of any one of the following: first relay node identifier information, radio bearer identifier information, configuration information of the SDAP, configuration information of the PDCP, and RLC Configuration information, configuration information of the logical channel, identification information of the second device, session connection identification information, and data flow identification information.
  • the radio bearer identification information may be a DRB identifier.
  • the first radio bearer configuration information is carried in an RRC message of the first relay node on the first radio interface (for example, an RRC reconfiguration value message), and is sent separately from the second control plane request message; or the first a radio bearer configuration information is included in the second control plane request message as a container (for example, an RRC container); or the second control plane request message is used as a container (for example, an NGAP message container) together with the first bearer configuration information, It is included in the same RRC message (for example, RRC reconfiguration value message).
  • the first relay node may identify, according to the inclusion relationship between the container and the message/information, the association relationship between the wireless bearer of the first relay node and the session connection (and the data flow) of the second device.
  • the first relay node may obtain the correspondence between the session connection identifier information and/or the data stream identifier information of the second device and the radio bearer identifier information of the first radio interface by using the foregoing first radio bearer configuration information.
  • the control plane protocol stack has multiple options, the format and information content of the second control plane request message are different under different protocol stack architectures.
  • the second control plane request message is an NGAP message, and is carried in the DRB of the first relay node of the first radio interface, where the message carries the first The identifier and/or the third identifier are used to identify the second device; in the case of the control plane protocol stack architecture 1-B, the second control plane request message is an NGAP message, and is carried by the first relay node of the first wireless interface. In the SRB, the message carries the first identifier and/or the third identifier, and is used to identify the second device.
  • the second control plane request message is an RRC message, which is carried in the
  • the first relay node of the wireless interface is transmitted in the SRB, and the message carries the first identifier and/or the third identifier, and is used to identify the second device.
  • the first identifier/third identifier is not the NGAP ID.
  • the first relay node acquires, according to the first radio bearer configuration information, a mapping relationship between the session connection and/or the data flow of the uplink second device and the DRB of the first relay node on the first radio interface. Since the user plane protocol stack has multiple candidate modes, the specific process of the first relay node transmitting the uplink data packet of the second device on the first wireless interface is also slightly different.
  • the first relay node receives the uplink data packet of the second device on the second radio interface; Session connection identification information and/or data flow identification information, generating a GTP-U data packet (adding transport layer information, such as GTP TEID, in the GTP-U data packet header according to the second transport layer information); optionally, in GTP- The data packet identification information is added to the U data packet; the GTP-U data packet is carried on the DRB of the first radio interface according to the first radio bearer configuration information.
  • the first relay node receives the uplink data packet of the second device on the second radio interface;
  • Corresponding session connection identification information and/or data flow identification information adding an adaptive identifier, configured to identify the second device and the session connection and/or the data flow corresponding to the second device on the first wireless interface, and generate the first
  • the wireless interface data packet is configured to transmit the first wireless interface data packet on the DRB of the first wireless interface according to the first radio bearer configuration information.
  • the first relay node if the first relay node does not establish a radio bearer corresponding to the radio bearer identification information indicated in the first radio bearer configuration information, the first relay node establishes and configures the radio based on the first radio bearer configuration information. Hosted.
  • the first relay node sends a third control plane request message to the second relay node, where the second relay node receives the third sent by the first relay node on the second radio interface.
  • Control plane request message the third control plane request message is used to request the second relay node to allocate resources for the session connection of the second device.
  • the third control plane request message includes any one of the following information of the second device or a combination of any multiple: a fourth identifier, a fifth identifier, session connection identifier information, fifth transport layer information, and slice correlation Information, QoS parameters for session connections, data flow identification information, QoS parameters for data flows, and NAS messages related to session connection establishment.
  • the fourth identifier and/or the fifth identifier are used to identify the second device on the second wireless interface;
  • the fifth transport layer information is information corresponding to the session connection that distinguishes different GTP tunnels on the second wireless interface, for example, GTP TEID and/or transport layer address for upstream data transmission.
  • the fifth transport layer information may be the same as the second transport layer information, that is, the first relay node does not change the information and directly sends the information to the second relay node; or the fifth transport layer information is different from the second transport layer information. That is, the first relay node allocates transport layer information (for example, GTP TEID) for the session connection, and replaces the second transport layer information as the fifth transport layer information, and sends the information to the second relay node.
  • transport layer information for example, GTP TEID
  • the session connection identifier information, the slice related information, the session connection QoS parameter, the data flow identifier information, the QoS parameter of the data flow, and the NAS message related to the session connection establishment in the third control plane request message The contents of the second control plane request message are the same.
  • the first relay node sends the second radio bearer configuration information to the second relay node on the second radio interface, where the radio bearer on the second radio interface is added, modified, and released.
  • the second radio bearer configuration information includes any one of the following information or a combination of any one of the following: the second relay node identifier information, the radio bearer identifier information, the configuration information of the SDAP, the configuration information of the PDCP, and the RLC. Configuration information, configuration information of the logical channel, identification information of the second device, session connection identification information, and data flow identification information.
  • the radio bearer identification information may be a DRB identifier.
  • the second radio bearer configuration information is carried in an RRC message of the second relay node on the second radio interface (for example, an RRC reconfiguration value message), and is sent separately from the third control plane request message; or the first
  • the second radio bearer configuration information is included in the third control plane request message as a container (for example, an RRC container); or the third control plane request message is used as a container (for example, an NGAP message container) together with the second bearer configuration information. Contained in the same RRC message (for example, RRC reconfiguration value message).
  • the second relay node may identify an association relationship between the wireless bearer of the second relay node and the session connection (and the data flow) of the second device based on the inclusion relationship of the container and the message/information.
  • the second relay node may obtain the correspondence between the session connection identifier information and/or the data stream identifier information of the second device and the radio bearer identifier information of the second radio interface by using the foregoing second radio bearer configuration information.
  • the control plane protocol stack has multiple options, the format and information content of the third control plane request message are different under different protocol stack architectures.
  • the second control plane request message is an NGAP message, and is carried in the DRB of the second relay node of the second radio interface;
  • the second control plane request message is an NGAP message, and is carried in the SRB of the second relay node of the second radio interface;
  • the second The control plane request message is an RRC message, and is carried in the SRB of the second relay node of the second radio interface, and the fourth identifier/fifth identifier is not the NGAP ID.
  • the second relay node receives the third control plane request message at the second wireless interface.
  • the second relay node acquires, according to the second radio bearer configuration information, a mapping relationship between the session connection and/or the data flow of the uplink second device and the DRB of the second relay node on the second radio interface. Since the user plane protocol stack has multiple candidate modes, the specific process of the second relay node transmitting the uplink data packet of the second device on the second wireless interface is also slightly different.
  • the second relay node on the second radio interface has a peer GTP-U protocol layer with the first relay node, the second relay node receives the uplink of the second device on the third radio interface.
  • the data stream identification information is added to the GTP-U data packet; and the GTP-U data packet is carried on the DRB of the second wireless interface according to the second radio bearer configuration information.
  • the second relay node when the second relay node and the host base station do not have the GTP-U protocol layer on the second radio interface, the second relay node receives the uplink data packet of the second device on the third radio interface; Corresponding session connection identification information and/or data flow identification information, adding an adaptive identifier, configured to identify, by the second wireless interface, the second device and the session connection and/or the data flow corresponding to the second device, and generate the second The wireless interface data packet is configured to transmit the second wireless interface data packet on the DRB of the second wireless interface according to the second radio bearer configuration information.
  • the second relay node if the second relay node does not establish a radio bearer corresponding to the radio bearer identification information indicated in the second radio bearer configuration information, the second relay node establishes and configures the radio based on the second radio bearer configuration information. Hosted.
  • the second relay node sends the third radio bearer configuration information to the second device on the third radio interface, where the radio bearer on the third radio interface is added, modified, and released.
  • the third radio bearer configuration information includes any one of the following information or a combination of any one of the following: the second device identifier information, the radio bearer identifier information, the configuration information of the SDAP, the session connection identifier information, and the data stream identifier information. , PDCP configuration information, RLC configuration information, and logical channel configuration information.
  • the radio bearer identification information may be a DRB identifier.
  • the second device acquires the correspondence between the session connection identifier information and/or the data stream identifier information of the second device and the radio bearer identifier information of the third radio interface by using the foregoing third radio bearer configuration information.
  • the second relay node receives the uplink data packet of the second device on the third radio interface, and learns, according to the radio bearer and/or the logical channel that carries the data packet, the session connection to which the uplink data packet belongs. / or data stream.
  • the second relay node sends the NAS message of the second device to the second device on the third wireless interface, and receives the NAS response message.
  • the second relay node sends a third control plane response message to the first relay node on the second radio interface, where the first relay node receives the second relay node sent by the second relay node.
  • the third control plane response message is used to respond to the third control plane request message.
  • the third control plane response message includes any one of the following information related to the second device or a combination of any multiple: a fourth identifier, a fifth identifier, session connection identifier information, and a sixth transport layer information, Data flow identification information, and NAS response messages related to session connection establishment.
  • the sixth transport layer information is information corresponding to the session connection that distinguishes different GTP tunnels on the second radio interface, such as a GTP TEID and/or a transport layer address, for downlink data transmission.
  • the sixth transport layer information is allocated by the second relay node.
  • the second relay node sends, by the second radio interface, the second radio bearer configuration completion information to the first relay node, to indicate that the radio bearer on the second radio interface is configured.
  • the second radio bearer configuration completion information is carried in an RRC message of the second relay node on the second radio interface (for example, an RRC reconfiguration value completion message), and is sent and sent separately from the second control plane response message.
  • the second radio bearer configuration completion information is included as a container (eg, RRC container) in response to the third control plane response message; or the third control plane response message is used as a container (eg, an NGAP message container) Together with the second bearer configuration completion information described above, it is included in the same RRC message (eg, RRC reconfiguration value completion message).
  • the format and information content of the third control plane response message are similar to the third control plane request message, and are not described here.
  • the first relay node receives the third control plane response message sent by the second relay node on the second wireless interface.
  • the first relay node sends a second control plane response message to the donor base station on the first wireless interface, in response to the second control plane request message.
  • the second control plane response message includes any one or any combination of the following information related to the second device: a first identifier, a third identifier, session connection identifier information, and third transport layer information, Slice related information, data flow identification information, and NAS response messages related to session connection establishment.
  • the third transport layer information is information corresponding to the session connection that distinguishes different GTP tunnels on the first radio interface, such as a GTP TEID and/or a transport layer address, for downlink data transmission.
  • the third transport layer information is different from the sixth transport layer information, that is, the first relay node allocates transport layer information (for example, GTP TEID) to the session connection, and replaces the sixth transport layer information as the third transport layer information. , sent to the host base station node.
  • transport layer information for example, GTP TEID
  • the first relay node sends the first radio bearer configuration completion information to the first relay node on the first radio interface, to indicate that the radio bearer on the first radio interface is configured.
  • the first radio bearer configuration completion information is carried in an RRC message of the first relay node on the first radio interface (for example, an RRC reconfiguration value completion message), and is sent and sent separately from the second control plane response message.
  • the first radio bearer configuration completion information is included in the second control plane response message as a container (for example, an RRC container); or the second control plane response message is used as a container (for example, an NGAP message container) Together with the first bearer configuration completion information described above, it is included in the same RRC message (eg, RRC reconfiguration value completion message).
  • the format and information content of the second control plane response message are similar to the second control plane request message, and are not described here.
  • the first relay node sends a second control plane response message to the host base station on the first radio interface, where the host base station receives a second control plane response message sent by the first relay node on the first radio interface.
  • the second control plane response message is responsive to the second control plane request message.
  • the host base station sends a first control plane response message to the core network control plane node (for example, AMF) through the NG interface, where the core network control plane node receives the first control plane response message sent by the host base station on the over-NG interface.
  • the first control plane response message is responsive to the first control plane request message.
  • the first control plane response message includes any one of the following information related to the second device or a combination of any one of the following: the first terminal identifier, the second terminal identifier, the session connection identifier information, and the fourth transmission Layer information, slice related information, data flow identification information, and NAS response messages related to session connection establishment.
  • the fourth transport layer information is NG-U tunnel establishment information corresponding to the session connection, for example, a GTP TEID and/or a transport layer address of the donor base station, for downlink data transmission.
  • the fourth transport layer information may be different from the third transport layer information, that is, the host base station allocates transport layer information (for example, GTP TEID) for the session connection, and replaces the third transport layer information as the fourth transport layer information, and sends the information.
  • the first control plane response message is an NGAP message, such as PDU SESSION RESOURCE SETUP RESPONSE, or PDU SESSION RESOURCE MODIFY RESPONSE, or INITIAL CONTEXT SETUP RESPONSE.
  • the host base station when the host base station transmits the downlink data of the session connection of the second device on the first wireless interface, generate a GTP-U data packet based on the third transmission information, for example, add a third transmission to the GTP-U data packet.
  • the GTP-U data packet is generated based on the sixth transmission information, for example, added in the GTP-U data packet.
  • FIG. 23 shows a schematic flowchart of a method 800 for performing session establishment by a three-hop RN/terminal device through a control plane based on the control plane protocol stacks 1-A-B and 1-B-B according to an embodiment of the present application.
  • the host base station configures a first mapping relationship for the first relay node, and the host base station configures a second mapping relationship for the second relay node, but the configuration information of the second mapping relationship is transmitted by the first relay node to the second relay node.
  • a node (which may be transparently transmitted or sent to the second relay node after being processed by the first relay node).
  • the method 800 includes:
  • the second device accesses the second relay node by using the third wireless interface, and further, the second wireless interface between the second relay node and the first relay node, and the first relay node and the host base station.
  • the first wireless interface transmits signaling and data to the core network.
  • the second device may be a terminal device or an RN, such as a third relay node.
  • the first wireless interface is the Un1 port; the second wireless interface is the Un2 port; when the second device is the terminal device, the third wireless interface is the Uu port; when the second device is the RN, the third wireless interface is the Un3 port. .
  • the core network control plane node (for example, AMF) sends a first control plane request message through the NG interface, and the host base station receives the first control plane request message through the NG interface.
  • the first control plane request message is used to request the host base station to allocate resources of the session connection to the second device.
  • the first control plane request message includes any one of the following information related to the second device or a combination of any one of the following: the first terminal identifier, the second terminal identifier, the session connection identifier information, and the first transmission Layer information, slice related information, QoS parameters for session connections, data flow identification information, QoS parameters for data flows, and NAS messages related to session connection establishment.
  • the first transport layer information is an NG-U tunnel establishment information corresponding to the session connection, for example, a GTP TEID and/or a transport layer address including a core network user plane node, for uplink data transmission.
  • the first terminal identifier and/or the second terminal identifier are used to identify the second device.
  • the first control plane request message is an NGAP message, such as PDU SESSION RESOURCE SETUP REQUEST, or PDU SESSION RESOURCE MODIFY REQUEST, or INITIAL CONTEXT SETUP REQUEST.
  • the session connection is a PDU session or a PDU session resource.
  • the data stream is a QoS flow.
  • the slice related information is a slice type or S-NSSAI.
  • the host base station sends a second control plane request message to the first relay node on the first radio interface, where the first relay node receives the second control plane request message sent by the host base station.
  • the second control plane request message includes any one of the following information of the second device or a combination of any multiple: a fourth identifier, a third identifier, session connection identifier information, second transport layer information, and slice correlation Information, QoS parameters for session connections, data flow identification information, QoS parameters for data flows, and NAS messages related to session connection establishment.
  • the second transport layer information is information corresponding to the session connection that distinguishes different GTP tunnels on the first radio interface, such as a GTP TEID and/or a transport layer address, for uplink data transmission.
  • the second transport layer information may be the same as the first transport layer information, that is, the host base station does not change the information and directly sends the information to the first relay node; or the second transport layer information is different from the first transport layer information, that is, the host The base station allocates transport layer information (for example, GTP TEID) to the session connection, and replaces the first transport layer information as the second transport layer information, and sends the information to the first relay node.
  • transport layer information for example, GTP TEID
  • the host base station sends the first radio bearer configuration information to the first relay node on the first radio interface, for adding, modifying, and releasing the radio bearer on the first radio interface.
  • the first radio bearer configuration information includes any one of the following information or a combination of any one of the following: first relay node identifier information, radio bearer identifier information, configuration information of the SDAP, configuration information of the PDCP, and RLC Configuration information, configuration information of the logical channel, identification information of the second device, session connection identification information, QoS parameters of the session connection, data flow identification information, QoS parameters of the data flow, and the second relay node on the second wireless interface Wireless bearer identification information.
  • the radio bearer identification information may be a DRB identifier.
  • the first radio bearer configuration information is carried in an RRC message of the first relay node (for example, an RRC reconfiguration value message) on the first radio interface, and is sent separately from the second control plane request message.
  • RRC message of the first relay node for example, an RRC reconfiguration value message
  • the first relay node receives the second control plane request message on the first radio interface, and does not perform parsing, and directly forwards to the second relay node by using the second radio interface, where the second relay node receives the second radio interface.
  • Two control plane request messages The first relay node receives the first radio bearer configuration information on the first radio interface.
  • the first relay node obtains the radio bearer identifier information of the first radio interface.
  • the correspondence between the radio bearer identification information of the second relay node on the second radio interface is used for sending uplink and/or downlink data packets.
  • the downlink data of the radio bearer carried on the first radio interface is sent by the second relay node on the radio bearer on the second radio interface; or the second relay node is carried in the second radio node.
  • the uplink data of the radio bearer on the radio interface is sent through the radio bearer on the first radio interface.
  • the first relay node if the first relay node does not establish a radio bearer corresponding to the radio bearer identification information indicated in the first radio bearer configuration information, the first relay node establishes and configures the radio based on the first radio bearer configuration information. Hosted.
  • the first relay node sends the second radio bearer configuration information to the second relay node on the second radio interface, where the radio bearer on the second radio interface is added, modified, and released.
  • the second radio bearer configuration information includes any one of the following information or a combination of any one of the following: the second relay node identifier information, the radio bearer identifier information, the configuration information of the SDAP, the configuration information of the PDCP, and the RLC. Configuration information, configuration information of the logical channel, identification information of the second device, session connection identification information, and data flow identification information.
  • the first relay node acquires, by using the first radio bearer configuration information, the correspondence between the radio bearer identifier information of the second relay node and the session connection identifier information (and the data stream identifier information) of the second device, and then carries the The second radio bearer configuration information.
  • the correspondence between the radio bearer identifier information of the second relay node and the session connection identifier information (and the data stream identifier information) of the second device may be carried in the first radio bearer configuration information as a container, where The relay node is directly transmitted to the second relay node without parsing.
  • the first relay node performs the radio bearer protocol of the second radio interface by using the QoS parameter of the session connection and/or the QoS parameter of the data flow carried in the first radio bearer configuration information.
  • Stack configuration such as logical channel configuration information (eg, scheduling priority, etc.).
  • the second radio bearer configuration information is carried in an RRC message of the second relay node on the second radio interface (for example, an RRC reconfiguration value message), and is sent separately from the second control plane request message.
  • the second relay node acquires, according to the second radio bearer configuration information, a mapping relationship between the session connection and/or the data flow of the uplink second device and the DRB of the second relay node on the second radio interface. Since the user plane protocol stack has multiple candidate modes, the specific process of the second relay node transmitting the uplink data packet of the second device on the second wireless interface is also slightly different. Illustratively, in a case where the second relay node on the second radio interface has a peer GTP-U protocol layer with the first relay node, the second relay node receives the uplink of the second device on the third radio interface.
  • a data packet generating a GTP-U data packet based on the session connection identification information and/or the data flow identification information corresponding thereto (adding transport layer information (for example, GTP TEID) in the GTP-U data packet header according to the second transport layer information;
  • the data stream identification information is added to the GTP-U data packet; and the GTP-U data packet is carried on the DRB of the second wireless interface according to the second radio bearer configuration information.
  • the second relay node when the second relay node and the host base station do not have the GTP-U protocol layer on the second radio interface, the second relay node receives the uplink data packet of the second device on the third radio interface; Corresponding session connection identification information and/or data flow identification information, adding an adaptive identifier, configured to identify, by the second wireless interface, the second device and the session connection and/or the data flow corresponding to the second device, and generate the second The wireless interface data packet is configured to transmit the second wireless interface data packet on the DRB of the second wireless interface according to the second radio bearer configuration information.
  • the second relay node if the second relay node does not establish a radio bearer corresponding to the radio bearer identification information indicated in the second radio bearer configuration information, the second relay node establishes and configures the radio based on the second radio bearer configuration information. Hosted.
  • the second relay node sends the third radio bearer configuration information to the second device, where the second device receives the third radio bearer configuration information sent by the second relay node.
  • the third radio bearer configuration information is used to add, modify, and release radio bearers on the third radio interface.
  • the third radio bearer configuration information includes any one of the following information or a combination of any one of the following: the second device identifier information, the radio bearer identifier information, the configuration information of the SDAP, the session connection identifier information, and the data stream identifier information. , PDCP configuration information, RLC configuration information, and logical channel configuration information.
  • the radio bearer identification information may be a DRB identifier.
  • the second device acquires the correspondence between the session connection identifier information and/or the data stream identifier information of the second device and the radio bearer identifier information of the third radio interface by using the foregoing third radio bearer configuration information.
  • the second relay node receives the uplink data packet of the second device on the third radio interface, and learns, according to the radio bearer and/or the logical channel that carries the data packet, the session connection to which the uplink data packet belongs. / or data stream.
  • the second relay node sends the NAS message of the second device to the second device on the third wireless interface, and receives the NAS response message.
  • the second relay node sends a second control plane response message to the first relay node on the second radio interface, and is configured to respond to the second control plane request message.
  • the second control plane response message includes any one of the following information related to the second device or a combination of any multiple: a fourth identifier, a third identifier, session connection identifier information, and sixth transport layer information, Data flow identification information, and NAS response messages related to session connection establishment.
  • the sixth transport layer information is information corresponding to the session connection that distinguishes different GTP tunnels on the second radio interface, such as a GTP TEID and/or a transport layer address, for downlink data transmission.
  • the sixth transport layer information is allocated by the second relay node.
  • the second relay node sends, by the second radio interface, the second radio bearer configuration completion information to the first relay node, to indicate that the radio bearer on the second radio interface is configured.
  • the second radio bearer configuration completion information is carried in an RRC message of the second relay node on the second radio interface (for example, an RRC reconfiguration value completion message), and is sent and sent separately from the second control plane response message. There is no order in the order.
  • the first relay node receives the second control plane response message sent by the second relay node on the second radio interface, and does not perform parsing, and directly forwards the message to the host base station, where the host base station receives the first medium on the first radio interface.
  • the second control plane response message sent by the node is
  • the first relay node sends the first radio bearer configuration completion information to the first relay node on the first radio interface, to indicate that the radio bearer on the first radio interface is configured.
  • the first radio bearer configuration completion information is carried in an RRC message of the first relay node on the first radio interface (for example, an RRC reconfiguration value completion message), and is sent and sent separately from the second control plane response message. There is no order in the order.
  • the host base station sends a first control plane response message to the core network control plane node (for example, AMF) through the NG interface, where the core network control plane node receives the first control plane response message sent by the host base station on the NG interface, where The first control plane response message is for responding to the first control plane request message.
  • the core network control plane node for example, AMF
  • the first control plane response message includes any one of the following information related to the second device or a combination of any one of the following: the first terminal identifier, the second terminal identifier, the session connection identifier information, and the fourth transmission Layer information, slice related information, data flow identification information, and NAS response messages related to session connection establishment.
  • the fourth transport layer information is NG-U tunnel establishment information corresponding to the session connection, for example, a GTP TEID and/or a transport layer address of the donor base station, for downlink data transmission.
  • the fourth transport layer information may be different from the sixth transport layer information, that is, the host base station allocates transport layer information (for example, GTP TEID) to the session connection, and replaces the sixth transport layer information as the fourth transport layer information, and sends the information.
  • transport layer information for example, GTP TEID
  • the first control plane response message is an NGAP message, such as PDU SESSION RESOURCE SETUP RESPONSE, or PDU SESSION RESOURCE MODIFY RESPONSE, or INITIAL CONTEXT SETUP RESPONSE.
  • the host base station when the host base station transmits downlink data of the session connection of the second device on the first wireless interface, generate a GTP-U data packet based on the sixth transmission information, for example, adding a sixth transmission to the GTP-U data packet.
  • the first relay node receives the downlink data of the session connection of the second device on the first radio interface, and is based on the radio bearer and the second radio of the first radio interface acquired in the first radio bearer configuration information.
  • the above methods 400 and 500 are introduced by combining the protocol stack architecture.
  • FIG. 24 and FIG. 27 are schematic diagrams showing two L3 protocol stack user plane architectures according to an embodiment of the present application.
  • a second radio interface ie, Un2 or Uu interface
  • the DRB carries the data transmission of the RN2/UE itself (and the UE served by the RN2); the uplink of this part of the data needs to be forwarded to the Donor by the RN1 through the first radio interface (ie, Un1), and then forwarded to the corresponding core network through the Donor.
  • the downlink of the data is sent by the core network to the Donor and sent to the RN2/UE via the RN1. Therefore, it is necessary to determine the DRB used by the RN1 to forward the uplink and/or downlink data, and the manner in which the first wireless interface forwards data (for example, GTP). Packet, or SDAP SDU packet).
  • FIG. 24 shows a schematic diagram of an L3 protocol stack user plane architecture 1 according to an embodiment of the present application, where the protocol stack of the Un1 port includes a GTP-U protocol layer, and the GTP data packet bearer is transmitted in the Un1 DRB.
  • the host base station is the same as the protocol stack of the core network user plane node serving the RN.
  • the specific protocol stack is similar to the prior art and will not be described here.
  • the control plane requests to establish a session connection (for example, a PDU session) and/or a data flow (for example, QoS flow) corresponding to the session connection, and the core network configures the NG-U interface for the RN2/UE.
  • the data transmission tunnel is sent, and the tunnel establishment information is sent to the host base station through the NGAP message of the NG-C.
  • the foregoing control plane process involves the following information interaction: on the NG-C interface, the core network sends the RN2/UE related information in any one or any combination of the following to the host base station through the NGAP message: Identification information of the session connection, identification information of the data flow, QoS parameters, and NG-U tunnel establishment information.
  • the NG-U tunnel establishment information may include any one of the following information or a combination of any one of the following: GTP-U TEID, IP address, and port number.
  • the host base station and the RN1 have a peer-to-peer protocol layer, specifically including: a GTP-U layer, a UDP layer (optionally), an IP layer (optionally), and an SDAP layer (optionally, It can be configured as transparent transmission, PDCP layer, RLC layer, MAC layer, and PHY layer.
  • the GTP-U layer (which may also be combined with the UDP layer and/or the IP layer) may be used to distinguish data carried in the same DRB on the Un1 port, for example, a GTP tunnel (optionally, identified by a pair of TEIDs, respectively corresponding to the uplink) And downlink) correspond to a UE/RN session connection.
  • the protocol stack of the Un1 port further includes an adaptive layer function for adding and/or parsing the first adaptive identifier.
  • the adaptive function may be included in an existing protocol layer, such as an SDAP layer/PDCP layer/RLC layer/MAC layer/PHY layer; or the adaptive function may be separately deployed in a protocol layer, for example, referred to as adaptation (Adaptation, Referred to as Adapt layer.
  • the adaptation layer may be deployed between the GTP-U layer and the PDCP layer, or between the PDCP layer and the RLC layer, or between the RLC layer and the MAC layer, or deployed in the MAC and PHY layers. between.
  • the method for distinguishing the data type in the Un1 port and the description of the first adaptive identifier refer to the description of the 1-A protocol stack, and details are not described herein again.
  • the host base station maps the GTP tunnel received by the NG-U to the GTP tunnel of the Un1 port. For example, the host base station allocates the GTP TEID on the NG-U to the corresponding session connection, and informs the core network through the NGAP message of the NG-C. When the core network transmits the data of the session connection, the GTP TEID is used for identification. Ground, carrying the QoS flow identifier on the GTP-U packet.
  • the GTP tunnel of the Un1 port is transmitted on the DRB established for the RN1 on the Un1 port, and any one of the following manners or a combination of any one of the following may be adopted:
  • Manner 1 Map data of one GTP tunnel to the same DRB for transmission
  • Manner 2 The data packets in the GTP tunnel are mapped to multiple DRBs according to the QoS requirements of the data flow. Specifically, one or more QoS flows in the GTP-U are mapped to one DRB, and the QoS requirements of the one or more QoS flows are matched with the DRB.
  • the QoS flows that are mapped to the same GTP-U tunnel on the multiple DRBs use the same GTP TEID, and are used by the RN1 to identify and aggregate the data packets of the GTP tunnel, and send the packets to the Un2/Uu port.
  • the GTP tunnel corresponds to the session connected to the SDAP entity.
  • Manner 3 Assign a class identifier to the data flow in the GTP tunnel (for example, mapping to a QCI according to QoS requirements, where the class identifier is QCI), and multiple data streams can be assigned the same category identifier, one or more categories. The identity is mapped to a DRB. When the packet is transmitted on the Un1 port, the category identifier is carried.
  • the category identifier is carried on a GTP data packet on the Un1 port (for example, DSCP is used to represent QCI).
  • the GTP tunnel corresponds to one session connection of one UE/RN
  • the data of the GTP tunnels of multiple UEs/RNs can be mapped to different DRBs or the same DRB. If it is a different DRB, the DRB carries only one UE/RN data; if it is the same DRB, the DRB may carry data of multiple UE/RNs, and the data may have similar QoS requirements.
  • data for multiple GTP tunnels of one UE/RN can be mapped to different DRBs, or to the same DRB. If it is a different DRB, the DRB only carries data of one session connection of the UE; if it is the same DRB, the DRB may carry data of multiple session connections of the UE/RN, and the data may have similar QoS requirements.
  • the RN1 For the uplink, the RN1 processes the data packet received on the Un2/Uu port (for example, GTP-U encapsulation) based on the first uplink mapping relationship, and then sends the data packet to the host base station through the Un1 port.
  • Un2/Uu port for example, GTP-U encapsulation
  • the data packet sent by the RN1 on the Un1 port carries the first adaptive identifier, and is used by the host base station to distinguish the data on the Un1 port.
  • An optional method is that the RN1 aggregates the data packets received on the Un2 according to the GTP tunnel to generate GTP data packets sent on the Un1 port.
  • the RN1 processes the data packet received at the Un2 port, obtains the PDU session and the QoS flow corresponding to the data packet, and generates a corresponding GTP data packet, where the GTP TEID and the QFI are carried. Then, the RN1 transmits the GTP data packet of the Un2 port to the DRB of the Un1 port of the RN1 in a manner similar to the downlink. For example, any one of the following manners or a combination of any one of the following may be adopted:
  • Manner 1 Map data of one GTP tunnel to the same DRB for transmission
  • Manner 2 The data packets in the GTP tunnel are mapped to multiple DRBs according to the QoS requirements of the data flow. Specifically, one or more QoS flows in the GTP-U are mapped to one DRB, and the QoS requirements of the one or more QoS flows are matched with the DRB. Optionally, the QoS flows that are mapped to the same GTP-U tunnel on the multiple DRBs use the same GTP TEID, and are used by the host base station to identify and aggregate the data packets of the GTP tunnel and send the data packets to the core network.
  • Manner 3 Assign a class identifier to the data flow in the GTP tunnel (for example, mapping to a QCI according to QoS requirements, where the class identifier is QCI), and multiple data streams can be assigned the same category identifier, one or more categories.
  • the identity is mapped to a DRB.
  • the class identifier is carried when the data packet is transmitted on the Un1 port.
  • the category identifier is carried on a GTP data packet on the Un1 port (for example, DSCP is used to represent QCI).
  • the RN1 is based on a correspondence between the PDU session (or GTP TEID) and/or the QFI and the classification identifier (referred to as a classification mapping relationship, optionally, the correspondence may be corresponding to one RN/UE),
  • the classification identifier corresponding to the data packet is obtained, so that the data packet is carried in the DRB based on the correspondence between the classification identifier and the DRB of the Un1 interface.
  • the manner in which the RN1 obtains the classification mapping relationship is: the configuration of the primary base station, or the QAM configuration, or the correspondence between the PDU session (or GTP TEID) and/or the QFI and the classification identifier of the data packet received at the Un1 interface. .
  • Fig. 25 is a diagram showing a data transmission process of an Un1 radio interface. Different data flows in one session connection can be mapped to different Un1 port DRBs; data streams of different UEs/RNs can be mapped to the same Un1 port DRB. Corresponding to the above method 2 (similar to the uplink and downlink).
  • Fig. 26 is a diagram showing a packet mapping process inside RN1 in the data transmission process.
  • the base station part of the RN1 receives the uplink data on the Un2 port, and obtains the PDU session corresponding to the uplink data based on the DRB information carrying the uplink data and the QFI information on the data packet, thereby generating a GTP data packet, where the GTP data packet carries the GTP TEID. And QFI.
  • An optional method is that the RN1 adds a type identifier to the data packet based on the categorization mapping relationship.
  • the type identifier can be carried in the IP layer, for example, by using a DSCP identifier, that is, the type identifier has a correspondence with the DSCP.
  • the UE part of the RN1 reads the type identifier, and the GTP data packet is carried in the Un1 port based on the first uplink mapping relationship.
  • the RN1 adds the DRB identifier to the data packet based on the first uplink mapping relationship.
  • the DRB identifier may be carried in the IP layer, for example, by using a DSCP identifier, that is, the DRB identifier and the DSCP identifier.
  • the UE has a correspondence relationship, and the UE part of the RN1 reads the DRB identifier, and transmits the GTP data packet to the corresponding DRB of the Un1 port.
  • the correspondence between the type identifier/DRB identifier and the DSCP identifier may be internally defined by the RN1, and the base station part and the UE part of the RN1 are correspondingly and interpreted.
  • RN1 and RN2/UE On the Un2/Uu interface, RN1 and RN2/UE have peer-to-peer protocol layers, including: SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer.
  • the protocol stack of the Un port further includes an adaptation layer function for adding and/or parsing the second adaptive identifier.
  • the second adaptation function may be included in an existing protocol layer, such as an SDAP layer/PDCP layer/RLC layer/MAC layer/PHY layer; or the adaptation function may be separately deployed in a protocol layer, for example, called adaptation ( Adaptation, referred to as Adapt) layer.
  • the adaptation layer may be deployed on the SDAP layer, or between the SDAP layer and the PDCP layer, or between the PDCP layer and the RLC layer, or between the RLC layer and the MAC layer, or deployed in the MAC layer. Between the PHY layer.
  • the method for distinguishing the data type in the Un2 port and the description of the second adaptive identifier refer to the previous description, and details are not described herein again.
  • the function may not be enabled at this time, that is, no additional identification is needed.
  • RN1 configures the DRB of the radio interface for the RN2/UE through the control plane RRC message, and simultaneously informs the RN2/UE of the mapping relationship between the QoS flow and the DRB in each uplink PDU session.
  • the RN2/UE transmits the QoS flow to the RN1 based on the correspondence between the PDU session (and QoS flow) and the DRB in the corresponding DRB.
  • FIG. 27 is a schematic diagram of an L3 protocol stack user plane architecture 2 according to an embodiment of the present application, where the protocol stack of the Un1 port does not include the GTP-U protocol layer, and the different identifiers belonging to the Un1 port are distinguished by the adaptive identifier. The data.
  • the host base station is the same as the protocol stack of the core network user plane node serving the RN.
  • the specific protocol stack is similar to the prior art and will not be described here.
  • the control plane requests to establish a session connection (for example, a PDU session) and/or a data flow (for example, QoS flow) corresponding to the session connection, and the core network configures the RN on the NG-U interface.
  • the data transmission tunnel transmits the tunnel establishment information to the host base station through the NGAP message of the NG-C.
  • the foregoing control plane process involves the following information interaction: on the NG-C interface, the core network sends the RN2 related information or any combination of any one of the following information to the host base station through the NGAP message: session connection Identification information, identification information of the data flow, QoS parameters, and NG-U tunnel establishment information.
  • the NG-U tunnel establishment information may include any one of the following information or a combination of any one of the following: GTP-U TEID, IP address, and port number.
  • the host base station and the RN1 have a peer-to-peer protocol layer, and specifically include: an SDAP layer (optionally, which can be configured as a transparent transmission), a PDCP layer, an RLC layer, a MAC layer, and a PHY layer.
  • the protocol stack of the Un1 port also includes an adaptation layer function for adding and/or parsing the first adaptive identity.
  • the adaptive function may be included in an existing protocol layer, such as an SDAP layer/PDCP layer/RLC layer/MAC layer/PHY layer; or the adaptive function may be separately deployed in a protocol layer, for example, referred to as adaptation (Adaptation, Referred to as Adapt layer.
  • the adaptation layer may be deployed on the SDAP layer, or between the SDAP layer and the PDCP layer, or between the PDCP layer and the RLC layer, or between the RLC layer and the MAC layer, or deployed. Between the MAC and PHY layers.
  • the first adaptive identifier may include any one of the following information or a combination of any of the following: a two-hop RN identifier and/or hop count information (for identifying RN2), and a second UE identifier ( UE for identifying RN2 service), one-hop RN identification and/or hop count information (for identifying RN1), first UE identification (for identifying the UE served by RN1), three-hop RN identification and/or hop count information (Three-hop, four-hop or even n-hop RN for identifying data transmitted through RN2 and RN1), third UE identity (UE for identifying multi-hop RN service), NGAP message type, XnAP message type, GTP-U The message type (belonging to NG-U or Xn-U), the user plane packet type, and the user plane packet information.
  • a two-hop RN identifier and/or hop count information for identifying RN2
  • UE for identifying RN2 service UE for identifie
  • the user plane data packet information includes any one of the following information or a combination of any one of the following: session connection information, data flow information, and classification identification information, and information about the radio bearer where the data packet is transmitted when the second wireless interface is transmitted.
  • the donor base station maps the data in the GTP tunnel received by the NG-U to the DRB transmission established for the RN1 at the Un1 port.
  • the bearer is transmitted on the DRB established for the RN1 on the Un1 port, and may be adopted in the following manner. Any one or any combination of any:
  • Manner 1 Map data of one GTP tunnel to the same DRB for transmission
  • Manner 2 The data packets in the GTP tunnel are mapped to multiple DRBs according to the QoS requirements of the data flow. Specifically, one or more QoS flows in the GTP-U are mapped to one DRB, and the QoS requirements of the one or more QoS flows are matched with the DRB.
  • the data that is mapped to the QoS flows belonging to the same GTP-U tunnel on the multiple DRBs needs to carry the first adaptive identifier, so that the RN1 identifies and aggregates the data packets of the GTP tunnel, and sends the data packet to the Un2 port.
  • the SDAP entity connected to the session corresponding to the GTP tunnel.
  • Manner 3 Assign a class identifier to the data flow in the GTP tunnel (for example, mapping to a QCI according to QoS requirements, where the class identifier is QCI), and multiple data streams can be assigned the same category identifier, one or more categories. The identity is mapped to a DRB. Optionally, when the data packet is transmitted on Un2, the category identifier is included in the first adaptive identifier.
  • the RN1 For the uplink, the RN1 processes the data packet received on the Un2 port based on the first uplink mapping relationship, and then sends the data packet to the host base station through the Un1 port.
  • the data packet sent by the RN1 on the Un1 port carries the first adaptive identifier, and is used by the host base station to distinguish the data on the Un1 port.
  • An optional method is that the data packet received by the RN1 on the Un2 obtains the PDU session and the QoS flow corresponding to the data packet, and then generates a corresponding data packet sent on the Un1 port, where the first adaptive identifier is carried. Then, the RN1 transmits the data packet of the Un2 port to the DRB of the Un1 port of the RN1 in a manner similar to the downlink. For example, any one of the following manners or a combination of any one of the following may be adopted:
  • Manner 1 Map the data of one PDU session to the same DRB for transmission
  • the PDU session data packet is mapped to multiple DRBs according to the QoS requirements of the data flow. Specifically, one or more QoS flows of the PDU session are mapped to one DRB, and the QoS requirements of the one or more QoS flows are matched with the DRB.
  • the data packet that belongs to the same PDU session on the multiple DRBs carries the first adaptive identifier, and is used to enable the host base station to identify and aggregate the data packets of the PDU session, by using the same NG-U.
  • the GTP tunnel is sent to the core network.
  • Manner 3 Assign a class identifier to the data flow of the PDU session (for example, mapping to a QCI according to QoS requirements, where the class identifier is QCI), and multiple data streams may be assigned the same category identifier, one or more category identifiers. Map to a DRB.
  • the class identifier is carried when the data packet is transmitted on the Un1 port.
  • the category identifier is included in the first adaptive identifier.
  • the RN1 is based on the correspondence between the PDU session and/or the QFI and the classification identifier (referred to as a classification mapping relationship, optionally, the correspondence may be corresponding to one RN/UE), and the data packet is correspondingly
  • the classification identifier is based on the correspondence between the classification identifier and the DRB of the Un1 interface, and the data packet is carried in the DRB for transmission.
  • the manner in which the RN1 obtains the classification mapping relationship is: a configuration of the host base station, or a QAM configuration, or a correspondence between the PDU session and/or the QFI of the data packet received at the Un1 interface and the classification identifier.
  • RN1 and RN2/UE On the Un2/Uu interface, RN1 and RN2/UE have peer-to-peer protocol layers, including: SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer.
  • the protocol stack of the Un port further includes an adaptation layer function for adding and/or parsing the second adaptive identifier.
  • the second adaptive function may be included in an existing protocol layer, such as an SDAP layer/PDCP layer/RLC layer/MAC layer/PHY layer; or the adaptive function may be separately deployed in a protocol layer, for example, called adaptive ( Adaptation, referred to as Adapt) layer.
  • the adaptation layer may be deployed on the SDAP layer, or between the SDAP layer and the PDCP layer, or between the PDCP layer and the RLC layer, or between the RLC layer and the MAC layer, or deployed in the MAC layer. Between the PHY layer.
  • the adaptive function if the RN2 does not enable the base station module to provide services for the UE, the function may not be enabled at this time, that is, no additional identification is needed.
  • the RN1 configures the DRB of the radio interface for the RN2/UE through the control plane RRC message, and simultaneously informs the RN2/UE of the mapping relationship between the QoS flow and the DRB in each uplink PDU session.
  • the RN2/UE transmits the QoS flow to the RN1 based on the correspondence between the PDU session (and QoS flow) and the DRB in the corresponding DRB.
  • FIG. 31 and FIG. 32 are schematic diagrams showing three L3 protocol stack user plane architectures according to an embodiment of the present application.
  • a third radio interface ie, Un3 or The DRB of the Uu port carries the data transmission of the RN3/UE itself (and the UE served by the RN3); the uplink of the part of the data needs to be forwarded to the RN1 by the RN2 through the second radio interface (ie, Un2); (ie, Un1) is forwarded to Donor by RN1, and then forwarded to the corresponding core network node through Donor.
  • the downlink of this part of data is sent to Donor by the core network, sent to RN2 via RN1, and then sent to RN3/UE via RN2. Therefore, it is necessary to determine the DRB used when the RN1 and the RN2 forward the uplink and/or downlink data, and the manner of data forwarding of the first radio interface and the second radio interface, for example, whether it is processed by the GTP-U layer.
  • FIG. 28 shows a schematic diagram of an L3 protocol stack user plane architecture 1-A in accordance with an embodiment of the present application.
  • the host base station is the same as the protocol stack of the core network user plane node serving the RN.
  • the specific protocol stack is similar to the prior art and will not be described here.
  • the control plane requests to establish a session connection (for example, a PDU session) and/or a data flow (for example, QoS flow) corresponding to the session connection, and the core network configures the NG-U interface for the RN3/UE.
  • the data transmission tunnel is sent, and the tunnel establishment information is sent to the host base station through the NGAP message of the NG-C.
  • the foregoing control plane process involves the following information interaction: on the NG-C interface, the core network sends the RN3/UE related information in any one or any combination of the following to the host base station through the NGAP message: Identification information of the session connection, identification information of the data flow, QoS parameters, and NG-U tunnel establishment information.
  • the NG-U tunnel establishment information may include any one of the following information or a combination of any one of the following: GTP-U TEID, IP address, and port number.
  • the host base station and the RN1 have a peer-to-peer protocol layer, specifically including: a GTP-U layer, a UDP layer (optionally), an IP layer (optionally), and an SDAP layer (optionally, It can be configured as transparent transmission, PDCP layer, RLC layer, MAC layer, and PHY layer.
  • the GTP-U layer (which may also be combined with the UDP layer and/or the IP layer) may be used to distinguish data carried in the same DRB on the Un1 port, for example, a GTP tunnel (optionally, identified by a pair of TEIDs, respectively corresponding to the uplink) And downlink) correspond to a UE session connection.
  • the protocol stack of the Un1 port further includes an adaptive layer function for adding and/or parsing the first adaptive identifier.
  • the configuration of the adaptive layer, the method of distinguishing the data type in the Un1 port, and the use of the first adaptive identifier are similar to those in the L3 protocol stack user plane architecture 1, and are not described here.
  • the host base station maps the GTP tunnel received by the NG-U to the GTP tunnel of the Un1 port. For example, the host base station allocates the GTP TEID on the NG-U to the corresponding session connection, and informs the core network through the NGAP message of the NG-C.
  • the GTP TEID is used for identification.
  • the QoS flow identifier is carried on the GTP-U data packet.
  • the GTP tunnel of the Un1 port is transmitted on the DRB established for the RN1 on the Un1 port, and any one of the following manners or a combination of any one of the following may be adopted:
  • Manner 1 Map data of one GTP tunnel to the same DRB for transmission
  • Manner 2 The data packets in the GTP tunnel are mapped to multiple DRBs according to the QoS requirements of the data flow. Specifically, one or more QoS flows in the GTP-U are mapped to one DRB, and the QoS requirements of the one or more QoS flows are matched with the DRB.
  • the foregoing QoS flows that belong to the same GTP-U tunnel on multiple DRBs use the same GTP TEID, and are used to enable RN1 to identify and aggregate the data packets of the GTP tunnel, and associate with the Un2 corresponding to the session connection.
  • the GTP tunnel of the mouth The GTP tunnel of the mouth.
  • Manner 3 Assign a class identifier to the data flow in the GTP tunnel (for example, mapping to a QCI according to QoS requirements, where the class identifier is QCI), and multiple data streams can be assigned the same category identifier, one or more categories.
  • the identity is mapped to a DRB.
  • the category identifier is carried.
  • the category identifier is carried on a GTP data packet on the Un1 port (for example, DSCP is used to represent QCI).
  • the class identifier is carried when the data packet is transmitted on the Un2/Uu port.
  • the category identifier is carried on a GTP data packet on the Un2/Uu port (eg, DSCP is used to represent QCI).
  • the RN1 For the uplink, the RN1 processes the data packet received on the Un2/Uu port (for example, GTP-U encapsulation) based on the first uplink mapping relationship, and then sends the data packet to the host base station through the Un1 port.
  • the data packet sent by the RN1 on the Un1 port carries the first adaptive identifier, and is used by the host base station to distinguish the data on the Un1 port.
  • An optional method is that the RN1 aggregates the data packets received on the Un2 according to the GTP tunnel to generate GTP data packets sent on the Un1 port.
  • the RN1 processes the data packet received at the Un2 port, and obtains a PDU session and a QoS flow corresponding to the data packet based on the information carried on the GTP packet, such as TEID and QFI, to generate a corresponding GTP data packet, where GTP TEID for QFI and Un1 ports.
  • Another optional method is: without clustering the GTP tunnel, directly generating the GTP data packet based on the information carried in the GTP data packet received on the Un2, and finding the corresponding Un1 port DRB.
  • the RN1 transmits the GTP data packet of the Un2 port to the DRB of the Un1 port of the RN1 in a manner similar to the downlink.
  • any one of the following manners or a combination of any one of the following may be adopted:
  • Manner 1 Map data of one GTP tunnel to the same DRB for transmission
  • Manner 2 The data packets in the GTP tunnel are mapped to multiple DRBs according to the QoS requirements of the data flow. Specifically, one or more QoS flows in the GTP-U are mapped to one DRB, and the QoS requirements of the one or more QoS flows are matched with the DRB. Optionally, the QoS flows that are mapped to the same GTP-U tunnel on the multiple DRBs use the same GTP TEID, and are used by the host base station to identify and aggregate the data packets of the GTP tunnel and send the data packets to the core network.
  • Manner 3 The classification identifier based on the data stream is mapped to the corresponding DRB transmission.
  • One possible way is to assign a class identifier to the data flow in the GTP tunnel (for example, mapping to a QCI according to QoS requirements, in which case the class identifier is QCI), and multiple data streams can be assigned the same category identifier, one Or multiple category IDs are mapped to one DRB.
  • the class identifier is carried when the data packet is transmitted on the Un1 port.
  • the category identification is carried on a GTP packet on the Un1 port (e.g., DSCP is used to represent QCI).
  • the RN1 is based on a correspondence between the PDU session (or GTP TEID) and/or the QFI and the classification identifier (referred to as a classification mapping relationship, optionally, the correspondence may be corresponding to one RN/UE),
  • the classification identifier corresponding to the data packet is obtained, so that the data packet is carried in the DRB based on the correspondence between the classification identifier and the DRB of the Un1 interface.
  • the manner in which the RN1 obtains the classification mapping relationship is: the configuration of the primary base station, or the QAM configuration, or the correspondence between the PDU session (or GTP TEID) and/or the QFI and the classification identifier of the data packet received at the Un1 interface.
  • Another possible way is to carry the classification identifier on the GTP data packet received by the Un2 port, and directly carry the foregoing data packet on the corresponding DRB for transmission based on the classification mapping relationship.
  • RN1 and RN2 have peer-to-peer protocol layers, including: GTP-U layer, UDP layer (optionally), IP layer (optionally), SDAP layer (optionally, Configured as transparent transmission, PDCP layer, RLC layer, MAC layer, and PHY layer.
  • GTP-U layer (which may also be combined with the UDP layer and/or the IP layer) may be used to distinguish data carried in the same DRB on the Un2 port, for example, a GTP tunnel (optionally, identified by a pair of TEIDs, respectively corresponding to the uplink) And downlink) correspond to a UE/RN session connection.
  • the protocol stack of the Un2 port further includes an adaptive layer function for adding and/or parsing the second adaptive identifier.
  • the adaptive function may be included in an existing protocol layer, such as an SDAP layer/PDCP layer/RLC layer/MAC layer/PHY layer; or the adaptive function may be separately deployed in a protocol layer, for example, referred to as adaptation (Adaptation, Referred to as Adapt layer.
  • the adaptation layer may be deployed between the GTP-U layer and the PDCP layer, or between the PDCP layer and the RLC layer, or between the RLC layer and the MAC layer, or deployed in the MAC and PHY layers. between.
  • the method for distinguishing the data type in the Un2 port and the description of the second adaptive identifier refer to the description in the control plane protocol stack, and details are not described herein again.
  • an optional mode is that RN1 maps the GTP tunnel received at Un1 to the GTP tunnel of the Un2 port.
  • RN1 receives the GTP data packet at the Un1 port, and aggregates the data packets belonging to the same session connection based on the information carried by the GTP data packet (for example, TEID), and associates the GTP tunnel of the Un2 interface with the GTP tunnel of the Un2 port, and then carries the UnTP port.
  • the port is transmitted on the DRB.
  • the RN1 does not perform GTP tunneling, and directly generates GTP data packets based on the information carried in the GTP data packets received on the Un1, and finds the corresponding Un2 port DRB, which is then carried in the Un2 port. Transfer on the DRB.
  • the identifier of the QoS flow is carried on the GTP-U data packet.
  • the manner in which the GTP tunnel of the Un2 port is transmitted on the DRB established by the RN2 on the Un2 port is similar to the processing of the Un1 port, and any one of the following modes or a combination of any multiple may be adopted:
  • Manner 1 Map data of one GTP tunnel to the same DRB for transmission
  • the data packets in the GTP tunnel are mapped to multiple DRBs according to the QoS requirements of the data flow. Specifically, one or more QoS flows in the GTP-U are mapped to one DRB, and the QoS requirements of the one or more QoS flows are matched with the DRB.
  • the QoS flows that are mapped to the same GTP-U tunnel on the multiple DRBs use the same GTP TEID, and are used by the RN2 to identify and aggregate the data packets of the GTP tunnel, and send the packets to the Un3/Uu port.
  • the GTP tunnel corresponds to the session connected to the SDAP entity.
  • Manner 3 The classification identifier based on the data stream is mapped to the corresponding DRB transmission.
  • One possible way is to assign a class identifier to the data flow in the GTP tunnel (for example, mapping to a QCI according to QoS requirements, in which case the class identifier is QCI), and multiple data streams can be assigned the same category identifier, one Or multiple category IDs are mapped to one DRB.
  • the class identifier is carried when the data packet is transmitted on the Un2 port.
  • the category identifier is carried on a GTP data packet on the Un2 port (for example, DSCP is used to represent QCI).
  • the RN1 is based on a correspondence between the PDU session (or GTP TEID) and/or the QFI and the classification identifier (referred to as a classification mapping relationship, optionally, the correspondence may be corresponding to one RN/UE),
  • the classification identifier corresponding to the data packet is obtained, so that the data packet is carried in the DRB based on the correspondence between the classification identifier and the DRB of the Un2 interface.
  • the manner in which the RN1 obtains the classification mapping relationship is: the configuration of the primary base station, or the QAM configuration, or the correspondence between the PDU session (or GTP TEID) and/or the QFI and the classification identifier of the data packet received at the Un1 interface.
  • Another possible way is to carry the classification identifier on the GTP data packet received by the Un1 interface, and directly transmit the foregoing data packet to the DRB corresponding to the Un2 port based on the classification mapping relationship.
  • the RN2 For the uplink, the RN2 processes the data packet received on the Un3/Uu port based on the second uplink mapping relationship (for example, GTP-U encapsulation), and then sends the packet to the RN1 through the Un2 port.
  • the data packet sent by the RN2 on the Un2 port carries the second adaptive identifier, and is used by the RN1 to distinguish the data on the Un2 port.
  • the RN2 receives the data packet on the Un3/Uu port, and processes the data packet belonging to a PDU session/SDAP entity through the GTP-U layer of the Un2 port to generate a GTP data packet sent on the Un2 port.
  • the RN2 processes the data packet received at the Un3/Uu port, obtains the PDU session and the QoS flow corresponding to the data packet, and generates a corresponding GTP data packet, where the GTP TEID and the QFI are carried.
  • the RN2 transmits the GTP data packet of the Un2 port to the DRB of the Un2 port of the RN2 in a manner similar to the downlink. For example, any one of the following manners or a combination of any one of the following may be adopted:
  • Manner 1 Map data of one GTP tunnel to the same DRB for transmission
  • Manner 2 The data packets in the GTP tunnel are mapped to multiple DRBs according to the QoS requirements of the data flow. Specifically, one or more QoS flows in the GTP-U are mapped to one DRB, and the QoS requirements of the one or more QoS flows are matched with the DRB. Optionally, the QoS flows that are mapped to the same GTP-U tunnel on the multiple DRBs use the same GTP TEID, and are used by the RN1 to identify and aggregate the data packets of the GTP tunnel and send the data packets to the core network.
  • Manner 3 Assign a class identifier to the data flow in the GTP tunnel (for example, mapping to a QCI according to QoS requirements, where the class identifier is QCI), and multiple data streams can be assigned the same category identifier, one or more categories.
  • the identity is mapped to a DRB.
  • the class identifier is carried when the data packet is transmitted on the Un2 port.
  • the category identifier is carried on a GTP data packet on the Un2 port (for example, DSCP is used to represent QCI).
  • the RN2 is based on a correspondence between the PDU session (or the GTP TEID) and/or the QFI and the classification identifier (referred to as a classification mapping relationship, optionally, the correspondence may be corresponding to one RN/UE),
  • the classification identifier corresponding to the data packet is obtained, so that the data packet is carried in the DRB based on the correspondence between the classification identifier and the DRB of the Un2 interface.
  • the manner in which the RN2 obtains the classification mapping relationship is: the configuration of the primary base station, or the QAM configuration, or the correspondence between the PDU session (or GTP TEID) and/or the QFI and the classification identifier of the data packet received at the Un1 interface. .
  • the GTP tunnel of the Un1 connected to the same session and the GTP tunnel of the Un2 may have different TEIDs and/or IP addresses, and the RN1 forwards the GTP packet received by one of the radio interfaces on another radio interface.
  • the received GTP data packet needs to be processed to generate a GTP data packet sent on another wireless interface.
  • the process includes changing the GTP TEID and/or IP address, and the like. For example, for a PDU session, the downlink TEID and/or IP address of the Un1 port is allocated by the donor base station and notified to the RN1.
  • the uplink TEID and/or IP address of the Un1 interface is allocated by the RN1, and the host base station is notified;
  • the TEID and/or IP address is assigned by RN1 and is notified to RN2.
  • the uplink TEID and/or IP address of Un2 is allocated by RN2 and notified to RN1; thus, RN1 knows the upper and lower interfaces of Un1 and Un2 of the PDU session. Line TEID and / or IP address.
  • 29 is a schematic diagram of a data transmission process of an Un1 radio interface and an Un2 radio interface.
  • Different data flows in one session connection can be mapped to different Un1 port DRBs; data streams of different UEs/RNs can be mapped to the same An Un1 port DRB.
  • Corresponding to the second mode of the Un1 port (similar to the uplink and downlink).
  • different data flows in one session connection can be mapped to different Un2 port DRBs; data streams of different UEs/RNs can be mapped to the same Un2 port DRB.
  • the mapping relationship between the data stream and the radio interface DRB need not be the same, and the uplink may be performed by RN1 and RN2, respectively.
  • FIG. 30 is a diagram showing a packet mapping process inside RN2 and inside RN1 in a data transmission process.
  • the base station part of the RN2 receives the uplink data on the Un3 port, and obtains the PDU session corresponding to the uplink data based on the DRB information carrying the uplink data and the QFI information on the data packet, thereby generating a GTP data packet, where the GTP data packet carries the GTP TEID. And QFI.
  • An optional method is that the RN2 adds a type identifier to the data packet based on the categorization mapping relationship.
  • the type identifier can be carried in the IP layer, for example, by using a DSCP identifier, that is, the type identifier has a correspondence with the DSCP.
  • the UE part of the RN2 reads the type identifier, and the GTP data packet is carried in the Un2 port according to the second uplink mapping relationship.
  • the RN2 adds the DRB identifier to the data packet based on the second uplink mapping relationship.
  • the DRB identifier may be carried in the IP layer, for example, by using a DSCP identifier, that is, the DRB identifier and the DSCP identifier.
  • the UE has a correspondence relationship, and the UE part of the RN2 reads the DRB identifier, and transmits the GTP data packet to the corresponding DRB of the Un2 port.
  • the correspondence between the type identifier/DRB identifier and the DSCP identifier may be internally defined by the RN2, and the base station part and the UE part of the RN2 are correspondingly and interpreted.
  • the type identifier/DRB identifier may continue to be carried in the uplink data packet sent by the Un2, and the RN1 determines that the data to be received in the Un2 is sent to the host base station through the DRB of the Un1 port, for example, the foregoing identifier is used.
  • the input information for the first mapping relationship may be internally defined by the RN2, and the base station part and the UE part of the RN2 are correspondingly and interpreted.
  • the type identifier/DRB identifier may continue to be carried in the uplink data packet sent by the Un2, and the RN1 determines that the data to be received in the Un2 is sent to the host base station through the DRB of the Un1 port, for example, the foregoing identifier is used.
  • the type identifier/DRB identifier may continue to be carried in the IP layer (for example, in the form of a DSCP, and the correspondence between the identifier and the DSCP identifier is also needed, and the RN1 needs to be learned.
  • the method that the RN1 learns may be configured for the host base station.
  • the RN1 is configured by default, and the RN2 uses the corresponding relationship specified by the protocol by default.
  • the RN2 learns in a similar manner, that is, the configuration of the host base station, the OAM configuration, the RN1 configuration, or the protocol specified by the RN2. Correspondence).
  • the action of the RN1 transmitting on the Un1 port after receiving the uplink data packet at the Un2 port is similar to that in FIG. The difference is that the RN1 can directly transmit the data in the uplink data packet to the DRB of the Un1 port according to the first mapping relationship based on the information in the uplink data packet received on the Un2 interface.
  • RN1 receives the GTP data packet on the Un2 port, processes it (for example, changes the GTP TEID and/or IP address therein), and generates a GTP data packet sent on the Un1 port.
  • the GTP data packet is transmitted on the corresponding DRB of the Un1 port according to the type identifier/DRB identifier carried on the data packet received on the Un2 port.
  • the DRB of the Un1 port is determined based on the type identifier and the first uplink mapping relationship, or the DRB of the Un1 port is determined based on the DRB identifier and the first uplink mapping relationship.
  • RN2 and RN3/UE have peer-to-peer protocol layers, including: SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer.
  • the protocol stack of the Un port further includes an adaptation layer function for adding and/or parsing the adaptive identifier.
  • the adaptive function may be included in an existing protocol layer, such as an SDAP layer/PDCP layer/RLC layer/MAC layer/PHY layer; or the adaptive function may be separately deployed in a protocol layer, for example, referred to as adaptation (Adaptation, Referred to as Adapt layer.
  • the adaptation layer may be deployed on the SDAP layer, or between the SDAP layer and the PDCP layer, or between the PDCP layer and the RLC layer, or between the RLC layer and the MAC layer, or deployed in the MAC layer.
  • the PHY layer Between the PHY layer.
  • the method for distinguishing data types and the description of the adaptive identifiers on the interface of the Un3 refer to the descriptions of the previous Un2 port and the second adaptive identifier, and details are not described herein.
  • the function may not be enabled at this time, that is, no additional identification is needed.
  • the RN2 aggregates the data packets that belong to the PDU session received by the Un2 interface, and the RN3/UE is transmitted on the DRB of the Un3/Uu after being processed by the SDAP layer corresponding to the Un3/Uu interface.
  • the RN2 configures the DRB of the radio interface for the RN3/UE through the control plane RRC message, and simultaneously informs the RN3/UE of the mapping relationship between the QoS flow and the DRB in each uplink PDU session.
  • the RN3/UE sends the QoS flow to the RN2 based on the correspondence between the PDU session (and QoS flow) and the DRB in the corresponding DRB.
  • the RN2 will pass the data packet belonging to a PDU session received by the SDAP entity on the Un3/Uu port. After processing, it will be converted into the GTP packet sent on the Un2 port and sent to the RN1 through the Un2 port.
  • FIG. 31 shows another schematic diagram of the L3 protocol stack user plane architecture 2 in accordance with an embodiment of the present application.
  • the protocol stack of the Un1 port and the Un2 port does not include the GTP-U protocol layer, and the data belonging to different nodes that are carried in the Un1 port/Un2 port are distinguished by the adaptive identifier.
  • the host base station is the same as the protocol stack of the core network user plane node serving the RN.
  • the specific protocol stack is similar to the prior art and will not be described here.
  • the control plane requests to establish a session connection (for example, a PDU session) and/or a data flow (for example, QoS flow) corresponding to the session connection, and the core network configures the NG-U interface for the RN3/UE.
  • the data transmission tunnel is sent, and the tunnel establishment information is sent to the host base station through the NGAP message of the NG-C.
  • the foregoing control plane process involves the following information interaction: on the NG-C interface, the core network sends the RN3/UE related information in any one or any combination of the following to the host base station through the NGAP message: Identification information of the session connection, identification information of the data flow, QoS parameters, and NG-U tunnel establishment information.
  • the NG-U tunnel establishment information may include any one of the following information or a combination of any one of the following: GTP-U TEID, IP address, and port number.
  • the host base station and the RN1 have a peer-to-peer protocol layer, and specifically include: an SDAP layer (optionally, which can be configured as a transparent transmission), a PDCP layer, an RLC layer, a MAC layer, and a PHY layer.
  • the protocol stack of the Un1 port also includes an adaptation layer function for adding and/or parsing the first adaptive identity.
  • the adaptive function may be included in an existing protocol layer, such as an SDAP layer/PDCP layer/RLC layer/MAC layer/PHY layer; or the adaptive function may be separately deployed in a protocol layer, for example, referred to as adaptation (Adaptation, Referred to as Adapt layer.
  • the adaptation layer may be deployed on the SDAP layer, or between the SDAP layer and the PDCP layer, or between the PDCP layer and the RLC layer, or between the RLC layer and the MAC layer, or deployed. Between the MAC and PHY layers.
  • the first adaptive identifier may include any one of the following information or a combination of any of the following: a two-hop RN identifier and/or hop count information (for identifying RN2), and a second UE identifier ( UE for identifying RN2 service), one-hop RN identification and/or hop count information (for identifying RN1), first UE identification (for identifying the UE served by RN1), three-hop RN identification and/or hop count information (for identifying RN3), third UE identity (UE for identifying multi-hop RN service), NGAP message type, XnAP message type, GTP-U message type (belonging to NG-U or Xn-U), user plane data Package type, as well as user plane packet information.
  • a two-hop RN identifier and/or hop count information for identifying RN2
  • UE for identifying RN2 service UE for identifying RN2 service
  • one-hop RN identification and/or hop count information for identifying RN1
  • the user plane data packet information includes any one of the following information or a combination of any one of the following: session connection information, data flow information, and classification identification information, and information about the radio bearer where the data packet is transmitted when the second wireless interface is transmitted.
  • the donor base station maps the data in the GTP tunnel received by the NG-U to the DRB transmission established for the RN1 at the Un1 port.
  • the bearer is transmitted on the DRB established for the RN1 on the Un1 port, and may be adopted in the following manner. Any one or any combination of any:
  • Manner 1 Map data of one GTP tunnel to the same DRB for transmission
  • Manner 2 The data packets in the GTP tunnel are mapped to multiple DRBs according to the QoS requirements of the data flow. Specifically, one or more QoS flows in the GTP-U are mapped to one DRB, and the QoS requirements of the one or more QoS flows are matched with the DRB.
  • the data that is mapped to the QoS flows belonging to the same GTP-U tunnel on the multiple DRBs needs to carry the first adaptive identifier, so that the RN1 identifies and aggregates the data packets of the GTP tunnel, and sends the data packet to the Un2 port.
  • the SDAP entity connected to the session corresponding to the GTP tunnel.
  • Manner 3 Assign a class identifier to the data flow in the GTP tunnel (for example, mapping to a QCI according to QoS requirements, where the class identifier is QCI), and multiple data streams can be assigned the same category identifier, one or more categories. The identity is mapped to a DRB. Optionally, when the data packet is transmitted on Un2, the category identifier is included in the first adaptive identifier.
  • the RN1 For the uplink, the RN1 processes the data packet received on the Un2 port based on the first uplink mapping relationship, and then sends the data packet to the host base station through the Un1 port.
  • the data packet sent by the RN1 on the Un2 port carries the first adaptive identifier, and is used by the host base station to distinguish the data on the Un1 port.
  • An optional method is that the data packet received by the RN1 on the Un2 obtains the PDU session and the QoS flow corresponding to the data packet, and then generates a corresponding data packet sent on the Un1 port, where the first adaptive identifier is carried. Then, the RN1 transmits the data packet of the Un2 port to the DRB of the Un1 port of the RN1 in a manner similar to the downlink. For example, any one of the following manners or a combination of any one of the following may be adopted:
  • Manner 1 Map the data of one PDU session to the same DRB for transmission
  • the PDU session data packet is mapped to multiple DRBs according to the QoS requirements of the data flow. Specifically, one or more QoS flows of the PDU session are mapped to one DRB, and the QoS requirements of the one or more QoS flows are matched with the DRB.
  • the data packet that is mapped to multiple DRBs that belong to the same PDU session carries the first adaptive identifier, and is used to enable the host base station to identify and aggregate the data packets of the PDU session through the same NG-U.
  • the GTP tunnel is sent to the core network.
  • Manner 3 Assign a class identifier to the data flow of the PDU session (for example, mapping to a QCI according to QoS requirements, where the class identifier is QCI), and multiple data streams may be assigned the same category identifier, one or more category identifiers. Map to a DRB.
  • the class identifier is carried when the data packet is transmitted on the Un1 port.
  • the category identifier is included in the first adaptive identifier.
  • the RN1 is based on the correspondence between the PDU session and/or the QFI and the classification identifier (referred to as a classification mapping relationship, optionally, the correspondence may be corresponding to one RN/UE), and the data packet is correspondingly
  • the classification identifier is based on the correspondence between the classification identifier and the DRB of the Un1 interface, and the data packet is carried in the DRB for transmission.
  • the manner in which the RN1 obtains the classification mapping relationship is: a configuration of the host base station, or a QAM configuration, or a correspondence between the PDU session and/or the QFI of the data packet received at the Un1 interface and the classification identifier.
  • RN1 and RN2 have peer-to-peer protocol layers, including: SDAP layer (optionally, can be configured as transparent transmission), PDCP layer, RLC layer, MAC layer, and PHY layer.
  • the protocol stack of the Un2 port also includes an adaptation layer function for adding and/or parsing the second adaptive identifier.
  • the adaptive function may be included in an existing protocol layer, such as an SDAP layer/PDCP layer/RLC layer/MAC layer/PHY layer; or the adaptive function may be separately deployed in a protocol layer, for example, referred to as adaptation (Adaptation, Referred to as Adapt layer.
  • the adaptation layer may be deployed on the SDAP layer, or between the SDAP layer and the PDCP layer, or between the PDCP layer and the RLC layer, or between the RLC layer and the MAC layer, or deployed.
  • the second adaptive identifier may include any one of the following information or a combination of any multiple: two-hop RN identifier and/or hop count information (for identifying RN2), and second UE identifier.
  • the user plane data packet information includes any one of the following information or a combination of any one of the following: session connection information, data flow information, and classification identification information, and information of the radio bearer where the data packet is transmitted when the third wireless interface is transmitted.
  • RN1 will process the data packet received on the Un1 port and send it to RN2 through the Un2 port.
  • the data packet sent by the RN1 on the Un2 port carries a second adaptive identifier, and is used by the RN2 to distinguish data on the Un2 port.
  • An optional method is that the data packet received by the RN1 on the Un1 obtains the PDU session and the QoS flow corresponding to the data packet, and then generates a corresponding data packet sent by the Un2 port, where the second adaptive identifier is carried. Then, the RN1 transmits the data packet of the Un1 port to the DRB of the Un2 port of the RN2.
  • the data packet received by the RN1 on the Un1 obtains the PDU session and the QoS flow corresponding to the data packet, and then generates a corresponding data packet sent by the Un2 port, where the second adaptive identifier is carried. Then, the RN1 transmits the data packet of the Un1 port to the DRB of the Un2 port of the RN2.
  • any one of the following manners or a combination of any one of the following may be adopted:
  • Manner 1 Map the data of one PDU session to the same DRB for transmission
  • Manner 2 The PDU session data packet is mapped to multiple DRBs according to the QoS requirements of the data flow. Specifically, one or more QoS flows of the PDU session are mapped to one DRB, and the QoS requirements of the one or more QoS flows are matched with the DRB.
  • the data packet that belongs to the same PDU session on the multiple DRBs carries the second adaptive identifier, and is used to enable the RN2 to identify and aggregate the data packet of the PDU session, after the SDAP processing corresponding to the PDU session. It is sent to the RN3/UE on the Un3/Uu port.
  • Manner 3 The classification identifier based on the data stream is mapped to the corresponding DRB transmission.
  • One possible way is to assign a category identifier to the data stream of the PDU session (for example, mapping to a QCI according to QoS requirements, and the category identifier is QCI), and multiple data streams can be assigned the same category identifier, one or Multiple category IDs are mapped to one DRB.
  • the class identifier is carried when the data packet is transmitted on the Un2 port.
  • the category identifier is carried in the second adaptive identifier on the Un2 port.
  • the RN1 is based on the correspondence between the PDU session and/or the QFI and the classification identifier (referred to as a classification mapping relationship, optionally, the correspondence may be corresponding to one RN/UE), and the data packet is correspondingly
  • the classification identifier is based on the correspondence between the classification identifier and the DRB of the Un2 interface, and the data packet is carried in the DRB for transmission.
  • the manner in which the RN1 obtains the classification mapping relationship is: a configuration of the host base station, or a QAM configuration, or a correspondence between the PDU session and/or the QFI of the data packet received at the Un1 interface and the classification identifier.
  • Another possible way is to carry the classification identifier in the first adaptive identifier of the data packet received by the Un1 interface, and directly carry the foregoing data packet on the corresponding DRB for transmission based on the classification mapping relationship.
  • the class identifier is carried when the data packet is transmitted on the Un2 port.
  • the category identifier is included in the second adaptive identifier.
  • the RN1 is based on the correspondence between the PDU session and/or the QFI and the classification identifier (referred to as a classification mapping relationship, optionally, the correspondence may be corresponding to one RN/UE), and the data packet is correspondingly
  • the classification identifier is transmitted based on the correspondence between the classification identifier and the DRB of the Un2 interface (for example, based on the first downlink mapping relationship), and the data packet is carried in the DRB.
  • the manner in which the RN1 obtains the classification mapping relationship is: a configuration of the host base station, or a QAM configuration, or a correspondence between the PDU session and/or the QFI of the data packet received at the Un1 interface and the classification identifier.
  • the RN2 For the uplink, the RN2 processes the data packet received on the Un3/Uu port based on the second uplink mapping relationship, and then sends the data packet to the RN1 through the Un2 port.
  • the data packet sent by the RN2 on the Un2 port carries the second adaptive identifier, and is used by the RN1 to distinguish the data on the Un2 port.
  • An optional method is that the data packet received by the RN2 on the Un/3Uu obtains the PDU session and the QoS flow corresponding to the data packet, and then generates a corresponding data packet sent by the Un2 port, where the second adaptive identifier is carried. Then, the RN2 transmits the data packet of the Un3/Uu port to the DRB of the Un2 port of the RN2 in a manner similar to the downlink. For example, any one of the following manners or a combination of any one of the following may be adopted:
  • Manner 1 Map the data of one PDU session to the same DRB for transmission
  • Manner 2 The PDU session data packet is mapped to multiple DRBs according to the QoS requirements of the data flow. Specifically, one or more QoS flows of the PDU session are mapped to one DRB, and the QoS requirements of the one or more QoS flows are matched with the DRB.
  • the data packet that belongs to the same PDU session on the multiple DRBs carries the second adaptive identifier, and is used to enable the RN1 to identify and aggregate the data packet of the PDU session, and process the SDAP layer corresponding to the PDU session. Then sent to the core network.
  • Manner 3 Assign a class identifier to the data flow of the PDU session (for example, mapping to a QCI according to QoS requirements, where the class identifier is QCI), and multiple data streams may be assigned the same category identifier, one or more category identifiers. Map to a DRB.
  • the class identifier is carried when the data packet is transmitted on the Un2 port.
  • the category identifier is included in the second adaptive identifier.
  • the RN2 is based on the correspondence between the PDU session and/or the QFI and the classification identifier (referred to as a classification mapping relationship, optionally, the correspondence may be corresponding to one RN/UE), and the corresponding data packet is obtained.
  • the classification identifier is based on the correspondence between the classification identifier and the DRB of the Un2 interface, and the data packet is carried in the DRB for transmission.
  • the manner in which the RN2 obtains the classification mapping relationship is: a configuration of the host base station, an RN1 configuration, or a QAM configuration, or a correspondence between the PDU session and/or the QFI of the data packet received at the Un2 interface and the classification identifier.
  • RN2 and RN3/UE On the Un3/Uu interface, RN2 and RN3/UE have peer-to-peer protocol layers, including: SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer.
  • the protocol stack of the Un port further includes an adaptation layer function for adding and/or parsing the adaptive identifier.
  • the adaptive function may be included in an existing protocol layer, such as an SDAP layer/PDCP layer/RLC layer/MAC layer/PHY layer; or the adaptive function may be separately deployed in a protocol layer, for example, referred to as adaptation (Adaptation, Referred to as Adapt layer.
  • the adaptation layer may be deployed on the SDAP layer, or between the SDAP layer and the PDCP layer, or between the PDCP layer and the RLC layer, or between the RLC layer and the MAC layer, or deployed in the MAC layer.
  • the PHY layer For the description of the method for distinguishing data types and the description of the adaptive identifiers on the interface of the Un3, refer to the descriptions of the previous Un2 port and the second adaptive identifier, and details are not described herein.
  • the adaptive function if the RN3 does not enable the base station module to provide services for the UE, the function may not be enabled at this time, that is, no additional identification is needed.
  • the RN2 aggregates the data packets that belong to the PDU session received by the Un2 interface, and the RN3/UE is transmitted on the DRB of the Un3/Uu after being processed by the SDAP layer corresponding to the Un3/Uu interface.
  • the RN2 configures the DRB of the radio interface for the RN3/UE through the control plane RRC message, and simultaneously informs the RN3/UE of the mapping relationship between the QoS flow and the DRB in each uplink PDU session.
  • the RN3/UE sends the QoS flow to the RN2 based on the correspondence between the PDU session (and QoS flow) and the DRB in the corresponding DRB.
  • the RN2 will pass the data packet belonging to a PDU session received by the SDAP entity on the Un3/Uu interface. After processing, it will be converted into the data packet sent by the Un2 interface and sent to the RN1 through the Un2 interface.
  • FIG. 32 shows another schematic diagram of the L3 protocol stack user plane architecture 1-B in accordance with an embodiment of the present application.
  • the host base station is the same as the protocol stack of the core network user plane node serving the RN.
  • the specific protocol stack is similar to the prior art and will not be described here.
  • the control plane requests to establish a session connection (for example, a PDU session) and/or a data flow (for example, QoS flow) corresponding to the session connection, and the core network configures the NG-U interface for the RN3/UE.
  • the data transmission tunnel is sent, and the tunnel establishment information is sent to the host base station through the NGAP message of the NG-C.
  • the foregoing control plane process involves the following information interaction: on the NG-C interface, the core network sends the RN3/UE related information in any one or any combination of the following to the host base station through the NGAP message: Identification information of the session connection, identification information of the data flow, QoS parameters, and NG-U tunnel establishment information.
  • the NG-U tunnel establishment information may include any one of the following information or a combination of any one of the following: GTP-U TEID, IP address, and port number.
  • Un1 wireless interface Transmit GTP-U data packets (data is GTP-U encapsulated as an SDP of Adap./SDAP), RN1 does not interpret GTP-U data packets
  • the donor base station has the following protocol layers: GTP-U layer, UDP layer (optionally), IP layer (optionally), SDAP layer (optionally, can be configured as transparent transmission), PDCP layer, RLC layer, MAC layer, and PHY layer.
  • GTP-U layer, the UDP layer (optionally), the IP layer (optionally) and the RN2 peer; the PDCP layer, the RLC layer, the MAC layer, and the PHY layer are peered with the RN1.
  • the above GTP-U layer (which may also be combined with the UDP layer and/or the IP layer) may be used to distinguish data carried in the same DRB on the Un1 port (upstream) or the Un2 port (downlink), such as a GTP tunnel (optionally , through a pair of TEID identification, respectively corresponding to the uplink and downlink) corresponding to a UE session connection.
  • the protocol stack of the Un1 port further includes an adaptive layer function for adding and/or parsing the first adaptive identifier.
  • the configuration of the adaptive layer, the method of distinguishing the data type in the Un1 port, and the use of the first adaptive identifier are similar to those in the L3 protocol stack user plane architecture 1-A, and are not described here.
  • the donor base station maps the GTP tunnel received at the NG-U to the GTP tunnel sent at the Un1 port. For example, the host base station allocates the GTP TEID on the NG-U to the corresponding session connection, and informs the core network through the NGAP message of the NG-C.
  • the GTP TEID is used for identification.
  • the QoS flow identifier is carried on the GTP-U data packet.
  • the GTP tunnel of the Un1 port is transmitted on the DRB established for the RN1 on the Un1 port, and any one of the following manners or a combination of any one of the following may be adopted:
  • Manner 1 Map data of one GTP tunnel to the same DRB for transmission
  • Manner 2 The data packets in the GTP tunnel are mapped to multiple DRBs according to the QoS requirements of the data flow. Specifically, one or more QoS flows in the GTP-U are mapped to one DRB, and the QoS requirements of the one or more QoS flows are matched with the DRB. Optionally, the QoS flows that are mapped to the same GTP-U tunnel on the multiple DRBs use the same GTP TEID, and are used to enable the RN2 to identify and aggregate the data packets of the GTP tunnel, and associate with the Un3 corresponding to the session connection. /Uu port PDU session/SDAP entity.
  • Manner 3 Assign a class identifier to the data flow in the GTP tunnel (for example, mapping to a QCI according to QoS requirements, where the class identifier is QCI), and multiple data streams can be assigned the same category identifier, one or more categories. The identity is mapped to a DRB.
  • the category identifier is carried.
  • the category identifier is carried on the GTP data packet on the Un1 port (for example, DSCP is used to represent the QCI); or carried in the first adaptive identifier.
  • the RN1 For the uplink, the RN1 processes the data packet received on the Un2 port based on the first uplink mapping relationship (for example, after processing through the Un2 port protocol stack and the Un1 port protocol stack), and then sends the data packet to the host base station through the Un1 port.
  • the data packet sent by the RN1 on the Un1 port carries the first adaptive identifier, and is used by the host base station to distinguish the data on the Un1 port.
  • the RN1 aggregates the data packets received on the Un2 according to the PDU session to generate a data packet sent by the Un1 port.
  • the RN1 processes the data packet received at the Un2 port, and obtains a PDU session and a QoS flow corresponding to the data packet based on the information carried on the data packet (for example, the second adaptive identifier), thereby generating a corresponding Un1 port data packet.
  • Another alternative is to not collect the PDU session and directly find the corresponding Un1 port DRB based on the information carried in the data packet received on Un2. Then, the RN1 transmits the generated data packet on the DRB of the Un1 port of the RN1 in a manner similar to the downlink. For example, any one of the following manners or a combination of any one of the following may be adopted:
  • Manner 1 Map the data of one PDU session to the same DRB for transmission
  • Manner 2 The data packets in the PDU session are mapped to multiple DRBs according to the QoS requirements of the data flow. Specifically, one or more QoS flows in the PDU session are mapped to one DRB, and the QoS requirements of the one or more QoS flows are matched with the DRB.
  • Manner 3 The classification identifier based on the data stream is mapped to the corresponding DRB transmission.
  • One possible way is to assign a category identifier to the data stream of the PDU session (for example, mapping to a QCI according to QoS requirements, and the category identifier is QCI), and multiple data streams can be assigned the same category identifier, one or Multiple category IDs are mapped to one DRB.
  • the class identifier is carried when the data packet is transmitted on the Un1 port.
  • the category identifier is carried in the first adaptive identifier.
  • the RN1 is based on a correspondence between the PDU session (or GTP TEID) and/or the QFI and the classification identifier (referred to as a classification mapping relationship, optionally, the correspondence may be corresponding to one RN/UE),
  • the classification identifier corresponding to the data packet is obtained, so that the data packet is carried in the DRB based on the correspondence between the classification identifier and the DRB of the Un1 interface.
  • the manner in which the RN1 obtains the classification mapping relationship is: a configuration of the host base station, or a QAM configuration, or a correspondence between the PDU session and/or the QFI of the data packet received at the Un1 interface and the classification identifier.
  • Another possible way is to carry the classification identifier (for example, the second adaptive identifier) on the data packet received by the Un2 interface, and directly carry the foregoing data packet on the corresponding DRB for transmission based on the classification mapping relationship.
  • RN2 On the Un2 port, RN2 has the following protocol layers: GTP-U layer, UDP layer (optionally), IP layer (optionally), SDAP layer (optionally, can be configured for transparent transmission), PDCP Layer, RLC layer, MAC layer, and PHY layer.
  • GTP-U layer, the UDP layer (optionally), the IP layer (optionally) is peered with the donor base station; the PDCP layer, the RLC layer, the MAC layer, and the PHY layer are peered with the RN1.
  • the above GTP-U layer (which may also be combined with the UDP layer and/or the IP layer) may be used to distinguish data carried in the same DRB on the Un1 port (upstream) or the Un2 port (downlink), such as a GTP tunnel (optionally , through a pair of TEID identification, respectively corresponding to the uplink and downlink) corresponding to a UE session connection.
  • the protocol stack of the Un2 port further includes an adaptive layer function for adding and/or parsing the second adaptive identifier.
  • the configuration of the adaptive layer, the method of distinguishing the data type in the Un2 port, and the use of the second adaptive identifier are similar to those in the L3 protocol stack user plane architecture 1-A, and are not described here.
  • an optional mode is that RN1 aggregates the data received in Un1, and remaps (for example, based on the second downlink mapping relationship) to the DRB of the Un2 port.
  • the RN1 receives the data packet at the Un1 port, and aggregates the data packets that belong to the same session connection based on the information carried by the data packet (for example, the first adaptive identifier), and then carries the data packet transmitted on the DRB of the Un2 port.
  • the data packet of the Un2 port is carried in the DRB and transmitted.
  • the second adaptive identifier is carried on the Un2 port data packet.
  • the data packet of the Un2 port is transmitted on the DRB established by the RN2 on the Un2 port, and any one of the following manners or a combination of any one of the following may be adopted:
  • Manner 1 Map the data of one PDU session to the same DRB for transmission
  • Manner 2 The data packets in the PDU session are mapped to multiple DRBs according to the QoS requirements of the data flow. Specifically, one or more QoS flows in the PDU session are mapped to one DRB, and the QoS requirements of the one or more QoS flows are matched with the DRB.
  • Manner 3 The classification identifier based on the data stream is mapped to the corresponding DRB transmission.
  • One possible way is to assign a class identifier to the data stream in the PDU session (for example, mapping to a QCI according to QoS requirements, and the class identifier is QCI), and multiple data streams can be assigned the same category identifier, one Or multiple category IDs are mapped to one DRB.
  • the class identifier is carried when the data packet is transmitted on the Un2 port.
  • the category identifier is carried in the second adaptive identifier on the Un2 port.
  • the RN1 is based on the correspondence between the PDU session and/or the QFI and the classification identifier (referred to as a classification mapping relationship, optionally, the correspondence may be corresponding to one RN/UE), and the data packet is correspondingly
  • the classification identifier is based on the correspondence between the classification identifier and the DRB of the Un2 interface, and the data packet is carried in the DRB for transmission.
  • the manner in which the RN1 obtains the classification mapping relationship is: a configuration of the host base station, or a QAM configuration, or a correspondence between the PDU session and/or the QFI of the data packet received at the Un1 interface and the classification identifier.
  • Another possible way is to carry the classification identifier on the data packet received by the Un1 port, and directly transmit the foregoing data packet to the DRB corresponding to the Un2 port based on the classification mapping relationship.
  • the RN2 For the uplink, the RN2 processes the data packet received on the Un3/Uu port based on the second uplink mapping relationship (for example, GTP-U encapsulation), and then sends the packet to the RN1 through the Un2 port.
  • the data packet sent by the RN2 on the Un2 port carries the second adaptive identifier, and is used by the RN1 to distinguish the data on the Un2 port.
  • the RN2 receives the data packet on the Un3/Uu port, and processes the data packet belonging to a PDU session/SDAP entity through the GTP-U layer of the Un2 port to generate a GTP data packet sent on the Un2 port.
  • the RN2 processes the data packet received at the Un3/Uu port, obtains the PDU session and the QoS flow corresponding to the data packet, and generates a corresponding GTP data packet, where the GTP TEID and the QFI are carried.
  • the RN2 transmits the GTP data packet of the Un2 port to the DRB of the Un2 port of the RN2 in a manner similar to the downlink. For example, any one of the following manners or a combination of any one of the following may be adopted:
  • Manner 1 Map data of one GTP tunnel to the same DRB for transmission
  • Manner 2 The data packets in the GTP tunnel are mapped to multiple DRBs according to the QoS requirements of the data flow. Specifically, one or more QoS flows in the GTP-U are mapped to one DRB, and the QoS requirements of the one or more QoS flows are matched with the DRB.
  • Manner 3 Assign a class identifier to the data flow in the GTP tunnel (for example, mapping to a QCI according to QoS requirements, where the class identifier is QCI), and multiple data streams can be assigned the same category identifier, one or more categories.
  • the identity is mapped to a DRB.
  • the class identifier is carried when the data packet is transmitted on the Un2 port.
  • the class identifier is carried on the GTP data packet on the Un2 port (for example, DSCP is used to represent the QCI) for the host base station to read.
  • the category identifier is carried in the second adaptive identifier of the Un2 port, and is used for reading by the RN1.
  • the RN2 is based on a correspondence between the PDU session (or the GTP TEID) and/or the QFI and the classification identifier (referred to as a classification mapping relationship, optionally, the correspondence may be corresponding to one RN/UE),
  • the classification identifier corresponding to the data packet is obtained, so that the data packet is carried in the DRB based on the correspondence between the classification identifier and the DRB of the Un2 interface.
  • the manner in which the RN2 obtains the classification mapping relationship is: a configuration of the primary base station, an RN1 configuration, or a QAM configuration, or a PDU session (or GTP TEID) and/or a QFI and a classification identifier of the data packet received at the Un2 interface. Correspondence.
  • Figure 33 is a diagram showing a packet mapping process inside RN2 and inside RN1 in a data transmission process.
  • the base station part of the RN2 receives the uplink data on the Un3/Uu port, and obtains the PDU session corresponding to the uplink data based on the DRB information carrying the uplink data and the QFI information on the data packet, thereby generating a GTP data packet, where the GTP data packet is carried.
  • GTP TEID and QFI An optional method is that the RN2 adds a type identifier to the data packet based on the categorization mapping relationship.
  • the type identifier can be carried in the IP layer, for example, by using a DSCP identifier, that is, the type identifier has a correspondence with the DSCP.
  • the relationship may be carried in the second adaptive identifier; the UE part of the RN2 reads the type identifier, and the GTP data packet is carried in the Un2 port according to the second uplink mapping relationship.
  • the RN2 adds the DRB identifier to the data packet based on the second uplink mapping relationship.
  • the DRB identifier may be carried in the IP layer, for example, by using a DSCP identifier, that is, the DRB identifier and the DSCP identifier.
  • the UE has a corresponding relationship; and/or the DRB identifier can be carried in the second adaptive identifier.
  • the UE part of the RN2 reads the DRB identifier, and sends the GTP data packet to the corresponding DRB of the Un2 port for transmission.
  • the correspondence between the type identifier/DRB identifier and the DSCP identifier may be internally defined by the RN2, and the base station part and the UE part of the RN2 are correspondingly and interpreted.
  • the type identifier/DRB identifier may continue to be carried in the uplink data packet sent by the Un2, and the RN1 determines that the data to be received in the Un2 is sent to the host base station through the DRB of the Un1 port, for example, the foregoing identifier is used.
  • the type identifier/DRB identifier may continue to carry the Un1 port, for example, carried in the first adaptive identifier.
  • the action of the RN1 transmitting on the Un1 port after receiving the uplink data packet at the Un2 port is similar to that in FIG.
  • the difference is that RN1 does not submit the above GTP data packet to the GTP-U protocol layer for resolution, so the Un1 port DRB cannot be determined using the information of the GTP header. Therefore, the RN1 may determine the DRB of the Un1 port based on the information of the second adaptive identifier (based on the second uplink mapping relationship), or determine the DRB of the Un1 port based on the mapping relationship between the DRB of the Un2 interface and the DRB of the Un1 interface (based on the second uplink). Mapping relations).
  • RN2 and RN3/UE On the Un3/Uu interface, RN2 and RN3/UE have peer-to-peer protocol layers, including: SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer.
  • the protocol stack of the Un port further includes an adaptation layer function for adding and/or parsing the adaptive identifier.
  • the adaptive function may be included in an existing protocol layer, such as an SDAP layer/PDCP layer/RLC layer/MAC layer/PHY layer; or the adaptive function may be separately deployed in a protocol layer, for example, referred to as adaptation (Adaptation, Referred to as Adapt layer.
  • the adaptation layer may be deployed on the SDAP layer, or between the SDAP layer and the PDCP layer, or between the PDCP layer and the RLC layer, or between the RLC layer and the MAC layer, or deployed in the MAC layer.
  • the PHY layer Between the PHY layer.
  • the method for distinguishing data types and the description of the adaptive identifiers on the interface of the Un3 refer to the descriptions of the previous Un2 port and the second adaptive identifier, and details are not described herein.
  • the function may not be enabled at this time, that is, no additional identification is needed.
  • the RN2 aggregates the data packets that belong to the PDU session received by the Un2 interface, and the RN3/UE is transmitted on the DRB of the Un3/Uu after being processed by the SDAP layer corresponding to the Un3/Uu interface.
  • the RN2 configures the DRB of the radio interface for the RN3/UE through the control plane RRC message, and simultaneously informs the RN3/UE of the mapping relationship between the QoS flow and the DRB in each uplink PDU session.
  • the RN3/UE sends the QoS flow to the RN2 based on the correspondence between the PDU session (and QoS flow) and the DRB in the corresponding DRB.
  • the RN2 will pass the data packet belonging to a PDU session received by the SDAP entity on the Un3/Uu port. After processing, it will be converted into the GTP packet sent on the Un2 port and sent to the RN1 through the Un2 port.
  • FIG. 34 shows a schematic diagram of a protocol stack combination in accordance with an embodiment of the present application.
  • RN1 accesses the donor base station, establishes the Un1 interface with the host base station; RN2 accesses RN1, establishes the Un2 interface with RN1; UE1 accesses RN1, establishes with RN1 Uu1 port; UE2 accesses RN2 and establishes Uu2 port with RN2.
  • the three-hop RN accesses the RN2, and the UE accesses the three-hop RN, and the behaviors of the RN2 and the RN1 may be referred to, and details are not described herein again.
  • the Un1, Un2, Uu1, and Uu2 interface control plane/user plane protocol stacks can each adopt the above-mentioned various control plane/user plane protocol stack candidate manners.
  • RN1 and RN2 can forward data packets.
  • the mapping relationship used is determined based on the type of the packet (control plane or user plane)/attribute information.
  • FIG. 35 shows a flow diagram of a control plane message of the UE 2 accessing the RN 2 according to an embodiment of the present application.
  • the control plane protocol stack 1-AB is used, that is, the uplink, and the RN2 generates the NGAP message for the UE2, and is carried on the DRB of the Un2 interface (optionally, also on the SRB), and sent to the RN1, the RN1.
  • the NGAP message is not parsed, and is transmitted on the DRB of the Un1 port, and the NGAP message is parsed by the host base station.
  • the host base station In the downlink mode, the host base station generates an NGAP message for the UE2, and the DRB of the Un1 port is sent to the RN1.
  • the RN1 does not analyze the packet, and only performs forwarding, and the RN2 parses the packet after receiving it on the Un2 port.
  • FIG. 36 shows a flow diagram of user plane data of UE2 accessing RN2 according to an embodiment of the present application.
  • RN2 is GTP encapsulation for UE2 data, and is carried on DR2 of Un2, and sent to RN1, RN1 does not parse GTP data packet, and GTP
  • the data packet is carried on the DRB of the Un1 port and sent to the host base station, and the GTP data packet is parsed by the host base station.
  • the downlink is in the corresponding manner, that is, the host base station performs GTP encapsulation for the data of the UE2, and is carried on the DRB of the Un1, and is sent to the RN1.
  • the RN1 does not parse the GTP data packet, and carries it to the DRB of the Un2 and sends it to the RN2.
  • the RN2 parses the GTP data packet, and further processes it and sends it to the UE2.
  • FIG. 37 shows a flow diagram of a control plane message of UE1 accessing RN1 according to an embodiment of the present application.
  • the control plane protocol stack 1-A is used, that is, the uplink, and the RN1 generates the NGAP message for the UE1, and carries the DRB of the Un1 interface (optionally, it can also be the SRB, that is, the protocol stack 1-B) ), sent to the host base station.
  • the host base station In the downlink mode, the host base station generates an NGAP message for the UE1 and sends it to the RN1 at the Un1 port.
  • FIG. 38 shows a flow diagram of a user plane message of UE1 accessing RN1 according to an embodiment of the present application.
  • user plane protocol stack 1 that is, uplink
  • RN1 is used for GTP encapsulation of the data of the UE, and is carried on the DRB of Un1 and sent to the host base station.
  • the downlink is in a corresponding manner, that is, the host base station performs GTP encapsulation on the data of the UE1, and is carried on the DRB of the Un1, and is sent to the RN1, and the RN1 further processes and sends the data to the UE.
  • each protocol layer shown in FIG. 4-7, 9-18, 24, 27-28, 31-32, and 34-38 in the present application can be regarded as a function of a relay device and a network device. Modules, these functional modules can be implemented in pure hardware, pure software implementation, or a combination of hardware and software.
  • the transmission method according to the embodiment of the present application is described in detail above with reference to FIG. 1 to FIG. 38.
  • the relay node according to the embodiment of the present application is described in detail below with reference to FIG. 39 to FIG.
  • FIG. 39 shows a schematic block diagram of a relay node 900 according to an embodiment of the present application.
  • the relay node 900 includes:
  • the processing module 910 is configured to generate first data.
  • the processing module 910 is further configured to: according to the attribute information of the first data and the first mapping relationship, control the transceiver module 920 to send the first data to the network device by using the first wireless interface, where the first wireless interface is a wireless interface for performing data transmission between the first relay node and the network device;
  • the first mapping relationship is a correspondence between attribute information of the first data and a radio bearer used to send the first data.
  • the transceiver module 920 receives the first data sent by the second relay node by using a second wireless interface, where the second wireless interface is the first relay node and the second relay node a wireless interface for data transmission between;
  • the processing module 910 is further configured to acquire attribute information of the first data, where the attribute information of the first data includes at least one of the following information: session connection information, data flow information, and information of the first wireless interface.
  • the message type of the first data is the first user plane data
  • the transceiver module 920 receives the first data sent by the second relay node by using the second wireless interface, and the processing module 910 is further configured to: pass the first data to the second relay Node peering PHY protocol layer, MAC protocol layer, RLC protocol layer and PDCP protocol layer processing;
  • the transceiver module 920 sends the first data to the network device by using the first wireless interface, and the processing module 910 is further configured to: pass the first data to a PDCP protocol layer that is peered with the network device. , RLC protocol layer, MAC protocol layer and PHY protocol layer processing;
  • the first user plane data is data of a terminal device connected to the second relay node.
  • the first data is the first user plane data
  • the transceiver module 920 receives the first data sent by the second relay node by using the second wireless interface, and the processing module 910 is further configured to: pass the first data to the second relay Node peering PHY protocol layer, MAC protocol layer, RLC protocol layer, PDCP protocol layer and GTP-U protocol layer processing;
  • the transceiver module 920 sends the first data to the network device by using the first wireless interface, and the processing module 910 is further configured to: pass the first data to a GTP-U protocol layer that is peered with the network device. , PDCP protocol layer, RLC protocol layer, MAC protocol layer and PHY protocol layer processing;
  • the first user plane data is data of a terminal device connected to the second relay node.
  • the first data is the first control plane data
  • the transceiver module 920 receives the first data sent by the second relay node by using the second wireless interface, and the processing module 910 is further configured to: pass the first data to the second relay Node peering PHY protocol layer, MAC protocol layer, RLC protocol layer and PDCP protocol layer processing;
  • the processing module 910 is further configured to: pass the first data to a PDCP protocol layer that is peered with the network device, RLC protocol layer, MAC protocol layer and PHY protocol layer processing;
  • the first control plane data is control plane information related to a terminal device accessing the second relay node.
  • the processing module 910 is further configured to: Processing by the second relay node peering NGAP protocol layer;
  • the processing module 910 is further configured to: pass the first data to an NGAP that is peered with the network device. Protocol layer processing.
  • the processing module 910 is further configured to: The RRC protocol layer processing of the second relay node peer;
  • the processing module 910 is further configured to: pass the first data to an RRC that is peered with the network device. Protocol layer processing.
  • the transceiver module 920 receives the first data sent by the terminal device by using a third wireless interface, where the third wireless interface is a wireless interface that the first relay node communicates with the terminal device;
  • the processing module 910 is further configured to acquire attribute information of the first data, where the attribute information of the first data includes at least one of the following information: session connection information, data flow information, and information of the first wireless interface. Information carried by the radio, information of the radio bearer of the third radio interface, message type, and information of the terminal device.
  • the message type of the first data is the second user plane data
  • the transceiver module 920 sends the first data to the network device by using the first wireless interface, and the processing module 910 is further configured to: pass the first data to a GTP-U that is peered with the network device.
  • the protocol layer, the PDCP protocol layer, the RLC protocol layer, the MAC protocol layer, and the PHY protocol layer; and the second user plane data is data of the terminal device.
  • the first data is the second control plane data
  • the transceiver module 920 sends the first data to the network device by using the first wireless interface, and the processing module 910 is further configured to: pass the first data to an NGAP protocol layer, PDCP, that is peered with the network device.
  • the protocol layer, the RLC protocol layer, the MAC protocol layer and the PHY protocol layer process; the second control plane data is control plane information related to the terminal device.
  • the first mapping relationship is determined by the first relay node; or,
  • the first mapping relationship is configured by the network device or the operation and management entity OAM; or
  • the first data carries information for acquiring the first mapping relationship.
  • FIG. 40 shows a schematic block diagram of a relay node 1000 according to an embodiment of the present application.
  • the relay node 1000 includes:
  • the transceiver module 1010 is configured to receive second data sent by the terminal device.
  • the processing module 1020 is configured to send the second data to the first relay node by using the second wireless interface according to the attribute information of the second data and the second mapping relationship, where the second wireless interface is the first a wireless interface for performing data transmission between the relay node and the second relay node;
  • the second mapping relationship is a correspondence between attribute information of the second data and a radio bearer used to send the second data
  • the attribute information of the second data includes at least one of the following: session connection information, data stream information, information of a radio bearer of the second radio interface, a message type, and information of the terminal device.
  • the message type of the second data is the first user plane data
  • the transceiver module 1010 sends the second data to the first relay node by using the second wireless interface, and the processing module 1020 is further configured to pass the second data to a GTP that is peered with the network device.
  • a U protocol layer a PDCP protocol layer peered with the first relay node, an RLC protocol layer, a MAC protocol layer, and a PHY protocol layer;
  • the first user plane data is data of the terminal device.
  • the message type of the second data is the first user plane data
  • the transceiver module 1010 sends the second data to the first relay node by using the second wireless interface, where the processing module 1020 is further configured to compare the second data with the first relay node.
  • GTP-U protocol layer PDCP protocol layer, RLC protocol layer, MAC protocol layer and PHY protocol layer processing;
  • the first user plane data is data of the terminal device.
  • the message type of the second data is the first user plane data
  • the transceiver module 1010 sends the second data to the first relay node by using the second wireless interface, where the processing module 1020 is further configured to compare the second data with the first relay node.
  • PDCP protocol layer RLC protocol layer, MAC protocol layer and PHY protocol layer processing;
  • the first user plane data is data of the terminal device.
  • processing module 1020 is further configured to generate first control plane data
  • the transceiver module 1010 is further configured to send the first control plane data to the first relay node by using a radio bearer of the second radio interface, where the second radio interface is the first relay node and the second relay a wireless interface for data transmission between nodes;
  • the processing module 1020 is further configured to: pass the first control plane data to the network device.
  • the first control plane data is control plane information related to the terminal device.
  • the second mapping relationship is determined by the second relay node; or,
  • the first mapping relationship is configured by the network device or the operation and management entity OAM; or
  • the first mapping relationship is configured by the first relay node; or
  • the second relay node acquires the first mapping relationship carried by the second data.
  • the network device is a host base station or a third relay node, where the network device is directly or indirectly connected to the first relay node.
  • FIG. 41 is a schematic block diagram of a relay node 1100 provided by an embodiment of the present application.
  • the relay node 1100 includes one or more processors 1110, a memory 1120, and a communication interface 1130; the one or more processors 1110, the memory 1120, and the communication interface 1130 are each connected by an internal path;
  • the memory 1120 is configured to store a computer execution instruction
  • the one or more processors 1110 are configured to execute computer execution instructions stored by the memory 1120, so that the relay node 1100 can perform data interaction with other devices through the communication interface 1130 to perform the foregoing method embodiments. Transmission method.
  • the one or more processors 1110 are configured to perform the following operations:
  • the control communication interface 1130 sends the first data to the network device by using the first wireless interface according to the attribute information of the first data and the first mapping relationship, where the first wireless interface is the first relay node and the a wireless interface for data transmission between network devices;
  • the first mapping relationship is a correspondence between attribute information of the first data and a radio bearer used to send the first data.
  • the relay node 1100 may be specifically the relay node 900 in the foregoing embodiment, and may be used to perform various steps and/or processes corresponding to the relay node 900 in the foregoing method embodiment.
  • FIG. 42 shows a schematic block diagram of a relay node 1200 provided by an embodiment of the present application.
  • the relay node 1200 includes one or more processors 1210, a memory 1220, and a communication interface 1230; the one or more processors 1210, the memory 1220, and the communication interface 1230 are each connected by an internal path;
  • the memory 1220 is configured to store a computer execution instruction
  • the one or more processors 1210 are configured to execute computer execution instructions stored by the memory 1220, so that the relay node 1200 can perform data interaction with other devices through the communication interface 1230 to perform the foregoing method embodiments. Transmission method.
  • the one or more processors 1210 are configured to perform the following operations:
  • the second mapping relationship is a correspondence between attribute information of the second data and a radio bearer used to send the second data
  • the attribute information of the second data includes at least one of the following: session connection information, data stream information, information of a radio bearer of the second radio interface, a message type, and information of the terminal device.
  • the relay node 1200 may be specifically the relay node 1000 in the foregoing embodiment, and may be used to perform various steps and/or processes corresponding to the relay node 1000 in the foregoing method embodiments.
  • the embodiment of the present application further provides a chip system, the chip system includes: one or more processors, one or more memories, and an interface circuit, wherein the interface circuit is responsible for information interaction between the chip system and the outside world, One or more memories, the interface circuit, and the one or more processors are interconnected by a line, the one or more memories having instructions stored therein; the instructions being executed by the one or more processors to The first relay node or the second relay node may be caused to perform an operation of the first relay node or the second relay node corresponding to the above method.
  • the embodiment of the present application further provides a communication system, including: a first relay node, and/or a second relay node; wherein the first relay node is the first relay described in the foregoing aspects. a node, the second relay node being the second relay node described in the above aspects.
  • the embodiment of the present application further provides a computer program product, which is applied to a first relay node or a second relay node, where the computer program product includes a series of instructions when the instruction is executed, so that the The network device, the server, or the terminal device may perform an operation of the first relay node or the second relay node corresponding to the above method.
  • the processor may be an integrated circuit chip with signal processing capabilities.
  • each step of the foregoing method embodiment may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA), or the like. Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory.
  • the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
  • RAM Random Access Memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM).
  • SDRAM Double Data Rate SDRAM
  • DDR SDRAM Double Data Rate SDRAM
  • ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • SLDRAM Synchronous Connection Dynamic Random Access Memory
  • DR RAM direct memory bus random access memory
  • system and “network” are used interchangeably herein.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the character "/" in this article generally indicates that the contextual object is an "or" relationship.
  • B corresponding to A means that B is associated with A, and B can be determined according to A.
  • determining B from A does not mean that B is only determined based on A, and that B can also be determined based on A and/or other information.
  • the computer program product can include one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic disk), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read only memory, a random access memory, a magnetic disk, or an optical disk.

Landscapes

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

Abstract

本申请提供一种传输方法和中继节点，该方法包括：第一中继节点根据第一数据的属性信息和第一映射关系，通过第一无线接口向网络设备发送所述第一数据，所述第一无线接口为所述第一中继节点和所述网络设备之间进行数据传输的无线接口；其中，所述第一映射关系为所述第一数据的属性信息与发送所述第一数据使用的无线承载之间的对应关系。本申请实施例的传输方法，可以支持R10 Relay中多跳场景，从而满足未来网络更加多样化的需求。

Description

一种传输方法和中继节点
本申请要求于2017年12月1日提交中国专利局、申请号为201711252183.6、申请名称为“一种传输方法和中继节点”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种传输方法和中继节点。
背景技术
第10版长期演进技术(Long Term Evolution Release 10，LTE R10)中引入了中继(Relay)技术，由于Relay节点具备无线自回传，节省传统基站部署有线回传链路时的挖沟埋线成本，同时增加了部署的灵活性，尤其适用于5G及演进的通信系统的网络初期铺展。
但是，现有R10 Relay仅能支持比较简单的部署场景，如单跳单宿主基站(donor base station)，为了能提供更好的性能，满足未来网络更加多样化的需求，如何在R10 Relay中支持多跳场景，以满足未来网络更加多样化的需求，成为了一个亟待解决的问题。
发明内容
本申请提供一种传输方法和中继节点，可以支持R10 Relay中多跳场景，从而满足未来网络更加多样化的需求。
第一方面，提供了一种传输方法，该方法包括：第一中继节点根据第一数据的属性信息和第一映射关系，通过第一无线接口向网络设备发送所述第一数据，所述第一无线接口为所述第一中继节点和所述网络设备之间进行数据传输的无线接口；其中，所述第一映射关系为所述第一数据的属性信息与发送所述第一数据使用的无线承载之间的对应关系。
结合第一方面，在第一方面的某些可能的实现方式中，所述第一中继节点通过第二无线接口接收第二中继节点发送的所述第一数据，所述第二无线接口为所述第一中继节点和所述第二中继节点之间进行数据传输的无线接口；所述第一中继节点获取所述第一数据的属性信息，所述第一数据的属性信息包含以下信息中的至少一种：会话连接信息、数据流信息、所述第一无线接口的无线承载的信息、所述第二无线接口的无线承载的信息、消息类型以及所述第一数据所属节点的信息。
结合第一方面，在第一方面的某些可能的实现方式中，所述第一数据的消息类型为第一用户面数据时，所述第一中继节点通过所述第二无线接口接收所述第二中继节点发送的所述第一数据，所述第一数据经过与所述第二中继节点对等的PHY协议层，MAC协议层，RLC协议层和PDCP协议层处理；所述第一中继节点通过所述第一无线接口向所述网络设备发送所述第一数据，所述第一数据经过与所述网络设备对等的PDCP协议层，RLC协 议层，MAC协议层和PHY协议层处理；所述第一用户面数据为与所述第二中继节点连接的终端设备的数据。
在一些可能的实现方式中，该第一数据还经过自适应功能处理，添加自适应标识，该自适应标识用于第一中继节点获取数据的属性信息。
本申请实施例的传输方法，中继节点接收时无需解析GTP-U数据，发送时无需进行GTP-U封装，有助于简化中继节点的行为，节省处理处理开销，加快数据转发的速度。
结合第一方面，在第一方面的某些可能的实现方式中，所述第一数据为第一用户面数据时，所述第一中继节点通过所述第二无线接口接收所述第二中继节点发送的所述第一数据，所述第一数据经过与所述第二中继节点对等的PHY协议层，MAC协议层，RLC协议层，PDCP协议层和GTP-U协议层处理；所述第一中继节点通过所述第一无线接口向所述网络设备发送第一数据，所述第一数据经过与所述网络设备对等的GTP-U协议层，PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；所述第一用户面数据为与所述第二中继节点连接的终端设备的数据。
本申请实施例的传输方法，中继节点无需针对不同的用户面数据进行不同的处理，沿用现有的机制，对标准工作改动较少，中继节点可以获知每一个终端设备的用户面数据的信息。
结合第一方面，在第一方面的某些可能的实现方式中，所述第一数据为所述第一控制面数据时，所述第一中继节点通过所述第二无线接口接收所述第二中继节点发送的所述第一数据，所述第一数据经过与所述第二中继节点对等的PHY协议层，MAC协议层，RLC协议层和PDCP协议层处理；所述第一中继节点通过第一无线接口向所述网络设备发送所述第一数据时，所述第一数据经过与所述网络设备对等的PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；所述第一控制面数据为与接入所述第二中继节点的终端设备相关的控制面信息。
在一些可能的实现方式中，该第一数据还经过自适应功能处理，添加自适应标识，该自适应标识用于第一中继节点获取数据的属性信息。
本申请实施例的传输方法，通过自适应层的功能来代替GTP-U封装，有助于节省中继节点进行数据封装以及解封装的开销。
结合第一方面，在第一方面的某些可能的实现方式中，所述第一中继节点通过所述第二无线接口接收所述第二中继节点发送的所述第一数据时，所述第一数据还经过与所述第二中继节点对等的NGAP协议层处理；所述第一中继节点通过所述第一无线接口向所述网络设备发送所述第一数据时，所述第一数据还经过与所述网络设备对等的NGAP协议层处理。
本申请实施例的传输方法，通过NGAP层的处理，可以获取终端设备相关的控制面信息，有助于简化中继节点的行为，节省处理处理开销，加快数据转发的速度。
结合第一方面，在第一方面的某些可能的实现方式中，所述第一中继节点通过所述第二无线接口接收所述第二中继节点发送的所述第一数据时，所述第一数据还经过与所述第二中继节点对等的RRC协议层处理；所述第一中继节点通过所述第一无线接口向所述网络设备发送所述第一数据时，所述第一数据还经过与所述网络设备对等的RRC协议层处理。
本申请实施例的传输方法，用RRC层代替NGAP层进行，减少了中继节点解析和重组NGAP消息的过程，将NGAP消息承载在SRB上传输，有助于区分控制面数据类型。
结合第一方面，在第一方面的某些可能的实现方式中，所述第一中继节点通过第三无线接口接收终端设备发送的所述第一数据，所述第三无线接口为第一中继节点与所述终端设备通信的无线接口；所述第一中继节点获取所述第一数据的属性信息，所述第一数据的属性信息包含以下信息中的至少一种：会话连接信息、数据流信息、所述第一无线接口的无线承载的信息、所述第三无线接口的无线承载的信息、消息类型以及所述终端设备的信息。
结合第一方面，在第一方面的某些可能的实现方式中，所述第一数据的消息类型为第二用户面数据时，所述第一中继节点通过所述第一无线接口向所述网络设备发送所述第一数据，所述第一数据经过与所述网络设备对等的GTP-U协议层，PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；所述第二用户面数据为所述终端设备的数据。
本申请实施例的传输方法，中继节点同时为终端设备和多条中继节点服务，可以区分两种数据类型，针对每一种数据类型，进行更加适当的处理。
结合第一方面，在第一方面的某些可能的实现方式中，所述第一数据为第二控制面数据时，所述第一中继节点通过所述第一无线接口向所述网络设备发送第一数据，所述第一数据经过与所述网络设备对等的NGAP协议层，PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；所述第二控制面数据为与所述终端设备相关的控制面信息。
结合第一方面，在第一方面的某些可能的实现方式中，第一映射关系由第一中继节点确定；或者，所述第一映射关系由所述网络设备或运营和管理实体OAM配置；或者，所述第一中继节点在第一无线接口接收的所述第一数据时，所述第一数据携带用于获取所述第一映射关系的信息。
第二方面，提供了一种传输方法，该方法包括：第二中继节点接收终端设备发送的第二数据；所述第二中继节点根据所述第二数据的属性信息和第二映射关系，通过第二无线接口向第一中继节点发送所述第二数据，所述第二无线接口为所述第一中继节点和第二中继节点之间进行数据传输的无线接口；所述第二映射关系为第二数据的属性信息与发送所述第二数据使用的无线承载之间的对应关系；所述第二数据的属性信息包含以下信息中的至少一种：会话连接信息、数据流信息、所述第二无线接口的无线承载的信息、消息类型以及所述终端设备的信息。
结合第二方面，在第二方面的某些可能的实现方式中，所述第二数据的消息类型为第一用户面数据时，所述第二中继节点通过所述第二无线接口向所述第一中继节点发送所述第二数据，所述第二数据经过与网络设备对等的GTP-U协议层，与第一中继节点对等的PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；所述第一用户面数据为所述终端设备的数据。
本申请实施例的传输方法，中继节点无需解析GTP-U数据，有助于简化中继节点的行为，节省处理处理开销，加快数据转发的速度。
结合第二方面，在第二方面的某些可能的实现方式中，所述第二数据的消息类型为第一用户面数据时，所述第二中继节点通过所述第二无线接口向所述第一中继节点发送所述第二数据，所述第二数据经过与第一中继节点对等的GTP-U协议层，PDCP协议层，RLC 协议层，MAC协议层和PHY协议层处理；所述第一用户面数据为所述终端设备的数据。
本申请实施例的传输方法，通过GTP-U协议层携带相关信息，有助于中继节点进行数据转发。
结合第二方面，在第二方面的某些可能的实现方式中，所述第二数据的消息类型为第一用户面数据时，所述第二中继节点通过所述第二无线接口向所述第一中继节点发送所述第二数据，所述第二数据经过与第一中继节点对等的PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；所述第一用户面数据为所述终端设备的数据。
在一些可能的实现方式中，该第一数据还经过自适应功能处理，添加自适应标识，该自适应标识用于第一中继节点获取数据的属性信息。
本申请实施例的传输方法，中继节点不进行GTP-U封装，而是用自适应层标识携带，有助于节省中继节点对数据处理的过程。
第三方面，提供了一种传输方法，该方法包括：第二中继节点生成第一控制面数据；第二中继节点使用第二无线接口的无线承载向第一中继节点发送所述第一控制面数据，所述第二无线接口为所述第一中继节点和第二中继节点之间进行数据传输的无线接口；所述第二中继节点通过所述第二无线接口向所述第一中继节点发送所述第一控制面数据时，所述第一控制面数据经过与网络设备对等的NGAP协议层，与第一中继节点对等的PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；所述第一控制面数据为与终端设备相关的控制面信息。
结合第二和第三方面，在第二和第三方面的某些可能的实现方式中，所述第二映射关系由第二中继节点确定；或者，所述第一映射关系由所述网络设备或运营和管理实体OAM配置；或者，所述第一映射关系由所述第一中继节点配置；或者所述第二中继节点获取所述第二数据携带的所述第一映射关系。
结合第二方面和第三方面的某些可能的实现方式，所述网络设备为宿主基站或者第三中继节点，其中，所述网络设备与所述第一中继节点直接或者间接相连。
第四方面，提供了一种中继节点，用于执行第一方面或第一方面任意可能的实现方式中的方法。具体地，该网络设备包括用于执行上述第一方面或第一方面的任一种可能的实现方式中的方法的模块。
第五方面，提供了一种中继节点，用于执行第二方面或第二方面任意可能的实现方式中的方法。具体地，该中继节点包括用于执行上述第二方面或第二方面的任一种可能的实现方式中的方法的模块。
第六方面，提供了一种中继节点，用于执行第三方面或第三方面任意可能的实现方式中的方法。具体地，该中继节点包括用于执行上述第三方面或第三方面的任一种可能的实现方式中的方法的模块。
第七方面，提供了另一种中继节点，该中继节点包括：收发器、存储器和处理器。其中，该收发器、该存储器和该处理器通过内部连接通路互相通信，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制接收器接收信号，并控制发送器发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第一方面或第一方面的任一种可能的实现方式中的方法。
第八方面，提供了另一种中继节点，该中继节点包括：收发器、存储器和处理器。其 中，该收发器、该存储器和该处理器通过内部连接通路互相通信，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制接收器接收信号，并控制发送器发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第二方面或第二方面的任一种可能的实现方式中的方法。
第九方面，提供了另一种中继节点，该中继节点包括：收发器、存储器和处理器。其中，该收发器、该存储器和该处理器通过内部连接通路互相通信，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制接收器接收信号，并控制发送器发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第三方面或第三方面的任一种可能的实现方式中的方法。
第十方面，提供了一种通信系统，该系统包括上述第四方面或第四方面的任一种可能实现方式中的中继节点以及第五方面或第五方面的任一种可能实现方式中的中继节点；或者
该系统包括上述第四方面或第四方面的任一种可能实现方式中的中继节点以及第六方面或第六方面的任一种可能实现方式中的中继节点；或者
该系统包括上述第七方面或第七方面的任一种可能实现方式中的中继节点以及第八方面或第八方面的任一种可能实现方式中的中继节点；或者
该系统包括上述第七方面或第七方面的任一种可能实现方式中的中继节点以及第九方面或第九方面的任一种可能实现方式中的中继节点。
第十一方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码被计算机运行时，使得所述计算机执行上述第一方面或第一方面任一种可能实现方式中的方法。
第十二方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码被计算机运行时，使得所述计算机执行上述第二方面或第二方面任一种可能实现方式中的方法。
第十三方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码被计算机运行时，使得所述计算机执行上述第三方面或第三方面任一种可能实现方式中的方法。
第十四方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的指令。
第十五方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第二方面或第二方面的任意可能的实现方式中的方法的指令。
第十六方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第三方面或第三方面的任意可能的实现方式中的方法的指令。
第十七方面，提供了一种芯片系统，应用于中继节点中，该芯片系统包括：一个或多个处理器、一个或多个存储器和接口电路，所述接口电路负责所述芯片系统与外界的信息交互，所述一个或多个存储器、所述接口电路和所述一个或多个处理器通过线路互联，所述一个或多个存储器中存储有指令；所述指令被所述一个或多个处理器执行，以进行上述各个方面的所述的方法中所述第一中继节点的操作。
第十八方面，提供了一种芯片系统，应用于中继节点中，该芯片系统包括：一个或多 个处理器、一个或多个存储器和接口电路，所述接口电路负责所述芯片系统与外界的信息交互，所述一个或多个存储器、所述接口电路和所述一个或多个处理器通过线路互联，所述一个或多个存储器中存储有指令；所述指令被所述一个或多个处理器执行，以进行上述各个方面的所述的方法中所述第二中继节点的操作。
附图说明
图1是LTE R10 Relay的控制面协议栈架构。
图2是LTE R10 Relay的用户面协议栈架构。
图3是LTE R10 Relay中中继节点入网方法的示意性流程图。
图4是本申请实施例的两跳RN入网方法的示意性流程图。
图5是本申请实施例的L3协议栈控制面架构1-A的示意图。
图6是本申请实施例的L3协议栈控制面架构1-B的示意图。
图7是本申请实施例的L3协议栈控制面架构2的示意图。
图8是本申请实施例的三跳RN入网方法的示意性流程图。
图9是本申请实施例的L3协议栈控制面架构1-A-A的示意图。
图10是本申请实施例的L3协议栈控制面架构1-B-A的示意图。
图11是本申请实施例的L3协议栈控制面架构2的另一示意图。
图12是本申请实施例的L3协议栈控制面架构1-A-B的示意图。
图13是本申请实施例的L3协议栈控制面架构1-B-B的示意图。
图14是本申请实施例的L3协议栈控制面架构1-A-A的另一示意图。
图15是本申请实施例的L3协议栈控制面架构1-B-A的另一示意图。
图16是本申请实施例的L3协议栈控制面架构2的再一示意图。
图17是本申请实施例的L3协议栈控制面架构1-A-B的另一示意图。
图18是本申请实施例的L3协议栈控制面架构1-B-B的另一示意图。
图19是本申请实施例的传输方法的示意性流程图。
图20是本申请实施例的传输方法的另一示意性流程图。
图21示出了根据本申请实施例的二跳RN/终端设备通过控制面进行会话建立的方法的示意性流程图。
图22示出了一种三跳RN/终端设备通过控制面进行会话建立的方法的示意性流程图。
图23示出了根据本申请实施例的基于控制面协议栈1-A-B和1-B-B介绍三跳RN/终端设备通过控制面进行会话建立的方法的示意性流程图。
图24是本申请实施例的L3协议栈用户面架构1的一示意图。
图25是一种Un1无线接口的数据传输过程的示意图。
图26是一种数据传输过程中RN1映射过程的示意图。
图27是本申请实施例的L3协议栈用户面架构2的一示意图。
图28是本申请实施例的L3协议栈用户面架构1-A的一示意图。
图29是一种Un1无线接口的数据传输过程的示意图。
图30是一种数据传输过程中RN1映射过程的示意图。
图31是本申请实施例的L3协议栈用户面架构2的另一示意图。
图32是本申请实施例的L3协议栈用户面架构1-B的另一示意图。
图33是一种数据传输过程中RN1映射过程的示意图。
图34是根据本申请实施例的协议栈组合的示意图。
图35是本申请实施例的接入RN2的UE2的控制面消息的流向示意图。
图36是本申请实施例的接入RN2的UE2的用户面数据的流向示意图。
图37是本申请实施例的接入RN1的UE1的控制面消息的流向示意图。
图38是本申请实施例的接入RN1的UE1的用户面消息的流向示意图。
图39是本申请实施例的中继节点的示意性框图。
图40是本申请实施例的中继节点的另一示意性框图。
图41是本申请实施例的中继节点的再一示意性框图。
图42是本申请实施例的中继节点的再一示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、未来的第五代(5th Generation，5G)系统或新无线(New Radio，NR)等。
本申请实施例中的终端设备可以指用户设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者未来演进的公用陆地移动通信网络(Public Land Mobile Network，PLMN)中的终端设备等，本申请实施例对此并不限定。
本申请实施例中的网络设备可以是用于与终端设备通信的设备，该网络设备可以是宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(Evolutional NodeB，eNB或eNodeB)，还可以是云无线接入网络(Cloud Radio Access Network，CRAN)场景下的无线控制器，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等，本申请实施例并不限定。
第10版长期演进技术(Long Term Evolution Release 10，LTE R10)中引入了中继(Relay)技术，图1示出了LTE R10 Relay的控制面协议栈架构。控制面中包括用户设备(User Equipment，UE)、中继节点(Relay Node，RN)、宿主基站(DeNB)和为UE服务的移动管理模块(Mobility Management Entity，MME)(图中记为MME-UE)，UE的协议栈中从上至下包括非接入层(Non-Access Stratum，NAS)、无线资源控制(Radio Resource Control，RRC)层、分组数据汇聚协议(Packet Data Convergence Protocol，PDCP) 层、无线链路控制(Radio Link Control，RLC)层、媒体接入控制(Media Access Control，MAC)层和物理层(Physical，PHY)层；RN与UE通信的协议栈中从上至下包括RRC层、PDCP层、RLC层、MAC层和PHY层，与宿主基站通信的协议栈中从上至下包括S1应用协议(S1Application Protocol，简称S1-AP)层、流控制传输协议(Stream Control Transmission Protocol，SCTP)层、网络之间互连的协议(Internet Protocol，IP)层、PDCP层、RLC层、MAC层和PHY层；宿主基站与RN通信的协议栈中从上至下包括S1-AP层、SCTP层、IP层、PDCP层、RLC层、MAC层和PHY层；与MME-UE通信的协议栈中从上至下包括S1-AP层、SCTP层、IP层、数据链路层(也可以称为L2层)和物理层(也可以称为L1层)；MME-UE的协议栈中从上至下包括NAS、S1-AP层、SCTP层、IP层、L2层和L1层。R10 Relay控制面有完整的协议栈，UE的RRC消息终结在RN，同时RN为UE提供S1/X2消息的代理(proxy)，其中，S1接口为宿主基站和CN控制面实体之间的接口，X2接口可以为宿主基站和RN(或者RN和RN)之间的接口。
图2示出了LTE R10 Relay的用户面协议栈架构。用户面中包括UE、RN、宿主基站和为UE服务的服务网关(Serving Gateway，SGW)/公用数据网网关(Public Data Network Gateway，PGW)(图中记为SGW-UE/PGW-UE)，其中，UE的协议栈中从上至下包括IP层、PDCP层、RLC层、MAC层和PHY层；RN与UE通信的协议栈中从上至下包括PDCP层、RLC层、MAC层和PHY层，与宿主基站通信的协议栈中从上至下包括通用分组无线服务隧道协议用户面(General Packet Radio Service Tunneling Protocol-User Plane，GTP-U)层、用户数据报协议(User Datagram Protocol，UDP)层、IP层、PDCP层、RLC层、MAC层和PHY层；宿主基站与RN通信的协议栈中从上至下包括GTP-U层、UDP层、IP层、PDCP层、RLC层、MAC层和PHY层，与SGW-UE/PGW-UE通信的协议栈中从上至下包括GTP-U层、UDP层、IP层、L2层和L1层；SGW-UE/PGW-UE中从上至下包括IP层、GTP-U层、UDP层、IP层、L2层和L1层。R10 Relay用户面也有完整的协议栈，能够为UE提供无线接口数据无线承载(Data Radio Bearer，DRB)传输服务，并且可以将多个UE的数据进行汇聚，通过回传链路一并转发给宿主基站。
图3示出了LTE R10 Relay中中继节点入网方法100的示意性流程图，如图3所示，该方法100包括：
S110，中继节点(RN)开启UE模式接入宿主基站(DeNB)，建立控制面和数据面连接，目的是从运营和管理实体(Operation And Management，OAM)获取DeNB小区列表；
S120，RN从DeNB小区列表中选择一个DeNB小区以Relay模式接入，OAM配置RN小区的演进的通用移动通信系统陆地无线接入网小区全局标识符(Evolved UMTS Terrestrial Radio Access Network Cell Global Identifier，ECGI)，RN与DeNB建立回传链路的S1/X2连接。
由于Relay节点具备无线自回传，节省部署传统基站时铺设有线回传链路的挖沟埋线的成本，同时增加了部署的灵活性，尤其适用于5G及演进的通信系统的网络初期铺展。但是R10 Relay仅能支持比较简单的部署场景，如单跳单宿主基站，为了能提供更好的性能，满足未来网络更加多样化的需求，因此需要研究支持多跳场景的Relay。本申请实施例即提供基本的协议栈架构，基于各种协议栈架构同时介绍多跳Relay的入网流程，UE 的入网流程，以及用户面服务质量(Quality of Service，QoS)映射机制和配置方法。
在多跳RN场景下，与R10 Relay的区别是UE的数据包要经过多个RN节点，各节点的行为需要明确，可以从控制面和用户面两个角度进行分析：
控制面的问题是消息的生成和传递。一般来说无线接口控制面连接，是指直接相连的两个节点之间用于传输控制面消息的无线接口连接，例如UE与该UE接入的RN之间的无线接口控制面连接。由于在4G系统中，无线接口控制面连接称为无线资源控制RRC连接，本文为了便于描述，仅以RRC连接作为无线接口控制面连接的一种示例，对无线接口控制面连接的建立和消息传递的过程进行描述，但是上述过程并不限于4G系统，也不限于RRC连接的建立和管理，可以应用于5G及以后的演进网络中。与无线接口控制面连接类似的，接入网(Radio Access Network，简称RAN)与核心网(Core Network，简称CN)之间的接口的控制面连接是指直接相连的RAN节点与CN节点之间传输控制面消息的接口。在5G系统中，RAN与核心网之间的接口称为NG接口，其上承载NG应用层协议(Application Protocol，简称AP)，通过传输NGAP消息来进行接口的管理和接入网络的UE的管理。本文为了便于描述，仅以NG接口和NGAP消息作为RAN与CN之间接口和接口消息的一种示例，对RAN与CN之间接口的建立和消息传递的过程进行描述，但是上述过程并不限于5G系统(接口消息的名称仅为示例，也可以代表具有不同名称但是具有相同或类似功能的消息)，也不限于NG接口的管理和NGAP消息的传递，可以应用于5G以后的演进网络中。无线接口RRC连接建立完成后，接入网通过NGAP消息中的Initial UE message来通知核心网一个新的UE已经接入，进而核心网和接入网为该UE进行认证和/或安全激活，以及后续为该UE配置上下文和数据传输资源。对于本申请实施例中涉及的L3多跳RN，下一跳RN/UE与RN建立初始RRC连接之后，该RN如何通知Donor有新的RN/UE接入网络，可以通过RRC消息/或者NGAP的Initial UE message两种方式，若通过NGAP消息的方式，则该消息可以承载在信令无线承载(Signaling Radio Bearer，SRB)中或者承载在该RN的数据无线承载(DRB)中，后者与现有的R10 Relay类似。
用户面的问题是中间节点如何进行数据包的转发，例如，对于上行，是否需要区分是RN的数据还是UE的数据进行不同的转发行为，如何决定数据承载的无线接口无线承载(Radio Bearer，RB)；又例如，对于下行，RN如何区分是自己的数据还是下一条RN的数据。涉及到数据包的转发策略，包括数据包的标识，以按需区分数据包的来源/目的地；以及一个整体的QoS映射框架。
图4示出了根据本申请实施例的两跳RN入网方法200的示意性流程图，如图4所示，该方法200包括：
S201，第二中继节点获取接入信息，该接入信息用于第二中继节点获取接入第一中继节点所需的信息，例如随机接入资源等。可选地，该接入辅助信息中可以包括以下信息中的任一种或任意多种的组合：允许接入指示，跳数信息，以及RN专用随机接入资源。其中，允许接入指示用于第二中继节点确定是否可以接入该第一中继节点；跳数信息用于第二中继节点确定接入该第一中继节点后自身的跳数；RN专用随机接入资源用于指示第一中继节点提供的RN专用的随机接入资源，所述RN专用随机接入资源是指仅供RN进行随机接入时使用，普通UE不能使用该RN专用随机接入资源。。
可选地，第一中继节点向第二中继节点发送广播消息，其中携带该接入辅助信息。可选地，该广播消息为系统信息(System Information)。
S202，第二中继节点建立第二无线接口的控制面连接。其中，第二无线接口为第二中继节点与第一中继节点进行通信的无线接口。可选地，该控制面连接为RRC连接。
示例性的，该控制面连接建立过程包括以下S2021-S2023。
S2021，该第二中继节点向该第一中继节点发送随机接入请求消息，该第一中继节点向该第二中继节点发送随机接入请求响应。
S2022，该第二中继节点向该第一中继节点发送连接建立请求消息，该第一中继节点向该第二中继节点发送连接建立响应消息。
可选地，该连接建立请求消息可以为RRC连接建立请求消息(RRC Connection Setup Request)，该连接建立消息可以为RRC连接建立消息(RRC Connection Setup)。
S2023，该第二中继节点向该第一中继节点发送连接建立完成消息。
可选地，该连接建立完成消息可以为RRC连接建立完成消息(RRC Connection Setup Complete)。
S2024，可选地，第二中继节点向第一中继节点发送第一个上行NAS消息(第一NAS消息)。
可选地，该第一NAS消息用于表示第二中继节点向核心网的注册请求。
可选地，该第一NAS消息可以携带在上述控制面连接建立完成的消息中，例如RRC连接建立完成消息。
S203，该第一中继节点在第一无线接口，向网络设备发送第一消息，该第一消息是第一无线接口上上行第一个与该第二中继节点相关的消息(RN2 associated message)，可选地，该第一消息携带该第二中继节点的第一个上行NAS消息。该第一无线接口为该第一中继节点与该网络设备进行通信的无线接口。
可选地，该第一消息需要携带第二中继节点的第一标识，用于第一中继节点和宿主基站在该第一无线接口上识别第二中继节点。可选地，第一标识可以通过自适应功能添加(例如，第一标识存在于自适应层包头中)。
可选地，该第一标识可以包含以下信息中的任一种或任意多种的组合：RN1 RN/UE NGAP ID-Un1(第一中继节点为该标识对应的设备在第一无线接口上承载的NG连接分配的ID)，第二标识(其他形式的ID，可以用于识别该标识对应的设备)，SRB标识/DRB标识，逻辑信道标识，第一中继节点在第一无线接口为该标识对应的设备分配的标识，以及宿主基站在第一无线接口为该标识对应的设备分配的标识。
可选地，上述第一标识可能不区分是UE还是RN，即RN与UE使用相同的标识格式；或者，上述标识区分UE和RN，当设备为UE时，采用UE的标识格式，当设备为RN时，采用RN的标识格式；另外，如果套用现有的NGAP中UE ID，则RN1 RN/UE NGAP ID-Un1等同于RAN UE NGAP ID。示例性的，上述第二标识可以为以下标识的任一种或任意多种的组合：该标识对应的设备接入小区标识信息(例如为物理小区标识PCI，或者全局小区标识ECGI)，该标识对应的设备标识信息(例如小区级无线网络临时标识C-RNTI)，该标识对应的设备接入的RN的标识信息(可选地，其中携带RN标识，用于指示被接入的基站为RN)，该标识对应的设备接入的RN的跳数信息，核心网控制面节点为该标识对 应的设备分配的标识(例如S-TMSI，GUTI)，核心网控制面节点标识(例如AMF ID，AMF pointer，AMF group ID，AMF全局标识)。可以理解，一种可能的情况是，上述第二标识可能不区分UE和RN，即RN使用与UE相同的ID格式；另一种情况是，上述标识区分UE和RN，当设备为UE时，采用UE的标识格式，当设备为RN时，采用RN的标识格式。
需要说明的是，宿主基站为该网络设备的一种示例，为了方便描述，下面用宿主基站代替网络设备来进行实施方式的描述。
可选地，该第一消息可以为承载在第一无线接口上传输的NG接口应用层协议(NG application protocol，NGAP)的消息，例如初始UE消息(Initial UE message)。
可选地，上述NGAP消息可以承载在第一无线接口的DRB上，或者SRB上传输。
可选地，该第一消息可以为RRC消息。
可选地，该第一消息中携带该第二中继节点向核心网发送的第一个上行NAS消息，宿主基站将该第二中继节点的第一个上行NAS消息发送给为中继服务的核心网控制面节点。
可选地，宿主基站基于第一消息中的第一标识，识别出第二中继节点，并为第二中继节点分配NG-C接口上的第一终端标识，例如RAN UE NGAP ID。
可选地，宿主基站保存第二中继节点的第一标识与第一终端标识的对应关系。其中，第一终端标识用于宿主基站和/或核心网控制面节点在NG-C接口上识别中继节点。
示例性的，若第一消息为承载在第一无线接口中传输的NGAP消息，且其中携带的RN1 RN NGAP ID-Un1为第一中继节点内唯一的标识，宿主基站收到第一消息后，需要将其中的RN1 RN NGAP ID-Un1替换为宿主基站为第二中继节点分配的在NG-C接口上能够识别该第二中继节点的标识，例如RAN RN NGAP ID。宿主基站保存第二中继节点的上述RN1 RN NGAP ID-Un1与RAN RN NGAP ID的映射关系。
宿主基站接收该核心网控制面节点的响应消息。
示例性的，该步骤具体包括步骤S206-208。
S204，宿主基站收到第一消息后，获知第二中继节点通过第一中继节点接入网络，宿主基站根据第一消息生成第一NGAP消息发送给为中继服务的核心网控制面节点(CN CP_RN，例如AMF)。
可选地，该第一NGAP消息携带上述第二中继节点的第一个上行NAS消息。示例性的，该NGAP消息为初始UE消息。
S205，核心网对该第二中继节点进行认证和安全，成功后允许该第二中继节点注册，失败则拒绝该第二中继节点在网络中注册。
S206，该核心网节点向宿主基站发送第二NGAP消息。可选地，该第二NGAP消息携带核心网对上述第二中继节点的第一个上行NAS消息的响应消息。
可选地，该NAS响应消息为表示注册成功或拒绝的NAS消息。可选地该NGAP消息为初始上下文配置请求。
可选地，该NGAP消息中包含核心网节点为RN2分配的用于在NG-C上识别RN2的标识，例如AMF RN NGAP ID。宿主基站收到上述NGAP消息，基于其中包含的RAN RN NGAP ID识别出RN2，并保存AMF RN NGAP ID与该RN2的对应关系。
S207，宿主基站在该第一无线接口，向该第一中继节点发送第二消息。可选地，该第二消息携带上述第二中继节点的第一个上行NAS响应消息。可选地，该第二消息包括初始上下文配置请求中的至少部分。
可选地，由于宿主基站在NG-C上收到的响应消息中包含核心网控制面节点为第二中继节点分配的第二终端标识，例如AMF RN NGAP ID，当宿主基站基于该响应消息在第一无线接口上发送第二消息时，需要在第二消息中携带第二中继节点的第三标识，用于第一中继节点识别第二中继节点。
可选地，该第三标识可以包含以下信息中的任一种或任意多种的组合：Donor RN/UE NGAP ID(宿主基站为该标识对应的设备在第一无线接口上承载的NG连接分配的ID)，第二标识(其他形式的ID，可以用于识别该标识对应的设备)，SRB标识/DRB标识，逻辑信道标识，第一中继节点在第一无线接口为该标识对应的设备分配的标识，以及宿主基站在第一无线接口为该标识对应的设备分配的标识。
可选地，上述第三标识可能不区分是UE还是RN，即RN与UE使用相同的标识格式；或者，上述标识区分UE和RN，当设备为UE时，采用UE的标识格式，当设备为RN时，采用RN的标识格式；另外，如果套用现有的NGAP中UE ID，则Donor RN/UE NGAP ID等同于AMF UE NGAP ID。可以理解，第三标识可以与第一标识是同一个标识。
可选地，宿主基站将上述第二终端标识替换为第二中继节点的第三标识。
可选地，第二消息中还携带第二中继节点的第一标识。
可选地，宿主基站保存上述第二终端标识与第二中继节点的第三标识和/或第一标识的映射关系。其中，第二终端标识用于宿主基站和/或核心网控制面节点在NG-C接口上识别中继节点。
可选地，该第二消息可以为承载在第一无线接口传输的NGAP消息，例如初始上下文配置请求(Initial Context Setup Request)，或者为RRC消息。
进一步可选地，上述NGAP消息可以承载在第一无线接口的DRB上，或者SRB上传输。
可选地，该第二消息可以为RRC消息。
S208，该第一中继节点在第二无线接口，向该第二中继节点发送RRC重配置消息。
可选地，该第一中继节点向该第二中继节点发送其他RRC消息(例如为RN定义的RRC消息)。
需要说明的是，除了上述第二中继节点的初始接入过程，第一中继节点还可以向宿主基站发送其他与第二中继节点相关的控制面消息，反方向亦然。与S205、S20z和S209中对第一消息的处理类似的，第一中继节点需要在第一无线接口向宿主基站发送与第二中继节点相关的控制面消息时，该消息的格式与上述第一消息类似，即示例性的，可以为NGAP消息或者RRC消息；宿主基站收到上述控制面消息后可以进一步进行处理后生成NGAP消息通过NG-C接口发送给核心网。
可选地，宿主基站基于第一无线接口上接收到的消息中的第一标识，识别出RN，并在对应的在NG-C接口上发送的NGAP消息中添加与该RN对应的RAN UE NGAP ID。宿主基站在NG-C接口接收上述NGAP消息的响应消息，生成对上述控制面消息的响应消息在第一无线接口发送给第一中继节点，该响应消息的格式与上述第二消息类似，即示例 性的，可以为NGAP消息或者RRC消息。
可选地，宿主基站基于NG-C接口上接收到的响应消息中的AMF UE NGAP ID和/或RAN UE NGAP ID，识别出RN，并在对应的在第一无线接口上发送的响应消息添加与该RN对应的第一标识。
类似的，核心网向宿主基站发送与第二中继节点相关的NGAP消息，触发宿主基站在第一无线接口发送与第二中继节点相关的控制面消息的格式与第二消息类似。
可选地，宿主基站基于NG-C接口上接收到的NGAP消息中的AMF UE NGAP ID和/或RAN UE NGAP ID，识别出RN，并在对应的在第一无线接口上发送的控制面消息中添加与该RN对应的第三标识。相应的，若第二中继节点需要对上述控制面消息进行响应，则上述响应消息的格式与第一消息类似；宿主基站基于在第一无线接口接收的控制面响应消息生成NG-C接口上的NGAP消息。
可选地，宿主基站基于第一无线接口上接收到的消息中的第一标识，识别出RN，并在对应的在NG-C接口上发送的NGAP消息中添加与该RN对应的RAN UE NGAP ID。
以上结合图4对两跳RN的入网流程进行了说明，下面将结合该第二中继节点、第一中继节点、网络设备以及核心网节点的控制面架构进行详细说明。
为了方便描述，以下将该第二中继节点记为RN2，该第一中继节点记为RN1，该网络设备记为宿主基站(Donor)，该核心网节点记为CN CP_RN。
图5示出了根据本申请实施例的L3协议栈控制面架构1-A的示意图。该L3协议栈控制面包括该第二中继节点(RN2)、该第一中继节点(RN1)、宿主基站(Donor)以及核心网节点(CN-CP_RN，为RN服务的核心网控制面功能)。其中，RN2为2跳RN，RN1为1跳RN。RN2与RN1通信的无线接口记为Un2，RN1与宿主基站通信的无线接口记为Un1，宿主基站与CN-CP_RN通信的地面接口记为NG-C。
(1)RN2的处理
Un2口：RN2与RN1通信的协议栈由上至下包括RRC层、PDCP层、RLC层、MAC层以及PHY层。此外在RRC层之上还有NAS层，该NAS层负责与核心网协商的相应流程，因此NAS消息通过RAN各跳节点(例如RN1和宿主基站)透传给CN-CP_RN，由CN-CP_RN进行解析和处理。PDCP层的功能包括传输用户数据/RRC消息、加密与解密、按序递交等。RLC层的功能包括传输上层协议数据单元(protocol data unit,PDU)、RLC重建、RLC SDU的级联/分段和重组(这个功能LTE有，但是未来演进的RAT可能取消该功能，或者把该功能移至其他协议层)等。MAC层的功能包括数据调度(例如不同UE的数据的优先级处理和调度、或者同一个UE不同逻辑信道(Logic Channel,LC)的优先级处理和数据的调度)、属于一个或多个LC的MAC SDU的复用/解复用等。PHY负责将上层数据通过无线资源传输出去。RRC消息承载在无线接口的SRB上，每个SRB有专属的PDCP实体、RLC实体、以及对应的MAC层逻辑信道。
(2)RN1的处理
Un2口：RN1与RN2通信的协议栈与RN2的协议栈对等，由上至下包括RRC层、PDCP层、RLC层、MAC层以及PHY层。各层功能与RN1类似。
可选地，对于上行UL，RN1解读在Un2口收到的RRC消息，进行处理(例如读取RRC信息内容)后，可能会触发生成相应NGAP消息，承载在Un1口的DRB发送给宿 主基站。若Un2口收到的RRC消息中包含NAS PDU，RN2将该NAS PDU封装在NGAP消息中，通过Un1口发送宿主基站。
可选地，对于下行DL，RN1生成发送给RN2的RRC消息，经过下层协议栈处理后，通过Un2口发送给RN2，若在Un1口收到的NGAP消息中包含NAS消息，则通过Un2口的RRC消息发送给RN2。
Un1口：RN1与宿主通信的协议栈由上至下包括NGAP层、SCTP层(可选地)、IP层(可选地)、业务数据自适应协议(Service data adaptation protocol，SDAP)层(可选地，即可以配置为透传)、PDCP层、RLC层、MAC层以及PHY层。
可选地，对于上行UL，生成的NGAP消息(可能包含NAS消息)，可选地，进一步经过SCTP层处理和/或IP层处理(可选地)，承载在DRB的数据包中通过Un1口发送给宿主基站。
可选地，对于下行DL，RN1在Un1口上接收宿主基站发送的数据包，，获取数据包中携带的NGAP消息，传递给上层NGAP协议层处理(可选地，其中经过SCTP层处理和/或IP层处理)。经过Un1口的NGAP协议层处理后，将处理后的NGAP消息内容(可能包含NAS消息)发送给Un2口的协议层。示例性的，将在Un1口收到的NGAP消息中携带的NAS消息发送给Un2口的RRC层。
一种可能的情况是：
在Un1口上的RN1的DRB可能承载以下几种数据中任一种或任意多种的组合：RN1的数据，RN1服务的UE的数据，RN2的数据，RN2服务的UE的数据，其他RN的数据，其他RN服务的UE的数据，RN1为其服务的UE生成的NGAP消息，RN1为其服务的UE封装的GTP-U数据包，RN2为其服务的UE生成的NGAP消息(该消息的部分内容可以经过RN1的改动和/或替换)，RN2为其服务的UE封装的GTP-U数据包(该消息的部分内容可以经过RN1的改动和/或替换)，其他RN为其服务的UE生成的NGAP消息(该消息的部分内容可以经过RN1的改动和/或替换)，其他RN为其服务的UE封装的GTP-U数据包(该消息的部分内容可以经过RN1的改动和/或替换)，RN1为其服务的UE生成的XnAP消息，RN2为其服务的UE生成的XnAP消息(该消息的部分内容可以经过RN1的改动和/或替换)，其他RN为其服务的UE生成的XnAP消息(该消息的部分内容可以经过RN1的改动和/或替换)，以及其他RN为其服务的UE封装的GTP-U数据包(该消息的部分内容可以经过RN1的改动和/或替换)。RN1/宿主基站在Un1上接收上述不同类型的数据后可能需要进行区分处理，因此需要能够识别上述不同类型的数据包，可以通过以下几种方式中的任一种或任意几种的组合来实现：
(a)为不同类型的数据包分配不同的DRB，通过DRB标识则可以区分数据类型；
(b)为不同类型的数据包分配不同的逻辑信道LC，通过LC标识即可区分数据类型；
(c)在数据包上添加第一自适应标识，用于区分Un1口上DRB中的数据类型。可选地，该第一自适应标识可以包含以下信息中的任一种或任意多种的组合：二跳RN标识和/或跳数信息(用于识别RN2)，第二UE标识(用于识别RN2服务的UE)，一跳RN标识和/或跳数信息(用于识别RN1)，第一UE标识(用于识别RN1服务的UE)，三跳RN标识和/或跳数信息(用于识别通过RN2和RN1传递数据的三跳、四跳乃至n跳的RN)，第三UE标识(用于识别多跳RN服务的UE)，NGAP消息类型，XnAP消息类型，GTP-U 消息类型(属于NG-U或Xn-U)，以及用户面数据包类型。
示例性的，为上行数据包添加自适应标识以及对下行数据包解析数据包标识的过程称为自适应功能。具体的，该自适应功能可以包含于现有的协议层，例如SDAP层/PDCP层/RLC层/MAC层/PHY层；或者自适应功能可以单独部署在一个协议层中，例如称为自适应(Adaptation，简称Adapt)层。
可选地，自适应层可以部署在NGAP层与PDCP层之间，或者部署在PDCP层与RLC层之间，或者部署在RLC层与MAC层之间，或者部署在MAC与PHY层之间。
(3)宿主基站的处理
Un1口：宿主基站与RN1通信的协议栈与RN1对等，由上至下包括NGAP层、SCTP层(可选地)、IP层(可选地)、SDAP层(可选地，即可以配置为透传)、PDCP层、RLC层、MAC层以及PHY层。需要说明的是，由于RN1与宿主基站用于在Un1口上通信的协议栈对等，因此，若需要呈现自适应功能，则呈现方式相同，参考RN1的描述。
可选地，对于上行UL，宿主基站在Un1口接收RN1发送的数据包，进行处理(例如通过自适应层功能获取数据包对应的DRB标识，或者LC标识，或者以下标识中的任一种或任意多种的组合：RN2标识，NGAP消息类型，以及RN2的跳数信息等。)后，获取其中的NGAP消息，传递给上层NGAP协议层处理(可选地，其中经过SCTP层处理和/或IP层处理)。将处理后的NGAP消息内容发送给NG-C接口的NGAP层。若Un1口收到的NGAP消息中包含NAS PDU，宿主基站将将该NAS PDU封装在NGAP消息中，通过NG-C接口发送给CN-CP_RN。
可选地，对于下行DL，宿主基站将发送给RN2的NGAP消息，进一步经过SCTP层处理和/或IP层处理(可选地)，经过自适应层处理(例如增加RN2标识、增加NGAP消息类型，或增加其他信息内容、以及进一步封装等)，携带在DRB数据包中，经过下层协议栈处理后，通过Un1口发送给RN1。
需要说明的是，在宿主基站内部可能需要在NG-C接口上收到的核心网发送的与RN2相关的NGAP消息(RN2 associated NGAP message)转换为在Un1无线接口上发送给RN1的NGAP消息；类似的，宿主基站将在Un1无线接口上收到的与RN2相关的NGAP消息转换为NG-C上的NGAP消息后发送给核心网。其中，宿主基站的处理可能和R10 Relay技术类似。
可选地，将NGAP消息的内容保持不变，将NGAP消息中识别该RN2的NGAP ID进行替换。示例性的，在Un1口上，RAN RN NGAP ID为RN1分配的，AMF UE NGAP ID为宿主基站分配的，当宿主基站在NG-C口上发送与该NGAP消息对应的消息时，将RAN UE NGAP ID替换为宿主基站为RN2分配的在NG-C接口上的NGAP标识，将AMF UE NGAP ID替换为AMF为该RN2在NG-C接口上分配的NGAP标识；类似的，宿主基站在NG-C口上接收到核心网发送的与该RN2对应的NGAP消息后，将其在Un1口上发送给RN1时，将AMF UE NGAP ID替换为宿主基站在Un1口上为该RN2分配的NGAP标识，将RAN UE NGAP ID替换为RN1在Un1口上为该RN2分配的NGAP标识。若Un1口的协议栈也包含SCTP层和IP层，则宿主基站也可以对IP地址，端口号等IP包头/SCTP包头上携带的内容进行替换处理。
另外，一种可能的情况是，RN1可以生成与RN2相关的XnAP消息(RN2 associated  XnAP message)，RN1在Un1口上向宿主基站发送或者接收宿主基站发送的XnAP消息，宿主基站在Xn-C接口上向其他基站发送或接收该与RN2相关的XnAP消息，或者宿主基站在其他无线接口上向其他RN发送或者接收其他RN发送的与该RN2相关的XnAP消息。宿主基站对该与RN2相关的XnAP消息的处理与对NGAP消息的处理类似，例如对UE XnAP ID的替换，以及可能的对IP地址，端口号等IP包头/SCTP包头上携带的内容进行替换处理。
应理解，在L3协议栈控制面架构1-A下，Un1口的第一消息和第二消息的形式是NGAP消息，该NGAP消息携带于承载在DRB上的数据包中。
图6示出了根据本申请实施例的L3协议栈控制面架构1-B的示意图。该L3协议栈控制面包括该第二中继节点(RN2)、该第一中继节点(RN1)、宿主基站(Donor)以及核心网节点(CN-CP_RN，为RN服务的核心网控制面功能)。其中，RN2为2跳RN，RN1为1跳RN。RN2与RN1通信的无线接口记为Un2，RN1与Donor通信的无线接口记为Un1，Donor与CN-CP_RN通信的地面接口记为NG，其控制面记为NG-C。
(1)RN2的处理
Un2口：RN2与RN1通信的协议栈由上至下包括RRC层、PDCP层、RLC层、MAC层以及PHY层。此外在RRC层之上还有NAS层，该NAS层负责与核心网协商的相应流程，因此NAS消息通过RAN各跳节点(例如RN1和宿主基站)透传给核心网节点CN-CP_RN，由CN-CP_RN解析和处理。
(2)RN1的处理
Un2口：RN1与RN2通信的协议栈与RN2的协议栈对等，由上至下包括RRC层、PDCP层、RLC层、MAC层以及PHY层。各层功能与RN1类似。
可选地，对于上行UL，RN1的RRC层解读在Un2口收到的RRC消息，进行处理(例如读取RRC信息内容)后，可能会触发生成相应NGAP消息，承载在Un1口的SRB发送给宿主基站。若Un2口收到的RRC消息中包含NAS PDU，RN2将该NAS PDU封装在NGAP消息中，通过Un1口发送宿主基站。
可选地，对于下行DL，RN1生成发送给RN2的RRC消息，经过下层协议栈处理后，通过Un2口发送给RN2，若在Un1口收到的NGAP消息中包含NAS消息，则通过Un2口的RRC消息发送给RN2。
Un1口：RN1与宿主通信的协议栈由上至下包括NGAP层、SCTP层(可选地)、IP层(可选地)、RRC层、PDCP层、RLC层、MAC层以及PHY层。其中，RRC层可能具有自适应功能；或者，该自适应功能可以包含于现有的协议层，例如PDCP层/RLC层/MAC层/PHY层；或者自适应功能部署在一个独立的协议层，该协议层的位置可以再RRC层与PDCP层之间，或者在PDCP与RLC层之间，或者在RLC层与MAC层之间，或者在MAC层与PHY层之间。由于PDCP层/RLC层/MAC层/PHY层是RAN控制面与用户面共有的协议层，因此，若自适应功能部署在这些协议层中，为控制面与用户面采用统一的自适应功能方案提供了可能。
可选地，对于上行UL，生成的NGAP消息(可能包含NAS消息)，经过SCTP层处理和/或IP层处理(可选地)，承载在RRC消息中通过Un1口发送给宿主基站。
可选地，对于下行DL，RN1在Un1口接收宿主基站发送的RRC消息，进行处理后， 获取其中的NGAP消息部分，传递给上层NGAP协议层处理(可选地，其中经过SCTP层处理和/或IP层处理)。经过Un1口的NGAP协议层处理后，将处理后的NGAP消息内容(可能包含NAS消息)发送给Un2口的NGAP层。
一种可能的情况是：
在Un1口上的RN1的SRB可能承载以下几种信息/消息中任一种或任意多种的组合：RN1的RRC消息，RN1为其服务的UE生成的NGAP消息，RN2为其服务的UE生成的NGAP消息(该消息的部分内容可以经过RN1的改动和/或替换)，其他RN为其服务的UE生成的NGAP消息(该消息的部分内容可以经过RN1的改动和/或替换)，RN1为其服务的UE生成的XnAP消息，RN2为其服务的UE生成的XnAP消息(该消息的部分内容可以经过RN1的改动和/或替换)，以及其他RN为其服务的UE生成的XnAP消息(该消息的部分内容可以经过RN1的改动和/或替换)。RN1/宿主基站在Un1上接收上述不同类型的RRC消息后可能需要进行区分处理，因此需要能够识别上述不同类型的RRC消息，可以通过以下几种方式中的任一种或任意几种的组合来实现：
(a)为不同类型的RRC消息分配不同的SRB，通过SRB标识则可以区分消息类型；
(b)为不同类型的RRC消息分配不同的逻辑信道LC，通过LC标识即可区分消息类型；
(c)在RRC消息上添加第二自适应标识，用于区分Un1口上SRB中的消息类型。
可选地，该第二自适应标识可以包含以下信息中的任一种或任意多种的组合：二跳RN标识和/或跳数信息(用于识别RN2)，第二UE标识(用于识别RN2服务的UE)，一跳RN标识和/或跳数信息(用于识别RN1)，第一UE标识(用于识别RN1服务的UE)，三跳RN标识和/或跳数信息(用于识别通过RN2和RN1传递数据的三跳、四跳乃至n跳的RN)，第三UE标识(用于识别三跳RN服务的UE)，NGAP消息类型，XnAP消息类型，以及RRC消息类型。
示例性的，为上行RRC消息添加自适应标识以及对下行RRC消息解析标识的过程称为自适应功能。具体的，该自适应功能可以包含于现有的协议层，例如RRC层/PDCP层/RLC层/MAC层/PHY层；或者自适应功能可以单独部署在一个协议层中，例如称为自适应(Adaptation，简称Adapt)层。
可选地，自适应层可以部署在NGAP层与RRC层之间，或者部署在RRC层与PDCP层之间，或者部署在PDCP层与RLC层之间，或者部署在RLC层与MAC层之间，或者部署在MAC与PHY层之间。
(3)宿主基站的处理
Un1口：宿主基站与RN1通信的协议栈与RN1对等，由上至下包括NGAP层、SCTP层(可选地)、IP层(可选地)、RRC层、PDCP层、RLC层、MAC层以及PHY层。需要说明的是，由于RN1与宿主基站用于在Un1口上通信的协议栈对等，因此，若需要呈现自适应功能，则呈现方式相同，参考RN1的描述。
可选地，对于上行UL，宿主基站在Un1口接收RN1发送的RRC消息，进行处理(例如获取RN2标识、获取RRC消息类型、获取SRB标识，或获取其他信息内容、以及进一步解封装等)后，获取其中的NGAP消息部分，传递给上层NGAP协议层处理(可选地，其中经过SCTP层处理和/或IP层处理)。将处理后的NGAP消息内容发送给NG-C 接口的NGAP层。若Un1口收到的NGAP消息中包含NAS PDU，宿主基站将该NAS PDU封装在NGAP消息中，通过NG-C接口发送给CN-CP_RN。
可选地，对于下行DL，宿主基站将发送给RN2的NGAP消息，进一步经过SCTP层处理和/或IP层处理(可选地)，携带在RRC消息经过RRC层处理(例如增加RN2标识、增加SRB标识、增加RRC消息类型，或增加其他信息内容、以及进一步封装等)，经过下层协议栈处理后，通过Un1口发送给RN1。
需要说明的是，在宿主基站内部可能需要在NG-C/Xn-C接口上收到的与RN2相关的NGAP/XnAP消息(RN2 associated NGAP/XnAP message)转换为在Un1无线接口上发送给RN1的NGAP/XnAP消息，宿主基站的处理与1-A架构下的处理类似，参考1-A架构的描述。
应理解，在L3协议栈控制面架构1-B下，Un1口的第一消息和第二消息的形式是携带在RRC消息中的NGAP消息。
图7示出了根据本申请实施例的L3协议栈控制面架构2的示意图。该L3协议栈控制面包括该第二中继节点(RN2)、该第一中继节点(RN1)、宿主基站(Donor)以及核心网节点(CN-CP_RN，为RN服务的核心网控制面功能)。其中，RN2为2跳RN，RN1为1跳RN。RN2与RN1通信的无线接口记为Un2，RN1与Donor通信的无线接口记为Un1，Donor与CN-CP_RN通信的地面接口记为NG-C。
(1)RN2的处理
Un2口：RN2与RN1通信的协议栈由上至下包括RRC层、PDCP层、RLC层、MAC层以及PHY层。此外在RRC层之上还有NAS层，该NAS层负责与核心网协商的相应流程，因此NAS消息通过RAN各跳节点(例如RN1和宿主基站)透传给为RN服务的核心网控制面节点CN-CP_RN，由CN-CP_RN解析和处理。RRC层的功能包括RRC连接控制、接收系统消息、移动性管理、NAS消息传输等。
(2)RN1的处理
Un2口：RN1与RN2通信的协议栈与RN2的协议栈对等，由上至下包括RRC层、PDCP层、RLC层、MAC层以及PHY层。各层功能与RN1类似。
可选地，对于上行UL，RN1的RRC层解读在Un2口收到的RRC消息，进行处理(例如提取出某些信息、或增加某些信息内容、或进一步封装)后传递给Un1口的协议栈处理。若Un2口收到的RRC消息中包含NAS PDU，RN1将该NAS PDU透传给RN2在Un1口的RRC层协议栈，由RN2在Un1口将该NAS PDU透传给宿主基站。
可选地，对于下行DL，RN1基于在Un1口接收的与RN2相关的(RN2 associated message)RRC消息，生成发送给RN2的RRC消息，发送给下层协议栈处理后通过Un2口发送给RN2。
Un1口：RN1与宿主通信的协议栈由上至下包括RRC层、PDCP层、RLC层、MAC层以及PHY层。其中，RRC层可能具有自适应层功能；或者，该自适应功能可以包含于现有的协议层，例如PDCP层/RLC层/MAC层/PHY层；或者自适应功能部署在一个独立的协议层，该协议层的位置可以再RRC层与PDCP层之间，或者在PDCP与RLC层之间，或者在RLC层与MAC层之间，或者在MAC层与PHY层之间。由于PDCP层/RLC层/MAC层/PHY层是RAN控制面与用户面共有的协议层，因此，若自适应功能部署在这些协议层 中，为控制面与用户面采用统一的自适应功能方案提供了可能。
可选地，对于上行UL，Un1口的RRC层协议栈接收Un2口协议栈传递来的RRC信息，进行处理(例如增加RN2标识、增加RRC消息类型、增加SRB标识，或增加其他信息内容、以及进一步封装等)后传递给下层协议栈。
可选地，对于下行DL，RN1在Un1口接收宿主基站发送的RRC消息，进行处理(例如获取RN2标识、获取RRC消息类型、获取SRB标识，或获取其他信息内容、以及进一步解封装等)后，传递给RN1在Un2口的协议栈。需要说明的是，RRC层的自适应层功能，可能包括增加/获取RN2标识、增加/获取RRC消息类型、增加/获取SRB标识，或增加/获取其他信息内容、以及进一步封装/解封装等。上述自适应层功能也可以通过定义一个独立于RRC层的单独的自适应层来实现。
一种可能的情况是：
在Un1口上的RN1的SRB可能承载以下几种信息中任一种或任意多种的组合：RN1的RRC消息，RN1服务的UE相关的RRC消息(RN1生成)，RN2相关的RRC消息(RN1生成)，RN2服务的UE相关的RRC消息(RN2生成，可能经过RN1的改动)数据，其他RN相关的RRC消息(RN1生成)，以及其他RN服务的UE相关的RRC消息(其他RN生成，可能经过RN1的改动)。RN1/宿主基站在Un1上接收上述不同类型的RRC消息后可能需要进行区分处理，因此需要能够识别上述不同类型的数据包，可以通过以下几种方式中的任一种或任意几种的组合来实现：
(a)为不同类型的RRC消息分配不同的SRB，通过SRB标识则可以区分消息类型；
(b)为不同类型的RRC消息分配不同的逻辑信道LC，通过LC标识即可区分消息类型；
(c)在RRC消息上添加第三自适应标识，用于区分Un1口RRC消息。
可选地，该第三自适应标识可以包含以下信息中的任一种或任意多种的组合：二跳RN标识和/或跳数信息(用于识别RN2)，第一UE标识(用于识别RN2服务的UE)，一跳RN标识和/或跳数信息(用于识别RN1)，第二UE标识(用于识别RN1服务的UE)，多跳RN标识和/或跳数信息(用于识别通过RN2和RN1传递数据的三跳、四条以及n跳的RN)，第三UE标识(用于识别多跳RN服务的UE)，以及RRC消息类型。示例性的，为上行RRC消息添加标识以及对下行RRC消息解析标识的过程称为自适应功能。具体的，该自适应功能可以包含于现有的协议层，例如RRC层/PDCP层/RLC层/MAC层/PHY层；或者自适应功能可以单独部署在一个协议层中，例如称为自适应(Adaptation，简称Adapt)层。可选地，自适应层可以部署在RRC层与PDCP层之间，或者部署在PDCP层与RLC层之间，或者部署在RLC层与MAC层之间，或者部署在MAC与PHY层之间。
(3)宿主基站的处理
Un1口：宿主基站与RN1通信的协议栈与RN1对等，由上至下包括RRC层、PDCP层、RLC层、MAC层以及PHY层。需要说明的是，由于RN1与宿主基站用于在Un1口上通信的协议栈对等，因此，若需要呈现自适应功能，则呈现方式相同，参考RN1的描述。
可选地，对于上行UL，宿主基站的RRC层协议栈接收RN1发来的RRC信息，进行处理(例如获取RN2标识、获取RRC消息类型、获取SRB标识，或获取其他信息内容、 以及进一步解封装等)后，可能触发生成相应的NGAP消息，通过NG-C接口发送给CN-CP_RN。若Un1口收到的RRC消息中包含NAS PDU，宿主基站将将该NAS PDU封装在NGAP消息中，通过NG-C接口发送给CN-CP_RN。
例如，对于下行DL，宿主基站将发送给RN2的RRC消息经过RRC层处理(例如增加RN2标识、增加SRB标识、增加RRC消息类型，或增加其他信息内容、以及进一步封装等)，经过下层协议栈处理后，通过Un1口发送给RN1。
应理解，在L3协议栈控制面架构2下，Un1口的第一消息和第二消息的形式是RRC消息。
图8示出了根据本申请实施例的三跳RN入网方法300的示意性流程图。如图8所示，该方法300包括：
S301，第三中继节点获取接入辅助信息，该接入辅助信息用于第三中继节点获取接入第二中继节点所需的信息，例如随机接入资源等。具体的，该接入辅助信息的内容参考S201中的描述。
S302，第三中继节点建立第三无线接口的控制面连接。其中，第三无线接口为第三中继节点与第二中继节点进行通信的无线接口。可选地，该控制面连接为RRC连接。具体的，该步骤与S202类似，在此不再赘述。
S3021，可选地，第三中继节点向第二中继节点发送第一个上行NAS消息(第二NAS消息)。
可选地，该第二NAS消息用于表示第三中继节点向核心网的注册请求。
可选地，该第二NAS消息可以携带在上述控制面连接建立的最后一条上行消息中，例如RRC连接建立完成消息。
S303，该第二中继节点向该第一中继节点发送第三消息，该第三消息是第二无线接口上上行第一个与该第三中继节点相关的消息(RN3 associated message)。该第三消息用于指示该第三中继节点接入网络。可选地，该第三消息携带该第三中继节点的第一个上行NAS消息。
可选地，该第三消息需要携带第三中继节点的第四标识，用于第二中继节点和/或第一中继节点在该第二无线接口上识别第三中继节点。
可选地，第四标识可以通过自适应功能添加(例如，第四标识存在于自适应层包头中)。
可选地，该第四标识可以包含以下信息中的任一种或任意多种的组合：RN2 RN/UE NGAP ID-Un2(第二中继节点为该标识对应的设备在第二无线接口上承载的NG连接分配的ID)，第二标识(其他形式的ID，可以用于识别该标识对应的设备)，SRB标识/DRB标识，逻辑信道标识，第二中继节点在第二无线接口为该标识对应的设备分配的标识)，以及第一中继节点在第二无线接口为该标识对应的设备分配的标识。第二标识的内容参见S205中的描述。
可选地，上述第四标识可能不区分是UE还是RN，即RN与UE使用相同的标识格式；或者，上述标识区分UE和RN，当设备为UE时，采用UE的标识格式，当设备为RN时，采用RN的标识格式；另外，如果套用现有的NGAP中UE ID，则RN2 RN/UE NGAP ID-Un2等同于RAN UE NGAP ID。
可选地，该第三消息可以为RRC消息，承载在第二无线接口(该第二中继节点)的 SRB上。
可选地，该第三消息可以为承载在第二无线接口上传输的NGAP消息，例如初始UE消息Initial UE message。可选地，上述NGAP消息可以承载在第二无线接口的DRB上，或者SRB上传输。
S304，第一中继节点在第二无线接口上收到第三消息后，一种可能的处理是：解析第三消息的部分信息或全部信息，获知第三中继节点(即一个新的RN)通过第二中继节点接入网络，该第一中继节点根据该第三消息，向网络设备发送第四消息，该第四消息用于指示该第三中继节点接入网络；另一种可能的处理时：不解析第三消息，将第三消息作为第四消息透传给网络设备，简称为透传情况。
可选地，该第四消息携带该第三中继节点的第一个上行NAS消息。
可选地，该第四消息需要携带第三中继节点的第一标识，用于第一中继节点和/或宿主基站在该第一无线接口上识别第三中继节点。
可选地，第一标识可以通过自适应功能添加(例如，第一标识存在于自适应层包头中)。
可选地，第一中继节点基于第三消息中的第四标识，识别第三中继节点，并为第三中继节点分配在第一无线接口上用于识别第三中继节点的第一标识。
可选地，第一中继节点保存第三中继节点的第四标识与第一标识的对应关系。第一标识的相关描述参见S205，在此不再赘述。示例性的，若第三消息为承载在第二无线接口中传输的NGAP消息，且其中携带的RN2 RN/UE NGAP ID-Un2为第二中继节点内唯一的标识，第一中继节点收到第三消息后，需要将其中的RN2 RN/UE NGAP ID-Un2替换为第一中继节点为第三中继节点分配的在第一无线接口上能够识别该第三中继节点的标识，例如RN1 RN/UE NGAP ID-Un1。第一中继节点保存第三中继节点的上述RN2 RN/UE NGAP ID-Un2与RN 1 RN/UE NGAP ID-Un1的映射关系。
需要说明的是，一种可能的情况是，第一标识携带的信息不能区分该标识对应的RN的跳数信息，宿主基站基于第一标识无法获知接入网络的中继节点是2跳RN(例如第二中继节点)，3跳RN(例如第三中继节点)，或者跳数大于3的RN，因此，如果宿主基站需要获知网络的拓扑情况(例如第三中继节点接入第二中继节点，进而通过第一中继节点传输信令和/或数据)，则需要第一中继节点发送第四消息的同时，进一步提示该第四消息也与第二中继节点有关。一种可能的方式是，在第四消息中进一步携带第二中继节点的第一标识；另一种可能的方式是，第一中继节点与宿主基站传输与第二中继节点有关的信息时，使用第二中继节点专用资源(例如专门为第二中继节点配置的第一无线接口的SRB/DRB和/或逻辑信道)，当宿主基站在该专用资源上收到第四消息，即可获知该第四消息指示接入的RN是通过第二中继节点接入的，而不是通过第一中继节点直接接入的。可选地，上述专用资源在第二中继节点接入第一中继节点后，由宿主基站配置给第一中继节点。
可选地，该第四消息为RRC消息，承载在该第一无线接口上(该第一中继节点)的的SRB上。
可选地，该第四消息为NGAP消息，例如，初始UE消息(Initial UE message)。
S305，宿主基站收到第四消息后，获知第三中继节点通过第二中继节点和/或第一中继节点接入网络，并生成相应的第三NGAP消息发送给为中继服务的核心网控制面节点。
可选地，该第四消息中携带第三中继节点向核心网发送的第一个上行NAS消息，宿主基站将该第三中继节点的第一个上行NAS消息发送给为中继服务的核心网控制面节点。
可选地，宿主基站基于第四消息中的第一标识/第三标识(透传情况，第四消息中不包含第一标识，包含第四标识)，识别第三中继节点，为第三中继节点分配NG-C接口上的第一终端标识，例如RAN UE NGAP ID。
可选地，宿主基站保存第三中继节点的第一标识/第四标识与第一终端标识的对应关系。
示例性的，该NGAP消息为该第三中继节点的初始UE消息(Initial UE message)。
示例性的，若第四消息为承载在第一无线接口中传输的NGAP消息，且携带的RN1RN/UE NGAP ID-Un1(透传情况下，第四消息不包含RN1 RN/UE NGAP ID-Un1，包含RN2 RN/UE NGAP ID-Un2)，宿主基站收到第四消息后，需要将其中的RN1 RN/UE NGAP ID-Un1/RN2 RN/UE NGAP ID-Un2替换为宿主基站为第三中继节点分配的在NG-C接口上能够识别该第三中继节点的第一终端标识，例如RAN RN NGAP ID。可选地，宿主基站保存第三中继节点的上述RN1 RN/UE NGAP ID-Un1/RN2 RN/UE NGAP ID-Un2与RAN RN/UE NGAP ID的映射关系。
宿主基站接收该核心网控制面节点的响应消息。
示例性的，该步骤具体包括步骤S3051-3052。
可选地S3051，核心网为该第三中继节点进行认证和安全配置。
S3052，若核心网通过该第三中继节点的注册，则需要通过第四NGAP消息回复该第三中继节点注册成功。
可选地，该第四NGAP消息可以为Attach Accept消息。
核心网通过该第四NGAP消息通知该网络设备为该第三中继节点建立必要的上下文。可选地，该第四NGAP消息中携带上述NAS消息。
示例性的，该第四NGAP消息为Initial Context Setup Request消息。
可选地，该第四NGAP消息中包含核心网控制面实体(例如AMF)为该第三中继节点分配的第二终端设备标识信息，例如AMF UE/RN NGAP ID，该第二终端设备标识信息用于在NG-C接口上识别该第三中继节点。
S306，该网络设备接收到来自核心网的该第四NGAP消息，并根据该第四NGAP消息生成第五消息发送给该第一中继节点。可选地，该第五消息中包括指示该第三中继节点注册成功的NAS信息。
可选地，该第五消息为RRC消息，承载在该第一无线接口上(该第一中继节点)的SRB上。
可选地，该第五消息为NGAP消息，例如初始上下文建立消息(Initial Context Setup)。
可选地，上述第五消息(NGAP消息)可以承载在DRB或者SRB上发送。
可选地，由于网络设备在NG-C上收到的响应消息中包含核心网控制面节点为第三中继节点分配的第二终端标识，例如AMF UE NGAP ID，当网络设备基于该响应消息在第一无线接口上发送第五消息时，网络设备在第五消息中携带第三中继节点的第三标识，用于网络设备在第一无线接口识别第三中继节点。
可选地，一种可能的处理是：第五消息中还携带第三中继节点的第一标识，用于第一中继节点识别第三中继节点；另一种可能的处理是：与S303中的透传情况相对应的，第一中继节点不解析该第五消息，将第五消息作为第六消息透传给网络设备，此时第五消息中还携带第三中继节点的第四标识，用于第二中继节点识别第三中继节点。各种标识的相关内容参加前面的描述，在此不再赘述。
可选地，网络设备基于上述NGAP消息生成第五消息时，将上述NGAP消息中的第二终端标识替换为第三中继节点的第三标识。
可选地，该网络设备保存第三中继节点的以下信息中的至少两种之间的关联关系：第二终端标识，第一终端标识，第三标识，第四标识，以及第一标识。。例如AMF UE NGAP ID、RAN UE NGAP ID、Donor RN/UE NGAP ID-Un1、RN1 RN/UE NGAP ID-Un1或RN2 RN/UE NGAP ID-Un2对应同一个中继节点(RN3)。
S307，该第一中继节点根据该第五消息，生成第六消息在第二无线接口上发送给该第二中继节点。一种可能的处理是：第一中继节点解析第五消息的部分信息或全部信息；另一种可能的处理时：不解析第五消息，将第五消息作为第六消息透传给第二中继节点，即透传情况。可选地，该第六消息包括核心网通知UE注册成功的NAS消息。
可选地，该第六消息为RRC消息，承载在该第二无线接口(Un2口)的SRB上。
可选地，该第六消息为NGAP消息，例如，Intial Context Setup Request消息。可选地，该第六消息承载在第二无线接口(Un2口)上该第二中继节点的SRB/DRB上，例如与第一消息采用相同的SRB/DRB。
可选地，第一中继节点在第一无线接口上收到的第五消息中包含第三中继节点的第三标识，例如Donor UE/RN NGAP ID-Un1，宿主基站基于该第五消息生成在第二无线接口上发送的第六消息时，需要在第六消息中携带第三中继节点的第五标识，用于在第二无线接口上识别该第三中继节点。
可选地，第五标识可以通过自适应功能添加(例如，第五标识存在于自适应层包头中)。
可选地，该第五标识可以包含以下信息中的任一种或任意多种的组合：RN1 RN/UE NGAP ID-Un2(第一中继节点为该标识对应的设备在第二无线接口上承载的NG连接分配的ID)，第二标识(其他形式的ID，可以用于识别该标识对应的设备)，SRB标识/DRB标识，逻辑信道标识，第二中继节点在第二无线接口为该标识对应的设备分配的标识)，以及第一中继节点在第二无线接口为该标识对应的设备分配的标识。
可选地，上述第四标识可能不区分是UE还是RN，即RN与UE使用相同的标识格式；或者，上述标识区分UE和RN，当设备为UE时，采用UE的标识格式，当设备为RN时，采用RN的标识格式；另外，如果套用现有的NGAP中UE ID，则RN1 RN/UE NGAP ID-Un2等同于AMF UE NGAP ID。
可以理解，第五标识可以与第四标识是同一个标识。此时，可选地，第六消息还携带第三中继节点的第四标识。
可选地，该第一中继节点存储第三中继节点的以下信息中的至少两种之间的关联关系：第一标识、第三标识、第四标识，以及第五标识。例如，Donor RN/UE NGAP ID-Un1、RN1 RN/UE NGAP ID-Un1、RN1 RN/UE NGAP ID-Un2、RN2 RN/UE NGAP ID-Un2对应同一个中继节点(RN3)。
S308，该第二中继节点接收该第六消息，该第六消息包括第三NAS消息。
可选地，第二中继节点将第六消息中携带的第二NAS消息发送给该第三中继节点，该第三NAS消息用于指示该第三中继节点在核心网注册结果。
可选地，上述第三NAS消息携带在RRCConnectionReconfiguration消息中发送。
可选地，该第二中继节点存储第三中继几点的以下信息中的至少两种之间的关联关系：第五标识，第四标识，以及该第二中继节点为该第三中继节点在第三接口分配的标识信息(例如C-RNTI-Un3口)。例如RN1 RN/UE NGAP ID-Un2、RN2 RN/UE NGAP ID-Un2、C-RNTI-Un3对应同一个中继节点(RN3)。
需要说明的是，除了上述第三中继节点的初始接入过程，第二中继节点还可以向第一中继节点发送其他与第三中继节点相关的控制面消息，反方向亦然。与本实施例中对第三消息的处理类似的，第二中继节点需要在第二无线接口向第一中继节点发送与第三中继节点相关的控制面消息时，该消息的格式与上述第三消息类似，即示例性的，可以为NGAP消息或者RRC消息；第一中继节点收到上述控制面消息后可以进一步进行处理后生成第一无线接口的控制面消息，该消息的格式与上述第四消息类似，即示例性的，可以为NGAP消息或者RRC消息，通过第一无线接口发送给网络设备。
可选地，第一中继节点基于第二无线接口上接收到的消息中的第四标识，识别出RN，并在对应的在第一无线接口上发送的控制面消息中添加与该RN对应的第一标识。类似的，宿主基站在第一无线接口向第一中继节点发送与第三中继节点相关的控制面消息，该消息的格式与第五消息类似，从而触发第一中继节点在第二无线接口向第二中继节点发送与第三中继节点相关的控制面消息，该消息的格式与第六消息类似。可选地，第一中继节点基于在第一无线接口上接收到的控制面消息中的第三标识，识别出RN，并在对应的在第二无线接口上发送的控制面消息中添加与该RN对应的第五标识。
需要说明的是，宿主基站为该网络设备的一种示例，为了方便描述，下面用宿主基站代替网络设备来进行实施方式的描述。
图9示出了根据本申请实施例的L3协议栈控制面架构1-A-A的示意图。该L3协议栈控制面包括该第三中继节点(RN3)、该第二中继节点(RN2)、该第一中继节点(RN1)、宿主基站(Donor)以及核心网节点(CN-CP_RN，为RN服务的核心网控制面功能)。其中，RN3为3跳RN，RN2为2跳RN，RN1为1跳RN。RN3与RN2通信的无线接口记为Un3，RN2与RN1通信的无线接口记为Un2，RN1与Donor通信的无线接口记为Un1，Donor与CN-CP_RN通信的地面接口记为NG-C。
图10示出了根据本申请实施例的L3协议栈控制面架构1-B-A的示意图。该L3协议栈控制面包括该第三中继节点(RN3)、该第二中继节点(RN2)、该第一中继节点(RN1)、宿主基站(Donor)以及核心网节点(CN-CP_RN，为RN服务的核心网控制面功能)。其中，RN3为3跳RN，RN2为2跳RN，RN1为1跳RN。RN3与RN2通信的无线接口记为Un3，RN2与RN1通信的无线接口记为Un2，RN1与Donor通信的无线接口记为Un1，Donor与CN-CP_RN通信的地面接口记为NG-C。
下面以图10所示的协议栈架构为例描述各个节点的行为。应理解，图9所示的协议栈架构中RN2的动作与图10所示的协议栈架构中RN2的动作类似，不同之处在于：图10所示的协议栈架构中RN2与RN1在Un2口上通信的协议栈包含RRC层，即在Un2口 上NGAP消息承载在SRB中；图9所示的协议栈架构中RN2与RN1在Un2口上通信的协议栈不包含RRC层，即在Un2口的NGAP消息承载在DRB中。两种协议栈架构中，RN1都需要有NGAP层，在NGAP层对收到的NGAP消息进行解析，再将新生成的NGAP消息通过Un1口发送出去。
(1)RN3的处理
在Un3口，RN3与RN2通信的协议栈由上至下包括RRC层、PDCP层、RLC层、MAC层以及PHY层。此外在RRC层之上还有NAS层，该NAS层负责与核心网协商的相应流程，因此NAS消息通过RAN各跳节点(例如RN2、RN1和宿主基站)透传给核心网节点CN-CP_RN，由CN-CP_RN解析和处理。
(2)RN2的处理
Un3口：RN2与RN3通信的协议栈与RN3的协议栈对等，由上至下包括RRC层、PDCP层、RLC层、MAC层以及PHY层。
可选地，对于上行UL，RN2解读在Un3口收到的RRC消息，进行处理(例如读取RRC信息内容)后，可能会触发生成相应NGAP消息，承载在Un2口的SRB发送给宿主基站，即将NGAP消息作为RRC消息的内容或内容的一部分。若Un3口收到的RRC消息中包含NAS PDU，RN2将该NAS PDU封装在NGAP消息中，通过Un2口发送给RN1。
可选地，对于下行DL，RN2生成发送给RN3的RRC消息，经过下层协议栈处理后，通过Un3口发送给RN3，若在Un2口收到的NGAP消息中包含NAS消息，则通过Un3口的RRC消息发送给RN3。
Un2口：RN2与RN1通信的协议栈由上至下包括NGAP层、SCTP层(可选地)、IP层(可选地)、RRC层(可选地，当不存在RRC层时，则协议栈1-B-A与1-A-A相同)、PDCP层、RLC层、MAC层以及PHY层。
可选地，对于上行UL，生成的NGAP消息(可能包含NAS消息)，进一步经过SCTP层处理和/或IP层处理(可选地)，后承载在RRC消息(当不存在RRC层时，则承载在DRB数据包)中通过Un2口发送给RN1。可选地，上述NGAP消息经过自适应功能的处理，例如包括增加RN3标识、增加RN2标识、增加RRC消息类型、增加SRB标识、增加NGAP消息类型、或增加其他信息内容等后传递给下层协议栈。
可选地，对于下行DL，RN2在Un2口上接收RN1发送的RRC消息(当不存在RRC层时，则接收DRB数据包)，进行处理(例如获取RN2标识、获取RN3标识、获取RRC消息类型、获取NGAP消息类型、获取SRB标识，或获取其他信息内容等)后，获取其中的NGAP消息部分，传递给上层NGAP协议层处理(可选地，其中经过SCTP层处理和/或IP层处理)。经过Un2口的NGAP协议层处理后，将处理后的NGAP消息内容(可能包含NAS消息)发送给Un3口的协议层。示例性的，将在Un2口收到的NGAP消息中携带的NAS消息发送给Un3口的RRC层。
一种可能的情况是：
在Un2口上的RN2的SRB可能承载以下几种信息/消息中任一种或任意多种的组合：RN2的RRC消息，RN2为其服务的UE生成的NGAP消息，RN3为其服务的UE生成的NGAP消息(该消息的部分内容可以经过RN2的改动和/或替换)，其他RN为其服务的UE生成的NGAP消息(该消息的部分内容可以经过RN2的改动和/或替换)，RN2为其 服务的UE生成的XnAP消息，RN3为其服务的UE生成的XnAP消息(该消息的部分内容可以经过RN2的改动和/或替换)，以及其他RN为其服务的UE生成的XnAP消息(该消息的部分内容可以经过RN1的改动和/或替换)。RN2/RN1在Un2上接收上述不同类型的RRC消息后可能需要进行区分处理，因此需要能够识别上述不同类型的RRC消息，可以通过以下几种方式中的任一种或任意几种的组合来实现：
(a)为不同类型的RRC消息分配不同的SRB，通过SRB标识则可以区分消息类型；
(b)为不同类型的RRC消息分配不同的逻辑信道LC，通过LC标识即可区分消息类型；
(c)在RRC消息上添加第四自适应标识，用于区分Un2口上SRB中的消息类型。可选地，该第四自适应标识可以包含以下信息中的任一种或任意多种的组合：三跳RN标识和/或跳数信息(用于识别RN3)，第三UE标识(用于识别RN3服务的UE)，二跳RN标识和/或跳数信息(用于识别RN2)，第二UE标识(用于识别RN2服务的UE)，多跳RN标识和/或跳数信息(用于识别通过RN3和RN2传递数据的四跳乃至n跳的RN)，第四UE标识(用于识别四跳乃至n跳RN服务的UE)，NGAP消息类型，XnAP消息类型，以及RRC消息类型。
示例性的，为上行RRC消息添加自适应标识以及对下行RRC消息解析标识的过程称为自适应功能。具体的，该自适应功能可以包含于现有的协议层，例如RRC层/PDCP层/RLC层/MAC层/PHY层；或者自适应功能可以单独部署在一个协议层中，例如称为自适应(Adaptation，简称Adapt)层。
可选地，自适应层可以部署在NGAP层与RRC层之间，或者部署在RRC层与PDCP层之间，或者部署在PDCP层与RLC层之间，或者部署在RLC层与MAC层之间，或者部署在MAC与PHY层之间。
当不存在RRC层协议栈时，一种可能的情况是：
在Un2口上的RN2的DRB可能承载以下几种数据中任一种或任意多种的组合：RN2的数据，RN2服务的UE的数据，RN3的数据，RN3服务的UE的数据，其他RN的数据，其他RN服务的UE的数据，RN2为其服务的UE生成的NGAP消息，RN2为其服务的UE封装的GTP-U数据包，RN3为其服务的UE生成的NGAP消息(该消息的部分内容可以经过RN2的改动和/或替换)，RN3为其服务的UE封装的GTP-U数据包(该消息的部分内容可以经过RN2的改动和/或替换)，其他RN为其服务的UE生成的NGAP消息(该消息的部分内容可以经过RN2的改动和/或替换)，其他RN为其服务的UE封装的GTP-U数据包(该消息的部分内容可以经过RN2的改动和/或替换)，RN2为其服务的UE生成的XnAP消息，RN3为其服务的UE生成的XnAP消息(该消息的部分内容可以经过RN3的改动和/或替换)，其他RN为其服务的UE生成的XnAP消息(该消息的部分内容可以经过RN3的改动和/或替换)，以及其他RN为其服务的UE封装的GTP-U数据包(该消息的部分内容可以经过RN3的改动和/或替换)。RN2/RN1在Un2上接收上述不同类型的数据后可能需要进行区分处理，因此需要能够识别上述不同类型的数据包，可以通过以下几种方式中的任一种或任意几种的组合来实现：
(a)为不同类型的数据包分配不同的DRB，通过DRB标识则可以区分数据类型；
(b)为不同类型的数据包分配不同的逻辑信道LC，通过LC标识即可区分数据类型；
(c)在数据包上添加第五自适应标识，用于区分Un2口DRB中的数据类型。可选地，该第五自适应标识可以包含以下信息中的任一种或任意多种的组合：三跳RN标识和/或跳数信息(用于识别RN3)，第三UE标识(用于识别RN3服务的UE)，二跳RN标识和/或跳数信息(用于识别RN2)，第二UE标识(用于识别RN2服务的UE)，多跳RN标识和/或跳数信息(用于识别通过RN3和RN2传递数据的四跳乃至n跳的RN)，第四UE标识(用于识别多跳RN服务的UE)，NGAP消息类型，XnAP消息类型，GTP-U消息类型(属于NG-U或Xn-U)，以及用户面数据包类型。
示例性的，为上行数据包添加自适应标识以及对下行数据包解析数据包标识的过程称为自适应功能。具体的，该自适应功能可以包含于现有的协议层，例如SDAP层/PDCP层/RLC层/MAC层/PHY层；或者自适应功能可以单独部署在一个协议层中，例如称为自适应(Adaptation，简称Adapt)层。可选地，自适应层可以部署在NGAP层与PDCP层之间，或者部署在PDCP层与RLC层之间，或者部署在RLC层与MAC层之间，或者部署在MAC与PHY层之间。
(3)RN1的处理
Un2口：RN1与RN2通信的协议栈与RN2的协议栈对等，由上至下包括NGAP、SCTP(可选地)、IP(可选地)、RRC层(可选地)、PDCP层、RLC层、MAC层以及PHY层。各层功能与RN2类似。
可选地，对于上行UL，RN1的RRC层解读在Un2口收到的RRC消息，进行处理(例如读取RRC信息内容，获取RN3标识、获取消息类型)后，将其中的NGAP消息提取出来，发送给上层NGAP层，进而生成Un1口的NGAP消息。
可选地，对于下行DL，基于Un1口收到的NGAP消息，生成在Un2口上发送给RN2的NGAP消息(例如将Un1口的RN3的NGAP ID映射为Un2口的RN3的NGAP ID)，经过RRC层处理后(例如包括增加RN3、增加RN2标识、增加RRC消息类型、增加SRB标识、增加NGAP消息类型、或增加其他信息内容、以及进一步封装等)，经过下层协议栈处理后，通过Un2口的SRB发送给RN2。
Un1口：RN1与宿主通信的协议栈由上至下包括NGAP、SCTP(可选地)、IP(可选地)、RRC层(可选地)、PDCP层、RLC层、MAC层以及PHY层。需要说明的是，RRC层为可选地含义为：如果有RRC层，则NGAP消息承载在Un1口的SRB上，此时与协议栈1-B中的Un1口相同；如果没有RRC层，则NGAP消息承载在Un1口的DRB上，此时与协议栈1-A中的Un1口相同。RN1的行为与协议栈1-B或协议栈1-A中Un1口上RN1的行为类似，例如在Un1口上对各种数据类型进行区分的方法，以及自适应功能的部署方式等，参考上述两种协议栈中对RN1行为的描述。此处仅描述简单的数据包处理流程。
可选地，对于上行UL，将Un2口收到的NGAP消息(可能包含NAS消息)，经过处理后生成NGAP消息(例如将Un2口的RN3的NGAP ID映射为Un1口的RN3的NGAP ID)，进一步送到下层协议栈，可选地经过处理后(例如包括增加RN3、增加RN2标识、增加RRC消息类型、增加SRB标识、增加NGAP消息类型、或增加其他信息内容、以及进一步封装等)后通过Un1口发送给宿主基站。
可选地，对于下行DL，RN1在Un1口接收宿主基站发送的承载的NGAP消息，经过 处理(例如获取RN1标识、获取RN2标识、获取RN3标识、获取RRC消息类型、获取NGAP消息类型、获取SRB标识，或获取其他信息内容、以及进一步解封装等)后，获取其中的NGAP消息部分，传递给上层的NGAP层，经过处理(例如将Un1口的RN3的NGAP ID映射为Un2口的RN3的NGAP ID)，生成在Un2口发送的NGAP消息。
(4)宿主基站的处理
在Un1口，宿主基站的协议栈与RN1对等，由上至下包括NGAP层、SCTP层(可选地)、IP层(可选地)、RRC层(可选地)、PDCP层、RLC层、MAC层以及PHY层。与RN1对应的，宿主基站的详细的行为参考1-A和1-B中的描述，此处仅简单描述数据包的处理过程。
可选地，对于上行UL，宿主基站在Un1口接收RN1发送的RRC消息或DRB数据包，进行处理(例如获取RN2标识、获取RN3标识、获取RRC消息类型、获取SRB标识，获取NGAP消息类型、或获取其他信息内容等)后，获取其中的NGAP消息部分，传递给上层NGAP协议层处理(可选地，其中经过SCTP层处理和/或IP层处理)。将处理后的NGAP消息内容发送给NG-C接口的NGAP层(例如将Un1口的RN3的NGAP ID映射为NG-C口的RN3的NGAP ID)。若Un1口收到的NGAP消息中包含NAS PDU，宿主基站将将该NAS PDU封装在NGAP消息中，通过NG-C接口发送给CN-CP_RN。
可选地，对于下行DL，宿主基站将发送给RN3的NGAP消息，进一步经过SCTP层处理和/或IP层处理(可选地)，经过处理后携带在RRC消息或DRB数据包中(例如增加RN2标识、增加RN3标识、增加NGAP消息类型、增加SRB标识、增加RRC消息类型，或增加其他信息内容、以及进一步封装等)，经过下层协议栈处理后，通过Un1口发送给RN1。
图11示出了根据本申请实施例的L3协议栈控制面架构2的另一示意图。该L3协议栈控制面包括该第三中继节点(RN3)、该第二中继节点(RN2)、该第一中继节点(RN1)、宿主基站(Donor)以及核心网节点(CN-CP_RN，为RN服务的核心网控制面功能)。其中，RN3为3跳RN，RN2为2跳RN，RN1为1跳RN。RN3与RN2通信的无线接口记为Un3，RN2与RN1通信的无线接口记为Un2，RN1与Donor通信的无线接口记为Un1，Donor与CN-CP_RN通信的地面接口记为NG-C。
应理解，图11中RN2的动作与图7中协议栈架构2中RN1的动作类似，为了简洁，在此不再赘述。
图12示出了根据本申请实施例的L3协议栈控制面架构1-A-B的示意图。该L3协议栈控制面包括该第三中继节点(RN3)、该第二中继节点(RN2)、该第一中继节点(RN1)、宿主基站(Donor)以及核心网节点(CN-CP_RN，为RN服务的核心网控制面功能)。其中，RN3为3跳RN，RN2为2跳RN，RN1为1跳RN。RN3与RN2通信的无线接口记为Un3，RN2与RN1通信的无线接口记为Un2，RN1与Donor通信的无线接口记为Un1，Donor与CN-CP_RN通信的地面接口记为NG-C。
应理解，该L3协议栈控制面架构1-A-B中RN1不解析RN2发送的NGAP消息内容，即不区分承载该NGAP消息的DRB中的数据类型，将Un2口的RN2的该DRB的PDCP SDU承载在Un1口上RN1的DRB上发送给宿主基站。
图13示出了根据本申请实施例的L3协议栈控制面架构1-B-B的示意图。该L3协议 栈控制面包括该第三中继节点(RN3)、该第二中继节点(RN2)、该第一中继节点(RN1)、宿主基站(Donor)以及核心网节点(CN-CP_RN，为RN服务的核心网控制面功能)。其中，RN3为3跳RN，RN2为2跳RN，RN1为1跳RN。RN3与RN2通信的无线接口记为Un3，RN2与RN1通信的无线接口记为Un2，RN1与Donor通信的无线接口记为Un1，Donor与CN-CP_RN通信的地面接口记为NG-C。
应理解，该L3协议栈控制面架构1-B-B中，RN2的RRC消息与RN2生成的NGAP消息承载在不同的SRB/LC上，RN1不解析RN2发送的NGAP消息，将承载该NGAP消息的SRB/LC上的RRC消息内容承载在Un1口上的RN1的SRB或者DRB上发送给宿主基站。
(1)RN3的处理
Un3口：RN3与RN2通信的协议栈由上至下包括RRC层、PDCP层、RLC层、MAC层以及PHY层。此外在RRC层之上还有NAS层，该NAS层负责与核心网协商的相应流程，因此NAS消息通过RAN各跳节点(例如RN2、RN1和宿主基站)透传给核心网节点CN-CP_RN，由CN-CP_RN解析和处理。
(2)RN2的处理
Un3口：RN2与RN3通信的协议栈与RN3的协议栈对等，由上至下包括RRC层、PDCP层、RLC层、MAC层以及PHY层。各层功能与RN3类似。
可选地，对于上行UL，RN2解读在Un3口收到的RRC消息，进行处理(例如读取RRC信息内容)后，可能会触发生成相应NGAP消息，承载在Un2口的SRB发送给宿主基站，即将NGAP消息作为RRC消息的内容或内容的一部分。若Un3口收到的RRC消息中包含NAS PDU，RN2将该NAS PDU封装在NGAP消息中，通过Un2口发送给RN1。
可选地，对于下行DL，RN2生成发送给RN3的RRC消息，经过下层协议栈处理后，通过Un3口发送给RN3，若在Un2口收到的NGAP消息中包含NAS消息，则通过Un3口的RRC消息发送给RN3。
Un2口：RN2与RN1通信的协议栈由上至下包括RRC层(可选地，当不存在RRC层时，则协议栈1-B-B与1-A-B相同)、PDCP层、RLC层、MAC层以及PHY层。需要说明的是，上述协议层与RN1是对等的，在这些协议层之上，还有与宿主基站对等的NGAP层、SCTP层(可选地)、IP层(可选地)。RN2在Un2口的行为与图10所示的协议栈架构中RN2在Un2口的行为类似，参考图10中的具体描述，例如在Un2口上进行数据类型的区分的方法和自适应功能的部署方式，此处仅对简单的数据包处理流程进行描述。
可选地，对于上行UL，生成的NGAP消息(可能包含NAS消息)，进一步经过SCTP层处理和/或IP层处理(可选地)，后承载在RRC消息(当不存在RRC层时，则承载在DRB数据包)中通过Un2口发送给RN1。可选地，上述NGAP消息经过自适应功能的处理，例如包括增加RN3标识、增加RN2标识、增加RRC消息类型、增加SRB标识、增加NGAP消息类型、或增加其他信息内容等后传递给下层协议栈。
可选地，对于下行DL，RN2在Un2口接收RN1发送的RRC消息(当不存在RRC层时，则接收DRB数据包)，进行处理(例如获取RN2标识、获取RN3标识、获取RRC消息类型、获取NGAP消息类型、获取SRB标识，或获取其他信息内容等)后，获取其中的NGAP消息部分，传递给上层NGAP协议层处理(可选地，其中经过SCTP层处理 和/或IP层处理)。经过Un2口的NGAP协议层处理后，将处理后的NGAP消息内容(可能包含NAS消息)发送给Un3口的协议层。示例性的，将在Un2口收到的NGAP消息中携带的NAS消息发送给Un3口的RRC层。
(3)RN1的处理：无需解析NGAP消息内容，直接将NGAP消息转发给上一节点或者下一节点。
Un2口：RN1与RN2通信的协议栈从RRC开始与RN2的协议栈对等，由上至下包括RRC层(可选地)、PDCP层、RLC层、MAC层以及PHY层。各层功能与RN2类似。
可选地，对于上行UL，
对于存在RRC层的协议栈架构，RN1接收承载在Un2口上的SRB的RRC消息，进行处理(例如获取RN3标识、获取消息类型)后，将其中的NGAP消息提取出来，通过Un1口发送给宿主基站。
可选地，RN1通过上述RRC消息所在的SRB标识或者逻辑信道标识区分上述RRC消息是否为RN2的RRC消息。若是则递交给Un2口上的RRC层进行解析；若否则不递交给Un2口的RRC层，直接转发给Un1口的协议栈。
可选地，上述NGAP消息可以承载在Un1口的SRB或者DRB上发送给宿主基站。
对于不存在RRC层的协议栈架构，RN1接收承载在Un2口的DRB数据包，进行处理(例如获取RN3标识、获取消息类型)后，将其中的NGAP消息提取出来，通过Un1口发送给宿主基站。
可选地，RN1通过上述数据包所在的DRB标识或者逻辑信道标识区分上述数据包为RN2为RN3生成的NGAP消息，将数据包的PDCP SDU直接转发给Un1口的协议栈。
可选地，上述NGAP消息可以承载在Un1口的SRB或者DRB上发送给宿主基站。
可选地，对于向DL，基于Un1口收到的RRC消息/DRB数据包，生成发送给RN2的RRC消息/DRB数据包，经过处理后(例如包括增加RN3、增加RN2标识、增加RRC消息类型、增加SRB标识、增加NGAP消息类型、或增加其他信息内容等)，经过下层协议栈处理后，通过Un2口发送给RN2。
Un1口：RN1与宿主通信的协议栈由上至下包括RRC层(可选地)、PDCP层、RLC层、MAC层以及PHY层。需要说明的是，RRC层为可选地含义为：如果有RRC层，则NGAP消息承载在Un1口的SRB上，此时与协议栈1-B中的Un1口相同；如果没有RRC层，则NGAP消息承载在Un1口的DRB上，此时与协议栈1-A中的Un1口相同。RN1的行为与协议栈1-B或协议栈1-A中Un1口上RN1的行为类似，例如在Un1口上对各种数据类型进行区分的方法，以及自适应功能的部署方式等，参考上述两种协议栈中对RN1行为的描述，与上述两种协议栈不同的是，RN1无需解读。此处仅描述简单的数据包处理流程。
可选地，对于上行UL，将Un2口收到的NGAP消息(可能包含NAS消息)，经过RRC层处理后(例如包括增加RN3、增加RN2标识、增加RRC消息类型、增加SRB标识、增加NGAP消息类型、或增加其他信息内容、以及进一步封装等)后承载在RRC消息中通过Un1口发送给宿主基站。
可选地，对于下行DL，RN1在Un1口接收宿主基站发送的RRC消息，进行处理(例如获取RN1标识、获取RN2标识、获取RN3标识、获取RRC消息类型、获取NGAP消 息类型、获取SRB标识，或获取其他信息内容、以及进一步解封装等)后，获取其中的NGAP消息部分，传递给Un2口的RRC层处理。
(4)宿主基站的处理
在Un1口，宿主基站RRC层以下的协议栈与RN1对等，RRC层以上的NGAP层与RN2对等，由上至下包括NGAP层、SCTP层(可选地)、IP层(可选地)、RRC层、PDCP层、RLC层、MAC层以及PHY层。其中，RRC层可能具有自适应层功能。
例如，对于UL，宿主基站在Un1口接收RN1发送的RRC消息，进行处理(例如获取RN2标识、获取RN3标识、获取RRC消息类型、获取SRB标识，获取NGAP消息类型、或获取其他信息内容、以及进一步解封装等)后，获取其中的NGAP消息部分，传递给上层NGAP协议层处理(可选地，其中经过SCTP层处理和/或IP层处理)。将处理后的NGAP消息内容发送给NG-C接口的NGAP层。若Un1口收到的NGAP消息中包含NAS PDU，宿主基站将将该NAS PDU封装在NGAP消息中，通过NG-C接口发送给CN-CP_RN。
例如，对于下行DL，宿主基站将发送给RN3的NGAP消息，进一步经过SCTP层处理和/或IP层处理(可选地)，携带在RRC消息经过RRC层处理(例如增加RN2标识、增加RN3标识、增加NGAP消息类型、增加SRB标识、增加RRC消息类型，或增加其他信息内容、以及进一步封装等)，经过下层协议栈处理后，通过Un1口发送给RN1。
终端设备通过两跳RN入网方法与方法300类似，不同点在于：
(1)终端设备与该第二中继节点通信的第三接口为Uu口，该第三中继节点与该第二中继节点通信的是Un3口。Uu口和Un3口的无线接口机制可能不同。
应理解，所述不同的无线接口机制是指物理层传输技术不同或者部分不同；或者，物理层传输技术相同但是物理层以上协议栈不同；或者，协议栈结构和协议层功能大部分相同，使用的无线传输资源不同。本申请实施例中可见，Uu与Un3协议栈相同，物理层传输技术以及使用的无线传输资源可能不同；
(2)需要在各节点的自适应层增加UE标识，用于网络设备能够识别出这是一个终端设备相关的控制面消息，从而为该终端设备发送NGAP消息给核心网节点时，将该NGAP消息路由至为该终端设备服务的核心网节点(CN-CP for UE)。
图14示出了根据本申请实施例的L3协议栈控制面架构1-A-A的另一示意图，应理解，图14对应于图9，不同之处在于，UE通过两跳RN入网，为了简洁，在此不再赘述。
图15示出了根据本申请实施例的L3协议栈控制面架构1-B-A的另一示意图，应理解，图15对应于图10，不同之处在于，UE通过两跳RN入网，为了简洁，在此不再赘述。
图16示出了根据本申请实施例的L3协议栈控制面架构2的再一示意图，应理解，图16对应于图11，不同之处在于，UE通过两跳RN入网，为了简洁，在此不再赘述。
图17示出了根据本申请实施例的L3协议栈控制面架构1-A-B的另一示意图，应理解，图17对应于图12，不同之处在于，UE通过两跳RN入网，为了简洁，在此不再赘述。
图18示出了根据本申请实施例的L3协议栈控制面架构1-B-B的另一示意图，应理解，图18对应于图13，不同之处在于，UE通过两跳RN入网，为了简洁，在此不再赘述。
上面结合图3至图18，介绍了两跳和三跳RN或者终端设备的入网流程以及控制面协议栈架构，下面结合图19至图30，介绍用户面的数据传输过程以及数据面的协议栈架构。
图19示出了根据本申请实施例的传输方法400的示意性流程图，如图19所示，该方法400包括：
S410，第一中继节点确定第一映射关系，所述第一映射关系用于确定第一数据包的属性信息与发送所述第一数据包使用的无线承载之间的对应关系；第一中继节点通过第一无线接口与网络设备通信；第一中继节点通过第二无线接口与第一设备通信。其中，示例性的，网络设备可以为宿主基站或者RN；第一设备可以为UE或者RN(例如第二中继节点)。
可选地，当第一设备为第二中继节点时，该第一数据包是属于某个第二中继节点服务的终端设备的数据包，此时，终端设备的信息可以包含该终端设备的标识；或者该第一数据包属于某个多跳RN服务的终端设备的数据包，此时终端设备的信息可以包含该终端设备的标识，以及每一个终端设备与第二中继节点之间为该终端设备转发数据包的多跳RN的标识信息。
可选地，该第一数据包的属性信息可能包含以下信息中的任一种或多种的组合：第一设备的信息，终端设备的信息，会话连接信息，数据流信息，该数据包在第二无线接口传输时所在的数据无线承载的信息，该第一数据包在第二无线接口传输时所用的逻辑信道的信息，该第一数据包在第一无线接口传输时所在的数据无线承载的信息，该第一数据包在第一无线接口传输时所用的逻辑信道的信息。其中，终端设备的信息用于识别该第一数据包所属的第二中继节点服务的终端设备。示例性的，会话连接为协议数据单元会话或分包数据单元会话(protocal/packet data unit session,PDU session)或PDU session resource。示例性的，数据流为服务质量流(quality of service flow,QoS flow)。可理解，无线承载的信息和/或逻辑信道的信息包含了该无线承载的信息和/或逻辑信道在传输的无线接口上所属的节点的信息，即通过无线承载的信息和/或逻辑信道的信息可以在传输的无线接口上识别其所属的节点。示例性地，无线承载包含数据无线承载和信令无线承载，无线承载的信息包含无线承载的标识。
可选地，第一映射关系包括第一上行映射关系和/或第一下行映射关系。
其中，第一上行映射关系可以为以下方式的任意一种：
(1)第一数据包的会话连接信息和/或数据流信息，与在第一无线接口发送该第一数据包使用的数据无线承载的信息和/或逻辑信道的信息之间的对应关系；
(2)在第二无线接口接收该第一数据包使用的数据无线承载的信息和/或逻辑信道的信息，与在第一无线接口发送该第一数据包使用的数据无线承载的信息和/或逻辑信道的信息之间的对应关系；
(3)在第二无线接口接收该第一数据包使用的数据无线承载的信息和/或逻辑信道的信息，以及第一数据包所属的第一设备和/或终端设备的信息，与在第一无线接口发送该第一数据包使用的数据无线承载的信息和/或逻辑信道的信息之间的对应关系。
其中，方式(1)的粒度最细，可以为一个UE/RN的一个PDU session内的QFI到DRB的映射；方式2的粒度最粗，为第二无线接口的DRB到第一无线接口的DRB的映射；方式(3)为前两种方式的折中，在方式(2)的基础上增加了UE/RN的维度，即第二无线接口的DRB中属于某个UE/RN的数据到第一无线接口的DRB的映射。
第一下行映射关系的候选方式与上行类似，可以为以下方式的任意一种：
(1)第一数据包的会话连接信息和/或数据流信息，与在第二无线接口发送该第一数 据包使用的无线承载的信息和/或逻辑信道的信息之间的对应关系；
(2)在第一无线接口接收该第一数据包使用的无线承载的信息和/或逻辑信道的信息，与在第二无线接口发送该第一数据包使用的无线承载的信息和/或逻辑信道的信息之间的对应关系；
(3)在第一无线接口接收该第一数据包使用的数据无线承载的信息和/或逻辑信道的信息，以及第一数据包所属的第一设备和/或终端设备的信息，与在第二无线接口发送该第一数据包使用的无线承载的信息和/或逻辑信道的信息之间的对应关系。
可选地，第一中继节点获取上述第一映射关系的方式可以为以下方式中的任一种或任意多种的组合：
(1)从宿主基站发送的配置信息中获取；
(2)从OAM发送的配置信息中获取；
(3)从第一数据包中携带的信息中获取；
(4)通过第一数据包的下行发送方式获取第一上行映射关系；
(5)第一中继节点自行决定；
(6)从网络设备发送的配置信息中获取。
其中，可选地，方式(3)中，从第一数据包中携带的信息中获取，具体包括获取第一下行映射关系。示例性的，第一中继节点在第一无线接口接收第一数据包，获取第一数据包中携带的以下信息中的任一种或任意多种的组合：会话连接信息，数据流信息，在第二无线接口发送该第一数据包使用的无线承载的信息和/或逻辑信道的信息，第一设备的信息，以及终端设备的信息；从而获取第一下行映射关系。可选地，方式(3)中还包括获取第一上行映射关系。示例性的，第一中继节点在第二无线接口接收第一数据包，获取第一数据包中携带的以下信息中的任一种或任意多种的组合：会话连接信息，数据流信息，在第一无线接口发送该第一数据包使用的数据无线承载的信息和/或逻辑信道的信息，第一设备的信息，以及终端设备的信息；从而获取第一上行映射关系。
可选地，方式(4)中，通过第一数据包的下行发送方式获取第一上行映射关系，具体包括，第一中继节点获取第一数据包的以下信息中的任一种或任意多种的组合：会话连接信息，数据流信息，在第二无线接口发送该第一数据包使用的无线承载的信息和/或逻辑信道的信息，在第一无线接口发送该第一数据包使用的无线承载的信息和/或逻辑信道的信息，以及第一数据包所属的第一设备和/或终端设备的信息；从而获取以下映射关系中的任一种，作为第一上行映射关系：会话连接信息和/或数据流信息与第一无线接口的无线承载和/或逻辑信道的信息的对应关系，第一无线接口的无线承载和/或逻辑信道的信息与第二无线接口的无线承载和/或逻辑信道的信息的对应关系，第一无线接口的无线承载和/或逻辑信道的信息以及第一设备和/或终端设备的信息与第二无线接口的无线承载和/或逻辑信道的信息的对应关系。
可选地，方式(5)中，第一中继节点自行决定，还包括第一中继节点获取以下信息中的任一种或者任意多种：第一数据包的会话连接的QoS信息，第一数据包的数据流的QoS信息，在第一无线接口发送该第一数据包使用的数据无线承载的信息和/或逻辑信道的QoS信息，以及在第二无线接口发送该第一数据包使用的数据无线承载的信息和/或逻辑信道的QoS信息。其中QoS信息可以包括QoS参数，或者调度要求(例如逻辑信道的 调度优先级等)，或者QoS分类等级(QCI)等。第一中继节点基于上述QoS相关信息，决定第一映射关系。
S420，所述第一中继节点通过所述第二无线接口接收第二中继节点发送的第一数据包，所述第二无线接口为所述第一中继节点和所述第二中继节点之间进行数据传输的无线接口。
S430，所述第一中继节点确定所述第一数据包的属性信息。
可选地，第一中继节点确定所述第一数据包的属性信息的方式可以为以下方式中的任一种或任意多种的组合：
(1)通过该第一数据包中携带的自适应标识获取以下信息中的任一种或任意多种的组合：第一设备的信息，终端设备的信息，会话连接信息，以及数据流信息。
(2)通过接收该第一数据包所使用的第二无线接口的无线承载/逻辑信道，确定第一无线接口的无线承载和/或逻辑信道的信息。
(3)通过该第一数据包携带的传输层信息(例如GTP TEID)和/或数据流信息(例如GTP数据包中携带的QFI)获取以下信息中的任一种或任意多种的组合：第一设备的信息，终端设备的信息，会话连接信息，以及数据流信息。
S440，所述第一中继节点根据所述第一数据包的属性信息和所述第一映射关系，通过所述第一无线接口向网络设备发送所述第一数据包，所述第一无线接口为所述第一中继节点和所述网络设备之间进行数据传输的无线接口。
图20示出了根据本申请实施例的传输方法500的示意性流程图，如图20所示，该方法500包括：
S510，第二中继节点确定第二映射关系，所述第二映射关系为第二数据包的属性信息与发送所述第二数据包使用的无线承载之间的对应关系。第二中继节点通过第二无线接口与第一中继节点通信；第二中继节点通过第三无线接口与第一设备通信。其中，示例性的，第一设备可以为UE或者RN(例如第三中继节点)。
可选地，该第二数据包的属性信息可能包含以下信息中的任一种或多种的组合：第二设备的信息，会话连接信息，数据流信息，该数据包在第三无线接口传输时所在的无线承载的信息，该第二数据包在第三无线接口传输时所用的逻辑信道的信息，该第二数据包在第二无线接口传输时所在的无线承载的信息，该第二数据包在第二无线接口传输时所用的逻辑信道的信息。示例性的，会话连接为PDU session或PDU session resource。示例性的，数据流为QoS flow。
可选地，第二映射关系包括第二上行映射关系和/或第二下行映射关系。
其中，第二上行映射关系可以为以下方式的任意一种：
(1)第二数据包的会话连接信息和/或数据流信息，与在第二无线接口发送该第二数据包使用的无线承载的信息和/或逻辑信道的信息之间的对应关系；
(2)在第三无线接口接收该第二数据包使用的无线承载的信息和/或逻辑信道的信息，与在第二无线接口发送该第二数据包使用的无线承载的信息和/或逻辑信道的信息之间的对应关系；
(3)在第三无线接口接收该第二数据包使用的无线承载的信息和/或逻辑信道的信息，以及第二数据包所属的第二设备的信息，与在第二无线接口发送该第二数据包使用的 无线承载的信息和/或逻辑信道的信息之间的对应关系。
其中，方式(1)的粒度最细，可以为一个UE/RN的一个PDU session内的QFI到DRB的映射；方式(2)的粒度最粗，为第三无线接口的DRB到第二无线接口的DRB的映射；方式3为前两种方式的折中，在方式(2)的基础上增加了UE/RN的维度，即第三无线接口的DRB中属于某个UE/RN的数据到第二无线接口的DRB的映射。
第二下行映射关系的候选方式与上行类似，可以为以下方式的任意一种：
(1)第二数据包的会话连接信息和/或数据流信息，与在第三无线接口发送该第二数据包使用的无线承载的信息和/或逻辑信道的信息之间的对应关系；
(2)在第二无线接口接收该第二数据包使用的无线承载的信息和/或逻辑信道的信息，与在第三无线接口发送该第二数据包使用的无线承载的信息和/或逻辑信道的信息之间的对应关系；
(3)在第二无线接口接收该第二数据包使用的无线承载的信息和/或逻辑信道的信息，以及第二数据包所属的第二设备的信息，与在第三无线接口发送该第二数据包使用的无线承载的信息和/或逻辑信道的信息之间的对应关系。
可选地，第二中继节点获取上述第二映射关系的方式可以为以下方式中的任一种或任意多种的组合：
(1)从宿主基站发送的配置信息中获取；
(2)从OAM发送的配置信息中获取；
(3)从第一数据包中携带的信息中获取；
(4)通过第一数据包的下行发送方式获取第一上行映射关系；
(5)第二中继节点自行决定；
(6)从第一中继节点发送的配置信息中获取。
其中，可选地，方式(3)中，从第二数据包中携带的信息中获取，具体包括获取第二下行映射关系。示例性的，第二中继节点在第二无线接口接收第二数据包，获取第二数据包中携带的以下信息中的任一种或任意多种的组合：会话连接信息，数据流信息，在第三无线接口发送该第二数据包使用的无线承载的信息和/或逻辑信道的信息，以及第二设备的信息；从而获取第二下行映射关系。可选地，方式3中还包括获取第二上行映射关系。示例性的，第二中继节点在第三无线接口接收第二数据包，获取第二数据包中携带的以下信息中的任一种或任意多种的组合：会话连接信息，数据流信息，在第二无线接口发送该第二数据包使用的无线承载的信息和/或逻辑信道的信息，以及第二设备的信息；从而获取第二上行映射关系。
可选地，方式(4)中，通过第二数据包的下行发送方式获取第二上行映射关系，具体包括，第二中继节点获取第二数据包的以下信息中的任一种或任意多种的组合：会话连接信息，数据流信息，在第三无线接口发送该第二数据包使用的无线承载的信息和/或逻辑信道的信息，在第二无线接口发送该第二数据包使用的无线承载的信息和/或逻辑信道的信息，以及第二设备的信息；从而获取以下映射关系中的任一种，作为第一上行映射关系：会话连接信息和/或数据流信息与第二无线接口的无线承载和/或逻辑信道的信息的对应关系，第二无线接口的无线承载和/或逻辑信道的信息与第三无线接口的无线承载和/或逻辑信道的信息的对应关系，第二无线接口的无线承载和/或逻辑信道的信息以及第二设 备的信息与第三无线接口的无线承载和/或逻辑信道的信息的对应关系。
可选地，方式(5)中，第二中继节点自行决定，还包括第二中继节点获取以下信息中的任一种或者任意多种：第二数据包的会话连接的QoS信息，第二数据包的数据流的QoS信息，在第二无线接口发送该第二数据包使用的数据无线承载的信息和/或逻辑信道的QoS信息，以及在第三无线接口发送该第二数据包使用的数据无线承载的信息和/或逻辑信道的QoS信息。其中QoS信息可以包括QoS参数，或者调度要求(例如逻辑信道的调度优先级等)，或者QoS分类等级(QCI)等。第二中继节点基于上述QoS相关信息，决定第一映射关系。
S520，所述第二中继节点通过所述第三无线接口接收终端设备发送的第二数据包；
S530，所述第二中继节点确定所述第二数据包的属性信息；
可选地，第二中继节点确定所述第二数据包的属性信息的方式可以为以下方式中的任一种或任意多种的组合：
(1)通过该第二数据包中携带的自适应标识获取以下信息中的任一种或任意多种的组合：第二设备的信息，会话连接信息，数据流信息。
(2)通过接收该第二数据包所使用的第三无线接口的无线承载/逻辑信道，确定第二无线接口的无线承载和/或逻辑信道的信息。
(3)通过该第二数据包携带的传输层信息(例如GTP TEID)和/或数据流信息(例如GTP数据包中携带的QFI)获取以下信息中的任一种或任意多种的组合：第二设备的信息，会话连接信息，数据流信息。
S540，所述第二中继节点根据所述第二数据包的属性信息和所述第二映射关系，通过所述第二无线接口向所述第一中继节点发送所述第二数据包
图21示出了根据本申请实施例的二跳RN/终端设备通过控制面进行会话建立的方法600的示意性流程图。其中，宿主基站为第一中继节点配置第一映射关系。如图21所示，该方法600包括：
S601，第一设备通过第二无线接口接入第一中继节点，进而通过第一中继节点与宿主基站之间的第一无线接口与核心网传输信令和数据。
可选地，第一设备可以为终端设备或者RN，例如第二中继节点。
示例性的，第一无线接口为Un1口；第一设备为终端设备时，第二无线接口为Uu口；第一设备为RN时，第二无线接口为Un2口。
S602，核心网控制面节点(例如AMF)通过NG接口向宿主基站发送第一控制面请求消息，宿主基站通过NG接口接收第一控制面请求消息，该第一控制面请求消息用于请求宿主基站为该第一设备分配会话连接的资源。
可选地，该第一控制面请求消息包含与第一设备相关的以下信息中的任一种或任意多种的组合：第一终端标识，第二终端标识，会话连接标识信息，第一传输层信息，切片相关信息，会话连接的QoS参数，数据流标识信息，数据流的QoS参数，以及与会话连接建立相关的NAS消息。其中，第一传输层信息为与该会话连接对应的NG-U隧道建立信息，例如，包含核心网用户面节点的GTP TEID和/或传输层地址，用于上行数据传输。其中，第一终端标识和/或第二终端标识用于识别该第一设备；切片相关信息用于中继节点识别与该会话连接对应的切片类型等信息，可用于进行不同切片的差异化调度等操作。
示例性的，该第一控制面请求消息为NGAP消息，例如PDU SESSION RESOURCE SETUP REQUEST，或者PDU SESSION RESOURCE MODIFY REQUEST，或者INITIAL CONTEXT SETUP REQUEST。示例性的，会话连接为PDU session或PDU session resource。示例性的，数据流为QoS flow。示例性的，切片相关信息为切片类型或S-NSSAI。
S603，宿主基站在第一无线接口向第一中继节点发送第二控制面请求消息，该第一中继节点在第一无线接口接收该宿主基站发送的该第二控制面请求消息，该第二控制面请求消息用于请求第一中继节点为第一设备的会话连接分配资源。
可选地，第二控制面请求消息包含第一设备的以下信息中的任一种或任意多种的组合：第一标识，第三标识，会话连接标识信息，第二传输层信息，切片相关信息，会话连接的QoS参数，数据流标识信息，数据流的QoS参数，以及与会话连接建立相关的NAS消息。其中，第二传输层信息为与该会话连接对应的在第一无线接口上区分不同GTP隧道的信息，例如GTP TEID和/或传输层地址，用于上行数据传输。需要说明的是第二传输层信息可以与第一传输层信息相同，即宿主基站不改变该信息直接发送给第一中继节点；或者第二传输层信息与第一传输层信息不同，即宿主基站为该会话连接分配传输层信息(例如GTP TEID)，作为第二传输层信息，替换第一传输层信息，发送给第一中继节点。
可选地，宿主基站在第一无线接口向第一中继节点发送第一无线承载配置信息，用于增加，修改和释放第一无线接口上的无线承载。
可选地，第一无线承载配置信息包含以下信息中的任一种或任意多种的组合：第一中继节点标识信息，无线承载标识信息，SDAP的配置信息，PDCP的配置信息，RLC的配置信息，逻辑信道的配置信息，第一设备的标识信息，会话连接标识信息，以及数据流标识信息。其中，无线承载标识信息可以为DRB标识。
可选地，第一无线承载配置信息承载在第一无线接口上的第一中继节点的RRC消息中(例如RRC重配值消息)，与上述第二控制面请求消息分别发送；或者该第一无线承载配置信息作为一个容器(例如RRC container)包含与上述第二控制面请求消息中；或者上述第二控制面请求消息作为一个容器(例如NGAP消息容器)与上述第一承载配置信息一起，包含与同一个RRC消息(例如RRC重配值消息)中。
可选地，第一中继节点可以基于上述容器与消息/信息的包含关系，识别第一中继节点的无线承载与第一设备的会话连接(以及数据流)的关联关系。
可选地，第一中继节点可以通过上述第一无线承载配置信息获取上行的该第一设备的会话连接标识信息和/或数据流标识信息与第一无线接口的无线承载标识信息的对应关系。需要说明的是，由于控制面协议栈具有多种可选方式，在不同的协议栈架构下，上述第二控制面请求消息的格式和信息内容也各不相同。示例性的，在控制面协议栈架构1-A情况下，该第二控制面请求消息为NGAP消息，承载在第一无线接口的第一中继节点的DRB中传输，该消息中携带第一标识和/或第三标识，用于识别第一设备；在控制面协议栈架构1-B情况下，该第二控制面请求消息为NGAP消息，承载在第一无线接口的第一中继节点的SRB中传输，该消息中携带第一标识和/或第三标识，用于识别第一设备；在控制面协议栈架构2情况下，该第二控制面请求消息为RRC消息，承载在第一无线接口的第一中继节点的SRB中传输，该消息中携带第一标识和/或第三标识，用于识别第一设备，此时第一标识/第三标识不为NGAP ID。
第一中继节点在第一无线接口接收第二控制面请求消息。
可选地，第一中继节点基于第一无线承载配置信息获取上行第一设备的会话连接和/或数据流与第一中继节点在第一无线接口的DRB的映射关系。由于用户面协议栈有多种候选方式，第一中继节点在第一无线接口上发送第一设备的上行数据包的具体流程也略有不同。示例性的，第一无线接口上第一中继节点与宿主基站具有GTP-U协议层的情况下(如图21所示)，第一中继节点在第二无线接口收到第一设备的上行数据包；基于与其对应的会话连接标识信息和/或数据流标识信息，生成GTP-U数据包(按照第二传输层信息在GTP-U数据包包头添加传输层信息，例如GTP TEID)；可选地，在GTP-U数据包中添加数据流标识信息；依据第一无线承载配置信息将上述GTP-U数据包承载在第一无线接口的DRB上传输。
示例性的，第一无线接口上第一中继节点与宿主基站不具有GTP-U协议层的情况下，第一中继节点在第二无线接口收到第一设备的上行数据包；基于与其对应的会话连接标识信息和/或数据流标识信息，增加自适应标识，用于在第一无线接口标识该第一设备以及该第一设备对应的会话连接和/或数据流，生成在第一无线接口数据包；依据第一无线承载配置信息将上述第一无线接口数据包承载在第一无线接口的DRB上传输。可以理解，若第一中继节点未建立与上述第一无线承载配置信息中指示的无线承载标识信息对应的无线承载，则第一中继节点基于上述第一无线承载配置信息建立和配置该无线承载。
可选地S604，第一中继节点在第二无线接口向第一设备发送第二无线承载配置信息，该第二无线承载配置信息用于增加，修改和释放第二无线接口上的无线承载。
可选地，第二无线承载配置信息包含以下信息中的任一种或任意多种的组合：第一设备标识信息，无线承载标识信息，SDAP的配置信息，会话连接标识信息，数据流标识信息，PDCP的配置信息，RLC的配置信息，以及逻辑信道的配置信息。其中，无线承载标识信息可以为DRB标识。
可选地，第一设备通过上述第二无线承载配置信息获取上行的该第一设备的会话连接标识信息和/或数据流标识信息与第二无线接口的无线承载标识信息的对应关系。示例性的，第一中继节点在第二无线接口收到该第一设备的上行数据包，根据承载该数据包的无线承载和/或逻辑信道则可获知该上行数据包所属的会话连接和/或数据流。
可选地，第一中继节点在第二无线接口将第一设备的NAS消息发送给第一设备，并接收NAS响应消息。
S605，第一中继节点在第一无线接口上向宿主基站发送第二控制面响应消息，用于响应第二控制面请求消息。
可选地，第二控制面响应消息包含与第一设备相关的以下信息中的任一种或任意多种的组合：第一标识，第三标识，会话连接标识信息，第三传输层信息，切片相关信息，数据流标识信息，以及与会话连接建立相关的NAS响应消息。其中，第三传输层信息为与该会话连接对应的在第一无线接口上区分不同GTP隧道的信息，例如GTP TEID和/或传输层地址，用于下行数据传输。
可选地，第三传输层信息为第一中继节点分配的。
可选地，第一中继节点在第一无线接口向第一中继节点发送第一无线承载配置完成信息，用于表示对第一无线接口上的无线承载完成配置。
可选地，第一无线承载配置完成信息承载在第一无线接口上的第一中继节点的RRC消息中(例如RRC重配值完成消息)，与上述第二控制面响应消息分别发送，发送先后顺序不限；或者该第一无线承载配置完成信息作为一个容器(例如RRC container)包含与上述第二控制面响应消息中；或者上述第二控制面响应消息作为一个容器(例如NGAP消息容器)与上述第一承载配置完成信息一起，包含与同一个RRC消息(例如RRC重配值完成消息)中。上述第二控制面响应消息的格式和信息内容与第二控制面请求消息类似，在此不再赘述。
S606，宿主基站在第一无线接口上接收第一中继节点发送的第二控制面响应消息。宿主基站通过NG接口向核心网控制面节点(例如AMF)发送第一控制面响应消息，用于响应第一控制面请求消息。
可选地，该第一控制面响应消息包含与第一设备相关的以下信息中的任一种或任意多种的组合：第一终端标识，第二终端标识，会话连接标识信息，第四传输层信息，切片相关信息，数据流标识信息，以及与会话连接建立相关的NAS响应消息。其中，第四传输层信息为与该会话连接对应的NG-U隧道建立信息，例如，宿主基站的GTP TEID和/或传输层地址，用于下行数据传输。需要说明的是第四传输层信息可能与第三传输层信息不同，即宿主基站为该会话连接分配传输层信息(例如GTP TEID)，作为第四传输层信息，替换第三传输层信息，发送给核心网控制面节点。示例性的，该第一控制面响应消息为NGAP消息，例如PDU SESSION RESOURCE SETUP RESPONSE，或者PDU SESSION RESOURCE MODIFY RESPONSE，或者INITIAL CONTEXT SETUP RESPONSE。
可选地，宿主基站在第一无线接口上传输该第一设备的会话连接的下行数据时，基于第三传输信息生成GTP-U数据包，例如，在GTP-U数据包中添加第三传输层信息中包含的GTP TEID。
图22示出了一种三跳RN/终端设备通过控制面进行会话建立的方法700的示意性流程图。其中，宿主基站为第一中继节点配置第一映射关系。第一中继节点为第二中继节点配置第二映射关系。如图22所示，该方法700包括：
S701，第二设备通过第三无线接口接入第二中继节点，进而通过第二中继节点与第一中继节点之间的第二无线接口和第一中继节点与宿主基站之间的第一无线接口，与核心网传输信令和数据。可选地，第二设备可以为终端设备或者RN，例如第三中继节点。示例性的，第一无线接口为Un1口；第二无线接口为Un2口；第二设备为终端设备时，第三无线接口为Uu口；第二设备为RN时，第三无线接口为Un3口。
S702，核心网控制面节点(例如AMF)通过NG接口向宿主基站发送第一控制面请求消息，该宿主基站通过NG接口接收该核心网控制面节点发送的该第一控制面请求消息，该第一控制面请求消息用于请求宿主基站为该第二设备分配会话连接的资源。
可选地，该第一控制面请求消息包含与第二设备相关的以下信息中的任一种或任意多种的组合：第一终端标识，第二终端标识，会话连接标识信息，第一传输层信息，切片相关信息，会话连接的QoS参数，数据流标识信息，数据流的QoS参数，以及与会话连接建立相关的NAS消息。其中，第一传输层信息为与该会话连接对应的NG-U隧道建立信息，例如，包含核心网用户面节点的GTP TEID和/或传输层地址，用于上行数据传输。其中，第一终端标识和/或第二终端标识用于识别该第二设备。示例性的，该第一控制面请 求消息为NGAP消息，例如PDU SESSION RESOURCE SETUP REQUEST，或者PDU SESSION RESOURCE MODIFY REQUEST，或者INITIAL CONTEXT SETUP REQUEST。示例性的，会话连接为PDU session或PDU session resource。示例性的，数据流为QoS flow。示例性的，切片相关信息为切片类型或S-NSSAI。
S703，宿主基站在第一无线接口向第一中继节点向第一中继节点发送第二控制面请求消息，该第一中继节点在第一无线接口接收该宿主基站发送的该第二控制面请求消息，该第二控制面请求消息用于请求第一中继节点为第二设备的会话连接分配资源。
可选地，第二控制面请求消息包含第二设备的以下信息中的任一种或任意多种的组合：第一标识，第三标识，会话连接标识信息，第二传输层信息，切片相关信息，会话连接的QoS参数，数据流标识信息，数据流的QoS参数，以及与会话连接建立相关的NAS消息。其中，第二传输层信息为与该会话连接对应的在第一无线接口上区分不同GTP隧道的信息，例如GTP TEID和/或传输层地址，用于上行数据传输。需要说明的是第二传输层信息可以与第一传输层信息相同，即宿主基站不改变该信息直接发送给第一中继节点；或者第二传输层信息与第一传输层信息不同，即宿主基站为该会话连接分配传输层信息(例如GTP TEID)，作为第二传输层信息，替换第一传输层信息，发送给第一中继节点。
可选地，宿主基站在第一无线接口向第一中继节点发送第一无线承载配置信息，用于增加，修改和释放第一无线接口上的无线承载。
可选地，第一无线承载配置信息包含以下信息中的任一种或任意多种的组合：第一中继节点标识信息，无线承载标识信息，SDAP的配置信息，PDCP的配置信息，RLC的配置信息，逻辑信道的配置信息，第二设备的标识信息，会话连接标识信息，以及数据流标识信息。其中，无线承载标识信息可以为DRB标识。
可选地，第一无线承载配置信息承载在第一无线接口上的第一中继节点的RRC消息中(例如RRC重配值消息)，与上述第二控制面请求消息分别发送；或者该第一无线承载配置信息作为一个容器(例如RRC container)包含与上述第二控制面请求消息中；或者上述第二控制面请求消息作为一个容器(例如NGAP消息容器)与上述第一承载配置信息一起，包含于同一个RRC消息(例如RRC重配值消息)中。
可选地，第一中继节点可以基于上述容器与消息/信息的包含关系，识别第一中继节点的无线承载与第二设备的会话连接(以及数据流)的关联关系。
可选地，第一中继节点可以通过上述第一无线承载配置信息获取上行的该第二设备的会话连接标识信息和/或数据流标识信息与第一无线接口的无线承载标识信息的对应关系。需要说明的是，由于控制面协议栈具有多种可选方式，在不同的协议栈架构下，上述第二控制面请求消息的格式和信息内容也各不相同。示例性的，在控制面协议栈架构1-A情况下，该第二控制面请求消息为NGAP消息，承载在第一无线接口的第一中继节点的DRB中传输，该消息中携带第一标识和/或第三标识，用于识别第二设备；在控制面协议栈架构1-B情况下，该第二控制面请求消息为NGAP消息，承载在第一无线接口的第一中继节点的SRB中传输，该消息中携带第一标识和/或第三标识，用于识别第二设备；在控制面协议栈架构2情况下，该第二控制面请求消息为RRC消息，承载在第一无线接口的第一中继节点的SRB中传输，该消息中携带第一标识和/或第三标识，用于识别第二设备，此时第一标识/第三标识不为NGAP ID。
可选地，第一中继节点基于第一无线承载配置信息获取上行第二设备的会话连接和/或数据流与第一中继节点在第一无线接口的DRB的映射关系。由于用户面协议栈有多种候选方式，第一中继节点在第一无线接口上发送第二设备的上行数据包的具体流程也略有不同。示例性的，第一无线接口上第一中继节点与宿主基站具有GTP-U协议层的情况下，第一中继节点在第二无线接口收到第二设备的上行数据包；基于与其对应的会话连接标识信息和/或数据流标识信息，生成GTP-U数据包(按照第二传输层信息在GTP-U数据包包头添加传输层信息，例如GTP TEID)；可选地，在GTP-U数据包中添加数据流标识信息；依据第一无线承载配置信息将上述GTP-U数据包承载在第一无线接口的DRB上传输。示例性的，第一无线接口上第一中继节点与宿主基站不具有GTP-U协议层的情况下，第一中继节点在第二无线接口收到第二设备的上行数据包；基于与其对应的会话连接标识信息和/或数据流标识信息，增加自适应标识，用于在第一无线接口标识该第二设备以及该第二设备对应的会话连接和/或数据流，生成在第一无线接口数据包；依据第一无线承载配置信息将上述第一无线接口数据包承载在第一无线接口的DRB上传输。可以理解，若第一中继节点未建立与上述第一无线承载配置信息中指示的无线承载标识信息对应的无线承载，则第一中继节点基于上述第一无线承载配置信息建立和配置该无线承载。
S704，第一中继节点在第二无线接口向第二中继节点发送第三控制面请求消息，该第二中继节点在该第二无线接口接收该第一中继节点发送的该第三控制面请求消息，该第三控制面请求消息用于请求第二中继节点为第二设备的会话连接分配资源。
可选地，第三控制面请求消息包含第二设备的以下信息中的任一种或任意多种的组合：第四标识，第五标识，会话连接标识信息，第五传输层信息，切片相关信息，会话连接的QoS参数，数据流标识信息，数据流的QoS参数，以及与会话连接建立相关的NAS消息。其中，第四标识和/或第五标识用于在第二无线接口上识别第二设备；第五传输层信息为与该会话连接对应的在第二无线接口上区分不同GTP隧道的信息，例如GTP TEID和/或传输层地址，用于上行数据传输。需要说明的是第五传输层信息可以与第二传输层信息相同，即第一中继节点不改变该信息直接发送给第二中继节点；或者第五传输层信息与第二传输层信息不同，即第一中继节点为该会话连接分配传输层信息(例如GTP TEID)，作为第五传输层信息，替换第二传输层信息，发送给第二中继节点。
可选地，该第三控制面请求消息中的会话连接标识信息，切片相关信息，会话连接的QoS参数，数据流标识信息，数据流的QoS参数，以及与会话连接建立相关的NAS消息与第二控制面请求消息中的内容相同。
可选地，第一中继节点在第二无线接口向第二中继节点发送第二无线承载配置信息，用于增加，修改和释放第二无线接口上的无线承载。
可选地，第二无线承载配置信息包含以下信息中的任一种或任意多种的组合：第二中继节点标识信息，无线承载标识信息，SDAP的配置信息，PDCP的配置信息，RLC的配置信息，逻辑信道的配置信息，第二设备的标识信息，会话连接标识信息，以及数据流标识信息。其中，无线承载标识信息可以为DRB标识。
可选地，第二无线承载配置信息承载在第二无线接口上的第二中继节点的RRC消息中(例如RRC重配值消息)，与上述第三控制面请求消息分别发送；或者该第二无线承载配置信息作为一个容器(例如RRC container)包含与上述第三控制面请求消息中；或者 上述第三控制面请求消息作为一个容器(例如NGAP消息容器)与上述第二承载配置信息一起，包含与同一个RRC消息(例如RRC重配值消息)中。
可选地，第二中继节点可以基于上述容器与消息/信息的包含关系，识别第二中继节点的无线承载与第二设备的会话连接(以及数据流)的关联关系。
可选地，第二中继节点可以通过上述第二无线承载配置信息获取上行的该第二设备的会话连接标识信息和/或数据流标识信息与第二无线接口的无线承载标识信息的对应关系。需要说明的是，由于控制面协议栈具有多种可选方式，在不同的协议栈架构下，上述第三控制面请求消息的格式和信息内容也各不相同。示例性的，在控制面协议栈架构1-A-A和1-B-A情况下，该第二控制面请求消息为NGAP消息，承载在第二无线接口的第二中继节点的DRB中传输；在另一种控制面协议栈架构下，该第二控制面请求消息为NGAP消息，承载在第二无线接口的第二中继节点的SRB中传输；在控制面协议栈架构2情况下，该第二控制面请求消息为RRC消息，承载在第二无线接口的第二中继节点的SRB中传输，此时第四标识/第五标识不为NGAP ID。
第二中继节点在第二无线接口接收第三控制面请求消息。可选地，第二中继节点基于第二无线承载配置信息获取上行第二设备的会话连接和/或数据流与第二中继节点在第二无线接口的DRB的映射关系。由于用户面协议栈有多种候选方式，第二中继节点在第二无线接口上发送第二设备的上行数据包的具体流程也略有不同。示例性的，第二无线接口上第二中继节点与第一中继节点具有对等的GTP-U协议层的情况下，第二中继节点在第三无线接口收到第二设备的上行数据包；基于与其对应的会话连接标识信息和/或数据流标识信息，生成GTP-U数据包(按照第五传输层信息在GTP-U数据包包头添加传输层信息，例如GTP TEID)；可选地，在GTP-U数据包中添加数据流标识信息；依据第二无线承载配置信息将上述GTP-U数据包承载在第二无线接口的DRB上传输。示例性的，第二无线接口上第二中继节点与宿主基站不具有GTP-U协议层的情况下，第二中继节点在第三无线接口收到第二设备的上行数据包；基于与其对应的会话连接标识信息和/或数据流标识信息，增加自适应标识，用于在第二无线接口标识该第二设备以及该第二设备对应的会话连接和/或数据流，生成在第二无线接口数据包；依据第二无线承载配置信息将上述第二无线接口数据包承载在第二无线接口的DRB上传输。可以理解，若第二中继节点未建立与上述第二无线承载配置信息中指示的无线承载标识信息对应的无线承载，则第二中继节点基于上述第二无线承载配置信息建立和配置该无线承载。
可选地，第二中继节点在第三无线接口向第二设备发送第三无线承载配置信息，用于增加，修改和释放第三无线接口上的无线承载。
可选地，第三无线承载配置信息包含以下信息中的任一种或任意多种的组合：第二设备标识信息，无线承载标识信息，SDAP的配置信息，会话连接标识信息，数据流标识信息，PDCP的配置信息，RLC的配置信息，以及逻辑信道的配置信息。其中，无线承载标识信息可以为DRB标识。
可选地，第二设备通过上述第三无线承载配置信息获取上行的该第二设备的会话连接标识信息和/或数据流标识信息与第三无线接口的无线承载标识信息的对应关系。示例性的，第二中继节点在第三无线接口收到该第二设备的上行数据包，根据承载该数据包的无线承载和/或逻辑信道则可获知该上行数据包所属的会话连接和/或数据流。
可选地，第二中继节点在第三无线接口将第二设备的NAS消息发送给第二设备，并接收NAS响应消息。
S706，第二中继节点在第二无线接口上向第一中继节点发送第三控制面响应消息，该第一中继节点在该第二无线接口上接收该第二中继节点发送的该第三控制面响应消息，该第三控制面响应消息用于响应第三控制面请求消息。
可选地，第三控制面响应消息包含与第二设备相关的以下信息中的任一种或任意多种的组合：第四标识，第五标识，会话连接标识信息，第六传输层信息，数据流标识信息，以及与会话连接建立相关的NAS响应消息。其中，第六传输层信息为与该会话连接对应的在第二无线接口上区分不同GTP隧道的信息，例如GTP TEID和/或传输层地址，用于下行数据传输。可选地，第六传输层信息为第二中继节点分配的。
可选地，第二中继节点在第二无线接口向第一中继节点发送第二无线承载配置完成信息，用于表示对第二无线接口上的无线承载完成配置。
可选地，第二无线承载配置完成信息承载在第二无线接口上的第二中继节点的RRC消息中(例如RRC重配值完成消息)，与上述第二控制面响应消息分别发送，发送先后顺序不限；或者该第二无线承载配置完成信息作为一个容器(例如RRC container)包含与上述第三控制面响应消息中；或者上述第三控制面响应消息作为一个容器(例如NGAP消息容器)与上述第二承载配置完成信息一起，包含与同一个RRC消息(例如RRC重配值完成消息)中。上述第三控制面响应消息的格式和信息内容与第三控制面请求消息类似，在此不再赘述。
第一中继节点在第二无线接口上接收第二中继节点发送的第三控制面响应消息。第一中继节点在第一无线接口上向宿主基站发送第二控制面响应消息，用于响应第二控制面请求消息。
可选地，第二控制面响应消息包含与第二设备相关的以下信息中的任一种或任意多种的组合：第一标识，第三标识，会话连接标识信息，第三传输层信息，切片相关信息，数据流标识信息，以及与会话连接建立相关的NAS响应消息。其中，第三传输层信息为与该会话连接对应的在第一无线接口上区分不同GTP隧道的信息，例如GTP TEID和/或传输层地址，用于下行数据传输。
可选地，第三传输层信息与第六传输层信息不同，即第一中继节点为该会话连接分配传输层信息(例如GTP TEID)，作为第三传输层信息，替换第六传输层信息，发送给宿主基站节点。
可选地，第一中继节点在第一无线接口向第一中继节点发送第一无线承载配置完成信息，用于表示对第一无线接口上的无线承载完成配置。
可选地，第一无线承载配置完成信息承载在第一无线接口上的第一中继节点的RRC消息中(例如RRC重配值完成消息)，与上述第二控制面响应消息分别发送，发送先后顺序不限；或者该第一无线承载配置完成信息作为一个容器(例如RRC container)包含与上述第二控制面响应消息中；或者上述第二控制面响应消息作为一个容器(例如NGAP消息容器)与上述第一承载配置完成信息一起，包含与同一个RRC消息(例如RRC重配值完成消息)中。上述第二控制面响应消息的格式和信息内容与第二控制面请求消息类似，在此不再赘述。
S707，该第一中继节点在第一无线接口上向该宿主基站发送第二控制面响应消息，该宿主基站在第一无线接口上接收第一中继节点发送的第二控制面响应消息，该第二控制面响应消息用于响应该第二控制面请求消息。
S708，宿主基站通过NG接口向核心网控制面节点(例如AMF)发送第一控制面响应消息，该核心网控制面节点在该过NG接口接收该宿主基站发送的该第一控制面响应消息，该第一控制面响应消息用于响应第一控制面请求消息。
可选地，该第一控制面响应消息包含与第二设备相关的以下信息中的任一种或任意多种的组合：第一终端标识，第二终端标识，会话连接标识信息，第四传输层信息，切片相关信息，数据流标识信息，以及与会话连接建立相关的NAS响应消息。其中，第四传输层信息为与该会话连接对应的NG-U隧道建立信息，例如，宿主基站的GTP TEID和/或传输层地址，用于下行数据传输。需要说明的是第四传输层信息可能与第三传输层信息不同，即宿主基站为该会话连接分配传输层信息(例如GTP TEID)，作为第四传输层信息，替换第三传输层信息，发送给核心网控制面节点。示例性的，该第一控制面响应消息为NGAP消息，例如PDU SESSION RESOURCE SETUP RESPONSE，或者PDU SESSION RESOURCE MODIFY RESPONSE，或者INITIAL CONTEXT SETUP RESPONSE。
可选地，宿主基站在第一无线接口上传输该第二设备的会话连接的下行数据时，基于第三传输信息生成GTP-U数据包，例如，在GTP-U数据包中添加第三传输层信息中包含的GTP TEID。
可选地，第一中继节点在第二无线接口上传输该第二设备的会话连接的下行数据时，基于第六传输信息生成GTP-U数据包，例如，在GTP-U数据包中添加第六传输层信息中包含的GTP TEID。
图23示出了根据本申请实施例的基于控制面协议栈1-A-B和1-B-B介绍三跳RN/终端设备通过控制面进行会话建立的方法800的示意性流程图。其中宿主基站为第一中继节点配置第一映射关系，宿主基站为第二中继节点配置第二映射关系，但是该第二映射关系的配置信息由第一中继节点传输给第二中继节点(可以为透传或者第一中继节点处理后发送给第二中继节点两种可选方式)。如图23所示，该方法800包括：
S801，第二设备通过第三无线接口接入第二中继节点，进而通过第二中继节点与第一中继节点之间的第二无线接口和第一中继节点与宿主基站之间的第一无线接口，与核心网传输信令和数据。
选地，第二设备可以为终端设备或者RN，例如第三中继节点。示例性的，第一无线接口为Un1口；第二无线接口为Un2口；第二设备为终端设备时，第三无线接口为Uu口；第二设备为RN时，第三无线接口为Un3口。
S802，核心网控制面节点(例如AMF)通过NG接口发送第一控制面请求消息，宿主基站通过NG接口接收第一控制面请求消息。该第一控制面请求消息用于请求宿主基站为该第二设备分配会话连接的资源。
可选地，该第一控制面请求消息包含与第二设备相关的以下信息中的任一种或任意多种的组合：第一终端标识，第二终端标识，会话连接标识信息，第一传输层信息，切片相关信息，会话连接的QoS参数，数据流标识信息，数据流的QoS参数，以及与会话连接建立相关的NAS消息。其中，第一传输层信息为与该会话连接对应的NG-U隧道建立信 息，例如，包含核心网用户面节点的GTP TEID和/或传输层地址，用于上行数据传输。其中，第一终端标识和/或第二终端标识用于识别该第二设备。示例性的，该第一控制面请求消息为NGAP消息，例如PDU SESSION RESOURCE SETUP REQUEST，或者PDU SESSION RESOURCE MODIFY REQUEST，或者INITIAL CONTEXT SETUP REQUEST。示例性的，会话连接为PDU session或PDU session resource。示例性的，数据流为QoS flow。示例性的，切片相关信息为切片类型或S-NSSAI。
S803，宿主基站在第一无线接口向第一中继节点发送第二控制面请求消息，该第一中继节点在该第一无线接口接收该宿主基站发送的该第二控制面请求消息。
可选地，第二控制面请求消息包含第二设备的以下信息中的任一种或任意多种的组合：第四标识，第三标识，会话连接标识信息，第二传输层信息，切片相关信息，会话连接的QoS参数，数据流标识信息，数据流的QoS参数，以及与会话连接建立相关的NAS消息。其中，第二传输层信息为与该会话连接对应的在第一无线接口上区分不同GTP隧道的信息，例如GTP TEID和/或传输层地址，用于上行数据传输。需要说明的是第二传输层信息可以与第一传输层信息相同，即宿主基站不改变该信息直接发送给第一中继节点；或者第二传输层信息与第一传输层信息不同，即宿主基站为该会话连接分配传输层信息(例如GTP TEID)，作为第二传输层信息，替换第一传输层信息，发送给第一中继节点。
可选地，宿主基站在第一无线接口向第一中继节点发送第一无线承载配置信息，用于增加，修改和释放第一无线接口上的无线承载。
可选地，第一无线承载配置信息包含以下信息中的任一种或任意多种的组合：第一中继节点标识信息，无线承载标识信息，SDAP的配置信息，PDCP的配置信息，RLC的配置信息，逻辑信道的配置信息，第二设备的标识信息，会话连接标识信息，会话连接的QoS参数，数据流标识信息，数据流的QoS参数，以及第二中继节点在第二无线接口上的无线承载标识信息。其中，无线承载标识信息可以为DRB标识。
可选地，第一无线承载配置信息承载在第一无线接口上的第一中继节点的RRC消息中(例如RRC重配值消息)，与上述第二控制面请求消息分别发送。
S803，第一中继节点在第一无线接口接收第二控制面请求消息，不进行解析，直接通过第二无线接口转发给第二中继节点，第二中继节点在第二无线接口接收第二控制面请求消息。第一中继节点在第一无线接口接收第一无线承载配置信息。
可选地，若第一无线承载配置信息中包含第二中继节点在第二无线接口上的无线承载标识信息，则第一中继节点获取其在第一无线接口上的无线承载标识信息与该第二中继节点在第二无线接口上的无线承载标识信息的对应关系，用于上行和/或下行数据包的发送。示例性的，将承载在该第一无线接口上的无线承载的下行数据通过该第二中继节点在第二无线接口上的无线承载发送；或者将承载在该第二中继节点在第二无线接口上的无线承载的上行数据通过该第一无线接口上的无线承载发送。可以理解，若第一中继节点未建立与上述第一无线承载配置信息中指示的无线承载标识信息对应的无线承载，则第一中继节点基于上述第一无线承载配置信息建立和配置该无线承载。
可选地，第一中继节点在第二无线接口向第二中继节点发送第二无线承载配置信息，用于增加，修改和释放第二无线接口上的无线承载。
可选地，第二无线承载配置信息包含以下信息中的任一种或任意多种的组合：第二中 继节点标识信息，无线承载标识信息，SDAP的配置信息，PDCP的配置信息，RLC的配置信息，逻辑信道的配置信息，第二设备的标识信息，会话连接标识信息，以及数据流标识信息。
可选地，第一中继节点通过第一无线承载配置信息获取第二中继节点的无线承载标识信息与第二设备的会话连接标识信息(以及数据流标识信息)的对应关系，进而携带在第二无线承载配置信息中。
可选地，上述第二中继节点的无线承载标识信息与第二设备的会话连接标识信息(以及数据流标识信息)的对应关系可以作为一个容器携带在第一无线承载配置信息中，第一中继节点无需解析，直接透传给第二中继节点。
可选地，第一中继节点通过第一无线承载配置信息中携带的会话连接的QoS参数和/或数据流的QoS参数，进而为第二中继节点进行第二无线接口的无线承载的协议栈配置，例如逻辑信道配置信息(例如调度优先级等)。
可选地，第二无线承载配置信息承载在第二无线接口上的第二中继节点的RRC消息中(例如RRC重配值消息)，与上述第二控制面请求消息分别发送。
可选地，第二中继节点基于第二无线承载配置信息获取上行第二设备的会话连接和/或数据流与第二中继节点在第二无线接口的DRB的映射关系。由于用户面协议栈有多种候选方式，第二中继节点在第二无线接口上发送第二设备的上行数据包的具体流程也略有不同。示例性的，第二无线接口上第二中继节点与第一中继节点具有对等的GTP-U协议层的情况下，第二中继节点在第三无线接口收到第二设备的上行数据包；基于与其对应的会话连接标识信息和/或数据流标识信息，生成GTP-U数据包(按照第二传输层信息在GTP-U数据包包头添加传输层信息，例如GTP TEID)；可选地，在GTP-U数据包中添加数据流标识信息；依据第二无线承载配置信息将上述GTP-U数据包承载在第二无线接口的DRB上传输。示例性的，第二无线接口上第二中继节点与宿主基站不具有GTP-U协议层的情况下，第二中继节点在第三无线接口收到第二设备的上行数据包；基于与其对应的会话连接标识信息和/或数据流标识信息，增加自适应标识，用于在第二无线接口标识该第二设备以及该第二设备对应的会话连接和/或数据流，生成在第二无线接口数据包；依据第二无线承载配置信息将上述第二无线接口数据包承载在第二无线接口的DRB上传输。可以理解，若第二中继节点未建立与上述第二无线承载配置信息中指示的无线承载标识信息对应的无线承载，则第二中继节点基于上述第二无线承载配置信息建立和配置该无线承载。
S804，第二中继节点在第三无线接口向第二设备发送第三无线承载配置信息，该第二设备在该第三无线接口接收该第二中继节点发送的该第三无线承载配置信息，该第三无线承载配置信息用于增加，修改和释放第三无线接口上的无线承载。
可选地，第三无线承载配置信息包含以下信息中的任一种或任意多种的组合：第二设备标识信息，无线承载标识信息，SDAP的配置信息，会话连接标识信息，数据流标识信息，PDCP的配置信息，RLC的配置信息，以及逻辑信道的配置信息。其中，无线承载标识信息可以为DRB标识。
可选地，第二设备通过上述第三无线承载配置信息获取上行的该第二设备的会话连接标识信息和/或数据流标识信息与第三无线接口的无线承载标识信息的对应关系。示例性 的，第二中继节点在第三无线接口收到该第二设备的上行数据包，根据承载该数据包的无线承载和/或逻辑信道则可获知该上行数据包所属的会话连接和/或数据流。
可选地，第二中继节点在第三无线接口将第二设备的NAS消息发送给第二设备，并接收NAS响应消息。
S805，第二中继节点在第二无线接口上向第一中继节点发送第二控制面响应消息，用于响应第二控制面请求消息。可选地，第二控制面响应消息包含与第二设备相关的以下信息中的任一种或任意多种的组合：第四标识，第三标识，会话连接标识信息，第六传输层信息，数据流标识信息，以及与会话连接建立相关的NAS响应消息。其中，第六传输层信息为与该会话连接对应的在第二无线接口上区分不同GTP隧道的信息，例如GTP TEID和/或传输层地址，用于下行数据传输。
可选地，第六传输层信息为第二中继节点分配的。
可选地，第二中继节点在第二无线接口向第一中继节点发送第二无线承载配置完成信息，用于表示对第二无线接口上的无线承载完成配置。
可选地，第二无线承载配置完成信息承载在第二无线接口上的第二中继节点的RRC消息中(例如RRC重配值完成消息)，与上述第二控制面响应消息分别发送，发送先后顺序不限。
S805，第一中继节点在第二无线接口上接收第二中继节点发送的第二控制面响应消息，不进行解析，直接转发给宿主基站，宿主基站在第一无线接口上接收第一中继节点发送的第二控制面响应消息。
可选地，第一中继节点在第一无线接口向第一中继节点发送第一无线承载配置完成信息，用于表示对第一无线接口上的无线承载完成配置。
可选地，第一无线承载配置完成信息承载在第一无线接口上的第一中继节点的RRC消息中(例如RRC重配值完成消息)，与上述第二控制面响应消息分别发送，发送先后顺序不限。
S806，宿主基站通过NG接口向核心网控制面节点(例如AMF)发送第一控制面响应消息，该核心网控制面节点在该NG接口接收该宿主基站发送的该第一控制面响应消息，该第一控制面响应消息用于响应第一控制面请求消息。
可选地，该第一控制面响应消息包含与第二设备相关的以下信息中的任一种或任意多种的组合：第一终端标识，第二终端标识，会话连接标识信息，第四传输层信息，切片相关信息，数据流标识信息，以及与会话连接建立相关的NAS响应消息。其中，第四传输层信息为与该会话连接对应的NG-U隧道建立信息，例如，宿主基站的GTP TEID和/或传输层地址，用于下行数据传输。需要说明的是第四传输层信息可能与第六传输层信息不同，即宿主基站为该会话连接分配传输层信息(例如GTP TEID)，作为第四传输层信息，替换第六传输层信息，发送给核心网控制面节点。示例性的，该第一控制面响应消息为NGAP消息，例如PDU SESSION RESOURCE SETUP RESPONSE，或者PDU SESSION RESOURCE MODIFY RESPONSE，或者INITIAL CONTEXT SETUP RESPONSE。
可选地，宿主基站在第一无线接口上传输该第二设备的会话连接的下行数据时，基于第六传输信息生成GTP-U数据包，例如，在GTP-U数据包中添加第六传输层信息中包含的GTP TEID。
可选地，第一中继节点在第一无线接口上接收该第二设备的会话连接的下行数据，并基于在第一无线承载配置信息中获取的第一无线接口的无线承载与第二无线接口的无线承载的映射关系，在第二无线接口上传输该第二设备的会话连接的下行数据。
具体地，通过结合一下协议栈架构来介绍上述方法400和500。
图24和图27示出了根据本申请实施例的两种L3协议栈用户面架构的示意图，RN2/UE通过RN1接入后，建立与RN1之间第二无线接口(即Un2或Uu口)的DRB，承载RN2/UE自身(以及RN2服务的UE)的数据传输；这部分数据的上行需要通过第一无线接口(即Un1)，由RN1转发给Donor，从而通过Donor转发给相应的核心网节点，这部分数据的下行由核心网发送给Donor，经由RN1发送给RN2/UE，因此需要确定RN1转发上行和/或下行数据时使用的DRB，以及第一无线接口数据转发的方式(例如GTP数据包、或者SDAP SDU数据包)。
图24示出了根据本申请实施例的L3协议栈用户面架构1的一示意图，其中Un1口的协议栈包含GTP-U协议层，GTP数据包承载在Un1DRB中传输。
(1)NG-U口
宿主基站与为RN服务的核心网用户面节点的协议栈对等，具体的协议栈组成与现有技术类似，在此不再赘述。
RN2/UE接入RN1后，通过控制面流程请求建立会话连接(例如PDU session)和/或与该会话连接对应的数据流(例如QoS flow)，核心网为该RN2/UE配置NG-U接口上的数据传输隧道，并将该隧道建立信息通过NG-C的NGAP消息发送给宿主基站。
示例性的，上述控制面流程中涉及如下信息交互：在NG-C接口，核心网将该RN2/UE相关的以下信息中的任一种或任意多种的组合通过NGAP消息发送给宿主基站：会话连接的标识信息，数据流的标识信息，QoS参数，NG-U隧道建立信息。其中NG-U隧道建立信息可能包含以下信息中的任一种或任意多种的组合：GTP-U TEID，IP地址，以及端口号等信息。
(2)Un1无线接口：传输GTP-U数据包
协议栈：在Un1口，宿主基站与RN1具有对等的协议层，具体包含：GTP-U层，UDP层(可选地)，IP层(可选地)，SDAP层(可选地，即可以配置为透传)，PDCP层，RLC层，MAC层，以及PHY层。上述GTP-U层(还可以结合UDP层和/或IP层)可以用于区分承载在Un1口上同一个DRB中的数据，例如一个GTP隧道(可选地，通过一对TEID识别，分别对应上行和下行)对应一个UE/RN的会话连接。
可选地，该Un1口的协议栈还包含自适应层功能，用于添加和/或解析第一自适应标识。该自适应功能可以包含于现有的协议层，例如SDAP层/PDCP层/RLC层/MAC层/PHY层；或者自适应功能可以单独部署在一个协议层中，例如称为自适应(Adaptation，简称Adapt)层。
可选地，自适应层可以部署在GTP-U层与PDCP层之间，或者部署在PDCP层与RLC层之间，或者部署在RLC层与MAC层之间，或者部署在MAC与PHY层之间。在Un1口区分数据类型的方法以及第一自适应标识的相关描述参见1-A协议栈的描述，在此不再赘述。
对于下行，宿主基站将在NG-U接收的GTP隧道映射为Un1口的GTP隧道。示例性 的，宿主基站为对应的会话连接分配NG-U上的GTP TEID，通过NG-C的NGAP消息告知核心网，核心网传输该会话连接的数据时，采用该GTP TEID进行标识，可选地，在GTP-U数据包上携带QoS flow的标识。
可选地，将该Un1口的GTP隧道承载在为RN1在Un1口建立的DRB上传输可以采用以下方式中的任一种或任意多种的组合：
方式一：把一个GTP隧道的数据映射到同一个DRB中传输；
方式二：将该GTP隧道中数据包按照数据流的QoS要求映射到多个DRB上。具体的，将该GTP-U中的一个或多个QoS flow映射到一个DRB上，上述一个或多个QoS flow的QoS要求与该DRB相匹配的。
可选地，上述映射到多个DRB上属于同一个GTP-U隧道的QoS流使用相同的GTP TEID，用于令RN1识别和汇聚上述GTP隧道的数据包，并发送到Un2/Uu口与该GTP隧道对应的会话连接的SDAP实体上。
方式三：为该GTP隧道中的数据流分配一个类别标识(例如按照QoS要求映射到一个QCI，此时类别标识即为QCI)，多个数据流可以分配相同的类别标识，一个或多个类别标识映射到一个DRB上。在Un1口上传输该数据包时，携带该类别标识。
可选地，该类别标识携带在Un1口上的GTP数据包上(例如用DSCP代表QCI)。
可以理解，上述GTP隧道对应一个UE/RN的一个会话连接，对于多个UE/RN的GTP隧道的数据，可以映射到不同的DRB，或者相同的DRB中。若为不同的DRB，则该DRB仅承载一个UE/RN的数据；若为相同的DRB，则该DRB中可能承载着多个UE/RN的数据，这些数据可能具有类似的QoS需求。类似的，对于一个UE/RN的多个GTP隧道的数据可以映射到不同的DRB，或者相同的DRB中。若为不同的DRB，则该DRB仅承载该UE的一个会话连接的数据；若为相同的DRB，则该DRB中可能承载着该UE/RN的多个会话连接的数据，这些数据可能具有类似的QoS需求。
对于上行，RN1基于第一上行映射关系将在Un2/Uu口上收到的数据包经过处理(例如，进行GTP-U封装)后，通过Un1口发送给宿主基站。
可选地，RN1在Un1口上发送的数据包携带第一自适应标识，用于宿主基站区分Un1口上的数据。
一种可选方式是，RN1将在Un2上接收的数据包，按照GTP隧道进行汇聚，生成在Un1口发送的GTP数据包。
可选地，RN1处理在Un2口接收的数据包，获得该数据包对应的PDU session和QoS flow，进而生成对应的GTP数据包，其中携带GTP TEID和QFI。随后RN1按照与下行类似的方式将该Un2口的GTP数据包承载在RN1的Un1口的DRB上传输，例如可以采用以下方式中的任一种或任意多种的组合：
方式一：把一个GTP隧道的数据映射到同一个DRB中传输；
方式二：将该GTP隧道中数据包按照数据流的QoS要求映射到多个DRB上。具体的，将该GTP-U中的一个或多个QoS flow映射到一个DRB上，上述一个或多个QoS flow的QoS要求与该DRB相匹配的。可选地，上述映射到多个DRB上属于同一个GTP-U隧道的QoS流使用相同的GTP TEID，用于令宿主基站识别和汇聚上述GTP隧道的数据包，并发送给核心网。
方式三：为该GTP隧道中的数据流分配一个类别标识(例如按照QoS要求映射到一个QCI，此时类别标识即为QCI)，多个数据流可以分配相同的类别标识，一个或多个类别标识映射到一个DRB上。可选地，在Un1口上传输该数据包时，携带该类别标识。可选地，该类别标识携带在Un1口上的GTP数据包上(例如用DSCP代表QCI)。可选地，RN1基于PDU session(或GTP TEID)和/或QFI与分类标识之间的对应关系(简称为分类映射关系，可选地，该对应关系可能是与一个RN/UE对应的)，获知数据包对应的分类标识，从而基于分类标识与Un1口的DRB的对应关系，将该数据包承载在该DRB中传输。可选地，RN1获取分类映射关系的方式为：宿主基站配置，或QAM配置，或获得在Un1口接收的数据包的PDU session(或GTP TEID)和/或QFI与分类标识之间的对应关系。
图25示出了一种Un1无线接口的数据传输过程的示意图。一个会话连接中的不同数据流可以映射到不同的Un1口DRB中；不同UE/RN的数据流可以映射到同一个Un1口DRB。对应上述方式二(上下行类似)。
图26示出了一种数据传输过程中RN1内部的数据包映射过程的示意图。
RN1的基站部分在Un2口接收上述上行数据，基于承载上行数据的DRB信息和数据包上的QFI信息，获知上述上行数据对应的PDU session，从而生成GTP数据包，该GTP数据包上携带GTP TEID和QFI。一种可选的方式是，RN1基于分类映射关系关系在上述数据包上打上类型标识(可选地，类型标识可以携带在IP层，例如用DSCP标识体现，即类型标识与DSCP之间具有对应关系)；RN1的UE部分读取类型标识，基于第一上行映射关系，将上述GTP数据包承载在Un1口发送。另一种可选的方式是，RN1基于第一上行映射关系在上述数据包上打上DRB标识(可选的，DRB标识可以携带在IP层，例如用DSCP标识体现，即DRB标识与DSCP标识之间具有对应关系)，RN1的UE部分读取DRB标识，将上述GTP数据包承载在Un1口的对应的DRB上发送。
可选地，上述类型标识/DRB标识与DSCP标识之间的对应关系可以为RN1内部定义，用于RN1的基站部分和UE部分进行对应与解读。
(3)Un2/Uu无线接口
协议栈：在Un2/Uu口，RN1与RN2/UE具有对等的协议层，具体包含：SDAP层，PDCP层，RLC层，MAC层，以及PHY层。
可选地，该Un口的协议栈还包含自适应层功能，用于添加和/或解析第二自适应标识。该第二自适应功能可以包含于现有的协议层，例如SDAP层/PDCP层/RLC层/MAC层/PHY层；或者自适应功能可以单独部署在一个协议层中，例如称为自适应(Adaptation，简称Adapt)层。
可选地，自适应层可以部署在SDAP层之上，或者SDAP层与PDCP层之间，或者部署在PDCP层与RLC层之间，或者部署在RLC层与MAC层之间，或者部署在MAC与PHY层之间。在Un2口区分数据类型的方法以及第二自适应标识的相关描述参见之前的描述，在此不再赘述。
可选地，对于自适应功能，若RN2没有开启基站模块为UE提供服务，此时该功能可以不启用，即无需进行额外标识。
对于下行，RN1通过控制面RRC消息为RN2/UE配置无线接口的DRB，同时将上行 各个PDU session里的QoS flow与DRB的映射关系告诉RN2/UE。
对于上行，RN2/UE基于PDU session(以及QoS flow)与DRB的对应关系，将QoS flow放在对应DRB中发送给RN1。
图27示出了根据本申请实施例的L3协议栈用户面架构2的一示意图，其中，Un1口的协议栈不包含GTP-U协议层，通过自适应标识区分承载在Un1口的属于不同节点的数据。
(1)NG-U口
宿主基站与为RN服务的核心网用户面节点的协议栈对等，具体的协议栈组成与现有技术类似，在此不再赘述。
RN2/UE接入RN1后，通过控制面流程请求建立会话连接(例如PDU session)和/或与该会话连接对应的数据流(例如QoS flow)，核心网为该RN配置NG-U接口上的数据传输隧道，并将该隧道建立信息通过NG-C的NGAP消息发送给宿主基站。
示例性的，上述控制面流程中涉及如下信息交互：在NG-C接口，核心网将该RN2相关的以下信息中的任一种或任意多种的组合通过NGAP消息发送给宿主基站：会话连接的标识信息，数据流的标识信息，QoS参数，NG-U隧道建立信息。其中NG-U隧道建立信息可能包含以下信息中的任一种或任意多种的组合：GTP-U TEID，IP地址，以及端口号等信息。
(2)Un1无线接口：无GTP-U封装(数据直接作为Adap./SDAP的SDU)
协议栈：在Un1口，宿主基站与RN1具有对等的协议层，具体包含：SDAP层(可选地，即可以配置为透传)，PDCP层，RLC层，MAC层，以及PHY层。该Un1口的协议栈还包含自适应层功能，用于添加和/或解析第一自适应标识。该自适应功能可以包含于现有的协议层，例如SDAP层/PDCP层/RLC层/MAC层/PHY层；或者自适应功能可以单独部署在一个协议层中，例如称为自适应(Adaptation，简称Adapt)层。
可选地，自适应层可以部署在SDAP层之上，或者部署在SDAP层与PDCP层之间，或者部署在PDCP层与RLC层之间，或者部署在RLC层与MAC层之间，或者部署在MAC与PHY层之间。如之前实施例中介绍，第一自适应标识可以包含以下信息中的任一种或任意多种的组合：二跳RN标识和/或跳数信息(用于识别RN2)，第二UE标识(用于识别RN2服务的UE)，一跳RN标识和/或跳数信息(用于识别RN1)，第一UE标识(用于识别RN1服务的UE)，三跳RN标识和/或跳数信息(用于识别通过RN2和RN1传递数据的三跳、四跳乃至n跳的RN)，第三UE标识(用于识别多跳RN服务的UE)，NGAP消息类型，XnAP消息类型，GTP-U消息类型(属于NG-U或Xn-U)，用户面数据包类型，以及用户面数据包信息。其中，用户面数据包信息包含以下信息中的任一种或任意多种的组合：会话连接信息，数据流信息，分类标识信息，该数据包在第二无线接口传输时所在的无线承载的信息，该数据包在第二无线接口传输时所用的逻辑信道的信息，该数据包在第一无线接口传输时所在的无线承载的信息，该数据包在第一无线接口传输时所用的逻辑信道的信息，该数据包在第三无线接口传输时所在的无线承载的信息，以及该数据包在第三无线接口传输时所用的逻辑信道的信息。
对于下行，宿主基站将在NG-U接收的GTP隧道中的数据映射到为RN1在Un1口建立的DRB传输。
可选地，将该NG-U口的GTP隧道的数据包处理(例如经过Un1口和Un2口的协议栈处理)后，承载在为RN1在Un1口建立的DRB上传输，可以采用以下方式中的任一种或任意多种的组合：
方式一：把一个GTP隧道的数据映射到同一个DRB中传输；
方式二：将该GTP隧道中数据包按照数据流的QoS要求映射到多个DRB上。具体的，将该GTP-U中的一个或多个QoS flow映射到一个DRB上，上述一个或多个QoS flow的QoS要求与该DRB相匹配的。可选地，上述映射到多个DRB上属于同一个GTP-U隧道的QoS流的数据需要携带第一自适应标识，用于令RN1识别和汇聚上述GTP隧道的数据包，并发送到Un2口与该GTP隧道对应的会话连接的SDAP实体上。
方式三：为该GTP隧道中的数据流分配一个类别标识(例如按照QoS要求映射到一个QCI，此时类别标识即为QCI)，多个数据流可以分配相同的类别标识，一个或多个类别标识映射到一个DRB上。可选地，在Un2上传输该数据包时，在第一自适应标识中包含该类别标识。
对于上行，RN1基于第一上行映射关系将在Un2口上收到的数据包经过处理后，通过Un1口发送给宿主基站。可选地，RN1在Un1口上发送的数据包携带第一自适应标识，用于宿主基站区分Un1口上的数据。
一种可选方式是，RN1在Un2上接收的数据包，获得该数据包对应的PDU session和QoS flow，进而生成对应的在Un1口发送的数据包，其中携带第一自适应标识。随后RN1按照与下行类似的方式将该Un2口的数据包承载在RN1的Un1口的DRB上传输，例如可以采用以下方式中的任一种或任意多种的组合：
方式一：把一个PDU session的数据映射到同一个DRB中传输；
方式二：将该PDU session数据包按照数据流的QoS要求映射到多个DRB上。具体的，将该PDU session的一个或多个QoS flow映射到一个DRB上，上述一个或多个QoS flow的QoS要求与该DRB相匹配的。可选地，上述映射到多个DRB上属于同一个PDU session的数据包上携带第一自适应标识，用于令宿主基站识别和汇聚上述PDU session的数据包，通过同一个NG-U上的GTP隧道发送给核心网。
方式三：为该PDU session的数据流分配一个类别标识(例如按照QoS要求映射到一个QCI，此时类别标识即为QCI)，多个数据流可以分配相同的类别标识，一个或多个类别标识映射到一个DRB上。可选地，在Un1口上传输该数据包时，携带该类别标识。可选地，该类别标识包含与第一自适应标识中。可选地，RN1基于PDU session和/或QFI与分类标识之间的对应关系(简称为分类映射关系，可选地，该对应关系可能是与一个RN/UE对应的)，获知数据包对应的分类标识，从而基于分类标识与Un1口的DRB的对应关系，将该数据包承载在该DRB中传输。可选地，RN1获取分类映射关系的方式为：宿主基站配置，或QAM配置，或获得在Un1口接收的数据包的PDU session和/或QFI与分类标识之间的对应关系。
(3)Un2/Uu无线接口
协议栈：在Un2/Uu口，RN1与RN2/UE具有对等的协议层，具体包含：SDAP层，PDCP层，RLC层，MAC层，以及PHY层。可选地，该Un口的协议栈还包含自适应层功能，用于添加和/或解析第二自适应标识。该第二自适应功能可以包含于现有的协议层， 例如SDAP层/PDCP层/RLC层/MAC层/PHY层；或者自适应功能可以单独部署在一个协议层中，例如称为自适应(Adaptation，简称Adapt)层。可选地，自适应层可以部署在SDAP层之上，或者SDAP层与PDCP层之间，或者部署在PDCP层与RLC层之间，或者部署在RLC层与MAC层之间，或者部署在MAC与PHY层之间。在Un2/Uu口区分数据类型的方法以及第二自适应标识的相关描述参见之前的描述，在此不再赘述。可选地，对于自适应功能，若RN2没有开启基站模块为UE提供服务，此时该功能可以不启用，即无需进行额外标识。
对于下行，RN1通过控制面RRC消息为RN2/UE配置无线接口的DRB，同时将上行各个PDU session里的QoS flow与DRB的映射关系告诉RN2/UE。
对于上行，RN2/UE基于PDU session(以及QoS flow)与DRB的对应关系，将QoS flow放在对应DRB中发送给RN1。
图28、图31和图32示出了根据本申请实施例的3种L3协议栈用户面架构的示意图，RN3/UE通过RN2接入后，建立与RN2之间第三无线接口(即Un3或Uu口)的DRB，承载RN3/UE自身(以及RN3服务的UE)的数据传输；这部分数据的上行需要通过第二无线接口(即Un2)，由RN2转发给RN1；再经由第一无线接口(即Un1)，由RN1转发给Donor，从而通过Donor转发给相应的核心网节点，这部分数据的下行由核心网发送给Donor，经由RN1发送给RN2，再经由RN2发送给RN3/UE。因此需要确定RN1和RN2转发上行和/或下行数据时使用的DRB，以及第一无线接口、第二无线接口的数据转发的方式，例如是否经过GTP-U层处理。
图28示出了根据本申请实施例的L3协议栈用户面架构1-A的一示意图。
(1)NG-U口，与L3协议栈用户面架构1中处理类似
宿主基站与为RN服务的核心网用户面节点的协议栈对等，具体的协议栈组成与现有技术类似，在此不再赘述。
RN3/UE接入RN2后，通过控制面流程请求建立会话连接(例如PDU session)和/或与该会话连接对应的数据流(例如QoS flow)，核心网为该RN3/UE配置NG-U接口上的数据传输隧道，并将该隧道建立信息通过NG-C的NGAP消息发送给宿主基站。
示例性的，上述控制面流程中涉及如下信息交互：在NG-C接口，核心网将该RN3/UE相关的以下信息中的任一种或任意多种的组合通过NGAP消息发送给宿主基站：会话连接的标识信息，数据流的标识信息，QoS参数，NG-U隧道建立信息。其中NG-U隧道建立信息可能包含以下信息中的任一种或任意多种的组合：GTP-U TEID，IP地址，以及端口号等信息。
(2)Un1无线接口：传输GTP-U数据包，与L3协议栈用户面架构1中处理类似
协议栈：在Un1口，宿主基站与RN1具有对等的协议层，具体包含：GTP-U层，UDP层(可选地)，IP层(可选地)，SDAP层(可选地，即可以配置为透传)，PDCP层，RLC层，MAC层，以及PHY层。上述GTP-U层(还可以结合UDP层和/或IP层)可以用于区分承载在Un1口上同一个DRB中的数据，例如一个GTP隧道(可选地，通过一对TEID识别，分别对应上行和下行)对应一个UE的会话连接。可选地，该Un1口的协议栈还包含自适应层功能，用于添加和/或解析第一自适应标识。自适应层的部署方式、在Un1口区分数据类型的方法以及第一自适应标识的用途与L3协议栈用户面架构1中处理 类似，在此不再赘述。
对于下行，宿主基站将在NG-U接收的GTP隧道映射为Un1口的GTP隧道。示例性的，宿主基站为对应的会话连接分配NG-U上的GTP TEID，通过NG-C的NGAP消息告知核心网，核心网传输该会话连接的下行数据时，采用该GTP TEID进行标识，可选地，在GTP-U数据包上携带QoS flow的标识。可选地，将该Un1口的GTP隧道承载在为RN1在Un1口建立的DRB上传输可以采用以下方式中的任一种或任意多种的组合：
方式一：把一个GTP隧道的数据映射到同一个DRB中传输；
方式二：将该GTP隧道中数据包按照数据流的QoS要求映射到多个DRB上。具体的，将该GTP-U中的一个或多个QoS flow映射到一个DRB上，上述一个或多个QoS flow的QoS要求与该DRB相匹配的。可选地，上述映射到多个DRB上属于同一个GTP-U隧道的QoS流使用相同的GTP TEID，用于令RN1识别和汇聚上述GTP隧道的数据包，并关联到该会话连接对应的Un2口的GTP隧道。
方式三：为该GTP隧道中的数据流分配一个类别标识(例如按照QoS要求映射到一个QCI，此时类别标识即为QCI)，多个数据流可以分配相同的类别标识，一个或多个类别标识映射到一个DRB上。在Un1口上传输该数据包时，携带该类别标识。可选地，该类别标识携带在Un1口上的GTP数据包上(例如用DSCP代表QCI)。可选地，在Un2/Uu口上传输该数据包时，携带该类别标识。可选地，该类别标识携带在Un2/Uu口上的GTP数据包上(例如用DSCP代表QCI)。
对于上行，RN1基于第一上行映射关系将在Un2/Uu口上收到的数据包经过处理(例如，进行GTP-U封装)后，通过Un1口发送给宿主基站。可选地，RN1在Un1口上发送的数据包携带第一自适应标识，用于宿主基站区分Un1口上的数据。
一种可选方式是，RN1将在Un2上接收的数据包，按照GTP隧道进行汇聚，生成在Un1口发送的GTP数据包。可选地，RN1处理在Un2口接收的数据包，基于GTP包上携带的信息(例如TEID和QFI)，获得该数据包对应的PDU session和QoS flow，进而生成对应的GTP数据包，其中携带QFI和Un1口的GTP TEID。另一种可选的方式是：不进行GTP隧道的聚类，直接基于Un2上收到的GTP数据包携带的信息，生成GTP数据包，找到对应的Un1口DRB。随后RN1按照与下行类似的方式将该Un2口的GTP数据包承载在RN1的Un1口的DRB上传输，例如可以采用以下方式中的任一种或任意多种的组合：
方式一：把一个GTP隧道的数据映射到同一个DRB中传输；
方式二：将该GTP隧道中数据包按照数据流的QoS要求映射到多个DRB上。具体的，将该GTP-U中的一个或多个QoS flow映射到一个DRB上，上述一个或多个QoS flow的QoS要求与该DRB相匹配的。可选地，上述映射到多个DRB上属于同一个GTP-U隧道的QoS流使用相同的GTP TEID，用于令宿主基站识别和汇聚上述GTP隧道的数据包，并发送给核心网。
方式三：基于数据流的分类标识映射到对应的DRB中传输。一种可能的方式是：为该GTP隧道中的数据流分配一个类别标识(例如按照QoS要求映射到一个QCI，此时类别标识即为QCI)，多个数据流可以分配相同的类别标识，一个或多个类别标识映射到一个DRB上。可选地，在Un1口上传输该数据包时，携带该类别标识。可选地，该类别标 识携带在Un1口上的GTP数据包上(例如用DSCP代表QCI)。可选地，RN1基于PDU session(或GTP TEID)和/或QFI与分类标识之间的对应关系(简称为分类映射关系，可选地，该对应关系可能是与一个RN/UE对应的)，获知数据包对应的分类标识，从而基于分类标识与Un1口的DRB的对应关系，将该数据包承载在该DRB中传输。可选地，RN1获取分类映射关系的方式为：宿主基站配置，或QAM配置，或获得在Un1口接收的数据包的PDU session(或GTP TEID)和/或QFI与分类标识之间的对应关系。另一种可能的方式是：在Un2口接收到的GTP数据包上携带分类标识，直接基于分类映射关系，将上述数据包承载在对应DRB上传输。
(3)Un2无线接口：传输GTP-U数据包
协议栈：在Un2口，RN1与RN2具有对等的协议层，具体包含：GTP-U层，UDP层(可选地)，IP层(可选地)，SDAP层(可选地，即可以配置为透传)，PDCP层，RLC层，MAC层，以及PHY层。上述GTP-U层(还可以结合UDP层和/或IP层)可以用于区分承载在Un2口上同一个DRB中的数据，例如一个GTP隧道(可选地，通过一对TEID识别，分别对应上行和下行)对应一个UE/RN的会话连接。
可选地，该Un2口的协议栈还包含自适应层功能，用于添加和/或解析第二自适应标识。该自适应功能可以包含于现有的协议层，例如SDAP层/PDCP层/RLC层/MAC层/PHY层；或者自适应功能可以单独部署在一个协议层中，例如称为自适应(Adaptation，简称Adapt)层。
可选地，自适应层可以部署在GTP-U层与PDCP层之间，或者部署在PDCP层与RLC层之间，或者部署在RLC层与MAC层之间，或者部署在MAC与PHY层之间。在Un2口区分数据类型的方法以及第二自适应标识的相关描述参见控制面协议栈中的描述，在此不再赘述。
对于下行，一种可选的方式是RN1将在Un1接收的GTP隧道映射为Un2口的GTP隧道。示例性的，RN1在Un1口接收GTP数据包，并基于GTP数据包携带的信息(例如TEID)，将属于同一个会话连接的数据包聚合，并关联到Un2口的GTP隧道，进而承载在Un2口的DRB上传输。另一种可选的方式是：RN1不进行GTP隧道的聚类，直接基于Un1上收到的GTP数据包携带的信息，生成GTP数据包，找到对应的Un2口DRB，进而承载在Un2口的DRB上传输。
可选地，在GTP-U数据包上携带QoS flow的标识。可选地，将该Un2口的GTP隧道承载在为RN2在Un2口建立的DRB上传输的方式与Un1口的处理类似，可以采用以下方式中的任一种或任意多种的组合：
方式一：把一个GTP隧道的数据映射到同一个DRB中传输；
方式二：将该GTP隧道中数据包按照数据流的QoS要求映射到多个DRB上。具体的，将该GTP-U中的一个或多个QoS flow映射到一个DRB上，上述一个或多个QoS flow的QoS要求与该DRB相匹配的。可选地，上述映射到多个DRB上属于同一个GTP-U隧道的QoS流使用相同的GTP TEID，用于令RN2识别和汇聚上述GTP隧道的数据包，并发送到Un3/Uu口与该GTP隧道对应的会话连接的SDAP实体上。
方式三：基于数据流的分类标识映射到对应的DRB中传输。一种可能的方式是：为该GTP隧道中的数据流分配一个类别标识(例如按照QoS要求映射到一个QCI，此时类 别标识即为QCI)，多个数据流可以分配相同的类别标识，一个或多个类别标识映射到一个DRB上。可选地，在Un2口上传输该数据包时，携带该类别标识。可选地，该类别标识携带在Un2口上的GTP数据包上(例如用DSCP代表QCI)。可选地，RN1基于PDU session(或GTP TEID)和/或QFI与分类标识之间的对应关系(简称为分类映射关系，可选地，该对应关系可能是与一个RN/UE对应的)，获知数据包对应的分类标识，从而基于分类标识与Un2口的DRB的对应关系，将该数据包承载在该DRB中传输。可选地，RN1获取分类映射关系的方式为：宿主基站配置，或QAM配置，或获得在Un1口接收的数据包的PDU session(或GTP TEID)和/或QFI与分类标识之间的对应关系。另一种可能的方式是：在Un1口接收到的GTP数据包上携带分类标识，直接基于分类映射关系，将上述数据包承载在Un2口对应DRB上传输。
对于上行，RN2基于第二上行映射关系将在Un3/Uu口上收到的数据包经过处理(例如，进行GTP-U封装)后，通过Un2口发送给RN1。可选地，RN2在Un2口上发送的数据包携带第二自适应标识，用于RN1区分Un2口上的数据。
一种可选方式是，RN2在Un3/Uu口上接收数据包，将属于一个PDU session/SDAP实体的数据包，经过Un2口的GTP-U层处理，生成在Un2口发送的GTP数据包。可选地，RN2处理在Un3/Uu口接收的数据包，获得该数据包对应的PDU session和QoS flow，进而生成对应的GTP数据包，其中携带GTP TEID和QFI。随后RN2按照与下行类似的方式将该Un2口的GTP数据包承载在RN2的Un2口的DRB上传输，例如可以采用以下方式中的任一种或任意多种的组合：
方式一：把一个GTP隧道的数据映射到同一个DRB中传输；
方式二：将该GTP隧道中数据包按照数据流的QoS要求映射到多个DRB上。具体的，将该GTP-U中的一个或多个QoS flow映射到一个DRB上，上述一个或多个QoS flow的QoS要求与该DRB相匹配的。可选地，上述映射到多个DRB上属于同一个GTP-U隧道的QoS流使用相同的GTP TEID，用于令RN1识别和汇聚上述GTP隧道的数据包，并发送给核心网。
方式三：为该GTP隧道中的数据流分配一个类别标识(例如按照QoS要求映射到一个QCI，此时类别标识即为QCI)，多个数据流可以分配相同的类别标识，一个或多个类别标识映射到一个DRB上。可选地，在Un2口上传输该数据包时，携带该类别标识。可选地，该类别标识携带在Un2口上的GTP数据包上(例如用DSCP代表QCI)。可选地，RN2基于PDU session(或GTP TEID)和/或QFI与分类标识之间的对应关系(简称为分类映射关系，可选地，该对应关系可能是与一个RN/UE对应的)，获知数据包对应的分类标识，从而基于分类标识与Un2口的DRB的对应关系，将该数据包承载在该DRB中传输。可选地，RN2获取分类映射关系的方式为：宿主基站配置，或QAM配置，或获得在Un1口接收的数据包的PDU session(或GTP TEID)和/或QFI与分类标识之间的对应关系。需要说明的是，同一会话连接的Un1的GTP隧道与Un2的GTP隧道可能具有不同的TEID和/或IP地址，RN1将在其中一个无线接口收到的GTP数据包在另一个无线接口进行转发的过程中，需要将收到的GTP数据包进行处理后生成在另一个无线接口发送的GTP数据包。示例性的，处理过程包括更改GTP TEID和/或IP地址等。例如，对于一个PDU session，Un1口的下行TEID和/或IP地址由宿主基站分配，并告知给RN1，Un1口 的上行TEID和/或IP地址由RN1分配的，并告知宿主基站；Un2的下行TEID和/或IP地址由RN1分配的，并告知给RN2，Un2的上行TEID和/或IP地址由RN2分配的，并告知给RN1；从而RN1获知了该PDU session的Un1口和Un2口的上下行TEID和/或IP地址。
图29示出了一种Un1无线接口和Un2无线接口的数据传输过程的示意图，一个会话连接中的不同数据流可以映射到不同的Un1口DRB中；不同UE/RN的数据流可以映射到同一个Un1口DRB。对应Un1口的方式二(上下行类似)。类似的，一个会话连接中的不同数据流可以映射到不同的Un2口DRB中；不同UE/RN的数据流可以映射到同一个Un2口DRB。上述数据流到无线接口DRB的映射关系无需相同，上行可以分别由RN1和RN2进行。
图30示出了一种数据传输过程中RN2内部以及RN1内部的数据包映射过程的示意图。
RN2的基站部分在Un3口接收上述上行数据，基于承载上行数据的DRB信息和数据包上的QFI信息，获知上述上行数据对应的PDU session，从而生成GTP数据包，该GTP数据包上携带GTP TEID和QFI。一种可选的方式是，RN2基于分类映射关系关系在上述数据包上打上类型标识(可选地，类型标识可以携带在IP层，例如用DSCP标识体现，即类型标识与DSCP之间具有对应关系)；RN2的UE部分读取类型标识，基于第二上行映射关系，将上述GTP数据包承载在Un2口发送。另一种可选的方式是，RN2基于第二上行映射关系在上述数据包上打上DRB标识(可选地，DRB标识可以携带在IP层，例如用DSCP标识体现，即DRB标识与DSCP标识之间具有对应关系)，RN2的UE部分读取DRB标识，将上述GTP数据包承载在Un2口的对应的DRB上发送。可选地，上述类型标识/DRB标识与DSCP标识之间的对应关系可以为RN2内部定义，用于RN2的基站部分和UE部分进行对应与解读。可选地，上述类型标识/DRB标识可以继续携带在Un2发送的上行数据包中，用于RN1决定将在Un2收到的数据，通过Un1口的那个DRB发送给宿主基站，例如将上述标识做为第一映射关系的输入信息。可选地，上述类型标识/DRB标识可以继续携带在IP层(例如一DSCP的形式，此时上述标识与DSCP标识之间的对应关系，RN1也需要获知。RN1获知的方法可以为宿主基站配置，OAM配置，或者通过协议规定，RN1默认使用协议规定的对应关系。可选地，RN2获知方式类似，即为宿主基站配置，OAM配置，RN1配置，或者通过协议规定，RN2默认使用协议规定的对应关系)。
RN1在Un2口收到上行数据包后在Un1口发送的动作与图26中类似。不同之处在于，RN1还可以直接基于在Un2口上收到的上行数据包中的信息按照第一映射关系，将上述上行数据包中的数据承载在Un1口的DRB中发送。示例性的，RN1在Un2口上收到GTP数据包，对其处理(例如更改其中的GTP TEID和/或IP地址等)后生成在Un1口发送的GTP数据包。按照在Un2口上收到的数据包上携带的类型标识/DRB标识，将上述GTP数据包在Un1口的对应的DRB上传输。例如，基于类型标识和第一上行映射关系，确定Un1口的DRB；或者基于DRB标识和第一上行映射关系，确定Un1口的DRB。(4)Un3/Uu无线接口
协议栈：在Un3/Uu口，RN2与RN3/UE具有对等的协议层，具体包含：SDAP层， PDCP层，RLC层，MAC层，以及PHY层。
可选地，该Un口的协议栈还包含自适应层功能，用于添加和/或解析自适应标识。该自适应功能可以包含于现有的协议层，例如SDAP层/PDCP层/RLC层/MAC层/PHY层；或者自适应功能可以单独部署在一个协议层中，例如称为自适应(Adaptation，简称Adapt)层。
可选地，自适应层可以部署在SDAP层之上，或者SDAP层与PDCP层之间，或者部署在PDCP层与RLC层之间，或者部署在RLC层与MAC层之间，或者部署在MAC与PHY层之间。在Un3口区分数据类型的方法以及自适应标识的相关描述参见之前的Un2口和第二自适应标识的描述，在此不再赘述。
可选地，对于自适应功能，若RN3没有开启基站模块为UE提供服务，此时该功能可以不启用，即无需进行额外标识。
对于下行，RN2将在Un2口收到的属于一个PDU session的数据包汇聚，通过Un3/Uu口对应的SDAP层处理后，承载在Un3/Uu的DRB上发送个RN3/UE。
RN2通过控制面RRC消息为RN3/UE配置无线接口的DRB，同时将上行各个PDU session里的QoS flow与DRB的映射关系告诉RN3/UE。
对于上行，RN3/UE基于PDU session(以及QoS flow)与DRB的对应关系，将QoS flow放在对应DRB中发送给RN2。RN2将在Un3/Uu口通过一个SDAP实体收到的属于一个PDU session的数据包，经过处理后，转换为在Un2口发送的GTP数据包，通过Un2口发送给RN1。
图31示出了根据本申请实施例的L3协议栈用户面架构2的另一示意图。其中，Un1口和Un2口的协议栈不包含GTP-U协议层，通过自适应标识区分承载在Un1口/Un2口的属于不同节点的数据。
(1)NG-U接口
宿主基站与为RN服务的核心网用户面节点的协议栈对等，具体的协议栈组成与现有技术类似，在此不再赘述。
RN3/UE接入RN2后，通过控制面流程请求建立会话连接(例如PDU session)和/或与该会话连接对应的数据流(例如QoS flow)，核心网为该RN3/UE配置NG-U接口上的数据传输隧道，并将该隧道建立信息通过NG-C的NGAP消息发送给宿主基站。
示例性的，上述控制面流程中涉及如下信息交互：在NG-C接口，核心网将该RN3/UE相关的以下信息中的任一种或任意多种的组合通过NGAP消息发送给宿主基站：会话连接的标识信息，数据流的标识信息，QoS参数，NG-U隧道建立信息。其中NG-U隧道建立信息可能包含以下信息中的任一种或任意多种的组合：GTP-U TEID，IP地址，以及端口号等信息。
(2)Un1无线接口：无GTP-U封装，与图24所示的实施例类似
协议栈：在Un1口，宿主基站与RN1具有对等的协议层，具体包含：SDAP层(可选地，即可以配置为透传)，PDCP层，RLC层，MAC层，以及PHY层。该Un1口的协议栈还包含自适应层功能，用于添加和/或解析第一自适应标识。该自适应功能可以包含于现有的协议层，例如SDAP层/PDCP层/RLC层/MAC层/PHY层；或者自适应功能可以单独部署在一个协议层中，例如称为自适应(Adaptation，简称Adapt)层。
可选地，自适应层可以部署在SDAP层之上，或者部署在SDAP层与PDCP层之间，或者部署在PDCP层与RLC层之间，或者部署在RLC层与MAC层之间，或者部署在MAC与PHY层之间。如之前实施例中介绍，第一自适应标识可以包含以下信息中的任一种或任意多种的组合：二跳RN标识和/或跳数信息(用于识别RN2)，第二UE标识(用于识别RN2服务的UE)，一跳RN标识和/或跳数信息(用于识别RN1)，第一UE标识(用于识别RN1服务的UE)，三跳RN标识和/或跳数信息(用于识别RN3)，第三UE标识(用于识别多跳RN服务的UE)，NGAP消息类型，XnAP消息类型，GTP-U消息类型(属于NG-U或Xn-U)，用户面数据包类型，以及用户面数据包信息。其中，用户面数据包信息包含以下信息中的任一种或任意多种的组合：会话连接信息，数据流信息，分类标识信息，该数据包在第二无线接口传输时所在的无线承载的信息，该数据包在第二无线接口传输时所用的逻辑信道的信息，该数据包在第一无线接口传输时所在的无线承载的信息，该数据包在第一无线接口传输时所用的逻辑信道的信息。
对于下行，宿主基站将在NG-U接收的GTP隧道中的数据映射到为RN1在Un1口建立的DRB传输。
可选地，将该NG-U口的GTP隧道的数据包处理(例如经过Un1口和Un2口的协议栈处理)后，承载在为RN1在Un1口建立的DRB上传输，可以采用以下方式中的任一种或任意多种的组合：
方式一：把一个GTP隧道的数据映射到同一个DRB中传输；
方式二：将该GTP隧道中数据包按照数据流的QoS要求映射到多个DRB上。具体的，将该GTP-U中的一个或多个QoS flow映射到一个DRB上，上述一个或多个QoS flow的QoS要求与该DRB相匹配的。可选地，上述映射到多个DRB上属于同一个GTP-U隧道的QoS流的数据需要携带第一自适应标识，用于令RN1识别和汇聚上述GTP隧道的数据包，并发送到Un2口与该GTP隧道对应的会话连接的SDAP实体上。
方式三：为该GTP隧道中的数据流分配一个类别标识(例如按照QoS要求映射到一个QCI，此时类别标识即为QCI)，多个数据流可以分配相同的类别标识，一个或多个类别标识映射到一个DRB上。可选地，在Un2上传输该数据包时，在第一自适应标识中包含该类别标识。
对于上行，RN1基于第一上行映射关系将在Un2口上收到的数据包经过处理后，通过Un1口发送给宿主基站。可选地，RN1在Un2口上发送的数据包携带第一自适应标识，用于宿主基站区分Un1口上的数据。
一种可选方式是，RN1在Un2上接收的数据包，获得该数据包对应的PDU session和QoS flow，进而生成对应的在Un1口发送的数据包，其中携带第一自适应标识。随后RN1按照与下行类似的方式将该Un2口的数据包承载在RN1的Un1口的DRB上传输，例如可以采用以下方式中的任一种或任意多种的组合：
方式一：把一个PDU session的数据映射到同一个DRB中传输；
方式二：将该PDU session数据包按照数据流的QoS要求映射到多个DRB上。具体的，将该PDU session的一个或多个QoS flow映射到一个DRB上，上述一个或多个QoS flow的QoS要求与该DRB相匹配的。可选地，上述映射到多个DRB上属于同一个PDU session的数据包上携带第一自适应标识，用于令宿主基站识别和汇聚上述PDU session的 数据包，通过同一个NG-U上的GTP隧道发送给核心网。
方式三：为该PDU session的数据流分配一个类别标识(例如按照QoS要求映射到一个QCI，此时类别标识即为QCI)，多个数据流可以分配相同的类别标识，一个或多个类别标识映射到一个DRB上。可选地，在Un1口上传输该数据包时，携带该类别标识。可选地，该类别标识包含与第一自适应标识中。可选地，RN1基于PDU session和/或QFI与分类标识之间的对应关系(简称为分类映射关系，可选地，该对应关系可能是与一个RN/UE对应的)，获知数据包对应的分类标识，从而基于分类标识与Un1口的DRB的对应关系，将该数据包承载在该DRB中传输。可选地，RN1获取分类映射关系的方式为：宿主基站配置，或QAM配置，或获得在Un1口接收的数据包的PDU session和/或QFI与分类标识之间的对应关系。
(3)Un2无线接口：无GTP-U封装(数据直接作为Adap./SDAP的SDU)
协议栈：在Un2口，RN1与RN2具有对等的协议层，具体包含：SDAP层(可选地，即可以配置为透传)，PDCP层，RLC层，MAC层，以及PHY层。该Un2口的协议栈还包含自适应层功能，用于添加和/或解析第二自适应标识。该自适应功能可以包含于现有的协议层，例如SDAP层/PDCP层/RLC层/MAC层/PHY层；或者自适应功能可以单独部署在一个协议层中，例如称为自适应(Adaptation，简称Adapt)层。
可选地，自适应层可以部署在SDAP层之上，或者部署在SDAP层与PDCP层之间，或者部署在PDCP层与RLC层之间，或者部署在RLC层与MAC层之间，或者部署在MAC与PHY层之间。如之前实施例中介绍，该第二自适应标识可以包含以下信息中的任一种或任意多种的组合：二跳RN标识和/或跳数信息(用于识别RN2)，第二UE标识(用于识别RN2服务的UE)，一跳RN标识和/或跳数信息(用于识别RN1)，第一UE标识(用于识别RN1服务的UE)，三跳RN标识和/或跳数信息(用于识别RN3)，第三UE标识(用于识别三跳RN服务的UE)，NGAP消息类型，XnAP消息类型，RRC消息类型，用户面数据包类型，以及用户面数据包信息。其中，用户面数据包信息包含以下信息中的任一种或任意多种的组合：会话连接信息，数据流信息，分类标识信息，该数据包在第三无线接口传输时所在的无线承载的信息，该数据包在第三无线接口传输时所用的逻辑信道的信息，该数据包在第二无线接口传输时所在的无线承载的信息，该数据包在第二无线接口传输时所用的逻辑信道的信息，该数据包在第一无线接口传输时所在的无线承载的信息，该数据包在第一无线接口传输时所用的逻辑信道的信息。
对于下行，RN1将在Un1口上收到的数据包经过处理后，通过Un2口发送给RN2。可选地，RN1在Un2口上发送的数据包携带第二自适应标识，用于RN2区分Un2口上的数据。
一种可选方式是，RN1在Un1上接收的数据包，获得该数据包对应的PDU session和QoS flow，进而生成对应的在Un2口发送的数据包，其中携带第二自适应标识。随后RN1将该Un1口的数据包承载在RN2的Un2口的DRB上传输，例如可以采用以下方式中的任一种或任意多种的组合：
方式一：把一个PDU session的数据映射到同一个DRB中传输；
方式二：将该PDU session数据包按照数据流的QoS要求映射到多个DRB上。具体的，将该PDU session的一个或多个QoS flow映射到一个DRB上，上述一个或多个QoS  flow的QoS要求与该DRB相匹配的。可选地，上述映射到多个DRB上属于同一个PDU session的数据包上携带第二自适应标识，用于令RN2识别和汇聚上述PDU session的数据包，经过该PDU session对应的SDAP处理后在Un3/Uu口发送给RN3/UE。
方式三：基于数据流的分类标识映射到对应的DRB中传输。一种可能的方式是：为该PDU session的数据流分配一个类别标识(例如按照QoS要求映射到一个QCI，此时类别标识即为QCI)，多个数据流可以分配相同的类别标识，一个或多个类别标识映射到一个DRB上。可选地，在Un2口上传输该数据包时，携带该类别标识。可选地，该类别标识携带在Un2口上的第二自适应标识中。可选地，RN1基于PDU session和/或QFI与分类标识之间的对应关系(简称为分类映射关系，可选地，该对应关系可能是与一个RN/UE对应的)，获知数据包对应的分类标识，从而基于分类标识与Un2口的DRB的对应关系，将该数据包承载在该DRB中传输。可选地，RN1获取分类映射关系的方式为：宿主基站配置，或QAM配置，或获得在Un1口接收的数据包的PDU session和/或QFI与分类标识之间的对应关系。另一种可能的方式是：在Un1口接收到的数据包的第一自适应标识中携带分类标识，直接基于分类映射关系，将上述数据包承载在对应DRB上传输。可选地，在Un2口上传输该数据包时，携带该类别标识。可选地，该类别标识包含与第二自适应标识中。可选地，RN1基于PDU session和/或QFI与分类标识之间的对应关系(简称为分类映射关系，可选地，该对应关系可能是与一个RN/UE对应的)，获知数据包对应的分类标识，从而基于分类标识与Un2口的DRB的对应关系(例如基于第一下行映射关系获知)，将该数据包承载在该DRB中传输。可选地，RN1获取分类映射关系的方式为：宿主基站配置，或QAM配置，或获得在Un1口接收的数据包的PDU session和/或QFI与分类标识之间的对应关系。
对于上行，RN2基于第二上行映射关系将在Un3/Uu口上收到的数据包经过处理后，通过Un2口发送给RN1。可选地，RN2在Un2口上发送的数据包携带第二自适应标识，用于RN1区分Un2口上的数据。
一种可选方式是，RN2在Un/3Uu上接收的数据包，获得该数据包对应的PDU session和QoS flow，进而生成对应的在Un2口发送的数据包，其中携带第二自适应标识。随后RN2按照与下行类似的方式将该Un3/Uu口的数据包承载在RN2的Un2口的DRB上传输，例如可以采用以下方式中的任一种或任意多种的组合：
方式一：把一个PDU session的数据映射到同一个DRB中传输；
方式二：将该PDU session数据包按照数据流的QoS要求映射到多个DRB上。具体的，将该PDU session的一个或多个QoS flow映射到一个DRB上，上述一个或多个QoS flow的QoS要求与该DRB相匹配的。可选地，上述映射到多个DRB上属于同一个PDU session的数据包上携带第二自适应标识，用于令RN1识别和汇聚上述PDU session的数据包，通过该PDU session对应的SDAP层处理后发送给核心网。
方式三：为该PDU session的数据流分配一个类别标识(例如按照QoS要求映射到一个QCI，此时类别标识即为QCI)，多个数据流可以分配相同的类别标识，一个或多个类别标识映射到一个DRB上。可选地，在Un2口上传输该数据包时，携带该类别标识。可选地，该类别标识包含与第二自适应标识中。可选地，RN2基于PDU session和/或QFI与分类标识之间的对应关系(简称为分类映射关系，可选地，该对应关系可能是与一个 RN/UE对应的)，获知数据包对应的分类标识，从而基于分类标识与Un2口的DRB的对应关系，将该数据包承载在该DRB中传输。可选地，RN2获取分类映射关系的方式为：宿主基站配置，RN1配置，或QAM配置，或获得在Un2口接收的数据包的PDU session和/或QFI与分类标识之间的对应关系。
(4)Un3/Uu无线接口
协议栈：在Un3/Uu口，RN2与RN3/UE具有对等的协议层，具体包含：SDAP层，PDCP层，RLC层，MAC层，以及PHY层。可选地，该Un口的协议栈还包含自适应层功能，用于添加和/或解析自适应标识。该自适应功能可以包含于现有的协议层，例如SDAP层/PDCP层/RLC层/MAC层/PHY层；或者自适应功能可以单独部署在一个协议层中，例如称为自适应(Adaptation，简称Adapt)层。可选地，自适应层可以部署在SDAP层之上，或者SDAP层与PDCP层之间，或者部署在PDCP层与RLC层之间，或者部署在RLC层与MAC层之间，或者部署在MAC与PHY层之间。在Un3口区分数据类型的方法以及自适应标识的相关描述参见之前的Un2口和第二自适应标识的描述，在此不再赘述。可选地，对于自适应功能，若RN3没有开启基站模块为UE提供服务，此时该功能可以不启用，即无需进行额外标识。
对于下行，RN2将在Un2口收到的属于一个PDU session的数据包汇聚，通过Un3/Uu口对应的SDAP层处理后，承载在Un3/Uu的DRB上发送个RN3/UE。
RN2通过控制面RRC消息为RN3/UE配置无线接口的DRB，同时将上行各个PDU session里的QoS flow与DRB的映射关系告诉RN3/UE。
对于上行，RN3/UE基于PDU session(以及QoS flow)与DRB的对应关系，将QoS flow放在对应DRB中发送给RN2。RN2将在Un3/Uu口通过一个SDAP实体收到的属于一个PDU session的数据包，经过处理后，转换为在Un2口发送的数据包，通过Un2口发送给RN1。
图32示出了根据本申请实施例的L3协议栈用户面架构1-B的另一示意图。
(1)NG-U接口，与L3协议栈用户面架构1-B中处理类似
宿主基站与为RN服务的核心网用户面节点的协议栈对等，具体的协议栈组成与现有技术类似，在此不再赘述。
RN3/UE接入RN2后，通过控制面流程请求建立会话连接(例如PDU session)和/或与该会话连接对应的数据流(例如QoS flow)，核心网为该RN3/UE配置NG-U接口上的数据传输隧道，并将该隧道建立信息通过NG-C的NGAP消息发送给宿主基站。
示例性的，上述控制面流程中涉及如下信息交互：在NG-C接口，核心网将该RN3/UE相关的以下信息中的任一种或任意多种的组合通过NGAP消息发送给宿主基站：会话连接的标识信息，数据流的标识信息，QoS参数，NG-U隧道建立信息。其中NG-U隧道建立信息可能包含以下信息中的任一种或任意多种的组合：GTP-U TEID，IP地址，以及端口号等信息。
(2)Un1无线接口：传输GTP-U数据包(数据进行GTP-U封装后作为Adap./SDAP的SDU)，RN1不解读GTP-U数据包
协议栈：在Un1口，宿主基站具有以下协议层：GTP-U层，UDP层(可选地)，IP层(可选地)，SDAP层(可选地，即可以配置为透传)，PDCP层，RLC层，MAC层， 以及PHY层。其中，GTP-U层，UDP层(可选地)，IP层(可选地)与RN2对等；PDCP层，RLC层，MAC层，以及PHY层与RN1对等。上述GTP-U层(还可以结合UDP层和/或IP层)可以用于区分承载在Un1口(上行)或Un2口(下行)上同一个DRB中的数据，例如一个GTP隧道(可选地，通过一对TEID识别，分别对应上行和下行)对应一个UE的会话连接。可选地，该Un1口的协议栈还包含自适应层功能，用于添加和/或解析第一自适应标识。自适应层的部署方式、在Un1口区分数据类型的方法以及第一自适应标识的用途与L3协议栈用户面架构1-A中处理类似，在此不再赘述。
对于下行，宿主基站将在NG-U接收的GTP隧道映射为在Un1口发送的GTP隧道。示例性的，宿主基站为对应的会话连接分配NG-U上的GTP TEID，通过NG-C的NGAP消息告知核心网，核心网传输该会话连接的下行数据时，采用该GTP TEID进行标识，可选地，在GTP-U数据包上携带QoS flow的标识。可选地，将该Un1口的GTP隧道承载在为RN1在Un1口建立的DRB上传输可以采用以下方式中的任一种或任意多种的组合：
方式一：把一个GTP隧道的数据映射到同一个DRB中传输；
方式二：将该GTP隧道中数据包按照数据流的QoS要求映射到多个DRB上。具体的，将该GTP-U中的一个或多个QoS flow映射到一个DRB上，上述一个或多个QoS flow的QoS要求与该DRB相匹配的。可选地，上述映射到多个DRB上属于同一个GTP-U隧道的QoS流使用相同的GTP TEID，用于令RN2识别和汇聚上述GTP隧道的数据包，并关联到该会话连接对应的Un3/Uu口的PDU session/SDAP实体。
方式三：为该GTP隧道中的数据流分配一个类别标识(例如按照QoS要求映射到一个QCI，此时类别标识即为QCI)，多个数据流可以分配相同的类别标识，一个或多个类别标识映射到一个DRB上。在Un1口上传输该数据包时，携带该类别标识。可选地，该类别标识携带在Un1口上的GTP数据包上(例如用DSCP代表QCI)；或者携带在第一自适应标识中。
对于上行，RN1基于第一上行映射关系将在Un2口上收到的数据包经过处理(例如，经过Un2口协议栈和Un1口协议栈处理)后，通过Un1口发送给宿主基站。可选地，RN1在Un1口上发送的数据包携带第一自适应标识，用于宿主基站区分Un1口上的数据。
一种可选方式是，RN1将在Un2上接收的数据包，按照PDU session进行汇聚，生成在Un1口发送的数据包。可选地，RN1处理在Un2口接收的数据包，基于数据包上携带的信息(例如第二自适应标识)，获得该数据包对应的PDU session和QoS flow，进而生成对应的Un1口数据包。另一种可选的方式是：不进行PDU session的汇聚，直接基于Un2上收到的数据包携带的信息，找到对应的Un1口DRB。随后RN1按照与下行类似的方式将生成的数据包承载在RN1的Un1口的DRB上传输，例如可以采用以下方式中的任一种或任意多种的组合：
方式一：把一个PDU session的数据映射到同一个DRB中传输；
方式二：将该PDU session中数据包按照数据流的QoS要求映射到多个DRB上。具体的，将该PDU session中的一个或多个QoS flow映射到一个DRB上，上述一个或多个QoS flow的QoS要求与该DRB相匹配的。
方式三：基于数据流的分类标识映射到对应的DRB中传输。一种可能的方式是：为该PDU session的数据流分配一个类别标识(例如按照QoS要求映射到一个QCI，此时类 别标识即为QCI)，多个数据流可以分配相同的类别标识，一个或多个类别标识映射到一个DRB上。可选地，在Un1口上传输该数据包时，携带该类别标识。可选地，该类别标识携带在第一自适应标识中。可选地，RN1基于PDU session(或GTP TEID)和/或QFI与分类标识之间的对应关系(简称为分类映射关系，可选地，该对应关系可能是与一个RN/UE对应的)，获知数据包对应的分类标识，从而基于分类标识与Un1口的DRB的对应关系，将该数据包承载在该DRB中传输。可选地，RN1获取分类映射关系的方式为：宿主基站配置，或QAM配置，或获得在Un1口接收的数据包的PDU session和/或QFI与分类标识之间的对应关系。另一种可能的方式是：在Un2口接收到的数据包上携带分类标识(例如第二自适应标识)，直接基于分类映射关系，将上述数据包承载在对应DRB上传输。
(3)Un2无线接口：传输GTP-U数据包(下行数据RN1透传宿主基站封装的GTP数据包，上行数据由RN2进行GTP-U封装后作为Adap./SDAP的SDU)
协议栈：在Un2口，RN2具有以下协议层：GTP-U层，UDP层(可选地)，IP层(可选地)，SDAP层(可选地，即可以配置为透传)，PDCP层，RLC层，MAC层，以及PHY层。其中，GTP-U层，UDP层(可选地)，IP层(可选地)与宿主基站对等；PDCP层，RLC层，MAC层，以及PHY层与RN1对等。上述GTP-U层(还可以结合UDP层和/或IP层)可以用于区分承载在Un1口(上行)或Un2口(下行)上同一个DRB中的数据，例如一个GTP隧道(可选地，通过一对TEID识别，分别对应上行和下行)对应一个UE的会话连接。可选地，该Un2口的协议栈还包含自适应层功能，用于添加和/或解析第二自适应标识。自适应层的部署方式、在Un2口区分数据类型的方法以及第二自适应标识的用途与L3协议栈用户面架构1-A中处理类似，在此不再赘述。
对于下行，一种可选的方式是RN1将在Un1接收的数据进行汇聚，重新映射(例如基于第二下行映射关系)到Un2口的DRB。示例性的，RN1在Un1口接收数据包，并基于数据包携带的信息(例如第一自适应标识)，将属于同一个会话连接的数据包聚合，进而承载在Un2口的DRB上传输。另一种方式是，基于Un1口DRB与Un2口DRB的对应关系(例如第二下行映射关系)，将Un2口的数据包承载在DRB中发送。
可选地，在Un2口数据包上携带第二自适应标识。
可选地，将该Un2口的数据包承载在为RN2在Un2口建立的DRB上传输，可以采用以下方式中的任一种或任意多种的组合：
方式一：把一个PDU session的数据映射到同一个DRB中传输；
方式二：将该PDU session中数据包按照数据流的QoS要求映射到多个DRB上。具体的，将该PDU session中的一个或多个QoS flow映射到一个DRB上，上述一个或多个QoS flow的QoS要求与该DRB相匹配的。
方式三：基于数据流的分类标识映射到对应的DRB中传输。一种可能的方式是：为该PDU session中的数据流分配一个类别标识(例如按照QoS要求映射到一个QCI，此时类别标识即为QCI)，多个数据流可以分配相同的类别标识，一个或多个类别标识映射到一个DRB上。可选地，在Un2口上传输该数据包时，携带该类别标识。可选地，该类别标识携带在Un2口上第二自适应标识中。可选地，RN1基于PDU session和/或QFI与分类标识之间的对应关系(简称为分类映射关系，可选地，该对应关系可能是与一个RN/UE 对应的)，获知数据包对应的分类标识，从而基于分类标识与Un2口的DRB的对应关系，将该数据包承载在该DRB中传输。可选地，RN1获取分类映射关系的方式为：宿主基站配置，或QAM配置，或获得在Un1口接收的数据包的PDU session和/或QFI与分类标识之间的对应关系。另一种可能的方式是：在Un1口接收到的数据包上携带分类标识，直接基于分类映射关系，将上述数据包承载在Un2口对应DRB上传输。
对于上行，RN2基于第二上行映射关系将在Un3/Uu口上收到的数据包经过处理(例如，进行GTP-U封装)后，通过Un2口发送给RN1。可选地，RN2在Un2口上发送的数据包携带第二自适应标识，用于RN1区分Un2口上的数据。
一种可选方式是，RN2在Un3/Uu口上接收数据包，将属于一个PDU session/SDAP实体的数据包，经过Un2口的GTP-U层处理，生成在Un2口发送的GTP数据包。可选地，RN2处理在Un3/Uu口接收的数据包，获得该数据包对应的PDU session和QoS flow，进而生成对应的GTP数据包，其中携带GTP TEID和QFI。随后RN2按照与下行类似的方式将该Un2口的GTP数据包承载在RN2的Un2口的DRB上传输，例如可以采用以下方式中的任一种或任意多种的组合：
方式一：把一个GTP隧道的数据映射到同一个DRB中传输；
方式二：将该GTP隧道中数据包按照数据流的QoS要求映射到多个DRB上。具体的，将该GTP-U中的一个或多个QoS flow映射到一个DRB上，上述一个或多个QoS flow的QoS要求与该DRB相匹配的。
方式三：为该GTP隧道中的数据流分配一个类别标识(例如按照QoS要求映射到一个QCI，此时类别标识即为QCI)，多个数据流可以分配相同的类别标识，一个或多个类别标识映射到一个DRB上。可选地，在Un2口上传输该数据包时，携带该类别标识。可选地，该类别标识携带在Un2口上的GTP数据包上(例如用DSCP代表QCI)，用于宿主基站读取。可选地，该类别标识携带在Un2口的第二自适应标识中，用于RN1读取。可选地，RN2基于PDU session(或GTP TEID)和/或QFI与分类标识之间的对应关系(简称为分类映射关系，可选地，该对应关系可能是与一个RN/UE对应的)，获知数据包对应的分类标识，从而基于分类标识与Un2口的DRB的对应关系，将该数据包承载在该DRB中传输。可选地，RN2获取分类映射关系的方式为：宿主基站配置，RN1配置，或QAM配置，或获得在Un2口接收的数据包的PDU session(或GTP TEID)和/或QFI与分类标识之间的对应关系。
图33示出了一种数据传输过程中RN2内部以及RN1内部的数据包映射过程的示意图。
RN2的基站部分在Un3/Uu口接收上述上行数据，基于承载上行数据的DRB信息和数据包上的QFI信息，获知上述上行数据对应的PDU session，从而生成GTP数据包，该GTP数据包上携带GTP TEID和QFI。一种可选的方式是，RN2基于分类映射关系关系在上述数据包上打上类型标识(可选地，类型标识可以携带在IP层，例如用DSCP标识体现，即类型标识与DSCP之间具有对应关系；和/或该类型标识可以携带在第二自适应标识中)；RN2的UE部分读取类型标识，基于第二上行映射关系，将上述GTP数据包承载在Un2口发送。另一种可选的方式是，RN2基于第二上行映射关系在上述数据包上打上DRB标识(可选地，DRB标识可以携带在IP层，例如用DSCP标识体现，即DRB标 识与DSCP标识之间具有对应关系；和/或该DRB标识可以携带在第二自适应标识中)，RN2的UE部分读取DRB标识，将上述GTP数据包承载在Un2口的对应的DRB上发送。可选地，上述类型标识/DRB标识与DSCP标识之间的对应关系可以为RN2内部定义，用于RN2的基站部分和UE部分进行对应与解读。可选地，上述类型标识/DRB标识可以继续携带在Un2发送的上行数据包中，用于RN1决定将在Un2收到的数据，通过Un1口的那个DRB发送给宿主基站，例如将上述标识做为第一映射关系的输入信息。可选地，上述类型标识/DRB标识可以继续携带Un1口，例如携带在第一自适应标识中。
RN1在Un2口收到上行数据包后在Un1口发送的动作与图23中类似。不同之处在于，RN1不会将上述GTP数据包递交给GTP-U协议层解析，因此不能使用GTP包头的信息确定Un1口DRB。因此，RN1可以基于第二自适应标识的信息决定Un1口的DRB(基于第二上行映射关系)，或者基于Un2口的DRB与Un1口的DRB的映射关系决定Un1口的DRB(基于第二上行映射关系)。
(4)Un3/Uu无线接口
协议栈：在Un3/Uu口，RN2与RN3/UE具有对等的协议层，具体包含：SDAP层，PDCP层，RLC层，MAC层，以及PHY层。
可选地，该Un口的协议栈还包含自适应层功能，用于添加和/或解析自适应标识。该自适应功能可以包含于现有的协议层，例如SDAP层/PDCP层/RLC层/MAC层/PHY层；或者自适应功能可以单独部署在一个协议层中，例如称为自适应(Adaptation，简称Adapt)层。
可选地，自适应层可以部署在SDAP层之上，或者SDAP层与PDCP层之间，或者部署在PDCP层与RLC层之间，或者部署在RLC层与MAC层之间，或者部署在MAC与PHY层之间。在Un3口区分数据类型的方法以及自适应标识的相关描述参见之前的Un2口和第二自适应标识的描述，在此不再赘述。
可选地，对于自适应功能，若RN3没有开启基站模块为UE提供服务，此时该功能可以不启用，即无需进行额外标识。
对于下行，RN2将在Un2口收到的属于一个PDU session的数据包汇聚，通过Un3/Uu口对应的SDAP层处理后，承载在Un3/Uu的DRB上发送个RN3/UE。
RN2通过控制面RRC消息为RN3/UE配置无线接口的DRB，同时将上行各个PDU session里的QoS flow与DRB的映射关系告诉RN3/UE。
对于上行，RN3/UE基于PDU session(以及QoS flow)与DRB的对应关系，将QoS flow放在对应DRB中发送给RN2。RN2将在Un3/Uu口通过一个SDAP实体收到的属于一个PDU session的数据包，经过处理后，转换为在Un2口发送的GTP数据包，通过Un2口发送给RN1。
各种协议栈的一种组合方式
图34示出了根据本申请实施例的协议栈组合的示意图。
如图34所示，在一个无线网络中：RN1接入宿主基站，建立与宿主基站之间的Un1口；RN2接入RN1，建立与RN1之间的Un2口；UE1接入RN1，建立与RN1的Uu1口；UE2接入RN2，建立与RN2的Uu2口。需要说明的是，还可以有三跳RN接入RN2，UE接入三跳RN等情况，可以参考RN2和RN1的行为，在此不再赘述。
其中Un1，Un2，Uu1，以及Uu2接口控制面/用户面的协议栈均可分别采用上述各种控制面/用户面协议栈候选方式介绍的某种方式，RN1和RN2对数据包进行转发时可以基于数据包的类型(控制面或用户面)/属性信息确定使用的映射关系。
示例性的，图35示出了根据本申请实施例的接入RN2的UE2的控制面消息的流向示意图。对于UE2的控制面消息采用控制面协议栈1-A-B，即上行，RN2为UE2生成NGAP消息，并承载在Un2口的DRB(可选的，也可以为SRB上)上，发送给RN1，RN1不解析NGAP消息，将其承载在Un1口的DRB上发送，由宿主基站解析该NGAP消息。下行，采用对应的方式，即宿主基站为该UE2生成NGAP消息，并在Un1口的DRB发送给RN1，RN1不解析，仅做转发，由RN2在Un2口上接收后解析。
示例性的，图36示出了根据本申请实施例的接入RN2的UE2的用户面数据的流向示意图。对于UE2的用户面数据，采用用户面协议栈1-B，即上行，RN2为UE2的数据进行GTP封装，并承载在Un2的DRB上，发送给RN1，RN1不解析GTP数据包，并将GTP数据包承载在Un1口的DRB上发送给宿主基站，由宿主基站解析GTP数据包。下行采用对应的方式，即宿主基站为该UE2的数据进行GTP封装，并承载在Un1的DRB上，发送给RN1，RN1不解析GTP数据包，将其承载在Un2的DRB上发送给RN2，由RN2解析该GTP数据包，进一步处理后发送给UE2。
示例性的，图37示出了根据本申请实施例的接入RN1的UE1的控制面消息的流向示意图。对于UE1的控制面消息，采用控制面协议栈1-A，即上行，RN1为UE1生成NGAP消息，并承载在Un1口的DRB(可选的，也可以为SRB上，即协议栈1-B)上，发送给宿主基站。下行，采用对应的方式，即宿主基站为该UE1生成NGAP消息，并在Un1口发送给RN1。
示例性的，图38示出了根据本申请实施例的接入RN1的UE1的用户面消息的流向示意图。对于UE1的用户面数据，采用用户面协议栈1，即上行，RN1为UE的数据进行GTP封装，并承载在Un1的DRB上，发送给宿主基站。下行采用对应的方式，即宿主基站为该UE1的数据进行GTP封装，并承载在Un1的DRB上，发送给RN1，RN1进一步处理后发送给UE。
需要说明的是，本申请中图4-7，9-18，24，27-28，31-32，34-38中所示的各个协议层均可以视为组成中继设备、网络设备的功能模块，这些功能模块可以是纯硬件实现、纯软件实现，或者软硬件组合的方式实现。
以上结合图1至图38，详细得描述了根据本申请实施例的传输方法，下面结合图39至图42，详细描述根据本申请实施例的中继节点。
图39示出了根据本申请实施例的中继节点900的示意性框图，如图39所示，该中继节点900包括：
处理模块910，用于生成第一数据；
所述处理模块还910用于根据所述第一数据的属性信息和第一映射关系，控制收发模块920通过第一无线接口向网络设备发送所述第一数据，所述第一无线接口为所述第一中继节点和所述网络设备之间进行数据传输的无线接口；
其中，所述第一映射关系为所述第一数据的属性信息与发送所述第一数据使用的无线承载之间的对应关系。
可选地，所述收发模块920通过第二无线接口接收第二中继节点发送的所述第一数据，所述第二无线接口为所述第一中继节点和所述第二中继节点之间进行数据传输的无线接口；
所述处理模块910还用于获取所述第一数据的属性信息，所述第一数据的属性信息包含以下信息中的至少一种：会话连接信息、数据流信息、所述第一无线接口的无线承载的信息、所述第二无线接口的无线承载的信息、消息类型以及所述第一数据所属节点的信息。
可选地，所述第一数据的消息类型为第一用户面数据时，
所述收发模块920通过所述第二无线接口接收所述第二中继节点发送的所述第一数据，所述处理模块910还用于将所述第一数据经过与所述第二中继节点对等的PHY协议层，MAC协议层，RLC协议层和PDCP协议层处理；
所述收发模块920通过所述第一无线接口向所述网络设备发送所述第一数据，所述处理模块910还用于将所述第一数据经过与所述网络设备对等的PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；
所述第一用户面数据为与所述第二中继节点连接的终端设备的数据。
可选地，所述第一数据为第一用户面数据时，
所述收发模块920通过所述第二无线接口接收所述第二中继节点发送的所述第一数据，所述处理模块910还用于将所述第一数据经过与所述第二中继节点对等的PHY协议层，MAC协议层，RLC协议层，PDCP协议层和GTP-U协议层处理；
所述收发模块920通过所述第一无线接口向所述网络设备发送第一数据，所述处理模块910还用于将所述第一数据经过与所述网络设备对等的GTP-U协议层，PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；
所述第一用户面数据为与所述第二中继节点连接的终端设备的数据。
可选地，所述第一数据为所述第一控制面数据时，
所述收发模块920通过所述第二无线接口接收所述第二中继节点发送的所述第一数据，所述处理模块910还用于将所述第一数据经过与所述第二中继节点对等的PHY协议层，MAC协议层，RLC协议层和PDCP协议层处理；
所述收发模块920通过第一无线接口向所述网络设备发送所述第一数据时，所述处理模块910还用于将所述第一数据经过与所述网络设备对等的PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；
所述第一控制面数据为与接入所述第二中继节点的终端设备相关的控制面信息。
可选地，所述收发模块920通过所述第二无线接口接收所述第二中继节点发送的所述第一数据时，所述处理模块910还用于将所述第一数据还经过与所述第二中继节点对等的NGAP协议层处理；
所述收发模块920通过所述第一无线接口向所述网络设备发送所述第一数据时，所述处理模块910还用于将所述第一数据还经过与所述网络设备对等的NGAP协议层处理。
可选地，所述收发模块920通过所述第二无线接口接收所述第二中继节点发送的所述第一数据时，所述处理模块910还用于将所述第一数据还经过与所述第二中继节点对等的RRC协议层处理；
所述收发模块920通过所述第一无线接口向所述网络设备发送所述第一数据时，所述 处理模块910还用于将所述第一数据还经过与所述网络设备对等的RRC协议层处理。
可选地，所述收发模块920通过第三无线接口接收终端设备发送的所述第一数据，所述第三无线接口为第一中继节点与所述终端设备通信的无线接口；
所述处理模块910还用于获取所述第一数据的属性信息，所述第一数据的属性信息包含以下信息中的至少一种：会话连接信息、数据流信息、所述第一无线接口的无线承载的信息、所述第三无线接口的无线承载的信息、消息类型以及所述终端设备的信息。
可选地，所述第一数据的消息类型为第二用户面数据时，
所述收发模块920通过所述第一无线接口向所述网络设备发送所述第一数据，所述处理模块910还用于将所述第一数据经过与所述网络设备对等的GTP-U协议层，PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；所述第二用户面数据为所述终端设备的数据。
可选地，所述第一数据为第二控制面数据时，
所述收发模块920通过所述第一无线接口向所述网络设备发送第一数据，所述处理模块910还用于将所述第一数据经过与所述网络设备对等的NGAP协议层，PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；所述第二控制面数据为与所述终端设备相关的控制面信息。
可选地，第一映射关系由第一中继节点确定；或者，
所述第一映射关系由所述网络设备或运营和管理实体OAM配置；或者，
所述第一中继节点在第一无线接口接收的所述第一数据时，所述第一数据携带用于获取所述第一映射关系的信息。
图40示出了根据本申请实施例的中继节点1000的示意性框图，如图40所示，该中继节点1000包括：
收发模块1010，用于接收终端设备发送的第二数据；
处理模块1020，用于根据所述第二数据的属性信息和第二映射关系，通过第二无线接口向第一中继节点发送所述第二数据，所述第二无线接口为所述第一中继节点和第二中继节点之间进行数据传输的无线接口；
所述第二映射关系为第二数据的属性信息与发送所述第二数据使用的无线承载之间的对应关系；
所述第二数据的属性信息包含以下信息中的至少一种：会话连接信息、数据流信息、所述第二无线接口的无线承载的信息、消息类型以及所述终端设备的信息。
可选地，所述第二数据的消息类型为第一用户面数据时，
所述收发模块1010通过所述第二无线接口向所述第一中继节点发送所述第二数据，所述处理模块1020还用于将所述第二数据经过与网络设备对等的GTP-U协议层，与第一中继节点对等的PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；
所述第一用户面数据为所述终端设备的数据。
可选地，所述第二数据的消息类型为第一用户面数据时，
所述收发模块1010通过所述第二无线接口向所述第一中继节点发送所述第二数据，所述处理模块1020还用于将所述第二数据经过与第一中继节点对等的GTP-U协议层，PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；
所述第一用户面数据为所述终端设备的数据。
可选地，所述第二数据的消息类型为第一用户面数据时，
所述收发模块1010通过所述第二无线接口向所述第一中继节点发送所述第二数据，所述处理模块1020还用于将所述第二数据经过与第一中继节点对等的PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；
所述第一用户面数据为所述终端设备的数据。
可选地，所述处理模块1020还用于生成第一控制面数据；
所述收发模块1010还用于使用第二无线接口的无线承载向第一中继节点发送所述第一控制面数据，所述第二无线接口为所述第一中继节点和第二中继节点之间进行数据传输的无线接口；
所述收发模块1010通过所述第二无线接口向所述第一中继节点发送所述第一控制面数据时，所述处理模块1020还用于将所述第一控制面数据经过与网络设备对等的NGAP协议层，与第一中继节点对等的PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；
所述第一控制面数据为与终端设备相关的控制面信息。
可选地，其特征在于，
所述第二映射关系由第二中继节点确定；或者，
所述第一映射关系由所述网络设备或运营和管理实体OAM配置；或者，
所述第一映射关系由所述第一中继节点配置；或者
所述第二中继节点获取所述第二数据携带的所述第一映射关系。
可选地，其特征在于，所述网络设备为宿主基站或者第三中继节点，其中，所述网络设备与所述第一中继节点直接或者间接相连。
图41示出了本申请实施例提供的中继节点1100的示意性框图。该中继节点1100包括一个或多个处理器1110、存储器1120和通信接口1130；所述一个或多个处理器1110、所述存储器1120和所述通信接口1130均通过内部通路连接；
所述存储器1120，用于存储计算机执行指令；
所述一个或多个处理器1110，用于执行所述存储器1120存储的计算机执行指令，使得所述中继节点1100可以通过所述通信接口1130与其他装置进行数据交互来执行上述方法实施例提供的传输方法。
其中，该一个或多个处理器1110用于执行以下操作：
生成第一数据；
根据所述第一数据的属性信息和第一映射关系，控制通信接口1130通过第一无线接口向网络设备发送所述第一数据，所述第一无线接口为所述第一中继节点和所述网络设备之间进行数据传输的无线接口；
其中，所述第一映射关系为所述第一数据的属性信息与发送所述第一数据使用的无线承载之间的对应关系。
应理解，中继节点1100可以具体为上述实施例中的中继节点900，并且可以用于执行上述方法实施例中与中继节点900对应的各个步骤和/或流程。
图42示出了本申请实施例提供的中继节点1200的示意性框图。该中继节点1200包 括一个或多个处理器1210、存储器1220和通信接口1230；所述一个或多个处理器1210、所述存储器1220和所述通信接口1230均通过内部通路连接；
所述存储器1220，用于存储计算机执行指令；
所述一个或多个处理器1210，用于执行所述存储器1220存储的计算机执行指令，使得所述中继节点1200可以通过所述通信接口1230与其他装置进行数据交互来执行上述方法实施例提供的传输方法。
其中，该一个或多个处理器1210用于执行以下操作：
通过通信接口1230接收终端设备发送的第二数据；
根据所述第二数据的属性信息和第二映射关系，通过第二无线接口向第一中继节点发送所述第二数据，所述第二无线接口为所述第一中继节点和第二中继节点之间进行数据传输的无线接口；
所述第二映射关系为第二数据的属性信息与发送所述第二数据使用的无线承载之间的对应关系；
所述第二数据的属性信息包含以下信息中的至少一种：会话连接信息、数据流信息、所述第二无线接口的无线承载的信息、消息类型以及所述终端设备的信息。
应理解，中继节点1200可以具体为上述实施例中的中继节点1000，并且可以用于执行上述方法实施例中与中继节点1000对应的各个步骤和/或流程。
本申请实施例还提供了一种芯片系统，该芯片系统包括：一个或多个处理器、一个或多个存储器和接口电路，所述接口电路负责所述芯片系统与外界的信息交互，所述一个或多个存储器、所述接口电路和所述一个或多个处理器通过线路互联，所述一个或多个存储器中存储有指令；所述指令被所述一个或多个处理器执行，以使得所述第一中继节点或第二中继节点可以执行对应于上述方法的第一中继节点或第二中继节点的操作。
本申请实施例还提供了一种通信系统，包括：第一中继节点，和/或，第二中继节点；其中，所述第一中继节点为上述各个方面所述的第一中继节点，所述第二中继节点为上述各个方面所述的第二中继节点。
本申请实施例还提供了一种计算机程序产品，应用于第一中继节点或第二中继节点中，所述计算机程序产品包括一系列指令，当所述指令被运行时，以使得所述网络设备、服务器或终端设备可以执行对应于上述方法的第一中继节点或第二中继节点的操作。
在本申请实施例中，应注意，本申请实施例上述的方法实施例可以应用于处理器中，或者由处理器实现。处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质 位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
另外，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品可以包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁盘)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及 算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (20)

  1. 一种传输方法，其特征在于，包括：
    第一中继节点根据第一数据的属性信息和第一映射关系，通过第一无线接口向网络设备发送所述第一数据，所述第一无线接口为所述第一中继节点和所述网络设备之间进行数据传输的无线接口；
    其中，所述第一映射关系为所述第一数据的属性信息与发送所述第一数据使用的无线承载之间的对应关系。
  2. 根据权利要求1所述的方法，其特征在于，
    所述第一中继节点通过第二无线接口接收第二中继节点发送的所述第一数据，所述第二无线接口为所述第一中继节点和所述第二中继节点之间进行数据传输的无线接口；
    所述第一中继节点获取所述第一数据的属性信息，所述第一数据的属性信息包含以下信息中的至少一种：会话连接信息、数据流信息、所述第一无线接口的无线承载的信息、所述第二无线接口的无线承载的信息、消息类型以及所述第一数据所属节点的信息。
  3. 根据权利要求2所述的方法，其特征在于，所述第一数据的消息类型为第一用户面数据时，
    所述第一中继节点通过所述第二无线接口接收所述第二中继节点发送的所述第一数据，所述第一数据经过与所述第二中继节点对等的PHY协议层，MAC协议层，RLC协议层和PDCP协议层处理；
    所述第一中继节点通过所述第一无线接口向所述网络设备发送所述第一数据，所述第一数据经过与所述网络设备对等的PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；
    所述第一用户面数据为与所述第二中继节点连接的终端设备的数据。
  4. 根据权利要求2所述的方法，其特征在于，所述第一数据为第一用户面数据时，
    所述第一中继节点通过所述第二无线接口接收所述第二中继节点发送的所述第一数据，所述第一数据经过与所述第二中继节点对等的PHY协议层，MAC协议层，RLC协议层，PDCP协议层和GTP-U协议层处理；
    所述第一中继节点通过所述第一无线接口向所述网络设备发送第一数据，所述第一数据经过与所述网络设备对等的GTP-U协议层，PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；
    所述第一用户面数据为与所述第二中继节点连接的终端设备的数据。
  5. 根据权利要求2所述的方法，其特征在于，所述第一数据为所述第一控制面数据时，
    所述第一中继节点通过所述第二无线接口接收所述第二中继节点发送的所述第一数据，所述第一数据经过与所述第二中继节点对等的PHY协议层，MAC协议层，RLC协议层和PDCP协议层处理；
    所述第一中继节点通过第一无线接口向所述网络设备发送所述第一数据时，所述第一数据经过与所述网络设备对等的PDCP协议层，RLC协议层，MAC协议层和PHY协议 层处理；
    所述第一控制面数据为与接入所述第二中继节点的终端设备相关的控制面信息。
  6. 根据权利要求5所述的方法，其特征在于，所述第一中继节点通过所述第二无线接口接收所述第二中继节点发送的所述第一数据时，所述第一数据还经过与所述第二中继节点对等的NGAP协议层处理；
    所述第一中继节点通过所述第一无线接口向所述网络设备发送所述第一数据时，所述第一数据还经过与所述网络设备对等的NGAP协议层处理。
  7. 根据权利要求5或6所述的方法，其特征在于，所述第一中继节点通过所述第二无线接口接收所述第二中继节点发送的所述第一数据时，所述第一数据还经过与所述第二中继节点对等的RRC协议层处理；
    所述第一中继节点通过所述第一无线接口向所述网络设备发送所述第一数据时，所述第一数据还经过与所述网络设备对等的RRC协议层处理。
  8. 根据权利要求1所述的方法，其特征在于，
    所述第一中继节点通过第三无线接口接收终端设备发送的所述第一数据，所述第三无线接口为第一中继节点与所述终端设备通信的无线接口；
    所述第一中继节点获取所述第一数据的属性信息，所述第一数据的属性信息包含以下信息中的至少一种：会话连接信息、数据流信息、所述第一无线接口的无线承载的信息、所述第三无线接口的无线承载的信息、消息类型以及所述终端设备的信息。
  9. 根据权利要求8所述的方法，其特征在于，
    所述第一数据的消息类型为第二用户面数据时，
    所述第一中继节点通过所述第一无线接口向所述网络设备发送所述第一数据，所述第一数据经过与所述网络设备对等的GTP-U协议层，PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；
    所述第二用户面数据为所述终端设备的数据。
  10. 根据权利要求8所述的方法，其特征在于，所述第一数据为第二控制面数据时，
    所述第一中继节点通过所述第一无线接口向所述网络设备发送第一数据，所述第一数据经过与所述网络设备对等的NGAP协议层，PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；
    所述第二控制面数据为与所述终端设备相关的控制面信息。
  11. 根据权利要求1-10中任一项所述的方法，其特征在于，第一映射关系由第一中继节点确定；或者，
    所述第一映射关系由所述网络设备或运营和管理实体OAM配置；或者，
    所述第一中继节点在第一无线接口接收的所述第一数据时，所述第一数据携带用于获取所述第一映射关系的信息。
  12. 一种传输方法，其特征在于，包括：
    第二中继节点接收终端设备发送的第二数据；
    所述第二中继节点根据所述第二数据的属性信息和第二映射关系，通过第二无线接口向第一中继节点发送所述第二数据，所述第二无线接口为所述第一中继节点和第二中继节点之间进行数据传输的无线接口；
    所述第二映射关系为第二数据的属性信息与发送所述第二数据使用的无线承载之间的对应关系；
    所述第二数据的属性信息包含以下信息中的至少一种：会话连接信息、数据流信息、所述第二无线接口的无线承载的信息、消息类型以及所述终端设备的信息。
  13. 根据权利要求12所述的方法，其特征在于，所述第二数据的消息类型为第一用户面数据时，
    所述第二中继节点通过所述第二无线接口向所述第一中继节点发送所述第二数据，所述第二数据经过与网络设备对等的GTP-U协议层，与第一中继节点对等的PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；
    所述第一用户面数据为所述终端设备的数据。
  14. 根据权利要求12所述的方法，其特征在于，所述第二数据的消息类型为第一用户面数据时，
    所述第二中继节点通过所述第二无线接口向所述第一中继节点发送所述第二数据，所述第二数据经过与第一中继节点对等的GTP-U协议层，PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；
    所述第一用户面数据为所述终端设备的数据。
  15. 根据权利要求12所述的方法，其特征在于，所述第二数据的消息类型为第一用户面数据时，
    所述第二中继节点通过所述第二无线接口向所述第一中继节点发送所述第二数据，所述第二数据经过与第一中继节点对等的PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；
    所述第一用户面数据为所述终端设备的数据。
  16. 一种传输方法，其特征在于，包括：
    第二中继节点生成第一控制面数据；
    第二中继节点使用第二无线接口的无线承载向第一中继节点发送所述第一控制面数据，所述第二无线接口为所述第一中继节点和第二中继节点之间进行数据传输的无线接口；
    所述第二中继节点通过所述第二无线接口向所述第一中继节点发送所述第一控制面数据时，所述第一控制面数据经过与网络设备对等的NGAP协议层，与第一中继节点对等的PDCP协议层，RLC协议层，MAC协议层和PHY协议层处理；
    所述第一控制面数据为与终端设备相关的控制面信息。
  17. 根据权利要求12-16所述的方法，其特征在于，
    所述第二映射关系由第二中继节点确定；或者，
    所述第一映射关系由所述网络设备或运营和管理实体OAM配置；或者，
    所述第一映射关系由所述第一中继节点配置；或者
    所述第二中继节点获取所述第二数据携带的所述第一映射关系。
  18. 根据权利要求13或16所述的方法，其特征在于，所述网络设备为宿主基站或者第三中继节点，其中，所述网络设备与所述第一中继节点直接或者间接相连。
  19. 一种通信装置，其特征在于，包括处理电路和存储电路，所述存储电路中存储指 令，所述指令被调用时实现如权利要求1-18中任一项所述的方法。
  20. 一种计算机存储介质，包括指令代码，所述指令代码用于实现如权利要求1-18中任一项所述的方法。
PCT/CN2018/118925 2017-12-01 2018-12-03 一种传输方法和中继节点 WO2019105483A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711252183.6A CN109874153A (zh) 2017-12-01 2017-12-01 一种传输方法和中继节点
CN201711252183.6 2017-12-01

Publications (1)

Publication Number Publication Date
WO2019105483A1 true WO2019105483A1 (zh) 2019-06-06

Family

ID=66664345

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/118925 WO2019105483A1 (zh) 2017-12-01 2018-12-03 一种传输方法和中继节点

Country Status (2)

Country Link
CN (1) CN109874153A (zh)
WO (1) WO2019105483A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11239898B1 (en) * 2019-11-19 2022-02-01 T-Mobile Innovations Llc Relaying data to multiple access points

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114365540B (zh) * 2019-12-31 2023-11-17 华为技术有限公司 通信方法、设备及系统
CN112751871A (zh) * 2020-12-30 2021-05-04 京信网络系统股份有限公司 数据传输方法、装置、网络设备和存储介质
WO2023060435A1 (zh) * 2021-10-12 2023-04-20 Oppo广东移动通信有限公司 数据传输方法、装置、设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2306665A1 (en) * 2009-10-02 2011-04-06 Panasonic Corporation Relay backhaul uplink HARQ protocol
CN102036306A (zh) * 2009-09-29 2011-04-27 大唐移动通信设备有限公司 一种通信网络中网元数据的传输方法及通信系统
CN102349319A (zh) * 2009-03-11 2012-02-08 瑞典爱立信有限公司 中继节点的设置和配置
CN103797859A (zh) * 2011-09-06 2014-05-14 阿尔卡特朗讯 在移动通信网络上提供通信的方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101784125A (zh) * 2009-01-19 2010-07-21 大唐移动通信设备有限公司 一种tdd模式下的数据传输方法及系统
CN106034314A (zh) * 2015-03-10 2016-10-19 电信科学技术研究院 一种数据传输方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102349319A (zh) * 2009-03-11 2012-02-08 瑞典爱立信有限公司 中继节点的设置和配置
CN102036306A (zh) * 2009-09-29 2011-04-27 大唐移动通信设备有限公司 一种通信网络中网元数据的传输方法及通信系统
EP2306665A1 (en) * 2009-10-02 2011-04-06 Panasonic Corporation Relay backhaul uplink HARQ protocol
CN103797859A (zh) * 2011-09-06 2014-05-14 阿尔卡特朗讯 在移动通信网络上提供通信的方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11239898B1 (en) * 2019-11-19 2022-02-01 T-Mobile Innovations Llc Relaying data to multiple access points

Also Published As

Publication number Publication date
CN109874153A (zh) 2019-06-11

Similar Documents

Publication Publication Date Title
US11510131B2 (en) Configuration method, data transmission method, and apparatus
US11463937B2 (en) Data transmission method and apparatus
JP6718103B2 (ja) 通信方法
WO2019214709A1 (zh) 信息传输方法及装置
KR102305715B1 (ko) 중계 통신 방법과 중계 통신 장치 및 시스템
WO2019105483A1 (zh) 一种传输方法和中继节点
US11647561B2 (en) Node and communication method
US9591677B2 (en) Method of managing data bearers in a wireless access device and UEs
US20210377930A1 (en) Data transmission method and apparatus
CN110351747B (zh) 用于配置中继节点的方法和设备
WO2019206314A1 (zh) 一种通信方法及装置
WO2019091396A1 (zh) 通信方法及通信设备
WO2019042396A1 (zh) 网络接入和接入控制方法、装置
WO2017118191A1 (zh) 一种控制面信息的传输方法及装置
CN111865802A (zh) 一种通信方法及装置
KR102582320B1 (ko) Iab 네트워크를 위한 백홀 채널 관리
CN118042491A (zh) 用于配置中继节点的方法和设备
US9723591B2 (en) Independent signalling method for bearer management
CN116097890A (zh) 通信设备、数据传输的方法和装置
WO2019153295A1 (zh) 移动通信系统、方法及装置
KR20210073599A (ko) 릴레이 네트워크에서 제어 시그널링을 송신하는 방법, 구성 방법 및 장치
US20240155461A1 (en) Communication control method
WO2022262544A1 (zh) 一种通信的方法、装置及系统
US20230300606A1 (en) Technique of relaying capability information to a network node
WO2023286783A1 (ja) 通信制御方法

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18883689

Country of ref document: EP

Kind code of ref document: A1