Terminal and wirelss communication method

By differentiating mobile WAB-cells through enhanced system information blocks and reporting wireless backhaul failures, the system addresses issues of cell selection and failure reporting, enhancing connectivity and reducing handover failures in mobile scenarios.

WO2025243835A1PCT designated stage Publication Date: 2025-11-27NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2025/016723
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-05-21
Filing Date
2025-05-07
Publication Date
2025-11-27

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in distinguishing between mobile WAB-cells and normal cells, leading to unnecessary handovers and radio link failures, particularly in scenarios involving vehicles equipped with wireless communication nodes, and lack appropriate mechanisms for reporting wireless backhaul failures.

Method used

Incorporating specific system information blocks and indications in SIBs to differentiate between mobile WAB-cells and normal cells, and implementing fault processing units to transmit detailed failure information to the network, including WAB-specific RLF and recovery failure types, enabling accurate cell selection and failure reporting.

Benefits of technology

Enhances the ability of terminals and wireless communication nodes to perform appropriate settings and reliably report wireless backhaul failures, reducing unnecessary handovers and improving connectivity in mobile environments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2025016723_27112025_PF_FP_ABST
    Figure JP2025016723_27112025_PF_FP_ABST
Patent Text Reader

Abstract

Provided are a terminal and a wireless communication method that are capable of executing suitable configuration regarding WAB, in consideration of WAB architecture and the like. The terminal executes wireless communication with a wireless communication node connected to a network via a wireless backhaul. The terminal receives system information representing types of nearby cells including a cell formed by the wireless communication node, and selects a cell on the basis of the system information.
Need to check novelty before this filing date? Find Prior Art

Description

Terminal and wireless communication method

[0001] The present disclosure relates to a terminal and a wireless communication method that supports Wireless Access Backhaul (WAB).

[0002] The 3rd Generation Partnership Project (3GPP: registered trademark) is developing specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] For example, 3GPP Release-19 is studying Wireless Access Backhaul (WAB) (see Non-Patent Document 1). Specifically, the architecture and protocol stack of WAB are being studied. It has been agreed that WAB-gNB, which is equivalent to a radio base station (gNB) that can provide WAB functionality, will not provide Mobile Termination (MT), a function for connecting to a higher-level node on the network side (see Non-Patent Document 2).

[0004] In addition, 3GPP Release-18 defines Integrated Access and Backhaul (IAB), a mechanism similar to WAB. For example, it defines that a terminal (User Equipment, UE) located in a vehicle such as a train or automobile is to preferentially connect to a mobile IAB-Cell formed by wireless communication nodes in the vehicle (Non-Patent Document 3). The UE can recognize the mobile IAB-Cell by information elements (IEs) included in specific system information blocks (e.g., SIB1, SIB4).

[0005] 3GPP TR 38.799 V0.0.1 (R3-243171), 3rd Generation Partnership Project; Technical Specification Group RAN; NR; Study on additional topological enhancements for NR (Release 19), 3GPP, March 2024 “(draft) Report of 3GPP TSG RAN3 meeting #123-bis”, 3GPP TSG RAN3 meeting #124, 3GPP, March 2024 3GPP TS 38.304 V18.1.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; User Equipment (UE) procedures in Idle mode and RRC Inactive state (Release 18), 3GPP, March 2024

[0006] As mentioned above, WAB has some similarities with IAB, but there are also many differences, such as the fact that WAB-gNB does not provide MT and that the WAB architecture differs from IAB in some respects. On the other hand, even in WAB, it is considered preferable for a UE located in a vehicle to preferentially connect to a mobile WAB-Cell formed by a wireless communication node in the vehicle.

[0007] Therefore, the following disclosure has been made in light of the above circumstances, and aims to provide a terminal and a wireless communication method that can perform appropriate settings related to WAB while taking into consideration the WAB architecture, etc.

[0008] One aspect of the present disclosure is a terminal comprising a communication unit (wireless communication unit 210) that performs wireless communication with a wireless communication node connected to a network via a wireless backhaul, a receiving unit (system information acquisition unit 230) that receives system information indicating the types of neighboring cells including a cell formed by the wireless communication node, and a control unit (control unit 240) that selects the cell based on the system information.

[0009] One aspect of the present disclosure is a wireless communication node (WAB node 150) that connects to a network via a wireless backhaul and includes a communication unit (wireless communication unit 110) that performs wireless communication with a terminal, and a transmission unit (fault processing unit 130) that transmits fault information indicating a wireless link fault in the wireless backhaul to the network.

[0010] One aspect of the present disclosure is a wireless communication node that includes a communication unit that connects to a network via a wireless backhaul and performs wireless communication with a terminal, and a transmission unit that, in dual connectivity that connects to multiple cells simultaneously, when a failure occurs in a secondary cell group, transmits failure information to the network indicating that the failure is related to the wireless backhaul.

[0011] One aspect of the present disclosure is a radio base station (gNB100) that includes a communication unit (radio communication unit 110) that connects to a network via a radio backhaul and performs dual connectivity with a radio communication node that performs radio communication with a terminal, and a transmission unit (fault processing unit 130) that, when a fault occurs in a secondary cell group, transmits fault information indicating that the fault is related to the radio backhaul to other radio base stations that constitute the secondary node.

[0012] One aspect of the present disclosure is a wireless communication node comprising: a communication unit that connects to a network via a wireless backhaul and performs wireless communication with a terminal; and a transmission unit that, in dual connectivity that connects to multiple cells simultaneously, when a failure occurs in a master cell group, transmits fault information to the network indicating that the fault is related to the wireless backhaul.

[0013] One aspect of the present disclosure is a wireless communication node that connects to a network via a wireless backhaul and includes a communication unit that performs wireless communication with a terminal, and a transmission unit that transmits capability information to the network indicating whether the node supports at least one of detection and recovery of a wireless link failure of the wireless backhaul.

[0014] FIG. 1 is a schematic diagram of the overall configuration of a wireless communication system 10. FIG. 2 is a diagram showing the basic architecture of a network conforming to WAB. FIG. 3 is a diagram showing an example configuration of a WAB architecture when NG traffic of a WAB-gNB is transmitted via a PDU session backhaul. FIG. 4 is a functional block diagram of a WAB node 150. FIG. 5 is a functional block diagram of a UE 200. FIG. 6 is a diagram showing an example configuration of a WAB cell and a neighboring cell according to Operation Example 1. FIG. 7 is a diagram showing an example configuration of an SIB1 including a mobile WAB-Cell. FIG. 8 is a diagram showing an example configuration of an SIB1 including a WAB Cell. FIG. 9 is a diagram showing an example configuration of an SIB1 including a CellBarredWAB (barred). FIG. 10 is a diagram showing an example configuration of an SIB1 including a CellBarredWAB (barred, notBarred). FIG. 11 is a diagram showing an example configuration of an SIB1 including a WAB-support. FIG. 12 is a diagram showing an example configuration of an SIB1 including a CellBarredWAB (barred, notBarred). FIG. 13 is a diagram showing an example of the configuration of NPN-IdentityInfo-r16 including WAB-support. FIG. 14 is a diagram showing an example of a network configuration including a WAB node according to Operation Example 4. FIG. 15 is a diagram showing an example of a network configuration including a WAB node according to Operation Example 5. FIG. 16 is a diagram showing an example of the exchange of setting information between a master node and a secondary node according to Operation Example 6. FIG. 17 is a diagram showing an example of a network configuration including a WAB node according to Operation Example 7. FIG. 18 is a diagram showing an example of the hardware configuration of the gNB 100, the WAB node 150, and the UE 200. FIG. 19 is a diagram showing an example of the configuration of a vehicle 2001.

[0015] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.

[0016] (1) Overall Schematic Configuration of Wireless Communication System Fig. 1 is a diagram showing the overall schematic configuration of a wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (User Equipment 200, hereinafter, UE 200).

[0017] The wireless communication system 10 may be a wireless communication system conforming to a method called Beyond 5G, 5G Evolution, or 6G, or may include a wireless communication system conforming to a method called Long Term Evolution (LTE) or 4G. The wireless communication system 10 may support functions related to the Industrial Internet of Things (IIoT) and Ultra-Reliable and Low Latency Communications (URLLC).

[0018] The NG-RAN 20 includes a radio base station 100 (hereinafter, gNB 100) and a WAB node 150. Note that the specific configuration of the radio communication system 10, including the number of gNBs (or eNBs), WAB nodes, and UEs, is not limited to the example shown in FIG. 1 .

[0019] The gNB 100 may also employ a fronthaul (FH) interface defined by the Open Radio Access Network Alliance (O-RAN). The gNB 100 may include an O-RAN Distributed Unit (O-DU) and an O-RAN Radio Unit (O-RU). The gNB 100 can function as a type of NG-RAN node.

[0020] The WAB node 150 is a type of wireless communication node that complies with the Wireless Access Backhaul (WAB) standard.

[0021] The NG-RAN 20 actually includes multiple NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G core network (5GC, not shown). The 5GC may include logical nodes that provide network functions (NFs). The NFs may include an Access and Mobility Management Function that provides access and mobility management functions for the UE 200, a Session Management Function (SMF) that provides session management functions, and a Location Management Function (LMF) that controls communications related to location-based services defined in the 5GC. Furthermore, a Unified Data Management / User Data Repository (UDM / UDR) may be connected to the AMF and / or SMF.

[0022] NG-RAN20 and 5GC may simply be referred to as "networks." 5GC may introduce the concept of CUPS (Control and User Plane Separation), which clearly separates the functions of the user plane and the control plane.

[0023] The gNB100 is a radio base station conforming to NR, and performs radio communication conforming to NR with the UE200. The gNB100 may be configured to include a CU (Central Unit) and a DU (Distributed Unit), and the DU may be separated from the CU and installed in a different geographical location. One or more DUs may be connected to the CU. The gNB100 (gNB-CU) may be connected to each other via an Xn interface, and the CU and DU may be connected to each other via an F1 interface (such as an F1-AP). In this embodiment, the CU may be called a communication device or a central device. The DU may be called a distributed device.

[0024] Figure 2 shows the basic architecture of a network based on WAB. Figure 3 shows an example of the WAB architecture when NG traffic of a WAB-gNB is transmitted via a PDU session backhaul.

[0025] 2 and 3 , the WAB node 150 may be configured with a WAB-gNB that provides an interface with the UE 200 and a WAB-MT that provides an interface with an upper node on the network side (e.g., the gNB 100). The UE 200 and the AMF may be connected via an NG-C interface. The UE 200 and the WAB node 150 may be connected via an NR-Uu interface.

[0026] The gNB100 and UPF may function as serving nodes for the WAB-MT. The AMF may function as a serving node for the UE200. The gNB100 and WAB node 150 may be connected via an NR-Uu interface, and the gNB100 and UPF may be connected via an NG-U interface. The WAB-MT may be interpreted as a function equivalent to a UE. Furthermore, the gNB serving WAB-MT may be interpreted as a BH gNB or donor gNB, and the 5GC serving WAB-MT may be interpreted as a BH 5GC.

[0027] The gNB100 and UE200 are capable of supporting Massive MIMO, which generates more directional beams by controlling radio signals transmitted from multiple antenna elements; Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CCs); and Dual Connectivity (DC), which enables simultaneous communication between the UE and multiple NG-RAN nodes.

[0028] The type of DC may be Multi-RAT Dual Connectivity (MR-DC) that uses multiple radio access technologies, or NR-NR Dual Connectivity (NR-DC) that uses only NR. For example, one gNB may constitute a master node (MN), and one or more other gNBs may constitute secondary nodes (SNs).

[0029] In addition, the secondary node may be read as a secondary cell or a secondary cell group (SCG).

[0030] In this embodiment, the channels include a control channel and a data channel, such as a physical downlink control channel (PDCCH), a physical uplink control channel (PUCCH), a physical random access channel (PRACH), and a physical broadcast channel (PBCH).

[0031] The data channels include a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH).

[0032] The reference signal includes a Demodulation Reference Signal (DMRS), a Sounding Reference Signal (SRS), a Phase Tracking Reference Signal (PTRS), and a Channel State Information-Reference Signal (CSI-RS), and the signal includes a channel and a reference signal. Furthermore, the data may refer to data transmitted via a data channel.

[0033] (2) Functional Block Configuration of Wireless Communication System Next, the functional block configuration of wireless communication system 10 will be described. Specifically, the functional block configuration of WAB node 150 and UE 200 will be described. Fig. 4 is a functional block configuration diagram of WAB node 150. Fig. 5 is a functional block configuration diagram of UE 200.

[0034] (2.1) WAB Node 150 As shown in FIG. 4, the WAB node 150 includes a wireless communication unit 110, a backhaul connection unit 120, a fault processing unit 130, and a control unit 140.

[0035] The radio communication unit 110 transmits a downlink signal (DL signal) conforming to NR to the UE 200, and receives an uplink signal (UL signal) conforming to NR from the UE 200. The radio communication unit 110 also transmits a UL signal conforming to NR to the gNB 100, and receives a DL signal from the gNB 100.

[0036] The wireless communication unit 110 supports WAB and can perform wireless communication using wireless access (UE side) and wireless backhaul (gNB side). In this embodiment, the wireless communication unit 110 may be configured as a communication unit that connects to a network via a wireless backhaul and performs wireless communication with a terminal.

[0037] The backhaul connection unit 120 provides a connection interface with a wireless backhaul. Specifically, the backhaul connection unit 120 can provide a wireless interface (e.g., NR-Uu) with the gNB 100. The backhaul connection unit 120 can also provide a backhaul connection for a PDU session with the 5GC.

[0038] The fault processing unit 130 executes processing related to a fault in a wireless link. Specifically, the fault processing unit 130 can execute processing for a fault in a wireless link (wireless access) with the UE 200 and a wireless link (wireless backhaul) with the gNB 100.

[0039] More specifically, the fault processing unit 130 may constitute a transmitting unit that transmits fault information indicating a radio link failure (RLF) in the wireless backhaul to the network. The fault information may be interpreted as an RLF report. Note that the RLF does not necessarily have to be at the radio link level, but may be at the beam level or cell level.

[0040] The fault processing unit 130 may be configured as a transmitter that transmits fault information indicating that the fault is related to the wireless backhaul to the network when a fault occurs in a secondary cell group (SCG) in dual connectivity that simultaneously connects to multiple cells. Specifically, when an SCG failure occurs and the fault processing unit 130 reports SCGFailureInfo to a master node (Master gNB), the fault processing unit 130 may include WAB-BH-RLF or WAB-BH-RLFRecoveryFailure (which may be a tentative name) in failureType as the reason in SCGFailureInfo.

[0041] Furthermore, the fault processing unit 130 may be configured as a transmitter that transmits fault information indicating that the fault is related to the wireless backhaul to the network when a fault occurs in the master cell group in dual connectivity that simultaneously connects to multiple cells. Specifically, when an MCG failure occurs and the fault processing unit 130 reports MCGFailureInfo to the network, the fault processing unit 130 may include WAB-BH-RLF or WAB-BH-RLFRecoveryFailure (which may be a tentative name) in failureType as the reason in MCGFailureInfo.

[0042] The fault processing unit 130 may transmit capability information related to the above-described fault information to the network. Specifically, the fault processing unit 130 may be configured as a transmitter that transmits capability information indicating whether or not at least one of detection and recovery of a radio link failure (RLF) in the wireless backhaul is supported to the network.

[0043] More specifically, if the failure processing unit 130 supports WAB-BH-RLF-detection or WAB-BH-RLF-Detection-recovery, the failure processing unit 130 may include a WAB-BH-RLF-indication or a WAB-BH-RLF-Detection-recovery indication in the UE-NR-Capability IE and report it to the network.

[0044] The control unit 140 controls each functional block that configures the gNB 100. In particular, in this embodiment, the control unit 140 can execute control related to failures in the wireless backhaul.

[0045] Specifically, the control unit 140 can control the generation and transmission of an RLF report related to the wireless backhaul, and can also control the transmission of capability information related to fault information.

[0046] The above-described function of the WAB node 150 may be provided as a function of the radio base station (gNB100). In the case of the gNB100, the gNB100 (master node) may be configured with a transmitter that, when a failure occurs in the secondary cell group, transmits failure information indicating that the failure is related to the radio backhaul to other radio base stations constituting the secondary node.

[0047] (2.2) UE 200 As shown in FIG. 5, the UE 200 includes a radio communication unit 210, an RLF / HO reporting unit 220, a system information acquisition unit 230, and a control unit 240.

[0048] The wireless communication unit 210 transmits an uplink signal (UL signal) conforming to NR. The wireless communication unit 210 also receives an uplink signal (DL signal) conforming to NR. In this embodiment, the wireless communication unit 210 may constitute a communication unit that performs wireless communication with a WAB node 150 (wireless communication node) connected to a network via a wireless backhaul. Note that the wireless communication unit 210 can perform wireless communication with the WAB node 150 via wireless access, and can also perform direct wireless communication with the gNB 100 via wireless access.

[0049] The RLF / HO reporting unit 220 performs processing related to radio link failure (RLF) and handover (HO) reporting. Specifically, the RLF / HO reporting unit 220 can transmit an RLF report to the network. The RLF / HO reporting unit 220 can also transmit a handover failure report and a successful handover report to the network.

[0050] The RLF report may be interpreted as a report of a failure related to a radio link established by the UE 200. The handover failure report may be interpreted as a report of a situation when a handover to a target cell fails. The successful handover report may be interpreted as a report of a situation when a handover to a target cell is successful. In this way, the RLF / HO reporting unit 220 can transmit reports related to handover to the network.

[0051] Note that the serving cell may be interpreted simply as a cell to which the UE 200 is connected in relation to the target cell, but more precisely, in the case of an RRC_CONNECTED UE in which carrier aggregation (CA) is not configured, there is only one serving cell that constitutes the primary cell. In the case of an RRC_CONNECTED UE configured using CA, the serving cell may be interpreted as indicating a set of one or more cells including the primary cell and all secondary cells.

[0052] The RLF / HO reporting unit 220 may send a radio link failure report (RLF report), a handover failure report, or a successful handover report to the network, which report includes at least one of the status, quality, and result of the handover.

[0053] The RLF / HO reporting unit 220 can measure the quality of the serving cell of the UE 200 and neighboring cells of the serving cell and report the measurement results (Measurement Report) to the network. The RLF / HO reporting unit 220 can perform measurement reporting of the source cell (transfer source cell) and the target cell (transfer destination cell) during handover.

[0054] The quality to be measured may be, for example, the quality included in the Measurement Report specified in 3GPP TS38.331 (for example, RSRP (Reference Signal Received Power), RSRQ (Reference Signal Received Quality)).

[0055] The system information acquisition unit 230 acquires system information broadcast from the network. Specifically, the system information acquisition unit 230 can receive multiple types of system information blocks (SIBs) from the network.

[0056] In particular, in this embodiment, the system information acquisition unit 230 may constitute a receiving unit that receives system information indicating the types of neighboring cells including the cell formed by the WAB node 150 (wireless communication node).

[0057] Specifically, the system information acquisition unit 230 may receive SIB1 including the types of neighboring cells of the UE 200. Note that the system information does not necessarily have to be reported by SIB1, and may be reported by another SIB (for example, SIB4).

[0058] The system information acquisition unit 230 may receive system information indicating the type of cell formed by a WAB node (wireless communication node) mounted on a mobile object, a WAB node not mounted on a mobile object, or a WAB node providing the functionality of a wireless base station. Here, a mobile object may typically refer to a vehicle shared by multiple users, such as a train or other railroad vehicle, or a bus. However, the mobile object is not limited to such vehicles and may also include aircraft, ships, small automobiles, etc.

[0059] Furthermore, system information acquisition unit 230 may receive system information including access restrictions to a cell formed by WAB node 150. Specifically, system information acquisition unit 230 may receive an SIB including CellBarredWAB or cellBarredWAB-MT indicating that access to a cell formed by WAB node 150 is restricted.

[0060] The system information acquisition unit 230 may receive system information including whether wireless backhaul is supported. Specifically, the system information acquisition unit 230 may receive SIB1 indicating whether the network supports WAB.

[0061] The control unit 240 controls each functional block constituting the UE 200. In particular, in this embodiment, the control unit 240 may select a cell based on system information (e.g., SIB1) acquired by the system information acquisition unit 230. Specifically, the control unit 240 may select a cell to connect to based on the cell type of a neighboring cell of the UE 200 included in the system information.

[0062] As described above, the cell types may include cells formed by WAB nodes mounted on mobile objects such as trains, WAB nodes not mounted on mobile objects, or WAB nodes that provide the functionality of a radio base station.

[0063] (3) Operation of the Wireless Communication System Next, a description will be given of the operation of the wireless communication system 10. Specifically, the operation of the UE and WAB nodes related to the Wireless Access Backhaul (WAB) will be described.

[0064] (3.1) Assumptions Regarding Wireless Access Backhaul (WAB), 3GPP has agreed that a WAB node can include a gNB component (WAB-gNB) and a Mobile Termination (MT) component (WAB-MT). On the other hand, it has also agreed that a WAB-gNB does not provide the WAB-MT function.

[0065] Based on these agreements, the architecture and protocol stack of WAB are currently being considered (see Figures 2 and 3).

[0066] (3.2) Operation Example 1 Fig. 6 shows an example of the configuration of a WAB cell and neighboring cells according to Operation Example 1. As shown in Fig. 6, when a WAB node is mounted on a vehicle such as a train or bus, the cell formed by the WAB node (WAB-gNB-Cell) will move. In such a case, a UE served by the cell must preferentially select the cell (referred to as a mobile WAB-Cell (or WAB Cell)).

[0067] If a UE under the WAB node selects another neighboring cell (gNB), unnecessary HO and RLF may occur. Conversely, if a UE not under the WAB node selects a WAB-gNB-Cell, unnecessary HO and RLF may also occur. Therefore, the UE needs to distinguish between a mobile WAB-Cell (WAB-gNB-Cell) and a normal cell. Below, we will explain an example of signaling that realizes such UE operation.

[0068] Fig. 7 shows an example of the configuration of SIB1 including a mobile WAB-Cell. Fig. 8 shows an example of the configuration of SIB1 including a WAB Cell.

[0069] A new indication (e.g., mobile WAB-Cell, WAB Cell, or WAB-gNB-Cell) may be added to SIB1 broadcast from the gNB (network). If the indication is set to true, it may mean that the cell is a mobile WAB-Cell or a WAB Cell.

[0070] Alternatively, two indications, WAB Cell and mobile WAB-Cell (mobile cell), may be broadcast by SIB1. Also, a combination of these two indications may indicate that the cell is a mobile WAB-Cell.

[0071] If the indication is absent, it may mean that the cell is "not a WAB Cell" or "not a mobile WAB-Cell." Also, a UE in a vehicle equipped with a mobile WAB-Cell may determine that the frequency for the WAB Cell is the optimal cell that should be given the highest priority.

[0072] The UE may perform inter-freq cell reselection while taking into account the frequency for the mobile WAB-Cell (or WAB Cell). A UE inside a vehicle may preferentially select the frequency for the mobile WAB-Cell (or WAB Cell). A UE outside a vehicle preferably avoids selecting the frequency for the mobile WAB-Cell (or WAB Cell). The frequency for the mobile WAB-Cell (or WAB Cell) may be recognized by the UE by any of the following methods:

[0073] The mobile WAB Cell List is broadcast by SIB4. The mobile WAB Cell List may indicate a specific PCI (Physical Cell ID) range. In other words, the mobile WAB Cell List may indicate the range of PCIs in which mobile WAB-Cells are located.

[0074] The WAB Cell List is broadcast by SIB4. The WAB Cell List may indicate a specific PCI range. In other words, the WAB Cell List may indicate the range of PCIs in which the WAB Cells are located.

[0075] An indication of mobileWAB-Freq may be added to InterFreqCarrierFreqInfo in SIB4. This indication may mean that a mobile WAB node may be deployed on the inter-freq frequency. In other words, a mobile WAB-Cell (node) may be assumed to be deployed on an inter-frequency carrier.

[0076] An indication of WAB-Freq may be added to InterFreqCarrierFreqInfo in SIB4. This indication may mean that a WAB node may be deployed on the inter-freq frequency. In other words, the WAB node may be assumed to be deployed on an inter-frequency carrier.

[0077] Thus, a UE in a vehicle may identify a WAB cell by the mobile WAB-Cell or WAB Cell indication in SIB1. If such indication is broadcast by SIB4, the UE may narrow the search range for a WAB cell by "mobileWAB-cellist" or "WAB-cellist." Non-WAB cells may be excluded from the frequency prioritization of the mobile WAB-Cell for up to 300 seconds.

[0078] (3.3) Operation Example 2 As described above, it has been agreed that the WAB-gNB will not provide the WAB-MT function. An example of signaling that takes into account such agreement will be described below.

[0079] A new indication (e.g., mobile WAB-Cell, WAB Cell, or WAB-gNB-Cell) may be added to SIB1 (the indication in Operation Example 1 may be reused).

[0080] If this indication is set to true, it may mean that the cell is a mobile WAB-Cell.

[0081] Alternatively, two indications, WAB Cell and mobile WAB-Cell (mobile cell), may be broadcast by SIB1. If this indication is set to true, it may mean that the cell is barred (cellBarred) for WAB-MT. In other words, if this indication is set to true, the cell may not be considered as a candidate cell for cell (re)selection of the WAB node (WAB-MT).

[0082] Furthermore, if this indication is set to true, the "WAB-support" indication in the operation example 3 described later does not need to be set to true.

[0083] Alternatively, if the indication is set to true, it may mean that only UEs other than WAB-MT can camp on the cell, perform cell selection, and perform cell reselection.

[0084] If the indication is absent, it may mean that the cell is “not a WAB cell.” If the indication is absent and the “WAB-support” indication in Operation Example 3 is set to true, the WAB-MT may wait for the cell and perform cell selection and cell reselection.

[0085] Furthermore, a new barring indication (e.g., cellBarredWAB or cellBarredWAB-MT) may be added to SIB1. Fig. 9 shows an example of the configuration of SIB1 including CellBarredWAB (barred). Fig. 10 shows an example of the configuration of SIB1 including CellBarredWAB (barred, notBarred).

[0086] If cellBarredWAB or cellBarredWAB-MT is set to barred, it may mean that the cell is barred (cellBarred) for WAB-MT. In other words, if this indication is set to forbidden, the cell may not be considered as a candidate cell for cell (re)selection of the WAB node (WAB-MT).

[0087] Alternatively, when CellBarredWAB or cellBarredWAB-MT is set to barred, this may mean that only UEs other than WAB-MT can camp on the cell, perform cell selection, and cell reselection.

[0088] If CellBarredWAB or cellBarredWAB-MT is absent and the "WAB-support" indication in Operation Example 3 is set to true, WAB-MT may wait on the cell, and cell selection and cell reselection may be performed.

[0089] Furthermore, a new barring indication (e.g., cellBarredWAB or cellBarredWAB-MT) may be added to SIB1. When cellBarredWAB or cellBarredWAB-MT is not barred and the "WAB-support" indication in operation example 2 is set to true, WAB-MT may camp on the cell, and cell selection and cell reselection may be performed. This may also mean that UEs other than WAB-MT can camp on the cell, and cell selection and cell reselection are also possible.

[0090] (3.4) Operation Example 3 A specific gNB may be able to provide the WAB-MT functionality as a gNB serving WAB-MT. The gNB may also be unable to provide the WAB-MT functionality. In other words, the gNB may or may not want to barr the WAB-MT. The following describes an example of signaling that realizes such gNB operation.

[0091] A new indication (e.g., WAB-support) may be added to SIB1. Fig. 11 shows an example of the configuration of SIB1 including WAB-support. Fig. 12 shows an example of the configuration of PLMN-IdentityInfo including WAB-support. Fig. 13 shows an example of the configuration of NPN-IdentityInfo-r16 including WAB-support.

[0092] If the indication is set to true, it may mean that the cell supports WAB and that the cell is a target for cell (re)selection of a WAB-MT (WAB-node).

[0093] If this indication is absent, the WAB-MT (WAB-node) may determine that the cell is "barred." Since the WAB-gNB cannot provide the WAB-MT function, it is preferable not to set this indication to true. Also, if this indication is set to true, it is preferable not to set the indication of the "WAB-gNB-cell" in Operation Example 1 to true.

[0094] (3.5) Operation Example 4 Figure 14 shows an example network configuration including a WAB node according to Operation Example 4. When a radio link failure (RLF) occurs between a WAB-MT and a gNB serving WAB-MT, the failure cause of the failure must be distinguished from the failure cause reported by a normal UE. From the failure cause, the network can identify that the RLF occurred between the WAB-MT and the gNB serving WAB-MT.

[0095] When such an RLF occurs, the WAB-MT may report the following information to the gNB:

[0096] - Include WAB-BH-RLF as the rlf-cause in the RLF report.

[0097] - Add a new RLF cause as WAB-BH-RLFRecoveryFailure (tentative name is fine).

[0098] (3.6) Operation Example 5 Fig. 15 shows an example network configuration including a WAB node according to Operation Example 5. When a WAB-MT and a gNB serving WAB-MT are performing dual connectivity and an RLF occurs in an SCG, the WAB-MT can send SCGFailureInfo to the network, specifically, to the master node (Master gNB).

[0099] SCGFailureInfo may contain the following information:

[0100] - Include WAB-BH-RLF as failureType.

[0101] - Add a new RLF cause as WAB-BH-RLFRecoveryFailure (tentative name is fine).

[0102] As described above, Failure may include Recovery Failure, which means that recovery from RLF has failed.

[0103] (3.7) Operation Example 6 Figure 16 shows an example of configuration information exchange between a master node and a secondary node according to Operation Example 6. When a WAB-MT and a gNB serving WAB-MT are performing dual connectivity and an RLF occurs in the SCG, the WAB-MT can send SCGFailureInfo to the network, specifically, to the master node. The master node must then forward the SCGFailureInfo in the WAB-MT to the secondary node. The SCGFailureInfo may include the following information:

[0104] - Include WAB-BH-RLF as failureType of SCGFailureInfo in CG-configInfo.

[0105] - Add a new RLF cause as WAB-BH-RLFRecoveryFailure (tentative name is fine).

[0106] (3.8) Operation Example 7 Figure 17 shows an example network configuration including a WAB node according to Operation Example 7. When a WAB-MT and a gNB serving WAB-MT are performing dual connectivity and an RLF occurs in the MCG, the WAB-MT can send MCGFailureInfo to the network.

[0107] MCGFailureInfo may contain the following information:

[0108] - Include WAB-BH-RLF as failureType.

[0109] - Add a new RLF cause as WAB-BH-RLFRecoveryFailure (tentative name is fine).

[0110] (3.9) Operation Example 8 The WAB-MT (UE) may report capability information (UE capability) related to WAB-BH-RLF or WAB-BH-RLFRecoveryFailure to the network.

[0111] Specifically, if the WAB-MT supports WAB-BH-RLF-detection or WAB-BH-RLF-Detection-recovery, it may include at least one of a WAB-BH-RLF-indication or a WAB-BH-RLF-Detection-recovery indication in the UE-NR-Capability IE.

[0112] The above-described operational examples 1 to 8 are expected to have the following effects and advantages. Specifically, it is possible to reliably distinguish between a WAB-gNB-Cell and a normal cell. It is also possible to have the WAB-MT stand by the WAB-gNB-Cell and prevent cell selection and cell reselection. Furthermore, it is possible to implement signaling to support or restrict the WAB-MT, recognize the frequency for the mobile WAB-Cell (or WAB Cell) in inter-freq cell reselection, and report the RLF cause by the WAB-MT.

[0113] Therefore, the UE and WAB node can perform appropriate WAB settings while taking into consideration the WAB architecture, etc., and can reliably report failure conditions such as radio link failures to the network even when WAB is applied.

[0114] (4) Other Embodiments The contents of the present proposal have been explained above using examples, but it will be obvious to those skilled in the art that the present proposal is not limited to these descriptions and that various modifications and improvements are possible.

[0115] For example, the above-described operational example assumes WAB, but WAB can be a tentative name, and similar operations may be applied to network architectures other than WAB (e.g., IAB) as long as they utilize wireless backhaul (and wireless access).

[0116] In the above description, configure, activate, update, indicate, enable, specify, and select may be interchangeable. Similarly, link, associate, correspond, and map may be interchangeable, and allocate, assign, monitor, and map may be interchangeable.

[0117] Furthermore, specific, dedicated, UE-specific, and UE-dedicated may be interchangeable. Similarly, common, shared, group-common, UE-common, and UE-shared may be interchangeable.

[0118] The block diagrams (Figures 4 and 5) used to explain the above-described embodiments show functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (e.g., wired, wireless, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or multiple devices.

[0119] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how each is implemented.

[0120] Furthermore, the gNB 100, WAB node 150, and UE 200 (the devices) described above may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 18 is a diagram showing an example of the hardware configuration of the devices. As shown in Figure 18, the devices may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0121] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0122] Each functional block of the device (see FIGS. 4 and 5) is realized by any hardware element of the computer device or a combination of the hardware elements.

[0123] In addition, each function of the device is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.

[0124] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, and registers.

[0125] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. Furthermore, the various processes described above may be executed by a single processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0126] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 may store a program (program code), a software module, etc., capable of executing a method according to an embodiment of the present disclosure.

[0127] Storage 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0128] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.

[0129] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

[0130] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0131] Furthermore, each device such as the processor 1001 and the memory 1002 is connected to a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0132] Furthermore, the device may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0133] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0134] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, a 4th generation mobile communication system (4G), a 5th generation mobile communication system (5G), a 6th generation mobile communication system (6G), an xth generation mobile communication system (xG) (where x is, for example, an integer or a decimal), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable system, and a next-generation system extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G) may also be applied.

[0135] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0136] In the present disclosure, a specific operation described as being performed by a base station may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (e.g., MME or S-GW, etc., but are not limited to these). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (e.g., MME and S-GW) may also be used.

[0137] Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input and output via multiple network nodes.

[0138] The input and output information may be stored in a specific location (for example, a memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added. The output information may be deleted. The input information may be transmitted to another device.

[0139] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0140] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0141] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0142] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0143] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0144] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0145] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0146] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0147] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0148] In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0149] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0150] The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

[0151] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

[0152] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0153] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0154] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0155] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies hereinafter). For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel (or sidelink).

[0156] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station.

[0157] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0158] Numerology may be communication parameters that apply to the transmission and / or reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

[0159] A slot may consist of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) A slot may be a numerology-based time unit.

[0160] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0161] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0162] For example, one subframe may be referred to as a transmission time interval (TTI), multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0163] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station schedules each user terminal to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) in TTI units. Note that the definition of TTI is not limited to this.

[0164] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0165] In addition, when one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling, and the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0166] A TTI having a time length of 1 ms may be referred to as a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be referred to as a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0167] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0168] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

[0169] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may consist of one or more resource blocks.

[0170] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0171] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0172] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0173] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0174] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0175] The above-described structures of the radio frame, subframe, slot, minislot, and symbol are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations may be changed in various ways.

[0176] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0177] The reference signal may also be abbreviated as Reference Signal (RS) and may be called a pilot depending on the applicable standard.

[0178] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0179] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0180] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure 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.

[0181] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0182] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0183] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0184] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0185] 19 shows an example of the configuration of a vehicle 2001. As shown in Fig. 19, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013.

[0186] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user. The electronic control unit 2010 is composed of a microprocessor 2031, memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals from various sensors 2021 to 2027 provided in the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0187] The signals from the various sensors 2021 to 2028 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0188] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 1.

[0189] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0190] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driving assistance functions or autonomous driving functions.

[0191] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 1 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from a driving unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, a microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2028, which are provided in the vehicle 2001.

[0192] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0193] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021 to 2028 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021 to 2028, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0194] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle. The information service unit 2012 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, sensors 2021 to 2028, and the like provided in the vehicle 2001.

[0195] (Additional Note) The above disclosure may be expressed as follows: A first feature is a terminal including: a communication unit that performs wireless communication with a wireless communication node connected to a network via a wireless backhaul, a receiving unit that receives system information indicating types of neighboring cells including a cell formed by the wireless communication node, and a control unit that selects the cell based on the system information.

[0196] A second feature is that, in the first feature, the receiving unit receives the system information indicating a type of a cell formed by the wireless communication node mounted on a mobile body, the wireless communication node not mounted on the mobile body, or the wireless communication node providing a function of a wireless base station.

[0197] In a third feature based on the first or second feature, the receiver receives the system information including access restriction to a cell formed by the wireless communication node.

[0198] A fourth feature, in any one of the first to third features, is that the receiver receives the system information including whether the wireless backhaul is supported.

[0199] 10 Wireless communication system 20 NG-RAN 100 gNB 110 Wireless communication unit 120 Backhaul connection unit 130 Fault processing unit 140 Control unit 150 WAB node 200 UE 210 Wireless communication unit 220 RLF / HO reporting unit 230 System information acquisition unit 240 Control unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system section 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port

Claims

1. A terminal comprising: a communication unit that performs wireless communication with a wireless communication node connected to a network via a wireless backhaul; a receiving unit that receives system information indicating the types of neighboring cells including a cell formed by the wireless communication node; and a control unit that selects the cell based on the system information.

2. The terminal according to claim 1, wherein the receiving unit receives the system information indicating the type of cell formed by the wireless communication node mounted on a mobile body, the wireless communication node not mounted on the mobile body, or the wireless communication node providing the function of a wireless base station.

3. The terminal according to claim 1, wherein the receiving unit receives the system information including access restrictions to a cell formed by the wireless communication node.

4. The terminal according to claim 1, wherein the receiver receives the system information including whether the wireless backhaul is supported.

5. A wireless communication method in a terminal, comprising: a step of performing wireless communication with a wireless communication node connected to a network via a wireless backhaul; a step of receiving system information indicating the types of neighboring cells including a cell formed by the wireless communication node; and a step of selecting the cell based on the system information.