Data transmission method and device

Abstract

The present application provides a data transmission method and device. The method includes: a distributed unit of an IAB host node with integrated backhaul receives downlink data and service attribute information of the downlink data sent by a centralized unit of the IAB host node; the distributed unit of the IAB host node maps the downlink data to a corresponding radio link control channel BH RLC channel of a backhaul link according to the service attribute information of the downlink data or according to the service attribute information of the downlink data and the address information of the access IAB node, and sends the downlink data to the next-hop IAB node, so as to realize the transmission of user plane data in the IAB system.

Description

[0001] This application is a divisional application of the invention application "A data transmission method and device" with application number 201910118359.1 filed on February 15, 2019. Technical Field

[0002] The present application relates to wireless communication technology, and in particular to a data transmission method and device. Background Art

[0003] In the fifth generation (5G) communication technology, in order to cope with the explosive growth of mobile data traffic and massive device connections in the future, and to meet the emerging new services and application scenarios, the base station (gNB) can adopt a control plane-user plane (CU-DU) separation architecture, that is, a gNB can be composed of a CU and one or more DUs, where the CU and DU are connected through the F1 interface, and the CU and the core network 5GC are connected through the NG interface. The UE accesses the CU through the DU, the PHY / MAC / RLC layer equivalent to the UE is located on the DU, and the PDCP / RRC layer equivalent to the UE is located on the CU.

[0004] For the Integrated Access and Backhaul (IAB) system based on the above architecture, the protocol stack architecture of the user plane in the IAB system is mainly discussed, but no solution is given for how to transmit user plane data in the IAB system. Summary of the invention

[0005] The present application provides a data transmission method and device for realizing the transmission of user plane data in an IAB system.

[0006] In a first aspect, the present application provides a data transmission method, which can be applied to a distributed unit (DU) of an IAB donor node (donor) in an IAB system. The method may include: the IAB donor DU receives downlink data and service attribute information of the downlink data sent by a centralized unit (CU) of the IAB donor; the IAB donor DU maps the downlink data to a corresponding backhaul link radio link control (BH RLC) channel and sends it to a next-hop IAB node (node) according to the service attribute information of the downlink data or according to the service attribute information of the downlink data and the address information of the accessed IAB node.

[0007] In the present application, the IAB donor DU maps the downlink data sent by the IAB donor CU to the corresponding BH RLC channel and sends it to the next-hop IAB node, so that the IAB node can further map the downlink data to the corresponding BHRLC channel and / or the corresponding data radio bearer or logical channel on the air interface, thereby realizing the transmission of user plane data in the IAB system.

[0008] Based on the first aspect, in some possible implementations, the method further includes: a distributed unit of the IAB host node receives service attribute information and a BH RLC channel identifier sent by a centralized unit of the IAB host node, where the service attribute information corresponds to the BH RLC channel identifier; or, the distributed unit of the IAB host node receives service attribute information and address information of an accessed IAB node and a BH RLC channel identifier sent by a centralized unit of the IAB host node, where the service attribute information and the address information of an accessed IAB node correspond to the BH RLC channel identifier; the distributed unit of the IAB host node maps the downlink data to a corresponding BH RLC channel and sends it to a next-hop IAB node according to the service attribute information of the downlink data or the service attribute information of the downlink data and the address information of the accessed IAB node, including: the distributed unit of the IAB host node determines a first BH RLC channel identifier corresponding to the service attribute information of the downlink data according to the correspondence between the service attribute information and the BH RLC channel identifier, and maps the downlink data to the BH corresponding to the first BH RLC channel identifier. The RLC channel is sent to the IAB node of the next hop; or, the distributed unit of the IAB host node determines the first BH RLC channel identifier corresponding to the service attribute information of the downlink data and the address information of the access IAB node according to the correspondence between the service attribute information and the address information of the access IAB node and the BH RLC channel identifier, and maps the downlink data to the BH RLC channel corresponding to the first BH RLC channel identifier and sends it to the IAB node of the next hop.

[0009] Based on the first aspect, in some possible implementations, the method further includes: the distributed unit of the IAB host node sends a logical channel identifier corresponding to the BH RLC channel to the centralized unit of the IAB host node, where the logical channel identifier is used to instruct the centralized unit of the IAB host node to determine the logical channel allocated by the distributed unit of the IAB host node to the BH RLC channel.

[0010] Based on the first aspect, in some possible implementations, the method further includes: a distributed unit of the IAB host node receives service attribute information and service quality QoS information sent by a centralized unit of the IAB host node, and the service attribute information corresponds to the service QoS information; or, the distributed unit of the IAB host node receives service attribute information and address information of an accessed IAB node and service quality QoS information sent by a centralized unit of the IAB host node, and the service attribute information and address information of an accessed IAB node correspond to the service QoS information; the distributed unit of the IAB host node maps the downlink data to a corresponding BH RLC channel and sends it to a next-hop IAB node according to the service attribute information of the downlink data or the service attribute information of the downlink data and the address information of the accessed IAB node, including: the distributed unit of the IAB host node determines, according to the correspondence between the service attribute information and the service QoS information, the first service QoS information corresponding to the service attribute information of the downlink data, and maps the downlink data to the BH corresponding to the first service QoS information. The RLC channel is sent to the IAB node of the next hop; or, the distributed unit of the IAB host node determines the first service QoS information corresponding to the service attribute information of the downlink data and the address information of the access IAB node according to the correspondence between the service attribute information and the address information of the access IAB node and the service QoS information, and maps the downlink data to the BHRLC channel corresponding to the first service QoS information and sends it to the IAB node of the next hop.

[0011] Based on the first aspect, in some possible implementations, the method further includes: the distributed unit of the IAB host node carries the service bearer identifier or service attribute information of the downlink data or the service attribute information and the address information of the access IAB node in the adaptation layer and sends it to the next hop IAB node.

[0012] Based on the first aspect, in some possible implementations, the method further includes: the distributed unit of the IAB host node receives the service attribute information and the service bearer identifier sent by the centralized unit of the IAB host node, and the service attribute information corresponds to the service bearer identifier; or, the distributed unit of the IAB host node receives the service attribute information and the address information of the access IAB node and the service bearer identifier sent by the centralized unit of the IAB host node, and the service attribute information and the address information of the access IAB node correspond to the service bearer identifier; the distributed unit of the IAB host node maps the downlink data to the corresponding BH according to the service attribute information of the downlink data or the service attribute information and the address information of the access IAB node. The RLC channel is sent to the next-hop IAB node, including: the distributed unit of the IAB host node determines the first service bearer identifier corresponding to the service attribute information of the downlink data according to the correspondence between the service attribute information and the service bearer identifier, and carries the first service bearer identifier in the adaptation layer and sends it to the next-hop IAB node; or, the distributed unit of the IAB host node determines the first service bearer identifier corresponding to the service attribute information of the downlink data and the address information of the access IAB node according to the correspondence between the service attribute information and the address information of the access IAB node and the service bearer identifier, and carries the first service bearer identifier in the adaptation layer and sends it to the next-hop IAB node.

[0013] Based on the first aspect, in some possible implementations, the IAB node includes: a distributed unit of the IAB node and a mobile terminal unit of the IAB node; the method also includes: the distributed unit of the IAB host node receives the service bearer identifier or service attribute information or service attribute information of the uplink data and the address information of the access IAB node sent by the mobile terminal unit of the previous hop IAB node, wherein the service bearer identifier or service attribute information or service attribute information of the uplink data and the address information of the access IAB node are carried in the adaptation layer and sent.

[0014] Based on the first aspect, in some possible implementations, the method further includes: the distributed unit of the IAB host node receives indication information sent by the centralized unit of the IAB host node, where the indication information is used to instruct the distributed unit of the IAB host node to enable an F1 application protocol F1AP proxy function;

[0015] The distributed unit of the IAB host node responds to the indication information, allocates corresponding uplink F1 transport network layer UL F1 TNL information for the service bearer, and sends the UL F1 TNL information to the centralized unit of the IAB host node.

[0016] Based on the first aspect, in some possible implementations, the method further includes: the distributed unit of the IAB host node receives downlink F1 transport network layer DL F1 TNL information sent by the centralized unit of the IAB host node, where the DL F1 TNL information is allocated by the access IAB node for service bearer.

[0017] Based on the first aspect, in some possible implementations, the service attribute information of the downlink data is one of the following information: a Differentiated Services Code Point DSCP or a flow label of the downlink data, wherein the service attribute information of the downlink data is encapsulated in an IP layer header field.

[0018] In a second aspect, the present application provides a data transmission method, which can be applied to an IABnode in an IAB system. The method may include: the IAB node obtains downlink data and at least one of the following information of the downlink data: a radio link control BH RLC channel identifier of a backhaul link, a service bearer identifier, service attribute information, or service attribute information and address information of an access IAB node, wherein the service bearer identifier of the downlink data, the service attribute information of the downlink data, and the service attribute information of the downlink data and the address information of an access IAB node are received in an adaptation layer; the IAB node maps the downlink data to a corresponding BH RLC channel for transmission according to the at least one information.

[0019] Based on the second aspect, in some possible implementations, the method further includes: the IAB node receives the BH RLC channel identifier of the previous hop backhaul link and the BH RLC channel identifier of the next hop backhaul link, or the service bearer identifier and the BH RLC channel identifier, or the service attribute information and the BH RLC channel identifier, or the service attribute information and the address information of the access IAB node and the BH RLC channel identifier, sent by the centralized unit of the IAB host node, wherein the BH RLC channel identifier of the previous hop backhaul link corresponds to the BH RLC channel identifier of the next hop backhaul link, the service bearer identifier corresponds to the BH RLC channel identifier, the service attribute information corresponds to the BH RLC channel identifier, and the service attribute information and the address information of the access IAB node correspond to the BH RLC channel identifier; the IAB node maps the downlink data to the corresponding BH RLC channel according to the at least one information, including: the IAB node maps the downlink data to the corresponding BH RLC channel according to the BH RLC channel identifier of the previous hop backhaul link and the BH RLC channel identifier of the next hop backhaul link. The method comprises the following steps: determining a second BH RLC channel identifier corresponding to at least one information of the downlink data, mapping the downlink data to the BH RLC channel corresponding to the second BH RLC channel identifier, and sending the downlink data to the IAB node of the next hop through the BH RLC channel identifier according to the correspondence between the service bearer identifier and the BH RLC channel identifier, or the correspondence between the service attribute information and the BH RLC channel identifier, or the correspondence between the service attribute information and the address information of the access IAB node and the BH RLC channel identifier.

[0020] Based on the second aspect, in some possible implementations, the method further includes: the IAB node receives a service bearer identifier and service quality of service QoS information, or service attribute information and service QoS information, or service attribute information and address information of accessing the IAB node and service QoS information, or BH RLC channel identifier and service QoS information, sent by a centralized unit of the IAB host node, wherein the service bearer identifier corresponds to the service QoS information, the service attribute information corresponds to the service QoS information, the service attribute information and address information of accessing the IAB node correspond to the service QoS information, and the BH RLC channel identifier corresponds to the service QoS information; the IAB node maps the downlink data to the corresponding BH RLC channel for sending according to the at least one information, including: the IAB node maps the downlink data to the corresponding BH RLC channel according to the correspondence between the service bearer identifier and the service QoS information, or the correspondence between the service attribute information and the service QoS information, or the correspondence between the service attribute information and the address information of accessing the IAB node and the service QoS information, or the BH The correspondence between the RLC channel identifier and the service QoS information determines the second service QoS information corresponding to at least one information of the downlink data, and maps the downlink data to the BHRLC channel corresponding to the second service QoS information and sends it to the next hop IAB node.

[0021] Based on the second aspect, in some possible implementations, the method further includes: the IAB node receives a BH RLC channel identifier and a data radio bearer identifier or a logical channel identifier on an air interface, or a service bearer identifier and a data radio bearer identifier or a logical channel identifier on an air interface, or service attribute information and a data radio bearer identifier or a logical channel identifier on an air interface, or service attribute information and address information of accessing the IAB node and a data radio bearer identifier or a logical channel identifier on an air interface, the BH RLC channel identifier corresponds to the data radio bearer identifier or a logical channel identifier on the air interface, the service bearer identifier corresponds to the data radio bearer identifier or a logical channel identifier on the air interface, and the service bearer identifier corresponds to the data radio bearer identifier or a logical channel identifier on the air interface; the service attribute information and the address information of accessing the IAB node correspond to the data radio bearer identifier or a logical channel identifier on the air interface; the IAB node maps the downlink data to the corresponding BH RLC channel according to the at least one information and sends it, including: the IAB node maps the downlink data to the corresponding BH RLC channel according to the BH The correspondence between the RLC channel identifier and the data radio bearer identifier or the logical channel identifier, or the correspondence between the service bearer identifier and the data radio bearer identifier or the logical channel identifier, or the correspondence between the service attribute information and the data radio bearer identifier or the logical channel identifier, or the correspondence between the service attribute information and the address information of the access IAB node and the data radio bearer identifier or the logical channel identifier, determines the first data radio bearer identifier or the first logical channel identifier on the air interface corresponding to at least one information of the downlink data, and maps the downlink data to the radio bearer corresponding to the first data radio bearer identifier or the logical channel corresponding to the first logical channel identifier and sends it to the terminal.

[0022] Based on the second aspect, in some possible implementations, the IAB node includes: a distributed unit of the IAB node and a mobile terminal unit of the IAB node; the method also includes: the mobile terminal unit of the IAB node sends the service bearer identifier or service attribute information of the uplink data or the service attribute information and the address information of the access IAB node to the distributed unit of the IAB node on the next hop intermediate backhaul link.

[0023] Based on the second aspect, in some possible implementations, the method further includes: the IAB node mapping the uplink data to a BH RLC channel for receiving the downlink data and sending the uplink data, and the uplink data and the downlink data have the same service QoS information.

[0024] Based on the second aspect, in some possible implementations, the method further includes: the IAB node allocating downlink F1 transport network layer DL F1 TNL information for the service bearer, and sending the DL F1 TNL information to a centralized unit of the IAB host node.

[0025] In a third aspect, the present application provides a communication device, which may be a data transmission device or a chip or system on chip in the data transmission device, or a functional module in the data transmission device for implementing the method described in the first aspect or any possible implementation method of the first aspect. The communication device may implement the functions performed by the IAB donor DU in the above aspects or in each possible implementation method, and the functions may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. For example, the communication device may include: a first receiving unit for receiving downlink data and service attribute information of the downlink data sent by a centralized unit of the IAB host node; a first sending unit for mapping the downlink data to the corresponding radio link control BH RLC channel of the backhaul link and sending it to the next hop IAB node according to the service attribute information of the downlink data or according to the service attribute information of the downlink data and the address information of the access IAB node.

[0026] Based on the third aspect, in some possible implementations, the device also includes: a second receiving unit, used to receive service attribute information and a BH RLC channel identifier sent by a centralized unit of the IAB host node, the service attribute information corresponding to the BH RLC channel identifier; the first sending unit includes: a determining subunit and a sending subunit; the determining subunit is used to determine a first BH RLC channel identifier corresponding to the service attribute information of the downlink data according to the service attribute information and the BH RLC channel identifier; the sending subunit is used to map the downlink data to the BH RLC channel corresponding to the first BH RLC channel identifier and send it to the next hop IAB node.

[0027] Based on the third aspect, in some possible implementations, the device also includes: a second sending unit, used to send a BH RLC channel identifier and a logical channel identifier to a centralized unit of the IAB host node, the BH RLC channel identifier corresponds to the logical channel identifier, and the BH RLC channel identifier and the logical channel identifier are used to indicate that the centralized unit of the IAB host node determines the logical channel allocated by the distributed unit of the IAB host node to the BH RLC channel.

[0028] Based on the third aspect, in some possible implementations, the device also includes: a second receiving unit, used to receive service attribute information and service quality QoS information sent by a centralized unit of the IAB host node, the service attributes corresponding to the information and the service QoS information; the first sending unit includes: a determining subunit and a sending subunit; the determining subunit is used to determine the first service QoS information corresponding to the service attribute information of the downlink data according to the service attribute information and the service QoS information; the sending subunit is used to map the downlink data to the BH RLC channel corresponding to the first service QoS information and send it to the next hop IAB node.

[0029] Based on the third aspect, in some possible implementations, the device further includes: a third sending unit, configured to carry the service bearer identifier or service attribute information of the downlink data in the adaptation layer and send it to the next-hop IAB node.

[0030] Based on the third aspect, in some possible implementations, the device also includes: a second receiving unit, used to receive service attribute information and a service bearer identifier sent by a centralized unit of the IAB host node, and the service attribute information corresponds to the service bearer identifier; the third sending unit includes: a determination subunit and a sending subunit; the determination subunit is used to determine the first service bearer identifier corresponding to the service attribute information of the downlink data according to the service attribute information and the service bearer identifier; the sending subunit is used to carry the first service bearer identifier in the adaptation layer and send it to the next hop IAB node.

[0031] Based on the third aspect, in some possible implementations, the IAB node includes: a distributed unit of the IAB node and a mobile terminal unit of the IAB node; the device also includes: a third receiving unit, used to receive the service bearer identifier or service attribute information of the uplink data sent by the mobile terminal unit of the next-hop IAB node, wherein the service bearer identifier or service attribute information of the uplink data is carried in the adaptation layer and sent.

[0032] Based on the third aspect, in some possible implementations, the device further includes: a fourth receiving unit, a first allocation unit, and a fourth sending unit; the fourth receiving unit is used to receive indication information sent by the centralized unit of the IAB host node, and the indication information is used to instruct the distributed unit of the IAB host node to enable the F1 application protocol F1AP proxy function; the first allocation unit is used to respond to the indication information and allocate corresponding uplink F1 transport network layer UL F1 TNL information to the service bearer; the fourth sending unit is used to send the UL F1 TNL information to the centralized unit of the IAB host node.

[0033] Based on the third aspect, in some possible implementations, the device further includes: a fifth receiving unit, configured to receive downlink F1 transport network layer DL F1 TNL information sent by a centralized unit of the IAB host node, where the DL F1 TNL information is allocated by the access IAB node for service bearer.

[0034] Based on the third aspect, in some possible implementations, the service attribute information of the downlink data is one of the following information: the differentiated service code point DSCP or flow label of the downlink data; the DSCP of the downlink data and the address information of the access IAB node; the flow label and the address information of the access IAB node; wherein the service attribute information of the downlink data is encapsulated in the IP layer header field.

[0035] The first receiving unit to the fifth receiving unit mentioned in the third aspect above can be a receiving interface, a receiving circuit or a receiver, etc.; the sending subunit in the first sending unit and the second sending unit to the fourth sending unit can be a sending interface, a sending circuit or a transmitter, etc.; the determination subunit and the first allocation unit in the first sending unit can be one or more processors.

[0036] In a fourth aspect, the present application provides a communication device, which may be a data transmission device or a chip or system on chip in a data transmission device, or a functional module in a data transmission device for implementing the method described in the second aspect or any possible implementation method of the second aspect. The communication device may implement the functions performed by the IAB node in the above aspects or in each possible implementation method, and the functions may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. For example, the communication device may include: a sixth receiving unit 901, which is used to receive downlink data and at least one of the following information of the downlink data: a radio link control BH RLC channel identifier of a backhaul link, a service bearer identifier, service attribute information or service attribute information and address information of an access IAB node, wherein the service bearer identifier of the downlink data, the service attribute information of the downlink data, and the service attribute information of the downlink data and the address information of the access IAB node are received from an adaptation layer; a fifth sending unit 902, which is used to map the downlink data to a corresponding BH RLC channel for transmission according to the at least one information.

[0037] Based on the fourth aspect, in some possible implementations, the device further includes: a seventh receiving unit, configured to receive a BH RLC channel identifier of a previous hop backhaul link and a BH RLC channel identifier of a next hop backhaul link, a service bearer identifier and a BH RLC channel identifier, and / or service attribute information and a BH RLC channel identifier sent by a centralized unit of the IAB host node, wherein the BH RLC channel identifier of the previous hop backhaul link corresponds to the BH RLC channel identifier of the next hop backhaul link, the service bearer identifier corresponds to the BH RLC channel identifier, and the service attribute information corresponds to the BH RLC channel identifier; the fifth sending unit includes: a determining subunit and a sending subunit; the determining subunit is configured to determine a second BH RLC channel identifier corresponding to at least one information of the downlink data according to the BH RLC channel identifier of the previous hop backhaul link and the BH RLC channel identifier of the next hop backhaul link, the service bearer identifier and the BH RLC channel identifier, and / or the service attribute information and the BH RLC channel identifier; the sending subunit is configured to map the downlink data to the second BH The BH RLC channel corresponding to the RLC channel identifier is sent to the next hop IAB node.

[0038] Based on the fourth aspect, in some possible implementations, the device also includes: a seventh receiving unit, used to receive a service bearer identifier and service quality of service QoS information, service attribute information and service QoS information, and / or a BH RLC channel identifier and service QoS information sent by a centralized unit of the IAB host node, wherein the service bearer identifier corresponds to the service QoS information, the service attribute information corresponds to the service QoS information, and the BH RLC channel identifier corresponds to the service QoS information; the fifth sending unit includes: a determining subunit and a sending subunit; the determining subunit is used to determine the second service QoS information corresponding to at least one information of the downlink data according to the service bearer identifier and the service QoS information, the service attribute information and the service QoS information, and / or the BH RLC channel identifier and the service QoS information; the sending subunit is used to map the downlink data to the BH RLC channel corresponding to the second service QoS information and send it to the next hop IAB node.

[0039] Based on the fourth aspect, in some possible implementations, the device further includes: a seventh receiving unit, configured to receive a BH RLC channel identifier and a data radio bearer identifier or a logical channel identifier on an air interface, a service bearer identifier and a data radio bearer identifier or a logical channel identifier on an air interface, and / or service attribute information and a data radio bearer identifier or a logical channel identifier on an air interface, sent by a centralized unit of the IAB host node, wherein the BH RLC channel identifier corresponds to the data radio bearer identifier or the logical channel identifier on the air interface, the service bearer identifier corresponds to the data radio bearer identifier or the logical channel identifier on the air interface, and the service bearer identifier corresponds to the data radio bearer identifier or the logical channel identifier on the air interface; the fifth sending unit includes: a determining subunit and a sending subunit; the determining subunit is configured to determine, according to the BH The RLC channel identifier and the data radio bearer identifier or the logical channel identifier, the service bearer identifier and the data radio bearer identifier or the logical channel identifier and / or the service attribute information and the data radio bearer identifier or the logical channel identifier determine the first data radio bearer identifier or the first logical channel identifier on the air interface corresponding to at least one information of the downlink data; the sending subunit is used to map the downlink data to the radio bearer corresponding to the first data radio bearer identifier or the logical channel corresponding to the first logical channel identifier and send it to the terminal.

[0040] Based on the fourth aspect, in some possible implementations, the device further includes: a sixth sending unit, configured to send a service bearer identifier or service attribute information of the uplink data to a distributed unit of the IAB node on the next-hop intermediate backhaul link.

[0041] Based on the fourth aspect, in some possible implementations, the device further includes: a seventh sending unit, configured to map the uplink data to a BH RLC channel for receiving the downlink data and send the uplink data, wherein the uplink data and the downlink data have the same service QoS information.

[0042] Based on the fourth aspect, in some possible implementations, the device further includes: a second allocation unit and an eighth sending unit; the second allocation unit is used to allocate downlink F1 transport network layer DL F1 TNL information for the service bearer; the eighth sending unit is used to send the DL F1 TNL information to a centralized unit of the IAB host node.

[0043] The sixth receiving unit and the seventh receiving unit mentioned in the fourth aspect above can be a receiving interface, a receiving circuit or a receiver, etc.; the sending subunit in the fifth sending unit and the sixth sending unit to the eighth sending unit can be a sending interface, a sending circuit or a transmitter, etc.; the determination subunit and the second allocation unit in the fifth sending unit can be one or more processors.

[0044] In a fifth aspect, the present application provides a communication device, which may be a chip or a system on chip in an IAB donor DU. The communication device may implement the functions performed by the IAB donor DU in the above aspects or possible implementations, and the functions may be implemented by hardware, such as: in one possible implementation, the communication device may include: a processor and a communication interface, and the processor may be used to support the communication device to implement the functions involved in the above first aspect or any possible implementation of the first aspect, for example: the processor may receive downlink data and service attribute information of the downlink data sent by the IAB donor CU through the communication interface; and is also used to map the downlink data to the corresponding BH RLC channel and send it to the next hop IAB node according to the service attribute information of the downlink data. In another possible implementation, the communication device may also include a memory, and the memory is used to store computer execution instructions and data necessary for the communication device. When the communication device is running, the processor executes the computer execution instructions stored in the memory, so that the communication device performs the data transmission method as described in the above first aspect or any possible implementation of the first aspect.

[0045] In a sixth aspect, the present application provides a communication device, which may be a chip or a system on chip in an IAB node. The communication device may implement the functions performed by the IAB node in the above aspects or possible implementations, and the functions may be implemented by hardware, such as: In a possible implementation, the communication device may include: a processor and a communication interface, and the processor may be used to support the communication device to implement the functions involved in the above second aspect or any possible implementation of the second aspect, for example: the processor may obtain downlink data and at least one of the following information of the downlink data through the communication interface: a BH RLC channel identifier, a service bearer identifier, or service attribute information; and is also used to map the downlink data to the corresponding radio link control channel BH RLC channel of the backhaul link for transmission according to at least one information. In another possible implementation, the communication device may also include a memory, and the memory is used to store computer-executable instructions and data necessary for the communication device. When the communication device is running, the processor executes the computer-executable instructions stored in the memory, so that the communication device performs the data transmission method as described in the above second aspect or any possible implementation of the second aspect.

[0046] In a seventh aspect, the present application provides a computer-readable storage medium, which stores instructions. When the instructions are executed on a computer, the computer-readable storage medium is used to execute any one of the data transmission methods of the first to third aspects above.

[0047] In an eighth aspect, the present application provides a computer program or a computer program product. When the computer program or the computer program product is executed on a computer, the computer implements any one of the data transmission methods of the first to third aspects above.

[0048] In a ninth aspect, the present application provides a communication system, comprising an IAB donor DU, an IAB node, and an IAB donor CU; wherein the IAB donor DU is used to execute any of the data transmission methods in the first aspect; the IAB node is used to execute any of the data transmission methods in the second aspect; and the IAB donor CU is used to execute any of the data transmission methods in the third aspect. Optionally, the communication system may be an IAB system.

[0049] It should be understood that the third to ninth aspects of the present application are consistent with the technical solutions of the first to second aspects of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background technology, the drawings required for use in the embodiments of the present application or the background technology will be described below.

[0051] Figure 1 A schematic diagram of the structure of a communication system in an embodiment of the present application;

[0052] Figure 2A This is a schematic diagram of a first architecture of a communication system in an embodiment of the present application;

[0053] Figure 2B A schematic diagram of a second architecture of a communication system in an embodiment of the present application;

[0054] Figure 2C A third schematic diagram of the architecture of the communication system in the embodiment of the present application;

[0055] Figure 2D This is a schematic diagram of a fourth architecture of a communication system in an embodiment of the present application;

[0056] Figure 3 In the embodiment of this application Figure 2A Schematic diagram of the process of downlink data transmission method under the architecture Figure 1 ;

[0057] Figure 4 In the embodiment of this application Figure 2A Schematic diagram of the process of uplink data transmission method under the architecture Figure 1 ;

[0058] Figure 5 In the embodiment of this application Figure 2A Schematic diagram 2 of the flow chart of the downlink data transmission method under the architecture;

[0059] Figure 6 In the embodiment of this application Figure 2A Schematic diagram 2 of the flow chart of the uplink data transmission method under the architecture;

[0060] Fig. 7A In the embodiment of this application Figure 2B Schematic diagram of the process of downlink data transmission method under the architecture Figure 1 ;

[0061] Figure 7B In the embodiment of this application Figure 2B Schematic diagram 2 of the flow chart of the downlink data transmission method under the architecture;

[0062] Figure 8 The structure of the communication device in the embodiment of the present application is shown in FIG. Figure 1 ;

[0063] Fig. 9This is a second structural diagram of a communication device in an embodiment of the present application;

[0064] Fig.10 The structure of the communication device in the embodiment of the present application is shown in FIG. Figure 3 . DETAILED DESCRIPTION

[0065] The following is a description of the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. In the following description, reference is made to the drawings that form a part of the present application and show the specific aspects of the embodiments of the present application or the specific aspects of the embodiments of the present application in an illustrative manner. It should be understood that the embodiments of the present application can be used in other aspects and may include structural or logical changes not depicted in the drawings. Therefore, the following detailed description should not be understood in a restrictive sense, and the scope of the present application is defined by the appended claims. For example, it should be understood that the disclosure of the described method can be equally applicable to the corresponding device or system for performing the method, and vice versa. For example, if one or more specific method steps are described, the corresponding device may include one or more units such as functional units to perform the one or more method steps described (for example, one unit performs one or more steps, or multiple units, each of which performs one or more of the multiple steps), even if such one or more units are not explicitly described or illustrated in the drawings. On the other hand, for example, if a specific device is described based on one or more units such as functional units, the corresponding method may include a step to perform the functionality of the one or more units (e.g., a step to perform the functionality of the one or more units, or multiple steps, each of which performs the functionality of one or more of the multiple units), even if such one or more steps are not explicitly described or illustrated in the drawings. Further, it should be understood that, unless otherwise explicitly stated, the features of the various exemplary embodiments and / or aspects described herein may be combined with each other.

[0066] The embodiment of the present application provides a communication system, which may be an IAB system. The communication system may include: a terminal, an IAB node and an IAB donor; wherein the IAB node may be divided into an access IAB node and an IAB node on an intermediate backhaul link. The access IAB node mentioned here refers to an IAB node that is connected to the terminal, and the interface between the terminal and the IAB node is recorded as a Uu interface (i.e., an air interface); the IAB node on the intermediate backhaul link refers to a relay node located between the access IAB node and the IAB donor, and the interface between the IAB node on the intermediate backhaul link and the access IAB node and the IAB donor is recorded as a Un interface. The names of these interfaces are only examples and do not represent limitations on the interfaces. When the communication system version changes, the corresponding names may also be replaced by the names of corresponding functions in other wireless communication networks, all of which fall within the scope of the claims of the present application and their equivalent technologies. The above-mentioned terminal can be a device that provides voice or data connectivity to users, for example, it can also be called user equipment (UE, User Equipment), mobile station (mobile station), subscriber unit (subscriber unit), station (STAtion) or terminal equipment (TE, Terminal Equipment), etc. The terminal can be a cellular phone (cellular phone), a personal digital assistant (PDA, Personal Digital Assistant), a wireless modem (modem), a handheld device (handheld), a laptop computer (laptop computer), a cordless phone (cordless phone), a wireless local loop (WLL, Wireless Local Loop) station or a tablet computer (pad), etc. With the development of wireless communication technology, devices that can access a wireless communication system, can communicate with the network side of a wireless communication system, or can communicate with other devices through a wireless communication system can all be terminals in the embodiments of the present application, for example, terminals and cars in intelligent transportation, household appliances in smart homes, power meter reading instruments in smart grids, voltage monitoring instruments, environmental monitoring instruments, video monitoring instruments in intelligent security networks, cash registers, etc. In the embodiments of the present application, the terminal can communicate with network devices, and multiple terminals can also communicate with each other. The terminal can be static or mobile.

[0067] Take the two-hop data backhaul scenario as an example. Figure 1 This is a schematic diagram of the structure of the communication system in the embodiment of the present application, see Figure 1As shown, the communication system 10 includes: a terminal (such as UE) 11, an IAB node 1, an IAB node 2 and an IAB donor.

[0068] Among them, UE accesses IAB node2 (that is, accesses IAB node), and IAB donor is connected to the core network (such as 5GC) through the NG interface. IAB donor is the parent node of IAB node1, IAB node1 is the parent node of IAB node2, and IAB node2 is the parent node of UE. IAB node1 can be divided into two units, DU and MT, IAB node2 can be divided into two units, DU and MT, and IAB donor can be divided into two units, DU and CU. IAB node1 DU and IAB node1 MT communicate through the internal interface, IAB node2 DU and IAB node2 MT communicate through the internal interface, and IAB donor DU and IAB donor CU communicate through the F1 interface. The interface between UE and IAB node2 (specifically, the interface between UE and IAB node2 DU) is recorded as Uu interface, the interface between IAB node2 and IAB node1 (specifically, the interface between IAB node2 MT and IAB node1 DU) is recorded as Un2 interface, and the interface between IAB node1 and IAB donor (specifically, the interface between IAB node1 MT and IAB donor DU) is recorded as Un1 interface.

[0069] In practical applications, the IAB system is also applied to N-hop data backhaul scenarios, such as three-hop data backhaul scenarios, five-hop data backhaul scenarios, eight-hop data backhaul scenarios, etc. Correspondingly, the number N of IAB nodes in the IAB system can be an integer greater than or equal to 2, such as 3, 5, 8, etc., which is not specifically limited in the embodiments of the present application.

[0070] Figure 2A This is a schematic diagram of the first architecture of the communication system in the embodiment of the present application. Figure 2A In the IAB system of the architecture shown, a per UE per bearer is established between the IAB node2 and the IAB donor CU (that is, a corresponding General Packet Radio Service Tunnelling Protocol (GTP) tunnel (i.e., GTP-U tunnel) is established for each UE data radio bearer (DRB). The UE data is routed between the DU and the CU in the IAB donor through the IP layer.

[0071] Figure 2B is a schematic diagram of a second architecture of a communication system in an embodiment of the present application, in Figure 2B In the IAB system of the architecture shown, a per UE per bearer GTP tunnel (i.e., a GTP-U tunnel) is established between the IAB node2 and the IAB donor DU. The GTP between the DU and the CU in the IAB donor can be per UE per bearer or per IAB node1 MT per bearer (i.e., a corresponding GTP tunnel (i.e., a GTP-U tunnel) is established for each data radio bearer of the IAB node1 MT).

[0072] In addition, in addition to the IAB system of the above architecture, the embodiment of the present application also provides an IAB system of an architecture. According to different security mechanisms, the IAB system under the architecture can be further divided into: Figure 2C A third schematic diagram of the architecture of the communication system in the embodiment of the present application is shown in FIG. Figure 2C In the IAB system of the shown architecture, the Internet Protocol Security (IPsec) is used to securely protect the GTP tunnel. At this time, a per UE per bearer GTP is established between the IAB node2 and the IAB donor CU. The GTP between the DU and the CU in the IAB donor can be per UE per bearer or per IAB node1 MT per bearer. Among them, the per UE per bearer GTP is securely protected by IPsec.

[0073] Figure 2D This is a schematic diagram of a fourth architecture of a communication system in an embodiment of the present application. Figure 2D In the IAB system of the architecture shown, the Packet Data Convergence Protocol (PDCP) is used to securely protect the GTP. At this time, a per UE per bearer GTP is established between the IAB node2 and the IAB donor CU. The GTP between the DU and the CU in the IAB donor can be per UE per bearer or per IAB node1 MT per bearer. Among them, the per UE per bearer GTP is securely protected by the PDCP layer.

[0074] The embodiment of the present application provides a data transmission method, which can be applied to the above IAB system. The data transmission method is described in detail below in conjunction with the IAB systems of different architectures in the above two-hop data backhaul scenario.

[0075] Embodiment 1:

[0076] The present application provides a data transmission method, which is applied to the above Figure 2A The IAB system shown.

[0077] It should be noted that, in this first embodiment, the bearer mapping on each interface during user data transmission is determined by the IABdonor CU.

[0078] Figure 3 In the embodiment of this application Figure 2A Schematic diagram of the process of downlink data transmission method under the architecture Figure 1 , see Figure 3 As shown by the solid line, the downlink data transmission method may include:

[0079] S301: IAB donor CU receives downlink data from UE;

[0080] S302: The IAB donor CU carries the service attribute information of the downlink data in the IP layer header field and sends it to the IAB donor DU together with the downlink data;

[0081] Here, the service attribute information of the downlink data may be: DSCP / Flow Label (indicating DSCP or Flow Label).

[0082] In the embodiment of the present application, in order for the IAB donor CU to determine the bearer mapping on each interface when user data is transmitted, the IAB donor DU and each IAB node DU need to send the logical channel identifier (LCID, LogicChannel ID entification) corresponding to the BH RLC channel to the IAB donor CU. At this time, the BH RLC channel identifier can be the identifier of the logical channel corresponding to the BH RLC channel.

[0083] Specifically, because the IAB donor DU allocates the logical channel corresponding to the BH RLC channel on the Un1 interface, the IABnode1 DU allocates the logical channel corresponding to the BH RLC channel on the Un2 interface, and the IAB node2 DU allocates the logical channel corresponding to the UE DRB on the Uu interface. In order to facilitate the IAB donor CU to decide the mapping of the user plane bearers of each interface, the IAB donor DU needs to feed back the LCID of the logical channel allocated for the BH RLC channel on the Un1 interface to the IAB donor CU, and the IAB node1 DU needs to feed back the LCID of the logical channel allocated for the BH RLC channel on the Un2 interface to the IAB donor CU. Then, see Figure 3 As shown by the middle dotted line, the above method may further include: S303: the IAB donor DU sends the logical channel identifier corresponding to the BH RLC channel to the IAB donor CU, and the IAB node1 DU sends the logical channel identifier corresponding to the BH RLC channel to the IAB donorCU.

[0084] It should be noted that the above-mentioned BH RLC channel identifier may be a logical channel identifier corresponding to the BH RLC channel.

[0085] Then, the IAB donor CU can determine the correspondence between the service attribute information and the BH RLC channel identifier based on the BH RLC channel identifier sent by the IAB donor DU. For example, the IAB donor CU determines the correspondence between the DSCP / Flow Label and the BH RLC channel identifier on the Un1 interface, or the IAB donor CU determines the correspondence between the DSCP / Flow Label+the address information of the access IAB node and the BH RLC channel identifier on the Un1 interface. Then, the IAB donor CU sends the above-determined DSCP / Flow Label and the corresponding BH RLC channel identifier on the Un1 interface or the determined DSCP / Flow Label+the address information of the access IAB node and the corresponding BH RLC channel identifier on the Un1 interface to the IAB donor DU through the F1AP message between the IAB donor CU and the IAB donorDU.

[0086] In addition, the IAB donor CU can determine the correspondence between the BH RLC channel identifier of the previous hop backhaul link (on the Un1 interface) and the BH RLC channel identifier of the next hop backhaul link (on the Un2 interface) according to the BH RLC channel identifier sent by the IAB node1 DU, or determine the correspondence between the service bearer identifier (UE Bearer ID) and the BH RLC channel identifier, or determine the correspondence between the service attribute information and the BH RLC channel identifier, or determine the correspondence between the service attribute information and the address information of the access IAB node and the BH RLC channel identifier. Then, the IAB donor CU sends the determined BH RLC channel identifier on the Un1 interface and the BH RLC channel identifier on the Un2 interface, or the determined UE Bearer ID and the BH RLC channel identifier, or the determined DSCP / flow label and the BH RLC channel identifier, or the determined DSCP / flowlabel+the address information of the access IAB node and the BH RLC channel identifier to the IAB node1 DU through the F1AP message between the IAB donor CU and the IAB node1 DU.

[0087] In some possible implementations, the IAB node2 DU may also feed back the LCID of the logical channel allocated to the UE DRB on the Uu interface to the IAB donor CU. Figure 3As shown by the dotted line in the middle, the above method may further include: S304: IAB node2DU sends the LCID of the Uu interface to the IAB donor CU. The IAB donor CU may determine the correspondence between the BH RLC channel identifier on the Un2 interface and the DRB ID / LCID on the Uu interface according to the LCID of the Uu interface sent by the IAB node2DU, or the IAB donor CU determines the correspondence between the UE Bearer ID and the DRB ID / LCID on the Uu interface, or the IAB donor CU determines the correspondence between the DSCP / flow label and the DRB ID / LCID on the Uu interface, or the IAB donor CU determines the correspondence between the DSCP / flow label+address information of the access IAB node and the DRB ID / LCID on the Uu interface. Then, the IAB donor CU sends the determined BH RLC channel identifier on the Un2 interface and the corresponding DRB ID / LCID on the Uu interface, or the determined UE Bearer ID and the corresponding DRB ID / LCID on the Uu interface, or the determined DSCP / flowlabel and the corresponding DRB ID / LCID on the Uu interface, or the determined DSCP / flow label+address information of the access IAB node and the corresponding DRB ID / LCID on the Uu interface to the IAB node2 DU through the F1AP message between the IAB donor CU and the IAB node2 DU.

[0088] It should be noted that the above UE Bearer ID can be used to distinguish different bearers of different UEs under the IAB donor CU. It can be a newly defined identifier, or it can be represented by two parts, the UE identifier and the bearer identifier, or it can be represented by a tunnel endpoint identifier (GTP TEID, Tunnel Endpoint ID). Of course, the UE Bearer ID can also exist in other representation forms, which are not specifically limited in the embodiments of the present application.

[0089] Next, see Figure 3 As shown by the solid line, after S302, S305 is executed;

[0090] S305: The IAB donor DU extracts the service attribute information (such as DSCP / flow label) of the downlink data from the IP layer header field, and determines the first BH RLC channel identifier corresponding to the service attribute information of the downlink data according to the correspondence between the DSCP / flow label sent by the IAB donor CU and the BH RLC channel on the Un1 interface;

[0091] Alternatively, the IAB donor DU further extracts the address information of the access IAB node from the IP layer header field, and determines the service attribute information of the downlink data and the first BH RLC channel identifier corresponding to the address information of the access IAB node according to the correspondence between the DSCP / flow label+the address information of the access IAB node sent by the IAB donor CU and the BH RLC channel on the Un1 interface. Exemplarily, the address information of the access IAB node may be a destination ID, i.e., the IP address of the access IAB node (e.g., the IP address of IAB node2).

[0092] S306: The IAB donor DU maps the downlink data to the BHRLC channel corresponding to the first BH RLC channel identifier on the Un1 interface and sends it to the IAB node1 MT (i.e., the next hop IAB node);

[0093] In some possible implementations, the IAB donor DU may carry the service bearer identifier or service attribute information corresponding to the above-mentioned downlink data or the service attribute information and the address information of the access IAB node in the adaptation layer and send it to the IABnode1 MT. The IAB donor DU may obtain the corresponding relationship between the service attribute information (such as DSCP / flowlabel) and the UE bearer ID from the IAB donor CU, or the IAB donor DU may obtain the corresponding relationship between the service attribute information (such as DSCP / flow label) and the address information of the access IAB node and the UE bearer ID from the IAB donor CU. In this way, the IAB donor DU may obtain the corresponding UE bearer ID according to the DSCP / flow label extracted from the IP layer, or according to the DSCP / flow label extracted from the IP layer + the address information of the access IAB node, and then carry the UE bearer ID in the adaptation layer and send it to the IAB node1 MT.

[0094] In some possible implementations, the IAB donor CU may also send the address information of the access IAB node corresponding to the downlink data, that is, the IP address of the access IAB node (i.e., IAB node2) corresponding to the downlink data to the IABdonor DU. Then, the IAB donor DU may carry the service attribute information (i.e., DSCP / flow label) corresponding to the above-mentioned downlink data in the adaptation layer, and may also carry the DSCP / flow label+address information of the access IAB node (indicating the DSCP / flow label and the address information of the access IAB node) and send it to the IAB node1 MT.

[0095] S307: The IAB node1 MT sends the downlink data to the IAB node1 DU through the internal interface, and at the same time, sends at least one information of the downlink data to the IAB node1 DU through the internal interface.

[0096] Among them, at least one information of the above-mentioned downlink data may include: BH RLC channel identifier, service bearer identifier or service attribute information or service attribute information and address information of access IAB node, that is, IAB node1 MT sends the BH RLC channel identifier carried on Un1 interface to IAB node1 DU through the internal interface, or sends the UE bearer ID corresponding to the downlink data to IAB node1 DU through the internal interface. Alternatively, the DSCP / flow label or DSCP / flow label+address information of access IAB node corresponding to the downlink data is sent to IAB node1DU through the internal interface.

[0097] It should be noted that the service bearer identifier or service attribute information or service attribute information and the address information of the access IAB node sent by IAB node1 MT to IAB node1 DU are carried by IAB donor DU in the adaptation layer and sent to IABnode1MT. Of course, the adaptation layer can also carry DSCP / flow label + address information of the access IAB node.

[0098] S308: The IAB node1 DU determines a second BH RLC channel identifier corresponding to at least one information of the downlink data according to the BHRLC channel identifier of the previous hop backhaul link (on the Un1 interface) and the BH RLC channel identifier of the next hop backhaul link (on the Un2 interface) sent by the IAB donor CU, or the service bearer identifier and the BHRLC channel identifier, or the service attribute information and the BH RLC channel identifier, or the service attribute information and the address information of the access IAB node and the BH RLC channel identifier. Among them, the BH RLC channel identifier of the previous hop backhaul link corresponds to the BH RLC channel identifier of the next hop backhaul link, the service bearer identifier corresponds to the BH RLC channel identifier, the service attribute information corresponds to the BH RLC channel identifier, and the service attribute information and the address information of the access IAB node correspond to the BH RLC channel identifier.

[0099] Specifically, if the IAB node1 DU receives the BH RLC channel identifier of the downlink data carried on the Un1 interface from the IAB node1 MT through the internal interface, the IAB node1 DU may determine the second BH RLC channel identifier corresponding to the BH RLC channel identifier of the downlink data on the Un1 interface according to the correspondence between the BH RLC channel identifier on the Un1 interface and the BH RLC channel identifier on the Un2 interface obtained from the IAB donor CU;

[0100] Alternatively, if the IAB node1 DU receives the UE bearer ID of the downlink data from the IAB node1 MT through the internal interface, the IAB node1 DU may determine the second BH RLC channel identifier corresponding to the UE bearer ID of the downlink data according to the correspondence between the UE bearer ID obtained from the IAB donor CU and the BHRLC channel identifier on the Un2 interface.

[0101] In practical applications, the IAB node1 DU can carry the UE bearer ID of the downlink data in the adaptation layer and send it to the IAB node2 MT.

[0102] Furthermore, if the IAB node1 DU receives the service attribute information of the downlink data, i.e., the DSCP / flow label or the service attribute information and the IP address of the accessed IAB node, i.e., the DSCP / flowlabel+the address information of the accessed IAB node, from the IAB node1 MT through the internal interface, the IAB node1 DU can determine the second BH RLC channel identifier corresponding to the service attribute information of the downlink data according to the correspondence between the DSCP / flow label or the DSCP / flow label+the address information of the accessed IAB node obtained from the IAB donor CU and the BH RLC channel identifier on the Un2 interface.

[0103] In actual applications, the IAB node1 DU can carry the DSCP / flow label of the downlink data or the DSCP / flow label+address information of the access IAB node in the adaptation layer and send it to the IAB node2 MT.

[0104] S309: The IAB node1 DU maps the downlink data to the BH RLC channel corresponding to the second BH RLC channel identifier and sends it to the IAB node2 MT (ie, the next hop IAB node).

[0105] S310: The IAB node2 MT sends the downlink data to the IAB node2 DU through the internal interface, and at the same time, sends at least one information of the downlink data to the IAB node2 DU through the internal interface.

[0106] Here, the implementation process of S310 is similar to the implementation process of S307 described above, and will not be described in detail here.

[0107] S311: The IAB node2 DU determines the first DRB ID / first LCID on the Uu interface corresponding to at least one information of the downlink data according to the correspondence between the BH RLC channel identifier on the Un2 interface sent by the IAB donor CU and the DRB ID / LCID on the Uu interface, or the correspondence between the service bearer identifier (UE Bearer ID) sent by the IAB donor CU and the DRB ID / LCID on the Uu interface, or the correspondence between the DSCP / flow label determined by the IAB donor CU and the DRB ID / LCID on the Uu interface, or the correspondence between the DSCP / flow label+address information of the access IAB node and the DRB ID / LCID on the Uu interface determined by the IAB donor CU;

[0108] Specifically, if the IAB node2 DU receives the BH RLC channel identifier of the downlink data carried on the Un2 interface from the IAB node2 MT through the internal interface, the IAB node2 DU can determine the first DRB ID / first LCID corresponding to the BH RLC channel identifier of the downlink data carried on the Un2 interface according to the correspondence between the BH RLC channel identifier on the Un2 interface obtained from the IAB donor CU and the DRB ID / LCID on the Uu interface.

[0109] Alternatively, if the IAB node2 DU receives the UE bearer ID of the downlink data from the IAB node2 MT through the internal interface, the IAB node2 DU can determine the first DRB ID / first LCID corresponding to the UE bearer ID of the downlink data based on the correspondence between the UE bearer ID obtained from the IAB donor CU and the DRBID / LCID on the Uu interface.

[0110] Furthermore, if the IAB node2 DU receives the DSCP / flow label or the DSCP / flow label+address information of the access IAB node of the downlink data from the IAB node2 MT through the internal interface, the IAB node2 DU can determine the first DRB ID / first LCID corresponding to the service attribute information of the downlink data based on the correspondence between the DSCP / flow label or the DSCP / flow label+address information of the access IAB node obtained from the IAB donor CU and the DRB ID / LCID on the Uu interface.

[0111] S312: The IAB node1 DU maps the downlink data to the DRB corresponding to the first DRB ID or the logical channel corresponding to the first LCID and sends it to the UE.

[0112] Figure 4 In the embodiment of this application Figure 2A Schematic diagram of the uplink data transmission method under the architecture 2, see Figure 4 As shown by the solid line, similar to the above-mentioned downlink data transmission method, the uplink data transmission method may include:

[0113] S401: The UE maps the uplink data to the DRB / logical channel corresponding to the Uu interface and sends it to the IAB node2 DU (ie, the next-hop IAB node).

[0114] In the embodiment of the present application, similar to the above-mentioned downlink data transmission method, in order for the IAB donor CU to determine the bearer mapping on each interface during user data transmission, the IAB donor DU and each IAB node DU need to send the logical channel identifier (LCID, Logic Channel ID entification) corresponding to the BH RLC channel to the IAB donor CU. At this time, the BH RLC channel identifier can be the identifier of the logical channel corresponding to the BH RLC channel. Then, refer to Figure 4 As shown by the middle dotted line, the above method may further include: S402: the IAB donor DU sends a BH RLC channel identifier to the IAB donor CU, and the IAB node1DU sends a BH RLC channel identifier to the IAB donor CU.

[0115] Then, the IAB donor CU can determine the correspondence between the service attribute information and the BH RLC channel identifier according to the BH RLC channel identifier sent by the IAB donor DU and the IAB node1 DU. For example, the IAB donor CU determines the DSCP / FlowLabel and the corresponding BH RLC channel identifier on the Un1 interface, or the IAB donor CU determines the DSCP / Flow Label+the address information of the access IAB node and the corresponding BH RLC channel identifier on the Un1 interface. Then, the IAB donor CU sends the above-determined DSCP / Flow Label and the corresponding BH RLC channel identifier on the Un1 interface or the determined DSCP / Flow Label+the address information of the access IAB node and the corresponding BH RLC channel identifier on the Un1 interface to the IAB donor DU through the F1AP message between the IAB donor CU and the IABdonor DU.

[0116] In addition, the IAB donor CU can determine the correspondence between the BH RLC channel identifier of the previous hop backhaul link (on the Un1 interface) and the BH RLC channel identifier of the next hop backhaul link (on the Un2 interface), or the correspondence between the service bearer identifier and the BH RLC channel identifier, or the correspondence between the service attribute information and the BHRLC channel identifier, or the correspondence between the service attribute information and the address information of the access IAB node and the BH RLC channel identifier, based on the BH RLC channel identifier sent by the IAB node1 DU. Then, the IAB donor CU sends the determined BH RLC channel identifier on the Un1 interface and the BH RLC channel identifier on the Un2 interface, or the determined UE Bearer ID and the BH RLC channel identifier, or the determined DSCP / flowlabel and the BH RLC channel identifier, or the determined DSCP / flow label+the address information of the access IAB node and the BHRLC channel identifier to the IAB node1 MT through the Radio Resource Control (RRC) message between the IAB donor CU and the IAB node1 MT.

[0117] In some possible implementations, the IAB node2 DU may also feed back the LCID of the logical channel allocated to the UE DRB on the Uu interface to the IAB donor CU. Figure 4As shown by the dotted line in the middle, the above method may further include: S403: IAB node2DU sends the LCID of the Uu interface to the IAB donor CU. The IAB donor CU may determine the correspondence between the BH RLC channel identifier on the Un2 interface and the DRB ID / LCID on the Uu interface according to the LCID of the Uu interface sent by the IAB node2DU, or the IAB donor CU determines the correspondence between the UE Bearer ID and the BH RLC channel identifier on the Un2 interface, or the IAB donor CU determines the correspondence between the DSCP / flow label and the BH RLC channel identifier on the Un2 interface, or the IABdonor CU determines the correspondence between the DSCP / flow label+address information of the access IAB node and the BH RLC channel identifier on the Un2 interface. Then, the IAB donor CU sends the determined BH RLC channel identifier on the Un2 interface and the corresponding DRB ID / LCID on the Uu interface, the determined UE Bearer ID and the BH RLC channel identifier on the Un2 interface, the determined DSCP / flowlabel and the BH RLC channel identifier on the Un2 interface and / or the determined DSCP / flow label+address information of the access IAB node and the BH RLC channel identifier on the Un2 interface to the IAB node2 MT through the RRC message between the IAB donor CU and the IAB node2 MT.

[0118] In the embodiment of the present application, the IAB node1 MT can also obtain from the IAB node1 DU the correspondence between the BH RLC channel identifier on the Un1 interface determined by the above-mentioned IAB donor CU and the BH RLC channel identifier on the Un2 interface, or the correspondence between the determined UE Bearer ID and the BH RLC channel identifier, or the correspondence between the determined DSCP / flow label and the BHRLC channel identifier, or the correspondence between the determined DSCP / flow label+the address information of the access IAB node and the BHRLC channel identifier; similarly, the IAB node2 MT can also obtain from the IAB node2 DU the correspondence between the BH RLC channel identifier on the Un2 interface determined by the above-mentioned IABdonor CU and the DRB ID / LCID on the Uu interface, or the correspondence between the determined UE Bearer ID and the BH RLC channel identifier on the Un2 interface, or the correspondence between the determined DSCP / flowlabel and the BH RLC channel identifier on the Un2 interface, or the correspondence between the determined DSCP / flow label+the address information of the access IAB node and the BH RLC channel identifier on the Un2 interface.

[0119] Next, see Figure 4 As shown by the solid line, after S401, S404 is executed;

[0120] S404: The IAB node2 DU sends the uplink data to the IAB node2 MT through the internal interface, and at the same time, sends at least one information of the uplink data to the IAB node2 MT through the internal interface.

[0121] Among them, similar to the execution process of the above-mentioned S307, at least one information of the above-mentioned uplink data may include: BHRLC channel identifier, UE Bearer ID or service attribute information or service attribute information and address information of accessing the IAB node, that is, the IAB node2 DU sends the DRB ID / LCID carried by the uplink data on the Uu interface to the IAB node2 MT through the internal interface, or sends the UE bearer ID of the uplink data to the IAB node2 MT through the internal interface, or sends the service attribute information DSCP / flow label of the uplink data or DSCP / flow label+address information of the access IAB node to the IAB node2 MT through the internal interface.

[0122] In an embodiment of the present application, in S403, the IAB node2 DU receives uplink data from the DRB / logical channel corresponding to the Uu interface, and obtains the UE bearer ID or DSCP / flow label or DSCP / flow label+address information of the access IAB node corresponding to the uplink data based on the correspondence between the UE bearer ID obtained from the IAB donor CU and the DRB ID / LCID on the Uu interface, or the correspondence between the DSCP / flow label or the DSCP / flow label+address information of the access IAB node and the DRB ID / LCID on the Uu interface.

[0123] S405: The IAB node2 MT determines a fourth BH RLC channel identifier corresponding to at least one information of the uplink data according to the correspondence between the BH RLC channel identifier on the Un2 interface and the DRB ID / LCID on the Uu interface sent by the IAB donor CU or the IAB node2 DU, or the correspondence between the UE Bearer ID and the BH RLC channel identifier on the Un2 interface, or the correspondence between the DSCP / flow label and the BH RLC channel identifier on the Un2 interface, or the correspondence between the DSCP / flow label+address information of the access IAB node and the BH RLC channel identifier on the Un2 interface.

[0124] Specifically, if the IAB node2 MT receives the DRB / LCID of the uplink data carried on the Uu interface from the IAB node2 DU through the internal interface, the IAB node2 MT may determine the fourth BH RLC channel identifier corresponding to the DRB / LCID of the uplink data carried on the Uu interface according to the correspondence between the BH RLC channel identifier on the Un2 interface obtained from the IAB donor CU or the IAB node2 DU and the DRB ID / LCID on the Uu interface;

[0125] Alternatively, if the IAB node2 MT receives the UE bearer ID of the uplink data from the IAB node2 DU through the internal interface, the IAB node2 MT may determine the fourth BH RLC channel identifier corresponding to the UE bearer ID of the uplink data according to the correspondence between the UE bearer ID obtained from the IAB donor CU or the IAB node2 DU and the BH RLC channel on the Un2 interface.

[0126] In practical applications, the IAB node2 MT can carry the UE bearer ID of the uplink data in the adaptation layer and send it to the IAB node1 DU.

[0127] Furthermore, if the IAB node2 MT receives the DSCP / flow label or DSCP / flow label+address information of the uplink data of the UE from the IAB node2 DU through the internal interface, the IAB node2 MT can determine the fourth BH RLC channel identifier corresponding to the DSCP / flow label or DSCP / flow label+address information of the access IAB node of the uplink data based on the correspondence between the DSCP / flow label or DSCP / flow label+address information of the access IAB node obtained from the IAB donor CU or the IAB node2 DU and the BH RLC channel identifier on the Un2 interface.

[0128] At the same time, the IAB node2 MT can carry the DSCP / flow label of the uplink data or the DSCP / flow label+address information of the access IAB node in the adaptation layer and send it to the IAB node1 DU.

[0129] S406: The IAB node2 MT maps the uplink data to the BH RLC channel on the Un2 interface corresponding to the fourth BH RLC channel identifier and sends it to the IAB node1 DU (ie, the next hop IAB node).

[0130] S407: The IAB node1 DU sends the uplink data to the IAB node1 MT through the internal interface, and at the same time, sends at least one information of the downlink data to the IAB node1 MT through the internal interface.

[0131] Here, the implementation process of S406 is similar to the implementation process of S403 described above, and will not be repeated here.

[0132] S408: the IAB node1 MT determines a fifth BH RLC channel identifier corresponding to at least one information of the uplink data according to the correspondence between the BH RLC channel identifier of the previous hop backhaul link (on the Un1 interface) and the BH RLC channel identifier of the next hop backhaul link (on the Un2 interface) sent by the IAB donor CU or the IAB node1 DU, or the correspondence between the UE bearer ID and the BH RLC channel identifier, or the correspondence between the service attribute information and the BH RLC channel identifier, or the correspondence between the service attribute information and the address information of the access IAB node and the BH RLC channel identifier;

[0133] Specifically, if the IAB node1 MT receives the BH RLC channel identifier of the uplink data carried on the Un2 interface from the IAB node1 DU through the internal interface, the IAB node1 MT can determine the fifth BH RLC channel identifier corresponding to the BH RLC channel identifier of the uplink data carried on the Un2 interface according to the correspondence between the BH RLC channel identifier on the Un1 interface obtained from the IAB donor CU or the IAB node1 DU and the BH RLC channel identifier on the Un2 interface.

[0134] Alternatively, if the IAB node1 MT receives the UE bearer ID of the uplink data from the IAB node1 DU through the internal interface, the IAB node1 MT may determine the fifth BHRLC channel identifier corresponding to the UE bearer ID of the uplink data according to the correspondence between the UE bearer ID obtained from the IAB donor CU or the IAB node1 DU and the BH RLC channel identifier on the Un1 interface.

[0135] In practical applications, the IAB node1 MT can send the UE bearer ID of the uplink data to the IAB donor DU in the adaptation layer.

[0136] Furthermore, if the IAB node1 MT receives the DSCP / flow label or the DSCP / flow label+address information of the access IAB node of the uplink data from the IAB node1 DU through the internal interface, the IAB node1 MT can determine the fifth BH RLC channel identifier corresponding to the DSCP / flow label or the DSCP / flow label+address information of the access IAB node of the uplink data according to the correspondence between the DSCP / flow label or the DSCP / flow label+address information of the access IAB node obtained from the IAB donor CU or the IAB node1 DU and the BH RLC channel identifier on the Un1 interface.

[0137] In actual applications, the IAB node1 MT can carry the DSCP / flow label of the downlink data or the DSCP / flow label + the address information of the access IAB node in the adaptation layer and send it to the IAB donor DU.

[0138] S409: The IAB node1 MT maps the uplink data to the BH RLC channel on the Un1 interface corresponding to the fifth BH RLC channel identifier and sends it to the IAB donor DU (ie, the next-hop IAB node).

[0139] In the embodiment of the present application, for the data transmission of the above uplink data, in addition to the above Figure 4 In addition to the method described in the embodiment, each IAB node MT can also determine the bearer mapping when uplink data is sent according to the bearer mapping when downlink data is sent. Then, IAB node1 MT or IAB node2 MT can map the uplink data to the BH RLC channel for receiving downlink data and send it. At this time, the uplink data and the downlink data have the same service QoS information. Here, the IAB nodeMT obtains the bearer mapping relationship when downlink data is sent from the IAB node DU corresponding to itself, and determines the bearer mapping relationship when uplink data is sent.

[0140] The above-mentioned service QoS information is the service attribute corresponding to the UE, which may be composed of a service bearer identifier (UE bearer ID) and QoS configuration information. The QoS configuration information may include at least one of the following QoS parameters: 5G QoS identifier (5QI, 5G QoSIdentifier), allocation and retention priority (ARP, Allocation and Retention Priority), priority bit rate (PBR, Prioritised Bit Rate), packet delay budget (PDB, Packet Delay Budget), guaranteed flow bit rate (GFBR, Guaranteed Flow Bit Rate), maximum flow bit rate (MFBR, Maximum Flow Bit Rate), etc.

[0141] So far, the IAB system has Figure 2A The first type of data transmission is completed under the architecture shown.

[0142] Embodiment 2:

[0143] The present application provides a data transmission method, which is applied to the above Figure 2A The IAB system shown.

[0144] It should be noted that in the second embodiment, the bearer mapping on each interface during user data transmission is determined by each node itself.

[0145] Figure 5 In the embodiment of this application Figure 2A Flow chart 2 of the downlink data transmission method under the architecture of Figure 5 As shown by the solid line, the downlink data transmission method may include:

[0146] S501: The IAB donor CU receives downlink data from the UE;

[0147] S502: The IAB donor CU carries the service attribute information of the downlink data in the IP layer header field and sends it to the IAB donor DU together with the downlink data;

[0148] S503: The IAB donor DU extracts the service attribute information (such as DSCP / flow label) of the downlink data from the IP layer header field, and determines the first service QoS information corresponding to the service attribute information of the downlink data according to the service attribute information and the corresponding service QoS information sent by the IAB donor CU;

[0149] Optionally, the IAB donor DU further extracts the target address information of the downlink data from the IP layer header field. Exemplarily, the target address information may be the address information of the access IAB node, such as the IP address of IAB node2. The IABdonor DU determines the service attribute information of the downlink data and the first service QoS information corresponding to the IP address of IAB node2 according to the service attribute information sent by the IAB donor CU, the IP address of IAB node2 and the corresponding service QoS information.

[0150] In the embodiment of the present application, in order to enable the IAB donor DU to determine the bearer mapping in Un1 during user data transmission, the IAB donor CU may also send service attribute information and service QoS information, and the service attribute information corresponds to the service QoS information. Alternatively, the IAB donor CU may also send service attribute information + the IP address of the IAB node2 and the service QoS information, and the service attribute information + the IP address of the IAB node2 corresponds to the service QoS information. Then, the IAB donor DU may determine the first service QoS information corresponding to the service attribute information of the downlink data based on the service attribute information and the corresponding service QoS information sent by the IAB donor CU, or the IAB donor DU may determine the first service QoS information corresponding to the service attribute information of the downlink data + the IP address of the IAB node2 based on the service attribute information + the IP address of the IAB node2 and the corresponding service QoS information sent by the IAB donor CU.

[0151] S504: The IAB donor DU maps the downlink data to the BH RLC channel corresponding to the first service QoS information and sends it to the IAB node1 MT (i.e., the next hop IAB node);

[0152] In some possible implementations, the IAB donor DU may carry the service bearer identifier or service attribute information or service attribute information + IP address of IAB node2 corresponding to the above-mentioned downlink data in the adaptation layer and send it to the IAB node1MT. The IAB donor DU may obtain the corresponding relationship between the service attribute information (such as DSCP / flow label) and UEbearer ID from the IAB donor CU, so that the IAB donor DU can obtain the corresponding UE bearer ID according to the DSCP / flow label extracted from the IP layer, and then carry the UE bearer ID in the adaptation layer and send it to the IAB node1 MT. Alternatively, the IAB donor DU may obtain the corresponding relationship between the service attribute information (such as DSCP / flow label) + IP address of IABnode2 and UE bearer ID from the IAB donor CU, so that the IAB donor DU can obtain the corresponding UE bearer ID according to the DSCP / flow label extracted from the IP layer + IP address of IAB node2, and then carry the UE bearer ID in the adaptation layer and send it to the IAB node1 MT.

[0153] In some possible implementations, the IAB donor DU carries the DSCP / flow label or the DSCP / flow label+address information of the access IAB node corresponding to the downlink data in the adaptation layer and sends it to the IAB node1 MT.

[0154] S505: The IAB node1 MT sends the downlink data to the IAB node1 DU through the internal interface, and at the same time, sends at least one information of the downlink data to the IAB node1 DU through the internal interface.

[0155] At least one information of the above-mentioned downlink data may include: BH RLC channel identifier, service bearer identifier or service attribute information or service attribute information + address information of access IAB node, that is, IAB node1 MT sends the BH RLC channel identifier (such as LCID) carried on Un1 interface to IAB node1 DU through the internal interface, or sends the UE bearer ID corresponding to the downlink data to IAB node1 DU through the internal interface. Alternatively, the DSCP / flow label corresponding to the downlink data or the DSCP / flow label + address information of access IAB node is sent to IAB node1DU through the internal interface.

[0156] S506: The IAB node1 DU determines second service QoS information corresponding to at least one information of downlink data according to the UE bearer ID and service quality of service QoS information, or the service attribute information and the service QoS information, or the service attribute information + the address information of the access IAB node and the service QoS information, or the BH RLC channel identifier and the service QoS information sent by the IAB donor CU; wherein the service bearer identifier corresponds to the service QoS information, the service attribute information corresponds to the service QoS information, the service attribute information + the address information of the access IAB node corresponds to the service QoS information, and the BH RLC channel identifier corresponds to the service QoS information;

[0157] Specifically, if the IAB node1 DU receives the BH RLC channel identifier of the downlink data carried on the Un1 interface from the IAB node1 MT through the internal interface, the IAB node1 DU may determine the second service QoS information corresponding to the BH RLC channel identifier carried on the Un1 interface of the downlink data according to the correspondence between the BH RLC channel identifier on the Un1 interface obtained from the IAB donor CU and the service QoS information;

[0158] Alternatively, if the IAB node1 DU receives the UE bearer ID of the downlink data from the IAB node1 MT through the internal interface, the IAB node1 DU may determine the second service QoS information corresponding to the UE bearer ID of the downlink data according to the correspondence between the UE bearer ID and the service QoS information obtained from the IAB donor CU.

[0159] In practical applications, the IAB node1 DU can carry the UE bearer ID of the downlink data in the adaptation layer and send it to the IAB node2 MT.

[0160] Furthermore, if the IAB node1 DU receives the DSCP / flow label or the DSCP / flow label+address information of the access IAB node of the downlink data from the IAB node1 MT through the internal interface, the IAB node1 DU can determine the second service QoS information corresponding to the service attribute information of the downlink data according to the correspondence between the DSCP / flow label or the DSCP / flow label+address information of the access IAB node obtained from the IAB donor CU and the service QoS information.

[0161] In actual applications, the IAB node1 DU can carry the DSCP / flow label of the downlink data or the DSCP / flow label+address information of the access IAB node in the adaptation layer and send it to the IAB node2 MT.

[0162] S507: The IAB node1 DU maps the downlink data to the BH RLC channel corresponding to the second service QoS information and sends it to the IAB node2 MT (ie, the next hop IAB node).

[0163] S508: The IAB node2 MT sends the downlink data to the IAB node2 DU through the internal interface, and at the same time, sends at least one information of the downlink data to the IAB node2 DU through the internal interface.

[0164] Here, the implementation process of S308 is similar to the implementation process of S505 described above, and will not be repeated here.

[0165] S509: the IAB node2 DU determines the first DRB ID / first LCID on the Uu interface corresponding to at least one information of the downlink data according to the correspondence between the BH RLC channel identifier on the Un2 interface sent by the IAB donor CU and the DRB ID / LCID on the Uu interface, or the correspondence between the UE Bearer ID and the DRB ID / LCID on the Uu interface, or the correspondence between the DSCP / flow label and the DRB ID / LCID on the Uu interface, or the correspondence between the DSCP / flow label+the address information of the access IAB node and the DRB ID / LCID on the Uu interface;

[0166] S510: The IAB node1 DU maps the downlink data to the DRB corresponding to the first DRB ID or the logical channel corresponding to the first LCID and sends it to the UE.

[0167] Here, the implementation process of S509 and S510 is similar to the implementation process of S311 and S312 in the above-mentioned embodiment 1, and will not be described in detail here.

[0168] Figure 6 In the embodiment of this application Figure 2A Schematic diagram of the process of uplink data transmission method under architecture Figure 1 , see Figure 4 As shown by the solid line, similar to the above-mentioned downlink data transmission method, the uplink data transmission method may include:

[0169] S601: The UE maps the uplink data to the DRB / logical channel corresponding to the Uu interface and sends it to the IAB node2 DU (ie, the next-hop IAB node).

[0170] S602: The IAB node2 DU sends the uplink data to the IAB node2 MT through the internal interface, and at the same time, sends at least one information of the uplink data to the IAB node2 MT through the internal interface.

[0171] Here, the implementation process of S601 and S602 is similar to the implementation process of S401 and S402 in the above-mentioned embodiment 1, and will not be described in detail here.

[0172] S603: The IAB node2 MT determines fourth service QoS information corresponding to at least one information of uplink data according to the UE bearer ID and service quality of service QoS information, or the service attribute information and service QoS information, or the service attribute information + address information of the access IAB node and service QoS information, or the BH RLC channel identifier and service QoS information sent by the IAB donor CU;

[0173] Specifically, if the IAB node2 MT receives the UE bearer ID of the uplink data from the IAB node2 DU through the internal interface, the IAB node2 MT can determine the third service QoS information corresponding to the UE bearer ID of the uplink data according to the correspondence between the UE bearer ID and the service QoS information obtained from the IAB donor CU or the IAB node2 DU.

[0174] In practical applications, the IAB node2 MT can carry the UE bearer ID of the uplink data in the adaptation layer and send it to the IAB node1 DU.

[0175] Furthermore, if the IAB node2 MT receives the DSCP / flow label or the DSCP / flow label+the address information of the uplink data of the UE from the IAB node2 DU through the internal interface, the IAB node2 MT can determine the third service QoS information corresponding to the DSCP / flow label or the DSCP / flow label+the address information of the access IAB node of the uplink data based on the correspondence between the DSCP / flow label or the DSCP / flow label+the address information of the access IAB node obtained from the IAB donor CU or the IAB node2 DU and the service QoS information.

[0176] At the same time, the IAB node2 MT can carry the DSCP / flow label of the uplink data or the DSCP / flow label+address information of the access IAB node) in the adaptation layer and send it to the IAB node1 DU.

[0177] S604: The IAB node2 MT maps the uplink data to the BH RLC channel on the Un2 interface corresponding to the uplink data third service QoS information and sends it to the IAB node1 DU (ie, the next hop IAB node).

[0178] S605: The IAB node1 DU sends the uplink data to the IAB node1 MT through the internal interface, and at the same time, sends at least one information of the downlink data to the IAB node1 MT through the internal interface.

[0179] Here, the implementation process of S605 is similar to the implementation process of S602 described above, and will not be repeated here.

[0180] S606: The IAB node1 MT determines fifth service QoS information corresponding to at least one information of the uplink data according to the correspondence between the UE bearer ID and the service quality of service QoS information, or the correspondence between the service attribute information and the service QoS information, or the correspondence between the service attribute information + the address information of the access IAB node and the service QoS information, or the correspondence between the BH RLC channel identifier and the service QoS information, sent by the IAB donor CU or the IAB node1 DU;

[0181] Specifically, if the IAB node1 MT receives the BH RLC channel identifier of the uplink data carried on the Un1 interface from the IAB node1 DU through the internal interface, the IAB node1 MT may determine the fifth service QoS information corresponding to the BH RLC channel identifier of the uplink data carried on the Un1 interface according to the correspondence between the BH RLC channel identifier on the Un1 interface obtained from the IAB donor CU or the IAB node1 DU and the service QoS information;

[0182] Alternatively, if IAB node1 MT receives the UE bearer ID of uplink data from IAB node1 DU through the internal interface, IAB node1 MT may determine the fifth service QoS information corresponding to the UE bearer ID of uplink data according to the correspondence between the UE bearer ID and service QoS information obtained from the IAB donor CU or IAB node1 DU.

[0183] In practical applications, the IAB node1 MT can send the UE bearer ID of the uplink data to the IAB donor DU in the adaptation layer.

[0184] Furthermore, if the IAB node1 MT receives the DSCP / flow label or the DSCP / flow label+the address information of the uplink data of the UE from the IAB node1 DU through the internal interface, the IAB node1 MT can determine the fifth service QoS information corresponding to the DSCP / flow label or the DSCP / flow label+the address information of the access IAB node of the uplink data based on the correspondence between the DSCP / flow label or the DSCP / flow label+the address information of the access IAB node obtained from the IAB donor CU or the IAB node1 DU and the service QoS information.

[0185] In actual applications, the IAB node1 MT can carry the DSCP / flow label of the downlink data or the DSCP / flow label + the address information of the access IAB node) in the adaptation layer and send it to the IAB donor DU.

[0186] S607: The IAB node1 MT maps the uplink data to the BHRLC channel on the Un1 interface corresponding to the fifth service QoS information and sends it to the IAB donor DU (ie, the next-hop IAB node).

[0187] In the embodiment of the present application, for the data transmission of the above uplink data, in addition to the above Figure 6 In addition to the method described in the embodiment, each IAB node MT can also determine the bearer mapping when uplink data is sent according to the bearer mapping when downlink data is sent. Then, IAB node1 MT or IAB node2 MT can map the uplink data to the BH RLC channel for receiving downlink data and send it. At this time, the uplink data and the downlink data have the same service QoS information. Here, the IAB nodeMT obtains the bearer mapping relationship when downlink data is sent from the IAB node DU corresponding to itself, and determines the bearer mapping relationship when uplink data is sent.

[0188] So far, the IAB system has Figure 2A The second data transmission process is completed under the architecture shown.

[0189] Embodiment three:

[0190] Based on the above-mentioned embodiments 1 and 2, the present application embodiment provides a data transmission method, which is applied to the above-mentioned Figure 2B The IAB system shown.

[0191] It should be noted that in this third embodiment, the GTP tunnel established between the IAB donor CU and the IAB donor DU is per UE per bearer. This GTP is mapped one-to-one with the GTP established between the IAB donor DU and the IAB node2 DU.

[0192] Fig. 7A In the embodiment of this application Figure 2B Schematic diagram of the process of downlink data transmission method under the architecture Figure 1 , see Fig. 7A As shown by the solid line, the downlink data transmission method may include:

[0193] S701: IAB donor CU receives downlink data from UE;

[0194] S702: The IAB donor CU maps the downlink data to the corresponding GTP tunnel and sends it to the IAB donor DU;

[0195] S703: The IAB donor DU determines the sixth BH RLC channel identifier corresponding to the GTP tunnel identifier corresponding to the downlink data according to the correspondence between the GTP tunnel identifier and the BH RLC channel identifier sent by the IAB donor CU;

[0196] Here, the above-mentioned GTP tunnel identifier can be a tunnel endpoint identifier (TEID, Tunnel Endpoint ID) of the GTP tunnel.

[0197] Exemplarily, the GTP tunnel identifier TEID corresponding to the downlink data may be a TEID allocated by the IAB donor DU or a TEID allocated by the IAB donor CU.

[0198] S704: The IAB donor DU maps the downlink data to the BH RLC channel corresponding to the sixth BH RLC channel identifier and sends it to the IAB node1 MT (i.e., the next hop IAB node);

[0199] At the same time, the IAB donor DU carries the GTP tunnel identifier corresponding to the downlink data in the adaptation layer and sends it to the IABnode1 MT.

[0200] S705: The IAB node1 MT sends the downlink data to the IAB node1 DU through the internal interface, and at the same time, sends the GTP tunnel identifier corresponding to the downlink data to the IAB node1 DU through the internal interface.

[0201] S706: The IAB node1 DU determines the seventh BH RLC channel identifier corresponding to the GTP tunnel identifier corresponding to the downlink data according to the correspondence between the GTP tunnel identifier and the BH RLC channel identifier sent by the IAB donor CU.

[0202] S707: The IAB node1 DU maps the downlink data to the BH RLC channel corresponding to the seventh BH RLC channel identifier and sends it to the IAB node2 MT (ie, the next hop IAB node).

[0203] S708: The IAB node2 MT sends the downlink data to the IAB node2 DU through the internal interface, and at the same time, sends the GTP tunnel identifier corresponding to the downlink data to the IAB node2 DU through the internal interface.

[0204] S709: The IAB node2 DU determines the third DRB ID / third LCID on the Uu interface corresponding to the downlink data according to the correspondence between the BH RLC channel identifier on the Un2 interface sent by the IAB donor CU and the DRB ID / LCID on the Uu interface;

[0205] S710: The IAB node1 DU maps the downlink data to the DRB corresponding to the third DRB ID or the logical channel corresponding to the third LCID and sends it to the UE.

[0206] In this embodiment, illustratively, the BH RLC channel identifier may be an identifier LCID of a logical channel corresponding to the BH RLC channel.

[0207] In some possible implementations, Figure 7B In the embodiment of this application Figure 2B Flow chart 2 of the downlink data transmission method under the architecture of Figure 7B As shown, after S701, the method may further include: S711: the IAB donor DU receives downlink data from the GTP tunnel, and determines, according to the GTP tunnel identifier (such as TEID), sixth service QoS information corresponding to the downlink data transmitted on the GTP tunnel;

[0208] Then, S704 may be replaced by S712: the IAB donor DU maps the downlink data to the sixth service QoS information and sends it to the IAB node1 MT (ie, the next hop IAB node) in the corresponding BH RLC channel on the Un1 interface;

[0209] At the same time, the IAB donor DU carries the GTP tunnel identifier corresponding to the downlink data in the adaptation layer and sends it to the IABnode1 MT. The IAB node1 MT sends the downlink data to the IAB node1 DU through the internal interface, and at the same time, sends the GTP tunnel identifier corresponding to the downlink data to the IAB node1 DU through the internal interface.

[0210] Accordingly, S707 may be replaced by S713: the IAB node1 DU maps the downlink data to the sixth service QoS information and sends it to the IAB node2 MT (ie, the next hop IAB node) in the BH RLC channel corresponding to the Un2 interface.

[0211] Before the IAB node1 DU maps the downlink data to the sixth service QoS information and sends it to the IAB node2 MT in the corresponding BH RLC channel on the Un2 interface, the IAB node1 DU also needs to receive the correspondence between the GTP tunnel identifier and the sixth service QoS information sent by the IAB donor CU.

[0212] In the embodiment of the present application, Figure 2B Under the architecture, the bearer mapping scheme for uplink data transmission is the same as that for downlink. The bearer mapping is performed by IAB node2MT and IAB node1 MT. The mapping for uplink data transmission can be performed based on the mapping relationship for downlink data transmission, or based on the GTP tunnel identifier and the corresponding BH RLC channel identifier configured by the IAB donor CU, or based on the QoS information corresponding to the TEID carried in the adaptation layer.

[0213] In the embodiment of the present application, before S701, the IAB donor CU needs to instruct the IAB donor DU to enable the F1AP proxy function. Fig. 7A or Figure 7B As shown by the middle dotted line, the above data transmission method may further include:

[0214] S714: Instruction information sent by the IAB donor CU to the IAB donor DU, where the instruction information is used to instruct the IAB donor DU to enable the F1 application protocol (F1AP) proxy function;

[0215] S715: The IAB donor DU responds to the indication information and allocates the corresponding UL F1 TNL information for the service bearer;

[0216] S716: The IAB donor DU sends the UL F1 TNL information to the IAB donor CU;

[0217] S717: The IAB donor CU sends the UL F1-U TNL information to the IAB node2 DU.

[0218] Specifically, the IAB donor CU sends indication information to the IAB donor DU. According to the indication information, the IAB donor DU allocates the corresponding UL F1-U TNL information for the service bearer, and sends the UL F1-U TNL information to the IAB node2 DU through the IABdonor CU, so as to establish the UL GTP-U between the IAB node2 DU and the IAB donor DU. For example, the IAB donor DU sends the UL F1-U TNL information allocated by the IAB donor DU to the IAB donor CU through the F1AP UE Context Setup Response message. The IAB donor CU then sends the UL F1-U TNL information allocated by the IAB donor DU to the IAB node2 DU through the F1AP UE Context SetupRequest message. The UL F1-UTNL information includes the GTP-TEID and the TNL address (for example, the IP address of the IAB node2 DU).

[0219] In addition, the above data transmission method may further include: S718: IAB node2 DU allocates DL F1TNL information for the service bearer;

[0220] S719: IAB node2 DU sends DL F1 TNL information to IAB donor CU;

[0221] S720: The IAB donor CU sends the DL F1 TNL information to the IAB donor DU.

[0222] Specifically, IAB node2 DU allocates the corresponding DL F1-U TNL information for UE bearer, and sends the DL F1-U TNL information to IAB donor DU through IAB donor CU, so as to establish DL GTP-U between IAB donor DU and IABnode2 DU. For example, IAB node2 DU sends the DL F1-U TNL information allocated by IAB node2DU to IAB donor CU through F1AP UE Context Setup Response message. IAB donor CU then sends the DL F1-U TNL information allocated by IAB node2 DU to IAB donor DU through F1AP UE Context Modification Request message.

[0223] Embodiment 4:

[0224] Based on the above-mentioned embodiments 1 to 3, the present application embodiment provides a data transmission method, which is applied to the above-mentioned Figure 2B The IAB system shown.

[0225] It should be noted that, in this fourth embodiment, the GTP-U established between the IAB donor CU and the IAB donor DU is per IAB node1 MT per bearer.

[0226] Then, compared with the data transmission method of the above-mentioned embodiment, in the data transmission method described in this embodiment, when mapping downlink data bearers, the IAB donor CU sends downlink data to the IAB donor DU through the GTP tunnel, and carries the UE bearer ID in the GTP tunnel header field, so as to indicate to the IAB donor DU which UE's bearer data is transmitted in the GTP tunnel. The IAB donor DU can perform corresponding bearer mapping according to the correspondence between the UE bearer ID sent by the IAB donor CU and the BH RLC channel identifier on the Un1 interface, or according to the correspondence between the UE bearer ID sent by the IAB donor CU and the QoS information.

[0227] During downlink data bearer mapping, the IAB donor DU receives uplink data from the per UE per bearer GTP tunnel, maps the uplink data to the corresponding GTP tunnel and sends it to the IAB donor CU, and carries the UE bearer ID in the GTP tunnel header field so that the IAB donor CU can extract the uplink data from the GTP tunnel and send it to the corresponding PDCP layer of the UE for processing.

[0228] Embodiment five:

[0229] Based on the above-mentioned embodiments 1 to 3, the present application embodiment provides a data transmission method, which is applied to the above-mentioned Figure 2C and Figure 2B The IAB system shown.

[0230] It should be noted that, in this fifth embodiment, the GTP-U established between the IAB donor CU and the IAB donor DU can be per UE per bearer or per IAB node1 MT per bearer.

[0231] If the GTP-U between the IAB donor CU and the IAB donor DU is per UE per bearer, the bearer mapping method of the IAB system is similar to the bearer mapping method in Example 3; if the GTP tunnel between the IAB donor CU and the IAB donorDU is per IAB node1 MT per bearer, the bearer mapping method of the IAB system is similar to that in Example 4.

[0232] Based on the same inventive concept as the above method, an embodiment of the present application provides a communication device, which may be a data transmission device or a chip or system on chip in a data transmission device, or a functional module in a data transmission device for implementing the method described in any possible implementation method in the above embodiment. The communication device may implement the functions performed by the IAB donor DU in the above embodiment, and the functions may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. For example, Figure 8 The structure of the communication device in the embodiment of the present application is shown in FIG. Figure 1 , see Figure 8As shown, the communication device 800 may include: a first receiving unit 801, used to receive downlink data and service attribute information of the downlink data sent by a centralized unit of an access backhaul integrated IAB host node; a first sending unit 802, used to map the downlink data to a corresponding radio link control BH RLC channel of the backhaul link and send it to the next-hop IAB node according to the service attribute information of the downlink data or according to the service attribute information of the downlink data and the address information of the access IAB node.

[0233] In some possible implementations, the above-mentioned device also includes: the device also includes: a second receiving unit, used to receive service attribute information and a BH RLC channel identifier sent by a centralized unit of the IAB host node, the service attribute information corresponding to the BH RLC channel identifier; the first sending unit includes: a determining subunit and a sending subunit; the determining subunit is used to determine the first BH RLC channel identifier corresponding to the service attribute information of the downlink data according to the service attribute information and the BH RLC channel identifier; the sending subunit is used to map the downlink data to the BH RLC channel corresponding to the first BH RLC channel identifier and send it to the next hop IAB node.

[0234] In some possible implementations, the device also includes: a second sending unit, used to send a BH RLC channel identifier and a logical channel identifier to a centralized unit of the IAB host node, wherein the BH RLC channel identifier corresponds to the logical channel identifier, and the BH RLC channel identifier and the logical channel identifier are used to indicate that the centralized unit of the IAB host node determines the logical channel allocated by the distributed unit of the IAB host node to the BH RLC channel.

[0235] In some possible implementations, the device also includes: a second receiving unit, used to receive service attribute information and service quality QoS information sent by a centralized unit of the IAB host node, the service attributes corresponding to the information and the service QoS information; the first sending unit includes: a determining subunit and a sending subunit; the determining subunit is used to determine the first service QoS information corresponding to the service attribute information of the downlink data according to the service attribute information and the service QoS information; the sending subunit is used to map the downlink data to the BH RLC channel corresponding to the first service QoS information and send it to the next hop IAB node.

[0236] In some possible implementations, the device further includes: a third sending unit, configured to carry the service bearer identifier or service attribute information of the downlink data in the adaptation layer and send it to the next-hop IAB node.

[0237] In some possible implementations, the device also includes: a second receiving unit, used to receive service attribute information and a service bearer identifier sent by a centralized unit of the IAB host node, wherein the service attribute information corresponds to the service bearer identifier; the third sending unit includes: a determination subunit and a sending subunit; the determination subunit is used to determine the first service bearer identifier corresponding to the service attribute information of the downlink data according to the service attribute information and the service bearer identifier; the sending subunit is used to carry the first service bearer identifier in the adaptation layer and send it to the next-hop IAB node.

[0238] In some possible implementations, the IAB node includes: a distributed unit of the IAB node and a mobile terminal unit of the IAB node; the device also includes: a third receiving unit, used to receive the service bearer identifier or service attribute information of the uplink data sent by the mobile terminal unit of the next-hop IAB node, wherein the service bearer identifier or service attribute information of the uplink data is carried in the adaptation layer and sent.

[0239] In some possible implementations, the device further includes: a fourth receiving unit, a first allocation unit, and a fourth sending unit; the fourth receiving unit is used to receive indication information sent by the centralized unit of the IAB host node, and the indication information is used to instruct the distributed unit of the IAB host node to enable the F1 application protocol F1AP proxy function; the first allocation unit is used to respond to the indication information and allocate corresponding uplink F1 transport network layer UL F1 TNL information to the service bearer; the fourth sending unit is used to send the UL F1 TNL information to the centralized unit of the IAB host node.

[0240] In some possible implementations, the device further includes: a fifth receiving unit, configured to receive downlink F1 transport network layer DL F1 TNL information sent by a centralized unit of the IAB host node, where the DL F1 TNL information is allocated by the access IAB node for service bearer.

[0241] In some possible implementations, the service attribute information of the downlink data is one of the following information: the service attribute information of the downlink data is one of the following information: the differentiated service code point DSCP or flow label of the downlink data, wherein the service attribute information of the downlink data is encapsulated in the IP layer header field.

[0242] The first receiving unit to the fifth receiving unit mentioned in the above embodiments can be a receiving interface, a receiving circuit or a receiver, etc.; the sending subunit in the first sending unit and the second sending unit to the fourth sending unit can be a sending interface, a sending circuit or a transmitter, etc.; the determination subunit and the first allocation unit in the first sending unit can be one or more processors.

[0243] Based on the same inventive concept as the above method, an embodiment of the present application provides a communication device, which can be a data transmission device or a chip or system on chip in a data transmission device, or a functional module in a data transmission device for implementing the method described in the above embodiment. The communication device can implement the functions performed by the IAB node in the above embodiment, and the functions can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. For example, Fig. 9 FIG2 is a structural diagram of a communication device in an embodiment of the present application, see Fig. 9 As shown, the communication device 900 may include: a sixth receiving unit 901, used to receive downlink data and at least one of the following information of the downlink data: a radio link control BH RLC channel identifier of a backhaul link, a service bearer identifier, service attribute information or service attribute information and address information of an access IAB node, wherein the service bearer identifier of the downlink data, the service attribute information of the downlink data and the service attribute information of the downlink data and the address information of the access IAB node are received from an adaptation layer; a fifth sending unit 902, used to map the downlink data to a corresponding BH RLC channel for sending according to the at least one information.

[0244] In some possible implementations, the device further includes: a seventh receiving unit, configured to receive a BH RLC channel identifier of a previous hop backhaul link and a BH RLC channel identifier of a next hop backhaul link, a service bearer identifier and a BH RLC channel identifier, and / or service attribute information and a BH RLC channel identifier, sent by a centralized unit of the IAB host node, wherein the BH RLC channel identifier of the previous hop backhaul link corresponds to the BH RLC channel identifier of the next hop backhaul link, the service bearer identifier corresponds to the BH RLC channel identifier, and the service attribute information corresponds to the BH RLC channel identifier; the fifth sending unit includes: a determining subunit and a sending subunit; the determining subunit is configured to determine a second BH RLC channel identifier corresponding to at least one information of the downlink data according to the BH RLC channel identifier of the previous hop backhaul link and the BH RLC channel identifier of the next hop backhaul link, the service bearer identifier and the BH RLC channel identifier, and / or the service attribute information and the BH RLC channel identifier; the sending subunit is configured to map the downlink data to the BH RLC channel identifier corresponding to the second BH RLC channel identifier. The data is sent to the next-hop IAB node on the RLC channel.

[0245] In some possible implementations, the device also includes: a seventh receiving unit, used to receive a service bearer identifier and service quality of service QoS information, service attribute information and service QoS information, and / or a BH RLC channel identifier and service QoS information sent by a centralized unit of the IAB host node, wherein the service bearer identifier corresponds to the service QoS information, the service attribute information corresponds to the service QoS information, and the BH RLC channel identifier corresponds to the service QoS information; the fifth sending unit includes: a determining subunit and a sending subunit; the determining subunit is used to determine the second service QoS information corresponding to at least one information of the downlink data according to the service bearer identifier and the service QoS information, the service attribute information and the service QoS information, and / or the BH RLC channel identifier and the service QoS information; the sending subunit is used to map the downlink data to the BH RLC channel corresponding to the second service QoS information and send it to the next hop IAB node.

[0246] In some possible implementations, the device further includes: a seventh receiving unit, configured to receive a BH RLC channel identifier and a data radio bearer identifier or a logical channel identifier on an air interface, a service bearer identifier and a data radio bearer identifier or a logical channel identifier on an air interface, and / or service attribute information and a data radio bearer identifier or a logical channel identifier on an air interface, sent by a centralized unit of the IAB host node, BH The RLC channel identifier corresponds to the data radio bearer identifier or the logical channel identifier on the air interface, the service bearer identifier corresponds to the data radio bearer identifier or the logical channel identifier on the air interface, and the service bearer identifier corresponds to the data radio bearer identifier or the logical channel identifier on the air interface; the fifth sending unit includes: a determining subunit and a sending subunit; the determining subunit is used to determine the first data radio bearer identifier or the first logical channel identifier on the air interface corresponding to at least one information of the downlink data according to the BHRLC channel identifier and the data radio bearer identifier or the logical channel identifier, the service bearer identifier and the data radio bearer identifier or the logical channel identifier and / or the service attribute information and the data radio bearer identifier or the logical channel identifier; the sending subunit is used to map the downlink data to the radio bearer corresponding to the first data radio bearer identifier or the logical channel corresponding to the first logical channel identifier and send it to the terminal.

[0247] In some possible implementations, the apparatus further includes: a sixth sending unit, configured to send a service bearer identifier or service attribute information of the uplink data to a distributed unit of an IAB node on a next-hop intermediate backhaul link.

[0248] In some possible implementations, the device further includes: a seventh sending unit, configured to map the uplink data to a BH RLC channel for receiving the downlink data and send the uplink data, wherein the uplink data and the downlink data have the same service QoS information.

[0249] In some possible implementations, the device further includes: a second allocation unit and an eighth sending unit; the second allocation unit is used to allocate downlink F1 transport network layer DL F1 TNL information for the service bearer; the eighth sending unit is used to send the DL F1 TNL information to the centralized unit of the IAB host node.

[0250] The eighth receiving unit to the eleventh receiving unit mentioned in the above embodiments may be a receiving interface, a receiving circuit or a receiver, etc.; the ninth sending unit to the fifteenth sending unit may be a sending interface, a sending circuit or a transmitter, etc.; the first determination unit to the third determination unit may be one or more processors.

[0251] Based on the same inventive concept as the above method, the present application embodiment provides a communication device, which may be a chip or a system on a chip in an IAB donor DU. The communication device may implement the functions performed by the IAB donor DU in the above embodiment, and the functions may be implemented by hardware, such as: In one possible implementation, Fig.10 The structure of the communication device in the embodiment of the present application is shown in FIG. Figure 3 , see Fig.10 As shown by the solid line, the communication device 1000 may include: a processor 1001 and a communication interface 1002. The processor may be used to support the communication device to implement the functions involved in the above embodiments. For example, the processor may receive downlink data and service attribute information of the downlink data sent by the IAB donor CU through the communication interface; and may also be used to map the downlink data to a corresponding BH RLC channel and send it to the next hop IAB node according to the service attribute information of the downlink data. In another possible implementation manner, see Fig.10 As shown by the dotted line, the communication device may also include a memory 1003, which is used to store computer-executable instructions and data necessary for the communication device. When the communication device is running, the processor executes the computer-executable instructions stored in the memory, so that the communication device executes the data transmission method described in the above embodiment.

[0252] Based on the same inventive concept as the above method, the embodiment of the present application provides a communication device, which can be a chip or a system on a chip in an IAB node. The communication device can implement the functions performed by the IAB node in the above embodiment, and the functions can be implemented by hardware, such as: In a possible implementation, still refer to Fig.10 As shown by the solid line in the figure, the communication device may include: a processor and a communication interface. The processor may be used to support the communication device to implement the functions involved in the above embodiments. For example, the processor may obtain downlink data and at least one of the following information of the downlink data through the communication interface: a BH RLC channel identifier, a service bearer identifier, or service attribute information; and may also be used to map the downlink data to the corresponding radio link control channel BH RLC channel of the backhaul link for transmission according to at least one information. In another possible implementation, see Fig.10 As shown by the dotted line, the communication device may also include a memory, which is used to store computer-executable instructions and data necessary for the communication device. When the communication device is running, the processor executes the computer-executable instructions stored in the memory, so that the communication device executes the data transmission method described in the above embodiment.

[0253] Based on the same inventive concept as the above method, an embodiment of the present application provides a computer-readable storage medium, which stores instructions. When the instructions are executed on a computer, they are used to execute any of the data transmission methods in the above embodiments.

[0254] Based on the same inventive concept as the above method, an embodiment of the present application provides a computer program or a computer program product. When the computer program or the computer program product is executed on a computer, the computer implements any of the data transmission methods in the above embodiments.

[0255] Those skilled in the art will appreciate that the functions described in conjunction with the various illustrative logic blocks, modules, and algorithm steps disclosed herein can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions described in the various illustrative logic blocks, modules, and steps can be stored or transmitted as one or more instructions or codes on a computer-readable medium and executed by a hardware-based processing unit. Computer-readable media may include computer-readable storage media, which corresponds to tangible media, such as data storage media, or includes any communication media that facilitates the transfer of computer programs from one place to another (e.g., according to a communication protocol). In this manner, computer-readable media may generally correspond to (1) non-temporary tangible computer-readable storage media, or (2) communication media, such as signals or carrier waves. Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, codes, and / or data structures for implementing the techniques described in this application. A computer program product may include computer-readable media.

[0256] As an example and not limitation, such computer-readable storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage, flash memory, or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer. Also, any connection is properly referred to as a computer-readable medium. For example, if instructions are transmitted from a website, server or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio and microwave are included in the definition of media. However, it should be understood that computer-readable storage media and data storage media do not include connections, carrier waves, signals or other temporary media, but are actually directed to non-temporary tangible storage media. As used herein, disks and optical disks include compact disks (CDs), laser optical disks, optical optical disks, digital versatile disks (DVDs), and Blu-ray disks, where disks typically reproduce data magnetically, while optical disks reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0257] Instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, application specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuits. Thus, the term "processor" as used herein may refer to any of the aforementioned structures or any other structure suitable for implementing the techniques described herein. Additionally, in some aspects, the functions described by the various illustrative logic blocks, modules, and steps described herein may be provided within dedicated hardware and / or software modules configured for encoding and decoding, or incorporated in a combined codec. Moreover, the techniques may be fully implemented in one or more circuits or logic elements.

[0258] The techniques of the present application may be implemented in a variety of devices or apparatuses, including a wireless handset, an integrated circuit (IC), or a set of ICs (e.g., a chipset). Various components, modules, or units are described in this application to emphasize functional aspects of devices for performing the disclosed techniques, but do not necessarily need to be implemented by different hardware units. In fact, as described above, the various units may be combined in a codec hardware unit in conjunction with appropriate software and / or firmware, or provided by interoperating hardware units (including one or more processors as described above).

[0259] In the above embodiments, the description of each embodiment has different emphases. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0260] The above are only exemplary embodiments of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A communication method for a distributed unit of an IAB host node with integrated access backhaul or a chip in a distributed unit of the IAB host node, characterized in that: include: Receiving service attribute information, address information of the access IAB node and a radio link control BH RLC channel identifier of a backhaul link from a centralized unit of the IAB host node, wherein the service attribute information and the address information of the access IAB node correspond to the BH RLC channel identifier, and the service attribute information includes a differentiated service code point DSCP or a flow label; receiving downlink data and service attribute information of the downlink data from a centralized unit of the IAB host node; Determine, according to the correspondence between the service attribute information, the address information of the access IAB node and the BH RLC channel identifier, a first BH RLC channel identifier corresponding to the service attribute information of the downlink data and the address information of the access IAB node of the downlink data, and map the downlink data to a BHRLC channel corresponding to the first BH RLC channel identifier; The IAB host node is connected to the terminal via two-hop IAB nodes.

2. The method according to claim 1, characterized in that The method further includes sending the downlink data to a next-hop IAB node.

3. The method according to claim 1 or 2, characterized in that: The service attribute information of the downlink data is encapsulated in the Internet Protocol IP layer header field.

4. A communication method applied to a centralized unit of an IAB host node with integrated access backhaul or a chip in the centralized unit of the IAB host node, characterized in that: include: Sending service attribute information, address information of the access IAB node, and an identifier of a radio link control BH RLC channel of a backhaul link to a distributed unit of the IAB host node, wherein the service attribute information and the address information of the access IAB node correspond to the identifier of the BH RLC channel, and the service attribute information includes a differentiated service code point DSCP or a flow label; Sending downlink data and service attribute information of the downlink data to a distributed unit of the IAB host node; The IAB host node is connected to the terminal via two-hop IAB nodes.

5. The method according to claim 4, characterized in that The service attribute information of the downlink data is encapsulated in the Internet Protocol IP layer header field.

6. A communication device, characterized in that: The method comprises a unit for implementing the method according to any one of claims 1 to 3.

7. A communication device, characterized in that: The method comprises a unit for implementing the method according to claim 4 or 5.

8. A communication system, characterized in that: Includes the communication device as claimed in claim 6 and the communication device as claimed in claim 7.

9. A communication system, characterized in that: Comprising user equipment, the communication device as claimed in claim 6, and / or the communication device as claimed in claim 7.

10. A communication device, characterized in that: include: At least one processor, the processor being configured to enable the method of any one of claims 1 to 5 to be executed.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the method according to any one of claims 1 to 5 is implemented. 12 . A computer program product, comprising program instructions, which, when executed by a processor, enable the method according to claim 1 to be implemented.

Images