Routing method, apparatus and system

Abstract

Embodiments of the present application provide a routing method, device and system, wherein the method comprises: a first node performing routing selection when at least one of the following conditions is met: a BH RLF indication is received from a second node; first flow control feedback information is received and the first flow control feedback information indicates that data congestion occurs in a third node; a load of a first egress BH RLC channel exceeds an expected level; a load corresponding to a first routing identification exceeds an expected level.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communications. BACKGROUND

[0002] Integrated access and backhaul (IAB) enables wireless relaying in the next generation radio access network (NG-RAN). This relaying node is called IAB node, which supports both access and backhaul (BH) over 5G new radio (NR). All IAB nodes are connected to an IAB-donor through one or multiple hops. These multiple-hop connections form a Directed Acyclic Graph (DAG) topology rooted at the IAB-donor. The IAB-donor is responsible for performing centralized resource management, topology management and routing management in the IAB network topology.

[0003] In the existing standard (3GPP Rel-16), when a radio link failure (RLF) occurs, an IAB node can select another path to achieve re-routing. Figure 1 A simple IAB network deployment is shown, which contains four IAB nodes and one IAB-donor. When a backhaul radio link failure (BH RLF) occurs between IAB node 2 and IAB node 3, IAB node 2 can switch the uplink routing path from path 1 to path 2.

[0004] It should be noted that the above introduction to the technical background is only for the convenience of clearly and completely describing the technical scheme of the present application, and facilitating the understanding of those skilled in the art. The above technical scheme cannot be considered as known to those skilled in the art only because it is described in the background section of the present application. SUMMARY

[0005] The inventors found that the fluctuation of data rates on different paths can cause congestion on some paths, although other available paths that can reach the same endpoint actually have capacity. In the current standard, any specified data unit is fixed to be transmitted on one path. Even though multiple paths can be selected after a BH RLF occurs, there is currently no good re-routing mechanism to improve the flexibility of routing, and to avoid congested paths, or to avoid selecting poor-performing backhaul links.

[0006] To solve at least one of the above problems or other similar problems, embodiments of the present application provide a routing method, apparatus and system to avoid data loss, reduce congestion, and achieve load balancing.

[0007] According to an aspect of embodiments of the present application, a routing method is provided, the method comprising:

[0008] The first node performs routing selection when at least one of the following conditions is met:

[0009] receiving a BH RLF indication from a second node;

[0010] receiving a first flow control feedback information, and the first flow control feedback information indicates that a third node has data congestion;

[0011] a load of a first egress BH RLC channel exceeds an expected level;

[0012] a load corresponding to a first routing identity exceeds an expected level.

[0013] According to another aspect of embodiments of the present application, a routing method is provided, the method comprising:

[0014] The first node receives a first routing configuration message, the first routing configuration message comprising configuration information corresponding to a plurality of routing identities, the configuration information corresponding to each routing identity comprising at least one of: a priority, a number of hops, and an average delay.

[0015] According to still another aspect of embodiments of the present application, a routing method is provided, the method comprising:

[0016] The IAB donor sends a first routing configuration message to the first node, the first routing configuration message being used for the first node to select a routing identity, the first routing configuration message comprising configuration information corresponding to a plurality of routing identities, the configuration information corresponding to each routing identity comprising at least one of: a priority, a number of hops, and an average delay.

[0017] According to an aspect of embodiments of the present application, a routing apparatus is provided, configured in an IAB node in an IAB network, the apparatus comprising:

[0018] The selection unit performs routing selection when at least one of the following conditions is met:

[0019] receiving a BH RLF indication from a second node;

[0020] The first flow control feedback information is received, and the first flow control feedback information indicates that data congestion occurs at the third node;

[0021] The load of the first egress BH RLC channel exceeds an expected level;

[0022] The load corresponding to the first routing identification exceeds an expected level.

[0023] According to another aspect of the embodiments of the present application, a routing device is provided, configured in an IAB node in an IAB network, the device comprising:

[0024] a receiving unit configured to receive a first routing configuration message, the first routing configuration message comprising configuration information corresponding to a plurality of routing identifications, the configuration information corresponding to each routing identification comprising at least one of a priority, a number of hops, and an average delay.

[0025] According to still another aspect of the embodiments of the present application, a routing device is provided, configured in an IAB donor in an IAB network, the device comprising:

[0026] a first sending unit configured to send a first routing configuration message to a first node, the first routing configuration message being used for the first node to select a routing identification, the first routing configuration message comprising configuration information corresponding to a plurality of routing identifications, the configuration information corresponding to each routing identification comprising at least one of a priority, a number of hops, and an average delay.

[0027] One of the beneficial effects of the embodiments of the present application is that, according to the embodiments of the present application, data loss can be avoided, congestion can be reduced, and load balancing can be achieved. Specifically, if a local routing reselection decision is made when a BH RLF notification is received, or when congestion occurs in a nearby node, or when load balancing is needed, network performance such as delay, data loss, and the like can be improved.

[0028] Specific embodiments of the application are disclosed herein, and represented in the accompanying drawings, illustrating the principles of the application in a manner that is best suited to the understanding of its principles and its practical application. It should be understood, therefore, that those skilled in the art and relating fields might employ the principles set forth herein for other applications while still being deemed to be within the principles of the application as claimed. The application is to be limited only by the spirit and scope of the appended claims, along with the full scope of equivalents to which such claims are entitled.

[0029] Features described and / or illustrated with respect to one implementation can be used in the same or similar manner in one or more other implementations, in combination with or in place of features in other implementations, or in place of other features.

[0030] It should be emphasized that the term "including / comprises" as used herein refers to the presence of a feature, whole, step, or component, but does not exclude the presence or addition of one or more other features, wholes, steps, or components. Attached Figure Description

[0031] The elements and features described in one drawing or embodiment of this application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, similar reference numerals denote corresponding parts in several drawings and can be used to indicate corresponding parts used in more than one embodiment.

[0032] The accompanying drawings, which form part of the specification, are used to provide a further understanding of the embodiments of this application and illustrate the implementation methods of this application, together with the textual description, to explain the principles of this application. Obviously, the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without creative effort. In the drawings:

[0033] Figure 1 This is a schematic diagram of IAB network deployment;

[0034] Figure 2 This is a schematic diagram illustrating an example of a routing method according to an embodiment of the first aspect of this application;

[0035] Figure 3 This is a schematic diagram illustrating an example of an IAB node performing local route reselection after receiving a BH RLF instruction.

[0036] Figure 4 This is a schematic diagram illustrating an example of how an IAB node performs route reselection after receiving flow control feedback information.

[0037] Figure 5 This is a schematic diagram illustrating an example of how IAB nodes achieve load balancing through route reselection;

[0038] Figure 6 This is a schematic diagram illustrating an example of a routing method according to an embodiment of the second aspect of this application;

[0039] Figure 7 This is a schematic diagram illustrating an example of a routing method according to an embodiment of the third aspect of this application;

[0040] Figure 8 This is a schematic diagram of an example of a routing device according to an embodiment of this application;

[0041] Figure 9 This is a schematic diagram of another example of a routing device according to an embodiment of this application;

[0042] Figure 10 is a schematic diagram of still another example of a routing device of embodiments of the application;

[0043] Figure 11 is a schematic diagram of an example of a communication system of embodiments of the application;

[0044] Figure 12 is a schematic diagram of an example of an IAB node of embodiments of the application;

[0045] Figure 13 is a schematic diagram of an example of an IAB donor of embodiments of the application. DETAILED DESCRIPTION

[0046] The foregoing and other features of the present application will become apparent to those skilled in the art upon consideration of the following description of specific embodiments of the application, taken in conjunction with the accompanying drawings. In the description of embodiments of the application, specific terminology is employed for the sake of clarity. However, the application is not intended to be limited to the specific embodiments described, but rather, is intended to include all modifications, equivalents, and alternatives that fall within the scope of the appended claims.

[0047] In embodiments of the present application, the terms “first”, “second”, and the like, are used to distinguish different elements from one another, but do not indicate spatial or chronological order or the like, and the elements should not be limited by these terms. The term “and / or” includes any one and all combinations of the associated listed terms. The terms “comprise”, “include”, “have”, and the like, mean the presence of stated features, elements, components, or assemblies, but do not preclude the presence or addition of one or more other features, elements, components, or assemblies.

[0048] In embodiments of the present application, the singular forms “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise. The term “the” should be construed to mean “at least one” or “one or more” unless the context clearly indicates otherwise. The term “based on” should be interpreted as “based, at least in part, on” unless the context clearly indicates otherwise. The term “based on” should be interpreted as “based, at least in part, on” unless the context clearly indicates otherwise.

[0049] In the embodiments of the present application, the term "communication network" or "wireless communication network" can refer to a network conforming to any communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), and the like.

[0050] In addition, the communication between devices in the communication system can be performed according to any stage communication protocol, which can include but is not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and future 5G, 6G, and the like, and / or other currently known or to be developed communication protocols.

[0051] In the embodiments of the present application, the term "network device" refers to a device that accesses a terminal device to a communication network and provides services for the terminal device in the communication system, for example. The network device can include but is not limited to the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), and the like.

[0052] Among them, the base station can include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), and the like, in addition to remote radio head (RRH), remote radio unit (RRU), relay or low-power node (such as femto, pico, etc.). In addition, the term "base station" can include some or all functions thereof, and each base station can provide communication coverage for a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0053] In the embodiments of the present application, the term "user equipment" (UE) refers to a device that accesses a communication network through a network device and receives network services, which can also be referred to as "terminal equipment" (TE). The terminal equipment can be fixed or mobile, and can also be referred to as a mobile station (MS), a terminal, a user, a subscriber station (SS), an access terminal (AT), a station, and the like.

[0054] The terminal equipment can include, but is not limited to, the following devices: a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a machine type communication device, a laptop computer, a cordless phone, a smart phone, a smart watch, a digital camera, and the like.

[0055] For another example, in an Internet of Things (IoT) scenario or the like, the terminal equipment can also be a machine or device that performs monitoring or measurement, which can include, but is not limited to, the following devices: a machine type communication (MTC) terminal, a vehicle-mounted communication terminal, a device-to-device (D2D) terminal, a machine-to-machine (M2M) terminal, and the like.

[0056] According to an aspect of the embodiments of the present application, the embodiments of the present application can be used to improve the routing selection of the BAP (backhaul adaptation protocol) sublayer. Various embodiments of the present application will be described below with reference to the accompanying drawings. These embodiments are only exemplary and do not limit the present application.

[0057] In the following description, for the convenience of description, a 5G multi-hop IAB network deployment scenario is taken as an example, in which multiple UEs are connected to an IAB donor through multi-hop IAB nodes and finally access the 5G network. The definitions of IAB nodes and IAB donors can be referred to related technologies, and the description is omitted here. In addition, it should be noted that the above scenario is only an example of the implementation scenario of the embodiments of the present application, and does not limit the embodiments of the present application.

[0058] In the embodiments of the present application, in wireless backhaul, IP layer is carried above BAP sublayer, and multi-hop routing is implemented by BAP sublayer. Routing enhancement includes BAP procedures enhanced by path redundancy, such as local routing. Local routing refers to that, in addition to coping with wireless link failure, a local (that is, an intermediate IAB node) can make a routing selection / reselection decision. Each destination BAP address can have multiple entries in a local routing table to help implement local routing selection. Therefore, local routing between IAB nodes can be implemented by some enhancement techniques, such as local routing priority, so as to achieve load balancing, reduce congestion, performance optimization, etc.

[0059] In the embodiments of the present application, the routing selection method can be referred to as local routing or local re-routing. Specifically, when an IAB node makes a routing decision for a BAP packet, it can not route according to the routing ID (that is, the original route) contained in the BAP header. The specific action of routing selection can be the selection of routing ID, the selection of entries in routing configuration, the selection of path ID, the selection of egress connection, etc.

[0060] Embodiments of the first aspect

[0061] The embodiments of the present application provide a routing selection method, which is described from the side of an IAB node in an IAB network. For the convenience of description, the IAB node is referred to as a first node. The method of the embodiments of the first aspect of the present application describes the triggering condition of routing selection.

[0062] Figure 2 is a schematic diagram of an example of the routing selection method of the embodiments of the present application, as shown in Figure 2 The method comprises:

[0063] 201: The first node performs routing selection when at least one of the following conditions one to four is met:

[0064] Condition one: a BH RLF indication is received from a second node;

[0065] Condition two: first flow control feedback information is received, and the first flow control feedback information indicates that data congestion occurs in a third node;

[0066] Condition three: the load of a first egress BH RLC channel exceeds an expected level;

[0067] Condition four: the load corresponding to a first routing identifier exceeds an expected level.

[0068] According to the method in the embodiments of the present application, data loss can be avoided, congestion can be reduced, load balancing can be achieved, and thus network performance can be improved.

[0069] In the embodiments of the present application, the route selection refers to at least one of the following: selection of a route identifier, selection of an entry in a route configuration, selection of a path identifier, and selection of an egress connection.

[0070] In the embodiments of the present application, the data congestion refers to that the available buffer size of a BH RLC channel shown in the first flow control feedback information is lower than a first threshold value, or the available buffer size for a route identifier is lower than a second threshold value.

[0071] In the embodiments of the present application, the first egress BH RLC channel can be an egress connection ID corresponding to a route identifier in a BAP header, an ingress connection ID and an ingress BH RLC channel ID from which a BAP packet comes, and an egress BH RLC channel obtained according to BH RLC channel mapping configuration.

[0072] In the embodiments of the present application, the first route identifier can be a route identifier contained in a BAP header.

[0073] In the embodiments of the present application, according to condition one, the first node performs route selection when receiving the BH RLC indication. In some embodiments, when the first node receives the BH RLF indication from the second node, the first node performs route selection until the RLF of the first node is recovered and the IAB donor reconfigures the route for the first node.

[0074] In the embodiments of the present application, the second node can be a parent node of the first node. For example, if an IAB node (the first node) receives a BH RLF indication from its parent node (the second node), the route selection of the upstream traffic is triggered until the RLF of the IAB node is recovered and the IAB donor reconfigures the route for the IAB node. The reconfiguration of the route for the IAB node can be completed by a Donor-CU (Centralized Unit) of the IAB donor, but the present application is not limited thereto, and can also be completed by other units of the IAB donor.

[0075] Figure 3 is a schematic diagram of an example of the IAB node receiving the BH RLF indication and performing local route reselection, as Figure 3As shown, IAB node 3 (second node) detects BH RLF recovery failure at its IAB-MT (mobile termination) end, it sends a BH RLF indication to its child node, i.e. IAB node 2 (first node). When IAB node 2 receives the BH RLF indication from one of its parent nodes, IAB node 3, it switches the uplink data transmission path from path 1 to path 2 until IAB node 2’s RLF recovery is completed and the IAB node 2 is re-routed by the Donor-CU of the IAB-donor.

[0076] In the above example, the BH RLF indication can be sent in the form of a BAP control PDU (protocol data unit). However, the present application is not limited thereto.

[0077] In an embodiment of the present application, according to condition two, the first node performs routing selection when congestion occurs. That is, the first node performs routing selection when it receives a flow control feedback information (referred to as first flow control feedback information) and the flow control feedback information indicates that data congestion occurs at the third node. The flow control feedback information can come from the third node or any other node.

[0078] In an embodiment of the present application, the third node can be a parent node of the first node, or a child node of the first node. Taking the third node as a child node of the first node as an example. If an IAB node (first node) receives a flow control feedback information and the flow control feedback information indicates that data congestion occurs at another IAB node (third node), the IAB node (first node) can perform local routing selection.

[0079] In an embodiment of the present application, in some embodiments, data congestion can be that the available buffer size of a BH RLC channel in the flow control feedback information is lower than a first threshold, or the available buffer size for a routing identifier is lower than a second threshold.

[0080] In some embodiments, if the available buffer size of a BH RLC channel indicated in the flow control feedback information is below a first threshold, the first node performs local rerouting, which can be: rerouting BAP packets that are originally routed to the third node, e.g., not selecting a path to the third node when routing the BAP packets; or rerouting BAP packets that are originally mapped to the BH RLC channel, e.g., not selecting a path that leads to the mapping to the BH RLC channel when routing the BAP packets.

[0081] In some embodiments, if the available buffer size for a routing identity is below a second threshold in the flow control feedback information, the first node performs local rerouting, which can be: rerouting BAP packets that are originally routed to the third node, or rerouting BAP packets that contain the routing identity in the BAP header. The routing identity can include a destination BAP address and a path identity, but the application is not limited thereto. The BAP address is also referred to as DESTINATION in the BAP header.

[0082] In the above embodiments, the first threshold and the second threshold can be configured by the IAB donor for the first node. The application is not limited thereto, and the first threshold and the second threshold can also be predefined or preconfigured.

[0083] In the above embodiments, the flow control feedback information can be triggered due to buffer load exceeding a certain specified level, or it can be a response to a flow control polling.

[0084] For example, when the buffer load of the third node exceeds a certain specified level, the third node or other nodes sends the flow control feedback information to the first node.

[0085] For another example, when the third node or other nodes receives a flow control polling from the first node, the flow control feedback information about the third node is sent to the first node.

[0086] In some embodiments, the flow control polling and the flow control feedback information are both sent by the BAP control PDU of each node.

[0087] In the embodiments of the present application, in some embodiments, the duration of the route reselection can be determined by a timer. For example, a timer for route reselection can be set, and when the first node determines that data congestion occurs according to condition two, the timer is started, and the local route reselection for the route in which data congestion occurs is started when the timer is running. After the timer expires, the local route reselection for the route in which data congestion occurs is disabled, that is, the route reselection for the original route is stopped, and the original route selection is resumed.

[0088] In the above embodiments, there can be multiple timers, each corresponding to a route in which data congestion occurs, and the multiple timers can run independently at the same time, indicating the congestion time of different routes.

[0089] In the embodiments of the present application, in some embodiments, the duration of the route reselection can be determined by the traffic control feedback information (referred to as second traffic control feedback information) indicating that the original route does not have data congestion. For example, when the first node receives the second traffic control feedback information, and the second traffic control feedback information indicates that the original route does not have data congestion, the original route selection is resumed, and the route reselection for the original route is stopped. In some embodiments, the first node can obtain the above traffic control feedback information by sending a traffic control request to the third node, but the present application is not limited thereto. In addition, if the first node receives traffic control feedback information indicating that data congestion occurs (i.e., the first traffic control feedback information), the first node continues the route reselection of the new original route, and the specific implementation process is as described above, which will not be described here.

[0090] In the embodiments of the present application, the above two ways of determining the duration of the route reselection can be implemented separately or combined, for example, when one of the above two ways of determining the duration of the route reselection is satisfied, the local route reselection of the original route is stopped.

[0091] In the embodiments of the present application, the above original route is a general term. If the traffic control feedback information (first traffic control feedback information or second traffic control feedback information) is for route identification, the original route refers to the route or path indicated by the BAP header of the BAP packet. If the traffic control feedback information (first traffic control feedback information or second traffic control feedback information) is for BH RLC channel, the original route refers to the route or path of the packet originally mapped to the BH RLC channel according to the route indicated by the BAP header of the BAP packet and the BH RLC channel mapping configuration, which includes one or more parts of the route or path data mapped to the BH RLC channel.

[0092] Figure 4is a schematic diagram of one example of the IAB node performing route reselection after receiving the traffic control feedback information. In this example, the traffic control feedback information is sent by the third node. As shown in Figure 4 When the IAB node 5 (the first node) receives the traffic control feedback information from its child node, the IAB node 3 (the third node), and the traffic control feedback information indicates that the IAB node 3 has data congestion, the IAB node 5 performs route reselection for downlink traffic, switching from path 1 to path 2.

[0093] In the embodiments of the present application, according to condition three, the first node performs route selection when there is a need for load balancing. That is, the first node performs route selection when the load of the first egress BH RLC channel exceeds a desired level.

[0094] In some embodiments, the load of the first egress BH RLC channel exceeding a desired level means that the available or desired buffer size of the first egress BH RLC channel on the first egress link is lower than a third threshold, and the available buffer size of the second egress BH RLC channel on the second egress link is higher than a fourth threshold. Here, the available buffer size being lower than the third threshold can mean that the buffer data amount is higher than a certain threshold, or the buffer occupation is higher than a certain threshold, etc. The available buffer size being higher than the fourth threshold can mean that the buffer data amount is lower than a certain threshold, or the buffer occupation is lower than a certain threshold, etc. The load exceeding the desired level can also mean that the difference between the buffer data amount corresponding to the first egress BH RLC channel and the buffer data amount corresponding to the second egress BH RLC channel is higher than a certain threshold.

[0095] In the above embodiments, in some embodiments, the identity of the second egress link is indicated by a routing identity corresponding Next-Hop BAP Address IE in the BH Routing Configuration, and the BAP address corresponding to the routing identity is the same as the DESTINATION in the BAP header of the current packet. Thus, the second egress link and the first egress link can both be routed to the same BAP address.

[0096] In the above embodiments, in some embodiments, the second egress BH RLC channel is indicated by the Egress BH RLC CH ID IE of an entry in the BH RLC Channel Mapping Configuration, the ingress BH RLC CH ID of the entry matches the ingress BH RLC channel of the current BAP packet, the ingress connection ID of the entry matches the ingress connection of the current BAP packet, and the egress connection ID of the entry corresponds to the second egress connection. Thus, the second egress BH RLC channel is the egress BH RLC channel mapped according to the configuration after the second egress connection is selected.

[0097] Figure 5 is a schematic diagram of an example of an IAB node implementing load balancing through route reselection. As shown, when the condition of the available buffer size of the IAB node 2 is met, i.e., the available or expected buffer size of the first egress BH RLC channel on the first egress connection (the egress connection corresponding to path 1) is lower than the third threshold, and the available buffer size of the second egress BH RLC channel on the second egress connection (the egress connection corresponding to path 2) is higher than the fourth threshold, the IAB node 2 re-routes the uplink traffic from path 1 to path 2. Figure 5

[0098] Figure 5 For downlink traffic, the method of the embodiments of the present application is also applicable. For example, for downlink traffic, consistent with the method for uplink, when a certain IAB node has multiple child nodes, route reselection can be performed. The egress connection and egress BH RLC channel of the IAB node are in the direction of the child nodes. The route selection is also to select a route in the direction of the child nodes.

[0099] In the above embodiments, the third threshold and the fourth threshold can be configured by the IAB donor for the first node. The present application is not limited thereto, and the third threshold and the fourth threshold can also be predefined or preconfigured.

[0100] In the embodiments of the present application, according to condition four, the first node performs route selection when there is a demand for load balancing. That is, the first node performs route selection when the load corresponding to the first route identification exceeds the expected level.

[0101] ​In some embodiments, the first routing identity corresponding to an expected load exceeding a level refers to that the available buffer size corresponding to the first routing identity is lower than a fifth threshold, and the available buffer size corresponding to another routing identity with the same BAP address as the first routing identity is higher than a sixth threshold. Here, the available buffer size being lower than the fifth threshold can refer to that the buffer data amount is higher than a certain threshold, or the buffer occupation is higher than a certain threshold, etc. The available buffer size being higher than the sixth threshold can refer to that the buffer data amount is lower than a certain threshold, or the buffer occupation is lower than a certain threshold, etc. The expected load exceeding a level can also refer to that the difference between the buffer data amount corresponding to the first routing identity and the buffer data amount corresponding to another routing identity with the same BAP address as the first routing identity is higher than a certain threshold.

[0102] Still taking Figure 5 For example, when the condition of the available buffer size of the IAB node 2 is met, that is, the available buffer size corresponding to the first routing identity (corresponding to path 1) is lower than the fifth threshold, and the available buffer size corresponding to another routing identity (corresponding to path 2) with the same BAP address as the first routing identity is higher than the sixth threshold, the IAB node 2 re-routes the uplink service from path 1 to path 2.

[0103] Similarly, Figure 5 Taking the uplink service as an example, the embodiments of the present application are not limited thereto, and the method of the embodiments of the present application is also applicable to downlink services.

[0104] In the above embodiments, the fifth threshold and the sixth threshold can be configured by the IAB donor for the first node. The present application is not limited thereto, and the fifth threshold and the sixth threshold can also be predefined or preconfigured.

[0105] According to the method of the embodiments of the present application, data loss can be avoided, congestion can be reduced, load balancing can be achieved, and network performance can be improved.

[0106] Embodiments of the second aspect

[0107] The embodiments of the present application provide a routing selection method, which is described from the side of an IAB node in an IAB network. For the convenience of description, the IAB node is referred to as a first node. The method of the embodiments of the second aspect of the present application describes a specific method of routing selection. The triggering condition of the routing selection can be the same as that of the embodiments of the first aspect, but the present application is not limited thereto. In the case of triggering routing selection by other conditions, the routing selection can also be performed by the method of the embodiments of the second aspect of the present application.

[0108] Figure 6 is a schematic diagram of one example of the routing selection method of the embodiments of the present application, as Figure 6As shown, the method comprises:

[0109] 601: A first node receives a first routing configuration message, the first routing configuration message comprising configuration messages corresponding to a plurality of routing identities, each configuration message corresponding to a routing identity comprising at least one of: a priority, a number of hops, and an average delay.

[0110] According to the method of the embodiments of the present application, by adding the optional information elements or fields described above in the first routing configuration message for each routing identity, the IAB node (the first node) can make a local decision when performing routing reselection.

[0111] In the embodiments of the present application, in some embodiments, the "priority" described above is the routing priority recommended by the CU (referred to as Donor-CU) of the IAB donor to the IAB node. For example, for a number representing the "priority", a larger number indicates that the routing has higher transmission performance in the view of the Donor-CU.

[0112] In the embodiments of the present application, in some embodiments, the "number of hops" described above represents the number of hops remaining to reach the destination address in the routing identity, i.e., how many hops are left from the first node to reach the destination address in the routing identity.

[0113] In the embodiments of the present application, in some embodiments, the "average delay" described above represents the average end-to-end delay of the path corresponding to the routing identity observed by the IAB donor (for example, the Donor-CU of the IAB donor) in a certain time window, which can be obtained by any measurement and reporting method.

[0114] In the embodiments of the present application, in some embodiments, the first routing configuration message can be provided by the IAB donor through F1AP (F1 application protocol, F1 interface application protocol) signaling. The present application is not limited thereto. For the definition and implementation method of the F1AP signaling, reference can be made to the related art, and the description is omitted here.

[0115] In some embodiments, as shown, the method further comprises: Figure 6

[0116] 602: The first node selects a routing identity according to the first routing configuration message.

[0117] In the embodiments of the present application, the first routing configuration message described above can be a BAP mapping configuration (MAPPING CONFIGURATION) message, but the present application is not limited thereto.

[0118] ​The following Table 1 gives an example of the BAP mapping configuration message. As shown in Table 1, in the BAP mapping configuration message, a "priority" field, a "hops" field and an "average delay" field are added. In some embodiments, if the "priority" field is 0 (or other specific value, referred to as a first value), it indicates that the path ID can only be used when RLF occurs. In some embodiments, if the "priority" field is other than 0, it indicates the priority of the corresponding routing identification, and thus the first node can select the routing identification according to the priority indicated by the other value when performing routing selection.

[0119] Table 1:

[0120]

[0121] Table 1 above is only an example. Other entries or items can also be included in the BAP mapping configuration message.

[0122] In the embodiments of the present application, the first node obtains a BH routing configuration according to the first routing configuration message. The principle of selecting the routing identification is to select a new routing identification with the same BAP address as the routing identification in the current BAP header in the BH routing configuration. If there are multiple routing identifications to select from, the routing identification with high priority, few hops and low average delay can be selected. The specific algorithm is not limited.

[0123] In some embodiments, if the routing selection is caused by the load of the currently selected egress BH RLC channel (the first egress BH RLC channel) exceeding the expected level, the routing identification selected by the first node also needs to satisfy the following condition:

[0124] The available buffer size of the first egress BH RLC channel on the currently selected first egress connection (i.e., the first egress connection corresponding to the routing identification specified by the current BAP header) is lower than a third threshold, and the available buffer size of the second egress BH RLC channel on the second egress connection corresponding to the selected routing identification is higher than a fourth threshold. This condition has been described in the embodiments of the first aspect, and the description is omitted here.

[0125] In the embodiments of the present application, the first egress BH RLC channel can be the egress BH RLC channel obtained from the BH RLC channel mapping configuration according to the egress connection ID corresponding to the routing identification of the BAP header, the ingress connection ID and the ingress BH RLC channel ID from which the BAP data packet comes.

[0126] In some embodiments, if the route selection is caused by the load corresponding to the current routing identity (first routing identity) exceeding the expected level, the reselected routing identity also needs to satisfy the following conditions:

[0127] The available buffer size corresponding to the current routing identity (i.e., the routing identity specified by the current BAP header) is lower than the fifth threshold, and the available buffer size corresponding to the selected routing identity is higher than the sixth threshold. The description of this condition has been made in the embodiments of the first aspect, and is omitted here.

[0128] In the embodiments of the present application, the first routing identity can be a routing identity contained in the BAP header.

[0129] It is worth noting that the above Figure 6 only illustrates the embodiments of the present application, but the present application is not limited thereto. For example, some other operations can be added, or some operations therein can be reduced. Those skilled in the art can make appropriate modifications according to the above content, and the description of the above Figure 6 is not limited thereto.

[0130] According to the method of the embodiments of the present application, the network performance can be improved.

[0131] Embodiments of the third aspect

[0132] The embodiments of the present application provide a route selection method, which is described from the side of the IAB donor in the IAB network. The same content as the embodiments of the second aspect is not repeated.

[0133] Figure 7 is a schematic diagram of an example of the route selection method of the embodiments of the present application, as Figure 7 shown, the method comprises:

[0134] 701: The IAB donor sends a first routing configuration message to the first node, the first routing configuration message being used for the first node to select a routing identity, the above-mentioned first routing configuration message comprising configuration messages corresponding to a plurality of routing identities, the configuration message corresponding to each routing identity comprising at least one of the following: priority, hops, and average delay.

[0135] In the embodiments of the present application, the first node is an IAB node in the IAB network, for example, the IAB node in the embodiments of the first aspect, or the IAB node in the embodiments of the second aspect. According to the method of the embodiments of the present application, since the Donor-CU usually has more information of the entire topology network, it has higher authority for the IAB node, and by sending the routing configuration message to the IAB node through the IAB donor, it can help the IAB node (the first node) make a local decision when performing route selection.

[0136] In the above embodiments, the meanings of "priority", "hop count" and "average delay" are the same as those in the embodiments of the second aspect, and will not be repeated here. For example, the information of "priority" can be used to indicate whether local routing is allowed. For example, if the value of the above-mentioned priority is a first value, for example, 0, then the routing identifier corresponding to the priority is only used in the case of BH RLF; if the value of the above-mentioned priority is a value other than the first value, then the value of the priority can be used to indicate the priority of the corresponding routing identifier, so that the first node can select the routing identifier according to the priority indicated by the other value.

[0137] Thus, the Donor-CU can implement more fine-grained local routing control, for example, disable the local selection of certain routing identifiers, thereby improving the flexibility of route management.

[0138] In some embodiments, as shown in the method further includes: Figure 7

[0139] 702: The IAB donor sends a second routing configuration message to the first node, the second routing configuration message being used to enable or disable the above-mentioned route selection.

[0140] In the above embodiments, the second routing configuration message can be 1-bit information. Thus, the enablement or disablement of route selection can be realized by 1-bit information, thereby improving the flexibility of route management.

[0141] In the embodiments of the present application, the first routing configuration information can further include hop count and / or average delay, which can be implemented through a BAP mapping configuration message. The related content of the hop count and average delay and the content of the BAP mapping configuration message have been described in the embodiments of the second aspect, and the content is incorporated herein, and will not be repeated here.

[0142] According to the method of the embodiments of the present application, the flexibility of route management can be improved.

[0143] Embodiments of the fourth aspect

[0144] ​Embodiments of the present application provide a routing device, which can be an IAB node in an IAB network, or one or more components or assemblies configured in the IAB node. For the convenience of description, the IAB node is referred to as a first node.

[0145] Figure 8 FIG. 1 is a schematic diagram of an example of the routing device according to an embodiment of the present application. Since the principle of solving the problem of the device is similar to the method of the embodiments of the first aspect, the specific implementation thereof can refer to the implementation of the method of the embodiments of the first aspect, and the same content will not be described repeatedly. As shown in FIG. 1, the routing device 800 according to an embodiment of the present application comprises: Figure 8

[0146] a selection unit 801, which performs routing when at least one of the following conditions is met:

[0147] the first node receives a BH RLF indication from a second node;

[0148] the first node receives first flow control feedback information, and the first flow control feedback information indicates that a third node has data congestion;

[0149] the load of a first egress BH RLC channel exceeds an expected level;

[0150] the load corresponding to a first route identifier exceeds an expected level.

[0151] In embodiments of the present application, the second node described above can be a parent node of the first node described above, and the third node described above can be a child node of the first node described above, but the present application is not limited thereto.

[0152] In some embodiments, the selection unit 801 performs routing when the first node receives a BH RLF indication from a second node, until the RLF recovery of the first node is completed and the IAB donor performs routing reconfiguration on the first node.

[0153] In some embodiments, the selection unit 801 performs routing when the first node receives first flow control feedback information, and the first flow control feedback information indicates that the third node has data congestion, including:

[0154] If the available buffer size of one BH RLC channel or the available buffer size for a route identifier in the first flow control feedback information is lower than a first threshold value or a second threshold value, respectively, the selection unit 801 re-routes a BAP packet originally routed to the third node.

[0155] ​In some embodiments, the selecting unit 801 performs route selection when the first node receives the first flow control feedback information, and the first flow control feedback information indicates that data congestion occurs at the third node, comprising:

[0156] If the available buffer size of a BH RLC channel is lower than a first threshold value in the first flow control feedback information, the selecting unit 801 reselects the BAP packet originally mapped to the BH RLC channel;

[0157] If the available buffer size for a routing identifier is lower than a second threshold value in the first flow control feedback information, the selecting unit 801 reselects the BAP packet containing the routing identifier in the BAP header.

[0158] In some embodiments, the selecting unit 801 stops the route reselection for the original route if at least one of the following conditions is met:

[0159] The timer started when the data congestion occurs is timed out;

[0160] The second flow control feedback information is received, and the second flow control feedback information indicates that data congestion does not occur at the original route.

[0161] In some embodiments, if the first flow control feedback information is for a routing identifier, the original route refers to the route or path where the data congestion occurs; if the first flow control feedback information is for a BH RLC channel, the original route refers to the route or path of the packet originally mapped to the BH RLC channel where the data congestion occurs.

[0162] In some embodiments, the route or path of the packet of the BH RLC channel where the data congestion occurs includes one or more routing or path data mapped to the BH RLC channel.

[0163] In some embodiments, the load of the first egress BH RLC channel exceeding the expected level refers to that the available buffer size of the first egress BH RLC channel on the first egress connection is lower than a third threshold value, and the available buffer size of the second egress BH RLC channel on the second egress connection is higher than a fourth threshold value.

[0164] In some embodiments, the identifier of the second egress connection is indicated by a routing identifier corresponding next hop BAP address IE in the BH routing configuration, and the BAP address corresponding to the routing identifier and the DESTINATION on the BAP header of the current packet are the same.

[0165] In some embodiments, the second egress BH RLC channel is indicated by an egress BH RLC channel identity IE of an entry of the BH RLC channel mapping configuration, an ingress BH RLC channel identity of the entry matches an ingress BH RLC channel of the current BAP packet, an ingress connection identity of the entry matches an ingress connection of the current BAP packet, and an egress connection identity of the entry corresponds to the second egress connection.

[0166] In some embodiments, the third threshold and the fourth threshold are configured by an IAB donor for the first node.

[0167] In some embodiments, the first routing identity corresponding available buffer size exceeding an expected level means that the first routing identity corresponding available buffer size is lower than a fifth threshold, and another routing identity with a same BAP address as the first routing identity corresponding available buffer size is higher than a sixth threshold.

[0168] In some embodiments, the fifth threshold and the sixth threshold are configured by an IAB donor for the first node.

[0169] Figure 9 is a schematic diagram of another example of the routing device of the embodiments of the present application. Since the device solves the problem by the principle similar to the method of the embodiments of the second aspect, the specific implementation thereof can refer to the implementation of the method of the embodiments of the second aspect, and the same content will not be described repeatedly. As shown in Figure 9 The routing device 900 of the embodiments of the present application comprises:

[0170] A receiving unit 901 receives a first routing configuration message, the first routing configuration message comprising configuration information corresponding to a plurality of routing identities, the configuration information corresponding to each routing identity comprising at least one of the following: priority, hops, and average delay.

[0171] In some embodiments, as shown in Figure 9 The device 900 further comprises:

[0172] A selecting unit 902 selects a routing identity according to the first routing configuration message.

[0173] In some embodiments, the first routing configuration message is provided by an IAB donor through F1AP signaling.

[0174] In some embodiments, the priority is a priority of a route recommended by the IAB-donor for the first node; the hop count indicates a number of hops remaining to reach a destination address in the route identity; and the average delay is an average end-to-end delay observed by the IAB-donor for a path corresponding to the route identity over a time window.

[0175] In some embodiments, if the value of the priority is a first value, the route identity corresponding to the priority is only used in case of BH RLF; and if the value of the priority is other than the first value, the value of the priority indicates a priority of the corresponding route identity, and the first node performs route selection according to the priority indicated by the other value.

[0176] In some embodiments, if the route selection is caused by the load of the first egress BH RLC channel exceeding a desired level, the selected route identity further satisfies the following condition:

[0177] The available buffer size of the first egress BH RLC channel on the first egress connection is lower than a third threshold, and the available buffer size of the second egress BH RLC channel on the second egress connection corresponding to the selected route identity is higher than a fourth threshold.

[0178] In some embodiments, if the route selection is caused by the load of the first route identity exceeding a desired level, the selected route identity further satisfies the following condition:

[0179] The available buffer size corresponding to the first route identity is lower than a fifth threshold, and the available buffer size corresponding to the selected route identity is higher than a sixth threshold.

[0180] In the embodiments of the present application, the first egress BH RLC channel can be an egress connection ID corresponding to the route identity in the BAP header, an ingress connection ID and an ingress BH RLC channel ID from which the BAP packet comes, and an egress BH RLC channel obtained by the BH RLC channel mapping configuration.

[0181] In the embodiments of the present application, the first route identity can be a route identity contained in the BAP header.

[0182] It should be noted that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The route selection apparatus 800 / 900 of the embodiments of the present application can further include other components or modules, and the specific content of these components or modules can be referred to the related art.

[0183] In addition, for the sake of simplicity, Figure 8 and Figure 9The connection relationship or signal direction between each component or module is only exemplarily shown, but it should be understood by those skilled in the art that various related technologies such as bus connection can be adopted. Each component or module can be implemented by hardware facilities such as a processor, a memory, a transmitter, a receiver, etc., and the implementation of the present application is not limited thereto.

[0184] According to the embodiments of the present application, the network performance can be improved.

[0185] Embodiments of the fifth aspect

[0186] The embodiments of the present application provide a routing device, which can be an IAB donor in an IAB network, or can be one or more components or assemblies configured in the IAB donor.

[0187] Figure 10 is a schematic diagram of an example of the routing device according to the embodiments of the present application, as shown in Figure 10 The routing device 1000 according to the embodiments of the present application includes:

[0188] A first sending unit 1001 sends a first routing configuration message to a first node, the first routing configuration message being used for the first node to select a routing identifier, the first routing configuration message including configuration messages corresponding to a plurality of routing identifiers, and the configuration message corresponding to each routing identifier including at least one of a priority, a hop number, and an average delay.

[0189] In some embodiments, as shown in Figure 10 The device 1000 further includes:

[0190] A second sending unit sends a second routing configuration message to the first node, the second routing configuration message being used for enabling or disabling the routing.

[0191] In the above embodiments, the second routing configuration message is one-bit information.

[0192] In some embodiments, the priority is a priority of a route recommended by an IAB donor for the first node; the hop number indicates a remaining hop number to a destination address in the routing identifier; and the average delay is an average end-to-end delay of a path corresponding to the routing identifier observed by the IAB donor in a time window.

[0193] In some embodiments, if the value of the priority is a first value, the routing identity corresponding to the priority is only used in the case of BH RLF; if the value of the priority is a value other than the first value, the value of the priority indicates the priority of the corresponding routing identity, and the first node performs routing according to the priority indicated by the value.

[0194] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The routing selection apparatus 1000 of the embodiments of the present application can also include other components or modules, and the specific content of these components or modules can be referred to related technologies.

[0195] In addition, for the sake of simplicity, Figure 10 The connection relationship or signal path between the various components or modules is only exemplarily shown in the above, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The various components or modules described above can be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc.; the present application is not limited thereto.

[0196] According to the embodiments of the present application, the flexibility of routing management can be improved.

[0197] Embodiments of the sixth aspect

[0198] The embodiments of the present application provide a communication system.

[0199] Figure 11 is a schematic diagram of an example of the communication system according to the embodiments of the present application. As shown in Figure 11 The communication system 1100 according to the embodiments of the present application includes an IAB node 1101 and an IAB donor 1102. For the sake of simplicity, Figure 11 only four IAB nodes 1101 and one IAB donor 1102 are exemplarily described, but the embodiments of the present application are not limited thereto. For example, the communication system 1100 can also include terminal devices (not shown in the figure). The network architecture of the terminal devices, the IAB nodes 1101 and the IAB donor 1102 can be referred to related technologies, and the description is omitted here.

[0200] In the embodiments of the present application, the existing services or future implementable services can be transmitted between the IAB nodes 1101 and the terminal devices. For example, these services can include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), high reliability and low latency communication (URLLC) and vehicle-to-everything (V2X) communication, etc.

[0201] In some embodiments, the IAB node 1101 is configured to perform the method described in embodiments of the first aspect or the second aspect. In some embodiments, the IAB donor 1102 is configured to perform the method described in embodiments of the third aspect. For related content of the IAB node 1101 and the IAB donor 1102, please refer to the embodiments of the first aspect to the third aspect, which are omitted here.

[0202] Embodiments of the present application further provide an IAB node.

[0203] Figure 12 is a schematic diagram of an example of the IAB node according to an embodiment of the present application. As shown in the figure, the IAB node 1200 can include a processor 1201 and a memory 1202; the memory 1202 stores data and programs and is coupled to the processor 1201. It is worth noting that this figure is exemplary; other types of structures can also be used to supplement or replace this structure to achieve telecommunication functions or other functions. Figure 12 For example, the processor 1201 can be configured to execute programs to implement the method described in embodiments of the first aspect or the second aspect.

[0204] As shown in the figure, the IAB node 1200 can further include a communication module 1203, an input unit 1204, a display 1205, and a power supply 1206. Among them, the functions of the above-mentioned components are similar to those of the prior art, which will not be repeated here. It is worth noting that the IAB node 1200 does not necessarily include all the components shown in the figure, and the above-mentioned components are not essential; in addition, the IAB node 1200 can also include components not shown in the figure, which can be referred to the prior art.

[0205] Figure 12 For example, the processor 1301 can be configured to execute programs to implement the method described in embodiments of the third aspect. Figure 12 Figure 12 As shown in the figure, the IAB node 1200 can further include a communication module 1203, an input unit 1204, a display 1205, and a power supply 1206. Among them, the functions of the above-mentioned components are similar to those of the prior art, which will not be repeated here. It is worth noting that the IAB node 1200 does not necessarily include all the components shown in the figure, and the above-mentioned components are not essential; in addition, the IAB node 1200 can also include components not shown in the figure, which can be referred to the prior art.

[0206] Embodiments of the present application further provide an IAB donor.

[0207] Figure 13 is a schematic diagram of an example of the IAB node according to an embodiment of the present application. As shown in the figure, the IAB node 1200 can include a processor 1201 and a memory 1202; the memory 1202 stores data and programs and is coupled to the processor 1201. It is worth noting that this figure is exemplary; other types of structures can also be used to supplement or replace this structure to achieve telecommunication functions or other functions. Figure 13 For example, the processor 1301 can be configured to execute programs to implement the method described in embodiments of the third aspect.

[0208] As shown in the figure, the IAB node 1200 can further include a communication module 1203, an input unit 1204, a display 1205, and a power supply 1206. Among them, the functions of the above-mentioned components are similar to those of the prior art, which will not be repeated here. It is worth noting that the IAB node 1200 does not necessarily include all the components shown in the figure, and the above-mentioned components are not essential; in addition, the IAB node 1200 can also include components not shown in the figure, which can be referred to the prior art.

[0209] Figure 13 ​​​As shown, the IAB donor 1300 can further include a communication module 1303, an input unit 1304, a display 1305, a power supply 1306. Among them, the functions of the above-mentioned components are similar to those of the prior art, which will not be repeated here. It is worth noting that the IAB donor 1300 also does not necessarily include Figure 13 all the components shown in the prior art; in addition, the IAB donor 1300 can also include Figure 13 components not shown in the prior art.

[0210] The embodiments of the present application also provide a computer readable program, wherein when the program is executed in the IAB node, the program causes the computer to execute the method described in the embodiments of the first aspect or the second aspect in the IAB node.

[0211] The embodiments of the present application also provide a storage medium storing a computer readable program, wherein the computer readable program causes the computer to execute the method described in the embodiments of the first aspect or the second aspect in the IAB node.

[0212] The embodiments of the present application also provide a computer readable program, wherein when the program is executed in the IAB donor, the program causes the computer to execute the method described in the embodiments of the third aspect in the IAB donor.

[0213] The embodiments of the present application also provide a storage medium storing a computer readable program, wherein the computer readable program causes the computer to execute the method described in the embodiments of the third aspect in the IAB donor.

[0214] The above devices and methods of the present application can be realized by hardware, or by a combination of hardware and software. The present application relates to a computer readable program, which, when executed by a logic component, can enable the logic component to realize the above-mentioned devices or components, or to realize the above-mentioned various methods or steps. The logic component is, for example, a field programmable logic component, a microprocessor, a processor used in a computer, etc. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0215] The methods / apparatuses described in conjunction with the embodiments of the present application can be directly embodied as hardware, software modules executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figures and / or a combination of one or more of the functional block diagrams can correspond to each software module of the computer program flow, or to each hardware module. These software modules can correspond to each step shown in the figures, respectively. These hardware modules can be realized by, for example, fixing the software modules with a field programmable gate array (FPGA).

[0216] The software modules can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. The storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can reside in an ASIC. The software modules can be stored in a memory of the mobile terminal, or in a memory card that can be inserted into the mobile terminal. For example, if the device is a mobile terminal, the software modules can be stored in a MEGA-SIM card or a flash memory device that is larger than the memory of the mobile terminal.

[0217] One or more of the functional blocks described in the figures and / or one or more combinations of the functional blocks can 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 device, discrete gate or transistor logic, discrete hardware components, or any appropriate combination of the foregoing, performing the functions described herein. One or more of the functional blocks described in the figures and / or one or more combinations of the functional blocks can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0218] The application has been described in relation to particular embodiments, but those skilled in the art will appreciate that the description is illustrative only and is not intended to limit the scope of the application. Various modifications and changes can be made to the application by those skilled in the art which fall within the scope of the application as defined by the appended claims.

[0219] In relation to the above-described embodiments disclosed in the present embodiment, the following supplementary notes are also disclosed:

[0220] 1. A routing method, wherein the method comprises:

[0221] The first node performs routing when at least one of the following conditions is met:

[0222] receiving a BH RLF indication from the second node;

[0223] receiving a first flow control feedback information and the first flow control feedback information indicates that data congestion occurs at the third node;

[0224] a load of a first egress BH RLC channel exceeds a desired level;

[0225] a load corresponding to a first routing identification exceeds a desired level.

[0226] 1a. The method of the dependent clause 1, wherein the route selection refers to at least one of: selection of a routing identification, selection of an entry in a routing configuration, selection of a path identification, selection of an egress connection.

[0227] 1b. The method of the dependent clause 1, wherein the data congestion refers to: an available buffer size of a BH RLC channel in the first flow control feedback information is below a first threshold, or an available buffer size for a routing identification is below a second threshold.

[0228] 1c. The method of the dependent clause 1, wherein the first egress BH RLC channel is an egress connection ID corresponding to a routing identification in a BAP header, an ingress connection ID and an ingress BH RLC channel ID where the BAP packet comes from, an egress BH RLC channel obtained from a BH RLC channel mapping configuration.

[0229] 1d. The method of the dependent clause 1, wherein the first routing identification is a routing identification contained in a BAP header.

[0230] 2. The method of the dependent clause 1, wherein the load of the first egress BH RLC channel exceeds a desired level refers to:

[0231] an available buffer size of the first egress BH RLC channel on a first egress connection is below a third threshold, and an available buffer size of a second egress BH RLC channel on a second egress connection is above a fourth threshold.

[0232] 3. The method of the dependent clause 1, wherein the load corresponding to a first routing identification exceeds a desired level refers to:

[0233] an available buffer size corresponding to the first routing identification is below a fifth threshold, and an available buffer size corresponding to another routing identification having a same BAP address as the first routing identification is above a sixth threshold.

[0234] 4. The method of the dependent clause 1, wherein the first node performs route selection upon receiving a BH RLF indication from a second node until RLF recovery of the first node is completed and a routing reconfiguration of the first node by an IAB donor.

[0235] 5. The method of the dependent item 1, wherein the first node, upon receiving the first flow control feedback information and the first flow control feedback information indicating that the data congestion occurs at the third node, performs the route selection, comprising:

[0236] if the first flow control feedback information indicates that the available buffer size of a BH RLC channel is below a first threshold or the available buffer size for a route identification is below a second threshold, the first node re-routes the BAP packet originally routed to the third node.

[0237] 6. The method of the dependent item 1, wherein the first node, upon receiving the first flow control feedback information and the first flow control feedback information indicating that the data congestion occurs at the third node, performs the route selection, comprising:

[0238] if the first flow control feedback information indicates that the available buffer size of a BH RLC channel is below a first threshold, the first node re-routes the BAP packet originally mapped to the BH RLC channel;

[0239] if the first flow control feedback information indicates that the available buffer size for a route identification is below a second threshold, the first node re-routes the BAP packet containing the route identification in the BAP header.

[0240] 7. The method of the dependent item 1, wherein, after the first node, upon receiving the first flow control feedback information and the first flow control feedback information indicating that the data congestion occurs at the third node, performs the route reselection, the method further comprises:

[0241] if at least one of the following conditions is met, the route reselection for the original route is stopped:

[0242] a timer started upon the occurrence of the data congestion expires;

[0243] a second flow control feedback information is received, the second flow control feedback information indicating that the data congestion does not occur at the original route.

[0244] 8. The method of the dependent item 7, wherein,

[0245] if the first flow control feedback information is for a route identification, the original route refers to the route or path at which the data congestion occurs;

[0246] if the first flow control feedback information is for a BH RLC channel, the original route refers to the route or path of the BAP packet originally mapped to the BH RLC channel at which the data congestion occurs.

[0247] 9. The method of clause 8, wherein the route or path of the data packets of the BH RLC channel for which the data congestion occurs comprises a portion of one or more route or path data mapped to the BH RLC channel.

[0248] 10. The method of clause 2, wherein the identity of the second egress connection is indicated by a routing identity corresponding next hop BAP address IE in the BH routing configuration, and the routing identity corresponding BAP address and the DESTINATION on the BAP header of the current data packet are the same.

[0249] 11. The method of clause 2, wherein the second egress BH RLC channel is indicated by an egress BH RLC channel identity IE of an entry in the BH RLC channel mapping configuration, the ingress BH RLC channel identity of the entry matches the ingress BH RLC channel of the current BAP data packet, the ingress connection identity of the entry matches the ingress connection of the current BAP data packet, and the egress connection identity of the entry corresponds to the second egress connection.

[0250] 12. The method of clause 2, wherein the third threshold and the fourth threshold are configured by an IAB donor for the first node.

[0251] 13. The method of clause 3, wherein the fifth threshold and the sixth threshold are configured by an IAB donor for the first node.

[0252] 14. A routing method, wherein the method comprises:

[0253] receiving, by a first node, a first routing configuration message comprising configuration information corresponding to a plurality of routing identities, the configuration information corresponding to each routing identity comprising at least one of: a priority, a number of hops, and an average delay.

[0254] 15. The method of clause 14, wherein the method further comprises:

[0255] selecting, by the first node, a routing identity based on the first routing configuration message.

[0256] 15a. The method of clause 15, wherein the method further comprises:

[0257] if the routing selection is caused by a load of a first egress BH RLC channel exceeding a desired level, the selected routing identity satisfies the following condition:

[0258] the available buffer size of the first BH RLC channel on the first egress connection is below a third threshold and the selected routing identity corresponds to an available buffer size of the second BH RLC channel on the second egress connection that is above a fourth threshold.

[0259] 15b. The method of clause 15, wherein the method further comprises:

[0260] if the routing selection is caused by the first routing identity corresponding to a load exceeding a desired level, the selected routing identity satisfies the following condition:

[0261] the available buffer size corresponding to the first routing identity is below a fifth threshold and the available buffer size corresponding to the selected routing identity is above a sixth threshold.

[0262] 16. The method of clause 14, wherein the first routing configuration message is provided by the IAB donor through FlAP signaling.

[0263] 17. The method of clause 14, wherein,

[0264] the priority is a priority of a route recommended by the IAB donor to the first node;

[0265] the hop count indicates a number of hops remaining to reach a destination address in the routing identity;

[0266] the average delay is an average end-to-end delay observed by the IAB donor for a path corresponding to the routing identity over a time window.

[0267] 18. The method of clause 14 or 17, wherein,

[0268] if the value of the priority is a first value, the routing identity corresponding to the priority is only used in case of a BH RLF;

[0269] if the value of the priority is other than the first value, the value of the priority indicates a priority of the corresponding routing identity, and the first node performs routing selection according to the priority indicated by the other value.

[0270] 19. A method of routing selection, wherein the method comprises:

[0271] The IAB donor sends a first routing configuration message to the first node, the first routing configuration message being used for the first node to select a routing identity, the first routing configuration message comprising configuration messages corresponding to a plurality of routing identities, the configuration message corresponding to each routing identity comprising at least one of: a priority, a number of hops, and an average delay.

[0272] 20. The method of clause 19, wherein the method further comprises:

[0273] The IAB donor sends a second routing configuration message to the first node, the second routing configuration message being used to enable or disable the routing selection.

[0274] 21. The method of clause 20, wherein the second routing configuration message is a 1-bit information.

[0275] 22. The method of clause 19, wherein,

[0276] The priority is a priority of a route recommended by the IAB donor to the first node;

[0277] The number of hops indicates a number of hops remaining to reach a destination address in the routing identity;

[0278] The average delay is an average end-to-end delay observed by the IAB donor for a path corresponding to the routing identity in a time window.

[0279] 23. The method of clause 19 or 22, wherein,

[0280] If the priority has a first value, the routing identity corresponding to the priority is only used in case of a BH RLF;

[0281] If the priority has a value other than the first value, the value of the priority indicates a priority of the corresponding routing identity, and the first node selects the routing according to the priority indicated by the value.

[0282] 24. An IAB node in an IAB network, comprising a memory and a processor, the memory storing a computer program, wherein the processor is configured to execute the computer program to implement the method of any one of clauses 1 to 18.

[0283] 25. An IAB donor in an IAB network, comprising a memory and a processor, the memory storing a computer program, wherein the processor is configured to execute the computer program to implement the method of any one of clauses 19 to 23.

[0284] 26. A communication system including an IAB node and an IAB donor, wherein the IAB node is configured to perform the method of any of appendices 1 to 18 and the IAB donor is configured to perform the method of any of appendices 19 to 23.

Claims

1. A routing device configured at a first node, wherein, The apparatus comprises: a receiver configured to receive first flow control feedback information from a third node; a processor configured to perform local rerouting when the following conditions are met: the receiver receives the first flow control feedback information from the third node, and the first flow control feedback information indicates that data congestion occurs at the third node, wherein, if the available buffer size of one BH RLC channel is lower than a first threshold configured by an IAB-donor for the first node, the processor reroutes BAP packets originally mapped to the BH RLC channel, or, if the available buffer size for a routing identification is lower than a second threshold configured by an IAB-donor for the first node, the processor reroutes BAP packets containing the routing identification in a BAP header.

2. The apparatus of claim 1, wherein, The local rerouting comprises: routing reselection or selecting a different route from the routing identification in the BAP header.

3. The apparatus of claim 1, wherein, After the processor performs routing reselection upon receiving the first flow control feedback information, the processor stops routing reselection for the original route if at least one of the following conditions is met: a timer started when the data congestion occurs is expired; a second flow control feedback information is received, the second flow control feedback information indicates that data congestion does not occur at the original route.

Images