CN115915330A

CN115915330A - Routing method and communication device

Info

Publication number: CN115915330A
Application number: CN202111101156.5A
Authority: CN
Inventors: 孙飞; 李奎奎; 朱元萍; 史玉龙
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-08-04
Filing date: 2021-09-18
Publication date: 2023-04-04

Abstract

The embodiment of the application discloses a routing method and a communication device, which are applied to an IAB network, wherein the IAB network comprises a first BAP topology and a second BAP topology, the first BAP topology is managed by a first host node, the second BAP topology is managed by a second host node, and the first host node is different from the second host node; the routing method comprises the following steps: the first IAB node receives the first data packet; the first IAB node is managed by the first hosting node, at least one parent node of the first IAB node is managed by the second hosting node, the first IAB node belongs to the first BAP topology; the first IAB node processes the first data packet according to the BAP topology corresponding to the entry link for receiving the first data packet and the BAP topology to which the first IAB node belongs; the first data packet can be routed to the correct transmission path.

Description

Routing method and communication device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a routing method and a communications apparatus.

Background

Compared with the fourth generation mobile communication system, the fifth generation mobile communication (5 th generation,5 g) and the future mobile communication system provide more stringent requirements for various performance indexes of the network. For example, 5G has a capacity 1000 times higher than 4G, wider coverage requirements, ultra-high reliability and ultra-low latency. On one hand, in consideration of abundant high-frequency carrier frequency resources, in a hot spot area, in order to meet the requirement of 5G ultrahigh capacity, networking by using high-frequency small stations is more popular. Due to poor high-frequency carrier propagation characteristics, serious shielding attenuation and low coverage range, a large number of densely deployed small stations are required. However, it is expensive and difficult to provide optical fiber return for these small stations densely deployed in large quantities, so an economical and convenient return scheme is required. On the other hand, from the perspective of wide coverage requirements, network coverage is provided in some remote areas, the deployment difficulty of optical fibers is high, the cost is high, and a flexible and convenient access and return scheme also needs to be designed. The Integrated Access and Backhaul (IAB) technology provides ideas for solving the two problems: an access link (access link) and a Backhaul Link (BL) both adopt a wireless transmission scheme, so that optical fiber deployment is reduced.

In an IAB network, a relay node RN (relay node) or an IAB node (IAB node) may provide a User Equipment (UE) with radio access service and forward traffic data. The service data of the UE is transmitted to an IAB host (IAB donor) by the IAB node through a wireless backhaul link, and the IAB donor may also be referred to as a host node (donor node) or a host base station (donor gbb, dgNB). An IAB node is composed of a Mobile Termination (MT) part and a Distributed Unit (DU) part. When the IAB node faces its parent node, it can act as a terminal device, i.e. MT; when an IAB faces its child node (which may be another IAB node, or a UE), it is considered a network device, i.e. in the role of a DU. The donor base station (DgNB) may be an access network element with a complete base station function, or may be an access network element with a Centralized Unit (CU) and a Distributed Unit (DU) in separate forms. The host base station is connected to a network element of a core network (e.g., to a 5G core network) serving the UE and provides a wireless backhaul function for the IAB node.

In an IAB network, each IAB border node (boundary node) needs to route the packets passing through it to the correct path. Therefore, how to make the IAB border node route the data packet passing through it to the correct path is a problem to be solved.

Disclosure of Invention

The embodiment of the application discloses a routing method and a communication device, which can enable an IAB boundary node to route a data packet passing through the IAB boundary node to a correct path.

In a first aspect, an embodiment of the present application provides a routing method, where the routing method is applied to an access backhaul integrated IAB network, where the IAB network includes a first BAP topology and a second BAP topology, the first BAP topology is managed by a first host node, the second BAP topology is managed by a second host node, and the first host node is different from the second host node; the method may be performed by a first communication apparatus, which may be a communication device or a communication apparatus capable of supporting a communication device to implement the functions required by the method, such as a system on a chip. The first communication device is taken as the first IAB node for example. The method comprises the following steps:

the first IAB node receives the first data packet; the first IAB node is managed by the first hosting node, at least one parent node of the first IAB node is managed by the second hosting node, and the first IAB node belongs to the first BAP topology; and the first IAB node processes the first data packet according to the BAP topology corresponding to the inlet link for receiving the first data packet and the BAP topology of the first IAB node.

The first IAB node may determine, for the received first packet (downlink packet), whether to rewrite the BAP routing ID of the first packet. It should be appreciated that the first IAB node ensures that the first packet is routed to the correct path while being able to accurately determine whether the received BAP routing ID of the first packet is rewriting received.

In this embodiment of the present application, the first IAB node can accurately determine whether to rewrite the received BAP routing ID of the first data packet according to the BAP topology corresponding to the ingress link that receives the first data packet and the BAP topology to which the first IAB node belongs, and further route the first data packet to a correct path.

In a possible implementation manner, the processing, by the first IAB node, the first data packet according to the BAP topology corresponding to the ingress link that receives the first data packet and the BAP topology to which the first IAB node belongs includes: under the condition that the BAP topology corresponding to the entry link of the first IAB node receiving the first data packet is not the first BAP topology and does not meet a first condition, the first IAB node forwards the first data packet according to a second BAP routing identifier and a routing table; the first condition includes: the first BAP address matches the second BAP address; the second BAP routing identifier is obtained by rewriting a first BAP routing identifier of the first data packet, and the first BAP routing identifier comprises a destination BAP address and a path identifier of the first data packet; the first BAP address is obtained by rewriting a destination BAP address of the first data packet, and the second BAP address is a BAP address distributed by the first host node for the first IAB node; or, the first BAP address is a destination BAP address of the first packet, and the second BAP address is a BAP address allocated by the second donor node to the first IAB node.

When the BAP topology corresponding to the entry link of the first IAB node receiving the first data packet is not the first BAP topology and the first IAB node belongs to the first BAP topology, the first IAB node cannot identify the BAP route identifier of the first BAP node. If the first IAB node is to forward the first data packet, the BAP routing identity of the first data packet may be changed to its recognizable BAP routing identity. The first condition may be understood as a condition that the first IAB node determines whether to forward the first data packet when the BAP topology corresponding to the ingress link, where the first IAB node receives the first data packet, is not the first BAP topology. The first IAB node forwards the first packet when the first condition is not met. It should be understood that, in a case that the BAP topology corresponding to the ingress link of the first IAB node receiving the first data packet is not the first BAP topology and the first condition is not satisfied, the first IAB node forwards the first data packet and rewrites the BAP route identification of the first data packet.

In the implementation manner, when the BAP topology corresponding to the ingress link of the first IAB node receiving the first data packet is not the first BAP topology and does not satisfy the first condition, the first IAB node forwards the first data packet according to the second BAP route identifier and the route table; the first packet can be routed to the correct path.

In one possible implementation, the first condition further includes: the first indication information included in the first packet indicates that the first packet is to be delivered to an upper layer of a BAP layer of the first IAB node.

In this implementation, the first condition further includes: the first packet includes first indication information indicating that the first packet is to be delivered to an upper layer of a BAP layer of the first IAB node. In this implementation, the first data packet is delivered to the upper layer of the BAP layer of the first IAB node only if the condition that the first indication information indicates that the first data packet is delivered to the upper layer of the BAP layer of the first IAB node is satisfied, so that the first data packet can be prevented from being erroneously delivered to the upper layer of the BAP layer of the first IAB node.

In one possible implementation, before the first IAB node forwards the first packet according to a routing table, the method further includes: the first IAB node rewrites the first BAP routing identity of the first data packet into the second BAP routing identity; the first IAB node forwarding the first packet according to a routing table comprises: and the first IAB node forwards the first data packet according to the next hop BAP address matched with the second BAP routing identification in the routing table.

In this implementation, the first IAB node forwards the first data packet according to the next hop BAP address in the routing table that matches the second BAP routing identifier. Because the second BAP route identifier is a BAP route identifier which can be identified by a downstream node of the first IAB node, the first IAB node forwards the first data packet according to a next hop BAP address matched with the second BAP route identifier in the route table; the first data packet can be routed to the correct transmission path.

In a possible implementation manner, the processing, by the first IAB node, the first data packet according to the BAP topology corresponding to the ingress link that receives the first data packet and the BAP topology to which the first IAB node belongs includes: when the BAP topology corresponding to the entry link of the first IAB node receiving the first data packet is not the first BAP topology and meets a first condition, the first IAB node submits the first data packet to an upper layer of a BAP layer of the first IAB node; the first condition includes: the first BAP address matches the second BAP address; the first BAP address is obtained by rewriting a destination BAP address of the first data packet, and the second BAP address is a BAP address distributed by the first host node for the first IAB node; or, the first BAP address is a destination BAP address of the first packet, and the second BAP address is a BAP address allocated by the second donor node to the first IAB node.

When the BAP topology corresponding to the entry link of the first IAB node receiving the first data packet is not the first BAP topology, the BAP address of the first data packet is allocated by the second host node. Therefore, the first IAB node can accurately determine whether the first data packet needs to be delivered to the upper layer of the BAP layer of the first IAB node by determining whether the first condition is satisfied, and then route the first data packet to the correct transmission path.

In a possible implementation manner, the processing, by the first IAB node, the first data packet according to the BAP topology corresponding to the ingress link that receives the first data packet and the BAP topology to which the first IAB node belongs includes: under the condition that the BAP topology corresponding to the entry link of the first IAB node receiving the first data packet is the first BAP topology and the third BAP address is not matched with the fourth BAP address, the first IAB node forwards the first data packet according to a routing table; the third BAP address is a destination BAP address of the first data packet, and the fourth BAP address is a BAP address allocated by the first host node to the first IAB node.

When the BAP topology corresponding to the entry link of the first IAB node receiving the first data packet is the first BAP topology, the BAP address of the first data packet is allocated by the first host node. The first IAB node can accurately judge whether the first data packet needs to be delivered to the upper layer of the BAP layer of the first IAB node by judging whether the third BAP address is matched with the fourth BAP address, and then routes the first data packet to a correct transmission path.

In a possible implementation manner, the processing, by the first IAB node, the first data packet according to the BAP topology corresponding to the ingress link receiving the first data packet and the BAP topology to which the first IAB node belongs includes: when the BAP topology corresponding to the entry link of the first IAB node receiving the first data packet is the first BAP topology and the third BAP address is matched with the fourth BAP address, the first IAB node submits the first data packet to an upper layer of a BAP layer of the first IAB node; the third BAP address is a destination BAP address of the first data packet, and the fourth BAP address is a BAP address allocated by the first host node to the first IAB node.

In a second aspect, an embodiment of the present application provides another routing method, where the routing method is applied to an IAB network, where the IAB network includes a first BAP topology and a second BAP topology, the first BAP topology is managed by a first host node, the second BAP topology is managed by a second host node, and the first host node is different from the second host node; the method may be performed by a second communication device, which may be a communication apparatus or a communication device capable of supporting a communication apparatus to implement the functions required by the method, such as a system-on-a-chip. The second communication apparatus is taken as the first IAB node for example to describe below. The method comprises the following steps: the first IAB node receiving a second packet from a child node of the first IAB node; the first IAB node is managed by the first hosting node, at least one parent node of the first IAB node is managed by the second hosting node, and the first IAB node belongs to the first BAP topology; and the first IAB node forwards the second data packet according to a fourth BAP route identifier and a route table under the condition of obtaining the fourth BAP route identifier which has a mapping relation with the third BAP route identifier of the second data packet.

When the first IAB node obtains a fourth BAP route identifier which has a mapping relation with the third BAP route identifier of the second data packet, the third BAP route identifier of the second data packet needs to be rewritten. That is, the first IAB node is unable to forward the second packet using the third BAP route identification. At this time, the second data packet is forwarded according to a fourth BAP routing identifier and a routing table; the second data packet can be routed to the correct transmission path.

In the embodiment of the application, the second data packet is forwarded according to a fourth BAP route identifier and a route table under the condition of obtaining the fourth BAP route identifier which has a mapping relation with the third BAP route identifier of the second data packet; the second data packet can be routed to the correct transmission path.

In one possible implementation, the method further includes: and the first IAB node forwards the second data packet according to the third BAP route identifier and a route table under the condition that the first IAB node does not obtain the BAP route identifier which has a mapping relation with the third BAP route identifier of the second data packet.

When the first IAB node does not obtain the fourth BAP routing identity which has a mapping relation with the third BAP routing identity of the second data packet, it indicates that the third BAP routing identity of the second data packet does not need to be rewritten. That is to say, when the first IAB node does not obtain the fourth BAP route identifier having a mapping relationship with the third BAP route identifier of the second data packet, the first IAB node can correctly forward the second data packet according to the third BAP route identifier.

In the implementation manner, the first IAB node forwards the second data packet according to the third BAP route identifier and the route table under the condition that the first IAB node does not obtain the BAP route identifier having a mapping relationship with the third BAP route identifier of the second data packet; the second data packet can be routed to the correct transmission path.

In a third aspect, an embodiment of the present application provides another routing method, where the method is applied to an IAB network, where the IAB network includes a first BAP topology and a second BAP topology, the first BAP topology is managed by a first host node, the second BAP topology is managed by a second host node, and the first host node is different from the second host node; the method may be performed by a third communication device, which may be a communication apparatus or a communication device capable of supporting a communication apparatus to implement the functions required by the method, such as a system-on-chip. The third communication device is taken as the first IAB node for example. The method comprises the following steps:

the first IAB node receives the first data packet; the first IAB node processes the first data packet according to the second indication information in the first data packet and the BAP topology to which the first IAB node belongs; the second indication information indicates that the destination BAP address of the first data packet is allocated by the first host node, or the second indication information indicates that the destination BAP address of the first data packet is allocated by the second host node.

In this embodiment of the present application, the first IAB node can accurately determine whether to rewrit the received BAP routing ID of the first data packet according to the second indication information in the first data packet and the BAP topology to which the first IAB node belongs, and further route the first data packet to a correct path.

In a possible implementation manner, the processing, by the first IAB node, the first data packet according to the second indication information in the first data packet and the BAP topology to which the first IAB node belongs includes: under the condition that the second indication information indicates that the destination BAP address of the first data packet is allocated by the second host node and a first condition is not met, the first IAB node forwards the first data packet according to a second BAP routing identifier and a routing table; the first condition includes: the first BAP address matches the second BAP address; the second BAP routing identifier is obtained by rewriting a first BAP routing identifier of the first data packet, and the first BAP routing identifier comprises a destination BAP address and a path identifier of the first data packet; the first BAP address is obtained by rewriting a destination BAP address of the first data packet, and the second BAP address is a BAP address distributed by the first host node for the first IAB node; or the first BAP address is a destination BAP address of the first data packet, and the second BAP address is a BAP address allocated by the second host node to the first IAB node.

When the destination BAP address of the first packet is assigned by the second donor node and the first IAB node belongs to the first BAP topology, the first IAB node may not recognize the BAP route identification of the first BAP node. If the first IAB node is to forward the first data packet, the BAP route identification of the first data packet is changed into the identifiable BAP route identification. The first condition may be understood as a condition that the first IAB node determines whether to forward the first packet when the destination BAP address of the first packet is allocated by the second donor node. The first IAB node forwards the first packet when the first condition is not met. It should be appreciated that in the event that the destination BAP address of the first packet is assigned by the second host node and the first condition is not met, the first IAB node forwards the first packet and overwrites the BAP route identification of the first packet.

In the implementation manner, when the destination BAP address of the first data packet is allocated by the second host node and the first condition is not satisfied, the first IAB node forwards the first data packet according to the second BAP routing identifier and the routing table; the first packet can be routed to the correct path.

In this implementation, the first condition further includes: the first packet includes first indication information indicating that the first packet is to be delivered to an upper layer of a BAP layer of the first IAB node. In this implementation, when the condition that the first indication information indicates that the first data packet is delivered to the upper layer of the BAP layer of the first IAB node is satisfied, the first data packet is delivered to the upper layer of the BAP layer, so that the first data packet can be prevented from being delivered to the upper layer of the BAP layer of the first IAB node erroneously.

In one possible implementation, before the first IAB node forwards the first packet according to a routing table, the method further includes: the first IAB node rewrites the first BAP route identifier of the first data packet into the second BAP route identifier; the first IAB node forwarding the first packet according to a routing table comprises: and the first IAB node forwards the first data packet according to the next hop BAP address matched with the second BAP routing identifier in the routing table.

In this implementation, the first IAB node forwards the first packet according to the next hop BAP address in the routing table that matches the second BAP routing identity. The second BAP route identifier is a BAP route identifier which can be identified by a downstream node of the first IAB node, so that the first IAB node forwards the first data packet according to a next hop BAP address matched with the second BAP route identifier in the route table; the first data packet can be routed to the correct transmission path.

In a possible implementation manner, the processing, by the first IAB node, the first packet according to the second indication information in the first packet and the BAP topology to which the first IAB node belongs includes: the first IAB node submits the first data packet to an upper layer of a BAP layer of the first IAB node under the condition that the second indication information indicates that a destination BAP address of the first data packet is allocated by the second host node and a first condition is met; the first condition includes: the first BAP address matches the second BAP address; the first BAP address is obtained by rewriting a destination BAP address of the first data packet, and the second BAP address is a BAP address distributed by the first host node for the first IAB node; or, the first BAP address is a destination BAP address of the first packet, and the second BAP address is a BAP address allocated by the second donor node to the first IAB node.

When the second indication information indicates that the destination BAP address of the first data packet is allocated by the second host node, the first IAB node can accurately determine whether the first data packet needs to be delivered to the upper layer of the BAP layer of the first IAB node by determining whether the first condition is satisfied, and then route the first data packet to the correct transmission path.

In a possible implementation manner, the processing, by the first IAB node, the first packet according to the second indication information in the first packet and the BAP topology to which the first IAB node belongs includes: under the condition that the second indication information indicates that the destination BAP address of the first data packet is allocated by the first host node and the third BAP address does not match with the fourth BAP address, the first IAB node forwards the first data packet according to a routing table; the third BAP address is a destination BAP address of the first data packet, and the fourth BAP address is a BAP address allocated by the first host node to the first IAB node.

When the second indication information indicates that the destination BAP address of the first data packet is allocated by the first host node, the first IAB node can accurately determine whether the first data packet needs to be delivered to an upper layer of a BAP layer of the first IAB node by determining whether the third BAP address matches the fourth BAP address, and then route the first data packet to a correct transmission path.

In a possible implementation manner, the processing, by the first IAB node, the first packet according to the second indication information in the first packet and the BAP topology to which the first IAB node belongs includes: in the case that the second indication information indicates that the destination BAP address of the first data packet is allocated by the first host node and that a third BAP address matches a fourth BAP address, the first IAB node submitting the first data packet to an upper layer of a BAP layer of the first IAB node; the third BAP address is a destination BAP address of the first data packet, and the fourth BAP address is a BAP address allocated by the first host node to the first IAB node.

In a fourth aspect, an embodiment of the present application provides another routing method, where the method is applied to an IAB network, where the IAB network includes a first BAP topology and a second BAP topology, the first BAP topology is managed by a first host node, the second BAP topology is managed by a second host node, and the first host node is different from the second host node; the method may be performed by a fourth communication device, which may be a communication apparatus or a communication device capable of supporting a communication apparatus to implement the functions required by the method, such as a system-on-a-chip. The fourth communication device is taken as the first IAB node for example. The method comprises the following steps:

the first IAB node receives the first data packet; the first IAB node processes the first data packet according to the third indication information in the first data packet; the third indication information indicates to rewrite the BAP address of the first data packet, or the third indication information indicates not to rewrite the BAP address of the first data packet.

In this embodiment of the present application, the first IAB node can accurately determine whether to rewrite the received BAP routing ID of the first data packet according to the third indication information in the first data packet, and then route the first data packet to a correct path.

In one possible implementation manner, the processing, by the first IAB node, the first packet according to the third indication information in the first packet includes: under the condition that the third indication information indicates that the BAP address of the first data packet is rewritten and a first condition is not met, the first IAB node forwards the first data packet according to a second BAP routing identifier and a routing table; the first condition includes: the first BAP address matches the second BAP address; the second BAP routing identifier is obtained by rewriting a first BAP routing identifier of the first data packet, and the first BAP routing identifier comprises a destination BAP address and a path identifier of the first data packet; the first BAP address is obtained by rewriting a destination BAP address of the first data packet, and the second BAP address is a BAP address distributed by the first host node for the first IAB node; or the first BAP address is a destination BAP address of the first data packet, and the second BAP address is a BAP address allocated by the second host node to the first IAB node.

And in the case that the third indication information indicates that the BAP address of the first data packet is rewritten and the first condition is not met, the first IAB node forwards the first data packet and rewrites the BAP route identification of the first data packet.

In the implementation manner, under the condition that the third indication information indicates that the BAP address of the first data packet is rewritten and the first condition is not satisfied, the first IAB node forwards the first data packet according to the second BAP routing identifier and the routing table; the first packet can be routed to the correct path.

In one possible implementation, the first condition further includes: the first indication information included with the first data packet indicates that the first data packet is to be delivered to an upper layer of a BAP layer of the first IAB node.

In one possible implementation, before the first IAB node forwards the first packet according to a routing table, the method further includes: the first IAB node rewrites the first BAP routing identity of the first data packet into the second BAP routing identity; the first IAB node forwarding the first packet according to a routing table comprises: and the first IAB node forwards the first data packet according to the next hop BAP address matched with the second BAP routing identifier in the routing table.

In one possible implementation manner, the processing, by the first IAB node, the first packet according to the third indication information in the first packet includes: the first IAB node submits the first data packet to an upper layer of a BAP layer of the first IAB node under the condition that the third indication information indicates that the BAP address of the first data packet is rewritten and a first condition is met; the first condition includes: the first BAP address matches the second BAP address; the first BAP address is obtained by rewriting a destination BAP address of the first data packet, and the second BAP address is a BAP address distributed by the first host node for the first IAB node; or the first BAP address is a destination BAP address of the first data packet, and the second BAP address is a BAP address allocated by the second host node to the first IAB node.

When the third indication information indicates that the BAP address of the first data packet is rewritten, the first IAB node can accurately judge whether the first data packet needs to be delivered to the upper layer of the BAP layer of the first IAB node or not by judging whether the first condition is met or not, and then the first data packet is routed to the correct transmission path.

In one possible implementation manner, the processing, by the first IAB node, the first packet according to the third indication information in the first packet includes: under the condition that the third indication information indicates that the BAP address of the first data packet is not rewritten and the third BAP address is not matched with the fourth BAP address, the first IAB node forwards the first data packet according to a routing table; the third BAP address is a destination BAP address of the first data packet, and the fourth BAP address is a BAP address allocated by the first host node to the first IAB node.

When the third indication information indicates that the BAP address of the first data packet is not rewritten, the first IAB node can accurately judge whether the first data packet needs to be delivered to the upper layer of the BAP layer of the first IAB node or not by judging whether the third BAP address is matched with the fourth BAP address or not, and then the first data packet is routed to a correct transmission path.

In one possible implementation manner, the processing, by the first IAB node, the first packet according to the third indication information in the first packet includes: the first IAB node submits the first data packet to an upper layer of a BAP layer of the first IAB node under the condition that the third indication information indicates that the BAP address of the first data packet is not rewritten and the third BAP address is matched with a fourth BAP address; the third BAP address is a destination BAP address of the first data packet, and the fourth BAP address is a BAP address allocated by the first host node to the first IAB node.

In a fifth aspect, an embodiment of the present application provides a communication method, which is applied to an IAB network that includes a first BAP topology and a second BAP topology, where the first BAP topology is managed by a first host node, the second BAP topology is managed by a second host node, and the first host node is different from the second host node; the method may be performed by a fifth communication apparatus, which may be a communication device or a communication apparatus capable of supporting a communication device to implement the functions required by the method, such as a system on a chip. The fifth communication apparatus is described as an example of the first host node. The method comprises the following steps: the first host node transmits a first data packet; the first data packet includes second indication information indicating that a destination BAP address of the first data packet is allocated by the first host node. Optionally, before the first host node transmits the first data packet, the first host node generates the first data packet according to data to be transmitted.

In this embodiment of the present application, the first host node sends the first data packet including the second indication information, so that the boundary node in the IAB network accurately determines whether to rewrite the BAP route identifier of the first data packet according to the second indication information.

In one possible implementation manner, the sending, by the first host node, the first data packet includes: sending the first data packet to an IAB node in the second BAP topology.

In some embodiments, when the first host node issues a data packet through the BAP topology managed by the first host node, the data packet may not include indication information indicating that a destination BAP address of the data packet is allocated by the first host node, so that resource overhead may be reduced without modifying a format of an existing data packet.

In this implementation manner, the first host node sends the first data packet containing the second indication information to the IAB node in the second BAP topology, so that the boundary node in the IAB network accurately determines, according to the second indication information, that the BAP route identifier of the first data packet needs to be rewritten.

In one possible implementation manner, the sending, by the first host node, the first data packet includes: sending the first data packet to an IAB node in the first BAP topology.

In this implementation, the first host node sends a first data packet containing second indication information to the IAB node in the first BAP topology, so that the border node in the IAB network accurately determines, according to the second indication information, that the BAP routing identifier of the first data packet does not need to be rewritten.

In a sixth aspect, an embodiment of the present application provides a communication method, where the method is applied to an IAB network, where the IAB network includes a first BAP topology and a second BAP topology, the first BAP topology is managed by a first host node, the second BAP topology is managed by a second host node, and the first host node is different from the second host node; the method may be performed by a sixth communication apparatus, which may be a communication device or a communication apparatus capable of supporting a communication device to implement the functions required by the method, such as a system-on-chip. The sixth communication apparatus is described as an example of the first host node. The method comprises the following steps: the first host node transmits a first data packet; the first data packet includes third indication information, where the third indication information indicates to rewrite a BAP address of the first data packet, or the third indication information indicates not to rewrite the BAP address of the first data packet. Optionally, before the first host node transmits the first data packet, the first host node generates the first data packet according to data to be transmitted.

In this embodiment of the present application, the first host node sends the first data packet including the third indication information, so that the border node in the IAB network accurately determines whether to rewrite the BAP routing identifier of the first data packet according to the third indication information.

In one possible implementation manner, the sending, by the first host node, the first data packet includes: and sending the first data packet to an IAB node in the second BAP topology, wherein the third indication information indicates to rewrite the BAP address of the first data packet.

In this implementation, the first data packet including the third indication information is sent to the IAB node in the second BAP topology, and the boundary node in the IAB network can accurately and quickly determine, according to the third indication information, that the BAP routing identifier of the first data packet does not need to be rewritten, and then route the first data packet to the correct transmission path.

In one possible implementation manner, the sending, by the first host node, the first data packet includes: and sending the first data packet to an IAB node in the first BAP topology, wherein the third indication information indicates that the BAP address of the first data packet is not rewritten.

In the implementation manner, the first data packet including the third indication information is sent to the IAB node in the first BAP topology, and the boundary node in the IAB network can accurately and quickly determine the BAP routing identifier of the first data packet to be rewritten according to the third indication information, so as to route the first data packet to the correct transmission path.

In a seventh aspect, an embodiment of the present application provides a communication device, where the communication device has a function of implementing the behavior in the method embodiment of the first aspect. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions. The communication device may be a first IAB node (border node) in an IAB network, the IAB network comprising a first BAP topology and a second BAP topology, the first BAP topology being managed by a first host node, the second BAP topology being managed by a second host node, the first host node being different from the second host node, at least one parent node of the first IAB node being managed by the second host node, the first IAB node belonging to the first BAP topology. In one possible implementation, the system includes a transceiver module and a processing module, wherein:

the receiving and sending module is used for receiving a first data packet;

the processing module is configured to process the first data packet according to a BAP topology corresponding to an ingress link that receives the first data packet and a BAP topology to which the first IAB node belongs.

With regard to the technical effects brought about by the seventh aspect or various possible implementations of the seventh aspect, reference may be made to the introduction of the technical effects of the first aspect or various possible implementations of the first aspect.

In an eighth aspect, embodiments of the present application provide a communication device having a function of implementing the behaviors in the method embodiment of the second aspect. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions. The communication device may be a first IAB node in an IAB network, the IAB network comprising a first BAP topology and a second BAP topology, the first BAP topology being managed by a first hosting node, the second BAP topology being managed by a second hosting node, the first hosting node being different from the second hosting node, the first IAB node being managed by the first hosting node, at least one parent node of the first IAB node being managed by the second hosting node, the first IAB node belonging to the first BAP topology.

In one possible implementation, the system includes a transceiver module and a processing module, wherein:

the transceiver module is configured to receive a second data packet from a child node of the first IAB node;

and the processing module is configured to, when a fourth BAP routing identifier having a mapping relationship with a third BAP routing identifier of the second data packet is obtained, control the transceiver module to forward the second data packet according to the fourth BAP routing identifier and a routing table.

With regard to the technical effects brought about by the eighth aspect or the various possible embodiments of the eighth aspect, reference may be made to the introduction to the technical effects of the second aspect or the various possible embodiments of the second aspect.

In a ninth aspect, embodiments of the present application provide a communication device, where the communication device has a function of implementing the behaviors in the method embodiment of the third aspect. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above. The communication device may be a first IAB node in an IAB network, the IAB network comprising a first BAP topology and a second BAP topology, the first BAP topology being managed by a first host node, the second BAP topology being managed by a second host node, the first host node being different from the second host node, the first IAB node being managed by the first host node, at least one parent node of the first IAB node being managed by the second host node, the first IAB node belonging to the first BAP topology.

the receiving and sending module is used for receiving a first data packet;

the processing module is configured to process the first data packet according to the second indication information in the first data packet and the BAP topology to which the first IAB node belongs; the second indication information indicates that the destination BAP address of the first data packet is allocated by the first host node, or the second indication information indicates that the destination BAP address of the first data packet is allocated by the second host node.

With regard to the technical effects brought about by the various possible embodiments of the ninth aspect or the ninth aspect, reference may be made to the introduction of the technical effects of the various possible embodiments of the third aspect or the third aspect.

In a tenth aspect, the present application provides a communication apparatus having a function of implementing the behavior in the method embodiment of the fourth aspect. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above. The communication device may be a first IAB node in an IAB network, the IAB network comprising a first BAP topology and a second BAP topology, the first BAP topology being managed by a first hosting node, the second BAP topology being managed by a second hosting node, the first hosting node being different from the second hosting node, the first IAB node being managed by the first hosting node, at least one parent node of the first IAB node being managed by the second hosting node, the first IAB node belonging to the first BAP topology.

the receiving and sending module is used for receiving a first data packet;

the processing module is configured to process the first data packet according to third indication information in the first data packet; the third indication information indicates to rewrite the BAP address of the first data packet, or the third indication information indicates not to rewrite the BAP address of the first data packet.

With regard to the technical effects brought about by the tenth aspect or various possible embodiments of the tenth aspect, reference may be made to the introduction of the technical effects of the fourth aspect or various possible embodiments of the fourth aspect.

In an eleventh aspect, embodiments of the present application provide a communication device having a function of implementing the behavior in the method embodiment of the fifth aspect. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions. The communication device may be a first hosting node in an IAB network comprising a first BAP topology and a second BAP topology, the first BAP topology being managed by the first hosting node, the second BAP topology being managed by a second hosting node, the first hosting node being different from the second hosting node. In one possible implementation, the system includes a transceiver module and a processing module, wherein:

the processing module is used for controlling the transceiver module to send a first data packet; the first data packet includes second indication information indicating that a destination BAP address of the first data packet is allocated by the first host node.

In a possible implementation manner, the processing module is specifically configured to control the transceiver module to send the first data packet to an IAB node in the second BAP topology.

With regard to the technical effects brought about by the eleventh aspect or the various possible embodiments of the eleventh aspect, reference may be made to the introduction to the technical effects of the fifth aspect or the various possible embodiments of the fifth aspect.

In a twelfth aspect, the present application provides a communication apparatus having a function of implementing the behavior in the method embodiment of the sixth aspect. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions. The communication device may be a first host node in an IAB network comprising a first BAP topology and a second BAP topology, the first BAP topology being managed by the first host node, the second BAP topology being managed by a second host node, the first host node being different from the second host node. In one possible implementation, the system includes a transceiver module and a processing module, wherein:

the processing module is used for controlling the transceiver module to send a first data packet; the first data packet includes third indication information, where the third indication information indicates to rewrite a BAP address of the first data packet, or the third indication information indicates not to rewrite the BAP address of the first data packet.

In a possible implementation manner, the processing module is specifically configured to control the transceiver module to send the first data packet to an IAB node in the second BAP topology, and the third indication information indicates to rewrite a BAP address of the first data packet.

In a possible implementation manner, the processing module is specifically configured to control the transceiver module to send the first data packet to an IAB node in the first BAP topology, and the third indication information indicates that a BAP address of the first data packet is not rewritten.

With regard to the technical effects brought about by the twelfth aspect or the various possible embodiments of the twelfth aspect, reference may be made to the introduction to the technical effects of the sixth aspect or the various possible embodiments of the sixth aspect.

In a thirteenth aspect, the present application provides a communication device comprising a processor, which can be used to execute computer-executable instructions stored by a memory to cause a method shown in the above first aspect or any possible implementation manner of the first aspect to be performed, or to cause a method shown in the above second aspect or any possible implementation manner of the second aspect to be performed, or to cause a method shown in the above third aspect or any possible implementation manner of the third aspect to be performed, or to cause a method shown in the above fourth aspect or any possible implementation manner of the fourth aspect to be performed, or to cause a method shown in the above fifth aspect or any possible implementation manner of the fifth aspect to be performed, or to cause a method shown in the above sixth aspect or any possible implementation manner of the sixth aspect to be performed.

In the embodiment of the present application, in the process of executing the method, the process related to sending information in the method may be understood as a process of outputting information based on an instruction of a processor. In outputting the information, the processor outputs the information to the transceiver for transmission by the transceiver. After being output by the processor, the information may be further processed, possibly before reaching the transceiver. Similarly, when the processor receives incoming information, the transceiver receives the information and inputs it to the processor. Further, after the transceiver receives the information, the information may need to be further processed before being input to the processor.

The operations involving the processor, such as transmission and/or reception, may be generally understood as processor-based instruction output if not specifically stated or if not contradicted by actual role or inherent logic in the associated description.

In implementation, the processor may be a processor dedicated to performing the methods, or may be a processor executing computer instructions in a memory to perform the methods, such as a general-purpose processor. For example, the processor may also be adapted to execute a program stored in the memory, which when executed, causes the communication apparatus to perform a method as illustrated in the first aspect above or any possible implementation manner of the first aspect.

In one possible implementation, the memory is located outside the communication device.

In one possible implementation, the memory is located within the communication device described above.

In the embodiments of the present application, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.

In a possible implementation, the communication device further comprises a transceiver for receiving messages or sending messages, etc.

In a fourteenth aspect, the present application provides a communication device comprising processing circuitry and interface circuitry for acquiring data or outputting data; the processing circuit is configured to perform a corresponding method as shown in the first aspect or any possible implementation of the first aspect, or the processing circuit is configured to perform a corresponding method as shown in the second aspect or any possible implementation of the second aspect, or the processing circuit is configured to perform a corresponding method as shown in the third aspect or any possible implementation of the third aspect, or the processing circuit is configured to perform a corresponding method as shown in the fourth aspect or any possible implementation of the fourth aspect, or the processing circuit is configured to perform a corresponding method as shown in the fifth aspect or any possible implementation of the fifth aspect, or the processing circuit is configured to perform a corresponding method as shown in the sixth aspect or any possible implementation of the sixth aspect.

In a fifteenth aspect, the present application provides a computer-readable storage medium for storing a computer program, which, when run on a computer, causes the method shown in the first aspect or any possible implementation of the first aspect to be performed, or causes the method shown in the second aspect or any possible implementation of the second aspect to be performed, or causes the method shown in the third aspect or any possible implementation of the third aspect to be performed, or causes the method shown in the fourth aspect or any possible implementation of the fourth aspect to be performed, or causes the method shown in the fifth aspect or any possible implementation of the fifth aspect to be performed, or causes the method shown in the sixth aspect or any possible implementation of the sixth aspect to be performed.

Sixteenth aspect, the present application provides a computer program product comprising a computer program or computer code which, when run on a computer, causes a method as shown in the above first aspect or any possible implementation of the first aspect to be performed, or causes a method as shown in the above second aspect or any possible implementation of the second aspect to be performed, or causes a method as shown in the above third aspect or any possible implementation of the third aspect to be performed, or causes a method as shown in the above fourth aspect or any possible implementation of the fourth aspect to be performed, or causes a method as shown in the above fifth aspect or any possible implementation of the fifth aspect to be performed, or causes a method as shown in the above sixth aspect or any possible implementation of the sixth aspect to be performed.

In a seventeenth aspect, the present application provides a communication system comprising a first host node, a second host node, a first IAB node, one or more IAB nodes controlled by the first host node, and one or more IAB nodes controlled by the second host node; the first host node is different from the second host node, and the first IAB node is configured to perform the method of any of the first aspect to the fourth aspect.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments or the background art of the present application, the drawings required to be used in the embodiments or the background art of the present application will be described below.

Fig. 1 is a schematic structural diagram of an IAB system according to an embodiment of the present application;

fig. 2 is a schematic structural diagram of an IAB node according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of an IAB network according to an embodiment of the present application;

fig. 4 is a schematic diagram of a control plane protocol architecture in an IAB network according to an embodiment of the present application;

fig. 5 is a schematic diagram of a user plane protocol architecture in an IAB network according to an embodiment of the present application;

fig. 6 is an example of an IAB network architecture diagram provided in an embodiment of the present application;

fig. 7 is an example of a BAP topology of an IAB network according to an embodiment of the present disclosure;

fig. 8 is a flowchart of a routing method according to an embodiment of the present application;

fig. 9 is a flowchart of another routing method provided in the embodiment of the present application;

fig. 10 is a flowchart of another routing method provided in the embodiment of the present application;

fig. 11 is a flowchart of another routing method provided in the embodiment of the present application;

fig. 12 is a flowchart of another routing method provided in the embodiment of the present application;

fig. 13 is a flowchart of another routing method provided in the embodiment of the present application;

fig. 14 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 17 is a schematic structural diagram of another communication device according to an embodiment of the present application.

Detailed Description

The terms "first" and "second", etc. in the description, claims, and drawings of the present application are used only for distinguishing different objects, and are not used for defining the order, timing, priority, or importance of a plurality of objects. The "plurality" in the embodiment of the present application means two or more. Furthermore, the terms "comprising" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. Such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements recited, but may alternatively include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. In addition, the character "/" generally indicates that the preceding and succeeding related objects are in an "or" relationship, unless otherwise specified.

Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those skilled in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.

Before describing the present application, a part of terms in the embodiments of the present application will be briefly explained so as to be easily understood by those skilled in the art.

1) A terminal-side device is a device that provides voice and/or data connectivity to a user. In this embodiment, the terminal-side device may be referred to as a User Equipment (UE), a terminal device, a terminal, a Mobile Station (MS), a Mobile Terminal (MT), and the like. For example, the terminal side device may comprise a handheld device having wireless connection capability, or a communication device connected to a wireless modem. The terminal side device may communicate with the core network via a Radio Access Network (RAN), exchanging voice and/or data with the RAN.

Examples of some terminal-side devices are: a Mobile Station (MS), a subscriber unit (subscriber unit), a cellular phone (cellular phone), a smart phone (smart phone), a wireless data card, a Personal Digital Assistant (PDA), a computer, a tablet computer, a wireless modem (modem), a handheld device (handset), a laptop computer (laptop computer), a Machine Type Communication (MTC) terminal, a wearable device, a vehicle-mounted terminal device, and the like. Terminal side devices also include constrained devices, such as devices that consume less power, or devices that have limited memory, or devices that have limited computing power, and the like. The terminal-side device further includes information sensing devices such as a barcode, a Radio Frequency Identification (RFID), a sensor, a Global Positioning System (GPS), and a laser scanner.

The functions of the terminal-side device may be implemented by hardware components inside the terminal device, and the hardware components may be a processor and/or a programmable chip inside the terminal device. Alternatively, the chip may be implemented by an application-specific integrated circuit (ASIC) or a Programmable Logic Device (PLD). The PLD may be any one of or any combination of a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), a system on a chip (SOC).

2) A donor base station (donor gnnodeb), which may also be referred to as a donor node, may access the core network through the donor node. That is, the donor base station is a device for accessing the terminal-side device to the core network in the communication system. The host base station is typically connected to the core network by a wired link (e.g., fiber optic cable). The donor base station may be responsible for receiving and forwarding data of the core network to the wireless backhaul device (e.g., IAB node), or receiving and forwarding data of the wireless backhaul device to the core network. The host base station may typically be connected to the network by wire.

As an example, the donor base station may include a Radio Network Controller (RNC), a Node B (NB), a Base Station Controller (BSC), a Base Transceiver Station (BTS), a home base station (e.g., home evolved NodeB or home Node B, HNB), a Base Band Unit (BBU), etc., may also include an evolved NodeB (NodeB or eNB or e-NodeB, evolved Node B) in an evolved LTE system (LTE-Advanced, LTE-a), or may also include a next generation Node B (next generation Node B, G NB) in a fifth generation mobile communication technology (5G) New Radio (NR) system, etc. As another example, the Donor base station may include a Centralized Unit (CU) (herein abbreviated as Donor nb-CU) and a Distributed Unit (DU) (herein abbreviated as Donor nb-DU). The gNB-CU and the gNB-DU are connected via an F1 interface, which F1 interface may in turn further comprise a control plane interface (F1-C) and a user plane interface (F1-U). The Donor-CU is connected with the core network through a Next Generation (NG) interface. The gNB-CU or the Donor-CU can also exist in a form of separating a User Plane (UP) (abbreviated as CU-UP in the application) from a Control Plane (CP) (abbreviated as CU-CP in the application), namely the gNB-CU or the Donor-CU is composed of the CU-CP and the CU-UP. One gNB-CU may include one gNB-CU-CP and at least one gNB-CU-UP. Alternatively, one Donor-CU may include one Donor-CU-CP and at least one Donor-CU-UP.

The functionality of the donor base station may be implemented by hardware components within the donor base station, such as a processor and/or a programmable chip within the donor base station as described above. For example, the chip may be implemented by an ASIC, or a PLD. The PLD may be any one of a CPLD, an FPGA, a GAL, an SOC, or any combination thereof.

Technical features related to embodiments of the present application are described below.

In the IAB network, the IAB node may establish a wireless backhaul link with one or more upper nodes and access the core network through the upper nodes. The upper node may perform certain control (e.g., data scheduling, timing modulation, power control, etc.) on the relay node through various signaling. In addition, the relay node may establish an access link with one or more subordinate nodes and provide access services to the one or more subordinate nodes. The upper node of the relay node may be a base station or another relay node. The lower node of the relay node may be a terminal or another relay node. In some cases, an upper node of an IAB node may also be referred to as its upstream node or parent node, and a lower node of the IAB node may also be referred to as its downstream node or child node.

Fig. 1 shows an IAB system, where an IAB node provides wireless access and wireless backhaul of access services for UEs. The IAB donor node (IAB donor node) provides a wireless backhaul function to the IAB node and provides an interface for the UE and the core network. The IAB node is connected to the IAB donor node through a wireless backhaul link, so that the UE served by the IAB node is connected with the core network.

Fig. 2 shows a schematic structure diagram of an IAB node. The IAB node in NR can be divided into MT and DU. MT may also be understood as a component in the IAB node like a UE, which is referred to as a function residing on the IAB node. Since the MT functions like a general UE, it can be understood that the MT is used for the IAB node to communicate with the upper node. The DU is relative to the CU functions of the network device, and is used by the IAB node to communicate with subordinate nodes. It should be understood that the upper node may be a base station or other IAB node, and the lower node may be a UE or other IAB node.

The routing method provided by the embodiment of the application can be applied to various communication systems including relay nodes, such as an NR system, an LTE-a system, a Worldwide Interoperability for Microwave Access (WiMAX), a Wireless Local Area Network (WLAN), and the like. In LTE, the relay node is generally referred to as RN. In NR, a relay node is generally referred to as an IAB node. In some embodiments, the relay node may also be referred to as a relay device, or a relay transmission and reception point (rrtp), and the upper node of the relay node may be a network device (including a DU of the network device, or including a CU of the network device, etc.).

Fig. 3 shows an example of an IAB network comprising a plurality of UEs and a plurality of IAB nodes. Fig. 3 is an example of a system including 2 UEs and 5 IAB nodes. Wherein, the 2 UEs are UE1 and UE2, and the 5 IAB nodes are IAB node 1 to IAB node 5, respectively. It should be understood that the bold lines of fig. 3 illustrate the access link and the thin lines illustrate the backhaul link. Wherein, the UE2 can be connected with the host base station via the IAB node 5, the IAB node 2 and the IAB node 1. UE2 may also connect to the donor base station via IAB node 4, IAB node 2, and IAB node 1. Or UE2 may also be connected to the donor base station via IAB node 4, IAB node 3, and IAB node 1. UE1 may connect with the donor base station via IAB node 4, IAB node 3, and IAB node 1. UE1 may connect with the donor base station via IAB node 4, IAB node 2, and IAB node 1.

It should be noted that the communication system shown in fig. 3 is only an example, and does not limit an application scenario to which the embodiment of the present application is applied. It should be understood that the IAB node is used in the embodiment of the present application only for the description, and does not indicate that the scheme of the embodiment of the present application is only used in the NR scenario. In the embodiment of the present application, an IAB node may refer to any node or device having a relay function in a general way, and the use of an IAB node and a relay node in the implementation of the present application should be understood to have the same meaning.

In an IAB network, an IAB node is connected to a core network via an IAB host node. For example, under the 5G architecture of stand alone networking (SA), IAB nodes are connected to a 5G core network (5G core network,5gc/5 GCN) via IAB host nodes. For another example, in a Dual Connectivity (DC) or multi-connectivity (MC) 5G architecture (e.g., non-independent networking (NSA scenario, etc.), on the main path, the IAB node may be connected to an Evolved Packet Core (EPC) via an evolved NodeB (eNB) or connected to the 5G core via an IAB host.

In an IAB network, one or more IAB nodes may be included on one transmission path between a UE and an IAB host. Each IAB node needs to maintain a wireless backhaul link to the parent node and also needs to maintain a wireless link with the child node. If the sub-node of the IAB node is a UE, a radio access link is formed between the IAB node and its sub-node (i.e., UE). If the sub-node of the IAB node is another IAB node, a wireless backhaul link is formed between the IAB node and the sub-node (i.e., another IAB node). Referring to fig. 3, in the path "UE1 → IAB node 4 → IAB node 3 → IAB node 1 → IAB home", UE1 accesses IAB node 4 through a wireless access link, IAB node 4 connects to IAB node 3 through a wireless backhaul link, IAB node 3 connects to IAB node 1 through a wireless backhaul link, and IAB node 1 connects to IAB home node through a wireless backhaul link.

In the embodiment of the present application, an access IAB node refers to an IAB node to which a UE accesses, and an intermediate IAB node refers to an IAB node that provides a wireless backhaul service for the UE or the IAB node. Illustratively, referring to fig. 3, in the path UE1 → IAB node 4 → IAB node 3 → IAB node 1 → IAB home ", IAB node 4 is an access IAB node and IAB node 3 and IAB node 1 are intermediate IAB nodes. It should be noted that, for a UE accessing the IAB node, one IAB node is an access IAB node; for UEs accessing other IAB nodes, it is an intermediate IAB node. Therefore, whether an IAB node is specifically an access IAB node or an intermediate IAB node is not fixed and may be determined according to a specific application scenario.

There is an F1 interface between the DU of the IAB node and the CU hosted by the IAB. The F1 interface may comprise two parts, a control plane and a user plane, wherein the part of the user plane is maintained between the IAB-DU and the IAB knor CU-UP, and the control plane part is maintained between the IAB-DU and the IAB knor CU-CP. Of course, the F1 interface may also be referred to as an F1 interface, and the name of the interface is not limited in the embodiment of the present application. And this interface is referred to herein as the F1 interface for example.

The F1 interface may support a user plane protocol (F1-U/F1-U) and a control plane protocol (F1-C/F1-C), the user plane protocol comprising one or more of the following protocol layers: a General Packet Radio Service (GPRS) tunneling protocol user plane (GTP-U) protocol layer, a User Datagram Protocol (UDP) protocol layer, an Internet Protocol (IP) protocol layer, and the like; the control plane protocol includes one or more of the following protocol layers: f1 application protocol (F1 AP), stream Control Transport Protocol (SCTP), IP protocol layer, and the like. Through the control plane of the F1/F1 star interface, the IAB node and the IAB host may perform interface management, manage IAB-DU, and perform UE context related configuration. Through the user plane of the F1/F1 star interface, the functions of user plane data transmission, downlink transmission state feedback and the like can be executed between the IAB node and the IAB host.

For example, please refer to fig. 4 and fig. 5, wherein fig. 4 is a schematic diagram of a control plane protocol architecture in an IAB network, and fig. 5 is a schematic diagram of a user plane protocol architecture in the IAB network.

For the control plane, as shown in fig. 4, a Uu interface is established between UE1 and IAB2-DU, and the peer protocol layers include a Radio Link Control (RLC) layer, a Media Access Control (MAC) layer, and a physical layer (PHY) layer. An F1-C interface is established between the IAB2-DU and the IAB donor CU1, and peer protocol layers comprise an F1AP layer and an SCTP layer. The IAB donor DU1 and the IAB donor CU1 are connected by a wire, and the peer protocol layers include an Internet Protocol (IP) layer, L2 and L1. BL is established between the IAB node 2 and the IAB node 3, between the IAB node 3 and the IAB node 1, and between the IAB node 1 and the IAB node DU1, and peer protocol layers include a Backhaul Adaptation Protocol (BAP) layer, an RLC layer, an MAC layer, and a PHY layer. In addition, a peer Radio Resource Control (RRC) layer and a Packet Data Convergence Protocol (PDCP) layer are established between the UE1 and the IAB donor CU1, and a peer IP layer is established between the IAB2-DU and the IAB donor DU 1.

It can be seen that, compared with the control plane protocol stack of a single air interface, the control plane protocol stack of the IAB network, the DU accessed to the IAB node implements the function of the single air interface of the gNB-DU (i.e., the function of establishing a peer RLC layer, an MAC layer, and a PHY layer with the UE, and the function of establishing a peer F1AP layer and an SCTP layer with the CU). That is, the DU accessed to the IAB node in the IAB network realizes the function of a single air interface gNB-DU; the IAB donor CU realizes the function of the single-air-interface gNB-CU.

On the control plane, RRC messages are transported in F1AP messages encapsulated between the access IAB node and the IAB donor CU. Specifically, in the uplink direction, the UE1 encapsulates the RRC message in a PDCP Protocol Data Unit (PDU), and sequentially performs processing on an RLC layer, an MAC layer, and a PHY layer, and then sends the RRC message to the IAB2-DU. The IAB2-DU is processed by a PHY layer, an MAC layer and an RLC layer in sequence to obtain a PDCP PDU, the PDCP PDU is packaged in an F1AP message, and the PDCP PDU is processed by an SCTP layer and an IP layer in sequence to obtain an IP packet. The IAB2-MT sends the IP packet to the IAB3-DU after processing of a BAP layer, an RLC layer, an MAC layer and a PHY layer respectively. The IAB3-DU is processed by a PHY layer, an MAC layer, an RLC layer and a BAP layer in sequence to obtain an IP packet, and then the IAB3-MT adopts an operation similar to the IAB2-MT to send the IP packet to the IAB1-DU. Similarly, IAB1-MT sends the IP packet to IAB denor DU 1. After analyzing the IAB donor DU1 to obtain an IP packet, sending the IP packet to the IAB donor CU1, and processing the IP packet by the IAB donor CU1 through the SCTP layer, the F1AP layer and the PDCP layer in sequence to obtain an RRC message. The downstream direction is similar and will not be described further herein.

For the user plane, as shown in fig. 5, a Uu interface is established between UE1 and IAB2-DU, and peer protocol layers include an RLC layer, a MAC layer, and a PHY layer. An F1-U interface is established between the IAB2-DU and the IAB donor CU1, and the peer protocol layers comprise a GTP-U layer and a User Datagram Protocol (UDP) layer. The IAB donor DU1 and the IAB donor CU1 are connected through a wire, and peer protocol layers comprise an IP layer, an L2 layer and an L1 layer. BL is established between IAB node 2 and IAB node 3, between IAB node 3 and IAB node 1, and between IAB node 1 and IAB node DU1, and peer protocol layers include BAP layer, RLC layer, MAC layer and PHY layer. In addition, a peer SDAP layer and a peer PDCP layer are established between the UE1 and the IAB denor CU1, and a peer IP layer is established between the IAB2-DU and the IAB denor DU 1.

It can be seen that, compared with the single-air-interface user plane protocol stack, the user plane protocol stack of the IAB network, the DU of the IAB access node implements part of functions of the single-air-interface gNB-DU (i.e., functions of establishing a peer RLC layer, an MAC layer, and a PHY layer with the terminal, and establishing a peer GTP-U layer and a peer UDP layer with the IAB donor CU 1). It can be understood that the DU of the IAB access node realizes the function of a single air interface gNB-DU; the IAB donor CU realizes the function of a single-air-interface gNB-CU.

On the user plane, PDCP data packets are transported in GTP-U tunnels between the access IAB node and the IAB donor CU. The GTP-U tunnel is established on the F1-U interface.

The routing method provided by the application is mainly applied to IAB networks, including IAB networks of independent networking (SA) and IAB networks of non-independent Networking (NSA). The IAB node comprises an MT part and a DU part, the IAB donor can be further divided into the DU and CU parts, and the CU can be further divided into the CU-CP and CU-UP parts. Fig. 6 is an example of an IAB network architecture diagram provided in an embodiment of the present application. Fig. 6 shows an example of an IAB node connected to an IAB donor over a wireless backhaul link.

Fig. 6 is an example of a UE including 1 UE, 2 IAB nodes, and 2 IAB donors. The two IAB nodes are IAB node 1 and IAB node 2, and both comprise an MT part and a DU part; these two IAB donors are IAB donor 1 and IAB donor 2, respectively. The 2 IAB donors are IAB donor 1 and IAB donor 2, each IAB donor may be further divided into DU and CU sections, and the CU may be further divided into CU-CP and CU-UP sections. In fig. 6, the MT of IAB node 2 and the DU of IAB node 1, the MT of IAB node 1 and the DU of IAB donor 1, and the MT of IAB node 1 and the DU of IAB donor 2 all communicate via Backhaul (BH) links (link); a Uu interface is established between the UE and the IAB 2-DU; an F1-C interface is established between the IAB denor DU and the IAB denor CU-CP, and an F1-U interface is established between the IAB denor DU and the IAB denor CU-UP; the DU of IAB donor 2 and the CU of IAB donor 1 are connected through IP network.

The IAB node may be singly connected to one parent node or doubly connected to two parent nodes when the IAB node operates in the SA mode. Wherein the two parent nodes may be controlled by the same IAB donor, alternatively, by different IAB donors. An F1 interface is established between the DU portion of the IAB node and one IAB node, and the IAB node may be connected to a 5G core network, that is, the dotted portion in fig. 6. Wherein the IAB-denor-CU-CP is connected to control plane network elements (e.g., access and mobility management functions) in the 5GC through an NG control plane interface (NG-C), and the IAB-denor-CU-UP is connected to user plane network elements (e.g., user plane functions) in the 5GC through an NG user plane interface (NG-U).

When the IAB node operates in the NSA mode, the IAB-donor-CU-UP may be connected to the EPC (e.g., connected to a Serving Gateway (SGW)) through an S1 user plane interface (S1-U), the MeNB may have an LTE Uu air interface with the MT of the IAB node, the MeNB may have an X2-C interface with the IAB-donor-CU-CP, and the MeNB may be connected to the EPC (including an S1 interface user plane and an S1 interface control plane) through an S1 interface.

In another possible scenario, the MeNB in fig. 6 may also be replaced by a base station gNB of 5G. The LTE-Uu interface in fig. 6 is replaced with an NR-Uu interface, the gNB may establish an interface of a user plane and/or a control plane with the 5GC, the gNB and the IAB-donor provide a dual connectivity service for the IAB node, and the gNB may serve as a primary base station of the IAB node or a secondary base station.

The routing method provided by the application is used for solving the data forwarding problem of the boundary node (boundary node) in the IAB network. In other words, the routing method provided by the present application is used to solve the problem of how a border node in an IAB network routes a packet passing through it to a correct path. Border nodes in an IAB network may be referred to as border IAB nodes, or simply border nodes. The boundary nodes in the IAB network have the following characteristics: the edge node's DU terminates at an IAB-donor-CU different from the IAB-donor-CU at which its at least one parent node's DU terminates. The definition of a border IAB node (Boundary IAB node) may be as follows: IAB-node, while IAB-DU is terminated to a differential IAB-donor-CU this a parent DU. Assuming that an IAB node in the IAB network has two parents, the DU of the IAB node terminates in the CU of IAB-donor 1, the DU of one parent of the IAB node terminates in the CU of IAB-donor 1, and the DU of the other parent of the IAB node terminates in the CU of IAB-donor 2, the IAB node is a boundary node.

Fig. 7 is an example of a BAP topology of an IAB network according to an embodiment of the present application. In the present application, the BAP topology refers to a topology of a BAP layer. In fig. 7, IAB-MT1 and IAB-DU1 are two parts included in IAB node 1, IAB-MT2 and IAB-DU2 are two parts included in IAB node 2, IAB-MT3 and IAB-DU3 are two parts included in IAB node 3, and IAB-MT4 and IAB-DU4 are two parts included in IAB node 4. As shown in FIG. 7, the topology in the solid box represents BAP topology 1 controlled by Donor-CU1 and the topology in the dashed box represents BAP topology 2 controlled by Donor-CU 2. Wherein, BAP topology 1 includes IAB node 1, IAB node 2, and IAB node 4; BAP topology 2 includes IAB node 3. In fig. 7, the MT of IAB node 2, i.e. IAB-MT2, is connected to Donor-DU1 and Donor-DU2, respectively, via dual connections. The F1 interface of IAB node 2 is terminated on CU1, that is, CU1 is the F1-termination node of IAB node 2. For such BAP topologies, it may happen that traffic of one IAB node or traffic of UEs connected under the IAB node may be transmitted via several different classes of nodes. These different classes of nodes may include an IAB node managed by CU1 (e.g., IAB node 4) and an IAB node managed by CU2 (e.g., IAB node 3).

As shown in fig. 7, the IAB node 2 may receive the data packets sent by the CU1 via the Donor-DU1 and the IAB node 1 (see the path indicated by the solid arrows in fig. 7), and may also receive the data packets sent by the CU1 via the Donor-DU2 and the IAB node 3 (see the path indicated by the dashed arrows in fig. 7). IAB node 2 is a border node in the IAB network shown in fig. 7. Since the F1 interface of IAB node 2 terminates on CU1 (the DU for IAB node 2 terminates on CU 1), the DU for one parent node of IAB node 2 (IAB node 3) terminates on CU2.

IAB node 2, acting as a border node, needs to route the packets passing through it to the correct path. In fig. 7, the BAP routing ID recognizable by each IAB node in the BAP topology 1 under the control (or management) of CU1 is different from the BAP routing ID recognizable by each IAB node in the BAP topology 2 under the control (or management) of CU2. That is, the BAP routing ID that each IAB node within the BAP topology 1 can identify is not identifiable to each IAB node within the BAP topology 2 that is controlled (or managed) by the CU2. Likewise, the BAP routing ID that each IAB node within BAP topology 2 can identify is also unidentifiable to each IAB node within BAP topology 1 that is controlled by CU 1. For the downlink data packet, IAB node 2 needs to rewrite the BAP routing ID of the data packet from BAP topology 2, and after converting it into the BAP routing ID recognizable by the IAB node in BAP topology 1, can forward it to the downstream node. Similarly, for the uplink data packet, if the data packet received by the IAB node 2 needs to be transmitted through the BAP topology 2, the IAB node 2 needs to change the BAP routing ID rewriting of the original BAP topology 1 of the data packet into the BAP routing ID that can be recognized by the IAB node in the BAP topology 2, so as to forward the BAP routing ID to the upstream IAB node in the BAP topology 2. It can be seen that for a border node (e.g. IAB node 2) in the IAB network, if a packet passing through the border node is to be routed to a correct path, it needs to accurately determine whether the BAP routing ID of the rewriting packet is needed. The routing method provided by the application can accurately judge whether the BAP routing ID of the rewriting data packet is needed or not, and routes the data packet passing through the boundary node to a correct path.

The following describes a routing method provided in an embodiment of the present application with reference to the drawings. Fig. 8 is a flowchart of a routing method according to an embodiment of the present application. The routing method provided by the embodiment of the application can be applied to an IAB network, wherein the IAB network comprises a first BAP topology and a second BAP topology, the first BAP topology is managed by a first host node, the second BAP topology is managed by a second host node, and the first host node is different from the second host node. As shown in fig. 8, the method includes:

801. the first IAB node receives the first data packet.

The first IAB node is managed by a first host node, and at least one parent node of the first IAB node is managed by a second host node. That is, the first IAB node is a border node in the IAB network. The first IAB node belongs to a first BAP topology. The first packet may be a downstream packet, i.e., a packet from a node upstream of the first IAB node.

The IAB network illustrated in fig. 7 may be an example of one type of IAB network to which the method of fig. 8 is applicable. Wherein the first BAP topology corresponds to BAP topology 1, the second BAP topology corresponds to BAP topology 2, the first host node corresponds to CU1, the second host node corresponds to CU2, and the first IAB node corresponds to IAB node 2.

In a possible implementation manner, the method further includes: when a Radio Link Failure (RLF) occurs on a first radio link between a first IAB node and a parent node thereof, the first IAB node sends fourth indication information to a child node thereof during or before recovering (recovering) the first radio link; the fourth indication information indicates that the first IAB node generates RLF and a time for transmitting the fourth indication information is in or before a process of restoring the first radio link. The strength of the fourth indication information may be a BAP address (addrese) or a Backhaul (BH) link (link). In this implementation, the first IAB node may notify its child nodes in time that RLF has occurred between the first IAB node and its parent node. Further, after the first radio link between the first IAB node and the first parent node is successfully restored, the first IAB node sends fifth indication information to its child node; the fifth indication information indicates that the RLF recovery of the first IAB node is successful. In this implementation, the first IAB node sends the fifth indication information to its child node; its child nodes may be informed that the RLF recovery was successful.

802. And the first IAB node processes the first data packet according to the BAP topology corresponding to the entry link for receiving the first data packet and the BAP topology to which the first IAB node belongs.

The BAP topology corresponding to the ingress link through which the first IAB node receives the first data packet may be a BAP topology to which the IAB node that sends the first data packet to the first IAB node belongs. The BAP topology to which the ingress link of the first IAB node receiving the first data packet corresponds may be one of a first BAP topology and a second BAP topology. In some embodiments, after receiving the first data packet, the first IAB node may use the BAP topology to which the IAB node that sent the first data packet belongs as the BAP topology corresponding to the ingress link that received the first data packet. For example, a first IAB node receives a first data packet sent by its upstream node 1, and the BAP topology to which the upstream node 1 belongs is the BAP topology corresponding to the ingress link that receives the first data packet. Since the BAP topology to which the IAB node that sends the first data packet to the first IAB node belongs is the same as the BAP topology corresponding to the ingress link that the first IAB node receives the first data packet, step 801 may be replaced with: and the first IAB node processes the first data packet according to the BAP topology of the IAB node which sends the first data packet and the BAP topology of the first IAB node. The first IAB node knows the BAP topology to which it belongs. In some embodiments, the first IAB node belongs to the first BAP topology, i.e., the BAP topology to which the first IAB node belongs is the first BAP topology. In some embodiments, the configuration information in the first IAB node indicates a BAP topology to which the first IAB node belongs. In these embodiments, the first IAB node may determine from its configuration information the BAP topology to which it belongs.

An ingress link (ingress link) for receiving a downlink data packet by a first IAB node may include a first ingress link and a second ingress link, where a BAP topology corresponding to the first ingress link is a first BAP topology, and a BAP topology corresponding to the second ingress link is a second BAP topology. It should be understood that, if the first IAB node receives the first data packet through the first ingress link, the BAP topology corresponding to the ingress link through which the first IAB node receives the first data packet is the first BAP topology; if the first IAB node receives the first data packet through the second ingress link, the BAP topology corresponding to the ingress link through which the first IAB node receives the first data packet is the second BAP topology. In some embodiments, the first IAB node may store a first correspondence of the first ingress link with the first BAP topology and a second correspondence of the second ingress link with the second BAP topology, from which the first IAB node may determine that the first ingress link corresponds to the first BAP topology and from which the first IAB node may determine that the second ingress link corresponds to the second BAP topology. In some embodiments, the first IAB node may store a correspondence between each ingress link and its corresponding BAP topology, and the first IAB node may determine, according to the correspondences, the BAP topology corresponding to any ingress link that receives the downlink data packet.

In some embodiments, step 802 may be replaced with: and the first IAB node processes the first data packet according to the second indication information in the first data packet and the BAP topology to which the first IAB node belongs. The second indication information indicates that the destination BAP address of the first packet is allocated by the first host node. Alternatively, the second indication information indicates that the destination BAP address of the first packet is allocated by the second host node. The second indication information may be included in a header of the first packet. For example, the second indication information may be indication information (occupying one or more bits) additionally added on an existing BAP address. For example, the second indication information is two additional bits added to the existing BAP address; if the second indication information is 00, the second indication information indicates that the destination BAP is allocated by the first host node; if the second indication information is 11, the second indication information indicates that the destination BAP is allocated by the second host node. It should be understood that, if the second indication information indicates that the destination BAP address of the first data packet is allocated by the first host node, it indicates that the BAP topology corresponding to the ingress link of the first IAB node receiving the first data packet is the first BAP topology; and if the second indication information indicates that the destination BAP address of the first data packet is allocated by the second host node, indicating that the BAP topology corresponding to the entry link of the first IAB node for receiving the first data packet is the second BAP topology.

The first IAB node can determine whether to rewrite the BAP routing ID of the first data packet according to the second indication information and the BAP topology to which the first IAB node belongs. For example, the first IAB node determines to rewrite the BAP routing ID of the first packet if it belongs to the first BAP topology and the second indication information indicates that the destination BAP address of the first packet is allocated by the second host node. For another example, the first IAB node determines not to rewrite the BAP routing ID of the first data packet when it belongs to the first BAP topology and the second indication information indicates that the destination BAP address of the first data packet is allocated by the first host node. From the perspective of the host node, when forwarding the downlink data packet through the BAP topology controlled by the other node, the first host node and the second host node indicate (for example, through the second indication information) which host node the BAP address of the downlink data packet is allocated by. Therefore, after the boundary node (for example, the first IAB node) receives the downlink data packet, it can directly determine whether rewriting and other operations are required.

In some embodiments, step 802 may be replaced with: the first IAB node processes the first data packet according to the third indication information in the first data packet; the third instruction information indicates that the destination BAP address of the first packet is to be overwritten, or the third instruction information indicates that the destination BAP address of the first packet is not to be overwritten. It is understood that the third indication information indicates that the destination BAP address of the first packet is overwritten is the third indication information indicates that the destination BAP address of the first packet is a dummy BAP address. The third indication information indicates that the destination BAP address of the first packet is not overwritten may be understood that the third indication information indicates that the destination BAP address of the first packet is a real BAP address (non-dummy BAP address). The third indication information may occupy one or more bits in the header of the first data packet. For example, the third indication information may be indication information (occupying one or more bits) additionally added to the existing BAP address. For example, the third indication information is two additional bits added to the existing BAP address; if the third indication information is 00, the third indication information indicates that the destination BAP address of the first data packet is not rewritten; if the third indication information is 11, the third indication information indicates that the destination BAP address of the first packet is rewritten.

The first IAB node may determine, for a received downstream packet (e.g., the first packet), whether to rewrite the BAP routing ID of the downstream packet. It should be appreciated that the first IAB node can only ensure that the first packet is routed to the correct path when it can accurately determine whether the BAP routing ID of the first packet is received rewriting.

In this embodiment of the present application, the first IAB node can accurately determine whether to rewrite the received BAP routing ID of the first data packet according to the BAP topology corresponding to the ingress link receiving the first data packet and the BAP topology to which the first IAB node belongs, and further route the first data packet to a correct path.

Some possible examples of step 802 are described below.

Example 1

Under the condition that the BAP topology corresponding to the entry link of the first IAB node for receiving the first data packet is not the first BAP topology and does not meet a first condition, the first IAB node forwards the first data packet according to the second BAP route identifier and the route table; the first condition includes: the first BAP address matches the second BAP address; the second BAP routing identifier is obtained by rewriting a first BAP routing identifier of the first packet, where the first BAP routing identifier includes a destination BAP address and a path identifier of the first packet;

the first BAP address is obtained by rewriting a destination BAP address of the first packet, and the second BAP address is a BAP address allocated by the first host node to the first IAB node;

alternatively, the first BAP address is a destination BAP address of the first packet, and the second BAP address is a BAP address allocated by the second donor node to the first IAB node.

The first BAP address and the second BAP address may be matched, and the first BAP address and the second BAP address may be the same, or a specific mapping relationship may be satisfied between the first BAP address and the second BAP address, which is not limited in this application. In this application, two addresses (e.g., two BAP addresses) matching may mean that the two addresses are the same, or that a specific mapping relationship is satisfied between the two addresses, and this application is not limited thereto.

In some embodiments, the first IAB node may rewrite (rewriting) the destination BAP address of the first data packet to obtain the first BAP address. Wherein the first BAP address is a BAP address recognizable by the IAB node in the second BAP topology. In example one, before the first IAB node forwards the first packet according to the second BAP route identifier and the routing table, the first IAB node may perform the following operations: and the first IAB node rewrites the first BAP route identification of the first data packet into a second BAP route identification. For example, the first IAB node searches for a second BAP routing identifier corresponding to the first BAP routing identifier of the first packet in a rewriting table (rewriting table), where a BAP address included in the second BAP routing identifier is the first BAP address. The first IAB node may forward the first packet according to the second BAP route identifier and the route table by: and the first IAB node forwards the first data packet according to the next hop BAP address matched with the second BAP routing identification in the routing table. And if the routing table does not contain the next hop BAP address matched with the second BAP routing identification, discarding the first data packet.

The first condition may be understood as a condition that the first IAB node determines whether to forward the first data packet when the BAP topology corresponding to the ingress link, where the first IAB node receives the first data packet, is not the first BAP topology. If the first condition is met, the first IAB node delivers the first data packet to an upper layer of a BAP layer of the first IAB node; if the first condition is not met, the first IAB node forwards the first data packet. Whether the BAP topology corresponding to the ingress link of the first IAB node receiving the first data packet is the first BAP topology may be understood as a condition of whether to rewrite the BAP route identifier of the first data packet. If the BAP topology corresponding to the entry link of the first IAB node for receiving the first data packet is the first BAP topology, the first IAB node does not need to rewrite the BAP routing identifier of the first data packet; if the BAP topology corresponding to the entry link of the first IAB node receiving the first data packet is not the first BAP topology, the first IAB node may rewrite the BAP route identifier of the first data packet, and forward the first data packet by using the rewritten BAP route identifier.

In a possible implementation manner, the first condition further includes: the first indication information included in the first packet indicates that the first packet is to be delivered to an upper layer of a BAP layer of the first IAB node. In some embodiments, the first indication information may be included in a path identifier included in the first packet. The first indication information may be indication information (occupying one or more bits) additionally added to the existing path identity. For example, the first indication information is two additional bits added to the existing path identifier; if the first indication information is 00, the first indication information indicates not to submit to the upper layer; if the first indication information is 11, the first indication information indicates to deliver the upper layer (i.e. deliver the first data packet to the upper layer). In this implementation, an erroneous delivery of the first data packet to an upper layer of the BAP layer of the first IAB node can be avoided.

In this application, the BAP topology corresponding to the ingress link where the first IAB node receives the first data packet is not the first BAP topology, and may be replaced with: the second indication information in the first packet indicates that the destination BAP address of the first packet is assigned by the second host node, or the third indication information in the first packet indicates that the destination BAP address of the first packet is rewritten.

In example one, when a BAP topology corresponding to an ingress link, where the first IAB node receives the first data packet, is not the first BAP topology and does not satisfy a first condition, the first IAB node forwards the first data packet according to the second BAP route identifier and the route table; the first packet can be routed to the correct path.

Example two

When the BAP topology corresponding to the entry link of the first IAB node receiving the first data packet is not the first BAP topology and meets a first condition, the first IAB node submits the first data packet to an upper layer of a BAP layer of the first IAB node; the first condition includes: the first BAP address matches the second BAP address;

alternatively, the first BAP address is a destination BAP address of the first packet, and the second BAP address is a BAP address allocated by the second host node to the first IAB node.

If the first BAP address is obtained by rewriting the destination BAP address of the first data packet, the first BAP address is a BAP address which can be identified by the first IAB node (corresponding to the BAP address distributed by the first host node for the first IAB node). By judging whether the first BAP address is matched with the BAP address allocated to the first IAB by the first host node, whether the first data packet needs to be submitted to the upper layer of the BAP layer of the first IAB can be accurately judged.

When the BAP topology corresponding to the entry link of the first IAB node for receiving the first data packet is not the first BAP topology, the BAP address of the first data packet is allocated by the second host node. Therefore, the first IAB node can accurately judge whether the first data packet needs to be delivered to the upper layer of the BAP layer of the first IAB node by judging whether the destination BAP address of the first data packet is matched with the BAP address allocated to the first IAB node by the second host node.

In example two, when the BAP topology corresponding to the ingress link, where the first IAB node receives the first data packet, is not the first BAP topology and meets the first condition, the first IAB node submits the first data packet to an upper layer of a BAP layer of the first IAB node; the first packet can be routed to the correct path.

Example three

Under the condition that the BAP topology corresponding to the entry link of the first IAB node receiving the first data packet is the first BAP topology and the third BAP address is not matched with the fourth BAP address, the first IAB node forwards the first data packet according to the routing table; the third BAP address is a destination BAP address of the first packet, and the fourth BAP address is a BAP address allocated by the first host node to the first IAB node.

When the BAP topology corresponding to the entry link of the first IAB node receiving the first data packet is the first BAP topology, the BAP address of the first data packet is allocated by the first host node. The first IAB node can accurately judge whether the first data packet needs to be delivered to the upper layer of the BAP layer of the first IAB node by judging whether the third BAP address matches with the fourth BAP address.

In this application, the BAP topology corresponding to the ingress link through which the first IAB node receives the first data packet is the first BAP topology, and may be replaced with: the second indication information in the first packet indicates that the destination BAP address of the first packet is allocated by the first host node, or the third indication information in the first packet indicates that the destination BAP address of the first packet is not overwritten.

Example four

When the BAP topology corresponding to the ingress link through which the first IAB node receives the first packet is the first BAP topology and the third BAP address matches the fourth BAP address, the first IAB node submits the first packet to an upper layer of a BAP layer of the first IAB node; the third BAP address is a destination BAP address of the first packet, and the fourth BAP address is a BAP address allocated by the first host node to the first IAB node.

Some possible examples of step 802 are described above, and some possible implementations of the method flow in fig. 8 are described below with reference to the drawings. Fig. 9 is a flowchart of another routing method according to an embodiment of the present application. The method flow in fig. 9 is one possible implementation of the method flow in fig. 8. As shown in fig. 9, the method includes:

901. the first IAB node receives the first data packet.

902. The first IAB node determines whether the first packet is from the second BAP topology.

If yes, go to step 903; if not, go to step 904. If the first data packet is from the IAB node belonging to the second BAP topology, the first IAB node judges that the first data packet is from the second BAP topology; if the first data packet is not from the IAB node belonging to the second BAP topology, the first IAB node judges that the first data packet is not from the second BAP topology.

Step 902 may be replaced with: the first IAB node determines whether the first packet is from the first BAP topology. If yes, go to step 904; if not, go to step 903.

Step 902 may be replaced with: it is determined whether the first packet is from a Secondary Cell Group (SCG). If yes, go to step 903; if not, go to step 904. Alternatively, step 902 may be replaced with: it is determined whether the first packet is from a Master Cell Group (MCG). If yes, go to step 904; if not, go to step 903. Wherein the first IAB node belongs to the MCG.

Step 902 may be replaced with: it is determined whether the first packet is from the SCG. If yes, go to step 904; if not, go to step 903. Alternatively, step 902 may be replaced with: it is determined whether the first packet is from the MCG. If yes, go to step 903; if not, go to step 904. Wherein the first IAB node belongs to the SCG.

In some embodiments, step 902 may be replaced with: and judging whether the topology ID corresponding to the entry link receiving the first data packet indicates the second BAP topology or not. If yes, go to step 903; if not, go to step 904. In some embodiments, the first host node may configure the first IAB node in advance with a mapping relationship of the link ID of the ingress link and the topology ID. Specifically, the first host node may carry the mapping relationship by sending an RRC message to the MT side of the first IAB node, using a new cell CellGroupConfig in the message. Alternatively, the first host node may also send an F1AP message to the DU side of the first IAB node, where the F1AP message may carry the mapping relationship. The topology ID may be represented by 0-1, e.g. specifying ID =0 as the first BAP topology and others as the second BAP topology.

In some embodiments, step 902 may be replaced with: and judging whether the BAP routing ID in the packet header of the first data packet is matched with a routing table of the first BAP topology. If yes, go to step 904; if not, go to step 903.

In some embodiments, step 902 may be replaced with: and judging whether the BAP address in the packet header of the first data packet belongs to the first BAP address set. If yes, go to step 903; if not, go to step 904. In some embodiments, the second home node may configure the first IAB node with the first set of BAP addresses in advance by the first home node, e.g., the first set of BAP addresses may be or must include a set of dummy BAP addresses assigned by the second home node to the first IAB node and its descendants. All BAP addresses in the first set of BAP addresses may be configured in advance in the original BAP routing identification field of the rewrite table in step 903.

In some embodiments, step 902 may be replaced with: and judging whether the BAP path ID in the packet header of the first data packet belongs to the first BAP path ID set or not. If yes, go to step 903; if not, go to step 904. In some embodiments, the second hosting node may configure the first node with the first set of BAP path IDs in advance through the first hosting node, e.g., the first set of BAP path IDs may be or must include a set of special path IDs assigned by the second hosting node to indicate to the first IAB node and its descendants. All BAP path IDs in the first set of BAP path IDs may be configured in advance in the column of the original BAP route identification of the rewrite table in step 903.

In some embodiments, the first IAB node determines whether the first packet is from the second BAP topology replaced with: the first IAB node judges whether the BAP topology corresponding to the entry link for receiving the first data packet is a second BAP topology. If yes, go to step 903; if not, go to step 904. In some embodiments, the ingress link, to which the first IAB node receives the downlink data packet, may include a first ingress link and a second ingress link, where a BAP topology corresponding to the first ingress link is a first BAP topology, and a BAP topology corresponding to the second ingress link is a second BAP topology. It should be understood that, if the first IAB node receives the first data packet through the first ingress link, the BAP topology corresponding to the ingress link through which the first IAB node receives the first data packet is the first BAP topology; if the first IAB node receives the first data packet through the second ingress link, the BAP topology corresponding to the ingress link through which the first IAB node receives the first data packet is the second BAP topology.

903. The first IAB node rewrites the first BAP route identity of the first data packet to a second BAP route identity.

The first BAP routing identity may be understood as an original BAP routing identity of the first packet or a current BAP routing identity (BAP routing ID) of the first packet. The first BAP routing identity may comprise a destination BAP address and a path identity (path ID) of the first packet.

One possible implementation of step 903 is as follows: checking whether the first BAP routing identification of the first data packet is matched with a rewriting table (rewriting table), namely judging whether the first BAP routing identification can be rewritten; and if so, rewriting the first BAP route identifier into a second BAP route identifier based on the rewriting table. And if the first BAP routing identification does not match the rewriting table, delivering the first data packet to an upper layer of the BAP node of the first IAB node. The rewriting table may include one or more groups of BAP routing identifier mapping relationships, where each group of BAP routing identifier mapping relationships is used to map a type of BAP routing identifier that is not recognizable by the first IAB node (i.e., a BAP routing identifier that is recognizable by an IAB node in the second BAP topology) to a BAP routing identifier that is recognizable by the first IAB node. Checking whether the first BAP routing identity of the first packet matches the rewriting table may be: and inquiring whether the rewriting table contains the mapping relation between the first BAP routing identification and other BAP routing identifications. Rewriting the first BAP routing identifier into the second BAP routing identifier based on the rewriting table may be: and acquiring a second BAP routing identifier which has a BAP routing identifier mapping relation with the first BAP routing identifier based on the rewriting table.

Table 1 is an example of a rewriting table provided in the present application. Referring to table 1, the first column is the original BAP routing id, and the second column is the rewritten BAP routing id. It should be appreciated that each original BAP route identification in the first column is a BAP route identification recognizable by IAB nodes within the second BAP topology. Alternatively, each original BAP routing id in the first column corresponds to a BAP routing id from a downstream packet (e.g., the first packet) belonging to the second BAP topology. The rewritten BAP route identification in the second column is a BAP route identification recognizable by the first IAB node. In table 1, the original BAP routing identity of each row corresponds to the rewritten BAP routing identity in the row. For example, a first BAP routing identity in a first row corresponds to a second BAP routing identity in the first row. For example, the first BAP routing identity may look up whether the first column of table 1 contains the first BAP routing identity; if yes, the first BAP route identification is matched with the rewriting table; if not, the first BAP route identification does not match the rewriting table. In this example, if the first column in table 1 includes the first BAP routing identifier, the second BAP routing identifier having a mapping relationship with the first BAP routing identifier is obtained.

TABLE 1

Original BAP route identification	Rewritten BAP route identification
		First BAP route identification	Second BAP routing identifier
Third BAP routing identifier	Fourth BAP routing identifier
		…	…
(N) BAP routing identification	(N + 1) th BAP route identification

One possible implementation of step 903 is as follows: and the first IAB node directly rewrites the first BAP routing identifier based on the rewriting table to obtain a second BAP routing identifier. In the implementation mode, the first BAP routing identification can be quickly rewritten into the second BAP routing identification, and the operation is less.

904. And judging whether the BAP address of the first data packet is matched with the BAP address distributed by the first host node for the first IAB node.

If yes, go to step 905; if not, go to step 906. The first IAB node may store a BAP address assigned by the first host node for the first IAB node. Determining whether the BAP address of the first data packet matches the BAP address allocated by the first host node to the first IAB node may be: and judging whether the BAP address of the first data packet is the same as the BAP address allocated by the first host node for the first IAB node.

In the case where the first packet is not from the second BAP topology, step 904 may be: and judging whether the destination BAP address of the first data packet is matched with the BAP address distributed by the first host node for the first IAB node.

In the case where the first data packet is from a second BAP topology, step 904 may be: judging whether the rewritten BAP address of the first data packet matches the BAP address distributed by the first host node for the first IAB node; the rewritten BAP address is a BAP address included in the second BAP routing identifier.

905. The first IAB node submits the first data packet to an upper layer of a BAP layer of the first IAB node.

906. The first IAB node forwards the first packet according to the routing table.

In the case where the first packet is not from the second BAP topology, step 906 may be: and the first IAB node forwards the first data packet according to the next hop BAP address matched with the first BAP routing identification in the routing table. And if the next hop BAP address (entry) matched with the first BAP routing identification cannot be found in the routing table, judging that the first data packet is an error packet, and discarding the first data packet.

In the case where the first data packet is from a second BAP topology, step 906 may be: and the first IAB node forwards the first data packet according to the next hop BAP address matched with the second BAP routing identification in the routing table. And if the next hop BAP address (entry) matched with the second BAP routing identifier cannot be found in the routing table, judging that the first data packet is an error packet, and discarding the first data packet.

In some embodiments, the BAP layer of the first IAB node may route the first data packet according to its BAP address; the BAP routing ID of the first packet may also be re-written and then routed. Based on these two schemes, priorities of these two schemes can be set, and one possible example is as follows: if the first IAB node configures a rewriting table, the BAP layer of the first IAB node considers that the priority of the latter scheme is higher than that of the former scheme; otherwise, rerouting is based only on the BAP address.

In the embodiment of the application, whether the BAP routing identifier of the first data packet is rewritten or not is determined by judging whether the first data packet is from the second BAP topology or not, so that the data packet from the second BAP topology is forwarded out through the routing table. Whether the first data packet is forwarded or delivered to an upper layer of the BAP layer is determined by judging whether the BAP address of the first data packet is matched with the BAP address allocated to the first IAB by the first host node or not, the first data packet can be routed to a correct transmission path, and stable transmission of data of the IAB and the UE is guaranteed.

Fig. 10 is a flowchart of another routing method according to an embodiment of the present application. The method flow in fig. 10 is one possible implementation of the method flow in fig. 8. As shown in fig. 10, the method includes:

1001. the first IAB node receives the first data packet.

1002. The first IAB node determines whether the first data packet is from the second BAP topology.

If yes, go to step 1003; if not, go to step 1004. An implementation of step 1002 may be found in step 902.

1003. And judging whether the destination BAP address of the first data packet is matched with the BAP address distributed by the second host node for the first IAB node.

Step 1003 may be: and judging whether the destination BAP address of the first data packet is the same as the BAP address distributed by the second host node for the first IAB node or not. If yes, go to step 1004; if not, go to step 1005.

In some embodiments, step 1003 may be replaced with: and judging whether the destination BAP address of the first data packet belongs to the second BAP address set. If yes, go to step 1005; if not, go to step 1004. In some embodiments, the second host node may pre-configure the first IAB node with the second set of BAP addresses via the first host node. Alternatively, the second set of BAP addresses may be a set of dummy BAP addresses assigned by the second home node to descendant nodes of the first IAB node, but not including the address assigned to the first IAB node. Optionally, all BAP addresses in the second set of BAP addresses may be configured in advance in the column of the original BAP routing identity of the rewrite table in step 1005.

In some embodiments, step 1003 may be replaced with: and judging whether the destination BAP path ID of the first data packet belongs to the second BAP path ID set. If yes, go to step 1005; if not, go to step 1004. In some embodiments, the second donor node may pre-configure the first IAB node with the second set of BAP path IDs through the first donor node. Alternatively, the second BAP path ID set may be a set of special path IDs assigned by the second donor node to indicate descendant nodes to the first IAB node, but not including a path ID to indicate to the first IAB node. Alternatively, all BAP path IDs in the second set of BAP path IDs may be configured in advance in the column of the original BAP route identification of the rewrite table in step 1005.

1004. The first IAB node delivers the first data packet to an upper layer of the BAP layer of the first IAB node.

1005. The first IAB node rewrites the first BAP route identity of the first packet to a second BAP route identity.

See step 903 in FIG. 9 for an implementation of step 1005.

1006. And judging whether the destination BAP address of the first data packet is matched with the BAP address distributed by the first host node for the first IAB node.

Step 1006 may be: and judging whether the destination BAP address of the first data packet is the same as the BAP address distributed by the first host node for the first IAB node or not. If yes, go to step 1007; if not, go to step 1008.

1007. The first IAB node delivers the first data packet to an upper layer of the BAP layer of the first IAB node.

1008. The first IAB node forwards the first packet according to the routing table.

The implementation of step 1008 refers to step 906 in fig. 9.

In the embodiment of the application, whether the BAP routing identifier of the first data packet is rewritten or not is determined by judging whether the first data packet is from the second BAP topology or not, so that the data packet from the second BAP topology is forwarded out through the routing table. When the first data packet comes from the second BAP topology, whether the first data packet is forwarded or delivered to an upper layer of a BAP layer is determined by judging whether a target BAP address of the first data packet matches a BAP address allocated to the first IAB node by the second host node; when the first data packet does not come from the second BAP topology, whether the first data packet is forwarded or delivered to an upper layer of a BAP layer is determined by judging whether a destination BAP address of the first data packet is matched with a BAP address allocated to the first IAB node by the first host node or not; the first data packet can be routed to a correct transmission path, and stable transmission of data of the IAB node and the UE is guaranteed.

Fig. 11 is a flowchart of another routing method according to an embodiment of the present application. The method flow in fig. 11 is one possible implementation of the method flow in fig. 8. As shown in fig. 11, the method includes:

1101. the first IAB node receives the first data packet.

1102. The first IAB node determines whether the first packet is from the second BAP topology.

If yes, go to step 1103; if not, go to step 1104. The implementation of step 1102 may refer to step 902 or may replace the step of step 902.

1103. And judging whether the destination BAP address of the first data packet matches the BAP address distributed by the second host node for the first IAB node or not and the first indication information indicates to be delivered to an upper layer.

Step 1103 may be: and judging whether the destination BAP address of the first data packet is the same as the BAP address distributed by the second host node for the first IAB node or not and the first indication information indicates to submit to an upper layer. If the destination BAP address of the first packet is the same as the BAP address allocated by the second host node for the first IAB node and the first indication information indicates to submit to the upper layer, go to step 1104; otherwise, step 1105 is performed. The first indication information is included in the first data packet. The first indication information may indicate that the first packet is delivered to an upper layer of a BAP layer of the first IAB node or that the first packet is not delivered to an upper layer of a BAP layer of the first IAB node. In some embodiments, the first indication information may be included in a path identifier included in the first packet. The first indication information may be indication information (occupying one or more bits) additionally added on the existing path identity. For example, the first indication information is two additional bits added to the existing path identifier; if the first indication information is 00, the first indication information indicates that the upper layer is not submitted; if the first indication information is 11, the first indication information indicates to deliver the upper layer (i.e. to deliver the first data packet to the upper layer). In some embodiments, the first indication information may indicate whether to deliver to an upper layer with one or more special PathID (10 bits in size) values. For example, path ID =31 is handed to the upper layer, and otherwise, the upper layer is not handed. In this application, the upper layer of the BAP layer of the IAB node may refer to an IP layer on the DU side. After receiving the data packet, the BAP layer at MT side of IAB node determines that the data packet is for itself, and then the data packet is handed to the IP layer at DU side of itself.

1104. The first IAB node delivers the first data packet to an upper layer of the BAP layer of the first IAB node.

1105. The first IAB node rewrites the first BAP route identity of the first packet to a second BAP route identity.

See step 903 in FIG. 9 for an implementation of step 1105.

1106. And judging whether the destination BAP address of the first data packet is matched with the BAP address distributed by the first host node for the first IAB node.

Step 1106 may be: and judging whether the destination BAP address of the first data packet is the same as the BAP address distributed by the first host node for the first IAB node or not. If yes, go to step 1107; if not, go to step 1108.

1107. The first IAB node delivers the first data packet to an upper layer of the BAP layer of the first IAB node.

1108. The first IAB node forwards the first packet according to the routing table.

See step 906 in FIG. 9 for an implementation of step 1108.

In the embodiment of the application, whether the BAP routing identifier of the first data packet is rewritten or not is determined by judging whether the first data packet is from the second BAP topology or not, so that the data packet from the second BAP topology is forwarded out through the routing table. When the first data packet comes from the second BAP topology, whether the first data packet is forwarded or delivered to an upper layer of the BAP layer is determined by judging whether a target BAP address of the first data packet matches a BAP address allocated to the first IAB node by the second host node and whether the first indication information indicates that the first data packet is delivered to the upper layer; when the first data packet does not come from the second BAP topology, whether the first data packet is forwarded or delivered to an upper layer of a BAP layer is determined by judging whether a destination BAP address of the first data packet matches a BAP address allocated by the first host node for the first IAB node; and the first data packet is routed to a correct transmission path, so that stable transmission of data of the IAB node and the UE is ensured.

The foregoing describes a scheme for routing downstream packets to the correct transmission path. The following describes a scheme for routing an upstream packet to a correct transmission path with reference to the drawings. Fig. 12 is a flowchart of another routing method according to an embodiment of the present application. The method of fig. 12 is applicable to an IAB network that includes a first BAP topology managed by a first host node and a second BAP topology managed by a second host node, the first host node being different from the second host node. Any boundary node in the IAB network can forward the uplink data packet by using the method flow in fig. 12. In some embodiments, the border node in the IAB network may perform the routing methods in fig. 8 to 11 to forward the downstream packet, and may also perform the routing method in fig. 12 to forward the upstream packet. As shown in fig. 12, the method includes:

1201. the first IAB node receives a second packet from a child node of the first IAB node.

The first IAB node is managed by the first host node, at least one parent node of the first IAB node is managed by the second host node, and the first IAB node belongs to the first BAP topology. The first IAB node is a border node in the IAB network.

1202. And the first IAB node forwards the second data packet according to the fourth BAP route identifier and the route table under the condition of obtaining the fourth BAP route identifier which has a mapping relation with the third BAP route identifier of the second data packet.

In some embodiments, the first IAB node obtains the fourth BAP route identity having a mapping relationship with the third BAP route identity of the second data packet by looking up the rewrite table. For example, the first IAB node searches for a BAP routing identifier in the rewrite table, which has a mapping relationship with the third BAP routing identifier, to obtain a fourth BAP routing identifier. According to the fourth BAP routing identifier and the routing table, forwarding the second packet may be: and the first IAB node forwards the second data packet according to the next hop BAP address matched with the fourth BAP routing identification in the routing table.

Step 1202 may be replaced with: and under the condition that the first IAB node does not obtain the BAP route identifier which has a mapping relation with the third BAP route identifier of the second data packet, forwarding the second data packet according to the third BAP route identifier and the route table. In some embodiments, the first IAB node obtains a BAP route identifier having a mapping relationship with a third BAP route identifier of the second packet by looking up the rewrite table; and if the rewriting table does not contain the BAP routing identifier which has the mapping relation with the third BAP routing identifier, forwarding the second data packet according to the third BAP routing identifier and the routing table. According to the third BAP routing identifier and the routing table, forwarding the second packet may be: and the first IAB node forwards the second data packet according to the next hop BAP address matched with the third BAP routing identification in the routing table.

In the embodiment of the application, under the condition that a fourth BAP routing identifier which has a mapping relation with a third BAP routing identifier of a second data packet is obtained, the second data packet is forwarded according to the fourth BAP routing identifier and a routing table; the second data packet can be routed to the correct transmission path.

Fig. 13 is a flowchart of another routing method according to an embodiment of the present application. The method flow in fig. 13 is one possible implementation of the method flow in fig. 12. As shown in fig. 13, the method includes:

1301. the first IAB node receives a second packet from a child node of the first IAB node.

1302. And judging whether the third BAP routing identification of the second data packet is matched with the rewriting table.

Judging whether the third BAP routing identifier of the second packet matches the rewrite table may be: and judging whether the rewriting table contains a BAP routing identifier which has a mapping relation with a third BAP routing identifier of the second data packet. If yes, go to step 1303; if not, go to step 1304. The first BAP routing identity contains a destination BAP address and a path identity of the second packet.

In some embodiments, step 1302 may be replaced with: and judging whether the third BAP routing identification of the second data packet is matched with the routing table of the first BAP topology. If yes, go to step 1304; if not, go to step 1303.

In some embodiments, step 1302 may be replaced with: it is determined whether the third BAP address of the second packet belongs to a third BAP address set. If yes, go to step 1303; if not, go to step 1304. In some embodiments, the first host node may configure the first IAB node with the third set of BAP addresses in advance. Optionally, the third set of BAP addresses may or must include a BAP address assigned by the first host node to the first IAB node or a pseudo BAP address assigned by the first host node to the second host node. Optionally, all BAP addresses in the third set of BAP addresses may be configured in advance in the column of the original BAP routing identity of the rewrite table in step 1303.

In some embodiments, step 1302 may be replaced with: and judging whether the third BAP path ID of the second data packet belongs to the third BAP path ID set. If yes, go to step 1303; if not, go to step 1304. In some embodiments, the first host node may configure the first IAB node with the third set of BAP path IDs in advance. Optionally, the third set of BAP path IDs may be or must include the BAP path ID assigned by the first host node to indicate to the second host node. Alternatively, all path IDs in the third BAP path ID set may be configured in advance in the column of the original BAP routing identity of the rewrite table in step 1303.

1303. The first IAB node rewrites the third BAP route identity of the second packet to a fourth BAP route identity.

Please refer to step 903 for an implementation manner of step 1303.

1304. The first IAB node forwards the second packet according to the routing table.

In the case that the third BAP route identity matches the rewrite table, step 1304 may be: and the first IAB node forwards the second data packet according to the next hop BAP address matched with the fourth BAP routing identification in the routing table. And if the next hop BAP address (entry) matched with the fourth BAP routing identification cannot be found in the routing table, judging that the second data packet is an error packet, and discarding the second data packet.

In the case that the third BAP route identification does not match the rewrite table, step 1304 may be: and the first IAB node forwards the second data packet according to the next hop BAP address matched with the third BAP routing identification in the routing table. And if the next hop BAP address (entry) matched with the third BAP routing identification cannot be found in the routing table, judging that the second data packet is an error packet, and discarding the second data packet.

In the embodiment of the application, whether the BAP routing identifier of the second data packet is rewritten is determined by judging whether the third BAP routing identifier of the second data packet is matched with the rewriting table, so that the second data packet is forwarded according to the BAP routing identifier of the second data packet; the second data packet can be routed to the correct transmission path.

Fig. 14 shows a schematic structure of a communication apparatus 1400. The communication apparatus 1400 may correspondingly implement the functions or steps implemented by the IAB node (e.g., the first IAB node) in the above-described method embodiments. The communication apparatus may include a processing module 1410 and a transceiver module 1420. Optionally, a storage unit may also be included, which may be used to store instructions (code or programs) and/or data. The processing module 1410 and the transceiver module 1420 may be coupled with the storage unit, for example, the processing module 1410 may read instructions (code or program) and/or data in the storage unit to implement the corresponding method. The above units may be independently arranged, or may be partially or wholly integrated. For example, the transceiving module 1420 may include a transmitting module and a receiving module.

In some possible embodiments, the communication apparatus 1400 can implement the behavior and function of the first IAB node in the above method embodiments. For example, the communication device 1400 may be the first IAB node and may also be a component (e.g., a chip or a circuit) applied in the first IAB node. The transceiver module 1420 may be configured to perform all receiving or transmitting operations performed by the first IAB node in the embodiments of fig. 8, 9, 10, 11, 12, or 13, such as step 901 in the embodiment shown in fig. 8 and step 901 and step 906 in the embodiment shown in fig. 9, and/or other processes for supporting the techniques described herein. The processing module 1410 is configured to perform all operations performed by the first IAB node in the embodiments shown in fig. 8, 9, 10, 11, 12, or 13 except transceiving operations. For example, transceiver module 1420 may be used to perform step 802 in the embodiment shown in fig. 8, and/or other processes for supporting the techniques described herein. For another example, the transceiver module 1420 may be configured to perform the

steps

902, 903, 904, and 905 in the embodiment shown in fig. 9. Also for example, transceiver module 1420 may be configured to perform steps 1002 through 1007 in the embodiment shown in fig. 10. Also for example, transceiver module 1420 may be used to perform steps 1102-1107 in the embodiment shown in fig. 11. For another example, the transceiver module 1420 may be used to perform

steps

1201 and 1202 in the embodiment shown in fig. 12. For another example, the transceiver module 1420 may be used to perform

steps

1301 and 1304 in the embodiment shown in fig. 13. Reference may be made to method embodiments for the related detailed description.

In some possible implementations, the communication apparatus 1400 can correspondingly implement the behavior and functions of the first host node in the above method embodiments. For example, communication apparatus 1400 may be a first host node, and may also be a component (e.g., a chip or a circuit) applied in the first host node. Transceiving module 1420 may be configured to perform all receiving or transmitting operations performed by the first host node in the foregoing embodiments, and processing module 1410 may be configured to perform all operations except transceiving operations performed by the first host node in the foregoing embodiments. Reference may be made to method embodiments for the related detailed description.

Fig. 15 is a schematic structural diagram of a communication device 1500 according to an embodiment of the present disclosure. The communication apparatus 1500 may be a first IAB node, and may implement the function of the first IAB node in the method provided in this embodiment of the present application. Alternatively, the communication apparatus 1500 may also be an apparatus capable of supporting the first IAB node to implement the corresponding functions in the method provided in the embodiment of the present application. The communication device 1500 may be a system on a chip. In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices.

In a hardware implementation, the transceiver module 1420 may be a transceiver, and the transceiver is integrated in the communication apparatus 1500 to form the communication interface 1510.

The communications apparatus 1500 includes at least one processor 1520 configured to implement or support the communications apparatus 1500 to implement the functionality of the first IAB node in the methods provided by embodiments of the present application. For details, reference is made to the detailed description in the method example, which is not repeated herein.

The communications apparatus 1500 can also include at least one memory 1530 for storing program instructions and/or data. The memory 1530 and the processor 1520 are coupled. The coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, and may be an electrical, mechanical or other form for information interaction between the devices, units or modules. The processor 1520 may operate in conjunction with the memory 1530. The processor 1520 may execute program instructions and/or data stored in the memory 1530 to cause the communication device 1500 to implement the corresponding methods. At least one of the at least one memory may be included in the processor.

The communications apparatus 1500 can also include a communication interface 1510 for communicating with other devices over a transmission medium so that the apparatus used in the communications apparatus 1500 can communicate with other devices. Illustratively, when the communication device is a first IAB node, the other apparatus is another IAB node. Processor 1520 can send and receive data using communication interface 1510. The communication interface 1510 may specifically be a transceiver.

The specific connection medium between the communication interface 1510, the processor 1520 and the memory 1530 is not limited in this embodiment. In the embodiment of the present application, the memory 1530, the processor 1520 and the communication interface 1510 are connected by the bus 1540 in fig. 15, the bus is represented by a thick line in fig. 15, and the connection manner between other components is only schematically illustrated and is not limited thereto. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 15, but this is not intended to represent only one bus or type of bus.

In an embodiment of the present application, the processor 1520 may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware component, or the like that may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in a processor.

In this embodiment, the memory 1530 may be a non-volatile memory, such as a hard disk (HDD) or a solid-state drive (SSD), and may also be a volatile memory (RAM), for example. The memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory in the embodiments of the present application may also be circuitry or any other device capable of performing a storage function for storing program instructions and/or data.

It should be appreciated that fig. 16 illustrates another form of the communications apparatus 1500 when the communications apparatus 1500 is a first IAB node. In fig. 16, the communication device 1500 is a first IAB node, and it is to be understood that the first IAB node includes a CU and a DU, and the CU may include a communication interface, a processor, and a memory, and a bus connecting the communication interface, the processor, and the memory, wherein the communication interface may be used to communicate with the CU of the IAB host node or the DU of the IAB node. The DU may also include a communication interface for communicating with the MT of the IAB node, a processor, and a memory, and a bus connecting the communication interface, the processor, and the memory.

Fig. 17 is a schematic structural diagram of another communication device 170 according to an embodiment of the present disclosure. As shown in fig. 17, the communication apparatus shown in fig. 17 includes a logic circuit 1701 and an interface 1702. The processing module of fig. 14 may be implemented with the logic circuit 1701, and the transceiver module of fig. 14 may be implemented with the interface 1702. The logic circuit 1701 may be a chip, a processing circuit, an integrated circuit, or a system on chip (SoC) chip, and the interface 1702 may be a communication interface, an input/output interface, or the like. In the embodiments of the present application, the logic circuit and the interface may also be coupled to each other. The embodiments of the present application are not limited to the specific connection manner of the logic circuit and the interface.

In some embodiments of the present application, the logic and interfaces may be configured to perform the functions or operations performed by the first IAB node, etc., as described above.

The embodiment of the present application further provides a communication system, and in particular, the communication system includes a first host node, a second host node, a first IAB node, one or more IAB nodes controlled by the first host node, and one or more IAB nodes controlled by the second host node.

Embodiments of the present application also provide a computer-readable storage medium, which includes instructions that, when executed on a computer, cause the computer to perform the method of the above-described embodiments.

Also provided in embodiments of the present application is a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the above-described embodiments.

The embodiment of the present application provides a chip system, where the chip system includes a processor and may further include a memory, and is configured to implement the function of the first IAB node in the foregoing method. The chip system may be formed by a chip, and may also include a chip and other discrete devices.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

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

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific implementation of the present application, but the scope of the embodiments of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the embodiments of the present application, and all the changes or substitutions should be covered by the scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be subject to the protection scope of the claims.

Claims

1. A routing method is applied to an access backhaul integrated IAB network, the IAB network comprises a first Backhaul Adaptation Protocol (BAP) topology and a second BAP topology, the first BAP topology is managed by a first host node, the second BAP topology is managed by a second host node, and the first host node is different from the second host node; the method comprises the following steps:

the first IAB node receives the first data packet; the first IAB node is managed by the first hosting node, at least one parent node of the first IAB node is managed by the second hosting node, and the first IAB node belongs to the first BAP topology;

and the first IAB node processes the first data packet according to the BAP topology corresponding to the entry link for receiving the first data packet and the BAP topology of the first IAB node.

2. The routing method according to claim 1, wherein the processing the first data packet by the first IAB node according to the BAP topology corresponding to the ingress link receiving the first data packet and the BAP topology to which the first IAB node belongs comprises:

under the condition that the BAP topology corresponding to the entry link of the first IAB node for receiving the first data packet is not the first BAP topology and does not meet a first condition, the first IAB node forwards the first data packet according to a second BAP route identifier and a route table; the first condition includes: the first BAP address matches the second BAP address; the second BAP routing identifier is obtained by rewriting a first BAP routing identifier of the first data packet, and the first BAP routing identifier comprises a destination BAP address and a path identifier of the first data packet;

the first BAP address is obtained by rewriting a destination BAP address of the first data packet, and the second BAP address is a BAP address distributed by the first host node for the first IAB node;

or, the first BAP address is a destination BAP address of the first packet, and the second BAP address is a BAP address allocated by the second donor node to the first IAB node.

3. The routing method according to claim 2, wherein the first condition further comprises: the first indication information included in the first packet indicates that the first packet is to be delivered to an upper layer of a BAP layer of the first IAB node.

4. The routing method according to claim 2 or 3, wherein before the first IAB node forwards the first packet according to a routing table, the method further comprises:

the first IAB node rewrites the first BAP route identifier of the first data packet into the second BAP route identifier;

the first IAB node forwarding the first packet according to a routing table comprises:

and the first IAB node forwards the first data packet according to the next hop BAP address matched with the second BAP routing identifier in the routing table.

5. The routing method according to claim 2, wherein the processing the first data packet by the first IAB node according to the BAP topology corresponding to the ingress link receiving the first data packet and the BAP topology to which the first IAB node belongs comprises:

or the first BAP address is a destination BAP address of the first data packet, and the second BAP address is a BAP address allocated by the second host node to the first IAB node.

6. The routing method according to claim 5, wherein the target condition further comprises: the first indication information included in the first packet indicates that the first packet is to be delivered to an upper layer of a BAP layer of the first IAB node.

7. The routing method according to claim 2, wherein the processing, by the first IAB node, the first packet according to the BAP topology corresponding to the ingress link receiving the first packet and the BAP topology to which the first IAB node belongs, includes:

under the condition that the BAP topology corresponding to the entry link of the first IAB node receiving the first data packet is the first BAP topology and the third BAP address is not matched with the fourth BAP address, the first IAB node forwards the first data packet according to a routing table;

the third BAP address is a destination BAP address of the first data packet, and the fourth BAP address is a BAP address allocated by the first host node to the first IAB node.

8. The routing method according to claim 2, wherein the processing the first data packet by the first IAB node according to the BAP topology corresponding to the ingress link receiving the first data packet and the BAP topology to which the first IAB node belongs comprises:

when the BAP topology corresponding to the entry link of the first IAB node receiving the first data packet is the first BAP topology and the third BAP address is matched with the fourth BAP address, the first IAB node submits the first data packet to an upper layer of a BAP layer of the first IAB node;

9. A routing method is applied to an access backhaul integrated IAB network, the IAB network comprises a first Backhaul Adaptation Protocol (BAP) topology and a second BAP topology, the first BAP topology is managed by a first host node, the second BAP topology is managed by a second host node, and the first host node is different from the second host node; the method comprises the following steps:

the first IAB node receiving a second packet from a child node of the first IAB node; the first IAB node is managed by the first hosting node, at least one parent node of the first IAB node is managed by the second hosting node, and the first IAB node belongs to the first BAP topology;

and the first IAB node forwards the second data packet according to a fourth BAP route identifier and a route table under the condition of obtaining the fourth BAP route identifier which has a mapping relation with the third BAP route identifier of the second data packet.

10. The routing method according to claim 9, wherein the method further comprises:

and the first IAB node forwards the second data packet according to a third BAP route identifier and a route table under the condition that the BAP route identifier which has a mapping relation with the third BAP route identifier of the second data packet is not obtained.

11. A communication apparatus, wherein the communication apparatus is a first IAB node in an IAB network, the IAB network comprising a first BAP topology and a second BAP topology, the second BAP topology being managed by a second hosting node, the first hosting node being different from the second hosting node, at least one parent node of the first IAB node being managed by the second hosting node, the first IAB node being managed by the first hosting node; the communication device includes:

the receiving and sending module is used for receiving the first data packet;

and the processing module is used for processing the first data packet according to the BAP topology corresponding to the entry link for receiving the first data packet and the BAP topology to which the first IAB node belongs.

12. The communication device of claim 11,

the processing module is specifically configured to, when a BAP topology corresponding to an entry link, through which the first IAB node receives the first data packet, is not the first BAP topology and does not satisfy a first condition, control the transceiver module to forward the first data packet according to a second BAP route identifier and a route table; the first condition includes: the first BAP address matches the second BAP address; the second BAP routing identifier is obtained by rewriting a first BAP routing identifier of the first data packet, and the first BAP routing identifier comprises a destination BAP address and a path identifier of the first data packet;

13. The communications apparatus of claim 12, wherein the first condition further comprises: the first indication information included in the first packet indicates that the first packet is to be delivered to an upper layer of a BAP layer of the first IAB node.

14. The communication device according to claim 12 or 13,

the processing module is further configured to rewrite the first BAP routing identifier of the first data packet to the second BAP routing identifier;

the processing module is specifically configured to control the transceiver module to forward the first data packet according to the next hop BAP address matched with the second BAP routing identifier in the routing table.

15. The communication device of claim 12,

the processing module is specifically configured to submit the first data packet to an upper layer of a BAP layer of the first IAB node when a BAP topology corresponding to an entry link, where the first IAB node receives the first data packet, is not the first BAP topology and meets a first condition; the first condition includes: the first BAP address matches the second BAP address;

16. The communications apparatus of claim 15, wherein the target condition further comprises: the first indication information included in the first packet indicates that the first packet is to be delivered to an upper layer of a BAP layer of the first IAB node.

17. The communication device of claim 12,

the processing module is specifically configured to control the transceiver module to forward the first data packet according to a routing table when a BAP topology corresponding to an entry link, where the first IAB node receives the first data packet, is the first BAP topology and a third BAP address and a fourth BAP address are not matched;

18. The communication device of claim 12,

the processing module is specifically configured to submit the first data packet to an upper layer of a BAP layer of the first IAB node when a BAP topology corresponding to an entry link, where the first IAB node receives the first data packet, is the first BAP topology and a third BAP address is matched with a fourth BAP address;

19. A communication apparatus, wherein the communication apparatus is a first IAB node in an IAB network, the IAB network comprising a first BAP topology and a second BAP topology, the second BAP topology being managed by a second hosting node, the first hosting node being different from the second hosting node, at least one parent node of the first IAB node being managed by the second hosting node, the first IAB node being managed by the first hosting node; the communication apparatus includes:

a transceiver module configured to receive a second packet from a child node of the first IAB node;

and the processing module is used for controlling the transceiver module to forward the second data packet according to a fourth BAP route identifier and a route table under the condition of obtaining the fourth BAP route identifier which has a mapping relation with the third BAP route identifier of the second data packet.

20. The communication device of claim 19,

the processing module is further configured to, when a BAP route identifier having a mapping relationship with a third BAP route identifier of the second data packet is not obtained, control the transceiver module to forward the second data packet according to the third BAP route identifier and a route table.

21. A computer-readable storage medium, in which a computer program is stored, which computer program comprises program instructions which, when executed by a processor, cause the processor to carry out the method of any one of claims 1 to 10.