Communication Control Method
The communication control method addresses inefficiencies in multi-hop relay networks by linking hop numbers to logical channel groups and implementing local rerouting and conditional handover, improving resource allocation and ensuring continuous service in IAB nodes.
Patent Information
- Application Number
- JP2023518695
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-05-07
- Filing Date
- 2022-05-02
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2042-05-02
AI Technical Summary
Existing cellular communication systems face challenges in efficiently managing multi-hop relay networks, particularly in terms of resource allocation and failure recovery in Integrated Access and Backhaul (IAB) nodes, leading to inefficiencies and potential communication disruptions.
The proposed communication control method involves setting correspondence information between the number of hops and logical channel groups, transmitting buffer status reports and uplink grants based on this information, and implementing local rerouting and conditional handover strategies to manage IAB nodes effectively.
This approach enhances resource allocation fairness, reduces latency, and ensures continuous service by optimizing the communication control in multi-hop relay networks, particularly in scenarios involving IAB nodes.
Smart Images

Figure 0007587029000001 
Figure 0007587029000002 
Figure 0007587029000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a communication control method for use in a cellular communication system. [Background technology]
[0002] The Third Generation Partnership Project (3GPP), a standardization project for cellular communication systems, is considering the introduction of a new relay node called an Integrated Access and Backhaul (IAB) node (see, for example, "3GPP TS 38.300 V16.5.0 (2021-03)"). 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 donor base station having a first relay node and a second relay node that is a parent node of the first relay node, setting correspondence information indicating a correspondence relationship between a hop number of a logical channel (LCH) and a logical channel group (LCG) to the first relay node. The communication control method also includes the first relay node transmitting a buffer status report (BSR) to the second relay node based on the correspondence information. The communication control method further includes the second relay node transmitting an uplink grant (UL grant) to the first relay node based on the correspondence information and the buffer status report.
[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 an upper node of a first relay node setting a setting value related to a logical channel group to the first relay node. The communication control method also includes the first relay node determining a MAC Control Element (CE) format corresponding to the setting value. The communication control method further includes the first relay node transmitting a buffer status report to a second relay node that is a parent node of the first relay node, using the MAC Control Element format.
[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 higher-level node of a first relay node setting an integrated buffer status report to the first relay node. The communication control method also includes the first relay node transmitting, in accordance with the setting, the integrated buffer status report storing buffer sizes corresponding to logical channel groups classified by type of buffer status report, to a second relay node that is a parent node of the first relay node.
[0006] A communication control method according to a fourth aspect is a communication control method used in a cellular communication system. The communication control method includes a donor base station having a first relay node and a second relay node, which is a parent node of the first relay node, configured to set local rerouting and conditional handover (CHO) to the first relay node. The communication control method also includes the first relay node receiving, from the second relay node, a failure recovery notification indicating that recovery from a failure that has occurred in a backhaul link between the second relay node and a parent node of the second relay node is being attempted. The communication control method further includes the first relay node executing local rerouting or conditional handover in response to receiving the failure recovery notification. [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 an example of the configuration 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(A) is a diagram showing an example of transmitting a legacy BSR according to the first embodiment, and FIG. 9(B) and FIG. 9(C) are diagrams showing examples of transmitting a preemptive BSR according to the first embodiment. [Figure 10] FIG. 10A is a diagram illustrating an example of the configuration of a MAC CE of a short BSR according to the first embodiment, and FIG. 10B is a diagram illustrating an example of the configuration of a MAC CE of a long BSR. [Figure 11] FIG. 11 is a diagram illustrating an example of operation according to the first embodiment. [Figure 12] FIG. 12A is a diagram illustrating a configuration example of a cellular communication system according to the first embodiment, and FIG. 12B is a diagram illustrating an operation example according to a modification of the first embodiment. [Figure 13] 13A and 13B are diagrams illustrating an example of a BSR MAC CE in a fixed extended format according to the second embodiment. [Figure 14]14A and 14B are diagrams illustrating an example of a BSR MAC CE in a fixed extended format according to the second embodiment. [Figure 15] 15(A) and 15(B) are diagrams illustrating an example of a BSR MAC CE in a variable extension format according to the second embodiment. [Figure 16] FIG. 16 is a diagram illustrating an example of operation according to the second embodiment. [Figure 17] FIG. 17 illustrates an example of operation according to a modification of the second embodiment. [Figure 18] FIG. 18 is a diagram illustrating an example of operation according to the third embodiment. [Figure 19] FIG. 19 is a diagram illustrating an example of a relationship between nodes according to the fourth embodiment. [Figure 20] FIG. 20 is a diagram illustrating an example of operation according to the fourth embodiment. [Figure 21] FIG. 21 is a diagram illustrating an example of operation according to a modification of the fourth embodiment. [Figure 22] FIG. 22 is a diagram showing types of BH RLF notifications. 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 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. In addition, future cellular communication systems such as 6G may also be applied to the cellular communication system.
[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. A cell may be used without distinction from a base station, such as the gNB 200. 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 (or donor node, hereinafter sometimes referred to as "donor node") 200-1 is a terminal node of the NR backhaul on the network side, and is a donor base station with additional functions that 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 node 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 and / or a tablet terminal, a laptop PC, a sensor or a device provided in a sensor, a vehicle or a device provided in a vehicle, or an unmanned aerial vehicle or a device provided in an unmanned aerial 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 node 200-1 via the IAB node 300-2 and the IAB node 300-1.
[0021] FIG. 2 is a diagram showing the relationship between an IAB node 300 and its 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 DU of the parent IAB node or the donor node 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 node 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] In addition, all the IAB nodes 300 connected to the donor node 200 via one or more hops form a directed acyclic graph (DAG) topology (hereinafter, sometimes referred to as "topology") with the donor node 200 as the root. In this topology, as shown in FIG. 2, adjacent nodes on the IAB-DU interface are child nodes, and adjacent nodes on the IAB-MT interface are parent nodes. The donor node 200 centralizes, for example, resource, topology, and route management of the IAB topology. The donor node 200 is a gNB that provides network access to the UE 100 via a network of backhaul links and access links.
[0026] (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.
[0027] 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.
[0028] 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.
[0029] 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 baseband signals. The CPU executes programs stored in the memory to perform various processing. The processor performs processing of each layer described later. Furthermore, the control unit 230 may perform various processing in the gNB 200 (or the donor node 200) in each of the embodiments shown below.
[0030] (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.
[0031] 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.
[0032] 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.
[0033] 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 various processing in the IAB node 300 in each of the embodiments shown below.
[0034] (Configuration of user device) 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.
[0035] 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.
[0036] 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 120 may also perform each processing in the UE 100 in each of the following embodiments.
[0037] (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.
[0038] 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.
[0039] 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.
[0040] 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.
[0041] 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.
[0042] 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 CU of the donor node 200 via a radio bearer.
[0043] 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 CU of the donor node 200. When there is an RRC connection with the donor node 200, the IAB-MT is in an RRC connected state. When there is no RRC connection with the donor node 200, the IAB-MT is in an RRC idle state.
[0044] 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 NAS layer of the AMF 11.
[0045] Fig. 7 is a diagram showing a protocol stack for the F1-U protocol. Fig. 8 is a diagram showing a protocol stack for the F1-C protocol. Here, an example is shown in which the donor node 200 is divided into a CU and a DU.
[0046] 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 node 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.
[0047] In each backhaul link, PDUs (Protocol Data Units) of the BAP layer are transmitted by a backhaul RLC channel (BH NR RLC channel). By configuring multiple backhaul RLC channels in each BH link, traffic prioritization and QoS (Quality of Service) control are possible. The association between BAP PDUs and backhaul RLC channels is performed by the BAP layer of each IAB node 300 and the BAP layer of the donor node 200.
[0048] In addition, the CU of the donor node 200 terminates the F1 interface to the IAB node 300 and the DU of the donor node 200. The CU of the donor node 200 is a gNB-CU function of the donor node 200. In addition, the DU of the donor node 200 hosts the IAB BAP sublayer and provides wireless backhaul to the IAB node 300. The DU of the donor node 200 is a gNB-DU function of the donor node 200.
[0049] As shown in FIG. 8, the protocol stack of the F1-C protocol has an F1AP layer and an SCTP layer instead of the GTP-U layer and UDP layer shown in FIG.
[0050] 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 donor node 200 may be simply described as the processing or operation of the "donor node".
[0051] 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.
[0052] (First embodiment) Next, a first embodiment will be described.
[0053] (About BSR (Buffer Status Report)) In general, the BSR transmitted by the UE 100 (hereinafter, referred to as "legacy BSR" where appropriate) indicates the amount of untransmitted uplink data (i.e., uplink buffer amount) of each layer of the MAC, RLC, and PDCP for each logical channel group (LCG). Each LCG includes at least one logical channel and is a group set according to priority. Based on the legacy BSR received from the UE 100, the gNB 200 grasps the amount of untransmitted uplink data of the UE 100 for each LCG, and performs scheduling so as to allocate uplink radio resources to the UE 100 in accordance with the amount of untransmitted uplink data.
[0054] Fig. 9(A) is a diagram showing an example of transmission of a legacy BSR according to the first embodiment. In Fig. 9(A), it is expressed as "Regular BSR", but hereinafter, "Regular BSR" may also be referred to as legacy BSR.
[0055] FIG. 9(A) illustrates an example in which an IAB node 300-T transmits a legacy BSR to a parent node 300-P after receiving data from a child node 300-C.
[0056] As shown in Fig. 9(A), the IAB-MT of the IAB node 300-T uses the legacy BSR to report the amount of data waiting to be transmitted (or buffered) in the MAC and RLC in the IAB-MT of the IAB node 300-T as a buffer size. The IAB-DU of the parent node 300-P allocates uplink radio resources to the IAB node 300-T that correspond to this amount of data. The IAB-MT of the IAB node 300-T uses the allocated uplink radio resources to transmit the data to the parent node 300-P.
[0057] 9B and 9C are diagrams illustrating an example of transmission of a pre-emptive BSR according to the first embodiment.
[0058] As shown in Fig. 9(B), after the IAB-DU of the IAB node 300-T transmits an uplink grant (UL grant) to the child node 300-C, the IAB-MT of the IAB node 300-T transmits a preemptive BSR to the parent node 300-P before receiving UL data from the child node 300-C. Also, as shown in Fig. 9(C), after the IAB-DU of the IAB node 300-T receives a legacy BSR from the child node 300-C, the IAB-MT of the IAB node 300-T transmits a preemptive BSR to the parent node 300-P before transmitting a UL grant to the child node 300-C.
[0059] In this way, the preemptive BSR is transmitted to the parent node 300-P at an earlier timing than the legacy BSR. Therefore, the preemptive BSR can reduce the delay (latency) of the UL scheduling of the parent node 300-P to the IAB node 300-T, compared to the case of the legacy BSR.
[0060] 10A is a diagram showing a configuration example of a MAC CE of a short BSR (hereinafter, may be referred to as a "short BSR MAC CE") according to the first embodiment. When one LCG (Logical Channel Group) has data available for transmission, the short BSR MAC CE is used. That is, when reporting the buffer size of one LCG, the short BSR MAC CE is used.
[0061] As shown in FIG. 10(A), the short BSR MAC CE includes an "LCG ID" field and a "buffer size" field.
[0062] The "LCG ID" area is an area in which identification information of the logical channel group for which the buffer size is reported is stored. The area length of the "LCG ID" area is 3 bits.
[0063] The "buffer size field" is a field that stores the total amount of available data after the MAC PDU is constructed (i.e., after the logical channel prioritization procedure) across all logical channels in a logical channel group according to a predetermined calculation procedure. The length of the "buffer size" field is 5 bits.
[0064] 10B is a diagram showing a configuration example of a MAC CE of a long BSR (hereinafter, may be referred to as a "long BSR MAC CE") according to the first embodiment. The long BSR MAC CE is used when there is more than one LCG (Logical Channel Group) having data available for transmission. In other words, when reporting the buffer sizes of multiple LCGs, the long BSR MAC CE is used.
[0065] FIG. 10B also illustrates a configuration example of a MAC CE of a preemptive BSR (hereinafter, may be referred to as a "preemptive BSR MAC CE").
[0066] The BSR MAC CE shown in FIG. 10(B) is the LCG i " area and "Buffer Size area."
[0067] "L.C.G. i " field indicates the presence of a buffer size for logical channel group i. That is, LCG i When is set to "1", the buffer for logical channel group i size On the other hand, LCG i When set to "0", it indicates that the buffer size for logical channel group i is not reported. iThe length of the " area is 8 bits.
[0068] The "buffer size" field is the same as the "buffer size" field of the short BSR MAC CE when the MAC CE shown in Fig. 10(B) is a long BSR MAC CE. On the other hand, when the MAC CE shown in Fig. 10(B) is a preemptive BSR MAC CE, a predetermined buffer size is stored in the "buffer size field". The predetermined buffer size is the total amount of data expected to arrive at the IAB-MT of the IAB node 300 (IAB node 300-T in the case of Fig. 9) where the preemptive BSR is triggered, and does not include the total amount of data currently available in the IAB-MT.
[0069] In addition, the short BSR MAC CE in Fig. 10(A) represents the MAC CE of a short truncated BSR, and the long BSR MAC CE in Fig. 10(B) represents the MAC CE of a long truncated BSR.
[0070] The truncated BSR is a BSR that corresponds to padding bits (or padding data) that the MAC layer inserts when constructing a MAC PDU. If the padding bits are the same as the size of the short BSR with a subheader added, the MAC CE in Figure 10(A) is used. If the padding bits are larger than the size of the short BSR with a subheader added, the MAC CE in Figure 10(B) is used.
[0071] In the following, when there is no distinction between short BSR MAC CE and short truncated BSR MAC CE, it may be described as short BSR MAC CE. Also, when there is no distinction between long BSR MAC CE, preemptive BSR MAC CE, and long truncated BSR MAC CE, it may be described as long BSR MAC CE.
[0072] In the following, when there is no need to distinguish between preemptive BSR and legacy BSR, they may be referred to as "BSR."
[0073] In the first embodiment, an example is shown in which the IAB node 300 reports the buffer size of each logical channel group associated with the number of hops to a parent node.
[0074] Specifically, first, a donor base station (e.g., donor node 200) having first and second relay nodes under its control sets correspondence information indicating a correspondence relationship between the number of hops of a logical channel (LCH) and a logical channel group (LCG) to the first relay node (e.g., IAB node 300-T). Second, the first relay node transmits a buffer status report (BSR) to a second relay node (e.g., parent node 300-P) that is a parent node of the first relay node, based on the correspondence information. Third, the second relay node transmits an uplink grant (UL grant) to the first relay node based on the correspondence information and the buffer status report.
[0075] In this way, in the first embodiment, the number of hops of the LCH is linked to the LCG. The IAB node 300 uses the BSR to report the buffer size of the LCG linked to the number of hops to the parent node. Since the LCG is linked to the number of hops, the parent node can grasp the buffer size in the LCG as a buffer size corresponding to the number of hops. The parent node allocates uplink radio resources to the IAB node 300 using not only the buffer size but also the number of hops.
[0076] Therefore, the parent node can allocate more uplink radio resources to an IAB node 300 with a large delay (or a large number of hops) than to other nodes. This makes it possible to reduce delay and ensure fairness throughout the topology.
[0077] (Configuration example of the first embodiment) First, a configuration example of the first embodiment will be described. Fig. 12(A) is a diagram showing a configuration example of a cellular communication system 1 according to the first embodiment.
[0078] 12A, the donor node 200 has IAB nodes 300-P, 300-T, and 300-C under it. The topology (or network) constructed by the donor node 200 may include other IAB nodes.
[0079] The parent node of IAB node 300-T is IAB node 300-P. The child node of IAB node 300-T is IAB node 300-C. Hereinafter, IAB node 300-P may be referred to as parent node 300-P, and IAB node 300-C may be referred to as child node 300-C.
[0080] The upper node of the IAB node 300-T may be the parent node 300-P. Also, the upper node of the IAB node 300-T may be the donor node 200. Also, the parent node 300-P may be the donor node 200.
[0081] 12A shows an example in which the IAB node 300-T is connected to one parent node 300-P, but it may be connected to multiple parent nodes 300-P1, 300-P2, ... In this case, for example, the IAB node 300-T may be connected to parent nodes 300-P1 and 300-P2 by dual connectivity. A master cell group (MCG) in dual connectivity is set in the parent node 300-P1, and a secondary cell group (SCG) is set in the parent node 300-P2, so that the IAB node 300-T can be connected to the two parent nodes 300-P1 and 300-P2.
[0082] 12(A) shows an example in which child node 300-C is connected to IAB node 300-T, but instead of child node 300-C, UE 100 may be connected to IAB node 300-T. Also, both child node 300-C and UE 100 may be connected to IAB node 300-T. In the following, it is assumed that child node 300-C is connected to IAB node 300-T.
[0083] (Operation example of the first embodiment) Fig. 11 is a diagram showing an example of operation according to the first embodiment. The example of operation shown in Fig. 11 will be explained by appropriately using the configuration example of the cellular communication system 1 shown in Fig. 12(A).
[0084] As shown in FIG. 11, in step S10, the donor node 200 starts the process.
[0085] In step S11, the donor node 200 sets, to the IAB node 300-T (IAB-MT or IAB-DU), binding information in which an LCG is bound for each hop number. The binding information is classified according to the hop number of the LCH. For example, the binding information includes information such as the LCH hop number "2" is bound to LCG#8 to LCG#15, and the logical channel hop number "3" is bound to LCG#16 to LCG#32.
[0086] Here, the number of hops may be the total number of hops in the route to which the LCH belongs. Alternatively, the number of hops may be the number of hops in the LCH until the IAB node 300-T is reached. Alternatively, the number of hops may be the remaining number of hops from the IAB node 300-T to the donor node 200 in the LCH.
[0087] In this way, the linking information may be correspondence information that indicates the correspondence between the number of hops of the LCH and the LCG. Note that in the following, there are cases where the terms "link" and "correspond" are used interchangeably.
[0088] The CU of the donor node 200 may perform the setting by transmitting an RRC message including the binding information to the IAB-MT of the IAB node 300-T. Also, the CU of the donor node 200 may perform the setting by transmitting an F1AP message including the binding information to the IAB-DU of the IAB node 300-T.
[0089] The donor node 200 may also set the binding information in the parent node 300-P. In this case, the donor node 200 may perform the setting by transmitting an RRC message or an F1AP message including the binding information to the parent node 300-P in the same manner as described above. Alternatively, the binding information may be set in advance in the parent node 300-P as hard coding.
[0090] In step S12, the IAB-MT of the IAB node 300-T transmits a BSR to the parent node 300-P according to the setting. The BSR stores a buffer size for each LCG associated with a hop count. For example, the BSR stores the buffer size of LCG#8 corresponding to the hop count "2", the buffer size of LCG#9 corresponding to the hop count "2", ..., the buffer size of LCG#15 corresponding to the hop count "2", ..., the buffer size of LCG#16 corresponding to the hop count "3", .... Note that the BSR may be a legacy BSR as described above. Also, the BSR may be a preemptive BSR.
[0091] In step S13, the IAB-DU of the parent node 300-P uses the association information to identify the number of hops and the buffer state for each LCG in response to receiving the BSR. For example, when the parent node 300-P receives the buffer size of LCG#15 as the BSR, it uses the association information to identify that the buffer size for the number of hops corresponding to LCG#15 is "2".
[0092] In step S14, the IAB-DU of the parent node 300-P allocates uplink radio resources to the IAB-MT of the IAB node 300-T based on the association information and the BSR. Then, the parent node 300-P transmits a UL grant including the allocation information to the IAB node 300-T. For example, the IAB-DU of the parent node 300-P allocates more uplink radio resources to the IAB-MT of the IAB node 300-T in which data of an LCG with a larger number of hops than others is accumulated.
[0093] Then, in step S15, the series of processes ends.
[0094] (Modification of the first embodiment) Next, a modified example of the first embodiment will be described. The modified example of the first embodiment is an example in which multiple LCGs are assigned to one LCH for each hop number. Specifically, a first relay node (e.g., IAB node 300-T) identifies a logical channel group corresponding to the hop number of a packet received via a logical channel based on the correspondence information, and transmits a buffer status report including the buffer size of the logical channel group to a second relay node (e.g., parent node 300-P).
[0095] Fig. 12(B) is a diagram showing an operation example according to a modification of the first embodiment. The operation example shown in Fig. 12(B) will be explained by appropriately using the configuration example of the cellular communication system 1 shown in Fig. 12(A).
[0096] However, N UE bearers are mapped to one LCH (BH RLC channel) (1:N mapping), and each of the N UE bearers has a different route (number of hops) from the others.
[0097] When the binding information is set (step S11: same as in FIG. 11), the IAB node 300-T classifies packets received via an LCH (BH RLC channel) by the number of hops in step S120.
[0098] Here, the IAB node 300-T may check the number of hops, for example, as follows.
[0099] First, the number of hops may be obtained from the header of the received packet. If hop number information is stored in the BAP header of the received BAP packet, the IAB node 300-T (the IAB-DU of the IAB node 300-T) can confirm the number of hops by obtaining the hop number information from the BAP header.
[0100] Secondly, the number of hops may be obtained from the implementation of the IAB node 300-T. That is, the IAB-DU of the IAB node 300-T knows from which BH RLC channel a packet was received. Each time the IAB-DU of the IAB node 300-T receives a packet, it notifies the IAB-MT of the IAB node 300-T of which packet passed through which route. The IAB-MT of the IAB node 300-T may obtain the number of hops based on the information notified by the IAB-DU.
[0101] Then, in step S120, the IAB-MT of the IAB node 300-T identifies the LCG corresponding to the classified hop count based on the linking information, and calculates the buffer size for each LCG. The IAB-MT of the IAB node 300-T transmits a BSR including the calculated buffer size to the parent node 300-P.
[0102] The IAB node 300-T performs step S1 of 2 When the process is completed, the process from step S13 (FIG. 11) onwards is carried out in the same manner as in the first embodiment.
[0103] In the modification of the first embodiment, the IAB node 300-T identifies the LCG for each packet and calculates the buffer size, so that the IAB node 300-T can report the buffer size on a packet-by-packet basis to the parent node 300-P. The parent node 300-P can allocate more resources to the IAB node 300-T having a packet with a large delay than to the other nodes. This makes it possible to reduce delays and ensure fairness.
[0104] Second embodiment Next, a second embodiment will be described.
[0105] As shown in Figures 10(A) and 10(B), in 3GPP Release 16, the upper limit of the number of LCGs is 8 (e.g., Figure 10(B)) and the number of bits is 3 (e.g., Figure 10(A)). Hereinafter, the upper limit is represented as "X (Y bits)".
[0106] On the other hand, the upper limit of the number of LCHs for IAB-MT is up to 65,536 (16 bits). If the upper limit of the number of LCGs is secured to the same extent as the upper limit of the number of LCHs, the upper limit of the number of LCGs can also be set to 65,536 (16 bits). Consider a case where the number of LCGs is 65,536 (16 bits) for high-resolution scheduling. In such a case, when the IAB node 300 transmits 65,536 (16 bits) LCGs using the existing BSR MAC CE, the BSR shown in FIG. 10(B) is transmitted 8192 times.
[0107] However, this results in a large overhead.
[0108] Therefore, in the second embodiment, the upper limit value of the LCG can be set, and the IAB node 300-T reports the BSR to the parent node 300-P using the BSR MAC CE format corresponding to the set upper limit value of the LCG.
[0109] Therefore, the IAB node 300-T uses a BSR MAC CE of a fixed extension format and a BSR MAC CE of a variable extension format in addition to the existing BSR MAC CE format (FIGS. 10(A) and 10(B)). The IAB node 300-T selects (or determines) a MAC CE format that corresponds to the upper limit value of the LCG from among these MAC CE formats.
[0110] Specifically, first, a higher-level node (e.g., parent node 300-P or donor node 200) of a first relay node (e.g., IAB node 300-T) sets an upper limit value of a logical channel group to the first relay node. Second, the first relay node determines a MAC control element (CE) format corresponding to the upper limit value. Third, the first relay node transmits a buffer status report to a second relay node (e.g., parent node 300-P), which is a parent node of the first relay node, using the determined MAC control element format.
[0111] In this way, the IAB node 300-T can report the BSR using the BSR MAC CE corresponding to the upper limit value of the LCG, thereby eliminating the need to transmit the BSR multiple times, thereby enabling overhead reduction.
[0112] Next, specific examples of the BSR MAC CE in the fixed extension format and the BSR MAC CE in the variable extension format will be described.
[0113] Figures 13(A) and 13(B) are diagrams showing an example of the configuration of a BSR MAC CE in a fixed extended format according to the first embodiment. Both Figures 13(A) and 13(B) are diagrams showing an example in which the upper limit value of the LCG is 16 (4 bits). Of these, Figure 13(A) shows an example of a short BSR MAC CE in which the upper limit value of the LCG is 16 (4 bits). Also, Figure 13(B) shows an example of a long BSR MAC CE in which the upper limit value of the LCG is 16 (4 bits).
[0114] As shown in Fig. 13(A), when the upper limit of LCG is 16 (4 bits), the short BSR MAC CE has 4 bits in the "LCG ID" field to match the upper limit. This is one bit more than the short BSR MAC CE in Fig. 10(A). The "LCG ID" field stores the identification information of the logical channel group for which the buffer size is reported, which is the same as the existing short BSR MAC CE (Fig. 10(A)).
[0115] The "BS" field has 5 bits. The "BS" field, like the existing BSR MAC CE, stores the total amount of available data across all LCHs in the LCG according to a predetermined calculation procedure. After the "BS" field is "R" (reserved field).
[0116] As shown in Figure 13(B), the long BSR MAC CE has the LCG i " area is 16 according to the upper limit (LCG 0 ~LCG 15 ) exists. "LCG i The " field also stores a value indicating the presence of the LCGi buffer size, the same as that of the existing long BSR MAC CE. The "BS" field shown in FIG. 13(B) also stores a predetermined buffer size, the same as that of the existing long BSR MAC CE.
[0117] Figures 14(A) and 14(B) are diagrams showing examples of BSR MAC CE in a fixed extended format according to the second embodiment. Both Figures 14(A) and 14(B) show examples in which the upper limit value of LCG is 256 (8 bits). Of these, Figure 14(A) shows an example of a short BSR MAC CE in which the upper limit value of LCG is 256 (8 bits). Also, Figure 14(B) shows an example of a long BSR MAC CE in which the upper limit value of LCG is 256 (8 bits).
[0118] As shown in Figure 14 (A), when the upper limit of LCG is 256 (8 bits), the "LCG ID" field has 8 bits to match the upper limit. The "BS" field has 5 bits, and the rest is "R".
[0119] As shown in Fig. 14(B), when the upper limit of LCG is 256 (8 bits), i "There are 256 regions (LCG 0 ~LCG 255 )exist.
[0120] In this way, when the upper limit value of the LCG is set to 16 (4 bits), the IAB node 300-T decides to use the BSR MAC CE of FIG. 13(A) or FIG. 13(B), and when the upper limit value of the LCG is set to 256 (8 bits), the IAB node 300-T decides to use the BSR MAC CE shown in FIG. 14(A) or FIG. 14(B).
[0121] The upper limit is an example. When 32 (5 bits) is set as the upper limit, the IAB node 300-T uses a short BSR MAC CE with a 5-bit “LCG ID” field or a “LCG i In addition, if 64 (6 bits) is set as the upper limit, the IAB node 300-T may use a short BSR MAC CE with a 6-bit "LCG ID" or a short BSR MAC CE with a 6-bit "LCG ID" field. i It may be decided to use a long BSR MAC CE with 64 " regions.
[0122] The IAB node 300-T receives a short BSR MAC CE having an “LCG ID” field corresponding to the upper limit, or i It may be decided to use a long BSR MAC CE with a " field.
[0123] In addition, when reporting the buffer size of a specific LCG, the IAB node 300-T may decide to use the short BSR MAC CE, and when reporting the buffer sizes of multiple LCGs, may decide to use the long BSR MAC CE.
[0124] Fig. 15(A) and Fig. 15(B) are diagrams showing examples of variable extension formats according to the second embodiment. Of these, Fig. 15(A) shows an example of a short variable extension format for a short BSR MAC CE, and Fig. 15(B) shows an example of a long variable extension format for a long BSR MAC CE.
[0125] As shown in FIG. 15(A), the short variable extension format further includes an "LCG range" area.
[0126] The "LCG range" area stores bits corresponding to the upper limit of the LCG set in the IAB node 300-T. For example, if the upper limit of the LCG is "16 items (4 bits)", "00" is stored, if the upper limit of the LCG is "256 items (8 bits)", "01" is stored, if the upper limit of the LCG is "16,384 (14 bits)", "10" is stored, and if the upper limit of the LCG is "65,536 (16 bits)", "11" is stored.
[0127] The relationship between the upper limit value of the LCG and the bits stored in the "LCG range" area may be other than the above. Also, the number of bits stored in the "LCG range" area may be 3 or more, in accordance with the upper limit value of the LCG.
[0128] As shown in Fig. 15(A), the short variable extension format has an "LCG ID" area, but its bit length is variable according to the upper limit value of LCG. In other words, the "LCG ID" area in the (X) area in Fig. 15(A) can be moved from the top to the left in the (X) area on the drawing to match the upper limit value. This is combined with the "LCD ID" area (4 bits) outside the (X) area to form the "LCD ID" area.
[0129] For example, if the LCG upper limit is 256 (8 bits), the top two areas of the (X) area on the drawing and the two areas from the left of the second area from the top will be included in the "LCG ID" area. The "BS" area will also be left-justified following the "LCD ID" area, and the remaining area will become "R". Also, for example, if the LCG upper limit is 32 (5 bits), the left area of the topmost area of the (X) area on the drawing will be included in the "LCG ID" area.
[0130] In the example of Fig. 15(A), the "BS" field has 5 bits, but the "BS" field may have more than 5 bits.
[0131] 15B, the long variable extension format also includes an "LCG range" area. The "LCG range" area stores the upper limit value of the LCG, which is the same as the "LCG range" area of the short variable extension format.
[0132] In addition, "LCG i The "LCG" area is determined according to the upper limit of the LCG. i For example, if the upper limit of the LCG is 16 (4 bits), the number of LCG areas is set. 0 ~LCG 15 (m=15) i " area is set, and if there are 256 (8 bits), LCG 0 ~LCG 255 (m=255) up to 256 "LCG i " area is set.
[0133] The IAB node 300-T may arbitrarily use a fixed extension format (FIGS. 13(A) to 14(B)) or a variable extension format (FIGS. 15(A) and 15(B)).
[0134] Fig. 16 is a diagram showing an example of operation according to the second embodiment. The example of operation shown in Fig. 16 will be explained by appropriately using the example of the configuration of the cellular communication system 1 shown in Fig. 12(A).
[0135] As shown in FIG. 16, in step S30, the IAB node 300-T starts the process.
[0136] In step S31, the upper node (parent node 300-P or donor node 200) sets an upper limit value of the LCG to the IAB node 300-T. The upper limit value may be, for example, 8 (3 bits), 16 (4 bits), 32 (5 bits), ..., 256 (8 bits), ..., 16,384 (16 bits), ..., 65,536 (16 bits).
[0137] When the upper node is the parent node 300-P, the IAB-DU of the parent node 300-P may set the upper limit value of the LCG for the IAB-MT of the IAB node 300-T using a MAC CE, a BAP Control PDU, etc. When the upper node is the donor node 200, the CU of the donor node 200 may set the upper limit value of the LCG for the IAB-DU (or IAB-MT) of the IAB node 300-T using an F1AP message, an RRC message, etc.
[0138] When the upper node is the donor node 200, the donor node 200 may transmit the upper limit value of the LCG to the parent node 300-P. Alternatively, the IAB-MT of the IAB node 300-T, which has received the setting of the upper limit value of the LCG from the donor node 200, may transmit the upper limit value to the IAB-DU of the parent node 300-P.
[0139] In step S32, the IAB-MT of the IAB node 300-T determines (or selects) the MAC CE format to be used according to the set upper limit value. For example, when the upper limit value is 8, the IAB-MT of the IAB node 300-T selects an existing format (e.g., FIG. 10(A) or FIG. 10(B)). Also, when the upper limit value is 16 or more, the IAB-MT of the IAB node 300-T selects a fixed extension format (e.g., FIG. 13(A) to FIG. 14(B)) or a variable extension format (e.g., FIG. 15(A) or FIG. 15(B)).
[0140] In step S33, the IAB-MT of the IAB node 300-T transmits the legacy BSR and / or the preemptive BSR to the parent node 300-P using the determined format.
[0141] Then, in step S34, the IAB node 300-T ends the series of processes.
[0142] (Modification of the second embodiment) Next, a modified example of the second embodiment will be described. The modified example of the second embodiment is an example in which the upper limit value setting of the LCG is set to different values for the legacy BSR and the preemptive BSR. Specifically, a higher-level node (e.g., the parent node 300-P or the donor node 200) sets different upper limit values for the legacy BSR and the preemptive BSR to a first relay node (e.g., the IAB node 300-T).
[0143] This allows, for example, the IAB node 300-T to report buffer sizes according to different upper limits for the legacy BSR and the preemptive BSR. Specifically, for example, it is possible to meet a request to increase the upper limit of the LCG to increase the scheduling resolution, while allowing the upper limit of the preemptive BSR to be small.
[0144] Fig. 17 is a diagram illustrating an example of operation according to a modification of the second embodiment. The example of operation shown in Fig. 17 will be explained by appropriately using the example of the configuration of the cellular communication system 1 shown in Fig. 12(A).
[0145] As shown in FIG. 17, in step S40, a higher-level node (parent node 300-P or donor node 200) starts the process.
[0146] In step S41, the upper node sets the upper limit value of the LCG to different values for the legacy BSR and the preemptive BSR in the IAB node 300-T (IAB-MT or IAB-DU). Thereby, for example, the upper limit value of the LCG and the type of the BSR are linked and set. As in the second embodiment, when the upper node is the donor node 200, the setting may be performed using an F1AP message or the like. When the upper node is the parent node 300-P, the setting may be performed using a BAP Control PDU or the like.
[0147] In step S42, the IAB-MT of the IAB node 300-T determines (or changes) the MAC CE format to be used depending on the type of BSR. For example, when the upper limit value of LCG for the legacy BSR is 16 (4 bits), the IAB-MT of the IAB node 300-T selects the BSR MAC CE format of Fig. 13(A) or Fig. 13(B), and when the upper limit value of LCG for the preemptive BSR is 256 (8 bits), the IAB-MT of the IAB node 300-T selects the BSR MAC CE format of Fig. 14(A) or Fig. 14(B).
[0148] In step S43, the IAB-MT of the IAB node 300-T transmits the legacy BSR and the preemptive BSR using the determined MAC CE format.
[0149] Then, in step S44, the IAB node 300-T ends the series of processes.
[0150] Third embodiment Next, an example of the third embodiment will be described. The third embodiment is an example in which a legacy BSR and a preemptive BSR are transmitted by one BSR MAC CE.
[0151] Specifically, first, a higher-level node (e.g., parent node 300-P or donor node 200) of a first relay node (e.g., IAB node 300-T) sets an integrated buffer status report to the first relay node. Second, the first relay node transmits an integrated buffer status report, in which buffer sizes corresponding to logical channel groups classified by type of buffer status report are stored, to a second relay node (e.g., parent node 300-P) which is a parent node of the first relay node in accordance with the setting.
[0152] The integrated BSR MAC CE may be referred to as an integrated BSR. The integrated BSR stores, for example, LCG and the buffer size (BS) of each LCG, similarly to the legacy BSR (or preemptive BSR). When the integrated BSR reports the buffer size for one LCG, it may use a MAC CE in the same format as the short BSR MAC CE. When the integrated BSR reports the buffer sizes for multiple LCGs, it may use a MAC CE in the same format as the long BSR MAC CE.
[0153] This prevents the IAB node 300-T from transmitting a BSR in a different MAC CE format, making it possible to prevent, for example, processing delays.
[0154] Fig. 18 is a diagram illustrating an example of operation according to the third embodiment. The example of operation shown in Fig. 18 will be described by appropriately using the example of the configuration of the cellular communication system 1 shown in Fig. 12(A).
[0155] As shown in FIG. 18, in step S50, a higher-level node (parent node 300-P or donor node 200) starts the process.
[0156] In step S51, the upper node sets an integrated BSR to the IAB-MT of the IAB node 300-T. In this case, the upper node may set up a link between the LCG in the integrated BSR and the BSR type. For example, the link may be set up to indicate that LCG#0 to LCG#3 of the integrated BSR correspond to LCG#0 to LCG#3 of the legacy BSR, respectively, and that LCG#4 to LCG#7 of the integrated BSR correspond to LCG#0 to LCG#3 of the preemptive BSR, respectively.
[0157] When the upper node is the parent node 300-P, such an integrated BSR may be set using a BAP Control PDU, a MAC CE, or the like. When the upper node is the donor node 200, the integrated BSR may be set using an F1AP message, an RRC message, or the like. The donor node 200 may perform the setting for the parent node 300-P.
[0158] In step S52, the IAB-MT of the IAB node 300-T triggers the integrated BSR. The trigger may be a trigger condition of the legacy BSR. Also, the trigger may be a trigger condition of the preemptive BSR. For example, the IAB-MT of the IAB node 300-T may trigger the integrated BSR at the trigger timing of the legacy BSR. Also, the IAB-MT of the IAB node 300-T may trigger the integrated BSR at the trigger timing of the preemptive BSR. The upper node may set which of the two trigger conditions should trigger the integrated BSR in the IAB-MT of the IAB node 300-T.
[0159] In step S53, the IAB-MT of the IAB node 300-T identifies the buffer size (BS-L) of the legacy BSR and the buffer size (BS-P) of the preemptive BSR. Then, the IAB-MT of the IAB node 300-T stores these buffer sizes in the MAC CE of the integrated BSR in association with the LCG.
[0160] For example, the IAB node 300-T associates BS-L#0 to BS-L#3 with LCG#0 to LCG#3, respectively. Also, for example, the IAB node 300-T associates BS-P#0 to BS-P#3 with LCG#4 to LCG#7, respectively. Then, the IAB node 300-T stores BS-L#0 to BS-L#3 in the MAC CE of the integrated BSR, for example, as the buffer sizes of LCG#0 to LCG#3 of the integrated BSR. Also, the IAB node 300-T stores BS-P#0 to BS-P#3 in the MAC CE of the integrated BSR, for example, as the buffer sizes of LCG#4 to LCG#7 of the integrated BSR.
[0161] In step S54, the IAB-MT of the IAB node 300-T transmits the integrated BSR to the parent node 300-P.
[0162] Then, in step S55, the IAB node 300-T ends the series of processes.
[0163] (Fourth embodiment) Next, a fourth embodiment will be described.
[0164] (BH RLF Indication) In a network made up of multiple IAB nodes 300, a failure may occur in a backhaul link between the IAB nodes 300. Such a failure is called a "BH RLF (Backhaul Radio Link Failure)."
[0165] Fig. 19 is a diagram showing an example of a relationship between nodes according to the fourth embodiment. Fig. 19 also shows an example of a BH RLF according to the fourth embodiment. Fig. 19 shows an example in which a BH RLF occurs in BH link #1 between IAB node 300-P1, which is the parent node of IAB node 300-T, and node 500, which is the parent node of IAB node 300-P1.
[0166] Assume that the IAB-MT of the parent node 300-P1 detects a BH RLF. The IAB-DU of the parent node 300-P1 transmits a failure occurrence notification to the downstream IAB node 300-T.
[0167] A failure occurrence notification indicating that a BH RLF has been detected is called a Type 1 BH RLF Indication. The BH link RLF detected by a child node (parent node 300-P1 in the example of FIG. 19) may be a Type 1 BH RLF Indication.
[0168] Moreover, a recovery attempt notification indicating that recovery from a failure (BH RLF) that has occurred in a backhaul link is being attempted is called a Type 2 BH RLF Indication. In the example of Fig. 19, an example is shown in which parent node 300-P1 transmits a Type 2 BH RLF Indication to IAB node 300-T.
[0169] When there is no need to distinguish between Type 1 BH RLF Indication and Type 2 BH RLF Indication, they are referred to as Type 1 / 2 BH RLF Indication. Note that, in each embodiment, an example of Type 2 BH RLF Indication will be mainly described, but Type 2 BH RLF Indication may be read as Type 1 BH RLF Indication. As described above, Type 1 BH RLF Indication is transmitted when a BH RLF is detected, and Type 2 BH RLF Indication is transmitted when a recovery attempt is made. However, in IAB node 300, a BH RLF recovery attempt process is performed immediately after BH RLF detection, so Type 1 BH RLF Indication and Type 2 BH RLF Indication are substantially the same notification.
[0170] In addition, there is a recovery indication to indicate that the BH link has recovered from a BH RLF. Such a recovery indication is called Type 3 BH RLF Indication. In addition, there is a failure indication to indicate that the BH link has failed to recover from an RLF. Such a failure indication is called Type 4 BH RLF Indication.
[0171] 19, the IAB node 300-T that has received the Type 2 BH RLF Indication can perform various controls, the details of which will be described later.
[0172] In the following, Type 2 BH RLF Indication may be referred to as Type 2 Indication.
[0173] (local rerouting) As described above, in a network made up of a plurality of IAB nodes 300, a BH RLF may occur in a backhaul link between the IAB nodes 300.
[0174] In a multi-hop network in which a packet is forwarded in succession by a plurality of IAB nodes 300, a data packet can be forwarded to a destination IAB node 300 (or a donor node 200) via an alternative path. In the event of a line failure, forwarding a data packet using an alternative path may be referred to as local rerouting. Local rerouting is performed by ignoring the routing settings set by the donor node 200 and selecting an alternative path. Alternatively, local rerouting may be performed by selecting an alternative path from alternative path candidates set by the donor node 200.
[0175] (Conditional Handover) In a typical handover, the UE 100 reports the measurement values of the radio conditions of the serving cell and / or the neighboring cell to the gNB 200, and the gNB 200 determines a handover to the neighboring cell based on the report and transmits a handover command to the UE 100. For this reason, in a case where the radio conditions of the serving cell suddenly deteriorate, a typical handover may result in a communication interruption before the handover is executed.
[0176] In contrast, conditional handover can autonomously execute handover to a candidate cell that corresponds to a preset trigger condition when the trigger condition is satisfied, thus solving problems such as communication interruption that occur in general handover.
[0177] The execution condition of the conditional handover includes one or more trigger conditions. The configuration of the conditional handover includes a candidate cell and a trigger condition. The configuration of the conditional handover may include a plurality of combinations of the candidate cell and the trigger condition. The configuration of the conditional handover is performed, for example, by an RRC message from the CU of the donor node 200 to the IAB node 300 (the IAB-MT of the IAB node 300) and / or the UE 100.
[0178] (Control example of the fourth embodiment) For example, as shown in FIG. 19, consider a case where Dual Connectivity is set in the IAB node 300-T, and the IAB node 300-T is connectable to two parent nodes 300-P1 and 300-P2.
[0179] In this case, when the IAB node 300-T receives a Type 2 Indication from the parent node 300-P1, it can perform local rerouting and switch the connection destination to the parent node 300-P2. This allows the IAB node 300-T to transmit upstream packets to the destination node (donor node 200) by avoiding the BH link #1 where the failure has occurred, and allows the UE 100 to be provided with uninterrupted service.
[0180] However, consider a case where Dual Connectivity is not set for IAB node 300-T and IAB node 300-T is connected to only parent node 300-P1, and is in a single connection. In this case, even if IAB node 300-T receives a Type 2 Indication from parent node 300-P1, it cannot switch the connection to parent node 300-P1, and is in a state where it cannot do anything until it receives a Type 3 BH RLF Indication or a Type 4 BH RLF Indication.
[0181] Therefore, when the IAB node 300-T receives a Type 2 Indication from the parent node 300-P1, the IAB node 300-T is made capable of executing a conditional handover. Specifically, the IAB node 300-T switches the connection from the parent node 300-P1 to the parent node 300-P2 by the conditional handover. This enables the IAB node 300-T to transmit upstream packets to the destination node by avoiding the BH link #1, and to provide continuous service to the UE 100.
[0182] In this way, when the IAB node 300-T is capable of performing both local rerouting and conditional handover by triggering reception of a Type 2 Indication, the IAB node 300-T can select which one to perform when it receives a Type 2 Indication.
[0183] In this case, it is also possible to allow the IAB node 300-T to make such a selection by itself depending on its implementation.
[0184] However, the donor node 200 is a node that manages the entire topology, and has the ability to control the performance of the entire topology.
[0185] Therefore, in the fourth embodiment, the donor node 200 is allowed to set, for the IAB node 300-T, whether to execute local rerouting or conditional handover, triggered by reception of a Type 2 Indication.
[0186] Specifically, first, a donor base station (e.g., donor node 200) having a first and second relay node under its control sets local rerouting and conditional handover (CHO) to the first relay node (e.g., IAB node 300-T). Second, the first relay node receives a failure recovery notification from a second relay node (e.g., parent node 300-P1) which is the parent node of the first relay node, indicating that recovery from a failure that has occurred in a backhaul link (e.g., BH link #1) between the second relay node and the parent node (e.g., node 500) of the second relay node is being attempted. Third, the first relay node executes local rerouting or the conditional handover in response to the receipt of the failure recovery notification according to the setting. In such a case, the donor base station further sets to the first relay node whether to execute local rerouting or to execute conditional handover in response to the receipt of the failure recovery notification.
[0187] In this way, the donor node 200 sets the IAB node 300-T as to whether to perform local rerouting or conditional handover, making it possible to realize control that takes into account fairness across the entire topology.
[0188] (Operation example of the fourth embodiment) Fig. 20 is a diagram illustrating an example of operation according to the fourth embodiment. The example of operation will be described by appropriately using the configuration example shown in Fig. 19.
[0189] As shown in FIG. 20, in step S60, the donor node 200 starts the process.
[0190] In step S61, the CU of the donor node 200 sets up local rerouting and / or conditional handover to the IAB-MT of the IAB node 300-T. For example, the CU of the donor node 200 may use an RRC message to set up local rerouting and / or conditional handover.
[0191] In step S62, the CU of the donor node 200 sets the operation to be performed when a Type 2 Indication is received, to the IAB-MT of the IAB node 300-T. The operation setting is a setting regarding whether to perform local rerouting or conditional handover (or which to prioritize) when a Type 2 Indication is received.
[0192] Here, if "perform local rerouting" is set, the IAB node 300-T can forward packets to the parent node 300-P2 without performing setting processing for connection switching. Therefore, from a short-term perspective, there is an advantage in that the service can be continued without communication interruption.
[0193] On the other hand, when "perform conditional handover" is set, the IAB node 300-T performs setting processing related to connection switching, but can also reconstruct dual connectivity. Therefore, from a long-term perspective, there is an advantage in that the network load can be balanced and communication quality (throughput or latency) can be maintained.
[0194] In addition, the operation configuration may be configured, for example, by the CU of the donor node 200 to the IAB-MT of the IAB node 300-T using an RRC message.
[0195] In step S63, the IAB-MT of the IAB node 300-T receives a Type 2 Indication from the IAB-DU of the parent node 300-P1.
[0196] In step S64, the IAB-MT of the IAB node 300-T performs local rerouting or conditional handover according to the configuration.
[0197] In step S65, the IAB node 300-T ends the series of processes.
[0198] (Modification of the fourth embodiment) Next, a modified example of the fourth embodiment will be described. The modified example of the fourth embodiment is an example in which a rule is determined in advance, and the IAB node 300-T executes local rerouting or conditional handover according to the rule, triggered by reception of a Type 2 Indication.
[0199] Specifically, when a first relay node (e.g., IAB node 300-T) performs local rerouting or conditional handover, the first relay node performs local rerouting or conditional handover according to a preset rule.
[0200] Here, "pre-configured" means that, for example, when the IAB node 300-T is installed, it is configured (stored) in memory. The IAB-MT of the IAB node 300-T reads information related to the configuration from memory and executes it, triggering reception of a Type 2 Indication to execute local rerouting or conditional handover. Alternatively, it may be hard-coded in the specifications.
[0201] 21 is a diagram illustrating an example of an operation according to a modified example of the fourth embodiment. Steps S71 and S72 are the same as steps S61 and S63, respectively, of the fourth embodiment.
[0202] In step S72, the IAB node 300-T executes local rerouting or conditional handover according to a predetermined rule. The predetermined rule is, for example, as follows. That is, when the IAB node 300-T has a Dual Connectivity connection and a path (alternative path) for performing local rerouting exists, the IAB node 300-T executes local rerouting. Also, when the IAB node 300-T does not have a Dual Connectivity connection or a path (alternative path) for performing local rerouting does not exist, the IAB node 300-T executes conditional handover.
[0203] Then, in step S74, the IAB node 300-T ends the series of processes.
[0204] (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.
[0205] In addition, circuits that execute each process performed by UE 100, gNB 200, or IAB node 300 may be integrated, and at least a portion of UE 100, gNB 200, or IAB node 300 may be configured as a semiconductor integrated circuit (chip set, SoC (System on a chip)).
[0206] As used in this disclosure, the terms "based on" and "depending on" do not mean "based only on" or "depending only on," unless otherwise specified. The term "based on" means both "based only on" and "based at least in part on." Similarly, the term "depending on" means both "based only on" and "based at least in part on." Additionally, "obtain / acquire" may mean obtaining information from stored information, from information received from other nodes, or by generating information. The terms "include," "comprise," and variations thereof do not mean including only the items listed, but may include only the items listed, or may include additional items in addition to the items listed. Additionally, the term "or" as used in this disclosure is not intended to be an exclusive or. Additionally, any reference to elements using designations such as "first," "second," etc., as used in this disclosure is not intended to generally limit the quantity or order of those elements. These designations may be used herein as a convenient method of distinguishing between two or more elements. Thus, reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some manner. In this disclosure, where articles are added by translation, such as a, an, and the in English, these articles are intended to include the plural unless the context clearly indicates otherwise.
[0207] 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.
[0208] This application claims priority to U.S. Provisional Application No. 63 / 185,648 (filed May 7, 2021), the entire contents of which are incorporated herein by reference.
[0209] (Appendix 1) (Introduction) A revised work item on Enhancements to Integrated Access and Backhaul for NR (eIAB) has been approved in RAN#88e. Some of the main objectives are: Enhanced Topology Adaptation: Specification of procedures for inter-donor IAB node migration to enhance robustness and load balancing, including enhancements to reduce signaling load. Specification of enhancements to reduce service disruptions due to IAB node migration and BH RLF recovery. · Specification of enhanced 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.
[0210] Regarding topology, routing and transport enhancements, RAN2#113-e pointed out issues to be discussed in Rel-17, i.e. issues marked with "IF" for fairness, "IL" for delay or "IC" for congestion. In RAN2#113bis-e, possible solutions were discussed and only one agreement was reached: LCG range extended for IAB-MT. The size of LCG and BSR extensions require further discussion.
[0211] Appendix 1 discusses possible solutions to these problems, focusing on IL-4, IL-2, IL-3, IL-5, IL-6, IC-1, and IC-7. (Discussion) - Fairness across the entire topology - IF-4 IF-4 was designated as follows: · IF-4: The IAB node cannot provide more resources to BH RLC channels that aggregate more bearers and / or carry bearers with a higher load per bearer (i.e., the IAB node cannot provide more resources to BH RLC channels with a higher aggregate load).
[0212] According to the list, possible solutions for IF-4 are: · F1: The IAB node is configured with additional information by the CU. · F1-1: Related to the number of bearers in a particular BH RLC channel (actual number, average number, etc.). · F1-2: Related to the QoS of the bearer of a particular BH RLC channel. · F2: Additional information is added to the BAP header. · F2-1: Bearer ID. · F2-2: Bearer ID and hop count for a particular path. · F2-3: Number of UE DRBs in a particular BAP packet.
[0213] As for the F1 solutions, they are configured once i.e. provided together with the routing configuration. Therefore, they are simpler solutions that require less overhead and allow better "per RLC channel" scheduling. However, these solutions cannot be used for "per packet" prioritization of DL scheduling.
[0214] As for the F2 solutions, these are added to each BAP header, so that "per-packet" scheduling can be performed. However, it is clear that these solutions require more overhead in each BAP PDU compared to the F1 solution.
[0215] In terms of improving fairness, from a technical point of view, "per packet" scheduling is better than "per RLC channel" scheduling. These scheduling can be performed by the DL scheduler in the gNB (or IAB-DU). Meanwhile, for the UL, the LCP essentially provides "per RLC channel" scheduling. In this sense, it may not be necessary to do "per packet" scheduling only for DL, considering the additional overhead of all BAP PDUs in DL and UL. Therefore, a simple solution, namely the F1 solution, is more suitable to improve fairness across Rel-17 topologies.
[0216] Proposal 1: RAN2 needs to agree with the IAB donor to configure the IAB node with the number of bearers mapped to each BH RLC channel and the QoS of these bearers, i.e., use F1-1 and F1-2 to resolve IF-4.
[0217] - Multi-hop delay - IL-2 IL-2 was designated as follows: ·IL-2: Due to the current (Rel-16) limitation on the number of LCGs, IAB nodes may need to report joint buffer status for LCHs with significantly different QoS requirements.
[0218] A possible solution for IL-2 is as follows: · L4: A new behavior or function is specified for the IAB node. · L4-3: The number of LCGs in IAB-MT is increasing.
[0219] In RAN2#113bis-e, RAN2 "agreed to extend the LCG range for IAB-MT. The size of LCG and extension of BSR are subject to further study." According to the current specification, the current LCG space is 8 (i.e., maxLCG-ID is 7), which is common to UE and IAB-MT. For UE, the current LCH ID space is 32 (i.e., maxLC-ID). For IAB-MT, the maximum number of BH LCH IDs (i.e., maxLC-ID-Iab-r16) is 65,855, while the BH LCH ID space (i.e., BH-RLC channel ID-r16) is 65,536 (16 bits). If the same ratio is applied to the UE (i.e., LCG:LCH=1:4), 16,384 LCGs (14 bits) may be required for IAB-MT. This is certainly feasible, but may be a bit large to add to the MAC CE. Some companies have proposed expanding the LCG space to at least 16 (4 bits) or even 256 (8 bits), so RAN2 needs to consider what is best for the expanded LCG space.
[0220] Proposal 2: RAN2 needs to discuss optimal maximum numbers for the extended LCG space: 16 (4 bits), 256 (8 bits), 16,384 (14 bits), and even 65,536 (16 bits).
[0221] IL-3 IL-3 was designated as follows: IL-3: Preemptive BSR buffer size calculations are left to the implementation in Rel-16 and may vary from vendor to vendor.
[0222] A possible solution for IL-3 is as follows: · L4: A new behavior or function is specified for the IAB node. · L4-1: Buffer size calculation for preemptive BSR is specified.
[0223] For traditional BSR, the buffer size calculation is clearly specified. It is based on the data available for MAC, RLC, and PDCP. For RLC and PDCP, the data volume calculation procedures are specified in their respective specifications. In Rel-16, these mechanisms are reused for data volume calculation for IAB-MT preemptive BSR.
[0224] However, IAB nodes have a BAP layer instead of PDCP, and the BAP specification does not include data volume calculations. Therefore, the current specification lacks data available for transmission. To better schedule fairness across the topology, the buffer sizes reported by legacy BSRs need to be more accurate.
[0225] Observation 1: The lack of a procedure for data that can be sent in a BAP makes legacy BSR and preemptive BSR inaccurate.
[0226] In Rel-16, the calculation of the buffer size for preemptive BSR is highly dependent on the IAB-DU implementation, but the spec states that "The buffer size field specifies the total amount of data expected to arrive at the IAB-MT of the node for which preemptive BSR is triggered, and does not include the amount of data currently available at the IAB-MT." and As pointed out, some IAB nodes may report larger buffer sizes in preemptive BSR than actually arrive. It may be difficult to set up the same principle between child and parent nodes. For example, in multi-vendor deployments, this may lead to inefficient radio resource allocation, scheduling delays at parent nodes, and unfair resource requests between IAB-MTs. It may be more ambiguous when IAB nodes are configured with dual connectivity. Therefore, the buffer size calculation for preemptive BSR needs to be specified more precisely. One issue is that the buffer size calculation is not specified for IAB-DU, i.e. data buffered at the receiving side (MAC and RLC) of IAB-DU.
[0227] Observation 2: There is no buffered data procedure in the IAB-DU MAC and RLC receivers, so the amount of data reported in a Rel-16 preemptive BSR is up to the IAB-DU implementation.
[0228] Proposal 3: RAN2 needs to agree to specify the buffer size calculation for preemptive BSR (and possibly legacy BSR), i.e., using L4-1 to solve IL-3.
[0229] Another problem is that it is unclear from the parent node's perspective when the preemptive BSR is triggered. The MAC specification specifies two conditions as follows: This means that the trigger condition is up to the IAB-MT implementation in Rel-16. The parent node cannot accurately predict when data will actually be available for transmission, resulting in an inappropriate UL grant.
[0230] If configured, a preemptive BSR may be triggered for the specific case of IAB-MT if any of the following events occur: -UL grant is provided to a child IAB node or UE. -The BSR is received from a child IAB node or UE.
[0231] One simple solution is that the IAB node is configured to trigger the preemptive BSR either by sending a UL grant or by receiving a BSR. It is easy to configure it by the IAB donor, but the preemptive BSR is actually used by the parent node's IAB-DU, i.e., the scheduler. Therefore, at this point, it is necessary to consider further whether the trigger condition is configured by the IAB donor or dictated by the parent IAB node.
[0232] Proposal 4: RAN2 needs to agree that the triggers used for preemptive BSR are configured in the IAB node. Whether this is done by the IAB donor or its parent IAB node needs further study.
[0233] IL-5 and IL-6 IL-5 was designated as follows: · IL-5: The CU cannot place bearers with low PDB on routes with low congestion risk (high resource efficiency) or on RLF-free routes.
[0234] A possible solution for IL-5 is as follows. · L3: Additional signaling is introduced from the IAB node to the CU. ·L3-1: IAB node buffer / link status is shared with CU. L3-2: Delay measurements for each individual hop per BH RLC channel are shared with the CU. · L4: A new behavior or function is specified for the IAB node. · L4-2: Local rerouting is allowed for purposes other than RLF (e.g., based on the delay of the outgoing link). · F4: Additional signaling is introduced from the IAB node to the CU. · F4-1: BH Related to the load information for each RLC channel. · F4-2: Related to per-hop delay and per-hop packet loss on individual links.
[0235] IL-6 was designated as follows: ·IL-6: CU cannot configure routing based on actual (real-time) delay per BH RLC channel.
[0236] A possible solution for IL-6 is as follows: · L3: Additional signaling is introduced from the IAB node to the CU. L3-2: Delay measurements for each individual hop per BH RLC channel are shared with the CU. · F4: Additional signaling is introduced from the IAB node to the CU. · F4-2: Related to per-hop delay and per-hop packet loss on individual links. · L4: A new behavior or function is specified for the IAB node. · L4-2: Local rerouting is allowed for purposes other than RLF (e.g., based on the delay of the outgoing link).
[0237] The possible solution of IL-5 and IL-6 may have commonality with respect to additional signaling from the IAB node to the IAB donor, i.e., L3 and L4, which could be considered as a type of MDT and / or SON procedure, since it allows for centralized optimization.
[0238] Regarding L3-1, the current specification can be considered as allowing IAB nodes to share some buffer / link status with IAB donors, e.g., through RESOURCE STATUS UPDATE in F1-AP and measurement reporting framework in RRC. It can be seen as being possible to share Therefore, it is unclear what additional information needs to be reported to the CU.
[0239] Regarding L3-2 and F4-2, these solutions can be used generically for both IL-5 and IL-6 and can be considered the same from the latency measurement point of view. Existing L2 measurements specify "UL PDCP packet average latency per DRB per UE", but it is clear that PDCP packet average latency cannot be applied to IAB nodes. Therefore, it is expected that new L2 measurements will be required for the BAP layer.
[0240] Proposal 5: RAN2 needs to agree that IAB nodes report per-hop delay measurements to the IAB donor, i.e., use L3-2 to resolve IL-5 and IL-6.
[0241] Regarding L4-2, RAN2 has already agreed that "local rerouting can be triggered using a Type 2 RLF indication" and "local rerouting can be triggered by per-hop flow control indications", so there is no need to further discuss this issue in this agenda item; details of local rerouting can be discussed in other agenda items on enhanced topology adaptation.
[0242] Observation 3: Local rerouting for other purposes, i.e., L4-2, is discussed under Enhanced Topology Adaptation.
[0243] - Easing congestion - IC-1 and IC-7 IC-1 and IC-7 were designated with the following annotations: R2 concluded that there was sufficient interest among businesses to address two issues: · IC-1: It is not possible to mitigate long-term downstream congestion on a single link using existing Rel-16 DL HbH flow control mechanisms without relying on packet dropping. · IC-7: The CU (which is not aware of the local congestion state) cannot update the routing path that is experiencing congestion. Both IC-1 and CI-7 are associated with RAN3. It is not currently clear to what extent RAN2 will address this, as RAN3 appears to be addressing it as well.
[0244] RAN3 has discussed the symptoms of congestion and has agreed that: CP-based congestion indications may include reporting the following: By BAP Routing ID and / or Links for each child node and / or BH RLC CH ID (Down-selection requires further consideration). The CP-based congestion indication reuses the F1APGNB-DU status indication procedure. The CP-based congestion indication is related to DL congestion. For a UP-based approach to IAB congestion mitigation, we consider two options: No feature enhancements. Packet marking based approach.
[0245] Once the IAB donor receives a congestion indication from an IAB node, it can assume that it can avoid paths that experience congestion as implied in the RAN2 agreement above. There are several ways to address this issue: the IAB donor can update its routing configuration or direct local rerouting. In the latter case, RAN2 may be involved in how the congestion indication is used. In either case, RAN2 must wait for RAN3 to make a decision.
[0246] Finding 4: RAN2 may be involved in how IAB donors behave due to congestion indications after RAN3 has detailed them.
[0247] (Appendix 2) (introduction) A revised work item on NR Integrated Access and Backhaul Enhancements (eIAB) was approved in RAN#88e. Some of the objectives are to: Enhanced Topology Adaptation: Specification of procedures for inter-donor IAB node migration to enhance robustness and load balancing, including enhancements to reduce signaling load. - Specification of extensions to reduce service interruptions due to IAB node migration and BHRLF recovery. · Specification of enhanced 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.
[0248] In addition to the current agreement, Appendix 2 discusses various topics of Rel-17eIAB topology adaptation enhancements, namely BH RLF indication enhancements, conditional handover enhancements, and local rerouting enhancements.
[0249] (Discussion) BH RLF indication enhancements: In the Rel-16 email discussion, four types of BH RLF notifications were discussed, as shown in Figure 22.
[0250] Finally, only Type 4 "Recovery Failure" was specified as a BH RLF indication in Rel-16, which allows a child IAB-MT to recognize an RLF on its parent node's BH link and initiate an RLF recovery procedure.
[0251] Observation 1: Only Type 4 “Recovery Failure” was designated as a BH RLF indication in Rel-16.
[0252] Regarding the enhancements to Rel-17, RAN2 agreed to introduce Type 2 "Recovery Attempt" and Type 3 "BH Link Recovery", but the detailed IAB node operation still requires further study.
[0253] RAN2#113-e: RAN2 supporting Type 2 / 3 RLF indication (details require further study). Type 2 RLF indication can be used to trigger local re-routing. Type 2 RLF indication can be used to trigger deactivation of IAB supported in SIB. Type 2 RLF indication can be used to trigger deactivation or reduction of SR and / or BSR transmissions.
[0254] RAN2#113bis-e: Further consideration is required if other CHO execution conditions are required (e.g., whether a Type 2 RLF indication can be used as a trigger).
[0255] One thing under further consideration is whether / how to specify behavior related to three possible use cases for the new BHR LF indications that RAN2 has already agreed upon.
[0256] Regarding the triggering of local rerouting, since the BH RLF occurs on the UL from the perspective of the IAB node receiving the Type-2 BH RLF indication, the trigger needs to enable upstream local rerouting, i.e., UL path switching. In other words, downstream local rerouting is independent of the Type-2 BH RLF indication, since the IAB node receiving the Type-2 BH RLF indication can maintain a good BH link with the downstream node. Therefore, it can be considered as an IAB-MT behavior that needs to be clearly specified.
[0257] Proposal 1: RAN2 needs to agree to specify that IAB-MT triggers local rerouting on the upstream path when it receives a Type 2 BH RLF indication from a parent node.
[0258] Proposal 2: RAN2 should agree to specify that when the IAB-MT receives a Type 3 BH RLF indication from its parent node, it will stop local rerouting on the upstream path, i.e., revert to the configured "normal" routing.
[0259] Regarding the deactivation of the IAB-Support IE in SIB1, this can be considered as the widely-considered behavior of the IAB-DU until its implementation in Rel-16. Therefore, specifying it only in stage 2 is probably sufficient. In particular, it can be assumed that the IAB-DU will not remove the IAB-Support IE from SIB1 if there are still alternative routes to the donor. This needs to be made clear if the behavior is specified.
[0260] Proposal 3: RAN2 should consider whether to remove the IAB-Support IE from SIB1 when the IAB-DU receives a Type 2 BH RLF indication only in Stage 2 and there is no alternative route to the IAB donor.
[0261] According to the above RAN2 agreement, whether proposal 3 can be agreed or not, if the IAB-Support IE is not in SIB1, the IAB-MT will not initiate connection establishment to the parent node. One question is whether the UE is allowed to access the cell (i.e. the parent node) even if the parent node is under BH RLF. The RRC setup request will not be able to reach the CU, i.e. the donor, which will ultimately have a negative impact on the user. To avoid this, the cell has the option to forbid the UE access, stop SSB transmission, or broadcast a type 2 BH RLF indication over SIB1. As in proposal 3, if the IAB node has an alternative route to the donor, there is no need to remove the IAB-Support IE from SIB1.
[0262] Proposal 4: RAN2 should consider whether to prohibit UE access in addition to IAB-MT access when the IAB-DU receives a Type 2 BH RLF indication and there is no alternative route to the IAB donor.
[0263] Regarding deactivation or reduction of SR and / or BSR transmission, it needs to be clearly specified, since it may be considered as an IAB-MT behavior. Regarding deactivation or reduction, "deactivation" may be easier from the specification point of view. However, SR and / or BSR can only be transmitted after receiving Type 3, which may cause scheduling delays. On the other hand, "reduction" may allow scheduling to resume immediately after the BH link is restored, although it may cause unnecessary interference. Therefore, it needs to be discussed whether RAN2 supports "deactivation", "reduction", or both of SR and / or BSR. If both are supported, it needs to be configurable by the IAB donor. Furthermore, it is unclear how SR and / or BSR reduction should be handled if "reduction" is supported. It is conceivable to reuse the prohibition timer concept, but further consideration is required at this point.
[0264] Proposal 5: RAN2 needs to agree to specify that IAB-MT deactivates or reduces SR and / or BSR transmissions when it receives a Type 2 BH RLF indication from a parent node.
[0265] Proposal 6: RAN2 needs to agree to specify that the IAB-MT may resume normal procedures of SR and / or BSR transmission when it receives a Type 3 BH RLF indication from its parent node.
[0266] Proposal 7: RAN2 should consider whether to support "deactivation", "reduction", or both (i.e., configurable) of SR and / or BSR when a Type 2 BH RLF indication is received from a parent node.
[0267] Another thing under further consideration is whether the CHO will be triggered by the receipt of a Type 2 BH RLF indication. With a Type 2 BH RLF indication sent, the parent node has experienced a BH RLF and is attempting to recover the BH link. This, needless to say, means that the IAB node will not be able to communicate with the donor. If the IAB node is configured with dual connectivity, it may choose to perform local rerouting between the MCG and SCG, as in Proposal 1.
[0268] However, an IAB node with only one connection cannot do anything and must wait for either the parent node's BH recovery or for receiving a Type 4 BH RLF indication. Obviously, that would cause a long service interruption and negative impact to users. Therefore, an IAB node needs the option to trigger a CHO when it receives a Type 2 BH RLF indication. Furthermore, as a further optimization, it is worth considering whether an IAB node should cancel the CHO execution if it receives a Type 3 BH RLF indication before it actually executes the CHO.
[0269] Proposal 8: RAN2 needs to agree to specify that IAB-MT triggers CHO when it receives a Type 2 BH RLF indication from its parent node.
[0270] Proposal 9: RAN2 should consider whether to cancel CHO execution (if possible) when IAB-MT receives a Type 3 BH RLF indication from its parent node.
[0271] If both Proposal 1 and Proposal 8 can be agreed upon, i.e., for an IAB node configured with dual connectivity, local rerouting and CHO simultaneously, it can choose whether to trigger local rerouting or CHO when it receives a Type 2 BH indication. For example, local rerouting on receipt of Type 2 helps to avoid service interruptions, while CHO on receipt of Type 2 is better for long-term / topology-wide performance. Since local rerouting and CHO are triggered by conditions other than Type 2 receipt, it is assumed that they are primarily configured for different purposes, such as robustness of handover on event A3.
[0272] In this case, there are several options: either the IAB node implementation or the IAB donor configuration. Given that the donor is the node that manages the overall topology goals, it needs to be able to control the performance of the topology, so the choice of local rerouting or CHO on Type 2 reception needs to be configurable by the donor, rather than being left to the IAB node implementation.
[0273] Proposal 10: If both Proposal 1 and Proposal 8 can be agreed upon, RAN2 needs to further agree that the IAB donor can configure the IAB node to trigger local rerouting or CHO due to receiving a Type 2 BH RLF indication.
[0274] It is necessary to explain how to implement the new BH RLF indications in the specification. It seems that Type 2 and Type 3 BH RLF indications can be easily transmitted via BAP control PDUs, similar to the case of Type 4 BH RLF indication in Rel-16. As with Proposal 3 above, the UE cannot receive BAP control PDUs, so there is no BAP layer. Therefore, it is possible that these BH RLF indications are broadcast via SIB1, which is encoded by the DU. Therefore, RAN2 needs to consider whether they are transmitted via BAP control PDUs or SIB1.
[0275] Proposal 11: RAN2 needs to discuss whether Type 2 and Type 3 BH RLF indications are sent via BAP control PDU or SIB1.
[0276] (Conditional handover enhancements) Conditional Handover (CHO) was introduced in Rel-16 to improve mobility robustness. CHO can be used for designated Rel-16 IABs. RAN2#113-e and RAN2#113-e have reached the following agreement: Therefore, it is worth considering the CHO extension for eIAB in addition to Rel-16 CHO.
[0277] RAN2#113-e: RAN2 will discuss CHOs and will start with the discussion of CHOs within donors until RAN3 will proceed with the discussion of IAB node transfer between donors. RAN2 confirms the intent that Rel-16 CHO will / can be used for IAB-MT (further consideration is required as to whether any changes are necessary). RAN2 assumes that the Rel-16 specifications are the baseline for configuration of default route, IP address, and target path for intra-donor CHO.
[0278] RAN2#113bis-e: The use cases for IAB-MT CHO should be migration and RLF recovery. RAN2 requires a common solution for intra-CU / intra-DU CHO and intra-CU / inter-DU CHO. CHO event A3 and CHO event A5 are applicable to IAB-MT. Further consideration is required if other CHO execution conditions are required (e.g., whether a Type 2 RLF indication can be used as a trigger).
[0279] If Proposal 8 in the previous section can be agreed upon, it is possible that all CHO candidates (i.e., candidate cells) can trigger CHO simultaneously, since it does not depend on CHO event A3 / A5 but is a kind of mandatory trigger by Type 2 BH RLF indication.
[0280] According to the current specification, "If multiple NR cells are triggered for a conditional reconfiguration execution, it is up to the UE implementation to select which one. The UE shall select one of the triggered cells for the execution, taking into account the beam and beam quality." This is primarily targeted at the UE.
[0281] Observation 2: In Rel-16 CHO, when multiple candidate cells trigger CHO execution, it is up to the UE implementation to select which cell to use.
[0282] Regarding IAB-MT, it may not always be the best approach for IAB-MT to select one of the triggered cells by implementing it depending on the local radio quality. This is because the topology-wide goal may be effectively handled by the IAB donor as discussed in RAN2#112-e. Therefore, RAN2 needs to consider how IAB donor-controlled CHO execution with additional trigger conditions could work as in proposal 8. For example, the IAB donor could set priority information associated with the CHO candidate in the CHO configuration. The IAB-MT should select the most prioritized cell from all triggered CHO candidates that meet a certain radio quality (e.g., S criterion).
[0283] Proposal 12: RAN2 should consider whether an IAB donor-controlled CHO execution is required as an additional enhancement when all candidate cells trigger CHO upon receipt of a Type 2 BH RLF indication.
[0284] (Local rerouting enhancements) In Rel-16, local rerouting is only allowed if a BH RLF occurs. 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 the case of a BH RLF, the transmitting part of the BAP entity may reroute to an alternative path any BAP data PDUs that have not been acknowledged by lower layers before the BH RLF.
[0285] RAN2#113-e achieved the following agreements related to enhancing local rerouting capabilities: A Type 2 RLF indication can be used to trigger local rerouting. Local rerouting can be triggered by indicating per-hop flow control. Details such as trigger information, trigger conditions, and the role of CU settings require further study. RAN2 considers inter-donor DU local rerouting to be in scope.
[0286] However, the details of local rerouting are still unclear, at least from a configuration perspective. As agreed in RAN2#112-e, In Rel-17, we will discuss other cases (i.e., not limited to BH RLF) in RAN2, including benefits to central route decisions, as well as how topology-wide goals can be addressed. Therefore, the Rel-16 problem needs to be considered from an objective perspective of the entire topology. Needless to say, the IAB donor is the entity that handles the purpose of the entire topology, since it has complete knowledge and complete control of the IAB topology.
[0287] Observation 3: The IAB donor is the most appropriate entity to ensure the objectives of the entire topology.
[0288] 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.
[0289] Observation 4: In Rel-16 local rerouting, it is up to the IAB-MT implementation to decide which path is selected as the alternative path.
[0290] Therefore, the controllability of the IAB donor should become more important if local rerouting is extended beyond the BH RLF case. It is easy for the IAB donor to set up an alternative path. This requires that the IAB node select an alternative path when performing local rerouting. Modeling the alternative path requires further study, e.g., whether the alternative path has the same routing ID.
[0291] Proposal 13: RAN2 should consider whether IAB donors can configure IAB nodes with alternative paths in addition to the Rel-16 routing configuration.
[0292] Another aspect of IAB donor controllability needs to be considered: the IAB donor is aware of local rerouting and can start / stop local rerouting at IAB nodes to make the local rerouting and topology-wide goals coexist. For example, the IAB donor can consider whether the topology-wide goal is still achieved based on the knowledge of which IAB nodes are currently performing local rerouting. If the IAB donor realizes that the topology-wide goal cannot be achieved, the IAB donor can instruct the IAB nodes to start / stop local rerouting or the IAB donor may change the routing configuration of the entire IAB topology.
[0293] How local rerouting handles topology-wide goals is up to the IAB donor implementation, but the IAB donor may require information and control over the local decisions of IAB nodes.
[0294] Proposal 14: RAN2 should consider whether IAB nodes should notify IAB donors when local rerouting starts / stops.
[0295] Proposal 15: RAN2 needs to discuss whether an IAB donor can instruct an IAB node to start / stop local rerouting.
Claims
1. A communication control method for use in a cellular communication system, comprising: A host node of a first relay node sets a setting value related to a logical channel group to the first relay node; The first relay node determines a Medium Access Control (MAC) control element (CE) format corresponding to the setting value; the first relay node transmits a buffer status report to a second relay node that is a parent node of the first relay node, using the MAC control element format; A communication control method comprising the steps of:
2. The set value is a setting of an upper limit value of the logical channel group. The communication control method according to claim 1.
3. The MAC control element, for a long buffer status report or a preemptive buffer status report, i (L.C.G. i ) area The communication control method according to claim 2.
4. The MAC control element includes an extended Logical Channel Group ID (LCG ID) field for a Short Buffer Status Report (Short BSR). The communication control method according to claim 3.
5. The extended logical channel group ID field is 4 bits or more, and the extended logical channel group i The area is 16 bits or more.
5. The communication control method according to claim 3 or 4.
6. The MAC control element further includes an LCG range area in which the upper limit value is stored.
5. The communication control method according to claim 3 or 4.
7. Setting the upper limit value includes setting, by the upper node to the first relay node, different upper limit values for a legacy buffer status report and a preemptive buffer status report. The communication control method according to claim 2.
8. A communication control method for use in a cellular communication system, comprising: A donor node having a first relay node and a second relay node which is a parent node of the first relay node under the donor node sets correspondence information indicating a correspondence relationship between a hop number of a logical channel (LCH) and a logical channel group (LCG) to the first relay node; The first relay node transmits a Buffer Status Report (BSR) to the second relay node based on the corresponding information; and and transmitting an uplink grant (UL grant) to the first relay node based on the correspondence information and the buffer status report. Communications control method.
9. and transmitting the correspondence information to the second relay node. The communication control method according to claim 8.
10. The transmitting of the buffer status report includes the first relay node specifying the logical channel group corresponding to the number of hops of the packet received via the logical channel based on the correspondence information, and transmitting the buffer status report including a buffer size of the logical channel group to the second relay node. The communication control method according to claim 8.
11. A communication control method for use in a cellular communication system, comprising: A higher-level node of a first relay node sets an integrated buffer status report to the first relay node; the first relay node transmits, in accordance with the setting, the integrated buffer status report in which buffer sizes corresponding to logical channel groups classified by type of the integrated buffer status report are stored, to a second relay node that is a parent node of the first relay node; A communication control method comprising the steps of:
12. A communication control method for use in a cellular communication system, comprising: A donor node having a first relay node and a second relay node that is a parent node of the first relay node under its control performs local rerouting and conditional handover (CHO) settings to the first relay node; receiving, from the second relay node, a failure recovery notification indicating that a failure occurring in a backhaul link between the second relay node and a parent node of the second relay node is being attempted to be recovered from the failure; the first relay node performs the local rerouting or the conditional handover in response to receiving the failure recovery notification; A communication control method comprising the steps of:
13. The method further includes: the donor node, in response to receiving the failure recovery notification, configuring the first relay node to perform the local rerouting or the conditional handover. The communication control method according to claim 12.
14. Performing the local rerouting or the conditional handover includes the first relay node triggering the local rerouting or the conditional handover according to a preset rule. The communication control method according to claim 12.
15. A first relay node, comprising: a receiving unit that receives a setting value related to a logical channel group from an upper node of a first relay node; a control unit that determines a Medium Access Control (MAC) control element (CE) format corresponding to the setting value; a transmission unit that transmits a buffer status report to a second relay node that is a parent node of the first relay node, using the MAC control element format. A first relay node.
16. A first relay node, comprising: a receiving unit that receives correspondence information indicating a correspondence relationship between a hop number of a logical channel (LCH) and a logical channel group (LCG) from a donor node having the first relay node and a second relay node that is a parent node of the first relay node under the donor node; a transmitter for transmitting a Buffer Status Report (BSR) to the second relay node based on the correspondence information; a receiving unit for receiving an uplink grant (UL grant) based on the corresponding information and the buffer status report from the second relay node. A first relay node.
17. A first relay node, comprising: A receiving unit that receives information for setting an integrated buffer status report from an upper node of a first relay node; a transmitting unit that transmits the integrated buffer status report, in which buffer sizes corresponding to logical channel groups classified by type of the integrated buffer status report are stored, to a second relay node that is a parent node of the first relay node in accordance with the setting information. A first relay node.
18. A first relay node, comprising: receiving information for setting local rerouting and conditional handover (CHO) from a donor node having a first relay node and a second relay node that is a parent node of the first relay node; a receiving unit that receives, from the second relay node, a failure recovery notification indicating that a recovery from a failure that has occurred in a backhaul link between the second relay node and a parent node of the second relay node is being attempted; a control unit that executes the local rerouting or the conditional handover in response to receiving the failure recovery notification. A first relay node.
19. A processor for controlling a first relay node, comprising: A process of receiving a setting value related to a logical channel group from an upper node of a first relay node; determining a Medium Access Control (MAC) control element (CE) format corresponding to the set value; and transmitting a buffer status report to a second relay node, which is a parent node of the first relay node, using the MAC control element format. Processor.
20. A processor for controlling a first relay node, comprising: receiving correspondence information representing a correspondence relationship between a hop count of a logical channel (LCH) and a logical channel group (LCG) from a donor node having the first relay node and a second relay node that is a parent node of the first relay node under the donor node; transmitting a Buffer Status Report (BSR) to the second relay node based on the correspondence information; receiving an uplink grant (UL grant) from the second relay node based on the correspondence information and the buffer status report. Processor.
21. A processor for controlling a first relay node, comprising: A process of receiving information for setting an integrated buffer status report from an upper node of a first relay node; and transmitting the integrated buffer status report, in which buffer sizes corresponding to logical channel groups classified by type of the integrated buffer status report are stored, to a second relay node that is a parent node of the first relay node in accordance with the setting information. Processor.
22. A processor for controlling a first relay node, comprising: A process of receiving information for setting local rerouting and conditional handover (CHO) from a donor node having a first relay node and a second relay node that is a parent node of the first relay node; receiving, from the second relay node, a failure recovery notification indicating that a recovery from a failure occurring in a backhaul link between the second relay node and a parent node of the second relay node is being attempted; In response to receiving the failure recovery notification, a process of performing the local rerouting or the conditional handover is performed. Processor.
Citation Information
Patent Citations
Communication control method
WO2020196201A1
Communication control method
WO2021065763A1
