Communication control method, relay node, processor, program, and system
The method enhances IAB node recovery from wireless backhaul failures by transmitting failure information and using dynamic cell selection, reducing data loss and delays in mobile communication systems.
Patent Information
- Application Number
- JP2024135437
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2020-08-06
- Filing Date
- 2024-08-14
- Publication Date
- 2024-11-06
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Existing mobile communication systems with integrated access and backhaul (IAB) nodes face challenges in efficiently recovering from wireless backhaul link failures (BH RLF), leading to delays and loss of data transmission due to inadequate notification and recovery processes, particularly when child nodes continue to transmit data to non-functional IAB nodes.
The proposed solution involves IAB nodes transmitting failure information to lower nodes during RRC re-establishment, performing cell selection using permitted and non-permitted cell information, and transitioning to an RRC inactive state for easier recovery, along with mechanisms for dynamic cell information updates and RRC resume procedures to enhance BH RLF recovery.
This approach reduces data loss and delays by enabling timely recovery from BH RLF, ensuring continuous communication by allowing IAB nodes to prioritize appropriate cell selection and transition states, thereby maintaining network stability and efficiency.
Smart Images

Figure 2024156993000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a communication control method for use in a mobile communication system. [Background technology]
[0002] 3GPP (3rd Generation Partnership Project) (registered trademark; hereinafter the same), a standardization project for mobile communication systems, specifies a new relay node called an IAB (Integrated Access and Backhaul) node (see, for example, "3GPP TS 38.300 V16.2.0 (2020-07)"). 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 includes a relay node having a wireless backhaul link performing a recovery process for recovering the wireless backhaul link in response to an occurrence of an event related to a failure of the wireless backhaul link. The recovery process includes transmitting, as a part of the recovery process, fault information indicating the occurrence of the event to a lower node of the relay node when starting a Radio Resource Control (RRC) re-establishment process for re-establishing the wireless backhaul link.
[0004] A communication control method according to a second aspect includes receiving, by a first relay node having a wireless backhaul link, cell information used in performing a cell selection procedure for determining a target cell for re-establishing the wireless backhaul link from a donor base station, the cell information including any one of allowed cell information identifying a cell that is permitted to be selected as the target cell and non-allowed cell information identifying a cell that is not permitted to be selected as the target cell.
[0005] A communication control method according to a third aspect includes a first relay node having a wireless backhaul link transmitting a message to a second relay node subordinate to the first relay node for transitioning the second relay node to an RRC (Radio Resource Control) inactive state. [Brief description of the drawings]
[0006] [Figure 1] 1 is a diagram showing a configuration of a mobile communication system 1 according to an embodiment. [Diagram 2] A diagram showing the configuration of a gNB200 according to an embodiment. [Diagram 3] FIG. 2 is a diagram illustrating a configuration of an IAB node 300 according to an embodiment. [Figure 4] 1 is a diagram illustrating a configuration of a UE 100 according to an embodiment. [Diagram 5] FIG. 2 is a diagram illustrating an example of a protocol stack of a user plane according to an embodiment. [Figure 6] FIG. 2 is a diagram illustrating an example of a protocol stack of a control plane (F1-C) according to an embodiment. [Figure 7] FIG. 2 is a diagram illustrating an example of a protocol stack of a control plane (RRC and NAS) according to an embodiment. [Figure 8] FIG. 2 is a diagram illustrating an IAB topology according to an embodiment. [Figure 9] FIG. 2 is a diagram illustrating a first operation example of the first embodiment. [Figure 10] FIG. 11 is a diagram illustrating a second operation example of the first embodiment. [Figure 11] FIG. 11 is a diagram illustrating an operation example of the second embodiment. [Figure 12] FIG. 13 is a diagram illustrating an operation example of the third embodiment. [Figure 13] FIG. 13 illustrates types of BH RLF notifications. [Figure 14] FIG. 1 illustrates an identified solution to avoid re-establishment on descendant nodes. [Figure 15]FIG. 1 shows a comparison of mechanisms for lossless delivery of UL data in the case of hop-by-hop RLC ARQ. [Figure 16] FIG. 1 illustrates UL status delivery deployment options. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0007] A mobile 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.
[0008] (Configuration of a mobile communication system) First, a configuration of a mobile communication system according to an embodiment will be described. Fig. 1 is a diagram showing a configuration of a mobile communication system 1 according to an embodiment.
[0009] The mobile communication system 1 is a fifth generation (5G) mobile communication system based on the 3GPP standard. Specifically, the radio access method in the mobile 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 mobile communication system 1.
[0010] As shown in FIG. 1, the mobile communication system 1 includes a 5G core network (5GC) 10, a user equipment (UE: User Equipment) 100, a base station (called gNB) 200, and an IAB node 300. The IAB node 300 is an example of a relay node. In the embodiment, an example in which the base station is an NR base station (i.e., a gNB) will be mainly described, but the base station may be an LTE base station (i.e., an eNB).
[0011] 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.
[0012] Each gNB 200 is a fixed wireless communication node and manages one or more cells. A cell is used as a term indicating the smallest unit of a wireless communication area. A cell may be used as a term indicating a function or resource for performing wireless communication with a UE 100. One cell belongs to one carrier frequency.
[0013] 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.
[0014] Each gNB 200 is connected to other adjacent gNBs 200 via an inter-base station interface called an Xn interface. In FIG. 1, an example in which gNB 200-1 is connected to gNB 200-2 is shown.
[0015] 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.
[0016] The mobile communication system 1 uses NR for backhaul and supports IAB, which enables wireless relay of NR access. The donor gNB 200-1 is a terminal node of the NR backhaul on the network side, and is a gNB 200 with additional functions that support IAB. The backhaul can be multi-hopped via multiple hops (i.e., multiple IAB nodes 300).
[0017] Each IAB node 300 has a DU functional unit and an MT (Mobile Termination) functional unit.
[0018] The MT connects to the DU of the upper node (upper IAB node 300 or donor gNB 200-1). The MT connects to the CU of the donor gNB 200-1 using Radio Resource Control (RRC) and establishes a signaling radio bearer (SRB) carrying RRC messages and NAS messages with the donor gNB 200-1. The neighboring node (i.e., the upper node) on the MT's NR Uu radio interface is sometimes called the "parent node."
[0019] The DU manages the cell, similar to the gNB 200. The DU terminates the NR Uu radio interface to the UE 100 and the subordinate IAB node 300. The DU supports the F1 protocol to the CU of the donor gNB 200-1. Neighboring nodes (i.e., subordinate nodes) on the NR access interface of the DU are sometimes called "child nodes."
[0020] All IAB nodes 300 connected to the donor gNB 200-1 via one or more hops form an IAB topology with the donor gNB 200-1 as the root. Such an IAB topology is sometimes called a Directed Acyclic Graph (DAG). In the IAB topology, the direction of a parent node is sometimes called upstream or upper, and the direction of a child node is sometimes called downstream or lower.
[0021] The MT of each IAB node 300 in the IAB topology establishes a wireless backhaul link to a DU of a parent node (IAB node 300 or donor gNB 200-1). The MT of the IAB node 300 establishes one wireless backhaul link to one parent node.
[0022] The DU of the IAB node 300 sets one of the cells managed by the DU as a serving cell for a MT of a child node that has established a wireless backhaul link with the node itself. The serving cell is a cell that provides wireless resources used on the wireless backhaul link. The DU of the IAB node 300 may set a cell group (CG) consisting of multiple serving cells for the MT of the child node.
[0023] An IAB node 300 may have multiple parent nodes. In other words, one IAB node 300 may establish a wireless backhaul link with each of the multiple IAB nodes 300 that are parent nodes. For example, an IAB node 300 may have a dual connection with two parent nodes. One of the two parent nodes is a master node (MN) and the other is a secondary node (SN). The wireless backhaul link between the IAB node 300 and the MN may be called a MCG (Master Cell Group) link, and the wireless backhaul link between the IAB node 300 and the SN may be called a SCG (Secondary Cell Group) link.
[0024] FIG. 1 shows an example in which IAB node 300-1 wirelessly connects to donor gNB 200-1, IAB node 300-2 wirelessly connects to IAB node 300-1, IAB node 300-3 wirelessly connects to IAB node 300-2, and IAB node 300-4 wirelessly connects to IAB node 300-3, and the F1 protocol is transmitted over four backhaul hops.
[0025] The UE 100 is a mobile wireless communication device that performs wireless communication with a cell. The UE 100 may be any device that performs wireless communication with the gNB 200 or the IAB node 300. For example, the UE 100 is a mobile phone terminal, a tablet terminal, a notebook PC, a sensor or a device provided in a sensor, a vehicle or a device provided in a vehicle. The UE 100 is wirelessly connected to an upper node (the IAB node 300 or the gNB 200) via a wireless access link. When the IAB node 300 having a wireless access link with the UE 100 relays communication of the UE 100, it operates as an access IAB node 300 of the UE 100.
[0026] 1 shows an example in which UE 100 is wirelessly connected to IAB node 300-4. UE 100 indirectly communicates with donor gNB 200-1 via IAB node 300-4, IAB node 300-3, IAB node 300-2, and IAB node 300-1. Specifically, IAB node 300-4, IAB node 300-3, IAB node 300-2, and IAB node 300-1 relay uplink data from UE 100 to donor gNB 200-1, and relay downlink data from gNB 200-1 to UE 100.
[0027] Next, a configuration of the gNB 200 which is a base station according to the embodiment will be described. Fig. 2 is a diagram showing the configuration of the gNB 200. As shown in Fig. 2, the gNB 200 has a wireless communication unit 210, a network communication unit 220, and a control unit 230.
[0028] 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 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 a baseband signal (transmitted signal) output by the control unit 230 into a wireless signal, and transmits the signal from the antenna.
[0029] 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.
[0030] 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, which will be described later.
[0031] Next, a configuration of the IAB node 300, which is a relay node according to the embodiment, will be described. Fig. 3 is a diagram showing the configuration of the IAB node 300. As shown in Fig. 3, the IAB node 300 has a wireless communication unit 310 and a control unit 320. The IAB node 300 may have a plurality of wireless communication units 310.
[0032] The wireless communication unit 310 performs wireless communication (wireless backhaul link) with the gNB 200 or other IAB nodes 300, and wireless communication (wireless access link) with the UE 100. The wireless communication unit 310 for wireless backhaul link communication and the wireless communication unit 310 for wireless access link communication may be provided separately.
[0033] 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 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 a baseband signal (transmitted signal) output by the control unit 320 into a wireless signal, and transmits the signal from the antenna.
[0034] 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 programs 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 baseband signals. The CPU executes programs stored in the memory to perform various processing. The processor performs processing of each layer, which will be described later.
[0035] Next, a configuration of the UE 100 which is a user device according to the embodiment will be described. Fig. 4 is a diagram showing the configuration of the UE 100. As shown in Fig. 4, the UE 100 includes a radio communication unit 110 and a control unit 120.
[0036] The wireless communication unit 110 performs wireless communication in a wireless access link, i.e., wireless communication with the gNB 200 and wireless communication with the IAB node 300. 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 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 a baseband signal (transmitted signal) output by the control unit 120 into a wireless signal and transmits the signal from the antenna.
[0037] 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 programs 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 baseband signals. The CPU executes programs stored in the memory to perform various processing. The processor performs processing of each layer, which will be described later.
[0038] 4, the UE 100 may include a Global Navigation Satellite System (GNSS) receiver. The UE 100 does not necessarily have to include a GNSS receiver.
[0039] (Protocol Stack) Next, an example of a protocol stack configuration in the mobile communication system 1 according to the embodiment will be described. Fig. 5 is a diagram showing an example of a protocol stack of a user plane.
[0040] FIG. 5 shows an example of a user plane protocol stack in the case where user data is communicated between IAB node 300-2 and donor gNB 200-1.
[0041] As shown in Fig. 5, each of the IAB nodes 300-1 and 300-2 has the functional units of an MT and a DU. The MT has the layers of a Backhaul Adaptation Protocol (BAP), a Radio Link Control (RLC), and a Medium Access Control (MAC). The DU has the layers of a BAP, an RLC, and a MAC. Although Fig. 5 shows an example in which the BAP layer of the DU and the BAP layer of the MT are provided separately, the BAP layer of the DU and the BAP layer of the MT may be integrated.
[0042] The DU of the IAB node 300-2 and the CU of the donor gNB 200-1 have layers of User Datagram Protocol (UDP) and GPRS Tunnelling Protocol for User Plane (GTP-U). The DU of the IAB node 300-2 and the DU of the donor gNB 200-1 have an Internet Protocol (IP) layer. The GTP-U and UDP layers of the IAB node 300-2 communicate with the GTP-U and UDP layers of the CU of the donor gNB 200-1 via the IAB node 300-1.
[0043] FIG. 6 is a diagram illustrating an example of a protocol stack of the control plane (F1-C).
[0044] FIG. 6 shows an example of a control plane protocol stack in the case where F1-AP (Application Protocol) control signals are communicated between IAB node 300-2 and donor gNB 200-1.
[0045] As shown in Fig. 6, the DU of the IAB node 300-2 and the CU of the donor gNB 200-1 have layers of F1-AP and SCTP (Stream Control Transmission Protocol). The DU of the IAB node 300-2 and the DU of the donor gNB 200-1 have an IP layer. The F1-AP and SCTP layers of the IAB node 300-2 communicate with the F1-AP and SCTP layers of the CU of the donor gNB 200-1 via the IAB node 300-1.
[0046] FIG. 7 is a diagram illustrating an example of a protocol stack of the control plane (RRC and NAS).
[0047] FIG. 7 shows an example of a control plane protocol stack in the case where RRC control signals (RRC messages) are communicated between the IAB node 300-2 and the donor gNB 200-1, and NAS control signals (NAS messages) are communicated between the IAB node 300-2 and the AMF 11.
[0048] 7, the MT of the IAB node 300-2 and the CU of the donor gNB 200-1 have layers of RRC and PDCP (Packet Data Convergence Protocol). The RRC and PDCP layers of the IAB node 300-2 communicate with the RRC and PDCP layers of the CU of the donor gNB 200-1 via the IAB node 300-1.
[0049] In addition, the NAS layer of the MT of the IAB node 300-2 communicates with the NAS layer of the AMF 11.
[0050] Although not shown in Figure 7, the above-mentioned RRC control signals and NAS control signals are transmitted via the BAP layer of the DU of IAB node 300-1 and the BAP layer of the DU of donor gNB 200-1.
[0051] Although not shown in FIGS. 5 to 7, a PHY layer is provided below the MAC layer of each node.
[0052] Here, we will explain each protocol. The PHY layer performs coding / decoding, modulation / demodulation, antenna mapping / demapping, and resource mapping / demapping. Data and control information are transmitted between PHY layers via physical channels.
[0053] The MAC layer performs data priority control and retransmission processing using hybrid ARQ (HARQ). Data and control information are transmitted between MAC layers via transport channels. The MAC layer of the donor gNB 200-1 and the MAC layer of the DU include a scheduler. The scheduler determines the uplink and downlink transport format (transport block size, modulation and coding scheme (MCS)) and the resource blocks to be assigned to the UE 100.
[0054] The RLC layer uses the functions of the MAC layer and the PHY layer to transmit data to the RLC layer on the receiving side. Data and control information are transmitted between the RLC layers via logical channels.
[0055] The BAP layer performs routing processing and bearer mapping / demapping processing in the user plane. The details of the processing in the BAP layer will be described later.
[0056] The RRC layer transmits RRC signaling (RRC messages) for various configurations. The RRC layer controls logical channels, transport channels, and physical channels according to the establishment, re-establishment, and release of radio bearers. When there is an RRC connection between the RRC layers, the IAB node 300 is in an RRC connected state. When there is no RRC connection between the RRC layers, the IAB node 300 is in an RRC idle state.
[0057] When the RRC connection is inactive, the IAB node 300 (MT) is in the RRC inactive state. The RRC inactive state is a state different from the RRC idle state and the RRC connected state. The RRC inactive state is a state in which the context of the IAB node 300 is stored in the IAB node 300 and the donor gNB 200-1 (5GC10) in the same way as the RRC connected state.
[0058] The context may be an AS context of the IAB node 300. The AS context may include information for RRC re-establishment. The AS context may include radio access capabilities of the IAB node 300. The context may include a security context. The security context may include KgNB, a token, NCC (NextHopChainingCount), security capabilities, and security algorithms.
[0059] (IAB Topology) Next, an IAB topology according to an embodiment will be described. Fig. 8 is a diagram showing an IAB topology according to an embodiment.
[0060] As shown in FIG. 8, the IAB topology includes IAB node 300-1, IAB node 300-2(a), IAB node 300-2(b), IAB node 300-3(a), IAB node 300-3(b), IAB node 300-4(a), IAB node 300-4(b), and IAB node 300-4(c). The MT of each IAB node 300 establishes a wireless backhaul link with the DU of the parent node. IAB node 300-3(b) has a dual connection with IAB node 300-2(a) and IAB node 300-2(b), and establishes a wireless backhaul link with each of IAB node 300-2(a) and IAB node 300-2(b). In FIG. 8, the wireless backhaul links are shown by dashed lines.
[0061] Although not shown in FIG. 8, a DU of each IAB node 300 may be connected to a UE 100.
[0062] The donor gNB 200-1 sets a relay path between the donor gNB 200-1 and each IAB node 300. The relay path set in the IAB node 300 is a path that enables communication between the communication device served by the IAB node 300 and the donor gNB 200-1. The communication device served by the IAB node 300 includes a child node (MT) having a wireless backhaul link with the DU of the IAB node 300, and a UE 100 having a wireless access link with the DU of the IAB node 300.
[0063] The donor gNB200-1 may set up multiple relay paths to an IAB node 300 that has multiple parent nodes.
[0064] The donor gNB200-1 may set up, for example, the following four relay paths in the IAB topology:
[0065] Relay path #1: donor gNB 200-1←→ IAB node 300-1←→ IAB node 300-2(a)←→ IAB node 300-3(b)←→ IAB node 300-4(c) Relay path #2: donor gNB 200-1←→ IAB node 300-1←→ IAB node 300-2(a)←→ IAB node 300-3(a)←→ IAB node 300-4(a) Relay path #3: donor gNB 200-1←→ IAB node 300-1←→ IAB node 300-2(a)←→ IAB node 300-3(a)←→ IAB node 300-4(b) Relay path #4: donor gNB 200-1 ←→ IAB node 300-1 ←→ IAB node 300-2 (b) ←→ IAB node 300-3 (b) ←→ IAB node 300-4 (c)
[0066] The donor gNB 200-1 assigns a path identifier for identifying each relay path in the IAB topology. The donor gNB 200-1 also assigns an IAB identifier for identifying the IAB node 300 in the IAB topology to each IAB node 300 in the IAB topology. The IAB identifier may be a BAP address assigned to a BAP layer (BAP entity).
[0067] The donor gNB 200-1 transmits, to each IAB node 300 in the IAB topology, routing configuration information regarding a relay path passing through the IAB node 300. Each IAB node 300 stores the routing configuration information. The routing configuration information is transmitted by an RRC message or an F1AP message.
[0068] The routing configuration information sent to the IAB node 300 includes a path identifier of a relay path (one or more relay paths) passing through the IAB node 300, and an IAB identifier of a next node (i.e., a child node and / or a parent node) of the IAB node 300 on the relay path passing through the IAB node 300. The next node of the IAB node 300 on the relay path may be referred to as the "NEXT HOP" of the IAB node.
[0069] When the DU of the IAB node 300 establishes an F1-AP connection with the CU of the donor gNB 200-1, the DU of the IAB node 300 notifies the donor gNB 200-1 of the cell identifier of the cell managed by the DU of the own node. This allows the donor gNB 200-1 to know the cell identifier of the cell managed by the DU of each IAB node 300 in the IAB topology.
[0070] Topology structure information regarding the structure of the IAB topology may be exchanged between donor gNB200-1 (CU) and adjacent donor gNB200-2 (CU) via an inter-base station interface.
[0071] The topology structure information may further include an identifier of each IAB node 300 constituting the IAB topology. Such identifier includes at least one of an IAB identifier (BAP address), a DU identifier, and an MT identifier (C-RNTI (Cell-Radio Network Temporary Identifier)).
[0072] The topology structure information may further include routing configuration information.
[0073] (BH RLF recovery operation under existing specifications) In the above IAB topology, a radio backhaul link failure (RLF) may occur. Such an RLF is called a BH RLF.
[0074] Here, the recovery operation of the BH RLF in the existing specifications (for example, see "3GPP TS 38.331 V16.1.0") will be described.
[0075] According to the existing specifications, IAB node 300 performs a series of processes from detecting a BH RLF to recovering from the BH RLF (hereinafter referred to as "BH RLF recovery processes according to the existing specifications"), for example, as follows.
[0076] First, if the MT of the IAB node 300 detects an out-of-sync state N310 times in a row, it detects a radio problem and starts a timer T310. If the MT detects an in-sync state N311 times in a row after starting the timer T310, it stops the timer T310.
[0077] Second, the MT detects a BH RLF when timer T310 expires without stopping it. In response to detecting the BH RLF, the MT initiates an RRC re-establishment procedure to recover from the BH RLF. The MT initiates the RRC re-establishment procedure and starts timer T311, and performs a cell selection procedure. The MT selects a suitable cell through the cell selection procedure and re-establishes a wireless backhaul link to the selected cell. A suitable cell is a cell that satisfies at least a minimum wireless quality criterion.
[0078] Third, the MT transitions to the RRC idle state upon expiration of timer T311 without successful re-establishment of the radio backhaul link.
[0079] When the RRC re-establishment process fails (for example, when the timer T311 expires), the MT of the IAB node 300 transmits a recovery failure notification to its child node. The recovery failure notification is sometimes called a BH RLF indication.
[0080] When the IAB node 300 receives a recovery failure notification from its parent node, it initiates an RRC re-establishment process in the same way as when the IAB node 300 detects a BH RLF.
[0081] In the BH RLF recovery process of the existing specification, the IAB node 300 transmits a recovery failure notification to the child node only when the RRC re-establishment process fails. In other words, the IAB node 300 does not transmit any notification of the BH RLF detected by itself to its child node from the time when the BH RLF is detected to the time when the recovery fails, that is, while T311 is operating. During this time, the child node may transmit user data and control signals addressed to the donor base station 200 to the IAB node 300, assuming that the IAB node 300 is operating normally. If the IAB node 300 ultimately fails to recover from the BH RLF, there is a possibility that the user data and control signals may not reach the donor base station 200. Even if the IAB node 300 succeeds in recovering from the BH RLF before the expiration of T311, the user data and control signals may not reach the donor base station 200 while T311 is operating, causing a delay in the upstream direction. In the existing specifications, the timer value of T311 is a maximum of 30 seconds, so the delay is a maximum of 30 seconds.
[0082] As described above, the BH RLF recovery process of the existing specifications has a problem that even if the IAB node 300 detects a BH RLF, the child node of the IAB node 300 assumes that the IAB node 300 is operating normally (hereinafter referred to as "problem 1"). Problem 1 becomes prominent especially when the child node of the IAB node 300 relays traffic that requires low latency.
[0083] The first embodiment described below is an embodiment related to means for solving the first problem.
[0084] In addition, in the BH RLF recovery process of the existing specification, when the IAB node 300 starts the cell selection process in the RRC re-establishment process, the child node of the IAB node 300 operates normally. For example, the DU of the child node of the IAB node 300 continues to transmit SSB (Synchronization Signal and PBCH block), which is a downlink signal used for cell detection and measurement. Therefore, when the IAB node 300 performs the cell selection process in the RRC re-establishment process, the IAB node 300 may detect the cell managed by the DU of the child node as an appropriate cell. However, since the IAB node 300 does not have an available wireless backhaul link, the child node cannot communicate with the donor base station 200. As a result, there is a problem that the IAB node 300 cannot re-establish the RRC connection and cannot provide the relay function by the IAB (hereinafter referred to as "problem 2"). In particular, problem 2 becomes prominent when the IAB node 300 is physically close to the child node (in good wireless conditions).
[0085] The second embodiment described below is an embodiment related to means for solving the second problem.
[0086] Furthermore, in the BH RLF recovery process of the existing specifications, the transition of the MT of the IAB node 300 to the RRC inactive state was not taken into consideration (problem 3).
[0087] The third embodiment described below is an embodiment related to means for solving the problem 3.
[0088] (First embodiment) The following describes the first embodiment, which is an embodiment related to means for solving the above-mentioned problem 1.
[0089] The IAB node 300 according to the first embodiment performs a recovery process for recovering a wireless backhaul link in response to the occurrence of an event related to a failure of the wireless backhaul link. When starting an RRC re-establishment process as part of the recovery process, the IAB node 300 transmits failure information indicating the occurrence of the event to a lower node of the IAB node 300.
[0090] The event includes one of the following: the IAB node 300 detects a wireless backhaul link failure (BH RLF); and the IAB node 300 receives a restoration failure notification from an upper node.
[0091] This allows a lower node of the IAB node 300 to know that an event related to a failure of the wireless backhaul link has occurred in the IAB node 300 when the RRC re-establishment process is initiated in the IAB node 300.
[0092] In addition, the IAB node 300 may be configured to be able to execute an RRC re-establishment process and another process (e.g., a fast MCG link restoration process described later) that is easier to recover than the RRC re-establishment process as a restoration process for restoring the wireless backhaul link. In this case, the IAB node 300 does not perform the RRC re-establishment process if the other process is successful. Therefore, the IAB node 300 transmits failure information when starting the RRC re-establishment process, not when starting the restoration process.
[0093] (Operation Example 1 of the First Embodiment) An explanation will be given below of Operation Example 1 of the first embodiment. Fig. 9 is a diagram showing the operation of Operation Example 1 of the first embodiment.
[0094] 9, the IAB node 300-2(a) starts processing in a state in which a wireless backhaul link (BH link) with the IAB node 300-1 is established. Although not shown in the figure, the MT of the IAB node 300-2(a) has an RRC connection with a CU of the donor gNB 200-1.
[0095] In step S101, the IAB node 300-2(a) determines whether an event related to a failure of the wireless backhaul link occurs. Here, the event includes either one of the following: the IAB node 300-2(a) detects a BH RLF; and the IAB node 300-2(a) receives, from the IAB node 300-1, a restoration failure notification indicating that the IAB node 300-1 fails in a restoration process for restoring the wireless backhaul link. The restoration process refers to steps S102 to S107 described below.
[0096] If IAB node 300-2(a) determines that an event will occur (S101: YES), it advances the process to step S102.
[0097] In step S102, the IAB node 300-2(a) starts a restoration process for restoring the wireless backhaul link. Here, when the IAB node 300-2(a) is configured to be able to execute the RRC re-establishment process and other processes (e.g., first MCG link restoration process) as the restoration process, the IAB node 300-2(a) performs the other process first.
[0098] In step S103, the IAB node 300-2(a) determines whether to perform the RRC re-establishment process. If no other process is set, the IAB node 300-2(a) determines to perform the RRC re-establishment process. If another process is set and fails, the IAB node 300-2(a) determines to perform the RRC re-establishment process.
[0099] If IAB node 300-2(a) determines to perform RRC re-establishment processing (S103: YES), it proceeds to step S104.
[0100] In step S104, IAB node 300-2(a) starts the RRC re-establishment procedure (i.e., starts timer T311).
[0101] In step S105, when IAB node 300-2(a) starts the RRC re-establishment process, it transmits failure information to its subordinate node (IAB node 300-3(a)).
[0102] The fault information includes information indicating the event determined to have occurred in step S101. The fault information may further include information indicating that IAB node 300-2(a) initiates an RRC re-establishment procedure.
[0103] The failure information may be a BAP layer message (BAP Control PDU) or a MAC layer message (MAC CE).
[0104] The failure information may be a message of the RRC layer. For example, the DU of the IAB node 300-2(a) may broadcast the failure information in a system information block (SIB).
[0105] In step S106, IAB node 300-2(a) performs a cell selection process. IAB node 300-2(a) may perform the cell selection process using cell information in a second embodiment, which will be described later.
[0106] In step S107, IAB node 300-2(a) determines whether or not the RRC re-establishment process has been successful in the cell selected by the cell selection process. If the RRC re-establishment process has been successful (S107: YES), IAB node 300-2(a) ends the process.
[0107] If the RRC re-establishment process fails (S107: NO), in step S108, IAB node 300-2(a) transmits a recovery failure notification to IAB node 300-3(a).
[0108] In step S109, IAB node 300-2(a) transitions from the RRC connected state to the RRC idle state.
[0109] (Operation Example 2 of the First Embodiment) Operation example 2 is an operation example for a case in which the IAB node 300 has multiple wireless backhaul links (eg, an MCG link and an SCG link) and an event related to a failure of one wireless backhaul link (eg, the MCG link) occurs.
[0110] The IAB node 300 according to the second operation example performs a process for recovering one wireless backhaul link (e.g., an MCG link) via another wireless backhaul link (e.g., an SCG link) in response to the occurrence of an event related to a failure of the one wireless backhaul link. If the process fails, the IAB node 300 performs an RRC re-establishment process. The process is, for example, a fast MCG link recovery procedure. The fast MCG link recovery procedure will be described below.
[0111] First, the MT of the IAB node 300 generates an MCGFailureInformation message and transmits the MCGFailureInformation message to the CU of the donor gNB 200-1 via the SCG link. When the MT transmits the MCGFailureInformation message, it starts a timer T316 related to the fast MCG link recovery process.
[0112] Secondly, the MT of the IAB node 300 receives an RRC message (e.g., an RRC Reconfiguration message) for restoring the MCG link from the CU of the donor gNB 200-1 via the SCG link. The RRC message includes a contention-free random access preamble used for a random access procedure to the IAB node 300, which is a parent node corresponding to the MCG link, and radio settings used for wireless communication with the IAB node 300. In response to receiving the RRC message, the MT of the IAB node 300 restores the MCG link.
[0113] Third, if the MT does not receive an RRC message for restoring the MCG link and timer T316 expires, the MT performs an RRC re-establishment procedure.
[0114] The following describes the operation of Operation Example 2. FIG 10 is a diagram showing the operation of Operation Example 2.
[0115] 10, the IAB node 300-3(b) starts operation in a state in which an MCG link, which is a wireless backhaul link with the IAB node 300-2(a), and an SCG link, which is a wireless backhaul link with the IAB node 300-2(b), are established. The MT of the IAB node 300-3(b) has an RRC connection with a CU of the donor gNB 200-1.
[0116] In step S201, the IAB node 300-3(b) receives an RRC message including setting information for timer T316 from the donor gNB 200-1. By receiving the setting information for timer T316, the IAB node 300-3(b) recognizes that a fast MCG link recovery procedure is to be executed when an event related to a failure of the MCG link occurs.
[0117] In step S202, the IAB node 300-3(b) determines whether an event related to a failure of the MCG link occurs, including any one of the following: the IAB node 300-3(b) detects a BH RLF for the MCG link; and the IAB node 300-3(b) receives a restoration failure notification from the IAB node 300-2(a), indicating that the IAB node 300-2(a) fails a restoration process to restore the wireless backhaul link.
[0118] If IAB node 300-3(b) determines that an event will occur (S202: YES), it advances the process to step S203.
[0119] In step S203, IAB node 300-3(b) starts the fast MCG link recovery process (ie, starts timer T316).
[0120] In step S204, IAB node 300-3(b) sends an MCGFailureInformation message to donor gNB 200-1 via the SCG link.
[0121] In step S205, the IAB node 300-3(b) determines whether the recovery of the MCG link has been successful (i.e., whether an RRC message for recovering the MCG link has been received). If the recovery of the MCG link has been successful (S205: YES), the IAB node 300-3(b) stops the timer T316 and ends this flow.
[0122] If the MCG link recovery is not successful (S205: NO), in step S206, the IAB node 300-3(b) determines whether or not the timer T316 has expired. If the timer T316 has expired (step S206: YES), the IAB node 300-3(b) determines that the first MCG link recovery process has failed, and proceeds to step S208.
[0123] In step S208, IAB node 300-3(b) starts the RRC re-establishment procedure (ie, starts timer T311).
[0124] In step S209, when starting the RRC re-establishment process, the IAB node 300-3(b) transmits fault information to the lower node (IAB node 300-4(c)). The fault information includes information indicating the event determined to have occurred in step S202. The fault information may further include information indicating that the IAB node 300-3(b) starts the RRC re-establishment process.
[0125] The process of steps S210 to S213 is similar to the process of steps S106 to S 109. Here, "IAB node 300-2(a)" in steps S106 to S109 is replaced with "IAB node 300-3(b)."
[0126] Second embodiment The second embodiment is an embodiment related to means for solving the above-mentioned problem 2.
[0127] The IAB node 300 according to the second embodiment receives cell information used in performing a cell selection procedure for determining a target cell for re-establishing a wireless backhaul link from the donor gNB 200. The IAB node 300 stores the cell information. When starting an RRC re-establishment process, the IAB node 300 performs a cell selection process using the stored cell information.
[0128] The cell information includes either allowed cell information that identifies allowed cells, which are cells that the IAB node 300 is permitted to select as the target cell, or non-allowed cell information that identifies non-allowed cells, which are cells that the IAB node 300 is not permitted to select as the target cell.
[0129] The permitted cells of the IAB node 300 include at least one type of permitted cells: type 1 permitted cells, type 2 permitted cells, and type 3 permitted cells.
[0130] The type 1 allowed cells of an IAB node 300 are cells managed by an IAB node 300 that has a relay path with the donor gNB 200 of the IAB node 300, and the IAB node 300 is not present on the relay path. In the example of Fig. 8, the type 1 allowed cells of the IAB node 300-2(a) include a cell managed by the IAB node 300-1 and a cell managed by the IAB node 300-2(b).
[0131] The type 2 allowed cells of an IAB node 300 are cells managed by an IAB node 300 that has a relay path with the donor gNB 200 of the IAB node 300, that the IAB node 300 exists on the relay path, and that has a relay path different from the relay path. In the example of Fig. 8, the type 2 allowed cells of the IAB node 300-2(a) include a cell managed by an IAB node 300-3(b) and a cell managed by an IAB node 300-4(c).
[0132] The type 3 allowed cell of the IAB node 300 is a cell managed by an IAB node 300 under a donor gNB 200 (CU) different from the donor gNB 200 (CU) of the IAB node 300. The type 3 allowed cell may be called a different topology cell.
[0133] An unauthorised cell of an IAB node 300 is a cell managed by an IAB node 300 that has only one relay path with the donor gNB 200 of the IAB node 300 and that is on the relay path. In the example of Fig. 8, the unauthorised cells of an IAB node 300-2(a) include a cell managed by an IAB node 300-3(a), a cell managed by an IAB node 300-4(a), and a cell managed by an IAB node 300-4(b).
[0134] Next, the cell selection process using the cell information will be described.
[0135] In the cell selection process, when the IAB node 300 detects a type 1 allowed cell, the IAB node 300 selects the type 1 allowed cell as a target cell.
[0136] If the IAB node 300 does not detect a type 1 allowed cell and detects a type 2 allowed cell, it selects the type 2 allowed cell as the target cell.
[0137] When the IAB node 300 detects neither a type 1 allowed cell nor a type 2 allowed cell, and detects a type 3 allowed cell, the IAB node 300 selects the type 3 allowed cell as a target cell. Here, when the IAB node 300 re-establishes a radio backhaul link to a different topology cell, a child node of the IAB node 300 needs to establish an RRC connection to the donor gNB 200 to which the different topology cell belongs. Therefore, the type 2 allowed cell is selected preferentially over the type 3 allowed cell (different topology cell).
[0138] If the IAB node 300 does not detect any of the type 1 allowed cells or type 3 allowed cells, it does not select a target cell. In this case, T311 expires, and the IAB node 300 transitions to the RRC idle state and discards the stored cell information.
[0139] The IAB node 300 determines whether a detected cell is one of a type 1 allowed cell, a type 2 allowed cell, a type 3 allowed cell, and a non-allowed cell using the following determination method.
[0140] (Case 1) Case 1 is a case where the IAB node 300 stores allowed cell information. The decision method for case 1 is as follows.
[0141] The IAB node 300 determines the cells included in the allowed cell information as type 1 allowed cells.
[0142] The IAB node 300 determines, as a type 3 allowed cell, a cell that is not included in the allowed cell information and broadcasts IAB topology information that does not match the IAB topology information of the IAB node 300. The IAB topology information may be an identifier of the donor gNB 200 or an identifier of the IAB topology.
[0143] The IAB node 300 determines, as a non-allowed cell, a cell that is not included in the allowed cell information and that broadcasts IAB topology information that matches the IAB topology information of the IAB node 300 itself.
[0144] The IAB node 300 determines, as type 2 allowed cells, cells that are not included in the allowed cell information and that are managed by the IAB node 300 that is set as a dual-connection node (MN or SN) of the own IAB node 300. The IAB node 300 knows in advance, by an F1-AP message or an RRC message, the cells that are managed by the IAB node 300 that is set as a dual-connection node of the own IAB node 300.
[0145] Alternatively, the allowed cell information may include a cell identifier and type information indicating the type of the cell corresponding to the cell identifier (any one of types 1 to 3). In this case, the IAB node 300 determines the detected cell as any one of a type 1 allowed cell, a type 2 allowed cell, and a type 3 allowed cell based on the type information included in the allowed cell information.
[0146] Since the donor gNB 200-1 (CU) has topology structure information from the adjacent donor gNB 200-2 (CU), it can identify the type 3 allowed cells of the IAB node 300 and include them in the allowed cell information.
[0147] (Case 2) Case 2 is a case where the IAB node 300 stores non-permitted cell information. The decision method for case 2 is as follows.
[0148] The IAB node 300 determines the cells included in the non-permitted cell information as non-permitted cells.
[0149] Even if a cell is included in the non-allowed cell information, if the cell is managed by an IAB node 300 that is configured as a dual-connection node, the IAB node 300 determines the cell to be a type 2 allowed cell.
[0150] The IAB node 300 determines a cell that broadcasts IAB topology information that does not match the IAB topology information of the IAB node 300 as a type 3 allowed cell.
[0151] The IAB node 300 determines, as a type 1 permitted cell, a cell that is not included in the non-allowed cell information and that broadcasts IAB topology information that matches the IAB topology information of the IAB node 300 itself.
[0152] The IAB node 300 determines, as a type 3 allowed cell, a cell that is not included in the non-allowed cell information and broadcasts IAB topology information that does not match the IAB topology information of the IAB node 300 itself.
[0153] (Operation example of the second embodiment) An operation example of the second embodiment will be described below. Fig. 11 is a diagram showing an operation example of the second embodiment.
[0154] As shown in FIG. 11, IAB node 300-2(a) begins processing in a state in which it has an RRC connection with donor gNB 200-1.
[0155] In step S301, the donor gNB 200-1 transmits cell information to the IAB node 300-2(a). The IAB node 300-2(a) receives the cell information from the donor gNB 200-1 and stores the received cell information. The cell information includes either allowed cell information or non-allowed cell information.
[0156] The donor gNB 200-1 determines the information to be included in the cell information (allowed cell information or non-allowed cell information) based on the number of hops from the IAB node 300-2(a) to the donor gNB 200-1.
[0157] If the number of hops is equal to or greater than the threshold, the donor gNB 200-1 includes non-allowed cell information in the cell information. If the number of hops is less than the threshold, the donor gNB 200-1 includes permitted cell information in the cell information. For an IAB node 300 with a large number of hops, the number of lower nodes is smaller than the number of upper nodes, so the number of non-allowed cells is smaller than the number of permitted cells, and the size of the permitted cell information is larger than the size of the non-allowed cell information. On the other hand, for an IAB node 300 with a small number of hops, the size of the non-allowed cell information is larger than the size of the permitted cell information. The information size can be reduced by determining the information to be included in the cell information by comparing the number of hops with the threshold.
[0158] When transmitting cell information, the donor gNB 200-1 may set an expiration date for the cell information. Specifically, the donor gNB 200-1 transmits the cell information together with information indicating a timer value corresponding to the expiration date. When the IAB node 300-2(a) receives the cell information together with the timer value, the IAB node 300-2(a) stores the cell information and starts the timer. When the timer expires, the IAB node 300-2(a) discards the stored cell information.
[0159] In step S302, the IAB node 300-2(a) transmits an update request message to the donor gNB 200-1 requesting to update cell information. The update request message is an RRC message.
[0160] IAB node 300-2(a) may send an update request message if any one of the following conditions A and B is met.
[0161] Condition A: A timer started by IAB node 300-2(a) in response to receiving cell information expires.
[0162] Condition B: IAB node 300-2(a) discovered a cell that was not identified by the cell information.
[0163] Here, the IAB node 300-2(a) performs measurement according to measurement configuration information set by the donor gNB 200-1, for example, and if the cell discovered by the measurement is not included in the cell information, it determines that condition B is satisfied.
[0164] The update request message sent by IAB node 300-2(a) in response to condition B may be an inquiry message including an inquiry as to whether the discovered cell is an allowed cell or an unallowed cell. The inquiry message includes a cell identifier of the discovered cell.
[0165] In step S303, the donor gNB 200-1 transmits the updated cell information to the IAB node 300-2(a). The IAB node 300-2(a) receives the updated cell information and updates the stored cell information.
[0166] The updated cell information may be new cell information or may be information indicating a difference from the previously transmitted cell information (the cell information transmitted in step S301). The information indicating the difference is, for example, information including a cell identifier newly added to the previously transmitted cell information (the allowed cell information or the non-allowed cell information).
[0167] In step S303, even if the donor gNB 200-1 has not received an update request message from the IAB node 300-2(a), the donor gNB 200-1 may send updated cell information if any one of the following conditions C and D is satisfied.
[0168] Condition C: A change occurred in the IAB topology under donor gNB200-1.
[0169] For example, the donor gNB 200-1 determines that condition C is satisfied when a new IAB node 300 joins the IAB topology or when an IAB node 300 in the IAB topology leaves the IAB topology.
[0170] Condition D: A measurement report in accordance with the measurement configuration from donor gNB200-1 is received from IAB node 300-2(a), and the measurement report includes a cell identifier of a cell not configured in the measurement configuration.
[0171] In step S304, IAB node 300-2(a) starts the RRC re-establishment procedure (i.e., starts timer T311).
[0172] In step S305, IAB node 300-2(a) performs a cell selection process using the cell information. Here, IAB node 300-2(a) performs the cell selection process based on the cell selection method described above.
[0173] In step S306, the IAB node 300-2(a) determines whether the RRC re-establishment process for the cell selected by the cell selection process has been successful. If the RRC re-establishment process is successful (S306: YES), the IAB node 300-2(a) advances the process to step S307. On the other hand, if the RRC re-establishment process has failed (S306: NO), the IAB node 300-2(a) advances the process to step S310.
[0174] In step S307, the IAB node 300-2(a) determines whether its donor gNB 200 has changed. Here, if the IAB node 300-2(a) selects a different topology cell (type 3 allowed cell) as the target cell in step S305 and succeeds in the RRC re-establishment process for the cell, it determines that the donor gNB 200 has changed.
[0175] If the IAB node 300-2(a) determines that the donor gNB 200 has changed (S307: YES), the process proceeds to step S308. On the other hand, if the IAB node 300-2(a) determines that its donor gNB 200 has not changed (S307: NO), the process ends.
[0176] In step S308, the IAB node 300-2(a) transmits a message to the IAB node 300-3 subordinate thereto to cause the IAB node 300-3 to execute a process for establishing an RRC connection with the changed donor gNB 200. Such a process is an RRC re-establishment process or a handover process. Such a message is a BAP message (BAP Control PDU) or an RRC message (SIB).
[0177] In step S309, the IAB node 300-3 performs an RRC re-establishment process or a handover process in response to the message received in step S308.
[0178] The IAB node 300-3 may not execute a random access procedure in the RRC re-establishment process or handover process. In other words, the IAB node 300-3 performs a RACH-less RRC re-establishment process or a RACH-less handover process. In this case, the IAB node 300-3 transmits MSG3 without transmitting MSG1 (Random Access Preamble). The message in step S308 may include an indication indicating RACH-less.
[0179] In step S310, IAB node 300-2(a) transmits a restoration failure notification to IAB node 300-3.
[0180] In step S311, IAB node 300-2(a) transitions from an RRC connected state to an RRC idle state.
[0181] In the second embodiment, the IAB node 300 may be provided with the cell information from the parent node. The cell information may be received from the parent node together with the "fault information" in the first embodiment. The cell information may be included in the fault information.
[0182] Third embodiment The third embodiment is an embodiment related to means for solving the above-mentioned problem 3.
[0183] The IAB node 300 according to the third embodiment transitions to the RRC inactive state in response to an instruction message received from an upper node.
[0184] The IAB node 300 in the RRC inactive state restores the wireless backhaul link by performing an RRC resume procedure. The RRC resume procedure does not require recovery of the NAS, and therefore, makes it easier to restore the wireless backhaul link than the RRC re-establishment procedure.
[0185] An operation example of the third embodiment will be described below. Fig. 12 is a diagram showing an operation example of the third embodiment.
[0186] As shown in FIG. 12, IAB node 300-2(a) begins processing in a state in which it has an RRC connection with donor gNB 200-1.
[0187] In step S401, the IAB node 300-2(a) transmits an instruction message to the subordinate IAB node 300-3 for transitioning the IAB node 300-3 to the RRC inactive state. The instruction message may be a BAP message (BAP Control PDU) or an RRC message (SIB).
[0188] The IAB node 300-2(a) may transmit the instruction message when it is unable to secure a connection with the donor gNB 200-1. "IAB node 300-2(a) is unable to secure a connection with the donor gNB 200-1" means either that the above-mentioned "event related to a failure of a wireless backhaul link" occurs in the IAB node 300-2(a) or that the IAB node 300-2(a) receives the above-mentioned "failure information" from a higher-level node.
[0189] In step S402, the IAB node 300-3 transitions to the RRC inactive state in response to the received indication message.
[0190] The IAB node 300-3 may perform cell reselection immediately after transitioning to the RRC inactive state. In cell reselection, the IAB node 300-3 does not select the serving cell immediately before the transition (i.e., the cell managed by the IAB node 300-2(a)). Since the IAB node 300-2(a) transmits an indication message when it is unable to secure a connection with the donor gNB 200-1, if the IAB node 300-3 selects the serving cell immediately before the transition, there is a high possibility that it will not be able to communicate with the donor gNB 200-1. Therefore, the IAB node 300-3 does not select the serving cell immediately before the transition.
[0191] In step S403, the IAB node 300-3 sends an RRCResumeRequest message to the donor gNB 200-1.
[0192] The RRCResumeRequest message includes at least one of a cell identifier of a serving cell immediately before the transition, a C-RNTI, and a Short MAC-I. The donor gNB 200-1 can obtain the context of the IAB node 300-3 based on this information.
[0193] The RRCResumeRequest message may further include a Resume Cause having an indication to reserve the wireless backhaul link.
[0194] In step S404, the IAB node 300-3 receives the RRCResume message from the donor gNB 200-1. The RRCResume message includes the NCC. The NCC is information for deriving a security key called KgNB.
[0195] (Other embodiments) A program may be provided that causes a computer to execute each process performed by the IAB node 300 or the donor gNB 200. 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.
[0196] In addition, circuits for executing each process performed by the IAB node 300 or the donor gNB 200 may be integrated, and at least a part of the IAB node 300 or the donor gNB 200 may be configured as a semiconductor integrated circuit (chip set, SoC).
[0197] The above describes the embodiments in detail with reference to the drawings, but the specific configuration is not limited to that described above, and various design changes, etc. are possible without departing from the spirit of the invention.
[0198] In the above-mentioned embodiment and modified example, relay transmission by IAB has been described as an example, but the present invention is not limited to this and may be applied to other relay transmission systems. For example, the operations according to the above-mentioned embodiment and modified example may be applied to a relay node (Layer 3 relay node), a side link relay (a relay node using a side link used for direct communication between user devices), etc.
[0199] In the above embodiment, an example in which the cellular communication system 1 is a 5G cellular communication system has been mainly described. However, the base station in the cellular communication system 1 may be an eNB, which is an LTE base station. Also, the core network in the cellular communication system 1 may be an EPC (Evolved Packet Core). Furthermore, the gNB may be connected to the EPC, the eNB may be connected to the 5GC, and the gNB and the eNB may be connected via an inter-base station interface (Xn interface, X2 interface).
[0200] This application claims priority to U.S. Provisional Application No. 63 / 061883 (filed August 6, 2020), the entire contents of which are incorporated herein by reference.
[0201] (Additional Note) (introduction) A revised work item on NR eIAB (Enhancements to Integrated Access and Backhaul) was approved. Some of the objectives are to:
[0202] Topology Adaptation Extensions Specification of procedures for inter-donor IAB node mobility to enhance robustness and load balancing, including enhancements to reduce signaling load. -Specify extensions to reduce service interruptions due to IAB node movement and BH RLF recovery. · Specification of extensions to topology redundancy, including support for CP / UP separation. Topology, Routing and Transport Enhancements Specification of extensions to improve fairness, multi-hop delays, and congestion mitigation across topologies.
[0203] This appendix discusses initial considerations for Rel-17 eIAB topology adaptation extensions in terms of backhaul link quality assumptions, BH RLF indication extensions, BH RLF recovery and cell (re)selection, and lossless delivery extensions.
[0204] (Discussion) (Assuming backhaul link quality) During the Rel-15 research phase, the TR stated as one of the requirements backgrounds that "Wireless backhaul links are vulnerable to blockages due to moving objects such as vehicles, seasonal changes (foliage), infrastructure changes (new buildings), etc. Such vulnerabilities apply even to IAB nodes that are physically stationary." Therefore, various challenges arising from multi-hop / wireless backhaul and their potential solutions were studied, as captured in the TR.
[0205] Observation 1: The Rel-15 study identified various challenges posed by unstable backhaul links and potential solutions to these, which were well captured in TR38.874.
[0206] In the normative work of Rel-16, IAB nodes were assumed to be stationary, i.e., "fixed IAB nodes". Therefore, the backhaul (BH) was sufficiently stable in a well-designed deployment, even for backhaul links over mmWave and / or local area IAB nodes that may be deployed in an unmanaged manner. Therefore, only the basic functionality of the BH RLF was specified, i.e., BH RLF indication (aka "recovery failure" type 4) and recovery procedures combined with existing functionality such as RRC re-establishment, MCG / SCG failure indication, and / or conditional handover.
[0207] Observation 2: Rel-16 IAB assumed only fixed IAB nodes with sufficiently stable backhaul links.
[0208] In the Rel-17 extension, one of the intended use cases is "Mobile IAB Node", which may be part of "Inter-Donor IAB Node Mobility" even though it is not explicitly mentioned in the WID. Furthermore, sub-objectives in the WID such as "Extensions for Reducing Service Disruption Due to IAB Node Mobility and BH RLF Recovery" and "Enhancements for Topology Redundancy" clearly intend that the BH link is not stable, and mobility and BH RLF occur frequently in Rel-17 deployment scenarios. Therefore, according to the Rel-17 discussion, RAN2 should first have a common understanding of the assumptions for the BH link.
[0209] Proposal 1: RAN2 should assume that the quality of the backhaul link changes dynamically. Therefore, backhaul RLF is not a rare case as in Rel-17 eIAB.
[0210] (Extended BH RLF indication) In the Rel-16 email discussion, four types of BH RLF notifications were discussed, as shown in Figure 13.
[0211] Finally, only type 4 "recovery failure" is specified as the BH RLF indication in Rel-16, which causes the child IAB-MT to consider RLF on the BH link and initiate the RLF recovery procedure.
[0212] Finding 3: In Rel-16, only Type 4 “failure to recover” was defined as a BH RLF indication.
[0213] On the other hand, many companies still thought that other types of indications would be useful, so it was discussed further in the email. Eight out of 13 companies preferred to introduce Type 2 "attempting recovery", while the other two thought it would be discussed in Rel-17. Therefore, it can be seen that the majority of companies think that Type 2 indications are ready to be introduced in Rel-17. How to send Type 2 indications, such as by using BAP Control PDU, SIB1, or both, requires further consideration. Note that Type 1 and Type 2 have exactly the same meaning.
[0214] Proposal 2: RAN2 should agree that BH RLF indication type 2 "attempting recovery" is introduced. Whether it is sent via BAP Control PDU, SIB1, or both is for further consideration.
[0215] In addition, 9 out of 13 companies agreed to discuss Type 3 "BH link recovery" in Rel-17 as well. In detail, it can be considered whether such an explicit indication is really necessary. For example, if Type 2 indication is sent via SIB1, the indication will not be broadcasted once the BH link is not under RLF (i.e., "recovered"). Thus, downstream IAB nodes and UEs will know whether the BH link has recovered or not based on the absence of Type 2 indication in SIB1. Of course, if Type 3 indication is sent via BAP Control PDU, it has the advantage that downstream IAB nodes can quickly know the BH link recovery. However, in this case, UEs cannot know the fact because they do not have a BAP layer. Therefore, RAN2 should discuss whether Type 3 indication is necessary.
[0216] Proposal 3: If Proposal 3 can be agreed upon, RAN2 should discuss whether an explicit BH RLF indication when the BH RLF disappears, i.e., Type 3 "BH Link Recovery", will be introduced.
[0217] If Proposal 2 and / or Proposal 3 can be agreed upon, the behavior of the IAB-MT upon receiving the indication under BH link recovery should be considered. It was proposed that the IAB-MT should reduce / stop SR upon receiving Type 2 and resume operation upon receiving Type 3 (i.e., no BH RLF in the parent IAB node). This is one of the desired IAB-MT behaviors when the parent node tries to recover the BH link. It is assumed that other IAB-MT behaviors, such as suspending all RBs, are also possible.
[0218] Proposal 4: RAN2 should agree to reduce / stop scheduling requests after receiving an IAB-MT Type 2 indication and resume scheduling requests when the parent node no longer has a BH RLF.
[0219] Proposal 5: RAN2 should discuss the case where there are other IABMT operations while the parent node is trying to recover the BH link.
[0220] Regarding the IAB-DU sending the indication, if the BH link of the IAB node is under RLF, it is assumed to send a type 2 BH RLF indication. In the case of a single-connected BH, this is straightforward, since the indication is sent when RLF occurs on this BH link. However, in the case of a dual-connected BH, it becomes a bit more complicated. For example, when the IAB node detects RLF on the MCG, it initiates the MCG fault information procedure, but the SCG continues to function as the BH link, so it may not be necessary to send a type 2 indication at this point. If the MCG fault information procedure fails, such as due to T316 expiry, the IAB-MT will initiate RRC re-establishment, so a type 2 indication is sent at this point. Thus, a type 2 indication is sent when RRC re-establishment is initiated, not when the MCG / SCG fault information is triggered. In any case, since this is targeted at the behavior of the IAB-DU, it should be carefully considered whether / how to capture it in the specification. That is, it should be considered whether a note should be added or nothing should be captured in stage 2 and stage 3.
[0221] Proposal 6: RAN2 should agree that it may send a Type 2 BH RLF indication when the IAB-DU initiates an RRC re-establishment, but not when it initiates any of the RLF recovery procedures.
[0222] Proposal 7: RAN2 should discuss whether / how to capture IAB-DU behavior (i.e., Proposal 6) in its specifications.
[0223] (BH RLF Recovery and Cell (Re)Selection Enhancements) In the RRC re-establishment procedure, the IAB-MT first performs a cell selection procedure to find a suitable cell. In this cell selection procedure, potential issues were pointed out in Rel-16, such as the possibility that the IAB-MT may select a descendant node. Therefore, it was discussed in the email discussion.
[0224] Five possible solutions were discussed and summarized along with the rapporteur's views, as shown in Figure 14.
[0225] The conclusion was "No further action will be taken on this topic in Rel-16". This meant that RAN2 agreed to "Option 4: Nothing is needed as RRC re-establishment will fail if there is no BH connection". Option 4 was acceptable in Rel-16 deployment scenarios even if more time is needed for BH RLF recovery since it has to wait for failure (T301 expiry) and eventually move to idle.
[0226] Observation 4: In Rel-16, if an IAB node attempts an RRC re-establishment request to a descendant node, the IAB node must wait for the failure and eventually move to idle.
[0227] In Rel-17, cell (re)selection and RRC re-establishment may occur frequently in view of Proposal 1. Therefore, suboptimal operation, i.e. operation according to Finding 4, would cause significant performance degradation in terms of IAB topology stability and service continuity. Therefore, to optimize the IAB-MT operation during BH RLF recovery, as stated by the rapporteur in the above email discussion, "this topic may be discussed again in Rel-17."
[0228] Proposal 8: RAN2 should agree that cell (re)selection optimization is considered to avoid re-establishment on inappropriate nodes (e.g. descendant nodes).
[0229] Among the solutions identified, except for option 4 above, a common concept can be seen to be that for cell selection purposes, the IAB-MT is provided with either a whitelist or blacklist type. Considering that topology changes may occur frequently in Rel-17, for example due to "inter-donor IAB node movements", whitelists and blacklists have advantages and disadvantages depending on the topology and the location of the IAB nodes.
[0230] For example, from the perspective of IAB nodes near the IAB donor, i.e., the top of the DAG topology, it is more reasonable to provide a whitelist since the number of candidate nodes is small, possibly only IAB donor DUs.
[0231] However, in another example, where an IAB node is far away from the IAB donor, i.e., from the perspective of the bottom of the DAG topology, the whitelist may need to include a huge number of candidate nodes. Instead, the blacklist may include, for example, only downstream IAB nodes of the IAB node of concern, and possibly only a few child IAB nodes, thus providing the advantage of less overhead in this case.
[0232] One concern with whitelists is that due to the nature of Rel-17's "inter-donor IAB node movement," they may need to include candidate IAB nodes that belong to different / neighboring IAB topologies, potentially increasing the size of the list, whereas blacklists do not need to care about downstream IAB nodes, since they obviously belong to the same IAB topology.
[0233] Observation 5: Whitelists and blacklists have advantages and disadvantages depending on the topology and location of the IAB nodes.
[0234] It is therefore desirable for an IAB donor (or parent IAB node) to be able to choose between a whitelist or a blacklist when providing information to a child IAB node for cell selection purposes. It may be beneficial to reuse this information for cell reselection purposes.
[0235] Proposal 9: RAN2 should agree that whitelists or blacklists (i.e. selection structures) are provided to the IAB-MT for cell selection purposes to avoid re-establishment on descendant nodes. Whether these lists can also be used for cell reselection procedures requires further study.
[0236] If proposal 9 can be agreed upon, further consideration should be given to how the information, i.e. whitelist or blacklist, is provided. Option 1 assumes CHO configuration and may require some extensions. Option 2 assumes additional indications, e.g. BH RLF indication of type 2. Option 3 assumes providing topology-wide information not in the existing configuration. Option 5 assumes configuration by OAM, but as the rapporteur pointed out, this is doubtful.
[0237] Considering again the assumption of Rel-17 (i.e., proposal 1), i.e., parent IAB node or IAB donor should provide list to child IAB node when topology change occurs, the method of providing whitelist / blacklist should be dynamic. Therefore, option 5, i.e., OAM, should be excluded. Which method, i.e., option 1, 2, or 3, should be the baseline for enhancement needs further consideration.
[0238] Proposal 10: RAN2 should agree that the whitelist / blacklist will be dynamically provided by the parent IAB node or IAB donor whenever the topology changes. Details need further study.
[0239] (Lossless Delivery Extension) During the Rel-15 research phase, the issue of multi-hop RLC ARQ was discussed and captured in section 8.2.3 of the TR. In Rel-16, the protocol stack was defined for IAB with a non-separate RLC layer, i.e., end-to-end ARQ was eliminated in favor of hop-by-hop ARQ.
[0240] For hop-by-hop ARQ, challenges were identified in end-to-end reliability, i.e., lossless delivery of UL packets. Three solutions were identified and evaluated, as shown in Figure 15.
[0241] In Rel-16, the first solution, "changes in PDCP protocols / procedures", was not adopted because it would affect Rel-15 UEs.
[0242] The second solution, "re-routing of buffered PDCP PDUs at intermediate IAB nodes," was supported as an implementation choice at the BAP layer. Additionally, the BAP layer may "e.g., buffer data at the transmitting part of the BAP entity until the RLC-AM entity receives an acknowledgment, which is implementation dependent." These BAP implementations were considered to avoid packet loss in "most" cases of Rel-16 deployment scenarios, i.e., when fixed IAB nodes are used, but were not perfect, e.g., as shown in Figure 15.
[0243] The third solution, "introduction of UL status delivery", was a promised solution to ensure lossless delivery of UL data, taking into account the evaluation results cited in Figure 15. The idea was to delay the RLC ARQ to the UE, so that PDCP data recovery in the UE would be initiated when necessary. However, it was not specified in Rel-16, since fixed IAB nodes were assumed, and it was considered rare for UL packets to be dropped due to topology changes.
[0244] Considering the assumptions of Rel-17, i.e., in view of Proposal 1, the third solution should be further explored since it is no longer rare to lose UL packets during topology changes, which occur frequently in Rel-17. Therefore, in addition to the results captured in TR, RAN2 should discuss enhancement mechanisms to ensure lossless delivery in L2 multi-hop networks.
[0245] Proposal 11: RAN2 should agree to implement the solution specified in TR38.874, i.e. a mechanism to ensure lossless delivery under conditions of potentially frequent topology changes based on some form of "UL status delivery".
[0246] Regarding the details of the third solution, i.e., “Introduction of UL Status Distribution”, two options, C-1 and C-2, were discussed in the email discussion, as shown in Figure 16.
[0247] Regarding C-1 above, it is assumed that a "confirmation" from the IAB donor needs to be specified in the BAP or RRC for end-to-end signaling forwarding over multi-hop L2 networks. Therefore, a relatively high standard effort would be required to specify this option.
[0248] Regarding C-2 above, if it works well for IAB topologies, it can actually be implemented for Rel-16 IAB nodes, since it ultimately depends on the IAB-DU implementation when sending RLC ACK to the UE (or downstream IAB nodes), even though it should be assumed that OAM configures all IAB nodes with this option. Furthermore, it is simpler than C-1, since it assumes hop-by-hop feedback and does not assume additional Control PDUs. Therefore, C-2 should be the Rel-17 extension baseline for lossless delivery of UL packets.
[0249] Observation 6: Solution C-2 for “Introduction of UL Status Distribution” could be an extended baseline for Rel-17, which could also be implemented for Rel-16.
[0250] However, Rel-17 should expect dynamic topology changes that cause UL packet loss, so Rel-17 extensions will support C-2 as a standard supported feature. At least the Stage 2 specifications should describe the overall mechanism based on C-2. Otherwise, the 3GPP standard does not guarantee lossless delivery during IAB node handover. Furthermore, minor changes such as RLC and / or BAP are expected in Stage 3, but may not specify the details since they are considered as internal operation of IAB nodes.
[0251] Proposal 12: RAN2 should agree to specify an RLC ARQ mechanism for lossless delivery of UL packets in stage 2, which delays sending ACK to child nodes / UEs before receiving ACK from parent IAB node (i.e. C-2). Whether / how to specify in stage 3 needs further study.
Claims
1. A communication control method using a relay node having a wireless backhaul link with a higher-level node, comprising: After detecting a failure of the wireless backhaul link, the relay node determines whether to initiate a Radio Resource Control (RRC) re-establishment process for re-establishing the wireless backhaul link; When the relay node determines to start the RRC re-establishment procedure, starting the RRC re-establishment procedure; The relay node transmits, in response to initiation of the RRC re-establishment procedure, fault information indicating detection of a fault in the wireless backhaul link to a lower node of the relay node; the relay node transmitting, to the lower node, information indicating recovery from the failure of the wireless backhaul link in response to a success of the RRC re-establishment procedure; have Communications control method.
2. A relay node having a wireless backhaul link with an upper node, a control unit that determines whether to start a Radio Resource Control (RRC) re-establishment process for re-establishing the wireless backhaul link after detecting a failure of the wireless backhaul link; A transmitter unit, When the control unit determines to start the RRC re-establishment process, the control unit starts the RRC re-establishment process; The transmitter transmits fault information indicating detection of a fault in the wireless backhaul link to a lower node of the relay node in response to start of the RRC re-establishment process; The transmitter transmits, to the lower node, information indicating recovery from a failure of the wireless backhaul link in response to a success of the RRC re-establishment process. Relay node.
3. A processor for controlling a relay node having a wireless backhaul link with a higher-level node, a process of determining whether to start a radio resource control (RRC) re-establishment process for re-establishing the wireless backhaul link after detecting a failure of the wireless backhaul link; When it is determined that the RRC re-establishment process is to be started, a process of starting the RRC re-establishment process; a process of transmitting fault information indicating detection of a fault in the wireless backhaul link to a lower node of the relay node in response to initiation of the RRC re-establishment process; transmitting information indicating recovery from the failure of the wireless backhaul link to the lower node in response to a success of the RRC re-establishment procedure; Run Processor.
4. A program for controlling a relay node having a wireless backhaul link with a higher-level node, a process of determining whether to start a radio resource control (RRC) re-establishment process for re-establishing the wireless backhaul link after detecting a failure of the wireless backhaul link; When it is determined that the RRC re-establishment process is to be started, a process of starting the RRC re-establishment process; a process of transmitting fault information indicating detection of a fault in the wireless backhaul link to a lower node of the relay node in response to initiation of the RRC re-establishment process; and transmitting information indicating recovery from the failure of the wireless backhaul link to the lower node in response to a success of the RRC re-establishment procedure. program.
5. A system comprising the relay node and the upper node according to claim 2.
