Communication device, control device, communication device method, and control device method

Abstract

The purpose of the present invention is to provide a radio unit (RU) device capable of achieving power saving. The RU device according to the present disclosure comprises: a management unit that acquires first information relating to a correspondence between a physical component and a logic component in a fronthaul; and a communication unit that transmits the first information to a control device that controls the RU device.

Description

RU device, control device, communication system, method and program

[0001] The present disclosure relates to an RU device, a control device, a communication system, a method, and a program.

[0002] In recent years, radio access networks have been adopted that separate the baseband and radio sections of base stations and connect them via a fronthaul. The O-RAN (Open-Radio Access Network) fronthaul specifications established by the O-RAN Alliance define the fronthaul specifications between the O-RU (Radio Unit), which corresponds to the radio section, and the O-DU (Distributed Unit) and O-CU (Central Unit), which correspond to the baseband section. One of the goals of the O-RAN fronthaul specifications is to facilitate the connection of O-RUs from different vendors to O-DUs, thereby realizing multi-vendor radio access networks.

[0003] In the O-RAN fronthaul, specifications are defined for the C (Control)-Plane, U (User)-Plane, S (Synchronization)-Plane, and M-Plane. Non-Patent Document 1 mainly defines specifications for the M-Plane (Management-Plane) in the O-RAN fronthaul. Below, an overview of the functions related to the M-Plane disclosed in Non-Patent Document 1 will be described.

[0004] M-Plane provides management functions for O-RUs. Specifically, M-Plane specifies that O-DUs, SMOs (Service Management and Orchestration), or NMSs (Network Management Systems) are the network devices that manage O-RUs. M-Plane also specifies NETCONF (Network Configuration Protocol), a protocol commonly used for managing network devices. In NETCONF, the network device that manages the O-RUs corresponds to the NETCONF client, and the O-RUs to be managed correspond to the NETCONF server.

[0005] Here, the M-Plane has a Configuration Management function. Specifically, a NETCONF client such as an O-DU obtains information from the O-RU, such as the device status and the NETCONF functions supported by the O-RU. Furthermore, the NETCONF client sets parameters in the O-RU. NETCONF defines edit-config, which sets parameters, and get-config, which obtains parameter values. By using edit-config, the NETCONF client can change the device (hardware) state of the O-RU that can be configured or changed. For example, the configurable hardware state is the power state. Changing the power state can achieve energy saving in the O-RU. Specifically, the NETCONF client transitions the O-RU to the awake or sleeping state.

[0006] The awake state is a state in which the O-RU operates normally (normal mode) rather than in energy saving mode. On the other hand, the sleeping state is a state in which the O-RU operates in energy saving mode. In the sleeping state, only functions related to the M-Plane are operated, and functions related to the C / U / S-Plane can be stopped to reduce power consumption (see, for example, Section 9.1.3 of Non-Patent Document 1). For example, in the energy saving mode, the operation of some of the multiple antennas that the O-RU has may be stopped.

[0007] Also, Non-Patent Document 1 discloses that a NETCONF client assigns an extended antenna-carrier identifier (eAxC_ID). The eAxC ID is used by a C-Plane or U-Plane application to manage eCPRI (enhanced Common Public Radio Interface) communication between an O-DU and an O-RU in the C-Plane or U-Plane. The eAxC_ID may also be used to identify a data layer transmitted between an O-RU and an O-DU.

[0008] Non-Patent Document 2 discloses the hardware configuration of the O-RU and O-DU. Specifically, the O-RU has multiple DPUs (Digital Processing Units), which are physical components. Each DPU is associated with a logical component for executing processing related to the data layer.

[0009] O-RAN-WG4.MP.0-v10.00, O-RAN Working Group 4 (Open Fronthaul Interfaces WG) Management Plane SpecificationO-RAN.WG.7.OMAC-HAR.0-v03.00, O-RAN White Box Hardware Working Group Outdoor Macrocell Hardware Architecture and Requirements (FR1) Specification

[0010] The DPU performs processing related to the data layer in the associated logical component. Here, the O-DU can reduce the number of data layers processed in the O-RU to save power consumption of the O-RU. However, even if the O-DU reduces the number of data layers, if even one physical component in the O-RU that processes multiple data layers continues to operate to perform processing related to the data layer, the effect of saving power consumption of the O-RU is small. In other words, even if the total number of data layers processed by the O-RU is reduced, if the number of operating physical components cannot be reduced, the effect of saving power consumption of the O-RU is small.

[0011] In view of the above-mentioned problems, an object of the present disclosure is to provide an RU device, a control device, and a method that can achieve power saving for the RU device.

[0012] A RU (Radio Unit) device according to a first aspect of the present disclosure includes means for acquiring first information regarding a correspondence between a physical component and a logical component in a fronthaul, and means for transmitting the first information to a control device that controls the RU device.

[0013] A control device according to a second aspect of the present disclosure includes means for receiving first information from a Radio Unit (RU) device regarding a correspondence between physical components in the RU device and logical components in a fronthaul, and means for performing power saving control of the RU device using the first information.

[0014] A communication system according to a third aspect of the present disclosure is a communication system comprising an RU (Radio Unit) device and a control device that controls the RU device, wherein the RU device has means for acquiring first information regarding the correspondence between physical components and logical components in a fronthaul, and means for transmitting the first information to the control device that controls the RU device, and the control device has means for receiving from the RU device the first information regarding the correspondence between physical components in the RU (Radio Unit) device and logical components in a fronthaul, and means for performing power saving control of the RU device using the first information.

[0015] A method for an RU device according to a fourth aspect of the present disclosure includes obtaining first information regarding a correspondence between a physical component in the RU device and a logical component in the fronthaul, and transmitting the first information to a control device that controls the RU device.

[0016] A control device method according to a fifth aspect of the present disclosure receives first information from a Radio Unit (RU) device regarding a correspondence between physical components in the RU device and logical components in a fronthaul, and uses the first information to perform power saving control of the RU device.

[0017] A program according to a sixth aspect of the present disclosure causes a computer to acquire first information regarding the correspondence between physical components in an RU device and logical components in a fronthaul, and transmit the first information to a control device that controls the RU device.

[0018] The present disclosure can provide an RU device, a control device, a communication method, and a control method that can achieve power saving of the RU device.

[0019] FIG. 1 is a configuration diagram of an RU device according to the present disclosure. FIG. 2 is a diagram showing the flow of communication processing executed in an RU device according to the present disclosure. FIG. 3 is a configuration diagram of a control device according to the present disclosure. FIG. 4 is a diagram showing the flow of control processing executed in a control device according to the present disclosure. FIG. 5 is a configuration diagram of a communication system according to the present disclosure. FIG. 6 is a configuration diagram of hardware of an O-RU according to the present disclosure. FIG. 7 is a diagram showing the flow of processing related to get-config according to the present disclosure. FIG. 8 is a diagram showing a data model generated by an O-DU according to the present disclosure. FIG. 9 is a diagram showing the flow of processing related to edit-config according to the present disclosure. FIG. 10 is a configuration diagram of an RU device and a control device according to the present disclosure.

[0020] (Embodiment 1) An example of the configuration of an RU device 10 will be described with reference to Figure 1. The RU device 10 may be software or a module in which processing is performed by a processor executing a program stored in a memory. The RU device 10 may be, for example, an O-RU node (hereinafter referred to as O-RU) defined by the O-RAN alliance. The node may correspond to an entity (device) or a function.

[0021] The RU device 10 has a management unit 11 and a communication unit 12. The management unit 11 and the communication unit 12 may be software or modules that are executed by a processor executing a program stored in a memory, or may be hardware such as a circuit or a chip.

[0022] The RU apparatus 10 operates according to several operating modes. For example, the RU apparatus 10 operates in a power saving mode or a normal mode. The RU apparatus 10 has multiple antenna elements. For example, in the normal mode, all antennas of the RU apparatus 10 may operate, and in the power saving mode, at least one of the multiple antennas of the RU apparatus 10 may be stopped. Alternatively, among all the antenna elements of the RU apparatus 10, some may operate in the normal mode and some may operate in the power saving mode. The multiple antenna elements may be arranged in an array. In other words, the multiple antenna elements may constitute at least one antenna array.

[0023] Furthermore, the RU device 10 may reduce the number of operating physical components in the power saving mode. The physical components may be, for example, digital processing units (DPUs) or radio frequency (RF) processing units (RPUs). For example, the RU device 10 may stop operation of one or more of the multiple DPUs in the power saving mode. That is, each DPU may operate independently. Operating independently may mean that each DPU does not depend on the processing operation of other DPUs. Therefore, even if the operation of some DPUs is stopped, the other DPUs can still operate. Furthermore, the DPUs may be configured using field programmable gate arrays (FPGAs) or application specific integrated circuits (ASICs).

[0024] The RU device 10 has a wireless communication interface and, for example, combines Massive Multiple Input Multiple Output (MIMO) and digital beamforming technology to support wide bandwidths and enable more efficient communications. Massive MIMO, for example, arranges multiple antenna elements at equal intervals on a plane (antenna array) and electrically controls each antenna element to direct different beams to multiple users. As a result, multiple users can connect to the O-RU simultaneously.

[0025] An antenna array is configured with several antenna elements associated to form a desired radiation pattern at the RU unit 10. By configuring multiple antenna arrays at the RU unit 10, various radiation patterns can be realized for the beams emitted from the RU unit 10.

[0026] The management unit 11 manages the physical components by associating them with at least one logical component that identifies a data layer. A data layer may be referred to as, for example, a data stream. A data layer may be data transmitted with the same directivity in MIMO transmission. The data layers are logically distinguished using an extended antenna-carrier identifier (eAxC ID). For example, multiple data layers are transmitted within a common physical path used between the RU device 10 and the DU device, and each data layer is distinguished by being assigned an eAxC ID.

[0027] A logical component may be an endpoint, which is a unit for performing processing or calculations on a data stream identified by an eAxC ID. The eAxC ID is associated with an endpoint, and the endpoint is further associated with a physical component, thereby determining the data stream that the physical component processes. Associating an endpoint with an eAxC ID may mean assigning an eAxC ID to the endpoint.

[0028] Here, the management unit 11 acquires information (hereinafter, sometimes referred to as "first information") regarding the correspondence between multiple physical components (e.g., DPUs) in the RU device 10 and multiple logical components (e.g., endpoints) in the fronthaul. The management unit 11 may be used as a means for acquiring the first information. Here, the term "acquire" may include the meanings of "generate," "be input," "memorize," "hold," etc.

[0029] More specifically, the first information is information based on such a correspondence relationship. More specifically, the first information is information indicating such a correspondence relationship. That is, the first information includes, for example, information indicating a logical component and information indicating a physical component with which the logical component is associated. In the following, in the first embodiment, an example in which this information is included in the first information will be mainly described.

[0030] As will be described later, the first information is transmitted to the control device 20 and used for control of the power saving mode (i.e., power saving control) by the control device 20. Therefore, the first information can be said to be information related to the power saving of the RU device 10. More specifically, the first information can be said to be information for such power saving.

[0031] The communication unit 12 transmits the acquired first information to a control device that controls the RU device 10. The communication unit 12 may be used as a means for transmitting the first information to the control device. The control device may be referred to as a management device. The control device that controls the RU device 10 may be referred to as an RU controller. The control device may be, for example, a Distributed Unit (DU) device or a Service Management and Orchestration (SMO) node (hereinafter referred to as SMO). However, the control device that controls the RU device 10 is not limited to a DU device or an SMO. For example, the control device may be any node that can communicate with the RU device 10 and functions as a NETCONF client.

[0032] As described above, the first information includes information indicating a logical component and information indicating a physical component associated with the logical component. The information indicating a logical component may be, for example, information identifying a data layer. Specifically, the information identifying a data layer may be an endpoint. The information indicating a physical component may be, for example, identification information of the physical component. The communication unit 12 may transmit information indicating multiple physical components. In other words, the communication unit 12 may notify the control device of the logical component processed in each physical component.

[0033] Next, the flow of communication processing executed in the RU device 10 will be described with reference to Figure 2. First, the management unit 11 manages physical components by associating them with at least one logical component that identifies a data layer (S11). At this time, the management unit 11 acquires first information. Next, the communication unit 12 transmits the acquired first information to the control device that controls the RU device 10. The transmitted first information includes information indicating the logical component and information indicating the physical component with which the logical component is associated.

[0034] Next, a configuration example of the control device 20 will be described with reference to Fig. 3. The control device 20 may be software or a module in which processing is performed by a processor executing a program stored in a memory. The control device 20 may be, for example, a DU device, and more specifically, an O-DU node (hereinafter referred to as O-DU) defined in the O-RAN Alliance. Alternatively, the control device 20 may be an SMO node. The node may correspond to an entity (device) or a function.

[0035] The control device 20 has a communication unit 21 and a control unit 22. The communication unit 21 and the control unit 22 may be software or modules that perform processing when a processor executes a program stored in a memory, or the communication unit 21 and the control unit 22 may be hardware such as a circuit or a chip.

[0036] The communication unit 21 receives first information transmitted by the RU device 10. The communication unit 21 may be used as a means for receiving the first information. The received first information includes information indicating a logical component and information indicating a physical component with which the logical component is associated. A physical component may be associated with multiple logical components or may be associated with only one logical component.

[0037] The control unit 22 performs power saving control of the RU device 10 using the received first information. The control unit 22 may be used as a means for performing power saving control of the RU device 10. Here, power saving control will be specifically described. The control unit 22 can identify data layers processed in physical components by using information indicating logical components included in the first information and information indicating physical components included in the first information. In the power saving control of the RU device 10, the control unit 22 may, for example, instruct the RU device 10 to stop using some data layers. That is, the control unit 22 may instruct the RU device 10 to stop using logical components to be stopped. At this time, the control unit 22 may instruct the RU device 10 to stop using all logical components associated with the same physical component. This makes it possible for the RU device 10 to stop using physical components for which use of all logical components has been stopped. As a result, power saving in the RU device 10 can be achieved.

[0038] Next, the flow of control processing in the control device 20 will be described using Figure 4. First, the communication unit 21 receives first information transmitted by the RU device 10 (S21). The received first information includes information indicating a logical component and information indicating a physical component associated with the logical component. Next, the control unit 22 uses this information to perform power saving control of the RU device (S22).

[0039] As described above, the RU device 10 transmits first information (including information indicating a logical component and information indicating a physical component associated with the logical component) to the control device 20. The control device 20 can identify multiple logical components associated with the same physical component from the received information. This allows the control device 20 to select a logical component to be stopped so that the physical component can be stopped. As a result, power-saving operation in the RU device 10 can be achieved.

[0040] (Embodiment 2) Next, an example of the configuration of a communication system will be described with reference to Fig. 5. The communication system of Fig. 5 illustrates the M-Plane architecture model defined by the O-RAN Alliance. The communication system of Fig. 5 includes an O-RU 30, an O-DU 40, and an SMO 50. The O-RU 30 corresponds to the RU device 10 of Fig. 1. The O-DU 40 corresponds to the control device 20 of Fig. 3. In addition, the communication system may include an O-CU node and a Near-RT RIC (near real-time RAN intelligent controller) node (not shown). Furthermore, the SMO 50 may include a Non-RT RIC (non real-time RAN intelligent controller) node (not shown). The O-RU may be simply referred to as an RU. The O-DU may be simply referred to as a DU. The O-CU may be simply referred to as a CU.

[0041] Furthermore, the O-RU 30 and the O-DU 40 may perform communications related to the C-Plane and the U-Plane. A VLAN (Virtual Local Area Network) different from the VLAN assigned to the M-Plane may be assigned to the C-Plane and the U-Plane. Assigning a VLAN may mean assigning a VLAN ID. The same VLAN may be assigned to the C-Plane and the U-Plane, or different VLANs may be assigned to them.

[0042] The O-RU 30 is a logical node that performs lower-level functions of the physical layer (PHY-Low) and RF (Radio Frequency) processing. Alternatively, the O-RU 30 may be a physical device that incorporates the O-RU, which is a logical node. The lower-level functions of the physical layer may be, for example, Fast Fourier Transform (FFT) / Inverse FFT (IFFT) processing, Bea Forming (BF) processing, etc.

[0043] The O-DU 40 is a logical node that performs functions in the Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer, as well as functions higher than the physical layer. Alternatively, the O-DU 40 may be a physical device that incorporates the O-DU, which is a logical node. The functions higher than the physical layer may include, for example, encoding and modulation processing, and decoding and demodulation processing. The functions in the PDCP layer may be performed in a logical node called a Central Unit (CU) (not shown).

[0044] The SMO 50 performs maintenance and orchestration (control) of the RAN (Radio Access Network) and the RIC (RAN Intelligent Controller), which is a platform that realizes optimization of radio resource management and automation of operations. While FIG. 5 illustrates a configuration in which the O-RU 30 and the O-DU 40 are connected and the O-DU 40 and the SMO 50 are connected, the O-RU 30 and the SMO 50 may be connected as indicated by dotted lines. Also, while FIG. 5 illustrates a one-to-one configuration in which the O-RU 30, the O-DU 40, and the SMO 50 are connected, the O-RU 30 may be managed by multiple O-DUs 40. Furthermore, the O-RU 30 may be managed by multiple SMOs 50. The SMO 50 may also be replaced with an NMS.

[0045] Next, the hardware configuration of the O-RU 30 will be described using Figure 6. The O-RU 30 has an FPU (Fronthaul Processing Unit) 31, a DPU (Digital Processing Unit) 32, and an RPU (Radio Frequency Processing Unit) 35. The FPU 31 is connected to multiple DPUs 32. Furthermore, each DPU 32 is connected to multiple RPUs 35.

[0046] The FPU 31 receives compressed or decompressed eCPRI (Enhanced Common Public Radio Interface) packets from the O-DU 40 and performs optical to electrical conversion. The eCPRI packets may be packets transmitted via User Datagram Protocol (UDP) / IP, for example. The eCPRI packets may also be referred to as frames transmitted in a layer above UDP / IP.

[0047] The DPU 32 has a digital front end (DFE) 33 and an analog front end (AFE) 34. The DFE 33 receives eCPRI packets from the FPU 31 via a packet interface. The DFE 33 performs compression or decompression, low-phy processing, digital down-conversion (DDC), digital up-conversion (DUC), crest factor reduction (CFR), and digital pre-distortion (DPD) on the received packets. The low-phy processing may be, for example, fast Fourier transform (FFT), inverse FFT (IFFT), cyclic prefix (CP) addition, CP removal, physical random access channel (PRACH) filtering, etc.

[0048] The AFE 34 performs an analog-to-digital converter (ADC) or a digital-to-analog converter (DAC). The signal that has undergone ADC or DAC processing in the AFE 34 is output to the RPU 35.

[0049] The DPU 32, the AFE 34, and the RPU 35 may each be an FPGA- or ASIC-based module, and may be realized using a single SoC (System on a Chip) or multiple ICs (Integrated Circuits).

[0050] In the RPU 35, signal processing is performed using a mixer, a PA (Power Amplifier), an LNS (Low Noise Amplifier), etc. After the signal processing is performed, the signal is transmitted via an antenna element.

[0051] Next, the processing flow for get-config, which is included in NETCONF operations executed in the Configuration Management function, will be described using FIG. 7 . In FIG. 7 , the O-RU 30 operates as a NETCONF Server, and the O-DU 40 operates as a NETCONF Client. First, the O-DU 40 sends a request message to the O-RU 30 (S21). For example, an RPC (remote procedure call) get may be set in the request message. Next, the O-RU 30 sends a response message to the request message to the O-DU 30 (S22). For example, an RPC-reply may be set in the response message. The response message with an RPC-reply set contains, as data, parameters held by the O-RU 30 and the status of the O-RU 30. In other words, the O-DU 40 retrieves, from the O-RU 20, the parameters held by the O-RU 30, the status of the O-RU 30, and so on, by executing the get procedure.

[0052] The parameters held by the O-RU 30 may be represented, for example, in the form of a data model (YANG data model) described using YANG. Furthermore, a YANG data model indicating parameters or states of the O-RU 30 that can be changed by the O-DU 40 may be defined as a YANG module. Specifically, a YANG data model indicating parameters or states used in the M-Plane may be defined as a reusable YANG module.

[0053] For example, the O-DU 40 fetches, receives, or acquires a list of tx-arrays and rx-arrays in o-ran-uplane-conf.yang from the O-RU 30, and determines, identifies, or extracts the tx-array elements and rx-array elements. tx-arrays indicate the entire antenna array used for transmission, and rx-arrays indicate the entire antenna array used for reception. o-ran-uplane-conf.yang indicates a YANG module specified by the O-RAN Alliance. The tx-array elements and rx-array elements may be antenna arrays configured in the O-RU 30. The tx-array elements are antenna arrays related to transmission in the O-RU 30, and the rx-array elements are antenna arrays related to reception in the O-RU 30.

[0054] Furthermore, the O-DU 40 fetches, receives, or acquires a list of static-low-level-tx-endpoints and static-low-level-rx-endpoints in o-ran-uplane-conf.yang from the O-RU 30. The O-DU 40 determines, identifies, or extracts static-low-level-tx-endpoint elements and static-low-level-rx-endpoint elements. The static-low-level-tx-endpoint elements are, for example, information of the fronthaul data processing unit related to transmission, and the static-low-level-rx-endpoint elements are, for example, information of the fronthaul data processing unit related to reception.

[0055] Furthermore, the O-DU 40 fetches, receives, or acquires from the O-RU 30 the saving groups associated with the lists of static-low-level-tx-endpoints and static-low-level-rx-endpoints in o-ran-uplane-conf.yang. In the second embodiment, this information corresponds to the first information. The O-DU 40 determines, identifies, or extracts the saving groups associated with each of the static-low-level-tx-endpoint elements and static-low-level-rx-endpoint elements.

[0056] The saving group is information related to hardware in the O-RU 30 and may be, for example, information identifying the DPU 32. For example, suppose saving group=0 is associated with static-low-level-tx-endpoint elements=0 to 3. 0 to 3 are values ​​used to identify the static-low-level-tx-endpoint elements. In this case, the DPU 32 identified by saving group=0 processes the data layers associated with static-low-level-tx-endpoint elements=0 to 3. Furthermore, if saving group=1 is associated with static-low-level-tx-endpoint elements=4 to 7, the DPU 32 identified by saving group=1 processes the data layers associated with static-low-level-tx-endpoint elements=4 to 7. Alternatively, the saving group may be information identifying a group including multiple DPUs 32. Alternatively, the saving group may be information identifying a group including multiple physical components such as the DPU 32 and the RPU 35. 0 to 7 are values ​​used to identify static-low-level-tx-endpoint elements.

[0057] In this case, the O-DU 40 may hold information expressed as follows based on the information received from the O-RU 30 (i.e., the first information): static-low-level-tx-endpoint[0-3] saving-group=0 static-low-level-tx-endpoint[4-7] saving-group=1

[0058] After determining the tx-array elements and static-low-level-tx-endpoint elements, O-DU 40 examines the relationship between the tx-array elements and the static-low-level-tx-endpoint elements. Furthermore, after determining the rx-array elements and static-low-level-rx-endpoint elements, O-DU 40 analyzes the relationship between the rx-array elements and the static-low-level-rx-endpoint elements.

[0059] As a result of the analysis, for example, O-DU 40 may identify static-low-level-tx-endpoint elements associated with the antenna elements that make up the tx-array element. Furthermore, O-DU 40 may identify static-low-level-rx-endpoint elements associated with the antenna elements that make up the rx-array element.

[0060] Furthermore, O-DU 40 creates or generates a low-level-tx-endpoint element for the static-low-level-tx-endpoint element and a low-level-rx-endpoint element for the static-low-level-rx-endpoint element. The low-level-tx-endpoint element and the low-level-rx-endpoint element may be used, for example, to set desired parameters or states for the static-low-level-tx-endpoint element and the static-low-level-rx-endpoint element.

[0061] Furthermore, the O-DU 30 sets an eAxC (extended Antenna-Carrier) ID to the low-level-tx-endpoint element and the low-level-rx-endpoint. When the O-DU 40 generates multiple low-level-tx-endpoint elements, it sets a different eAxC ID value for each low-level-tx-endpoint element. Similarly, when the O-DU 40 generates multiple low-level-rx-endpoint elements, it sets a different eAxC ID value for each low-level-rx-endpoint element. The eAxC ID is a 16-bit value composed of a DU_Port_ID, an RU_Port_ID, a CC_ID, and a BandSector_ID. When the eAxC ID set in the low-level-tx-endpoint element is used for the C-Plane and the U-Plane, the eAxC ID used for the C-Plane may be the same as or different from the eAxC ID used for the U-Plane. When the eAxC ID set in the low-level-rx-endpoint is used in the C-Plane and the U-Plane, the eAxC ID when used in the C-Plane may be different from or the same as the eAxC ID when used in the U-Plane.

[0062] Furthermore, the O-DU 40 generates a tx-array-carrier and an rx-array-carrier. The tx-array-carrier and the rx-array-carrier have a parameter "active", and the parameter "active" is set to one of the values ​​"ACTIVE", "INACTIVE", or "SLEEP". The O-DU 30 generates a low-level-tx-links element and a low-level-rx-link element to associate the values ​​of the parameter "active" set in the tx-array-carrier and the rx-array-carrier with the low-level-tx-endpoint element and the low-level-rx-endpoint element. That is, the O-DU 40 associates the values ​​of the parameter "active" set in the tx-array-carrier and rx-array-carrier with the low-level-tx-endpoint element and low-level-rx-endpoint element via the low-level-tx-links element and low-level-rx-link element. "Associating" may be rephrased as "applying" or "setting," for example.

[0063] For example, when the parameter "active" is set to "ACTIVE", the antenna elements indicated by the static-low-level-tx-endpoint elements or the static-low-level-rx-endpoint elements may transition to an awake state. When the parameter "active" is set to "SLEEP", the antenna elements indicated by the static-low-level-tx-endpoint elements or the static-low-level-rx-endpoint elements may transition to a sleeping state. When the parameter "active" is set to "INACTIVE", all functions of the antenna elements indicated by the static-low-level-tx-endpoint elements or the static-low-level-rx-endpoint elements may be stopped.

[0064] The O-DU 40 associates the tx-array-carrier, whose parameter "active" is set to "SLEEP", with the low-level-tx-endpoint elements associated with the antenna element to be transitioned to the sleeping state. The O-DU 40 also associates the rx-array-carrier, whose parameter "active" is set to "SLEEP", with the low-level-rx-endpoint elements associated with the antenna element to be transitioned to the sleeping state.

[0065] Here, the data model generated by the O-DU 40 based on the parameters acquired from the O-RU 30 will be described with reference to FIG.

[0066] FIG. 8 shows an example of a data model related to a transmitting antenna array in the O-RU 30. The data model in FIG. 8 illustrates an example in which the transmitting antenna array in the O-RU 30 is configured with two antenna arrays, tx-array #0 and tx-array #1. The data model in FIG. 8 indicates that static-low-level-tx-endpoint #0 to static-low-level-tx-endpoint #i (i is an integer equal to or greater than 1) configure tx-array #0. It also indicates that static-low-level-tx-endpoint #j to static-low-level-tx-endpoint #n (j and n are integers equal to or greater than 1, with n > j = i + 1) configure tx-array #1. The number of antenna elements configuring tx-array #0 may be the same as or different from the number of antenna elements configuring tx-array #1. For example, tx-array #0 and tx-array #1 may be antenna arrays with different polarization planes.

[0067] Furthermore, low-level-tx-endpoint #0, which indicates the setting of static-low-level-tx-endpoint #0, is associated with the value set to the parameter "active" in tx-array-carrier #0 via low-level-tx-link #0. Similarly, for other static-low-level-tx-endpoints, low-level-tx-endpoint #n, which indicates the setting of static-low-level-tx-endpoint #n, is associated with the value set to the parameter "active" in tx-array-carrier #n via low-level-tx-link #n.

[0068] Here, an example of setting the parameter "active" when operating the O-RU 30 in power-saving mode will be described. The O-DU 40 reduces the number of data layer processes in the O-RU 30 and stops the operation of physical components in the O-RU 30, thereby achieving power savings in the O-RU 30. For example, the O-DU 40 may set the parameter "active" to "INACTIVE" for all static-low-level-tx-endpoints associated with saving group=0 so that it can stop the DPU 32. As a result, the DPU 32 identified by saving group=0 no longer has any data layers to process, and the O-RU 30 can stop supplying power to the DPU 32 identified by saving group=0. In this way, when reducing the number of data layer processes in the O-RU 30, the O-DU 40 sets the static-low-level-tx-endpoints associated with the same saving group to INACTIVE, allowing the O-RU 30 to stop the DPU 32. As a result, power savings in the O-RU 30 can be achieved. Furthermore, even when "SLEEP" is set as the parameter "active," the O-RU 30 may perform the same processing or operation as when "INACTIVE" is set.

[0069] The O-RU 30 may also associate at least one antenna element with the configured saving group. When "INACTIVE" is set for an endpoint associated with a specific saving group, the O-RU 30 may stop supplying power to the antenna element associated with that saving group. For example, "INACTIVE" may be set as the parameter "active" for all static-low-level-tx-endpoints associated with saving group=0. Thus, when the DPU 32 identified by saving group=0 is shut down, the O-RU 30 may stop supplying power to the antenna element associated with saving group=0. Stopping the supply of power to the antenna element may be achieved by stopping the supply of power to the RPU 35. This allows the RPU 35 and the antenna element to also be shut down, thereby achieving power saving for the O-RU 30.

[0070] Next, the flow of processing related to edit-config included in NETCONF operations executed in the Configuration Management function will be described using Fig. 9. As shown in Fig. 8, the O-DU 40 updates the configuration information acquired from the O-RU 30 to a data model indicating a static-low-level-tx-endpoint that transitions to power saving mode. The O-DU 40 transmits a request message in which rpc edit-config is set to the O-RU 30 (S31). The request message includes the data model updated in the O-DU 40.

[0071] Next, the O-RU 30 updates the status of the physical components according to the received data model (S32). For example, the O-RU 30 stops processing the data layer related to the static-low-level-tx-endpoint set to "INACTIVE." Furthermore, the O-RU 30 stops the DPU 32 for which there are no longer any data layers to process. Stopping the DPU 32 may involve stopping the supply of power to the DPU 32, or may involve shutting down the DPU 32. The O-RU 30 may also stop other physical components associated with the same saving group as the DPU 32 being stopped.

[0072] Next, the O-RU 30 transmits a response message in which rpc-reply is set to the O-DU 40 (S33).

[0073] As described above, the O-RU 30 according to the second embodiment transmits the first information (including the saving group, which is information about the static-low-level-tx-endpoint and information about the physical component with which the static-low-level-tx-endpoint is associated) to the O-DU 40. When the O-RU 30 is operated in the power saving mode, the O-DU 40 can stop the operation of the physical component in the O-RU 30 by setting all static-low-level-tx-endpoints associated with the same physical component to "INACTIVE." As a result, power saving in the O-RU 30 can be achieved.

[0074] Furthermore, when setting the static-low-level-tx-endpoint to "INACTIVE", the O-DU 40 may not assign an eAxC ID to the static-low-level-tx-endpoint set to "INACTIVE". As a result, the O-DU 40 can reduce the number of eAxC IDs. When setting the static-low-level-tx-endpoint to "SLEEP", the O-DU 40 may perform the same processing or operation as when "INACTIVE" is set.

[0075] The O-DU 40 may set the endpoint to "INACTIVE" by using a C-Plane message to specify an eAxC ID that will not conduct data. Alternatively, the O-DU 40 may stop all physical components associated with a saving group by specifying a saving-group value instead of specifying an eAxC ID. A C-Plane message, for example, is used to specify the saving-group value. The C-Plane message that specifies the saving-group value may use an existing C-Plane message (e.g., a C-Plane message similar to the C-Plane message for specifying the eAxC ID) or a new C-Plane message (e.g., a dedicated C-Plane message for specifying the saving-group value).

[0076] It should be noted that the saving groups are not limited to the specific example described above. For example, the physical components corresponding to each saving group (i.e., the physical components included in each saving group) are not limited to the DPU 32. Each saving group may include other physical components (e.g., an antenna amplifier, i.e., an amplifier included in the RPU 35) instead of or in addition to the DPU 32 (e.g., FPGA). The degree of energy saving achieved by each saving group may differ depending on the type of physical components associated with each saving group.

[0077] For example, suppose that saving-group=0 corresponds to multiple types of physical components (e.g., the DPU 32 and an antenna amplifier), and saving-group=1 corresponds to one type of physical component (e.g., the DPU 32). In this case, avoiding the use of endpoints corresponding to saving-group=0 is likely to achieve greater energy savings than avoiding the use of endpoints corresponding to saving-group=1. Therefore, the O-DU 40 may selectively stop the operation of saving-group=0 or saving-group=1 depending on the level of energy saving required.

[0078] Furthermore, the use of saving groups is not limited to energy saving. For example, failures may be managed for each saving group. That is, when a failure (e.g., a breakdown) occurs in a physical component included in one of the saving groups, the O-DU 40 receives an alarm corresponding to that saving group. In this case, the O-DU 40 may avoid using the endpoint corresponding to that saving group.

[0079] For example, assume that an alarm corresponding to saving-group=1 out of saving-group=0 and saving-group=1 is received. In this case, the O-DU 40 stops the operation of the endpoint corresponding to saving-group=1 and uses the endpoint corresponding to saving-group=0. This not only makes it possible to realize energy saving in the RU device 10, but also makes it possible to respond to failures in physical components in the RU device 10.

[0080] FIG. 10 is a block diagram showing an example configuration of an RU device 10 and a control device 20 (hereinafter referred to as the RU device 10, etc.). Referring to FIG. 10, the RU device 10, etc. includes a network interface 1201, a processor 1202, and a memory 1203. The network interface 1201 is used to communicate with network nodes (e.g., eNB, MME, P-GW, etc.). The network interface 1201 may include, for example, a network interface card (NIC) conforming to the IEEE 802.3 series. Here, eNB stands for evolved Node B, MME stands for Mobility Management Entity, and P-GW stands for Packet Data Network Gateway. IEEE stands for Institute of Electrical and Electronics Engineers.

[0081] The processor 1202 reads and executes software (computer programs) from the memory 1203 to perform the processing of the RU device 11 and the like described using flowcharts in the above-described embodiments. The processor 1202 may be, for example, a microprocessor, an MPU, or a CPU. The processor 1202 may include multiple processors.

[0082] The memory 1203 is configured by a combination of volatile memory and non-volatile memory. The memory 1203 may include storage located remotely from the processor 1202. In this case, the processor 1202 may access the memory 1203 via an I / O (Input / Output) interface (not shown).

[0083] 10, the memory 1203 is used to store software modules. The processor 1202 reads and executes these software modules from the memory 1203, thereby performing the processing of the RU device 10 and the like described in the above-described embodiment.

[0084] As explained using FIG. 10, each of the processors of the RU device 10, etc. executes one or more programs containing a group of instructions for causing a computer to perform the algorithm explained using the drawing.

[0085] The RU device 10 and the control device 20 each have a similar network interface, processor, and memory. In addition, the RU device 10 has an antenna for wireless communication with a UE or another RU device. As described above, the antenna uses an antenna array (array antenna).

[0086] In the above example, the program can be stored and supplied to a computer using various types of non-transitory computer-readable media. Non-transitory computer-readable media include various types of tangible storage media. Examples of non-transitory computer-readable media include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical disks), CD-ROMs (Read Only Memory), CD-Rs, CD-RWs, and semiconductor memories (e.g., mask ROMs, PROMs (Programmable ROMs), EPROMs (Erasable PROMs), flash ROMs, and RAMs (Random Access Memory)). The program may also be supplied to a computer by various types of transitory computer-readable media. Examples of transitory computer-readable media include electrical signals, optical signals, and electromagnetic waves. The transitory computer-readable media can be supplied to a computer via wired communication paths such as electric wires and optical fibers, or via wireless communication paths.

[0087] Although the present disclosure has been described above with reference to the embodiments, the present disclosure is not limited to the above-described embodiments. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present disclosure within the scope of the present disclosure. Furthermore, each embodiment can be combined with other embodiments as appropriate.

[0088] Each drawing is merely an example for describing one or more embodiments. Each drawing may not relate to only one particular embodiment, but may also relate to one or more other embodiments. As will be understood by those skilled in the art, various features or steps described with reference to any one drawing can be combined with features or steps shown in one or more other drawings to create, for example, an embodiment not explicitly shown or described. Not all features or steps shown in any one drawing are necessary to describe an exemplary embodiment, and some features or steps may be omitted. The order of steps described in any drawing may be changed as appropriate.

[0089] Some or all of the above embodiments can be described as, but are not limited to, the following supplementary notes. (Supplementary Note 1) A Radio Unit (RU) device comprising: means for acquiring first information regarding a correspondence between a physical component in the RU device and a logical component in a fronthaul; and means for transmitting the first information to a control device that controls the RU device. (Supplementary Note 2) The RU device according to Supplementary Note 1, wherein the first information includes information indicating the logical component and information indicating the physical component with which the logical component is associated. (Supplementary Note 3) The RU device according to Supplementary Note 1 or 2, wherein the physical component performs calculation processing related to a data layer identified by the logical component. (Supplementary Note 4) The RU device according to any one of Supplements 1 to 3, wherein the RU device has a plurality of the physical components, and each physical component operates independently. (Supplementary Note 5) The RU device according to any one of Supplements 1 to 4, further comprising: means for receiving a message instructing to operate in a power saving mode; and means for stopping operation of a physical component associated with identification information included in the message. (Supplementary Note 6) The RU device according to any one of Supplements 1 to 5, wherein the means for transmitting first information transmits the first information to the control device when a request message requesting acquisition of information is received from the control device. (Supplementary Note 7) The RU device according to any one of Supplements 1 to 6, wherein a data layer in the fronthaul is identified by an eAxC ID (extended antenna-carrier identifier), the eAxC ID is assigned to each endpoint managed by an M-Plane (Management Plane), and the endpoint is managed in association with the physical component.(Supplementary Note 8) A control device comprising: means for receiving, from an RU (Radio Unit) device, first information regarding a correspondence relationship between physical components in the RU device and logical components in a fronthaul, and means for performing power saving control of the RU device using the first information. (Supplementary Note 9) The control device according to Supplementary Note 8, further comprising: means for transmitting, to the RU device, a message including information indicating the logical component to be stopped. (Supplementary Note 10) A communication system comprising an RU (Radio Unit) device and a control device that controls the RU device, wherein the RU device comprises: means for acquiring first information regarding a correspondence relationship between physical components in the RU device and logical components in a fronthaul, and means for transmitting the first information to the control device that controls the RU device, and the control device comprises: means for receiving, from the RU device, first information regarding the correspondence relationship between physical components in the RU device and logical components in a fronthaul, and means for performing power saving control of the RU device using the first information. (Supplementary Note 11) The communication system according to Supplementary Note 10, wherein the first information includes information indicating the logical component and information indicating the physical component with which the logical component is associated. (Supplementary Note 12) A method of an RU (Radio Unit) device, comprising: acquiring first information regarding a correspondence relationship between a physical component in the RU device and a logical component in a fronthaul; and transmitting the first information to a control device that controls the RU device. (Supplementary Note 13) A method of a control device, comprising: receiving, from the RU device, first information regarding a correspondence relationship between a physical component in the RU device and a logical component in a fronthaul; and performing power saving control of the RU device using the first information.(Supplementary Note 14) A program causing a computer to execute the following: acquire first information regarding a correspondence relationship between a physical component in an RU device and a logical component in a fronthaul, and transmit the first information to a control device that controls the RU device. (Supplementary Note 15) A program causing a computer to execute the following: receive first information regarding a correspondence relationship between a physical component in an RU (Radio Unit) device and a logical component in a fronthaul, from the RU device, and perform power saving control of the RU device using the first information.

[0090] Some or all of the elements (e.g., configurations and functions) described in Supplementary Notes 2 to 7 that are dependent on Supplementary Notes 1 may also be dependent on Supplements 8, 10, and 12 to 15 in the same dependency relationship as Supplementary Notes 2 to 7. Some or all of the elements described in any Supplementary Note may be applied to various hardware, software, recording means for recording software, systems, and methods.

[0091] This application claims priority based on Japanese Patent Application No. 2023-019066, filed February 10, 2023, the disclosure of which is incorporated herein in its entirety.

[0092] 10 RU device 11 Management unit 12 Communication unit 20 Control device 21 Communication unit 22 Control unit 30 O-RU 31 FPU 32 DPU 33 DFE 34 AFE 35 RPU 40 O-DU 50 SMO

Claims

1. A communication device, A communication device comprising: a transmitting means for transmitting a first message including first information for identifying a physical component of the communication device associated with each logical component of the communication device to a control device that controls the communication device.

2. A receiving means for receiving a second message from the control device, the second message including the first information indicating a physical component that the communication device will stop; The communication device according to claim 1 , further comprising: means for stopping operation of the physical component indicated by the first information included in the second message.

3. The transmission means The communication device according to claim 1 , wherein when a request message requesting acquisition of information is received from the control device, the communication device transmits the first message including the first information to the control device.

4. A control device for controlling a communication device, a receiving means for receiving from the communication device a first message including first information for identifying a physical component of the communication device associated with each logical component included in the communication device; A control device comprising:

5. A control device as described in claim 4, further comprising means for sending a second message to the communication device including the first information indicating the physical component that the communication device will stop.

6. A control device as described in claim 4 or 5, wherein the receiving means receives the first message including the first information from the communication device when the control device sends a request message requesting the acquisition of information.

7. A method for a communication device, comprising: A method comprising: transmitting a first message to a control device that controls the communication device, the first message including first information for identifying a physical component of the communication device associated with each logical component included in the communication device.

8. receiving from the control device a second message including the first information indicating a physical component to be stopped by the communication device; The method of claim 7 , further comprising stopping operation of the physical component indicated by the first information included in the second message.

9. A method for a control device for controlling a communication device, comprising: A method comprising: receiving a first message from the communication device, the first message including first information for identifying a physical component of the communication device associated with each logical component included in the communication device.

10. The method of claim 9, wherein the communication device sends a second message to the communication device that includes the first information indicating the physical component to be stopped.