WO2020164178A1

WO2020164178A1 - Data transmission method and apparatus

Info

Publication number: WO2020164178A1
Application number: PCT/CN2019/080269
Authority: WO
Inventors: 刘菁; 戴明增; 朱元萍; 卓义斌; 曹振臻
Original assignee: 华为技术有限公司
Priority date: 2019-02-15
Filing date: 2019-03-28
Publication date: 2020-08-20
Also published as: CN111586890A; CN111586890B

Abstract

A data transmission method and apparatus. The method comprises: an integrated access and backhaul (IAB) node receiving a first message and second information from a network side device, wherein the second information is used for indicating a radio bearer of a terminal side device on a link between the terminal side device and the IAB node, and the second information is carried in an adaptation layer between the IAB node and the network side device for sending; and the IAB node sending, by means of the radio bearer indicated by the second information, the first message to the terminal side device.

Description

Data transmission method and device

This application claims the priority of a Chinese patent application filed with the State Intellectual Property Office of China, the application number is 201910117895.X, and the invention title is "a data transmission method and device" on February 15, 2019. The entire content is incorporated by reference In this application.

Technical field

This application relates to the field of wireless communication technology, and in particular to a data transmission method and device.

Background technique

The fifth-generation mobile communication system (5th-generation, 5G) introduces integrated access and backhaul (IAB) network technology, the access link and backhaul link in the IAB network (backhaul link) All adopt wireless transmission schemes to avoid fiber deployment, thereby reducing deployment costs and improving deployment flexibility.

In the IAB network, there are IAB nodes (IAB node) and IAB hosts (IAB donor). The terminal side device can access the IAB node (IAB node), so the service data of the terminal side device can be connected to the IAB donor (IAB donor) by the IAB node through the wireless backhaul link for transmission. The IAB node can work in standalone (SA) mode or non-standalone (NSA) mode. When the IAB node works in the NSA mode, how to transmit data between the IAB node and the terminal side device has not yet given a clear technical solution, which is an urgent problem to be solved.

Summary of the invention

The embodiments of the present application provide a data transmission method and device to solve the problem of how to transmit data between the IAB node and the terminal side device when the IAB node works in the NSA mode.

In the first aspect, an embodiment of the present application provides a data transmission method. The method includes: accessing an integrated backhaul IAB node to receive a first message and second information from a network side device, where the second information is used to indicate The radio bearer of the terminal-side device on the link between the terminal-side device and the IAB node, wherein the second information is carried in a peer adaptation layer between the IAB node and the network-side device and sent; The IAB node sends the first message to the terminal side device through the radio bearer indicated by the second information.

Through the above method, by adding an adaptation layer between the IAB node and the eNB to transmit the second information, the IAB node can determine the radio bearer used to send the first message to the terminal side device according to the second information, thereby implementing IAB Data transmission between nodes and terminal-side devices.

In a possible design, the second information includes an identifier and a bearer identifier of the terminal-side device.

In a possible design, the identifier of the terminal-side device includes NR CGI and C-RNTI; or, the identifier of the terminal-side device is the first F1AP identifier allocated by the IAB node for the terminal-side device; or The identifier of the terminal-side device is the second F1AP identifier allocated by the IAB host to the terminal-side device; or, the identifier of the terminal-side device includes the first F1AP identifier and the second F1AP identifier.

In a possible design, the bearer identifier is a data radio bearer identifier or a logical channel identifier.

In a possible design, the method further includes:

Receiving, by the IAB node, a second message from the terminal-side device through the radio bearer;

The IAB node carries the second information in the adaptation layer, and sends the second message to the network side device.

In a second aspect, an embodiment of the present application provides a data transmission method, which includes:

The network-side device carries second information in the peer-to-peer adaptation layer between the network-side device and the integrated access backhaul IAB node, and the second information is used to indicate that the terminal-side device is in the terminal-side device The radio bearer on the link with the IAB node; the network side device sends the first message and the second information to the IAB node.

In a possible design, when the anchor point of the data of the terminal-side device is on the IAB host, the network-side device establishes the GTP-U tunnel for the radio bearer of the terminal-side device, and the terminal-side device There is a one-to-one correspondence between the radio bearers of the devices.

In a possible design, before the network-side device sends the first message to the IAB node, the method further includes: the network-side device receives the IAB host's corresponding information in the GTP tunnel The first information carried in the GTP-U header field, where the first information is used to indicate the IAB node that the terminal side device accesses.

In a possible design, the first information is an identifier assigned by the network-side device to the IAB node on the interface between the network-side device and the IAB host, or the first information includes all The network-side device is the identifier assigned by the IAB node on the interface between the network-side device and the IAB host, and the IAB host is the IAB node on the interface between the network-side device and the IAB host The assigned ID.

In a possible design, when the anchor point of the data of the terminal-side device is on the IAB host, the network-side device establishes a GTP-U tunnel for the radio bearer of the IAB node for transmission Data of the terminal side device with the same quality of service QoS.

In a possible design, before the network-side device sends the first message to the IAB node, the method further includes: the network-side device receives the IAB host's corresponding information in the GTP tunnel The second information carried in the GTP-U header field.

In a possible design, when the anchor point of the data of the terminal side device is on the network side device, the method further includes: in the process of adding the secondary base station, the network side device receives The first information of the IAB host; the first information is used to indicate the IAB node that the terminal side device accesses.

In a possible design, the anchor point of the data of the terminal-side device is on the IAB host, and the method further includes:

The network-side device receives a second message and second information from the IAB node, and the second information is used to indicate that the terminal-side device is on the link between the terminal-side device and the IAB node. Radio bearer, the second information is carried in a peer adaptation layer between the network side device and the IAB node.

In a possible design, the method further includes: the network-side device sends a second message and second information to the IAB host, the second information carrying a GTP-U header field, wherein the The GTP-U header field is a GTP-U header field corresponding to the GTP tunnel established for the IAB node between the network side device and the IAB host.

In a third aspect, an embodiment of the present application provides a reporting method, the method includes: a terminal-side device receives third indication information from an integrated IAB node for access and backhaul, and the third indication information is used to indicate the IAB node A radio link failure RLF occurs on the last hop link; the terminal side device sends a first message to the network side device according to the first indication information, and the first message is used to indicate the occurrence of RLF.

Through the above method, when the terminal-side device receives the third indication information, it can indicate to the network-side device that RLF occurs, so that in the case of a radio link failure RLF on the last hop link of the IAB node, the terminal-side device directly Notifying the network side equipment can improve the efficiency of RLF reporting.

In a possible design, the first message includes fourth indication information, and the fourth indication information is used to indicate that RLF occurs on the access link of the terminal side device or the backhaul chain of the terminal side device RLF occurs on the road.

In a fourth aspect, an embodiment of the present application provides a reporting method. The method includes: accessing an integrated backhaul IAB node and determining that an interface between the IAB node and the IAB host has a radio link failure RLF; the IAB node The terminal-side device sends third indication information, where the third indication information is used to indicate that a radio link failure RLF occurs in the previous hop link of the IAB node.

Through the above method, when the IAB node determines that RLF occurs on the interface between the IAB node and the IAB host, it can send the third indication information to instruct the terminal side device to notify the network side device of the occurrence of RLF, thereby improving the efficiency of RLF reporting.

In a fifth aspect, an embodiment of the present application provides a data transmission method. The method includes: accessing the backhaul integrated IAB host to determine first indication information, where the first indication information is used to indicate that the IAB node cannot communicate with the terminal device Uplink data is offloaded; the IAB host sends the first indication information to the IAB node.

Through the above method, through the first indication information, the IAB node does not perform uplink offloading of the uplink data of the terminal side device, but directly sends it to the IAB host, so that the existing LTE-NR dual-connection data transmission technology can be used to transmit the terminal The data of the side device reduces the complexity of data transmission and improves system compatibility.

In a possible design, the sending of the first indication information by the IAB host to the IAB node includes: the IAB host sending the first indication information to the IAB through a radio access control RRC message; or The IAB host sends the first indication information to the IAB through an F1 application layer protocol AP message.

In a sixth aspect, an embodiment of the present application provides a data transmission method. The method includes: accessing an integrated backhaul IAB node and receiving first indication information from an IAB host, where the first indication information is used to indicate that the IAB node cannot communicate with the terminal. The uplink data of the side device is offloaded; the IAB node forwards the uplink data of the terminal side device to the IAB host when receiving the uplink data of the terminal side device according to the first indication information.

In a seventh aspect, an embodiment of the present application provides a data transmission method. The method includes: an IAB host CU receives second indication information from a network side device, where the second indication information is indication information of an IAB node; the IAB host The CU determines to establish the signaling radio bearer SRB3 for the IAB node according to the second indication information.

In a possible design, the method further includes: the IAB host CU sends a first logical channel identifier and a second logical channel identifier to the IAB host DU, and instructs the logic corresponding to the first logical channel identifier of the IAB host DU The channel is used to transmit the UE associated F1AP message or the Non-UE associated F1AP message, and the logical channel corresponding to the second logical channel identifier is used to transmit the Non-UE associated F1AP message or the UE associated F1AP message.

In a possible design, the method further includes: the IAB host CU receives the first logical channel identifier and the second logical channel identifier allocated from the IAB host DU, and the type indication information of the F1AP message, where the F1AP message The type indication information includes: UE associated F1AP or Non-UE associated F1AP message; the first logical channel identifier and the second logical channel identifier are in one-to-one correspondence with the type indication information of the one F1AP message.

In an eighth aspect, an embodiment of the present application provides a data transmission method, the method includes: an IAB host DU receives second indication information from an IAB host CU, where the second indication information is indication information of an IAB node; the IAB host The DU allocates dedicated RACH resources to the IAB node according to the second indication information.

In a possible design, the method further includes: the IAB donor DU separately establishes a signaling plane bearer or BH RLC channel for transmitting UE associated F1AP messages, and a signaling plane bearer or BH channel for transmitting Non-UEassociated F1AP messages. RLC channel; the IAB donor DU determines the signaling plane bearer for the UE associated F1AP message or the first logical channel corresponding to the BH RLC channel, and the signaling plane bearer or BH RLC for the Non-UE associated F1AP message. The second logical channel corresponding to the channel; the IAB donor DU sends the first logical channel identifier of the first logical channel and the second logical channel identifier of the second logical channel to the IAB donor CU.

In a possible design, the method further includes: the IAB host DU receives a first logical channel identifier and a second logical channel identifier from the IAB host CU; the IAB host DU establishes a connection with the first logical channel identifier The signaling plane bearer or BH RLC channel corresponding to the indicated first logical channel, and the signaling plane bearer or BH RLC channel corresponding to the second logical channel indicated by the second logical channel identifier is established; The signaling plane bearer or BH RLC channel corresponding to the first logical channel indicated by a logical channel identifier is used to transmit UE associated F1AP message or Non-UE associated F1AP message, corresponding to the second logical channel indicated by the second logical channel identifier The signaling plane bearer or the BH RLC channel is used to transmit the Non-UE associated F1AP message or the UE associated F1AP message.

In a ninth aspect, this application provides a device. The device has the function of implementing the IAB node involved in the first aspect to the eighth aspect. For example, the device includes the module or unit or means corresponding to the IAB node executing the steps involved in the first aspect to the eighth aspect ( means), the function or unit or means can be realized by software, or by hardware, or by hardware executing corresponding software.

In a possible design, the device includes a processing unit and a transceiving unit, and the functions performed by the processing unit and the transceiving unit may correspond to the steps performed by the IAB node involved in the first to eighth aspects.

In a possible design, the device includes a processor, and may also include a transceiver. The transceiver is used to send and receive signals, and the processor executes program instructions to accomplish any of the first to eighth aspects. In the design or implementation of the IAB node.

Wherein, the apparatus may further include one or more memories, and the memories are used for coupling with the processor. The one or more memories may be integrated with the processor, or may be provided separately from the processor, which is not limited in this application.

In a possible manner, the memory stores the necessary computer program instructions and/or data for realizing the functions of the IAB node involved in the first aspect to the eighth aspect. The processor can execute the computer program instructions stored in the memory to complete the method executed by the terminal-side device in any possible design or implementation of the first aspect to the eighth aspect.

In a tenth aspect, this application provides a device. The apparatus has the function of implementing the network-side equipment involved in the first aspect to the eighth aspect. For example, the apparatus includes the module or unit corresponding to the network-side equipment executing the steps involved in the first aspect to the eighth aspect or Means. The functions or units or means can be implemented by software, or by hardware, or by hardware executing corresponding software.

In a possible design, the device includes a processing unit, a transceiving unit, and the functions performed by the processing unit and transceiving unit can be the same as the network-side equipment involved in any possible design or implementation of the first to eighth aspects. The steps performed correspond to those.

In another possible design, the communication device includes a processor, and may also include a transceiver. The transceiver is used to send and receive signals, and the processor executes the program instructions to complete the first to eighth aspects. The method executed by the network side device in any possible design or implementation.

In a possible manner, the memory stores the necessary computer program instructions and/or data to implement the functions of the network side device involved in any possible design or implementation manner of the first aspect to the eighth aspect. The processor can execute the computer program instructions stored in the memory to complete the method executed by the network side device in any possible design or implementation of the first to eighth aspects.

In an eleventh aspect, this application provides a device. The device has the function of implementing the terminal-side equipment involved in the first aspect to the eighth aspect. For example, the device includes the terminal-side device executing the module or unit corresponding to the steps involved in the first aspect to the eighth aspect or Means, the functions or units or means can be implemented by software, or by hardware, or by hardware executing corresponding software.

In a possible design, the device includes a processing unit and a transceiving unit, and the functions performed by the processing unit and the transceiving unit may correspond to the steps performed by the terminal side equipment involved in the first to eighth aspects.

In a possible design, the device includes a processor, and may also include a transceiver. The transceiver is used to send and receive signals, and the processor executes program instructions to accomplish any of the first to eighth aspects. The method executed by the terminal-side device in the design or implementation of the.

In a possible manner, the memory stores necessary computer program instructions and/or data for realizing the functions of the terminal-side device involved in the first to eighth aspects. The processor can execute the computer program instructions stored in the memory to complete the method executed by the terminal-side device in any possible design or implementation of the first aspect to the eighth aspect.

The embodiment of the present application provides a computer-readable storage medium, which stores computer-readable instructions. When the computer reads and executes the computer-readable instructions, the communication device is caused to perform any of the above-mentioned possibilities. Method in design.

The embodiment of the present application provides a computer program product. When the computer reads and executes the computer program product, the communication device executes any of the above-mentioned possible design methods.

The embodiment of the present application provides a chip, which is connected to a memory, and is used to read and execute a software program stored in the memory, so as to implement any of the above-mentioned possible design methods.

Description of the drawings

FIG. 1 is a schematic diagram of a communication system applicable to the communication method of the embodiment of the present application;

FIG. 2 is a schematic diagram of a communication system applicable to the communication method of an embodiment of the present application;

FIG. 3 is a schematic diagram of a data transmission direction provided by an embodiment of this application;

FIG. 4 is a schematic diagram of a data transmission direction provided by an embodiment of this application;

FIG. 5 is a schematic diagram of a data transmission direction provided by an embodiment of this application;

FIG. 6 is a schematic diagram of a protocol stack architecture provided by an embodiment of the application;

FIG. 7 is a schematic diagram of data transmission according to an embodiment of this application;

FIG. 8 is a schematic diagram of data transmission according to an embodiment of the application;

FIG. 9 is a schematic diagram of data transmission according to an embodiment of this application;

FIG. 10 is a schematic diagram of a data transmission direction according to an embodiment of this application;

FIG. 11 is a schematic diagram of a protocol stack architecture provided by an embodiment of the application;

FIG. 12 is a schematic diagram of data transmission according to an embodiment of this application;

FIG. 13 is a schematic diagram of data transmission according to an embodiment of this application;

FIG. 14 is a schematic diagram of data transmission according to an embodiment of this application;

15 is a schematic structural diagram of a communication device provided by an embodiment of this application;

FIG. 16 is a schematic structural diagram of a communication device provided by an embodiment of this application.

detailed description

The embodiments of the present application will be described in detail below in conjunction with the accompanying drawings of the specification.

The embodiments of this application can be applied to various mobile communication systems, such as: new radio (NR) system, global system of mobile communication (GSM) system, code division multiple access, CDMA ) System, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, advanced long-term evolution (advanced long) term evolution, LTE-A) system, universal mobile telecommunication system (UMTS), evolved long term evolution (evolved long term evolution, eLTE) system, future communication system and other communication systems. Specifically, I will not Do restrictions.

To facilitate the understanding of the embodiments of the present application, first, the communication system shown in FIG. 1 is taken as an example to describe in detail the communication system applicable to the embodiments of the present application. Fig. 1 shows a schematic diagram of a communication system applicable to the communication method of the embodiment of the present application. As shown in Figure 1, the communication system includes a packet data core network (Evolved Packet Core, EPC) device, a network side device, an IAB host, an IAB node, and a terminal side device. For the terminal-side device, the network-side device can be used as the master station, and the IAB host can be used as the auxiliary station. Of course, it can also be the other way around, that is, the IAB host can be the master station and the network-side device can be used as the auxiliary station. Fig. 2 is another form of the communication system shown in Fig. 1, and the substantially expressed meanings are the same, which will not be repeated here.

In the embodiment of the present application, a node that supports integrated access and backhaul is called an IAB node, and the IAB node may also be called a relay node (RN). For the convenience of description, all are called IAB nodes below. The IAB node may include at least one mobile terminal (MT) unit and at least one distributed unit (DU). In FIG. 1 and FIG. 2, only the IAB node includes an MT unit and a DU as an example for description. The MT of the IAB node acts as a terminal-side module and is responsible for communicating with the parent node of the IAB node. The DU of the IAB node serves as the DU module to provide access services for the terminal side devices or other IAB nodes attached to it. For the convenience of description, the MT in the IAB node is referred to as "IAB node MT", and the DU in the IAB node is referred to as "IAB node DU".

The IAB node can provide wireless access services for the terminal side device, and the service data of the terminal side device is connected to the IAB donor (IAB donor) or the network side device by the IAB node through a wireless backhaul link. The IAB host can be an access network element with a complete base station function, or it can be an access network element in the form of a separate centralized unit (CU) and distributed unit (DU). For ease of presentation, in the embodiments of this application, the centralized unit of the IAB host is referred to as IAB host CU (donor CU), and the distributed unit of IAB host is referred to as IAB host DU (donor DU). It may be a form in which the control plane (CP) and the user plane (UP) are separated. For example, an IAB host CU is composed of one CU-CP and multiple CU-UPs, which is not discussed in the embodiment of this application. limited.

In the embodiment of the present application, the terminal-side device is a device with a wireless transceiver function or a chip that can be installed in the device. Wherein, the device with wireless transceiver function may also be called user equipment (UE), access terminal, user unit, user station, mobile station, remote station, remote terminal, mobile equipment, user terminal, user agent Or user device. In practical applications, the terminal-side devices in the embodiments of the present application may be mobile phones, tablets, computers with wireless transceiver functions, virtual reality (VR) terminals, augmented reality (augmented) Reality, AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, and wireless terminals in smart grid (smart grid) , Wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc. The embodiment of this application does not limit the application scenario. In this application, the aforementioned devices with wireless transceiver functions and chips that can be installed in the devices are collectively referred to as terminal-side devices.

In the embodiments of the present application, the network side device may be a wireless access device under various standards, such as an evolved Node B (eNB), a radio network controller (RNC), or a Node B (Node B). B, NB), base station controller (BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), the access point (AP), wireless relay node, wireless backhaul node, transmission point (transmission and reception point, TRP or transmission point, TP) in the wireless fidelity (WIFI) system It can also be the gNB or transmission point (TRP or TP) in the 5G (NR) system, one or a group of antenna panels (including multiple antenna panels) of the base station in the 5G system, or it can also constitute a gNB or The network node of the transmission point, such as a baseband unit (BBU), or a CU under a centralized unit-distributed (CU-DU) architecture.

In addition, in Figures 1 and 2, the names of the interfaces between the devices are also shown, such as the S1 interface between the EPC device and the network side device, the X2 interface between the network side device and the IAB host, and the network side device and The NR Uu interface between the IAB nodes, the LTE Uu interface between the network side device and the terminal side device, the NR Uu interface between the terminal side device and the IAB node, and the NR Un interface between the IAB node and the IAB host, these interfaces The name of is just an example and does not represent a limitation on the interface. When the communication system version changes, the corresponding name can also be replaced with the name of the corresponding function in other wireless communication networks.

The network architecture and business scenarios described in the embodiments of this application are intended to more clearly illustrate the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Those of ordinary skill in the art will know that with the network With the evolution of architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

Some scenarios in the embodiments of this application are described by taking the scenario of IAB in a wireless communication network as an example. It should be pointed out that the solutions in the embodiments of this application can also be applied to other wireless communication networks, and the corresponding names can also be other wireless communication networks. Replace the name of the corresponding function in the communication network.

In the first embodiment, in this implementation mode, it can be restricted that the IAB node will not receive the downlink data of the terminal side device through multiple connections, nor will the uplink data received from the terminal side device be sent through the network side device and the IAB host respectively. Diversion, described in detail below.

Refer to FIG. 3, which is a schematic flowchart of a data transmission method provided by an embodiment of this application. The method flow shown in FIG. 3 can be applied to the communication system shown in FIG. 1 and FIG. 2. In the flowchart shown in FIG. 3, the anchor point of the data of the terminal-side device is the network-side device.

In this implementation, as shown in Figure 3, for the downlink data transmission of the terminal-side device, after the network-side device obtains the downlink data of the terminal-side device from the EPC device, the network-side device transfers the downlink data of the terminal-side device to two channels. Offloading, for the first offloaded downlink data, the network side device directly sends the downlink data of the terminal side device to the terminal side device; for the second offloaded downlink data, the network side device sends the downlink data of the terminal side device to the IAB Host, and further forwarded by the IAB host to the terminal side device.

Correspondingly, as shown in Figure 3, for the uplink data transmission of the terminal-side device, the terminal-side device splits the uplink data in two ways, one is to directly send the split data to the network-side device, and the other is to send the split data to the IAB node , And further forwarded by the IAB node to the IAB host, the IAB host further forwards the received offload data to the network side device, and the network side device sends the uplink data of the terminal side device to the EPC device.

The anchor point of the data of the terminal-side device may also be the IAB host. Refer to FIG. 4, which is a schematic flowchart of a data transmission method provided in an embodiment of this application. The method flow shown in FIG. 4 can be applied to the communication system shown in FIG. 1 and FIG. 2. In the flowchart shown in FIG. 4, the anchor point of the data of the terminal-side device is the IAB host.

In this implementation mode, as shown in Figure 4, for the downlink data transmission of the terminal-side device, after the IAB host obtains the downlink data of the terminal-side device from the EPC device, the IAB host splits the downlink data of the terminal-side device in two ways. For the first channel of offloaded downlink data, the IAB sink sends the downlink data of the terminal side device to the network side device, and the network side device forwards it to the terminal side device; for the second channel of offloaded downlink data, the IAB sink sends the downlink data of the terminal side device Downlink data is sent to the IAB node, and the IAB node is further forwarded to the terminal side device.

Correspondingly, as shown in Figure 4, for the uplink data transmission of the terminal-side device, the terminal-side device splits the uplink data in two ways. One way is to directly send the split data to the network-side device, and the network-side device transmits the uplink data of the terminal-side device. The data is forwarded to the IAB host; one way is to send the offloaded data to the IAB node, and the IAB node further forwards it to the IAB host. Finally, the IAB host forwards the received data from the network side device and/or IAB node to the EPC device.

Exemplarily, if the IAB host adopts the CU-DU separation architecture, the IAB host in FIG. 3 or FIG. 4 may refer to the IAB host CU.

Exemplarily, in order to ensure the data of the terminal-side device, the transmission is performed according to the description shown in FIG. 3 or FIG. 4. Before the data transmission is performed, the IAB host sends first indication information to the IAB node, and the first indication information is used for Indicates that the IAB node cannot perform uplink offloading on the uplink data of the terminal side device. Alternatively, the first indication information may indicate that the IAB node can only build the BH RLC channel on the secondary cell group (Second Cell Group, SCG), or the first indication information may indicate other information (for example, indicating the IAB node The uplink data of the terminal-side device cannot be offloaded, or the IAB node is instructed not to establish a BH RLC channel with the network-side device, but according to this other information, the IAB node can implicitly learn that only the BH RLC channel can be built in On the secondary cell group. Alternatively, the first indication information may indicate that the IAB node does not need to establish a BH RLC channel with the network side device, or the first indication information indicates other information, but according to other information, the IAB node may hide It does not need to establish a BH RLC channel with the network side device.

Exemplarily, before the IAB node performs uplink data transmission, it needs to first determine whether the uplink data to be transmitted is backhaul data. If the uplink data to be transmitted is the backhaul data received from the child node of the IAB node, the IAB node sends the UL data to be transmitted to the parent node of the IAB node through the SCG; if the uplink data to be transmitted is The data generated by the IAB node itself (for example: Operation Administration and Maintenance (OAM) data of the IAB node), the IAB node can determine the data to be transmitted according to the threshold and/or main path information configured by the network side device Whether the uplink data needs to be sent to the network side device through the master cell group (Master Cell Group, MCG). For the data generated by the IAB node itself, if the amount of data exceeds the threshold configured by the network side device, the IAB node can choose a path to send the uplink data to the network side device, for example, by choosing to directly send the data to the network side Device, or choose to send data to the IAB host CU, and then the IAB host CU forwards it to the network side device. The path selected by the IAB node is called the main path.

In general, in a multi-connection scenario, for the backhaul data, the IAB node can only transmit the backhaul data through the SCG bearer. Exemplarily, the IAB host may send the first indication information to the IAB node through a radio resource control (radio resource control, RRC) message. At this time, the IAB node MT may receive the RRC message carrying the first indication information. The IAB host may also send the first indication information to the IAB node through an F1 application layer protocol (F1 application protocol, F1AP) message. In this case, the IAB node DU receives the F1AP message carrying the first indication information and sends the first indication The information is forwarded to the IAB node MT. In combination with the above description, if the IAB host adopts the CU-DU separation architecture, the first indication information may be sent by the IAB host CU.

As another possible implementation manner, before data transmission is performed, the IAB host does not need to send the first indication information to the IAB node. In order to ensure the data of the terminal side device, in the multi-connection scenario, the BH RLC channel of the IAB node can only be built on the SCG, or the IAB node does not need to establish a BH RLC channel with the network side device, or the IAB node can only connect back The data is transmitted through the SCG bearer.

In addition, in the processes shown in Figures 3 and 4, the network side device and the IAB node MT will not establish a corresponding user plane bearer for the return data, and at most will only establish a corresponding user plane for the IAB node's own data. Bearer.

In the second embodiment, in this implementation mode, the IAB node can receive the downlink data from the terminal-side device in a multi-connection mode, and then send it to the terminal-side device, and/or the IAB node can also receive the uplink data from the terminal-side device The data is split through the network side device and the IAB host respectively. For this reason, in this manner, the IAB host needs to instruct the network side device to send the data of the terminal side device to the IAB node. The IAB host can indicate the network-side device in a display manner, or in an implicit manner, as described in detail below.

In this implementation manner, the anchor point of the data of the terminal-side device may be the IAB host or the network-side device. The following description is divided into different situations.

In the first possible implementation manner, the anchor point of the data of the terminal side device is used as the IAB host for description.

In the first possible implementation, as shown in Figure 5, in the downlink direction, the IAB host obtains the downlink data of the terminal-side device from the EPC device, and the IAB host sends the downlink data of the terminal-side device directly to the IAB node, or through The network side device sends to the IAB node, and then the IAB node sends it to the terminal side device; in the upstream direction, the IAB node sends the uplink data of the terminal side device directly to the IAB host, or sends it to the IAB host through the network side device.

In this implementation manner, the protocol stack architecture of the terminal side device, IAB node, IAB host, and network side device for data transmission can be referred to as shown in FIG. 6. In Figure 6, an adaptation layer needs to be introduced between the IAB node MT and the network side device to carry the bearer identifier of the terminal side device, so that the IAB node can perform the downlink of the terminal side device according to the bearer identity of the terminal side device. The data is mapped to the radio bearer corresponding to the Uu interface and sent to the terminal side device, or the network side device can map the terminal side device's uplink data to the GTP-U tunnel corresponding to the X2 interface and send it to the IAB host according to the bearer identifier of the terminal side device.

In Figure 6, for the terminal side device, the IAB host serves as the primary station and the network side device serves as the secondary station. The terminal-side equipment is located on the DU of the IAB node on the radio link control (RLC) layer, medium access control (MAC) layer, and physical (PHY) layer of the NR Uu interface. The packet data convergence protocol (PDCP) layer and radio resource control (radio resource control, RRC) layer are located on the CU of the IAB host. It can also be said that the CU of the IAB host and the DU of the IAB node together serve as the terminal The master station of the side device. The protocol layers that the IAB node and the network-side equipment are equivalent to are the adaptation layer, the PDCP layer, the RLC layer, and the MAC layer. The IAB node is at the NR Un interface, and the protocol layer equivalent to the IAB host is the General Packet Radio Service (GPRS) tunneling protocol user plane (GPRS Tunnelling Protocol User Plane, GTP-U) layer, and the user datagram protocol ( user datagram protocol, UDP) layer, internet protocol (IP) layer, adaptation layer, RLC layer, MAC layer, etc. The network side device is on the X2 interface, and the protocol layers equivalent to the IAB host are the GTP-U layer, UDP layer, IP layer, L2 layer, and L1 layer.

It should be understood that the adaptation layer in FIG. 6 can be an independent protocol layer, or a sublayer or submodule of an existing protocol layer, for example, a sublayer of the RLC layer, or a sublayer of the MAC layer. The embodiment of the present application There is no restriction on this. It should also be understood that the adaptation layer may have other names, which are not limited in the embodiment of the present application.

It should be understood that the adaptation layer in FIG. 6 is deployed above the RLC layer, and the adaptation layer may also be deployed below the RLC layer, which is not limited in the embodiment of the present application.

It should be noted that, in this implementation manner, the IAB node does not perform reordering processing on the data packets of the terminal side device received by different paths. In the downstream direction, only the terminal-side device will reorder the terminal-side device data packets, while in the upstream direction, only the IAB host will re-order the terminal-side device data packets.

Exemplarily, in the foregoing implementation manner, if the IAB host adopts a CU-DU separation architecture, the data anchor point may be located on the IAB host CU, and the IAB host CU implements data forwarding.

In the first possible implementation, there are two possible solutions. Solution 1. The GTP-U tunnel between the IAB host and the network side device is based on the granularity of each bearer of each terminal side device. Established, that is, different bearers of different terminal side devices under the IAB node respectively establish corresponding GTP-U tunnels between the IAB host and the network side device. At this time, when the GTP-U tunnel is established, the IAB host sends the bearer identifier of the radio bearer corresponding to the GTP-U tunnel to the network side device. For example, the bearer identifier may be carried by the X2 AP message. The following describes how to transmit data in the upstream and downstream directions respectively.

As mentioned earlier, in the downlink direction, the IAB host can directly send the downlink data of the terminal-side device to the IAB node, and/or the IAB host can also send it to the IAB node through the network-side device, and then the IAB node to the terminal-side device . For the flow of the IAB host directly sending the downlink data of the terminal-side device to the IAB node, reference may be made to the description in the prior art, and the details are not repeated here in the embodiment of the application. The flow of the IAB host sending the downlink data of the terminal-side device to the IAB node through the network-side device can be as shown in Figure 7. As shown in FIG. 7, a schematic diagram of data transmission provided by an embodiment of this application.

Step 701: The IAB host obtains the first packet of the terminal side device.

Exemplarily, the IAB host may obtain the downlink data of the terminal-side device from the EPC device, and obtain the first packet after processing.

It should be noted that, for example, the first message may be a PDCP protocol data unit (protocol data unit, PDU).

Step 702: The IAB host sends the first message and the first information to the network side device.

The first information is used to indicate an IAB node, and the IAB node is used to forward a message from the network side device and sent to the terminal side device to the terminal side device. The first information is an identifier assigned by the network-side device to the IAB node on the interface between the network-side device and the IAB host, or the first information includes that the network-side device is the The identifier assigned by the IAB node on the interface between the network side device and the IAB host, and the IAB host is the identifier assigned by the IAB node on the interface between the network side device and the IAB host. For example, in an implementation manner, the first information may be an identifier assigned by the network side device to the IAB node on the X2 interface, for example, it may be an X2AP identifier assigned by the network side device to the IAB node; another In this implementation manner, the first information may also include the identifier assigned by the network side device to the IAB node on the X2 interface and the identifier assigned by the IAB host on the X2 interface for the IAB node, for example, Including the X2AP identifier assigned by the network side device to the IAB node, and the X2AP identifier assigned by the IAB host to the IAB node.

The IAB host carries the first message and the first information in the GTP tunnel established on the X2 interface and sends it to the network side device.

For example, taking the IAB host adopts the CU-DU separation architecture as an example, the IAB host CU determines the corresponding GTP-U tunnel on the X2 interface between the IAB host and the network-side device according to the first message, and the IAB host CU can The first information is carried in the GTP-U header field, and the first message is sent to the network side device through the GTP-U tunnel.

Step 703: The network side device receives the first information and the first message from the IAB host from the GTP-U tunnel.

Step 704: The network side device sends the first packet to the IAB node indicated by the first information.

Exemplarily, the first information indicates the IAB node MT, and the network side device can determine the IAB node according to the first information, so as to send the first message to the IAB node MT indicated by the first information.

In a possible implementation manner, the network side device receives the first packet of the terminal side device from the GTP-U tunnel, and obtains the second information according to the bearer identifier of the radio bearer corresponding to the GTP-U tunnel. The network side device sends the first message to the IAB node and carries the second information in the adaptation layer. The second information is used to uniquely identify the radio bearer of the terminal-side device, and the second information may be a newly defined identifier, or may include the identifier of the terminal-side device and the bearer identifier of the radio bearer. Wherein, the identity of the terminal-side device includes the NR cell global identifier (CGI) and the cell radio network temporary identity (C-RNTI); or, the identity of the terminal-side device is The first F1AP identifier allocated by the IAB node to the terminal-side device on the F1 interface with the IAB host; or, the identifier of the terminal-side device is that the IAB host is on the F1 interface with the IAB node The second F1AP identifier assigned to the terminal-side device; or, the identifier of the terminal-side device includes the first F1AP identifier and the second F1AP identifier. It should be noted that, regardless of the identification of the terminal-side device, before executing the process shown in FIG. 7, the IAB host sends the identification of the terminal-side device to the network-side device through an X2AP message. The bearer identifier is a data radio bearer identifier (for example: DRB ID) or a logical channel identifier (for example: LCID) allocated by the terminal-side device on the Uu interface.

It should be noted that the bearer identifier of the radio bearer corresponding to the GTP-U tunnel is sent to the network side device by the IAB host CU when the GTP-U tunnel is established.

Step 705: The IAB node MT receives the first message from the network side device.

Exemplarily, the adaptation layer of the IAB node MT includes the second information added by the network side device.

Step 706: The IAB node MT sends the first message to the IAB node DU.

It should be noted that the IAB node MT obtains the second information from the adaptation layer and sends it to the IAB node DU.

Step 707: The IAB node DU sends the first message to the terminal side device through the radio bearer on the terminal side device side indicated by the second information.

Another possible way in this embodiment is that when the GTP-U tunnel is established between the IAB host and the network side device, the X2AP message carries the indication information of the IAB node. In this way, there is no need to carry the first information in the foregoing steps 702, 703, and 704. For the network side device, after receiving the first message from the GTP-U tunnel, it knows which IAB node the first message needs to be sent to. The other steps remain unchanged, so I won't repeat them here.

The transmission of uplink data is similar to downlink data, that is, the IAB node MT carries the second information in the adaptation layer. The network side device maps the uplink data to the GTP-U tunnel corresponding to the X2 interface and sends it to the IAB host CU according to the second information.

As mentioned above, in the uplink direction, the IAB node can directly send the uplink data of the terminal side device to the IAB host, and/or send it to the IAB host through the network side device. For the flow of the IAB node directly sending the uplink data of the terminal-side device to the IAB host, reference may be made to the description in the prior art, and the details of the embodiment of the application are not repeated here. The flow of the IAB node sending the uplink data of the terminal side device to the IAB host through the network side device can be as shown in Figure 8.

As shown in FIG. 8, a schematic diagram of data transmission provided by an embodiment of this application.

Step 801: The IAB node obtains the second message from the terminal side device.

Exemplarily, the IAB node DU receives the second message through the radio bearer between the IAB node and the terminal side device, and sends the second message to the IAB node MT.

It should be noted that, for example, the second message may be a PDCP PDU.

Step 802: The IAB node sends the second information and the second message to the network side device.

Exemplarily, the IAB node MT carries the second information in the adaptation layer and sends it to the network side device.

Step 803: The network side device receives the second information and the second message from the IAB node.

Exemplarily, the network side device receives the second information sent by the IAB node from the adaptation layer.

Step 804: The network side device determines the GTP-U tunnel corresponding to the radio bearer indicated by the second information according to the second information, and sends the second message to the IAB through the GTP-U tunnel Host.

Step 805: The IAB host receives the second message from the network side device.

The IAB host sends the second message received from the GTP-U tunnel to the PDCP entity corresponding to the bearer identity of the radio bearer according to the bearer identity of the radio bearer corresponding to the GTP-U tunnel Process, and send the processed second message to the EPC device, the details are not repeated here.

In the upstream direction, in this embodiment, the IAB node can directly send the uplink data of the terminal-side device to the IAB host, and/or send it to the IAB host through the network-side device, that is, offload the uplink data of the terminal-side device. Therefore, When the IAB host configures the adaptation layer of the IAB node (the adaptation layer is the adaptation layer between the IAB host and the IAB node), the adaptation layer configuration information includes at least one of the following parameters: uplink data offload threshold, uplink data master path. The uplink data offload threshold is used to instruct the IAB node to send the uplink data of the terminal side device to the IAB host and the network side device only when the amount of uplink data of the terminal side device exceeds the uplink data offload threshold. The main uplink data path is used to indicate whether the IAB node sends the uplink data of the terminal side device to the IAB host node or the network side device when the amount of uplink data of the terminal side device is lower than the uplink data offload threshold.

Solution 2: The GTP-U tunnel between the IAB host and the network side device is established according to the granularity of each bearer of each IAB node MT, that is, each bearer of the IAB node MT is in the IAB host and network respectively A corresponding GTP-U tunnel is established between the side devices. At this time, one GTP-U tunnel is used to transmit the data of the terminal-side devices with the same quality of service (Quality of Service, QoS). At this time, when the GTP-U tunnel is established, the IAB host sends the bearer identifier of the radio bearer corresponding to the GTP-U tunnel to the network side device. For example, the X2 AP message can carry the bearer identifier of the terminal side device. The following describes how to transmit data in the upstream and downstream directions respectively.

As mentioned earlier, in the downlink direction, the IAB host can directly send the downlink data of the terminal-side device to the IAB node, and/or the IAB host can also send it to the IAB node through the network-side device, and then the IAB node can send it to the terminal-side device . For the flow of the IAB host directly sending the downlink data of the terminal-side device to the IAB node, reference may be made to the description in the prior art, and the details are not repeated here in the embodiment of the application. The flow of the IAB host sending the downlink data of the terminal side device to the IAB node through the network side device can be as shown in FIG. 9. As shown in FIG. 9, a schematic diagram of data transmission provided by an embodiment of this application.

Step 901: The IAB host obtains the first packet of the terminal side device.

It should be noted that, by way of example, the first packet may be a PDCP PDU.

Step 902: The IAB host sends the third information and the first message to the network side device through the GTP-U tunnel.

The third information is used to uniquely identify the radio bearer of the terminal-side device, and the third information may be a newly defined identifier, and may also include the identifier of the terminal-side device and the bearer identifier of the radio bearer. It should be noted that the third information and the second information in step 702 essentially represent the same information, and different expressions are used to distinguish them.

Exemplarily, the bearer identifier is a data radio bearer identifier (for example: DRB ID) or a logical channel identifier allocated by the terminal-side device on the radio bearer of the Uu interface. The identifier of the terminal-side device includes the NR cell global identifier (CGI) and the cell radio network temporary identity (C-RNTI); or, the identifier of the terminal-side device is the IAB The first F1AP identifier allocated by the node to the terminal-side device on the F1 interface between the node and the IAB host; or, the identifier of the terminal-side device is the F1 AP between the IAB host and the IAB node The second F1AP identifier assigned to the terminal-side device on the interface; or, the identifier of the terminal-side device includes the first F1AP identifier and the second F1AP identifier. It should be noted that, regardless of the identification of the terminal-side device, before executing the process shown in FIG. 9, the IAB host sends the identification of the terminal-side device to the network-side device through an X2AP message.

For example, taking the IAB host adopts the CU-DU separation architecture as an example, the IAB host CU may carry third information in the GTP-U header field, and send the third information and the third information to the network side device through the GTP-U tunnel. The first message.

Step 903: The network side device receives the third information and the first message from the IAB host through the GTP-U tunnel.

Step 904: The network side device sends the first message to the IAB node corresponding to the GTP-U tunnel.

Exemplarily, the network side device receives the first packet from the GTP-U tunnel, obtains the third information from the GTP-U header field, and then carries the third information in the adaptation layer, together with the first packet Sent to the IAB node corresponding to the GTP-U tunnel.

Step 905: The IAB node MT receives the first message from the network side device.

The IAB node MT receives the third information added by the network side device from the adaptation layer.

Step 906: The IAB node MT sends the first message to the IAB node DU.

It should be noted that the IAB node MT may obtain the third information from the adaptation layer and send it to the IAB node DU.

Step 907: The IAB node DU sends the first message to the terminal device through the radio bearer of the terminal device indicated by the third information.

The transmission of uplink data is similar to downlink data. If the IAB node obtains the second message from the terminal side device, the IAB node MT carries the third information in the adaptation layer and sends it to the network side device together with the second message. The network side device extracts the third information from the adaptation layer, carries it in the GTP-U header field and sends it to the IAB host. According to the radio bearer of the terminal side device indicated by the third information, the IAB host sends the second message to the PDCP entity corresponding to the radio bearer of the terminal side device for processing.

In the second possible implementation manner, the anchor point of the data of the terminal side device is the network side device for description.

In the second possible implementation manner, as shown in Figure 10, in the downlink direction, the network side device obtains the downlink data of the terminal side device from the EPC device, and the network side device directly sends the downlink data of the terminal side device to the IAB node. Or sent to the IAB node through the IAB host, and then sent by the IAB node to the terminal side device; in the upstream direction, the IAB node directly sends the uplink data of the terminal side device to the network side device, or sends it to the network side device through the IAB host.

In this implementation, before data transmission is performed, in order for the network-side device to determine the IAB node that the terminal-side device accesses, in the process of adding (Secondary Cell Group, SCG) for the terminal-side device, the IAB The host may send the fourth information used to indicate the IAB node that the terminal side device accesses to the network side device through the X2 interface. Further, the terminal side device accesses the IAB node DU, and the network side device needs to send data to the IAB node MT, so the fourth information may be used to indicate the IAB node MT that the terminal side device accesses.

Exemplarily, the fourth information may be the identifier of the IAB node MT, the identifier of the IAB node MT may be the X2AP identifier assigned by the network side device to the IAB node MT on the X2 interface, or the IAB host is the IAB node MT in X2 The X2AP identifier assigned on the interface, or the X2AP identifier assigned by the network side device on the X2 interface of the IAB node MT and the X2AP identifier assigned by the IAB host on the X2 interface of the IAB node MT.

In this implementation manner, the protocol stack architecture of the terminal side device, IAB node, IAB host, and network side device for data transmission can be referred to as shown in FIG. 11. In Figure 11, for the terminal-side device, the network-side device serves as the primary station, and the IAB host serves as the secondary station. In Figure 11, an adaptation layer needs to be introduced between the IAB node MT and the network side device to carry the fifth information so that the IAB node can map the downlink data of the terminal side device to the corresponding Uu interface according to the fifth information The radio bearer is sent to the terminal-side device, or so that the network-side device maps the uplink data of the terminal-side device to the PDCP entity corresponding to the radio bearer of the terminal-side device indicated by the fifth information according to the fifth information for processing.

Exemplarily, the fifth information is used to uniquely identify the radio bearer of the terminal-side device, and the fifth information may be a newly defined identifier, and may also include the identifier of the terminal-side device and the bearer identifier. It should be noted that the fifth information and the second information in step 702 substantially represent the same information, and different expressions are used to distinguish them.

Exemplarily, the bearer identifier is a data radio bearer identifier (for example: DRB ID) or a logical channel identifier allocated by the terminal-side device on the radio bearer of the Uu interface. The identifier of the terminal-side device includes the NR cell global identifier (CGI) and the cell radio network temporary identity (C-RNTI); or, the identifier of the terminal-side device is the IAB The first F1AP identifier allocated by the node to the terminal-side device on the F1 interface between the node and the IAB host; or, the identifier of the terminal-side device is the F1 AP between the IAB host and the IAB node The second F1AP identifier assigned to the terminal-side device on the interface; or, the identifier of the terminal-side device includes the first F1AP identifier and the second F1AP identifier. It should be noted that, regardless of the identification of the terminal-side device, before data transmission, the IAB host sends the identification of the terminal-side device to the network-side device through an X2AP message.

It should be understood that the adaptation layer in FIG. 11 can be an independent protocol layer, or a sublayer or submodule of an existing protocol layer, for example, a sublayer of the RLC layer, or a sublayer of the MAC layer. The embodiment of the present application There is no restriction on this. It should also be understood that the adaptation layer may have other names, which are not limited in the embodiment of the present application.

It should be understood that the adaptation layer in FIG. 11 is deployed above the RLC layer, and the adaptation layer may also be deployed below the RLC layer, which is not limited in the embodiment of the present application.

It should be noted that, in this implementation manner, the IAB node does not perform reordering processing on the data packets of the terminal side device received by different paths. In the downstream direction, only the terminal-side device will reorder the terminal-side device data packets, while in the upstream direction, only the network-side device will reorder the terminal-side device data packets.

In the second possible implementation manner, as mentioned above, in the downlink direction, the network side device can directly send the downlink data of the terminal side device to the IAB node, and/or send it to the IAB node through the IAB host, and then the IAB node Send to the terminal side device. For the flow of the network side device sending the downlink data of the terminal side device to the IAB node through the IAB host, reference may be made to the description in the prior art, which will not be repeated in the embodiment of the application. The flow of the network side device directly sending the downlink data of the terminal side device to the IAB node may be as shown in FIG. 12. As shown in FIG. 12, a schematic diagram of data transmission provided in an embodiment of this application.

Step 1201: The network side device obtains the first packet of the terminal side device.

Exemplarily, the network side device may obtain the downlink data of the terminal side device from the EPC device, and obtain the first message after processing.

It should be noted that, by way of example, the first packet may be a PDCP PDU.

Step 1202: The network side device sends the fifth information and the first message to the IAB node indicated by the fourth information.

Exemplarily, the network side device carries the fifth information in the adaptation layer.

It should be noted that the fourth information is obtained by the network side device from the IAB host during the SCG addition process of the terminal side device, and is used to indicate the IAB node that the terminal side device accesses.

Step 1203: The IAB node receives the first message and fifth information from the network side device.

Exemplarily, the IAB node MT receives the first message, and forwards the first message and the fifth information to the IAB node DU.

Step 1204: The IAB node sends the first message to the terminal-side device through the radio bearer of the terminal-side device indicated by the fifth information carried in the adaptation layer.

Exemplarily, the IAB node DU sends the first message to the terminal side device.

In the second possible implementation manner, in the uplink direction, the flow of the IAB node directly sending the uplink data of the terminal side device to the network side device may be as shown in FIG. 13. As shown in FIG. 13, a schematic diagram of data transmission provided by an embodiment of this application.

Step 1301: The IAB node obtains the second message from the terminal side device.

Exemplarily, the IAB node DU obtains the second message, and forwards the second message to the IAB node MT.

It should be noted that, by way of example, the first packet may be a PDCP PDU.

Step 1302: The IAB node sends the fifth information and the second message to the network side device.

Exemplarily, the IAB node MT carries the fifth information in the adaptation layer.

Step 1303: The network side device receives the second message and the fifth information from the IAB node.

Step 1304: The network side device determines the radio bearer indicated by the fifth information received in the adaptation layer, and sends the second packet to the PDCP entity corresponding to the radio bearer for processing.

Exemplarily, the network-side device may perform processing such as reordering the second message, which is not repeated here.

In the upstream direction, in this embodiment, the IAB node can directly send the uplink data of the terminal-side device to the network-side device, and/or send it to the network-side device through the IAB host, that is, offload the uplink data of the terminal-side device. When the network side device configures the adaptation layer of the IAB node (the adaptation layer is the adaptation layer between the network side device and the IAB node), the adaptation layer configuration information includes at least one of the following parameters: uplink data offload threshold, Main path of upstream data. The uplink data offload threshold is used to instruct the IAB node to send the uplink data of the terminal side device to the IAB host and the network side device only when the amount of uplink data of the terminal side device exceeds the uplink data offload threshold. The main uplink data path is used to indicate whether the IAB node sends the uplink data of the terminal side device to the IAB host node or the network side device when the amount of uplink data of the terminal side device is lower than the uplink data offload threshold.

There is an F1 interface between the IAB host CU and the IAB node DU, which can transmit F1AP messages. The F1AP messages can be F1AP (UE associated F1AP) messages associated with user equipment, or F1AP (Non-UE associated F1AP) associated with non-user equipment. news. Among them, the Non-UE associated F1AP message is mainly used for the management of the F1 interface, and the UE-associated F1AP message is mainly used for the context management of the terminal side device and the transmission of RRC messages.

When the IAB node is working in the non-standalone (Non-Standalone, NSA) mode, an embodiment of the application also provides a method for establishing a signaling bearer, which is used to transmit UE associated F1AP between the IAB node MT and the IAB host DU, respectively Messages and Non-UE associated F1AP messages establish two separate signaling plane bearers, or establish two separate backhaul (BH) RLC channels (channels), so as to ensure that Non-UE associated F1AP messages are transmitted The transmission priority of the F1AP message is higher than the transmission priority of the UE associated F1AP message, which is described in detail below.

As shown in FIG. 14, it is a schematic flowchart of a method for establishing a signaling bearer provided by an embodiment of this application. In Figure 14, the IAB host adopts the CU-DU separation architecture as an example for description. For the IAB host, the interaction between the network side device and the IAB host is actually implemented by the IAB host CU.

Step 1401: The IAB node sends a measurement report to the network side device.

The specific content included in the measurement report and the content type of the measurement report sent by the terminal-side device in the prior art are not limited in the embodiment of the present application, and will not be repeated here.

Step 1402: The network side device sends second indication information to the IAB host CU.

The second indication information shown is the IAB node indication information. According to the second indication information, the IAB host CU establishes a signaling radio bearer 3 (signalling radio bearer 3, SRB3) on the SCG for the IAB node.

Exemplarily, the second indication information may be sent during the SCG attachment process of the IAB node, and the network side device may carry the second indication information through a secondary station attachment request (SgNB Addition Request) message.

It should be noted that the IAB host shown is determined by the network-side device according to the measurement report. The specific determination is not limited in the embodiment of the present application, and will not be repeated here.

Step 1403: The IAB host CU sends the second indication information to the IAB host DU.

The IAB donor CU determines that the IAB node establishes SRB3 on the SCG according to the second indication information.

Exemplarily, the IAB host CU may carry the second indication information in a user equipment context setup request (UE Context Setup Request) message and send it to the IAB host DU, so that the IAB host DU knows that the IAB node that is about to be accessed is the IAB node. The node MT allocates exclusive random access channel (random access channel, RACH) resources.

Step 1404: The IAB host DU sends a user equipment context setup response (UE Context Setup Response) message to the IAB host CU.

According to the second indication information, the IAB donor DU can determine that the IAB node will be accessed, so as to allocate exclusive RACH resources for the IAB node MT.

Exemplarily, in a possible implementation manner, in step 1403, the IAB host CU may also send the first logical channel identifier and the second logical channel identifier to the IAB host DU, and the logical channel corresponding to the first logical channel identifier is used for The UE associated F1AP message or the Non-UE associated F1AP message is transmitted, and the logical channel corresponding to the second logical channel identifier is used to transmit the Non-UE associated F1AP message or the UE associated F1AP message. At this time, the IAB donor DU establishes the signaling plane bearer or BH RLC channel corresponding to the first logical channel indicated by the first logical channel identifier, and establishes the signal corresponding to the second logical channel indicated by the second logical channel identifier. The signaling plane bears or the BH RLC channel, for example, the signaling plane corresponding to the first logical channel identifier carries the SRB or BH RLC channel, and the signaling plane corresponding to the second logical channel identifier carries the SRB or BH RLC channel for the underlying parameters. Configuration, for example: perform corresponding RLC layer configuration, etc., and send the configuration result to the IAB host CU. Wherein, the signaling plane bearer or BH RLC channel corresponding to the first logical channel indicated by the first logical channel identifier is used to transmit UE associated F1AP message or Non-UE associated F1AP message, and the second logical channel identifier indicates The signaling plane bearer or BH RLC channel corresponding to the second logical channel is used to transmit the Non-UE associated F1AP message or the UE associated F1AP message.

In this implementation, the SRB or BH RLC channel corresponding to the logical channel identifier is used to transmit which type of F1AP message, which can be fixed, for example: the SRB or BH RLC channel corresponding to the first logical channel identifier is used to transmit UE associated The F1AP message, the SRB or BH RLC channel corresponding to the second logical channel identifier is used to transmit the Non-UE associated F1AP message, and vice versa. Or, it may not be fixed. Therefore, the IAB host CU needs to further instruct the IAB host DU, that is, the IAB host CU informs the IAB host DU of the correspondence between the SRB or BH RLC channel corresponding to the logical channel and different types of F1AP messages.

Exemplarily, in another possible implementation manner, in step 1403, the IAB host CU does not send the first logical channel identifier and the second logical channel identifier to the IAB host DU. At this time, in step 1404, the IAB host DU According to the second indication information, the signaling plane carrying the UE associated F1AP message carries the SRB or BH RLC channel, and the signaling plane carrying the Non-UE associated F1AP message carries the SRB or BH RLC channel to configure the underlying parameters, and to The IAB donor CU sends the first logical channel identifier and the second logical channel identifier, where the first logical channel identifier corresponds to the signaling plane of the UE associated F1AP message carrying the SRB or BH RLC channel, and the second logical channel identifier corresponds to the transmission of Non-UE The signaling plane of the associated F1AP message carries the SRB or BH RLC channel. The IAB host DU can also send the type indication information of the F1AP message to the IAB host CU, where the type indication information of the F1AP message can indicate the first logical channel identifier and the second logical channel identifier, which are associated with UE F1AP and Non-UE associated F1AP The correspondence of the messages indicates that the first logical channel identifier corresponds to the UE associated F1AP or the Non-UE associated F1AP message, and the second logical channel identifier corresponds to the UE associated F1AP or the Non-UE associated F1AP message.

In this implementation, the IAB host DU is required to further instruct the IAB host CU. The corresponding relationship between the allocated logical channel and different types of F1AP messages will be notified by the IAB host DU to the IAB host CU, so that the IAB host CU can know the corresponding logical channel identifier SRB or BH RLC channel is used to transmit which type of F1AP message.

Step 1405: The IAB host CU sends the first logical channel identifier and the second logical channel identifier to the network side device.

Exemplarily, the first logical channel identifier and the second logical channel identifier may be sent through a secondary station attach response (SgNB Addition Response) message, so that the network side device can associate the first logical channel identifier and the second logical channel identifier with the transmission UE The corresponding relationship between the SRB or RLC channel of the associated F1AP message and the NonUE associated F1AP message is sent to the IAB node.

In this implementation, the IAB host CU is required to further instruct the network-side device, so that the network-side device further instructs the IAB node, that is, further indicates the correspondence between the logical channel and different types of F1AP messages, so that the IAB node can learn the logical channel identifier correspondence Which type of F1AP message is the SRB or BH RLC channel used to transmit.

After the introduction of IAB in the NSA scenario, if a radio link failure (RLF) occurs, there is no clear solution for how the terminal-side device reports. To this end, the embodiment of the present application provides two possible implementation manners. Among them, the NSA scenario refers to a certain node, if it works in the NSA mode, then it is connected to a primary base station and a secondary base station at the same time.

The first possible implementation is that the IAB node works in NSA mode. When the IAB node MT determines that RLF has occurred on the interface between the IAB node and the IAB host, the IAB node MT sends an RLF report message to the network side device. The RLF report message is used to indicate that RLF has occurred on the NR Un interface. The RLF report message can carry Information such as the measurement result of the NR frequency point, so that the network side device can select a new MCG or SCG for the IAB node MT. The interface between the IAB node and the IAB host can be an NR Un interface or other interfaces, which will not be repeated here.

In this implementation, for the IAB node, if the network side device serves as the primary station and the IAB host serves as the secondary station, the IAB node reports the SCG RLF to the primary station. The RLF report can be an existing SCGFailureInformationNR message or Are other newly defined messages. This message carries a cause value to indicate that RLF occurs on the backhaul link. Or, for the IAB node, if the IAB host serves as the primary station and the network side device serves as the secondary station, the IAB node reports the MCG RLF to the secondary station. The RLF report can be a newly defined MCGFailureInformation message or other A newly defined message that carries a cause value to indicate that RLF occurs on the backhaul link.

In the second possible implementation manner, the terminal-side device works in NSA mode. When the IAB node determines that RLF occurs on the interface between the IAB node and the IAB host, the IAB node sends third indication information to the terminal side device, where the third indication information is used to indicate the last hop link of the IAB node RLF occurs. Among them, the IAB host is the parent node of the IAB node, and the IAB node is the parent node or access node of the terminal side device.

When the terminal-side device receives the third indication information from the IAB node, the terminal-side device sends a first message to the network-side device according to the third indication information, and the first message is used to indicate that RLF occurs. The first message may carry information such as the measurement result of the NR frequency point, so that the network side device can select a new MCG or SCG for the terminal side device.

In this implementation, for the terminal-side device, if the network-side device serves as the primary station and the IAB host serves as the secondary station, the terminal-side device sends a first message to the primary station. The first message is used by the terminal-side device to perform SCG In the RLF report, the first message may be an existing SCGFailureInformationNR message, or may be another newly defined message. Or, for the terminal-side device, if the IAB host serves as the primary station and the network-side device serves as the secondary station, the terminal-side device sends a first message to the secondary station, and the first message is used for the terminal-side device to perform MCG RLF In reporting, the first message may be a newly defined MCGFailureInformation message or other newly defined messages. Exemplarily, the first message further includes fourth indication information, the fourth indication information is used to indicate the reason for the occurrence of RLF, and the reason for the occurrence of RLF is that RLF occurs on the access link of the terminal-side device or the terminal-side device responds RLF occurs on the transmission link.

It is worth noting that this implementation can also be applied to IAB multi-hop scenarios. If the child node of the IAB node works in the NSA mode, when the child node of the IAB node receives the third indication information sent from the IAB node, the child node of the IAB node triggers the sending of the first message to the network side device. Wherein, the third indication information is used to indicate that RLF has occurred on a link or used to indicate that RLF has occurred on a backhaul link, and the first message is used to indicate that RLF has occurred. For the child nodes of the IAB node, if the network side device is the primary station and the IAB host is the secondary station, the child node of the IAB node sends a first message to the primary station, and the first message is used for the child of the IAB node The node performs the SCG RLF report, and the first message may be an existing SCGFailureInformationNR message, or may be another newly defined message. Or, for the child node of the IAB node, if the IAB host serves as the primary station and the network side device serves as the secondary station, the child node of the IAB node sends a first message to the secondary station, and the first message is used for the IAB The child nodes of the node perform RLF reporting of the MCG, and the first message may be a newly defined MCGFailureInformation message, or may be another newly defined message.

In this implementation, the child node of the IAB node may be a terminal-side device or other IAB nodes.

Exemplarily, the first message further includes fourth indication information, the fourth indication information is used to indicate the reason for the occurrence of RLF, and the reason for the occurrence of RLF is that RLF occurs on the access link or the RLF occurs on the backhaul link.

In the second possible implementation manner, it is equivalent to adding a trigger condition for the terminal side device or the IAB node to report the first message to the network side device, that is, the terminal side device or the IAB node receives the parent from the terminal side device or the IAB node. The third indication information sent by the node, where the third indication information is used to indicate RLF.

As shown in FIG. 15, a schematic structural diagram of a communication device provided in an embodiment of this application. The communication device can be used to perform actions of the terminal-side device, the network-side device, or the IAB host or IAB node in the foregoing method embodiments. The communication device 1500 includes a transceiver unit 1501 and a processing unit 1502.

When the communication device 1500 executes the actions of the IAB node:

The transceiver unit 1501 is configured to receive a first message and second information from a network side device, the second information is used to indicate the radio bearer of the terminal side device on the link between the terminal side device and the IAB node , Wherein the second information is carried in a peer-to-peer adaptation layer between the IAB node and the network side device and sent;

The processing unit 1502 is configured to send the first message to the terminal-side device through the transceiver unit 1501 through the radio bearer indicated by the second information.

In a possible design, the transceiver unit 1501 is also used for:

Receiving a second message from the terminal-side device through the radio bearer;

The second information is carried in the adaptation layer, and sent to the network side device with the second message.

When the communication device 1500 executes the actions of the network side equipment:

The processing unit 1502 is configured to carry second information in a peer-to-peer adaptation layer between a network-side device and an integrated IAB node for access and backhaul, and the second information is used to indicate that the terminal-side device is on the terminal-side The radio bearer on the link between the device and the IAB node;

The transceiver unit 1501 is configured to send the first message and the second information to the IAB node.

In a possible design, when the anchor point of the data of the terminal side device is on the IAB host, the GTP-U tunnel established for the radio bearer of the terminal side device is the same as the radio bearer of the terminal side device. One correspondence.

In a possible design, before the transceiver unit 1501 sends the first message to the IAB node, the transceiver unit 1501 is further configured to:

Receiving the first information carried by the IAB host in the GTP-U header field corresponding to the GTP tunnel, where the first information is used to indicate the IAB node accessed by the terminal side device.

In a possible design, when the anchor point of the data of the terminal-side device is on the IAB host, the GTP-U tunnel established for the radio bearer of the IAB node is used to transmit data with the same quality of service QoS The data of the terminal-side device.

Receiving the second information carried by the IAB host in the GTP-U header field corresponding to the GTP tunnel.

In a possible design, when the anchor point of the data of the terminal side device is on the network side device, the transceiving unit 1501 is further configured to:

In the process of adding the secondary base station, first information from the IAB host is received; the first information is used to indicate the IAB node that the terminal side device accesses.

In a possible design, the anchor point of the data of the terminal-side device is on the IAB host, and the transceiving unit 1501 is further configured to:

Receiving a second message and second information from the IAB node, where the second information is used to indicate the radio bearer of the terminal-side device on the link between the terminal-side device and the IAB node, and The second information is carried in a peer-to-peer adaptation layer between the network side device and the IAB node.

In a possible design, the transceiver unit 1501 is also used for:

Send a second message and second information to the IAB host, where the second information carries a GTP-U header field, where the GTP-U header field is between the network side device and the IAB host The GTP-U header field corresponding to the GTP tunnel established for the IAB node.

When the communication device 1500 executes the action of the terminal side device:

The transceiver unit 1501 is configured to receive third indication information from an integrated access backhaul IAB node, where the third indication information is used to indicate that the previous hop link of the IAB node has a radio link failure RLF;

The processing unit 1502 is configured to send a first message to the network side device through the above-mentioned transceiver unit 1501 according to the first indication information, and the first message is used to indicate that RLF occurs.

When the communication device 1500 executes the actions of the IAB node:

The processing unit 1502 is configured to determine that a radio link failure RLF occurs on the interface between the IAB node and the IAB host;

The transceiver unit 1501 is configured to send third indication information to the terminal-side device, where the third indication information is used to indicate that a radio link failure RLF occurs on the previous hop link of the IAB node.

FIG. 16 is a schematic structural diagram of a communication device provided by an embodiment of the present application. The communication device shown in FIG. 16 may be a hardware circuit implementation of the communication device shown in FIG. 15. The communication device can be applied to the flowcharts shown in FIGS. 2 to 14 to perform the functions of the network side device, the terminal side device, the IAB node, or the IAB host in the foregoing method embodiment. For ease of description, FIG. 16 only shows the main components of the communication device. Optionally, the communication device may be a network side device, a terminal side device, an IAB node or an IAB host. Optionally, as shown in FIG. 16, the communication device 1600 includes a processor 1601, a memory 1602, a communication interface 1603, and the like.

The processor 1601 is mainly used to process communication protocols and communication data, and to control the entire wireless communication device, execute software programs, and process data of the software programs, for example, to support the wireless communication device to perform the methods described in the above method embodiments Action etc. The memory 1602 is mainly used to store software programs and data. The communication interface 1603 is mainly used for conversion between baseband signals and radio frequency signals and processing of radio frequency signals.

In the embodiment of the present application, in addition, for the specific actions performed by the processor 1601 and the communication interface 1603 in the communication device 1600, reference may be made to the description in the foregoing method embodiments, and details are not described herein again.

Those skilled in the art should understand that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) containing computer-usable program codes.

This application is described with reference to flowcharts and/or block diagrams of methods, equipment (systems), and computer program products according to this application. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing equipment are generated It is a device that realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device. The device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Obviously, those skilled in the art can make various changes and modifications to the application without departing from the scope of the application. In this way, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, this application also intends to include these modifications and variations.

Claims

A data transmission method, characterized by comprising:

The access backhaul integrated IAB node receives the first message and second information from the network side device, and the second information is used to indicate that the terminal side device is on the link between the terminal side device and the IAB node. Radio bearer, where the second information is carried in a peer-to-peer adaptation layer between the IAB node and the network side device and sent;

The IAB node sends the first message to the terminal side device through the radio bearer indicated by the second information.
The method according to claim 1, wherein the second information includes an identifier and a bearer identifier of the terminal-side device.
The method according to claim 2, wherein the identifier of the terminal-side device includes NR CGI and C-RNTI; or, the identifier of the terminal-side device is assigned by the IAB node to the terminal-side device The first F1AP identifier; or, the identifier of the terminal-side device is the second F1AP identifier allocated to the terminal-side device by the IAB host; or, the identifier of the terminal-side device includes the first F1AP identifier and the first F1AP identifier 2. F1AP logo.
The method according to claim 2, wherein the bearer identifier is a data radio bearer identifier or a logical channel identifier.
The method according to any one of claims 1 to 4, wherein the method further comprises:

Receiving, by the IAB node, a second message from the terminal-side device through the radio bearer;

The IAB node carries the second information in the adaptation layer, and sends the second message to the network side device.
A data transmission method, characterized by comprising:

The network-side device carries second information in the peer-to-peer adaptation layer between the network-side device and the integrated access backhaul IAB node, and the second information is used to indicate that the terminal-side device is in the terminal-side device The radio bearer on the link with the IAB node;

The network side device sends the first message and the second information to the IAB node.
The method according to claim 6, wherein the second information includes an identifier and a bearer identifier of the terminal-side device.
The method according to claim 7, wherein the identifier of the terminal-side device includes NR CGI and C-RNTI; or, the identifier of the terminal-side device is assigned by the IAB node to the terminal-side device The first F1AP identifier; or, the identifier of the terminal-side device is the second F1AP identifier allocated to the terminal-side device by the IAB host; or, the identifier of the terminal-side device includes the first F1AP identifier and the first F1AP identifier 2. F1AP logo.
The method according to claim 7, wherein the bearer identifier is a data radio bearer identifier or a logical channel identifier.
The method according to claim 6, wherein when the anchor point of the data of the terminal-side device is on the IAB host, the network-side device establishes a GTP-U tunnel for the radio bearer of the terminal-side device , Corresponds to the radio bearer of the terminal side device one to one.
The method according to claim 10, wherein before the network-side device sends the first message to the IAB node, the method further comprises:

The network side device receives the first information carried by the IAB host in the GTP-U header field corresponding to the GTP tunnel, where the first information is used to indicate the IAB node accessed by the terminal side device.
The method according to claim 11, wherein the first information is an identifier assigned by the network-side device to the IAB node on the interface between the network-side device and the IAB host, or The first information includes the identifier assigned by the network side device to the IAB node on the interface between the network side device and the IAB host, and the IAB host is the IAB node between the network side device and the IAB host. The identifier assigned on the interface between hosts.
The method according to claim 6, wherein when the anchor point of the data of the terminal side device is on the IAB host, the network side device is the GTP-U established for the radio bearer of the IAB node The tunnel is used to transmit the data of the terminal side devices with the same quality of service QoS.
The method according to claim 13, wherein before the network side device sends the first message to the IAB node, the method further comprises:

The network side device receives the second information carried in the GTP-U header field corresponding to the GTP tunnel by the IAB host.
The method according to claim 6, wherein when the anchor point of the data of the terminal side device is on the network side device, the method further comprises:

In the process of adding the secondary base station, the network side device receives the first information from the IAB host; the first information is used to indicate the IAB node that the terminal side device accesses.
The method according to any one of claims 6 to 15, wherein the anchor point of the data of the terminal-side device is on the IAB host, and the method further comprises:

The network-side device receives a second message and second information from the IAB node, and the second information is used to indicate that the terminal-side device is on the link between the terminal-side device and the IAB node. Radio bearer, the second information is carried in a peer adaptation layer between the network side device and the IAB node.
The method of claim 16, wherein the method further comprises:

The network-side device sends a second message and second information to the IAB host, where the second information carries a GTP-U header field, where the GTP-U header field is the network-side device and all The GTP-U header field corresponding to the GTP tunnel established between the IAB hosts for the IAB node.
A reporting method, characterized in that it includes:

The terminal-side device receives third indication information from the integrated IAB node for access and backhaul, where the third indication information is used to indicate that a radio link failure RLF occurred on the previous hop link of the IAB node;

The terminal-side device sends a first message to the network-side device according to the first indication information, where the first message is used to indicate that RLF occurs.
The method according to claim 18, wherein the first message includes fourth indication information, and the fourth indication information is used to indicate that RLF occurs in the access link of the terminal-side device or the terminal RLF occurs on the backhaul link of the side device.
A reporting method, characterized in that it includes:

The access backhaul integrated IAB node determines that the interface between the IAB node and the IAB host has a radio link failure RLF;

The IAB node sends third indication information to the terminal side device, where the third indication information is used to indicate that a radio link failure RLF occurs on the previous hop link of the IAB node.
A communication device, characterized by comprising:

The transceiver unit is configured to receive a first message and second information from a network side device, where the second information is used to indicate the radio bearer of the terminal side device on the link between the terminal side device and the IAB node, Wherein, the second information is carried and sent in a peer-to-peer adaptation layer between the IAB node and the network side device;

The processing unit sends the first message to the terminal side device through the transceiver unit through the radio bearer indicated by the second information.
The apparatus according to claim 21, wherein the second information includes an identifier and a bearer identifier of the terminal-side device.
The apparatus according to claim 22, wherein the identifier of the terminal-side device includes NR CGI and C-RNTI; or, the identifier of the terminal-side device is allocated by the IAB node to the terminal-side device First F1AP identification; or, the identification of the terminal-side device is the second F1AP identification allocated to the terminal-side device by the IAB host; or, the identification of the terminal-side device includes the first F1AP identification and the first F1AP identification 2. F1AP logo.
The apparatus according to claim 22, wherein the bearer identifier is a data radio bearer identifier or a logical channel identifier.
The device according to any one of claims 21 to 24, wherein the transceiver unit is further configured to:

Receiving a second message from the terminal-side device through the radio bearer;

The second information is carried in the adaptation layer, and sent to the network side device with the second message.
A communication device, characterized by comprising:

The processing unit is configured to carry second information in the adaptation layer that is equivalent between the network-side device and the integrated access backhaul IAB node, and the second information is used to indicate that the terminal-side device is in the terminal The radio bearer on the link between the side device and the IAB node;

The transceiver unit is configured to send the first message and the second information to the IAB node.
The apparatus according to claim 26, wherein the second information includes an identifier and a bearer identifier of the terminal-side device.
The apparatus according to claim 27, wherein the identifier of the terminal-side device includes NR CGI and C-RNTI; or, the identifier of the terminal-side device is allocated by the IAB node to the terminal-side device The first F1AP identifier; or, the identifier of the terminal-side device is the second F1AP identifier allocated to the terminal-side device by the IAB host; or, the identifier of the terminal-side device includes the first F1AP identifier and the first F1AP identifier 2. F1AP logo.
The apparatus according to claim 27, wherein the bearer identifier is a data radio bearer identifier or a logical channel identifier.
The apparatus according to claim 26, wherein when the anchor point of the data of the terminal side device is on the IAB host, the GTP-U tunnel established for the radio bearer of the terminal side device is connected to the terminal side device. The radio bearers of the side devices correspond one to one.
The device according to claim 30, wherein before the transceiver unit sends the first message to the IAB node, the transceiver unit is further configured to:

Receiving the first information carried by the IAB host in the GTP-U header field corresponding to the GTP tunnel, where the first information is used to indicate the IAB node accessed by the terminal side device.
The apparatus according to claim 31, wherein the first information is an identifier assigned by the network-side device to the IAB node on the interface between the network-side device and the IAB host, or The first information includes the identifier assigned by the network side device to the IAB node on the interface between the network side device and the IAB host, and the IAB host is the IAB node between the network side device and the IAB host. The identifier assigned on the interface between hosts.
The apparatus according to claim 26, wherein when the anchor point of the data of the terminal side device is on the IAB host, the GTP-U tunnel established for the radio bearer of the IAB node is used for transmission Data of the terminal-side device with the same quality of service QoS.
The device according to claim 26, wherein before the transceiver unit sends the first message to the IAB node, the transceiver unit is further configured to:

Receiving the second information carried by the IAB host in the GTP-U header field corresponding to the GTP tunnel.
The apparatus according to claim 26, wherein when the anchor point of the data of the terminal side device is on the network side device, the transceiving unit is further configured to:

In the process of adding the secondary base station, first information from the IAB host is received; the first information is used to indicate the IAB node that the terminal side device accesses.
The apparatus according to any one of claims 26 to 35, wherein the anchor point of the data of the terminal-side device is on the IAB host, and the transceiving unit is further configured to:

Receiving a second message and second information from the IAB node, where the second information is used to indicate the radio bearer of the terminal-side device on the link between the terminal-side device and the IAB node, and The second information is carried in a peer-to-peer adaptation layer between the network side device and the IAB node.
The device according to claim 26, wherein the transceiver unit is further configured to:

Send a second message and second information to the IAB host, where the second information carries a GTP-U header field, where the GTP-U header field is between the network side device and the IAB host The GTP-U header field corresponding to the GTP tunnel established for the IAB node.
A communication device, characterized by comprising:

A transceiving unit, configured to receive third indication information from an integrated IAB node for access and backhaul, where the third indication information is used to indicate that a radio link failure RLF occurred on the previous hop link of the IAB node;

The processing unit is configured to send a first message to the network side device through the above-mentioned transceiver unit according to the first indication information, where the first message is used to indicate that RLF occurs.
The apparatus according to claim 38, wherein the first message includes fourth indication information, and the fourth indication information is used to indicate that RLF occurs on the access link of the terminal-side device or the terminal RLF occurs on the backhaul link of the side device.
A communication device, characterized by comprising:

A processing unit, configured to determine that a radio link failure RLF occurs on the interface between the IAB node and the IAB host;

The transceiver unit is configured to send third indication information to the terminal-side device, where the third indication information is used to indicate that a radio link failure RLF occurs on the previous hop link of the IAB node.