WO2021160140A1

WO2021160140A1 - Network coding method and communication apparatus

Info

Publication number: WO2021160140A1
Application number: PCT/CN2021/076399
Authority: WO
Inventors: 刘菁; 戴明增; 朱元萍
Original assignee: 华为技术有限公司
Priority date: 2020-02-14
Filing date: 2021-02-09
Publication date: 2021-08-19
Also published as: CN113271176B; CN113271176A

Abstract

Embodiments of the present application provide a network coding method. The method can be applied in an integrated access and backhaul (IAB) network. The IAB network comprises an IAB donor and an access IAB node. The IAB donor comprises a donor distributed unit (DU) and a donor centralized unit (CU). The method comprises: the donor DU performs network coding operation on data of user equipment sent by the donor CU to generate a coding data packet; the donor DU sends the generated coding data packet to the access IAB node. According to the embodiments of the present application, the network coding function is introduced into the IAB network so as to improve the reliability of data transmission in an IAB system and reduce the data transmission delay.

Description

Network coding method and communication device

Technical field

This application relates to the communication field, and more specifically, to a network coding method, communication device, and system that can be applied to an IAB communication network.

Background technique

The next-generation communication system puts forward more stringent requirements for various performance indicators of the communication network. For example, network capacity indicators need to be increased by 1000 times, wider coverage requirements, ultra-high reliability and ultra-low latency, and so on. Therefore, the Integrated Access And Backhaul (IAB) network technology has been introduced.

In an IAB network, a relay node (Relay Node, RN), or also called an IAB node (IAB node), can provide wireless access and wireless backhaul (BH) services for user equipment. Specifically, the service data of the user equipment is connected to the IAB Donor (IAB Donor) by the IAB node through a wireless backhaul link. The IAB Donor node may also be called a Donor IAB (Donor IAB) node or an IAB Donor base station. In the next-generation New Radio (NR) communication system, the IAB donor base station can be the donor next-generation base station (Donor gNodeB, DgNB). In the Long Term Evolution (LTE) system (or 4G system), The IAB donor base station may be a donor evolved base station (Donor eNodeB, DeNB), and the IAB donor node may also be referred to as gNB, eNB or IAB Donor for short.

At present, network coding functions in communication networks, such as Random Line Network Coding (RLNC) and fountain codes, generally include: after the sender sends encoded data packets to the receiver, the sender does not need to wait The feedback information of the receiving end, after receiving enough encoded packets, the receiving end can decode and restore the original data. Take the fountain code mechanism as an example. As shown in Figure 1, Figure 1 is a schematic diagram of a network coding mechanism, in which the sender takes a group of data to be transmitted as an object, and divides the object to obtain z blocks (Block), the size of each block can be the same in the case of equal division, and then each block is divided to obtain k symbols (Symbol), in the case of equal division, the size of each symbol The size can be the same, and the k symbols are network-encoded to obtain encoded data packets. As shown in Figure 2, Figure 2 is a schematic diagram of a data packet structure after network encoding. In addition to carrying encoded data (Data), each encoded data packet sent by the sender can also carry the following information: The original Block Number (Source Block Number, SBN) corresponding to the encoded data packet, the length of the SBN can be 8 bits (bit), and the encoding Symbol ID corresponding to the encoded data packet, the length of the Symbol number can be It is 24 bits. In order to ensure that the receiving end can decode correctly, the sending end usually needs to send some control information related to data encoding to the receiving end, as shown in Figure 3, which is a schematic diagram of control information used for network encoding. The control information includes: Transfer Length (used to indicate the length of the Object, in bytes, such as 40 bits), Symbol Size (used to indicate the length of the Symbol, in bytes), Z (used to indicate the length of the Object The number of blocks contained in the block), N (used to indicate the number of sub-blocks contained in the block), AI (used to indicate the alignment parameters between symbols), and reserved bits (for example, 8 bits) .

Different from the fountain code mechanism, in the application of the network coding mechanism RLNC, the intermediate node on the path does not simply forward the received coded data packet, but re-encodes the received coded data packet. Send (that is: the received encoded data packet does not need to be decoded directly before network encoding).

In the prior art, the above-mentioned network coding function is mainly applied to data transmission on the user plane, that is, in a multi-path scenario, if a link is blocked (blockage), the receiving end only needs to receive enough encoded data packets from the other path. The original data can be decoded and recovered, thereby improving the reliability of data transmission and reducing data transmission delay. However, the current network coding function is mainly applied in the application layer of the network, for example, in an application server in a communication network.

Summary of the invention

The embodiments of the present application provide a method, device, and system for applying network coding functions in an IAB network, so as to improve the reliability of data transmission in the IAB system. In addition, it can also prevent the receiving end from responding to the same data transmitted on different paths. The data carried by the UE performs a reordering operation, which can reduce the data transmission delay.

In the first aspect, a network coding method is provided. From the perspective of the following transmission, the method is applied to access to the backhaul integrated IAB network. The IAB network includes the IAB host node IAB Donor and the access IAB node. The IAB Donor includes The donor distributed unit Donor DU and the donor centralized unit Donor CU, the method includes: the Donor DU performs a network encoding operation on the user equipment data from the Donor CU to generate an encoded data packet, and the Donor DU sends the encoded data packet Give the access to the IAB node.

Through the network coding method provided in the first aspect, the network coding function is introduced into the IAB network. The network coding operation is performed on the user equipment (UE) data from the Donor CU in the Donor DU to generate coded data packets, and then the Donor The DU sends the generated coded data packets to the access IAB node through different transmission paths, then the IAB access node can decode it as long as it can receive enough coded data packets from the Donor DU from one transmission path. And restore the original data of the user equipment, thereby improving the reliability of data transmission. In addition, it can also avoid the IAB access node from performing reordering operations on the data carried by the same UE transmitted on different transmission paths, thereby reducing data transmission. Time delay. The network code involved in the embodiment of the application may be an RLNC code, a fountain code, or other codes, which is not limited in the embodiment of the application.

In a possible implementation of the first aspect, the method includes: the Donor DU receives first configuration information from the Donor CU, where the first configuration information is used to perform the network coding operation. In this implementation, the Donor CU sends configuration information to the Dornor DU so that the Donor DU can obtain the configuration information required for network coding operations. Optionally, the Donor CU sends the configuration information to the Dornor DU, which also means to indicate at the same time Donor DU's network coding operation function is activated.

In a possible implementation of the first aspect, the first configuration information includes any one or more of the following information: the type of network coding; the size of the data block for performing network coding; the data block for performing network coding is Divide into the number of source data blocks; and, the length of characters contained in each source data block.

In a possible implementation of the first aspect, the method includes: the Donor DU receives first indication information from the Donor CU, where the first indication information is used to activate the network coding operation function of the Donor DU, so that The network coding operation is performed on the Donor DU. Optionally, the first indication information may also be used to deactivate or deactivate the network coding function of the Donor DU. Through this implementation, the Donor CU sends instructions to activate or deactivate the network coding operation function of the Donor DU, so that the activation and deactivation of the network coding operation function of the Donor DU can be controlled by the Donor CU.

In a possible implementation of the first aspect, the method includes: the Donor DU receives second indication information from the Donor CU, and the second indication information may be used to indicate that the coded data packets generated by the Donor DU are in different The transmission ratio of the transmission path. For example, the second indication information may include: the transmission ratio of the encoded data packet on the transmission path 1, and/or the transmission ratio of the encoded data packet on the transmission path 2, where the transmission path 1 or the transmission path 2 is a different transmission link between the Donor DU and the access IAB node. For example, the transmission path 1 includes nodes: the Donor DU, the first IAB node and the access IAB node, and the transmission path 2 includes nodes: the Donor DU, the second IAB node and the access IAB node. Through this implementation method, the Donor CU can instruct the Donor DU to transmit the network coded data packets generated by the Donor DU on different links when transmitting data in the downlink direction, so as to more effectively realize the load balance between the different links. Or it is beneficial to determine the transmission ratio of encoded data packets on different links according to actual needs.

In a possible implementation of the first aspect, the method includes: the Donor DU determines the transmission ratio of the coded data packet in the transmission path 1 according to the transmission condition of the downlink transmission path, and/or, the coded data packet is in the transmission path The transmission ratio of 2; where the transmission path 1 includes nodes: the Donor DU, the first IAB node and the access IAB node, and the transmission path 2 includes nodes: the Donor DU, the second IAB node and the access IAB node . Through this implementation, the Donor DU can determine the transmission ratio of the encoded data packets generated by the Donor DU on different links according to the transmission conditions of the downlink transmission path, so as to achieve load balance between different links more effectively, or to facilitate It is actually necessary to determine the transmission ratio of encoded data packets on different links.

In a possible implementation manner of the first aspect, the Donor DU receives the transmission status of the downlink transmission path sent by the Donor CU, and the transmission status of the downlink transmission path includes: any of the following information of the transmission path 1 One or more types: path information, transmission data rate, transmission data volume, and receiving buffer size; and/or, any one or more of the following information of the transmission path 2: path information, transmission data rate, transmission data And the size of the receive buffer. Through this implementation, the Donor CU can notify the Donor DU of the downlink transmission status of the transmission path 1 and/or the transmission path 2. Optionally, after learning the downlink transmission status of transmission path 1 and/or transmission path 2, Donor DU can determine the transmission ratio of the encoded data packet in transmission path 1 according to the transmission status of the downlink transmission path, and/or the encoded data packet Transmission ratio in transmission path 2.

In a possible implementation of the first aspect, the method includes: the Donor DU receives second configuration information from the Donor CU, the second configuration information includes quality of service information and at least one path information, and the quality of service The information corresponds to at least one piece of path information, and the at least one piece of path information includes: information of the transmission path 1 and/or information of the transmission path 2. Wherein, optionally, the service quality information may be service quality information corresponding to service data of one or more user equipments. Through this implementation, after the Donor DU receives the second configuration information, the Donor DU can transmit the encoded data packet generated after the data to be transmitted through the network encoding operation according to the corresponding relationship between the service quality information of the data to be transmitted and the path information. Path 1, and/or, transmission path 2 for downlink transmission.

In a possible implementation of the first aspect, the quality of service information includes: a differentiated service code point DSCP, and/or a data flow label Flow Label; the path information includes: a path identifier Path ID, and/or a route Identifies the Routing ID.

In a possible implementation of the first aspect, the network coding operation is performed before the Donor DU performs the Backhaul Adaptation Protocol (BAP) layer adding operation. In other words, in the Donor DU protocol stack design, the function of network coding operation can be included in the BAP layer function, or when the Donor DU protocol stack is designed, the BAP layer and the Internet Protocol (Internet Protocol, A new protocol layer is introduced between IP) layers to implement network coding operations.

The first aspect of this application above mainly describes downlink transmission from the perspective of Donor DU, and the second aspect of this application is mainly discussed from the perspective of Donor CU. It is understandable that the above first aspect and second aspect can be the same technical solution. From different angles of description, it can be understood in combination with each other, the above first aspect and second aspect can also be used separately for the description of the technical solution. It is understandable that the technical effects of the same or similar technical features in different aspects have been described before, so we will not repeat them one by one in the following.

The second aspect of this application proposes a network coding method, which is applied to access backhaul integrated IAB network. The IAB network includes an IAB host node IAB Donor, and the host node includes a host centralized unit Donor CU and a host distributed unit Donor DU, the method includes: the Donor CU sends first configuration information to the Donor DU, the first configuration information is used to configure the Donor DU to perform a network encoding operation on the data of the user equipment, to generate an encoded data packet and the encoded data The packet is sent to the access IAB node in the IAB network.

Through the network coding method proposed in the second aspect, the Donor CU sends configuration information to the Dornor DU, so that the Donor DU can obtain the configuration information required for the network coding operation. Optionally, the Donor CU sends the configuration information to the Dornor DU, which also means that the network coding operation function of the Donor DU is also activated. By introducing the network coding function into the IAB network, the IAB access node in the IAB network can decode and recover the original data as long as it can receive enough encoded data packets from the Donor DU from one path, thereby improving Reliability of data transmission and reduction of data transmission delay. The network code involved may be an RLNC code, a fountain code, or other codes, which is not limited in the embodiment of the application.

In a possible implementation of the second aspect, the first configuration information includes any one or more of the following information: the type of network coding; the size of the data block for performing network coding; the data block for performing network coding is Divide into the number of source data blocks; and, the length of characters contained in each source data block.

In a possible implementation of the second aspect, the method includes: the Donor CU sends first indication information to the Donor DU, and the first indication information is used to activate the network coding operation function of the Donor DU to facilitate the The Donor DU performs the network coding operation, or the first indication information is used to deactivate the network coding operation function of the Donor DU.

In a possible implementation of the second aspect, the method includes: the Donor CU sends second indication information to the Donor DU, the second indication information includes the transmission ratio of the encoded data packet on the transmission path 1, and/or , The transmission ratio of the encoded data packet in transmission path 2; wherein, the transmission path 1 includes nodes: the Donor DU, the first IAB node and the access IAB node; the transmission path 2 includes nodes: the Donor DU, the second IAB The node and the access IAB node.

In a possible implementation of the second aspect, the method includes: the Donor CU sends second configuration information to the Donor DU, the second configuration information includes service quality information and at least one path information, the service quality information and Corresponding to the at least one path information, the at least one path information includes: the information of the transmission path 1 and/or the information of the transmission path 2.

In a possible implementation of the second aspect, the method includes: the Donor CU receives downlink data delivery status (Downlink Data Delivery Status, DDDS) information from the access IAB node, and the DDDS information includes path information and Any one or more of the following information corresponding to the path information: transmission data rate, transmission data volume, and receiving buffer size. Through this implementation, Donor CU can learn the data transmission status of each downlink transmission path, such as: transmission data rate, transmission data volume, and receiving buffer size, etc. one or more kinds of information. A technical effect brought by this is: Subsequent Donor CU can indicate the reasonable transmission ratio of data on each downlink transmission path according to the data transmission situation of each downlink transmission path.

In a possible implementation of the second aspect, the quality of service information includes: a differentiated service code point DSCP, and/or a data flow label Flow Label; the path information includes: a path identifier Path ID, and/or a route Identifies the Routing ID.

In a possible implementation of the second aspect, the method includes: the Donor CU sends the first configuration information to the access IAB node. Through this implementation, the access IAB node as the receiving end of the encoded data packet can obtain the configuration information required by the network encoding operation function, so that the received encoded data packet can be decoded and the original data can be restored.

In a possible implementation of the second aspect, the method includes: the Donor CU sends third indication information to the access IAB node, and the third indication information is used to activate the network coding operation function of the access IAB node , So that the access IAB node decodes the received network code packet.

The first aspect of this application above mainly describes the downlink transmission from the perspective of Donor DU. The second aspect of this application mainly describes the downlink transmission from the perspective of Donor CU. The following third aspect of this application mainly describes the embodiments of this application from the perspective of accessing IAB nodes. In the description, it can be understood that the first aspect, the second aspect, and the third aspect of the present application may be the same technical solution described from different angles, which can be understood in combination with each other, or may be used separately for the description of the technical solution. It is understandable that the technical effects of the same or similar technical features in different aspects have been described before, so they will not be repeated hereafter.

The third aspect of this application provides a network coding method, which is applied to a wireless access backhaul integrated IAB network. The IAB network includes an IAB host node IAB Donor and an access IAB node. The IAB Donor includes a host distributed unit Donor DU and donor centralized unit Donor CU, the method includes: the access IAB node receives the coded data packet generated after the Donor DU performs the network coding operation on the user equipment; the access IAB node responds to the received The encoded data packet performs a decoding operation to recover the data of the user equipment. Through the network coding method provided by the third aspect, the network coding operation is introduced in the IAB network. The network coding operation is performed on the data of the user equipment in the Donor DU to generate coded data packets, and then the Donor DU passes the generated coded data packets through different paths Sent to the access IAB node, then the access IAB node can decode and recover the original data as long as it can receive enough encoded data packets from the Donor DU from one path, thereby improving the reliability of data transmission The network code involved can be an RLNC code, a fountain code, or other codes, which is not limited in the embodiment of the present application.

In a possible implementation of the third aspect, the method includes: the access IAB node receives first configuration information from the Donor CU, where the first configuration information is used to indicate parameters related to network coding operations, so that The access IAB node performs a decoding operation on the received encoded data packet.

In a possible implementation of the third aspect, the first configuration information includes any one or more of the following information: the type of network coding; the size of the data block for performing network coding; the data block for performing network coding is Divide into the number of source data blocks; and, the length of characters contained in each source data block.

In a possible implementation of the third aspect, the method includes: the access IAB node sends downlink data transmission status DDDS information to the Donor CU, where the DDDS information includes path information and any of the following corresponding to the path information One or more kinds of information: transmission data rate, transmission data volume, and receiving buffer size.

In a possible implementation manner of the third aspect, the path information includes: Path ID, and/or Routing ID.

In a possible implementation of the third aspect, the method includes: the access IAB node receives third indication information from the Donor CU, the third indication information is used to activate the network coding of the access IAB node Function to facilitate the access IAB node to decode the received encoded data packet.

The fourth aspect of this application provides a network coding method from the perspective of upstream transmission. This method is applied to access to an integrated backhaul IAB network. The IAB network includes access to the IAB node and the IAB host node IAB Donor, the IAB Donor Including the host distributed unit Donor DU and the centralized unit Donor CU, the method includes: the access IAB node performs a network coding operation on the data of the user equipment UE to generate a coded data packet; the access IAB node passes the coded data packet The Donor DU is sent to the Donor CU.

Through the network coding method provided in the fourth aspect, the network coding function is introduced into the IAB network, and the network coding operation is performed on the data of the user equipment at the access IAB node to generate coded data packets, and then pass the generated coded data packets through Donor DU Sent to Donor CU, Donor DU or Donor CU can decode and recover the original data of the user equipment as long as it can receive enough encoded data packets from the access IAB node from one path. For example, The Donor DU can recover the original data (for example, the PDCP PDU of the UE) through decoding, and then send the original data of the UE to the CU for subsequent processing, thereby improving the reliability of data transmission and reducing the data transmission delay. The network codes involved may be RLNC codes, fountain codes, or other codes, which are not limited in the embodiment of the present application.

In a possible implementation manner of the fourth aspect, the method includes: the access IAB node receives first configuration information from the Donor CU, where the first configuration information is used to perform the network coding operation. In this implementation manner, the Donor CU sends configuration information to the access IAB node, so that the access IAB node obtains the configuration information required for the network coding operation. Optionally, the Donor CU sending the configuration information to the access IAB node also means that it also indicates that the network coding operation function of the access IAB node is activated.

In a possible implementation manner of the fourth aspect, the first configuration information includes any one or more of the following information: the type of network coding; the size of the data block for performing network coding; the data block for performing network coding is Divide into the number of source data blocks; and, the length of characters contained in each source data block.

In a possible implementation of the fourth aspect, the method includes: the access IAB node receives first indication information from the Donor CU, where the first indication information is used to activate the network coding of the access IAB node Operation function to facilitate the access IAB node to perform the network coding operation. Optionally, the first indication information may also be used to deactivate or deactivate the network coding function of the access IAB node. Through this implementation, the Donor CU sends an instruction to activate or deactivate the network coding operation function of the access IAB node, so that the activation and deactivation of the network coding operation function of the access IAB node can be controlled by the Donor CU.

In a possible implementation of the fourth aspect, the method includes: the access IAB node receives second indication information from the Donor CU, the second indication information includes: transmission of an encoded data packet on transmission path 1 The ratio, and/or, the transmission ratio of the encoded data packet on the transmission path 2; wherein, the transmission path 1 includes nodes: the access IAB node, the first IAB node and the Donor DU, and the transmission path 2 includes nodes: the connection Enter the IAB node, the second IAB node and the Donor DU. Through this implementation, Donor CU can instruct the access IAB node to transmit data in the uplink direction, and the transmission ratio of the network coded data packet generated by the access IAB node on different links, so as to more effectively realize the transmission between different links. Load balance, or it is helpful to determine the transmission ratio of encoded data packets on different links according to actual needs.

In a possible implementation of the fourth aspect, the method includes: the access IAB node determines the transmission ratio of the encoded data packet in the transmission path 1 according to the transmission situation of the uplink transmission path, and/or the encoded data packet is The transmission ratio of transmission path 2; wherein, the transmission path 1 includes nodes: the access IAB node, the first IAB node and the Donor DU, and the transmission path 2 includes nodes: the access IAB node, the second IAB node, and the Donor DU. Through this implementation method, the access IAB node can determine the transmission ratio of the encoded data packets generated by the access IAB node on different links according to the transmission situation of the uplink transmission path, so as to more effectively realize the load balance between the different links. Or it is beneficial to determine the transmission ratio of encoded data packets on different links according to actual needs.

In a possible implementation manner of the fourth aspect, the method includes: the access IAB node receives the transmission status of the uplink transmission path sent by the Donor CU, and the transmission status of the uplink transmission path includes: the transmission status of the transmission path 1 Any one or more of the following information: path information, transmission data rate, transmission data volume, and receiving buffer size; and/or, any one or more of the following information of the transmission path 2: path information, Transmission data rate, transmission data volume and receiving buffer size. Through this implementation, the Donor CU can notify the access IAB node of the uplink transmission status of the transmission path 1 and/or the transmission path 2. Optionally, after learning the uplink transmission status of transmission path 1 and or transmission path 2, the access IAB node can determine the transmission ratio of coded data packets on transmission path 1 according to the transmission status of the uplink transmission path, and/or the coded data The transmission ratio of the packet in transmission path 2.

In a possible implementation of the fourth aspect, the method includes: the access IAB node receives second configuration information from the Donor CU, where the second configuration information includes a General Packet Radio Service Tunneling Protocol (GTP) tunnel Information and at least one path information, the GTP tunnel information corresponds to at least one path information, and the at least one path information includes: path information of the transmission path 1, and/or path information of the transmission path 2, where the GTP tunnel is established The access IAB node and the Donor CU correspond to a bearer of the user equipment. Through this implementation, after the access IAB node receives the second configuration information, the access IAB node can generate the data to be transmitted after the network encoding operation according to the corresponding relationship between the service quality information of the data to be transmitted and the path information. The encoded data packet is transmitted upstream through transmission path 1, and/or transmission path 2.

In a possible implementation of the fourth aspect, for uplink transmission, the access IAB node can send the uplink data mapped to the GTP tunnel through the corresponding path according to the corresponding relationship between the GTP tunnel and the path, that is, there is A GTP tunnel, the GTP tunnel corresponds to two or more transmission paths, in this scenario, the distribution ratio is configured according to the per path.

In a possible implementation of the fourth aspect, the GTP tunnel information includes: IP address, and/or GTP tunnel endpoint identifier (TEID); the path information includes: Path ID, and/or Or, Routing ID.

In a possible implementation manner of the fourth aspect, for uplink transmission, the access IAB node may determine the transmission offload ratio of the uplink transmission link according to the link quality of the downlink transmission link, for example, access IAB The node can determine the link quality of different links according to DDDS to determine the split ratio. Exemplarily, the access IAB node can determine the offload ratio of uplink transmission according to the reception of downlink data on different paths. For example, for downlink transmission, the access IAB node receives 30 codes per second on transmission path 1. Data packets, 50 encoded data packets are received per second on transmission path 2, indicating that the link quality of path 2 is better than that of path 1, and more data can be transmitted. Then the access IAB node can be based on this information To determine the transmission split ratio of the uplink transmission link, for example, it is determined that 40% of the uplink data is transmitted on the transmission path 1, and 60% of the uplink data is transmitted on the transmission path 2.

In a possible implementation manner of the fourth aspect, the network coding operation is performed before the access IAB node performs the BAP adding operation. That is to say, when designing the protocol stack of the IAB access node, the function of network coding operation can be included in the BAP layer function, or, when designing the protocol stack of the access IAB node, between the BAP layer and the IP layer A new protocol layer is introduced to implement network coding operations.

The fourth aspect of this application above mainly describes uplink transmission from the perspective of accessing IAB nodes. The fifth aspect of this application below mainly discusses uplink transmission from the perspective of Donor CU. It is understandable that the above fourth and fifth aspects Aspects can be descriptions of the same technical solution from different angles, and can be understood in combination with each other. The above fourth and fifth aspects can also be used separately for the description of technical solutions. It is understandable that the technical effects of the same or similar technical features in different aspects have been described before, so they may not be repeated one by one in the following.

The fifth aspect of this application proposes a network coding method, which is applied to access backhaul integrated IAB network. The IAB network includes an IAB host node IAB Donor and an access IAB node. The IAB Donor includes a donor centralized unit Donor. CU and the host distributed unit Donor DU, the method includes: the Donor CU sends first configuration information to the access IAB node, and the first configuration information is used for the access IAB node to perform network coding operations on user equipment data, To generate an encoded data packet and send the encoded data packet to the Donor CU through the Donor DU.

Through the network coding method proposed in the fifth aspect, the Donor CU sends configuration information to the access IAB node, so that the access IAB node can obtain the configuration information required for the network coding operation. Optionally, the Donor CU sending the configuration information to the access IAB node also means that it also indicates that the network coding operation function of the access IAB node is activated. By introducing the network encoding function in the IAB network, the Donor DU or Donor CU in the IAB network can decode and recover the user equipment as long as it can receive enough encoded data packets from the access IAB node from one path To improve the reliability of data transmission and reduce the delay of data transmission, the network code involved can be RLNC code, fountain code, or other codes, which is not limited in the embodiment of this application. .

In a possible implementation of the fifth aspect, the first configuration information includes any one or more of the following information: the type of network coding; the size of the data block for performing network coding; the data block for performing network coding is Divide into the number of source data blocks; and, the length of characters contained in each source data block.

In a possible implementation of the fifth aspect, the method includes: the Donor CU sends first indication information to the access IAB node, where the first indication information is used to activate the network coding operation function of the access IAB node , So that the access IAB node performs the network coding operation, or the first indication information is used to deactivate the network coding operation function of the access IAB node.

In a possible implementation of the fifth aspect, the method includes: the Donor CU sends second indication information to the access IAB node, the second indication information includes the transmission ratio of the encoded data packet on the transmission path 1, and /Or, the transmission ratio of the encoded data packet in the transmission path 2; wherein, the transmission path 1 includes nodes: the access IAB node, the first IAB node and the Donor DU, and the transmission path 2 includes nodes: the access IAB node , The second IAB node and the Donor DU.

In a possible implementation of the fifth aspect, the method may include: the Donor CU sends uplink data transmission status information to the access IAB node, and the uplink data transmission status information includes: the following information of transmission path 1 Any one or more of: path information, transmission data rate, transmission data volume, and receiving buffer size; and/or, any one or more of the following information of transmission path 2: path information, transmission data rate, The amount of transmitted data and the size of the receiving buffer; where the transmission path 1 includes nodes: the access IAB node, the first IAB node and the Donor DU, and the transmission path 2 includes nodes: the access IAB node, the second IAB node And the Donor DU. In a possible implementation manner of the fifth aspect, the method includes: the Donor CU receives the uplink data transmission status information sent from the Donor DU.

In a possible implementation manner of the fifth aspect, the method may include: the Donor CU sends the first configuration information to the Donor DU. Through this implementation, the Donor DU as the receiving end of the encoded data packet can obtain the configuration information required by the network encoding operation function, so that the received encoded data packet can be decoded and the original data can be recovered.

In a possible implementation of the fifth aspect, the method may include: the Donor CU sends third indication information to the Donor DU, and the third indication information is used to activate the network coding operation function of the Donor DU to facilitate The Donor DU decodes the received network code packet.

The above fourth aspect of the present application mainly describes the uplink transmission from the perspective of accessing the IAB node. The fifth aspect of this application mainly describes uplink transmission from the perspective of Donor CU. The sixth aspect of this application below mainly describes the embodiments of this application from the perspective of Donor DU. The six aspects can be descriptions of the same technical solution from different angles, which can be understood in combination with each other, and can also be used separately for the description of the technical solution. It is understandable that the technical effects of the same or similar technical features in different aspects have been described before, so they may not be repeated one by one in the following.

The sixth aspect of this application proposes a network coding method, which is applied to a wireless access backhaul integrated IAB network. The IAB network includes an IAB host node IAB Donor and an access IAB node. The IAB Donor includes a host distributed unit Donor DU, the method includes: the Donor DU receives an encoded data packet generated after the access IAB node performs a network encoding operation on the user equipment data; the Donor DU decodes the received encoded data packet, and restores the User device data.

Through the network coding method provided by the sixth aspect, the network coding operation is introduced into the IAB network. The network coding operation is performed on the data of the user equipment at the access IAB node to generate coded data packets, and then the access IAB node will generate the The encoded data packet is sent to the Donor DU, then the Donor DU can decode and recover the original data of the user equipment as long as it can receive enough encoded data packets from the access IAB node from one path. To improve the reliability of data transmission and reduce the delay of data transmission, the network code involved may be an RLNC code, a fountain code, or other codes, which is not limited in the embodiment of the present application.

In a possible implementation manner of the sixth aspect, the host node further includes a centralized unit Donor CU, and the method includes: the Donor DU receives first configuration information from the Donor CU, and the first configuration information is used for Indicate the parameters related to the network encoding operation, so that the Donor DU can decode the received encoded data packet.

In a possible implementation manner of the sixth aspect, the first configuration information includes any one or more of the following information: the type of network coding; the size of the data block for performing network coding; the data block for performing network coding is Divide into the number of source data blocks; and, the length of characters contained in each source data block.

In a possible implementation manner of the sixth aspect, the method includes: the Donor DU sends uplink data transmission status information to the Donor CU, and the uplink data transmission status information includes: any of the following information of transmission path 1 One or more types: path information, transmission data rate, transmission data volume, and receiving buffer size; and/or, any one or more of the following information of transmission path 2: path information, transmission data rate, transmission data volume And the size of the receiving buffer; where the transmission path 1 includes nodes: the access IAB node, the first IAB node and the Donor DU, and the transmission path 2 includes nodes: the access IAB node, the second IAB node and the Donor DU.

In a possible implementation manner of the sixth aspect, the method includes: the Donor DU receives third indication information from the Donor CU, and the third indication information is used to activate the network coding function of the Donor DU to facilitate The Donor DU performs a decoding operation on the received encoded data packet.

In a seventh aspect, a communication device is provided. The device includes a unit for performing each operation/step in the above first aspect or any possible implementation of the first aspect. The unit may be a hardware circuit, or software, or The hardware circuit is implemented in combination with software, or implemented by the processor to execute program instructions.

In an eighth aspect, a communication device is provided. The device includes a unit for performing each operation/step in the above second aspect or any possible implementation of the second aspect. The unit may be a hardware circuit, or software, or The hardware circuit is implemented in combination with software, or implemented by the processor to execute program instructions.

In a ninth aspect, a communication device is provided. The device includes a unit for performing each operation/step in the above third aspect or any possible implementation of the third aspect. The unit may be a hardware circuit, or software, or The hardware circuit is implemented in combination with software, or implemented by the processor to execute program instructions.

In a tenth aspect, a communication device is provided. The device includes a unit for executing each operation/step in the above fourth aspect or any possible implementation of the fourth aspect. The unit may be a hardware circuit, or software, or The hardware circuit is implemented in combination with software, or implemented by the processor to execute program instructions.

In an eleventh aspect, a communication device is provided. The device includes a unit for performing each operation/step in the above fifth aspect or any possible implementation of the fifth aspect. The unit can be a hardware circuit or software, Either a hardware circuit combined with software is implemented, or a processor executes program instructions.

In a twelfth aspect, a communication device is provided. The device includes a unit for performing each operation/step in the above sixth aspect or any possible implementation manner of the sixth aspect. The unit may be a hardware circuit, or software, Either a hardware circuit combined with software is implemented, or a processor executes program instructions.

In a thirteenth aspect, a communication device is provided. The device includes at least one processor, the at least one processor is coupled to a memory, the memory stores computer instructions, and the at least one processor executes the computer instructions to enable the communication The apparatus executes the above first aspect or the method in any possible implementation of the first aspect.

In a fourteenth aspect, a communication device is provided, the device includes at least one processor, the at least one processor is coupled to a memory, the memory stores computer instructions, and the at least one processor executes the computer instructions to enable the communication The device executes the above second aspect or the method in any possible implementation manner of the second aspect.

In a fifteenth aspect, a communication device is provided. The device includes at least one processor, the at least one processor is coupled to a memory, the memory stores computer instructions, and the at least one processor executes the computer instructions to enable the communication The device executes the above third aspect or the method in any possible implementation manner of the third aspect.

In a sixteenth aspect, a communication device is provided. The device includes at least one processor coupled to a memory, the memory stores computer instructions, and the at least one processor executes the computer instructions to enable the communication The device executes the above fourth aspect or any possible implementation method of the fourth aspect.

In a seventeenth aspect, a communication device is provided. The device includes at least one processor coupled to a memory, the memory stores computer instructions, and the at least one processor executes the computer instructions to enable the communication The device executes the above fifth aspect or any possible implementation of the fifth aspect.

In an eighteenth aspect, a communication device is provided, the device includes at least one processor, the at least one processor is coupled to a memory, the memory stores computer instructions, and the at least one processor executes the computer instructions to enable the communication The device executes the above sixth aspect or the method in any possible implementation manner of the sixth aspect.

In a nineteenth aspect, an IAB Donor DU is provided, the IAB Donor DU includes the communication device provided in the seventh aspect, the IAB Donor DU includes the communication device provided in the twelfth aspect, or the IAB Donor DU includes the foregoing The communication device provided by the thirteenth aspect, or the IAB Donor DU includes the communication device provided by the eighteenth aspect.

In a twentieth aspect, an IAB Donor CU is provided, the IAB Donor CU includes the communication device provided in the eighth aspect, the IAB Donor DU includes the communication device provided in the eleventh aspect, or the IAB Donor DU includes the foregoing The communication device provided in the fourteenth aspect, or the IAB Donor DU includes the communication device provided in the seventeenth aspect.

In a twenty-first aspect, an access IAB node is provided, the access IAB node includes the communication device provided in the ninth aspect, the IAB Donor DU includes the communication device provided in the tenth aspect, or the access IAB The node includes the communication device provided by the fifteenth aspect, or the IAB Donor DU includes the communication device provided by the sixteenth aspect.

In a twenty-second aspect, a computer program product is provided. The computer program product includes a computer program. When the computer program is executed by a processor, the computer program is used to execute the first aspect to the sixth aspect and any possible implementation manners thereof. Methods.

In a twenty-third aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program. When the computer program is executed, it is used to execute the first aspect to the sixth aspect and any possibilities thereof. The method in the implementation.

In a twentieth aspect, a communication system is provided, and the communication system includes one or more of the aforementioned IAB Donor DU, IAB Donor CU, and access IAB nodes.

In a twenty-first aspect, a chip is provided, the chip includes: a processor, configured to call and run a computer program from a memory, so that a communication device installed with the chip executes the first to sixth aspects and any possibilities thereof The method in the implementation.

In the method for applying network coding in the IAB network provided by the embodiments of this application, in the downlink transmission direction, the Donor DU performs network coding operations on the data from the user equipment of the Donor CU to generate an encoded data packet, and then the Donor DU encodes the data. The data packet is sent to the access IAB node; in the uplink transmission direction, the access IAB node performs network coding operations on the data of the user equipment to generate a coded data packet, and then the access IAB node passes the coded data packet through the Donor DU Sent to the Donor CU, due to the introduction of the network encoding function, in the IAB system, the receiving end of the encoded data packet can decode as long as it can receive enough encoded data packets from the sender of the encoded data packet from one path. And restore the original data of the user equipment, thereby improving the reliability of data transmission in the IAB network. In addition, it can also prevent the receiving end in the IAB system from performing reordering operations on the data carried by the same UE transmitted on different paths, which can reduce Data transmission delay.

Description of the drawings

Figure 1 is a schematic diagram of a network coding mechanism;

Figure 2 is a schematic diagram of a data packet structure after network coding;

Figure 3 is a schematic diagram of control information used for network coding;

Figure 4 is a schematic diagram of a gNB adopting a CU-DU separation architecture;

Figure 5 is a schematic diagram of a gNB using gNB-CU-CP and gNB-CU-UP to separate;

FIG. 6 is a schematic diagram of an IAB system in a two-hop data backhaul scenario provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of a control plane protocol stack in an IAB communication system provided by an embodiment of the present application;

FIG. 8 is a schematic diagram of a user plane protocol stack in an IAB communication system provided by an embodiment of the present application;

FIG. 9 is a schematic diagram of a system that introduces a network coding function into an IAB communication system provided by an embodiment of the present application;

FIG. 10 is a schematic diagram of a system for introducing a network coding function into an IAB communication system according to an embodiment of the present application;

FIG. 11 is a schematic diagram of a method for introducing network coding in an IAB communication system according to an embodiment of the present application;

FIG. 12 is a schematic diagram of a method for introducing network coding in an IAB system according to an embodiment of the present application;

FIG. 13 is a schematic diagram of a system for introducing a network coding function into an IAB communication system provided by an embodiment of the present application;

FIG. 14 is a schematic diagram of a method for introducing network coding in an IAB system according to an embodiment of the present application;

FIG. 15 is a schematic diagram of a system for introducing a network coding function into an IAB communication system according to an embodiment of the present application;

FIG. 16 is a schematic diagram of a system for introducing a network coding function into an IAB communication system according to an embodiment of the present application;

FIG. 17 is a schematic diagram of a system for introducing a network coding function into an IAB communication system according to an embodiment of the present application;

FIG. 18 is a schematic diagram of a system for introducing a network coding function into an IAB communication system provided by an embodiment of the present application;

FIG. 19 is a schematic diagram of an IAB system provided by an embodiment of the present application;

FIG. 20 is a schematic diagram of a communication device provided by an embodiment of the present application;

FIG. 21 is a schematic diagram of a communication device provided by an embodiment of the present application.

Detailed ways

The technical solution in this application will be described below in conjunction with the accompanying drawings.

The technical solutions of the embodiments of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (Time Division Duplex) , TDD), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5th Generation (5G) communication system or New Radio (NR) communication system, and various subsequent evolutions Types of advanced communication systems, etc., are not limited here.

The terminal equipment or user equipment in the embodiments of this application may refer to an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, and a user agent. Or user device. The terminal device or user equipment can also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), Handheld devices with wireless communication functions, computing devices, or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G or NR networks, or future evolution of public land mobile communication networks (Public Land Mobile Network, The terminal equipment, etc. in the PLMN), the terminal equipment or the user equipment may also be an access IAB node, etc. in the IAB system, which is not limited in the embodiment of the present application.

The access IAB nodes, intermediate IAB nodes, IAB host nodes, etc. (which can be collectively referred to as network devices) involved in the embodiments of this application are defined from a functional perspective as access network devices that can be used to communicate with terminal devices. One or more of the network equipment may be an evolutionary base station (Evolutional NodeB, eNB or eNodeB) in the LTE system, and may also be a next-generation radio access base station (NR NodeB, gNB), a distributed unit DU in the gNB. , Or the centralized unit CU in the gNB, it can also be a wireless controller in the cloud radio access network (Cloud Radio Access Network, CRAN) scenario, or the network device can also be an access point, a vehicle-mounted device, a wearable device, and The network equipment in the future communication network is not limited in the embodiment of the present application.

In the embodiments of the present application, the terminal device or the network device may include a hardware layer, may also include an operating system layer running on the hardware layer, and may also include an application layer running on the operating system layer. The hardware layer includes a central processing unit (CPU), and may also include a memory, and the memory may include hardware such as a memory management unit (MMU) and memory (also referred to as main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, for example, Linux operating systems, Unix operating systems, Android operating systems, iOS operating systems, or windows operating systems. The application layer can include applications such as browsers, address books, word processing software, instant messaging software, and so on. Moreover, the embodiments of the present application do not particularly limit the specific structure of the execution body of the method provided in the embodiments of the present application, as long as the program can run the code of the method provided in the embodiments of the present application to perform the method according to the method provided in the embodiments of the present application. It is sufficient to perform processing or communication. For example, the execution subject of the method provided in the embodiments of the present application may be a terminal device or a network device, or a hardware device in the terminal device or network device that can call and execute the program.

In addition, various aspects or features of the present application can be implemented as methods, devices, or products using standard programming and/or engineering techniques. The term "article of manufacture" used in this application encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (for example, hard disks, floppy disks or tapes, etc.), optical disks (for example, compact discs (CD), digital versatile discs (DVD)) Etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.). In addition, various storage media described herein may represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.

In the New Radio (NR) technology, according to the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) NR version 15 (Release 15), access network equipment (such as base station gNB) can be centralized by one gNB Centralized Unit (CU) and one or more Distributed Unit (DU) of gNB. gNB-CU and gNB-DU are different logical nodes and can be deployed on different physical devices or on the same physical device. Figure 4 is a schematic diagram of a gNB adopting a CU-DU separation architecture. As shown in Figure 4, gNB adopts a CU-DU separation architecture, where gNB-CU and gNB-DU are connected through an F1 interface, and gNB-CU and The 5G core network (5G core network, 5GC) is connected through the NG interface, and the gNB and gNB are connected through the Xn interface. The Xn interface includes an Xn-C interface and an Xn-U interface. The Xn-C interface is used for the transmission of control plane signaling between two gNBs, and the Xn-U interface is used for the transmission of user plane data between the two gNBs. The interface between the gNB and the user equipment (user equipment, UE) is called the Uu interface (it can also be said that it is the interface between the UE and the gNB-DU). The terminal equipment (such as UE) accesses the gNB-CU through the gNB-DU. The physical (PHY) layer, the media access control (MAC) layer and the radio link control (RLC) layer equivalent to the terminal equipment are located on the gNB-DU and are equivalent to the terminal equipment The packet data convergence protocol (PDCP) layer, radio resource control (RRC) layer, and service data adaptation protocol (SDAP) layer are located on the gNB-CU.

It should be understood that the above-mentioned protocol layer settings on gNB-DU and gNB-CU are only one way, and there may be other protocol layer settings, for example: the PHY layer and MAC layer equivalent to the terminal device are located on the gNB-DU , The PDCP layer, RRC layer, and SDAP layer equivalent to the terminal device are located on the gNB-CU, and at the same time, the RLC layer equivalent to the terminal device is also located on the gNB-CU, which are all within the scope of protection of this application. This is not limited.

For the control plane, in the uplink (UL) direction, the gNB-DU encapsulates the RRC message generated by the terminal device in the F1 Application Protocol (F1 Application Protocol, F1AP) message of the F1 interface and sends it to the gNB-CU. In the downlink (DL) direction, the gNB-CU encapsulates the RRC message of the terminal device in an F1AP message and sends it to the gNB-DU. The gNB-DU extracts the RRC message from the F1AP message and maps it to the signaling radio bearer corresponding to the Uu interface. (Signalling Radio Bearer, SRB) is sent to the terminal device.

For the user plane, in the UL direction, the gNB-DU maps the data packets of the terminal equipment received from the data radio bearer (DRB) of the Uu interface to the corresponding General Packet Radio Service Tunneling Protocol (General Packet Radio Service). Radio Service Tunnelling Protocol (GTP) is sent to the gNB-CU in the tunnel. In the DL direction, gNB-CU maps the data packet of the terminal device to the corresponding GTP tunnel and sends it to gNB-DU. The gNB-DU extracts the data packet of the terminal device from the GTP tunnel and maps the data packet to the Uu interface The corresponding DRB is sent to the terminal device.

In the architecture design of the wireless access system where the control plane and the user plane are separated, Figure 5 is a schematic diagram of gNB adopting the separation of gNB-CU-CP and gNB-CU-UP. As shown in Figure 5, gNB-CU is divided into centralized units Control plane (Central Unit-Control Plane, CU-CP) entity (also called CU-CP node) and centralized unit user plane (Central Unit-User Plane, CU-UP) entity (also called CU-UP node). Among them, gNB-CU-CP is used to provide signaling control function, gNB-CU-UP is used to provide user plane data transmission function, gNB-CU-CP and gNB-CU-UP are connected through E1 interface, gNB -CU-CP and gNB-DU are connected through the F1 control plane (F1-C) interface, and gNB-CU-UP and gNB-DU are connected through the F1 user plane (F1-U) interface. Among them, gNB-CU-CP may include RRC layer functions and PDCP layer control plane functions (for example, for processing signaling radio bearer SRB signaling), gNB-CU-UP may include SDAP layer functions and PDCP layer users Face function (for example, used to process the data of the data radio bearer DRB, etc.). The wireless access architecture shown in Figure 5 also has the following characteristics: a gNB can contain one gNB-CU-CP, multiple gNB-CU-UPs, and multiple gNB-DUs; one DU can only connect to one gNB- CU-CP; one CU-UP can be connected to only one gNB-CU-CP; one DU can be connected to multiple gNB-CU-UPs under the control of the same CU-CP; one CU-UP is in the same CU-CP Can be connected to multiple gNB-DUs under the control of. It should be understood that FIG. 5 is only exemplary, and should not impose any limitation on the architecture of the gNB. For example, under the architecture of CU-DU separation and separation of CU-CP and CU-UP, gNB can include only one gNB-CU-UP, one gNB-CU-CP, one gNB-DU, or more gNBs. -CU-UP and gNB-DU. This application is not restricted here.

In the IAB network, IAB Donor can also adopt the above-mentioned CU-DU separation architecture, that is, IAB Donor is composed of IAB Donor CU (also known as Donor CU) and IAB Donor DU (also known as Donor DU) , Where the interface between IAB Donor CU and IAB Donor DU is the F1 interface. The IAB node can be composed of a mobile terminal (MT) unit and a distributed unit (DU). IAB-MT can also be called IAB-UE, which has the function of terminal equipment, and mainly completes operations similar to terminal equipment, so as to perform the wireless backhaul function between the IAB node and the IAB Donor. IAB-DU has part of the functions of a base station, and mainly completes operations similar to a base station, so as to provide wireless access functions for UEs or next-hop IAB nodes.

For the IAB Donor, the Donor DU can have similar functions to the gNB-DU in NR, and the Donor CU can have similar functions to the gNB-CU in NR. For the IAB node, the IAB-DU can have similar functions to the gNB-DU in the NR, providing access services for its sub-nodes. Among them, the sub-nodes of the IAB-DU can be terminal devices or other IAB nodes. IAB-MT can be compared to terminal equipment and used to provide data backhaul.

In the embodiments of the present application, the IAB node accessed by the terminal device may be referred to as the access IAB node, and the IAB node on the path between the access IAB node and the IAB Donor is referred to as an intermediate IAB node.

Take the two-hop data backhaul scenario as an example, as shown in Figure 6, Figure 6 is a schematic diagram of an IAB system in a two-hop data backhaul scenario, where the terminal device is connected to IAB node 2, then IAB node 2 is called access The IAB node (or the last-hop parent node of the terminal device), the terminal device is called the next-hop child node of the IAB node 2. IAB node 1 is called the intermediate IAB node, that is to say, the previous hop parent node of IAB node 1 is the IAB host node (IAB Donor), in other words, the next hop child node of IAB Donor is IAB node 1, and IAB node 1’s The next hop child node is IAB node 2. The IAB Donor is connected to the 5G core network through the NG interface, thus forming a two-hop data backhaul scenario. Among them, the PHY layer, MAC layer and RLC layer equivalent to the terminal device are located on the access IAB node (such as: the DU part of IAB node 2), and the PDCP layer, SDAP layer and RRC layer equivalent to the terminal device are located on the Donor On the CU.

Fig. 7 is a schematic diagram of a control plane protocol stack in an IAB communication system, showing the control plane protocol stack of an IAB node adopting a layer 2 data forwarding architecture in a two-hop data backhaul scenario, where the terminal device and the access IAB Nodes can transmit control signaling between the terminal device and the donor base station through Signaling Radio Bearer (SRB), such as RRC signaling, which is connected to an IAB node (such as IAB node 2 in Figure 7). DU part) Encapsulate the RRC message generated by the terminal device in an F1AP message and send it to the Donor CU. If the Donor CU adopts the CU CP-CU UP separation architecture, the IAB node 2 DU encapsulates the RRC message generated by the terminal device in an F1AP message and sends it to the Donor CU-CP. Among them, the IAB node 2 DU and the Donor CU-CP The interface is also called the F1-C interface.

Exemplarily, FIG. 7 specifically shows the control plane protocol stack architecture of the 2-hop data backhaul scenario composed of the terminal device, the IAB node 2, the IAB node 1, and the IAB host node.

Among them, the terminal equipment has a radio resource control (Radio Resource Control, RRC) layer, a packet data convergence protocol (Packet Data Convergence Protocol, PDCP) layer, a radio link control (Radio Link Control, RLC) layer, and a media access control (Media access control) layer. The functions of the Access Control (MAC) layer and the Physics (PHY) layer.

The functional entity (for example, it can be understood as the DU unit in the aforementioned IAB node) that is oriented to communicate with the terminal device in the IAB node 2 has the functions of the RLC, MAC, and PHY layers equivalent to the terminal device. The IAB node 2 is oriented to and The functional entity of IAB node 1 communication (for example, it can be understood as the MT unit in the aforementioned IAB node) has the functions of Backhaul Adaptation Protocol (BAP) layer, RLC layer, MAC layer and PHY layer. IAB node The functional entity facing terminal equipment in 2 and the functional entity facing IAB node 1 in IAB node 2 carry out the required interaction through the hardware or software or hardware combined with software functional module in the internal IAB node 2. In IAB node 2, It also has the F1 Application Protocol (F1Application Protocol, F1AP) layer, the Stream Control Transmission Protocol (SCTP) layer, and the Internet Protocol (IP) layer for the F1 interface that communicates with the IAB host node. ; The terminal device and the IAB node 2 transmit control signaling between the terminal device and the donor base station through a signaling radio bearer (Signaling Radio Bearer, SRB), such as RRC signaling, non-access Stratum (Non-access Stratum, NAS) signaling, etc.

In the IAB node 1, the functional entities for communicating with the IAB node 2 include the functions of the BAP layer, the RLC layer, the MAC layer, and the PHY layer. In the IAB node 1, the functional entities for communicating with the IAB host node also include the corresponding BAP layer. With the functions of the RLC layer, the MAC layer and the PHY layer, the IAB node 2 and the IAB node 1 can transmit data on the backhaul link through the backhaul radio link control protocol channel (BH RLC channel, BH RLC CH).

In the control plane protocol stack architecture as shown in Figure 7, based on the architecture that separates the control plane and the user plane, the IAB host node can include the IAB host node DU (IAB Donor DU) part and the host CU-CP (Donor CU-CP) part , IAB Donor DU and Donor CU-CP communicate and interact through the F1-C interface. In the IAB Donor DU part, the functional entities for communicating with IAB node 2 include: IP layer functions. Generally, the peer IP layer is located in the access IAB The IP layer function configured on the node (IAB node 2 in Figure 7) and Donor CU, IAB Donor DU is mainly for routing and forwarding according to the received IP packet. For example, for downlink transmission, IAB Donor DU is based on IAB The destination IP address in the IP packet sent by the Donor CU routes the IP packet to the corresponding access IAB node. For upstream transmission, IAB Donor DU routes to IAB Donor CU according to the destination IP address in the received IP packet. Therefore, the source and destination addresses in the IP packet involved here generally include the IP address of Donor CU and access to IAB. The IP address of the node may not include the IP address of IAB Donor DU. The IAB Donor DU shown in Figure 7 also includes the BAP layer, RLC layer, MAC layer and PHY layer for peer-to-peer communication with IAB node 1. IAB Donor DU and IAB node 1 can perform backhaul links through BH RLC CH Data transmission; IAB Donor DU also includes the IP layer for IAB Donor CU-CP, L2 (for example: the data link layer in the wired protocol stack architecture) and L1 (for example, the physical layer in the wired protocol stack architecture) functions, The Donor CU-CP part of the IAB host node has: functions for the RRC layer and PDCP layer for peer-to-peer communication with terminal equipment, functions for the F1AP layer, SCTP layer, and IP layer for peer-to-peer communication with IAB node 2, as well as The IAB Donor DU part of the IAB host node performs the functions of L2 and L1 for peer-to-peer communication.

Figure 8 is a schematic diagram of the user plane protocol stack in an IAB communication system. Figure 8 shows the user plane protocol stack in a two-hop data backhaul scenario. The Donor CU of the host node establishes a corresponding GPRS tunneling protocol (GPRS tunneling protocol, GTP) tunnel for the service bearer of each terminal device. The tunnel can be for a terminal device or a bearer for a terminal device. Perform configuration (that is, per UE bearer's GTP tunnel). If the Donor CU adopts the architecture that separates the control plane and the user plane, then for the data transmission of the user plane, the DU of the IAB node 2 can send the service data of the terminal device to the Donor CU-UP of the IAB host node through the corresponding GTP tunnel. Among them, the interface between IAB node2 DU and Donor CU-UP can be called F1-U interface.

Exemplarily, FIG. 8 specifically shows a user plane protocol stack architecture composed of a terminal device, an IAB node 2, an IAB node 1, and an IAB host node, which is suitable for a 2-hop data backhaul scenario.

Among them, the terminal device has the functions of the Service Data Adaptation Protocol (SDAP) layer, PDCP layer, RLC layer, MAC layer and PHY layer, and the terminal device is connected to the IAB node (IAB node 2 in Figure 8) The service data of the terminal device is transmitted between the data radio bearer (Data Radio Bearer, DRB).

Among them, the functional entity (for example, it can be understood as the DU part in the aforementioned IAB node) in the IAB node 2 for communication with the terminal device has the functions of the RLC layer, the MAC layer and the PHY layer for peer-to-peer communication with the terminal device. IAB The functional entity in node 2 oriented to communicate with IAB node 1 (for example, it can be understood as the MT unit in the aforementioned IAB node) has the functions of BAP layer, RLC layer, MAC layer and PHY layer; IAB node 2 also includes The IAB host node performs peer-to-peer communication IP layer, User Datagram Protocol (UDP) layer and GPRS Tunneling Protocol-User Plane (GTP-U) functions. It can be understood that the functional entities in IAB node 2 that are oriented to communicate with terminal devices and the functional entities in IAB node 2 that are oriented to communicate with IAB node 1 or the IAB host node can be implemented through internal hardware or software or a combination of hardware and software. Ways to carry out the required information exchange. The data transmission of the backhaul link can be performed between the IAB node 2 and the IAB node 1 through the backhaul radio link control protocol channel BH RLC CH.

In the IAB node 1, the functional entities for communicating with the IAB node 2 include the functions of the BAP layer, the RLC layer, the MAC layer, and the PHY layer. In the IAB node 1, the functional entities for communicating with the IAB host node also include the corresponding BAP layer. The functions of the RLC layer, the MAC layer and the PHY layer, the IAB node 1 and the IAB Donor DU in the IAB host node can perform the data transmission of the backhaul link through the backhaul radio link control protocol channel BH RLC CH.

As shown in Figure 8, in an architecture based on the separation of the control plane and the user plane, the IAB host node in the user plane protocol stack architecture can include the IAB host node DU (IAB Donor DU) part and the host CU-UP (Donor CU-UP). ) Part, the IAB Donor DU part includes: the function of the IP layer, which is used for routing selection according to the received IP packet and the IP address contained in the IP packet. IAB Donor DU also includes the BAP for peer-to-peer communication with IAB node 1. The functions of layer, RLC layer, MAC layer and PHY layer, IAB Donor DU and IAB node 1 can use BH RLC CH for backhaul link data transmission; IAB Donor DU also includes L2 and L1 for communication with Donor CU-UP The IAB Donor DU and Donor CU-UP communicate through the F1-U interface. The Donor CU-UP part of the IAB host node has the functions of the SDAP layer and PDCP layer for peer-to-peer communication with terminal devices, the functions of the GTP-U layer, UDP layer and IP layer for peer-to-peer communication with IAB node 2, and For L2 and L1 functions for peer-to-peer communication with IAB Donor DU.

Since the current network coding function is mainly used in the application layer of the network, it has not been used in the radio access network (RAN) system, especially the air interface between devices has not been introduced into the network. Encoding function to enhance the reliability of data transmission. Specific to the IAB communication network, in the scenario where there are multiple wireless transmission paths in the IAB network, the reliability of data transmission will decrease due to blockage of one link.

In view of this, the embodiment of the application proposes to introduce the network coding function in the transmission of the air interface of the IAB communication network, and use the characteristics of the network coding function (for example, no matter which link, as long as enough coded data packets are received, it can be correct. Decode and restore the original data) to improve the reliability of air interface data transmission in the IAB scenario and reduce the delay of data transmission.

The following embodiments of the present application provide multiple ways to implement the network coding function in the IAB communication system.

Figure 9 is a schematic diagram of a system that introduces a network coding function in an IAB communication system. It shows the application of network coding function in the scenario of multiple transmission links sharing Donor DU in the IAB system. Among them, the terminal equipment (for example, UE), IAB node 1, IAB node 2, IAB node 3, and the donor base station IAB Donor. The IAB Donor consists of two parts, one part is Donor DU, and the other part is Donor CU. As shown in Figure 9, the UE uses the IAB system to perform The data or signaling transmission can be carried out through two links, one link is UE-IAB node 1-IAB node 2-IAB Donor DU-IAB Donor CU, and the other link is UE-IAB node 1-IAB node 3 -IAB Donor DU-IAB Donor CU, it can be seen that the two links are converged on the same Donor DU, so they are called a total Donor DU. Among them, IAB node 1 can be called an access IAB node, IAB node 2 and IAB node 3 can be called intermediate nodes. It is understandable that the transmission of data or signaling can be from the UE to the Donor CU in the uplink direction through the above two paths or any one of them, or from the Donor CU to the UE in the downlink direction through the above two paths or Any path is performed, which is not limited in the embodiment of the present application.

In the Donor DU scenario with multiple links shown in Figure 9, the network coding function can be applied in 3 ways in the IAB system, including:

Application 1: The network coding function is executed on the access IAB node and the Donor DU respectively.

Application 2: The network coding function is executed on the UE and Donor CU respectively.

Application 3: The network coding function is executed on the access IAB node and the Donor CU respectively.

The following is an introduction to the implementation of the different applications in the above 3 respectively. The following mainly takes the user plane as an example to describe the technical solutions of the embodiments of the present application. It can be understood that, the same applies to the embodiments of the present application, and can be used to improve the reliability of control plane signaling transmission and reduce the control plane. The delay of signaling transmission.

The first embodiment mainly corresponds to the aforementioned application 1: the execution of the network coding function on the access IAB node and the Donor DU respectively is described in detail.

Figure 10 is a schematic diagram of a system that introduces a network coding function into an IAB communication system. Figure 10 shows a system consisting of UE, IAB node 1, IAB node 2, IAB node 3, IAB Donor DU, and IAB Donor CU. The IAB communication system of the transmission link, where path 1 includes UE-IAB node 1-IAB node 2-IAB Donor DU-IAB Donor CU, path 2 includes: UE-IAB node 1-IAB node 3-IAB Donor DU-IAB Donor CU. Figure 10 also shows the user plane protocol stack architecture of UE, IAB node 1, IAB node 2, IAB node 3, Donor DU, and Donor CU. Illustratively, the generality of the user plane protocol stack architecture shown in Figure 10 The description can refer to FIG. 8 and the foregoing description of FIG. 8. The difference between the IAB communication system shown in FIG. 10 and the IAB communication system shown in FIG. 8 is that the protocol stack of the IAB node 2 in FIG. 8 and Its function corresponds to the protocol stack and function of IAB node 1 in Fig. 10, and the protocol stack and function of IAB node 1 in Fig. 8 correspond to the protocol stack and/or IAB node 2 and/or IAB node 3 in Fig. 10 Its function will not be repeated here.

Based on Figure 10, in this embodiment of the application, the network coding function applied in the IAB system can be implemented in the existing BAP layer. For example, the network coding function can be realized by extending the function of the current BAP layer. Of course, the network coding function applied in the IAB system The network coding function can also be deployed in the function of the RLC layer in the IAB system shown in Figure 10, for example, deployed in one or more of UE, IAB node 1, IAB node 2, IAB node 3, Donor DU, and Donor CU. The RLC layer of each network element; or, as an alternative as shown in Figure 10, the network coding function can also be implemented by introducing a new protocol layer between the current IP layer and the BAP layer in the IAB system, for example, Introduce a dedicated network coding function layer (eg, RLNC layer). From the above, the protocol stack architecture shown in Figure 10, if the network coding function is set to be implemented at the BAP layer, the protocol stack shown in Figure 10 does not include the function of the network coding function layer (such as the RLNC layer), that is, RLNC The function is included in the BAP layer. If the network coding function needs to be implemented by a newly added network coding function layer, the protocol stack architecture of FIG. 10 includes a newly added network coding function layer (such as the RLNC layer). Of course, the functions of the RLNC layer and the functions of the BAP layer (or other layers: RLC layer or MAC layer, etc.) can be combined to form a new layer with network coding processing functions. The name of the protocol layer of the function is not specifically limited.

Based on the foregoing, in conjunction with FIG. 10, an embodiment of the present application proposes a network coding method, which is applied to an IAB network. The IAB network includes an IAB host node IAB Donor and an access IAB node. The IAB Donor includes an IAB host distributed unit IAB Donor DU and IAB host centralized unit IAB Donor CU, take the following line transmission as an example, as shown in Figure 11. Figure 11 is a schematic diagram of a method for introducing network coding in an IAB communication system. The method includes:

Operation 1101: The IAB Donor CU sends the user equipment (UE) data to the IAB Donor DU.

Exemplarily, the IAB Donor CU in the IAB host node (for the case where the user plane and the control plane are separated for the CU function, then Donor CU-UP) maps the PDCP protocol data unit (protocol data unit, PDU) of the UE to the corresponding After the GTP tunnel, an IP packet is generated, and the IP packet is sent to Donor DU.

Operation 1102: The IAB Donor DU performs a network encoding operation on the data of the user equipment to generate an encoded data packet.

Exemplarily, the Donor DU can be based on any one or more of the value of the differentiated services code point (DSCP), the value of the Flow Label, and the destination IP address carried in the header field of the received IP packet. First, determine the route and/or bearer mapping of the IP packet, and then the Donor DU performs network coding on the IP packet with the same route and bearer mapping to generate an encoded data packet.

Exemplarily, the network coding operation performed by the IAB Donor DU may be performed before the Donor DU performs the header addition operation at the BAP layer of the backhaul adaptation protocol. In other words, in the Donor DU protocol stack design, the function of network coding operation can be included in the BAP layer function, or, in the Donor DU protocol stack design, the BAP layer and the Internet Protocol (IP ) A new protocol layer is introduced between the layers to implement network coding operations.

In an optional network coding operation, for a 1:1 bearer mapping scenario, that is, the data of a bearer of the UE is mapped to a BH RLC channel configured for the bearer of the UE on the backhaul link. Upper transmission, that is to say, a dedicated BH RLC channel is configured for the bearer of the UE. Then, in this case, the network coding operation performed on the IAB Donor DU is configured and implemented based on the per UE bearer.

In another optional network coding operation, for N:1 bearer mapping scenarios (N is a positive integer greater than or equal to 2), N different UEs have the same or similar quality of service (QoS) requirements The bearer data can be mapped to the same BH RLC channel for transmission on the backhaul link. Exemplarily, for downlink transmission, when the Donor DU receives an IP packet for downlink transmission, it cannot distinguish or does not distinguish which UE the data of the IP packet belongs to. Therefore, in the N:1 bearer mapping scenario, in the IAB When the Donor DU performs the network coding operation, the bearer data packets with the same or similar QoS belonging to different UEs are put together to perform the network coding operation and then transmitted.

Operation 1103: the IAB Donor DU sends the generated coded data packet to the access IAB node 1 through different paths.

For example, IAB Donor DU can transmit the generated encoded data packet through transmission path 1 (via IAB node 2 as shown in Figure 10 and Figure 11), and/or through transmission path 2 (via IAB node 2 as shown in Figure 10 and Figure 11). IAB node 3) transmission, where the transmission path 1 includes nodes: the Donor DU, the IAB node 2 and the access IAB node, and the transmission path 2 includes nodes: the Donor DU, the IAB node 3 and the access IAB node.

In an optional design: the IAB Donor DU may receive indication information from the Donor CU, and the indication information is used to indicate the transmission ratio of the encoded data packets generated by the Donor DU in different transmission paths. For example, the indication information includes: the transmission ratio of the encoded data packet on the transmission path 1 and/or the transmission ratio of the encoded data packet on the transmission path 2. In this design, the Donor CU in the IAB host node decides how the Donor DU's downlink is to be offloaded. Specifically, the Donor CU can send to the Donor DU indication information for indicating the offload ratio on different transmission paths, for example, the instruction The information instructs Donor DU to transmit 70% of the coded data packets to IAB node 1 through path 1, and/or, to transmit 30% of the coded data packets to IAB node 1 through path 2. It can be understood that the network coding function is processed The specific transmission ratio of the latter encoded data packets on path 1 and path 2 is not limited in the embodiment of this application. For example, 60% of the encoded data packets may be transmitted to IAB node 1 through path 1, and/or 40% The encoded data packet is transmitted to the IAB node 1 through path 2, which is not limited here. Optionally, the Donor CU may carry the indication information for indicating the offload ratios on different transmission paths in the F1AP message and send it to the Donor DU. It is understandable that, in another optional manner, the indication information used to indicate the split ratio on different transmission paths may include the amount of data transmitted on different paths, such as the amount of data transmitted by path 1 (which can be represented by bits) , And/or, the amount of data transmitted by path 2 (indicated by bits). Through this implementation method, the Donor CU can instruct the Donor DU to transmit the network coded data packets generated by the Donor DU on different links when transmitting data in the downlink direction, so as to more effectively realize the load balance between the different links. Or it is beneficial to determine the transmission ratio of encoded data packets on different links according to actual needs.

Exemplarily, the distribution ratio of the data volume on different transmission paths in the embodiment of the present application generally refers to the distribution ratio of the encoded data packet obtained after encoding the original data, but other methods are not excluded.

In an optional design, the Donor DU may determine the transmission ratio of the encoded data packet on the transmission path 1 and/or the transmission ratio of the encoded data packet on the transmission path 2 according to the transmission condition of the downlink transmission path. Through this implementation, the Donor DU can determine the transmission ratio of the encoded data packets generated by the Donor DU on different links according to the transmission conditions of the downlink transmission path, so as to achieve load balance between different links more effectively, or to facilitate It is actually necessary to determine the transmission ratio of encoded data packets on different links.

In an optional design, the Donor DU may receive the transmission status of the downlink transmission path sent by the Donor CU. Exemplarily, the transmission status of the downlink transmission path includes: any one of the following information of the transmission path 1 or Multiple: path information, transmission data rate, transmission data volume, and receiving buffer size; and/or, any one or more of the following information of the transmission path 2: path information, transmission data rate, transmission data volume, and The size of the receive buffer. Optionally, after learning the downlink transmission status of transmission path 1 and or transmission path 2, Donor DU can determine the transmission ratio of the encoded data packet in transmission path 1 according to the transmission status of the downlink transmission path, and/or the encoded data packet Transmission ratio in transmission path 2.

In an optional design, the Donor DU may receive configuration information sent by the Donor CU. The configuration information includes quality of service information and at least one path information. The quality of service information corresponds to the at least one path information, and the at least one path The information includes: information of the transmission path 1 and/or information of the transmission path 2. Wherein, optionally, the service quality information may be service quality information corresponding to service data of one or more user equipments. Through this implementation, after the Donor DU obtains the configuration information, the Donor DU can pass the encoded data packet generated after the data to be transmitted through the network encoding operation through the transmission path according to the corresponding relationship between the quality of service information of the data to be transmitted and the path information. 1, and/or, transmission path 2 performs downlink transmission. Exemplarily, the service quality information may include: a differentiated service code point DSCP, and/or a data flow label Flow Label; the path information includes: a path identifier Path ID, and/or a routing identifier Routing ID. Through this implementation, when the Donor DU is performing downlink data transmission, it can determine the transmission ratio of encoded data packets on different transmission paths according to the quality of service information.

In an optional design, the Donor CU can receive the DDDS from the access IAB node. The DDDS information includes path information and any one or more of the following information corresponding to the path information: transmission data rate, transmission data And the size of the receive buffer. Through this implementation method, the Donor CU can learn one or more types of information such as the data transmission status of each downlink transmission path, the transmission data rate, the transmission data volume, and the size of the receiving buffer. A technical effect brought by this is that the follow-up Donor According to the data transmission conditions of each downlink transmission path, the CU can instruct Donor DU to transmit a reasonable transmission ratio on each downlink transmission path when transmitting encoded data packets.

Operation 1104: access the IAB node 1 to decode the received encoded data packet, and obtain the original data of the user equipment.

Exemplarily, the IAB node 1 decodes the encoded data packets received on different paths to obtain the IP packet, and sends the IP packet to the GTP-U layer for processing, and then obtains the PDCP PDU of the UE, and then obtains the PDCP PDU of the UE. The received PDCP PDU is sent to the UE, and the UE hands it to the PDCP layer for corresponding processing (for example, sorting and/or repeated packet detection operations at the PDCP layer), thereby obtaining the original data of the UE.

Through the network encoding method shown in Figure 11, the receiving end (IAB node 1) can decode and recover the user as long as it can receive enough encoded data packets from the sender (IAB Donor DU) from one path. The original data of the device, thereby improving the reliability of data transmission and reducing the delay of data transmission. The network coding operations involved here can be RLNC codes, fountain codes, or other applicable codes. Examples of this application There is no restriction on this.

Exemplarily, based on the method shown in Figure 11, in an optional design: before the Donor DU performs the network coding operation, the Donor CU can send configuration information to the Donor DU, which enables the Donor DU to perform the network coding operation, such as , The configuration information includes any one or more of the following information: the type of network coding; the size of the data block that performs network coding; the number of data blocks that perform network coding is divided into source data blocks; and, each source The length of the characters contained in the data block. Correspondingly, the Donor CU may also send the configuration information to the access IAB node, so that the access IAB node can receive and decode the network coded data packet according to the corresponding configuration information when receiving the network coded data packet in the downlink. In this design, Donor DU performs corresponding network coding operations based on the configuration information provided by Donor CU. In an optional design, Donor CU can send multiple sets of configuration information to Donor DU and/or access IAB nodes. The multiple sets of configuration information correspond to different types of network coding operations. Each set of configuration information can include the following Any one or more kinds of information: the type of network coding; the size of the data block that performs network coding; the number of data blocks that perform network coding is divided into source data blocks; and the length of characters contained in each source data block . In an optional design, Donor CU sends configuration information to Dornor DU, which can also mean that the network coding operation function of Donor DU is activated at the same time. Similarly, Donor CU sends configuration information to access IAB node 1. It means that the network coding operation function of indicating access to IAB node 1 is activated at the same time; in another optional way, before the Donor DU performs the network coding operation, the Donor CU can also send instructions to the Donor DU to indicate the Donor. The DU activates or turns on the network coding function, and performs the corresponding network coding operations. Optionally, the IAB Donor CU can also send instructions to the access IAB node 1 to instruct the access IAB node 1 to activate or enable the network coding function, and Perform the corresponding decoding operation.

Exemplarily, based on the method shown in Figure 11, in an optional design: Donor DU or access IAB node can obtain network coding operation configuration information from other networks, such as Donor DU or access IAB node can be managed from operation management The maintenance (operations, administration and maintenance, OAM) system obtains multiple sets of configuration information, which correspond to different types of network coding operations, and each set of configuration information may include any one or more of the following information: Type; the size of the data block for performing network coding; the number of source data blocks that the data block for performing network coding is divided into; and the length of characters contained in each source data block. Or the Donor DU or the access IAB node can pre-store these multiple sets of configuration information at the factory.

Exemplarily, based on the method shown in Figure 11, in an optional design: for the case where the Donor DU or the access IAB node is configured with multiple sets of configuration information for network coding operations, the Donor DU or the access IAB node can be configured from The Donor CU obtains indication information, which is used to indicate which set of configuration information the Donor DU or access to the IAB node needs to activate, and uses the activated configuration information to perform network coding operations or decoding operations. Combining the IAB system protocol stack architecture shown in FIG. 10 and the network coding method shown in FIG. 11, taking the realization of the network coding function in the BAP layer as an example, the following description of the embodiments of the present application will be continued.

Figure 12 shows a method of introducing network coding in the IAB system. The network coding function needs to be completed before the BAP layer header operation, for example: after the routing and bearer mapping operations are determined, before the BAP layer header operation, Introduce network coding operations. Exemplarily, the method includes:

Operation 1201: IAB access node (e.g., Figure 10, IAB node 1 in Figure 11, from the perspective of upstream transmission, the following is the same in this embodiment, and will not be repeated) or IAB host node (e.g., Figure 10, Figure 11 In the IAB Donor DU in the lower row transmission perspective, the following is the same in this embodiment, and will not be repeated here) Determine the transmission route of the UE's data. Exemplarily, the data transmission link between IAB node 1 and Donor DU includes IAB node 2 and/or IAB node 3. Therefore, IAB node 1 or Donor DU can determine UE data based on the routing information configured by Donor CU The address of the next hop transmission node in the IAB system, thereby determining whether the data transmission path is path 1 or path 2.

Operation 1202: the IAB access node or the IAB host node determines the bearer mapping of the data from the UE on the backhaul link. Exemplarily, once the transmission path of the UE’s data is determined, there may be multiple BH RLC channels on the transmission path. Therefore, in order to meet the quality of service (QoS) guarantee of the UE’s data in the transmission process (guarantee), the data of the UE needs to be mapped to the BH RLC channel corresponding to the QoS guarantee for transmission.

Operation 1203: the IAB access node or the IAB host node performs network coding processing operations on the UE data to be sent, for example, performing RLNC code operations.

Operation 1204: BAP plus header (header) operation. Exemplarily, in operation 1104, in the IAB access node or the IAB host node, the header information of the BAP layer is added to the data packet generated by the network coding operation in the RLNC mode, for example: the added header information includes the information used for routing Identification (Routing ID).

In a network coding operation, for a 1:1 bearer mapping scenario, that is, the data of a bearer of the UE is mapped to a BH RLC channel configured for the bearer of the UE on the backhaul link for transmission. That is to say, a dedicated BH RLC channel is configured for the bearer of the UE. In this case, the network coding function is configured and implemented based on the per UE bearer.

In another network coding operation, for N:1 bearer mapping scenarios (N is a positive integer greater than or equal to 2), bearers belonging to N different UEs with the same or similar quality of service (QoS) requirements The data can be mapped to the same BH RLC channel for transmission on the backhaul link. Exemplarily, for downlink transmission, when the Donor DU receives an IP packet for downlink transmission, it cannot distinguish or does not distinguish which UE the data of the IP packet belongs to. Therefore, in the N:1 bearer mapping scenario, it is different. The bearer data packets of the UEs with the same or similar QoS are put together to perform network coding operations and then transmitted.

With reference to the above embodiments of the application, another embodiment of the application is shown in FIG. 13, which is a schematic diagram of a system that introduces a network coding function into an IAB communication system, as shown in FIG. 13, where IP packets (IP Packets) are in The transmission between the Donor DU and the Donor CU is carried out through the F1 interface. In an optional design, the Donor CU adds the same DSCP/flow label value to the header field of the IP packet carried by the same UE. The Donor CU can give Donor DU configures the mapping relationship between the same DSCP/flow label value and different paths, that is: the same DSCP/flow label value can correspond to one or more paths, in other words, IP packets with the same DSCP/flow label value It can be mapped to multiple paths for transmission. Illustratively, DSCP 1/flow label 1 corresponds to path 1, and at the same time, DSCP 1/flow label 1 can also correspond to path 2. Donor DU performs network encoding processing on the IP packets from Donor CU to obtain encoded data packets (as shown in Figure 13, the symbol "□" indicates that the encoded data packets in the subsequent embodiments of this application can be represented by the same symbol), exemplary As shown in Figure 13, Donor DU performs network encoding processing on the IP packets from Donor CU to obtain 7 encoded data packets, (optional) based on the indication information sent by Donor CU to indicate the proportion of offloads on different paths, Donor DU The coded data packets are split to different paths for transmission, for example, 4 of the 7 coded data packets are transmitted through path 1, and or, 3 of the 7 coded data packets are transmitted through path 2. In an optional design, for the N:1 bearer mapping scenario, the Donor DU can perform network coding together with IP packets belonging to N UEs with the same route and/or bearer mapping, and then access the IAB node (as shown in Figure 10). The middle IAB node 1) decodes the received encoded data packet and recovers the IP packet, which is then handed over to the GTP-U layer for processing to distinguish the data of different UEs.

As shown in Figure 13, in an optional design, in order to help the Donor CU to make offloading decisions, the Donor CU needs to know the transmission conditions of the encoded data packets on different paths. Exemplarily, an IAB node (such as IAB node 1 in Figure 10, Figure 11) can be accessed to send a downlink data transmission status (Downlink Data Delivery Status, DDDS) feedback for the UE bearer (per UE bearer) to the Donor CU. , To know the transmission status of encoded data packets on different paths (such as the aforementioned path 1 and or path 2). In this design, the content carried in the existing DDDS message can be expanded, and the DDDS message can be added Any one or more of the following information:

Path information, for example: Path ID or Routing ID. Among them, the Routing ID includes the Path ID and the BAP address of the routing target node (for example, the BAP address of the access IAB node).

The transmission data rate, for example, the received data rate (Data rate).

The amount of transmitted data, for example, the amount of received data.

The size of the buffer, for example, the size of the buffer used for receiving.

Among them, the received data rate, the received data volume, and the received buffer size can respectively correspond to the path information one-to-one. It can also be understood that the newly added information in the DDDS message includes the received data rate for a certain transmission path or a certain transmission The received data volume of the path or the receiving buffer size of a certain transmission path. In this way, on the basis that the Donor CU obtains the transmission conditions of the encoded data packets on different transmission paths, the Donor CU can decide the transmission ratio or data volume of the encoded data packets on different transmission paths.

As shown in Figure 13, in an optional design, unlike the aforementioned Donor CU determines the proportion of network coded data packets on different paths, the Donor DU decides on its own the ratio of the network coded data packets to be transmitted on different paths. Shunt ratio. In this scenario, in order to help the Donor DU make better decisions about the transmission and distribution of encoded data packets, the Donor CU can notify the Donor DU of the transmission of the encoded data packets on different paths. For example, the Donor CU will make any of the following Or multiple types of information are sent to the Donor DU, so that the Donor DU can determine the distribution ratio of the network coded data packets transmitted on different paths:

Path information, for example: Path ID or Routing ID.

Transmission data rate, for example, receive data rate.

The amount of data transmitted, for example, the amount of data received.

The size of the buffer, such as the size of the buffer used for receiving.

The above information can be similar to the extended information carried in the aforementioned DDDS message, where the received data rate, the received data volume, and the received buffer size can respectively correspond to the path information one-to-one, and the details are not repeated here.

As shown in Figure 13, in an optional design, in order for the access IAB node to correctly decode the received encoded data packet, the Donor CU may send some network coding-related control information to the access IAB node. The control information related to the network coding can be carried in an RRC message or an F1AP message and sent. Among them, the control information related to network coding includes one or more of the following information:

The type of network coding, for example: Raptor Q code, or RLNC code, etc.

The size of the data block for network coding, such as the size or length of the object.

The number of source data blocks that the network coded data block is divided into, for example: the number of blocks contained in the Object, or the length of each block.

The length of the characters contained in each source data block, for example: the length of the symbol, or the number of symbols contained in each block.

In conjunction with the activation of the network coding function of the access IAB node as shown in Figure 13, in an optional design, the access IAB node only needs to receive the control information related to the network coding sent by the Donor CU, it is considered to be in the network of the IAB node. The coding function is activated. In another alternative design, the Donor CU may send an activation indication message to the IAB node to indicate that the downlink network coding function is activated. For example, the activation indication information may be used to indicate that the access IAB node needs to respond to the received The downlink data packet is decoded and then sent to the upper layer for processing. Exemplarily, the activation indication information may be carried in an RRC message sent by the Donor CU to the UE. It is understandable that the network coding function for uplink transmission and downlink transmission can be activated by using one activation indication information, or can be activated by using two activation indication information respectively. Exemplarily, when an activation indication message is used to activate the network coding function, when the access IAB node receives the activation indication information from the Donor CU, it will consider that the network coding functions for both uplink transmission and downlink transmission are activated by default; when When two activation indication messages are used to activate the network coding function, one of the activation indication messages is used to activate the network coding function for uplink transmission, and the other activation indication information is used to activate the network coding function for downlink transmission. The implementation method includes the use of a bit. When the value of this bit is 1, it means that the network coding function of uplink transmission is activated. When the value of this bit is 0, it means that the network coding function of downlink transmission is activated. Of course, you can It is understood that the value here is not limited. For example, when the value of this bit is 0, it means that the network coding function of uplink transmission is activated, and when the value of this bit is 1, it means that the network coding function of downlink transmission is activated. It is understandable that for the activation of the network coding function of IAB Donor DU in the IAB system, similarly, the network coding function for uplink transmission and downlink transmission can be activated using one activation indication message, or two activation indication messages can be used separately To activate, I won’t repeat it here.

Referring to FIG. 10, another embodiment of the present application proposes a network coding method, which is applied to an IAB network. The IAB network includes an IAB host node IAB Donor and an access IAB node. The IAB Donor includes an IAB host distributed unit IAB Donor DU and IAB host the centralized unit IAB Donor CU. Take upstream transmission as an example, as shown in Figure 14. Figure 14 is a schematic diagram of a method for introducing network coding in an IAB system. The method includes:

Operation 1401: send user equipment (UE) data to the access IAB node 1.

Operation 1402: Access the IAB node 1 to perform a network coding operation on data from one or more UEs, and generate coded data packets.

Exemplarily, the access IAB node 1 may determine the route of the IP packet according to any one or more of the value of DSCP, the value of Flow Label, and the target IP address carried in the header field of the IP packet of the received UE. And/or bearer mapping, the access IAB node 1 performs network coding on IP packets with the same route and bearer mapping to generate coded data packets.

Exemplarily, the access IAB node 1 to perform the network coding operation may be performed before the access IAB node 1 performs the backhaul adaptation protocol BAP layer header operation. That is to say, when designing the protocol stack for accessing the IAB node, the function of network coding operation can be included in the BAP layer function, or, when designing the protocol stack for accessing the IAB node, exemplarily, as shown in Figure 10 It shows that a new protocol layer is introduced between the BAP layer and the Internet Protocol (IP) layer to implement network coding operations.

In an optional network coding operation, for a 1:1 bearer mapping scenario, that is, the data of a bearer of a UE is mapped to a BH RLC channel configured for the bearer of the UE on the backhaul link. Uplink transmission, that is to say, a dedicated BH RLC channel is configured for the bearer of a UE. Then, in this case, the network coding operation performed on the access IAB node 1 is configured and implemented based on the per UE bearer.

In another optional network coding operation, for the N:1 bearer mapping scenario (N is a positive integer greater than or equal to 2), the data of bearers with the same or similar service quality requirements belonging to N different UEs are transmitted back The link can be mapped to the same BH RLC channel for transmission. Exemplarily, for uplink transmission, when the access IAB node 1 receives an IP packet for uplink transmission from one or more UEs, it cannot distinguish or does not distinguish which UE the data of the IP packet belongs to. Therefore, in In the N:1 bearer mapping scenario, when accessing the IAB node 1 to perform a network coding operation, bearer data packets with the same or similar QoS belonging to different UEs can be put together to perform the network coding operation and then transmitted.

Operation 1403: The access IAB node 1 sends the generated coded data packet to the access IAB Donor DU through different paths.

For example, the access IAB node 1 can transmit the generated encoded data packet through the transmission path 1 (via the IAB node 2 as shown in Figure 10 and Figure 11), and/or through the transmission path 2 (as shown in Figure 10 and Figure 11). Indicates transmission via IAB node 3), where the transmission path 1 includes nodes: the access IAB node, IAB node 2 and the Donor DU, and the transmission path 2 includes nodes: the access IAB node, IAB node 3 and the Donor DU.

In an optional design: the access IAB node may receive indication information from the Donor CU, where the indication information is used to indicate the transmission ratio of the encoded data packets generated by the access IAB node in different transmission paths. For example, the indication information includes: the transmission ratio of the encoded data packet on the transmission path 1 and/or the transmission ratio of the encoded data packet on the transmission path 2. In this design, the Donor CU in the IAB host node decides how to offload the uplink transmission of the access IAB node. Specifically, the Donor CU can send indication information for indicating the offload ratio to the access IAB node, for example, The indication information indicates that the access IAB node transmits 70% of the coded data packets to the IAB node 1 through path 1 and/or transmits 30% of the coded data packets to the IAB node 1 through path 2. Optionally, the Donor CU may carry the indication information for indicating the offload ratio in an RRC message or an F1AP message and send it to the access IAB node. It is understandable that, in another optional manner, the indication information sent by the Donor CU to indicate the split ratio may include the amount of data transmitted on different paths, such as the amount of data transmitted by path 1 (for example, represented by bits). ), and/or the amount of data transmitted by path 2 (for example, expressed in bits). Through this implementation, the Donor CU can instruct the access IAB node to transmit data in the uplink direction, the transmission ratio of the network coded data packet generated by the access IAB node on different links, so as to more effectively implement different links The load balance between the two, or is conducive to determining the transmission ratio of encoded data packets on different links according to actual needs.

In an optional design, the access IAB node may determine the transmission ratio of encoded data packets on transmission path 1 and/or the transmission ratio of encoded data packets on transmission path 2 according to the transmission conditions of the uplink transmission path. It is more effective to achieve load balance between different links, or to determine the transmission ratio of encoded data packets on different links according to actual needs.

In an optional design, the access IAB node may receive the transmission status of the uplink transmission path sent by the Donor CU. Illustratively, the transmission status of the uplink transmission path includes: any of the following information of transmission path 1 One or more types: path information, transmission data rate, transmission data volume, and receiving buffer size; and/or, any one or more of the following information of the transmission path 2: path information, transmission data rate, transmission data And the size of the receive buffer. Optionally, after learning the uplink transmission status of transmission path 1 and/or transmission path 2, the access IAB node can determine the transmission ratio of encoded data packets on transmission path 1 according to the transmission status of the uplink transmission path, and/or , The transmission ratio of encoded data packets in transmission path 2.

In an optional design, the access IAB node may receive configuration information sent by the Donor CU, the configuration information includes quality of service information and at least one path information, the quality of service information corresponds to the at least one path information, and the at least one path information A piece of path information includes: information of the transmission path 1 and/or information of the transmission path 2. Wherein, optionally, the service quality information may be service quality information corresponding to service data of one or more user equipments. Through this implementation, after the access IAB node obtains the configuration information, the access IAB node can, according to the corresponding relationship between the service quality information of the data to be transmitted and the path information, convert the data to be transmitted to the code generated after the network coding operation The data packet is transmitted upstream through transmission path 1, and/or transmission path 2. Exemplarily, the service quality information may include: differentiated service code point DSCP, and/or data flow label Flow Label, or, the service quality information may include: GTP tunnel identifier (ie: IP address + GTP TEID). In this case, the uplink transmission can perform bearer mapping and/or path selection through the GTP tunnel identifier, so the configuration information may include the GTP tunnel identifier and path information corresponding to the GTP tunnel identifier; the path information includes: path Identifies the Path ID, and/or, the Routing ID. Through this implementation manner, when the access IAB node performs data transmission in the uplink direction, the transmission ratio of the encoded data packets on different transmission paths can be determined according to the quality of service information.

In an optional design, the access IAB node may receive the path information of the uplink transmission path sent by the Donor CU and any one or more of the following information corresponding to the path information: transmission data rate, transmission data And the size of the receive buffer. Through this implementation, the access IAB node can learn one or more of the data transmission status, transmission data rate, transmission data volume, and receiving buffer size of each uplink transmission path, which brings a technical effect Yes, the subsequent access IAB node can set a reasonable transmission ratio in each uplink transmission path when transmitting encoded data packets according to the data transmission conditions of each uplink transmission path.

Operation 1404: the IAB Donor DU decodes the received encoded data packet to obtain the original data of the UE.

Exemplarily, IAB Donor DU decodes the encoded data packets received on different paths and obtains the original data IP packets before encoding. Then, IAB Donor DU further sends the decoded IP packets to IAB Donor. CU, IAB Donor CU sends the received IP packet to the GTP-U layer for processing, and then obtains the original data PDCP PDU of the UE, and then passes the obtained PDCP PDU to the PDCP layer for corresponding processing (for example, in the PDCP layer) Sequence and/or repeat packet detection operations), thereby further obtaining the PDCP SDU of the UE. Through the network coding method shown in Figure 14, the receiver (IAB Donor DU) can decode and pass IAB as long as it can receive enough encoded data packets from the sender (access to IAB node 1) from one path. Donor CU restores the original data of the user equipment, thereby improving the reliability of data transmission and reducing data transmission delay. The network code involved here can be RLNC, fountain code, or other codes. The application embodiment does not limit this.

Exemplarily, for this embodiment, regarding the restoration of the original data of the UE, the processing inconsistencies between the uplink transmission direction and the downlink transmission direction include: for example, in the downlink direction, the GTP tunnel is established on the access IAB node, so the connection The incoming IAB node can recover the UE PDCP PDU, and then send it to the UE through the air interface so that the PDCP layer on the UE recovers the PDCP SDU of the UE after processing. In the uplink direction, the GTP tunnel is established on the Donor CU, and the Donor DU can only Decoding restores the original IP packet before encoding, and then the Donor DU sends the restored IP packet to the Donor CU. After the Donor CU is processed by the GTP layer, the PDCP PDU of the UE can be obtained, and then the PDCP layer is processed to obtain the UE. PDCP SDU. In short, for uplink and downlink transmission, the original UE data can be the PDCP PDU of the UE, for downlink transmission, the PDCP PDU of the UE is restored on the access IAB node, and for uplink transmission, the UE is restored on the Donor CU. PDCP PDU.

Exemplarily, based on the method shown in Figure 14, in an optional design: before accessing the IAB node 1 to perform the network coding operation, the Donor CU can send configuration information to the accessing IAB node 1, and the configuration information makes the access The IAB node 1 can perform network coding operations. For example, the configuration information includes any one or more of the following information: the type of network coding; the size of the data block for performing network coding; the data block for performing network coding is divided into sources The number of data blocks; and, the length of characters contained in each source data block. Correspondingly, the Donor CU can also send the configuration information to the IAB Donor DU, so that the IAB Donor DU can receive and decode the corresponding configuration information according to the corresponding configuration information when the IAB Donor DU receives the network coded data packet in the uplink. In this design, Donor DU performs corresponding network coding operations based on the configuration information provided by Donor CU. In an optional design, Donor CU can send multiple sets of configuration information to Donor DU and/or access IAB nodes. The multiple sets of configuration information correspond to different types of network coding operations. Each set of configuration information can include the following Any one or more kinds of information: the type of network coding; the size of the data block that performs network coding; the number of data blocks that perform network coding is divided into source data blocks; and the length of characters contained in each source data block . In an optional design, the Donor CU sends configuration information to the access IAB node 1, which can also mean that the network coding operation function of the access IAB node 1 is activated at the same time. Similarly, the Donor CU sends the Donor DU The configuration information can also mean that the network coding function of the Donor DU is also activated; in another optional way, before the access IAB node 1 performs the network coding operation, the Donor CU can also send instructions to The access IAB node 1 instructs the access IAB node 1 to activate or enable the network coding function, and perform the corresponding network coding operation. Optionally, the IAB Donor CU can also send instructions to the IAB Donor DU to indicate the IABDonor DU activates or turns on the network encoding function, and executes the corresponding decoding operation.

Exemplarily, based on the method shown in Figure 14, in an optional design: Donor DU or access IAB node can obtain network coding operation configuration information from other networks, such as Donor DU or access IAB node can be managed from operation management The operation administration and maintenance (OAM) system obtains multiple sets of configuration information, and the multiple sets of configuration information correspond to different network coding types. Each set of configuration information may include any one or more of the following information: network coding type; The size of the data block for performing network coding; the number of source data blocks that the data block for performing network coding is divided into; and the length of characters contained in each source data block. Alternatively, the Donor DU or the access IAB node can pre-store these multiple sets of configuration information at the factory.

Exemplarily, based on the method shown in Figure 14, in an optional design: for the case where the Donor DU or the access IAB node is configured with multiple sets of configuration information for network coding operations, the Donor DU or the access IAB node can be from The Donor CU obtains indication information, which is used to indicate which set of configuration information the Donor DU or access to the IAB node needs to activate, and uses the activated configuration information to perform network coding operations or decoding operations.

FIG. 15 is a schematic diagram of a system that introduces a network coding function in an IAB communication system. With reference to FIG. 15, the following describes an embodiment of the present application with respect to the uplink transmission direction.

As shown in Figure 15, the UE sends at least one PDCP PDU it generates to the access IAB node, that is, IAB node 1) in Figure 15. IAB node 1 maps the UE’s PDCP PDU to the corresponding GTP tunnel to generate IP Packet, and perform network encoding on one or more IP packets with the same routing and bearer mapping to generate encoded data packets, and then map the generated encoded data packets to different paths and send them to the Donor DU, and the Donor DU will be different After decoding the encoded data packet received on the path, the IP packet is recovered and sent to the Donor CU. The Donor CU sends the received IP packet to the GTP-U layer for processing, and then obtains the PDCP PDU of the UE, and then sends the PDCP PDU to the PDCP layer for processing.

With reference to Figure 15, in an alternative design, the IAB node 1 sends the coded data packet after network coding to the Donor DU. For the offloading decision of the network coded packet on different paths, the embodiment of this application proposes the following alternative methods :

Method 1: Donor CU decides the upstream offload strategy for accessing IAB node 1.

Exemplarily, in an optional design, Donor CU is the same bearer of the same UE and the bearer establishes two GTP tunnels between IAB node 1 and Donor CU, as shown in Figure 15, GTP-U 1 and GTP-U 2, These two GTP tunnels correspond to one DRB of the same UE between the UE and the IAB node 1. Donor CU configures the mapping relationship between these two GTP tunnels and different transmission paths for the access IAB node, and sends the corresponding configuration information to the access IAB node. The configuration information may include: GTP-U 1 is mapped to path 1, through IAB node 2 performs transmission, and/or, GTP-U 2 is mapped to path 2, and is transmitted through IAB node 3. Of course, GTP-U 1 can also be mapped to path 2 and transmitted through IAB node 3, and /Or, GTP-U 2 is mapped to path 1, and is transmitted through IAB node 2, which is not limited in the embodiment of the present application.

With reference to Figure 15, in an optional design, in order to help the access IAB node perform the offload decision of the Donor CU, the Donor CU may send offload ratio indication information to the IAB node 1, and the offload ratio indication information corresponds to the GTP tunnel identifier. It can be configured together when the GTP tunnel is established, or it can be adjusted according to the path link condition after the GTP tunnel is established, so that the access IAB node can learn a certain percentage (for example, expressed as a percentage) from the same DRB of the same UE. The data volume needs to be diverted to GTP-U 1 for transmission, and/or a certain percentage (for example, expressed as a percentage) of the data volume needs to be diverted to GTP-U 2 for transmission, for example: the percentage of offload information indicates that 70% of the data volume is diverted For transmission on GTP-U 1, 30% of the data volume is shunted to GTP-U 2 for transmission. . Alternatively, the offload ratio indication information may also correspond to path information, where the path information may be Path ID or Routing ID. The Donor CU may carry the offload ratio indication information in an RRC message and send it to the MT part that accesses the IAB node 1, or carry it in an F1 AP message and send it to the DU part that accesses the IAB node 1.

With reference to Figure 15, in an optional design, Donor CU determines the mapping relationship between GTP tunnels and paths. For example, GTP-U 1 is mapped to path 1, and transmitted through IAB node 2, and GTP-U 2 is mapped To path 2, it is transmitted through IAB node 3; but the specific data distribution ratio is determined by the access IAB node itself. For example, the access IAB node decides on its own that a certain amount or proportion of data is offloaded to GTP-U 1 for transmission, and/or a certain amount or proportion of data is offloaded to GTP-U 2 for transmission. Optionally, access to IAB node 1 can also adjust the proportion of encoded data packets sent on different paths according to the conditions of sending data on different paths. For example, access to IAB node 1 can be based on the load of path 1 and path 2. According to the situation, adjust the transmission ratio on different paths. If the load on path 1 is high, increase the transmission ratio on path 2.

With reference to Figure 16, Figure 16 is another schematic diagram of the introduction of the network coding function in the IAB system. The difference from the IAB system shown in Figure 15 is that in the IAB system shown in Figure 16, the Donor CU is the same UE bearer Only one GTP tunnel GTP-U 1 is established between the access IAB node (IAB node1DU) and the Donor CU. This GTP tunnel GTP-U 1 corresponds to the UE DRB between the UE and the IAB node 1. Donor CU can configure the mapping relationship between this GTP tunnel and different paths for access to IAB node 1. For example: Donor CU provides configuration information for access to IAB node 1. The configuration information includes: GTP-U 1 is mapped to path 1, which can be For transmission through IAB node 2, GTP-U 1 can also be mapped to path 2, and transmitted through IAB node 3. In this scenario, for the same reason, in order to help the access IAB node 1 perform the offload decision of the Donor CU, the Donor CU may send a offload ratio indication information to the access IAB node. For example, the offload ratio indication information may be the same as the path information. Correspondingly, the path information can be Path ID or Routing ID, so that the access IAB node knows that a certain percentage or amount of data received from the same UE DRB needs to be transmitted through path 1, and/or, a certain percentage Or the amount of data needs to be transmitted through path 2. Exemplarily, the Donor CU may carry the offload ratio indication information in an RRC message and send it to the MT accessing the IAB node, or carry it in an F1AP message and send it to the DU accessing the IAB node. In another optional design, the Donor CU can also determine the mapping relationship between the GTP tunnel and the path, but the data distribution ratio is determined by the access IAB node 1, that is, the access IAB node 1 receives from the same UE DRB After PDCP PDU, a certain percentage of the data volume of the network coded packet obtained after network coding is transmitted through path 1, and/or a certain percentage of data volume is transmitted through path 2. In addition, the access IAB node can also adjust the proportion of coded data packets sent on different paths according to the data sent on different paths. I won't repeat them here.

In combination with the IAB system shown in Figure 16, in an optional design, in order to allow the access IAB node 1 to perform network coding on the uplink data to be sent, the Donor CU can send some network coding-related configurations to the access IAB node information. Exemplarily, the configuration information control information related to the network coding may be carried in an RRC message or an F1AP message and sent to the access IAB node. The configuration information related to the network coding may include one or more of the following configurations:

The type of network coding, for example: Raptor Q code, or RLNC code, etc.

The number of source data blocks into which the data block for network coding is divided, for example: the number of blocks contained in the Object, or the length of each block.

In conjunction with the IAB system shown in Figure 16, regarding the activation of the network coding function, in an optional design, as long as the access IAB node receives the network coding-related configuration information sent by the Donor CU, it defaults to the uplink network coding function Activated. In another optional method for activating the network coding function, the Donor CU can send an activation indication message to the access IAB node to indicate that the uplink network coding function needs to be activated. Exemplarily, the activation indication information is used to indicate that the access IAB node needs to perform network coding on the uplink data to be sent. Exemplarily, the activation indication information may be carried in an RRC message or F1AP message sent by the Donor CU to the access IAB node. It is understandable that the network coding function for uplink transmission and downlink transmission can be activated using one activation indication message, or two activation indication messages can be used separately, for example, when one activation indication message is used to activate the network coding function , When the access IAB node receives the activation indication information from the Donor CU, it will consider that the network coding functions for both uplink transmission and downlink transmission are activated by default; when two activation indications are used to activate the network coding function, One activation indication information is used to activate the network coding function of uplink transmission, and the other activation indication information is used to activate the network coding function of downlink transmission. An exemplary implementation includes using a bit, when the value of the bit is 1. When the value is 0, it means the network coding function of the uplink transmission is activated. When the bit value is 0, it means the network coding function of the downlink transmission is activated. Of course, it is understandable that the value here is not limited, for example, when the bit When the value is 0, it means that the network coding function for uplink transmission is activated. When the bit is 1, it means that the network coding function for downlink transmission is activated.

In an optional design, in the embodiment of the present application, the configuration information related to network coding used for uplink transmission and the configuration information related to network coding used for downlink transmission may be a set of information, that is, uplink transmission and downlink transmission adopt The same network coding configuration information, it can be understood that, in the embodiment of this application, the configuration information related to the network coding used in the uplink transmission direction and the configuration information related to the network coding used in the downlink transmission direction can also be two independent sets of each other. Configuration information, that is, different network coding configurations are used for uplink transmission and downlink transmission.

The above embodiments of the present application mainly solve the problem of reduced reliability of data transmission when a link is blocked in the scenario of multi-path transmission in the IAB system, and at the same time, it also avoids the modification of the existing UE. A good way to achieve good results. The embodiment of this application introduces the network coding function on the access IAB node and the Donor DU respectively, and utilizes the characteristics of network coding (that is, no matter which link it is from, it can be decoded correctly as long as enough coded data packets are received) , Thereby improving the reliability of data transmission in the IAB scenario and reducing the time delay of data transmission.

The second embodiment mainly corresponds to the aforementioned application 2: the execution of the network coding function on the UE and the Donor CU respectively is described in detail.

Another embodiment of this application is shown in Figure 17. Figure 17 is a schematic diagram of the IAB system introducing the network coding function, showing UE, IAB node 1, IAB node 2, IAB node 3, Donor DU, Donor CU and other network elements, where There are two transmission paths between IAB node 1 and Donor DU. Among them, transmission path 1 includes nodes: IAB node 1, IAB node 2 and Donor DU, and transmission path 2 includes: IAB node 1, IAB node 3 and Donor DU. . For the description of each network element shown in FIG. 17 and the specific protocol layers contained therein, reference may be made to the foregoing embodiment, such as the description of the embodiment shown in FIG. 10, which will not be repeated here. Unlike the embodiment shown in FIG. 10, in the IAB system shown in FIG. 17, the network coding function is executed on the UE and the Donor CU respectively. Exemplarily, the network coding function can be in the existing PDCP layer Realize (for example, expand the function of the existing PDCP layer), or, as shown in FIG. 17, introduce a new protocol layer between the PDCP layer and the GTP layer (for example, introduce a new RLNC protocol layer). With reference to the IAB system described in FIG. 17, the network coding can be implemented per UE bearer, that is, the data of different bearers of the same UE can be independently network coded.

In an optional design, the network coding function can also be implemented in the GTP layer or the protocol layers below the GTP layer (for example: the existing UDP layer or the IP layer or a new protocol layer), that is: the following line transmission as an example Donor CU maps a PDCP PDU of the UE to the corresponding GTP tunnel to obtain a GTP tunnel packet. Donor CU can perform network coding operations on one or more GTP tunnel packets to obtain the network coded data packet and encapsulate it in an IP packet and send it to Donor DU, the Donor DU sends the received IP packets to the access IAB node through different paths. Correspondingly, the access IAB node decodes the IP packets received from different paths to obtain the GTP tunnel packet, and sends it to the GTP layer for processing to obtain the PDCP PDU of the UE, and further sends the obtained PDCP PDU to the UE. .

With reference to Figure 17, for example, in this embodiment, the network coding function is implemented in the existing PDCP layer, or the implementation in a new protocol layer between the PDCP layer and the GTP layer is taken as an example for description. For downlink transmission In the direction, the system processing flow after the introduction of the network coding function includes:

After the Donor CU performs network encoding on one or more PDCP PDUs belonging to the UE, it maps the encoded data packet to the corresponding GTP tunnel to generate an IP packet, and sends the IP packet to the Donor DU. The Donor DU can be based on the received IP The DSCP/flow label value carried in the header field maps the received IP packets to different paths and sends them to IAB node 1. For example, transmission path 1 transmits through IAB node 2, transmission path 2 transmits through IAB node 3, and IAB node 1 The IP packets received from different paths are sent to the GTP-U layer for processing, and then the encoded data packets are obtained, and the encoded data packets are sent to the UE. The UE decodes the received encoded data packet and recovers the PDCP PDU of the UE, which is then handed over to the PDCP layer for processing (for example, sorting and/or duplicate packet detection).

After introducing the network coding function, the IAB system can make offloading decisions on different transmission paths in the downstream direction. Illustratively, in an optional design, the Donor CU determines the downstream offloading of the Donor DU. For example, the Donor CU determines the Which IP packets of the bearer of the same UE are sent through transmission path 1, and which IP packets are sent through transmission path 2. For example, Donor CU can add different IP headers of one or more IP packets belonging to the bearer of the same UE To achieve the DSCP/flow label. According to the mapping relationship between different DSCP/flow label values and different paths configured by the Donor CU, the Donor DU maps the IP packets with different DSCP/flow label values received from the Donor CU to the corresponding paths for transmission.

In combination with the system shown in Figure 17, in an optional design, in order to help the Donor CU to make offloading decisions, the Donor CU needs to know the transmission status of IP packets on different paths. For example, it can be accessed through an IAB node (IAB Node 1) implements the per UE bearer DDDS feedback sent to the Donor CU, where the content carried in the existing DDDS message needs to be extended, and one or more of the following information is additionally added:

-Path information, for example: Path ID, or Routing ID. Among them, the Routing ID includes Path ID and BAP address (the BAP address of the routing target, for example: the BAP address of the access IAB node).

-The received data rate data rate.

-The amount of data received.

-The size of the receiving buffer.

Among them, the received data rate, the amount of received data, and the size of the received buffer all correspond to the path information one-to-one. That is, the DDDS message carries the received data rate or the amount of received data or the size of the received buffer on a certain transmission path.

In an optional design, if the Donor CU adopts the CP-UP separation architecture, the GTP tunnels (GTP-U1 and/or GTP-U2) of the per UE bearer are established at the access IAB node (IAB node 1 in Figure 17). DU part) and Donor CU-UP. In this case, Donor CU-CP needs to send to Donor CU-UP an offload ratio indication information for multipath transmission. The offload ratio indication information can be combined with the GTP tunnel identifier. Correspondingly, or, the offload ratio indication information may correspond to the path information, where the path information may be Path ID or Routing ID, which is used to indicate the percentage of the same UE bearer that Donor CU-UP needs to share The data volume is diverted to GTP-U1 for transmission, and/or what percentage of the data volume is diverted to GTP-U2 for transmission. Alternatively, the offload ratio indication information can be used to indicate that the Donor CU-UP needs to mark what percentage of the IP packets in the same UE bearer with the DSCP1/flow label1 value, and/or what percentage of the IP packets need to be marked with DSCP2/flow label2 value.

For the deployment and activation of the network coding function of the IAB system shown in Figure 17, in order for the receiving end UE to correctly decode the received coded data packet, Donor CU needs to send some network coding-related configuration information to the UE. The configuration information related to network coding can be carried in an RRC message and sent to the UE. Among them, the configuration information related to network coding includes one or more of the following information:

-The type of network coding, for example: Raptor Q code, or RLNC code, etc.

-The size of the data block for network coding, for example: the size/length of the object.

-How many source data blocks are divided into the data block for network coding, for example: the number of blocks contained in the Object.

-The length of the characters contained in each source data block, for example: the length of the symbol.

In an optional design, once the UE receives the network coding-related control information sent by the Donor CU, the network coding function in the downlink direction is activated by default.

In another optional design, the Donor CU sends an activation indication message to the UE to indicate that the network coding function in the downlink direction is activated. For example, the activation indication information can be used to indicate that the UE needs to respond to the received downlink data. After the packet is decoded by the network, it is sent to the PDCP layer for processing. Exemplarily, the activation indication information may be carried in an RRC message and sent to the UE. The network coding functions for uplink and downlink can be activated by using one activation indication message, or can be activated by using two activation indication messages respectively.

Exemplarily, with reference to Figure 17, for the uplink transmission direction, the system processing flow after the introduction of the network coding function includes:

Similar to the downlink direction, after the UE performs network encoding on its PDCP PDU, it sends the encoded data packet to the access IAB node (IAB node 1 in Figure 17), and IAB node 1 maps the received encoded data packet to the corresponding GTP After the tunnel, IP packets are generated, and the IP packets are mapped to different paths and sent to the Donor DU, and the Donor DU sends the IP packets received on the different paths to the Donor CU. Donor CU sends the received IP packet to the GTP-U layer for processing and then obtains the encoded data packet, decodes the obtained encoded data packet, and recovers the PDCP PDU of the UE, and then sends the PDCP PDU to the PDCP layer To process.

Exemplarily, in conjunction with the IAB system shown in FIG. 17, for the offloading decisions of different transmission paths in the upstream transmission direction, the Donor CU may decide to access the upstream offloading of the IAB node (IAB node 1 in FIG. 17), namely: Donor CU Decide which IP packets belonging to the same UE bearer are sent through transmission path 1, and which IP packets are sent through transmission path 2. Among them, in an optional design, the Donor CU is the same UE bearer that establishes two GTP tunnels GTP-U1 and GTP-U2 between the access IAB node (the DU part of IAB node 1) and the Donor CU. The GTP tunnel corresponds to the same UE DRB between the UE and the IAB node 1. Donor CU can also configure the mapping relationship between these two different GTP tunnels and different paths for accessing IAB nodes, for example: map GTP-U 1 to path 1, perform uplink transmission through IAB node 2, and/or GTP-U 2 is mapped to transmission path 2, and is transmitted through IAB node 3.

In an optional design, in order to help the access IAB node perform the offload decision of the Donor CU, the Donor CU sends an indication message to the access IAB node (IAB node 1 in Figure 17) to indicate the offload ratio on different paths. So that the access IAB node knows what percentage of the data volume received from the same UE DRB needs to be diverted to GTP-U1 for transmission, and/or what percentage of the data volume needs to be diverted to GTP-U 2 for transmission . For example: the indication information is used to indicate that 70% of the data volume is diverted to GTP-U 1 for transmission, and/or 30% of the data volume is diverted to GTP-U 2 for transmission; exemplarily, the data volume refers to The amount of data after encoding. Optionally, the offload ratio indication information can correspond to the GTP tunnel identifier, that is, the Donor CU is configured to the access IAB node during the GTP tunnel establishment process, or the Donor CU is based on the chain of the transmission path after the GTP tunnel is established. When the path condition is configured and adjusted, it is configured to the access IAB node; or, the offload ratio indication information may correspond to path information, where the path information may be Path ID or Routing ID. Exemplarily, the Donor CU may carry the offload ratio indication information in an RRC message and send it to the MT accessing the IAB node, or carry it in an F1AP message and send it to the DU accessing the IAB node.

In an optional design, the Donor CU determines the mapping relationship between the GTP tunnel and the path, but the data distribution ratio is determined by the access IAB node itself, that is, after the access IAB node receives the encoded data packet from the same UE DRB, The access IAB node decides on its own what percentage of the data volume is diverted to GTP-U 1 for transmission, and/or what percentage of data volume is diverted to GTP-U 2 for transmission. Optionally, the access IAB node can also adjust the transmission ratio of encoded data packets on different paths by itself according to the conditions of sending data on different paths.

In combination with the IAB system shown in Figure 17, in another optional design, the Donor CU can be the same UE’s bearer when accessing the IAB node (the DU part of IAB node 1 in Figure 17) and the Donor CU. A GTP tunnel GTP-U 1 is established. This GTP tunnel corresponds to the UE DRB between the UE and the IAB node 1 in a one-to-one correspondence. Optionally, the Donor CU can also configure the mapping relationship between this GTP tunnel and different paths for the access IAB node. For example, the GTP-U 1 can be mapped to the transmission path 1, and transmitted through the IAB node 2, and/or, The GTP-U 1 can be mapped to the transmission path 2 and transmitted through the IAB node 3.

Exemplarily, in order to help the access IAB node to perform the offload decision of the Donor CU, the Donor CU may also send indication information to the access IAB node for indicating the offload ratio on different transmission paths, so that the access IAB node can learn from the same UE DRB What percentage of the received data volume needs to be transmitted through transmission path 1, and/or, what percentage of the data volume needs to be transmitted through transmission path 2. For example: the indication information is used to indicate that 70% of the data volume is transmitted through the transmission path 1, and/or 30% of the data volume is transmitted through the path 2. Optionally, the indication information corresponds to path information, where the path information may be Path ID or Routing ID. Exemplarily, the Donor CU may carry the indication information in the RRC message and send it to the MT part that accesses the IAB node, or the Donor CU may carry the indication information in the F1AP message and send it to the DU part that accesses the IAB node.

In an optional design, the Donor CU determines the mapping relationship between the GTP tunnel and the path, but the data distribution ratio is determined by the access IAB node itself, that is, the access IAB node receives data from the same UE DRB and performs the encoding operation to generate After encoding the data packet, determine by itself what percentage of the data volume is transmitted through path 1, and/or, what percentage of the data volume is transmitted through path 2. Optionally, the access IAB node can also adjust the transmission ratio of encoded data packets on different paths by itself according to the conditions of sending data on different paths.

In conjunction with the IAB system shown in Figure 17, in the design of the deployment and activation of the network coding function in the IAB system, for example, in order for the sending end UE to perform network coding on the uplink data to be sent, Donor CU sends the network to the UE Encoding-related configuration information. The configuration information related to the network coding may include one or more of the following:

-The type of network coding, for example: Raptor Q code, or RLNC code, etc.

-The size of the data block for network coding, for example: the length of the object, in bytes.

-How many source data blocks are the data block for performing network coding divided into, for example: the number of blocks contained in the object, or the length of the block.

-The length of the characters contained in each source data block, for example: the length of the symbol, or the number of symbols contained in each block.

Exemplarily, the Donor CU may carry the foregoing network coding-related configuration information in an RRC message and send it to the UE.

In an optional design, once the UE receives the network coding-related configuration information sent by the donor CU, the function of the UL network coding is activated by default. In another optional design, the Donor CU may send indication information for activating the network coding function to the UE, which is used to indicate that the network coding function for the uplink transmission direction is activated. Specifically, the activation indication for the uplink transmission The information may instruct the UE to perform network coding on the uplink data to be sent, and the activation indication information may be carried in an RRC message and sent to the UE. The network coding function for uplink transmission and downlink transmission can be activated by using the same activation indication information, or can be activated by using two activation indication information respectively.

It is worth noting that the configuration information related to network coding used for uplink transmission and the configuration information related to network coding used for downlink transmission can be a set of information, that is, the same network coding configuration information is used for uplink transmission and downlink transmission, which is understandable However, in the embodiment of this application, the configuration information related to network coding used in the uplink transmission direction and the configuration information related to network coding used in the downlink transmission direction may also be two independent sets of configuration information, namely, uplink transmission and downlink transmission. Use different network coding configurations respectively.

From the above, in conjunction with the embodiment of the present application shown in FIG. 17, an improvement over the prior art is that the embodiment of the present application introduces the network coding function in the L2 protocol on the RAN side, which solves the problem of IAB In the case of multiple connections in the system, the reliability of data transmission is reduced due to the blockage of one link. , That is, by introducing network coding functions on the UE and Donor CU respectively, and using the characteristics of network coding (no matter which link, as long as enough coded data packets are received, it can be decoded correctly), thereby improving the performance in the IAB scenario. The reliability of data transmission reduces the time delay of data transmission.

It is worth noting that the solution of the second embodiment is also applicable to cross-donor DU scenarios. For example, for cross-donor DU scenarios, UE, IAB node 1 (access to IAB node), IAB node 2, IAB node 3. Network elements such as IAB Donor DU1, IAB Donor DU2, and IAB Donor CU form an IAB communication system with two transmission links. Among them, transmission path 1 includes: UE-IAB node 1-IAB node 2-IAB Donor DU1-IAB Donor CU, transmission path 2 includes: UE-IAB node 1-IAB node 3-IAB Donor DU2-IAB Donor CU, and network coding functions are implemented on UE and IAB Donor CU respectively. For the network coding operation mechanism and process applicable to the cross-DonorDU scenario, please refer to the description of the second embodiment, which will not be repeated here.

The third embodiment mainly corresponds to the aforementioned application 3: the execution of the network coding function on the access IAB node and the Donor CU respectively is described in detail.

Another embodiment of this application is shown in Figure 18. Figure 18 is a schematic diagram of an IAB system introducing network coding functions, showing UE, IAB node 1, IAB node 2, IAB node 3, Donor DU, Donor CU and other network elements Among them, there are two transmission paths between IAB node 1 and Donor DU. Among them, transmission path 1 includes nodes: IAB node 1, IAB node 2 and Donor DU, and transmission path 2 includes: IAB node 1, IAB node 3 and Donor DU. For the description of the network elements shown in FIG. 18 and the specific protocol layers contained therein, reference may be made to the foregoing embodiments, such as the description of the embodiments shown in FIG. 10 and FIG. 17, which will not be repeated here.

The embodiment shown in FIG. 10 and FIG. 17 is different. In the IAB system shown in FIG. 18, the network coding function is performed on the access IAB node and the Donor CU respectively, that is, for downlink transmission , The access IAB node sends the IP packets received on different paths to the GTP-U layer for processing and obtains the encoded data packet, decodes the encoded data packet, and restores the PDCP PDU of the UE, and then restores it. The PDCP PDU is sent to the UE and handed over to the PDCP layer of the UE for processing (for example, performing operations such as sorting and/or repeated packet detection). That is to say, in the embodiment shown in FIG. 17, the UE and the access IAB node (the DU part of IAB node 1 in FIG. 17) are transmitted with coded data packets, and the coded data packets are decoded by the UE and restored. Out PDCP PDU. However, in the embodiment shown in FIG. 18, the access IAB node decodes the encoded data packet and recovers the PDCP PDU of the UE, which is then sent to the UE through the interface between the UE and the access IAB node.

This embodiment can follow the solution described in the embodiment shown in FIG. 18, but one difference is that in the embodiment shown in FIG. 17, Donor CU sends all configuration information related to network coding. To the UE, but in this embodiment, the information needs to be sent to the access IAB node, that is, the Donor CU configures the information related to the network coding of the per UE bearer for the access IAB node.

It is worth noting that the solution of the third embodiment is also applicable to the cross-donor DU scenario. For example, for the cross-donor DU scenario, UE, IAB node 1 (access to IAB node), IAB node 2, IAB node 3. Network elements such as IAB Donor DU1, IAB Donor DU2, and IAB Donor CU form an IAB communication system with two transmission links. Among them, transmission path 1 includes: UE-IAB node 1-IAB node 2-IAB Donor DU1-IAB Donor CU, transmission path 2 includes: UE-IAB node 1-IAB node 3-IAB Donor DU2-IAB Donor CU, and the function of network coding is implemented on the access IAB node and IAB Donor CU respectively. Exemplarily, for the network coding operation mechanism and process applicable to the cross-DonorDU scenario, please refer to the description of the third embodiment, which will not be repeated here.

From the above, combined with the embodiment shown in FIG. 18, compared with the prior art, the application of network coding is mainly at the application layer, and there is no application at the RAN side. This embodiment introduces the network in the L2 protocol on the RAN side. The coding function mainly solves the problem of reducing the reliability of data transmission when one link is blocked in the IAB multi-connection scenario, while avoiding changes to the UE, that is, by introducing network coding on the access IAB node and Donor CU respectively The function uses the characteristics of network coding (no matter which link it is from, as long as enough coded data packets are received, it can be decoded correctly), thereby improving the reliability of data transmission in the IAB scenario and reducing the delay of data transmission.

The foregoing embodiments of this application mainly take a two-hop backhaul link as an example for description. Similarly, all the solutions in the embodiments of this application are also applicable to the scenario of a multi-hop backhaul link, that is, access between the IAB node and the Donor DU. There can be at least 2 IAB nodes on each path (except for the access IAB nodes).

Example four

Fig. 19 is a schematic diagram of an IAB system provided by another embodiment of the application. As shown in Fig. 19, in an IAB network, an IAB node can be connected to at least one parent node (for example, IAB node 3 in Fig. 19), and then pass through the parent node. The node is connected to the IAB host. If the IAB host is considered as a separate architecture for the centralized unit (CU, Centralized Unit) and the distributed unit (DU, Distributed Unit), the IAB host (IAB Donor) can include the IAB host CU (Donor CU) and the IAB host DU (Donor) DU) part. Optionally, the IAB host CU may also be in a form in which the control plane (CP, control plane) and the user plane (UP, user plane) are separated, so that the IAB host CU includes the IAB host CU-CP and the IAB host CU-UP. Since the IAB node also supports multiple connections on the backhaul link, the IAB node may connect to one or more IAB host DUs, and then connect to the IAB host CU via one or more IAB host DUs. The IAB node in the embodiment of the present application may be directly connected to the IAB host DU, or connected to the IAB host DU through one or more intermediate IAB nodes. For example, in FIG. 19, the IAB node 3 is connected to the IAB host DU1 via the intermediate IAB node 2, and is connected to the IAB host DU2 via the intermediate IAB node 1. For another example, the IAB node 1 in FIG. 19 is directly connected to the IAB host DU2. The wireless link between the IAB nodes may be a wireless backhaul link based on the NR standard. The interface between the IAB host CU-CP and the CU-UP can be called the E1 interface, the interface between the IAB host DU and the IAB host CU can be called the F1 interface, where the IAB host DU and the IAB host CU-CP The interface can be called the F1 control plane (F1-C) interface, and the interface between the IAB host DU and the IAB host CU-UP can be called the F1 user plane (F1-U) interface.

In an optional design, the DU part of the IAB node needs to obtain the IP address first, and then use its own IP address to communicate with the IAB host CU or other network elements (such as the OAM server of the IAB node, the security gateway SeGW (security gateway), etc. ) Communication, where the IAB host CU may also specifically include IAB host CU-CP, IAB host CU-UP), because the IP layer-based communication between the IAB node and the IAB host CU or the other network elements needs to be connected to the IAB The host DU transmits IP data packets, so the IP address obtained by the IAB node needs to have a corresponding relationship with the IAB host DU it is connected to. The corresponding relationship may mean that the IP address of the IAB node and the IP address of the IAB host DU are in the same network segment, or The IP address of the IAB node is the same as the network prefix part of the IP address of the IAB host DU, or the IP address of the IAB node is allocated by the IAB host DU (for example, the IP address of the IAB node is obtained by the IAB host DU from the address server and allocated , Or the IP address of the IAB node is allocated by the IAB host DU from the IP address resource pool maintained by it), so that it can ensure that the IAB node needs to receive IP layer data packets from the IAB host CU or the other network elements , These IP layer data packets will be forwarded to the IAB host DU that the IAB node is connected to, and then transmitted to the IAB node via the IAB host DU. Correspondingly, if an IAB node wants to transmit an IP layer data packet via an IAB host DU it is connected to, if the source IP address it selects is not an IP address corresponding to the IAB host DU, and the intermediate node forwarded by the IP layer ( Including IAB donor DU) is configured with certain source IP address filtering rules (for example, only the data packets with the source IP address of the specified network segment can be forwarded, and the others will be discarded), then these IP layer data packets may not pass at the IP layer The source IP address filtering rules configured by the forwarding intermediate nodes (including IAB donor DU) cause data packets to be discarded at these intermediate nodes. In order to avoid this problem, the following solutions are considered in the embodiments of this application:

In an optional design, the IAB host CU provides the IAB node with a mapping rule for source IP address selection. The mapping rule is used to specify a mapping relationship between an IAB node's own IP address and any one or more of the following : The designated BAP layer address; the designated BAP routing ID (BAP routing ID); or, the general packet radio service tunneling protocol (general packet radio service tunneling) of the F1 interface user plane data packet between the IAB node and the IAB host CU protocol, GTP for short) tunnel information; or, the F1 interface control plane (F1-C) data packet type information between the IAB node and the IAB host CU; or the non-F1 interface (non-F1 interface) transmitted between the IAB node and the IAB host CU -F1) Type information of the data packet.

Exemplarily, the designated BAP address (BAP address) is a target node of uplink transmission, that is, an IAB host node (specifically, it may be, for example, an IAB host CU or an IAB host DU). The designated route identifier of the BAP layer is used to identify the transmission path from the IAB node to a designated IAB host DU. Optionally, the designated BAP layer routing identifier includes the BAP layer address of the IAB host node and the transmission path identifier (BAP path ID) to the IAB host node. Further optionally, the BAP layer address of the IAB node is used to identify the designated IAB host DU. The GTP tunnel protocol tunnel information on the user plane of the F1 interface between the IAB node and the IAB host CU may be GTP TEID+IP address. Exemplarily, GTP TEID refers to the tunnel endpoint identifier (tunnel endpoint identifier, TEID for short) of the GTP tunnel allocated by the IAB host CU (specifically, the IAB host CU-UP) for the data radio bearer (DRB) of the terminal device served by the IAB node ), the IP address is the IP address of the IAB host CU (specifically, it may be the IAB host CU-UP). The type information of the F1 interface control plane data packet between the IAB node and the IAB host CU may specifically be a UE-associated F1AP message type or a UE-independent (UE-associated) F1AP message type.

Optionally, the IAB host CU may use a control plane message (for example, an F1AP message or an RRC message) to send the mapping rule for source IP address selection to the IAB node. Based on this mapping rule, when the IAB node needs to send an uplink data packet, it can select the appropriate source IP address according to the BAP layer routing identifier to be added to the uplink data packet; or, if the uplink data packet is F1 interface control plane data Packet, you can select the appropriate source IP address according to whether the uplink data packet belongs to the UE-related F1AP message type or the UE-independent F1AP message type, or the uplink data packet is a data packet on the F1 interface user plane, then you can Select the appropriate source IP address according to the GTP tunnel information in the upstream data packet; or, if the upstream data packet is a data packet with a non-F1 interface type, you can select the IP address corresponding to the non-F1 interface type in the mapping rule as Source IP address. The appropriate IP address selected by the mapping rule is the IP address corresponding to the designated IAB host DU. The IAB node uses this IP address as the source IP address to send uplink data packets, which can avoid data packets being forwarded at the IP layer. The node was discarded because the source IP address filtering criteria did not meet the problem.

Based on the solution of the fourth embodiment of the present application, when an access IAB node transmits an uplink data packet, it can select an appropriate source IP address for the uplink data packet to send the uplink data packet according to the mapping rule selected by the source IP address it obtains , To avoid the problem of data packets being discarded because the source IP address filtering criteria are not met in the nodes forwarded by the IP layer.

The foregoing describes in detail the system-side or method-side embodiments provided by the embodiments of the present application with reference to FIGS. 1 to 19, and the following describes the device embodiments of the present application with reference to FIGS. 20 and 21. It should be understood that the description of the method embodiment and the description of the device embodiment correspond to each other, and therefore, the parts that are not described in detail may refer to the previous method embodiment.

As shown in FIG. 20, it is a schematic structural diagram of a communication device 2000 provided by an embodiment of this application. The apparatus 2000 can correspond to the UE described in the foregoing method embodiment, and access an IAB node (such as the IAB node 1 or the DU part of the IAB node 1 or the MT part of the IAB node 1), IAB Donor, Donor DU, or Donor CU. Or, it can also be applied to the aforementioned UE to access the IAB node (such as IAB node 1 or the DU part of IAB node 1 or the MT part of IAB node 1), IAB Donor, Donor DU, or Donor CU chip or hardware components .

Each module or unit in the device 2000 can be used to execute the UE in the above system or method embodiment, and access the IAB node (IAB node 1 or the DU part of IAB node 1 or the MT part of IAB node 1), IAB Donor, Donor DU, or each operation or processing performed by Donor CU. For example, the device 2000 includes a transceiver unit 2010 and a processing unit 2020. The processing unit 2020 is used to execute the UE in the above method side embodiment and access the IAB node (IAB node 1 or the DU part of IAB node 1 or the MT part of IAB node 1 ), IAB Donor, Donor DU, or Donor CU respectively perform operations or processing procedures. The transceiver unit 2010 is used to perform the necessary specific information transceiver and interaction under the driving of the processing unit 2020, so as to achieve the implementation of the aforementioned system or method side The corresponding technical effects described in the example. The device 2000 may also include a necessary storage unit to store computer programs or instructions required to implement the foregoing method-side embodiments. It should be understood that the processing unit 2020 may be implemented by one or more processors, or by a chip system. The transceiver unit 2010 may be implemented by a transceiver, an input/output interface, or an interface circuit. The storage unit may be a memory.

As shown in FIG. 21, another type of communication device 2100 provided by an embodiment of the present application may include at least one processor 2110, and may also include a transceiver 2130. The transceiver 2130 may be an interface circuit or an input/output circuit. The device 2100 may further include a memory 2120. When the device 2100 does not include the memory 2120, the memory 2120 is an external memory. The aforementioned processor 2110, transceiver 2130, and memory 2120 may be coupled through a communication line. The device 2100 can correspond to the UE described in the foregoing system or method embodiment, and access an IAB node (such as IAB node 1 or the DU part of IAB node 1 or the MT part of IAB node 1), IAB node, IAB Donor, Donor DU, Or Donor CU. Or, it can also be applied to UE, access to IAB node (such as IAB node 1 or the DU part of IAB node 1 or the MT part of IAB node 1), IAB node, IAB Donor, Donor DU, or Donor CU chip or Hardware components.

In the communication device 2100, the memory 2120 stores computer instructions, and the at least one processor 2110 executes the computer instructions, so that the device 2100 implements the UE in the above system or method side embodiment and accesses an IAB node (such as an IAB node). 1 or the DU part of the IAB node 1 or the MT part of the IAB node 1), the operation or processing performed by the IAB node, IAB Donor, Donor DU, or Donor CU, respectively.

It should also be understood that the division of the units in the above device is only a division of logical functions, and may be fully or partially integrated into one physical entity in actual implementation, or may be physically separated. In addition, the units in the device can be all implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; part of the units can also be implemented in the form of software called by the processing elements, and some of the units can be implemented in the form of hardware. For example, each unit can be a separate processing element, or it can be integrated in a certain chip of the device for implementation. In addition, it can also be stored in the memory in the form of a program, which is called and executed by a certain processing element of the device. Function. Here, the processing element may also be called a processor, and may be an integrated circuit with signal processing capability. In the implementation process, each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in a processor element or implemented in a form of being called by software through a processing element.

In an example, the unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, for example: one or more application specific integrated circuits (ASIC), or, one or Multiple digital signal processors (digital signal processors, DSP), or, one or more field programmable gate arrays (FPGA), or a combination of at least two of these integrated circuits. For another example, when the unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processors that can call programs. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).

It should be understood that, in this embodiment of the application, the processor may be a central processing unit (CPU), and the processor may also be other general-purpose processors, DSPs, ASICs, FPGAs or other programmable logic devices, discrete gates, or Transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.

The above-mentioned embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented by software, the above-mentioned embodiments may be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on the computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.

The computer instruction may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instruction may be transmitted from a website, computer, server, or data center through a cable (For example, infrared, wireless, microwave, etc.) to transmit to another website, computer, server or data center. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that includes one or more sets of available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium. The semiconductor medium may be a solid state drive.

In another implementation, in the above method-side embodiment, the UE accesses an IAB node (such as IAB node 1 or the DU part of IAB node 1 or the MT part of IAB node 1), IAB node, IAB Donor, Donor DU, or The unit of Donor CU that implements each step in the above method embodiments may be configured as one or more processing elements. These processing elements are set on the baseband device of the network equipment. The processing elements here may be integrated circuits, for example: one or more One ASIC, or, one or more DSPs, or, one or more FPGAs, one or more general-purpose application processors, or a combination of these types of integrated circuits. These integrated circuits can be integrated together to form a chip.

In the above-mentioned network elements, the units that implement the steps in the above methods can be integrated together and implemented in the form of a system-on-chip. For example, the baseband device includes the SOC chip for implementing the above methods.

The embodiment of the present application also provides a communication system. The communication system includes: the aforementioned UE, which accesses an IAB node (such as the IAB node 1 or the DU part of the IAB node 1 or the MT part of the IAB node 1), the IAB node, and the IAB One or more of Donor, Donor DU, or Donor CU.

The embodiment of the present application also provides a computer-readable medium for storing computer program code, and the computer program includes instructions for executing the method provided by the embodiment of the present application. The readable medium may be a read-only memory (ROM) or a random access memory (RAM), which is not limited in the embodiment of the present application.

This application also provides a computer program product. The computer program product includes instructions. When the instructions are executed, the UE in the foregoing embodiment is executed to access an IAB node (such as IAB node 1 or the DU part of IAB node 1). Or the MT part of IAB node 1), IAB Donor, Donor DU, or Donor CU respectively corresponding operations.

An embodiment of the present application also provides a system chip, which includes a processing unit and a communication unit. The processing unit may be, for example, a processor, and the communication unit may be, for example, an input/output interface, a pin, or a circuit. The processing unit can execute computer instructions, so that the chip in the communication device executes any of the methods provided in the foregoing embodiments of the present application.

Optionally, any communication device provided in the foregoing embodiments of the present application may include the system chip.

Optionally, the computer instructions are stored in a storage unit.

Optionally, the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit can also be a storage unit in the terminal located outside the chip, such as a ROM or other storage units that can store static information and instructions. Types of static storage devices, RAM, etc. Wherein, the processor mentioned in any one of the foregoing may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits used to control the execution of the programs of the foregoing communication method. The processing unit and the storage unit can be decoupled, respectively set on different physical devices, and connected in a wired or wireless manner to realize the respective functions of the processing unit and the storage unit, so as to support the system chip to implement the above-mentioned embodiments Various functions in. Alternatively, the processing unit and the memory may also be coupled to the same device.

It can be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of random access memory (RAM) are available, such as static random access memory (static RAM, SRAM), dynamic random access memory (DRAM), and synchronous dynamic random access memory (DRAM). Access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory Take memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).

The terms "system" and "network" in this article are often used interchangeably in this article. The term "and/or" in this article is only an association relationship describing the associated objects, which means that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, exist alone B these three situations. In addition, the character "/" in this text generally indicates that the associated objects before and after are in an "or" relationship.

The terms "uplink" and "downlink" appearing in this application are used to describe the direction of data/information transmission in a specific scenario. For example, the "uplink" direction generally refers to the direction or distribution of data/information from the terminal to the network side. The direction of transmission from the centralized unit to the centralized unit. The "downlink" direction generally refers to the direction in which data/information is transmitted from the network side to the terminal, or the direction in which the centralized unit transmits to the distributed unit. It can be understood that "uplink" and "downlink" "It is only used to describe the direction of data/information transmission, and the specific start and end equipment of the data/information transmission is not limited.

Various messages/information/equipment/network elements/systems/devices/actions/operations/processes/concepts and other objects that may appear in this application are given names. It is understandable that these specific names are not It constitutes a limitation on related objects. The assigned name can be changed according to factors such as the scene, context or usage habits. The understanding of the technical meaning of the technical terms in this application should mainly be based on the function embodied/performed in the technical solution And technical effects to determine.

A person of ordinary skill in the art may realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the unit is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The unit described as a separate component may or may not be physically separated, and the component displayed as a unit may or may not be a physical unit, that is, it may be located in one place, or may also be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

If this function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method in each embodiment of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), and random access.

The above are only specific implementations of this application, but the scope of protection of this application is not limited to this. Any person skilled in the art can easily conceive of changes or substitutions within the technical scope disclosed in this application, which shall cover Within the scope of protection of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims

A network coding method, the method is applied to the access backhaul integrated IAB network, the IAB network includes the IAB host node IAB Donor and the access IAB node, the IAB Donor includes the host distributed unit Donor DU and the host centralized Donor CU, the method includes:

The Donor DU performs a network encoding operation on the data from the user equipment of the Donor CU to generate an encoded data packet;

The Donor DU sends the encoded data packet to the access IAB node.
The network coding method according to claim 1, wherein the method further comprises:

The Donor DU receives first configuration information from the Donor CU, where the first configuration information includes any one or more of the following information:

Type of network coding;

The size of the data block for network coding;

The number of data blocks that perform network coding is divided into source data blocks; and,

The length of characters contained in each source data block.
The network coding method according to any one of claims 1-2, wherein the method further comprises:

The Donor DU receives first indication information from the Donor CU, where the first indication information is used to activate a network coding operation function of the Donor DU, so that the Donor DU can perform the network coding operation.
The network coding method according to any one of claims 1-3, wherein the method further comprises:

The Donor DU receives second indication information from the Donor CU, where the second indication information includes: the transmission ratio of the coded data packet on the transmission path 1, and/or, the coded data packet is on the transmission path 2 transmission ratio;

Wherein, the transmission path 1 includes nodes: the Donor DU, a first IAB node and the access IAB node, and the transmission path 2 includes nodes: the Donor DU, a second IAB node and the access IAB node.
The network coding method according to any one of claims 1-3, wherein the method further comprises:

The Donor DU determines the transmission ratio of the encoded data packet on the transmission path 1 and/or the transmission ratio of the encoded data packet on the transmission path 2 according to the transmission condition of the downlink transmission path;

Wherein, the transmission path 1 includes nodes: the Donor DU, a first IAB node and the access IAB node, and the transmission path 2 includes nodes: the Donor DU, a second IAB node and the access IAB node.
The network coding method according to claim 5, wherein the method further comprises:

The Donor DU receives the transmission status of the downlink transmission path sent by the Donor CU, and the transmission status of the downlink transmission path includes:

Any one or more of the following information of the transmission path 1: path information, transmission data rate, transmission data volume, and receiving buffer size; and/or,

Any one or more of the following information of the transmission path 2: path information, transmission data rate, transmission data volume, and receiving buffer size.
8. The network coding method according to any one of claims 4-6, wherein the method further comprises:

The Donor DU receives second configuration information from the Donor CU, where the second configuration information includes quality of service information and at least one path information, the quality of service information corresponds to at least one path information, and the at least one path The information includes: information of the transmission path 1 and/or information of the transmission path 2.
The network coding method according to claim 7, wherein the quality of service information includes: a differentiated service coding point DSCP, and/or a data flow label Flow Label; the path information includes: a path identifier Path ID, and /Or, Routing ID.
8. The network coding method according to any one of claims 1-8, wherein the network coding operation is performed before the Donor DU performs the BAP adding operation.
A network coding method, the method is applied to access and backhaul integrated IAB network, the IAB network includes an IAB host node IAB Donor, and the host node includes a host centralized unit Donor CU and a host distributed unit Donor DU, The method includes:

The Donor CU sends first configuration information to the Donor DU, where the first configuration information is used to configure the Donor DU to perform a network encoding operation on the data of the user equipment to generate an encoded data packet, and the encoded data packet It is sent to the access IAB node in the IAB network.
The network coding method according to claim 10, wherein the first configuration information includes any one or more of the following information:

Type of network coding;

The size of the data block for network coding;

The number of data blocks that perform network coding is divided into source data blocks; and,

The length of characters contained in each source data block.
The network coding method according to claim 10 or 11, wherein the method further comprises:

The Donor CU sends first indication information to the Donor DU, where the first indication information is used to activate the network coding operation function of the Donor DU, so that the Donor DU can perform the network coding operation.
The network coding method according to any one of claims 10-12, wherein the method further comprises:

The Donor CU sends second indication information to the Donor DU, where the second indication information includes the transmission ratio of the coded data packet on the transmission path 1, and/or, the transmission of the coded data packet on the transmission path 2 Proportion;

Wherein, the transmission path 1 includes nodes: the Donor DU, the first IAB node, and the access IAB node; the transmission path 2 includes nodes: the Donor DU, the second IAB node, and the access IAB node.
The network coding method according to any one of claims 10-12, wherein the method further comprises:

The Donor CU sends second configuration information to the Donor DU, where the second configuration information includes quality of service information and at least one path information, the quality of service information corresponds to the at least one path information, and the at least one path The information includes: information of transmission path 1 and/or information of transmission path 2.
The network coding method according to any one of claims 10-14, wherein the method further comprises:

The Donor CU receives downlink data transmission status DDDS information from the access IAB node, where the DDDS information includes path information and any one or more of the following information: transmission data rate, transmission data volume, and receiving buffer the size of.
The network coding method according to claim 14 or 15, wherein the quality of service information includes: a differentiated service code point DSCP, and/or a data flow label Flow Label; and the path information includes: Path ID , And/or, Routing ID.
The network coding method according to any one of claims 10-16, wherein the method further comprises:

The Donor CU sends the first configuration information to the access IAB node.
The network coding method according to any one of claims 10-17, wherein the method further comprises:

The Donor CU sends third indication information to the access IAB node, where the third indication information is used to activate the network coding operation function of the access IAB node, so that the access IAB node can respond to all received information. The network code packet is decoded.
A network coding method, said method is applied to access backhaul integrated IAB network, said IAB network includes access IAB node and IAB host node IAB Donor, said IAB Donor includes host distributed unit Donor DU and centralized Unit Donor CU, the method includes:

The access IAB node performs a network encoding operation on the data of the user equipment to generate an encoded data packet;

The access IAB node sends the encoded data packet to the Donor CU through the Donor DU.
The network coding method according to claim 19, wherein the method further comprises:

The access IAB node receives first configuration information from the Donor CU, where the first configuration information includes any one or more of the following information:

Type of network coding;

The size of the data block for network coding;

The number of data blocks that perform network coding is divided into source data blocks; and,

The length of characters contained in each source data block.
The network coding method according to any one of claims 19-20, wherein the method further comprises:

The access IAB node receives first indication information from the Donor CU, where the first indication information is used to activate the network coding operation function of the access IAB node, so that the access IAB node can perform all the operations. Describe the network coding operation.
22. The network coding method according to any one of claims 19-21, wherein the method further comprises:

The access IAB node receives second indication information from the Donor CU, where the second indication information includes: the transmission ratio of the coded data packet on the transmission path 1, and/or, the coded data packet is Transmission ratio of transmission path 2;

Wherein, the transmission path 1 includes nodes: the access IAB node, the first IAB node, and the Donor DU, and the transmission path 2 includes nodes: the access IAB node, the second IAB node, and the Donor DU.
22. The network coding method according to any one of claims 19-21, wherein the method further comprises:

The access IAB node determines the transmission ratio of the encoded data packet on the transmission path 1 and/or the transmission ratio of the encoded data packet on the transmission path 2 according to the transmission condition of the uplink transmission path;

Wherein, the transmission path 1 includes nodes: the access IAB node, the first IAB node, and the Donor DU, and the transmission path 2 includes nodes: the access IAB node, the second IAB node, and the Donor DU.
The network coding method of claim 23, wherein the method further comprises:

The access IAB node receives the transmission status of the uplink transmission path sent by the Donor CU, and the transmission status of the uplink transmission path includes:

Any one or more of the following information of the transmission path 1: path information, transmission data rate, transmission data volume, and receiving buffer size; and/or,

Any one or more of the following information of the transmission path 2: path information, transmission data rate, transmission data volume, and receiving buffer size.
The network coding method according to any one of claims 22-24, wherein the method further comprises:

The access IAB node receives second configuration information from the Donor CU, where the second configuration information includes General Packet Radio Service Tunneling Protocol (GTP) tunnel information and at least one path information, and the GTP tunnel information and at least Corresponding to one path information, the at least one path information includes: path information of the transmission path 1, and/or path information of the transmission path 2, and the GTP tunnel is established between the access IAB node and the Between donors and CUs, it corresponds to a bearer of the user equipment.
The network coding method according to claim 25, wherein the GTP tunnel information includes: IP address, and, GTP tunnel endpoint identification; the path information includes: Path ID, and/or, routing identification ID.
The network coding method according to any one of claims 19-26, wherein the network coding operation is performed before the access IAB node performs the BAP adding operation.
A network coding method, said method is applied to access backhaul integrated IAB network, said IAB network includes IAB host node IAB Donor and access IAB node, and said IAB Donor includes donor centralized unit Donor CU and host distribution Donor DU, the method includes:

The Donor CU sends first configuration information to the access IAB node, where the first configuration information is used by the access IAB node to perform network coding operations on user equipment data to generate coded data packets and send the The encoded data packet is sent to the Donor CU through the Donor DU.
The network coding method according to claim 28, wherein the first configuration information includes any one or more of the following information:

Type of network coding;

The size of the data block for network coding;

The number of data blocks that perform network coding is divided into source data blocks; and,

The length of characters contained in each source data block.
The network coding method according to claim 28 or 29, wherein the method further comprises:

The Donor CU sends first indication information to the access IAB node, where the first indication information is used to activate the network coding operation function of the access IAB node, so that the access IAB node can execute the network Encoding operation.
The network coding method according to any one of claims 28-30, wherein the method further comprises:

The Donor CU sends second indication information to the access IAB node, where the second indication information includes the transmission ratio of the encoded data packet on the transmission path 1, and/or, the encoded data packet is on the transmission path 2. Transmission ratio;

Wherein, the transmission path 1 includes nodes: the access IAB node, the first IAB node, and the Donor DU, and the transmission path 2 includes nodes: the access IAB node, the second IAB node, and the Donor DU.
The network coding method according to any one of claims 28-30, wherein the method further comprises:

The Donor CU sends uplink data transmission status information to the access IAB node, and the uplink data transmission status information includes:

Any one or more of the following information of transmission path 1: path information, transmission data rate, transmission data volume, and receiving buffer size; and/or,

Any one or more of the following information of transmission path 2: path information, transmission data rate, transmission data volume, and receiving buffer size;

Wherein, the transmission path 1 includes nodes: the access IAB node, the first IAB node, and the Donor DU, and the transmission path 2 includes nodes: the access IAB node, the second IAB node, and the Donor DU.
The network coding method according to claim 32, wherein the method further comprises:

The Donor CU receives the uplink data transmission status information sent from the Donor DU.
The network coding method according to any one of claims 28-33, wherein the method further comprises:

The Donor CU sends the first configuration information to the Donor DU.
The network coding method according to any one of claims 28-34, wherein the method further comprises:

The Donor CU sends third indication information to the Donor DU, where the third indication information is used to activate the network coding operation function of the Donor DU, so that the Donor DU can interpret the received network coding packet. Code operation.
A communication device applied to access to an integrated backhaul IAB network, characterized in that the device includes at least one processor, and the at least one processor is coupled with at least one memory;

The at least one processor is configured to execute a computer program or instruction stored in the at least one memory, so that the communication device executes the method according to any one of claims 1 to 9, or causes the communication The device executes the method according to any one of claims 10 to 18, or causes the communication device to execute the method according to any one of claims 19 to 27, or causes the communication device to execute the method according to claim 28 The method of any one of to 35.
A computer-readable storage medium, characterized in that a computer program or instruction is stored in the computer-readable storage medium, and when the computer program or instruction is executed, it executes as described in any one of claims 1 to 9 The method described above, or execute the method according to any one of claims 10 to 18, or execute the method according to any one of claims 19 to 27, or execute any one of claims 28 to 35 The method described.