Network device, wireless base station, and wireless communication method

Abstract

This network device executes control relating to an interface in a wireless base station that provides a wireless backhaul. The network device receives, from the radio base station, an uplink setting transfer message including identification information that indicates that the type of the wireless base station is a backhaul wireless base station that provides a wireless backhaul, and transmits a downlink setting transfer message including the identification information to another wireless base station.

Description

Network device, radio base station, and radio communication method

[0001] The present disclosure relates to a network device, a radio base station, and a radio communication method that support Wireless Access Backhaul (WAB).

[0002] The 3rd Generation Partnership Project (3GPP: registered trademark) has standardized the 5th generation mobile communication system (also called 5G, New Radio (NR), or Next Generation (NG)), and is also proceeding with the standardization of the next generation, called Beyond 5G, 5G Evolution, or 6G.

[0003] In 3GPP Release-19, studies on Wireless Access Backhaul (WAB) are underway (Non-Patent Documents 1, 2). For example, it has been agreed that a WAB-gNB, which is a function equivalent to a radio base station (gNB) that can provide a WAB function, supports the Xn interface between radio access network nodes (RAN nodes).

[0004] Also, in 3GPP Release-18, a mechanism for automatically establishing the Xn interface by RAN nodes exchanging Transport Network Layer (TNL) configuration information (Xn TNL Configuration Info) has been defined (Non-Patent Document 3).

[0005] On the other hand, in Non-Patent Document 1, it has been agreed to prevent the setting of the Xn interface between WAB-gNBs, such as with other neighboring WAB-gNBs.

[0006] "New WID on additional topological enhancements for NR", RP-242395, 3GPP TSG RAN Meeting #105, 3GPP, September 2024 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 3GPP TS 38.413 V18.4.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP) (Release 18), 3GPP, December 2024

[0007] However, if the mechanism described above for automatically establishing the Xn interface is followed, it will not be possible to prevent the setting of the Xn interface between the WAB and gNB, and there is a risk that an unintended Xn interface may be set.

[0008] Therefore, the following disclosure is made in light of these circumstances and aims to provide network equipment, wireless base stations, and wireless communication methods that can reliably prevent the unintended configuration of Xn interfaces between WABs and gNBs.

[0009] One aspect of the present disclosure is a network device (AMF70) comprising: a control unit (control unit 77) that performs control relating to an interface at a wireless base station that provides wireless backhaul; a receiving unit (TNL processing unit 75) that receives an uplink setting transfer message from the wireless base station, which includes identification information indicating that the type of wireless base station is a backhaul wireless base station that provides wireless backhaul; and a transmitting unit (TNL processing unit 75) that transmits a downlink setting transfer message including the identification information to another wireless base station.

[0010] One aspect of the present disclosure is a network device (AMF70) comprising: a control unit (control unit 77) that performs control relating to an interface at a wireless base station that provides wireless backhaul; a receiving unit (TNL processing unit 75) that receives an uplink setting transfer message from another wireless base station, which includes identification information indicating that the other wireless base station is a backhaul wireless base station that provides the wireless backhaul; and a transmitting unit (TNL processing unit 75) that transmits a downlink setting transfer message including the identification information to the wireless base station.

[0011] One aspect of the present disclosure is a network device (AMF70) comprising: a control unit (control unit 77) that performs control relating to an interface at a wireless base station providing wireless backhaul; a receiving unit (TNL processing unit 75) that receives an uplink setting transfer message from the wireless base station, which includes a request for setting information relating to the network layer transport function at a neighboring wireless base station located near the wireless base station; and a transmitting unit (TNL processing unit 75) that transmits a downlink setting transfer message containing the setting information to another wireless base station.

[0012] One aspect of the present disclosure is a radio base station (gNB100) comprising a control unit (control unit 140) that performs control relating to an interface in a backhaul radio base station that provides radio backhaul, and a transmission unit (TNL processing unit 130) that, when an interface is established with the backhaul radio base station, transmits identification information of an adjacent radio base station adjacent to itself and setting information relating to the network layer transport function at itself to the backhaul radio base station via the interface.

[0013] Figure 1 is an overall schematic diagram of the wireless communication system 10. Figure 2 is a diagram showing the basic architecture of the network according to WAB. Figure 3 is a functional block diagram of AMF70. Figure 4 is a functional block diagram of gNB100. Figure 5 is a diagram showing example 1 of SON configuration transfer between AMF and RAN node related to operation example 1. Figure 6 is a diagram showing example 2 of SON configuration transfer between AMF and RAN node related to operation example 1. Figure 7 is a diagram showing an example of SON configuration transfer configuration. Figure 8 is a diagram showing an example of SON Information configuration. Figure 9 is a diagram showing an example of SON Information reject configuration. Figure 10 is a diagram showing example 1 of SON configuration transfer between AMF and RAN node related to operation example 2. Figure 11 is a diagram showing example 2 of SON configuration transfer between AMF and RAN node related to operation example 2. Figure 12 is a diagram showing an example of Xn interface configuration between WAB-gNB, BH-gNB and neighbor gNB. Figure 13 shows an example of the hardware configuration of BH RAN node 80, gNB100, WAB node 150, and UE200. Figure 14 shows an example of the configuration of vehicle 2001.

[0014] The embodiments will be described below with reference to the drawings. Note that identical or similar reference numerals are used to denote the same functions and components, and their descriptions will be omitted as appropriate.

[0015] (1) Overall schematic diagram 1 of the wireless communication system is an overall schematic diagram of the wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system in accordance with 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN20) and a terminal 200 (User Equipment 200, hereinafter, UE200).

[0016] The wireless communication system 10 may be a wireless communication system conforming to a method called Beyond 5G, 5G Evolution, or 6G, or it 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 URLLC (Ultra-Reliable and Low Latency Communications).

[0017] NG-RAN20 includes BH RAN nodes 80, radio base stations 100 (hereinafter referred to as gNB100), and WAB nodes 150. The specific configuration of the wireless communication system 10, including the number of gNBs (eNBs, etc.), BH RAN nodes, gNBs, WAB nodes, and UEs, is not limited to the example shown in Figure 1.

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

[0019] A WAB node 150 is a type of wireless communication node that conforms to Wireless Access Backhaul (WAB). A WAB node 150 may provide a WAB. Specifically, a WAB node 150 may configure one or more links that constitute a WAB. As shown in Figure 1, a WAB node 150 may be mounted on a vehicle such as a train or bus and move around.

[0020] NG-RAN20 actually includes multiple NG-RAN Nodes, specifically gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). 5GC may include logical nodes that provide network functions (NFs). NFs may include an Access and Mobility Management Function 70 (AMF70) that provides access and mobility management functions for UE200, a Session Management Function (SMF) that provides session management functions, and a Location Management Function (LMF) that handles communication control related to location information services defined in 5GC. Furthermore, a UDM / UDR (Unified Data Management / User Data Repository) may be connected to the AMF and / or SMF.

[0021] NG-RAN20 and 5GC may simply be referred to as "networks." In 5GC, the concept of CUPS (Control and User Plane Separation), in which the functions of the user plane and the control plane are clearly separated, may be introduced.

[0022] BH RAN node 80 is a RAN node that constitutes the wireless backhaul. BH RAN node 80 may be connected to WAB node 150 via an Xn interface. BH RAN node 80 may also be connected to 5GC that constitute the wireless backhaul.

[0023] The gNB100 is a radio base station compliant with NR and performs NR-compliant wireless communication with the UE200. The gNB100 may also consist of a CU (Central Unit) and a DU (Distributed Unit), and the DU may be located separately from the CU at a geographically different location. One or more DUs may be connected to the CU. The gNB100 (gNB-CU) may be connected by an Xn interface, and the CU and DU may be connected by an F1 interface (F1-AP, etc.). In this embodiment, the CU may be called a communication device or a central device, etc. The DU may be called a distributed device, etc.

[0024] In the wireless communication system 10, a Neighbor Relation Table (NRT, also called an NCRT (Neighbor Cell Relation Table)) may be used for handover (HO) of the UE200 to other cells and for managing the identification information (CGI: Cell Global Identifier) ​​of neighboring cells. The contents of the NRT may be manually pre-configured, but an Automatic Neighbor Relation (ANR) function that automatically associates information (CGI) of neighboring cells may be introduced.

[0025] Furthermore, the wireless communication system 10 may support conditional handover (CHO). CHO allows a UE200-led handover to be performed when specific execution conditions are met. If CHO is not applicable, a normal handover may be performed (this may be called CHO recovery).

[0026] Furthermore, the wireless communication system 10 may support conditional addition or change (CPAC) of Primary SCells (PSCells). A PSCell is a type of secondary cell. PSCell means Primary SCell (secondary cell), and it may be interpreted as corresponding to any of several SCells.

[0027] Figure 2 shows the basic architecture of a network compliant with WAB. Specifically, Figure 2 shows an example of a WAB architecture configuration when NG traffic of WAB-gNB is transmitted via PDU session backhaul.

[0028] As shown in Figure 2, the WAB node 150 (WAB node) may consist of a WAB-gNB that provides an interface with the UE200 and a WAB-MT that provides an interface with a higher-level node on the network side (e.g., gNB100). The UE200 and the AMF may be connected via an NG-C interface. The UE200 and the WAB node 150 may be connected via an NR-Uu interface.

[0029] Furthermore, the WAB-gNB and the BH RAN node (BH RAN node 80) may be connected via the Xn interface as described above.

[0030] The gNB100 and UE200 can support Massive MIMO, which generates a more directional beam by controlling the radio signals transmitted from multiple antenna elements; carrier aggregation (CA), which uses multiple component carriers (CCs) bundled together; and dual connectivity (DC), which enables simultaneous communication between the UE and multiple NG-RAN Nodes.

[0031] The DC type may be Multi-RAT Dual Connectivity (MR-DC), which utilizes multiple radio access technologies, or NR-NR Dual Connectivity (NR-DC), which utilizes only NR. For example, one gNB may constitute the master node (MN), and one or more other gNBs may constitute secondary nodes (SN).

[0032] Note that the term "secondary node" may be interpreted as "secondary cell" or "secondary cell group (SCG)."

[0033] In this embodiment, the channel includes a control channel and a data channel. The control channel includes PDCCH (Physical Downlink Control Channel), PUCCH (Physical Uplink Control Channel), PRACH (Physical Random Access Channel), and PBCH (Physical Broadcast Channel), among others.

[0034] Furthermore, data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel), among others.

[0035] Reference signals include Demodulation Reference Signal (DMRS), Sounding Reference Signal (SRS), Phase Tracking Reference Signal (PTRS), and Channel State Information-Reference Signal (CSI-RS), while signals include channels and reference signals. Furthermore, "data" may refer to data transmitted via a data channel.

[0036] Furthermore, Layer 1 can be interpreted as including lower layers such as the physical layer. Layer 3 is a layer higher than Layer 1. The upper layers may include at least one of the following: the Wireless Link Control Layer (RLC), the Packet Data Convergence Protocol Layer (PDCP), or the Wireless Resource Control Layer (RRC), and the Media Access Control Layer (MAC) may be positioned between the lower and upper layers.

[0037] (2) Functional Block Configuration of the Wireless Communication System Next, the functional block configuration of the wireless communication system 10 will be described. Specifically, the functional block configurations of AMF70 and gNB100 will be described. Figure 3 is a functional block configuration diagram of AMF70. Figure 4 is a functional block configuration diagram of gNB100.

[0038] Note that Figures 3 and 4 only show the main functional blocks relevant to the description of the embodiment, and the device has other functional blocks (e.g., a power supply unit). Also, Figures 3 and 4 show the functional block configuration of the device; please refer to Figure 13 for the hardware configuration.

[0039] (2.1) AMF70 As shown in Figure 5, the AMF70 comprises a network IF unit 71, a C-plane processing unit 73, a TNL processing unit 75, and a control unit 77.

[0040] The network interface unit 71 provides a network interface (IF) to the RAN node (gNB100). For example, the network interface unit 71 may provide an NG interface as the network interface to the RAN node.

[0041] The C-plane processing unit 73 executes processing in the control plane (C-plane). Specifically, the C-plane processing unit 73 may execute processing related to signaling and control messages. For example, the C-plane processing unit 73 may execute processing related to connection or release between the UE 200 and the network, authentication and authorization of the UE 200, location management of the UE 200, and management of sessions with the UE 200.

[0042] Note that "authorization" may mean verification of the UE 200 (the user himself / herself), and "authentication" may mean granting legitimate rights to the UE 200 (the user). Here, it may be interpreted that authentication includes authorization.

[0043] The TNL processing unit 75 executes processing related to the TNL (Transport Network Layer). The TNL may be interpreted as a layer for transmitting data in a mobile communication network. The TNL may provide a mechanism for efficiently transferring data between network nodes and may mainly provide the following functions.

[0044] - Data transfer: Transmitting data from the UE 200 to the network and data from the network to the UE. - Ensuring reliability: Providing a mechanism to ensure that data is transferred accurately and completely. - Network management: Assisting in the management of connections and resources between network nodes. The TNL may mainly use protocols such as IP (Internet Protocol) and UDP (User Datagram Protocol) to transfer data. Thereby, high efficiency and reliability can be achieved throughout the communication network. As a specific example, the TNL can support data communication between gNBs 100 via the Xn interface.

[0045] In this embodiment, the TNL processing unit 75 may receive an uplink configuration transfer message including identification information indicating that the type of the radio base station (RAN node type) is a backhaul radio base station (e.g., WAB-gNB) that provides a wireless backhaul (WAB) from a radio base station (WAB-gNB) that provides a wireless backhaul. In this embodiment, the TNL processing unit 75 may constitute a receiving unit.

[0046] Specifically, the TNL processing unit 75 may receive an Uplink RAN configuration transfer (SON configuration transfer) including the identification information (which may also be referred to as an indicator) from a RAN node such as a gNB.

[0047] Further, the TNL processing unit 75 may receive an Uplink RAN configuration transfer including identification information indicating that the type of the other radio base station is a backhaul radio base station (e.g., WAB-gNB) that provides a wireless backhaul from another radio base station.

[0048] The TNL processing unit 75 may receive an uplink configuration transfer message including a request for setting information regarding the transport function of the network layer in a neighboring radio base station located in the vicinity of the radio base station from the radio base station. Specifically, the TNL processing unit 75 may receive an Uplink RAN configuration transfer including a request for Xn TNL Configuration Info from a RAN node such as a gNB.

[0049] Xn TNL Configuration Info is defined, for example, in Section 9.2.3.96 of 3GPP TS 38.423. Xn TNL Configuration Info may be used to signal the IP address of the GTP (GPRS Tunneling Protocol)-U endpoint and the IP address of the IPSec endpoint used for establishing an IPSec tunnel.

[0050] The TNL processing unit 75 may transmit a downlink configuration transfer message containing the identification information (indicator) to a RAN node such as a gNB (radio base station or other radio base station). In this embodiment, the TNL processing unit 75 may constitute a transmission unit. Specifically, the TNL processing unit 75 may transmit a Downlink RAN ​​configuration transfer (SON configuration transfer) containing the identification information (indicator) to the RAN node.

[0051] Furthermore, the TNL processing unit 75 may send a Downlink RAN ​​configuration transfer message containing the configuration information (Xn TNL Configuration Info) to a RAN node (another radio base station).

[0052] The control unit 77 controls each functional block that constitutes the AMF 70. In this embodiment, the control unit 77 may perform control related to the interface at the wireless base station (WAB-gNB) that provides wireless backhaul.

[0053] Specifically, the control unit 77 can perform control related to the establishment of the Xn interface in the WAB-gNB. More specifically, the control unit 77 may control the establishment of the Xn interface in the WAB-gNB by whether or not to send a Downlink RAN ​​configuration transfer including Xn TNL Configuration Info to a RAN node (which may include the WAB-gNB) via the TNL processing unit 75.

[0054] (2.2) gNB100 As shown in Figure 4, the gNB100 comprises a wireless communication unit 110, a network IF unit 120, a TNL processing unit 130, and a control unit 140.

[0055] The wireless communication unit 110 transmits a downlink signal (DL signal) in accordance with 6G to the UE200. The wireless communication unit 110 also receives an uplink signal (UL signal) in accordance with 6G from the UE200.

[0056] The network interface unit 120 provides a network interface (IF) to the core network (5GC). For example, the network interface unit 120 may provide an NG interface as a network interface to the NF included in the 5GC. Alternatively, the network interface unit 120 may provide an Xn interface to connect RAN nodes to each other.

[0057] The TNL processing unit 130 performs processing related to the Transport Network Layer (TNL). In this embodiment, if an interface is established with a backhaul radio base station (WAB-gNB), the TNL processing unit 130 may transmit identification information of adjacent radio base stations adjacent to its own station and configuration information regarding the network layer transport function at its own station to the backhaul radio base station via the interface. In this embodiment, the TNL processing unit 130 may constitute a transmission unit.

[0058] Specifically, the TNL processing unit 130 may send the global RAN node ID, TAI (Tracking Area Identity), NR CGI (Cell Global Identifier), and Xn TNL Configuration Info of the adjacent gNB(s) to the WAB-gNB via the Xn interface.

[0059] The control unit 140 controls each functional block that constitutes the gNB 100. In this embodiment, the control unit 140 may perform control related to the interface in the wireless base station (WAB-gNB) that provides wireless backhaul.

[0060] Specifically, the control unit 140 can perform control related to the establishment of the Xn interface in the WAB-gNB. More specifically, the control unit 140 may control the establishment of the Xn interface in the WAB-gNB by having the TNL processing unit 130 send an Uplink RAN ​​configuration transfer, including Xn TNL Configuration Info, to another RAN node (which may include the WAB-gNB) via the AMF70.

[0061] (3) Operation of the Wireless Communication System Next, the operation of the wireless communication system 10 will be described. Specifically, an example of operation related to the transmission and reception of Xn TNL Configuration Info will be described.

[0062] Furthermore, the technical challenges that can be addressed by the following examples of operation are not limited to those challenges, and other technical challenges not mentioned can be clearly understood by a person with ordinary skill in the art from the description of this embodiment.

[0063] By applying a mechanism to automatically establish Xn interfaces between RAN nodes, network operators (telecommunications carriers) can reduce operational costs. Therefore, 3GPP TS 38.413 enables the exchange of Xn TNL Configuration Info between RAN nodes where Xn interfaces are not configured, by sending an SON configuration transfer using Uplink RAN ​​configuration transfer and Downlink RAN ​​configuration transfer, thereby achieving automatic establishment of Xn interfaces.

[0064] (3.1) Example of operation 1 As described above, when Xn TNL Configuration Info is exchanged between RAN nodes (gNBs) via AMF using SON configuration transfer, there is a possibility that WAB-gNBs may exchange Xn TNL Configuration Info with each other and establish an Xn interface. On the other hand, 3GPP has agreed to prevent the establishment of Xn interfaces between WAB-gNBs, such as with other nearby WAB-gNBs.

[0065] Furthermore, it is possible for a WAB-gNB and a non-WAB-gNB (i.e., a normal gNB) to configure an Xn interface. In this case, when a WAB-gNB and a non-WAB-gNB automatically establish an Xn interface, the non-WAB-gNB needs to be aware of whether the other RAN node is a WAB-gNB or not. It is necessary to add WAB-gNBinding to the Xn setup request or Xn setup response message.

[0066] Even when allowing automatic establishment of Xn interfaces between WAB-gNBs, WAB-gNBs need to be aware of whether the other party is a WAB-gNB or not. Furthermore, with the future introduction of 6G gNBs, there is a possibility that 5G WAB-gNBs and neighbor 6G gNBs will automatically establish Xn interfaces. Alternatively, 6G WAB-gNBs and neighbor 5G gNBs may also automatically establish Xn interfaces. In this case, they need to be aware of each other's gNB types. It is also necessary to prevent automatic establishment of Xn interfaces between 5G-WAB-gNBs and 6G-WAB-gNBs.

[0067] Figure 5 shows example 1 of SON configuration transfer between AMF and RAN node related to operation example 1. Figure 6 shows example 2 of SON configuration transfer between AMF and RAN node related to operation example 1.

[0068] Figure 7 shows an example configuration for SON configuration transfer. Figure 8 shows an example configuration for SON Information. Figure 9 shows an example configuration for SON Information reject.

[0069] As shown in Figure 5, if RAN node1 is WAB-gNB, a new indicator may be added to the SON configuration transfer included in the Uplink RAN ​​configuration transfer sent from RAN node1 to AMF to indicate that the source RAN node type is WAB-gNB, backhaul gNB, normal gNB, 6G WAB-gNB, 6G backhaul gNB, 6G normal gNB, 5G WAB-gNB, 5G backhaul gNB, or 5G normal gNB. If the indicator indicating WAB-gNB is true, it may mean that the source base station is WAB-gNB.

[0070] Similarly, in the SON configuration transfer included in the Downlink RAN ​​configuration transfer sent from AMF to RAN node2, a new indicator may be added to indicate that the source RAN node type is WAB-gNB, backhaul gNB, normal gNB, 6G WAB-gNB, 6G backhaul gNB, 6G normal gNB, 5G WAB-gNB, 5G backhaul gNB, or 5G normal gNB. If the indicator for WAB-gNB is true, it may mean that the source base station is a WAB-gNB.

[0071] As shown in Figure 6, in the SON configuration transfer included in the Uplink RAN ​​configuration transfer sent from RAN node2 to AMF, a new indicator may be added to indicate that the target RAN node type is WAB-gNB, backhaul gNB, normal gNB, 6G WAB-gNB, 6G backhaul gNB, 6G normal gNB, 5G WAB-gNB, 5G backhaul gNB, or 5G normal gNB. If the indicator indicating WAB-gNB is true, it may mean that the target base station is a WAB-gNB.

[0072] If RAN node2 is also WAB-gNB, the SON information (see Figure 8) of the SON configuration transfer included in the Uplink RAN ​​configuration transfer sent from RAN node2 to AMF may have a SON information reject (see Figure 9) added. The SON information reject may also have a cause value (for example, target gNB is WAB-gNB) added to it.

[0073] Similarly, in the SON configuration transfer included in the Downlink RAN ​​configuration transfer sent from AMF to RAN node1, a new indicator may be added to indicate that the target RAN node type is WAB-gNB, backhaul gNB, normal gNB, 6G WAB-gNB, 6G backhaul gNB, 6G normal gNB, 5G WAB-gNB, 5G backhaul gNB, or 5G normal gNB. If the indicator for WAB-gNB is true, it may mean that the target base station is a WAB-gNB.

[0074] If RAN node2 is also WAB-gNB, a SON information reject (see Figure 9) may be added to the SON information (see Figure 8) of the SON configuration transfer during the Uplink RAN ​​configuration transfer sent from RAN node2 to AMF. A cause value (for example, target gNB is WAB-gNB (or both source and target gNB are WAB-gNB)) may also be added to the SON information reject.

[0075] (3.2) Operation Example 2 A WAB-gNB may automatically establish an Xn interface with a neighbor gNB. To enable the WAB-gNB to establish (configure) an Xn interface with a neighbor gNB more efficiently, it is conceivable that the neighbor gNB's Xn TNL Configuration Info is sent to the WAB-gNB via a BH-gNB (BH RAN node).

[0076] Figure 10 shows example 1 of SON configuration transfer between AMF and RAN node related to operation example 2. Figure 11 shows example 2 of SON configuration transfer between AMF and RAN node related to operation example 2. Figure 12 shows an example of Xn interface configuration between WAB-gNB, BH-gNB and neighbor gNB.

[0077] As shown in Figure 10, if RAN node1 is a WAB-gNB, the SON configuration transfer included in the Uplink RAN ​​configuration transfer sent from RAN node1 to AMF may include a SON information request for the neighbor gNB of RAN node2 (i.e., a request for the neighbor gNB's Xn TNL Configuration Info). The SON information request may also include the neighbor gNB's global RAN node ID, selected TAI, and NR CGI.

[0078] Similarly, the SON configuration transfer included in the Downlink RAN ​​configuration transfer sent from AMF to RAN node2 may include a SON information request for the neighbor gNB of RAN node2 (i.e., a request for the neighbor gNB's Xn TNL Configuration Info). The SON information request may include the neighbor gNB's global RAN node ID, selected TAI, and NR CGI.

[0079] As shown in Figure 11, the SON configuration transfer included in the Uplink RAN ​​configuration transfer sent from RAN node2 to AMF may contain the Xn TNL Configuration Info or Xn TNL Configuration Info list of the neighbor gNB(s) requested by RAN node1.

[0080] Similarly, the SON configuration transfer included in the Downlink RAN ​​configuration transfer sent from AMF to RAN node1 may contain the Xn TNL Configuration Info or Xn TNL Configuration Info list of the neighbor gNB(s) that RAN node1 requests.

[0081] Furthermore, if RAN node1 is a WAB-gNB, RAN node2 is a BH-gNB, and an Xn interface has already been established between RAN node1 and RAN node2, RAN node2 may send the global RAN node ID, TAI, NR CGI, Xn TNL Configuration Info, or Xn TNL Configuration Info list of its neighboring gNB(s) to RAN node1 via the Xn interface.

[0082] As shown in the example above, the RAN node can exchange an indicator (identification information) that it is a WAB-gNB during SON configuration transfer, thus reliably preventing unintended configuration (automatic establishment) of the Xn interface between WAB-gNBs.

[0083] Furthermore, as shown in the example operation described above, a WAB-gNB can provide other RAN nodes with the global RAN node ID, TAI, NR CGI, Xn TNL Configuration Info, or Xn TNL Configuration Info list of its neighboring gNB(s). This ensures that unintended configuration (automatic establishment) of Xn interfaces between WAB-gNBs can be reliably prevented.

[0084] (4) Other Embodiments Although embodiments have been described above, it will be obvious to those skilled in the art that the embodiments are not limited to those described and that various modifications and improvements are possible.

[0085] For example, the above example assumed a WAB, but WAB is just a placeholder name, and similar operation may be applied to any network architecture that utilizes wireless backhaul (and wireless access), other than WAB (e.g., IAB).

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

[0087] Furthermore, "specific," "dedicated," "UE specific," and "UE individual" may be interpreted interchangeably. Similarly, "common," "shared," "group-common," "UE common," and "UE shared" may be interpreted interchangeably.

[0088] The block diagrams (Figures 3 and 4) used in the description of the embodiments above show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining software with the one or more of the above devices.

[0089] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In any case, as mentioned above, the method of implementation is not particularly limited.

[0090] Furthermore, the BH RAN node 80, gNB 100, WAB node 150, and UE 200 (the device) described above may function as a computer that processes the wireless communication method of this disclosure. Figure 13 shows an example of the hardware configuration of the device. As shown in Figure 13, the device may be configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, and bus 1007.

[0091] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the device may include one or more of the devices shown in the diagram, or it may be configured to omit some of the devices.

[0092] Each functional block of the device (see Figures 3 and 4) is implemented by any hardware element of the computer device, or a combination of such hardware elements.

[0093] Furthermore, each function in the device is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of the reading and writing of data in the memory 1002 and storage 1003.

[0094] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, and so on.

[0095] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. Moreover, the above-mentioned various processes may be executed by one processor 1001, or by two or more processors 1001 simultaneously or sequentially. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from a network via a telecommunications line.

[0096] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store a program (program code), software module, etc., that can execute a method according to one embodiment of this disclosure.

[0097] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., Compact Disc, Digital Multipurpose Disc, Blu-ray® Disc), a smart card, flash memory (e.g., a card, stick, key drive), a floppy® disk, a magnetic strip, etc. Storage 1003 may also be called an auxiliary storage device. The recording medium described above may also be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0098] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc.

[0099] The communication device 1004 may be configured to include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD).

[0100] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

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

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

[0103] Furthermore, notification of information is not limited to the embodiments described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

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

[0105] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be reordered, provided they do not contradict each other. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0106] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node. 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 can be performed by the base station and at least one other network node (for example, an MME or S-GW, but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station, it may also be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0107] Information and signals (such as data) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may occur via multiple network nodes.

[0108] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be sent to other devices.

[0109] The determination may be made by a value represented by one bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0110] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0111] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0112] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technologies (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

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

[0114] In addition, terms used 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 the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0115] The terms “system” and “network” as used in this disclosure are interchangeable.

[0116] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or corresponding other information. For example, wireless resources may be indicated by an index.

[0117] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Since various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are not restrictive in any way.

[0118] In this disclosure, terms such as "Base Station (BS)," "wireless 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.

[0119] A base station can house one or more (e.g., three) cells (also called sectors). If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0120] The terms "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base stations and base station subsystems that provide communication services in this coverage.

[0121] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform control or operation based on the information.

[0122] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0123] 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 appropriate term.

[0124] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (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 be a device that does not necessarily move during communication operation. 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.

[0125] Furthermore, the term "base station" in this disclosure may be interpreted as "mobile station" (user terminal, hereinafter the same). For example, the various aspects / embodiments of this 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), Vehicle-to-Everything (V2X), etc.). In this case, the mobile station may have the functions that a base station has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc. may be interpreted as side channel (or side link).

[0126] Similarly, the term "mobile station" in this disclosure may be interpreted as "base station." In this case, the base station may be configured to have the functions that a mobile station has.

[0127] A wireless frame may consist of one or more frames in the time domain. Each of these one or more frames in the time domain may be called a subframe. A subframe may further consist 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.

[0128] Numerology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerology may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

[0129] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). A slot may also be a time unit based on neurology.

[0130] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called PDSCH (or PUSCH) mapping type B.

[0131] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

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

[0133] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0134] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Note that when a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0135] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0136] A TTI with a time length of 1ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0137] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

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

[0139] Furthermore, the time domain of RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0140] One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0141] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0142] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a given BWP.

[0143] A BWP may include BWPs for UL (UL BWP) and BWPs for DL ​​(DL BWP). One or more BWPs may be set within a single carrier for a UE.

[0144] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0145] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0146] The terms “connected,” “coupled,” and any variations thereof mean 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” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

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

[0148] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

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

[0150] 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 in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the First and Second elements do not imply that only two elements may be employed therein, or that the First element must precede the Second element in any way.

[0151] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to be exclusive OR.

[0152] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0153] The terms “determining” and “determining” as used in this disclosure may encompass a wide variety of actions. “Determining” and “determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in a table, database, or other data structure), or ascertaining. “Determining” and “determining” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, or accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having "judgmented" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having "judgmented" or "decided" about some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0154] In this 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 "combine" may be interpreted similarly to "different."

[0155] Figure 14 shows an example of the configuration of vehicle 2001. As shown in Figure 14, 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.

[0156] The drive unit 2002 consists 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 rear wheels based on the operation of the steering wheel operated by the user. The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 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).

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

[0158] The Information Services Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including car navigation systems, audio systems, speakers, televisions, and radios, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via communication modules 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0159] Information Services Unit 2012 may include input devices that accept input from external sources (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) and output devices that perform output to external sources (e.g., displays, speakers, LED lamps, touch panels, etc.).

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

[0161] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via its communication port 2033 between 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, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2028 of the vehicle 2001.

[0162] 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 external devices. For example, it can send and receive various types of information to and from external devices 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 or a mobile station.

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

[0164] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 installed in the vehicle. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers 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 the external device in a memory 2032 that is available to the microprocessor 2031. Based on the information stored in 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-2028, etc., installed in the vehicle 2001.

[0165] This application is based on Japanese Patent Application No. 2025-024510, filed on February 18, 2025. All of its contents are included herein.

[0166] 10 Wireless communication system 20 NG-RAN 70 AMF 71 Network IF section 73 C-plane processing section 75 TNL processing section 77 Control section 80 BH RAN node 100 gNB 110 Wireless communication section 120 Network IF section 130 TNL processing section 140 Control section 150 WAB node 200 UE 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 Rotation speed 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 Driver assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port

Claims

1. A network device comprising: a control unit that performs control relating to an interface at a wireless base station that provides wireless backhaul; a receiving unit that receives an uplink setting transfer message from the wireless base station, which includes identification information indicating that the type of wireless base station is a backhaul wireless base station that provides wireless backhaul; and a transmitting unit that transmits a downlink setting transfer message, which includes the identification information, to another wireless base station.

2. A network device comprising: a control unit that performs control over the interface at a wireless base station providing wireless backhaul; a receiving unit that receives an uplink setting transfer message from another wireless base station, which includes identification information indicating that the other wireless base station is a backhaul wireless base station providing the wireless backhaul; and a transmitting unit that transmits a downlink setting transfer message, which includes the identification information, to the wireless base station.

3. A network device comprising: a control unit that performs control over the interface at a wireless base station providing wireless backhaul; a receiving unit that receives an uplink setting transfer message from the wireless base station, which includes a request for setting information regarding the network layer transport function at a neighboring wireless base station located near the wireless base station; and a transmitting unit that transmits a downlink setting transfer message containing the setting information to another wireless base station.

4. A radio base station comprising: a control unit that performs control over the interface at a backhaul radio base station that provides radio backhaul; and a transmission unit that, when an interface is established with the backhaul radio base station, transmits identification information of an adjacent radio base station adjacent to itself and setting information regarding the network layer transport function at itself to the backhaul radio base station via the interface.

5. A wireless communication method in a network device, comprising the steps of: performing control over an interface at a wireless base station providing wireless backhaul; receiving an uplink setting transfer message from the wireless base station, which includes identification information indicating that the type of wireless base station is a backhaul wireless base station providing the wireless backhaul; and transmitting a downlink setting transfer message, which includes the identification information, to another wireless base station.

6. A wireless communication method in a network device, comprising the steps of: performing control over an interface at a wireless base station providing wireless backhaul; receiving an uplink setting transfer message from another wireless base station, which includes identification information indicating that the other wireless base station is a backhaul wireless base station providing the wireless backhaul; and transmitting a downlink setting transfer message, which includes the identification information, to the wireless base station.

Images