A communication method and related device

Abstract

The embodiment of the application discloses a communication method and related equipment. In the scene where an IAB network is managed by multiple IAB host nodes, the BAP routing identifier of a data packet in a first network segment is replaced by a BAP routing identifier in a second network segment through a first IAB node, so that the data packet is normally transmitted in the second network segment, and the problem of abnormal data packet transmission caused by the fact that the IAB network is managed by multiple IAB host nodes is reduced. It can be guaranteed that the data packet is normally transmitted in the IAB network which is spliced by multiple network segments managed by different host nodes.

Description

[0001] This application claims priority to Chinese Patent Application No. 202110057037.8, filed on January 15, 2021, entitled "A Communication Method and Related Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to a communication method and related equipment. Background Technology

[0003] In the 3rd Generation Partnership Project (3GPP) Release 15 Integrated Access and Backhaul (IAB) network architecture, there are host nodes (IABdonors) and IAB nodes. Considering a central unit (CU) - distributed unit (DU) architecture, the IABdonor includes an IABdonorCU and an IABdonorDU. An IAB node can include two functional units: a mobile terminal (MT) and a DU. The MT is used for communication between the IAB node and its parent node, while the DU is used for communication between the IAB node and its child nodes.

[0004] Currently, each IAB node in the IAB network and its parent node are connected to the same host node. This host node manages the topology, routing, and quality of service (QoS) of the IAB network.

[0005] However, if the IAB network is managed by multiple host nodes, how to control the IAB nodes in the IAB network to ensure the normal transmission of data packets is an urgent problem to be solved. Summary of the Invention

[0006] This application provides a communication method and related equipment that enables data packets to be transmitted normally within multiple network segments in an IAB network scenario where multiple IAB host nodes manage multiple network segments.

[0007] The first aspect of this application provides a communication method, which can be executed by a first IAB node or by a component of the first IAB node (such as IAB-DU, IAB-MT, processor, chip, or chip system). This method is applied to an integrated access backhaul IAB network, which includes a first network segment and a second network segment. The first network segment is managed by a first host node, and the second network segment is managed by a second host node. The first and second host nodes are different. The method includes: the first IAB node receiving a first data packet in the first network segment, the first data packet including a first backhaul adaptation protocol (BAP) routing identifier, the first BAP routing identifier being used for transmission of the first data packet in the first network segment; the first IAB node obtaining a first correspondence; the first IAB node replacing the first BAP routing identifier in the first data packet with a second BAP routing identifier according to the first correspondence, obtaining a second data packet; and the first IAB node sending the second data packet to a next-hop node in the second network segment, the next-hop node being either a parent node or a child node of the first IAB node.

[0008] In this embodiment, in a scenario where the IAB network is managed by multiple IAB host nodes, the first IAB node replaces the BAP routing identifier of the data packet in the first network segment with the BAP routing identifier in the second network segment. This ensures normal transmission of the data packet in the second network segment and reduces data packet transmission anomalies caused by the IAB network being managed by multiple IAB host nodes. This guarantees that data packets are correctly routed in IAB networks composed of multiple network segments managed by different host nodes.

[0009] Optionally, in one possible implementation of the first aspect, the above steps further include: the first IAB node obtaining the second correspondence; the first IAB node sending the second data packet to the next-hop node in the second network segment, including: the first IAB node determining, based on the second correspondence, to send the second data packet to the next-hop node in the second network segment through the first backhaul radio link control (RLC) channel of the egress link.

[0010] In this possible implementation, when the exit mappings of the two network segments are managed by different host nodes, the first IAB node can obtain the correct exit mapping in the second network segment through the second correspondence, thereby enabling the normal transmission of data packets in the second network segment.

[0011] Optionally, in one possible implementation of the first aspect, before the above steps—namely, the first IAB node replacing the first BAP routing identifier in the first data packet with the second BAP routing identifier according to the first correspondence—to obtain the second data packet, the method further includes: the first IAB node determining that the BAP address in the first BAP routing identifier in the first data packet is the BAP address of the first IAB node, and that the first data packet satisfies a preset condition; the first IAB node determining that the first data packet satisfies the preset condition includes at least one of the following: the first data packet includes indication information, and the first IAB node determines that the first data packet satisfies the preset condition based on the indication information. If the first correspondence also includes the first BAP routing identifier in the first data packet, the first IAB node determines that the first data packet satisfies the preset condition.

[0012] In this possible implementation, the first IAB sets conditions before changing the BAP route identifier, reducing invalid processing of data packets that need to be received and processed by the upper protocol layer of BAP, thus saving network resources. Furthermore, whether the first data packet meets the conditions can be determined by indication information, or by whether the first correspondence includes the first BAP route identifier.

[0013] Optionally, in one possible implementation of the first aspect, before the first IAB node replaces the first BAP route identifier in the first data packet with the second BAP route identifier according to the first correspondence, and obtains the second data packet, the method further includes: the first IAB node determining that the BAP address in the first BAP route identifier in the first data packet is the BAP address of the first IAB node.

[0014] In this possible implementation, compared to determining whether to generate a second data packet based on preset conditions, this method adds conditions related to the BAP address, making the first IAB node's judgment more accurate.

[0015] Optionally, in one possible implementation of the first aspect, the indication information in the above steps includes the destination Internet Protocol (IP) address of the first data packet. When the destination IP address in the first data packet is not the IP address of the first IAB node, the first IAB node determines that the first data packet meets the preset conditions.

[0016] This possible implementation provides an implicit preset condition, which reduces the invalidation of data packets that need to be received and processed by the upper protocol layer of BAP, thus saving network resources.

[0017] Optionally, in one possible implementation of the first aspect, the first network segment in the above steps includes a first IAB node and an upstream node of the first IAB node; the second network segment includes a first IAB node and a downstream node of the first IAB node; the first IAB node receiving a first data packet in the first network segment includes: the first IAB node receiving a first data packet sent by the upstream node in the first network segment; the first IAB node sending a second data packet to the next-hop node in the second network segment includes: the first IAB node sending a second data packet to the downstream node in the second network segment, wherein the BAP address in the second BAP routing identifier is the BAP address of the downstream node.

[0018] In this possible implementation, during the transmission of downlink data packets across network segments, the first IAB node replaces the BAP routing identifier of the downlink data packet in the first network segment with the BAP routing identifier in the second network segment. This ensures normal transmission of the downlink data packet in the second network segment, reducing data packet transmission anomalies caused by the IAB network being managed by multiple IAB host nodes. This guarantees normal transmission of downlink data packets across network segments in an IAB network composed of multiple network segments managed by different host nodes.

[0019] Optionally, in one possible implementation of the first aspect, the first network segment in the above steps includes a first IAB node and downstream nodes of the first IAB node; the second network segment includes the first IAB node and upstream nodes of the first IAB node; the first IAB node receiving a first data packet in the first network segment includes: the first IAB node receiving a first data packet sent by the downstream node in the first network segment; the first IAB node sending a second data packet to the next-hop node in the second network segment includes: the first IAB node sending a second data packet to the upstream node in the second network segment, wherein the BAP address in the second BAP routing identifier is the BAP address of the second host node.

[0020] In this possible implementation, during the transmission of uplink data packets across network segments, the first IAB node replaces the BAP routing identifier of the uplink data packet in the first network segment with the BAP routing identifier in the second network segment. This ensures normal transmission of the uplink data packet in the second network segment, reducing data packet transmission anomalies caused by the IAB network being managed by multiple IAB host nodes. This guarantees normal transmission of uplink data packets across network segments in an IAB network composed of multiple network segments managed by different host nodes.

[0021] Optionally, in one possible implementation of the first aspect, the upstream node of the first IAB node in the above steps is the parent node of the first IAB node; before the first IAB node sends the second data packet to the upstream node in the second network segment, the method further includes: the first IAB node determining that the BAP address in the first BAP routing identifier in the first data packet is the BAP address of the first IAB node.

[0022] In this possible implementation, the BAP route identifier is limited to the BAP address, and the first IAB node can perform the replacement process more simply.

[0023] Optionally, in one possible implementation of the first aspect, the first BAP route identifier in the above steps includes a first BAP address and / or a first path identifier, and the second BAP route identifier includes a second BAP address and / or a second path identifier.

[0024] In this possible implementation, the BAP route identifier is limited to the BAP address, and the first IAB node can perform the replacement process more simply.

[0025] Optionally, in one possible implementation of the first aspect, the first correspondence in the above steps is configured by a first host node or a second host node; the first IAB node obtains the first correspondence, including any one of the following: the first IAB node obtains a first BAP route identifier and a second BAP route identifier, and the first BAP route identifier and the second BAP route identifier have a correspondence; the first IAB node obtains the IP header information in the first data packet and the second BAP route identifier, and the IP header information and the second BAP route identifier have a correspondence; the IP header information includes at least one of the following: destination IP address, Differentiated Service Code Point (DSCP), and Flow label.

[0026] This possible implementation provides multiple scenarios for the first IAB node to obtain the first correspondence, which facilitates the first IAB node to determine the second BAP route identifier and thus complete the BAP route identifier conversion between different network segments.

[0027] Optionally, in one possible implementation of the first aspect, the step of the first IAB node obtaining the second correspondence includes any one of the following: the first IAB node obtains a first BAP routing identifier and a first backhaul RLC channel of the first IAB node's egress link, and the first BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link have a correspondence; the first IAB node obtains a second BAP routing identifier and a first backhaul RLC channel of the first IAB node's egress link, and the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link have a correspondence; the first IAB node obtains the IP header information in the first data packet and the first backhaul RLC channel of the first IAB node's egress link, and the IP header information includes the destination IP address, the Differentiated Service Code Point (DSCP), and the Flow label. At least one of the labels; the first IAB node obtains the second backhaul RLC channel of the first IAB node ingress link and the first backhaul RLC channel of the first IAB node egress link, and the second backhaul RLC channel of the first IAB node ingress link and the first backhaul RLC channel of the first IAB node egress link have a corresponding relationship.

[0028] This possible implementation provides multiple scenarios for the first IAB node to obtain the second correspondence, facilitating the first IAB node to determine the exit link of the second network segment, thereby enabling the normal transmission of data packets in the second network segment.

[0029] The second aspect of this application provides a communication method, which can be executed by a first IAB node or by a component of the first IAB node (such as IAB-DU, IAB-MT, processor, chip, or chip system). The method is applied to an integrated access backhaul IAB network. The method includes: the first IAB node obtaining a second correspondence; and the first IAB node determining, based on the second correspondence, to send a second data packet to the next-hop node through the first backhaul RLC channel of the egress link in the second network segment.

[0030] In this embodiment of the application, the first IAB node determines, based on the second correspondence, to send the second data packet to the next hop node through the first backhaul RLC channel of the egress link in the second network segment, which can ensure the normal transmission of the second data packet in the second network segment.

[0031] Optionally, in one possible implementation of the second aspect, the IAB network includes a first network segment and a second network segment, the first network segment is managed by a first host node, and the second network segment is managed by a second host node. The first host node and the second host node are different. Before the first IAB node obtains the second correspondence, the method further includes: the first IAB node receives a first data packet in the first network segment. The first data packet includes a first backhaul adaptation protocol (BAP) routing identifier, which is used for the transmission of the first data packet in the first network segment.

[0032] In this possible implementation, when the IAB network is managed by multiple IAB host nodes, the first IAB node determines, based on the second correspondence, to send the second data packet to the next-hop node via the first backhaul RLC channel of the egress link in the second network segment. This reduces the egress mapping anomaly caused by the IAB network being managed by multiple IAB host nodes. It ensures normal data packet transmission in IAB networks composed of multiple network segments managed by different host nodes.

[0033] Optionally, in one possible implementation of the second aspect, the second data packet in the above steps includes a second BAP route identifier, which is used for the transmission of the second data packet in the second network segment.

[0034] This possible implementation allows each host node to control packet routing only within its own network segment. The boundary node between the two network segments then performs proxy operations at the BAP or IP layer, reducing the outbound mapping anomalies caused by multiple IAB host nodes managing the IAB network. This ensures normal packet transmission even in IAB networks composed of multiple network segments managed by different host nodes.

[0035] Optionally, in one possible implementation of the second aspect, the first data packet and the second data packet in the above steps are the same data packet, and the first BAP route identifier is the same as the second BAP route identifier.

[0036] In this possible implementation, the IAB network includes a network segment, and the return RLC channel of the egress link is determined through a second correspondence, which can accurately determine the channel for transmitting data packets.

[0037] Optionally, in one possible implementation of the second aspect, the above steps further include: the first IAB node obtaining the first correspondence; the first IAB node replacing the first BAP route identifier in the first data packet with the second BAP route identifier according to the first correspondence, thereby obtaining the second data packet;

[0038] In this possible implementation, each host node only controls the routing of data packets within its own network segment. By having the boundary node of the two network segments (i.e., the first IAB node) perform proxy operations at the BAP layer or IP layer, the first BAP routing identifier contained in the received data packet for routing in the first network segment is replaced with the second BAP routing identifier that will be used for routing in the second network segment. Through this splicing routing method, it is ensured that data packets can be routed reasonably and correctly in the network topology management of newly emerging cross-host base stations.

[0039] A third aspect of this application provides a communication method, which can be executed by a first host node or by a component of the first host node (e.g., DU, CU, processor, chip, or chip system). This method is applied to an integrated access backhaul (IAB) network, which includes a first network segment and a second network segment. The first network segment is managed by the first host node, and the second network segment is managed by a second host node. The first and second host nodes are different. The method includes: the first host node obtaining a first BAP routing identifier and a second BAP routing identifier, which have a corresponding relationship; the first BAP routing identifier is used for data packet transmission in the first network segment, and the second BAP routing identifier is used for data packet transmission in the second network segment; the first host node sending the first BAP routing identifier and the second BAP routing identifier to a first IAB node, which is located in both the first and second network segments. Alternatively, the first host node obtains the IP header information and the second BAP routing identifier from the data packet. The IP header information and the second BAP routing identifier have a corresponding relationship. The second BAP routing identifier is used for data packet transmission in the second network segment. The first host node sends the IP header information and the second BAP routing identifier from the data packet to the first IAB node, which is located in both the first and second network segments.

[0040] In this embodiment, in a scenario where the IAB network is managed by multiple IAB host nodes, a first host node configures a first correspondence with a first IAB node, enabling data packets to be transmitted normally in the second network segment. This reduces data packet transmission anomalies caused by the IAB network being managed by multiple IAB host nodes. It ensures that data packets are correctly routed in IAB networks composed of multiple network segments managed by different host nodes.

[0041] Optionally, in one possible implementation of the third aspect, the above steps further include: the first host node obtaining the first BAP routing identifier and the first backhaul RLC channel of the first IAB node egress link, wherein the first BAP routing identifier and the first backhaul RLC channel of the first IAB node egress link have a corresponding relationship.

[0042] The first host node sends the first BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link to the first IAB node.

[0043] or,

[0044] The first host node obtains the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link, and the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link have a corresponding relationship.

[0045] The first host node sends the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link to the first IAB node.

[0046] or,

[0047] The first host node obtains the IP header information in the first data packet and the first backhaul RLC channel of the first IAB node's egress link. The IP header information in the first data packet and the first backhaul RLC channel of the first IAB node's egress link have a corresponding relationship.

[0048] The first host node sends the IP header information from the first data packet to the first IAB node and the first return RLC channel of the first IAB node's egress link.

[0049] or,

[0050] The first host node obtains the second backhaul RLC channel of the first IAB node ingress link and the first backhaul RLC channel of the first IAB node egress link. The second backhaul RLC channel of the first IAB node ingress link and the first backhaul RLC channel of the first IAB node egress link have a corresponding relationship.

[0051] The first host node sends the second backhaul RLC channel of the first IAB node's ingress link and the first backhaul RLC channel of the first IAB node's egress link to the first IAB node.

[0052] In this possible implementation, when the IAB network is managed by multiple IAB host nodes, a second mapping is configured for the first IAB node by the first host node. This ensures that data packets can determine the correct exit mapping in the second network segment, reducing data packet transmission anomalies caused by the multiple IAB host nodes managing the IAB network. This guarantees normal data packet transmission in IAB networks composed of multiple network segments managed by different host nodes.

[0053] Optionally, in one possible implementation of the third aspect, the above steps further include: the first host node sending configuration information to the access IAB node, the configuration information being used to indicate that the BAP address of the first IAB node is used as the destination BAP address of the uplink data packet.

[0054] In this possible implementation, for uplink transmission, the first host node sends configuration information to the access node, causing the access node to add the BAP address of the first IAB node to the BAP layer of the uplink data packet, thereby enabling the normal transmission of the uplink data packet in the first network segment. This also allows the first IAB node to subsequently change the BAP routing identifier normally.

[0055] Optionally, in one possible implementation of the third aspect, the first network segment in the above steps includes a first IAB node and downstream nodes of the first IAB node; the second network segment includes a first IAB node and upstream nodes of the first IAB node; the method further includes: the first host node obtaining a third correspondence and a fourth correspondence, the third correspondence being the correspondence between the IP address of the distributed unit (DU) in the first IAB node and the BAP address of the mobile terminal (MT) in the first IAB node, and the fourth correspondence being the correspondence between the BAP address of the MT in the first IAB node and the IP address of the DU in the downstream node of the first IAB node; the first host node sending the third correspondence and the fourth correspondence to the second host node, the third correspondence and the fourth correspondence being used by the second host node to determine the first BAP routing identifier.

[0056] In this possible implementation, after the first host obtains the third and fourth correspondences, it sends the third and fourth correspondences to the second host node, so that the second host node can provide the correct first BAP route identifier for the DU part of the second host.

[0057] Optionally, in one possible implementation of the third aspect, the first network segment in the above steps includes a first IAB node and downstream nodes of the first IAB node; the second network segment includes the first IAB node and upstream nodes of the first IAB node; the method further includes: the first host node determining a third BAP route identifier used for downlink transmission of data packets in the first network segment, the second BAP route identifier including the third BAP route identifier; and the first host node sending the third BAP route identifier to the second host node.

[0058] In this possible implementation, the first host node configures the BAP route identifier in the first network segment and informs the second host, thereby enabling the second host node to configure the first correspondence relationship with the first IAB node.

[0059] Optionally, in one possible implementation of the third aspect, the first network segment in the above steps includes the first IAB node and the downstream node of the first IAB node; the second network segment includes the first IAB node and the upstream node of the first IAB node; the method further includes: the first host node receiving a fourth BAP routing identifier sent by the second host node, the fourth BAP routing identifier being used for uplink transmission of data packets in the second network segment, and the second BAP routing identifier including the fourth BAP routing identifier.

[0060] In this possible implementation, the first host node receives the BAP routing identifier sent by the second host node for the second network segment, thereby enabling the first host to configure the first correspondence relationship with the IAB node.

[0061] A fourth aspect of this application provides a communication method, which can be executed by a second host node or by a component of the second host node (e.g., DU, CU, processor, chip, or chip system). This method is applied to an integrated access backhaul (IAB) network, which includes a first network segment and a second network segment. The first network segment is managed by a first host node, and the second network segment is managed by a second host node. The first and second host nodes are different, and the first IAB node is located in both the first and second network segments. The method includes:

[0062] The second host node obtains the first BAP route identifier and the second BAP route identifier. The first BAP route identifier and the second BAP route identifier have a corresponding relationship. The first BAP route identifier is used for data packets to be transmitted in the first network segment, and the second BAP route identifier is used for data packets to be transmitted in the second network segment.

[0063] The second host node sends the first BAP route identifier and the second BAP route identifier to the first IAB node. The first IAB node is located in the first network segment and the second network segment.

[0064] or,

[0065] The second host node obtains the IP header information and the second BAP route identifier from the data packet. The IP header information and the second BAP route identifier have a corresponding relationship. The second BAP route identifier is used for data packet transmission in the second network segment.

[0066] The second host node sends the IP header information and the second BAP routing identifier from the data packet to the first IAB node. The first IAB node is located in both the first and second network segments.

[0067] In this embodiment, in a scenario where the IAB network is managed by multiple IAB host nodes, a first correspondence is configured for the first IAB node through a second host node. This ensures that data packets are transmitted normally in the second network segment, reducing data packet transmission anomalies caused by the IAB network being managed by multiple IAB host nodes. This guarantees that data packets are correctly routed in IAB networks composed of multiple network segments managed by different host nodes.

[0068] Alternatively, in one possible implementation of the fourth aspect, the above steps further include:

[0069] The second host node obtains the first BAP route identifier and the first backhaul RLC channel of the first IAB node's egress link, and the first BAP route identifier and the first backhaul RLC channel of the first IAB node's egress link have a corresponding relationship.

[0070] The second host node sends the first BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link to the first IAB node.

[0071] or,

[0072] The second host node obtains the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link, and the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link have a corresponding relationship.

[0073] The second host node sends the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link to the first IAB node.

[0074] or,

[0075] The second host node obtains the IP header information in the first data packet and the first backhaul RLC channel of the first IAB node's egress link. The IP header information in the first data packet and the first backhaul RLC channel of the first IAB node's egress link have a corresponding relationship.

[0076] The second host node sends the IP header information from the first data packet to the first IAB node and the first backhaul RLC channel of the first IAB node's egress link.

[0077] or,

[0078] The second host node obtains the second backhaul RLC channel of the first IAB node's ingress link and the first backhaul RLC channel of the first IAB node's egress link. The second backhaul RLC channel of the first IAB node's ingress link and the first backhaul RLC channel of the first IAB node's egress link have a corresponding relationship.

[0079] The second host node sends the second backhaul RLC channel of the first IAB node's ingress link and the first backhaul RLC channel of the first IAB node's egress link to the first IAB node.

[0080] In this possible implementation, when the IAB network is managed by multiple IAB host nodes, a second host node configures a second mapping relationship for the first IAB node. This ensures that data packets can determine the correct exit mapping in the second network segment, reducing data packet transmission anomalies caused by the multiple IAB host nodes managing the IAB network. This guarantees normal data packet transmission in IAB networks composed of multiple network segments managed by different host nodes.

[0081] Optionally, in one possible implementation of the fourth aspect, the above steps further include: the second host node sending configuration information to the access IAB node, the configuration information being used to indicate that the BAP address of the first IAB node is used as the destination BAP address of the uplink data packet.

[0082] In this possible implementation, for uplink transmission, the second host node sends configuration information to the access node, causing the access node to add the BAP address of the first IAB node to the BAP layer of the uplink data packet, thereby enabling the normal transmission of the uplink data packet in the first network segment. This also allows the first IAB node to subsequently change the BAP routing identifier normally.

[0083] Optionally, in one possible implementation of the fourth aspect, the first network segment in the above steps includes the first IAB node and its downstream nodes; the second network segment includes the first IAB node and its upstream nodes; the method further includes: the second host node receiving a third correspondence and a fourth correspondence sent by the first host node, wherein the third correspondence is the correspondence between the IP address of the distributed unit (DU) in the first IAB node and the BAP address of the mobile terminal (MT) in the first IAB node, and the fourth correspondence is the correspondence between the BAP address of the MT in the first IAB node and the IP address of the DU in the downstream node of the first IAB node; the second host node determines the first BAP routing identifier based on the third correspondence and the fourth correspondence.

[0084] In this possible implementation, the second host node receives the third and fourth correspondences, and thus the second host node can provide the correct first BAP route identifier for the DU part of the second host.

[0085] Optionally, in one possible implementation of the fourth aspect, the first network segment in the above steps includes the first IAB node and the downstream node of the first IAB node; the second network segment includes the first IAB node and the upstream node of the first IAB node; the method further includes: the second host node receiving a third BAP routing identifier sent by the first host node, the third BAP routing identifier being used for downlink transmission of data packets in the first network segment, and the second BAP routing identifier including the third BAP routing identifier.

[0086] In this possible implementation, the second host node receives the BAP routing identifier sent by the first host node for the first network segment, thereby enabling the second host to configure the first correspondence between the IAB nodes.

[0087] Optionally, in one possible implementation of the fourth aspect, the first network segment in the above steps includes the first IAB node and the downstream node of the first IAB node; the second network segment includes the first IAB node and the upstream node of the first IAB node; the method further includes: the second host node determining the fourth BAP route identifier used for uplink transmission of data packets in the second network segment, the second BAP route identifier including the fourth BAP route identifier; the second host node sending the fourth BAP route identifier to the first host node.

[0088] In this possible implementation, the second host node configures the BAP route identifier in the second network segment and informs the first host, thereby enabling the first host node to configure the first correspondence relationship with the first IAB node.

[0089] The fifth aspect of this application provides a communication device, which may be a first IAB node or a component of the first IAB node (e.g., IAB-DU, IAB-MT, or a processor, chip, or chip system). The communication device executes the methods in the first aspect or any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect.

[0090] The sixth aspect of this application provides a communication device, which may be a first host node or a component of the first host node (e.g., DU, CU, or processor, chip, or chip system). The communication device executes the methods in the aforementioned third aspect or any possible implementation thereof.

[0091] The seventh aspect of this application provides a communication device, which may be a second host node or a component of the second host node (e.g., DU, CU, or processor, chip, or chip system), and the communication device performs the methods in the fourth aspect or any possible implementation thereof.

[0092] An eighth aspect of this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the methods of the first aspect or any possible implementation thereof, the second aspect or any possible implementation thereof, the third aspect or any possible implementation thereof, or the fourth aspect or any possible implementation thereof.

[0093] The ninth aspect of this application provides a computer program product that, when executed on a computer, causes the computer to perform the methods in the first aspect or any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect, the third aspect or any possible implementation of the third aspect, or the fourth aspect or any possible implementation of the fourth aspect.

[0094] A tenth aspect of this application provides a communication device, including: a processor coupled to a memory, the memory being used to store programs or instructions, which, when executed by the processor, cause the device to implement the methods of the first aspect or any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect.

[0095] The eleventh aspect of this application provides a communication device, including: a processor coupled to a memory, the memory being used to store programs or instructions, which, when executed by the processor, cause the device to implement the methods in the third aspect or any possible implementation of the third aspect.

[0096] The twelfth aspect of this application provides a communication device, including: a processor coupled to a memory for storing programs or instructions, wherein when the programs or instructions are executed by the processor, the device implements the methods in the fourth aspect or any possible implementation thereof.

[0097] The thirteenth aspect of this application provides a communication system, including at least one of the communication devices provided in the fifth aspect, the sixth aspect, and the seventh aspect.

[0098] The fourteenth aspect of this application provides a communication system, including at least one of the communication devices provided in the tenth aspect, the eleventh aspect, and the twelfth aspect.

[0099] The fifteenth aspect of this application provides a communication method that can be executed by an IAB node or by a component of the IAB node (such as an IAB-DU, IAB-MT, IAB donor, processor, chip, or chip system). The method is applied to an integrated access backhaul IAB network. The method includes: the IAB node receiving a data packet, and the IAB node determining that the data packet is abnormal based on the type of the data packet and / or the attributes of the IAB node.

[0100] Optionally, in one possible implementation of aspect fifteen, the data packet categories include uplink and downlink. That is, the data packets include uplink data packets and / or downlink data packets.

[0101] Optionally, in one possible implementation of the fifteenth aspect, the data packet includes: a parent node data packet and / or a child node data packet, wherein the parent node data packet is a data packet sent by the parent node of the IAB node, and the child node data packet is a data packet sent by the child node of the IAB node.

[0102] Optionally, in one possible implementation of the fifteenth aspect, the data packet includes: an upstream data packet and / or a downstream data packet, wherein the upstream data packet is a data packet sent by an upstream node of the IAB node, and the downstream data packet is a data packet sent by a downstream node of the IAB node.

[0103] Optionally, in one possible implementation of aspect fifteen, the IAB node receives a data packet, and the IAB node determines that the data packet anomaly, based on the data packet category and / or the attributes of the IAB node, includes at least one of the following:

[0104] 1. When an IAB node receives an uplink data packet, if the BAP header of the uplink data packet carries the BAP address of the IAB node, then the IAB node determines that the uplink data packet is an erroneous or abnormal data packet.

[0105] Optionally, the IAB node receives uplink data packets specifically through the receiving portion of the BAP layer entity located in the IAB-DU.

[0106] In this possible implementation, once the IAB node determines that the uplink data packet is erroneous or abnormal, it can discard the packet. This simplifies the criteria for determining uplink data packet abnormalities and reduces the cache space occupied by erroneous or abnormal uplink data packets on the IAB node.

[0107] 2. When an IAB-donor DU receives an uplink data packet, if the BAP address in the BAP header of that uplink data packet is not the BAP address of the IAB-donor DU, then the IAB-donor DU determines that the data packet is an erroneous or abnormal data packet.

[0108] In this possible implementation, once the IAB-donor DU determines that the uplink data packet is erroneous or abnormal, it can discard the packet. This simplifies the criteria for determining uplink data packet abnormalities and reduces the cache space occupied by erroneous or abnormal uplink data packets in the IAB-donor DU.

[0109] The sixteenth aspect of this application provides a communication method that can be executed by an IAB node or by a component of the IAB node (such as an IAB-DU, IAB-MT, IAB donor, processor, chip, or chip system). The method is applied to an integrated access backhaul IAB network. The method includes: before the IAB node sends a data packet, the IAB node determines that the data packet is abnormal based on the type of the data packet and / or the attributes of the IAB node.

[0110] Alternatively, in one possible implementation of the sixteenth aspect, the data packet categories include uplink and downlink. That is, the data packets include uplink data packets and / or downlink data packets.

[0111] Optionally, in one possible implementation of the sixteenth aspect, the data packet includes: a parent node data packet and / or a child node data packet, wherein the parent node data packet is a data packet sent by the parent node of the IAB node, and the child node data packet is a data packet sent by the child node of the IAB node.

[0112] Optionally, in one possible implementation of the sixteenth aspect, the data packet includes: an upstream data packet and / or a downstream data packet, wherein the upstream data packet is a data packet sent by an upstream node of the IAB node, and the downstream data packet is a data packet sent by a downstream node of the IAB node.

[0113] Optionally, in one possible implementation of the sixteenth aspect, before the IAB node sends a data packet, the IAB node determines that the data packet anomaly, based on the data packet category and / or the attributes of the IAB node, includes at least one of the following:

[0114] 1. Before sending a data packet, if an IAB node cannot find any entry in its routing table that contains the destination BAP address of the data packet, then the IAB node determines that the data packet is an error or an abnormal data packet.

[0115] Optionally, the IAB node is specifically the transmission portion of the BAP layer entity located in IAB-MT / DU.

[0116] In this possible implementation, once the IAB node determines that a data packet is erroneous or abnormal, it can discard the packet. On the one hand, this simplifies the criteria for determining packet abnormality, reducing the amount of buffer space occupied by erroneous or abnormal packets in the IAB node. On the other hand, it reduces the network resource consumption caused by sending erroneous or abnormal packets.

[0117] 2. Before sending a downlink data packet, if the IAB-donor-DU cannot find any entry in its routing table that contains the destination BAP address of the packet, then the IAB-donor-DU determines that the downlink data packet is an erroneous or abnormal packet.

[0118] In this possible implementation, once the IAB-donor-DU determines that the downlink data packet is erroneous or abnormal, it can discard the packet. On the one hand, this simplifies the criteria for determining downlink data packet abnormality, reducing the buffer space occupied by erroneous or abnormal downlink data packets in the IAB-donor-DU. On the other hand, it reduces the network resource consumption caused by sending erroneous or abnormal downlink data packets.

[0119] Regarding aspects fifteen and sixteen, compared to the generally complex methods used in the prior art to determine data packet anomalies, the data packet processing method provided in this application can simplify the conditions for determining data packet anomalies in specific situations, and more accurately identify more abnormal data packets. The related beneficial effects can be found in the description above.

[0120] The technical effects of aspects five, eight, nine, ten, thirteen, and fourteen, or any one of their possible implementations, can be found in the first aspect or the technical effects of different possible implementations of the first aspect, and will not be repeated here.

[0121] The technical effects of aspects five, eight, nine, ten, thirteen, and fourteen, or any one of their possible implementations, can be found in aspect two or different possible implementations of aspect two, and will not be repeated here.

[0122] The technical effects of aspects six, eight, nine, eleven, thirteen, and fourteen, or any one of their possible implementations, can be found in aspect three or the technical effects of different possible implementations of aspect three, and will not be repeated here.

[0123] The technical effects of aspects seven, eight, ten, twelfth, thirteenth, and fourteenth, or any one of their possible implementations, can be found in aspect four or the technical effects of different possible implementations of aspect four, and will not be repeated here.

[0124] As can be seen from the above technical solutions, the embodiments of this application have the following advantages: In a scenario where the IAB network is managed by multiple IAB host nodes, the first BAP routing identifier is information used for data packet routing in the first network segment composed of IAB nodes controlled by the first host node, while the second BAP routing identifier is information used for data packet routing in the second network segment composed of IAB nodes controlled by the second host node. By having the first IAB node replace the BAP routing identifier of the data packet in the first network segment with the BAP routing identifier in the second network segment, the data packet can be transmitted normally in the second network segment, reducing the data packet transmission anomaly caused by the IAB network being managed by multiple IAB host nodes. Attached Figure Description

[0125] Figure 1 This is a schematic diagram of an IAB standalone networking scenario;

[0126] Figure 2 This is a schematic diagram of an IAB non-standalone networking scenario;

[0127] Figure 3 This is a schematic diagram of an IAB network system architecture;

[0128] Figure 4 This is a schematic diagram of an IAB network user plane protocol stack.

[0129] Figure 5 This is a schematic diagram of an IAB network control plane protocol stack.

[0130] Figure 6 This is a schematic diagram of a cross-host switching scenario in an embodiment of this application;

[0131] Figure 7 This is a schematic diagram of a dual-homed connection scenario in an embodiment of this application;

[0132] Figure 8 This is a schematic diagram of a top-to-bottom cross-host switching scenario in an embodiment of this application;

[0133] Figure 9 This is a schematic diagram of a bottom-up cross-host switching scenario in an embodiment of this application;

[0134] Figure 10 This is another schematic diagram of a dual-homed connection scenario in the embodiments of this application;

[0135] Figure 11 This is a flowchart illustrating a communication method in an embodiment of this application;

[0136] Figure 12 This is another flowchart illustrating the communication method in an embodiment of this application;

[0137] Figures 13 to 19 These are schematic diagrams of several structures of the communication device in the embodiments of this application. Detailed Implementation

[0138] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0139] In the description of this application, unless otherwise stated, " / " signifies "or," for example, A / B can mean A or B. "And / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. Additionally, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first," "second," etc., are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or execution order, and that "first," "second," etc., do not necessarily imply differences.

[0140] First, some terms used in the embodiments of this application will be explained to facilitate understanding by those skilled in the art.

[0141] 1. Communication systems: including but not limited to narrowband Internet of Things (NB-IoT) systems, wireless local access network (WLAN) systems, long-term evolution (LTE) systems, next-generation 5G mobile communication systems, or communication systems after 5G, such as new radio (NR) and device-to-device (D2D) communication systems.

[0142] 2. Network equipment: also known as base stations, including but not limited to evolved node base (eNB), radio network controller (RNC), node B (NB), basestation controller (BSC), base transceiver station (BTS), home evolved NodeB (or home node B (HNB)), baseband unit (BBU), evolved LTE (eLTE) base station, NR base station (gNB), etc.

[0143] 3. Terminal equipment: including but not limited to any of the following: user equipment (UE), mobile station, access terminal, user unit, user station, mobile station, remote station, remote terminal, mobile device, terminal, wireless communication equipment, user agent, station (ST) in wireless local access network (WLAN), cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication function, computing device, other processing device connected to wireless modem, vehicle-mounted equipment, wearable device, mobile station in future 5G networks, and terminal equipment in future evolved public land mobile network (PLMN) networks. The following illustrative example uses UE as the terminal equipment.

[0144] 4. Wireless Backhaul Node (also known as IAB Node): This node provides wireless backhaul services to nodes (e.g., terminals) that wirelessly access the wireless backhaul node. The wireless backhaul service refers to data and / or signaling backhaul services provided via the wireless backhaul link. The wireless backhaul node can be an IAB node or a relay node (RN). This application does not limit the type of node; it can be one of the aforementioned base stations or terminal devices with forwarding capabilities, or it can be an independent device. In a network containing a wireless backhaul node (using an IAB network as an example), the wireless backhaul node can provide wireless access services to terminals and connect to the host base station (donor gNB) via the wireless backhaul link to transmit user service data.

[0145] For example, the wireless backhaul node can also be a customer premises equipment (CPE), a residential gateway (RG), or other similar devices. In this case, the method provided in this application embodiment can also be applied to home access scenarios.

[0146] Furthermore, the following is a brief introduction to the concepts involved in IAB networks.

[0147] 1. Wireless backhaul node and host node:

[0148] In this embodiment, the node supporting integrated access and backhaul is referred to as a wireless backhaul node. In LTE communication systems, this wireless backhaul node can also be called a relay node (RN), and in 5G, it can also be called an IAB node. For ease of description, the IAB node will be used as an example below.

[0149] IAB nodes can provide wireless access services to terminal devices, whose data (including user plane data and control plane signaling) is transmitted by the IAB node to the host node via a wireless backhaul link.

[0150] In this embodiment, the host node is also referred to as an IAB host (IAB onor) or a host base station (donorgNodeB, DgNB). Specifically, the DgNB can be an access network element with complete base station functionality, or it can be an access network element with separate centralized units (CU) and distributed units (DU). The DgNB connects to the core network element serving the terminal equipment, for example, it connects to the 5G core network (5G core, 5GC) and provides wireless backhaul functionality for the IAB node. For ease of description, this embodiment refers to the centralized unit of the host node as the host CU (donor CU) and the distributed unit of the host node as the host DU (donor DU). The donor CU may also have a separate control plane (CP) or user plane (UP) configuration. For example, a CU may consist of one CU-CP and multiple CU-UPs, which is not limited in this embodiment.

[0151] 2. Parent node, child node, downstream node, upstream node:

[0152] Each IAB node considers its neighboring nodes that provide radio access and / or radio backhaul services as its parent nodes. Correspondingly, each IAB node can be considered a child node of its parent node. IAB networks can support multi-hop and multi-connection networking; therefore, multiple transmission paths may exist between the terminal device and the host node. On a given transmission path, there are defined hierarchical relationships between the terminal device and the IAB node providing radio access services, between IAB nodes themselves, and between an IAB node and the host node providing backhaul services. Specifically, the node providing radio backhaul services to an IAB node is called its parent node, or the node providing radio access services to a terminal device is called its parent node. The IAB node can be considered a child node of its parent node, and the terminal device can be considered a child node of its parent node. Here, the parent node of an IAB node can be another IAB node or the host node. When an IAB node communicates directly with a host node via the radio interface, the parent node of that IAB node is the host node.

[0153] Alternatively, a child node can also be called a subordinate node or a downstream node, and a parent node can also be called a superior node or an upstream node.

[0154] 3. Intermediate IAB nodes:

[0155] Intermediate IAB nodes refer to IAB nodes that provide wireless backhaul services to other IAB nodes (e.g., access IAB nodes or other intermediate IAB nodes), or IAB nodes on the path between access IAB nodes and the IAB host.

[0156] 4. Access Link:

[0157] The wireless link used by a terminal device to communicate with a node (e.g., an IAB node, a host node, or a host DU) that provides it with wireless access services includes an access link for uplink transmission and an access link for downlink transmission. The access link for uplink transmission is also called an uplink access link or access uplink, and its transmission direction is from the terminal device to the node; the access link for downlink transmission is also called a downlink access link or access downlink, and its transmission direction is from the node to the terminal device. In this application, the access link of the terminal device is a wireless link, therefore, the access link can also be called a wireless access link.

[0158] 5. Backhaul link:

[0159] A backhaul link refers to the wireless link used by an IAB node to communicate with its parent node. The parent node can be either an IAB node or a host node. Backhaul links include those used for uplink transmission and those used for downlink transmission. A backhaul link used for uplink transmission is also called an uplink backhaul link or a backhaul uplink link, and its transmission direction is from the IAB node to its parent node. A backhaul link used for downlink transmission is also called a downlink backhaul link or a backhaul downlink link, and its transmission direction is from the parent node to the IAB node. In this application, the backhaul link between the IAB node and its parent node is a wireless link; therefore, the backhaul link can also be called a wireless backhaul link.

[0160] 6. Transmission path:

[0161] The entire route from the sending node to the receiving node consists of at least one link. In this embodiment, a link represents a connection between adjacent nodes. That is, the transmission path is the transmission path between the sending node and the receiving node, starting from the sending node and ending at the receiving node. For ease of description, the transmission path between the sending node and the receiving node, starting from the sending node and ending at the receiving node, can be described as the transmission path between the sending node and the receiving node.

[0162] In uplink transmission, any node other than the host node between the terminal device and the host node can be used as the sending node, and the sending node's parent node (e.g., the sending node's parent node or the parent node's parent node) can be used as the receiving node. For example, the sending node can be an IAB node, and the receiving node can be the parent node of that IAB node. The entire route between that IAB node and its parent node represents a transmission path. As another example, the sending node can be an IAB node, and the receiving node can be the host node. The entire route between that IAB node and its host node represents a transmission path.

[0163] Similarly, in downlink transmission, the sending node can be any node other than the terminal device between the host node and the terminal device, and the receiving node can be a subordinate node of the sending node (e.g., a child node of the sending node or a child node of a child node). For example, the sending node can be an IAB node, and the receiving node can be a child node of that IAB node; the end-to-end route between the IAB node and its child nodes represents a transmission path. As another example, the sending node can be an IAB node, and the receiving node can be a terminal device; the end-to-end route between the IAB node and the terminal device represents a transmission path.

[0164] 7. F1 interface and its protocol layer:

[0165] The F1 interface refers to the logical interface between the DU part of the IAB node and the host node (or donor-CU). The F1 interface can also be called the F1* interface, which supports both the user plane and the control plane.

[0166] The protocol layer of the F1 interface refers to the communication protocol layer on the F1 interface.

[0167] All node and message names in this application are merely for descriptive convenience and may differ in actual networks. This application should not be interpreted as limiting the names of various nodes and messages. Conversely, any name that has the same or similar function as the nodes or messages used in this application is considered a method or equivalent substitution of this application and is within the scope of protection of this application; further details will not be provided below.

[0168] Compared to fourth-generation mobile communication systems, fifth-generation mobile communication (5G) places more stringent demands on all aspects of network performance. For example, it requires a 1000-fold increase in capacity, wider coverage, and ultra-high reliability and ultra-low latency. On the one hand, considering the abundance of high-frequency carrier resources, the use of high-frequency small cell networks is becoming increasingly popular in hotspot areas to meet the ultra-high capacity demands of 5G. However, high-frequency carriers have poor propagation characteristics, suffer severe attenuation due to obstruction, and have limited coverage, thus requiring a large-scale, dense deployment of small cells. Consequently, providing fiber optic backhaul for these densely deployed small cells is costly and difficult to implement, necessitating an economical and convenient backhaul solution. On the other hand, from the perspective of wide coverage requirements, providing network coverage in remote areas presents significant challenges and costs associated with fiber optic deployment, necessitating the design of flexible and convenient access and backhaul solutions. IAB technology offers a solution to these two problems: both its access link and backhaul link utilize wireless transmission schemes, reducing fiber optic deployment.

[0169] In the current 5G standard, considering the limited coverage of high-frequency bands, multi-hop networking may be used in IAB networks to ensure network coverage performance. Furthermore, considering the reliability requirements of service transmission, IAB nodes can support dual connectivity (DC) or multi-connectivity to cope with possible anomalies in the backhaul link, such as link interruption or blockage and load fluctuations, thus improving transmission reliability. Therefore, IAB networks support both multi-hop and multi-connectivity networking. Between the terminal device served by the IAB node and the IAB donor, there exists at least one transmission path composed of multiple links. A transmission path includes multiple nodes, such as a UE, one or more IAB nodes, and an IAB donor (if the IAB donor has a separate CU and DU configuration, it also includes an IAB-donor-DU part and an IAB-donor-CU part). Each IAB node considers the adjacent node providing access and backhaul services as its parent node; correspondingly, each IAB node can be considered a child node of its parent node.

[0170] Please see Figure 1 , Figure 1 This is a schematic diagram of an IAB standalone networking scenario.

[0171] The parent node of IAB node 1 is the IAB donor. IAB node 1 is the parent node of IAB node 2 and IAB node 3. IAB node 2 and IAB node 3 are both the parent nodes of IAB node 4. The parent node of IAB node 5 is IAB node 2. The UE's uplink data packets can be transmitted to the host site IAB donor via one or more IAB nodes, and then sent by the IAB donor to the mobile gateway device (such as the User Plane Functional Unit (UPF) in the 5G core network). Downlink data packets will be received by the IAB donor from the mobile gateway device and then sent to the UE via the IAB nodes. Figure 1 The diagram shows an IAB standalone (SA) networking scenario, where both the IAB node and the UE establish a connection with the network only through the NR standard air interface.

[0172] Figure 1 The IAB standalone networking scenario shown is merely an example. In IAB scenarios that combine multi-hop and multi-connection, there are many other possibilities, such as the IAB donor and the IAB node under another IAB donor forming a dual connection to serve the UE, etc. Specific details are not limited here.

[0173] In addition to supporting features such as IAB networks Figure 1 In addition to the standalone networking scenarios shown, IAB networks can also support, for example, Figure 2 The non-standalone networking scenario shown.

[0174] Please see Figure 2 , Figure 2 This is a schematic diagram of an IAB non-standalone networking scenario.

[0175] The IAB node supports dual connectivity for 4G and 5G networks (E-UTRAN NR Dual Connectivity, EN-DC). The LTE base station eNB is the master base station (MeNB), providing LTE air interface (LTE Uu) connectivity for the IAB node and establishing an S1 interface with the 4G core network – evolved packet core (EPC) – for user plane and control plane transmission. The IAB-donor gNB is the secondary base station, providing NR air interface (NR Uu) connectivity for the IAB node and establishing an S1 interface with the core network EPC for user plane transmission. Similarly, the UE also supports EN-DC. The UE connects to the master base station eNB via the LTE Uu interface and to the secondary base station IAB node via the NR Uu interface. The UE's secondary base station can also be an IAB donor gNB.

[0176] It should be noted that Figure 2 This is just a networking example; NSA scenarios in IAB networks also support multi-hop IAB networking, for example... Figure 2 The UE in the UE can be another IAB node, meaning that the IAB node can connect to the IAB donorgNB via a multi-hop radio backhaul link.

[0177] The IAB non-standalone networking scenario in this application can also be referred to as the IAB EN-DC networking scenario.

[0178] The above has been combined Figure 1 and Figure 2 This paper describes both Standalone (SA) and Non-Standalone (NSA) IAB networks. The following sections describe the IAB network system architecture with separate host nodes (CU and DU) and IAB nodes (MT and DU). Please refer to [link / reference]. Figure 3 , Figure 3 This is a schematic diagram of the IAB network system architecture.

[0179] When the IAB node operates in SA mode, the IAB donor can connect to the 5GC. Specifically, the IAB donor CU-CP connects to control plane elements in the 5GC via the NG control plane interface (NG-C), such as the access and mobility management function (AMF). The IAB donor CU-UP connects to user plane elements in the 5GC via the NG user plane interface (NG-U), such as the user plane function (UPF).

[0180] When the IAB node operates in NSA mode (or EN-DC mode), the IAB donor CU-UP can connect to the EPC, such as the servicing gateway (SGW), via the S1 user plane interface (S1-U). The MeNB connects to the MT of the IAB node via the LTE-Uu air interface, the MeNB connects to the IAB donor CU-CP via the X2-C interface, and the MeNB connects to the EPC (including the SI interface user plane and the S1 interface control plane) via the S1 interface.

[0181] certainly, Figure 3The MeNB shown can be replaced with a 5G base station gNB. The LTE-Uu air interface between the MeNB and the MT of the IAB node is replaced with an NR-Uu air interface. The gNB can establish user plane and / or control plane interfaces with the 5GC. The gNB and the IAB-donor provide dual-link services for the IAB node. The gNB can act as the main base station or auxiliary base station of the IAB node. The specific role is not limited here.

[0182] Currently, the IAB network has decided to introduce a new protocol layer in the wireless backhaul link: the backhaul adaptation protocol (BAP) layer. This BAP layer is located above the radio link control (RLC) layer and can be used to implement functions such as packet routing in the wireless backhaul link and bearer mapping.

[0183] An F1 interface (or F1* interface, etc.) needs to be established between the IAB node (or IAB DU) and the host node (or IAB donor CU). This F1 interface supports user plane protocols (F1-U / F1*-U) and control plane protocols (F1-C / F1*-C).

[0184] The IAB network user plane protocol stack can be referenced. Figure 4 The user plane protocol includes one or more of the following protocol layers: General Packet Radio Service Tunneling Protocol User Plane (GTP-U) layer, User Datagram Protocol (UDP) layer, Internet Protocol (IP) layer, etc.

[0185] Through the user plane of the F1 / F1* interface, IAB nodes and IAB hosts can perform functions such as transmitting user plane data and providing downlink transmission status feedback.

[0186] The IAB network control plane protocol stack can be referenced. Figure 5 The control plane protocol includes one or more of the following protocol layers: F1 application protocol (F1AP) layer, stream control transport protocol (SCTP) layer, IP protocol layer, etc.

[0187] Through the control plane of the F1 / F1* interface, IAB nodes and IAB hosts can perform interface management, manage IAB-DUs, and perform UE context-related configurations.

[0188] Currently, each IAB node and its parent node are connected to the same IAB host, and the MT and DU of each IAB node can be considered to be managed by the same IAB host. Therefore, topology management, routing configuration, and quality of service (QoS) management in an IAB network composed of IAB nodes under an IAB host are all controlled by a single IAB host (specifically, it can be an IAB donor CU or an IAB donor CU-CP). For example, Figure 1 In the scenario shown, during the network entry process, the IAB host knows which parent node the IAB node connected to. If the IAB host is in a CU-DU separation configuration, it can also know which IAB donor DU the IAB node is connected to (i.e., the IAB donor DU the parent node is connected to). Any topology updates to the IAB node (such as adding or changing a parent node) are completed under the control of the IAB host. This means that when there is only one IAB host in the IAB network, the IAB host can know the network topology status of the IAB nodes and IAB donor DUs. Therefore, the IAB host (specifically, the IAB donor CU) can manage routing configuration in the IAB network based on the network topology status. This routing configuration includes how IAB nodes / IAB donor DUs add routing information in the BAP header to upper-layer data packets, and the configuration of the routing table for each IAB node / IAB donor DU. Furthermore, since the IAB donor CU is aware of the QoS requirements of the services provided by the IAB nodes and UEs, and the establishment, modification, and other management of the backhaul RLC channel (BH RLC CH) for each radio backhaul link are all under the control of the IAB donor CU, the QoS guarantee of data packets on the radio backhaul link is also controlled by the IAB host (specifically, the IAB donor CU). Specifically, the IAB donor CU provides QoS guarantees for data transmission by controlling the mapping relationship of data packets on the BH RLC channel of the radio backhaul link, and the mapping of the BH RLC channel for each IAB node / IAB donor DU is also executed according to the configuration provided by the IAB host (specifically, the IAB donor CU).

[0189] However, the above-described IAB host management of IAB networks only considers scenarios where a single IAB host manages the IAB network, controlling network topology, routing configuration, and BH RLC channel mapping management. When an IAB node can connect to multiple IAB hosts, or when the MT and DU of an IAB node are not managed by the same IAB host, services of one IAB node or services of a UE connected to an IAB node may need to be transmitted through several different types of nodes. Taking the example of an IAB node connecting to two IAB hosts, we can categorize these different types of nodes as follows: IAB nodes managed by IAB donor CU1 (i.e., both the MT and DU of the IAB node are connected to IAB donor CU1 and can be managed or configured by IAB donor CU1); IAB nodes managed by IAB donor CU2 (i.e., both the MT and DU of the IAB node are connected to IAB donor CU2 and can be managed or configured by IAB donor CU2); and IAB nodes jointly managed by IAB donor CU1 and IAB donor CU2 (i.e., the MT and DU of the IAB node are connected to two different IAB hosts, for example, the MT of the IAB node is connected to IAB donor CU2 and is managed or configured by IAB donor CU2, while the DU of the IAB node is connected to IAB donor CU1 and is managed or configured by IAB donor CU1).

[0190] The following describes the scenarios where an IAB node can connect to multiple IAB hosts, and where the MT and DU of an IAB node are not managed by the same IAB host:

[0191] The following describes the scenarios in which the communication method provided in the embodiments of this application is applicable:

[0192] Please see Figure 6This scenario involves an IAB node performing a cross-host node handover. In this scenario, a third IAB node can switch its connection from the source parent node (first IAB node) to the target parent node (second IAB node). The first IAB node comprises an MT portion (MT1) and a DU portion (DU1), connecting to the first host node via the DU portion (donor DU1) of the first host node, which in turn connects to the CU portion (CU1) of the first host node. Similarly, the second IAB node comprises an MT portion (MT2) and a DU portion (DU2), connecting to the second host node via the DU portion (donor DU2) of the second host node, which in turn connects to the CU portion (CU2) of the second host node. The third IAB node comprises an MT portion (MT3) and a DU portion (DU3). If multiple logical DUs are allowed within an IAB node, for example, if the third IAB node has two logical DUs: DU3a and DU3b, then the DU of the third node can specifically be DU3a or DU3b. The third IAB node can provide access services to the UE or other IAB nodes. This switching scenario can be understood as the process of a third IAB node switching from the first host node to the second host node. It can also be understood as the process of switching from one link (source link) to another link (target link).

[0193] During the cross-IAB host node switchover process of an IAB node, since both the IAB node and downstream nodes need to switch connections to the new IAB host, the execution order has many possibilities, such as top-down, bottom-up, nested, or arbitrary. Combining these various possible execution orders, the cross-host switchover process of an IAB node can be divided into four phases. Figure 6 The four stages are: initial stage, intermediate stage (option 1), intermediate stage (option 2), and final stage. During the switchover process, the initial stage can go directly to the final stage (without going through the intermediate stage), the initial stage can go through intermediate stage option 1 to the final stage, the initial stage can go through intermediate stage option 2 to the final stage, and the switchover process can also only include the transition from the initial stage to the intermediate stage, or only include the transition from the intermediate stage to the final stage; the specifics are not limited here.

[0194] Therefore, during the migration process of the entire IAB node and its subordinate UEs and IAB nodes, there may be situations where the MT and DU parts of an IAB node are connected to two different IAB host nodes, respectively. For example: Figure 6The network state shown in Intermediate Stage Option 1 can be understood as a state that can occur when the IAB node and downstream nodes perform handover in a top-down order. The network state shown in Intermediate Stage Option 2 can be understood as a state that can occur when the IAB node and downstream nodes perform handover in a bottom-up order. Specifically, for Intermediate Stage Option 1, CU1 can configure or manage Donor DU1, MT1, DU1a, DU3a, and the UE; CU2 can configure or manage Donor DU2, MT2, DU2b, and MT3. For Intermediate Stage Option 2, CU1 can manage Donor DU1, MT1, DU1a, and MT3; CU2 manages Donor DU2, MT2, DU2b, DU3b, and the UE. The specific management of IAB nodes by the host node is described above and will not be repeated here.

[0195] Please see Figure 7The scenario describes a dual-connection scenario where an IAB node connects to multiple host nodes. In scenario (a), the third IAB node is dual-connected to the networks of two IAB donors, with its DU portion connected to the first host CU. Communication between the two can include two links: one link (leg#1) includes: first host node CU (Donor1-CU), first host node DU (Donor1-DU), first IAB node MT (IAB1-MT), first IAB node DU (IAB1-DU), third IAB node MT (IAB3-MT), and third IAB node DU (IAB3-DU). The other link (leg#2) includes: first host node CU (Donor1-CU), second host node DU (Donor2-DU), second IAB node MT (IAB2-MT), second IAB node DU (IAB2-DU), third IAB node MT (IAB3-MT), and third IAB node DU (IAB3-DU). (b) In this scenario, the third IAB node is dual-connected to the networks of two IAB donors. Its subordinate child nodes, namely the fourth IAB node (specifically its DU part), can communicate with the CU of the first host node through two different links. One of the links (leg#1) includes: the first host node CU (Donor1-CU), the first host node DU (Donor1-DU), the first IAB node (including the MT (IAB1-MT) and the DU (IAB1-DU) of the first IAB node), the third IAB node (including the MT (IAB3-MT) and the DU (IAB3-DU) of the third IAB node), and the fourth IAB node (including the MT (IAB4-MT) and the DU (IAB4-DU) of the fourth IAB node). The other link (leg#2) includes: the first host node CU (Donor1-CU), the second host node DU (Donor2-DU), the second IAB node (including the MT of the second IAB node (IAB2-MT) ​​and the DU of the second IAB node (IAB2-DU)), the third IAB node (including the MT of the third IAB node (IAB3-MT) and the DU of the third IAB node (IAB3-DU)), and the fourth IAB node (including the MT of the fourth IAB node (IAB4-MT) and the DU of the fourth IAB node (IAB4-DU)).

[0196] Please see Figure 8 This application provides a schematic diagram of a top-down cross-host handover scenario. The node undergoing the handover is IAB node 2 (which can be referred to as IAB node2 or IAB2), and IAB2 can provide access and backhaul services for one or more UEs / subnodes. Figure 8 The diagram illustrates a UE1 accessing a cell served by IAB2, and a sub-node IAB3. IAB3 also has UE2 and UE3, which access the cell served by IAB3. It is understood that in practical applications, IAB2 may also have one or more grandchild nodes (IAB nodes connected to IAB2 via at least two hops of radio backhaul links), and IAB3 may serve even more UEs, sub-nodes, or grandchild nodes; specific details are not limited here.

[0197] IAB2 originates from the parent node (i.e. Figure 8 The S-parent IAB1 shown connects to the target parent node (i.e., ...) after the switch is performed. Figure 8 As shown in the diagram, after the T-parent IAB4), its downstream node IAB3, as well as UE1 and UE2, perform a handover following IAB2.

[0198] As mentioned earlier, during the handover process between IAB nodes and their host nodes, it's possible for the MT and DU portions of an IAB node to connect to two different IAB host nodes, respectively. For example... Figure 8 As shown, once the IAB2-MT handover is complete, the MT portion of IAB2 has been connected to the target IAB host (i.e., Figure 8 The T donor CU2 shown in the diagram, but the IAB2-DU portion is also linked to the source IAB host (i.e., Figure 8 As shown in the diagram, the downstream child node (IAB3) of IAB2 and the UEs (UE1, UE2, UE3) are still connected to S donor CU1. In this case, for IAB3 to transmit data packets with S node CU1, it needs to go through... Figure 8 The path shown by the curve is transmitted via IAB2 (a node jointly managed by two host nodes), IAB4, and T donor DU2 (both IAB4 and T donor DU2 belong to nodes managed by T donor CU2). In addition, the data packet will also be transmitted via the IP transport network between T donor DU2 and S donor CU1.

[0199] Please see Figure 9 This application provides a schematic diagram of a bottom-up cross-host switching scenario, the structure of which is similar to the aforementioned one. Figure 8 The architecture shown is similar and will not be described again here. Similar to the aforementioned... Figure 8 The difference is, Figure 9This is a bottom-up cross-host handover scenario. IAB2 and its subordinate nodes perform a handover from S donor CU1 to T donor CU2. IAB2 and its downstream nodes are considered a group. If the handover order is bottom-up, the downstream nodes perform the handover first, and IAB2's MT performs the handover last. In this case, if IAB3-DU, UE2, and UE3 have already switched to T donor CU2, while IAB2 is still connected to S-parent IAB1, although IAB3-DU is now managed by T donor CU2, and the control plane of the IAB3-MT portion is still connected to S donor CU1, the data and signaling transmission between IAB3-DU and T donor CU2 needs to be transmitted via nodes controlled by S donor CU1 (IAB2, IAB1, S donor DU1) (see [link]). Figure 9 The path indicated by the curve in the diagram is such that such a transmission path may also include nodes controlled by two different host nodes.

[0200] Please see Figure 10 This is another schematic diagram of a dual-homed connection scenario in an embodiment of this application. The structure in this scenario is the same as described above. Figure 8 The architecture shown is similar and will not be described again here. Similar to the aforementioned... Figure 8 and Figure 9 The difference is, Figure 10 This is a dual-homed connection scenario. Specifically, IAB2 first connects to the first parent node (i.e., ...). Figure 10 A connection is established with the S-parent IAB1 shown in the diagram, and then a secondary station is added to connect with the second parent node (i.e., Figure 10 A connection is established between the first parent node and the first host node (i.e., T-parent IAB4). Figure 10 As shown in the diagram, S donor CU1), the second parent node is connected to the second host node (i.e. Figure 10 The T donor CU2 is shown in the diagram. The DU portion of IAB2 is connected to the S donor CU1, but the MT portion of IAB2 accesses both the cell served by IAB1 (specifically, the DU portion of IAB1) and the cell served by IAB4 (specifically, the DU portion of IAB4). The child nodes and downstream UEs of IAB2 maintain connections with the S donor CU1. Therefore, services of UEs served by IAB2, as well as services of IAB3 (including services of downstream UE2 and UE3), can be transmitted via IAB2, IAB4, and T donor DU2.

[0201] Understandably, in practical applications, Figures 6 to 10The architecture can also include more IAB nodes and / or more host nodes. Furthermore, the IAB network can be divided into more segments, each managed by a different host node.

[0202] Question 1: Regarding the above Figures 6 to 10 In scenarios involving wireless backhaul networks, there is a need to connect IAB nodes controlled by different host nodes to form a transmission path for service transmission. On such wireless backhaul paths, how to perform routing management and configuration of the IAB network, and wireless bearer mapping, to ensure that data packets are correctly routed and transmitted in this cross-host network topology, and that reasonable QoS guarantees are provided during transmission.

[0203] To address issue 1, this application provides a communication method (see details in the embodiments below). Figure 11 and Figure 12 The overall solution (as described in the corresponding embodiment) is as follows: the first BAP routing identifier is information used for packet routing in the first network segment composed of IAB nodes controlled by the first host node, while the second BAP routing identifier is information used for packet routing in the second network segment composed of IAB nodes controlled by the second host node. The first IAB node (i.e., the boundary node) can be regarded as a proxy node of the BAP layer in the two networks, responsible for converting the BAP routing identifier of the data packet in the two network segments, thereby enabling the data packet to be transmitted normally in the two networks.

[0204] The communication method in the embodiments of this application is described below.

[0205] Please see Figure 11 One embodiment of the communication method in this application includes steps 1101 to 1106.

[0206] In the embodiments of this application, Figure 11 The communication method shown is applied to the downlink transmission of data packets. For ease of understanding, it is combined with... Figure 8 The architecture is described. Therefore, the first IAB node in this embodiment is... Figure 8In the IAB2 configuration, the parent node of the first IAB node is IAB4, the child node of the first IAB node is IAB3, the first host node is T donor (including Tdonor CU2 and T donor DU2), and the second host node is S donor (including S donor CU1 and S donor DU1). The first and second host nodes are different. The first host node (CU2) manages the first network segment, which includes Tdonor, the T IAB parent node (i.e., IAB4), and the MT portion of the first IAB node (i.e., IAB2-MT). The second host node (CU1) manages the second network segment, which includes S donor, the DU portion of the first IAB node (i.e., IAB2-DU), and the child node of the first IAB node (IAB3).

[0207] For downlink transmission, the previous hop node of the first IAB node is its parent node (IAB4), and the next hop node is its child node (IAB3). The first IAB node (IAB2) is located in both the first and second network segments. It can also be understood that the first IAB node (IAB2) is managed by the first host node (T donor) and the second host node (S donor). Specifically, the MT portion (IAB2-MT) ​​of the first IAB node is managed by the first host node (T donor), and the DU portion (IAB2-DU) is managed by the second host node (S donor). The host node's management of the IAB node can be understood as a control plane connection (e.g., RRC connection and / or F1 connection) between the host node and the IAB node, through which necessary configurations (e.g., routing and bearer mapping related configurations) can be provided to the IAB node. It can be understood that the first IAB node (IAB2) can also be called a boundary IAB node.

[0208] In step 1101, S donor CU1 sends a downlink data packet to T donor DU2.

[0209] Optionally, S donor CU1 sends downlink data packets to T donor DU2 via the IP network, and T donor DU2 receives the downlink data packets accordingly.

[0210] In one embodiment, the downlink data packet needs to be sent to an IAB node in the second network segment, such as a data packet sent to the IAB2-DU part or a data packet sent to the DU part of IAB3. The following description uses the example of a data packet sent to the DU part of IAB3.

[0211] In step 1102, T donor DU2 adds the first BAP route identifier to the downlink data packet to obtain the first data packet.

[0212] T donor DU2 (hereinafter referred to as DU2) can add a first BAP route identifier to downlink packets based on the configuration information provided by T donor CU2. Therefore, before T donor DU2 adds a first BAP route identifier to downlink packets, T donor CU2 (hereinafter referred to as CU2) needs to configure DU2 first. The configuration of DU2 by CU2 may include: assigning a BAP layer identifier (BAP address) to DU2, establishing or modifying the configuration information required for BH RLC CH between DU2 and its child node (e.g., IAB4), providing routing configuration for downlink transmission for DU2, and configuring BH RLC CH mapping between DU2 and the next-hop node (e.g., IAB4).

[0213] Optionally, the configuration information required for the BH RLC CH may include at least one of the following: the BH RLC CH identifier, the QoS parameters corresponding to the BH RLC CH, and the priority corresponding to the BH RLC CH.

[0214] Optionally, the routing configuration for downlink transmission may include: the mapping between IP header information and the first BAP route identifier, the mapping between the first BAP route identifier and the identifier of the next hop node (e.g., the identifier of IAB4), etc.

[0215] Optionally, the BH RLC CH mapping configuration between DU2 and the next-hop node (e.g., IAB4) can be a mapping relationship from IP header information to BH RLC CH.

[0216] Optionally, the aforementioned IP header information includes at least one of the following: source IP address, destination IP address, differentiated services code point (DSCP), and flow label. The flow label is the flow label field in the IPv6 packet header.

[0217] Optionally, in configuring the BH RLC CH mapping between DU2 and the next-hop node (e.g., IAB4), when CU2 indicates the mapping relationship from IP header information to BH RLC CH to DU2, the BH RLC CH can be identified by the identifier of the next-hop node (e.g., the BAP layer identifier of IAB4) and the identifier of a BH RLC CH (i.e., BH RLC CH ID).

[0218] If the aforementioned downlink data packet is to be sent to the IAB2-DU portion, in order for CU2 to correctly configure DU2, CU2 needs to know the third mapping relationship, and thus can configure the correct first BAP route identifier to DU2. The third mapping relationship is the correspondence between the IP address of the DU (e.g., IAB2-DU) in the first IAB node and the BAP address of the MT (e.g., IAB2-MT) ​​in the first IAB node. If the aforementioned downlink data packet is to be sent to a downstream node of IAB2 (e.g., the IAB3-DU portion), in order for CU2 to correctly configure DU2, CU2 needs to know the fourth mapping relationship, and thus can configure the correct first BAP route identifier to DU2. The fourth mapping relationship is the correspondence between the BAP address of the MT (e.g., IAB2-MT) ​​in the first IAB node and the IP address of the DU in the downstream node of the first IAB node (e.g., IAB3).

[0219] There are three ways to obtain the third correspondence in CU2, which are described below:

[0220] 1. Since CU2 manages IAB2-MT, on the one hand, CU2 can assign BAP addresses to IAB2-MT. On the other hand, IAB2-MT can inform CU2 of the IP address of IAB2-DU through radio resource control (RRC) messages. Therefore, CU2 can obtain the IP addresses of IAB2-DUs co-deployed with IAB2-MT, and thus obtain a third-party mapping relationship.

[0221] 2. Since CU2 manages IAB2-MT, on the one hand, CU2 can allocate BAP addresses to IAB2-MT. On the other hand, IAB2-MT can request IP addresses for IAB2-DU via radio resource control (RRC) messages from CU2. Therefore, CU2 can send the IP addresses allocated to IAB2-DU to IAB2-MT via RRC messages, thus CU2 can naturally obtain the IP addresses of IAB2-DUs co-deployed with IAB2-MT, and thereby obtain the third-party mapping relationship.

[0222] 3. Since CU1 manages IAB2-DU, on the one hand, CU1 knows the IP address of IAB2-DU. On the other hand, IAB2-DU can obtain the BAP address (or BAP layer identifier) ​​configured by CU2 for IAB2-MT from IAB2-MT, and inform CU1 of the BAP address of IAB2-MT (for example, by including it in an F1AP message). Therefore, CU1 can obtain the BAP address of IAB2-MT and the IP address of IAB2-DU, and thus obtain the third mapping relationship. CU1 then sends this third mapping relationship to CU2. Specifically, CU1 can send the third mapping relationship to CU2 in an XnAP message. For example, CU1 may include the BAP address of IAB2-MT and one or more IP addresses of the DU portion of IAB2 in the XnAP message sent to CU2.

[0223] CU2 obtains the fourth mapping relationship as follows: IAB2-DU can obtain the BAP address (or BAP layer identifier) ​​configured by CU2 for IAB2-MT from IAB2-MT, and inform CU1 of the BAP address of IAB2-MT through the F1AP message. Since the downstream nodes of IAB2 are managed by CU1, CU1 can know which downstream nodes IAB2 has and the IP addresses of the DU portion of these downstream nodes, and thus determine the fourth mapping relationship. CU1 then informs CU2 of the fourth mapping relationship. Specifically, CU1 can send the fourth mapping relationship to CU2 in an XnAP message. For example, the XnAP message sent by CU1 to CU2 may include the identifier of IAB2-MT (e.g., the BAP address) and the IP addresses of one or more downstream nodes of IAB2 (specifically, the IP addresses of the DU portion of these downstream nodes). Of course, CU1 can also send other identifiers of IAB2-MT (such as the identifier assigned to IAB2-MT on the Xn interface, i.e., UE XnAP ID) and the IP address of the DU part in the downstream node of IAB2 to CU2. CU2 can determine IAB2-MT based on the other identifiers of IAB2-MT in the XnAP message. Since it has assigned the BAP address to IAB2-MT, CU2 can then determine the fourth correspondence.

[0224] DU2 receives downlink data packets, selects a first BAP route identifier based on the configuration performed on DU2 by CU2 and the IP header information of the downlink data packets, and adds the first BAP route identifier to the header information of the BAP layer to obtain the first data packet.

[0225] The first BAP route identifier in this embodiment includes the first BAP address and / or the first path identifier.

[0226] Optionally, if the first BAP route identifier includes the first BAP address, in Figure 11 In the process of transmitting downlink data packets as shown, the first BAP address is the BAP address of the last hop node in the first network segment (which can also be understood as the destination IAB node in the first network segment). For Figure 8 In the architecture shown, since it is a downlink transmission, the first BAP address used in the first network segment is the BAP address of the destination IAB node in the first network segment, that is, the BAP address of IAB2.

[0227] Optionally, for Figure 8 In this context, the first BAP address is the BAP address of IAB2, and the first path identifier is the downlink transmission path identifier between DU2 and IAB2.

[0228] In step 1103, T donor DU2 sends the first data packet to IAB2 via IAB4, and IAB2 receives the first data packet accordingly.

[0229] After DU2 receives the first data packet, it determines the BH RLC CH of the egress link based on the configuration of DU2 by CU2 in step 1102 and the IP header information of the first data packet, and sends the first data packet to IAB4 through the BH RLC CH of the egress link. Specifically, it can be that T donor DU2 sends the first data packet to MT in IAB4.

[0230] Since IAB4 is managed by CU2, CU2 can provide downlink transmission routes and BH RLC CH mapping configurations for IAB4. The downlink transmission routes can be the mapping relationship between the first BAP route identifier and the identifier of the next-hop node (e.g., IAB2). The BH RLC CH mapping configuration can be the mapping relationship between the BH RLC CH of the ingress link between IAB4 and the previous hop node (e.g., DU2) and the BH RLC CH of the egress link between IAB4 and the next hop node (e.g., IAB2).

[0231] IAB4 receives the first data packet, determines the BH RLC CH of the egress link based on the configuration of IAB4 by CU2 and the first data packet, and sends the first data packet to IAB2 through the BH RLC CH of the egress link.

[0232] IAB2 receives the first data packet sent by the previous hop node (i.e., IAB4) in the first network segment.

[0233] In step 1104, IAB2 obtains the first correspondence.

[0234] The first correspondence in this embodiment includes the correspondence between data packets (which may be BAP routing identifiers and / or IP header information in the data packets) and second BAP routing identifiers. That is, the first correspondence may include the correspondence between the first BAP routing identifier and the second BAP routing identifier in the first data packet, and / or the first correspondence may include the correspondence between the IP header information in the first data packet and the second BAP routing identifier. The second BAP routing identifier contains a second BAP address and a second BAP path identifier, used for routing from IAB2 to its downstream nodes on the wireless backhaul link in the second network segment. This second BAP routing identifier can indicate a transmission path from IAB2 to its downstream nodes in the second network segment. The aforementioned IP header information may specifically refer to any one or more of the following: source IP address, destination IP address, DSCP, and flow label.

[0235] Furthermore, the first correspondence may also include at least one of the following:

[0236] 1. Indication information, which indicates that the first correspondence is used for uplink and / or downlink transmission. Specifically, for uplink transmission, the previous hop node of the boundary IAB node (i.e., IAB2) is a child node of IAB2, and the next hop node of IAB2 is its parent node. For downlink transmission, the previous hop node of IAB2 is its parent node, and the next hop node of IAB2 is its child node. For example, the indication information is used to indicate the specific transmission direction to which the first correspondence applies. For instance, if the first correspondence includes the correspondence between the first BAP route identifier and the second BAP route identifier in the first data packet, the indication information can indicate whether the correspondence between the first BAP route identifier and the second BAP route identifier applies to uplink transmission or downlink transmission, or both. Alternatively, if the first correspondence includes the correspondence between the IP header information and the second BAP route identifier in the first data packet, the indication information can be used to indicate whether the correspondence between the IP header information and the second BAP route identifier applies to uplink transmission or downlink transmission, or both.

[0237] 2. An identifier related to the first network segment, which corresponds to the first BAP routing identifier. For example, the identifier of the host node (specifically, the host CU or host CU-CP) to which the first network segment belongs, corresponding to the first BAP routing identifier. In this embodiment, the identifier of the host node can be the gNB ID of the host node, or the IP address of the host CU or host CU-CP, or other identifiers assigned to the host CU or host CU-CP by the network management (OAM). For example, the previous hop node is in the first network segment, and the next hop node is in the second network segment. The identifier related to the first network segment, corresponding to the first BAP routing identifier, can be understood as one or more nodes on the transmission path determined by the first BAP routing identifier located in the first network segment. The first BAP routing identifier is used to identify a transmission path to the first IAB node in the first network segment.

[0238] 3. An identifier related to the second network segment, which corresponds to the second BAP route identifier. For example, the identifier of the host node (specifically, the host CU) to which the second network segment belongs, corresponding to the second BAP route identifier. The identifier related to the second network segment, corresponding to the second BAP route identifier, can be understood as indicating that one or more nodes on the transmission path determined by the second BAP route identifier are located in the second network segment. This second BAP route identifier is used to identify a transmission path from the first IAB node to a target node in the second network segment.

[0239] 4. Previous-hop node identifier, which corresponds to the first BAP route identifier. The correspondence between the previous-hop node identifier and the first BAP route identifier can be understood as follows: the previous-hop node is the node preceding the first IAB node in the transmission path indicated by the first BAP route identifier.

[0240] 5. Next-hop node identifier, which corresponds to the second BAP route identifier. The next-hop node identifier corresponds to the first BAP route identifier, and can be understood as: the next-hop node is the node following the first IAB node in the transmission path indicated by the first BAP route identifier.

[0241] Of course, the first correspondence can include multiple scenarios from the above-mentioned cases. For example, the first correspondence can include the CU identifier of the first network segment corresponding to the first BAP route identifier, and the CU identifier of the second network segment corresponding to the second BAP route identifier. And / or, the first correspondence can also include the identifier of the previous hop node corresponding to the first BAP route identifier, and the identifier of the next hop node corresponding to the second BAP route identifier.

[0242] It is understandable that the above situations are just examples, and in practical applications, other content may also be included, which is not limited here.

[0243] Furthermore, the various scenarios mentioned above and the first correspondence can be represented by the same correspondence (e.g., the first correspondence), or by different information (e.g., the first correspondence and an indication message). If different information is used, it is generally configured by the same host node.

[0244] The previous hop node identifier or next hop node identifier (hereinafter referred to as the previous / next hop node identifier) ​​in the embodiments of this application can be the BAP address of the previous / next hop node, or the IP address of the previous / next hop node. In practical applications, there may be other cases. For example, when the previous / next hop node is a child node of IAB node 2, the identifier of the child node can be the C-RNTI of the child node and the identifier of the cell accessed by the child node, or the control plane identifier of the child node on the F1 interface between IAB node 2 and the host node (the body can be the host CU or the host CU-CP) (such as the gNB-DU UE F1AP ID assigned by IAB node 2 to the child node, and / or the gNB-CU UE F1AP ID assigned by the host CU to the child node). The specific form of the identifier is not limited here.

[0245] Since the MT and DU of IAB2 are controlled by different IAB host nodes, IAB2-MT can connect to CU2 via RRC, while IAB2-DU can connect to CU1 via F1. Therefore, the routing configuration required by this IAB2 node can be configured by CU1 or CU2. That is, in this embodiment, there are two ways for IAB2 to obtain the first correspondence, which are described below:

[0246] 1. CU1 determines the first correspondence and sends the first correspondence to IAB2. This can also be understood as CU1 configuring the first correspondence for IAB2.

[0247] CU2 informs CU1 of the mapping between the IP header information configured by CU2 for DU2 and the first BAP routing identifier. CU2 can convey this mapping to CU1 via XnAP messages. Therefore, CU1 knows which IAB node it manages (e.g., IAB3, specifically the DU part of IAB3) the destination IP address in the IP header information corresponds to. CU1 can then determine the BAP address (or second BAP address, e.g., the BAP address of IAB3) in the second BAP routing identifier to which this IP header information or the first BAP routing identifier will be mapped. The second BAP path identifier (or second BAP routing ID) in the second BAP routing identifier can be determined by CU1 itself, for example, CU1 can determine a path to IAB3 based on the load and / or link quality of the second network segment. Furthermore, by determining the BAP address and the second path identifier in the second BAP routing identifier, CU1 determines the second BAP routing identifier. Combining the IP header information obtained from CU2 with the information of the first BAP route identifier, CU1 can determine the first correspondence and send the first correspondence to IAB2. Correspondingly, IAB2 receives the first correspondence sent by CU1.

[0248] Optionally, CU1 sends the first correspondence to IAB2-DU via F1AP.

[0249] 2. CU2 determines the first correspondence and sends the first correspondence to IAB2. This can also be understood as CU2 configuring the first correspondence for IAB2.

[0250] In this possible approach, CU1 needs to send one or more BAP route identifiers allocated by CU1 in the second network segment to CU2. These one or more BAP route identifiers indicate one or more transmission paths from IAB2 to its downstream nodes in the second network segment, including a second BAP route identifier. Additionally, CU1 needs to send the mapping relationship between the IP addresses and BAP addresses of the downstream nodes of the IAB2 node to CU2. Since CU2 has pre-determined the IP address of IAB3 in the IP header information when configuring how to determine the first BAP route identifier based on the IP header information for the donor DU2, CU2 can determine that the IAB node corresponding to the first BAP route identifier is a downstream node of IAB2 (taking IAB3 as an example). Combining the mapping relationship between the IP address and BAP address of IAB3 sent by CU1, CU2 can further determine the BAP address of IAB3 in the second network segment. Then, it selects a second BAP route identifier from one or more BAP route identifiers provided by CU1 that include the BAP address of IAB3, and maps the second BAP route identifier to the first BAP route identifier to obtain the first mapping relationship. Then, CU2 sends the first correspondence to IAB2, and IAB2 receives the first correspondence sent by CU2.

[0251] Optionally, CU2 sends the first mapping relationship to IAB2-MT via RRC messages.

[0252] In step 1105, IAB2 replaces the first BAP route identifier in the first data packet with the second BAP route identifier according to the first correspondence, and obtains the second data packet.

[0253] After IAB2 obtains the first correspondence and the first data packet, IAB2 can replace the first BAP route identifier in the first data packet with the second BAP route identifier according to the first correspondence to obtain the second data packet.

[0254] Optionally, before IAB2 replaces the first BAP route identifier in the first data packet with the second BAP route identifier, the IAB node can determine whether the first data packet meets the preset conditions. If the first data packet meets the preset conditions, then IAB2 replaces the first BAP route identifier in the first data packet with the second BAP route identifier.

[0255] Optionally, before IAB2 replaces the first BAP route identifier in the first data packet with the second BAP route identifier, the IAB node can determine whether the BAP address in the first BAP route identifier in the first data packet is the BAP address of IAB2, and whether the first data packet meets the preset conditions.

[0256] Optionally, if the BAP address in the first BAP route identifier in the first data packet is the BAP address of IAB2, and it is determined that the first data packet meets the preset conditions, then IAB2 replaces the first BAP route identifier in the first data packet with the second BAP route identifier according to the first correspondence, thus obtaining the second data packet.

[0257] In another alternative approach, IAB 2 can also, when the first data packet meets the preset conditions (without first determining whether the BAP address contained in the first data packet is the BAP address of IAB 2), replace the first BAP route identifier in the first data packet with the second BAP route identifier according to the first correspondence, to obtain the second data packet.

[0258] Optionally, if the BAP address in the first BAP routing identifier of the first data packet is the BAP address of IAB2, and the first data packet does not meet the preset conditions, then IAB2 will hand over the first data packet to the upper protocol layer of the IAB2 BAP layer for reception and processing.

[0259] The preset conditions in the embodiments of this application may include at least one of the following:

[0260] 1. The first data packet includes indication information, which is used by IAB2 to determine that the first data packet meets preset conditions. This indication information may refer to the first data packet carrying a special BAP path identifier, the first data packet carrying a special BAP address, the presence or specific value of special bits in the BAP layer header information of the first data packet, or the destination IP address in the first data packet not being the IP address of IAB2, etc.

[0261] 2. The first BAP route identifier carried in the first data packet is consistent with the BAP route identifier in the first correspondence.

[0262] It is understandable that the above two examples are just examples. In practical applications, there may be other preset conditions, which are not limited here.

[0263] In this embodiment of the application, IAB2 determines that the first data packet meets the preset conditions. This can be understood as the first data packet including indication information, and IAB2 determines that the first data packet meets the preset conditions based on the indication information.

[0264] In one possible embodiment, if the indication information is a special BAP address, IAB2 can be configured with at least two BAP addresses (such as BAP address 2A and BAP address 2B). When the BAP address contained in the BAP routing identifier portion of the data packet is BAP address 2A, after receiving the data packet, IAB2 can remove the BAP header from the data packet and submit it to the upper protocol layer (e.g., the IP layer). When the BAP address contained in the BAP routing identifier portion of the data packet is BAP address 2B, after receiving the data packet, IAB2 can replace the BAP routing identifier in the BAP header of the data packet with a second BAP routing identifier to obtain a second data packet. Optionally, IAB2 can receive configuration information from CU1 or CU2, which indicates that BAP address 2B is a special BAP address for IAB2 (for example, when CU2 configures BAP address 2B for IAB2 via an RRC message, it carries indication information indicating that the address is a special BAP address).

[0265] In another possible embodiment, if the indication information is a special BAP path identifier, then IAB2 can be configured with at least one special BAP path identifier (such as BAP path ID 2X). When the BAP path identifier contained in the BAP routing identifier portion of the data packet is a path identifier other than BAP path ID 2X, after receiving the data packet, IAB2 can remove the BAP layer header from the data packet and submit it to the upper protocol layer (e.g., the IP layer). When the BAP path identifier contained in the BAP routing identifier portion of the data packet is BAP path ID 2X, after receiving the data packet, IAB2 can replace the BAP routing identifier in the BAP layer header of the data packet with a second BAP routing identifier to obtain a second data packet. Optionally, IAB2 can receive configuration information from CU1 or CU2, which is used to indicate that BAP path ID 2X is a special BAP path identifier for IAB2 (for example, when CU1 configures the routing table entry corresponding to the BAP route identifier carrying BAP path ID 2X for IAB2 via F1AP message, it carries indication information to indicate that the path identifier is a special BAP path identifier).

[0266] Optionally, when the indication information indicates that the destination IP address in the first data packet is not the IP address of IAB2, IAB2 can obtain the destination IP address of the first data packet when stripping the BAP layer of the first data packet, and thus determine that the first data packet meets the preset conditions.

[0267] In another possible embodiment, IAB2 determining that the first data packet meets the preset conditions may include: IAB2 determining that the first data packet meets the preset conditions based on a first correspondence. For example, IAB2 determines whether the first data packet meets the preset conditions based on whether the first BAP routing identifier in the first correspondence matches the BAP routing identifier carried in the first data packet. Specifically, when the BAP routing identifier in the first data packet matches the first BAP routing identifier in the first correspondence, after receiving the first data packet, IAB2 can replace the BAP routing identifier in the BAP layer header of the first data packet with a second BAP routing identifier to obtain the second data packet. When the BAP routing identifier in the first data packet is inconsistent with the first BAP routing identifier in the first correspondence: After IAB2 receives the first data packet, if the BAP address portion of the BAP routing identifier in the first data packet is the same as the BAP address of IAB2, then IAB2 can remove the BAP layer header from the first data packet and submit it to the upper protocol layer (e.g., IP layer). Alternatively, if the BAP address portion of the BAP routing identifier in the first data packet is different from the BAP address of IAB2, then IAB2 can select a suitable next-hop node based on the BAP routing identifier in the first data packet and the configured routing table, and forward the first data packet to that next-hop node. The step of determining whether the BAP address portion of the BAP routing identifier in the first data packet is the same as the BAP address of IAB2 can be performed before or after determining whether the BAP routing identifier in the first data packet is the same as the first BAP routing identifier in the first correspondence. In this method, IAB2 can directly determine whether the first data packet is sent to the second network segment or submitted to the upper protocol layer based on the first correspondence. Compared with other methods (such as the aforementioned two BAP addresses or special BAP path identifiers), this method can reduce additional configuration overhead.

[0268] Optionally, after obtaining the second data packet, IAB2 can select a suitable next-hop node based on the second BAP route identifier in the second data packet and the configured routing table, and then forward the second data packet to that next-hop node.

[0269] The aforementioned preset conditions or indication information may be agreed upon through a protocol, or may be made known to IAB2 by sending control plane messages to IAB2 through CU1 and / or CU2 to carry indications of the aforementioned preset conditions. No specific limitation is made here.

[0270] In this embodiment of the application, from the perspective of the internal processing of IAB2, there are many ways for IAB2 to replace the first BAP route identifier in the first data packet with the second BAP route identifier according to the first correspondence, which are described below:

[0271] 1. IAB2-MT removes the first BAP route identifier and adds the second BAP route identifier.

[0272] IAB2 receives the first data packet sent by IAB4 in the first network segment. Specifically, the receiving part of the BAP entity of IAB2-MT receives the first data packet sent by DU in IAB4. If IAB2-MT determines that the BAP address in the first data packet is its own BAP address (i.e., the BAP address obtained by IAB2), and determines that the first data packet meets the preset conditions, then IAB2-MT removes the first BAP routing identifier (or the first BAP address in the first BAP routing identifier) ​​from the first data packet, determines the second BAP routing identifier according to the first correspondence, and then adds the second BAP routing identifier to the data packet to obtain the second data packet.

[0273] 2. Remove the first BAP route identifier from IAB2-MT and add the second BAP route identifier to IAB2-DU.

[0274] IAB2 receives the first data packet sent by IAB4 in the first network segment. Specifically, the receiving part of the BAP entity of IAB2-MT receives the first data packet sent by DU in IAB4. If IAB2-MT determines that the BAP address in the first data packet is its own BAP address (i.e., the BAP address obtained by IAB2), and determines that the first data packet meets the preset conditions, then IAB2-MT removes the first BAP routing identifier (or the first BAP address in the first BAP routing identifier) ​​from the first data packet, and then hands the first data packet with the first BAP routing identifier removed to the IAB2-DU side. After receiving the first data packet with the first BAP routing identifier removed, IAB2-DU adds a second BAP routing identifier to the data packet according to the first correspondence, thus obtaining the second data packet.

[0275] It is understandable that in the above process, the data packet received by IAB2-DU is the first data packet without the first BAP route identifier. Therefore, IAB2-DU can obtain the first BAP route identifier of the first data packet from IAB2-MT, and then determine the second BAP route identifier based on the first BAP route identifier. Alternatively, IAB2-DU can directly determine the second BAP route identifier based on the IP header information of the data packet.

[0276] 3. IAB2-DU removes the first BAP route identifier and adds the second BAP route identifier.

[0277] IAB2 receives the first data packet sent by IAB4 in the first network segment. Specifically, the receiving part of the BAP entity of IAB2-MT receives the first data packet sent by DU in IAB4. IAB2-MT forwards the first data packet directly to IAB2-DU. If IAB2-DU determines that the BAP address in the first data packet is its own BAP address (i.e., the BAP address of IAB2, specifically the BAP address obtained by IAB2-MT), and determines that the first data packet meets the preset conditions, then IAB2-DU removes the first BAP routing identifier (or the first BAP address in the first BAP routing identifier) ​​from the first data packet, determines the second BAP routing identifier according to the first correspondence, and then adds the second BAP routing identifier to the data packet to obtain the second data packet.

[0278] Optionally, IAB2-MT can inform IAB2-DU of its obtained BAP address through the node's internal interface, so that IAB2-DU can determine whether the BAP address in the first data packet is its own BAP address.

[0279] It is understandable that there are many ways to change the BAP route identifier in IAB2. The above are just examples. In practical applications, there are other ways to change the BAP route identifier in IAB2: for example, IAB2-DU removes the first BAP route identifier, and IAB2-MT adds the second BAP route identifier. The specifics are not limited here.

[0280] In step 1106, IAB2 sends a second data packet to IAB3, and correspondingly, IAB3 receives the second data packet sent by IAB2.

[0281] Optionally, after IAB2 receives the first data packet and before sending the second data packet to its child node (IAB3), IAB2 can determine whether it needs to forward the second data packet to the next-hop node in the second network segment. If the first data packet meets preset conditions, then IAB2 sends the second data packet to the next-hop node (IAB3) in the second network segment. For downlink transmission, the next-hop node of IAB2 is its child node.

[0282] Optionally, IAB2 may determine, either after deleting the first BAP identifier of the first data packet or before deleting the first BAP identifier of the first data packet, whether to hand over the first data packet stripped of its BAP layer to the upper protocol layer for processing, or to continue forwarding it to the next-hop node in the second network segment. If the first data packet meets a preset condition, IAB2 sends the second data packet to the next-hop node (IAB3) in the second network segment. For a description of the first data packet meeting the preset condition, please refer to the relevant description in step 1105; details will not be repeated here.

[0283] In this embodiment, the preset condition can be understood as the condition for IAB2 to send the second data packet to IAB3, or it can be understood as the condition for IAB2 to replace the first BAP route identifier in the first data packet with the second BAP route identifier. The specific condition is not limited here.

[0284] Optionally, before sending the second data packet to its child nodes, IAB2 can also obtain a second mapping relationship. IAB2 then determines, based on the second mapping relationship, to send the second data packet to IAB3 through the first backhaul RLC channel (first BHRLC CH) of the egress link in the second network segment. That is, IAB2 selects a suitable RH RLCCH of the egress link for the data packet to be transmitted, thereby ensuring the QoS requirements of the transmission.

[0285] In this application embodiment, there are several cases of the second correspondence relationship, which are described below:

[0286] 1. The second correspondence is the correspondence between the first BAP route identifier and the BH RLCCH of the exit link of the first IAB node (i.e., IAB2).

[0287] 2. The second correspondence is the correspondence between the second BAP route identifier and the BH RLCCH of the exit link of the first IAB node (i.e., IAB2).

[0288] 3. The second correspondence is the correspondence between the IP header information in the first data packet and the BH RLC CH of the egress link of the first IAB node (i.e., IAB2). Specifically, the IP header information can refer to any one or more of the following: source IP address, destination IP address, DSCP, and flow label.

[0289] 4. The second correspondence is the correspondence between the second backhaul RLC channel of the ingress link of the first IAB node (i.e., IAB2) and the first backhaul RLC channel of the egress link of the first IAB node (i.e., IAB2). Specifically, it can be the correspondence between the second BH RLC CH of the ingress link of the first IAB node (i.e., IAB2) and the first BH RLC CH of the egress link of the first IAB node (i.e., IAB2).

[0290] In this application, for downlink transmission: the ingress link of an IAB node refers to the link between the IAB node and the previous hop node (such as a parent node), for example, the link between IAB2 and IAB4 is the ingress link of IAB2 in downlink transmission; the egress link refers to the link between the IAB node and the next hop node (such as a child node), for example, the link between IAB2 and IAB3 is the egress link of IAB2 in downlink transmission. For uplink transmission: the ingress link of an IAB node refers to the link between the IAB node and the previous hop node (such as a child node), for example, the link between IAB2 and IAB3 is the ingress link of IAB2 in uplink transmission; the egress link refers to the link between the IAB node and the next hop node (such as a parent node), for example, the link between IAB2 and IAB4 is the egress link of IAB2 in uplink transmission.

[0291] Optionally, since there may be multiple CHs on a link, in order to correctly identify the BH RLC CH of the link, the BH RLC CH of the ingress link can be jointly marked by the identifier of the ingress link (which can be the identifier of the previous hop node) and the BH RLC CH ID assigned on the ingress link, and the BH RLC CH of the egress link can be jointly marked by the identifier of the egress link (which can be the identifier of the next hop node) and the BH RLC CH ID assigned on the egress link.

[0292] It is understandable that there are multiple cases of the second correspondence obtained by IAB2, or that there are multiple cases of the second correspondence. It is also understandable that there may be other cases in practical applications, which are not limited here.

[0293] In this embodiment, the IAB node obtaining the correspondence can be understood as follows: the configuration information received by the IAB node from CU1 / CU2 contains two pieces of information, and the IAB node can assume that there is a correspondence between these two pieces of information. Alternatively, the standard predefines the correspondence in the IAB node. For example, the four cases described above for IAB2 to obtain the second correspondence can be understood as the following four descriptions:

[0294] 1. IAB2 receives control plane messages sent by CU1 / CU2, which include the first BAP route identifier and the identifier of the first backhaul RLC channel of the first IAB node egress link corresponding to the first BAP route identifier, thereby obtaining the second correspondence.

[0295] 2. IAB2 receives the control plane message sent by CU1 / CU2, which includes the second BAP route identifier and the identifier of the first backhaul RLC channel of the first IAB node egress link corresponding to the second BAP route identifier, thereby obtaining the second correspondence.

[0296] 3. IAB2 receives control plane messages sent by CU1 / CU2, which include first IP header information and the identifier of the first backhaul RLC channel of the first IAB node egress link corresponding to the first IP header information, thereby obtaining the second correspondence. Specifically, the first IP header information may include any one or more of the following: first source IP address, first destination IP address, first DSCP, and first flow label.

[0297] 4. IAB2 receives control plane messages sent by CU1 / CU2, which contain the identifier of the second backhaul RLC channel of the first IAB node ingress link and the identifier of the first backhaul RLC channel of the corresponding first IAB node egress link, thereby obtaining the second correspondence.

[0298] Since the MT and DU of IAB2 are controlled by different IAB host nodes, IAB2-MT can be connected to CU2 via RRC, while IAB2-DU can be connected to CU1 via F1. Therefore, the BH RLC CH mapping configuration required by the IAB2 node can be configured by CU1 or CU2. That is, there are two ways for IAB2 to obtain the second correspondence in this application embodiment, which are described below:

[0299] 1. CU1 determines the second mapping relationship and sends the second mapping relationship to IAB2. This can also be understood as CU1 configuring the second mapping relationship for IAB2.

[0300] Optionally, CU1 sends the second correspondence to IAB2-DU via F1AP.

[0301] 2. CU2 determines the second mapping relationship and sends it to IAB2. This can also be understood as CU2 configuring the second mapping relationship for IAB2.

[0302] Optionally, CU2 sends a second mapping relationship to IAB2-MT via an RRC message.

[0303] In this embodiment of the application, CU1 / CU2 sending a mapping relationship to IAB2 can be understood as CU1 / CU2 configuring IAB2. For example, CU1 / CU2 sending a first mapping relationship to IAB2 can be understood as CU1 / CU2 configuring routing for IAB2. CU1 / CU2 sending a second mapping relationship to IAB2 can be understood as CU1 / CU2 configuring RH RLC CH mapping for IAB2.

[0304] In this embodiment, the IAB network may include more network segments and be managed by multiple host nodes. The BAP address in the BAP routing identifier used to transmit data packets in each network segment is the BAP address of the last-hop node in that network segment. Specifically, in the last network segment in the data packet transmission direction, the last-hop node in that segment is the target node located in that segment. For example, in downlink transmission, the BAP address in the first BAP routing identifier of the first network segment is the BAP address of the last-hop node (IAB2) in the first network segment, while the BAP address in the second BAP routing identifier of the second network segment (i.e., the last network segment in the downlink direction) is the target node (IAB3) in the second network segment. Similarly, in uplink transmission, the BAP address in the BAP routing identifier of the last network segment in the uplink direction is the target node (i.e., the host DU) in that segment.

[0305] For example, if the IAB network includes a topology consisting of three adjacent network segments (identified as 1, 2, and 3 respectively) and each is managed by a different host node, then the BAP address of the BAP route identifier used in the second network segment is either the BAP address of the boundary node between the second network segment and the first network segment or the BAP address of the boundary node between the second network segment and the third network segment. The specific boundary node identifier used is determined according to the transmission direction.

[0306] Furthermore, if the downstream nodes of the first IAB node include multiple different IAB nodes, and the destination BAP address of the downlink data packets in the first network segment is the BAP address of the first IAB node, in order to determine the last-hop IAB node in the second network segment based on the first BAP routing identifier at the first IAB node, one possible embodiment requires the first host node to configure different BAP path identifiers in the first network segment for different downstream IAB nodes when configuring the correspondence between IP header information and the first BAP routing identifier. This ensures that the first BAP routing identifiers of data packets from different IAB nodes in the second network segment are different in the first network segment.

[0307] In this embodiment of the application, step 1104 does not necessarily have a temporal relationship with steps 1101 to 1103. That is, step 1104 can be before step 1101, before step 1102, or before step 1105.

[0308] In this application embodiment, the principle of the scheme for switching hosts sequentially from top to bottom is similar to that of the scheme for switching hosts sequentially from bottom to top, and can be referred to... Figure 11 The relevant descriptions in the illustrated embodiments are not limited here.

[0309] In this embodiment, in a scenario where the IAB network is managed by multiple IAB host nodes, the first IAB node replaces the BAP routing identifier of the data packet in the first network segment with the BAP routing identifier in the second network segment. This ensures normal transmission of the data packet in the second network segment, avoiding data packet transmission anomalies caused by the IAB network being managed by multiple IAB host nodes. This guarantees that data packets are correctly routed and provided with transmission services according to reasonable QoS guarantees in IAB networks composed of multiple network segments managed by different host nodes.

[0310] In other words, the solution in this embodiment allows each host node to control only the routing of data packets within its own network segment. Then, the boundary node between the two network segments performs (specifically, at the BAP layer or the IP layer) the proxy operation of BAP layer routing and QoS mapping. It replaces the first BAP routing identifier in the first network segment contained in the received data packet with the second BAP routing identifier that will be used for routing in the second network segment. Through this splicing routing method, it ensures that data packets can be routed reasonably and correctly in the network topology management of newly emerging cross-host base stations, and also performs reasonable BH RLC channel mapping at the boundary of the two network segments to ensure the QoS requirements of the data packets.

[0311] Please see Figure 12 Another embodiment of the communication method in this application includes steps 1201 to 1206.

[0312] In the embodiments of this application, Figure 12 The communication method shown is applied to the uplink transmission of data packets. For ease of understanding, it is similar to the one described above. Figure 11 The illustrated embodiments are similar, combined with Figure 8 The architecture is described. Therefore, the first IAB node in this embodiment is... Figure 8In the IAB2 configuration, the parent node of the first IAB node is IAB4, the child node of the first IAB node is IAB3, the first host node is S donor (including S donor CU1 and S donor DU1), and the second host node is T donor (including T donor CU2 and T donor DU2). The first and second host nodes are different. The first host node (CU1) manages the first network segment, which includes S donor, the DU portion of the first IAB node (i.e., IAB2-DU), and the child node of the first IAB (IAB3). The second host node (CU2) manages the second network segment, which includes T donor, the T IAB parent node (i.e., IAB4), and the MT portion of the first IAB node (i.e., IAB2-MT). The previous hop node of the first IAB node is the child node of the first IAB node (i.e., IAB3), and the next hop node of the first IAB node is the parent node of the first IAB node (i.e., IAB4). The first IAB node (IAB2) is located in both the first and second network segments. It can also be understood that the first IAB node (IAB2) is managed by both the second host node (T donor) and the first host node (S donor). Specifically, the MT portion (IAB2-MT) ​​of the first IAB node is managed by the second host node (T donor), and the DU portion (IAB2-DU) of the first IAB node is managed by the first host node (S donor). The host node's management of the IAB node can be understood as a control plane connection (e.g., RRC connection and / or F1 connection) between the host node and the IAB node, through which the host node can provide necessary configurations (e.g., routing and bearer mapping related configurations). It can be understood that the first IAB node (IAB2) can also be called a boundary IAB node.

[0313] In step 1201, IAB3 adds the first BAP route identifier to the uplink data packet to obtain the first data packet.

[0314] When an IAB sub-node acts as an access IAB node for a UE, IAB3 generates uplink data packets. These uplink data packets can be data packets from the F1 interface user plane (F1-U), data packets from the F1 interface control plane (F1-C), or data packets from non-F1 services, etc., without any specific limitations here.

[0315] Before IAB3 adds the first BAP route identifier to the uplink data packet, CU1 needs to configure IAB3. The configuration of IAB3 by CU1 may include one or more of the following: assigning a BAP layer identifier (BAP address) to IAB3, establishing or modifying the configuration information required for BH RLC CH between IAB3 and its parent node (e.g., IAB2), providing configuration information for routes used for uplink transmission to IAB3, and providing BH RLC CH mapping configuration for the link between IAB3 and IAB2.

[0316] Optionally, the configuration information required for the BH RLC CH may include at least one of the following: the identifier of the BH RLC CH, the configuration of the RLC layer corresponding to the BH RLC CH, the configuration of the medium access control (MAC) layer corresponding to the BH RLC CH, and the configuration of the logical channel corresponding to the BH RLC CH.

[0317] Optionally, the configuration information for the uplink transmission route may include: the correspondence between the upper-layer service data information maintained by IAB3 and the first BAP route identifier, and the routing table entry corresponding to the first BAP route identifier (i.e., the first BAP route identifier and the identifier of the corresponding next-hop node). The uplink egress link refers to the BH link between IAB3 and its parent node IAB2. The BH RLC CH of the uplink egress link can be jointly identified by the identifier of IAB2 and a BH RLC CH ID.

[0318] Optionally, the BH RLC CH mapping configuration of the link between IAB3 and IAB2 may include at least one of the following: a mapping relationship between upper-layer service data information and the BH RLC CH of the uplink egress link, and an identifier for a designated default BH RLC CH used to transmit services other than F1-U services. In this application, when configuring the mapping relationship between upper-layer service data information and the BH RLC CH of the uplink egress link, the identifier of the uplink egress link (indicated by the identifier of the next-hop node) and the identifier of a BH RLC CH (i.e., BH RLC CH ID) can be used to jointly identify a BH RLC CH of the egress link.

[0319] Optionally, the upper-layer service data information may include at least one of the following: tunnel information of the F1 interface user plane (including the uplink TEID and target IP address of the F1 interface GTP-U tunnel), UE-related F1AP messages, non-UE-related F1AP messages, non-F1 interface services, etc.

[0320] Before IAB3 adds the first BAP route identifier to the uplink data packet, CU1 needs to send configuration information to IAB3. This configuration information is used to indicate the first BAP route identifier to be added corresponding to the uplink data packet. The first BAP route identifier corresponds to the upper-layer service data information of the uplink data packet. The first BAP route identifier contains the BAP address of IAB2, which is the destination BAP address of the uplink data packet in the first network segment.

[0321] After receiving the configuration information sent by CU1, IAB3 adds a first BAP route identifier to the uplink data packet, thus obtaining the first data packet. The destination BAP address in the first BAP route identifier is the BAP address of IAB2, meaning the destination BAP address in the first BAP route identifier is the BAP address of the last hop node in the first network segment.

[0322] In step 1202, IAB3 sends a first data packet to IAB2. Correspondingly, IAB2 receives the first data packet sent by IAB3.

[0323] After IAB3 receives the first data packet, it determines the egress link and the BH RLC CH of the egress link based on the configuration of IAB3 by CU1 in step 1201 and the first BAP route identifier, and sends the first data packet to IAB2 through the BH RLC CH of the egress link. Correspondingly, IAB2 receives the first data packet. Specifically, IAB2 may receive the first data packet sent by the previous hop node (i.e., IAB3) in the first network segment.

[0324] Optionally, IAB3 sends the first data packet to IAB2, specifically, DU in IAB3 sends the first data packet to MT in IAB2.

[0325] In step 1203, IAB2 obtains the first correspondence.

[0326] In this step, the description of how IAB2 obtains the first correspondence can be found in the preceding text. Figure 11 The relevant description of step 1104 in the illustrated embodiment will not be repeated here.

[0327] Easy to understand, and Figure 11 The difference between the downlink transmission shown is that the specific content of the second BAP route identifier in this step is different. Figure 11 The content differs; for example, the BAP address (i.e., the second BAP address) contained in the second BAP route identifier in this step is the BAP address of DU2. However... Figure 11 In the illustrated embodiment, the second BAP address in the second BAP route identifier is the BAP address of IAB3.

[0328] In step 1204, IAB2 replaces the first BAP route identifier in the first data packet with the second BAP route identifier according to the first correspondence, thereby obtaining the second data packet.

[0329] In this step, IAB2 replaces the first BAP route identifier in the first data packet with the second BAP route identifier according to the first correspondence. The description of the second data packet can be found above. Figure 11 The relevant description of step 1105 in the illustrated embodiment will not be repeated here.

[0330] In one possible embodiment, besides determining whether the BAP route identifier needs to be replaced for the data packet based on the conditions in step 1105, IAB2 can also make a determination for uplink transmission in another possible way: IAB2 determines whether the BAP address in the first BAP route identifier of the first data packet is the BAP address of IAB2. If it is, it means that the first data packet needs to be forwarded to the next hop node (e.g., IAB4) in the second network segment, and the first BAP route identifier needs to be replaced; if not, then IAB2 can not change the first BAP route identifier, but directly look up the configured routing table based on the first BAP route identifier and select the appropriate next hop node; furthermore, if IAB2 cannot find the corresponding first BAP route identifier in the routing table... If the table entry matches the BAP address in the first BAP route identifier, IAB2 can further check if any entry matches the content of the first BAP address field in the first BAP route identifier. If so, the next-hop node can be selected from any matching entry. If not, IAB2 can further confirm whether a new BAP route identifier has been configured in the first BAP route identifier, or whether a new BAP address has been configured in the first BAP route identifier. If so, the first BAP route identifier / first BAP address in the first data packet can be replaced with the new BAP route identifier / new BAP address. Then, based on the replacement result, the routing table is searched to select the next-hop node. After selecting the next-hop node, the BH RLC CH for the outgoing link is selected, and the modified second data packet is sent to the next-hop node. The new BAP route identifier / new BAP address can be considered a special type of second BAP route identifier / second BAP address.

[0331] In step 1205, IAB2 sends the second data packet to T donor DU2 via IAB4, and T donor DU2 receives the second data packet accordingly.

[0332] In this embodiment, IAB2 can also obtain a second correspondence, the relevant description of which can be found in the foregoing. Figure 11 The relevant description of step 1106 in the illustrated embodiment will not be repeated here.

[0333] In this embodiment, IAB2 can also determine whether it needs to send the second data packet to IAB4 in the second network segment before sending the second data packet to IAB4. The relevant description can be found in the foregoing. Figure 11 The description of step 1106 in the illustrated embodiment will not be repeated here.

[0334] Optionally, after obtaining the second data packet and the second correspondence, IAB2 determines the BH RLCCH of the outgoing link and sends the second data packet to IAB4 through the BH RLCCH of the outgoing link. Specifically, IAB2-MT sends the second data packet to the DU of IAB4. That is, IAB2 sends the second data packet to the next-hop node (i.e., IAB4) in the second network segment.

[0335] Since IAB4 is managed by CU2, CU2 can provide IAB4 with uplink routing and BH RLC CH mapping configuration. The uplink routing can be a mapping between the second BAP route identifier and the identifier of the next-hop node (DU2). The BH RLC CH mapping configuration can be a mapping relationship between the BH RLC CH of the ingress link between IAB4 and the previous hop node (IAB2) and the BH RLC CH of the egress link between IAB4 and the next-hop node (DU2).

[0336] IAB4 receives the second data packet and, based on the configuration of IAB4 by CU2 and the second data packet, determines the BH RLC CH of the outgoing link, and then sends the second data packet to DU2 through the BH RLC CH of the outgoing link. Correspondingly, DU2 receives the second data packet sent by IAB4.

[0337] In step 1206, T donor DU2 sends IP packets to the target node.

[0338] After receiving the second data packet sent by IAB4, DU2 removes the BAP layer header information from the second data packet, and delivers the BAP layer service data unit (SDU) to the IP layer. Then, it forwards the IP data packet to the target node of the IP layer through the IP layer routing.

[0339] Optionally, if the target node is CU1, DU2 will forward the uplink data packets of the F1 interface generated by IAB3 to CU1.

[0340] In this embodiment of the application, step 1203 does not necessarily have a temporal relationship with steps 1201 and 1202. That is, step 1203 can be before step 1201 or before step 1202, and step 1203 can be before step 1204.

[0341] In this application embodiment, the principle of the scheme for switching hosts sequentially from top to bottom is similar to that of the scheme for switching hosts sequentially from bottom to top, and can be referred to... Figure 11 as well as Figure 12 The relevant descriptions in the illustrated embodiments are not limited here.

[0342] In this embodiment, in a scenario where the IAB network is managed by multiple IAB host nodes, the first IAB node replaces the BAP routing identifier of the data packet in the first network segment with the BAP routing identifier in the second network segment. This ensures normal transmission of the data packet in the second network segment, avoiding data packet transmission anomalies caused by the IAB network being managed by multiple IAB host nodes. This guarantees that data packets are correctly routed and provided with transmission services according to reasonable QoS guarantees in IAB networks composed of multiple network segments managed by different host nodes.

[0343] In other words, the solution in this embodiment allows each host node to control only the routing of data packets within its own network segment. Then, the boundary node between the two network segments performs (specifically, at the BAP layer or the IP layer) the proxy operation of BAP layer routing and QoS mapping. It replaces the first BAP routing identifier in the first network segment contained in the received data packet with the second BAP routing identifier that will be used for routing in the second network segment. Through this splicing routing method, it ensures that data packets can be routed reasonably and correctly in the network topology management of newly emerging cross-host base stations, and also performs reasonable BH RLC channel mapping at the boundary of the two network segments to ensure the QoS requirements of the data packets.

[0344] The following describes problem 2 in the prior art and the technical means adopted in the embodiments of this application:

[0345] Question 2: Regarding the aforementioned independent network formation of a single host (e.g.) Figure 1 ), IAB non-standalone networking (such as Figure 2 , Figure 3 ) and cross-host networking (such as Figure 6 , Figure 7 In scenarios where an IAB node receives a data packet, if the BAP header of the packet carries the BAP address of the IAB node and no entry in the routing table contains the destination BAP address of the packet, then the data packet is considered abnormal. However, this method of determining abnormal data packets by the IAB node does not take into account the specific circumstances of actual operation and does not consider the handling of abnormal data packets at the host DU. This may result in some abnormal packets that should be dropped not being identified and thus not being dropped, occupying the cache space of the IAB node or the host DU.

[0346] To address issue 2, this application provides a data packet processing method applicable to IAB nodes or IAB donor DUs in single-host independent networking, IAB non-standalone networking, or cross-host networking scenarios. Compared to the complex and general methods used in the prior art to determine data packet anomalies, the data packet processing method provided in this application can more accurately determine the conditions for data packet anomalies in certain specific situations (uplink and downlink data packets, IAB nodes and IAB donor DUs).

[0347] The following describes how IAB nodes or IAB donor DUs can resolve issue 2.

[0348] I. For IAB nodes.

[0349] 1. In one possible approach, the BAP layer entity of the IAB node (specifically, the receiving part located in the IAB-DU) receives an uplink data packet. If the BAP layer header of the uplink data packet carries the BAP address of the IAB node, then the IAB node determines that the uplink data packet is an erroneous or abnormal data packet.

[0350] Furthermore, once the IAB node determines that the uplink data packet is an error or an abnormal data packet, it can discard the uplink data packet.

[0351] On the one hand, it simplifies the conditions for judging uplink data packet anomalies. On the other hand, it avoids erroneous or abnormal uplink data packets occupying the cache space of the IAB node.

[0352] 2. In another possible approach, before sending a data packet, the BAP layer entity of the IAB node (specifically, the sending part of the BAP entity located on the IAB-MT or IAB-DU side) determines that the data packet is an erroneous or abnormal packet if it cannot find any entry in its routing table containing the destination BAP address of the data packet.

[0353] Furthermore, once the IAB node determines that the packet is an error or an abnormal packet, it can discard the packet.

[0354] On the one hand, simplifying the criteria for judging abnormal data packets can prevent erroneous or abnormal data packets from consuming the buffer space of the IAB node. On the other hand, it avoids the network resource consumption caused by sending erroneous or abnormal data packets.

[0355] II. Regarding IAB donor DU.

[0356] 1. In one possible scenario, the BAP layer entity of the IAB-donor DU (specifically, the receiving part) receives an uplink data packet whose BAP address in the BAP layer header is not the BAP address of the IAB-donor DU. In this case, the IAB-donor DU determines that the data packet is an erroneous or abnormal packet.

[0357] Furthermore, once the IAB-donor DU determines that the uplink data packet is an error or an abnormal packet, it can discard the uplink data packet.

[0358] On the one hand, it simplifies the conditions for judging uplink data packet anomalies. On the other hand, it avoids erroneous or abnormal uplink data packets occupying the buffer space of the IAB-donor DU.

[0359] 2. In another possible approach, the BAP layer entity of the IAB-donor-DU (specifically, the sending part) determines that the downlink data packet is an erroneous or abnormal packet if it cannot find any entry in the routing table containing the destination BAP address of the packet before sending the downlink data packet.

[0360] Furthermore, once the IAB-donor-DU determines that the downlink data packet is an erroneous or abnormal packet, it can discard the downlink data packet.

[0361] On the one hand, simplifying the criteria for judging downlink data packet anomalies can prevent erroneous or abnormal downlink data packets from consuming the IAB-donor-DU's buffer space. On the other hand, it avoids the network resource consumption caused by sending erroneous or abnormal downlink data packets.

[0362] In this embodiment, compared to the common and complex methods used in the prior art to determine data packet anomalies, the data packet processing method provided in this embodiment can simplify the conditions for determining data packet anomalies in specific situations, and more accurately identify more abnormal data packets. The related beneficial effects can be found in the description above.

[0363] The communication device in the embodiments of this application is described below. Please refer to [link / reference]. Figure 13 Another embodiment of the communication device in this application is described. The communication device can be a first IAB node or a component of the first IAB node (e.g., DU, MT, processor, chip, or chip system). This communication device is used to access an integrated IAB network for backhaul. The IAB network includes a first network segment and a second network segment. The first network segment is managed by a first host node, and the second network segment is managed by a second host node. The first host node and the second host node are different. The communication device includes:

[0364] The receiving unit 1301 is configured to receive a first data packet in a first network segment. The first data packet includes a first backhaul adaptation protocol (BAP) route identifier, which is used for the transmission of the first data packet in the first network segment.

[0365] Acquisition unit 1302 is used to acquire the first correspondence relationship;

[0366] The replacement unit 1303 is used to replace the first BAP route identifier in the first data packet with the second BAP route identifier according to the first correspondence relationship, so as to obtain the second data packet;

[0367] The sending unit 1304 is used to send a second data packet to the next-hop node in the second network segment. The next-hop node is either the parent node or the child node of the first IAB node.

[0368] In this embodiment, the operations performed by each unit in the communication device are the same as those described above. Figure 11 and Figure 12 The operations performed by the first IAB node (i.e., IAB2) in the illustrated embodiment are similar and will not be described again here.

[0369] In this embodiment, in a scenario where the IAB network is managed by multiple IAB host nodes, the replacement unit 1303 replaces the BAP routing identifier of the data packet in the first network segment with the BAP routing identifier in the second network segment. This ensures that the data packet is transmitted normally in the second network segment, reducing data packet transmission anomalies caused by the IAB network being managed by multiple IAB host nodes. This guarantees that data packets are correctly routed in IAB networks composed of multiple network segments managed by different host nodes.

[0370] Please see Figure 14 Another embodiment of the communication device in this application embodiment, wherein the communication device may be a first IAB node or a component of the first IAB node (e.g., DU, MT, or processor, chip, or chip system), the communication device is used to access a backhaul integrated IAB network, the IAB network including a first network segment and a second network segment, the first network segment being managed by a first host node, the second network segment being managed by a second host node, the first host node and the second host node being different, the communication device including:

[0371] The receiving unit 1401 is configured to receive a first data packet in a first network segment. The first data packet includes a first backhaul adaptation protocol (BAP) route identifier, which is used for the transmission of the first data packet in the first network segment.

[0372] Acquisition unit 1402 is used to acquire the first correspondence relationship;

[0373] The replacement unit 1403 is used to replace the first BAP route identifier in the first data packet with the second BAP route identifier according to the first correspondence relationship, so as to obtain the second data packet;

[0374] The sending unit 1404 is used to send a second data packet to the next-hop node in the second network segment. The next-hop node is either the parent node or the child node of the first IAB node.

[0375] The communication device in this embodiment also includes:

[0376] The determining unit 1405 is used to determine that the BAP address in the first BAP routing identifier in the first data packet is the BAP address of the first IAB node, and that the first data packet meets the preset conditions.

[0377] Optionally, the first data packet includes indication information, and the determining unit 1405 is specifically used to determine, based on the indication information, that the first data packet meets preset conditions.

[0378] Optionally, the acquisition unit 1402 is also used to acquire the second correspondence;

[0379] Optionally, the sending unit 1404 is specifically used for the second correspondence, determining to send the second data packet to the next hop node through the first backhaul radio link control (RLC) channel of the egress link in the second network segment.

[0380] Optionally, the indication information includes the destination Internet Protocol (IP) address of the first data packet. When the destination IP address in the first data packet is not the IP address of the first IAB node, the first IAB node determines that the first data packet meets the preset conditions.

[0381] Optionally, the first network segment includes the first IAB node and its upstream node; the second network segment includes the first IAB node and its downstream node; the receiving unit 1401 is specifically used to receive the first data packet sent by the upstream node in the first network segment; the sending unit 1404 is specifically used to send the second data packet to the downstream node in the second network segment, wherein the BAP address in the second BAP routing identifier is the BAP address of the downstream node.

[0382] Optionally, the first network segment includes the first IAB node and its downstream nodes; the second network segment includes the first IAB node and its upstream nodes; the receiving unit 1401 is specifically used to receive the first data packet sent by the downstream node in the first network segment; the sending unit 1404 is specifically used to send the second data packet to the upstream node in the second network segment, wherein the BAP address in the second BAP routing identifier is the BAP address of the second host node.

[0383] Optionally, the upstream node of the first IAB node is the parent node of the first IAB node; the determining unit 1405 is further configured to determine that the BAP address in the first BAP routing identifier in the first data packet is the BAP address of the first IAB node.

[0384] Optionally, the first BAP route identifier includes a first BAP address and / or a first path identifier, and the second BAP route identifier includes a second BAP address and / or a second path identifier.

[0385] Optionally, the first correspondence is configured by the first host node or the second host node; the acquisition unit 1402 is used to acquire the first correspondence, which includes any one of the following: the acquisition unit 1402 is specifically used to acquire the first BAP route identifier and the second BAP route identifier, and the first BAP route identifier and the second BAP route identifier have a correspondence; the acquisition unit 1402 is specifically used to acquire the IP header information in the first data packet and the second BAP route identifier, and the IP header information and the second BAP route identifier have a correspondence; the IP header information includes at least one of the following: destination IP address, Differentiated Service Code Point (DSCP), and Flow label.

[0386] Optionally, the acquisition unit 1402 is used to acquire a second correspondence, including any one of the following: The acquisition unit 1402 is specifically used to acquire a first BAP routing identifier and a first backhaul RLC channel of the first IAB node's egress link, wherein the first BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link have a correspondence; the acquisition unit 1402 is specifically used to acquire a second BAP routing identifier and a first backhaul RLC channel of the first IAB node's egress link, wherein the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link have a correspondence; the acquisition unit 1402 is specifically used to acquire IP header information in a first data packet and a first backhaul RLC channel of the first IAB node's egress link, wherein the IP header information in the first data packet and the first backhaul RLC channel of the first IAB node's egress link have a correspondence, wherein the IP header information includes at least one of a destination IP address, a Differentiated Service Code Point (DSCP), and a Flow label; the acquisition unit 1402 is specifically used to acquire a second BH RLC CH of the first IAB node's ingress link and a first BH RLC CH of the first IAB node's egress link, wherein the second BH RLC of the first IAB node's ingress link... CH corresponds to the first BH RLC CH of the first IAB node's outgoing link.

[0387] In this embodiment, the operations performed by each unit in the communication device are the same as those described above. Figure 11 and Figure 12The operations performed by the first IAB node (i.e., IAB2) in the illustrated embodiment are similar and will not be described again here.

[0388] In this embodiment, in a scenario where the IAB network is managed by multiple IAB host nodes, the replacement unit 1403 replaces the BAP routing identifier of the data packet in the first network segment with the BAP routing identifier in the second network segment. This ensures that the data packet is transmitted normally in the second network segment, reducing data packet transmission anomalies caused by the IAB network being managed by multiple IAB host nodes. This guarantees that data packets are correctly routed in IAB networks composed of multiple network segments managed by different host nodes.

[0389] Please see Figure 15 Another embodiment of the communication device in this application, wherein the communication device may be a first IAB node or a component of the first IAB node (e.g., DU, MT, or processor, chip, or chip system), the communication device is used to access the integrated backhaul IAB network, and the communication device includes:

[0390] Acquisition unit 1501 is used for the first IAB node to acquire the second correspondence relationship;

[0391] The sending unit 1502 is used to determine, according to the second correspondence, to send the second data packet to the next hop node through the first backhaul RLC channel of the egress link in the second network segment.

[0392] Optionally, the communication device further includes:

[0393] Optionally, the receiving unit 1503 is configured to receive a first data packet in the first network segment. The first data packet includes a first backhaul adaptation protocol (BAP) route identifier, which is used for the transmission of the first data packet in the first network segment.

[0394] The replacement unit 1504 is used to replace the first BAP route identifier in the first data packet with the second BAP route identifier according to the first correspondence relationship, so as to obtain the second data packet.

[0395] Optionally, the replacement unit 1504 is used to replace the first BAP route identifier in the first data packet with the second BAP route identifier according to the first correspondence, so as to obtain the second data packet.

[0396] Optionally, the acquisition unit 1501 is also used to acquire the first correspondence relationship;

[0397] Optionally, the IAB network includes a first network segment and a second network segment. The first network segment is managed by a first host node, and the second network segment is managed by a second host node. The first host node and the second host node are different.

[0398] Optionally, the second data packet includes a second BAP routing identifier, which is used for transmission of the second data packet in the second network segment. In this possible implementation, each host node is allowed to control data packet routing only within its own network segment, and then the boundary node between the two network segments performs proxy operations at the BAP or IP layer, reducing the exit mapping anomaly problems caused by multiple IAB host nodes managing the IAB network. This ensures normal data packet transmission in IAB networks composed of multiple network segments managed by different host nodes.

[0399] Optionally, the first data packet and the second data packet are the same data packet, and the first BAP routing identifier and the second BAP routing identifier may be the same or different. In this possible implementation, each host node only controls the routing of data packets within its own network segment. By having the boundary node of the two network segments (i.e., the first IAB node) perform proxy operations at the BAP layer or IP layer, the first BAP routing identifier for routing in the first network segment contained in the received data packet is replaced with the second BAP routing identifier that will be used for routing in the second network segment. Through this concatenated routing method, it is ensured that data packets can be routed reasonably and correctly in the management of network topologies with multiple newly emerging cross-host base stations.

[0400] In this embodiment, the operations performed by each unit in the communication device are the same as those described above. Figure 11 and Figure 12 The operations performed by the first IAB node (i.e., IAB2) in the illustrated embodiment are similar and will not be described again here.

[0401] In this embodiment, in a scenario where the IAB network is managed by multiple IAB host nodes, the sending unit 1502 determines, based on the second correspondence, to send the second data packet to the next-hop node via the first backhaul RLC channel of the egress link in the second network segment. This reduces the egress mapping anomaly caused by the IAB network being managed by multiple IAB host nodes. It ensures normal data packet transmission in IAB networks composed of multiple network segments managed by different host nodes.

[0402] Please see Figure 16 Another embodiment of the communication device in this application embodiment, wherein the communication device may be a first host node or a component of the first host node (e.g., CU, DU, or processor, chip, or chip system), the communication device is used to access the integrated IAB network for backhaul, the IAB network includes a first network segment and a second network segment, the first network segment is managed by the first host node, the second network segment is managed by the second host node, the first host node and the second host node are different, and the communication device includes:

[0403] The acquisition unit 1601 is used to acquire a first BAP route identifier and a second BAP route identifier. The first BAP route identifier and the second BAP route identifier have a corresponding relationship. The first BAP route identifier is used for data packets to be transmitted in the first network segment, and the second BAP route identifier is used for data packets to be transmitted in the second network segment. The sending unit 1602 is used to send the first BAP route identifier and the second BAP route identifier to the first IAB node. The first IAB node is located in both the first network segment and the second network segment.

[0404] Alternatively, the acquisition unit 1601 is used to acquire the IP header information and the second BAP routing identifier in the data packet. The IP header information and the second BAP routing identifier in the data packet have a corresponding relationship. The second BAP routing identifier is used for the data packet to be transmitted in the second network segment. The sending unit 1602 is used to send the IP header information and the second BAP routing identifier in the data packet to the first IAB node. The first IAB node is located in both the first network segment and the second network segment.

[0405] Optionally, the acquisition unit 1601 is further configured to acquire the first BAP routing identifier and the first backhaul RLC channel of the first IAB node egress link, wherein the first BAP routing identifier and the first backhaul RLC channel of the first IAB node egress link have a corresponding relationship; Optionally, the sending unit 1602 is further configured to send the first BAP routing identifier and the first backhaul RLC channel of the first IAB node egress link to the first IAB node.

[0406] Optionally, the acquisition unit 1601 is further configured to acquire the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link, wherein the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link have a corresponding relationship; optionally, the sending unit 1602 is further configured to send the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link to the first IAB node.

[0407] Optionally, the acquisition unit 1601 is further configured to acquire the IP header information in the first data packet and the first backhaul RLC channel of the first IAB node's egress link, wherein the IP header information in the first data packet and the first backhaul RLC channel of the first IAB node's egress link have a corresponding relationship; Optionally, the sending unit 1602 is further configured to send the IP header information in the first data packet and the first backhaul RLC channel of the first IAB node's egress link to the first IAB node.

[0408] Optionally, the acquisition unit 1601 is further configured to acquire the second backhaul RLC channel of the first IAB node ingress link and the first backhaul RLC channel of the first IAB node egress link, wherein the second backhaul RLC channel of the first IAB node ingress link and the first backhaul RLC channel of the first IAB node egress link have a corresponding relationship; Optionally, the transmission unit 1602 is further configured to transmit the second backhaul RLC channel of the first IAB node ingress link and the first backhaul RLC channel of the first IAB node egress link to the first IAB node.

[0409] Optionally, the sending unit 1602 is further configured to send configuration information to the access IAB node, the configuration information being used to indicate that the BAP address of the first IAB node is used as the destination BAP address of the uplink data packet.

[0410] Optionally, the first network segment includes a first IAB node and downstream nodes of the first IAB node; the second network segment includes a first IAB node and upstream nodes of the first IAB node; the acquisition unit 1601 is further configured to acquire a third correspondence and a fourth correspondence, wherein the third correspondence is the correspondence between the IP address of the distributed unit DU in the first IAB node and the BAP address of the mobile terminal MT in the first IAB node, and the fourth correspondence is the correspondence between the BAP address of the MT in the first IAB node and the IP address of the DU in the downstream node of the first IAB node; the sending unit 1602 is further configured to send the third correspondence and the fourth correspondence to the second host node, wherein the third correspondence and the fourth correspondence are used by the second host node to determine the first BAP routing identifier.

[0411] Optionally, the first network segment includes the first IAB node and its downstream nodes; the second network segment includes the first IAB node and its upstream nodes.

[0412] Optionally, the communication device further includes:

[0413] The determining unit 1603 is used to determine the third BAP route identifier used for downlink transmission of data packets in the first network segment, wherein the second BAP route identifier includes the third BAP route identifier.

[0414] The receiving unit 1604 is used to receive the fourth BAP route identifier sent by the second host node. The fourth BAP route identifier is used for uplink transmission of data packets in the second network segment. The second BAP route identifier includes the fourth BAP route identifier.

[0415] Optionally, the sending unit 1602 is also used to send a third BAP route identifier to the second host node.

[0416] Optionally, the first network segment includes the first IAB node and its downstream nodes; the second network segment includes the first IAB node and its upstream nodes.

[0417] In this embodiment, the operations performed by each unit in the communication device are the same as those described above. Figure 11 (such as the operations performed by CU2) and Figure 12 The operations performed by the host node in the embodiment shown (as in the operation performed by CU1) are similar and will not be repeated here.

[0418] In this embodiment, in a scenario where the IAB network is managed by multiple IAB host nodes, the sending unit 1602 sends a first correspondence to the first IAB node, enabling data packets to be transmitted normally in the second network segment. This reduces data packet transmission anomalies caused by the IAB network being managed by multiple IAB host nodes. It ensures that data packets are correctly routed in IAB networks composed of multiple network segments managed by different host nodes.

[0419] Please see Figure 17 Another embodiment of the communication device in this application is described. This communication device can be a second host node or a component of the second host node (e.g., CU, DU, processor, chip, or chip system). This communication device is used in an integrated access backhaul (IAB) network. The IAB network includes a first network segment and a second network segment. The first network segment is managed by a first host node, and the second network segment is managed by a second host node. The first host node and the second host node are different. The communication device includes:

[0420] The acquisition unit 1701 is used for the second host node to acquire the first BAP route identifier and the second BAP route identifier. The first BAP route identifier and the second BAP route identifier have a corresponding relationship. The first BAP route identifier is used for data packets to be transmitted in the first network segment, and the second BAP route identifier is used for data packets to be transmitted in the second network segment. The sending unit 1702 is used for the second host node to send the first BAP route identifier and the second BAP route identifier to the first IAB node. The first IAB node is located in both the first network segment and the second network segment.

[0421] Alternatively, the acquisition unit 1701 is used for the second host node to acquire the IP header information and the second BAP routing identifier in the data packet. The IP header information and the second BAP routing identifier in the data packet have a corresponding relationship. The second BAP routing identifier is used for the data packet to be transmitted in the second network segment. The sending unit 1702 is used to send the IP header information and the second BAP routing identifier in the data packet to the first IAB node. The first IAB node is located in both the first network segment and the second network segment.

[0422] Optionally, the acquisition unit 1701 is further configured to acquire the first BAP routing identifier and the first backhaul RLC channel of the first IAB node egress link, wherein the first BAP routing identifier and the first backhaul RLC channel of the first IAB node egress link have a corresponding relationship; the transmission unit 1702 is further configured to transmit the first BAP routing identifier and the first backhaul RLC channel of the first IAB node egress link to the first IAB node.

[0423] Optionally, the acquisition unit 1701 is further configured to acquire the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link, wherein the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link have a corresponding relationship; the transmission unit 1702 is further configured to transmit the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link to the first IAB node.

[0424] Optionally, the acquisition unit 1701 is further configured to acquire the IP header information in the first data packet and the first backhaul RLC channel of the first IAB node's egress link, wherein the IP header information in the first data packet and the first backhaul RLC channel of the first IAB node's egress link have a corresponding relationship; the sending unit 1702 is further configured to send the IP header information in the first data packet and the first backhaul RLC channel of the first IAB node's egress link to the first IAB node.

[0425] Optionally, the acquisition unit 1701 is further configured to acquire the second backhaul RLC channel of the first IAB node ingress link and the first backhaul RLC channel of the first IAB node egress link, wherein the second backhaul RLC channel of the first IAB node ingress link and the first backhaul RLC channel of the first IAB node egress link have a corresponding relationship; the transmission unit 1702 is further configured to transmit the second backhaul RLC channel of the first IAB node ingress link and the first backhaul RLC channel of the first IAB node egress link to the first IAB node.

[0426] Optionally, the sending unit 1702 is further configured to send configuration information to the access IAB node, the configuration information being used to indicate that the BAP address of the first IAB node is used as the destination BAP address of the uplink data packet.

[0427] Optionally, the first network segment includes the first IAB node and its downstream nodes; the second network segment includes the first IAB node and its upstream nodes.

[0428] Optionally, the communication device further includes:

[0429] The receiving unit 1703 is used to receive the third correspondence and the fourth correspondence sent by the first host node. The third correspondence is the correspondence between the IP address of the distributed unit DU in the first IAB node and the BAP address of the mobile terminal MT in the first IAB node. The fourth correspondence is the correspondence between the BAP address of the MT in the first IAB node and the IP address of the DU in the downstream node of the first IAB node.

[0430] The determining unit 1704 is used to determine the first BAP route identifier based on the third correspondence and the fourth correspondence.

[0431] Optionally, the first network segment includes the first IAB node and its downstream nodes; the second network segment includes the first IAB node and its upstream nodes; the receiving unit 1703 is further configured to receive a third BAP routing identifier sent by the first host node, the third BAP routing identifier being used for downlink transmission of data packets in the first network segment, and the second BAP routing identifier including the third BAP routing identifier.

[0432] Optionally, the first network segment includes the first IAB node and the downstream node of the first IAB node; the second network segment includes the first IAB node and the upstream node of the first IAB node; the determining unit 1704 is further configured to determine the fourth BAP route identifier used for uplink transmission of data packets in the second network segment, wherein the second BAP route identifier includes the fourth BAP route identifier.

[0433] Optionally, the sending unit 1702 is also used to send the fourth BAP route identifier to the first host node.

[0434] In this embodiment, the operations performed by each unit in the communication device are the same as those described above. Figure 11 (such as the operations performed by CU1) and Figure 12 The operations performed by the host node in the example shown (as in the operation performed by CU2) are similar and will not be repeated here.

[0435] In this embodiment, in a scenario where the IAB network is managed by multiple IAB host nodes, the sending unit 1702 sends a first correspondence to the first IAB node, enabling data packets to be transmitted normally in the second network segment. This reduces data packet transmission anomalies caused by the IAB network being managed by multiple IAB host nodes. It ensures that data packets are correctly routed in IAB networks composed of multiple network segments managed by different host nodes.

[0436] Please see Figure 18The above-described embodiments of the communication device provided in this application are schematic diagrams of the structure of the communication device. Specifically, the communication device can be an IAB node as described in the preceding embodiments, such as a first IAB node, a parent node of the first IAB node, or a child node of the first IAB node, or IAB1, IAB2, IAB3, or IAB4. The structure of this communication device can be referenced... Figure 18 The structure shown.

[0437] The communication device includes at least one processor 1811, at least one memory 1812, at least one transceiver 1813, at least one network interface 1814, and one or more antennas 1815. The processor 1811, memory 1812, transceiver 1813, and network interface 1814 are connected, for example, via a bus. In this embodiment, the connection may include various interfaces, transmission lines, or buses, etc., and this embodiment is not limited in this respect. The antenna 1815 is connected to the transceiver 1813. The network interface 1814 enables the communication device to connect to other communication devices via a communication link. For example, the network interface 1814 may include a network interface between the communication device and core network equipment, such as an S1 interface. The network interface may also include a network interface between the communication device and other network equipment (e.g., other access network equipment or core network equipment), such as an X2 or Xn interface.

[0438] The processor 1811 is primarily used to process communication protocols and communication data, control the entire communication device, execute software programs, and process data from the software programs, for example, to support the communication device in performing the actions described in the embodiments. The communication device may include a baseband processor and a central processing unit (CPU). The baseband processor is primarily used to process communication protocols and communication data, while the CPU is primarily used to control the entire terminal device, execute software programs, and process data from the software programs. Figure 18 The processor 1811 can integrate the functions of a baseband processor and a central processing unit. Those skilled in the art will understand that the baseband processor and the central processing unit can also be independent processors interconnected via technologies such as buses. Those skilled in the art will understand that a terminal device can include multiple baseband processors to adapt to different network standards, and a terminal device can include multiple central processing units to enhance its processing capabilities. The various components of the terminal device can be connected via various buses. The baseband processor can also be described as a baseband processing circuit or a baseband processing chip. The central processing unit can also be described as a central processing circuit or a central processing chip. The function of processing communication protocols and communication data can be built into the processor or stored in memory as a software program, with the processor executing the software program to implement the baseband processing function.

[0439] The memory is primarily used to store software programs and data. The memory 1812 can exist independently or be connected to the processor 1811. Optionally, the memory 1812 can be integrated with the processor 1811, for example, integrated within a single chip. The memory 1812 can store program code that executes the technical solutions of the embodiments of this application, and its execution is controlled by the processor 1811. The various types of computer program code being executed can also be considered as drivers for the processor 1811.

[0440] Figure 18 Only one memory and one processor are shown. In actual communication devices, there may be multiple processors and multiple memories. Memory can also be called storage medium or storage device, etc. Memory can be a storage element on the same chip as the processor, i.e., an on-chip storage element, or it can be a separate storage element; this application does not limit this.

[0441] Transceiver 1813 can be used to support the reception or transmission of radio frequency (RF) signals between the communication device and other IAB nodes (e.g., UE, IAB node, or IABdonor). Transceiver 1813 can be connected to antenna 1815. Transceiver 1813 includes a transmitter Tx and a receiver Rx. Specifically, one or more antennas 1815 can receive RF signals. The receiver Rx of transceiver 1813 is used to receive the RF signals from the antennas, convert the RF signals into digital baseband signals or digital intermediate frequency (IF) signals, and provide the digital baseband signals or IF signals to the processor 1811 so that the processor 1811 can perform further processing on the digital baseband signals or IF signals, such as demodulation and decoding. In addition, the transmitter Tx in transceiver 1813 is also used to receive modulated digital baseband signals or IF signals from processor 1811, convert the modulated digital baseband signals or IF signals into RF signals, and transmit the RF signals through one or more antennas 1815. Specifically, the receiver Rx can selectively perform one or more stages of downmixing and analog-to-digital conversion on the radio frequency signal to obtain a digital baseband signal or a digital intermediate frequency (IF) signal. The order of the downmixing and IF conversion processes is adjustable. The transmitter Tx can selectively perform one or more stages of upmixing and digital-to-analog conversion on the modulated digital baseband signal or digital IF signal to obtain a radio frequency signal. The order of the upmixing and IF conversion processes is also adjustable. The digital baseband signal and the digital IF signal can be collectively referred to as digital signals.

[0442] A transceiver can also be called a transceiver unit, transceiver, or transceiver device. Optionally, the device in the transceiver unit that performs the receiving function can be considered as the receiving unit, and the device in the transceiver unit that performs the transmitting function can be considered as the transmitting unit. That is, the transceiver unit includes a receiving unit and a transmitting unit. The receiving unit can also be called a receiver, input port, or receiving circuit, and the transmitting unit can be called a transmitter, transmitter, or transmitting circuit, etc.

[0443] It should be noted that, Figure 18 The communication device shown can be specifically used to implement Figure 11 and Figure 12 The steps implemented by the IAB node in the corresponding method embodiment, and the corresponding technical effects achieved by the communication device, Figure 18 The specific implementation methods of the communication devices shown can all be referred to Figure 11 and Figure 12 The descriptions in the corresponding method embodiments will not be repeated here.

[0444] Figure 19 This is a schematic diagram of a structure of the IAB donor provided in an embodiment of this application. The IAB donor can adopt a CU-DU separated architecture. Figure 19 As shown, this IAB donor can be applied to, for example... Figures 6 to 10 In the system shown, the functions of the first host node or the second host node in the above method embodiments are implemented.

[0445] The IAB donor may include one or more DU 1101 and one or more CU 1102. DU 1101 may include at least one antenna 11011, at least one radio frequency unit 11012, at least one processor 11013, and at least one memory 11014. The DU 1101 is primarily used for transmitting and receiving radio frequency signals, converting radio frequency signals to baseband signals, and performing some baseband processing. CU 1102 may include at least one processor 11022 and at least one memory 11021. CU 1102 and DU 1101 can communicate via an interface, where the control plane interface can be F1-C and the user plane interface can be F1-U.

[0446] The CU 1102 is mainly used for baseband processing and base station control. The DU 1101 and CU 1102 can be physically installed together or separately, i.e., a distributed base station. The CU 1102 is the control center of the base station, also known as a processing unit, and is mainly used to complete baseband processing functions. For example, the CU 1102 can be used to control the base station to execute the network device operation procedures described in the above method embodiments.

[0447] Specifically, the baseband processing on CU and DU can be divided according to the protocol layer of the wireless network, as detailed above.

[0448] In one example, the CU 1102 can be composed of one or more single boards. Multiple single boards can collectively support a single access indication wireless access network (such as a 5G network), or they can each support wireless access networks with different access standards (such as LTE, 5G, or other access networks). The memory 11021 and processor 11022 can serve one or more single boards. That is, each single board can have its own memory and processor, or multiple single boards can share the same memory and processor. Furthermore, each single board can also have necessary circuitry. Similarly, the DU 1101 can be composed of one or more single boards. Multiple single boards can collectively support a single access indication wireless access network (such as a 5G network), or they can each support wireless access networks with different access standards (such as LTE, 5G, or other access networks). The memory 11014 and processor 11013 can serve one or more single boards. That is, each single board can have its own memory and processor, or multiple single boards can share the same memory and processor. Furthermore, each single board can also have necessary circuitry.

[0449] Optionally, CU 1102 can transmit with the child nodes of the IAB donor through DU 1101. CU 1102 can connect to other IAB donors through an interface. CU 1102 can receive data and / or messages from other IAB donors (e.g., CUs of other IAB donors) through this interface, or CU 1102 can send data and / or messages to other IAB donors through this interface.

[0450] This application also provides a computer-readable storage medium storing one or more computer-executable instructions. When the computer-executable instructions are executed by a processor, the processor executes a method implemented by the communication device described above, such as the method implemented by the IAB donor, the target parent node of the first IAB node, the first IAB node, or the child node of the first IAB node.

[0451] This application also provides a computer program product (or computer program) that stores one or more computers. When the computer program product is executed by the processor, the processor executes the method implemented by the above-mentioned communication device, such as the method implemented by the IAB donor, the target parent node of the first IAB node, the first IAB node, or the child node of the first IAB node.

[0452] This application also provides a chip system including a processor for supporting a communication device in implementing the methods described above, such as those implemented by the IAB donor and IAB node. In one possible design, the chip system may further include a memory for storing necessary program instructions and data for the communication device. The chip system may be composed of chips or may include chips and other discrete components.

[0453] This application also provides a communication system, which includes the above-mentioned communication devices, such as the above-mentioned IABdonor, the first IAB node, the parent node of the first IAB node and / or the child node of the first IAB node.

[0454] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0455] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.

[0456] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0457] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0458] If the integrated unit is implemented as 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 this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A communication method, characterized in that, The method is applied to an integrated access backhaul (IAB) network, which includes a first network segment and a second network segment. The first network segment is managed by a first host node, and the second network segment is managed by a second host node. The first host node and the second host node are different. The method includes: The first IAB node receives a first data packet in the first network segment. The first data packet includes a first backhaul adaptation protocol (BAP) route identifier, which is used for the transmission of the first data packet in the first network segment. The first IAB node obtains the first correspondence; If the first BAP route identifier included in the first correspondence is in the first data packet, the first IAB node determines that the first data packet meets the preset conditions; If the first data packet meets the preset condition, the first IAB node replaces the first BAP route identifier in the first data packet with the second BAP route identifier according to the first correspondence relationship, and obtains the second data packet. The first IAB node sends the second data packet to the next-hop node in the second network segment, where the next-hop node is either the parent node or a child node of the first IAB node. The first IAB node is located in both the first network segment and the second network segment; The first correspondence also includes an identifier related to the second network segment, which corresponds to the second BAP route identifier.

2. The method according to claim 1, characterized in that, The first network segment includes the first IAB node and the upstream node of the first IAB node; the second network segment includes the first IAB node and the downstream node of the first IAB node. The first IAB node receives a first data packet in the first network segment, including: The first IAB node receives the first data packet sent by the upstream node in the first network segment; The first IAB node sends the second data packet to the next-hop node in the second network segment, including: The first IAB node sends the second data packet to the downstream node in the second network segment, and the BAP address in the second BAP routing identifier is the BAP address of the downstream node.

3. The method according to claim 1 or 2, characterized in that, The first network segment includes the first IAB node and its downstream nodes; the second network segment includes the first IAB node and its upstream nodes. The first IAB node receives a first data packet in the first network segment, including: The first IAB node receives the first data packet sent by the downstream node in the first network segment; The first IAB node sends the second data packet to the next-hop node in the second network segment, including: The first IAB node sends the second data packet to the upstream node in the second network segment, and the BAP address in the second BAP routing identifier is the BAP address of the second host node.

4. The method according to any one of claims 1 to 3, characterized in that, The first BAP route identifier includes a first BAP address and / or a first path identifier, and the second BAP route identifier includes a second BAP address and / or a second path identifier.

5. The method according to any one of claims 1 to 4, characterized in that, The first correspondence is configured by the first host node or the second host node; The first IAB node obtains the first correspondence, including: The first IAB node obtains the first BAP route identifier and the second BAP route identifier, and the first BAP route identifier and the second BAP route identifier have a corresponding relationship.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: The first IAB node obtains the second correspondence; The first IAB node sends the second data packet to the next-hop node in the second network segment, including: Based on the second correspondence, the first IAB node determines to send the second data packet to the next-hop node through the first backhaul radio link control (RLC) channel of the egress link in the second network segment; The first IAB node obtains the second correspondence, which includes any one of the following: The first IAB node obtains the first BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link, and the first BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link have a corresponding relationship. The first IAB node obtains the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link, and the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link have a corresponding relationship. The first IAB node obtains the Internet Protocol (IP) header information from the first data packet and the first backhaul RLC channel of the first IAB node's egress link. The IP header information in the first data packet corresponds to the first backhaul RLC channel of the first IAB node's egress link. The IP header information includes at least one of the following: a destination IP address, a Differentiated Service Code Point (DSCP), and a flow label; or... The first IAB node acquires the second backhaul RLC channel of the first IAB node's ingress link and the first backhaul RLC channel of the first IAB node's egress link, and the second backhaul RLC channel of the first IAB node's ingress link and the first backhaul RLC channel of the first IAB node's egress link have a corresponding relationship.

7. The method according to any one of claims 1 to 6, characterized in that, The first IAB node obtains the first correspondence, including: The first IAB node receives the first correspondence from the first host node or the second host node.

8. A communication method, characterized in that, The method is applied to an integrated access backhaul (IAB) network, which includes a first network segment and a second network segment. The first network segment is managed by a first host node, and the second network segment is managed by a second host node. The first host node and the second host node are different. The method includes: The first host node or the second host node obtains a first BAP route identifier and a second BAP route identifier. The first BAP route identifier and the second BAP route identifier have a corresponding relationship. The first BAP route identifier is used for data packets to be transmitted in the first network segment, and the second BAP route identifier is used for the data packets to be transmitted in the second network segment. The first host node or the second host node sends a first correspondence relationship to the first IAB node. The first correspondence relationship includes the first BAP route identifier, the second BAP route identifier, and an identifier related to the second network segment. The identifier corresponds to the second BAP route identifier. The first IAB node is located in the first network segment and the second network segment.

9. The method according to claim 8, characterized in that, The method further includes: The first host node or the second host node obtains the first BAP routing identifier and the first backhaul RLC channel of the first IAB node egress link, and the first BAP routing identifier and the first backhaul RLC channel of the first IAB node egress link have a corresponding relationship. The first host node or the second host node sends the first BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link to the first IAB node. or, The first host node or the second host node obtains the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link, and the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link have a corresponding relationship. The first host node or the second host node sends the second BAP routing identifier and the first backhaul RLC channel of the first IAB node's egress link to the first IAB node. or, The first host node or the second host node obtains the IP header information in the first data packet and the first backhaul RLC channel of the first IAB node's egress link, and the IP header information in the first data packet and the first backhaul RLC channel of the first IAB node's egress link have a corresponding relationship. The first host node or the second host node sends the IP header information in the first data packet and the first backhaul RLC channel of the first IAB node's egress link to the first IAB node. or, The first host node or the second host node obtains the second backhaul RLC channel of the first IAB node ingress link and the first backhaul RLC channel of the first IAB node egress link, and the second backhaul RLC channel of the first IAB node ingress link and the first backhaul RLC channel of the first IAB node egress link have a corresponding relationship. The first host node or the second host node sends the second backhaul RLC channel of the first IAB node's ingress link and the first backhaul RLC channel of the first IAB node's egress link to the first IAB node.

10. The method according to claim 8 or 9, characterized in that, The method further includes: The first host node or the second host node sends configuration information to the access IAB node, the configuration information being used to indicate that the BAP address of the first IAB node is used as the destination BAP address of the uplink data packet.

11. A communication device, characterized in that, The method includes a processor coupled to a memory for storing computer programs or instructions, and the processor for executing the computer programs or instructions in the memory such that the method of any one of claims 1 to 7 is performed.

12. A communication device, characterized in that, The method includes a processor coupled to a memory for storing computer programs or instructions, and the processor is configured to execute the computer programs or instructions in the memory such that the method of any one of claims 8 to 10 is performed.

13. A communication system, characterized in that, include: A first IAB node, a first host node, and / or a second host node, wherein the first IAB node is used to perform the method of any one of claims 1 to 7, the first host node is used to perform the method of any one of claims 8 to 10, and the second host node is used to perform the method of any one of claims 8 to 10.

14. A chip, characterized in that, The chip includes a processor and a communication interface coupled to the processor. The processor is configured to run a computer program or instructions that cause the method of any one of claims 1 to 7 to be executed, or cause the method of any one of claims 8 to 10 to be executed.

15. A computer storage medium, characterized in that, The computer storage medium stores instructions that, when executed on the computer, cause the computer to perform the method as described in any one of claims 1 to 7, or cause the computer to perform the method as described in any one of claims 8 to 10.

Images