First network device and method

Abstract

The present invention executes flexible control of an energy saving (ES) mode of a radio unit (RU). When certain conditions are satisfied, the RU device autonomously transitions from the normal mode to the ES mode, or requests a control device to shift the RU device from the normal mode to the ES mode.

Description

Technical Field

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

Background Art

[0002] In recent years, a radio access network that separates a baseband unit and a radio unit of a base station and connects the baseband unit and the radio unit via a fronthaul has been used. The O-RAN (Open-Radio Access Network) fronthaul specification defined by the O-RAN Alliance defines the fronthaul specification between an O-RU (O-RAN Radio Unit) corresponding to the radio unit and an O-DU (O-RAN Distributed Unit) corresponding to the baseband unit. One purpose of the O-RAN fronthaul specification is to facilitate the connection between an O-RU of a different vendor from the vendor of the O-DU and to realize multi-vendorization of the radio access network. Note that the O-DU may also be simply called a DU. Also, the O-RU may also be simply called a RU.

[0003] Non-Patent Document 1 specifies the M(Management)-Plane, which is defined for transmitting management data between O-RUs and O-DUs. The M-Plane provides management functions for O-RUs. In the M-Plane, the O-DU or SMO (Service Management and Orchestration) is defined as the device that manages the O-RUs. The O-RUs under management correspond to NETCONF servers, and the device that manages (controls) the O-RUs (RU control device) corresponds to a NETCONF client. The M-Plane supports protocol stacks that transmit signals used in NETCONF (NETwork CONFiguration protocol) using Ethernet / IP / TCP (Transmission Control Protocol) / SSH (Secure Shell), and optionally Ethernet / IP / TCP (Transmission Control Protocol) / TLS (Transport Layer Security) (see, for example, sections 9.1.2 and 9.1.3 of Non-Patent Document 1).

[0004] For example, Non-Patent Document 1 describes how to change the Power State of an O-RU. When the Power State is AWAKE, the O-RU operates normally (not in ES mode (Energy saving mode)), and when the Power State is SLEEPING, the O-RU operates in Energy saving mode. The Power State of an O-RU is changed when the RU control unit sends an RPC (Remote Procedure Call) message to the O-RU indicating an edit-config request. In other words, normally, changes in the Power State of an O-RU are triggered by the RU control unit. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] O-RAN-WG4.MP.0-v09.00,“O-RAN Working Group 4 (Open Fronthaul Interfaces WG) Management Plane Specification” [Overview of the project] [Problems that the invention aims to solve]

[0006] Non-patent document 1 assumes that the DU device or SMO acts as the control entity to set the state of the RU device.

[0007] The inventors have found that flexible control of the ES mode of an RU device can be achieved by having the RU device proactively decide and control its transition to ES mode (for example, by allowing the transition to ES mode to be triggered by the RU device). This point is not sufficiently discussed in Non-Patent Document 1.

[0008] One of the objectives that the embodiments disclosed herein seek to achieve is to provide a control device and RU device that contribute to solving at least one of several problems, including the problems described above. It should be noted that this objective is only one of several objectives that the embodiments disclosed herein seek to achieve. Other objectives or problems and novel features will be revealed in this specification or in the accompanying drawings. [Means for solving the problem]

[0009] In one embodiment, the RU (Radio Unit) device is At least one memory, At least one processor coupled to the at least one memory, Equipped with, The at least one processor autonomously switches the RU device from normal mode to ES (Energy Saving) mode when predetermined conditions are met.

[0010] In other embodiments, the RU (Radio Unit) device is, At least one memory, At least one processor coupled to the at least one memory, Equipped with, The aforementioned at least one processor requests the RU control device to switch the RU device from normal mode to ES (Energy Saving) mode when certain conditions are met.

[0011] In other embodiments, the control device is At least one memory, At least one processor coupled to the at least one memory, Equipped with, The aforementioned at least one processor sends an RPC (Remote Procedure Call) message to the RU (Radio Unit) device that is based on the NETCONF (Network Configuration Protocol) protocol and indicates an edit-config request. The RPC message includes configuration information that allows the RU device to autonomously switch from normal mode to ES (Energy Saving) mode when predetermined conditions are met.

[0012] In other embodiments, the control device is At least one memory, At least one processor coupled to the at least one memory, Equipped with, The aforementioned at least one processor sends an RPC (Remote Procedure Call) message to the RU (Radio Unit) device that is based on the NETCONF (Network Configuration Protocol) protocol and indicates an edit-config request. The RPC message includes configuration information that allows the RU device to request the RU control device to switch the RU device from normal mode to ES (Energy Saving) mode when predetermined conditions are met.

[0013] In other embodiments, the method performed by the RU (Radio Unit) device is: This includes autonomously switching the RU device from normal mode to ES (Energy Saving) mode when predetermined conditions are met.

[0014] In other embodiments, the method performed by the RU (Radio Unit) device is: This includes requesting the RU control device to switch the RU device from normal mode to ES (Energy Saving) mode when certain conditions are met.

[0015] In other embodiments, the control unit is executed by the control unit, This includes sending an RPC (Remote Procedure Call) message to the RU (Radio Unit) device that is based on the NETCONF (Network Configuration Protocol) protocol and indicates configuration editing (edit-config), The RPC message includes configuration information that allows the RU device to autonomously switch from normal mode to ES (Energy Saving) mode when predetermined conditions are met.

[0016] In other embodiments, the control unit is executed by the control unit, This includes sending an RPC (Remote Procedure Call) message to the RU (Radio Unit) device that is based on the NETCONF (Network Configuration Protocol) protocol and indicates configuration editing (edit-config), The RPC message includes setting information that allows the RU device to request the RU control device to shift the RU device from the normal mode to the ES (Energy Saving) mode when a predetermined condition is satisfied.

[0017] In another aspect, the program causes a RU (Radio Unit) device to execute a process including autonomously shifting the RU device from the normal mode to the ES (Energy Saving) mode when a predetermined condition is satisfied.

[0018] In another aspect, the program causes a RU (Radio Unit) device to execute a process including requesting the RU control device to shift the RU device from the normal mode to the ES (Energy Saving) mode when a predetermined condition is satisfied.

[0019] In another aspect, the program causes a control device to execute a process including transmitting an RPC (Remote Procedure Call) message based on the NETCONF (Network Configuration Protocol) protocol and indicating an edit-config to a RU (Radio Unit) device, where the RPC message includes setting information that allows the RU device to autonomously shift the RU device from the normal mode to the ES (Energy Saving) mode when a predetermined condition is satisfied.

[0020] In another aspect, the program causes a control device to execute a process including transmitting an RPC (Remote Procedure Call) message based on the NETCONF (Network Configuration Protocol) protocol and indicating an edit-config to a RU (Radio Unit) device, The RPC message includes configuration information that allows the RU device to request the RU control device to switch the RU device from normal mode to ES (Energy Saving) mode when predetermined conditions are met. [Effects of the Invention]

[0021] This disclosure makes it possible to provide RU devices, control devices, methods, and programs that contribute to solving at least one of several problems, including those described above. [Brief explanation of the drawing]

[0022] [Figure 1] This figure shows an example of the procedure for obtaining the State of a RU. [Figure 2] This diagram shows an example of the procedure for changing the State of a RU. [Figure 3] This is a diagram illustrating the Power State of RU. [Figure 4] This diagram shows the possible transitions and the combinations of the "active" and "state" parameters. [Figure 5] This is a block diagram showing an example of the system. [Figure 6] This figure shows an example of the processing operation of the RU device and control device of the present disclosure. [Figure 7] This figure shows another example of the processing operation of the RU device and control device of the present disclosure. [Figure 8] This figure shows another example of the processing operation of the RU device and control device of the present disclosure. [Figure 9] This figure shows another example of the processing operation of the RU device and control device of the present disclosure. [Figure 10] This is a diagram showing an example of the configuration of a control device. [Figure 11] This figure shows an example of the configuration of a DU device. [Figure 12] This figure shows an example of the configuration of an RU device. [Figure 13]This figure shows an example of the configuration of an SMO (Scaling Modulation) device. [Modes for carrying out the invention]

[0023] The embodiments will be described below with reference to the drawings. In this disclosure, the drawings may be associated with one or more embodiments. Also, each element in the drawings may correspond to one or more embodiments. Furthermore, in the embodiments, the same or equivalent elements are denoted by the same reference numerals, and redundant descriptions are omitted.

[0024] The multiple embodiments described below can be implemented independently or in combination as appropriate. These multiple embodiments have novel features that differ from each other. Therefore, these multiple embodiments contribute to solving different objectives or problems and contribute to producing different effects.

[0025] The following embodiments are primarily described for RU devices and control devices conforming to the O-RAN technical specifications. However, these embodiments may also be applied to other systems that support similar technologies to these RU devices and control devices.

[0026] As used herein, depending on the context, “(if)” may be interpreted as meaning “when,” “at or around the time,” “after,” “upon,” “in response to determining,” “in accordance with a determination,” or “in response to detecting.” These expressions may be interpreted as having the same meaning depending on the context.

[0027] First, the related technologies will be described. Each embodiment is based on these technologies. In other words, these technologies can be incorporated into each embodiment.

[0028] (protocol) C (Control)-Plane is a protocol for transferring control signals. U (User)-Plane is a protocol for transferring user data. C / U-Plane supports a protocol stack that directly transmits signals used in eCPRI or RoE (Radio over Ethernet) over Ethernet, and optionally a protocol stack that transmits signals via UDP (User Datagram Protocol) / IP. S-Plane is a protocol for achieving synchronization between devices. S-Plane supports protocol stacks that transmit signals used in PTP (Precision Time Protocol) and SyncE (Synchronous Ethernet) over Ethernet. M(Management)-Plane is a protocol for handling maintenance and monitoring signals. M-Plane supports protocol stacks that transmit signals used in NETCONF (NETwork CONFiguration protocol) via Ethernet / IP / TCP (Transmission Control Protocol) / SSH (Secure Shell), and optionally via Ethernet / IP / TCP (Transmission Control Protocol) / TLS (Transport Layer Security).

[0029] (Logical architecture) The O-RAN (Open-Radio Access Network) Alliance adopts a configuration that separates the RAN's communication processing functions into three components: RU (Radio Unit), DU (Distributed Unit), and CU (Central Unit). Furthermore, it defines "RIC (RAN Intelligent Controller)," a platform that optimizes wireless resource management and automates operations, and "SMO (Service Management and Orchestration)," a framework for RAN maintenance and orchestration. The RU and DU are connected by an open fronthaul. CUS / M-Plane signals are transmitted through this open fronthaul between the RU and DU. Alternatively, the RU and SMO may be connected by an open fronthaul, and M-Plane signals may be transmitted through this open fronthaul. In this case as well, CUS-Plane signals are transmitted through the open fronthaul between the RU and DU. Furthermore, the DU and SMO are connected via the O1 interface. The CU and SMO are also connected via the O1 interface. The managed RUs correspond to the NETCONF server, and the device that manages (controls) the RUs (RU control device) corresponds to the NETCONF client. The NETCONF client may be installed in the DU or in the SMO.

[0030] (Retrieving the State of the RU) Figure 1 shows an example of the procedure for obtaining the State of an RU. In Figure 1, the RU controller is NETCONF <get>Use the procedure to obtain the state of the RU.

[0031] Specifically, the RU control unit sends an RPC (Remote Procedure Call) message to the RU indicating a get. The RU responds to the RPC message by sending an RPC reply message to the RU control unit. This RPC reply message contains information indicating the RU's state. In other words, the RU control unit, <get>The State of the RU can be retrieved via request.

[0032] (Modifying the State of the RU) The RU controller can change the configurable state of a RU for RUs that support optional hardware-state features defined in the RU's hardware. The RU controller can change the NETCONF without resetting. <edit-config>The configurable State of a RU can be changed using the provided procedure.

[0033] Figure 2 shows an example of the procedure for changing the State of the RU. The RU control unit does not reset NETCONF <edit-config>Use the procedure to change the configurable State of the RU.

[0034] Specifically, the RU control unit sends an RPC message to the RU indicating a configuration edit (edit-config). The RU changes its state based on this RPC message. Then, if the change is successful, <ok>Send an RPC response message indicating this to the RU control unit.

[0035] [power-state] The configurable state of the RU is, for example, power-state. As shown in Figure 3, the RU's Power State can be "AWAKE" or "SLEEPING". Figure 3 is a diagram illustrating the RU's Power State. The RU control device is NETCONF <edit-config>The Power State of a Unit (RU) can be changed using a specific procedure. Specifically, the RU control unit controls the Power State of a Unit by editing the "energy-saving-enabled" parameter of the Unit, which is done by sending an RPC message to the Unit indicating an edit-config request. -AWAKE: This Power State indicates that the RU is operating normally, i.e., not in ES (Energy Saving) mode. -SLEEPING: This Power State indicates that the RU is in ES mode.

[0036] (RU Carrier configuration) The RU control unit is NETCONF <edit-config>The parameters of the RU can be set (updated) using the procedure. For example, the RU control unit performs activation by setting the value of the "active" parameter for the tx-array-carrier(s) element (and / or rx-array-carrier(s) element) to "ACTIVE". The RU control unit also performs deactivation by setting the value of the "active" parameter for the tx-array-carrier(s) element (and / or rx-array-carrier(s) element) to "INACTIVE". The RU control unit also puts the tx-array-carrier(s) element (and / or rx-array-carrier(s) element) to sleep by setting the value of the "active" parameter for the tx-array-carrier(s) element (and / or rx-array-carrier(s) element) to "SLEEP". A tx-array-carrier(s) element (and / or rx-array-carrier(s) element) is in sleep mode when the value of the "active" parameter is "SLEEP" and the value of the "State" parameter is "READY". Figure 4 shows the possible transitions and the combinations of the "active" parameter and the "state" parameter.

[0037] Here, tx-array-carrier(s) is a data node generated by the RU control unit that includes carrier configuration parameters and is associated with the RU's transmit array (tx-array) information. Similarly, rx-array-carrier(s) is a data node generated by the RU control unit that includes carrier configuration parameters and is associated with the RU's receive array (rx-array) information. tx-array-carrier(s) and rx-array-carrier(s) are generated for each carrier and each transmit / receive array, and the carrier's center frequency, bandwidth, transmit power, etc., are set for the RU.

[0038] <Example of system configuration> Next, an example of a system configuration common to multiple embodiments will be described. Figure 5 is a block diagram showing an example of a system. In Figure 5, System 1 includes a DU device 10, an RU device 20, and an SMO device 30.

[0039] The DU device 10 may be a logical node that performs functions in the PDCP (Packet Data Convergence Protocol) layer, the RLC (Radio Link Control) layer, and the MAC (Media Access Control) layer, as well as higher-level functions of the physical layer, or it may be a physical device that houses this logical node. The higher-level functions of the physical layer may include, for example, encoding and modulation processing, as well as decoding and demodulation processing. The functions in the PDCP layer may be performed in a logical node called a CU (Central Unit) (not shown).

[0040] The RU device 20 may be a logical node that performs lower-level functions of the physical layer (PHY-Low) and RF (Radio Frequency) processing, or it may be a physical device that houses this logical node. Lower-level functions of the physical layer may include, for example, FFT (Fast Fourier Transform) / IFFT (Inverse FFT) processing, BF (Beam Forming) processing, etc.

[0041] The SMO device 30 is a platform that optimizes wireless resource management and automates operations, and it performs maintenance and orchestration for the RIC (RAN Intelligent Controller) and RAN (Radio Access Network).

[0042] In Figure 5, the DU device 10 has a control unit (control device) 11. This control unit (control device) 11 corresponds to a NETCONF client. The RU device 20 has a control unit 21. Either the RU device 20 itself or the control unit 21 corresponds to a NETCONF server.

[0043] Furthermore, in Figure 5, the DU device 10 and the SMO device 30 are connected via the O1 interface. In addition, the DU device 10 and the RU device 20 are connected via an open fronthaul. This open fronthaul can transmit signals from the CUS-Plane and the M-Plane.

[0044] The control unit (control device) 11 (NETCONF client) may be located in the SMO device 30 instead of the DU device 10. In this case, the RU device 20 and the SMO device 30 may also be connected by an open fronthaul. In this case, the open fronthaul connecting the DU device 10 and the RU device 20 transmits CUS-Plane signals, while the open fronthaul connecting the RU device 20 and the SMO device 30 transmits M-Plane signals.

[0045] <First Embodiment> The system configuration may be the same as the example shown in Figure 5. Figure 6 shows an example of the processing operation of the RU device and control device of this disclosure.

[0046] The control device 11 (NETCONF client) sends a message indicating acquisition (sometimes referred to as the "first request message" below) to the RU device 20 (step S11). The message indicating acquisition may also be an RPC (Remote Procedure Call) message. The RU device 20 responds to the first message by sending a response message (sometimes referred to as the "first response message" below) to the control device 11 (step S12). The response message may also be an RPC response (rpc-reply) message. In other words, the processing operation of the RU device and control device in the first embodiment shown in Figure 6 is NETCONF <get>This may also be a processing operation of the RU device 20 and the control device 11 in accordance with the procedure. Note that the "first request message" may also be an RPC (Remote Procedure Call) message indicating acquisition (get-config).

[0047] The first request message may include "request information" indicating, for example, that it is requesting the RU device 20 to send a first response message containing "requested information." The request information may also indicate a request for an entire information set containing multiple information elements, or it may indicate a request for each information element. The requested information is "information about the RU device 20," and may be, for example, the capability information of the RU device 20.

[0048] The RU device 20 receives a first request message and generates a first response message containing the requested information based on the request information in this first request message. For example, if the requested information is the Capability information of the RU device 20, the first response message will contain the Capability information. Note that "information concerning the RU device 20" is NETCONF <get>In addition to the procedure, or NETCONF <get>Instead of following the procedure, the control device 11 may, for example, acquire the information from the RU device 20 during the connection establishment process between the RU device 20 and the control device 11 (as part of the establishment procedure).

[0049] Next, a specific example of the "information relating to the RU device 20" in the first embodiment will be described. That is, the first message may include request information relating to any one or any combination (including all) of the information elements described below. The first response message may also include any one or any combination (including all) of the information elements described below, based on the request information. Alternatively, the first response message may include some or all of the content relating to any combination (including all) of the information elements described below, based on the request information.

[0050] (Example of an information element 1) The information element in Example 1 is Capability information indicating that the RU device 20 has the capability to autonomously transition from normal mode to ES (Energy Saving) mode (or whether or not the RU device 20 has such capability). If the Capability of the RU device 20 is valid, the RU device 20 will autonomously transition to ES mode when the "predetermined conditions" for transitioning to ES mode are met. This mode in which the RU device 20 can autonomously transition to ES mode may also be called "Self Saving mode". In other words, Self Saving mode is an ES mode triggered by the RU device 20. To put it another way, in Self Saving mode, the transition from normal mode to ES (Energy Saving) mode is triggered by the RU device 20. For this reason, Self Saving mode may also be called "RU-triggered Saving mode". The "predetermined conditions" and "ES mode" will be explained in detail later.

[0051] (Example of an information element 2) The information element in Example 2 is Capability information that indicates (or indicates whether or not the RU device 20 has the capability to send a message (e.g., a Notification message) to the control device 11 to notify the control device 11 that the RU device 20 has autonomously transitioned from normal mode to ES mode. If the information element in Example 2 indicates that this Capability is valid, the RU device 20 sends the message (e.g., a Notification message) to the control device 11 when it autonomously transitions from normal mode to ES mode. By receiving this message, the control device 11 can understand that the RU device 20 has autonomously transitioned to ES mode.

[0052] Here, we will describe a function or configuration that allows the RU device 20 to stop (or lower its operating level) when in "ES mode".

[0053] (ES mode example 1) In ES mode, the RU device 20 may disable the operation of at least some of the antennas it comprises. Specifically, for example, the RU device 20 may disable the operation of at least one of the multiple antenna arrays (tx-arrays and rx-arrays) it comprises.

[0054] In this case, the RU device 20 may set the corresponding parameters when transitioning from normal mode to ES mode. Specifically, for example, the RU device 20 may set the parameters in the same way as "Parameter Example 1," "Parameter Example 2," or "Parameter Example 3" described in the third embodiment.

[0055] (ES mode example 2) In ES mode, the RU device 20 may shut down the C / U (Control / User) plane, the S (Synchronization) plane, the M (Management) plane, and at least one of the components of the RU device 20.

[0056] The components of the RU device 20 described above may include either a digital device section or an analog device section, or both. The digital device section may be at least one of the following: FPGA (Field Programmable Gate Array), CPLD (Complex Programmable Logic Device), ASIC (Application Specific Integrated Circuit), processor, and network interface of the RU device 20. The analog device section may be a PA (Power Amplifier). Furthermore, for example, if the RU device 20 includes multiple antenna arrays as the analog device section, in ES mode, the RU device 20 may shut down some of the multiple antenna arrays.

[0057] (ES mode example 3) In addition, in ES mode, the RU device 20 may lower its voltage.

[0058] Lowering the voltage of the RU device 20 as described above may involve at least one of the following: "reducing the antenna transmission power of the RU device 20," "stopping the components of the RU device 20," and "stopping the power supply from the RU device 20 to external devices connected to the RU device 20."

[0059] The above action of "reducing the antenna transmission power of the RU device 20" may also mean autonomously reducing the antenna output to the minimum value of the antenna transmission power of the RU device 20. The minimum value of the antenna transmission power of the RU device 20 may be indicated from the RU device 20 to the control device 11 by the "min-power-per-antenna" parameter of the module-capability.yang module.

[0060] The phrase "stopping the components of the RU device 20" above may also mean turning off the switches for the components of the RU device 20.

[0061] The above action of "stopping the power supply from RU device 20 to an external device connected to RU device 20" may refer to an external device connected to the ALD (Antenna Line Device) port of RU device 20. This external device may be an antenna tilt control device that controls the tilt of the antenna of RU device 20.

[0062] Next, I will explain the "specified conditions".

[0063] The "predetermined conditions" may include any one or any combination of the following: (Condition 1) the "overheat determination parameter" of the RU device 20 satisfies the overheat condition; (Condition 2) the number of user equipment (UEs) communicating with the RU device 20 is less than a threshold; or (Condition 3) the transition time to a predetermined ES mode is reached.

[0064] Condition 1 may also be that the temperature of the RU device 20 (e.g., internal temperature) is higher than the overheat detection threshold. When this condition 1 is met, the RU device 20 switches to ES mode, which reduces the power consumption of the RU device 20 and thus reduces the heat generated in the RU device 20. This prevents or eliminates overheating in the RU device 20.

[0065] Regarding (Condition 2), the RU device 20 can determine the number of UEs communicating with the RU device 20 when performing channel information-based beamforming (Channel Info Based BF). The RU device 20 may autonomously switch from ES mode to normal mode when the number of user devices (UEs) communicating with the RU device 20 changes from being below a threshold to being above a threshold.

[0066] As described above, according to the first embodiment, the RU device 20 sends an RPC (Remote Procedure Call) message to the control device 11 in response to an RPC message indicating acquisition (get or get-config). This RPC response message includes information about the RU device 20. This information about the RU device 20 includes capability information indicating that the RU device 20 has the capability to autonomously transition from normal mode to ES mode (or whether or not the RU device 20 has such capability).

[0067] This configuration of the RU device 20 allows the control device 11 (NETCONF client) to flexibly control the "Self Saving mode" of the RU device 20.

[0068] Furthermore, the RU device 20 sends an RPC (Remote Procedure Call) message to the control unit 11 in response to an RPC message indicating acquisition (get or get-config). This RPC response message includes information about the RU device 20. This information about the RU device 20 includes capability information indicating that the RU device 20 has the capability to send a message (e.g., a Notification message) to the control unit 11 to notify the control unit 11 that the RU device 20 has autonomously transitioned from normal mode to ES mode (or whether the RU device 20 has such capability).

[0069] With this configuration of the RU device 20, the control device 11 can determine that the RU device 20 has autonomously transitioned to ES mode.

[0070] <Variation> The system in the first embodiment may be modified as follows: The first message may contain request information about one or any combination (including all) of the information elements described below, instead of the examples 1 and 2 of the information elements described above. The first response message may also contain one or any combination (including all) of the information elements described below, based on the request information. Alternatively, the first response message may contain some or all of the content relating to any combination (including all) of the information elements described below, based on the request information.

[0071] (Example of an information element 3) The information element in Example 3 is Capability information that indicates (or whether or not) the RU device 20 has the capability to request the control device 11 to transition the RU device 20 from normal mode to ES mode when the "predetermined conditions" for transitioning the RU device 20 to ES mode are met. If this Capability is valid, the RU device 20 requests the control device 11 to transition the RU device 20 from normal mode to ES mode when the "predetermined conditions" are met. In response to this request, the control device 11 executes control to transition the RU device 20 from normal mode to ES mode. This control uses, for example, edit-config. Even in this case, the transition from normal mode to ES mode can be said to be triggered by the RU device 20, with the request from the RU device 20 being the starting point (RU triggered Saving mode). Furthermore, by receiving this Capability information, the control device 11 can understand that it may receive the above request from the RU device 20 in the future.

[0072] (Example of an information element 4) The information element in Example 4 is Capability information indicating that the RU device 20 has the capability to send a message (e.g., a Notification message) to the control device 11 requesting the control device 11 to transition the RU device 20 from normal mode to ES mode when the "predetermined conditions" for transitioning the RU device 20 to ES mode are met (or indicating whether or not the RU device 20 has such capability). If this Capability is valid, the RU device 20 sends the message (e.g., a Notification message) to the control device 11 when the "predetermined conditions" are met. The control device 11 then executes control to transition the RU device 20 from normal mode to ES mode in response to the message. This control is performed using, for example, edit-config. In this case as well, the transition from normal mode to ES mode can be said to be triggered by the RU device 20, with the message from the RU device 20 being the starting point (RU triggered Saving mode). By receiving this Capability information, the control device 11 can understand that it may receive the above message from the RU device 20 in the future.

[0073] Furthermore, the aspect of the information element in Example 4, "sending a message to the control device 11 requesting the control device 11 to switch the RU device 20 from normal mode to ES mode," can be considered a specific example of the aspect of the information element in Example 3, "requesting the control device 11 to switch the RU device 20 from normal mode to ES mode."

[0074] <Second Embodiment> The system configuration may be the same as the example shown in Figure 5. Figure 7 shows another example of the processing operation of the RU device and control device of this disclosure.

[0075] The control device 11 (NETCONF client) sends a message indicating configuration editing (edit-config) to the RU device 20 (hereinafter sometimes referred to as the "second request message") (step S21). The second request message may also be an RPC message. The second request message includes at least one of the following configuration information elements.

[0076] (Example 1 of a configuration information element) The second request message includes a configuration information element indicating, for example, that the RU device 20 is permitted to autonomously transition from normal mode to ES mode when certain conditions are met. This configuration information element is used in conjunction with the Capability information of the "Information Element of Example 1" described in the first embodiment. That is, the control device 11 may receive a first response message containing the Information Element of Example 1, thereby understanding that "the RU device 20 has the capability to autonomously transition from normal mode to ES (Energy Saving) mode," and then transmit a second request message containing this configuration information element.

[0077] When the RU device 20 receives a second request message containing the above-mentioned configuration information element, it activates a parameter indicating that the RU device 20 is permitted to autonomously transition to ES mode (step S22). This parameter may be a new parameter not described in Non-Patent Literature 1 (for example, the "self-saving-enabled" parameter). This sets the RU device 20 to the above-mentioned "Self Saving mode". In other words, the RU device 20 autonomously transitions from normal mode to ES mode when predetermined conditions are met. (Example 2 of a configuration information element)

[0078] Alternatively, for example, the second request message may include a configuration information element indicating that the RU device 20 is permitted to request the control device 11 to switch the RU device 20 from normal mode to ES mode (more specifically, to send a request message to the control device 11) when certain conditions are met. This configuration information element is used in conjunction with, for example, the "information element of Example 3" or the "information element of Example 4" described in the first embodiment. That is, the control device 11 may receive a first response message containing the information element of Example 3 (or the information element of Example 4) and, after understanding that "the RU device 20 has the ability to request the control device 11 to switch the RU device 20 from normal mode to ES mode (more specifically, the ability to send a request message to the control device 11)," send a second request message containing this configuration information element.

[0079] When the RU device 20 receives a second request message containing the above-mentioned configuration information elements, it may activate a parameter indicating that it is permitted to make the request to the control device 11 or a parameter indicating that it is permitted to send the message to the control device 11 (step S22). As a result, the RU device 20 enters a state in which it makes the above-mentioned request when the above-mentioned predetermined conditions are met (more specifically, a state in which it sends a message for the above-mentioned request).

[0080] The RU device 20 sends an RPC reply (rpc-reply) message (hereinafter sometimes referred to as the "second reply message") to the control device 11 in response to the second message (step S23). That is, Figure 7 shows NETCONF <edit-config>An example of the processing operation of the RU device 20 and the control device 11, following the procedure, is shown.

[0081] <Third Embodiment> The system configuration may be the same as the example shown in Figure 5. Figure 8 shows another example of the processing operation of the RU device and control device of this disclosure. In the third embodiment, it is assumed that the RU device 20 is set to the Self Saving mode described in the second embodiment.

[0082] The RU device 20 waits until the above-mentioned "predetermined conditions" are met (step S31 NO). If the above-mentioned "predetermined conditions" are met (step S31 YES), the RU device 20 autonomously switches its mode from normal mode to ES mode (step S32). This allows the RU device 20 to flexibly control the transition to ES mode.

[0083] At this time, the RU device 20 may change the settings of any of the following parameters.

[0084] (Parameter example 1) The RU device 20 may also set the value of the active parameter of the tx / rx-array-carriers of the RU device 20 to SLEEP or INACTIVE.

[0085] (Parameter example 2) The RU device 20 may set the value of the active parameter of the tx / rx-array-carriers of the RU device 20 to a value that indicates that the RU device 20 has autonomously transitioned to ES mode. For example, the value that indicates that the RU device 20 has autonomously transitioned to ES mode may be a new value not described in Non-Patent Literature 1 (e.g., "SELF-SLEEP").

[0086] (Parameter example 3) The RU device 20 may set the value of a parameter indicating autonomous transition to ES mode to SLEEP. The parameter indicating autonomous transition to ES mode may be, for example, a novel parameter not described in Non-Patent Document 1 (e.g., the "self-active" parameter). Self-active is a parameter that selectively takes the value of, for example, "ACTIVE" or "SLEEP".

[0087] Then, the RU device 20 sends a notification to the control device 11 (NETCONF client) indicating that the RU device 20 has autonomously transitioned to ES mode (step S33). This allows the control device 11 to understand that the RU device 20 has autonomously transitioned to ES mode. Note that the order of steps S32 and S33 is not limited to this, and step S32 may be performed after step S33.

[0088] <Fourth Embodiment> The system configuration may be the same as the example shown in Figure 5. Figure 9 shows another example of the processing operation of the RU device and control device of this disclosure. In the fourth embodiment, it is assumed that the RU device 20 is in a state in which the request described in the second embodiment is accepted (more specifically, in a state in which the transmission of a message for the request is accepted).

[0089] The RU device 20 waits until the above-mentioned "predetermined conditions" are met (step S41 NO). If the above-mentioned "predetermined conditions" are met (step S41 YES), the RU device 20 sends a message (e.g., a Notification message) to the control device 11 requesting a mode change for the RU device 20 (change to ES mode) (step S42). This allows the RU device 20 to flexibly control the transition to ES mode.

[0090] When the control device 11 receives the above message, that is, in response to receiving the above message, it sends an RPC message (hereinafter sometimes referred to as the "third request message") indicating configuration editing (edit-config) to the RU device 20 (step S43).

[0091] The third request message may include one of the following configuration information elements:

[0092] (Example 1 of a configuration information element) The configuration information element in Example 1 is configuration information that sets the value of the active parameter of the tx / rx-array-carriers of the RU device 20 to SLEEP or INACTIVE.

[0093] (Example 2 of a configuration information element) The configuration information element in Example 2 is configuration information that sets the value of the active parameter of tx / rx-array-carriers of the RU device 20 to a value that indicates that the RU device 20 has autonomously transitioned to ES mode.

[0094] (Example 3 of configuration information elements) The setting information element in Example 3 is setting information that sets the value of the parameter indicating the autonomous transition of the RU device 20 to ES mode to SLEEP.

[0095] When the RU device 20 receives the third request message, it switches its mode from normal mode to ES mode (step S44).

[0096] Specifically, the RU device 20 changes the parameter settings based on the configuration information contained in the third request message. For example, if the third request message contains the configuration information element of Example 1 above, the RU device 20 sets the value of the active parameter of the tx / rx-array-carriers of the RU device 20 to SLEEP or INACTIVE. Also, if the third request message contains the configuration information element of Example 2 above, the RU device 20 sets the value of the active parameter of the tx / rx-array-carriers of the RU device 20 to a value indicating that the RU device 20 has autonomously transitioned to ES mode. Also, if the third request message contains the configuration information element of Example 3 above, the RU device 20 sets the value of the parameter indicating the autonomous transition of the RU device 20 to ES mode to SLEEP.

[0097] The RU device 20 sends an RPC reply (rpc-reply) message ("third reply message") to the control device 11 in response to the third request message (step S45). That is, Figure 9 shows NETCONF <edit-config>An example of the processing operations of the RU device 20 and the control device 11 according to the procedure is shown. Note that the order of steps S44 and S45 is not limited to this, and step S44 may be performed after step S45.

[0098] <Other Embodiments> <1> Figure 10 shows an example of the configuration of a control device. In Figure 10, the control device 100 has a processor 101 and a memory 102. The control device 11 may have the configuration shown in Figure 10. The processor 101 may be, for example, a microprocessor, an MPU (Micro Processing Unit), or a CPU (Central Processing Unit). The processor 101 may include multiple processors. The memory 102 is composed of a combination of volatile memory and non-volatile memory. The memory 102 may include multiple physically independent memory devices. The volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM), or a combination thereof. The non-volatile memory is Mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or a hard disk drive, or any combination thereof. The memory 102 may include storage located away from the processor 101. In this case, the processor 101 may access memory 102 via an I(Input) / O(Output) interface, which is not shown.

[0099] Memory 102 may store one or more software modules (computer programs) containing instruction sets and data for processing by the control device 11 as described in the above-described embodiments. In some implementations, the processor 101 may be configured to read the software modules from memory 102 and execute them to perform the processing of the control device 11 as described in the above-described embodiments.

[0100] <2> Figure 11 shows an example configuration of a DU device. In Figure 11, the device 200 includes a network interface 201, a processor 202, and memory 203. The DU device 10 may have the configuration shown in Figure 11.

[0101] Network interface 201 is used, for example, to communicate with network elements (e.g., SMO device 30, other RAN nodes). Network interface 1201 may include, for example, a network interface card (NIC) compliant with the IEEE 802.3 series.

[0102] The processor 202 may be, for example, a microprocessor, an MPU, or a CPU. The processor 202 may include multiple processors.

[0103] Memory 203 consists of volatile memory and non-volatile memory. Memory 203 may include multiple physically independent memory devices. Volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM), or a combination thereof. Non-volatile memory is Mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or hard disk drive, or any combination thereof. Memory 203 may include storage located away from the processor 202. In this case, the processor 202 may access memory 203 via a network interface 201 or an I / O interface.

[0104] The memory 203 may store one or more software modules (computer programs) containing instruction sets and data for performing the processing by the DU device 10 as described in the above embodiments. In some implementations, the processor 202 may be configured to perform the processing of the DU device 10 as described in the above embodiments by reading and executing the software modules from the memory 203.

[0105] <3> Figure 12 shows an example configuration of an RU device. In Figure 12, the device 300 includes an antenna array 301, a radio frequency transceiver 302, a network interface 303, a processor 304, and memory 305. The RU device 20 may have the configuration shown in Figure 12. The RF transceiver 302 performs analog RF signal processing to communicate with UEs. The RF transceiver 302 may include multiple transceivers. The RF transceiver 302 is coupled with the antenna array 301 and the processor 304. The RF transceiver 302 receives modulation symbol data from the processor 304, generates a transmit RF signal, and supplies the transmit RF signal to the antenna array 301. The RF transceiver 302 also generates a baseband receive signal based on the received RF signal received by the antenna array 301 and supplies it to the processor 304. The RF transceiver 302 may include an analog beamformer circuit for beamforming. The analog beamformer circuit includes, for example, multiple phase shifters and multiple power amplifiers.

[0106] The network interface 303 is used to communicate with network nodes (e.g., DU10, SMO30). The network interface 303 may include, for example, a network interface card (NIC) compliant with the IEEE 802.3 series.

[0107] Processor 304 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. Processor 304 may include multiple processors. For example, processor 304 may include a modem processor (e.g., Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (e.g., Central Processing Unit (CPU) or Micro Processing Unit (MPU)) that performs control plane processing.

[0108] The processor 304 may include a digital beamformer module for beamforming. The digital beamformer module may include a Multiple Input Multiple Output (MIMO) encoder and a precoder.

[0109] Memory 305 is comprised of a combination of volatile and non-volatile memory. Volatile memory may be, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM), or a combination thereof. Non-volatile memory may be Mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or a hard disk drive, or any combination thereof. Memory 305 may also include storage located away from the processor 304. In this case, the processor 304 may access memory 305 via a network interface 303 or an I / O interface not shown.

[0110] The memory 305 may store one or more software modules (computer programs) containing instruction sets and data for performing processing by the RU device 20 as described in the above embodiments. In some implementations, the processor 304 may be configured to perform the processing of the RU device 20 as described in the above embodiments by reading and executing the software modules from the memory 305.

[0111] The antenna array 301 may correspond to the tx-array and rx-array described above.

[0112] <4> Figure 13 shows an example configuration of an SMO device. In the example in Figure 13, the SMO device 400 is implemented as a computer system. The computer system 400 includes one or more processors 401, memory 402, and mass storage 403, which communicate with each other via a bus 407. The one or more processors 401 may include, for example, a Central Processing Unit (CPU) or a Graphics Processing Unit (GPU) or both. The computer system 400 may also include other devices such as one or more output devices 404, one or more input devices 405, and one or more peripherals 406. The one or more peripherals 406 may include a modem or a network adapter, or any combination thereof.

[0113] One or both of the memory 402 and the mass storage 403 include a computer-readable medium storing one or more instruction sets. These instructions may be partially or completely located in the memory of one or more processors 401. When executed by one or more processors 401, these instructions cause one or more processors 401 to provide the functionality of the SMO device 30 described in the embodiments described above.

[0114] While the present disclosure has been described above with reference to embodiments, the disclosure is not limited thereto. Various modifications to the structure and details of the present disclosure are possible, as can be understood by those skilled in the art within the scope of the disclosure. Furthermore, each embodiment can be combined with other embodiments as appropriate.

[0115] Some or all of the above embodiments may also be described as follows, but are not limited to the following: (Note 1) RU (Radio Unit) device, At least one memory, At least one processor coupled to the at least one memory, Equipped with, The at least one processor autonomously transitions the RU device from normal mode to ES (Energy Saving) mode when predetermined conditions are met. RU equipment. (Note 2) RU (Radio Unit) device, At least one memory, At least one processor coupled to the at least one memory, Equipped with, The at least one processor requests the RU control device to switch the RU device from normal mode to ES (Energy Saving) mode when certain conditions are met. RU equipment. (Note 3) The aforementioned at least one processor is Based on the NETCONF (Network Configuration Protocol) protocol, an RPC (Remote Procedure Call) message indicating retrieval (get or get-config) is received from the RU control unit. In response to the RPC message, an RPC reply (rpc-reply) message is sent to the RU control device. The RPC response message includes capability information indicating that the RU device has the ability to autonomously transition from normal mode to ES (Energy Saving) mode. The RU device described in Appendix 1. (Note 4) The aforementioned at least one processor is Based on the NETCONF (Network Configuration Protocol) protocol, an RPC (Remote Procedure Call) message indicating retrieval (get or get-config) is received from the RU control unit. In response to the RPC message, an RPC reply (rpc-reply) message is sent to the RU control device. The RPC response message includes capability information indicating that the RU device has the ability to request the RU control device to switch the RU device from normal mode to ES (Energy Saving) mode. The RU device described in Appendix 2. (Note 5) The at least one processor sends a notification message to the RU control unit to inform it that it has autonomously transitioned the RU device from normal mode to ES (Energy Saving) mode. The RU device described in Appendix 1. (Note 6) The at least one processor sends a notification message to the RU control device requesting it to switch the RU device from normal mode to ES (Energy Saving) mode. The RU device described in Appendix 2. (Note 7) The aforementioned predetermined conditions are: The overheat determination parameters of the RU device satisfy the overheating conditions. The number of user devices (UEs) communicating with the RU device is less than the threshold, or The predetermined time for transitioning to ES mode will be reached. Including any one or any combination of the following: The RU device described in Appendix 1 or 2. (Note 8) When the at least one processor autonomously transitions the RU device from normal mode to ES mode, Set the value of the active parameter of the tx / rx-array-carriers of the RU device to SLEEP or INACTIVE, Set the value of the active parameter of the tx / rx-array-carriers of the RU device to a value (SELF-SLEEP) that indicates the RU device has autonomously transitioned from normal mode to ES mode, or The value of the parameter (self-active) indicating the autonomous transition of the RU device to ES mode is set to SLEEP. The RU device described in Appendix 1. (Note 9) The at least one processor receives a message from the RU control device in response to a request from the RU device to switch the RU device from normal mode to ES (Energy Saving) mode, which is an RPC (Remote Procedure Call) message based on the NETCONF (Network Configuration Protocol) protocol and indicating an edit-config request, The aforementioned RPC message is: Setting information to set the value of the active parameter of the tx / rx-array-carriers of the RU device to SLEEP or INACTIVE. Setting information to set the value of the active parameter of the tx / rx-array-carriers of the RU device to a value (SELF-SLEEP) that indicates the RU device has autonomously transitioned from normal mode to ES mode, or The setting information for setting the parameter (self-active) that indicates the autonomous transition of the RU device to ES mode to SLEEP, including, The RU device described in Appendix 2. (Note 10) The at least one processor, in the ES mode, stops at least one of the C / U (Control / User)-plane, S (Synchronization)-plane, M (Management)-plane, and components of the RU device. The RU device described in Appendix 1 or 2. (Note 11) The aforementioned component includes at least one of a digital device section and an analog device section. The RU device described in Appendix 10. (Note 12) The digital device section includes at least one of the following: FPGA (Field Programmable Gate Array), CPLD (Complex Programmable Logic Device), ASIC (Application Specific Integrated Circuit), processor, and network interface. The RU device described in Appendix 11. (Note 13) The analog device section is an antenna array or a PA (Power Amplifier). The RU device described in Appendix 11. (Note 14) The at least one processor, in the ES mode, lowers the voltage of the RU device. The RU device described in Appendix 1 or 2. (Note 15) Lowering the voltage of the RU device means To reduce the antenna transmission power of the RU device, To stop the PA (Power Amplifier) ​​of the aforementioned RU device, and, To stop the power supply from the RU device to an external device connected to the RU device, including at least one of the following: The RU device described in Appendix 14. (Note 16) At least one memory, At least one processor coupled to the at least one memory, Equipped with, The aforementioned at least one processor sends an RPC (Remote Procedure Call) message to the RU (Radio Unit) device that is based on the NETCONF (Network Configuration Protocol) protocol and indicates an edit-config request. The RPC message includes configuration information that allows the RU device to autonomously switch from normal mode to ES (Energy Saving) mode when predetermined conditions are met. Control device. (Note 17) At least one memory, At least one processor coupled to the at least one memory, Equipped with, The aforementioned at least one processor sends an RPC (Remote Procedure Call) message to the RU (Radio Unit) device that is based on the NETCONF (Network Configuration Protocol) protocol and indicates an edit-config request. The RPC message includes configuration information that allows the RU device to request the RU control device to switch the RU device from normal mode to ES (Energy Saving) mode when predetermined conditions are met. Control device. (Note 18) When the RU device requests the at least one processor to switch from normal mode to ES (Energy Saving) mode, the processor sends an RPC (Remote Procedure Call) message to the RU device that is based on the NETCONF (Network Configuration Protocol) protocol and indicates an edit-config request. The aforementioned RPC message is: Setting information to set the value of the active parameter of the tx / rx-array-carriers of the RU device to SLEEP or INACTIVE. Setting information to set the value of the active parameter of the tx / rx-array-carriers of the RU device to a value (SELF-SLEEP) that indicates the RU device has autonomously transitioned from normal mode to ES mode, or The setting information for setting the parameter (self-active) that indicates the autonomous transition of the RU device to ES mode to SLEEP, including, The control device described in Appendix 17. (Note 19) A method performed by a Radio Unit (RU) device, This includes autonomously switching the RU device from normal mode to ES (Energy Saving) mode when certain conditions are met. method. (Note 20) A method performed by a Radio Unit (RU) device, This includes requesting the RU control device to switch the RU device from normal mode to ES (Energy Saving) mode when certain conditions are met. method. (Note 21) Receiving an RPC (Remote Procedure Call) message from the RU control unit that is based on the NETCONF (Network Configuration Protocol) protocol and indicates retrieval (get or get-config), In response to the aforementioned RPC message, an RPC response (rpc-reply) message is transmitted to the RU control device. It further includes, The RPC response message includes capability information indicating that the RU device has the ability to autonomously transition from normal mode to ES (Energy Saving) mode. The method described in Appendix 19. (Note 22) Receiving an RPC (Remote Procedure Call) message from the RU control unit that is based on the NETCONF (Network Configuration Protocol) protocol and indicates retrieval (get or get-config), In response to the aforementioned RPC message, an RPC response (rpc-reply) message is transmitted to the RU control device. It further includes, The RPC response message includes capability information indicating that the RU device has the ability to request the RU control device to switch the RU device from normal mode to ES (Energy Saving) mode. The method described in Appendix 20. (Note 23) The further includes sending a Notification message to the RU control unit to inform the RU control unit that the RU device has autonomously switched from normal mode to ES (Energy Saving) mode, The method described in Appendix 19. (Note 24) The further includes sending a Notification message to the RU control device requesting the RU device to switch from normal mode to ES (Energy Saving) mode, The method described in Appendix 20. (Note 25) The aforementioned predetermined conditions are: The overheat determination parameters of the RU device satisfy the overheating conditions. The number of user devices (UEs) communicating with the RU device is less than the threshold, or The predetermined time for transitioning to ES mode will be reached. Including any one or any combination of the following: The method described in Appendix 19 or 20. (Note 26) When the RU device autonomously switches from normal mode to ES mode, Set the value of the active parameter of the tx / rx-array-carriers of the RU device to SLEEP or INACTIVE. The value of the active parameter of the tx / rx-array-carriers of the RU device is set to a value (SELF-SLEEP) that indicates the RU device has autonomously transitioned from normal mode to ES mode, or The value of the parameter (self-active) indicating the autonomous transition of the RU device to ES mode is set to SLEEP. including, The method described in Appendix 19. (Note 27) The RU control device receives a message from the RU control device in response to receiving a Notification message, which is an RPC (Remote Procedure Call) message based on the NETCONF (Network Configuration Protocol) protocol and indicating configuration editing (edit-config), further comprising: The aforementioned RPC message is: Setting information to set the value of the active parameter of the tx / rx-array-carriers of the RU device to SLEEP or INACTIVE. Setting information to set the value of the active parameter of the tx / rx-array-carriers of the RU device to a value (SELF-SLEEP) that indicates the RU device has autonomously transitioned from normal mode to ES mode, or The setting information for setting the parameter (self-active) that indicates the autonomous transition of the RU device to ES mode to SLEEP, including, The method described in Appendix 20. (Note 28) In the aforementioned ES mode, at least one of the C / U (Control / User)-plane, S (Synchronization)-plane, M (Management)-plane, and the components of the RU device are stopped. The method described in Appendix 19 or 20. (Note 29) The aforementioned component includes at least one of a digital device section and an analog device section. The method described in Appendix 28. (Note 30) The digital device section includes at least one of the following: FPGA (Field Programmable Gate Array), CPLD (Complex Programmable Logic Device), ASIC (Application Specific Integrated Circuit), processor, and network interface. The method described in Appendix 29. (Note 31) The analog device section is an antenna array or a PA (Power Amplifier). The method described in Appendix 29. (Note 32) In the aforementioned ES mode, the voltage of the RU device is reduced. The method described in Appendix 19 or 20. (Note 33) The voltage of the aforementioned RU device is reduced. The antenna transmission power of the RU device is reduced. The Power Amplifier (PA) of the aforementioned RU device is stopped, and The power supply from the RU device to an external device connected to the RU device is stopped. including at least one of the following: The method described in Appendix 32. (Note 34) A method performed by a control device, This includes sending an RPC (Remote Procedure Call) message to the RU (Radio Unit) device that is based on the NETCONF (Network Configuration Protocol) protocol and indicates configuration editing (edit-config), The RPC message includes configuration information that allows the RU device to autonomously switch from normal mode to ES (Energy Saving) mode when predetermined conditions are met. method. (Note 35) A method performed by a control device, This includes sending an RPC (Remote Procedure Call) message to the RU (Radio Unit) device that is based on the NETCONF (Network Configuration Protocol) protocol and indicates configuration editing (edit-config), The RPC message includes configuration information that allows the RU device to request the RU control device to switch the RU device from normal mode to ES (Energy Saving) mode when predetermined conditions are met. method. (Note 36) If the RU device requests that it switch from normal mode to ES (Energy Saving) mode, the following is further included: sending an RPC (Remote Procedure Call) message to the RU device that is based on the NETCONF (Network Configuration Protocol) protocol and indicates an edit-config request: The aforementioned RPC message is: Setting information to set the value of the active parameter of the tx / rx-array-carriers of the RU device to SLEEP or INACTIVE. Setting information to set the value of the active parameter of the tx / rx-array-carriers of the RU device to a value (SELF-SLEEP) that indicates the RU device has autonomously transitioned from normal mode to ES mode, or The setting information for setting the parameter (self-active) that indicates the autonomous transition of the RU device to ES mode to SLEEP, including, The method described in Appendix 35. (Note 37) In the RU (Radio Unit) device, When predetermined conditions are met, the RU device is made to perform a process that includes autonomously switching from normal mode to ES (Energy Saving) mode. program. (Note 38) In the RU (Radio Unit) device, If predetermined conditions are met, the system will execute a process that includes requesting the RU control device to switch the RU device from normal mode to ES (Energy Saving) mode. program. (Note 39) In the control device, The process involves sending an RPC (Remote Procedure Call) message to the RU (Radio Unit) device that is based on the NETCONF (Network Configuration Protocol) protocol and indicates a configuration edit (edit-config). The RPC message includes configuration information that allows the RU device to autonomously switch from normal mode to ES (Energy Saving) mode when predetermined conditions are met. program. (Note 40) In the control device, The process involves sending an RPC (Remote Procedure Call) message to the RU (Radio Unit) device that is based on the NETCONF (Network Configuration Protocol) protocol and indicates a configuration edit (edit-config). The RPC message includes configuration information that allows the RU device to request the RU control device to switch the RU device from normal mode to ES (Energy Saving) mode when predetermined conditions are met. program.

[0116] This application claims priority based on Japanese Patent Application No. 2022-151204, filed on 22 September 2022, and incorporates all of its disclosures herein. [Explanation of symbols]

[0117] 1 System 10 DU equipment 11 Control Unit (Control Device) 20RU equipment 21 Control Unit 30 SMO device < / get> < / get> < / get> < / ok> < / get> < / get>

Claims

1. A first network device, The system includes a control means for switching the first network device from normal mode to ES (Energy Saving) mode when predetermined conditions are met. In the ES mode, the control means stops at least one of the C / U (Control / User)-plane, S (Synchronization)-plane, M (Management)-plane, and the components of the first network device. The aforementioned predetermined conditions include the time of transition to the ES mode being predetermined, The first network device.

2. Receiving means for receiving a first message from a second network device, The system further comprises a transmission means for transmitting a second message to the second network device in response to the first message, The second message includes capability information indicating that the first network device has the capability to transition from normal mode to ES mode. The first network device according to claim 1.

3. The first message is an RPC (Remote Procedure Call) message indicating acquisition (get or get-config), The receiving means receives the first message from the second network device based on the NETCONF (Network Configuration Protocol) protocol. The second message mentioned above is an RPC response (rpc-reply) message. The first network device according to claim 2.

4. The present invention further comprises a transmission means for transmitting a Notification message to the second network device to notify the second network device that the first network device has autonomously switched from normal mode to ES (Energy Saving) mode. The first network device according to claim 1.

5. The aforementioned predetermined conditions are: The overheat determination parameter of the first network device satisfies the overheat condition. The number of terminal devices communicating with the first network device is less than a threshold. Further including one or both of the following: The first network device according to claim 1.

6. When the control means autonomously transitions the first network device from normal mode to ES mode, Set the value of the active parameter of the tx / rx-array-carriers of the first network device to SLEEP or INACTIVE, The value of the tx / rx-array-carriers active parameter of the first network device is set to a value (SELF-SLEEP) that indicates the first network device has autonomously transitioned from normal mode to ES mode, or The value of the parameter (self-active) indicating the autonomous transition of the first network device to ES mode is set to SLEEP. The first network device according to claim 1.

7. The aforementioned component includes at least one of a digital device section and an analog device section. The first network device according to claim 1.

8. The digital device section includes at least one of the following: FPGA (Field Programmable Gate Array), CPLD (Complex Programmable Logic Device), ASIC (Application Specific Integrated Circuit), processor, and network interface. The first network device according to claim 7.

9. The analog device section is an antenna array or a PA (Power Amplifier). The first network device according to claim 8.

10. A method for a first network device, When certain conditions are met, the first network device is switched from normal mode to ES (Energy Saving) mode, The ES mode includes stopping the C / U (Control / User)-plane, S (Synchronization)-plane, M (Management)-plane, and at least one of the components of the first network device, The aforementioned predetermined conditions include the time of transition to the ES mode being predetermined, method.

Images