Communication method and relay device

The network-controlled repeater device addresses the reduced coverage issue in 5G systems by amplifying and directionally transmitting high-frequency signals, expanding base station coverage and managing interference, while ensuring efficient beam control and detection within the 5G mobile communication framework.

WO2024232393A1PCT designated stage expired Publication Date: 2024-11-14KYOCERA CORP
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2024/017139
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-11
Filing Date
2024-05-08
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

The challenge in 5G mobile communication systems is the reduced coverage of base stations due to high-frequency radio signals, such as millimeter wave and terahertz waves, which necessitates the use of repeater devices to enhance signal reach and manage interference.

Method used

A network-controlled repeater device (NCR) is employed to relay wireless signals between base stations and user devices, controlled by the network, which amplifies and directionally transmits signals to expand coverage while minimizing interference, and includes a control terminal that manages radio resource control and beam failure detection processes.

Benefits of technology

The NCR device effectively expands the coverage of base stations, maintains low interference, and ensures efficient beam management and failure detection, even in RRC inactive states, thereby enhancing the overall performance of 5G mobile communication systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2024017139_14112024_PF_FP_ABST
    Figure JP2024017139_14112024_PF_FP_ABST
Patent Text Reader

Abstract

Provided is a communication method which is carried out by a relay device comprising a relay that carries out a relay operation for relaying a radio signal transmitted between a base station and a user device, and a control terminal that receives, from the base station, a control signal for use in control of the relay, said method comprising: a step for receiving, from a first cell, setting information pertaining to the relay operation; a step for using the setting information to carry out the relay operation when the control terminal is in a radio resource control (RRC) inactive state in the first cell; a step for stopping the relay operation when cell re-selection from the first cell to a second cell is carried out; and a step for re-starting the relay operation using the setting information when cell re-selection to the first cell is carried out within a prescribed time after the cell re-selection to the second cell has been carried out.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method and relay device

[0001] The present disclosure relates to a communication method and a relay device used in a mobile communication system.

[0002] In recent years, fifth-generation (5G) mobile communication systems have been attracting attention. NR (New Radio), a radio access technology of 5G systems, is capable of wideband transmission using higher frequency bands than LTE (Long Term Evolution), a fourth-generation radio access technology.

[0003] Wireless signals (radio waves) in high frequency bands such as millimeter waves or terahertz waves have a tendency to propagate in a highly directional manner, which can lead to a reduction in the coverage area of ​​base stations. To solve this problem, a repeater device, which is a type of relay device that relays wireless signals between a network and a user device and can be controlled from a network, has attracted attention (see, for example, Non-Patent Document 1).

[0004] Such a repeater device can, for example, amplify a radio signal received from a base station and transmit the signal using directional transmission, thereby expanding the coverage of the base station while suppressing interference. Note that such a repeater device is also called an NCR (Network-Controlled Repeater).

[0005] 3GPP contribution: RP-213700, “New SI: Study on NR Network-controlled Repeaters”

[0006] A communication method according to a first aspect is a communication method executed by a relay device having a relay device that performs a relay operation to relay radio signals transmitted between a base station and a user equipment, and a control terminal that receives a control signal used to control the relay device from the base station, and includes the steps of receiving configuration information related to the relay operation from a first cell, performing the relay operation using the configuration information when the control terminal is in a radio resource control (RRC) inactive state in the first cell, stopping the relay operation when cell reselection from the first cell to a second cell is performed, and resuming the relay operation using the configuration information when cell reselection to the first cell is performed within a predetermined time after cell reselection to the second cell.

[0007] A relay device according to a second aspect includes a relay that performs a relay operation to relay radio signals transmitted between a base station and a user equipment, and a control terminal that receives a control signal used to control the relay from the base station, wherein the control terminal includes a receiving unit that receives configuration information related to the relay operation from a first cell, and a control unit that controls the relay to perform the relay operation using the configuration information when the control terminal is in a radio resource control (RRC) inactive state in the first cell, and the control unit stops the relay operation when cell reselection from the first cell to a second cell is performed, and resumes the relay operation using the configuration information when cell reselection to the first cell is performed within a predetermined time after cell reselection to the second cell.

[0008] A communication method according to a third aspect is a communication method executed by a relay device having a relay device that performs relaying operations to relay radio signals transmitted between a base station and a user device, and a control terminal that receives a control signal from the base station used to control the relay device, and includes the steps of receiving first setting information regarding the relaying operation from the base station, receiving second setting information from the base station regarding whether the control terminal will perform a beam failure detection process with the base station when the control terminal is in a radio resource control (RRC) inactive state, and controlling the relaying operation based on the first setting information and controlling the detection process based on the second setting information when the control terminal is in the RRC inactive state.

[0009] A relay device according to a fourth aspect comprises a relay that performs relaying operations to relay radio signals transmitted between a base station and a user device, and a control terminal that receives a control signal from the base station used to control the relay, wherein the control terminal includes a receiving unit that receives first setting information regarding the relaying operation from the base station and receives second setting information from the base station regarding whether the control terminal will perform a beam failure detection process with the base station when the control terminal is in a radio resource control (RRC) inactive state, and a control unit that controls the relaying operation based on the first setting information and controls the detection process based on the second setting information when the control terminal is in the RRC inactive state.

[0010] 1 is a diagram illustrating a configuration of a mobile communication system according to an embodiment. FIG. 2 is a diagram illustrating a protocol stack configuration of a radio interface of a user plane that handles data. FIG. 3 is a diagram illustrating a protocol stack configuration of a radio interface of a control plane that handles signaling (control signals). FIG. 4 is a diagram illustrating an example of an application scenario of an NCR device (relay device) according to an embodiment. FIG. 5 is a diagram illustrating an example of an application scenario of an NCR device according to an embodiment. FIG. 6 is a diagram illustrating an example of a control method of an NCR device according to an embodiment. FIG. 7 is a diagram illustrating an example of a configuration of a protocol stack in an NCR device according to an embodiment. FIG. 8 is a diagram illustrating an example of a configuration of an NCR device according to an embodiment. FIG. 9 is a diagram illustrating a configuration of a UE (user equipment) according to an embodiment. FIG. 10 is a diagram illustrating an example of a configuration of a gNB (base station) according to an embodiment. FIG. 11 is a diagram illustrating an operation of a mobile communication system according to a first embodiment. FIG. 12 is a flow diagram illustrating an example of an operation of an NCR device according to a first embodiment. FIG. 13 is a diagram illustrating an operation of a mobile communication system according to a second embodiment. FIG. 14 is a flow diagram illustrating an example of an operation of an NCR device according to a second embodiment. FIG. 15 is a diagram illustrating a RIS device (relay device) according to a third embodiment. FIG. 16 is a diagram illustrating a RIS device (relay device) according to a third embodiment.

[0011] 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.

[0012] (1) First Embodiment First, a description will be given of the first embodiment. A relay device according to the embodiment is a repeater device (that is, an NCR device) that can be controlled from a network.

[0013] (1.1) Overview of Mobile Communication System FIG. 1 is a diagram showing the configuration of a mobile communication system according to an embodiment.

[0014] The mobile communication system 1 conforms to the 5th Generation System (5GS) standard of the 3rd Generation Partnership Project (3GPP) (registered trademark; the same applies hereinafter). While the following description will be given using 5GS as an example, the mobile communication system may also be at least partially based on the Long Term Evolution (LTE) system. The mobile communication system may also be at least partially based on the 6th Generation (6G) system.

[0015] The mobile communication system 1 includes a user equipment (UE) 100, a 5G radio access network (NG-RAN: Next Generation Radio Access Network) 10, and a 5G core network (5GC: 5G Core Network) 20. Hereinafter, the NG-RAN 10 may be simply referred to as the RAN 10. Furthermore, the 5GC 20 may be simply referred to as the core network (CN) 20. The RAN 10 and the CN 20 constitute a network 5 of the mobile communication system 1.

[0016] The UE 100 is a mobile wireless communication device. The UE 100 may be any device that is used by a user. For example, the UE 100 may be a mobile phone terminal (including a smartphone) and / or a tablet terminal, a notebook PC, a communication module (including a communication card or a chipset), a sensor or a device provided in a sensor, a vehicle or a device provided in a vehicle (Vehicle UE), or an aircraft or a device provided in an aircraft (Aerial UE).

[0017] The NG-RAN 10 includes a base station (referred to as "gNB" in the 5G system) 200. The gNBs 200 are connected to each other via an Xn interface, which is an interface between base stations. The gNB 200 manages one or more cells. The gNB 200 performs wireless communication with the UE 100 that has established a connection with its own cell. The gNB 200 has a radio resource management (RRM) function, a routing function for user data (hereinafter simply referred to as "data"), a measurement control function for mobility control and scheduling, etc. The term "cell" is used to indicate the smallest unit of a wireless communication area. The term "cell" is also used to indicate a function or resource for wireless communication with the UE 100. One cell belongs to one carrier frequency (hereinafter simply referred to as "frequency").

[0018] The gNB200 may be functionally divided into a central unit (CU) and a distributed unit (DU). The CU controls the DU. The CU is a unit including upper layers included in the protocol stack described below, such as an RRC layer, an SDAP layer, and a PDCP layer. The CU is connected to the core network via an NG interface, which is a backhaul interface. The CU is connected to neighboring base stations via an Xn interface, which is an interface between base stations. The DU forms a cell. The DU202 is a unit including lower layers included in the protocol stack described below, such as an RLC layer, a MAC layer, and a PHY layer. The DU is connected to the CU via an F1 interface, which is a fronthaul interface.

[0019] In addition, gNBs can also be connected to the Evolved Packet Core (EPC), which is the core network of LTE. LTE base stations can also be connected to 5GC. LTE base stations and gNBs can also be connected via an inter-base station interface.

[0020] The 5GC20 includes an AMF (Access and Mobility Management Function) and a UPF (User Plane Function) 300. The AMF performs various mobility controls for the UE 100. The AMF manages the mobility of the UE 100 by communicating with the UE 100 using NAS (Non-Access Stratum) signaling. The UPF controls data forwarding. The AMF and the UPF are connected to the gNB 200 via an NG interface, which is an interface between a base station and a core network.

[0021] FIG. 2 is a diagram showing the configuration of a protocol stack of a radio interface of a user plane that handles data.

[0022] The user plane radio interface protocol includes a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a service data adaptation protocol (SDAP) layer.

[0023] 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 UE100 and the PHY layer of gNB200 via a physical channel. The PHY layer of UE100 receives downlink control information (DCI) transmitted from gNB200 on a physical downlink control channel (PDCCH). Specifically, UE100 performs blind decoding of the PDCCH using a radio network temporary identifier (RNTI) and acquires successfully decoded DCI as DCI addressed to the UE. The DCI transmitted from gNB200 has CRC (Cyclic Redundancy Code) bits scrambled by the RNTI added.

[0024] In addition, the gNB 200 transmits a synchronization signal block (SSB: Synchronization Signal / PBCH block). For example, the SSB is composed of four consecutive OFDM (Orthogonal Frequency Division Multiplex) symbols, and includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a physical broadcast channel (PBCH) / master information block (MIB), and a PBCH demodulation reference signal (DMRS). The bandwidth of the SSB is, for example, 240 consecutive subcarriers, that is, a bandwidth of 20 RBs.

[0025] 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 UE 100 and the MAC layer of the gNB 200 via a transport channel. The MAC layer of the gNB 200 includes 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 allocated to the UE 100.

[0026] The RLC layer transmits data to the receiving RLC layer using the functions of the MAC layer and PHY layer. Data and control information are transmitted between the RLC layer of the UE 100 and the RLC layer of the gNB 200 via a logical channel.

[0027] The PDCP layer performs header compression / decompression, encryption / decryption, and the like.

[0028] The SDAP layer maps IP flows, which are units for Quality of Service (QoS) control by the core network, to radio bearers, which are units for QoS control by the Access Stratum (AS). Note that if the RAN is connected to the EPC, SDAP may not be required.

[0029] FIG. 3 is a diagram showing the configuration of a protocol stack of a radio interface of a control plane that handles signaling (control signals).

[0030] The protocol stack of the radio interface of the control plane has an RRC (Radio Resource Control) layer and an NAS (Non-Access Stratum) layer instead of the SDAP layer shown in FIG.

[0031] RRC signaling for various settings is transmitted between the RRC layer of UE100 and the RRC layer of gNB200. 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 a connection (RRC connection) between the RRC of UE100 and the RRC of gNB200, UE100 is in an RRC connected state. When there is no connection (RRC connection) between the RRC of UE100 and the RRC of gNB200, UE100 is in an RRC idle state. When the connection between the RRC of UE100 and the RRC of gNB200 is suspended, UE100 is in an RRC inactive state.

[0032] 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 UE 100 and the NAS layer of the AMF 300A. Note that the UE 100 has an application layer and the like in addition to the radio interface protocol. Also, a layer lower than the NAS layer is called an AS (Access Stratum).

[0033] (1.2) Example of Application Scenario of Relay Device FIGS. 4 and 5 are diagrams showing an example of an application scenario of the NCR device according to the embodiment.

[0034] Compared to 4G / LTE, 5G / NR enables broadband transmission using higher frequency bands. Radio signals in high frequency bands, such as the millimeter wave band or terahertz wave band, have high line-of-sight properties, which poses a challenge in reducing the coverage of the gNB 200. In FIG. 4, the UE 100 may be located outside the coverage area of ​​the gNB 200, for example, outside an area where radio signals can be received directly from the gNB 200. A shield may exist between the gNB 200 and the UE 100, preventing the UE 100 from communicating with the gNB 200 within line-of-sight.

[0035] As shown in Figure 4, a repeater device (500A), which is a type of relay device that relays radio signals between the gNB 200 and the UE 100, and an NCR device 500A that can be controlled from the network 5 is introduced into the mobile communication system 1. Such a repeater device may be referred to as a smart repeater device.

[0036] For example, the NCR device 500A amplifies a radio signal (radio wave) received from the gNB 200 and transmits it by directional transmission. Specifically, the NCR device 500A receives a radio signal transmitted by the gNB 200 by beamforming. The NCR device 500A then amplifies the received radio signal without demodulating or modulating it, and transmits the amplified radio signal by directional transmission. Here, the NCR device 500A may transmit a radio signal with a fixed directivity (beam). The NCR device 500A may also transmit a radio signal with a variable (adaptive) directional beam. This allows the coverage of the gNB 200 to be efficiently expanded.

[0037] Also, as shown in FIG. 5, a new UE (hereinafter referred to as "NCR-MT (Mobile termination)") 100B, which is a type of control terminal for controlling the NCR device 500A, is introduced. That is, the NCR device 500A relays radio signals transmitted between the gNB 200 and the UE 100, specifically, the radio signals. NCR-Fwd (Forward) 510A, which is a type of repeater that changes the propagation state of the radio signal without demodulating or modulating the radio signal, and NCR-MT 520A that performs wireless communication with the gNB 200 and controls the NCR-Fwd 510A.

[0038] In this way, the NCR-MT 520A establishes a wireless connection with the gNB 200 and performs wireless communication with the gNB 200, thereby controlling the NCR device 500A in cooperation with the gNB 200. This enables efficient coverage expansion using the NCR device 500A. The NCR-MT 520A controls the NCR device 500A according to control from the gNB 200. The NCR-MT 520A also has functions similar to those of the UE 100.

[0039] The NCR-MT 520A may be configured separately from the NCR-Fwd 510A. For example, the NCR-MT 520A may be located near the NCR-Fwd 510A and electrically connected to the NCR-Fwd 510A. The NCR-MT 520A may be connected to the NCR-Fwd 510A by wire or wirelessly. Alternatively, the NCR-MT 520A may be configured integrally with the NCR-Fwd 510A. The NCR-MT 520A and the NCR-Fwd 510A may be fixedly installed, for example, at the coverage edge (cell edge) of the gNB 200 or on a wall or window of a building. The NCR-MT 520A and the NCR-Fwd 510A may be installed, for example, in a vehicle or the like and be mobile. Also, one NCR-MT 520A may control multiple NCR-Fwds 510A.

[0040] Note that the configuration is not limited to one in which the NCR-MT 520A directly controls one or more NCR-Fwds 510A, and may be one in which the NCR-MT 520A indirectly controls one or more NCR-Fwds 510A. For example, the NCR-MT 520A may control one or more NCR-Fwds 510A via a higher layer (for example, an application layer).

[0041] In the example shown in FIG. 5, the NCR device 500A (NCR-Fwd 510A) dynamically or quasi-statically changes the beam to be transmitted or received. For example, the NCR-Fwd 510A forms a beam toward each of the UE 100a and the UE 100b. The NCR-Fwd 510A may also form a beam toward the gNB 200. For example, in the communication resources between the gNB 200 and the UE 100a, the NCR-Fwd 510A transmits a radio signal received from the gNB 200 toward the UE 100a by beamforming, and / or transmits a radio signal received from the UE 100a toward the gNB 200 by beamforming. In the communication resources between the gNB 200 and the UE 100b, the NCR-Fwd 510A transmits a radio signal received from the gNB 200 toward the UE 100b by beamforming, and / or transmits a radio signal received from the UE 100b by beamforming toward the gNB 200. Instead of or in addition to beamforming, the NCR-Fwd 510A may form a null (so-called null steering) toward a UE 100 (not shown) and / or a neighboring gNB 200 (not shown) that is not a communication partner for interference suppression.

[0042] FIG. 6 is a diagram showing an example of a control method for the NCR device 500A according to the embodiment.

[0043] The NCR-Fwd 510A relays radio signals (also referred to as "UE signals") between the gNB 200 and the UE 100. The UE signals include uplink signals (also referred to as "UE-UL signals") transmitted from the UE 100 to the gNB 200 and downlink signals (also referred to as "UE-DL signals") transmitted from the gNB 200 to the UE 100. The NCR-Fwd 510A relays UE-UL signals from the UE 100 to the gNB 200 and relays UE-DL signals from the gNB 200 to the UE 100. The radio link between the NCR-Fwd 510A and the UE 100 is also referred to as an "access link." The radio link between the NCR-Fwd 510A and the gNB 200 is also referred to as a "backhaul link."

[0044] The NCR-MT 520A transmits and receives radio signals (herein referred to as "NCR-MT signals") to and from the gNB 200. The NCR-MT signals include uplink signals (herein referred to as "NCR-MT-UL signals") transmitted from the NCR-MT 520A to the gNB 200, and downlink signals (herein referred to as "NCR-MT-DL signals") transmitted from the gNB 200 to the NCR-MT 520A. The NCR-MT-DL signals include signaling (e.g., NCR control signals) for controlling the NCR device 500A. The radio link between the NCR-MT 520A and the gNB 200 is also referred to as a "control link."

[0045] The gNB200 directs a beam to the NCR-MT520A based on the NCR-MT-UL signal from the NCR-MT520A. Because the NCR device 500A is co-located with the NCR-MT520A, if the backhaul link and the control link have the same frequency, when the gNB200 directs a beam to the NCR-MT520A, the beam will also be directed to the NCR-Fwd510A. The gNB200 uses this beam to transmit an NCR-MT-DL signal and a UE-DL signal. The NCR-MT520A receives the NCR-MT-DL signal. In addition, when the NCR-Fwd 510A and the NCR-MT 520A are at least partially integrated, the functions (e.g., antennas) for transmitting, receiving, or relaying UE signals and / or NCR-MT signals may be integrated in the NCR-Fwd 510A and the NCR-MT 520A. Note that the term "beam" includes a transmitting beam and / or a receiving beam. A beam is a general term for transmission and / or reception controlled to maximize the power of transmitted waves and / or received waves in a specific direction by adjusting / adapting antenna weights, etc.

[0046] FIG. 7 is a diagram for explaining an example of the configuration of a protocol stack in the NCR device 500A according to the embodiment.

[0047] The NCR-Fwd 510A relays radio signals transmitted and received between the gNB 200 and the UE 100. The NCR-Fwd 510A has an RF (Radio Frequency) function that amplifies and relays received radio signals, and performs directional transmission using beamforming (e.g., analog beamforming).

[0048] The NCR-MT 520A has entities for each of the layers: Layer 1 and / or Layer 2 (L1 / L2), RRC, and NAS. The L1 / L2 (especially PHY and MAC) and RRC of the NCR-MT 520A are also referred to as the "AS of the NCR-MT 520A."

[0049] The NCR-MT 520A may have at least one of an OAM client that communicates with the OAM (Operation, Administration, Maintenance) server 400, a NAS layer that communicates with the AMF 300A, and an F1-AP (Application Protocol) layer. The OAM client, NAS layer, and F1-AP layer of the NCR-MT 520A are also referred to as the "upper layers of the NCR-MT 520A" based on the AS of the NCR-MT 520A.

[0050] A backhaul link is established between the gNB200 and the NCR-Fwd510A. An access link is established between the UE100 and the NCR-Fwd510A. The NCR-Fwd510A relays radio signals transmitted between the gNB200 and the UE100 via the backhaul link and the access link. The NCR-Fwd510A changes the propagation state of the radio signal without demodulating or modulating the radio signal.

[0051] In addition, a control link is established between gNB200 and L1 / L2 of NCR-MT520A. L1 / L2 of NCR-MT520A transmits and receives L1 / L2 signaling with gNB200 via the control link. An RRC connection is established between gNB200 and RRC of NCR-MT520A. RRC of NCR-MT520A transmits and receives RRC messages with gNB200 via the RRC connection. NCR-MT520A receives downlink signaling (also referred to as an "NCR control signal" or simply "control signal") from gNB200 via the RRC connection and / or the control link.

[0052] The gNB 200 (transmitter 210) transmits an NCR control signal to the NCR-MT 520A. The NCR control signal may be an RRC message, which is a control signal of the RRC layer (i.e., Layer 3). The NCR control signal may be a MAC Control Element (CE), which is a control signal of the MAC layer (i.e., Layer 2). The NCR control signal may be downlink control information (DCI), which is a control signal of the PHY layer (i.e., Layer 1). The NCR control signal may be UE-specific signaling. The NCR control signal may be broadcast signaling. The NCR control signal may be a fronthaul message (e.g., an F1-AP message). If the NCR-MT 520A is a type or part of a base station, the NCR-MT 520A may communicate with the gNB 200 via an Xn AP (Xn-AP), which is an inter-base station interface.

[0053] Hereinafter, an NCR control signal transmitted in an RRC message (and / or MAC CE) and used for static or semi-static control of the NCR-Fwd 510A will also be referred to as "NCR setting information (NCR setting)" or simply as "setting information." Such setting information may also be referred to as "Side Control Configuration." Here, the RRC message may be an RRC Reconfiguration message. The NCR setting information includes, for example, information for setting the NCR-Fwd 510A to on / off. The NCR setting information may also include, for example, information for semi-static beam setting of the NCR-Fwd 510A.

[0054] On the other hand, an NCR control signal transmitted in L1 / L2 signaling, i.e., DCI (and / or MAC CE), and used for dynamic control of the NCR-Fwd 510A is also referred to as "NCR control information" or simply "control information." The NCR control information may also be referred to as "Side Control Information." The CRC bits of the PDCCH carrying the NCR control information are scrambled by a newly introduced dedicated RNTI. This dedicated RNTI is also referred to as "NCR-RNTI." The NCR control information may include, for example, information on dynamic beam control of the NCR-Fwd 510A. The NCR setting information may include information instructing dynamic on / off of the NCR-Fwd 510A.

[0055] For example, when the NCR-MT 520A is in the RRC connected state, the NCR device 500A can turn on or off the NCR-Fwd 510A according to the NCR control information received from the gNB 200. On the other hand, after the NCR-MT 520A transitions to the RRC inactive state, the NCR device 500A can turn on or off the NCR-Fwd 510A according to the latest (last) setting information received from the gNB 200.

[0056] In addition, the NCR control signal (e.g., NCR setting information by RRC and / or NCR control information by L1 / L2 signaling) held by the NCR device 500A (NCR-MT 520A) may be referred to as an NCR-Fwd context.

[0057] Also, if a radio link failure (RLF) with the gNB200 is detected by the NCR-MT520A, the NCR-MT520A performs cell selection and triggers RRC connection re-establishment (also referred to as "RRC re-establishment"). Here, if the NCR-MT520A enters an RRC idle state because a suitable cell cannot be found in the cell selection, the NCR device 500A turns off the NCR-Fwd510A. Note that the NCR-Fwd510A is off during the RRC connection re-establishment procedure.

[0058] The NCR control signal may include frequency control information that specifies the center frequency of the radio signal (e.g., component carrier) to be relayed by the NCR-Fwd 510A. When the NCR control signal received from the gNB 200 includes frequency control information, the NCR-MT 520A (control unit 523) controls the NCR-Fwd 510A to relay the radio signal having the center frequency indicated by the frequency control information (step S2A). The NCR control signal may include multiple pieces of frequency control information that specify different center frequencies. By including frequency control information in the NCR control signal, the gNB 200 can specify the center frequency of the radio signal to be relayed by the NCR-Fwd 510A via the NCR-MT 520A.

[0059] The NCR control signal may include mode control information that specifies the operation mode of the NCR-Fwd 510A. The mode control information may be associated with frequency control information (center frequency). The operation mode may be any of a mode in which the NCR-Fwd 510A performs omnidirectional transmission and / or reception, a mode in which the NCR-Fwd 510A performs fixed-directivity transmission and / or reception, a mode in which the NCR-Fwd 510A performs transmission and / or reception using a variable directional beam, and a mode in which the NCR-Fwd 510A performs MIMO (Multiple Input Multiple Output) relay transmission. The operation mode may be any of a beamforming mode (i.e., a mode that emphasizes improving the desired wave) and a null steering mode (i.e., a mode that emphasizes suppressing interference waves). When the NCR control signal received from the gNB 200 includes mode control information, the NCR-MT 520A (control unit 523) controls the NCR-Fwd 510A to operate in the operating mode indicated by the mode control information (step S2A). By including the mode control information in the NCR control signal, the gNB 200 can specify the operating mode of the NCR-Fwd 510A via the NCR-MT 520A.

[0060] Here, the mode in which the NCR device 500A performs omnidirectional transmission and / or reception is a mode in which the NCR-Fwd 510A performs omnidirectional relaying, and may be referred to as omni-mode. The mode in which the NCR-Fwd 510A performs fixed directional transmission and / or reception may be a directional mode realized by a single directional antenna. This mode may be a beamforming mode realized by applying fixed phase / amplitude control (antenna weight control) to multiple antennas. Any of these modes may be specified (set) by the gNB 200 to the NCR-MT 520A. The mode in which the NCR-Fwd 510A performs transmission and / or reception using a variable directional beam may be a mode in which analog beamforming is performed. This mode may be a mode in which digital beamforming is performed. This mode may be a mode in which hybrid beamforming is performed. This mode may be a mode in which an adaptive beam specific to the UE 100 is formed. Any of these modes may be specified (set) from the gNB 200 to the NCR-MT 520A. Note that in an operation mode in which beamforming is performed, beam control information, described below, may be provided from the gNB 200 to the NCR-MT 520A. The mode in which the NCR device 500A performs MIMO relay transmission may be a mode in which SU (Single-User) spatial multiplexing is performed. This mode may also be a mode in which MU (Multi-User) spatial multiplexing is performed. This mode may also be a mode in which transmit diversity is performed. Any of these modes may be specified (set) from the gNB 200 to the NCR-MT 520A. The operation modes may include a mode in which relay transmission by the NCR-Fwd 510A is turned on (activated) and a mode in which relay transmission by the NCR-Fwd 510A is turned off (deactivated). Any of these modes may be specified (set) by an NCR control signal from gNB200 to NCR-MT520A.

[0061] The NCR control signal may include beam control information that specifies the transmission direction, transmission weight, or beam pattern when the NCR-Fwd 510A performs directional transmission. The beam control information may be associated with frequency control information (center frequency). The beam control information may include a PMI (Precoding Matrix Indicator). The beam control information may include beam formation angle information. When the NCR control signal received from the gNB 200 includes beam control information, the NCR-MT 520A (control unit 523) controls the NCR-Fwd 510A to form the transmission directivity (beam) indicated by the beam control information. By including beam control information in the NCR control signal, the gNB 200 can control the transmission directivity of the NCR device 500A via the NCR-MT 520A.

[0062] The NCR control signal may include output control information that specifies the degree to which the NCR-Fwd 510A amplifies the radio signal (amplification gain) or transmission power. The output control information may be information indicating a difference value (i.e., a relative value) between the current amplification gain or transmission power and a target amplification gain or transmission power. When the NCR control signal received from the gNB 200 includes output control information, the NCR-MT 520A (control unit 523) controls the NCR-Fwd 510A to change the amplification gain or transmission power to the amplification gain or transmission power indicated by the output control information. The output control information may be associated with frequency control information (center frequency). The output control information may be information that specifies any one of the amplifier gain, beamforming gain, and antenna gain of the NCR-Fwd 510A. The output control information may be information that specifies the transmission power of the NCR-Fwd 510A.

[0063] When one NCR-MT 520A controls multiple NCR-Fwds 510A, the gNB 200 (transmitter 210) may transmit an NCR control signal to the NCR-MT 520A for each NCR-Fwd 510A. In this case, the NCR control signal may include an identifier (NCR identifier) ​​of the corresponding NCR-Fwd 510A. The NCR-MT 520A (controller 523) that controls multiple NCR-Fwds 510A determines the NCR-Fwd 510A to which the NCR control signal is applied based on the NCR identifier included in the NCR control signal received from the gNB 200. Note that the NCR identifier may be transmitted from the NCR-MT 520A to the gNB 200 together with the NCR control signal, even when the NCR-MT 520A controls only one NCR-Fwd 510A.

[0064] In this way, the NCR-MT 520A (control unit 523) controls the NCR-Fwd 510A based on the NCR control signal from the gNB 200. This enables the gNB 200 to control the NCR-Fwd 510A via the NCR-MT 520A.

[0065] (1.3) Configuration Example of Each Device A configuration example of each device in the mobile communication system 1 according to the embodiment will be described.

[0066] 8 is a diagram showing an example of the configuration of an NCR device 500A (relay device) according to an embodiment. The NCR device 500A includes an NCR-Fwd 510A, an NCR-MT 520A, and an interface 530.

[0067] The NCR-Fwd 510A includes a radio unit 511A and an NCR control unit 512A. The radio unit 511A includes an antenna unit 511a including multiple antennas (multiple antenna elements), an RF circuit 511b including an amplifier, and a directivity control unit 511c that controls the directivity of the antenna unit 511a. The RF circuit 511b amplifies and relays (transmits) radio signals transmitted and received by the antenna unit 511a. The RF circuit 511b may convert analog radio signals into digital signals and then reconvert them to analog signals after digital signal processing. The directivity control unit 511c may perform analog beamforming using analog signal processing. The directivity control unit 511c may perform digital beamforming using digital signal processing. The directivity control unit 511c may perform hybrid analog and digital beamforming. The NCR control unit 512A controls the radio unit 511A in response to control signals from the NCR-MT 520A. The NCR control unit 512A may include at least one processor.

[0068] The NCR-MT 520A has a receiving unit 521, a transmitting unit 522, and a control unit 523. The receiving unit 521 performs various receptions under the control of the control unit 523. The receiving unit 521 includes an antenna and a receiver. The receiver converts a radio signal (wireless signal) received by the antenna into a baseband signal (received signal) and outputs it to the control unit 523. The transmitting unit 522 performs various transmissions under the control of the control unit 523. The transmitting unit 522 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmitted signal) output by the control unit 523 into a radio signal and transmits it from the antenna. The control unit 523 performs various controls on the NCR-MT 520A. The operations of the NCR-MT 520A (and the NCR device 500A) described above and below may be operations controlled by the control unit 523. The control unit 523 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in 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 processes. In addition, the control unit 523 executes the functions of at least one layer of PHY, MAC, RRC, and F1-AP.

[0069] The interface 530 electrically or logically connects the NCR-Fwd 510A and the NCR-MT 520A. The control unit 523 of the NCR-MT 520A controls the NCR-Fwd 510A via the interface 530. The interface 530 may be a logical entity of an upper layer (e.g., an application layer).

[0070] In the embodiment, the receiver 521 of the NCR-MT 520A receives signaling (NCR control signal) used to control the NCR device 500A from the gNB 200 via wireless communication. The controller 523 of the NCR-MT 520A controls the NCR device 500A based on the signaling. This enables the gNB 200 to control the NCR-Fwd 510A via the NCR-MT 520A.

[0071] (1.3.2) Example of configuration of user equipment Fig. 9 is a diagram showing the configuration of the UE 100 (user equipment) according to the embodiment. The UE 100 has a receiving unit 110, a transmitting unit 120, and a control unit 130. The receiving unit 110 and the transmitting unit 120 constitute a wireless communication unit that performs wireless communication with the gNB 200.

[0072] The receiving unit 110 performs various types of reception under the control of the control unit 130. The receiving unit 110 includes an antenna and a receiver. The receiver converts a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 130.

[0073] The transmitting unit 120 performs various transmissions under the control of the control unit 130. The transmitting unit 120 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmission signal) output by the control unit 130 into a radio signal and transmits it from the antenna.

[0074] The control unit 130 performs various controls and processes in the UE 100. Such processes include processes of each layer described below. The operations of the UE 100 described above and below may be operations controlled by the control unit 130. The control unit 130 includes at least one processor and at least one 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 processes.

[0075] (1.3.3) Configuration example of base station Fig. 10 is a diagram showing a configuration example of a gNB 200 (base station) according to an embodiment. The gNB 200 has a transmitter 210, a receiver 220, a controller 230, and a backhaul communication unit 240.

[0076] The transmitting unit 210 performs various transmissions under the control of the control unit 230. The transmitting unit 210 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmission signal) output by the control unit 230 into a radio signal and transmits it from the antenna. The receiving unit 220 performs various receptions under the control of the control unit 230. The receiving unit 220 includes an antenna and a receiver. The receiver converts a radio signal received by the antenna into a baseband signal (reception signal) and outputs it to the control unit 230. The transmitting unit 210 and the receiving unit 220 may be capable of beamforming using multiple antennas.

[0077] The control unit 230 performs various controls in the gNB 200. The operations of the gNB 200 described above and below may be operations controlled by the control unit 230. The control unit 230 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in 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 processes.

[0078] The backhaul communication unit 240 is connected to adjacent base stations via an inter-base station interface. The backhaul communication unit 240 is connected to the AMF / UPF 300 via a base station-core network interface. The gNB is composed of a CU (Central Unit) and a DU (Distributed Unit) (i.e., functionally divided), and the two units may be connected via an F1 interface.

[0079] In the embodiment, the transmitter 210 of the gNB 200 transmits signaling (NCR control signal) used to control the NCR-Fwd 510A to the NCR-MT 520A via wireless communication. This enables the gNB 200 to control the NCR device 500A via the NCR-MT 520A.

[0080] (1.4) Operation According to the First Embodiment FIGS. 11 and 12 are diagrams for explaining the operation of the mobile communication system 1 according to the first embodiment.

[0081] As shown in STEP 1 of Figure 11, the NCR device 500A is in an RRC connected state in cell a (first cell) of the gNB 200a. The gNB 200a transmits an RRC Reconfiguration message including the NCR setting to the NCR device 500A. The NCR device 500A receives the RRC Reconfiguration message including the NCR setting from the gNB 200a (cell a) and performs relay operation using the NCR setting.

[0082] In this embodiment, the NCR configuration includes a periodic beam indication. In the periodic beam indication, the period and beam are configured by the RRC. The NCR device 500A performs periodic beamforming based on the periodic beam indication.

[0083] As shown in STEP 2 of Figure 11, gNB200a transmits an RRC Release message including a suspend setting to NCR device 500A. NCR device 500A receives the RRC Release message from gNB200a (cell a) and transitions to an RRC inactive state.

[0084] In this embodiment, the RRC Release message for transitioning the NCR-MT 520A from the RRC connected state to the RRC inactive state includes a timer value.

[0085] After the NCR-MT 520A transitions to the RRC inactive state, the NCR-MT 520A controls the NCR-Fwd 510A according to the latest (last) NCR setting. In this embodiment, the NCR-MT 520A controls the NCR-Fwd 510A to continue periodic beamforming operation according to the NCR setting (latest setting) received in STEP 1.

[0086] 12, the NCR-MT 520A in the RRC inactive state performs cell reselection from cell a (first cell) to cell b (second cell). In response to the cell reselection to cell b (second cell), the NCR-MT 520A turns off the NCR-Fwd 510A (i.e., stops the relay operation).

[0087] In this embodiment, the NCR-MT 520A starts a timer to which the above-mentioned timer value is set in response to cell reselection from cell a to cell b. At least while the timer is running, the NCR-MT 520A retains the NCR settings (latest settings) without discarding them, even if the NCR-Fwd 510A is off.

[0088] In the illustrated example, cell b is managed by a gNB 200b that is different from gNB 200a that manages cell a. However, cell a and cell b may be managed by the same gNB 200.

[0089] 12, if the NCR-MT 520A performs cell reselection to cell a within a predetermined time after performing cell reselection to cell b, the NCR-MT 520A resumes relay operation using the NCR setting (latest setting). Specifically, if the NCR-MT 520A performs cell reselection to cell a before the timer expires, the NCR-MT 520A resumes periodic beamforming using the NCR setting (latest setting).

[0090] In this way, when the NCR-MT 520A in the RRC inactive state reselects the original cell within a predetermined period after reselecting another cell, it restores (turns on) the operation of the NCR-Fwd 510A according to the latest settings. On the other hand, when the NCR-MT 520A in the RRC inactive state reselects the original cell after a predetermined period has elapsed after reselecting another cell, it continues to turn off the NCR-Fwd 510A.

[0091] This allows the NCR-MT520A to autonomously resume relaying operations when it returns to the original cell after temporarily camping in another cell, thereby enabling efficient control of relaying operations.

[0092] FIG. 13 is a flowchart showing an example of the operation of the NCR device 500A according to the first embodiment.

[0093] In step S11, the NCR-MT 520A in the RRC connected state receives an NCR setting from the gNB 200. The NCR setting includes a periodic beam indication. The NCR-MT 520A may store the cell ID of the serving cell (cell a) when the NCR setting is performed.

[0094] In step S12, the NCR-MT 520A in the RRC connected state performs relay operation with periodic beamforming using the NCR setting received in step S11.

[0095] In step S13, the NCR-MT 520A in the RRC connected state receives an RRC Release message including a timer value from the gNB 200. The RRC Release message includes a suspend setting, and the NCR-MT 520A transitions to the RRC inactive state in accordance with the suspend setting.

[0096] In step S14, the NCR-MT 520A in the RRC inactive state continues the relay operation with periodic beamforming using the NCR configuration received in step S11.

[0097] In step S15, the NCR-MT 520A in the RRC inactive state performs cell reselection to another cell (cell b). In response to the cell reselection to another cell (cell b), the NCR-MT 520A in the RRC inactive state turns off the NCR-Fwd 510A and starts the timer to which the timer value received in step S13 is set.

[0098] In step S16, the NCR-MT 520A determines whether to reselect the original cell (cell a) where the NCR setting was performed. The NCR-MT 520A may identify the original cell by comparing the stored cell ID with the cell ID of the reselected cell.

[0099] When cell reselection to the original cell (cell a) is performed (step S16: YES), in step S17, the NCR-MT 520A determines whether the timer started in step S15 is running (has not yet expired). If it is determined that the timer has expired (step S17: NO), the NCR-MT 520A keeps the NCR-Fwd 510A off. When the timer expires, the NCR-MT 520A may discard the NCR settings (latest settings) that it has retained.

[0100] On the other hand, if it is determined that the timer is running (step S17: YES), in step S18, NCR-MT520A turns on NCR-Fwd510A and resumes relay operation with periodic beamforming using the NCR settings (latest settings).

[0101] (2) Second Embodiment The second embodiment will be described, focusing mainly on the differences from the first embodiment. The second embodiment relates to beam fault detection and recovery performed by the NCR-MT520A. Note that the second embodiment may be implemented separately from the first embodiment. The second embodiment may also be implemented in combination with the first embodiment.

[0102] (2.1) Overview of Beam Failure Detection and Recovery An overview of general beam failure detection and recovery will be described. General beam failure detection (also referred to as "BFD") and beam failure recovery (also referred to as "BFR") are performed by UE100 in an RRC connected state. For beam failure detection, gNB200 configures UE100 with SSB or CSI (Channel State Information)-RS as a reference signal (RS) for BFD. The MAC entity of UE100 in an RRC connected state declares (detects) beam failure when the number of beam failure instance indicators from the physical layer reaches a threshold (maximum count value) set by gNB200 before a timer set by gNB200 expires.

[0103] After beam failure is detected in the primary cell (PCell), the MAC entity of UE100 does the following: - triggers BFR by initiating a random access procedure in the PCell; - selects an appropriate beam to perform BFR (if the gNB200 provides dedicated random access resources for a specific beam, it is prioritized by UE100); - if the random access procedure includes contention-based random access, includes an indicator of beam failure in the PCell in the BFR (Beam Failure Recovery) MAC CE (Control Element).

[0104] When the random access procedure is completed, the UE 100 considers that the BFR of the PCell is completed.

[0105] On the other hand, as described above, even if the NCR-MT 520A transitions from the RRC connected state to the RRC inactive state, the NCR device 500A can continue relaying according to the latest NCR settings. Therefore, it is desirable that the NCR-MT 520A be able to perform BFD and BFR even in the RRC inactive state. For example, when the NCR-MT 520A is in the RRC inactive state and the NCR-Fwd 510A is on, the NCR device 500A can turn off the NCR-Fwd 510A in response to detecting a beam obstruction with the gNB 200.

[0106] In the second embodiment below, an operation that enables the NCR-MT 520A in the RRC inactive state to appropriately control BFD and BFR will be described.

[0107] (2.2) Operation According to the Second Embodiment FIG. 14 is a diagram for explaining the operation of the mobile communication system 1 according to the second embodiment.

[0108] As shown in STEP 1 of FIG. 14, the NCR device 500A is in an RRC connected state in the cell of the gNB 200. The gNB 200 transmits an RRC Reconfiguration message including an NCR setting to the NCR device 500A. The NCR device 500A receives the RRC Reconfiguration message including the NCR setting from the gNB 200 and performs relay operation using the NCR setting. The NCR setting may include a periodic beam indication. That is, the NCR setting includes information for setting relay operation with periodic beamforming, and the NCR-Fwd 510A is set to on. Such setting information is an example of first setting information related to relay operation. NCR-MT520A receives first setting information regarding relay operation from gNB200.

[0109] As shown in STEP 2 of Figure 14, gNB200 transmits an RRC Release message including a suspend setting to NCR device 500A. NCR device 500A receives the RRC Release message from gNB200 and transitions to an RRC inactive state.

[0110] In this embodiment, the RRC Reconfiguration message sent from gNB200 to NCR-MT520A in STEP 1, or the RRC Release message sent from gNB200 to NCR-MT520A in STEP 2, includes second setting information regarding whether NCR-MT520A will perform beam failure detection processing (BFD) with gNB200 in an RRC inactive state. In other words, NCR-MT520A receives second setting information from gNB200 regarding whether NCR-MT520A will perform beam failure detection processing with gNB200 in an RRC inactive state.

[0111] However, instead of providing the second configuration information to the NCR-MT 520A by such dedicated signaling, the gNB 200 may provide the second configuration information to the NCR-MT 520A by broadcast signaling. For example, the gNB 200 may transmit a system information block (SIB) including the second configuration information to the UE 100.

[0112] 14, after the NCR-MT 520A transitions to the RRC inactive state, the NCR-MT 520A controls the NCR-Fwd 510A in accordance with the latest NCR setting. In this embodiment, the NCR-MT 520A in the RRC inactive state controls the relay operation (NCR-Fwd 510A) based on the first setting information, and also controls the BFD (and BFR) based on the second setting information.

[0113] Thus, in this embodiment, NCR-MT520A receives second setting information from gNB200 regarding whether or not to perform beam interference detection processing with gNB200 in the RRC inactive state. NCR-MT520A in the RRC inactive state controls BFD (and BFR) based on the second setting information. This makes it possible to appropriately control BFD (and BFR) performed by NCR-MT520A in the RRC inactive state.

[0114] The basic operation of BFD performed by the NCR-MT 520A in the RRC inactive state may be an operation that applies general BFD. The MAC entity of the NCR-MT 520A may perform BFD in the RRC inactive state by continuing to use the BFD reference signal (RS), timer value, and maximum count value set by the gNB 200 during the RRC connected state. Specifically, the MAC entity of the NCR-MT 520A in the RRC inactive state declares (detects) beam failure when the number of beam failure instance indicators from the physical layer reaches a threshold (maximum count value) set by the gNB 200 before the timer set by the gNB 200 expires.

[0115] Alternatively, at least one of the reference signal (RS), timer value, and maximum count value for the RRC inactive state may be a parameter independent of the reference signal (RS), timer value, and maximum count value for the RRC connected state. The second configuration information may include information for setting at least one of the reference signal (RS), timer value, and maximum count value for the RRC inactive state. When the second configuration information includes such information, the NCR-MT 520A may be considered to be specified (configured) to perform BFD in the RRC inactive state.

[0116] In this embodiment, the second setting information may include information specifying whether or not the NCR-MT 520A performs the detection process (BFD) in the RRC inactive state. That is, the gNB 200 may set the NCR-MT 520A to perform BFD in the RRC inactive state.

[0117] In this embodiment, when the NCR-MT 520A is in the RRC inactive state, in response to the detection of a beam failure by the detection process (BFD), the NCR-MT 520A may initiate an RRC connection resume to transition to the RRC connected state. That is, when the NCR-MT 520A detects a beam failure in the RRC inactive state, the NCR-MT 520A may resume the RRC connection and transition to the RRC connected state. For example, when the NCR-MT 520A initiates the RRC connection resume, it selects an available beam before transmitting a random access preamble (Msg1) on the physical random access channel (PRACH) and transmits Msg1 using the PRACH resource associated with that beam (SSB index). The gNB200 determines the beam (SSB index) selected by the NCR-MT520A from the resources for which Msg1 was received, and transmits a random access response (Msg2) using the antenna weight corresponding to that beam. Msg2 includes a UL grant, and the NCR-MT520A transmits an RRC Resume Request message (Msg3) to the gNB200. Then, the NCR-MT520A receives an RRC Resume message (Msg4) from the gNB200 and transitions to the RRC connected state.

[0118] In this embodiment, the second setting information may include information specifying whether to continue relay operation when the NCR-MT 520A detects a beam failure in the RRC inactive state. For example, when the gNB 200 detects a beam failure in the RRC inactive state, the NCR-Fwd 510A may be set to the NCR-MT 520A as to whether to turn off the NCR-Fwd 510A or to continue to turn it on.

[0119] In this embodiment, when the NCR-MT 520A is in the RRC inactive state, the NCR-MT 520A may stop relaying operation in response to a beam failure detected by the detection process (BFD) and a failure to identify a candidate beam that satisfies a predetermined quality standard. For example, when the NCR-MT 520A detects a beam failure in the RRC inactive state and is unable to acquire a new beam that satisfies the quality standard (within a certain time period or within a certain number of recovery attempts), the NCR-MT 520A may turn off the NCR-Fwd 510A.

[0120] FIG. 15 is a flowchart showing an example of the operation of the NCR device 500A according to the second embodiment.

[0121] In step S21, the NCR-MT 520A receives an RRC Reconfiguration message including an NCR setting from the gNB 200. The NCR setting includes first setting information related to relay operation. The first setting information includes setting information indicating that the NCR-Fwd 510A is turned on. The first setting information may include a periodic beam indication. The NCR setting may further include second setting information related to whether the NCR-MT 520A performs beam failure detection processing (BFD) with the gNB 200 in an RRC inactive state. Hereinafter, the second setting information is also referred to as "BFD / BFR setting for the RRC inactive state."

[0122] In step S22, the NCR-MT 520A in the RRC connected state may perform relay operation using the NCR-Fwd 510A in the ON state based on the first setting information included in the NCR setting received in step S11.

[0123] In step S23, the NCR-MT 520A in the RRC connected state receives an RRC Release message including a suspend setting from the gNB 200. The NCR-MT 520A transitions to an RRC inactive state in response to the suspend setting. The RRC Release message may include a BFD / BFR setting (second setting information) for the RRC inactive state.

[0124] The BFD / BFR configuration for the RRC inactive state includes at least one of the following configuration information a) to c).

[0125] a) Setting whether to perform BFD in the RRC inactive state.

[0126] b) Setting of processing when beam failure is detected in RRC inactive state: For example, the setting may include information specifying whether or not to resume RRC connection when beam failure is detected in RRC inactive state.

[0127] b1) If RRC connection resume is not performed, the setting may include information specifying whether to turn off NCR-Fwd 510A while continuing the RRC inactive state, or to keep NCR-Fwd 510A on according to the latest setting.

[0128] b2) If RRC connection resume is not performed, the configuration may include information specifying whether or not to perform BFR.

[0129] b3) When BFR is performed, the setting may include parameters specifying the conditions for determining whether BFR has failed. The parameters may include a timer value for the determination and / or an upper limit for the number of attempts for the determination. In this case, the NCR-MT 520A in the RRC inactive state may determine that BFR has failed in response to the inability to discover (acquire) a candidate beam that satisfies a predetermined quality criterion within the timer value, or the unsuccessful random access procedure for a candidate beam that satisfies the predetermined quality criterion. The NCR-MT 520A in the RRC inactive state may determine that BFR has failed in response to the number of times that a candidate beam that does not satisfy the predetermined quality criterion has been discovered reaching the upper limit, or the number of times that a random access procedure for a candidate beam that satisfies the predetermined quality criterion has failed reaching the upper limit.

[0130] b4) When BFR is performed, the setting may include information specifying a process to be performed when BFR fails. For example, the information may include information specifying whether the NCR-MT 520A resumes the RRC connection. When RRC resume is not performed (when the RRC inactive state is maintained), the information may include information specifying whether the NCR-Fwd 510A is turned off or maintained in the on state.

[0131] In step S24, the NCR-MT 520A that has transitioned to the RRC inactive state performs relay operation using the NCR-Fwd 510A in the ON state based on the first setting information included in the NCR setting (latest setting). Also, the NCR-MT 520A in the RRC inactive state performs BFD based on the BFD / BFR setting (second setting information) for the RRC inactive state.

[0132] In step S25, the NCR-MT 520A in the RRC inactive state checks whether or not a beam failure has been detected by BFD. If no beam failure has been detected, the process returns to step S24.

[0133] If a beam failure is detected (step S25: YES), in step S26, NCR-MT520A in the RRC inactive state performs the operation specified in the BFD / BFR setting (second setting information) for the RRC inactive state (e.g., BFR and / or RRC connection resume).

[0134] (2.1) Modification of the Second Embodiment In the second embodiment, an example was described in which the gNB 200 explicitly sets the NCR-MT 520A as to whether or not to perform beam failure detection (BFD) and / or beam failure recovery (BFR). However, this is not limited to this. The NCR-MT 520A can determine whether or not to perform beam failure detection and / or beam failure recovery processing in the RRC inactive state based on the operating state of the NCR-Fwd 510A.

[0135] That is, when the NCR-MT 520A transitions to the RRC inactive state, if the NCR-Fwd 510A is in the on state (for example, performing periodic beamforming operation), the NCR-MT 520A performs beam failure detection and / or beam failure recovery processing in the RRC inactive state. Also, if the NCR-Fwd 510A is in the off control (not performing relay operation), the beam failure detection and / or beam failure recovery processing in the RRC inactive state is not performed. This allows the NCR-MT 520A to determine whether or not to perform beam failure detection and / or beam failure recovery processing in the RRC inactive state without explicit setting from the gNB 200.

[0136] (3) Third Embodiment Next, a third embodiment will be described, focusing on differences from the above-described embodiments. As shown in Fig. 16, the relay device according to the third embodiment is a reconfigurable intelligent surface (RIS) device 500B that changes the propagation direction of an incident radio wave (wireless signal) by reflection or refraction. The term "NCR" in the above-described embodiments can be read as "RIS."

[0137] RIS is a type of repeater (hereinafter also referred to as "RIS-Fwd") that can perform beamforming (directivity control) similar to NCR by changing the properties of a metamaterial. In the case of RIS, the range (distance) of the beam may also be changed by controlling the reflection direction and / or refraction direction of each unit element. For example, the RIS may be configured to control the reflection direction and / or refraction direction of each unit element and to focus (direct the beam) on a nearby UE or a distant UE.

[0138] The RIS device 500B has a new UE (hereinafter referred to as "RIS-MT") 520B, which is a control terminal for controlling the RIS-Fwd 510B. The RIS-MT 520B establishes a wireless connection with the gNB 200 and performs wireless communication with the gNB 200, thereby controlling the RIS-Fwd 510B in cooperation with the gNB 200. The RIS-Fwd 510B may be a reflective RIS. Such a RIS-Fwd 510B changes the propagation direction of incident radio waves by reflecting the radio waves. Here, the reflection angle of the radio waves is variably settable. The RIS-Fwd 510B reflects radio waves incident from the gNB 200 toward the UE 100. The RIS-Fwd 510B may be a transparent RIS. Such a RIS-Fwd 510B changes the propagation direction of the radio waves by refracting the incident radio waves. Here, the refraction angle of the radio wave can be variably set.

[0139] FIG. 17 is a diagram showing an example configuration of a RIS-Fwd (repeater) 510B and a RIS-MT (control terminal) 520B according to the second embodiment. The RIS-MT 520B includes a receiver 521, a transmitter 522, and a controller 523. This configuration is similar to that of the above-described embodiment. The RIS-Fwd 510B includes a RIS 511B and a RIS controller 512B. The RIS 511B is a metasurface constructed using a metamaterial. For example, the RIS 511B is constructed by arranging structures that are very small relative to the wavelength of radio waves in an array. By making the structures different shapes depending on their placement, it is possible to arbitrarily design the direction and / or beam shape of the reflected waves. The RIS 511B may also be a transparent dynamic metasurface. The RIS 511B may be configured by overlaying a transparent glass substrate on a transparent metasurface substrate on which a large number of small structures are regularly arranged, and by slightly moving the overlaid glass substrate, it may be possible to dynamically control three patterns: a mode that transmits incident radio waves, a mode that transmits some of the radio waves and reflects some of them, and a mode that reflects all of the radio waves. The RIS control unit 512B controls the RIS 511B in response to a RIS control signal from the control unit 523 of the RIS-MT 520B. The RIS control unit 512B may include at least one processor and at least one actuator. The processor decodes the RIS control signal from the control unit 523 of the RIS-MT 520B and drives the actuator in response to the RIS control signal.

[0140] (4) Other Embodiments In the above-described embodiment, an example has been described in which the relay device that performs relay transmission is the NCR device 500A or the RIS device 500B. However, the relay device that performs relay transmission is not limited to the NCR device 500A or the RIS device 500B, and may be an IAB (Integrated Access and Backhaul) node defined in the 3GPP technical specifications.

[0141] The above-described operational flows are not limited to being implemented independently, but can also be implemented by combining two or more operational flows. For example, some steps of one operational flow may be added to another operational flow, or some steps of one operational flow may be replaced with some steps of another operational flow. In each flow, it is not necessary to execute all steps, and only some steps may be executed.

[0142] In the above embodiment, an example in which the base station is an NR base station (gNB) has been described, but the base station may be an LTE base station (eNB). The base station may also be a relay node such as an IAB node. The base station may also be a DU (Distributed Unit) of the IAB node.

[0143] In the above-described embodiments and examples, an example in which the base station is an NR base station (gNB) has been described, but the base station may be an LTE base station (eNB) or a 6G base station. The base station may also be a relay node such as an IAB (Integrated Access and Backhaul) node. The base station may also be a DU of the IAB node. The UE 100 may also be an MT (Mobile Termination) of the IAB node.

[0144] That is, the UE 100 may be a terminal function unit (a type of communication module) for a base station to control a repeater that relays signals. Such a terminal function unit is referred to as an MT. Examples of the MT include, in addition to the IAB-MT, an NCR (Network Controlled Repeater)-MT and a RIS (Reconfigurable Intelligent Surface)-MT.

[0145] The term "network node" primarily refers to a base station, but may also refer to a core network device or a part of a base station (CU, DU, or RU). A network node may also be configured by a combination of at least a part of a core network device and at least a part of a base station.

[0146] A program may be provided that causes a computer to execute each process performed by the communication device according to the above-described embodiment, for example, the UE100 (NCR-MT520A, RIS-MT520B) or the gNB200. The program may be recorded on a computer-readable medium. Using a computer-readable medium, the program can be installed on a computer. Here, the computer-readable medium on which the program is recorded may be a non-transitory recording medium. The non-transitory recording medium is not particularly limited, and may be, for example, a recording medium such as a CD-ROM or a DVD-ROM. Furthermore, circuits that execute each process performed by the UE100 or the gNB200 may be integrated, and at least a portion of the UE100 or the gNB200 may be configured as a semiconductor integrated circuit (chip set, SoC: System on a chip).

[0147] A program may be provided that causes a computer to execute each process performed by the UE 100, the gNB 200, or the relay device. The program may be recorded on a computer-readable medium. Using a computer-readable medium, the program can be installed on a computer. Here, the computer-readable medium on which the program is recorded may be a non-transitory recording medium. The non-transitory recording medium is not particularly limited, and may be, for example, a recording medium such as a CD-ROM or a DVD-ROM. Furthermore, circuits that execute each process performed by the UE 100, the gNB 200, or the relay device may be integrated, and at least a portion of the UE 100, the gNB 200, or the relay device may be configured as a semiconductor integrated circuit (chip set, SoC: System on a chip).

[0148] The functions performed by the UE 100, the gNB 200 (network node), or the relay device may be implemented in circuitry or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), a CPU (a Central Processing Unit), conventional circuits, and / or combinations thereof, programmed to perform the described functions. A processor includes transistors and other circuits and is considered to be circuitry or processing circuitry. A processor may also be a programmed processor that executes a program stored in memory. In this specification, circuitry, unit, or means refers to hardware that is programmed to perform the described functions or hardware that executes them. The hardware may be any hardware disclosed herein or any hardware known to be programmed or capable of performing the described functions. If the hardware is a processor, the circuitry, means, or unit is a combination of hardware and software used to configure the hardware and / or processor.

[0149] As used in this disclosure, the terms "based on" and "depending on / in response to" do not mean "based only on" or "depending only on," unless expressly stated otherwise. The term "based on" means both "based only on" and "based at least in part on." Similarly, the term "depending on" means both "depending only on" and "depending at least in part on." The terms "include," "comprise," and variations thereof do not mean including only the listed items, but may mean including only the listed items or may include additional items in addition to the listed items. Additionally, the term "or," as used in this disclosure, is not intended to mean an exclusive or. Furthermore, any reference to elements using designations such as "first," "second," etc., as used in this disclosure does not 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, a 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 way. In this disclosure, where articles are added by translation, such as a, an, and the in English, these articles shall include the plural unless the context clearly indicates otherwise.

[0150] 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 can be made within the scope that does not deviate from the gist of the invention.

[0151] This application claims priority to U.S. Provisional Application No. 63 / 501,479 (filed May 11, 2023), the entire contents of which are incorporated herein by reference.

[0152] (5) Supplementary Note A The following supplementary note is provided regarding the features of the above-described embodiment.

[0153] (Supplementary Note 1) A communication method executed by a relay device having a relay device that performs a relay operation to relay a radio signal transmitted between a network node and a user equipment, and a control terminal that receives a control signal used to control the relay device from the network node, the communication method comprising: a step of receiving configuration information related to the relay operation from a first cell; a step of performing the relay operation using the configuration information when the control terminal is in a radio resource control (RRC) inactive state in the first cell; a step of stopping the relay operation when cell reselection from the first cell to a second cell is performed; and a step of resuming the relay operation using the configuration information when cell reselection to the first cell is performed within a predetermined time after cell reselection to the second cell.

[0154] (Supplementary Note 2) The communication method according to Supplementary Note 1, further comprising: a step of receiving a timer value that determines the predetermined time from the first cell; and a step of starting a timer to which the timer value is set in response to performing the cell reselection from the first cell to the second cell.

[0155] (Supplementary Note 3) The communication method according to Supplementary Note 2, further comprising the step of receiving an RRC release message from the first cell for transitioning the control terminal from an RRC connected state to the RRC inactive state, wherein the RRC release message includes the timer value.

[0156] (Supplementary Note 4) The communication method according to Supplementary Note 2 or 3, wherein the step of resuming the relay operation includes the step of resuming the relay operation using the configuration information when the cell reselection to the first cell is performed before the timer expires.

[0157] (Supplementary Note 5) The communication method according to any one of Supplementary Notes 1 to 4, wherein the setting information includes a setting for periodic beamforming in the relay operation, and wherein the step of resuming the relay operation includes a step of resuming the periodic beamforming using the setting information.

[0158] (Supplementary Note 6) A relay device comprising: a repeater that performs a relay operation to relay a radio signal transmitted between a network node and a user equipment; and a control terminal that receives a control signal used to control the repeater from the network node, wherein the control terminal includes: a receiving unit that receives configuration information related to the relay operation from a first cell; and a control unit that controls the repeater to perform the relay operation using the configuration information when the control terminal is in a radio resource control (RRC) inactive state in the first cell, wherein the control unit stops the relay operation when cell reselection from the first cell to a second cell is performed, and resumes the relay operation using the configuration information when cell reselection to the first cell is performed within a predetermined time after the cell reselection to the second cell.

[0159] (Supplementary Note 7) A communication method executed by a relay device having a relay device that performs a relay operation to relay radio signals transmitted between a network node and a user device, and a control terminal that receives a control signal used to control the relay device from the network node, the communication method comprising: a step of receiving first setting information regarding the relay operation from the network node; a step of receiving second setting information from the network node regarding whether the control terminal will perform a beam failure detection process with the network node in a radio resource control (RRC) inactive state; and a step of controlling the relay operation based on the first setting information and controlling the detection process based on the second setting information when the control terminal is in the RRC inactive state.

[0160] (Supplementary Note 8) The communication method according to Supplementary Note 7, wherein the second setting information includes information specifying whether or not the control terminal performs the detection process in the RRC inactive state.

[0161] (Supplementary Note 9) The communication method according to Supplementary Note 7 or 8, further comprising the step of initiating an RRC connection resume for the control terminal to transition to an RRC connected state in response to the beam failure being detected by the detection process when the control terminal is in the RRC inactive state.

[0162] (Supplementary Note 10) The communication method according to any one of Supplementary Notes 7 to 9, wherein the second setting information includes information specifying whether to continue the relay operation when the control terminal detects the beam failure in the RRC inactive state.

[0163] (Supplementary Note 11) The communication method described in any one of Supplementary Notes 7 to 10, further comprising a step of stopping the relay operation when the control terminal is in the RRC inactive state and the beam failure is detected by the detection process and a candidate beam that satisfies a predetermined quality standard is not identified.

[0164] (Supplementary Note 12) A relay device comprising: a relay that performs a relay operation to relay a radio signal transmitted between a network node and a user equipment; and a control terminal that receives a control signal used to control the relay from the network node, wherein the control terminal includes: a receiving unit that receives first setting information related to the relay operation from the network node and receives second setting information from the network node related to whether the control terminal will perform a beam fault detection process with the network node in a radio resource control (RRC) inactive state; and a control unit that controls the relay operation based on the first setting information and controls the detection process based on the second setting information when the control terminal is in the RRC inactive state.

[0165] (6) Appendix B 1. Introduction RAN#99 approved a three-month extension of the work item on Network Controlled Repeaters (NCRs) to resolve remaining issues for RAN2#119bis-e, RAN2#120, and RAN2#121.

[0166] This appendix discusses the open / potential issues for RAN2 that remain in the NCR.

[0167] 2. Discussion 2.1. Wake-up Timer As agreed in RAN2, "The network should be able to send the NCR-MT to RRC idle." Therefore, a gNB can intentionally put the NCR-MT into idle state due to policies such as NCR power saving and network congestion. However, since RAN paging is not available for an idle NCR-MT, a gNB has no way to transition the NCR-MT to connected, i.e., unreachable. Therefore, it is clear that once the NCR is released to idle state, it is no longer a network-controlled repeater and is considered similar to, for example, a legacy RF repeater.

[0168] Observation 1: Even if the gNB intentionally puts the NCR-MT in idle state due to policies such as NCR power saving or network congestion, the gNB cannot page the NCR-MT.

[0169] To solve this problem, RAN2#121bis-e discussed whether to rely on OAM implementation or introduce a wake-up timer, but the conclusion was postponed as follows:

[0170] Proposal 1: In Rel-18, the "wake-up timer" IE is not defined in the RRC Release message.

[0171] One view is, "We want to ensure network control in a simple way. NAS can trigger service requests and registration requests." Another view is, "Since NCR-WRD is off during RRC idle, the original intention is no longer valid. The only goal is to return to RRC connected. We believe there are multiple implementation-specific ways to achieve this. There is no time to send an LS to CT1." Another view is, "The main motivation against a timer is the impact on NAS, but that impact seems minor. If the impact on NAS is significant, we will agree on an OAM solution." Another view is, "The biggest issue is not the impact on NAS, but the motivation for having such a timer." Another view is, "The timer is handled by the AS, and when the timer expires, it notifies the NAS. Since OAM is static and cannot be used in this case, gNB control is preferable." Another view is, "In the same case, it may be handled by OAM. RAN3 agrees that OAM is supported." Another view is, "We need to consider whether interoperability is a key issue within the scope of NCR." Another view is, "Both solutions will work." Further consideration is needed on the above points.

[0172] Therefore, this issue should be discussed thoroughly, a conclusion should be reached, and the Rel-17 NCR WI should be completed.

[0173] 2.1.1 OAM-based solutions In other words, the OAM server generates DL OAM traffic (U-plane data) that triggers the AMF to initiate CN paging to the NCR-MT. However, it is assumed that there is no way for the gNB to send UL OAM traffic (U-plane data, e.g., indicating release to IDLE) when the NCR-MT receives an RRC release after the gNB releases the NCR-MT. Therefore, it is unclear how the OAM server knows that the NCR-MT is idle.

[0174] Observation 2: After the NCR-MT is released by the gNB, there is no way to send UL OAM traffic, so the OAM does not know whether the NCR-MT is idle.

[0175] In addition, it is somewhat unnatural for the gNB to intentionally release the NCR-MT for some purpose while the OAM server is forced to reconnect the NCR-MT. To solve these issues, some coordination between the gNB-OAM and the NCR-OAM is necessary. However, this would increase the operator's workload or eliminate multi-vendor interoperability.

[0176] Observation 3: DL OAM traffic can be an option to trigger the AMF to page an idle NCR-MT, but it requires coordination between the gNB-OAM and the NCR-OAM, leading to reduced efficiency in network operations and reduced interoperability.

[0177] Another implementation option is to use an OAM client on the NCR-MT. The OAM client can use the NCR-MT's release state as well as failure states (e.g., RLF, RRC resume failure) and initial access states (e.g., power on) to determine the NCR-MT's transition to an idle state. In the case of failure and initial access, the OAM client may generate UL OAM traffic (i.e., U-plane data) to connect to the OAM server. UL packets trigger the RRC connection establishment procedure, as is currently the case. That is, for an NCR-MT in an idle state, RRC connection establishment is an automatic process, so the NCR-MT initiates RRC connection establishment immediately after being released from the gNB.

[0178] Observation 4: The use of UL OAM traffic is another option to trigger the NCR-MT to initiate RRC connection establishment, but it may occur immediately after the gNB releases the NCR-MT to the idle state.

[0179] Given the above observations, OAM-based solutions can introduce other problems, so these implementations do not work properly on their own.

[0180] On the other hand, the advantages of an OAM-based solution are clear and do not affect the specification.

[0181] Observation 5: The advantage of an OAM-based solution is that it does not impact specifications.

[0182] 2.1.2 Timer-Based Solutions A wake-up timer was proposed as a trigger for the NCR-MT to return to an RRC connection and was discussed in RAN2#121 offline and online states, and RAN2#121bis-e offline and online states. The idea is that the NCR-MT starts a timer (if configured in the RRC release), and when the timer expires, the NCR-MT initiates the RRC connection establishment procedure. This simple solution solves the issue described in Observation 3 (especially when the OAM server does not implement automatic generation of DL traffic such as keep-alive messages) and allows the gNB to control the idle NCR-MT.

[0183] Keep-alive messages as an OAM-based solution require a large number of unnecessary messages, especially if the gNB rarely puts the NCR-MT in idle state, but this depends on the gNB implementation.

[0184] Observation 6: A wake-up timer can solve the issue identified in Observation 3, especially when the OAM server does not implement so-called keep-alive messages and the RRC connection control is entirely under the control of the gNB.

[0185] With RAN2#121bis-e, some companies were concerned about the extent to which it would affect NAS specifications. Generally, the following two approaches are considered:

[0186] AS-based approach When the wake-up timer expires, the AS can operate in the same way as if it had received a paging message, i.e., the AS indicates the UE-ID (i.e., UE-Identity) to the NAS. The NAS can also operate as if the access attempt is an MT access (i.e., Access Identity 0 and Access Category 0 of "MT_acc"), so the AS can set the establishment cause with the MT access according to the NAS access attempt. Since the expiration of the wake-up timer means that the network (i.e., gNB) will call back the NCR-MT to connected, this establishment cause (i.e., MT access) is considered to be in line with the current definition. This solution has no (or almost no) impact on the NAS specifications, but the AS specifications need to be slightly modified as to the behavior when the timer expires.

[0187] NAS-based approach - The AS notifies the NAS when the wake-up timer expires, and the NAS requests the establishment of a signaling connection. This is considered a new definition of an access attempt, and so besides the slight impact on the AS specification of the new behavior on timer expiry, it may require, for example, the addition of procedural descriptions (or annotations) to the NAS specification.

[0188] Another option would be for the AS to forward the wake-up timer value when set in the RRC release. The NAS would handle the timer and request the establishment of a signaling connection upon timer expiry. This solution would require the timer handling to be specified in the NAS specification in addition to the new definition of the access attempt described above. Therefore, in addition to the new behavior in the AS specification, this option has the most impact on the NAS specification.

[0189] Based on the above analysis, it can be concluded that the timer should be handled by the AS to minimize potential NAS impact. Furthermore, an AS-based approach is preferable because it minimizes (or even avoids) impact on other WGs. In this sense, it can be said that there is no longer any major concern about the impact on the NAS specification.

[0190] Observation 7: The wake-up timer has no (or very little) impact on the operation of the NAS as long as the timer is handled by the AS.

[0191] It should be noted that if the OAM-based solution discussed in the previous section is preferred, the gNB always chooses not to set a timer on RRC release, i.e., this option is not harmful and ensures efficient network operation and interoperability.

[0192] Proposal 1: RAN2 should agree to introduce a wake-up timer for gNBs to control idle NCR-MTs to establish RRC connections.

[0193] Proposal 2: RAN2 should discuss whether the AS should act as if it received a paging message, i.e., whether the AS should indicate its UE-ID to the NAS when the wake-up timer expires.

[0194] If Proposal 1 is acceptable, the timer value needs to be discussed. According to existing mechanisms related to access restriction / prohibition in idle state, 300 seconds (or 5 minutes) is, for example, a typical period for a UE to exclude a prohibited cell from candidates for cell reselection, and this can be the minimum value of this timer. The discussion in RAN2#121bis-e shows an example in which a gNB may not use NCR during periods of low traffic (e.g., at night) and may set NCR to idle. Therefore, a timer value upper limit of 12 hours is considered reasonable. If the timer value is 8 bits, the mapping would be, for example, "300 seconds (5 minutes), 10 minutes, 30 minutes, 60 minutes (1 hour), 3 hours, and 12 hours."

[0195] Proposal 3: RAN2 should discuss the range of values ​​for the wake-up timer (e.g., from 300 seconds to 12 hours).

[0196] Proposal 4: RAN2 should discuss how many bits the wake-up timer setting should be (e.g., the baseline is 8 bits).

[0197] Another possibility is a prohibition timer, which causes the NCR-MT to start a timer (if configured in the RRC release) and prohibits the NCR-MT from initiating the RRC connection establishment procedure while the timer is running. This solution solves the problem in Observation 3 (especially when the OAM server implements frequent automatic generation of DL traffic such as keep-alive messages) and Observation 4, and allows the gNB to control even idle NCR-MTs.

[0198] Observation 8: The prohibition timer, like Observation 4, can solve the problem identified in Observation 3 (especially when keep-alive messages occur frequently), and the RRC connection control of the NCR-MT is entirely under the control of the gNB.

[0199] In other words, an idle NCR-MT can also be network controlled, which is considered more efficient as it does not require two separate timers for the wake-up timer and the inhibit timer.

[0200] Observation 9: The wake-up timer and inhibit timer combined into one timer is efficient and feasible.

[0201] Proposal 5: If Proposal 1 is acceptable, RAN2 should further discuss whether to prohibit the NCR-MT from initiating RRC connection establishment while the wake-up timer is running, i.e., whether the wake-up timer also functions as a prohibition timer (one timer).

[0202] While it is clear that RRC connection establishment via UL traffic (e.g., UL OAM client packets) will be prohibited if Proposal 5 is accepted, it is worth considering whether the same is true for DL ​​traffic (e.g., DL OAM server packets). If RRC connection establishment via DL traffic is prohibited, the NCR will be unreachable from the network / OAM client while the timer is running. Therefore, the prohibition timer should only apply to RRC connection establishment via UL traffic. For example, this may be the case if the gNB wants to prevent the NCR-MT from returning to connected via DL traffic (e.g., via OAM server keep-alive messages). Therefore, whether this restriction should be configurable by the gNB is a separate issue.

[0203] Proposal 6: If proposal 5 can be agreed upon, RAN2 should further discuss whether the prohibition timer can be applied only to UL traffic (e.g., OAM client), i.e., whether RRC connection establishment is allowed for DL ​​traffic (e.g., OAM server, paging reception) when the timer is running.

[0204] Proposal 7: If Proposal 6 is agreed upon, RAN2 should further discuss whether restrictions can be set by the gNB, i.e., whether the prohibition timer applies only to UL traffic or to both DL and UL traffic.

[0205] 2.2. Beam Monitoring Inactivity in RRC As a background, RAN2#120 has agreed to the on or off operation of NCR-Fwd when NCR-MT is connected and inactive.

[0206] NCR-FW On / Off - When the NCR-MT is in RRC connected mode, the NCR-Fwd can be turned on or off according to the side control information received from the gNB. - After the NCR-MT enters RRC inactive mode, the NCR-Fwd can be turned on or off according to the last setting received from the gNB. - Releasing to RRC idle requires further study.

[0207] Finally, RAN2#121bis-e agreed to use the idle NCR-MT.

[0208] When NCR-MT is in RRC idle state, NCR-Fwd is off.

[0209] According to the above agreement, the basic principles of NCR are considered to be as follows: - The NCR-Fwd is under the control of the gNB when the NCR-MT is connected or inactive. - The NCR-Fwd is considered to be out of the control of the gNB when the NCR-MT is idle.

[0210] Observation 10: NCR-Fwd is under the control of gNB when NCR-MT is inactive.

[0211] As another background, RAN2#121 has agreed that NCR-MT will resume the RRC connection immediately after cell reselection to a different cell and provide a new side control configuration.

[0212] - If an NCR-MT in RRC inactive state reselects a cell different from the last serving cell from which it received side control configuration, NCR-FWD will be turned off. - After cell reselection, the NCR-MT will resume receiving side control configuration from the new gNB (possible by network configuration using existing specifications). Further consideration is needed for the cases where the NCR-MT moves to an acceptable cell and then returns, and when no cell is found.

[0213] Observation 11: If the NCR-MT reselects a different cell, the NCR-Fwd is already turned off and the NCR-MT must restart the RRC connection to the new cell to provide the side control configuration.

[0214] In addition to these, RAN2#121bis-e is discussing whether beam monitoring of backhaul links is required when NCR-MT is inactive.

[0215] Proposal 4: If necessary, the implementation can perform beam monitoring of the backhaul link when the NCR-MT is in the RRC inactive state.

[0216] Some people say, "I'm not opposed, but I'm unsure what "enforcement" means." Others say, "What happens if the NCR-FWD selects a new beam during RRC inactivity?" Some think, "It's up to the network whether to send the UE to RRC inactivity, and the network needs to be aware of the situation (e.g., whether the beam can be changed) and, in that case, can keep the UE RRC connected." Some people say, "Can we agree that the NCR-FWD is off in this case?" Some people say, "We want to prevent the beam from being changed without the network's knowledge during inactivity." The above points can be further discussed.

[0217] An important point in the above discussion was what happens when a beam failure is detected by an inactive NCR-MT. According to the previous discussion, the possible actions are as follows:

[0218] Alt. 1: Turn off NCR-Fwd if beam failure is detected or if beam failure recovery fails. Alt. 2: If beam failure is detected, NCR-MT resumes RRC connection.

[0219] Considering the principle of Remark 10, Alt. 1 is unacceptable because it means that the NCR-Fwd can be automatically turned off even if the NCR-MT is still camped on the cell that provided the last side control configuration. Alternatively, Alt. 1 could mean that the NCR itself can control the on / off of the NCR-Fwd even if the NCR-MT is connected, which is not only inappropriate but also violates the RAN2 agreement mentioned above.

[0220] On the other hand, Alt. 2 can be considered a variant of NCR behavior during cell reselection in Finding 11. That is, Alt. 2 requires the NCR-MT to acquire a new side control configuration upon beam failure. Therefore, Alt. 2 is considered a viable solution, although there may be cases where the NCR-Fwd needs to be turned off upon beam failure detection, as in Alt. 1. On the other hand, offline discussions have pointed out that the gNB monitors the end-to-end radio link with the UE, and therefore, depending on the implementation, it can detect such failures. This is rather consistent with the principle identified in Finding 10, namely, that the NCR is under the control of the gNB when the NCR-MT is inactive.

[0221] In summary, Alt. 2 is a visible solution, but at the same time, it is not a necessary one. Considering the time remaining to solve other necessary issues, beam monitoring in inactive mode does not need to be supported, at least not in Rel-18.

[0222] Proposal 8: RAN2 should agree that beam monitoring in inactive mode will not be supported in this release.

[0223] 2.3 Frequency Prioritization in Cell Reselection By way of background, RAN2#120 agreed to the following statement: NCR-MT supports cell reselection and RRM measurements in RRC idle and RRC inactive states.

[0224] In Rel-18, NCR-MT does not support handover and RRM measurements in RRC Connected.

[0225] An issue in cell reselection is the priority handling of specific cells. In the case of legacy RF repeaters, their placement is determined by network planning and / or field RF measurements. Therefore, it is assumed that desired cell(s) are planned for each NCR. That is, network planning determines the relationship between serving cells and NCRs. Such desired cells may be configured as NCRs by OAM.

[0226] Observation 12: The NCR can set a desired cell, for example, by OAM, where the desired cell means the cell that the NCR-MT intends to camp on and / or connect to.

[0227] In fact, RAN3 supports BL CR of the Stage-2 specification, and the allowed cell list and the forbidden cell list can be set by the OAM server in the NCR (that is, the OAM client).

[0228] X.Y OAM Aspects The transport connection between the NCR node and its OAM is provided by the NCR-MT PDU session. The NCR may be configured with a list of gNB cells to which the NCR-MT is allowed to connect and / or a list of gNB cells to which the NCR-MT is prohibited from connecting.

[0229] Since the NCR-MT is a type of UE, it is self-evident that it must follow the idle / inactive mode operation specified in TS38.304. In the email discussions of RAN2#121bis-e, some companies believed that the Stage-2 specification allows NCR implementations to override the TS38.304-specific operation. However, this is inconsistent with the 3GPP specification suite and common sense implementation practices. Therefore, standard support is necessary to ensure NCR network planning.

[0230] Furthermore, RAN3 states that the NCR is allowed to connect to allowed cells, i.e., it does not guarantee camping on allowed cells. Similarly, the Stage-2 specification states that the NCR is not allowed to connect to prohibited cells, i.e., it does not assume anything to avoid camping on prohibited cells. In such cases, it is necessary to consider what happens if the UE cannot camp on an allowed cell (due to frequency priority and / or radio conditions) even if the allowed cell meets the S criterion, and what happens if the UE camps on a prohibited cell (because the RAN3 specification does not mention camping, it simply mentions not connecting to a cell).

[0231] Observation 13: The specification of allowed cell lists and forbidden cell lists in Stage-2 of RAN3 does not mean that the implementation of NCR-MT is allowed to override the cell reselection procedure strictly specified in TS38.304.

[0232] The simplest approach is to enhance the prioritization of cell reselection. Similar to MBS and sidelink frequencies (which are prioritized according to UE preferences), exceptions to the NCR-MT's prioritization can be defined, allowing allowed cells to be considered the highest priority and forbidden cells the lowest priority. This enhancement allows the NCR-MT to always measure and attempt to reselect allowed cells and to avoid reselecting forbidden cells. Therefore, it is necessary to define these exceptions at least at the frequency level when the NCR-MT requires such prioritization, i.e., when the cell list is configured by the OAM.

[0233] The simplest approach is to enhance the prioritization of cell reselection. Similar to MBS and sidelink frequencies (which are prioritized according to UE preferences), exceptions to the NCR-MT's prioritization can be defined, allowing allowed cells to be considered the highest priority and forbidden cells the lowest priority. This enhancement allows the NCR-MT to always measure and attempt to reselect allowed cells and to avoid reselecting forbidden cells. Therefore, it is necessary to define these exceptions at least at the frequency level when the NCR-MT requires such prioritization, i.e., when the cell list is configured by the OAM.

[0234] Proposal 9: RAN2 should agree that the NCR-MT will consider certain frequencies as highest or lowest priority based on the NCR-MT's expected functionality (e.g., when the allowed cell list and / or forbidden cell list are configured by the OAM).

[0235] Considering that the NCR-MT is deployed at the cell edge (i.e., extending the coverage of the macrocell), the ranking may cause the NCR-MT to reselect an undesirable cell on the same frequency.

[0236] Proposal 10: RAN2 should discuss whether NCR-MT is allowed to prioritize a specific cell (cell of interest) in the intra-frequency cell reselection procedure.

[0237] 2.4 RRC Release with Redirection RAN2#121bis-e has agreed to support redirection for UEs as it is. RAN2 will ensure that RRC Release with Redirection is applicable to NCR-MT and that NCR-Fwd is off when NCR-MT selects a new cell by redirection (no impact on the specification).

[0238] As specified by RAN3, the NCR is configured with an allowed cell list and / or a forbidden cell list, so the NCR-MT can identify the frequencies of the allowed / forbidden cells using, for example, the inter-frequency cell reselection information provided by SIB4. Since the cell selection is performed at the time of redirection configuration, it is up to the NCR-MT implementation which cell of the identified frequency the NCR-MT selects.

[0239] On the other hand, since the gNB may not be aware of the frequencies of interest of the NCR-MT or the allowed / forbidden cell list set in the NCR by the NCR's OAM, the issue remains as to how the gNB can identify a specific frequency for redirection, i.e., how to set the redirectedCarrierInfo IE.

[0240] Observation 14: It is not clear how the gNB sets redirectedCarrierInfo upon RRC release, since the gNB may not know the allowed / forbidden cell list configured in the NCR by the OAM and the corresponding frequencies on which these cells operate.

[0241] That is, the operator enters all allowed / prohibited lists set by the NCR OAM into each NCR within the coverage of the gNB. This solution does not affect the specifications, but it places a heavy burden on the operator every time an NCR is deployed in the network.

[0242] Another solution is to allow the NCR-MT to notify the gNB of the allowed / forbidden cell list via UE Assistance Information, UE Capability, etc. This automatic configuration will reduce the operator's workload regarding this configuration, and was approved by the RAN Plenary.

[0243] Therefore, RAN2 should at least discuss how to address this issue in the Rel-18 NCR.

[0244] Proposal 11: RAN2 should discuss whether the gNB will identify the specific frequency to be set in the redirectedCarrierInfo IE within the RRC release based on the OAM implementation or a new UE report.

[0245] 1: Mobile communication system 100: UE 200: gNB 210: Transmitter 220: Receiver 230: Controller 240: Backhaul communication unit 300A: AMF 400: OAM server 500A: NCR device 510A: NCR-Fwd 520A: NCR-MT 500B: RIS device 510B: RIS-Fwd 520B: RIS-MT 511A: Wireless unit 511a: Antenna unit 511b: RF circuit 511c: Directivity control unit 512A: NCR control unit 512B: RIS control unit 521: Receiver 522: Transmitter 523: Controller 530: Interface

Claims

1. A communication method executed by a relay device having a relay operation for relaying radio signals transmitted between a network node and a user equipment, and a control terminal for receiving a control signal used to control the relay device from the network node, the communication method comprising: receiving configuration information related to the relay operation from a first cell; performing the relay operation using the configuration information when the control terminal is in a radio resource control (RRC) inactive state in the first cell; stopping the relay operation when cell reselection from the first cell to a second cell is performed; and resuming the relay operation using the configuration information when cell reselection to the first cell is performed within a predetermined time after cell reselection to the second cell.

2. The communication method according to claim 1, further comprising: receiving a timer value from the first cell that defines the predetermined time; and starting a timer to which the timer value is set in response to performing cell reselection from the first cell to the second cell.

3. The communication method according to claim 2, further comprising receiving an RRC release message from the first cell for transitioning the control terminal from an RRC connected state to the RRC inactive state, the RRC release message including the timer value.

4. The communication method according to claim 2 or 3, wherein resuming the relay operation includes resuming the relay operation using the configuration information when the cell reselection to the first cell is performed before the timer expires.

5. A communication method as described in claim 1 or 2, wherein the setting information includes a setting for periodic beamforming in the relay operation, and resuming the relay operation includes resuming the periodic beamforming using the setting information.

6. A relay device comprising: a relay device that performs a relay operation to relay a radio signal transmitted between a network node and a user equipment; and a control terminal that receives a control signal used to control the relay device from the network node, wherein the control terminal includes: a receiving unit that receives configuration information related to the relay operation from a first cell; and a control unit that controls the relay device to perform the relay operation using the configuration information when the control terminal is in a radio resource control (RRC) inactive state in the first cell, wherein the control unit stops the relay operation when cell reselection from the first cell to a second cell is performed, and resumes the relay operation using the configuration information when cell reselection to the first cell is performed within a predetermined time after cell reselection to the second cell.

7. A communication method executed by a relay device having a relay operation for relaying radio signals transmitted between a network node and a user equipment, and a control terminal for receiving a control signal from the network node for use in controlling the relay device, the communication method comprising: receiving first setting information regarding the relay operation from the network node; receiving second setting information from the network node regarding whether or not the control terminal will perform a beam interference detection process with the network node in a radio resource control (RRC) inactive state; and when the control terminal is in the RRC inactive state, controlling the relay operation based on the first setting information and controlling the detection process based on the second setting information.

8. The communication method according to claim 7, wherein the second setting information includes information for specifying whether or not the control terminal performs the detection process in the RRC inactive state.

9. The communication method according to claim 7, further comprising initiating an RRC connection resume for the control terminal to transition to an RRC connected state in response to detection of the beam failure by the detection process when the control terminal is in the RRC inactive state.

10. The communication method according to claim 7, wherein the second setting information includes information specifying whether or not to continue the relay operation when the control terminal detects the beam failure in the RRC inactive state.

11. The communication method described in claim 7, further comprising stopping the relay operation when the control terminal is in the RRC inactive state, the detection process detects a beam failure, and a candidate beam that satisfies a predetermined quality standard is not identified.

12. A relay device comprising: a relay that performs relaying operation to relay radio signals transmitted between a network node and a user equipment; and a control terminal that receives a control signal from the network node used to control the relay, wherein the control terminal includes: a receiving unit that receives first setting information regarding the relaying operation from the network node and receives second setting information from the network node regarding whether the control terminal will perform a beam interference detection process with the network node when the control terminal is in a radio resource control (RRC) inactive state; and a control unit that controls the relaying operation based on the first setting information and controls the detection process based on the second setting information when the control terminal is in the RRC inactive state.

Citation Information

Patent Citations

  • Communication control method and radio relay device

    WO2021090686A1

  • US202363501479P