Wireless communication node and wireless communication method

Abstract

This wireless communication node controls: connection in a wireless control layer with a wireless base station providing wireless backhaul; and / or handover with another wireless communication node of the wireless base station. The wireless communication node transmits, to the other wireless communication node, a handover message including configuration information related to a transport function of a network layer in the wireless base station.

Description

Wireless Communication Node and Wireless Communication Method

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

[0002] The 3rd Generation Partnership Project (3GPP: registered trademark) has specified the 5th generation mobile communication system (also referred to as 5G, New Radio (NR), or Next Generation (NG)), and is further promoting the specification of the next generation, such as 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 the 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] "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

[0006] Since WAB-gNBs may be installed and moved on vehicles such as trains and buses, they may perform handovers between RAN nodes (BH RAN nodes) that constitute the wireless backhaul. In this case, the BH RAN node receiving the handover needs to know the WAB-gNB's Xn TNL Configuration Info in order to establish an Xn interface with the WAB-gNB.

[0007] However, because the Xn TNL Configuration Info is configured by the OAM system that supports operation, management, and maintenance, a significant delay is unavoidable. Therefore, when attempting to obtain the Xn TNL Configuration Info from the OAM side during a WAB-gNB handover in transit, the delay becomes a problem, potentially leading to handover failures.

[0008] Therefore, the following disclosure is made in light of these circumstances and aims to provide a wireless communication node and wireless communication method that can quickly and reliably provide Xn TNL Configuration Info to a BH RAN node.

[0009] One aspect of the present disclosure is a wireless communication node (BH RAN node 80) comprising a wireless base station (WAB node 150) that provides wireless backhaul, a control unit (control unit 87) that controls at least one of the connection in the wireless resource control layer and the handover of the wireless base station to other wireless communication nodes, and a transmission unit (message processing unit 85) that transmits a handover message including configuration information regarding the transport function of the network layer in the wireless base station to the other wireless communication node.

[0010] 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 the BH RAN node 80. Figure 4 is a diagram showing an example of reconnection between a WAB node and a BH RAN node. Figure 5 is a diagram showing an example where a WAB node resumes RRC connection to a neighboring BH RAN node when the WAB-gNB and the neighboring BH RAN node are in an RRC INACTIVE state. Figure 6 is a diagram showing an example of a handover sequence between a WAB node and a BH RAN node. Figure 7 is a diagram showing an example of a sequence in the event of a handover failure or wireless link failure between a WAB node and a BH RAN node. Figure 8 is a diagram showing an example of a sequence in the event of a handover failure or wireless link failure between a WAB node and a BH RAN node when CHO or LTM is applied. Figure 9 is a diagram showing an example of a sequence in which a WAB-gNB and a BH RAN node resume RRC connection when they are in an RRC INACTIVE state. Figure 10 shows an example of the hardware configuration of BH RAN node 80, gNB100, WAB node 150, and UE200. Figure 11 shows an example of the configuration of vehicle 2001.

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

[0012] (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).

[0013] 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).

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

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

[0016] WAB node 150 is a type of wireless communication node that conforms to Wireless Access Backhaul (WAB). WAB node 150 may provide a WAB. Specifically, WAB node 150 may configure one or more links that constitute a WAB.

[0017] 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 (SMF) 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, UDM / UDRs (Unified Data Management / User Data Repository) may be connected to the AMF and / or SMF.

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

[0019] BH RAN node 80 is a RAN node that constitutes the wireless backhaul. BH RAN node 80 may be connected to WAB node 150 by an Xn interface. BH RAN node 80 may also be connected to 5GC that constitute the wireless backhaul. In this embodiment, BH RAN node 80 may constitute a wireless communication node.

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

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

[0022] 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).

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

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

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

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

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

[0028] 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).

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

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

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

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

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

[0034] (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 configuration of the BH RAN node 80 will be described. Figure 3 is a diagram of the functional block configuration of the BH RAN node 80.

[0035] As shown in Figure 3, the BH RAN node 80 includes a wireless communication unit 81, a network IF unit 83, a message processing unit 85, and a control unit 87.

[0036] The wireless communication unit 81 transmits a downlink signal (DL signal) in accordance with NR. The wireless communication unit 81 also receives an uplink signal (UL signal) in accordance with NR. Specifically, the wireless communication unit 81 may send and receive wireless signals with the WAB node 150 (WAB-gNB).

[0037] The network interface unit 83 provides interfaces for connecting to wireless access network nodes (RAN nodes) and the core network (5GC). Specifically, the network interface unit 83 may provide an Xn interface and an NG interface. The NG interface may be interpreted as an interface connecting the RAN node and the 5GC.

[0038] The message processing unit 85 performs processing related to the sending and receiving of messages at multiple layers. In particular, in this embodiment, the message processing unit 85 may send and receive various messages at the Radio Resource Control Layer (RRC). Such messages may include, for example, RRC Resume Request and RRC Resume. Other messages, such as RRC Reconfiguration, RRC Reconfiguration Complete and RRC Release, may also be included.

[0039] RRC Resume Request and RRC Resume can be interpreted as messages to resume a suspended RRC connection. RRC Resume Request and RRC Resume can also be used to resume the RRC connection with WAB node 150.

[0040] The message processing unit 85 may send a handover message containing configuration information regarding the network layer transport function at the WAB node 150 (WAB-gNB) to another wireless communication node. In this embodiment, the message processing unit 85 may constitute a transmission unit. Specifically, the message processing unit 85 may send a handover request message containing TNL (Transport Network Layer) configuration information (Xn TNL Configuration Info) to the target BH RAN node (other wireless communication node) to which the WAB-gNB will be handed over.

[0041] Xn TNL Configuration Info is defined, for example, in 3GPP TS 38.423, section 9.2.3.96. 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 to establish the IPSec tunnel.

[0042] Further, the message processing unit 85 may receive a message of the radio resource control layer including Xn TNL Configuration Info (configuration information) from a mobile terminal function (MT) that constitutes a wireless backhaul. In the present embodiment, the message processing unit 85 may constitute a receiving unit. Specifically, the message processing unit 85 may receive an RRC Reconfiguration Complete message including Xn TNL Configuration Info from the WAB-MT. Note that other RRC messages may be used instead of the RRC Reconfiguration Complete.

[0043] The message processing unit 85 may transmit a message of the radio resource control layer including configuration information regarding the transport function of the network layer in other radio communication nodes to the WAB-MT. Specifically, the message processing unit 85 may transmit an RRC Reconfiguration including Xn TNL Configuration Info to the WAB-MT.

[0044] Thus, the message processing unit 85 may transmit Xn TNL Configuration Info (configuration information) to other radio communication nodes such as a target BH RAN node at the time of re-establishment or resumption in the RRC.

[0045] The control unit 87 controls each functional block that constitutes the BH RAN node 80. In particular, in the present embodiment, the control unit 87 may control at least one of the connection in the radio resource control layer with the WAB node 150 (WAB-gNB) and the handover to other radio communication nodes of the WAB node 150.

[0046] Specifically, the control unit 87 may control the transmission and reception of various messages in the RRC via the message processing unit 85, and may execute a connection in the RRC with the WAB-gNB and the like. Further, the control unit 87 may control a handover (which may be referred to as a transition, cell selection, cell reselection, etc.) between the BH RAN nodes of the WAB node 150.

[0047] (3) Operation of the wireless communication system Next, the operation of the wireless communication system 10 will be described. Specifically, the operation regarding handover between the BH RAN nodes of the WAB node 150 (WAB-gNB) will be described.

[0048] As shown in FIG. 2, an Xn interface can be set between the WAB-gNB and the BH RAN node. Since the WAB node 150 may move, it may execute switching of the connection destination wireless communication node such as handover between the BH RAN nodes.

[0049] FIG. 4 shows an example of reconnection between the WAB node and the BH RAN node. FIG. 5 shows an example of RRC connection resume between the WAB node and the BH RAN node. Specifically, FIG. 4 shows an example in which the WAB node reconnects to a neighboring BH RAN node when the WAB-gNB fails in handover or a radio link failure (RLF) occurs. FIG. 5 shows an example in which the WAB node resumes the RRC connection to the neighboring BH RAN node when the WAB-gNB and the neighboring BH RAN node are in the RRC INACTIVE state.

[0050] The handover destination BH RAN node (other wireless communication node) needs to recognize the Xn TNL Configuration Info in order to set the Xn interface with the WAB-gNB. This is because resource coordination is required on the Xn interface to avoid interference when both the radio resources used for communication between the WAB-MT and the BH RAN node and the radio resources used for communication between the UE and the WAB-gNB utilize the same frequency band.

[0051] Also, when a handover fails or an RLF occurs, the WAB node may reconnect to a neighboring BH RAN node. Even when the WAB-gNB and the neighboring BH RAN node are in the RRC INACTIVE state, the WAB node may also resume the RRC connection to the neighboring BH RAN node.

[0052] Xn TNL Configuration Info is configured by the OAM system that supports operation, management, and maintenance. However, considering that WAB nodes may move, the configuration of Xn TNL Configuration Info by OAM has significant latency, and a configuration method with less latency is required. The following describes an example of operation that can solve this problem.

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

[0054] Figure 6 shows an example of a handover sequence between a WAB node and a BH RAN node. As shown in Figure 6, the Source BH RAN node is aware of the Xn TNL Configuration Info (hereinafter abbreviated as TNL Configuration Info), global RAN node ID, TAI (Tracking Area Identity), and NR CGI (Cell Global Identifier) ​​of the WAB-gNB of the subordinate WAB node. Therefore, the Source BH RAN node may notify the Target BH RAN node of the WAB-gNB's TNL configuration info, global RAN node ID, TAI, and NR CGI via a handover request message.

[0055] Alternatively, the source BH RAN node may send the UE type of its subordinate UEs (i.e., an indicator showing WAB-MT) and the ID of the WAB-MT to the target BH RAN node via a handover request message. In the case of CHO, the source BH RAN node may notify multiple target BH RAN nodes of the WAB-gNB's TNL configuration info, global RAN node ID, TAI, and NR CGI via a handover request message. In the case of LTM, the source BH RAN node may notify multiple target BH RAN nodes of the WAB-gNB's TNL configuration info, global RAN node ID, TAI, and NR CGI via an LTM request message.

[0056] Alternatively, the RRC Reconfiguration Complete message sent by WAB-MT to the target BH RAN node may notify the target BH RAN node of the WAB-gNB's TNL configuration info, global RAN node ID, TAI, and NR CGI.

[0057] Furthermore, since the Source BH RAN node is aware of the target BH-gNB's TNL configuration info, global RAN node ID, TAI, and NR CGI, the Source BH RAN node may notify the WAB-MT of the target BH-gNB's TNL configuration info, global RAN node ID, TAI, and NR CGI via an HO command (RRC Reconfiguration). Alternatively, within the WAB node, the WAB-MT may notify the WAB-gNB of the target BH-gNB's TNL configuration info, global RAN node ID, TAI, and NR CGI.

[0058] Furthermore, in addition to the handover, CHO, and LTM mentioned above, during CHO fast failure recovery or LTM fast failure recovery, if a WAB-MT successfully recovers from a fast failure in a cell, the WAB-gNB collaborating with that WAB-MT can quickly establish an Xn interface with the target BH RAN node.

[0059] Figure 7 shows an example sequence of events during a handover failure or radio link failure between a WAB node and a BH RAN node. As shown in Figure 7, in the case of reconnection in RRC, the WAB-MT may send an RRC Reestablishment Request to the new BH RAN node, including the WAB-MT ID and UE type (i.e., an indicator of the WAB-MT).

[0060] The Retrieve UE context request message sent from the new BH RAN node to the old BH RAN node may include the WAB-MT context ID and request the WAB-gNB TNL configuration info. The Retrieve UE context response message sent back from the old BH RAN node to the new BH RAN node may include the WAB-gNB TNL configuration info, global RAN node ID, TAI, NR CGI, UE type (i.e., an indicator showing WAB-MT), and the ID of the said WAB-MT.

[0061] The RRC Reestablishment message sent from the new BH RAN node to the WAB-MT may include the new BH-gNB's TNL configuration info, global RAN node ID, TAI, and NR CGI. Alternatively, the RRC Reestablishment Request or RRC Reestablishment Complete message sent from the WAB-MT to the target BH RAN node may notify the target BH RAN node of the WAB-gNB's TNL configuration info, global RAN node ID, TAI, and NR CGI.

[0062] Figure 8 shows an example sequence of events during a handover failure or radio link failure between a WAB node and a BH RAN node when CHO or LTM is applied. As shown in Figure 8, in CHO or LTM, RRC Reconfiguration and RRC Reconfiguration Complete may also include information such as TNL configuration info. In the case of CHO or LTM, the source BH RAN node may notify the WAB-MT of the TNL configuration info, global RAN node ID, TAI, and NR CGI information of multiple target BH-gNBs via the RRC Reconfiguration message.

[0063] Figure 9 shows an example sequence of events in which a WAB-gNB and a BH RAN node resume RRC connectivity in an RRC INACTIVE state. As shown in Figure 9, in the case of RRC Resume, an RRC Resume Request including the WAB-MT ID and UE type (i.e., an indicator of the WAB-MT) may be sent from the WAB-MT to the new BH RAN node.

[0064] The Retrieve UE context request message sent from the new BH RAN node to the old BH RAN node may include the WAB-MT context ID and request the WAB-gNB TNL configuration info. The Retrieve UE context response message sent back from the old BH RAN node to the new BH RAN node may include the WAB-gNB TNL configuration info, global RAN node ID, TAI, NR CGI, UE type (i.e., an indicator showing WAB-MT), and the ID of the said WAB-MT.

[0065] The RRC Resume message sent from the new BH RAN node to the WAB-MT may include the new BH-gNB's TNL configuration info, global RAN node ID, TAI, and NR CGI. Alternatively, the WAB-MT may notify the target BH RAN node of the WAB-gNB's TNL configuration info, global RAN node ID, TAI, and NR CGI through an RRC Resume Request message or RRC Resume Complete message sent to the target BH RAN node.

[0066] As shown in the example above, since the Xn TNL Configuration Info can be included in the handover or RRC message, it is possible to provide the Xn TNL Configuration Info to the BH RAN node more quickly and reliably compared to obtaining the Xn TNL Configuration Info from the OAM side. This makes it possible to quickly configure the Xn interface between the WAB-gNB and the target BH-gNB (BH RAN node).

[0067] (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.

[0068] 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).

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

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

[0071] The block diagram (Figure 3) used in the description of the above-mentioned embodiments shows 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 be realized by combining the above one device or the above multiple devices with software.

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

[0073] 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 10 shows an example of the hardware configuration of the device. As shown in Figure 10, 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.

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

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

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

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

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

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

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

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

[0082] 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).

[0083] 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).

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

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

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

[0087] 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).

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

[0089] 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).

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

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

[0092] 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).

[0093] 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).

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

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

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

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

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

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

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

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

[0102] 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)).

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

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

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

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

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

[0108] 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0127] 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".

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

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

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

[0131] 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."

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

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

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

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

[0136] 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."

[0137] 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."

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

[0139] 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).

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

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

[0142] 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.).

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

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

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

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

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

[0148] (Note) The above disclosure may be expressed as follows: The first feature is a wireless communication node comprising: a wireless base station providing wireless backhaul; a control unit controlling at least one of the connection in the wireless resource control layer and the handover of the wireless base station to other wireless communication nodes; and a transmission unit transmitting a handover message to the other wireless communication node, which includes configuration information relating to the network layer transport function of the wireless base station.

[0149] The second feature is that, in the first feature, the system may include a receiving unit that receives messages from the wireless resource control layer, including the configuration information, from the mobile termination function that constitutes the wireless backhaul.

[0150] A third feature is that, in the first or second feature, the transmitting unit may transmit a message from the radio resource control layer, which includes configuration information relating to the transport function of the network layer in the other wireless communication node, to the mobile termination function constituting the wireless backhaul.

[0151] A fourth feature is that, in the first to third features, the transmitting unit may transmit the setting information to the other wireless communication node during re-establishment or restart in the wireless resource control layer.

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

[0153] 10 Wireless communication system 20 NG-RAN 80 BH RAN node 81 Wireless communication unit 83 Network IF unit 85 Message processing unit 87 Control unit 100 gNB 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 Pneumatic 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 wireless communication node comprising: a wireless base station providing wireless backhaul; a control unit controlling at least one of the connection in the wireless resource control layer and the handover of the wireless base station to other wireless communication nodes; and a transmission unit transmitting a handover message to the other wireless communication node, which includes configuration information relating to the network layer transport function of the wireless base station.

2. The wireless communication node according to claim 1, further comprising a receiving unit that receives messages from the wireless resource control layer, including the configuration information, from the mobile termination function constituting the wireless backhaul.

3. The wireless communication node according to claim 1, wherein the transmitting unit transmits a message from the wireless resource control layer, which includes configuration information relating to the transport function of the network layer in the other wireless communication node, to the mobile termination function constituting the wireless backhaul.

4. The wireless communication node according to claim 1, wherein the transmitting unit transmits the setting information to the other wireless communication node during re-establishment or restart in the wireless resource control layer.

5. A wireless communication method at a wireless communication node, comprising: a wireless base station providing wireless backhaul; controlling at least one of the connection at the wireless resource control layer and the handover of the wireless base station to other wireless communication nodes; and transmitting a handover message to the other wireless communication nodes, including configuration information relating to the network layer transport function at the wireless base station.

Images