Wireless Routing Method and Device

Abstract

A wireless routing method and apparatus is provided, the method being applied to a first IAB node, the method including: for upstream data, selecting an exit link without performing a lookup in a routing table, or performing a lookup in a routing table and selecting an exit link without using a routing table when routing ambiguity occurs; and performing routing based on the selected exit link.

Description

Technical Field

[0001] The present invention relates to the technical field of communications.

Background Art

[0002] IAB (Integrated Access and Backhaul) realizes the function of wireless relay in the next generation radio access network (NG-RAN). This relay node is called an IAB node (IAB-node), which can support access and backhaul (BH) simultaneously by 5G NR (New Radio). All IAB nodes are connected to one IAB donor by single-hop or multi-hop. These multi-hop connections form a DAG (Directed Acyclic Graph) topology structure with the IAB donor as the root node. The IAB donor is responsible for performing centralized resource management, topology management, and routing management in the IAB network topology.

[0003] The IAB node supports the functions of the gNB-DU (distributed unit) and is referred to as the IAB-DU, which can serve normal user equipment (UE) and IAB sub-nodes. The IAB node can also support some functions of the UE and may be called the IAB-MT (mobile termination). The IAB-MT can support, for example, the functions of the UE physical layer, the AS (access stratum) layer, the RRC (radio resource control), and the NAS (non-access stratum) layer, and can be connected to the IAB parent node. The terminal node on the network side is referred to as the IAB-donor, which enables access of the IAB-MT or UE to the network through a backhaul or an access link. The IAB-donor can be further divided into the IAB-donor-CU (central unit) and the IAB-donor-DU. The IAB-DU and the IAB-donor-CU are connected via the F1 interface. In the case of an independent networking scenario, the gNB and the IAB-donor-CU are connected via the Xn interface.

[0004] Note that the introduction of the above background art is for clearly and completely explaining the technical solution of the present invention and for easy understanding by those skilled in the art. These technical solutions should not be construed as well-known to those skilled in the art just because they are described in the background art of the present invention.

Summary of the Invention

Problems to be Solved by the Invention

[0005] To support multi-hop routing and forwarding of data packets, the IAB has introduced a Backhaul Adaptation Protocol (BAP) sublayer. The BAP sublayer is located above the RLC (radio link control) sublayer and below the IP layer, and supports functions such as selection of the destination node and path of data packets, routing and forwarding of data packets, bearer mapping, traffic (flow) control and feedback, and notification of backhaul link failure.

[0006] In the case of a multi-hop scenario, in order to realize the relay transfer of data packets, the IAB node determines the destination node to which the data packet will arrive, and then, based on the routing table, determines the next-hop node corresponding to the target (destination) node to be reached and needs to perform the transmission. The routing table is also called the backhaul routing configuration. The donor-CU sets, for the IAB node via F1AP signaling, the mapping from each F1-U Tunnel, Non-UE associated F1AP message, UE-associated F1AP message, and Non-F1 Traffic initiated by the IAB node to the BAP routing identifier (ID). The IAB node determines the BAP routing identifier corresponding to different types of uplink IP packets initiated by the IAB node based on the routing identifier mapping information, and then encapsulates a BAP sub-header (also referred to as the BAP header or BAP header) containing the BAP routing identifier information for these uplink IP packets. The donor-CU sets, via F1AP signaling, the mapping from different types of downlink data packets to the BAP routing identifier for the donor-DU. The donor-DU determines the BAP routing identifier corresponding to the received downlink IP packet based on the routing identifier mapping information, and then encapsulates a BAP sub-header containing the BAP routing identifier information for these downlink IP packets.

[0007] The BAP routing identifier includes the destination BAP address and the path identity between the IAB node and the donor-DU. The BAP address is also referred to as DESTINATION in the BAP header. Each IAB node and donor-DU has one BAP address set.

[0008] The inventors have discovered the following: That is, all existing BAP routings are managed and configured by the donor-CU of its own topology. The BAP address of each IAB node is set via RRC signaling by the donor-CU that manages the IAB node. During cross-topology transmission, in some scenarios, conflicts (competition) of BAP addresses or conflicts of routing identifiers may occur, so the routing may become ambiguous.

[0009] To solve one or more of the above problems, embodiments of the present invention provide a wireless routing method and apparatus. For upstream data, instead of looking up the routing table to select an egress link for routing, or when ambiguity in routing occurs after looking up the routing table, an egress link is selected without using the routing table for routing, so that the ambiguity in routing caused by conflicts of BAP addresses or routing identifiers can be avoided, and various scenarios of cross-topology transmission can be supported.

Means for Solving the Problem

[0010] According to a first aspect of an embodiment of the present invention, a wireless routing apparatus is provided. The apparatus is used for a first IAB node, and the apparatus includes: For upstream data, a selection unit that selects an egress link without looking up the routing table, or selects an egress link without using the routing table when ambiguity in routing occurs after looking up the routing table; and A first routing unit that performs routing based on the selected egress link.

[0011] According to a second aspect of an embodiment of the present invention, a wireless routing apparatus is provided. The apparatus is used for a first IAB node, and the apparatus includes a second routing unit. After the receiving unit of the BAP entity of the first IAB node in the second routing unit receives the BAP data packet and passes the BAP data packet to the transmitting unit of the co-located BAP entity, only the egress link corresponding to the node connected to the co-located BAP entity is selected for routing.

[0012] According to a third aspect of the embodiments of the present invention, a BAP address setting device is provided, and the device includes: a first setting unit provided in the first IAB donor CU and configured to set a BAP address for the DU of the first IAB node; and a second setting unit provided in the second IAB donor CU and configured to set a BAP address for the MT of the first IAB node.

[0013] According to a fourth aspect of the embodiments of the present invention, a BAP address setting device is provided, and the device includes a third setting unit, which does not change the BAP address under the management of the same IAB donor CU after setting the BAP address for the BAP entity of the IAB node.

[0014] According to a fifth aspect of the embodiments of the present invention, a network device is provided, and the network device includes the device described in the first aspect of the embodiments of the present invention.

[0015] According to a sixth aspect of the embodiments of the present invention, a network device is provided, and the network device includes the device described in the second aspect or the third aspect or the fourth aspect of the embodiments of the present invention.

[0016] According to a seventh aspect of the embodiments of the present invention, a communication system is provided, and the communication system includes the network device described in the fifth aspect of the embodiments of the present invention and / or the network device described in the sixth aspect of the embodiments of the present invention, and a terminal device.

[0017] According to an eighth aspect of the embodiments of the present invention, a wireless routing method is provided, and the method is used for a first IAB node, and the method includes: For upstream data, select an egress link without performing a lookup in the routing table, or select an egress link without using the routing table when a routing ambiguity occurs after performing a lookup in the routing table; and including performing routing based on the selected egress link.

[0018] According to a ninth aspect of an embodiment of the present invention, a wireless routing method is provided, which is used in a first IAB node, and the method includes:[[]] after a receiving unit of a BAP entity of the first IAB node receives a BAP data packet and passes the BAP data packet to a transmitting unit of a co-located BAP entity, only selecting an egress link corresponding to a node connected to the co-located BAP entity and performing routing.

[0019] According to a tenth aspect of an embodiment of the present invention, a method for setting a BAP address is provided, and the method includes:[[]] a first IAB donor CU setting a BAP address for a DU of a first IAB node; and a second IAB donor CU setting a BAP address for an MT of the first IAB node.

[0020] According to an eleventh aspect of an embodiment of the present invention, a method for setting a BAP address is provided, and the method includes not changing the BAP address under the management of the same IAB donor CU after setting the BAP address for a BAP entity of an IAB node.

[0021] According to a twelfth aspect of an embodiment of the present invention, a computer-readable program is provided. When the program is executed by a wireless routing device or a network device, the program causes the wireless routing device or the network device to execute the wireless routing method described in the eighth aspect or the ninth aspect of an embodiment of the present invention.

[0022] According to the thirteenth aspect of the embodiment of the present invention, a storage medium storing a computer-readable program is provided, wherein the computer-readable program causes a wireless routing device or a network device to execute the wireless routing method described in the eighth aspect or the ninth aspect of the embodiment of the present invention.

[0023] According to the fourteenth aspect of the embodiment of the present invention, a computer-readable program is provided, wherein when the program is executed by a BAP address setting device or a network device, the program causes the BAP address setting device or the network device to execute the BAP address setting method described in the tenth aspect or the eleventh aspect of the embodiment of the present invention.

[0024] According to the fifteenth aspect of the embodiment of the present invention, a storage medium storing a computer-readable program is provided, wherein the computer-readable program causes a BAP address setting device or a network device to execute the BAP address setting method described in the tenth aspect or the eleventh aspect of the embodiment of the present invention.

Advantages of the Invention

[0025] The advantageous effects according to the embodiments of the present invention are at least as follows: that is, for upstream data, routing is performed by selecting an egress link without looking up the routing table, or when routing ambiguity occurs after looking up the routing table, routing is performed by selecting an egress link without using the routing table. By doing so, it is possible to avoid routing ambiguity due to BAP address conflict or routing identifier conflict, so various scenarios of cross-topology transmission can be supported.

[0026] Specific embodiments of the present invention are disclosed in detail by referring to the following description and drawings, showing aspects in which the principles of the present invention can be adopted. It should be noted that the embodiments of the present invention are not limited in scope by these. Within the scope of the appended claims, the embodiments of the present invention may include various changes, modifications, and alternatives.

[0027] Also, the features described and / or shown for one embodiment can be used in one or more other embodiments in the same or a similar manner, combined with the features in other embodiments, or replace the features in other embodiments.

[0028] Note that terms such as "comprising / including" when used in this specification refer to the presence of features, elements, steps, or assemblies, but also refer to the fact that they do not exclude the presence or addition of one or more other features, elements, steps, or assemblies.

Brief Description of the Drawings

[0029] The elements and features described in one drawing or one embodiment of the present invention can be combined with the elements and features shown in one or more other drawings or embodiments. Also, in the drawings, similar reference numerals indicate corresponding parts in several drawings and are also used to indicate corresponding parts used in multiple embodiments.

[0030] The included drawings are used to provide a further understanding of the embodiments of the present invention. These drawings form a part of this specification, illustrate the embodiments of the present invention, and are used to explain the principles of the present invention together with the written description. Also, as is obvious, the drawings described below are only for showing some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without creative labor.

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Mode for Carrying Out the Invention

[0031] By referring to the accompanying drawings and the following description, the foregoing and other features of the present invention will become apparent. Although specific embodiments of the present invention are disclosed in the specification and drawings, they are only examples that can adopt the principles of the present invention. It should be understood that the present invention is not limited to the described embodiments, that is, the present invention also includes all changes, modifications, and alternatives within the scope of the appended claims.

[0032] In the embodiments of the present invention, the term "communication network" or "wireless communication network" may refer to a network conforming to any of the following communication standards, for example, LTE (Long Term Evolution), LTE-A (LTE-Advanced), WCDMA (registered trademark) (Wideband Code Division Multiple Access), HSPA (High-Speed Packet Access), etc.

[0033] Also, the communication between devices in the communication system may be performed according to any stage of communication protocol. For example, it may include, but is not limited to, the following communication protocols, that is, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and future 5G, New Radio (NR), etc., and / or other conventional or future-developed communication protocols.

[0034] In an embodiment of the present invention, the term "network device" refers to, for example, a device that connects a terminal device to a communication network and provides services to the terminal device in a communication system. The network device may include, but is not limited to, the following, that is, "Node" and / or "donar" in the IAB architecture, base station (BS, Base Station), access point (AP, AccessPoint), transmission reception point (TRP, Transmission Reception Point), broadcast transmitter, mobile management entity (MME, Mobile Management Entity), network gateway, server, radio network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller), and the like.

[0035] Among them, the base station may include, but is not limited to, the following, that is, Node B (NodeB or NB), evolved Node B (eNodeB or eNB), 5G base station (gNB), etc., and may further include RRH (Remote Radio Head), RRU (Remote Radio Unit), relay or low-power node (for example, femto, pico, etc.). In addition, the term "base station" may include some or all of their functions, and each base station can provide communication coverage for a specific geographical area. The term "cell" may refer to a base station and / or the area it covers, which depends on the context of the term.

[0036] In an embodiment of the present invention, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network by a network device and receives services from the network. The user equipment may be fixed or mobile, and is also referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, etc. For example, it is a terminal device served by an IAB node or an IAB donor in an IAB architecture.

[0037] Among them, the user equipment may include, but is not limited to, for example, a cellular phone, a PDA (Personal Digital Assistant), a wireless modem, a wireless communication device, a portable device, a machine type communication device, a laptop computer, a cordless telephone, a smartphone, a smartwatch, a digital camera, etc.

[0038] Also, for example, in a scenario such as IoT (Internet of Things), the user equipment may further be a device or apparatus that performs monitoring or measurement. For example, it may include, but is not limited to, the following, that is, a machine type communication (MTC) terminal, a vehicle-mounted communication terminal, a D2D (Device to Device) terminal, an M2M (Machine to Machine) terminal, etc.

[0039] Hereinafter, the scenario of the embodiment of the present invention will be described based on examples, but the present invention is not limited thereto.

[0040] FIG. 1 is a diagram showing the architecture of the entire IAB in an embodiment of the present invention. As shown in FIG. 1, the architecture of the entire IAB uses the standalone (SA) mode. FIG. 2 is another diagram showing the architecture of the entire IAB in an embodiment of the present invention. As shown in FIG. 2, the architecture of the entire IAB uses the dual connectivity (EN-DC) mode. In the dual connectivity mode, the IAB node is connected to one MeNB by E-UTRA, and the IAB donor terminates X2-C as the SgNB.

[0041] FIG. 3 is a diagram showing the protocol stack of the F1-U interface between the IAB-DU and the IAB-donor-CU, and FIG. 4 is a diagram showing the protocol stack of the F1-C interface between the IAB-DU and the IAB-donor-CU. In FIGS. 3 and 4, F1-U and F1-C are described by taking a two-hop backhaul as an example.

[0042] In an embodiment of the present invention, F1-U and F1-C use the IP transport layer between the IAB-DU and the IAB-donor-CU, and F1-U and F1-C have security protection.

[0043] In an embodiment of the present invention, in the wireless backhaul, the IP layer is transmitted by the BAP sublayer so as to ensure multi-hop routing, and the IP layer can also be used for non-F1 services, for example, OAM (Operation Administration and Maintenance) services.

[0044] In an embodiment of the present invention, in each backhaul link, the BAP PDUs are transmitted by the BH RLC channel. In each BH link, a plurality of BH RLC channels may be set, and in this way, traffic prioritization and QoS (Quality of Service) enforcement can be permitted.

[0045] In an embodiment of the present invention, the BAP entity in each IAB node and IAB-donor-DU performs mapping of the BH RLC channel of BAP PDUs.

[0046] Hereinafter, an exemplary application scenario in an embodiment of the present invention will be exemplarily described.

[0047] In 3GPP (registered trademark), in order to achieve inter-donor topology redundancy (or inter-CU topology redundancy), it is determined to support the following two cases. In principle, one IAB-DU has an F1 interface with only one donor-CU, that is, Case 1: The IAB node has a multi-connection with two IAB donors; and Case 2: The parent node and / or ancestor node of the IAB node has a multi-connection with two IAB donors at the same time.

[0048] FIG. 5 is a diagram showing an exemplary application scenario 1 in an embodiment of the present invention. As shown in FIG. 5, the shown scenario is an inter-donor topology redundancy scenario. The IAB node 3 is a dual-connection node, which is simultaneously connected to donor-CU1 and donor-CU2. The IAB-DU (IAB-DU3) of the IAB node 3 and one parent node DU (IAB-DU2) terminate at different IAB-donor-CUs, that is, they terminate at donor-CU1 and donor-CU2 respectively. In an embodiment of the present invention, the IAB node 3 may be referred to as a boundary IAB node.

[0049] As shown in Fig. 5, the IAB-DU (IAB-DU3) of IAB node 3 terminates at CU1 with F1, and the DU (IAB-DU2) of one of the parent nodes of IAB node 3, i.e., IAB node 2, terminates at CU2 with F1. The descendant IAB nodes of IAB node 3 refer to the following, i.e., nodes that access the network through the border IAB node, and each node is singly connected to its parent node. For example, IAB node 4 is a descendant IAB node of IAB node 3, and its parent node (IAB node 3) is connected to donor-CU1 and donor-CU2 simultaneously.

[0050] The F1-termination node refers to the donor-CU that terminates the F1 interface of the border IAB node and the descendant nodes, for example, donor-CU1. As shown in Fig. 5, both IAB-DU3 and IAB-DU4 terminate at donor-CU1 with F1.

[0051] The Non-F1-termination node refers to the CU with a donor function that does not terminate the F1 interface of the border IAB node and the descendant nodes, for example, donor-CU2.

[0052] Also, Fig. 5 is only one exemplary configuration of the scenario, and it may further have other IAB nodes. For example, there may be further multiple nodes for multi-hop connection between IAB node 3 and IAB node 4.

[0053] In an embodiment of the present invention, the main purpose of topology redundancy is to be able to perform service load balancing. When there are too many service flows in the topology managed by one donor-CU, some services can be offloaded to the topology network managed by another donor-CU, that is, data transmission is performed through the redundant path. When service offloading is required, the donor that terminates the F1 interface starts service offloading to other donors, and the F1 interfaces of the border IAB node and its descendant nodes below all terminate at the same donor. For the IAB-MT that is dual-connected to two IAB-donors, load balancing based on each F1-U pipeline (tunnel) should be supported. When performing donor-to-donor topology redundancy, for F1-C traffic, the load balancing granularity is associated for each transport network layer (TNL).

[0054] Also, in R17, radio link failure (RLF) recovery and migration between donors are supported, which means that the source parent node and the destination parent node are served by different IAB-donor-CUs.

[0055] In the scenario of partial migration, the IAB-MT of the border IAB node has already migrated to the second IAB-donor-CU, the IAB-DU of the border IAB node still terminates F1 at the first IAB-donor-CU, and when the border IAB node has descendant IAB nodes, its descendant IAB nodes also still terminate F1 (F1-terminating) at the first IAB-donor-CU.

[0056] FIG. 6 is a diagram showing an exemplary application scenario 2 in an embodiment of the present invention. As shown in FIG. 6, what is shown is a scenario of one partial migration.

[0057] As shown in FIG. 6, IAB node 3 is a border IAB node, which is a transition node. The IAB-MT3 of IAB node 3 has changed from being singly connected to one parent node (IAB node 1) to being singly connected to another parent node (IAB node 2). The IAB-DU3 of IAB node 3 and the child node IAB node 4 of IAB node 3 are all still F1-connected to donor-CU1, but the path through which this F1 connection finally reaches CU1 via IAB node 2.

[0058] All current BAP routings are managed and configured by the donor-CU of its own topology. The BAP address of each IAB node is set using RRC signaling by the donor-CU that manages the IAB node. In the case of the scenario of donor-to-donor topology redundancy, the border IAB node may have one BAP address in each topology.

[0059] For example, in the scenario of FIG. 5, the BAP addresses of IAB node 1, IAB node 4, and donor-DU1 are set by donor-CU1, and they constitute the first topology. The BAP addresses of IAB node 2 and donor-DU2 are set by donor-CU2, and they constitute the second topology. The border IAB node, that is, IAB node 3, belongs to the two topologies. IAB node 3 may have one BAP address set by donor-CU1 and donor-CU2 respectively. These two BAP addresses may be the same or different. Since different donor-CUs assign independently when assigning BAP addresses without a negotiation process, the BAP addresses in the two topologies may be the same, that is, a conflict of BAP addresses may occur. In some scenarios during cross-topology transmission, the conflict of BAP addresses may cause routing ambiguity.

[0060] For example, the two parent nodes of IAB node 3 as a border IAB node, namely, IAB node 1 and IAB node 2, belong to the first topology and the second topology respectively, and the BAP addresses of IAB node 1 and IAB node 2 may be the same. When the BAP addresses of IAB node 1 and IAB node 2 are the same, and IAB node 3 needs to receive and route an upstream BAP data packet (which may also be called uplink data, that is, data received by the IAB-DU from its child node), in the routing table, the Next Hop BAP Address corresponding to one or more BAP routing identifiers may be ambiguous. Thus, since the BAP address of the next hop in the routing table does not know which of IAB node 1 and IAB node 2 it refers to, it will cause routing ambiguity.

[0061] Also, since IAB node 3 as a border IAB node can pass through different topologies in the upstream direction, the routing identifiers used by the two topologies may be the same. That is, there may be two entries in the routing table of IAB node 3 that contain the same routing identifier. Similarly, the routing identifier in the direction of the second path in the upstream direction may also be the same as the downstream routing identifier. When IAB node 3 performs a lookup in the routing table after receiving a BAP data packet, there may be a case where the routing identifier in the routing table is not unique. Thus, since the next hop node cannot be determined either, it will cause routing ambiguity.

[0062] Also, in the scenarios of FIGS. 5 and 6, since the first topology and the second topology are each independently assigned a BAP address, the BAP addresses between the two topologies may conflict. For example, the BAP addresses of IAB node 2 and IAB node 4 may be the same. Both IAB node 2 and IAB node 4 are adjacent nodes of IAB node 3, and all of their BAP addresses may appear in the "next-hop BAP address" of the routing table of IAB node 3. When the next-hop BAP address corresponding to a certain routing identifier is this BAP address, since it is unknown which egress link to send the BAP data packet to, routing ambiguity will occur.

[0063] Also, in the partial transition scenario shown in FIG. 6, IAB-MT3 has already migrated to the topology of donor-CU2, and donor-CU2 has also set the BAP address by means of an RRC message. However, since IAB-DU3 is still managed by donor-CU1, what is actually stored in donor-CU1 is still the BAP address of IAB node 3 before migration, that is, the BAP address assigned by donor-CU1 through RRC. In the topology managed by donor-CU1, the BAP addresses corresponding to IAB node 3 in all routing tables are all the old BAP address of IAB node 3. The BAP address regarding the parent node IAB node 3 stored by the child node of IAB node 3 is also the old BAP address. Thus, it may bring uncertainty to the setting of the BAP address. For example, when a new IAB node 5 (not shown in FIG. 6) accesses IAB node 3 and becomes a child node of IAB node 3, and this child node needs to have the BAP address of the parent node set (stored), in this case, it may bring uncertainty as to which BAP address of IAB node 3 should be used. That is, there is a problem of ambiguity when using multiple BAP addresses of the border IAB node.

[0064] Also, according to the existing mechanism, once the BAP address is set for the BAP entity of the IAB node, the BAP address cannot change.

[0065] Also, in the scenarios shown in FIGS. 5 and 6, radio link failure (RLF) may also occur in the links connected to the border IAB node.

[0066] For example, in the scenario of redundancy of the donor - to - donor topology shown in FIG. 5, radio link failure (RLF) may occur in the link of a certain parent node of the border IAB node. For example, a radio link failure occurred in the link of the parent node of the second path shown in FIG. 5, that is, the link between IAB node 3 and IAB node 2.

[0067] FIG. 7 is a diagram showing the radio link failure that occurred in Application Scenario 1 in an embodiment of the present invention. In FIG. 7, it is shown that a radio link failure occurred in the link between IAB node 3 and IAB node 2.

[0068] In the scenario of partial migration shown in FIG. 6, after a predetermined period has elapsed since the partial migration, the border IAB node may experience a radio link failure (RLF). For example, a radio link failure occurred in the link from IAB node 3 to IAB node 2 in FIG. 6, that is, an interruption occurred. IAB node 3 may perform RLF recovery and return to the original parent node, that is, IAB node 1. Thus, all of IAB node 3 and its descendant nodes return to the scenario before the partial migration, that is, a rollback (reversal) of the partial migration occurs, which may also be understood as another migration.

[0069] FIG. 8 is a diagram showing the rollback of the partial migration that occurred in Application Scenario 2 in an embodiment of the present invention. In FIG. 8, it is shown that IAB node 3 and its descendant node (IAB node 4) return to the scenario before the partial migration, that is, a rollback of the partial migration occurs.

[0070] When a radio link failure occurs in a link connected to the border IAB node shown in FIGS. 7 and 8, there is currently no effective mechanism for routing.

[0071] To solve one or more of the above problems, various embodiments in the embodiments of the present invention will be described below with reference to the drawings. Note that these embodiments are merely examples and do not limit the present invention.

Embodiment

[0072] An embodiment of the present invention provides a wireless routing method, which is used for a first IAB node.

[0073] In an embodiment of the present invention, the IAB-DU of the first IAB node and one parent node of the first IAB node terminate at different IAB donor CUs (IAB-donor-CUs). For example, the first IAB node is called a border IAB node.

[0074] For example, the first IAB node is IAB node 3 in FIG. 5.

[0075] FIG. 9 is a diagram showing a wireless routing method in Embodiment 1 of the present invention. As shown in FIG. 9, the method includes the following steps.

[0076] Step 901: For upstream data, select an egress link without looking up the routing table, or select an egress link without using the routing table when routing ambiguity occurs after looking up the routing table; and Step 902: Perform routing based on the selected egress link.

[0077] In this way, for the data in the upstream direction of the first IAB node, instead of performing a lookup on the routing table, the egress link is directly selected for routing, or when a routing ambiguity occurs after performing a lookup on the routing table, the routing table is not used and the egress link is selected for routing, thereby avoiding routing ambiguity due to BAP address conflict or routing identifier conflict.

[0078] For example, in the scenario shown in FIG. 5, even if the BAP addresses of IAB node 1 and IAB node 2 are the same, or there are two entries containing the same routing identifier in the routing table of IAB node 3, or the routing identifier in the direction of the second path in the upstream direction is the same as the routing identifier in the downstream direction, since IAB node 3 does not perform a lookup on the routing table and directly selects the egress link for routing, routing ambiguity due to BAP address conflict or routing identifier conflict can be avoided.

[0079] In an embodiment of the present invention, for example, the data in the upstream direction includes BAP data packets.

[0080] In step 901, for the data in the upstream direction, the first IAB node selects the egress link without performing a lookup on the routing table. In other words, the first IAB node does not need to set the upstream routing entry and directly selects the egress link for routing.

[0081] Alternatively, in step 901, when a routing ambiguity appears after performing a lookup on the routing table, the egress link is selected. For example, when duplicate routing IDs appear, or when the BAP address of the next hop is for two parent nodes, the egress link is selected without using the routing table. Hereinafter, the method by which the first IAB node selects the egress link in step 901 will be specifically described.

[0082] In step 901, an egress link can be selected by performing a lookup on the first BAP header rewriting table. For example, by performing a lookup on the first BAP header rewriting table, it is possible to determine whether the first BAP header rewriting table contains an entry for the routing identifier in the BAP header of the upstream BAP data packet, thereby selecting an egress link.

[0083] For example, after the receiving part of the BAP entity of the first IAB node DU receives a BAP data packet and transmits it to the transmitting part of the co-located BAP entity (the BAP entity of the IAB-MT), a lookup is performed on the first BAP header rewriting table to determine whether the first BAP header rewriting table contains an entry for the routing identifier in the BAP header of the upstream BAP data packet.

[0084] In an embodiment of the present invention, the first BAP header rewriting table may also be referred to as the first header rewriting configuration, or may be referred to as the first routing identifier mapping configuration. What it contains is the mapping relationship between the old (previous) routing identifier and the new routing identifier. The first BAP header rewriting table is for the first IAB node to rewrite the routing identifier of the BAP header.

[0085] In an embodiment of the present invention, the old routing identifier may also be referred to as the ingress routing identifier or the routing identifier to be rewritten. It represents the BAP routing identifier that needs to be rewritten or replaced. The new routing identifier may also be referred to as the egress routing identifier.

[0086] The first BAP header rewriting table is used for inter-topology transmission, and is applicable to the case of topology redundancy where the first IAB node is in a dual connection, and the case of single connection where the first IAB node is in a partial transition, and can be divided into upstream and downstream BAP header rewritings. When the first BAP header rewriting table is the BAP header rewriting setting regarding upstream, the routing identifier corresponding to the new routing identifier is the routing identifier of the second path in FIG. 5.

[0087] In an embodiment of the present invention, the first BAP header rewriting table may be set by the DU IAB donor CU that manages the first IAB node. For example, in the case of the scenario shown in FIG. 5, the first BAP header rewriting table at IAB node 3 is set by donor-CU1.

[0088] FIG. 10 is a diagram showing a realization method of step 901 in Embodiment 1 of the present invention. As shown in FIG. 10, the method includes the following steps.

[0089] Step 1001: When the routing identifier in the BAP header of the BAP data packet is the same as the previous routing ID in one entry of the first BAP header rewriting table, select the egress link corresponding to the parent node that terminates at the IAB donor CU (IAB-donor-CU) different from the first IAB node; and / or Step 1002: When the routing identifier in the BAP header of the BAP data packet is different from the previous routing IDs in all entries of the first BAP header rewriting table, select the egress link corresponding to the parent node that terminates at the IAB donor CU (IAB-donor-CU) the same as the first IAB node.

[0090] In an embodiment of the present invention, the selected egress link is available. When the selected egress link is unavailable, processing, such as re-routing, etc., may be performed according to the prior art.

[0091] For example, when the routing identifier in the BAP header of the BAP data packet is the same as the old routing identifier in one entry of the first BAP header rewrite table, select the egress link corresponding to the parent node, i.e., IAB node 2, which terminates at an IAB-donor-CU different from IAB-DU3 in FIG. 5. That is, the BAP data packet needs to be transmitted via the second path. When the routing identifier in the BAP header of the BAP data packet is different from the old routing identifiers in all entries of the first BAP header rewrite table, select the egress link corresponding to the parent node, i.e., IAB node 1, which terminates at the same IAB-donor-CU as IAB-DU3 in FIG. 5. That is, the BAP data packet needs to be transmitted via the first path.

[0092] In an embodiment of the present invention, determining whether one parent node and a first IAB node DU terminate at the same IAB-donor-CU means determining whether the parent node and the first IAB node belong to the same topology. In a scenario of redundant donor-to-donor topologies, the F1 terminal node may be a master node (MN) or a secondary node (SN). Therefore, the MCG (master cell group) may correspond to the first path or the second path. Similarly, the SCG (secondary cell group) may also correspond to the first path or the second path. Hereinafter, a specific determination method will be exemplarily described.

[0093] In the bap-Config IE in the RRCReconfiguration (RRC reconfiguration) message, there are selectable fields defaultUL-BAP-RoutingID and defaultUL-BH-RLC-Channel for setting the default uplink path. The IAB node uses them to perform routing and select the BH RLC channel for F1-C and non-F1 flows (traffic) in the processes of bootstrapping, handover, RRC recovery of IAB-MT, and RRC re-establishment of IAB-MT. These two fields are only required in the bootstrapping process of the IAB node. When receiving the latest RRC reconfiguration message containing these two fields, it is possible to determine which cell group (or parent node link) corresponds to the F1-terminated donor and which cell group corresponds to the non-F1-terminated donor.

[0094] FIG. 11 is a diagram showing a method for determining whether a parent node is F1-terminated to the same IAB donor CU as the first IAB node in Embodiment 1 of the present invention. As shown in FIG. 11, the method includes the following steps.

[0095] Step 1101: When the latest RRC reconfiguration message received by the first IAB node and containing at least one of defaultUL-BAP-RoutingID and defaultUL-BAP-BH-RLC-Channel is from one parent node, the F1-terminated donor of the parent node and the first IAB node DU is the same, and the F1-terminated donor of the other parent node of the first IAB node is different from that of the first IAB node, that is, the F1-terminated donor of the other parent node is the non-F1-terminated donor of the first IAB node, and at least one of the defaultUL-BAP-RoutingID and the defaultUL-BAP-BH-RLC-Channel is included in the first BAP configuration IE (bap-Config IE) in the RRC reconfiguration message.

[0096] FIG. 12 is a diagram showing another method for determining whether a parent node terminates at the same IAB donor CU as the first IAB node in Embodiment 1 of the present invention. As shown in FIG. 12, the method includes the following steps.

[0097] Step 1201: Add a new IE representing the second BAP setting to the RRCReconfiguration message, for example, called secondary-bap-Config, and the fields therein are the same as the existing bap-Config, indicating that the setting is from a non-F1 terminated donor CU.

[0098] The method further includes the following steps.

[0099] Step 1202: When the latest RRC reconfiguration message including the first BAP setting IE (bap-Config IE) is received from one of the parent nodes of the first IAB node, the parent node and the first IAB node terminate at the same IAB donor CU; and / or Step 1203: When the latest RRC reconfiguration message including the second BAP setting IE is received from one of the parent nodes of the first IAB node, the parent node and the first IAB node terminate at different IAB donor CUs.

[0100] The method shown in FIG. 9 can be used, for example, when the first IAB node is in a dual connection and no radio link failure occurs in any of the links between the first IAB node and its parent node. Hereinafter, the case where the first IAB node is in a dual connection and a radio link failure (RLF) occurs in the link between the first IAB node and one of its parent nodes will be described.

[0101] FIG. 13 is another diagram showing the wireless routing method in Embodiment 1 of the present invention. As shown in FIG. 13, the method includes the following steps.

[0102] Step 1301: When the first IAB node is in dual connection and a radio link failure (RLF) occurs in the link between the first IAB node and one of its parent nodes, select an available egress link.

[0103] For example, in the scenario shown in FIG. 7, when a radio link failure occurs in the link between IAB node 3 and one of its parent nodes, i.e., IAB node 2, select an available egress link, i.e., the egress link corresponding to the other parent node (IAB node 1).

[0104] Also, for example, for the scenario shown in FIG. 8, a radio link failure occurs in the link from IAB node 3 to IAB node 2, i.e., an interruption occurs. When IAB node 3 performs RLF recovery and returns to the original parent node, i.e., IAB node 1, select an available egress link, i.e., the egress link corresponding to IAB node 1.

[0105] In this way, when a radio link failure occurs in the link connected to the border IAB node, an effective routing mechanism can be provided.

[0106] Also, when a radio link failure occurs in the link connected to the border IAB node, rewrite the BAP header based on the second BAP header rewrite table.

[0107] For example, as shown in FIG. 7, when a radio link failure occurs in the link of the parent node of the second path, the second path becomes unusable, and the border IAB node should re-route the BAP data packets that originally needed to be routed via the second path to the first path. Also, since the routing ID included in the BAP header of the BAP data received by the border IAB node is still for donor-DU2, it is necessary to rewrite the BAP header at the border IAB node. The BAP header rewrite at this time is to rewrite the BAP routing ID for donor-DU2 in the BAP header to the BAP routing ID for donor-DU1, and this new BAP routing ID is in the topology managed by CU1. At this time, the corresponding one is the second BAP header rewrite table.

[0108] Also, for example, as shown in FIG. 8, in the process of partial migration rollback, the settings of donor-CU1 for the border IAB node (IAB node 3) and its descendant nodes (IAB node 4) require a certain period of time. During this period, the uplink data of the descendant nodes may still use the original routing settings, or on-the-fly data (data in transmission) may still exist. Therefore, the routing ID included in the BAP header of the BAP data received by the border IAB node is still for donor-DU2, that is, the one before RLF recovery, and it is necessary to rewrite the BAP header at the border IAB node. The BAP header rewrite at this time is to rewrite the BAP routing ID for donor-DU2 in the BAP header to the BAP routing ID for donor-DU1, and this new BAP routing ID is in the topology managed by CU1. At this time, the corresponding one is also the second BAP header rewrite table.

[0109] In an embodiment of the present invention, the second BAP header rewrite table is also referred to as the second header rewrite setting, which is used in the case of RLF occurrence or handover of the border node. Further, the second header rewrite setting may be referred to as the header rewrite setting for inter-donor-DU re-routing, which is only for the uplink data.

[0110] In an embodiment of the present invention, the first BAP header rewrite table and the second BAP header rewrite table are set as two tables, or are set as two separate partial entries in one table. In this way, it is possible to avoid the uncertainty of routing selection caused by two same "old routing identifiers" corresponding to different "new routing identifiers".

[0111] In an embodiment of the present invention, when the BAP header rewrite table is set in the first IAB node, it is necessary to determine whether to perform a rewrite on the BAP header.

[0112] FIG. 14 is a diagram showing a method of performing a rewrite using the BAP header rewrite table in Embodiment 1 of the present invention. As shown in FIG. 14, the method includes the following steps.

[0113] Step 1401: When the first IAB node is in dual connection and no radio link failure occurs in any of the links between the first IAB node and its parent node, look up the first BAP header rewrite table using the routing identifier of the BAP header of the upstream BAP data packet to determine whether to perform a BAP header rewrite; and / or Step 1402: When the first IAB node is in dual connection and a radio link failure occurs in the link between the first IAB node and one of its parent nodes, look up the second BAP header rewrite table using the routing identifier of the BAP header of the BAP data packet to determine whether to perform a BAP header rewrite.

[0114] When the first IAB node is in a dual connection or a single connection, further, the following method may be used to determine whether to perform BAP header rewriting. When a first BAP header rewriting table is set, first, use the routing identifier in the BAP header of the BAP data packet to perform a lookup on the first BAP header rewriting table, find the matched new routing identifier, and when the corresponding egress link is available, perform BAP header rewriting according to the first BAP header rewriting table. Also, when the matched new routing identifier is not found, or when the matched new routing identifier is found but the corresponding egress link is unavailable, perform a lookup on the second BAP header table to determine whether to perform BAP header rewriting.

[0115] When the first IAB node is in a dual connection or a single connection, further, the following method may be used to determine whether to perform BAP header rewriting. Since the second BAP header table is usually for the case of RLF occurrence, it is necessary to perform re-routing in one primary period. Once the setting of each descendant node is completed, the on-the-fly data transmission is also completed, and the donor-CU can release or delete the second BAP header table of the first IAB node. Therefore, the second BAP header rewriting table can be regarded as having a high priority. When the first BAP header rewriting table and the second BAP header rewriting table are set, determine whether to perform BAP header rewriting according to the second BAP header rewriting table. Alternatively, as long as the second BAP header rewriting table is set, it may be said that BAP header rewriting is performed according to the second BAP header rewriting table.

[0116] In step 1401 or step 1402, when the routing identifier in the BAP header of the BAP data packet is the same as the previous routing ID in one entry of the BAP header rewrite table for which the lookup is performed, it is necessary to perform BAP header rewriting. Also, when the routing identifier in the BAP header of the BAP data packet is different from the previous routing identifiers in all entries of the BAP header rewrite table for which the lookup is performed, it is not necessary to perform BAP header rewriting. In an embodiment of the present invention, after step 1401 or step 1402, that is, after performing header rewriting, the selection operation of the egress link in step 901 or step 1301 can be performed.

[0117] FIG. 15 is a diagram showing a specific implementation of the wireless routing method in Embodiment 1 of the present invention. As shown in FIG. 15, the method includes the following steps.

[0118] Step 1501: The receiving part of the BAP entity of the first IAB node DU receives the BAP data packet and transmits it to the transmitting part of the co-located BAP entity; Step 1502: When the first IAB node is in dual connection and no wireless link failure occurs in any of the links between the first IAB node and its parent node, perform a lookup on the first BAP header rewrite table using the routing identifier of the BAP header of the upstream BAP data packet to determine whether to perform BAP header rewriting; Step 1503: Perform BAP header rewriting based on the first BAP header rewrite table; Step 1504: By performing a lookup on the first BAP header rewrite table, determine whether the first BAP header rewrite table includes an entry for the routing identifier in the BAP header of the upstream BAP data packet, thereby selecting an egress link; Step 1505: When the first IAB node is in dual connection and a radio link failure occurs in the link between the first IAB node and one of its parent nodes, perform a lookup in the second BAP header rewrite table using the routing identifier in the BAP header of the BAP data packet to determine whether to perform BAP header rewriting; Step 1506: Perform BAP header rewriting based on the second BAP header rewrite table; Step 1507: Select an available egress link; and Step 1508: Perform routing based on the selected egress link, that is, transmit the BAP data packet after BAP header rewriting to the node of the next hop via the selected egress link.

[0119] In an embodiment of the present invention, the MT and DU of the first IAB node may each be set with a BAP address. That is, the first IAB donor CU sets a BAP address for the DU of the first IAB node, and the second IAB donor CU sets a BAP address for the MT of the first IAB node.

[0120] For example, the BAP address of the first IAB node DU is used for the first IAB donor CU of the first IAB node to manage the process of setting for the nodes of the first topology.

[0121] For example, the settings performed by the first IAB donor CU for the nodes of the first topology include at least one of routing table setting, BHR RLC Channel setting and mapping, and UE context setting.

[0122] For example, when the second IAB node selects the cell of the first IAB node DU as the serving cell during cell selection, the first IAB donor CU that manages the first IAB node performs cell group configuration (CellGroupConfig) for the second IAB node by means of an RRC reconfiguration message, and the BAP address (bap-Address) in the cell group configuration represents the BAP address of the parent node DU belonging to the cell group.

[0123] In this way, the problem of ambiguity when using multiple BAP addresses of the border IAB node can be solved.

[0124] For example, in the scenario shown in FIG. 6, one new IAB node 5 (not shown in FIG. 6) selects the cell of IAB-DU3 as the serving cell during cell selection and accesses IAB node 3. IAB-donor-CU1 performs cell group configuration (CellGroupConfig) for IAB node 5 by means of RRCReconfiguration, and the bap-Address in the CellGroupConfig represents the BAP address of the parent node DU belonging to the cell group. Alternatively, it can be said that the bap-Address in the CellGroupConfig represents the BAP address saved by the parent node belonging to the cell group in its F1 terminating CU.

[0125] For non-border IAB nodes, the IAB-MT and IAB-DU can use the same BAP address. Also, when a non-border IAB node becomes a border IAB node, BAP addresses can be set for its IAB-MT and IAB-DU respectively.

[0126] In an embodiment of the present invention, after setting a BAP address for the BAP entity of an IAB node, the BAP address cannot be changed under the management of the same IAB donor CU. Also, when the IAB donor CU managing the IAB node changes or a new IAB donor is added, the changed or newly added IAB donor CU re - sets the BAP address of the BAP entity of the IAB node. In this way, the problem that the BAP address cannot be changed in the existing mechanism can be solved.

[0127] As can be seen from the above - mentioned embodiment, for upstream data, the first IAB node directly selects an egress link for routing without looking up the routing table, or when routing ambiguity occurs after looking up the routing table, it selects an egress link for routing without using the routing table, thereby avoiding routing ambiguity caused by BAP address conflict or routing identifier conflict.

Embodiment

[0128] An embodiment of the present invention provides a wireless routing method, which is applied to a first IAB node. The IAB - DU of the first IAB node and one parent node of the first IAB node terminate at different IAB donor CUs (IAB - donor - CUs). For example, the first IAB node is referred to as a border IAB node.

[0129] For example, the first IAB node is the IAB node 3 in FIGS. 5 and 6.

[0130] FIG. 16 is a diagram showing the wireless routing method in Embodiment 2 of the present invention. As shown in FIG. 16, the method includes the following steps.

[0131] Step 1601: After the receiving unit of the BAP entity of the first IAB node receives the BAP data packet and passes the BAP data packet to the transmitting unit of the co-located BAP entity, only select the egress link corresponding to the node connected to the co-located BAP entity for routing.

[0132] In this way, the problem that conflicts may occur in the uplink / downlink link routing identifiers in the routing table can be further solved.

[0133] For example, in step 1601, after the receiving unit of the BAP entity of the first IAB node receives the BAP data packet and passes the BAP data packet to the transmitting unit of the co-located BAP entity, obtain the BAP address of the next hop corresponding to the routing identifier of the BAP header by looking up the routing table, and when the BAP addresses of the two adjacent nodes of the first IAB node are both the same as the BAP address of the next hop, among the two adjacent nodes, select the egress link corresponding to the node connected to the co-located BAP entity for routing.

[0134] In this way, for the scenarios of FIGS. 5 and 6, since the BAP addresses are respectively and independently assigned to the first topology and the second topology, the BAP addresses between the two topologies may conflict. For example, the BAP addresses of IAB node 2 and IAB node 4 may be the same. Both IAB node 2 and IAB node 4 are adjacent nodes of IAB node 3, and their BAP addresses may all appear in the "BAP address of the next hop" in the routing table of IAB node 3. When the BAP address of the next hop corresponding to a certain routing identifier is this BAP address, since it is not known which egress link to send the BAP data packet to, routing ambiguity may occur. In contrast, in the present invention, in step 1601, by selecting the egress link corresponding to the node connected to the co-located BAP entity among the two adjacent nodes for routing, the problem of routing ambiguity can be solved.

Embodiment

[0135] In an embodiment of the present invention, a method for setting a BAP address is provided, and this method is used for an IAB donor.

[0136] FIG. 17 is a diagram showing the BAP address setting method in Embodiment 3 of the present invention. As shown in FIG. 17, this method includes the following steps.

[0137] Step 1701: The first IAB donor CU sets a BAP address for the DU of the first IAB node; and Step 1702: The second IAB donor CU sets a BAP address for the MT of the first IAB node.

[0138] For example, the BAP address of the first IAB node DU is used for the first IAB donor CU of the first IAB node to manage the process of setting for the nodes of the first topology.

[0139] For example, the settings performed by the first IAB donor CU for the nodes of the first topology include at least one of routing table setting, BH RLC Channel setting and mapping, and UE context setting.

[0140] For example, when the second IAB node selects the cell of the first IAB node DU as the serving cell when performing cell selection, the first IAB donor CU that manages the first IAB node performs cell group setting (CellGroupConfig) for the second IAB node by an RRC reconfiguration message, and the BAP address (bap-Address) in the cell group setting represents the BAP address of the parent node DU belonging to the cell group.

[0141] For example, in the scenario shown in FIG. 6, one new IAB node 5 (not shown in FIG. 6) selects IAB-DU 3 as the serving cell during cell selection and accesses IAB node 3. The IAB-donor-CU 1 performs cell group configuration (CellGroupConfig) for the IAB node 5 by means of RRCReconfiguration. The bap-Address in the CellGroupConfig represents the BAP address of the parent node DU belonging to the cell group. Alternatively, it may be said that the bap-Address in the CellGroupConfig represents the BAP address that the parent node belonging to the cell group stores in its F1 terminated CU.

[0142] In this way, the problem of ambiguity when using multiple BAP addresses of the border IAB node can be solved.

Embodiment

[0143] In an embodiment of the present invention, a method for setting a BAP address is provided, and the method is used for an IAB donor.

[0144] FIG. 18 is a diagram showing a method for setting a BAP address in Embodiment 4 of the present invention. As shown in FIG. 18, the method includes the following steps.

[0145] Step 1801: After setting a BAP address for the BAP entity of the IAB node, the BAP address is not changed under the management of the same IAB donor CU.

[0146] As shown in FIG. 18, the method further includes the following steps.

[0147] Step 1802: When the IAB donor CU managing the IAB node changes or a new IAB donor is added, the changed or newly added IAB donor CU re-sets the BAP address of the BAP entity of the IAB node.

[0148] In this way, it is possible to solve the problem that the BAP address cannot be changed in the existing mechanism.

Embodiment

[0149] In an embodiment of the present invention, a wireless routing device is provided, and the device is used for a first IAB node. The device corresponds to the method described in Embodiment 1.

[0150] FIG. 19 is a diagram showing a wireless routing device in Embodiment 5 of the present invention. As shown in FIG. 19, the device 1900 includes the following.

[0151] Selection unit 1901: For upstream data, select an egress link without performing a lookup in the routing table, or select an egress link without using the routing table when a routing ambiguity occurs after performing a lookup in the routing table; and First routing unit 1902: Perform routing based on the selected egress link.

[0152] In an embodiment of the present invention, the selection unit 1901 can select an egress link by performing a lookup in a first BAP header rewrite table.

[0153] For example, the selection unit 1901 performs a lookup in the first BAP header rewrite table to determine whether the first BAP header rewrite table contains an entry for the routing identifier in the BAP header of the upstream BAP data packet.

[0154] In an embodiment of the present invention, when the routing identifier in the BAP header of the BAP data packet is the same as the previous routing ID in one entry of the first BAP header rewrite table, the selection unit selects an exit link corresponding to a parent node that terminates at an IAB-donor-CU different from the first IAB node, and / or when the routing identifier in the BAP header of the BAP data packet is different from the previous routing identifiers in all entries of the first BAP header rewrite table, the selection unit selects an exit link corresponding to a parent node that terminates at the same IAB-donor-CU as the first IAB node.

[0155] In an embodiment of the present invention, when the RRC reconfiguration message received by the first IAB node and including at least one of the latest defaultUL-BAP-RoutingID and defaultUL-BAP-BH-RLC-Channel is from one parent node, the F1 termination donor of the parent node and the first IAB node DU is the same, and the F1 termination donor of another parent node of the first IAB node and the first IAB node is different, that is, the F1 termination donor of the another parent node is the non-F1 termination donor of the first IAB node, and at least one of the defaultUL-BAP-RoutingID and the defaultUL-BAP-BH-RLC-Channel is included in the first BAP configuration IE (bap-Config IE) in the RRC reconfiguration message.

[0156] Alternatively, when the first IAB node receives an RRC reconfiguration message including the latest first BAP configuration IE (bap-Config IE) from one of its parent nodes, the parent node and the first IAB node terminate at the same IAB donor CU for F1, and / or when the first IAB node receives an RRC reconfiguration message including the latest second BAP configuration IE from one of its parent nodes, the parent node and the first IAB node terminate at different IAB donor CUs for F1.

[0157] In an embodiment of the present invention, after the receiving unit of the BAP entity of the first IAB node DU receives a BAP data packet and passes it to the transmitting unit of the co-located BAP entity, the selection unit 1901 performs a lookup on the first BAP header rewriting table to determine whether the first BAP header rewriting table contains an entry for the routing identifier in the BAP header of the BAP data packet.

[0158] In an embodiment of the present invention, when the first IAB node is in a dual connection and a radio link failure (RLF) occurs in the link between the first IAB node and one of its parent nodes, the selection unit 1901 selects an available egress link.

[0159] In an embodiment of the present invention, the apparatus 1900 further includes the following.

[0160] A first rewriting unit 1903: when the first IAB node is in a dual connection and no radio link failure occurs in the link between the first IAB node and its parent node, perform a lookup on the first BAP header rewriting table using the routing identifier of the BAP header of the upstream BAP data packet to determine whether to perform BAP header rewriting; and / or Second Rewriting Unit 1904: When the first IAB node is in dual connection and a radio link failure occurs in the link between the first IAB node and one of its parent nodes, a lookup is performed on the second BAP header rewriting table using the routing identifier of the BAP header of the BAP data packet to determine whether to perform BAP header rewriting.

[0161] In an embodiment of the present invention, the apparatus 1900 further includes the following.

[0162] Third Rewriting Unit 1905: When the first BAP header rewriting table is set, first perform a lookup on the first BAP header rewriting table using the routing identifier in the BAP header of the BAP data packet to find the matching new routing identifier, and when the corresponding exit link is available, perform BAP header rewriting according to the first BAP header rewriting table. Also, when no matching new routing identifier is found, or when a matching new routing identifier is found but the corresponding exit link is unavailable, perform a lookup on the second BAP header table to determine whether to perform BAP header rewriting.

[0163] In an embodiment of the present invention, the apparatus 1900 further includes the following.

[0164] Fourth Rewriting Unit 1906: When the first BAP header rewriting table and the second BAP header rewriting table are set, determine whether to perform BAP header rewriting according to the second BAP header rewriting table.

[0165] In an embodiment of the present invention, the first BAP header rewriting table and the second BAP header rewriting table are set as two tables, or are set as two separate partial entries in one table.

[0166] In an embodiment of the present invention, for the realization of the functions of each of the above units, reference can be made to the realization method of the related steps in Embodiment 1, and the detailed description thereof is omitted here.

[0167] As can be seen from the above embodiments, for upstream data, the first IAB node directly selects an egress link for routing without performing a lookup in the routing table, or when a routing ambiguity occurs after performing a lookup in the routing table, it selects an egress link and performs routing without using the routing table, thereby avoiding routing ambiguity caused by BAP address conflict or routing identifier conflict.

Embodiment

[0168] In an embodiment of the present invention, a wireless routing device is provided, and the device is used for a first IAB node. The device corresponds to the method described in Embodiment 2.

[0169] FIG. 20 is a diagram showing a wireless routing device in Embodiment 6 of the present invention. As shown in FIG. 20, the device 2000 includes the following.

[0170] A second routing unit 2001: After the receiving part of the BAP entity of the first IAB node receives a BAP data packet and passes the BAP data packet to the transmitting part of the co-located BAP entity, it selects only the egress link corresponding to the node connected to the co-located BAP entity for routing.

[0171] For example, after the receiving unit of the BAP entity of the first IAB node in the second routing unit 2001 receives the BAP data packet and passes the BAP data packet to the transmitting unit of the co-located BAP entity, the next-hop BAP address corresponding to the routing identifier of the BAP header is obtained according to the lookup routing table, and when the BAP addresses of the two adjacent nodes of the first IAB node are all the same as the BAP address of the next hop, among the two adjacent nodes, the exit link corresponding to the node connected to the co-located BAP entity is selected for routing.

[0172] In this way, the problem of routing ambiguity can be solved.

Embodiment

[0173] In an embodiment of the present invention, a BAP address setting device is provided, and the device is used for an IAB donor. The device corresponds to the method described in Embodiment 3.

[0174] FIG. 21 is a diagram showing a BAP address setting device in Embodiment 7 of the present invention. As shown in FIG. 21, the device 2100 includes the following.

[0175] The first setting unit 2101: provided in the first IAB donor CU, and sets a BAP address for the DU of the first IAB node; and The second setting unit 2102: provided in the second IAB donor CU, and sets a BAP address for the MT of the first IAB node.

[0176] For example, the BAP address of the first IAB node DU is used for the first IAB donor CU of the first IAB node to manage the process of setting for the nodes of the first topology.

[0177] For example, the setting performed by the first IAB donor CU for the nodes of the first topology includes at least one of routing table setting, BHR RLC Channel setting and mapping, and UE context setting.

[0178] For example, when the second IAB node selects a cell and selects the cell of the first IAB node DU as the serving cell, the first IAB donor CU that manages the first IAB node performs cell group configuration (CellGroupConfig) for the second IAB node by means of an RRC reconfiguration message, and the BAP address (bap-Address) in the cell group configuration represents the BAP address of the parent node DU belonging to the cell group.

[0179] For example, in the scenario shown in FIG. 6, one new IAB node 5 (not shown in FIG. 6) selects IAB-DU3 as the serving cell during cell selection and accesses IAB node 3. IAB-donor-CU1 performs cell group configuration (CellGroupConfig) for IAB node 5 by means of RRCReconfiguration, and the bap-Address in CellGroupConfig represents the BAP address of the parent node DU belonging to the cell group. Alternatively, it may be said that the bap-Address in CellGroupConfig represents the BAP address saved by the parent node belonging to the cell group in its F1 terminate CU.

[0180] In this way, the problem of ambiguity when using multiple BAP addresses of the border IAB node can be solved.

Example

[0181] In an embodiment of the present invention, a BAP address setting device is provided, and the device is used for an IAB donor. The device corresponds to the method described in Embodiment 4.

[0182] FIG. 22 is a diagram showing a BAP address setting device in Embodiment 7 of the present invention. As shown in FIG. 22, the device 2200 includes a third setting unit 2201 and a fourth setting unit 2202.

[0183] After the third setting unit 2201 sets the BAP address for the BAP entity of the IAB node, it does not change the BAP address under the management of the same IAB donor CU.

[0184] When the IAB donor CU managing the IAB node changes or a new IAB donor is added, the fourth setting unit 2202 in the changed or newly added IAB donor CU re-sets the BAP address of the BAP entity of the IAB node.

[0185] In this way, it is possible to solve the problem that the BAP address cannot be changed in the existing mechanism.

Example

[0186] In an embodiment of the present invention, a network device is provided, and the network device includes the wireless routing device described in Embodiment 5.

[0187] FIG. 23 is a block diagram showing the system configuration of the network device in Embodiment 9 of the present invention. As shown in FIG. 23, the network device 2300 may include a processor 2310 and a memory 2320, and the memory 2320 is connected to the processor 2310. Among them, the memory 2320 can store various data, and can further store a program 2330 for information processing, and by executing the program 2330 under the control of the processor 2310, it can receive various information transmitted by the terminal device and transmit various information to the terminal device.

[0188] In one implementation, the function of the wireless routing device can be integrated into the processor 2310.

[0189] For example, the processor 2310 may be configured as follows, that is, for upstream data, it selects an egress link without performing a lookup in the routing table, or selects an egress link without using the routing table when a routing ambiguity occurs after performing a lookup in the routing table; and performs routing based on the selected egress link.

[0190] In another embodiment, the wireless routing device may be provided separately from the processor 2310. For example, the wireless routing device may be configured as a chip connected to the processor 2310, and the functions of the wireless routing device may be realized under the control of the processor 2310.

[0191] Also, as shown in FIG. 23, the network device 2300 may further include a transceiver 2340, an antenna line 2350, etc. Among them, the functions of these components are the same as those in the prior art, and the detailed description thereof is omitted here. Note that the network device 2300 does not necessarily include all the components shown in FIG. 23. Also, the network device 2300 may further include components not shown in FIG. 23, and for this, reference can be made to the prior art.

[0192] As can be seen from the above embodiments, the first IAB node can resolve the routing ambiguity caused by the conflict of the BAP address or the conflict of the routing identifier by directly selecting an egress link for routing without performing a lookup in the routing table for upstream data.

Embodiment

[0193] In an embodiment of the present invention, a communication system is provided, and the communication system includes the network device described in Embodiment 9.

[0194] FIG. 24 is a diagram showing a communication system according to Embodiment 10 of the present invention. As shown in FIG. 24, the communication system 2400 includes a first IAB node 2401, a child node 2402 of the first IAB node, a terminal device 2403 served by the first IAB node, a first parent IAB node 2404 and a second parent IAB node 2405 of the first IAB node, a first IAB donor 2406, and a second IAB donor 2407. The first IAB node 2401 can access the network through the first parent IAB node 2404 and the second parent IAB node 2405, that is, it can perform dual connection.

[0195] For example, the first IAB node 2401 may be the network device described in Embodiment 9, for example, the IAB node 3 in FIG. 5.

[0196] Also, the above-described apparatus and method may be implemented by software or hardware, or may be implemented by a combination of hardware and software. The present invention further relates to a computer-readable program as follows, that is, when the program is executed by a logic component, the logic component realizes the above-described apparatus or component, or realizes the various methods or steps described above in the logic component. The logic component may be, for example, an FPGA (Field Programmable Gate Array), a microprocessor, a processor used in a computer, or the like. The present invention further relates to a storage medium storing the above-described program, for example, a hard disk, a magnetic disk, an optical hard disk, a DVD, a flash memory, or the like.

[0197] Furthermore, one or more combinations of the functional blocks described in the drawings and / or one or more combinations of the functional blocks may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic component, discrete gate or transistor logic component, discrete hardware assembly, or any other suitable combination for performing the functions described herein. Also, one or more combinations of the functional blocks described in the drawings and / or one or more combinations of the functional blocks may further be configured as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors connected communicatively to a DSP, or any other configuration combination.

[0198] As described above, the preferred embodiments of the present invention have been described. However, the present invention is not limited to such embodiments, and any changes to the present invention belong to the technical scope of the present invention as long as they do not depart from the spirit of the present invention.

[0199] Also, with regard to the above-described embodiments and the like, the following supplementary notes are disclosed.

[0200] (Supplementary Note 1) (Supplementary Note 1) A wireless routing device, wherein the device is used for a first IAB node, and the device For upstream data, a selection unit that selects an egress link without performing a lookup in the routing table or selects an egress link without using the routing table when a routing ambiguity occurs after performing a lookup in the routing table; and A device including a first routing unit that performs routing based on the selected egress link.

[0201] (Supplementary Note 2) The device according to Supplementary Note 1, wherein The apparatus, wherein the selection unit selects an egress link by performing a lookup on the first BAP header rewrite table.

[0202] (Appendix 3) The apparatus according to Appendix 2, wherein the selection unit performs a lookup on the first BAP header rewrite table to determine whether the first BAP header rewrite table contains an entry of a routing identifier in the BAP header of the upstream BAP data packet.

[0203] (Appendix 4) The apparatus according to Appendix 3, when the routing identifier in the BAP header of the BAP data packet is the same as the previous routing identifier in one entry of the first BAP header rewrite table, the selection unit selects an egress link corresponding to a parent node that terminates at an IAB-donor-CU different from the first IAB node; and / or when the routing identifier in the BAP header of the BAP data packet is different from the previous routing identifiers in all entries of the first BAP header rewrite table, the selection unit selects an egress link corresponding to a parent node that terminates at an IAB-donor-CU the same as the first IAB node.

[0204] (Appendix 5) The apparatus according to Appendix 4, When the RRC reconfiguration message received by the first IAB node and including at least one of the latest defaultUL-BAP-RoutingID and defaultUL-BAP-BH-RLC-Channel is from one parent node, the F1 terminated donor of the parent node and the first IAB node DU is the same, the F1 terminated donor of another parent node of the first IAB node and the first IAB node is different, and at least one of the defaultUL-BAP-RoutingID and the defaultUL-BAP-BH-RLC-Channel is included in the first BAP configuration IE (bap-Config IE) in the RRC reconfiguration message, the apparatus.

[0205] (Appendix 6) The apparatus according to Appendix 4, wherein when having received, from one parent node of the first IAB node, an RRC reconfiguration message including the latest first BAP configuration IE (bap-Config IE), the parent node and the first IAB node are F1 terminated to the same IAB donor CU; and / or when having received, from one parent node of the first IAB node, an RRC reconfiguration message including the latest second BAP configuration IE, the parent node and the first IAB node are F1 terminated to different IAB donor CUs, the apparatus.

[0206] (Appendix 7) The apparatus according to Appendix 3, wherein after the receiving unit of the BAP entity of the first IAB node DU receives a BAP data packet and passes it to the transmitting unit of the co-located BAP entity, the selection unit performs a lookup on the first BAP header rewrite table to determine whether the first BAP header rewrite table includes an entry for the routing identifier in the BAP header of the BAP data packet, the apparatus.

[0207] (Appendix 8) The apparatus according to Appendix 1, wherein The selection of the exit link is a device in which when the first IAB node is in dual connection and a radio link failure (RLF) occurs in the link between the first IAB node and one of its parent nodes, the selection unit selects an available exit link.

[0208] (Appendix 9) The device according to Appendix 1, wherein the device further when the first IAB node is in dual connection and no radio link failure occurs in any of the links between the first IAB node and its parent nodes, performs a lookup in the first BAP header rewrite table using the routing identifier of the BAP header of the upstream BAP data packet to determine whether to perform BAP header rewriting; and / or a device including a second rewriting unit that, when the first IAB node is in dual connection and a radio link failure occurs in the link between the first IAB node and one of its parent nodes, performs a lookup in the second BAP header rewrite table using the routing identifier of the BAP header of the BAP data packet to determine whether to perform BAP header rewriting.

[0209] (Appendix 10) The device according to Appendix 1, wherein the device further When the first BAP header rewrite table is set, first performs a lookup in the first BAP header rewrite table using the routing identifier in the BAP header of the BAP data packet, finds the matched new routing identifier, and when the corresponding exit link is available, performs BAP header rewriting according to the first BAP header rewrite table, and when the matched new routing identifier is not found, or when the matched new routing identifier is found but the corresponding exit link is unavailable, performs a lookup in the second BAP header table to determine whether to perform BAP header rewriting, and includes a third rewriting unit.

[0210] (Appendix 11) The apparatus according to Appendix 1, wherein the apparatus further comprises a fourth rewriting unit configured to determine whether to perform BAP header rewriting according to the second BAP header rewriting table when the first BAP header rewriting table and the second BAP header rewriting table are set.

[0211] (Appendix 12) The apparatus according to any one of Appendices 9-11, wherein the first BAP header rewriting table and the second BAP header rewriting table are set as two tables or as two separate entries in one table.

[0212] (Appendix 13) The apparatus according to any one of Appendices 1-12, wherein the MT and DU of the first IAB node are each set with a BAP address.

[0213] (Appendix 14) The apparatus according to Appendix 13, wherein the BAP address of the first IAB node DU is used to manage the process of the first IAB donor CU of the first IAB node performing settings for the nodes of the first topology.

[0214] (Appendix 15) The apparatus according to Appendix 14, wherein the settings performed by the first IAB donor CU for the nodes of the first topology include at least one of routing table setting, BHR RLC Channel setting and mapping, and UE context setting.

[0215] (Appendix 16) The apparatus according to Appendix 13, When the second IAB node selects the cell of the first IAB node DU as the serving cell when performing cell selection, the first IAB donor CU that manages the first IAB node performs cell group configuration (CellGroupConfig) for the second IAB node by means of an RRC reconfiguration message, and the BAP address (bap-Address) in the cell group configuration represents the BAP address of the parent node DU belonging to the cell group, the apparatus.

[0216] (Appendix 17) The apparatus according to any one of Appendices 1-16, wherein the IAB-DU of the first IAB node and one parent node of the first IAB node terminate at different IAB donor CUs (IAB-donor-CUs), the apparatus.

[0217] (Appendix 18) The apparatus according to any one of Appendices 1-12, after setting a BAP address for the BAP entity of the IAB node, the BAP address is not changed under the management of the same IAB donor CU, the apparatus.

[0218] (Appendix 19) The apparatus according to Appendix 18, when the IAB donor CU that manages the IAB node changes or a new IAB donor is added, the changed or newly added IAB donor CU reconfigures the BAP address of the BAP entity of the IAB node, the apparatus.

[0219] (Appendix 20) A wireless routing apparatus, the apparatus is used for a first IAB node, and the apparatus includes a second routing unit that, after the receiving unit of the BAP entity of the first IAB node receives a BAP data packet and passes the BAP data packet to the transmitting unit of the co-located BAP entity, selects only the egress link corresponding to the node connected to the co-located BAP entity for routing, the apparatus.

[0220] (Appendix 21) The apparatus according to Appendix 20, wherein the second routing unit receives a BAP data packet at a receiving part of a BAP entity of the first IAB node, and after passing the BAP data packet to a transmitting part of a co-located BAP entity, obtains a BAP address of a next hop corresponding to a routing identifier of a BAP header by looking up a routing table, and when BAP addresses of two adjacent nodes of the first IAB node are all the same as the BAP address of the next hop, selects an exit link corresponding to a node connected to the co-located BAP entity among the two adjacent nodes to perform routing.

[0221] (Appendix 22) An apparatus for setting a BAP address, wherein the apparatus includes a first setting unit provided in a first IAB donor CU and configured to set a BAP address for a DU of a first IAB node; and a second setting unit provided in a second IAB donor CU and configured to set a BAP address for an MT of the first IAB node.

[0222] (Appendix 23) The apparatus according to Appendix 22, wherein in a process in which a first IAB donor CU performs setting for nodes of a first topology, a BAP address of the first IAB node DU is used.

[0223] (Appendix 24) The apparatus according to Appendix 23, wherein the setting performed by the first IAB donor CU for nodes of the first topology includes at least one of routing table setting, BHR LC Channel setting and mapping, and UE context setting.

[0224] (Appendix 25) The apparatus according to Appendix 22, When the second IAB node selects the cell of the first IAB node DU as the serving cell when performing cell selection, the first IAB donor CU performs cell group configuration (CellGroupConfig) for the second IAB node by means of an RRC reconfiguration message, and the BAP address (bap-Address) in the cell group configuration represents the BAP address of the parent node DU belonging to the cell group, the device.

[0225] (Appendix 26) A device for setting a BAP address, The device is After setting a BAP address for the BAP entity of the IAB node, a third setting unit that does not change the BAP address under the management of the same IAB donor CU, the device.

[0226] (Appendix 27) The device according to Appendix 26, When the IAB donor CU managing the IAB node changes or a new IAB donor increases, a fourth setting unit in the changed or newly increased IAB donor CU re-sets the BAP address of the BAP entity of the IAB node, the device.

[0227] (Appendix 28) A network device, The network device includes the device according to any one of Appendices 1-21, the network device.

[0228] (Appendix 29) A network device, The network device includes the device according to any one of Appendices 22-27, the network device.

[0229] (Appendix 30) A communication system, The communication system includes the network device according to Appendix 28 and / or the network device according to Appendix 29, and a terminal device, the communication system.

[0230] (Appendix II) (Appendix 1) A wireless routing method, which is used for a first IAB node, and the method comprises: For upstream data, selecting an egress link without performing a lookup in the routing table, or selecting an egress link without using the routing table when a routing ambiguity occurs after performing a lookup in the routing table; and Performing routing based on the selected egress link.

[0231] (Appendix 2) The method according to Appendix 1, wherein the selection of the egress link comprises selecting an egress link by performing a lookup in a first BAP header rewrite table.

[0232] (Appendix 3) The method according to Appendix 2, wherein selecting an egress link by performing a lookup in the first BAP header rewrite table comprises determining whether the first BAP header rewrite table contains an entry of a routing identifier in the BAP header of the upstream BAP data packet by performing a lookup in the first BAP header rewrite table.

[0233] (Appendix 4) The method according to Appendix 3, wherein when the routing identifier in the BAP header of the BAP data packet is the same as the previous routing identifier in an entry of the first BAP header rewrite table, selecting an egress link corresponding to a parent node that terminates at an IAB-donor-CU different from the first IAB node; and / or A method of selecting an egress link corresponding to a parent node that terminates at an IAB donor CU (IAB-donor-CU) the same as a first IAB node when a routing identifier in a BAP header of the BAP data packet is different from old routing identifiers in all entries of the first BAP header rewrite table.

[0234] (Appendix 5) The method according to Appendix 4, when an RRC reconfiguration message including at least one of the latest defaultUL-BAP-RoutingID and defaultUL-BAP-BH-RLC-Channel received by the first IAB node is from one parent node, the F1 terminating donor of the parent node and the first IAB node DU is the same, the F1 terminating donor of another parent node of the first IAB node and the first IAB node is different, and at least one of the defaultUL-BAP-RoutingID and the defaultUL-BAP-BH-RLC-Channel is included in a first BAP configuration IE (bap-Config IE) in the RRC reconfiguration message.

[0235] (Appendix 6) The method according to Appendix 4, when there has been a reception of an RRC reconfiguration message including a latest first BAP configuration IE (bap-Config IE) from one parent node of the first IAB node, the parent node and the first IAB node terminate at the same IAB donor CU; and / or when there has been a reception of an RRC reconfiguration message including a latest second BAP configuration IE from one parent node of the first IAB node, the parent node and the first IAB node terminate at different IAB donor CUs.

[0236] (Appendix 7) The method according to Appendix 3, After the receiving unit of the BAP entity of the first IAB node DU receives the BAP data packet and passes it to the transmitting unit of the co-located BAP entity, A method of determining whether the first BAP header rewrite table includes an entry for a routing identifier in the BAP header of the BAP data packet by performing a lookup on the first BAP header rewrite table.

[0237] (Appendix 8) The method according to Appendix 1, The selection of the egress link, A method including selecting an available egress link when the first IAB node is in dual connection and a radio link failure (RLF) occurs on the link between the first IAB node and one of its parent nodes.

[0238] (Appendix 9) The method according to Appendix 1, The method further includes, When the first IAB node is in dual connection and no radio link failure occurs on any of the links between the first IAB node and its parent nodes, performing a lookup on the first BAP header rewrite table using the routing identifier of the BAP header of the upstream BAP data packet to determine whether to perform BAP header rewriting; and / or When the first IAB node is in dual connection and a radio link failure occurs on the link between the first IAB node and one of its parent nodes, performing a lookup on the second BAP header rewrite table using the routing identifier of the BAP header of the BAP data packet to determine whether to perform BAP header rewriting.

[0239] (Appendix 10) The method according to Appendix 1, The method further includes, When the first BAP header rewrite table is set, first perform a lookup in the first BAP header rewrite table using the routing identifier in the BAP header of the BAP data packet, find the matched new routing identifier, and when the corresponding egress link is available, perform BAP header rewriting according to the first BAP header rewrite table. Also, when no matched new routing identifier is found, or when a matched new routing identifier is found but the corresponding egress link is unavailable, perform a lookup in the second BAP header table to determine whether to perform BAP header rewriting. A method.

[0240] (Appendix 11) The method according to Appendix 1, wherein The method further When the first BAP header rewrite table and the second BAP header rewrite table are set, determining whether to perform BAP header rewriting according to the second BAP header rewrite table. A method.

[0241] (Appendix 12) The method according to any one of Appendices 9-11, wherein The first BAP header rewrite table and the second BAP header rewrite table are set as two tables, or are set as two separate entries in one table. A method.

[0242] (Appendix 13) The method according to any one of Appendices 1-12, wherein The MT and DU of the first IAB node are each set with a BAP address. A method.

[0243] (Appendix 14) The method according to Appendix 13, wherein The BAP address of the first IAB node DU is used to manage the process in which the first IAB donor CU of the first IAB node performs settings for the nodes of the first topology. A method.

[0244] (Appendix 15) The method according to Appendix 14, wherein the configuration performed by the first IAB donor CU for the nodes of the first topology includes at least one of routing table configuration, BHR LC Channel configuration and mapping, and UE context configuration.

[0245] (Appendix 16) The method according to Appendix 13, wherein when the second IAB node selects the cell of the first IAB node DU as the serving cell when performing cell selection, the first IAB donor CU that manages the first IAB node performs cell group configuration (CellGroupConfig) for the second IAB node by an RRC reconfiguration message, and the BAP address (bap-Address) in the cell group configuration represents the BAP address of the parent node DU belonging to the cell group.

[0246] (Appendix 17) The method according to any one of Appendices 1-16, wherein the IAB-DU of the first IAB node and one parent node of the first IAB node terminate at different IAB donor CUs (IAB-donor-CU) via F1.

[0247] (Appendix 18) The method according to any one of Appendices 1-12, wherein after setting the BAP address for the BAP entity of the IAB node, the BAP address is not changed under the management of the same IAB donor CU.

[0248] (Appendix 19) The method according to Appendix 18, wherein when the IAB donor CU that manages the IAB node changes or a new IAB donor is added, the changed or newly added IAB donor CU reconfigures the BAP address of the BAP entity of the IAB node.

[0249] (Appendix 20) A wireless routing method, which is used for a first IAB node, and the method includes: After the receiving unit of the BAP entity of the first IAB node receives a BAP data packet and passes the BAP data packet to the transmitting unit of the co-located BAP entity, only select an egress link corresponding to a node connected to the co-located BAP entity to perform routing.

[0250] (Appendix 21) The method according to Appendix 20, After the receiving unit of the BAP entity of the first IAB node receives a BAP data packet and passes the BAP data packet to the transmitting unit of the co-located BAP entity, obtain the BAP address of the next hop corresponding to the routing identifier of the BAP header through a lookup routing table, and when the BAP addresses of the two adjacent nodes of the first IAB node are all the same as the BAP address of the next hop, select an egress link corresponding to the node connected to the co-located BAP entity among the two adjacent nodes to perform routing.

[0251] (Appendix 22) A method for setting a BAP address, including: The first IAB donor CU sets a BAP address for the DU of the first IAB node; and The second IAB donor CU sets a BAP address for the MT of the first IAB node.

[0252] (Appendix 23) The method according to Appendix 22, In the process of the first IAB donor CU performing settings for the nodes of the first topology, use the BAP address of the first IAB node DU.

[0253] (Appendix 24) The method according to Appendix 23, The setting performed by the first IAB donor CU for the nodes of the first topology is a method including at least one of routing table setting, BHR RLC Channel setting and mapping, and UE context setting.

[0254] (Appendix 25) The method according to Appendix 22, When the second IAB node selects the cell of the first IAB node DU as the serving cell when performing cell selection, the first IAB donor CU performs cell group setting (CellGroupConfig) for the second IAB node by an RRC reconfiguration message, and the BAP address (bap-Address) in the cell group setting represents the BAP address of the parent node DU belonging to the cell group.

[0255] (Appendix 26) A method for setting the BAP address, The method includes: After setting the BAP address for the BAP entity of the IAB node, not changing the BAP address under the management of the same IAB donor CU.

[0256] (Appendix 27) The method according to Appendix 26, When the IAB donor CU managing the IAB node changes or a new IAB donor is added, the changed or newly added IAB donor CU reconfigures the BAP address of the BAP entity of the IAB node.

Claims

1. An apparatus for wireless routing, applied to a first IAB node, comprising: a processor, wherein the processor is configured to: rewrite the BAP routing identifier in the BAP header of the BAP data packet based on a first BAP header rewriting setting for the BAP data packet; and rewrite the BAP routing identifier in the BAP header for the upstream BAP data packet based on a second BAP header rewriting setting. When the first BAP header rewriting setting is set, the processor looks up the first BAP header rewriting setting using the BAP routing identifier in the BAP header of the BAP data packet, finds a matched exit routing identifier, and when the corresponding exit link is available, performs BAP header rewriting according to the first BAP header rewriting setting. When the matched exit routing identifier is not found, or when the matched exit routing identifier is found but the corresponding exit link is unavailable, the processor looks up the second BAP header rewriting setting to determine whether to perform BAP header rewriting. An apparatus.

2. The apparatus according to claim 1, wherein the processor selects an exit link by looking up the first BAP header rewriting setting.

3. The apparatus according to claim 1, wherein the processor determines whether the first BAP header rewriting setting includes an entry of the BAP routing identifier in the BAP header of the BAP data packet by looking up the first BAP header rewriting setting.

4. The apparatus according to claim 3, wherein when the BAP routing identifier in the BAP header of the BAP data packet is the same as the entry routing identifier in one entry of the first BAP header rewriting setting, the processor rewrites the BAP header using the exit routing identifier mapped to the entry routing identifier.

5. The apparatus according to claim 1, wherein the first BAP header rewriting setting is used for inter-topology transmission.

6. The apparatus according to claim 5, When the first BAP header rewriting setting is used for upstream traffic, the egress routing identifier corresponds to the routing identifier in the second topology, and the second topology is controlled by a non-F1-terminating donor-CU, the apparatus.

7. The apparatus according to claim 3, after the receiving part of the BAP entity of the first IAB node receives the BAP data packet and passes it to the transmitting part of the co-located BAP entity, the processor determines whether the first BAP header rewriting setting includes an entry for the BAP routing identifier in the BAP header of the BAP data packet by performing a lookup on the first BAP header rewriting setting, the apparatus.

8. The apparatus according to claim 1, wherein the first BAP header rewriting setting is set by the F1-terminating donor-CU of the first IAB node, the apparatus.

9. The apparatus according to claim 1, wherein the second BAP header rewriting setting is used for inter-donor-DU re-routing, and the BAP header rewriting is to rewrite the BAP routing identifier to one donor DU to the BAP routing identifier to one alternative donor DU, the apparatus.

10. The apparatus according to claim 1, wherein the first IAB node is a boundary IAB node, the apparatus.

11. The apparatus according to claim 1, wherein the MT and DU of the first IAB node are each set with a BAP address, the apparatus.

12. The apparatus according to claim 11, wherein the BAP address of the DU of the first IAB node is used to manage a process in which the first IAB donor-CU of the first IAB node performs a setting for a node in the first topology, the apparatus.

13. The apparatus according to claim 12, wherein the setting performed by the first IAB donor-CU for a node in the first topology includes at least one of a routing table setting, a BH RLC Channel setting and mapping, and a UE context setting, the apparatus.

14. The apparatus according to claim 11, wherein when the second IAB node selects the cell of the DU of the first IAB node as the serving cell, the first IAB donor CU that manages the first IAB node performs cell group configuration (CellGroupConfig) for the second IAB node by an RRC reconfiguration message, and the BAP address (bap-Address) in the cell group configuration represents the BAP address of the parent node DU belonging to the cell group set by the cell group configuration.

15. The apparatus according to claim 1, wherein the IAB-DU of the first IAB node and one parent node of the first IAB node terminate at different IAB donor CUs (IAB-donor-CUs).

16. The apparatus according to claim 1, wherein after setting a BAP address for the BAP entity of the IAB node, the BAP address is not changed under the management of the same IAB donor CU.

17. The apparatus according to claim 16, wherein when the IAB donor CU (IAB-donor-CU) of the IAB node changes or a new IAB donor CU is added, the fourth setting unit in the changed or newly added IAB donor CU reconfigures the BAP address of the IAB node.

18. A network device applied to a first IAB node, comprising a processor, and the processor is configured to rewrite the BAP routing identifier in the BAP header of the BAP data packet based on a first BAP header rewriting setting for the BAP data packet; and rewrite the BAP routing identifier in the BAP header of the BAP data packet in the upstream direction based on a second BAP header rewriting setting. ​ When the first BAP header rewriting setting is set, the processor performs a lookup on the first BAP header rewriting setting using the BAP routing identifier in the BAP header of the BAP data packet, finds the matched egress routing identifier, and when the corresponding egress link is available, performs BAP header rewriting according to the first BAP header rewriting setting. Also, when the matched egress routing identifier is not found, or when the matched egress routing identifier is found but the corresponding egress link is unavailable, the processor performs a lookup on the second BAP header rewriting setting to determine whether to perform BAP header rewriting. A network device.

Images