Base station and communication method
The base station's DU/RU configuration enables dynamic switching and redundancy on the fronthaul interface, addressing the lack of management and resilience in O-RAN standards, reducing power consumption and ensuring service continuity.
Patent Information
- Application Number
- PCT/JP2025/017573
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-14
- Publication Date
- 2026-11-19
AI Technical Summary
Existing O-RAN standards do not specify functions for managing radio units (RUs) accommodated by distributed units (DUs) on the fronthaul interface, nor do they provide resilience functions for service continuity in case of DU failures or communication interruptions.
A base station with a first and second DU and an RU that includes a receiving unit for connection requests, a transmitting unit for interface connection requests, and a control unit for establishing connections between DUs via the fronthaul interface, enabling dynamic switching and redundancy to manage traffic, power consumption, and resilience.
This solution reduces power consumption during low traffic periods, maintains cell area coverage, and ensures service continuity by minimizing cell downtime and improving availability through dynamic DU/RU switching and redundancy.
Smart Images

Figure JP2025017573_19112026_PF_FP_ABST
Abstract
Description
Base station and communication method
[0001] The present invention relates to a base station and a communication method in a communication system.
[0002] In NR (New Radio, also referred to as "5G"), which is a wireless communication system based on the 3GPP (registered trademark) standard, and systems succeeding NR (e.g., "6G"), technologies that satisfy requirements such as large system capacity, high data transmission rate, low latency, simultaneous connection of a large number of terminals, low cost, and power saving are being studied.
[0003] For NR, a network architecture including 5GC (5G Core Network) corresponding to EPC (Evolved Packet Core), which is the core network in the LTE (Long Term Evolution) network architecture, and NG-RAN (Next Generation - Radio Access Network) corresponding to E-UTRAN (Evolved Universal Terrestrial Radio Access Network), which is the RAN (Radio Access Network) in the LTE network architecture, is under study (for example, see Non-Patent Document 1).
[0004] 3GPP TS 38.300 V18.5.0 (2025-03) O-RAN.WG4.TS.CUS.0-R004-v17.01(2025-01) O-RAN.WG4.TS.MP.0-R004-v17.01(2025-01)
[0005] In O-RAN (Open-Radio Access Network), specifications related to the Front Haul (FH) interface that connects the Distributed Unit (DU) and the Radio Unit (RU) in the next-generation radio access network are defined (for example, see Non-Patent Documents 2-3).
[0006] However, O-RAN does not specify functions for managing RUs accommodated by the DU in accordance with traffic, etc., on the FH interface, nor does it specify resilience functions that enable service continuity in the event of a failure or communication interruption at the DU through redundancy (flexibility).
[0007] The present invention has been made in view of the above points, and aims to provide a function for switching between a distributed unit (DU) and a radio unit (RU) in an FH interface between a distributed unit (DU) and a radio unit (RU) in a wireless communication system.
[0008] According to the disclosed technology, a base station is provided having a first distributed unit, a second distributed unit, and a radio unit, wherein the radio unit includes a receiving unit that receives a first message from a network node requesting a change in the connection destination from the first distributed unit to the second distributed unit, a transmitting unit that transmits a second message to the second distributed unit requesting a connection via a fronthaul interface, and a control unit that establishes a connection via a fronthaul interface with the second distributed unit.
[0009] According to the disclosed technology, a wireless communication system can provide a function for switching between a distributed unit (DU) and a radio unit (RU) in the FH interface between the DU and the RU.
[0010] This figure shows an example configuration of a wireless communication system in an embodiment of the present invention (1). This figure shows an example configuration of a wireless communication system in an embodiment of the present invention (2). This figure shows an example of a logical architecture in O-RAN. This figure shows an example configuration of a 6G network architecture in an embodiment of the present invention. This figure shows an example configuration of DU redundant connection using FH-flex in an embodiment of the present invention. This figure illustrates failover in the event of a DU failure in an embodiment of the present invention. This figure shows an example of a first sequence diagram in an embodiment of the present invention. This figure shows an example of a second sequence diagram in an embodiment of the present invention. This figure shows an example of FH C-plane parameters in an embodiment of the present invention. This figure shows an example of FH M-plane parameters in an embodiment of the present invention. This figure shows an example of O1 interface parameters in an embodiment of the present invention. This figure shows an example of the functional configuration of a base station 10 and a network node 30 in an embodiment of the present invention. This figure shows an example of the functional configuration of a terminal 20 in an embodiment of the present invention. This figure shows an example of the hardware configuration of a base station 10 and a terminal 20 in an embodiment of the present invention.
[0011] Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to those described below.
[0012] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies may be used as appropriate. However, such existing technologies may be, for example, existing LTE or existing NR, but are not limited to existing LTE or NR.
[0013] Furthermore, in the embodiments of the present invention described below, terms such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel), which are used in existing LTE systems, will be used. This is for convenience of description, and similar signals, functions, etc., may be called by other names. Also, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even if a signal is used in NR, it is not necessarily explicitly stated as "NR-".
[0014] Furthermore, in the embodiments of the present invention, the duplex system may be a TDD (Time Division Duplex) system, an FDD (Frequency Division Duplex) system, or any other system (for example, a Flexible Duplex).
[0015] Furthermore, in embodiments of the present invention, "configuring" wireless parameters means that predetermined values are pre-configured, or that wireless parameters notified from the base station 10 or terminal 20 are configured. Also, in the following description, " / " means "and / or" unless otherwise specified, or unless it is clear from the context that it has a different meaning.
[0016] Figure 1 shows an example configuration (1) of a wireless communication system according to an embodiment of the present invention. The wireless communication system according to an embodiment of the present invention includes a base station 10 and a terminal 20, as shown in Figure 1. Figure 1 shows one base station 10 and one terminal 20, but this is an example, and there may be multiple base stations 10 and terminals 20.
[0017] Base station 10 is a communication device that provides one or more cells and communicates wirelessly with terminal 20. The physical resources of the wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain may be defined by the number of subcarriers or resource blocks. Base station 10 transmits synchronization signals and system information to terminal 20. Synchronization signals are, for example, NR-PSS and NR-SSS. System information is transmitted, for example, in NR-PBCH and is also called broadcast information. Synchronization signals and system information may also be called SSB (SS / PBCH block). As shown in Figure 1, base station 10 transmits control signals or data to terminal 20 via DL (Downlink) and receives control signals or data from terminal 20 via UL (Uplink). Both base station 10 and terminal 20 are capable of transmitting and receiving signals using beamforming. Furthermore, both the base station 10 and the terminal 20 can apply MIMO (Multiple Input Multiple Output) communication to DL or UL. Also, both the base station 10 and the terminal 20 may communicate via Carrier Aggregation (CA) through secondary cells (SCell) and primary cells (PCell). Additionally, the terminal 20 may communicate via Dual Connectivity (DC) through the primary cell of base station 10 and the primary secondary cell group cell (PSCell) of another base station 10.
[0018] Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module. As shown in Figure 1, Terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. Terminal 20 also receives various reference signals transmitted from the base station 10 and performs propagation path quality measurement based on the reception results of said reference signals.
[0019] Furthermore, various requirements are being considered for the next generation of 6G. For example, these requirements may include ultra-broadband communication, mission-critical communication, ultra-massive connection, universal coverage, intelligent connection, and ubiquitous sensing.
[0020] Furthermore, these requirements may include ultra-high-speed communication, large-capacity communication, ultra-wide coverage, ultra-low power consumption, cost reduction, ultra-low latency, ultra-high reliability communication, ultra-high connectivity, and sensing.
[0021] To meet these requirements, the new concept aims for extensibility (e.g., making it more effective for future use), ease of operation, customizability (e.g., making it easier to operate), and sustainability (e.g., cost reduction, a more robust configuration, and resilience). Furthermore, guaranteed communication, ensuring a minimum level of performance at all times, is being considered.
[0022] Figure 2 shows an example configuration (2) of a wireless communication system according to an embodiment of the present invention. Figure 2 shows an example configuration of a wireless communication system when DC (Dual connectivity) is performed. As shown in Figure 2, a base station 10A that will be an MN (Master Node) and a base station 10B that will be an SN (Secondary Node) are provided. Base stations 10A and 10B are each connected to the core network. Terminal 20 can communicate with both base station 10A and base station 10B.
[0023] A cell group provided by base station 10A, which is an MN (Mobile Network), is called an MCG (Master Cell Group), and a cell group provided by base station 10B, which is an SN (Mobile Network), is called an SCG (Secondary Cell Group). In a data center, an MCG consists of one PCell and one or more SCells, and an SCG consists of one PSCell (Primary SCG Cell) and one or more SCells.
[0024] Figure 3 shows an example of the logical architecture in O-RAN. As shown in Figure 3, at base station 10, distributed units (O-DUs) and radio units (O-RUs) are connected via an open fronthaul interface (which may also be simply called a fronthaul interface). This interface transmits and receives control signals, user data, and synchronization signals in the Open FH CUS-Plane, and management signals in the Open FH M-Plane. Furthermore, the Service Management and Orchestration (SMO), which manages and integrates services, communicates with the O-RUs via the Open FH M-Plane, with the O-DUs via the O1 interface, and with the O-Cloud via the O2 interface. Furthermore, in SMO, the non-real-time control unit (Non-RT (Real Time) RIC (RAN Intelligent Controller)) communicates with the near-real-time control unit (Near-RT (Real Time) RIC) via the A1 interface. The O-CU control plane (O-CU-CP) and the O-CU user plane (O-CU-UP) communicate with the O-DU via the F1-c and F1-u interfaces, respectively. The Near-RT RIC communicates with the O-DU and O-CU-CP, etc., via the E2 interface.
[0025] O-DU, O-CU, O-RU, SMO, and RIC may be deployed on the same base station, on different base stations, or in different locations other than base stations (nearby, remote, etc.). They may be treated as base station equipment or as network nodes. Furthermore, O-DU and O-CU may be deployed on a virtualization infrastructure and may be denoted as vDU (virtual DU) and vCU (virtual CU), for example.
[0026] (Challenges in conventional FH interfaces) - Reducing unnecessary power consumption Operating all DUs during periods of low traffic load results in unnecessary power consumption. For example, during the day, traffic is high and it is necessary to operate all DUs at full capacity to handle peak processing at the cell level, but traffic often drops sharply at night. However, keeping multiple DUs running at night increases power costs, while it is not possible to shut down all RUs to maintain cell area (coverage). - Ensuring resilience For example, if multiple RUs are centrally connected to a single DU, there is a risk that a wide range of cells will shut down simultaneously in the event of a DU failure. On the other hand, excessively increasing redundancy increases equipment costs and power consumption, so it is necessary to consider the balance between power saving and resilience. - Flexible fronthaul connection switching In the O-RAN FH interface standard, the connection between DUs and RUs is basically fixed, and there are no provisions regarding dynamic switching functions (so-called FH flex). Therefore, it is necessary to provide a DU and RU switching function in FH interfaces (C-Plane, M-plane, etc.) / O1 interfaces.
[0027] (Example) This example describes a function for switching between a distributed unit (DU) and a wireless unit (RU) in the FH interface between the DU and the RU. This function enables power reduction and improved resilience.
[0028] (System Overview) - Dynamic switching of RUs accommodated by a DU The DU / RU supports the function of dynamically switching any RU to a different DU, for example, switching the DU to which an RU is connected from the first DU to the second DU, by extending the C-plane / M-plane messages in the FH interface. Alternatively, the SMO may perform the dynamic switching of RUs using the O1 interface. Here, the SMO configuration may be either hierarchical mode or hybrid mode.
[0029] Furthermore, the DU / RU may conserve power by, for example, migrating the RU to the first DU and turning off the power to the second DU during periods of low traffic, such as at night. If traffic increases during the daytime, the power to the second DU may be turned on again, and the RU may be migrated to the second DU, thereby making full use of the processing capacity of all DUs. ・Resiliency through redundancy When one DU fails, the DU / RU minimizes the impact of cell downtime by migrating the RU from the failed DU to another DU using C-plane messages (including Section Type, Section Extension, etc.) on the FH interface, M-plane messages, and messages on the O1 interface. The RU / DU may also send a notification to the SMO regarding this migration. This reduces the risk of multiple cells going down simultaneously due to the failure of one DU and improves availability. ・Utilization of O-RAN standard interfaces The DU / RU may perform dynamic switching control between RUs and DUs using existing or new Section Type (ST) and Section Extension (SE) in C-plane messages on the FH interface.
[0030] Furthermore, the DU / RU / SMO may perform configuration changes, energy management, and integrated management of fault detection information related to the switching control by using management commands for M-plane messages on the FH interface and / or the O1 interface. • Load balancing and power saving mode The DU / RU may dynamically change the allocation between DUs and RUs to optimally distribute the required processing capacity. Even while accommodating multiple RUs in a single DU, load balancing may be achieved by quickly activating other DUs and re-accommodating RUs when traffic becomes concentrated.
[0031] (Details of the method) Details of the FH-flex technology used in this embodiment will be described below. Basic configuration diagram 4 is a diagram showing an example of the configuration of a 6G network architecture in an embodiment of the present invention. As shown in Figure 4, the wireless communication network in this embodiment consists of a 5G and 6G core network, a plurality of 5G / 6G CUs, and a plurality of 5G / 6G DUs connected to each CU. In addition, each DU has one or more 5G / 6G RUs that control the wireless resources.
[0032] Figure 5 shows an example of a DU redundant connection configuration using FH-flex in an embodiment of the present invention. As shown in Figure 5, an RU simultaneously establishes FH interfaces with multiple DUs. Furthermore, roles are divided among the DUs (primary DU and secondary DU), and the operating DU is switched depending on the failure or load conditions. Load balancing Figure 6 is a diagram illustrating failover in the event of a DU failure in an embodiment of the present invention. As shown in Figure 6, during high load periods such as daytime hours, RU#1 and RU#2 may be connected to different DUs (DU#1 and DU#2), and both DUs may be operated at full capacity to handle peak traffic. Alternatively, the processing capacity of one DU per cell may be utilized to stably handle the traffic demand of each cell.
[0033] On the other hand, during low-load periods such as at night, when traffic demand decreases, RU#2 may be switched from DU#2 to DU#1, and the power to DU#2 may be turned off. This allows for reduced power consumption by limiting the number of operational DUs to one while maintaining the cell area. • File over procedure in case of DU failure The DU / RU may be designed to use FH flex control to transfer RUs connected to the failed DU to a healthy DU if one of the multiple DUs (for example, either DU#1 or DU#2) fails. This minimizes the cell downtime and reduces the impact on users.
[0034] (Explanation using a sequence diagram regarding the power saving procedure) Figure 7 is a diagram showing an example of a first sequence diagram in an embodiment of the present invention. This sequence diagram describes the procedure for saving power by moving the RU connected to DU10A (source) to DU10B (destination) and turning off the power to DU10A. In this sequence diagram, it may be assumed that messages between SMO30 and DU10A / DU10B / DU10C are sent and received via the O1 interface. The processing of each step will be described below.
[0035] S101: SMO30 sends a request message to DU10A requesting information about traffic / load on DU10A.
[0036] S102: DU10A sends a response message to SMO30 for the request message received in S101. The response message includes information about traffic / load on DU10A.
[0037] S103: Based on the traffic / load information received in S102, SMO30 determines that the traffic / load on DU10A is low and decides to move the RUs (Units of Traffic) that DU10A accommodates to DU10B in order to save power.
[0038] S104: SMO30 sends a request message to DU10B requesting confirmation and reservation of resources for connecting an additional RU. The request message may include information about the RU for which the connection is requested.
[0039] S105: DU10B sends a response message to SMO30 for the request message received in S104. The response message may include information indicating, for example, that it is possible to secure resources to add RUs as a result of the confirmation.
[0040] S106: SMO30 sends a request message to DU10B requesting preparation for connection with the RU via the FH interface. The request message may include information about the RU requesting the connection.
[0041] S107: The DU10B transmits a message responding to the request message received in S106. The response message may include, for example, information indicating that the requested connection preparation is completed.
[0042] S108: The SMO30 transmits a request message to the RU10C, requesting a change of the DU to be connected. The request message includes information indicating that the connection destination DU is DU10B.
[0043] S109: The RU10C transmits a request message to the DU10B, requesting a connection via the FH interface. The request message may be a message requesting establishment of a Control Plane (C-Plane) or Management Plane (M-Plane) connection on the FH interface.
[0044] S110: Establishment and synchronization of the FH interface connection are performed between the DU10B and the RU10C.
[0045] S111: The DU10B transmits a response message to the RU10C for the request message received in S109. The response message may include information indicating that the requested connection change is completed.
[0046] S112: The RU10C transmits a response message to the SMO30 for the request message received in S108. The response message may include information indicating that the requested connection change is completed.
[0047] S113: The SMO30 transmits a request message to the DU10A, requesting to release the resource of the RU10C.
[0048] S114: The DU10A transmits a response message to the SMO30 for the request message received in S113. The response message may include information indicating that the requested resource release is completed.
[0049] S115: The SMO30 performs confirmation (Idle Check) that no RU is connected under the DU10A.
[0050] S116: SMO30 sends a request message to DU10A requesting a power off.
[0051] S117: Based on the request message received in S116, DU10A performs a power-off operation on its own device.
[0052] (Explanation of Failover Procedure Using Sequence Diagrams) Figure 8 shows an example of a second sequence diagram in an embodiment of the present invention. In this sequence diagram, when SMO30 detects a failure in DU10A, it changes the destination of the RU from DU10A to DU10B. In this sequence diagram, it may be assumed that messages between SMO30 and DU10A / DU10B / DU10C are sent and received via the O1 interface. The processing of each step will be described below.
[0053] S201: SMO30 detects a failure in DU10A. For example, SMO30 may periodically send a health check message to DU10A and detect whether or not DU10A is faulty based on whether or not it responds.
[0054] S202: SMO30 identifies RU10B as an RU affected by the failure of DU10A (i.e., an RU connected to DU10A).
[0055] S203: SMO30 sends a request message to DU10B requesting confirmation of status and resources. This request message may include, for example, information about a newly connected RU (RU identifier / number, etc.), and may request confirmation that the RU is in a state where it can accept it (traffic / load) and that there are available resources.
[0056] S204: DU10B sends a response message to SMO30 for the request message received in S203. The response message may include information indicating, for example, that it is possible to accept an additional RU as a result of the confirmation.
[0057] S205: SMO30 sends a request message to DU10B requesting it to prepare to accept the RU.
[0058] S206: DU10B sends a response message to SMO30 for the request message received in S205. The response message may include information indicating that the RU is ready for acceptance.
[0059] S207: SMO30 sends a request message to RU10C requesting a change in the connected DU. The request message includes information indicating that the connected DU is DU10B.
[0060] S208: RU10C sends a request message to DU10B requesting a connection via the FH interface. This request message may also request the establishment of a connection between the control plane (C-Plane) or the management plane (M-Plane) on the FH interface.
[0061] S209: The FH interface connection is established and synchronized between DU10B and RU10C.
[0062] S210: DU10B sends a response message to RU10C for the request message received in S208. The response message may include information indicating that the requested connection has been modified.
[0063] S211: RU10C sends a response message to SMO30 for the request message received in S207. The response message may include information indicating that the requested connection change has been completed.
[0064] S212: SMO30 updates the network status information (i.e., updates the status to indicate that DU10A is stopped and RU10C is connected to DU10B).
[0065] S213: SMO30 sends a request message to DU10A requesting that it release the resources of RU10C.
[0066] (Modifications) The following describes modifications of the DU switching control based on traffic / load or fault, as described in the above embodiment. The processes described in the embodiment and modifications may be used in combination.
[0067] (Modification 1) The DU switching control described in the above embodiment may be performed by the DU instead of the SMO, based on information about faults detected by the DU itself. The DU may notify the SMO of the DU switching before and / or after the completion of the switching.
[0068] (Modification 2) When the SMO / DU / RU performs the DU switching control described in the above embodiment, multiple candidate DUs may be registered in advance, and in the event of a failure, the optimal DU selected from among the multiple candidates may be used as the destination DU.
[0069] (Modification 3) When the SMO / DU performs the DU switching control described in the above embodiment, it may minimize DU resources during low load periods such as at night, and in the event of a failure, it may perform a process to start a replacement DU for the failed DU.
[0070] (Modification 4) In the RU switching described in the above embodiment, the DU may be changed while maintaining the cell ID / frequency band. Here, C-plane messages in the FH interface may be added and used as needed. This makes it possible to minimize the configuration change processing on the terminal side (e.g., re-attach / registration).
[0071] (Variation 5) SMO / DU / RU may be configured to activate additional DUs on demand not only during daytime hours, but also in cases where traffic increases sporadically, such as during events or disasters.
[0072] (Modification 6) The SMO may collect statistical data on the resource utilization rate / failure rate of each DU, analyze it using AI / ML, and in preparation for the next predicted congestion time, power on the DU in advance and perform processing to accommodate RUs in the DU.
[0073] (Example of FH C-Plane Parameters) Figure 9 shows an example of FH C-plane parameters in an embodiment of the present invention. In the messages in the above-described embodiments and modifications (for example, the messages described in the sequence diagram, and / or other messages that are transmitted separately in advance / periodically), the DU / RU may assume that the parameters shown in Figure 9 are included in the control plane messages transmitted and received via the FH interface.
[0074] For example, in S109 of Figure 7, RU10C may include the parameter FailoverState=START (fault detected) in the message (FH connection request) sent to DU10B. Also, in S111 of Figure 7, DU10B may include the parameter FailoverState=COMPLETE (switchover complete) in the message (FH connection response) sent to RU10C.
[0075] Furthermore, for example, in Modification 2, the DU may send a message containing a CandidateDUList to the RU in order to notify it of multiple candidate DUs.
[0076] Furthermore, for example, in Modification 4, when switching RUs, a message containing the settings CellContinuity=1 (enable cell ID maintenance) / FreqBankKeep=True (maintain frequency band) in SectionTypeExtension may be sent and received between the DU and the RU.
[0077] (Example of FH M-Plane Parameters) Figure 10 shows an example of FH M-plane parameters in an embodiment of the present invention. In the messages in the above-described embodiments and modifications (for example, the messages described in the sequence diagram, and / or other messages that are sent separately in advance / periodically), the SMO / DU / RU may assume that the parameters shown in Figure 10 are included in the management plane messages that are sent and received via the FH interface. For example, when configuring multiple DUs, the SMO may send a message containing the parameters shown in Figure 10 via the FH M-Plane between the SMO and the DUs.
[0078] (Example of parameters in the O1 interface) Figure 11 shows an example of parameters for the O1 interface in an embodiment of the present invention. In the messages in the above embodiments and modifications (for example, the messages described in the sequence diagram, and / or other messages sent separately in advance / periodically), the SMO / DU / RU may assume that the parameters shown in Figure 11 are included in the messages sent and received via the O1 interface. For example, when the SMO makes a setting for the DU or RU, it may send a message via the O1 interface that includes the parameters shown in Figure 11.
[0079] (Effects) The above-described embodiments and modifications make it possible to reduce power costs by reducing the number of DUs during low-traffic periods such as at night. In addition, since the cell area is maintained before and after switching the RU connection destination, it is also possible to suppress a decrease in the quality perceived by the user.
[0080] Furthermore, by instantly transferring the RU to another DU in the event of a DU failure, the risk of multiple cells failing simultaneously can be reduced. In addition, by localizing the scope of the failure, service continuity can be improved.
[0081] Furthermore, by implementing FH Flex while maintaining compatibility with existing O-RAN specifications using control plane / management plane messages in the FH interface and messages in the O1 interface, future expansion and widespread adoption will be facilitated.
[0082] Furthermore, based on FH Flex, it is possible to achieve power saving and failover while combining it with advanced functions such as load balancing and AI-driven automatic optimization.
[0083] In other words, in a wireless communication system, a function can be provided to switch between a distributed unit (DU) and a radio unit (RU) at the FH interface between the DU and the RU.
[0084] (Device Configuration) Next, an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processing and operations described above will be explained. The base station 10, network node 30, and terminal 20 include functions to implement the above-described embodiment. However, the base station 10, network node 30, and terminal 20 may each be equipped with only some of the functions in the embodiment.
[0085] <Base Station 10 and Network Node 30> Figure 12 shows an example of the functional configuration of a base station 10 and a network node 30 in an embodiment of the present invention. As shown in Figure 12, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 12 is merely an example. The functional classifications and names of the functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. The network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions in the system architecture may be composed of multiple network nodes 30 separated by function.
[0086] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 or other network node 30 and transmitting the signal by wire or wireless. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 or other network node 30 and obtaining information from the received signal, for example, information from a higher layer. A communication unit including the transmitting unit 110 and the receiving unit 120 may be configured.
[0087] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20. The contents of the setting information include, for example, information related to the operation described in the embodiment.
[0088] The control unit 140 performs control related to setting, instructing, and notifying the operations described in the embodiment. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120.
[0089] <Terminal 20> Figure 13 is a diagram showing an example of the functional configuration of terminal 20 in an embodiment of the present invention. As shown in Figure 13, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 13 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as the communication unit.
[0090] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and acquires signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving PSS, SSS, PBCH, DL / UL / SL control signals, etc. transmitted from the base station 10. The setting unit 230 also stores pre-set setting information. The content of the setting information is, for example, information related to the operation described in the embodiment.
[0091] As described in the embodiment, the control unit 240 performs control related to setting, instructing, and notifying the operations described in the embodiment. The signal transmission function unit of the control unit 240 may be included in the transmission unit 210, and the signal reception function unit of the control unit 240 may be included in the reception unit 220.
[0092] (Hardware Configuration) The block diagrams (Figures 12 and 13) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by hardware, software, or a combination thereof. 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, wireless, etc.). A functional block may be realized by combining the above one device or the above multiple devices with software.
[0093] For example, a base station, terminal, network node, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 14 is a diagram showing an example of the hardware configuration of a base station and a terminal according to one embodiment of the present disclosure. The base station 10 and terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.
[0094] In this disclosure, any two terms selected from the set of terms such as circuit, device, unit, module, chip, and means may be used interchangeably. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figures, or it may be configured to omit some of the devices.
[0095] Each function in the base station 10 and terminal 20 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 and control communication by the communication device 1004, or to control the reading, writing, or both of the reading and writing of data in the memory 1002 and storage 1003.
[0096] The processor 1001 controls the entire computer, for example, by running the operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the baseband signal processing unit 104 and call processing unit 105 described above may be implemented by the processor 1001. Although only one processor 1001 is shown in the diagram, there may be multiple processors.
[0097] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from the storage 1003, the communication device 1004, or both 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. For example, the control unit 401 of the terminal 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly. The above-described various processes have been explained as being executed by one processor 1001, but they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via a telecommunications line, or provided to the computer device via the communication device 1004, for example.
[0098] Furthermore, this disclosure also provides a computer program product, which includes a computer program. This computer program product may implement the steps of the method described in the above embodiments when the computer program is executed by a computer (for example, a processor 1001).
[0099] The memory 1002 is a computer-readable recording medium and may be composed of, for example, ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), or at least a combination of these. The memory 1002 may also be called a register, cache, main memory, etc. The memory 1002 can store executable programs (program code), software modules, etc., for implementing a wireless communication method according to one embodiment of the present disclosure.
[0100] The storage 1003 is a computer-readable recording medium and may consist of, for example, an optical disc such as a CD-ROM (Compact Disc 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., card, stick, key drive), a floppy® disk, a magnetic strip, or a combination of at least two of these. The storage 1003 may also be called an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, server, or other suitable medium including memory 1002, storage 1003, or both memory 1002 and storage 1003.
[0101] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via a wired network, a wireless network, or both wired and wireless networks, and is also referred to as a network device, network controller, network card, or communication module, for example. The communication device 1004 may include a high-frequency switch, duplexer, filter, frequency synthesizer, or a combination of at least two of these. For example, the above-mentioned transmit / receive antenna 101, amplifier unit 102, transmit / receive unit 103, or transmission path interface 106 may be implemented by the communication device 1004. The transmit / receive unit 103 may be implemented with physically or logically separated transmitting unit 103a and receiving unit 103b.
[0102] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, or a combination of at least two of these). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, or a combination of at least two of these). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).
[0103] Furthermore, each device, such as the processor 1001 and 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.
[0104] Furthermore, the base station 10 and terminal 20 may be configured with hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), an FPGA (Field Programmable Gate Array), a GPU (Graphics Processing Unit), an NPU (Neural Processing Unit), or a combination of at least two of these, and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.
[0105] O-CU may be interpreted as CU, control device, communication device, aggregation device, central device, management device, etc. Each of these devices may be rephrased as a unit, node, etc. For example, O-CU may be interpreted as a central unit, aggregation node, etc.
[0106] O-DU may be interpreted as DU, control device, communication device, distributed device, high-PHY device, etc. Each of these devices may be rephrased as unit, node, etc. For example, O-DU may be interpreted as distributed unit, distributed node, etc.
[0107] O-RU may be interpreted as RU, radio equipment, RF (Radio Frequency) equipment, low PHY equipment, etc. Each piece of equipment may be rephrased as a unit, node, etc. For example, O-RU may be interpreted as a radio unit, radio node, etc.
[0108] SMO may be interpreted as a control device, communication device, or management device. Each of these devices may be rephrased as a unit, node, etc. For example, SMO may be interpreted as a management unit, management node, etc.
[0109] Non-Real Time RIC may be interpreted as RIC, non-real-time control device, control device, or communication device. Each of these devices may be rephrased as a unit, node, etc. For example, Non-Real Time RIC may be interpreted as a control unit, control node, etc.
[0110] Near-Real Time RIC may be interpreted as RIC, quasi-real-time control device, control device, or communication device. Each of these devices may be rephrased as a unit, node, etc. For example, Non-Real Time RIC may be interpreted as a control unit, control node, etc.
[0111] <Configuration relating to this embodiment> (Note 1) A base station having a first distributed unit, a second distributed unit, and a wireless unit, wherein the wireless unit includes a receiving unit that receives a first message from a network node requesting a change in the connection destination from the first distributed unit to the second distributed unit, a transmitting unit that transmits a second message to the second distributed unit requesting a connection via a fronthaul interface, and a control unit that establishes a connection via a fronthaul interface with the second distributed unit. (Note 2) The base station according to Note 1, wherein the second distributed unit includes a second receiving unit that receives a third message from a network node that has determined a reduction in traffic or load in the first distributed unit requesting confirmation of its own resources, and a second transmitting unit that transmits a fourth message to the network node in response to the third message, wherein the second receiving unit receives a fifth message from the network node requesting preparation for a connection via a fronthaul interface with the wireless unit, and the second transmitting unit transmits a sixth message to the network node in response to the fifth message. (Note 3) The base station according to Note 1, wherein the second distributed unit includes a second receiving unit that receives a seventh message from a network node that has detected a failure in the first distributed unit, requesting confirmation of the status and resources of the device itself, and a second transmitting unit that transmits an eighth message to the network node in response to the seventh message, wherein the second receiving unit receives a ninth message from the network node requesting preparation for acceptance of the wireless unit, and the second transmitting unit transmits a tenth message to the network node in response to the ninth message. (Note 4) The base station according to Note 3, wherein the second receiving unit receives the seventh message which includes information about the wireless unit and confirms whether acceptance of the wireless unit is possible.(Appendix 5) A communication method performed by a base station having a first distributed unit, a second distributed unit, and a radio unit, comprising: receiving a first message from a network node requesting a change in the connection destination from the first distributed unit to the second distributed unit; transmitting a second message to the second distributed unit requesting a connection via a fronthaul interface; and establishing a connection with the second distributed unit via a fronthaul interface.
[0112] In any of the above configurations, a function for switching between a distributed unit (DU) and a radio unit (RU) can be provided in the FH interface between the DU and the radio unit (RU) in the wireless communication system.
[0113] (Supplement to Embodiments) Embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values are merely examples, and any appropriate values may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may be stored in any suitable storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or other appropriate storage medium.
[0114] Each aspect / embodiment described in this disclosure is an LTE (Long Term Evolution), LTE-A (LTE-Advanced), IMT-Advanced (International Mobile Telecommunications-Advanced), 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 5G-A (5G-Advanced), 6G (6th generation mobile communication system), xG (xth generation mobile communication system (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), NX (New radio access), FX (Future generation radio access), O-RAN (Open Radio Access Network), W-CDMA (Wideband Code Division Multiple Access) (registered trademark), GSM (Global System for Mobile communications) (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE (Institute of Electrical and Electronics Technology) Engineers) 802.11, IEEE 802.11x (where x is any string such as b, a, g, n, ac, ax, be, bn, etc., and x=n is also called Wi-Fi 4, x=ac is Wi-Fi 5, x=ax is Wi-Fi 6 or Wi-Fi 6E, x=be is Wi-Fi 7, x=bn is Wi-Fi 8, etc. Note that Wi-Fi is a registered trademark.This may be applied to systems based on technologies such as IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, network virtualization technologies (e.g., NFV (Network Function Virtualization), SFC (Service Function Chaining), SDN (Software Defined Networking)), or LPWA (Low Power Wide Area). Furthermore, each aspect / embodiment described in this disclosure may be applied to systems based on a combination of at least two of these technologies. Of course, "based on" means not only systems that utilize the technology, but also systems that utilize extensions or modifications of the technology.
[0115] In this disclosure, any two terms selected from the set of terms such as "Base Station (BS)", "Radio Base Station", "Fixed Station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "Access Point (AP)", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Radio Unit (RU)", "Remote Unit (RU)", "Control Unit (CU)", "Distributed Unit (DU)", "Remote Radio Head (RRH)", "Node", "Gateway", "Ground Base Station", "Stratospheric Base Station", "Unmanned Aerial Vehicle", "High Altitude Platform Station (HAPS)", "Airborne Platform", "Panel", "Cell", "Radio Access Network (RAN)", and "Network" may be used interchangeably.
[0116] Each cell contained within a base station may be referred to as a macrocell, small cell, femtocell, picocell, serving cell, or supercell, among other terms. In this disclosure, any two terms selected from the set of terms such as “cell,” “sector,” “cell group,” “carrier,” “component carrier,” “cluster,” “bandwidth part (BWP),” and “carrier bandwidth” may be used interchangeably.
[0117] In this disclosure, any two terms selected from the set of terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "Device", "module", and "Terminal" may be used interchangeably.
[0118] The terminal may be called 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, router (e.g., home router, mobile router, etc.), TCU (Telematics Control Unit), or some other appropriate term.
[0119] Each base station and terminal may consist of one or more devices. Devices that constitute at least a part of each base station and terminal may be called transmitting devices, receiving devices, communication devices, etc. Furthermore, the devices constituting at least a part of each base station and terminal may be, but are not limited to, objects themselves such as vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, unmanned aerial vehicles, stratospheric base stations (e.g., High Altitude Platform Stations (HAPS)), artificial satellites (e.g., Low Earth Orbit (LEO) satellites, Middle Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites), drones (registered trademark), multicopters, quadcopters, balloons, and IoT (Internet of Things) devices (e.g., smart meters, sensors), or include, but are not limited to, objects or devices mounted on such objects. Furthermore, the object in question may be a moving object (hereinafter referred to as a "moving object"; this does not exclude the possibility of the moving object being in a stationary state) or a fixedly positioned object (hereinafter referred to as a "non-moving object").
[0120] Furthermore, the term "base station" in this disclosure may be interpreted as "terminal." For example, the various aspects / embodiments of this disclosure may be applied to configurations in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.) or communication over a non-terrestrial network (NTN). In this case, the terminal 20 may have at least some of the functions of the base station 10 described above. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink") or terms corresponding to NTN (for example, feeder link or service link). For example, an uplink channel or a downlink channel may be interpreted as a sidelink channel.
[0121] Furthermore, this disclosure is also applicable when at least some of the equipment constituting the base station and terminal operates outside of the ground (for example, in the atmosphere or in outer space).
[0122] Furthermore, the term "terminal" in this disclosure may be interpreted as "base station." In this case, the base station 10 may be configured to have the same functions as the terminal 20 described above.
[0123] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or at least two combinations thereof. Physical layer signaling may also be called L1 (Layer 1) control information. MAC signaling may be called, for example, a MAC control element (CE) or a MAC PDU (Protocol Data Unit). RRC signaling may also be called an RRC message or an information element (IE) within the RRC message. The RRC message may be a message used for, for example, controlling an RRC connection (e.g., setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, measurement reporting, or notification of terminal capability, or it may be an information element within the message. Furthermore, the notification of information may be explicit or implicit. An explicit notification of information is the notification of the information itself, while an implicit notification of information may be the notification of information other than the information in question, or the fulfillment of certain conditions which constitutes notification of the information in question.Furthermore, notification of information may include not only notification between the same layer of different devices (e.g., between lower layers or upper layers of base station 10 and terminal 20), but also notification between different layers within the same or different devices (e.g., between lower and upper layers within base station 10 or terminal 20). Also, notification of information from one device to another may be carried out via one or more devices. With respect to any information described in this disclosure (e.g., variables, constants, parameters, settings), information indicating / specifying (or relating to) the value of such arbitrary information may be notified from any first device (e.g., terminal / base station) to any second device (e.g., base station / terminal), even if not specifically stated in the embodiments described above.
[0124] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be reordered, provided they are consistent. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.
[0125] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node, or by a part of it (e.g., CU, RU, or DU). It is clear that various operations performed for communication with terminals in a RAN or core network may be performed by at least a part of the base station and other network nodes other than the base station. The other network nodes may be a single node or a combination of multiple nodes. A network node is, for example, a node provided in various core networks such as EPC (Evolved Packet Core) or 5GC (5G Core Network), and provides one or more network functions (NFs).
[0126] Furthermore, in this disclosure, the action of "a terminal receiving information from a base station" is accompanied by the actions of "a base station transmitting the information to the terminal," "a base station generating the information," or both. Similarly, the action of "a terminal transmitting information to a base station" is accompanied by the action of "a base station receiving the information from the terminal." In addition, actions such as "a terminal is configured to..." or "a terminal is configured to..." may include the actions of "a base station transmitting configuration information regarding the terminal's settings" and "the terminal setting a predetermined action based on the configuration information."
[0127] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during execution.
[0128] The above description of the disclosure is illustrative, and the present invention is not limited to the embodiments described herein. The disclosure can be implemented as modified and altered forms without departing from the spirit of the invention. The disclosure and its modifications and altered forms are included within the scope of the present invention and its equivalents.
[0129] Any reference to elements using the designations “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, or that the first element must precede the second element in any way.
[0130] Radio resources can be defined by a combination of units of resources in one or more domains, such as the time domain, frequency domain, spatial domain, code domain, and power domain.
[0131] For example, resources in the time domain may be defined by one or more time units. These one or more time units include, for example, radio frames, subframes, slots, symbols, transmission time intervals (TTI), or at least two combinations thereof, but the names of the time units are not limited to these. Furthermore, these time units may be fixed-length time units that do not depend on numerology, variable-length time units that do depend on numerology, or both. Examples of fixed-length time units include, but are not limited to, subframes consisting of one or more slots, and radio frames containing multiple subframes. Examples of variable-length time units include, but are not limited to, symbols and slots containing a fixed number of symbols. Note that a certain time unit may be divided into shorter time units. Examples of shorter time units include, but are not limited to, mini-slots consisting of fewer symbols than the number of symbols that make up a slot. The time units described above may include, for example, time units used as units for scheduling, link adaptation, etc. Furthermore, any time unit in this disclosure may be interpreted as being interchangeable with other time units.
[0132] Numerology refers to parameters that define the physical layer structure, and may be parameters based on at least one of the following: subcarrier spacing (SCS), symbol length, cyclic prefix length, and sampling time.
[0133] Resources in the frequency domain may be defined, for example, by one or more frequency units. Such one or more frequency units may include, for example, subcarriers, resource blocks (RBs), bandwidth parts (BWPs), carrier bandwidths, or a combination of at least two of these, but the names of frequency units are not limited to these. Furthermore, the number of subcarriers included in a frequency unit may be a fixed number regardless of the neurology, or a variable number that changes depending on the neurology. For example, an RB consists of a predetermined number of consecutive subcarriers in the frequency domain, and the number of subcarriers included in the RB may be the same regardless of the neurology, for example, 12, but is not limited to this. Similarly, a BWP may consist of, for example, one or more consecutive RBs within a carrier bandwidth, but is not limited to this. For terminal 20, one or more BWPs may be set within one carrier, and at least one of the BWPs may be activated. Furthermore, any frequency unit in this disclosure may be interpreted as another frequency unit.
[0134] Furthermore, resources in both the time domain and the frequency domain may be defined, for example, by one or more time / frequency units composed of time units and frequency units. Such time / frequency units are, but are not limited to, resource elements (REs) consisting of one symbol and one subcarrier, resource element groups (REGs) consisting of a predetermined number of REs, and control resource sets (CORESETs) consisting of a predetermined number of symbols and a predetermined number of RBs.
[0135] Furthermore, resources in the spatial domain may be defined, for example, by one or more spatial units. Such spatial units include, but are not limited to, beams, MIMO (Multi Input Multi Output) layers, antenna ports, or at least two combinations thereof.
[0136] Furthermore, resources in the code domain may be defined, for example, by one or more code units. Such code units may be, but are not limited to, cyclic shifts (CS), orthogonal cover codes (OCC), or combinations thereof.
[0137] 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.
[0138] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.
[0139] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device
Claims
1. A base station having a first distributed unit, a second distributed unit, and a radio unit, wherein the radio unit includes a receiving unit that receives a first message from a network node requesting a change in the connection destination from the first distributed unit to the second distributed unit, a transmitting unit that transmits a second message to the second distributed unit requesting a connection via a fronthaul interface, and a control unit that establishes a connection via a fronthaul interface with the second distributed unit.
2. The base station according to claim 1, wherein the second distributed unit includes a second receiving unit that receives a third message from a network node that has determined that traffic or load in the first distributed unit has been reduced, requesting confirmation of the resources of the device itself, and a second transmitting unit that transmits a fourth message to the network node in response to the third message, the second receiving unit receives a fifth message from the network node requesting preparation for connection via a fronthaul interface with the wireless unit, and the second transmitting unit transmits a sixth message to the network node in response to the fifth message.
3. The base station according to claim 1, wherein the second distributed unit includes a second receiving unit that receives a seventh message from a network node that has detected a failure in the first distributed unit, requesting confirmation of the status and resources of the device itself, and a second transmitting unit that transmits an eighth message to the network node in response to the seventh message, the second receiving unit receives a ninth message from the network node requesting preparation for acceptance of the wireless unit, and the second transmitting unit transmits a tenth message to the network node in response to the ninth message.
4. The base station according to claim 3, wherein the second receiving unit receives the seventh message which includes information about the wireless unit and confirms whether the wireless unit is ready to be received.
5. A communication method performed by a base station having a first distributed unit, a second distributed unit, and a wireless unit, comprising: receiving a first message from a network node requesting a change in the connection destination from the first distributed unit to the second distributed unit; transmitting a second message to the second distributed unit requesting a connection via a fronthaul interface; and establishing a connection with the second distributed unit via a fronthaul interface.
