COMMUNICATION CONTROL METHOD, RELAY NODE, AND PROCESSOR

The communication control method in cellular systems enables local rerouting and centralized management of relay nodes to address data transmission challenges in relay nodes, enhancing network robustness and reducing service interruptions.

JP7592143B2Active Publication Date: 2024-11-29KYOCERA CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2023202792
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2021-01-04
Filing Date
2023-11-30
Publication Date
2024-11-29
Estimated Expiration
2041-12-22

AI Technical Summary

Technical Problem

Existing cellular communication systems face challenges in managing data packet transmission and flow control in relay nodes, particularly in scenarios where backhaul link failures occur, leading to congestion and service interruptions.

Method used

The implementation of a communication control method in cellular communication systems that includes relay nodes capable of performing local rerouting of data packets to alternative paths based on flow control feedback messages and failure occurrence notifications, with centralized management by the IAB donor to optimize routing decisions.

Benefits of technology

This approach enhances network robustness by reducing service interruptions and latency during backhaul link failures, improving load balancing, and maintaining efficient data transmission across dynamic radio conditions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007592143000001
    Figure 0007592143000001
  • Figure 0007592143000002
    Figure 0007592143000002
  • Figure 0007592143000003
    Figure 0007592143000003
Patent Text Reader

Abstract

To provide a communication control method in which one or a plurality of relay nodes called IAB (Integrated Access and Backhaul) nodes intervene in communication between a base station and user equipment and relay this communication.SOLUTION: Disclosed is a communication control method used in a cellular communication system, which includes the steps of: receiving, by a relay node interposed between a parent node and a child node, a flow control feedback message from the parent node or the child node; and performing local rerouting to forward a data packet to an alternate path different from a path to the parent node or child node which has transmitted the flow control feedback message in response to a certain period of time elapsed after the relay node has received the flow control feedback message.SELECTED DRAWING: Figure 11
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a communication control method, a relay node, and a processor for use in a cellular communication system. [Background technology]

[0002] In the cellular communication system standardization project 3GPP (Third Generation Partnership Project) (registered trademark, hereinafter the same), the introduction of a new relay node called an IAB (Integrated Access and Backhaul) node is being considered (see, for example, "3GPP TS 38.300 V16.3.0 (2020-09)"). One or more relay nodes are involved in communication between a base station and a user device, and relay this communication. Summary of the Invention

[0003] A communication control method according to a first aspect is a communication control method used in a cellular communication system. The communication control method includes a relay node between a parent node and a child node receiving a flow control feedback message from the parent node or the child node. The communication control method also includes the relay node performing local rerouting to forward a data packet to an alternative path different from a path to the parent node or the child node that transmitted the flow control feedback message in response to a lapse of a certain period of time after receiving the flow control feedback message.

[0004] A communication control method according to a second aspect is a communication control method used in a cellular communication system. The communication control method includes a relay node between a parent node and a child node attempting to forward a data packet to the parent node or the child node. The communication control method also includes, when the relay node is unable to forward the data packet for a certain period of time, performing local rerouting to forward the data packet to an alternative path different from the path to the parent node or the child node.

[0005] A communication control method according to a third aspect is a communication control method used in a cellular communication system. The communication control method includes a relay node performing local rerouting to forward a data packet to an alternative path different from a path to the other relay node in response to at least one of the following execution conditions being satisfied: receiving a flow control feedback control message, receiving a notification of a failure occurrence between a backhaul link between the relay node and the other relay node, and being unable to forward a data packet for a certain period of time. The communication control method also includes the relay node stopping the local rerouting in response to a stop condition being satisfied after performing the local rerouting.

[0006] A communication control method according to a fourth aspect is a communication control method for use in a cellular communication system, the communication control method including a donor base station having a first relay node subordinate thereto transmitting a first message related to local rerouting to the first relay node, and the first relay node performing an operation related to local rerouting in response to receiving the first message. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a cellular communication system according to an embodiment. [Diagram 2]FIG. 2 is a diagram showing the relationship between IAB nodes, parent nodes, and child nodes. [Diagram 3] FIG. 3 is a diagram illustrating an example configuration of a gNB (base station) according to one embodiment. [Figure 4] FIG. 4 is a diagram illustrating a configuration example of an IAB node (relay node) according to an embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an example of a configuration of a UE (user equipment) according to an embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of a protocol stack related to an RRC connection and a NAS connection of an IAB-MT. [Figure 7] FIG. 7 is a diagram illustrating an example of a protocol stack for the F1-U protocol. [Figure 8] FIG. 8 is a diagram illustrating an example of a protocol stack for the F1-C protocol. [Figure 9] FIG. 9 is a diagram illustrating an example of local rerouting in the first embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of local rerouting in the first embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of the operation of the first embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of local rerouting in the second embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of local rerouting in the second embodiment. [Figure 14] FIG. 14 is a diagram illustrating an example of operation in the second embodiment. [Figure 15] FIG. 15 is a diagram illustrating an example of local rerouting in the third embodiment. [Figure 16] FIG. 16 is a diagram illustrating an example of local rerouting in the third embodiment. [Figure 17] FIG. 17 is a diagram illustrating an example of operation in the third embodiment. [Figure 18]FIG. 18 is a diagram illustrating an example of a stop instruction in the fourth embodiment. [Figure 19] FIG. 19 is a diagram illustrating an example of a stop instruction in the fourth embodiment. [Figure 20] FIG. 20 is a diagram illustrating an example of operation in the fourth embodiment. [Figure 21] FIG. 21 is a diagram illustrating an example of local rerouting in the fifth embodiment. [Figure 22] FIG. 22 is a diagram illustrating an example of the operation of the fifth embodiment. [Diagram 23] FIG. 23 is a diagram illustrating an example of a notification by an IAB node in the sixth embodiment. [Figure 24] FIG. 24 is a diagram illustrating an example of the operation of the sixth embodiment. [Diagram 25] FIG. 25 is a diagram illustrating an example of the operation of the seventh embodiment. [Figure 26] FIG. 26 is a diagram illustrating another operation example of the seventh embodiment. [Figure 27] FIG. 27 is a diagram illustrating an example of the operation of the eighth embodiment. [Figure 28] FIG. 28 is a diagram illustrating an example of the operation of the ninth embodiment. [Figure 29] FIG. 29 is a diagram illustrating an example of operation in the tenth embodiment. [Diagram 30] FIG. 30 is a diagram illustrating an example of operation in the eleventh embodiment. [Diagram 31] FIG. 31 is a diagram illustrating an example of the operation of the twelfth embodiment. [Diagram 32] FIG. 32 is a diagram illustrating types of BH RLF notifications. [Diagram 33] FIG. 33 illustrates an extended BH RLF indication transmission option. [Diagram 34] FIG. 34 is a diagram of the implementation of CHO. [Diagram 35] FIG. 35 illustrates an identified solution to avoid re-establishment on descendant nodes. [Diagram 36]FIG. 36 illustrates a comparison of mechanisms for lossless delivery of UL data in the case of hop-by-hop RLCARQ. [Figure 37] FIG. 37 illustrates the "C) Introduction of UL Status Delivery" option. [Figure 38] FIG. 38 illustrates RAN2 signaling issues that may arise with IAB node movement between donors. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] A cellular communication system according to an embodiment will be described with reference to the drawings. In the description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.

[0009] (Configuration of Cellular Communication System) First, a configuration example of a cellular communication system according to an embodiment will be described. The cellular communication system 1 according to an embodiment is a 3GPP 5G system. Specifically, the radio access method in the cellular communication system 1 is NR (New Radio), which is a 5G radio access method. However, LTE (Long Term Evolution) may be applied at least partially to the cellular communication system. Furthermore, the cellular communication system 1 may also be applied to future cellular communication systems such as 6G.

[0010] FIG. 1 is a diagram illustrating an example of the configuration of a cellular communication system 1 according to an embodiment.

[0011] As shown in Fig. 1, the cellular communication system 1 includes a 5G core network (5GC) 10, a user equipment (UE: User Equipment) 100, base station devices (hereinafter, sometimes referred to as "base stations") 200-1 and 200-2, and IAB nodes 300-1 and 300-2. The base station 200 may be referred to as a gNB.

[0012] In the following, an example in which base station 200 is an NR base station will be mainly described, but base station 200 may also be an LTE base station (i.e., an eNB).

[0013] In the following, the base stations 200-1 and 200-2 may be referred to as gNB 200 (or base station 200), and the IAB nodes 300-1 and 300-2 may be referred to as IAB node 300.

[0014] The 5GC 10 has an Access and Mobility Management Function (AMF) 11 and a User Plane Function (UPF) 12. The AMF 11 is a device that performs various mobility controls for the UE 100. The AMF 11 manages information on the area in which the UE 100 is located by communicating with the UE 100 using Non-Access Stratum (NAS) signaling. The UPF 12 is a device that performs transfer control of user data.

[0015] Each gNB 200 is a fixed wireless communication node and manages one or more cells. A cell is used as a term indicating the smallest unit of a wireless communication area. A cell may be used as a term indicating a function or resource for performing wireless communication with a UE 100. One cell belongs to one carrier frequency.

[0016] Each gNB 200 is mutually connected to the 5GC 10 via an interface called an NG interface. In FIG. 1, two gNBs 200-1 and 200-2 connected to the 5GC 10 are illustrated.

[0017] Each gNB 200 may be divided into a central unit (CU) and a distributed unit (DU). The CU and the DU are connected to each other via an interface called an F1 interface. The F1 protocol is a communication protocol between the CU and the DU, and includes an F1-C protocol, which is a control plane protocol, and an F1-U protocol, which is a user plane protocol.

[0018] The cellular communication system 1 supports IAB, which enables wireless relay of NR access using NR for backhaul. The donor gNB 200-1 is a terminal node of the NR backhaul on the network side, and is a donor base station with additional functions to support IAB. The backhaul can be multi-hopped via multiple hops (i.e., multiple IAB nodes 300).

[0019] FIG. 1 illustrates an example in which IAB node 300-1 wirelessly connects to donor gNB 200-1, IAB node 300-2 wirelessly connects to IAB node 300-1, and the F1 protocol is transmitted over two backhaul hops.

[0020] The UE 100 is a mobile wireless communication device that performs wireless communication with a cell. The UE 100 may be any device that performs wireless communication with the gNB 200 or the IAB node 300. For example, the UE 100 is a mobile phone terminal, a tablet terminal, a laptop PC, a sensor or a device provided in a sensor, and / or a vehicle or a device provided in a vehicle. The UE 100 wirelessly connects to the IAB node 300 or the gNB 200 via an access link. FIG. 1 shows an example in which the UE 100 is wirelessly connected to the IAB node 300-2. The UE 100 indirectly communicates with the donor gNB 200-1 via the IAB node 300-2 and the IAB node 300-1.

[0021] FIG. 2 is a diagram showing the relationship between the IAB node 300, parent nodes, and child nodes.

[0022] As shown in FIG. 2, each IAB node 300 has an IAB-DU corresponding to a base station function unit and an IAB-MT (Mobile Termination) corresponding to a user equipment function unit.

[0023] An adjacent node (i.e., an upper node) on the NR Uu radio interface of the IAB-MT is called a parent node. The parent node is a parent IAB node or a DU of the donor gNB 200. The radio link between the IAB-MT and the parent node is called a backhaul link (BH link). FIG. 2 shows an example in which the parent nodes of the IAB node 300 are IAB nodes 300-P1 and 300-P2. The direction toward the parent node is called upstream. From the perspective of the UE 100, the upper node of the UE 100 may correspond to the parent node.

[0024] Adjacent nodes (i.e., lower nodes) on the NR access interface of the IAB-DU are called child nodes. The IAB-DU manages cells, similar to the gNB 200. The IAB-DU terminates the NR Uu radio interface to the UE 100 and the lower IAB nodes. The IAB-DU supports the F1 protocol to the CU of the donor gNB 200-1. In FIG. 2, an example is shown in which the child nodes of the IAB node 300 are the IAB nodes 300-C1 to 300-C3, but the child nodes of the IAB node 300 may include the UE 100. The direction toward the child nodes is called downstream.

[0025] (Base station configuration) Next, a configuration of the gNB 200 which is a base station according to the embodiment will be described. Fig. 3 is a diagram illustrating an example of the configuration of the gNB 200. As shown in Fig. 3, the gNB 200 has a wireless communication unit 210, a network communication unit 220, and a control unit 230.

[0026] The wireless communication unit 210 performs wireless communication with the UE 100 and wireless communication with the IAB node 300. The wireless communication unit 210 has a receiving unit 211 and a transmitting unit 212. The receiving unit 211 performs various receptions under the control of the control unit 230. The receiving unit 211 includes an antenna, and converts (down-converts) a wireless signal received by the antenna into a baseband signal (received signal) and outputs the signal to the control unit 230. The transmitting unit 212 performs various transmissions under the control of the control unit 230. The transmitting unit 212 includes an antenna, and converts (up-converts) a baseband signal (transmitted signal) output by the control unit 230 into a wireless signal and transmits the signal from the antenna.

[0027] The network communication unit 220 performs wired communication (or wireless communication) with the 5GC10 and wired communication (or wireless communication) with other adjacent gNBs 200. The network communication unit 220 has a receiving unit 221 and a transmitting unit 222. The receiving unit 221 performs various receptions under the control of the control unit 230. The receiving unit 221 receives a signal from the outside and outputs the received signal to the control unit 230. The transmitting unit 222 performs various transmissions under the control of the control unit 230. The transmitting unit 222 transmits the transmission signal output by the control unit 230 to the outside.

[0028] The control unit 230 performs various controls in the gNB 200. The control unit 230 includes at least one memory and at least one processor electrically connected to the memory. The memory stores programs executed by the processor and information used in the processing by the processor. The processor may include a baseband processor and a CPU (Central Processing Unit). The baseband processor performs modulation / demodulation and encoding / decoding of a baseband signal. The CPU executes programs stored in the memory to perform various processing. The processor performs processing of each layer, which will be described later. Furthermore, the control unit 230 may perform each processing in the gNB 200 in each of the embodiments shown below.

[0029] (Configuration of relay node) Next, the configuration of the IAB node 300, which is a relay node (or relay node device, hereinafter sometimes referred to as a "relay node") according to the embodiment, will be described. FIG. 4 is a diagram showing an example of the configuration of the IAB node 300. As shown in FIG. 4, the IAB node 300 has a wireless communication unit 310 and a control unit 320. The IAB node 300 may have multiple wireless communication units 310.

[0030] The wireless communication unit 310 performs wireless communication (BH link) with the gNB 200 and wireless communication (access link) with the UE 100. The wireless communication unit 310 for BH link communication and the wireless communication unit 310 for access link communication may be provided separately.

[0031] The wireless communication unit 310 has a receiving unit 311 and a transmitting unit 312. The receiving unit 311 performs various receptions under the control of the control unit 320. The receiving unit 311 includes an antenna, and converts (down-converts) a wireless signal received by the antenna into a baseband signal (received signal), and outputs the signal to the control unit 320. The transmitting unit 312 performs various transmissions under the control of the control unit 320. The transmitting unit 312 includes an antenna, and converts (up-converts) a baseband signal (transmitted signal) output by the control unit 320 into a wireless signal, and transmits the signal from the antenna.

[0032] The control unit 320 performs various controls in the IAB node 300. The control unit 320 includes at least one memory and at least one processor electrically connected to the memory. The memory stores a program executed by the processor and information used in the processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation / demodulation and encoding / decoding of a baseband signal. The CPU executes a program stored in the memory to perform various processing. The processor performs processing of each layer, which will be described later. The control unit 320 may also perform each processing in the IAB node 300 in each of the embodiments shown below.

[0033] (User device configuration) Next, a configuration of the UE 100 which is a user device according to the embodiment will be described. Fig. 5 is a diagram illustrating an example of the configuration of the UE 100. As shown in Fig. 5, the UE 100 includes a radio communication unit 110 and a control unit 120.

[0034] The wireless communication unit 110 performs wireless communication in an access link, that is, wireless communication with the gNB 200 and wireless communication with the IAB node 300. The wireless communication unit 110 may also perform wireless communication in a side link, that is, wireless communication with another UE 100. The wireless communication unit 110 has a receiving unit 111 and a transmitting unit 112. The receiving unit 111 performs various receptions under the control of the control unit 120. The receiving unit 111 includes an antenna, and converts (down-converts) a wireless signal received by the antenna into a baseband signal (received signal) and outputs the signal to the control unit 120. The transmitting unit 112 performs various transmissions under the control of the control unit 120. The transmitting unit 112 includes an antenna, and converts (up-converts) a baseband signal (transmitted signal) output by the control unit 120 into a wireless signal and transmits the signal from the antenna.

[0035] The control unit 120 performs various controls in the UE 100. The control unit 120 includes at least one memory and at least one processor electrically connected to the memory. The memory stores a program executed by the processor and information used in the processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation / demodulation and encoding / decoding of a baseband signal. The CPU executes a program stored in the memory to perform various processing. The processor performs processing of each layer, which will be described later. The control unit 130 may also perform each processing in the UE 100 in each of the following embodiments.

[0036] (Protocol stack configuration) Next, a configuration of a protocol stack according to an embodiment will be described. Fig. 6 is a diagram illustrating an example of a protocol stack related to an RRC connection and a NAS connection of an IAB-MT.

[0037] As shown in FIG. 6, the IAB-MT of IAB node 300-2 has a physical (PHY) layer, a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Resource Control (RRC) layer, and a Non-Access Stratum (NAS) layer.

[0038] The PHY layer performs encoding / decoding, modulation / demodulation, antenna mapping / demapping, and resource mapping / demapping. Data and control information are transmitted between the PHY layer of the IAB-MT of the IAB node 300-2 and the PHY layer of the IAB-DU of the IAB node 300-1 via a physical channel.

[0039] The MAC layer performs data priority control, retransmission processing using Hybrid Automatic Repeat reQuest (HARQ), random access procedures, etc. Data and control information are transmitted between the MAC layer of the IAB-MT of IAB node 300-2 and the MAC layer of the IAB-DU of IAB node 300-1 via a transport channel. The MAC layer of the IAB-DU includes a scheduler. The scheduler determines the transport format (transport block size, modulation and coding scheme (MCS)) and the assigned resource blocks for uplink and downlink.

[0040] The RLC layer transmits data to the RLC layer on the receiving side by utilizing the functions of the MAC layer and the PHY layer. Data and control information are transmitted between the RLC layer of the IAB-MT of the IAB node 300-2 and the RLC layer of the IAB-DU of the IAB node 300-1 via a logical channel.

[0041] The PDCP layer performs header compression / decompression and encryption / decryption. Data and control information are transmitted between the PDCP layer of the IAB-MT of the IAB node 300-2 and the PDCP layer of the donor gNB 200 via a radio bearer.

[0042] The RRC layer controls logical channels, transport channels, and physical channels according to the establishment, re-establishment, and release of radio bearers. RRC signaling for various settings is transmitted between the RRC layer of the IAB-MT of the IAB node 300-2 and the RRC layer of the donor gNB 200. When there is an RRC connection with the donor gNB 200, the IAB-MT is in the RRC connected state. When there is no RRC connection with the donor gNB 200, the IAB-MT is in the RRC idle state.

[0043] The NAS layer, which is located above the RRC layer, performs session management, mobility management, etc. NAS signaling is transmitted between the NAS layer of the IAB-MT of the IAB node 300-2 and the AMF 11.

[0044] Figure 7 is a diagram showing a protocol stack for the F1-U protocol. Figure 8 is a diagram showing a protocol stack for the F1-C protocol. Here, an example is shown in which the donor gNB 200 is divided into a CU and a DU.

[0045] As shown in Fig. 7, each of the IAB-MT of the IAB node 300-2, the IAB-DU of the IAB node 300-1, the IAB-MT of the IAB node 300-1, and the DU of the donor gNB 200 has a BAP (Backhaul Adaptation Protocol) layer as a layer above the RLC layer. The BAP layer is a layer that performs routing processing and bearer mapping / demapping processing. In the backhaul, the IP layer is transmitted through the BAP layer, enabling routing in multiple hops.

[0046] In each backhaul link, the PDUs (Protocol Data Units) of the BAP layer are transmitted by a backhaul RLC channel (BH NR RLC channel). Each BH link configures multiple backhaul RLC channels, which allows for traffic prioritization and QoS (Quality of Service) control. The association between the BAP PDUs and the backhaul RLC channels is performed by the BAP layer of each IAB node 300 and the BAP layer of the donor gNB 200.

[0047] As shown in FIG. 8, the protocol stack of the F1-C protocol has an F1AP layer and a Stream Control Transmission Protocol (SCTP) layer instead of the GTP-U layer and UDP layer shown in FIG.

[0048] In the following, the processing or operation performed by the IAB-DU and IAB-MT of the IAB may be simply described as the processing or operation of the "IAB." For example, the transmission of a BAP layer message by the IAB-DU of the IAB node 300-1 to the IAB-MT of the IAB node 300-2 will be described as the IAB node 300-1 transmitting the message to the IAB node 300-2. In addition, the processing or operation of the DU or CU of the IAB donor 200 may be simply described as the processing or operation of the "IAB donor."

[0049] Also, the upstream direction and the uplink (UL) direction may be used interchangeably, and the downstream direction and the downlink (DL) direction may be used interchangeably.

[0050] Furthermore, hereinafter, donor gNB200 may be referred to as IAB donor 200.

[0051] (First embodiment) Flow control may be performed in the cellular communication system 1. Flow control can avoid congestion (or congestion; hereinafter, may be referred to as "congestion") associated with packet drops in the IAB node 300 and the IAB donor 200.

[0052] Downstream flow control in 3GPP is supported by the BAP sublayer. The IAB node 300 sends feedback information about the available buffer size in each ingress BH RLC channel to the parent node when the buffer size exceeds a certain amount or when a flow control poll is received. The feedback information is sent using the BAP Control PDU.

[0053] Flow control in the upstream direction is not specifically defined in 3GPP, and is considered to be performed by UL scheduling on the MAC layer (or by UL grant) depending on the implementation.

[0054] On the other hand, in the cellular communication system 1, local rerouting may be performed. In 3GPP, local rerouting is defined as forwarding a data packet via an alternative path when a line failure (BH RLF (Backhaul Radio Link Failure)) occurs in a backhaul link. In general, the IAB donor 200 performs routing settings for each IAB node 300. Then, each IAB node 300 selects a relay node to which the data packet is to be forwarded from among multiple relay nodes according to the routing settings. Local rerouting may be performed by ignoring such routing settings and selecting an alternative path as described above.

[0055] The above-described flow control and local rerouting may be combined to perform the following control. That is, when the IAB node 300 receives an uplink flow control feedback message from a parent node, it performs local rerouting. In other words, when the IAB node 300 receives the message from a parent node, it selects an alternative path and transfers the data packet to another parent node on the alternative path.

[0056] However, if the IAB node 300 performs local rerouting immediately after receiving an uplink flow control feedback message, data packets may be forwarded to an alternative path even though the congestion situation of the parent node that sent the message has improved.

[0057] Therefore, in the first embodiment, first, a relay node (e.g., IAB node 300) between a parent node and a child node receives a flow control feedback message from the parent node or the child node. Second, the relay node executes local rerouting to transfer a data packet to an alternative path different from the path to the parent node or the child node that transmitted the flow control feedback message, in response to the lapse of a certain period of time after receiving the flow control feedback message.

[0058] This allows, for example, the IAB node 300 to monitor the congestion status of the parent node or child node for a certain period of time even if it receives a flow control feedback message. Therefore, if the congestion status improves, the IAB node 300 can maintain the path to the parent node before the certain period of time has elapsed.

[0059] Fig. 9 is a diagram showing an example of local rerouting when the IAB node 300-T receives a flow control feedback message from the parent node IAB node 300-P1. As shown in Fig. 9, the IAB node 300-T receives the message from the IAB node 300-P1, and after a certain period of time, transfers the data packet to the other parent node IAB node 300-P2 on the alternative path. Note that the flow control feedback message in this case is an uplink flow control feedback message.

[0060] Fig. 10 is a diagram showing an example of local rerouting when IAB node 300-T receives a flow control feedback message from IAB node 300-C1, which is a child node. As shown in Fig. 10, IAB node 300-T receives the message from IAB node 300-C1, and after a certain period of time has passed, transfers the data packet to another child node, IAB node 300-C2, on an alternative path. Note that the flow control feedback message in this case is a downlink flow control feedback (DL flow control feedback) message.

[0061] The flow control feedback message may be transmitted as a message of the BAP layer, such as a BAP Control PDU, or may be a MAC CE and / or RRC message.

[0062] FIG. 11 is a diagram illustrating an example of operation in the first embodiment.

[0063] The IAB node 300-T starts processing in step S10, and then receives a flow control feedback message from the parent node 300-P1 or the child node 300-C1 in step S11.

[0064] In step S12, the IAB node 300-T measures the fixed period. The fixed period is a period from when the IAB node 300-T receives the flow control feedback message. For example, when the IAB node 300-T receives the message, the IAB node 300-T starts a timer to measure the fixed period. The fixed period may be set in advance by the IAB donor 200 or the parent node 300-P1, or may be included in the flow control feedback message. For example, the IAB node 300-T makes the timer count, and when the count value reaches the fixed period, the fixed period expires and the fixed period is determined to have elapsed. Alternatively, the IAB node 300-T may use the number of times the flow control feedback message is received to measure the fixed period. That is, when the IAB node 300-T receives a flow control feedback message from the parent node 300-P1 or the child node 300-C1, the IAB node 300-T increments a counter. When the counter value reaches a threshold, the IAB node 300-T determines that the fixed period has elapsed. The threshold may be preset by the IAB donor 200 or parent node 300-P1, or may be included in the flow control feedback message. Alternatively, the IAB node 300-T may combine these timer and counter determinations to measure the fixed period. That is, the IAB node 300-T starts a timer and increments a counter when it first receives a flow control feedback message. If the counter value reaches the threshold before the timer expires, the IAB node 300-T determines that the fixed period has elapsed. If the timer expires, the IAB node 300-T resets (i.e., sets) the counter value to zero.

[0065] In step S13, the IAB node 300-T executes local rerouting in response to the lapse of a certain period of time.

[0066] That is, when a certain period of time has elapsed since the IAB node 300-T receives a flow control feedback message from the parent node 300-P1, the IAB node 300-T forwards the data packet to an alternative path other than the path to the parent node 300-P1. The alternative path is the same alternative path as when the destination of the data packet is the path to the parent node 300-P1. Also, when a certain period of time has elapsed since the IAB node 300-T receives a flow control feedback message from the child node 300-C1, the IAB node 300-T forwards the data packet to an alternative path other than the path to the child node 300-C1. The alternative path is the same alternative path as when the destination of the data packet is the path to the child node 300-C1. The local rerouting may include a process of selecting an alternative path and / or transmitting a packet to the alternative path.

[0067] In step S14, the IAB node 300-T ends the series of processes.

[0068] In the first embodiment, when the IAB node 300-T receives a downlink flow control feedback message from the child node 300-C1, the IAB node 300-T may execute local rerouting without a lapse of a certain period of time.

[0069] In the first embodiment, a Type 1 Indication, a Type 2 Indication, or a Type 1 / 2 Indication of the BH RLF may be used instead of the flow control feedback message.

[0070] The Type 1 Indication is an example of a failure occurrence notification indicating that a BH RLF has been detected (RLF detected). The Type 2 Indication is an example of a failure occurrence notification indicating that recovery from a BH RLF is being attempted (Trying to recover). Furthermore, the Type 1 / 2 Indication is also an example of a failure occurrence notification, and is a notification used when there is no need to distinguish between the Type 1 Indication and the Type 2 Indication.

[0071] The types of notifications include Type 3 Indication (RLF recovered) and Type 4 Indication (Recovery failure). The Type 3 Indication is a recovery notification indicating that the IAB node 300-T has recovered from the BH RLF. The Type 4 Indication is an example of a recovery failure notification indicating that the IAB node 300-T has failed to recover from the BH RLF.

[0072] Furthermore, in the first embodiment, instead of measuring a certain period of time, the parent node 300-P1 or the child node 300-C1 may determine whether or not to perform local rerouting in response to a request from the parent node 300-P1 or the child node 300-C1. For example, the parent node 300-P1 or the child node 300-C1 may include an identifier indicating whether or not to perform local rerouting in a flow control feedback message. The IAB node 300-T may determine whether or not to perform local rerouting based on the identifier. This allows the parent node 300-P1 or the child node 300-C1 to control the local rerouting of the IAB node 300-T in response to the congestion situation.

[0073] Second embodiment The second embodiment is an example in which the IAB node 300 executes local rerouting when it is unable to forward a data packet to a parent node or a child node for, for example, a certain period of time.

[0074] That is, first, a relay node (e.g., IAB node 300) between a parent node and a child node attempts to forward a data packet to the parent node or the child node. Second, if the relay node is unable to forward the data packet for a certain period of time, it performs local rerouting to forward the data packet to an alternative path different from the path to the parent node or the child node.

[0075] This allows, for example, the IAB node 300 to give up on the current parent node or child node and transmit the data packet to an alternative path, thereby reducing the latency caused by the data packet transfer.

[0076] 12 is a diagram showing an example of local rerouting in the upstream direction for the IAB node 300-T. When the IAB node 300-T is unable to forward a data packet to the parent node, the IAB node 300-P1, for a certain period of time, the IAB node 300-T performs local rerouting. That is, the IAB node 300-T forwards the data packet to the IAB node 300-P2 on an alternative path different from the path to the IAB node 300-P1.

[0077] 13 is a diagram showing an example of local rerouting in the downstream direction for the IAB node 300-T. When the IAB node 300-T is unable to forward a data packet to the child node IAB node 300-C1 for a certain period of time, the IAB node 300-T executes local rerouting. That is, the IAB node 300-T forwards the data packet to the IAB node 300-C2 on an alternative path different from the path to the IAB node 300-C1.

[0078] FIG. 14 is a diagram illustrating an example of operation in the second embodiment.

[0079] The IAB node 300-T starts processing in step S20, and then transfers a data packet to the parent node 300-P1 or the child node 300-C1 in step S21.

[0080] In step S22, if the IAB node 300-T is unable to forward the data packet for a certain period of time, it executes local rerouting.

[0081] Here, "when data packets cannot be transferred for a certain period of time" refers to, for example, the following in the UL direction.

[0082] That is,

[0083] (A1) "When data packets cannot be forwarded for a certain period of time" refers to when the IAB node 300-T does not receive a UL grant from the parent node 300-P1 even after sending a scheduling request (SR (Scheduling Request)) to the parent node 300-P1 a certain number of times.

[0084] (A2) Or, “when data packets cannot be forwarded for a certain period of time” means when the IAB node 300-T does not receive a UL grant for a certain period of time after transmitting an SR or a buffer status report (BSR) to the parent node 300-P1.

[0085] (A3) or "when data packets cannot be transferred for a certain period of time" refers to when the number of retransmissions of HARQ / RLC from the IAB node 300-T to the parent node 300-P1 reaches a certain number. However, in this case, even if the number of retransmissions of HARQ / RLC reaches a certain number, it is preferable to do so before RLF occurs.

[0086] (A4) or "when data packets cannot be transferred for a certain period of time" refers to when the wireless condition (RSRP (Reference Signal Received Power) / RSRQ (Reference Signal Received Quality)) between the IAB node 300-T and the parent node 300-P1 falls below a certain value. However, even if the wireless condition falls below a certain value, it is preferable that this should occur before RLF occurs.

[0087] (A5) Or, "when a data packet cannot be forwarded for a certain period of time" means when, after receiving a data packet from child node 300-C1, IAB node 300-T is unable to forward the data packet to parent node 300-P1 (or the data packet remains there) for a certain period of time.

[0088] In addition, "when data packets cannot be transferred for a certain period of time" in the DL direction includes, for example, the following.

[0089] That is,

[0090] (B1) "When data packets cannot be transferred for a certain period of time" refers to when the number of retransmissions of HARQ / RLC from IAB node 300-T to child node 300-C1 reaches a certain number.

[0091] (B2) or "when data packets cannot be transferred for a certain period of time" refers to when the wireless condition between the IAB node 300-T and the child node 300-C1 falls below a certain value. The wireless condition in this case is notified to the IAB node 300-T by a measurement report from the child node 300-C1.

[0092] (B3) Or, “when a data packet cannot be forwarded for a certain period of time” means when the IAB node 300-T is unable to forward (remains in) a data packet received from the parent node 300-P1 to the child node 300-C1 for a certain period of time.

[0093] The "certain number of times," "certain time," and "certain value" in (A1) to (B3) above may be set by the parent node 300-P1 or the IAB donor 200. The IAB node 300-T may measure the "certain time" using an internal timer. Furthermore, the "certain number of times," "certain time," "certain value," and timer may exist or be measured separately for each BH RLC channel, each LCG (Logical Channel Group), each source and / or destination, and each routing ID. The timer value may be associated with the BH RLC channel, etc.

[0094] Third embodiment In the first embodiment, an example has been described in which the IAB node 300 performs local rerouting after a certain period of time has elapsed since receiving a flow control feedback message. In this case, when the IAB node 300 receives a flow control leaving feedback message, it can stop the execution of local rerouting. The flow control leaving feedback message is a message for notifying that the IAB node 300 that transmitted the message has returned from a congested state to a normal state that is not congested.

[0095] On the other hand, in the second embodiment, the IAB node makes its own decision to execute local rerouting.

[0096] The third embodiment is an embodiment regarding how to stop local rerouting when the local rerouting is executed in the IAB node 300 in the second embodiment.

[0097] That is, a relay node (e.g., the IAB node 300) stops local rerouting after a certain period of time has elapsed after executing local rerouting. This makes it possible for the IAB node 300 to stop local rerouting that it started to execute on its own initiative.

[0098] Fig. 15 is a diagram showing an example of a case where local rerouting is performed in the upstream direction. As shown in Fig. 15, the IAB node 300-T performs local rerouting by forwarding a data packet to the IAB node 300-P2 on an alternative path. After performing local rerouting for a certain period of time, the IAB node 300-T stops local rerouting.

[0099] 16 is a diagram showing an example of a case where local rerouting is performed in the downstream direction. In this case, the IAB node 300-T performs local rerouting for the IAB node 300-C2 for a certain period of time, and then stops the local rerouting.

[0100] FIG. 17 is a diagram illustrating an example of operation in the third embodiment.

[0101] When the IAB node 300-T starts processing in step S30, it starts counting the timer from the time when it is determined in step S31 that local rerouting is to be performed. In other words, while the timer is running, local rerouting is being performed. Then, the timer of the IAB node 300-T counts up until the count value reaches a predetermined timer value. The predetermined timer value may be set for the IAB node 300-T by, for example, the parent node 300-P1 (or the parent node 300-P2) or the IAB donor 200. The predetermined timer value may also be set for each alternative path.

[0102] In step S32, the IAB node 300-T stops local rerouting when the count value reaches a predetermined timer value, i.e., when the timer expires. Specifically, the IAB node 300-T attempts to forward the data packet to a path according to the routing configuration, that is, to a path to the parent node 300-P1 or the child node 300-C1 in the examples of Figs. 15 and 16.

[0103] (Fourth embodiment) The IAB donor 200 manages the IAB topology constructed by the subordinate IAB nodes 300. In addition, the IAB donor 200 can grasp the congestion state of each IAB node 300.

[0104] As described above, the IAB-CU of the IAB donor 200 provides a routing configuration to the IAB-DU of each IAB node 300. The provided routing configuration includes a routing ID and a BAP address of the next hop. Each IAB node 300 performs routing based on the routing ID stored in the BAP header of the data packet. The routing ID is composed of a (destination) BAP address and a BAP path ID. When the (destination) BAP address matches the own BAP address, each IAB node 300 determines that the data packet has reached the destination. On the other hand, when the (destination) BAP address does not match the own BAP address, each IAB node 300 transfers the received data packet to the IAB node 300 of the next hop BAP address according to the routing configuration. The routing configuration by the IAB donor 200 is performed, for example, by a BAP MAPPING CONFIGURATION message of the F1-AP.

[0105] In this way, the routing settings are centrally managed by the IAB donor 200. When the IAB node 300 is in a state where data packets can be transferred according to such routing settings, the IAB donor 200 takes the initiative in stopping local rerouting. This makes it possible to accommodate centralized management by the IAB donor 200. The fourth embodiment is an example in which the IAB donor 200 stops local rerouting being executed in the IAB node 300 in this way.

[0106] That is, in the fourth embodiment, first, a donor base station (e.g., IAB donor 200) transmits a first message indicating a stop instruction of local rerouting to a first relay node (e.g., IAB node 300). Second, the first relay node stops local rerouting in response to receiving the first message.

[0107] 18 shows an example in which the IAB node 300-T is performing local rerouting in the upstream direction to the IAB node 300-P2. In this case, the IAB-CU of the IAB donor 200 transmits a message indicating a stop instruction to the IAB-DU of the IAB node 300-T. Upon receiving the message, the IAB node 300-T stops local rerouting to the IAB node 300-P2.

[0108] 19 shows an example in which the IAB node 300-T is performing local rerouting in the downstream direction to the IAB node 300-C2. In this case, too, when the IAB node 300-T receives a message indicating a stop instruction from the IAB donor 200, the IAB node 300-T stops local rerouting to the IAB node 300-C2.

[0109] FIG. 20 is a diagram illustrating an example of operation in the fourth embodiment.

[0110] The IAB node 300 starts processing in step S40, and then executes local rerouting in step S41.

[0111] In step S42, when the IAB donor 200 becomes in a predetermined state, it transmits a message indicating a stop instruction of local rerouting to the IAB node 300-T. The "predetermined state" is when the IAB donor 200 monitors the load (or congestion) status for each route and detects a path with a load lower than a certain value. For example, each IAB node 300 transmits the load status to the IAB donor 200 using an F1-AP message or an RRC message. This enables the IAB donor 200 to monitor the load status for each route. The IAB donor 200 transmits a message indicating a stop instruction based on this load status. The message indicating the stop instruction is transmitted by an F1-AP message or an RRC message.

[0112] The message indicating the stop instruction may include, for example, the following information. That is, a BH RLC Channel ID may be included in the message. In this case, the BH RLC Channel having the ID is the target of the stop instruction. Or, a BH LCG ID may be included in the message. In this case, the BH LCG having the ID is also the target of the stop instruction. Or, a routing ID consisting of a destination ID and a path ID may be included in the message. In this case, the route of the routing ID is the target of the stop instruction. Or, an alternative path ID may be included in the message. In this case, the alternative path of the alternative path ID is the target of the stop instruction. The message indicating the stop instruction may include the validity period of the stop instruction in addition to the above IDs. In this case, the validity period may be expressed by a timer value or the like.

[0113] In step S43, the IAB node 300 stops local rerouting in response to receiving the message indicating the instruction to stop local rerouting. Stopping local rerouting may include stopping data transmission to an alternative path, (re)selecting a path based on the routing configuration (i.e., the main path used before the execution of local rerouting), and transmitting data to the (re)selected path.

[0114] In step S44, the IAB node 300 ends the series of processes.

[0115] As another example of the fourth embodiment, the IAB donor 200 may transmit a message indicating an instruction to start a stopped local rerouting to the IAB node 300. In this case, the message may include a routing ID and an ID of an alternative path that are the subject of the instruction to start. The IAB node 300 can grasp which alternative path of which routing ID to start local rerouting on the basis of the information.

[0116] As another example of the fourth embodiment, the IAB donor 200 may transmit a message indicating a change (or update) instruction for local rerouting to the IAB node 300. The message may include a routing ID to be changed and an ID of an alternative path. Alternatively, the message may include information instructing local rerouting to a path indicating the next priority (e.g., when a path with the first priority is currently selected, a path with the second priority, etc.), or information instructing local rerouting to a path other than the path currently selected by the IAB node 300.

[0117] Furthermore, as another example in the fourth embodiment, the IAB donor 200 may transmit a message indicating an instruction to maintain or cancel the maintenance of the ongoing or stopped local rerouting to the IAB node 300. When the IAB node 300 receives a message indicating the maintenance of the ongoing or stopped local rerouting, the IAB node 300 maintains the decision to perform or stop the local rerouting as it is. On the other hand, when the IAB node 300 receives a message indicating the cancellation of the maintenance of the ongoing or stopped local rerouting, the IAB node 300 cancels the decision to perform or stop the local rerouting. Furthermore, a valid period of the maintenance may be set. That is, when the IAB node 300 receives a message indicating the maintenance, the IAB node 300 starts a timer. While the timer is running, the IAB node 300 maintains the decision (state) to perform or stop the local rerouting. When the timer expires, the IAB node 300 may not maintain the decision (state) to perform or stop the local rerouting. In other words, the IAB node 300 can make a decision to perform or stop the local rerouting. The timer value may be preset by the IAB donor 200 or parent node, or may be set by a message indicating the maintenance.

[0118] The messages described above as other examples are transmitted as, for example, an F1-AP message or an RRC message.

[0119] Fifth embodiment In the fourth embodiment, an example has been described in which the IAB donor 200 explicitly instructs the IAB node 300 to start local rerouting. In the fifth embodiment, an example is described in which the IAB donor 200 notifies each IAB node 300 of the BH RLF in the downstream direction of each IAB node 300 as assist information when determining to perform local rerouting in each IAB node 300.

[0120] Generally, the IAB-MT of the IAB node 300 detects a radio link failure (BH RLF) of the BH in the upstream direction of the IAB node. Therefore, the IAB node 300 basically has no means for detecting a BH RLF in the downstream direction.

[0121] In the fifth embodiment, the IAB node 300 can perform local rerouting by receiving a notification of the occurrence of a BH RLF in the downstream direction of the IAB node 300 from the IAB donor 200. Such a notification can assist the IAB node 300 in determining local rerouting in the downstream direction.

[0122] That is, in the fifth embodiment, first, a donor base station (e.g., IAB donor 200) transmits a first message to a first relay node. The first message indicates that a radio link failure occurs in a backhaul link in a downstream direction from the first relay node to a second relay node subordinate to the first relay node. Second, the first relay node performs local rerouting in response to receiving the first message.

[0123] FIG. 21 is a diagram showing an example of local rerouting in the fifth embodiment. When the IAB donor 200 detects a BH RLF in the downstream direction of the IAB node 300-T, it notifies the IAB node 300-T of the occurrence of a DL BH RLF. For example, when the IAB donor 200 receives a measurement report from an IAB node 300-C that is a child node of the IAB node 300-T, it may determine that a DL BH RLF has been detected in the IAB node 300-T. Then, the IAB donor 200 notifies the IAB node 300-T of the occurrence of a DL BH RLF in the IAB node 300-T. When the IAB node 300-T receives the notification of the occurrence of a DL BH RLF, it performs local rerouting and transfers the data packet to another child node on an alternative path.

[0124] FIG. 22 is a diagram illustrating an example of the operation of the fifth embodiment.

[0125] When the IAB donor 200 starts processing in step S50, in step S51, the IAB donor 200 detects the DL direction RLF in the IAB node 300-T. For example, the IAB-CU of the IAB donor 200 may detect the DL BH RLF in the IAB node 300-T by receiving a measurement report from the IAB-MT of the child node 300-C of the IAB node 300-T. Alternatively, for example, in the child node 300-C, when DC (Dual Connectivity) is performed between the IAB node 300-T and another IAB node, the IAB donor 200 receives MCG (Master Cell Group) Failure Information and / or SCG (Secondary Cell Group) Failure Information from the child node 300-C. As a result, the IAB donor 200 may detect the DL BH RLF in the IAB node 300-T.

[0126] In step S52, the IAB donor 200 notifies the IAB node 300-T that DL BH RLC has occurred. For example, the IAB-CU of the IAB donor 200 may transmit the notification to the IAB-DU of the IAB node 300 using an RRC message or an F1-AP message.

[0127] In step S53, the IAB node 300-T performs a predetermined operation in response to receiving the notification. The predetermined operation is local rerouting. That is, the IAB node 300-T transfers data packets to another child node on an alternative path by local rerouting for the link (or child node 300-C) on which the DL BH RLF occurs. Another predetermined operation is stopping DL transmission. That is, the IAB node 300-T stops transmitting data packets to the child node 300-C.

[0128] In step S54, the IAB node 300 (and the IAB donor 200) completes the series of operations.

[0129] As another example of the fifth embodiment, when the IAB donor 200 detects that the DL BH RLF in the IAB node 300-T has recovered, the IAB donor 200 may notify the IAB node 300-T of the recovery of the DL BH RLF. For example, the IAB-CU of the IAB donor 200 may notify the IAB-DU of the IAB node 300-T of the recovery of the DL BH RLF by using an RRC message or an F1-AP message.

[0130] Sixth embodiment The sixth embodiment is an example in which, when the IAB node 300 determines to start or stop execution of local rerouting, it notifies the IAB donor 200. That is, first, the first relay node (e.g., the IAB node 300) transmits a second message indicating that it has determined to start or stop execution of local rerouting to the donor base station (e.g., the IAB donor 200).

[0131] This allows, for example, the IAB donor 200 to know whether local rerouting is being performed in the IAB node 300. Then, the IAB donor 200 can instruct the IAB node 300 to stop or start the ongoing local rerouting, as described in the fourth embodiment.

[0132] Fig. 23 is a diagram showing an example of a notification by the IAB node 300-T. Fig. 23 shows an example of a case where execution of local rerouting in the downstream direction of the IAB node 300-T is determined.

[0133] As shown in FIG. 23, when the IAB node 300-T determines to start or stop execution of local rerouting from the child node 300-C1 to the child node 300-C2, it transmits a message to the IAB donor 200 indicating that.

[0134] In this case, the IAB donor 200 may, if necessary, upon receiving the message, send a message to the IAB node 300-T instructing the IAB node 300-T to allow or prohibit the start or stop of local rerouting.

[0135] The IAB node 300-T starts or stops the execution of local rerouting in response to receiving a message instructing permission or prohibition. Specifically, for example, the following occurs.

[0136] That is, when the IAB node 300-T receives a message indicating permission to start execution from the IAB donor 200 in response to the decision to start execution, the IAB node 300-T starts executing local rerouting in response to the reception of the message. Also, when the IAB node 300-T receives a message indicating prohibition of starting execution from the IAB donor 200 in response to the decision to start execution, the IAB node 300-T does not execute local rerouting in response to the reception of the message. Furthermore, when the IAB node 300-T receives a message indicating permission to stop execution from the IAB donor 200 in response to the decision to stop execution, the IAB node 300-T stops the currently executing local rerouting in response to the reception of the message. Furthermore, when the IAB node 300-T receives a message indicating prohibition of stopping execution from the IAB donor 200 in response to the decision to stop execution, the IAB node 300-T continues the execution without stopping the currently executing local rerouting in response to the reception of the message.

[0137] Although the example of FIG. 23 shows an example of starting execution of local rerouting in the downstream direction in the IAB node 300-T, it may also be a case of starting execution of local rerouting in the upstream direction in the IAB node 300-T.

[0138] FIG. 24 is a diagram illustrating an example of the operation of the sixth embodiment.

[0139] The IAB node 300-T starts processing in step S60, and transmits a message to the IAB donor 200 if it determines to start or stop execution of local rerouting in step S61.

[0140] The message may first include information indicating which route is the target of local rerouting. Specifically, the information may be a BH RLC Channel ID. Alternatively, the information may be a BH LCG ID. Alternatively, the information may be a routing ID consisting of a destination ID and a path ID.

[0141] Secondly, the message may include information indicating which route the local rerouting has been performed to. Specifically, the information may be an alternative path ID. In this case, the alternative path ID may be represented by a routing ID or a path ID.

[0142] Thirdly, the message may include information (reason information) indicating why execution of local rerouting is started or stopped. Specifically, the information may be due to reception of a Type 1 Indication, a Type 2 Indication, a Type 1 / 2 Indication, a Type 3 Indication, or a Type 4 Indication of the BH RLF. Or, the information may be due to reception of a flow control feedback message or a flow control leave feedback message. Or, the information may be due to a certain period of time having passed since reception of a flow control feedback message or a flow control leave feedback message. Or, the information may be due to an inability to transfer data packets (or due to a case where data packets cannot be transferred for a certain period of time in the second embodiment). Or, the information may be due to an instruction from a parent node.

[0143] The message may be sent as an RRC message or an F1-AP message.

[0144] In step S62, the IAB donor 200 may transmit a message indicating permission or prohibition to the IAB node 300-T. In this case, when the IAB donor 200 transmits a message indicating permission to start execution of local rerouting, the IAB donor 200 may indicate a routing ID or a path ID of the local rerouting destination in the message. The message may also be transmitted as an RRC message or an F1-AP message.

[0145] The IAB node 300-T may initiate or not initiate local rerouting depending on receipt of a message indicating permission or prohibition, as described above.

[0146] In step S61, when the IAB node 300 determines to execute local rerouting, it may send a message to the IAB donor 200 to ask the IAB donor 200 whether to execute local rerouting. In step S62, the IAB donor 200 instructs the IAB node 300 to permit or prohibit the request.

[0147] Seventh embodiment The seventh embodiment is an example in which the IAB node 300 combines a plurality of execution conditions to determine whether to execute or stop local rerouting.

[0148] Specifically, first, a relay node (e.g., IAB node 300) executes local rerouting to forward a data packet to an alternative path different from a path to another relay node in response to at least one of the following execution conditions being satisfied: receiving a flow control feedback control message, receiving a notification of a failure occurrence between a backhaul link between the relay node and another relay node, and being unable to forward a data packet for a certain period of time. Second, after executing local rerouting, the relay node stops local rerouting in response to a stop condition being satisfied.

[0149] By combining a plurality of execution conditions to determine whether to execute or stop local rerouting, it is possible to increase the flexibility of implementation and deployment for each network.

[0150] FIG. 25 is a diagram illustrating an example of the operation of the seventh embodiment.

[0151] The IAB node 300 starts processing in step S70, and then executes local rerouting in step S71 if one or more execution conditions are met.

[0152] For example, there are three execution conditions:

[0153] (C1) A flow control feedback message is received, or a certain period of time has elapsed since the flow control feedback message was received (first embodiment).

[0154] (C2) BH RLF Type 1 Indication, Type 2 Indication, or Type 1 / 2 Indication has been received.

[0155] (C3) Data packets could not be transferred for a certain period of time (second embodiment).

[0156] The IAB node 300 executes local rerouting when a situation occurs in which at least one of the three execution conditions is met.

[0157] In step S72, the IAB node 300 stops local rerouting if a stop condition is met.

[0158] The stop condition is, for example, reception of a Type 3 Indication of the BH RLF. Even if the IAB node 300 starts local rerouting in step S71, the IAB node 300 stops local rerouting in response to receiving a Type 3 Indication.

[0159] In step S73, the IAB node 300 ends the series of processes.

[0160] FIG. 26 is a diagram illustrating another operation example of the seventh embodiment.

[0161] The IAB node 300 starts processing in step S80, and executes local rerouting if a certain execution condition is met in step S81. The execution condition is at least one of the above three execution conditions (C1) to (C3).

[0162] In step S82, the IAB node 300 stops local rerouting when a stop condition corresponding to the execution condition is met. The stop condition corresponding to the execution condition is, for example, "receiving a flow control leave feedback message" for the execution condition "receiving a flow control feedback message". For example, it is assumed that the IAB node 300 starts local rerouting in step S81 due to the execution condition "receiving a flow control feedback message". In such a case, the IAB node 300 stops local rerouting when the stop condition "receiving a flow control leave feedback message" is met. In this case, it can be said that the stop condition corresponding to the execution condition is a condition with the opposite content to the execution condition. On the other hand, it is assumed that the IAB node 300 starts local rerouting due to the execution condition "receiving a flow control feedback message". In such a case, even if the IAB node 300 receives a Type 3 Indication, the stop condition corresponding to the execution condition is not met, so the IAB node 300 continues the execution without stopping local rerouting. This is because "receiving a Type 3 Indication" is a stop condition that does not correspond to the execution condition "receiving a flow control feedback message".

[0163] In step S83, the IAB node 300 ends the series of processes.

[0164] Eighth embodiment In the seventh embodiment, a plurality of execution conditions related to local rerouting has been described. The eighth embodiment is an example in which the IAB donor 200 sets, for the IAB node 300, an execution condition to be used by the IAB node 300 from among a plurality of execution conditions. Specifically, a donor base station (e.g., the IAB donor 200) having a relay node (e.g., the IAB node 300) under its control sets a plurality of execution conditions to the relay node.

[0165] FIG. 27 is a diagram illustrating an example of the operation of the eighth embodiment.

[0166] When the IAB donor 200 starts the process in step S90, in step S91, the IAB donor 200 sets, for the IAB node 300, execution conditions to be used by the IAB node 300 from among a plurality of execution conditions of local rerouting. The execution conditions to be set are:

[0167] (D1)BH RLF Type 4 Indication was received.

[0168] (D2)BH RLF Type 1 / 2 Indication was received.

[0169] (D3) A downlink flow control feedback message or an uplink flow control feedback message is received.

[0170] (D4) Data packets could not be transferred for a certain period of time (second embodiment).

[0171] (D5) One or more of the thresholds, timer values, and upper limit values ​​of the number of times related to the above (D1) to (D4). In addition, the IAB donor 200 may set the stop condition described in the seventh embodiment to the IAB node 300.

[0172] The configuration is performed, for example, by the IAB donor 200 sending an RRC message or an F1-AP message including one or more execution conditions (and a stop condition) to the IAB node 300.

[0173] In step S92, the IAB node 300 starts (or stops) local rerouting when a situation matches the set execution condition (or stop condition). When multiple execution conditions (or stop conditions) are set, the IAB node 300 starts (or stops) local rerouting when a situation matches one or more of the execution conditions.

[0174] In step S93, the IAB node 300 ends the series of processes.

[0175] Ninth embodiment The ninth embodiment is an example in which an alternative path is set in local rerouting in the IAB donor 200.

[0176] There is an argument that local rerouting should be performed under centralized control by the IAB donor 200, rather than distributed control by the IAB node 300. This is because the IAB donor 200 grasps the entire IAB topology, and the routing settings are optimized by the IAB donor 200. Therefore, there is an argument that the IAB donor 200 should also be able to set alternative paths in local rerouting. Specifically, the argument is that the IAB donor 200 should assign a different path to the IAB node 300 for the same routing ID (destination address + path ID).

[0177] The ninth embodiment is an example in which an alternative path is set by the IAB donor 200, specifically, a routing ID set by the IAB donor 200 in a routing setting is linked to a routing ID of an alternative path.

[0178] That is, first, a donor base station (e.g., IAB donor 200) sets an alternative path including information on the alternative path associated with information on the main path to a first relay node (e.g., IAB node 300). Second, the first relay node selects an alternative path based on the setting of the alternative path.

[0179] FIG. 28 is a diagram illustrating an example of the operation of the ninth embodiment.

[0180] The IAB donor 200 starts processing in step S100, and then sets alternative paths (s) in addition to the main path for the IAB node 300 in step S101.

[0181] The main path is, for example, a path set in the IAB node 300 by the routing setting by the IAB donor 200 described in the fourth embodiment. The IAB donor 200 has a main path set for each IAB node 300 in advance by the routing setting. The alternative path is, for example, a path selected when local rerouting is performed in the IAB node 300. In the examples of FIG. 18 and FIG. 19, the main path is a path from the IAB node 300-T to the IAB node 300-P1 or 300-C1, and the alternative path is a path from the IAB node 300-T to the IAB node 300-P2 or 300-C2.

[0182] 28, in step S101, the IAB donor 200 includes information about an alternative path in a BAP MAPPING CONFIGURATION message or an RRC Reconfiguration message of the F1-AP and transmits the message to the IAB node 300. As a result, the IAB donor 200 sets up an alternative path for the IAB node 300.

[0183] The information regarding the alternative path may include a plurality of pieces of information corresponding to a plurality of alternative paths.

[0184] The information about the alternative path first includes information linking the routing ID of the main path with the routing ID of the alternative path. For example, the information about the alternative path includes the routing ID of the alternative path, and the linking (or correspondence) may be performed by specifying the routing ID of the main path in correspondence with the routing ID. Alternatively, for example, a grouping ID may be used as the linking information. The grouping ID is an ID defined for grouping the path ID of the main path and the path ID of the alternative path. The grouping ID links the routing ID of the main path with the routing ID of the alternative path.

[0185] Secondly, the information on the alternative path includes a destination ID of the alternative path. The destination ID of the alternative path is the same as the destination ID of the main path. However, when inter-donor-DU rerouting is performed (the twelfth embodiment), the two destination IDs may be different.

[0186] Thirdly, the information on the alternative path includes a path ID of the alternative path. The path ID of the alternative path may be different from or the same as the path ID of the main path. When the path ID of the alternative path is the same as the path ID of the main path, a list of next hop BAP addresses may be set for each routing ID. In this case, the first entry in the list may be identified as the next hop BAP address of the main path, and the second and subsequent entries may be identified as next hop BAP addresses of the alternative paths. Alternatively, the order of the entries in the list may represent the priority order of the next hop BAP addresses.

[0187] The information about the alternative path fourthly includes a routing ID of the alternative path.

[0188] The information about the alternative path may further include the following information:

[0189] (E1) Next Hop BAP Address

[0190] (E2) IAB-donor-DU BAP address

[0191] (E3) Cell ID

[0192] (E4) Egress BH RLC CH ID

[0193] (E5) Ingress BH RLC CH ID may include all or part of the above.

[0194] The information about the alternative path may further include the following information:

[0195] (F1) Priority setting

[0196] (F2) Selection probability setting

[0197] (F3) Timer value indicating the valid period and timer value indicating the prohibited period may include all or part of the above.

[0198] The priority setting in (F1) above is setting information that allows an alternative path to be selected in descending order of priority. For example, if the setting information includes multiple alternative path priorities of "1", "2", ..., the IAB node 300 selects an alternative path with priority "1" when performing local rerouting and attempts to forward a packet. If the result is that the packet cannot be forwarded, the IAB node 300 selects an alternative path with priority "2". Alternatively, if the setting information includes the following information, priority setting may not be required.

[0199] (G1) Intra-donor-DU (within donor DU) alternative path (main path and alternative path exist in the same donor DU)

[0200] (G2) Intra-donor alternative path (main path and alternative path exist within the same donor)

[0201] (G3) Inter-donor alternative path (main path and alternative path exist in different donors) In this case, the IAB node 300 may select an alternative path in the following order: an alternative path within the donor DU, an alternative path within the donor, and an alternative path between donors.

[0202] The selection probability setting in (F2) above is a selection probability expressed as a percentage or real number (0 to 1) for each alternative path. For example, the IAB node 300 uses a random number to select an alternative path based on the random value and the selection probability. For example, assume that there are three alternative paths, each with a selection probability of {0.5, 0.3, 0.2}. In this case, when the random value is 0.4, the IAB node 300 selects the alternative path with the first selection probability, when the random value is 0.7, the alternative path with the second selection probability, and when the random value is 0.9, the alternative path with the third selection probability. It is desirable that the total value of the selection probabilities be 100% (or 1).

[0203] The above (F3) is a timer value indicating the valid period set for each alternative path and a timer value indicating the prohibition period. For example, the following timer values ​​are used:

[0204] That is, when the IAB node 300 selects an alternative path by local rerouting or starts forwarding packets to the alternative path, it starts counting the timer. Then, when the count value of the timer does not reach the timer value indicating the validity period (while it is running), the IAB node 300 can use the selected alternative path. On the other hand, when the count value of the timer reaches the timer value indicating the validity period (when the timer expires), the IAB node 300 stops (or prohibits) the use of the alternative path. Then, after the IAB node 300 ends (or stops or prohibits) the executed local rerouting, it starts counting the timer. Then, when the count value does not reach the timer value indicating the prohibition period (while it is running), the IAB node 300 prohibits the use of the terminated alternative path. The alternative path is removed from the selection candidates, and another alternative path is selected while the local rerouting continues. On the other hand, when the count value reaches the timer value indicating the prohibition period (when the timer expires), the IAB node 300 becomes able to use the terminated alternative path. The alternative path can be a selection candidate for the alternative path.

[0205] In step S102, when performing local rerouting, the IAB node 300 selects an alternative path based on the alternative path setting set by the IAB donor 200 and attempts to forward the packet.

[0206] In step S103, the IAB node 300 ends the series of processes.

[0207] Tenth embodiment When local rerouting is being performed in the IAB node 300, the IAB donor 200 may change the routing settings due to reasons such as a drop in performance of the entire topology. The tenth embodiment is an example in which the operation of local rerouting is stopped (or canceled) when the routing settings are changed.

[0208] Specifically, first, a first relay node (e.g., IAB node 300) starts local rerouting. Second, a donor base station (e.g., IAB donor 200) transmits a first message to the first relay node indicating that the routing configuration set in the first relay node is to be updated. Third, the first relay node stops local rerouting in response to receiving the first message.

[0209] FIG. 29 is a diagram illustrating an example of operation in the tenth embodiment.

[0210] The IAB node 300 starts processing in step S110, and then starts local rerouting in step S111.

[0211] In step S112, the IAB donor 200 updates the routing configuration of the IAB node due to a reason such as detection of a performance degradation of the entire topology. For example, the IAB donor 200 may detect a performance degradation of the entire topology by receiving a message indicating a load status such as an increase in the load on the IAB node 300 from the IAB donor 200. Then, the IAB donor 200 transmits a message indicating a setting update to all the subordinate IAB nodes 300. The message may be an F1-AP message or an RRC message.

[0212] In step S113, the IAB node 300 stops local rerouting in response to receiving a message indicating a configuration update. For example, assume that local rerouting is started by receiving a Type 2 Indication of the BF RLF. In this case, "stop" means that the IAB node 300 "stops" without waiting for a Type 3 Indication and does not need to expect the IAB node 300 to receive a Type 3 Indication.

[0213] In step S114, the IAB node 300 ends the series of processes.

[0214] Eleventh embodiment Even if the IAB node 300 selects an alternative path by local rerouting, the selected alternative path may be more congested than the previous path. This may increase the delay in data packet transfer and degrade the performance of the entire topology.

[0215] The eleventh embodiment is an example in which the IAB donor 200 transmits load information of each path to the IAB node 300. Specifically, first, the donor base station (e.g., the IAB donor 200) transmits a first message including load information of the path between the first relay node and the second relay node to a first relay node (e.g., the IAB node 300). Second, the first relay node executes or stops local rerouting based on the load information.

[0216] By transmitting load information of each path to the IAB node 300, the IAB donor 200 can select an alternative path with a good load situation when performing local rerouting in the IAB node 300. This makes it possible to prevent data packet transfer delays and performance degradation of the entire topology.

[0217] FIG. 30 is a diagram illustrating an example of operation in the eleventh embodiment.

[0218] When the IAB donor 200 starts processing in step S120, the IAB donor 200 transmits a message including load information of each path to the IAB node 300 in step S121.

[0219] The IAB donor 200 may send the message, for example, in the following cases. That is, the IAB donor 200 may send the message periodically. Or, the IAB donor 200 may send the message when requested by the IAB node 300. In this case, the "request" refers to, for example, a request sent from the IAB node 300 in response to a decision made by the IAB node 300 regarding local rerouting. Or, the IAB donor 200 sends the message when it judges it necessary. "When it is judged necessary" refers to, for example, when the load of a certain path increases significantly. The IAB donor 200 can obtain load information from the IAB node 300 on the path, and may judge that the load of a certain path has increased significantly based on the load information when the load of the path increases above a threshold in a short period of time.

[0220] The "load information of each path" included in the message including the "load information of each path" transmitted by the IAB donor 200 is, for example, a load level for each routing ID or a load level for each path ID. In this case, the load level is displayed as a percentage, for example, from 0 to 100%.

[0221] Instead of the "load information", priority information for the path may be notified. The IAB donor 200 can increase the priority of a path with a low load. This makes it possible for the IAB node 300 to increase the possibility of selecting a path with a low load as an alternative path. By transmitting a message including the priority information, for example, the priority information set in the IAB node 300 can be updated. Therefore, for example, when the IAB donor 200 detects that the load of a certain path has increased, it is also possible to set the priority of the path set in the IAB node 300 to a low priority by updating the priority information. This makes it possible to update the priority information of each path set by the routing setting by the IAB donor 200 by transmitting a message in step S121. The priority information can be updated using the message in step S121 more frequently than the setting by the routing setting.

[0222] In step S122, the IAB node 300 performs a predetermined operation using the load information.

[0223] The first predetermined operation is a judgment to execute or stop local rerouting. For example, the IAB node 300 judges to execute local rerouting when the currently used path is a main path and the load of the main path indicated by the load information exceeds a certain value. Also, for example, the IAB node 300 judges to stop local rerouting when the currently used path is an alternative path and the load of the alternative path indicated by the load information exceeds a certain value. When priority information is used instead of load information, the IAB node 300 judges to execute local rerouting when the priority information of the currently used main path is lower than a priority threshold. On the other hand, the IAB node 300 stops local rerouting when the priority information of the currently used alternative path is lower than a priority threshold. The certain value or the priority threshold may be set by the IAB donor 200.

[0224] Secondly, the predetermined operation is the selection of an alternative path. For example, when performing local rerouting, the IAB node 300 uses the load information to select an alternative path based on the following criteria. That is, the IAB node 300 selects the path with the lowest load among the loads indicated in the load information as the alternative path. Alternatively, the IAB node 300 may arbitrarily select a path from among paths with a load equal to or lower than a certain level. When priority information is used instead of the load information, the IAB node 300 selects the path with the highest priority among the priorities indicated in the priority information as the alternative path. Alternatively, the IAB node 300 may select an arbitrary path from among paths with a priority equal to or higher than a certain level as the alternative path.

[0225] Twelfth embodiment The twelfth embodiment is an example in which the IAB donor 200 sets an IAB-donor-DU BAP address to the IAB node 300. The IAB node 300 can select an IAB-donor-DU BAP address in an IAB donor other than the IAB donor 200 as an alternative path. This enables inter-donor-DU rerouting.

[0226] Specifically, first, the donor base station (e.g., IAB donor 200) sets the BAP address of the donor base station to the first relay node (e.g., IAB node 300). Second, the donor base station sets the BAP address of another donor base station different from the donor base station to the first relay node. Third, the first relay node decides to perform local rerouting. Fourth, the first relay node selects a path to either the BAP address of the donor base station or the BAP address of the other donor base station as an alternative path.

[0227] The IAB-donor-DU BAP address is, for example, the BAP address of the IAB-DU in the IAB donor.

[0228] FIG. 31 is a diagram illustrating an example of the operation of the twelfth embodiment.

[0229] When the IAB donor 200 starts the process in step S130, in step S131, the IAB donor 200 sets the IAB-donor-DU BAP address of another IAB donor that can be selected as an alternative path to the IAB node 300. The other IAB donor is an IAB donor different from the IAB donor 200. Here, the BAP address of the IAB-DU belonging to the other donor different from the IAB donor 200 is set. The IAB donor 200 sets the BAP address of the IAB-DU of the other IAB donor, for example, by using an F1-AP message. The BAP address of the IAB-DU of the IAB donor 200 itself is set by the IAB donor 200 before this process is performed by the routing setting as described in the fourth embodiment. The IAB donor 200 may have a forwarding path established with the other IAB donor in advance.

[0230] In step S132, the IAB node 300 decides to perform local rerouting. For example, the IAB node 300 may decide to perform local rerouting when it detects a BH RLF. Alternatively, the IAB node 300 may decide to perform local rerouting due to a trigger described in the above-mentioned (first embodiment), (second embodiment), (fourth embodiment), (seventh embodiment), or (eighth embodiment).

[0231] In step S134, the IAB node 300 selects an alternative path. The IAB node 300 selects, from among the routing settings (routing ID = destination BAP address + path ID), the BAP address of the IAB-DU of the IAB donor 200 (own donor) that matches the destination BAP address, or the path (routing ID) of the BAP address of the IAB-DU of another IAB donor that can be selected as an alternative path.

[0232] In step S134, the IAB node 300 forwards the packet to the selected alternative path.

[0233] In step S135, the IAB node 300 ends the series of processes.

[0234] (Other embodiments) A program may be provided that causes a computer to execute each process performed by the UE 100, the gNB 200, or the IAB node 300. The program may be recorded in a computer-readable medium. Using the computer-readable medium, it is possible to install the program in the computer. Here, the computer-readable medium on which the program is recorded may be a non-transient recording medium. The non-transient recording medium is not particularly limited, and may be, for example, a recording medium such as a CD-ROM or a DVD-ROM.

[0235] In addition, circuits that execute each process performed by the UE 100, the gNB 200, or the IAB node 300 may be integrated, and at least a part of the UE 100, the gNB 200, or the IAB node 300 may be configured as a semiconductor integrated circuit (chip set, SoC).

[0236] Although one embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to the above, and various design changes and the like are possible without departing from the scope of the invention. In addition, it is also possible to combine all or part of each embodiment as long as there is no contradiction.

[0237] This application claims priority to U.S. Provisional Application No. 63 / 133,490 (filed January 4, 2021), the entire contents of which are incorporated herein by reference.

[0238] (Additional Note) (introduction) A revised work item on NR eIAB (Enhancements to Integrated Access AND Backhaul) was approved. Some of the objectives are to:

[0239] Topology Adaptation Extensions Specification of procedures for inter-donor IAB node mobility to enhance robustness and load balancing, including enhancements to reduce signaling load. -Specify extensions to reduce service interruptions due to IAB node movement and BH RLF recovery. · Specification of extensions to topology redundancy, including support for CP / UP separation. Topology, Routing and Transport Enhancements Specification of extensions to improve fairness, multi-hop delays, and congestion mitigation across topologies.

[0240] Regarding the extension of topology adaptation, the following agreement was reached:

[0241] Consider extending topology adaptation to improve robustness (e.g. for fast shadowing), load balancing between different IAB nodes, IAB donor DUs and IAB donor CUs, and reducing signaling load. RAN2 will discuss enhancements to RLF indication / handling with a focus on reducing service interruption after a BH RLF. · CHO and potential IAB specific extensions to CHO are under consideration. DAPS and potential IAB-specific extensions to DAPS are not currently ruled out (although in the absence of a PDCP it is unclear how to support DAPS). Regarding message bundling, RAN2 will at least wait for further developments in RAN3 regarding topology adaptation procedures. ·RAN2 discusses local rerouting including its advantages over central route determination and how to address topology-wide goals.

[0242] This appendix discusses various topics of topology adaptation extensions to the Rel-17 eIAB.

[0243] (Discussion) (Extended BH RLF indication) In the Rel-16 email discussion, four types of BH RLF notifications were discussed, as shown in Figure 32. Finally, only type 4, "recovery failure", is specified as the BH RLF indication in Rel-16, which allows a child IAB-MT to recognize the RLF on the parent's BH link and initiate the RLF recovery procedure.

[0244] Finding 1: In Rel-16, only Type 4 “failure to recover” was defined as a BH RLF indication.

[0245] RAN2 agreed to "consider extending topology adaptation to improve robustness (e.g., for rapid shadowing)." This means that BH RLFs will occur more frequently in Rel-17 compared to Rel-16, as radio conditions are expected to change more dynamically.

[0246] Observation 2: In Rel-17, BH RLFs occur more frequently compared to Rel-16 deployments due to more dynamically changing radio conditions, including rapid shadowing.

[0247] The challenge in Rel-16 is that a child IAB node cannot forward upstream data during parent RLF recovery, or even if data is forwarded, the parent cannot forward data due to BH RLF, so in any case data cannot reach the IAB donor, resulting in service interruption.

[0248] Observation 3: Using the BH RLF indication (Type 4) in Rel-16 causes data transfer to be suspended at the IAB node while the parent's RLF recovery is in progress.

[0249] Therefore, child IAB nodes should be notified of parent's BH RLF as soon as possible to take appropriate actions to reduce delays. This is in line with RAN2's agreement that "RAN2 will discuss RLF indication / handling enhancements with a focus on reducing service interruptions after BH RLF." Therefore, RAN2 should introduce Type 2 "attempting recovery" BH RLF indication. Note that Type 1 and Type 2 have the same meaning.

[0250] Proposal 1: RAN2 should agree that BH RLF indication type 2 "attempting recovery" is introduced. Whether it will be sent via BAP Control PDU, SIB1, or both is for further consideration.

[0251] If we introduce Type 2 indication as in Proposal 1, it is very clear to introduce Type 3 "BH link recovered" since the child IAB-MT should also be notified when the parent BH RLF is recovered. However, since RAN2 has agreed to "consider topology adaptation enhancements to improve signaling load reduction", it should consider whether such an explicit indication is really necessary. If Type 3 indication is sent in a dedicated way to all child IAB nodes (e.g. via BAP Control PDU), it may cause a large overhead.

[0252] For example, if the type 2 indication is sent via SIB1, as shown in option 2 of Figure 33, the indication will not be broadcasted once the BH link is not under RLF (i.e., "recovered"). Thus, downstream IAB nodes and UEs will know whether the BH link has recovered or not based on the absence of type 2 indication in SIB1. Of course, if the type 3 indication is sent via BAP Control PDU, it has the advantage that downstream IAB nodes can quickly know the BH link recovery. However, it has the disadvantage that the UE cannot know the recovery because it does not have the BAP layer. Therefore, RAN2 should consider whether the type 3 indication is really necessary.

[0253] Proposal 2: If Proposal 1 is acceptable, RAN2 should consider whether an explicit BH RLF indication when the BH RLF disappears, i.e., Type 3 “BH Link Recovery”, should be introduced.

[0254] If Proposal 1 and / or Proposal 2 can be agreed upon, the behavior of the IAB-MT upon receiving an indication should be considered while the BH link is being restored. It was proposed that the IAB-MT should reduce / stop SR upon receiving an indication of type 2 and resume operation upon receiving an indication of type 3 (i.e., no more BH RLFs at the parent IAB node). This is one of the desired IAB-MT behaviors when the parent node is attempting to restore the BH link. It is assumed that other IAB-MT behaviors, such as suspending all RBs, are also possible.

[0255] Proposal 3: RAN2 should agree to reduce / stop scheduling requests after IAB-MT receives a Type 2 indication and resume scheduling requests when the parent node no longer has a BH RLF.

[0256] Considering the agreement that "RAN2 will discuss RLF indication / handling enhancements with a focus on reducing service interruptions after BH RLF", it should rather discuss how IAB-MT operates to reduce service interruptions. Local rerouting and conditional handover (CHO) enhancements could be considered as potential solutions when combined with BH RLF indication, but these are still under consideration. In our view, a common aspect of local rerouting and CHO is that they require some kind of trigger condition. So, Type 2 indication could serve for such purpose. Therefore, in addition to proposal 3, RAN2 should discuss other IAB-MT behaviors when the parent is trying to recover from BH RLF.

[0257] Proposal 4: RAN2 should discuss other IAB-MT behaviors when receiving a BH RLF indication of type 2. Further study is needed, e.g. triggering local rerouting and / or conditional handover.

[0258] (Conditional Handover Extension) Conditional Handover (CHO) is introduced in Rel-16 to improve mobility robustness. From our understanding, CHO can be used for specified Rel-16 IABs. RAN2 agreed that "CHO ​​and potential IAB specific extensions to CHO are under consideration". Therefore, it is worth considering CHO extensions for eIABs in addition to the Rel-16 CHO baseline. In Rel-16 CHO, it is performed when the corresponding CHO event (A3 / A5) is met or when the selected cell is a CHO candidate as a result of cell selection for RRC re-establishment, as shown in Figure 34.

[0259] CHO events A3 / A5 can be satisfied when an IAB node experiences a BH RLF on its BH link. On the other hand, these trigger conditions cannot be satisfied for an IAB specific RLF, i.e., RLF due to reception of a BH RLF indication (type 4), because the radio conditions of the IAB node's own BH link are good. In this case, one of the desired actions is for the IAB node to perform a CHO when it receives a BH RLF indication.

[0260] Observation 4: Rel-16 CHO is not automatically triggered / executed by CHO event A3 / A5 in IAB-MT because parental BH RLF recovery is ongoing and, even if it fails, the BH link between IAB-MT and parent is still good.

[0261] Therefore, it is worth discussing additional trigger conditions for CHO to improve the topology adaptation of Rel-17 eIAB. We believe that at least the existing BH RLF indication (i.e., Type 4) is a promising candidate for a new trigger, but if introduced, it could be further discussed whether CHO should also be performed upon receipt of a Type 2 indication.

[0262] Proposal 5: RAN2 should discuss whether additional trigger conditions for CHO are specified, at least when an IAB node receives a BH RLF indication (Type 4). If additional trigger conditions are introduced, further consideration is required as to whether they can be applied to Type 2.

[0263] If Proposal 5 is agreed, a problem may arise in that all CHO candidates (i.e. candidate cells) may be triggered to CHO at the same time, since it does not depend on CHO event A3 / A5 but is a kind of "forced" trigger by BH RLF indication.

[0264] The current specification states that "When multiple NR cells are triggered for a conditional reconfiguration execution, it is up to the UE implementation to select which one. For example, the UE selects one of the triggered cells for execution, taking into account the beam and beam quality." This is primarily targeted at UEs.

[0265] Observation 5: In Rel-16 CHO, when multiple candidate cells trigger CHO execution, it is up to the UE implementation to select which cell to select.

[0266] As for the IAB-MT, it is not always best if the IAB-MT selects one of the cells triggered by the implementation depending on the local radio quality, etc., since the purpose of the entire topology is properly handled by the IAB donor. Therefore, RAN2 should discuss how to check the execution of IAB donor-controlled CHO for additional trigger conditions such as in proposal 5. For example, the IAB donor may set priority information associated with the CHO candidates in the CHO configuration. The IAB-MT should select the highest priority cell from all triggered CHO candidates that meet a certain radio quality (e.g., S-criterion).

[0267] Proposal 6: RAN2 should consider whether IAB donor-controlled CHO execution is required as an additional enhancement when all candidate cells trigger CHO upon receipt of a BH RLF indication.

[0268] (Local Rerouting Extension) In Rel-16, local rerouting is only allowed if a BH RLF occurs, as described below. NOTE: For example, data buffering in the transmitting part of the BAP entity until the RLC-AM entity receives an acknowledgment is up to the implementation. In case of a BH RLF, the transmitting part of the BAP entity may reroute to an alternative path BAP data PDUs that have not been accepted by the lower layers before the BH RLF.

[0269] This indicates that local rerouting is beneficial to improve robustness and service interruption due to BH RLF. Therefore, Rel-17 should aim to apply local rerouting to other cases agreed by RAN2 that improve load balancing, signaling reduction, robustness and / or service interruption. It is worth considering additional conditions for starting / stopping local rerouting other than BH RLF, such as by receiving BH RLF indication as in proposal 4 (to improve robustness / service interruption) and / or by receiving flow control feedback (for load balancing / congestion mitigation). That is, in general, parent and / or child should be able to trigger local rerouting of IAB nodes depending on conditions.

[0270] Observation 6: In Rel-16, local rerouting is only allowed in the case of BH RLF, which improves robustness and service interruption.

[0271] Proposal 7: RAN2 should discuss whether additional conditions to start / stop local rerouting are introduced, which could be triggered by other IAB nodes, such as by receiving a BH RLF indication as in proposal 4, and / or by receiving flow control feedback.

[0272] If agreed, other cases in Rel-17, i.e. not limited to BH RLF, "RAN2 will discuss local rerouting including benefits over central routing and how to address topology-wide objectives." Therefore, the Rel-16 issue should be considered from an objective perspective of the entire topology. Needless to say, the IAB donor handles the topology-wide objectives since it has complete knowledge and complete control over the entire IAB topology.

[0273] In Rel-16 local rerouting, it is up to the implementation of the IAB node to select a path as an alternative path as long as the destination is the same. This means that local rerouting is based on local decisions and cannot be controlled from the IAB donor's perspective. This may not be consistent with the overall topology objectives, especially when many local decisions occur and accumulate in the IAB topology.

[0274] Observation 7: In Rel-16 local rerouting, it is up to the IAB-MT implementation to decide which path is selected as the alternative path.

[0275] Therefore, the controllability of the IAB donor should become more important if local rerouting is extended beyond the BH RLF case. Since an IAB node needs to select an alternative path when performing local rerouting, it is straightforward that the IAB donor can set up an alternative path. Modeling of the alternative path requires further consideration, such as whether the alternative path has the same routing ID.

[0276] Proposal 8: RAN2 should consider whether IAB donors can configure alternative paths to IAB nodes in addition to the Rel-16 routing configuration.

[0277] Another aspect of IAB donor controllability is that the IAB donor should be aware of local rerouting and should consider that it may start / stop local rerouting at an IAB node for the coexistence of local rerouting and topology-wide objectives. For example, the IAB donor may consider whether the topology-wide objective is still achieved based on its knowledge of which IAB nodes are currently performing local rerouting. If the IAB donor realizes that the topology-wide objective cannot be achieved, the IAB donor may instruct the IAB nodes to start / stop local rerouting or the IAB donor may change the routing configuration of the entire IAB topology.

[0278] How local rerouting is handled for topology-wide purposes is entirely up to the IAB donor implementation, but the IAB donor may require information and control over the local decisions of the IAB nodes.

[0279] Proposal 9: RAN2 should discuss whether IAB nodes should notify IAB donors when local rerouting starts / stops.

[0280] Proposal 10: RAN2 should discuss whether an IAB donor can instruct an IAB node to start / stop local rerouting.

[0281] (BH RLF Recovery and Cell (Re)Selection Enhancements) In the RRC re-establishment procedure, the IAB-MT first performs a cell selection procedure to find a suitable cell. In this cell selection procedure, potential issues were pointed out in Rel-16, such as the possibility that the IAB-MT may select a descendant node. Therefore, it was discussed in the email discussion.

[0282] Five possible solutions were discussed and summarized along with the rapporteur's views, as shown in Figure 35.

[0283] The conclusion was "No further action will be taken on this topic in Rel-16". This meant that RAN2 agreed to "Option 4: Nothing is needed as RRC re-establishment will fail if there is no BH connection". Option 4 was acceptable in Rel-16 deployment scenarios even if more time is needed for BH RLF recovery since it has to wait for failure (T301 expiry) and eventually move to idle.

[0284] Observation 8: In Rel-16, if an IAB node attempts an RRC re-establishment request to a descendant node, the IAB node must wait for the failure and eventually move to idle.

[0285] In Rel-17, cell (re)selection and RRC re-establishment may occur more frequently in view of Finding 2. Therefore, suboptimal operation, i.e. operation according to Finding 8, would cause significant performance degradation in terms of IAB topology stability and service continuity. Therefore, to optimize the IAB-MT operation during BH RLF recovery, as stated by the rapporteur in the above email discussion, "this topic may be discussed again in Rel-17."

[0286] Proposal 11: RAN2 should agree that cell (re)selection optimization is considered to avoid re-establishment on inappropriate nodes (e.g. descendant nodes).

[0287] Among the solutions identified, except for option 4 above, a common concept can be seen to be that for cell selection purposes, the IAB-MT is provided with either type of allowed list or blocked list. Given that topology changes may occur frequently in Rel-17, for example due to "inter-donor IAB node movements", allowed list and blocked list have advantages and disadvantages depending on the topology and the location of the IAB nodes.

[0288] For example, from the perspective of IAB nodes near the IAB donor, i.e., the top of the DAG topology, it may be more reasonable to provide a permission list since the number of candidate nodes is small, possibly only IAB donor DUs.

[0289] However, in another example, for IAB nodes far away from the IAB donor, i.e., from the perspective of the bottom of the DAG topology, it may be necessary to include a huge number of candidate nodes in the allow list. Instead, a block list may be more appropriate, for example, to include only downstream IAB nodes of the IAB node of concern, and possibly only a small number of child IAB nodes, thus reducing overhead.

[0290] One concern with the allowlist is that due to the nature of Rel-17's "inter-donor IAB node movement," it may be necessary to include candidate IAB nodes that belong to different / adjacent IAB topologies, potentially increasing the size of the list, whereas the blocklist has no such concern, since downstream IAB nodes obviously belong to the same IAB topology.

[0291] Observation 9: Allowed and blocked lists have advantages and disadvantages depending on the topology and location of the IAB nodes.

[0292] It may therefore be desirable for an IAB donor (or parent IAB node) to be able to choose whether to use an allowed list or a blocked list when providing information to a child IAB node for cell selection purposes. It should also be considered whether it would be beneficial to reuse that information for cell reselection purposes.

[0293] Proposal 12: RAN2 should agree that allowed or blocked lists (i.e. selection structures) are provided to the IAB-MT for cell selection purposes to avoid re-establishment to descendant nodes. Whether these lists can also be used for cell reselection procedures requires further study.

[0294] If proposal 12 can be agreed upon, further consideration should be given to how the information (i.e. allowlists or blocklists) will be provided. Option 1 assumes CHO configuration and may require some extensions. Option 2 assumes additional indications, e.g. BH RLF indication of type 2. Option 3 assumes providing topology-wide information not in the existing configuration. Option 5 assumes configuration by OAM, but as the rapporteur pointed out, this is doubtful.

[0295] Considering again the assumption of Rel-17 (i.e., observation 2), i.e., parent IAB node or IAB donor should provide list to child IAB node when topology change occurs, allow list / block list needs to be provided dynamically. Therefore, option 5, i.e., OAM, should be ruled out. Which method, i.e., option 1, 2, or 3, should be the baseline for enhancement needs further consideration.

[0296] Proposal 13: RAN2 should agree that the allow list / block list will be dynamically provided by the parent IAB node or IAB donor whenever the topology changes. Details need further study.

[0297] (Lossless Delivery Extension) During the Rel-15 research phase, the issue of multi-hop RLC ARQ was discussed and captured in section 8.2.3 of the TR. In Rel-16, the protocol stack was defined for IAB with a non-separate RLC layer, i.e., end-to-end ARQ was eliminated in favor of hop-by-hop ARQ.

[0298] For hop-by-hop ARQ, challenges were identified in end-to-end reliability, i.e., lossless delivery of UL packets. Three solutions were identified and evaluated, as shown in Figure 36.

[0299] In Rel-16, the first solution, "changes in PDCP protocols / procedures", was not adopted because it would affect Rel-15 UEs.

[0300] The second solution, "re-routing of buffered PDCP PDUs at intermediate IAB nodes", was supported as an implementation choice at the BAP layer. Additionally, the BAP layer may "e.g. buffer data at the transmitting part of the BAP entity until the RLC-AM entity receives an acknowledgment, which is implementation dependent". These BAP implementations were considered to avoid packet loss in "most" cases of Rel-16 deployment scenarios, i.e. when using fixed IAB nodes, but were not perfect, e.g. as shown in Figure 36.

[0301] The third solution, "introduction of UL status delivery", was a promising solution to ensure lossless delivery of UL data, taking into account the evaluation results cited in Figure 36. The idea was to delay the RLC ARQ to the UE, so that PDCP data recovery in the UE would be initiated when necessary. However, it was not specified in Rel-16, since fixed IAB nodes were assumed, and it was considered rare for topology changes to result in UL packet drops.

[0302] Considering the assumptions of Rel-17, i.e., in view of Proposal 1, the third solution should be further explored since it is no longer rare to lose UL packets during topology changes, which occur frequently in Rel-17. Therefore, in addition to the results captured in TR, RAN2 should discuss enhancement mechanisms to ensure lossless delivery in L2 multi-hop networks.

[0303] Proposal 14: RAN2 should agree to implement the solution specified in TR38.874, i.e. a mechanism to ensure lossless delivery under conditions of potentially frequent topology changes based on some form of "UL status delivery".

[0304] Regarding the details of the third solution, i.e., “Introduction of UL Status Distribution”, two options, C-1 and C-2, were discussed in the email discussion as shown in Figure 37.

[0305] Regarding C-1 above, it is assumed that a "confirmation" from the IAB donor needs to be specified in the BAP or RRC for end-to-end signaling forwarding over multi-hop L2 networks. Therefore, a relatively high standard effort would be required to specify this option.

[0306] Regarding C-2 above, if it works well for IAB topologies, it can actually be implemented for Rel-16 IAB nodes, since it ultimately depends on the IAB-DU implementation when sending RLC ACK to the UE (or downstream IAB nodes), even though it should be assumed that OAM configures all IAB nodes with this option. Furthermore, it is simpler than C-1, since it assumes hop-by-hop feedback and does not assume additional Control PDUs. Therefore, C-2 should be the Rel-17 extension baseline for lossless delivery of UL packets.

[0307] Observation 10: Solution C-2 for “Introduction of UL Status Distribution” could be an extended baseline for Rel-17, which could also be implemented for Rel-16.

[0308] However, Rel-17 should expect dynamic topology changes that cause UL packet loss, so Rel-17 extensions will support C-2 as a standard supported feature. At least the Stage 2 specifications should describe the overall mechanism based on C-2. Otherwise, the 3GPP standard does not guarantee lossless delivery during IAB node handover. Furthermore, minor changes such as RLC and / or BAP are expected in Stage 3, but may not specify the details since they are considered as internal operation of IAB nodes.

[0309] Proposal 15: RAN2 should agree to specify an RLC ARQ mechanism for lossless delivery of UL packets in stage 2, which delays sending ACK to child nodes / UEs before receiving ACK from parent IAB node (i.e. C-2). Whether / how to specify in stage 3 needs further study.

[0310] (IAB node transfer between donors) The IAB node integration procedure has been introduced in Rel-16 and will be used for the initial integration of IAB nodes, i.e., those still in the out-of-service stage.

[0311] Rel-17 aims to specify inter-donor IAB node movements, which will provide robust operation and apply to mobile IAB nodes. In contrast to Rel-16, Rel-17 inter-donor IAB node movements are performed in the in-service phase, so that an inter-donor IAB node movement of one IAB node will impact the entire topology and cause service interruption. In other words, Rel-17 inter-donor IAB node movements require consideration of how all IAB nodes in the IAB topology move to other IAB donors, specifically, how RRC reconfiguration with synchronization (i.e., handover commands) is provided to these affected IAB nodes.

[0312] Assuming that a child node (IAB node #2) is connected to a source IAB donor via a parent node (IAB node #1) as shown in FIG. 38, a set of signaling issues can be considered.

[0313] Case 1: If the parent is moved first, the RRC signaling path between the child and the source donor is released, so it is unclear how the child node can be moved. Case 2: When a child is moved first, the RRC signaling path to the target donor via the parent node has not yet been established, so it is unclear how the child node can reach the target donor (i.e., how to complete the RRC reconfiguration and send it to the target donor).

[0314] For case 1, the CHO may be reused with some extensions in the child nodes, i.e., the CHO is executed in the child node when the parent node is moved. In case 2, the child node's RRC reconfiguration transmission to the target donor may be delayed, for example, by its parent node.

[0315] In either case, one option could be for the child node to first be released and then reintegrated using Rel-16 procedures, although this may not be a desirable solution for Rel-17 given the significant service disruption.

[0316] While the overall procedure for inter-donor IAB node mobility is considered in RAN3, RAN2 needs to consider its impact on how multiple IAB nodes are reconfigured in a multi-hop network.

[0317] Proposal 16: RAN2 needs to consider how to reconfigure multi-hop IAB nodes due to inter-donor IAB node movement.

Claims

1. 1. A control method comprising: receiving, by a relay node, a flow control feedback message from a child node of the relay node; determining whether or not the relay node performs local rerouting to forward a data packet to an alternative path different from a path to the child node based on predetermined information included in the flow control feedback message; A communication control method comprising the steps of:

2. A relay node, a receiver for receiving a flow control feedback message from a child node of the relay node; a control unit that determines whether to perform local rerouting to transfer a data packet to an alternative path different from the path to the child node based on predetermined information included in the flow control feedback message. Relay node.

3. A processor for controlling a relay node, receiving a flow control feedback message from a child node of the relay node; and determining whether to perform local rerouting to transfer a data packet to an alternative path different from the path to the child node based on predetermined information included in the flow control feedback message. Processor.