External power source coordination through radio units (RUS) in a communication system

Abstract

The present disclosure relates to external power source coordination in a communication system. A method comprises receiving capability information exposed by a Radio Unit (RU) that is powered by an external power source and receiving power supply statistics information from the RU. The method comprises transmitting the power supply statistics information to a management entity and receiving, from the management entity, the one or more energy management policies for the RU. The method comprises activating one or more energy saving features for the RU based on the received one or more energy management policies.

Description

[0001] EXTERNAL POWER SOURCE COORDINATION THROUGH RADIO UNITS (RUs) IN A COMMUNICATION SYSTEM

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003]

[0001] This application claims priority to Indian provisional patent application 202441061780, filed on August 14, 2024, and Indian non- provisional patent application 202441061780. filed on March 27, 2025, the entire contents of which are incorporated herein by reference.

[0004] FIELD

[0005]

[0002] The present disclosure relates to external power source coordination through radio units (RUs) in a communication system.

[0006] BACKGROUND

[0007]

[0003] The information disclosed in this background section is only for enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

[0008]

[0004] In Third Generation Partnership Project (3GPP) , a disaggregated architecture of a base station (also referred to as "gNodeB" or "gNB") is defined as partitioning the gNB into multiple logical entities, each of which can be implemented in different ways. Typically, the gNB can be partitioned into one or more central unit(s) (CUs), one or more distributed units (DUs), and one or more radio units (RUs). The CUs, DUs, and RUs may be inter-connected with each other via different interfaces and can be deployed in different configurations. The RUs are deployed near cell sites and are connected to their respective DU(s) via standardized fronthaul interfaces.

[0005] In wireless communication systems (e.g., 4G, 5G, etc.), power consumption is a critical factor which affects operational costs and efficiency of the communication systems. Among different components of a communication system, the RUs consume significant power. The RUs may be powered by energy / power supply from various energy / power sources including direct electricity supply (e.g., from a power grid) and renewable power sources such as solar power and wind power. A battery back-up may also be provided with various power sources to supply power in emergency scenario to the RUs e.g., when the power source is not supplying the required power. Since the RUs are power-intensive components of the communication systems, most power-saving initiatives focus on optimizing energy efficiency of the RUs.

[0009] SUMMARY

[0010]

[0006] The techniques of the present disclosure solve problem related to power coordination with external power sources. The present disclosure facilitates enhanced power coordination with external power sources thereby optimizing energy efficiency and providing efficient power management for communication devices (e.g., RUs), and reducing environmental impacts.

[0011]

[0007] In one non-limiting embodiment, the present disclosure discloses a method which comprises receiving, at a Distributed Unit (DU), capability information exposed by a Radio Unit (RU) that is powered by an external power source. The capability information indicates whether the RU supports an external power source coordination feature. The method comprises receiving power supply statistics information from the RU. The power supply statistics information is associated with the external power source and is collected using a Power Management System (PMS) associated with the RU. The method comprises transmitting the power supply statistics information to a management entity for determining one or more energy management policies for the RU. The method comprises receiving, from the management entity, the one or more energy management policies for the RU and activating one or more energy saving features for the RU based on the received one or more energy management policies.

[0012]

[0008] In one non-limiting embodiment, the present disclosure discloses an apparatus which is configured to receive, at a Distributed Unit (DU), capability information exposed by a Radio Unit (RU) that is powered by an external power source. The capability information indicates whether the RU supports an external power source coordination feature. The apparatus is configured to receive power supply statistics information from the RU. The power supply statistics information is associated with the external power source and is collected using a PMS associated with the RU. The apparatus is configured to transmit the power supply statistics information to a management entity for determining one or more energy management policies for the RU, receive, from the management entity, the one or more energy management policies for the RU, and activate one or more energy saving features for the RU based on the received one or more energy management policies.

[0013]

[0009] In one non-limiting embodiment, the present disclosure discloses a non-transitoiy computer readable media storing one or more computer executable instructions which, when executed by an apparatus, cause the apparatus to receive, at a Distributed Unit (DU), capability information exposed by a Radio Unit (RU) that is powered by an external power source. The capability information indicates whether the RU supports an external power source coordination feature. The instructions cause the apparatus to receive power supply statistics information from the RU. The power supply statistics information is associated with the external power source and is collected using a PMS associated with the RU. The instructions cause the apparatus to transmit the power supply statistics information to a management entity for determining one or more energy management policies for the RU, receive, from the management entity, the one or more energy management policies for the RU, and activate one or more energy saving features for the RU based on the received one or more energy management policies.

[0014] BRIEF DESCRIPTION OF THE DRAWINGS

[0015]

[0010] Features, aspects, and advantages of embodiments of the disclosure will be described below with reference to the accompanying drawings, in which like reference numerals denote like elements, and wherein:

[0016] [Oil] FIG. 1 illustrates a high-level block diagram 100 of a disaggregated architecture of a communication system.

[0017]

[0012] FIG. 2 illustrates a high-level block diagram 200 of a disaggregated architecture defined by Open Radio Access Network Alliance.

[0018]

[0013] FIG. 3 illustrates a high-level block diagram of an example communication system 300 in which Radio Units (RUs) are deployed at a telecom site and Distributed Units (DUs) and Service Management and Orchestration (SMO) framework are deployed on a cloud.

[0019]

[0014] FIG. 4 illustrates a high-level block diagram of an example communication system 400 in which RUs and DUs are deployed at a telecom site and a SMO framework is deployed on a cloud.

[0020]

[0015] FIG. 5 illustrates an exemplary call flow diagram 500 between a Distributed Unit (DU)Distributed Unit (DU), a Radio Unit (RU), and a management entity.

[0021]

[0016] FIG. 6 illustrates a flowchart of an example method 600 of external power source coordination in a communication system.

[0022]

[0017] FIG. 7 illustrates a block diagram 700 of an apparatus. DETAILED DESCRIPTION

[0023]

[0018] The following detailed description of example embodiments refers to the accompanying drawings. The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations. Further, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, the flowchart and description of operations provided below relate to one of the various embodiments. It should be noted that it is possible to make other embodiments that do not exactly match the flowchart and its description. It is understood that in other embodiments one or more operations may be omitted, one or more operations may be added, one or more operations may be performed simultaneously (at least in part).

[0024]

[0019] It will be apparent that systems and / or methods, described herein may be implemented in different forms of hardware, software, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the implementations. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It is understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0025]

[0020] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of implementations includes each dependent claim in combination with every other claim in the claim set.

[0026] 1021] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Also, as used herein, the tenns “has,” “have,” “having,” “include,” “including.” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Furthermore, expressions such as “at least one of [A] and [B],” “[A] and / or [B],” or “at least one of [A] or [B] ” are to be understood as including only A. only B, or both A and B.

[0027]

[0022] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.

[0028]

[0023] The present disclosure may include terms and names defined in one or more standard organizations, such as the 3rd Generation Partnership Project (3GPP) standard organization, the European Telecommunications Standards Institute (ETSI), the Open Radio Access Network (O-RAN) Alliance standard organization, and the like. Various terms of the present disclosure as well as the associated features and operations, are to be interpreted as consistent with those specified in one or more technical specifications, unless explicitly specified otherwise.

[0029]

[0024] In the present disclosure, the terms like “communication system”, “system”, and “wireless communication system” have been used interchangeably throughout the specification. The terms like “battery back-up” and “battery based power source” have been used interchangeably throughout the specification. The terms like “power source” and “energy source” have been used interchangeably throughout the specification. The terms like “SMO” and “SMO framework” have been used interchangeably throughout the specification. In the present disclosure, the term “power source” or “energy source” may refer to any system, device, or mechanism that generates electrical energy for use in various applications (e.g.. for powering RUs). A power source may include at least one of a renewable power source, a non-renewable power source, or a battery-based power source. As an example, the renewable power source may include solar power source, wind power source, hydro power source, geothermal power source, but not limited thereto. As an example, the non-renewable power source produces energy using resources that exist in limited quantities and cannot be replenished on a short timescale. The non-renewable power source may use coal, natural gas, oil, etc. to generate power. The battery-based power source may include a power source that stores energy chemically and releases it as electrical energy when needed. The battery-based power sources may be rechargeable or single-use.

[0030]

[0025] In the present disclosure, “external power source coordination through Radio Units (RUs)” refers to a feature or mechanism in which the RUs within a communication system may dynamically interact with and manage various external power sources (e.g., renewable power sources, non-renewable power sources, or battery-based pow er sources, etc.). In the mechanism, the communication system may monitor, control, and optimize pow er consumption for the RUs based on information associated w ith the different power sources. The techniques of external powder source coordination disclosed herein provide efficient powder utilization, seamless switching between powder sources, and energy-aware network operations, thereby optimizing energy efficiency and network reliability, and reducing environmental impacts.

[0026] FIG. 1 illustrates a high-level block diagram 100 of a disaggregated architecture of an example communication system comprising a Radio Access Network (RAN) node or a base station 102 configured to serve a geographical area or cell 104. The cell 104 may comprise at least one UE 106 and the base station 102, which may be configured to provide wireless services to the at least one UE 106 served by the associated cell 104.

[0031]

[0027] The at least one UE 106 may be any mobile or non-mobile computing device including, but not limited to, a phone (e.g., a cellular phone or smart phone), a pager, a laptop computer, a desktop computer, a wireless handset, a portable communication device, a portable computing device (e.g., a personal data assistant), an entertainment device (e.g., a music or video device, or a satellite radio), a global positioning system device, or any other suitable computing device including a wired or wireless communications interface. In some embodiments of the present disclosure, the at least one UE 106 may be Intemet-of-Things (loT)-enabled device including, but not limited to, vehicles configured to communicate with the RAN node or a core network.

[0032]

[0028] The base station 102 may be a fourth generation (4G) Long Term Evolution (LTE) base station (referred to as an “evolved NodeB”, “eNodeB”, or “eNB”) or a fifth generation (5G) New Radio (NR) base station (referred to as a “gNodeB” or “gNB”). In a disaggregated architecture defined by 3GPP, the base station 102 may be implemented as the 5G NR base station (gNB) 102 and may be partitioned into multiple logical network entities. For instance, the base station 102 may be partitioned into a central unit (gNB-CU or CU) 108 and one or more distributed units (gNB-DUs or DUs) 110. In the embodiment of FIG. 1, the CU 108 may be further partitioned into a central unit control-plane entity 114 (gNB-CU-CP or CU-CP) and one or more central unit user-plane entities 116 (gNB-CU-Ups or CU-UPs) that may handle the control-plane and user-plane processing of the CU 108, respectively.

[0029] The base station 102 may comprise one or more physical entities such as Radio Units

[0033] (RUs) 112 including one or more antennas 118 for serving the at least one UE 106 in the associated cell. The CU 108 may be communicatively coupled with the one or more DUs 110 via an Fl interface. The DU 110 may be communicatively coupled with at least one RU 112 via a fronthaul interface 120. The CU-CP 114 may be communicatively coupled with each of the CU-UPs 116 via an El interface and may be further coupled with each of the DUs 110 via an Fl-C interface. Each of the DUs 110 may be communicatively coupled to each of the CU- UPs 116 via an Fl-U interface, as shown in FIG. 1.

[0034]

[0030] In one non-limiting embodiment, each DU 110 may host multiple cells. The CU-CP 114 may host one or more DUs 110 and one or more CU-UPs 116. In one example deployment, there may be one CU-CP 114 in a base station 102, and each DU 110 may be served by multiple CU-UPs 116. The CU-CP 114 is responsible for managing control plane protocols and procedures. For instance, the CU-CP 114 may host Packet Data Convergence Protocol - Control Plane (PDCP-C) layer and Radio Resource Control (RRC) layer, while the CU-UP 116 may host Packet Data Convergence Protocol - User Plane (PDCP-U) and Service Data Adaptation Protocol (SDAP) layers. The DU 110 may host lower layers such as Radio Link Control (RLC), Medium Access Control (MAC), and Physical (PHY) layers.

[0035]

[0031] The CU 108 may be configured to communicate with a core network 122 using a backhaul network 124. In one non-limiting embodiment of the present disclosure, the core network 122 may be a 5G core network which may utilize cloud-aligned, service-based architecture that spans across all 5G functions and interactions including authentication, security, session management etc.

[0036]

[0032] Each component of the base station 102 may be implemented as a physical network function (PNF) and / or as a virtual network function (VNF). For example, the RUs 112 may be implemented as a PNF and may be deployed at or near a telecom site (or cell site) where radio coverage is to be provided and the CU(s) 108 and the DUs 110 may be implemented using VNFs and may be deployed within cloud (for example, a cloud data center). In another example, the RUs 112 and DUs 110 may be implemented as PNFs and may be deployed at or near the telecom site and the CU 108 may be implemented using VNFs and may be deployed within the cloud.

[0037]

[0033] In some examples, the communication system 100 may be implemented using a RAN architecture and / or interfaces defined by the Open Radio Access Network (O-RAN) Alliance, as shown in FIG. 2.

[0038]

[0034] FIG. 2 illustrates a high-level block diagram 200 of a disaggregated architecture defined by the O-RAN Alliance. In the example shown in FIG. 2, RAN functions in the O- RAN architecture may be controlled and optimized by a RAN Intelligent Controller (RIC). The RIC is a software-defined component that implements modular applications to facilitate the multivendor operability required in O-RAN systems, as well as to automate and optimize RAN operations. The RIC may be divided into two ty pes: a non-real-time RIC (NRT-RIC) 202 and a near-real-time RIC (nRT-RIC) 204. The non-real time RIC 202 and the near-real time RIC 204 may be separate entities in the O-RAN architecture and serve different purposes. In some examples, the non-real time RIC 202 may be implemented as a standalone application in a cloud network. In other examples, the non-real time RIC 202 may be integrated with a Service Management and Orchestration (SMO) framework 206. In some examples, the near-real time RIC 204 may be implemented as a standalone application in a cloud network. In other examples, the near-real time RIC 204 may be embedded in O-CU.

[0039]

[0035] In the O-RAN architecture, each CU, DU, and RU may be implemented as an O-RAN central unit (O-CU), O-RAN distributed unit (O-DU) 210, and O-RAN radio unit (O-RU) 212, respectively. In the example shown in FIG. 2, the architecture 200 includes a single O-CU, which is split between an O-CU-CP 214 that handles control-plane functions and an O-CU-UP 216 that handles user-plane functions. The O-CU(s) control the operation of the O-DUs 210 over an interface (including Fl-c and Fl-u for the control plane and user plane, respectively). The O-CU-CP 214 and the O-CU-UP 216 may communicate with core network using the interfaces defined in the O-RAN specifications.

[0040]

[0036] The non-RT RIC 202 is the control point of a non-real-time control loop and operates on a timescale greater than Is within the SMO framework 206. The near-RT RIC 204 and the non-RT RIC 202 may communicate over an Al interface to optimize the O-RAN. The SMO framework 206 may be connected with underlying RAN elements (e.g., near-RT RIC 204. O- CU, O-CU-CP 214, O-CU-UP 216, O-DU 210. O-RU 212, O-eNB 218, etc.) via an O1 interface. Here, O-eNB 218 may be any O-RAN compliant LTE base station. The functionalities of the non-RT RIC 202 may be implemented through modular applications called rApps, and include providing policy based guidance and enrichment across an Al interface: performing data analytics; Artificial Intelligence / Machine Learning (AI / ML) training and inference for RAN optimization; and / or recommending configuration management actions over the O1 interface.

[0041]

[0037] The near-RT RIC 204 may operate on a timescale between 10ms and Is. The near-RT RIC 204 may use an E2 interface to connect and control underlying RAN elements or E2 nodes (e g., O-DU 210, O-CU, O-CU-CP 214, O-CU-UP 216, O-eNB 218, etc ). The near-RT RIC 204 may host xApps to implement functions such as quality of service (QoS) optimization, mobility optimization, slicing optimization, interference mitigation, load balancing, security, etc. The two types of RIC s may work together to optimize the O-RAN. For example, the Non- RT RIC 202 may provide, over the Al interface, the policies, data, and AI / ML models enforced and used by the near-RT RIC 204 for RAN optimization, and the near-RT RIC 204 may return policy feedback (i.e., how a policy set by the Non-RT RIC 202 works).

[0042]

[0038] The SMO framework 206, within which the Non-RT RIC 202 is located, manages and orchestrates RAN elements. Specifically, the SMO framework 206 manages and orchestrates what is referred to as the O-RAN Cloud (O-Cloud) 220. The O-Cloud 220 may be a collection of physical RAN nodes that host the RICs, O-CUs. and O-DUs 210. the supporting software components (e.g., the operating systems and runtime environments), and the SMO framework 206 itself. In other words, the SMO framework 206 manages the O-Cloud 220 from within. 02 interface is the interface between the SMO framework 206 and the O-Cloud 220 it resides in. Through the 02 interface, the SMO framework 206 provides infrastructure management services (IMS) and deployment management services (DMS).

[0043]

[0039] The O-DU 210 communicates with the O-RU 212 via an open fronthaul (FH) control, user, and synchronization (CUS) plane interface and an open FH Management Plane (M-plane) Interface. The FH MP interface may connect the O-RU 212 to the O-DU 210 and may also connect the O-RU 212 to the SMO framework 206. The O-DU 210 may use the M-Plane to manage the O-RU 212, while the SMO framework 206 is able to provide FCAPS (Fault, Configuration, Accounting, Performance, Security) services to the O-RU 212. The M-Plane is used by the O-DU 210 to retrieve the capabilities of the O-RU 212 and to send relevant configuration related to the C-Plane and U-Plane (data plane) to the O-RU 212.

[0044]

[0040] In one of deployment scenario of the O-RAN architecture 200, the O-RU 212 may be deployed in a telecom site and the O-DU 210 and the SMO framework 206 may be deployed in cloud. In another deployment scenario of the O-RAN architecture 200, both the O-RU 212 and the O-DU 210 may be deployed at the telecom site and the SMO framework 206 may be deployed in the cloud. In both deployment scenarios, the O-RUs 212 may be powered by power supply from various power sources including direct electricity supply (e.g., from a power grid) and renewable power sources such as solar power and wind power. A battery back-up may also be provided with various power sources to supply power in emergency scenario to the O-RUs 212 e.g., when the power source is not supplying the required power. Since the O-RUs 212 are power-intensive components of the communication system, most power-saving initiatives focus on optimizing energy efficiency of the O-RUs 212.

[0045]

[0041] Network energy saving is also of utmost importance for environmental sustainability, to reduce environmental impact (greenhouse gas emissions), and for operational cost savings. To minimize energy consumption and reduce operational costs and environmental impact, it is essential to coordinate with power sources to efficiently manage power sources powering the O-RUs 212. In order to coordinate with the power sources, power source related information (or power source information) such as an alarm or an alert from a power source powering the O-RU 212 are transmitted to an associated O-DU 210 or the SMO framework 206 for taking suitable actions. In existing architectures, the power source information is transmitted to the O-DU 210 or the SMO framework 206 via a separate transport network or interface which is different from existing transport network(s) / interface(s) between the O-RU 212, O-DU 210, and the SMO framework 206. How ever, establishing a separate transport network or interface only for transmitting the power source information may incur additional cost and may cause additional complexities to coordinate with the power sources. In other words, establishing a separate dedicated transport netw ork or interface to communicate between the pow er sources and the O-DU 210 or the SMO framew ork 206 may cause additional computational / design complexity and require additional power.

[0046]

[0042] The techniques of the present disclosure provide seamless power coordination without additional netw ork costs or complexities. Specifically, the techniques of the present disclosure leverage existing transport interfaces to communicate power source information, thereby reducing environmental impact, operational costs, and infrastructure overhead while providing reliable power management for O-RUs 212.

[0047]

[0043] FIG. 3 illustrates a high-level block diagram of an example communication system 300 in which one or more O-RUs 212 are deployed at a telecom site 302 and both O-DU(s) 210 and the SMO framework 206 are deployed on a cloud 304. The communication system 300 uses an existing interface between the one or more O-RUs 212 and the O-DUs 210 for communicating power source information between the O-RUs 212, and the O-DUs 210 and the SMO framework 206, in accordance with some embodiments of the present disclosure.

[0048]

[0044] FIG. 4 illustrates a high-level block diagram of an example communication system 400 in which both the one or more O-RUs 212 and the O-DUs 210 are deployed at the telecom site 302 and the SMO framework 206 is deployed on the cloud 304. Similar to FIG. 3, the communication system 400 also uses an existing interface between the one or more O-RUs 212 and the O-DUs 210 for communicating power source infomiation between the one or more O- RUs 212, and the O-DUs 210 and the SMO framework 206, in accordance with some embodiments of the present disclosure.

[0049]

[0045] The communication systems 300, 400 may include at least one intermediate Information and Communications (ICT) equipment such as at least one Next Generation Control Unit (NG-CU) 306 and at least one Next Generation Data Generation Unit (NG-DGU) 308. Each NG-DGU 308 and the NG-CU 306 may be associated with at least one other entity 310 e.g., via a non-standardized interface or a non-standardized protocol. The at least one other entity 310 may include a site equipment, one or more power sources, and one or more site control units. The one or more power sources may supply power to the one or more O-RUs 212. The power sources may include at least one of a renewable power source, a non-renewable power source, or a batery-based power source. As an example, the renewable power source may be, without limitation, solar power source, wind power source, and hydro power source. As an example, the non-renewable power source may be, without limitation, thermal power source which may use coal, natural gas and oil to generate power.

[0050]

[0046] In one example, each O-RU 212 may be connected with the intennediate ICT equipment e.g.. the NG-DGU 308 or the NG-CU 306, as shown in FIG 3-4. Here, the NG-DGU 308 or the NG-CU 306 may be external to the O-RU 212. An interface between the O-RU 212 and the NG-DGU 308 / NG-CU 306 may be standardized. In one example, the NG-DGU 308 and the NG-CU 306 may be Internet Of Things (loT) devices, Narrowband loT (NB loT) devices, but not limited thereto. In such example, a telemetry module of the O-RU 212 and the ICT equipment may be connected with Wi-Fi or a cellular network (e.g.. 4G, 5G), so that the ICT equipment may wirelessly report power related information to the O-RU 212. Each of the NG-DGU 308 or the NG-CU 306 may act as a power management system (PMS) for exposing power source information the O-RU 212. The interface between the PMS and the O-RU 212 may be standardized. In the present disclosure, the PMS may include the NG-DGU 308, the NG-CU 306, and / or any control panel.

[0051]

[0047] The NG-DGU 308 and the NG-CU 306 may gather power source information and provide the power source information to the O-RU 212 and the O-RU 212 may use an existing interface between the O-RU 212, O-DU 210, and the SMO framework 206 to transmit the power source information to the O-DU 210 and the SMO framework 206, as show n in FIG. 3- 4. In another embodiment, as shown in FIG. 4, the NG-DGU 308 and the NG-CU 306 may directly provide the power source information to the O-DU 210 (as the O-DU 210 is deployed at the telecom site) to reduce transmission delays.

[0048] In accordance with the present disclosure, the O-RU 212 may comprise an internal power unit (PU) 312, as shown in FIG. 3-4. The PU 312 may comprise a general purpose I / O (GP1O) card and / or a telemetry module acting as a data aggregation unit for collecting external power source information. The external entities NG-DGU 308 or the NG-CU 306 may report the power source information to the PU 312 and the PU 312 may provide the power source information to the O-RU 212 that may transmit relevant power source information to the O- DU 210 and the SMO framework 206.

[0052]

[0049] The SMO framework 206 and the O-DU 210 need to know a type of an external power source 310 powering an O-RU 212. so that energy saving may be planned depending on the external power source 310. In the present disclosure, Network Configuration Protocol (NETCONF) and Yet Another Next Generation (Y ANG) based data models may be utilized to facilitate coordination with the external power source 310 and communicate power source information to the O-DU 210 and / or SMO framework 206.

[0053]

[0050] The PMS (e.g., the NG-DGU 308, NG-CU 306) may generate specific power-related parameters that need to be exposed to the O-RU 212. The power-related parameters may be exposed and sent as a file to the O-RU 212. A format of the file may be standardized as per industry -standard formats (e.g., JavaScript Object Notation (JSON), Extensible Markup Language (XML), Hypertext Markup Language (HTML), Comma-Separated Values (CSV), etc.) to maintain consistency across different PMS and the O-RUs 212. A list of parameters to be included in the file may also be standardized. In one example, a new object in YANG model may be created to expose the file shared by the PMS 306, 308 to the O-RU 212. The file may be sent by the O-RU 212 to the O-DU 210 and then to the SMO 206 using existing file management operations. The file transmission may be triggered periodically or event-driven (e.g., power source change, battery' low alert).

[0051] In the O-RAN architecture, the O-RU 212 may coordinate with the external power source 310 using a standardized NETCONF / Y ANG interface between the O-RU 212 and the external power source 310 to gather the power source information. In another example, the O- RU 212 may coordinate with the external power source 310 using a standardized interface between the O-RU 212 and the intermediate ICT equipment that exposes the power source information. A yang module "hardware. yang" may be extended to include a power-supply identity. For example, Request for Comments (RFC) 8348 defines an identity "POWER SUPPLY” which may be added in the yang model (e.g., "o-ran -hardware. yang” module) to represent power supply related components. In one example, the O-RU 212 may indicate presence and label of its physical connectors of specific type. The O-RU 212 connectors may be exposed through o-ran-hardware.yang module as objects of class “O-RU-CONNECTOR”.

[0052] The O-RU 212 may provide information related to the external power source 310 to the O-DU 210 e.g., whether the O-RU 212 is running on a battery backup (or battery based power source), a renewable power source, or a non-renewable power source. The power source information is exposed to the O-DU 210 using the “POWER-SUPPLY” class in the o-ran- hardware.yang module. The reported power source information may include various details related to the external power source 310 such as a label specifying a type of the external power source 310; one or more notifications indicating a change of the external power source 310 (if any) along with relevant parameters (e.g., battery' capacity); and alarms indicating a low battery state (e.g., if battery' backup of the based power source drops below a threshold e.g., 80%). The reported power source information may further include periodic power supply statistics information to enable the O-DU 210 to make informed decisions regarding energy' -saving strategies.

[0053] Once the O-DU 210 receives the power source information from the O-RU 212, the O-

[0054] DU 210 may forward the received information to either non-RT RIC 202 of the SMO framework 206 or to the near RT RIC 204, where the received may be analyzed and translated into appropriate actions. In one example, if the O-RU 212 is operating on battery based power source and battery level of the battery based power source is below a threshold battery level (e.g., reaching less than 90% depletion level), the SMO framework 206 may trigger appropriate active to be the taken by the O-DU 210. In another example, the SMO 206 may provide one or more policies or configurations to the O-DU 210 through the O1 interface, instructing the O- DU 210 to take necessary course of action. For instance, when an O-RU 212 is running on battery based power source and battery level falls below a threshold battery’ level (e.g., less than 80%), the O-DU 210 may implement energy-saving mechanisms such as activating specific Sleep Modes (e.g., Sleep Mode #0, #1, or #2) or applying power-efficient configurations like TRx Control Configuration #1 or Symbol Blanking (STO) to reduce power consumption.

[0055]

[0054] In some examples, the operator may utilize power source information to determine an optimal external power source for the O-RU 212. If multiple external power sources 310 are available, real-time monitoring of power source infonnation may allow for dynamic switching between power sources to maximize efficiency and sustainability’.

[0056]

[0055] FIG. 5 illustrates an exemplary’ call flow diagram 500 between a Distributed Unit (DU)an O-DU 210, an O-RU 212, and a management entity7, in accordance with some embodiments of the present disclosure. The O-DU 210 and the O-RU 212 may be communicatively coupled via a fronthaul interface (e.g., FH MP interface). The O-RU 212 and the O-DU 210 may be configured to communicate using NETCONF YANG based data model. The O-RU 212 may be powered by an external power source 310 which may comprise one of a renewable power source, a non-renewable power source, or a battery based power source.

[0057] The management entity (ME) may comprise one of a Near-RT RIC 204 coupled with the O- DU 210 over the E2 interface or a Non-RT RIC 202 associated with a SMO Framework 206 and coupled with the O-DU 210 over an 01 interface.

[0058]

[0056] The O-RU 212 may be associated with an intermediate ICT equipment or a PMS 306, 308 which may include aNG-DGU 308 and / or a NG-CU 306. The O-RU 212 may comprise a power unit 312 that supports data collection from the external power sources 310. The power unit 312 may be connected with the PMS 306, 308 for receiving the power source infomration. Hence, the external power sources 310 may be connected to the PMS 306. 308 which may continuously monitor the external power sources 310 and gather power source information from the external power sources 310. The PMS 306, 308 may process and transmit the received power supply information to the po -er unit 312 of the O-RU 212. The O-RU 212 may provide the received power supply information to the O-DU 210 over the fronthaul M-plane interface for improving to network energy efficiency, as explained in the forthcoming paragraphs.

[0059]

[0057] \t operation SI, the O— RU 212, which is powered b the external power source 310, may expose its capability or capability' infomration to support external power source coordination feature. This capability may be communi cated / exposed using the o-ran-module- cap.yangmoA\Ac, which defines module capabilities for the O-RU 212. Specifically, the O-RU 212 may infomr the O-DU 210 (e.g., over the FH MP interface) that the O-RU 212 includes a pow er unit 312 that supports data collection from external power sources 310. The O-RU 212 may expose the capability infomration in different ways. In one example, the O-RU 212 may proactively expose basic capability information at the time of initialization or startup. In this case, the O-DU 210 may immediately recognize that the O-RU 212 supports external powder source coordination and may interact accordingly. In another example, if the O-RU 212 does not expose capability information at startup, the O-DU 210 may dynamically query and obtain capability information from the O-RU 212 when required. For instance, the O-DU 210 may actively retrieve the capability information by sending a subscription request to the O-RU 212.

[0058] In this manner, the O-DU 210 receives the capability infonnation that is exposed by the O-RU 212 and indicates whether the O-RU 212 supports the external power source coordination feature. Once the capability information is received, the O-DU 210 may determine whether the O-RU 212 supports the external power source coordination for efficient power management within the O-RAN architecture.

[0060]

[0059] At operation S2, the O-RU 212 may be connected with the external power source 310 which may be a renewable power source, a non-renewable power source, or a battery’ based power source. The operation S2 may occur before operation SI as well. The O-RU 212 may be connected to the external power source 310 through the PMS 306, 308 which facilitates power coordination and monitoring.

[0061]

[0060] At operation S3, the O-DU 210 may retrieve or identify the external power source 310 associated with the O-RU 212 by leveraging the hardware.yang module during startup process. Specifically, in response to determining that the O-RU 212 supports the external power source coordination feature (as determined in operation SI), the O-DU 210 may identify a type of the external power source 310 e.g., whether the power source 310 is a renewable power source, a non-renewable power source, or a battery based power source. The power unit 312 within the O-RU 212 may be responsible for gathering power source information from the PMS 308, 306 which acts as an intermediary’ between the external power sources 310 and the O-RU 212. The PMS 308, 306 may be designed to manage multiple power sources and may have dedicated ports for different types of power sources. Based on which port is in use, the PMS 308, 306 determines the type of power source powering the O-RU 212 and transmits this infonnation to the power unit 312 of the O-RU 212.

[0062] 1061] Once the O-RU 212 receives the power source information indicating the type of power source from the PMS 308, 306, the O-RU 212 transmits the information to the O-DU 210 using the NETCO F / YANG-based O-RAN fronthaul M-plane interface. This communication explicitly indicates a type of the external power source 310 being used thereby allowing the O- DU 210 to identify the power source and make informed energy management decisions. In some implementations, rather than waiting for the O-RU 212 to provide the power source information, the O-DU 210 may take a proactive approach by sending a request to the O-RU 212 to retrieve the power source information. In response, the O-RU 212 may transmit a reply message specifying the type of the power source 310 currently being used.

[0063]

[0062] At operation S4, the management entity may retrieve or identify the power source information of the O-RU 212. Specifically, once the O-DU 210 has retrieved / identified the power source information identifying the type of power source, the O-DU 210 may share the power source information with the management entity. The O-DU 210 may share the power source information via the 01 interface for Non-RT RIC 202 or may share via the E2 interface for Near-RT RIC 204. In one example, the O-DU 210 may proactively send power source information to the management entity' or the management entity may query the O-DU 210 to retrieve the pow er source information identify ing the type of power source.

[0064]

[0063] At operation S5, O-RU 212 may transmit a power source / supply change notification to the O-DU 210 whenever there is a change in the external power source 310 powdering the O- RU 212. The NETCONF / Y ANG-based notification mechanism may be used to convey the power source change update to the O-DU 210 over the Fronthaul (FH) M-plane interface. The O-RU 212 may continuously monitor its external power source 310 through the power unit 312 and the PMS 306, 308. Whenever a change of the external power source 310 is detected, a power source change event may be triggered. Such event may be triggered when a primary power source fails or becomes unstable, a scheduled or automated power source switch occurs for energy optimization (e.g., a solar power source may not be sufficient to power the O-RU 212 during night time or during bad weather), battery based power source is activated due to an outage of the primary power source.

[0065]

[0064] When the power source change occurs to another or a new external power source, the O-RU 212 may generate a NETCONF / YANG-based notification (e.g., power supply change notification) and sends it over the FH-MP interface to the O-DU 210. The notification may be structured using the o-ran-operations.yang module. The notification may be accompanied by information comprising characteristics of the other or new external power source such as a type of the new external power source, a reason for power source change, a battery level of the new external power source (if the new power source is battery-based), but not limited thereto. In one example, once the O-DU 210 detects the change of the external power source, the O-DU 210 may share the pow er source information identifying a type of the new pow er source with the management entity.

[0066]

[0065] At operations S6-S7, the O-RU 212 may continuously monitor a pow er level of the external power source 310. If the power level falls below a predefined threshold level, the O- RU 212 may generate and transmit an alarm notification to the O-DU 210 via the FH-MP interface. In other words, the O-DU 210 may receive the alarm when a power level of the external power source / supply falls below the predefined threshold value. In operation S6, the powder unit 312 within the O-RU 212 may continuously monitor the pow er level of connected external power source 310 based on power source information received from the PMS 308, 306. In operation S7, when the pow er level falls below the predefined threshold level, the O- RU 212 may generate and transmit an alarm notification or event using NETCONF / YANGbased notifications over the FH-MP interface.

[0067]

[0066] For example, when the O-RU 212 operates on a battery-based power source, a battery level of the power source may naturally drain over time due to continuous energy consumption. The O-RU 212 may actively monitor the battery level and upon determining that the battery level of the power source is draining, the O-RU 212 trigger alarm notification when the battery level reaches below a predefined threshold level. Similarly, if the O-RU 212 is powered by a solar-based renewable power source, energy availability may fluctuate due to environmental factors. For instance, solar power generation decreases significantly during nighttime or during adverse weather conditions such as cloudy days. If the solar power level drops below a predefined threshold level, the O-RU 212 may transmit an insufficient solar energy alarm notification to the O-DU 210.

[0068]

[0067] Such early warning or alarm notifications allow the management entity to take proactive measures, such as switching to an alternative power source or optimizing power consumption to extend operational longevity . The alarm notifications may include information indicating an alarm ty pe (e.g., low power level), remaining battery percentage (if applicable), estimated remaining runtime (e.g., battery may last for 30 minutes), a reason for alarm (e.g., solar power insufficient), but not limited thereto. It may be noted that the operations S6-S7 pertain to the external power source 310 which is currently supplying power to the O-RU 212. For instance, if the external power source was changed in operation S5, then the operations S6- S7 (or the alarm notification) pertain to the new external power source 310.

[0069]

[0068] At operation S8, the O-RU 212 may transmit power supply statistics information to the O-DU 210 or O-DU 210 may receive power supply statistics information from the O-RU 212. The power supply statistics information may be associated with the external power source 310 and may be continuously collected or gathered using the PMS 306, 308 associated with the O- RU 212. This power supply statistics information may provide information and insights related to a status and performance of the external power source 310, which helps in efficient power management and optimization within the O-RAN architecture. It may be noted that the power supply statistics information pertains to or is associated with the external power source 310 which is currently supplying power to the O-RU 212. For instance, if the external power source was changed in operation S5, then the power supply statistics infonnation pertains to the new external power source 310.

[0070]

[0069] The power supply statistics information associated with the external power source 310 may comprise one or more parameters, as shown in Table A below:

[0071]

[0070] Table A:

[0072]

[0071] At operation S9, the 0-DU 210 may transmit the power supply statistics information to the management entity (e.g., over the 01 interface) for determining one or more energymanagement policies or configurations for the O-RU 212. The management entity may process the received power supply statistics information to determine the most efficient energymanagement policies for the O-RU 212. Specifically, the management entity may process various types of data such as the received power supply statistics information (communicated via 01 interface), network traffic and load information (communicated via E2 interface), environmental and external data (communicated via external Application Programming

[0073] Interfaces (APIs)), operator-defined energy efficiency goals, but not limited thereto. The various types of data may be processed / analyzed by leveraging Al / ML-driven analytics, rulebased algorithms, and historical trends to determine the one or more energy management policies tailored to current power conditions of the O-RU 212. Once the one or more energy management policies are formulated, the management entity may transmit the energy management policies back to the O-DU 210.

[0074]

[0072] FIG. 5 shows that the management entity as the SMO framework 206. However, the present disclosure is not limited thereto and the management entity may comprise one of: the SMO framework 206, the Near-RT RIC 204 coupled with the O-DU 210 over the E2 interface, or the Non-RT RIC 202 associated with the SMO framework 206 and coupled with the O-DU 210 over the 01 interface.

[0075]

[0073] At operation S10, the O-DU 210 may receive the one or more energy management policies from the management entity. The one or more energy management policies may comprise one or more actions to be undertaken for energy savings at the O-RU 212. The one or more actions may comprise activating at least one energy saving mode for the O-RU 212, redistributing traffic of the O-RU 212 to at least one other O-RU 212, entering the O-RU 212 into an advanced sleep mode, or switching the O-RU 212 to an alternative power source, but not limited thereto.

[0076]

[0074] At operation Sil, the O-DU 210 may activate the one or more appropriate energy saving (ES) features for the O-RU 212 by instructing the O-RU 212 to undertake at least one action of the one or more actions. For example, the O-DU 210 may activate the energy saving mode for the O-RU, in which the O-DU 210 may instruct the O-RU 212 (e.g., using O-RAN fronthaul commands) to reduce power consumption by lowering transmission power when traffic demand is low, reducing a number of active antenna elements, but not limited thereto.

[0077] In another example, the O-DU 210 may redistribute the traffic of the O-RU 212 to the at least one other O-RU 212. If the O-RU 212 is consuming excessive power due to high network traffic or UEs, the O-DU 210 may initiate a handover process (e.g., using Xn or NG interface signaling) to redirect traffic to one or more nearby O-RUs 212 that have lower power consumption or better energy efficiency.

[0078]

[0075] In another example, the O-DU 210 may instruct the O-RU 212 to enter into the advanced sleep mode. Particularly, during periods of low user activity (e.g., night-time or off- peak hours), the O-DU 210 may instruct the O-RU 212 (e.g., over the fronthaul interface) to enter into the advanced sleep mode, where non-essential hardware components may be temporarily deactivated and the O-RU 212 may remain in a low-power state unless traffic demand increases. In another example, the O-DU 210 may instruct the O-RU 212 to switch to the alternative power source. Particularly, if a primary power source becomes unstable (e.g., grid failure or battery depletion), the O-DU 210 may instruct the O-RU 212 to switch to a backup power source. In yet another example, if resources of the O-RU 212 are under utilized (i.e., less Physical Resource Block (PRB) scheduling), The O-RU 212 may require less energy / power for processing user traffic. In such cases, the management entity (e.g., the SMO framework 206) may decide to switch power source that can best fit for current processing capability of the O-RU 212 and apply appropriate energy saving features. Specifically, the management entity' may request or provide policies to the O-DU 210 on activating energy saving features for the O-RU 212. The management entity' may identity' less user traffic for O- RU 212 and switch the external power source 310. The management entity may trigger / send commands to the O-DU 210 to activate the energy saving for a given resource requirements and / or the external power source 310. Alternatively, the O-DU 210 may analyze policies and decide to activate energy saving for the O-RU 212. The O-DU 210 may activate an appropriate energy saving feature and transmit an Energy Saving (ES) command to the O-RU 212. The O- RU 212 may process the command and implement the ES feature. The O-RU 212 may enter in an energy saving mode. Once user traffic requirements are restored, the management entity may again switch the external power source 310 and / or active energy saving features e.g., using the same above-discussed procedure.

[0079]

[0076] In one example of operation S9, the O-DU 210 may transmit data / information from operations S5-S7 (whichever is applicable) to the management entity along with the power supply statistics information to the management entity for determining the one or more energy management policies for the RU. Specifically, the O-DU 210 may transmit at least one of the alarm notification, the power supply change notification, or the characteristics of the new external power source along with the power supply statistics information to the management entity . The management entity may then determine the one or more energy management policies for the O-RU 212 based on one or more of: the alarm notification, the power supply change notification, the characteristics of the new external power source, the received power supply statistics information, the network traffic and load information, the environmental and external data, the operator-defined energy efficiency goals, but not limited thereto.

[0080]

[0077] In this manner, techniques of the present disclosure provides enhanced coordination with external power sources by utilizing existing interfaces for intelligent pow er management for the O-RUs 212. The techniques of the present disclosure continuously monitor power sources of the RUs 212 and based on the assessment, the communication system dynamically optimizes network operations, balances energy efficiency and user experience, optimizes energy consumption and operational efficiency of the network. Additionally, the disclosed techniques facilitate environmental adaptability by continuously monitoring fluctuations in renewable energy availability. The disclosed techniques may intelligently adjust energy consumption strategies based on renewable energy variability, thereby providing optimal power utilization, reduced reliance on non-renewable sources, and improved network sustainability.

[0081]

[0078] Referring now to FIG. 6, a flowchart is described illustrating an example method 600 performed by a Distributed Unit (DU) for external power source coordination through a Radio Unit (RU) in a communication system, according to an embodiment of the present disclosure.

[0079] The method 600 may include, at block 602, receiving, at the DU 210. capability information exposed by the RU 212 that is powered by an external power source 310. The capability information received at the DU 210 may indicate whether the RU 212 supports an external power source coordination feature in which the RU may dynamically interact with and manage various external power sources. At block 604, the method 600 may include receiving power supply statistics information from the RU 212. The power supply statistics infonnation may be associated with the external power source 310 and may be collected using a PMS 306, 308 associated with the RU 212.

[0082]

[0080] At block 606, the method 600 may include transmitting the power supply statistics information to a management entity 202, 204, 206 for detenwining one or more energy7management policies for the RU 212. At block 608, the method 600 may include receiving, from the management entity 202, 204, 206, the one or more energy7management policies for the RU 212. At block 610, the method 600 may include activating one or more energy7saving features for the RU 212 based on the received one or more energy7management policies.

[0083]

[0081] FIG. 7 illustrates a block diagram 700 of an apparatus or device, in accordance with some embodiments of the present disclosure. As shown in FIG. 7, the apparatus 700 may include a processor 710, a memory 720, a storage component 730, an input component 740, an output component 750, a communication interface 760, a bus 770, but not limited thereto.

[0084]

[0082] The processor 710, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 710 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and / or one or more single core processors, a distributed processing system, or the like. The processor 710 may be a Central Processing Unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), an application-specific integrated circuit (ASIC), or another type of processing component.

[0085]

[0083] The memory 720 includes a non-transitory computer readable medium. The memory 720 includes a random-access memory (RAM), a read only memory (ROM), and / or another type of dynamic or static storage device (e.g., a flash memoiy, a magnetic memory, and / or an optical memory) that stores information and / or instructions for use by processor 710. The memory' 720 comprises machine-readable instructions which are executable by the processor 710. These machine-readable instructions when executed by the processor 710 cause the processor 710 to perform one or more method steps of an embodiment described in the present disclosure.

[0086]

[0084] The storage component 730 stores information and / or software related to the operation and use of the apparatus 700. For example, the storage component 730 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and / or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another ty pe of non-transitory computer-readable medium, along with a corresponding drive.

[0085] The input component 740 is configured to receive information, such as user input. For example, the input component 740 may include, but not be limited to, a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone. Additionally, or alternatively, the input component 740 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gyroscope, and / or an actuator).

[0087]

[0086] The output component 750 is configured to provide output information from the apparatus 700. For example, the output component 750 may be. but not limited to, a display, a speaker, an instruction device to an external device, and / or one or more light-emitting diodes (LEDs).

[0088]

[0087] The communication interface 760 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 760 can be a wired connection, a wireless connection, or a combination of wired and wireless connections, and can be a direct connection or an indirect connection via a communication network that exists between the apparatus 700 and other devices. In other words, the standard of the communication interface 760 is not limited.

[0089]

[0088] The bus 770 acts as an interconnect between the processor 710, the memory 720, the storage component 730, the input component 740, the output component 750, and the communication interface 760 of the apparatus 700. The bus 770 may include a wired interconnection or a wireless interconnection.

[0090]

[0089] The number and arrangement of components shown in FIG. 7 are provided as an example. In practice, the apparatus 700 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 7. Additionally, or alternatively, a set of components (e.g., one or more components) of the apparatus 700 may perform one or more functions described as being performed by another set of components of the apparatus 700. Further, one or more method steps described in any of the embodiments may be performed utilizing a plurality of apparatuses 700 in communication with one another.

[0091]

[0090] In one non-limiting embodiment, the apparatus 700 may be used to implement some or all functions of any entity including UEs, various network entities of the O-RAN / RAN, various entities of the core network, but not limited thereto. Specifically, the apparatus 700 may implement the functionalities of the O-DU 210, O-RU 212, SMO framework 206.

[0092]

[0091] Additional description:

[0093]

[0092] In the present disclosure, there may be certain requirements on the Front Haul (FH). For example, the O-DU 210 and the SMO 206 (through the O-DU) may identify a power supply class. This class may be leveraged for defining and exposing the power source information by the O-RU 212. Various notifications may be defined for the FH e.g., for change of power source. As an example, notification for power source switched from Electricity Board (EB) supply or solar power to battery back-up and so on. Various alarms may be defined for the FH. For example, a battery back-up threshold is low or critical then an alarm may be defined to indicate low battery back-up to prolong the RU sendee. Critical alarm may be defined on battery drain or solar power is not sufficient due to various reason.

[0094]

[0093] A list of parameters to be reported as part of power supply statistics information (pow er supply availability) may include parameters that can be exposed by an O-RU 212 regarding power supply statistics, including information on power source availability, capacity, remaining batten backup, renewable power, and EB supply. The exemplary parameters are shown in Table A above. Additionally, some example parameters to be exposed are defined in Tables B and C, below :

[0095]

[0094] Table B:

[0096]

[0095] Table C:

[0097]

[0096] Exposing the power source information: Exposing the power source information (which comprises one or more parameters) may include integrating the PMS with the O-RU 212. Integrating the PMS with the O-RU to expose the power source information may involve several steps. This integration ensures that the O-RU may monitor and report on various power- related parameters through standardized interfaces.

[0098]

[0097] The steps for integration are discussed below.

[0099] (1). Identify capabilities:

[0100] • Determine types of power sources (e.g., battery, solar, EB) and the parameters that the PMS may monitor and control.

[0101] • Ensure that the PMS may communicate these parameters through a standardized protocol. (2). Select a standardized interface:

[0102] • O-RAN fronthaul interface (Open fronthaul): The O-RAN defines the open fronthaul interface, which may be used to communicate betw een the RU and the PMS.

[0103] • 3GPP management interface: The 3GPP defines management interfaces that can be used for monitoring and control. The management interfaces may include NETCONF / YANG, Simple Network Management Protocol (SNMP).

[0104] • ETSI NFV MANO interface: ETSI Network Functions Virtualization Management and Orchestration interfaces may also be used for integrating power management functions.

[0105] (3). Define data models and protocols:

[0106] • Use standardized data models such as YANG (Yet Another Next Generation) for NETCONF or MIBs (Management Information Bases) for SNMP.

[0107] • Ensure the PMS supports these data models to expose power-related parameters.

[0108] (4). Implement communication protocols:

[0109] • NETCONF / Y ANG: Implement NETCONF protocol on the O-RU to communicate with the PMS using YANG data models.

[0110] • SNMP: Implement SNMP agents on the O-RU to query and receive traps from the PMS.

[0111] • RESTful Application Programming Interfaces (APIs): If the PMS supports RESTful APIs, implement REST clients on the RU to fetch power-related information.

[0112] (5). Select a standardized interface:

[0113] • Develop software modules on the O-RU to interface with the PMS.

[0114] • These modules should be capable of: querying the PMS for power source information, receiving notifications or traps from the PMS, exposing the received information through the O-RU’s management interface.

[0115] (6). Testing and Validation: • Test integration in a controlled environment to ensure that the O-RU correctly receives and exposes power source information.

[0116] • Validate the accuracy and reliability of the data being reported.

[0117]

[0098] Example integration of the PMS with an O-RU using NETCONF / Y ANG is described below:

[0118] • Define YANG Model for power management.

[0119] • Implement a NETCONF client on the O-RU: develop a NETCONF client on the O-RU to query the PMS using the defined YANG model.

[0120] • Expose Information via RU management interface: ensure the O-RU’s management interface (e.g., NETCONF, SNMP) is configured to expose the power source information received from the PMS.

[0121]

[0099] In the integration of the PMS with the O-RU using NETCONF / Y ANG, the YANG model is defined first, as described below:

[0122] • The YANG model may be defined to represent the power management system’s various parameters, including battery status, power supply status, and alarm states.

[0123] • Create YANG models that define the power management parameters such as voltage, current, State Of Charge (SoC), State Of Health (SoH), temperature, and alarms.

[0124] • NETCONF RPC may be formulated to fetch power source information.

[0125] • The PMS may act as a NETCONF server, exposing the YANG model-defined data.

[0126] • Connect the O-RU to the PMS using an Ethernet cable. Ensure both O-RU and PMS are part of the same network or have proper routing between them.

[0127] • Utilize standard networking protocols such as Transmission Control Protocol / Intemet

[0128] Protocol (TCP / IP) for reliable data transfer. • Assign IP addresses to both the O-RU and the PMS so that they may communicate over a network.

[0129] • Use wireless technologies such as Wi-Fi or cellular communication if the O-RU and PMS are in locations where cabling is impractical. NB-IoT Devices may also be employed.

[0130]

[0100] In some embodiments, the present disclosure describes common API definition for coordination with external power sources, as follows:

[0131] • Overview o Purpose: standardize a communication interface for Power, Energy, and Environmental (PEE) data from site equipment, power units, building control units, and base stations (BSs). o Scope: the API serves as the primary interface for interactions between Network Management Systems (NMS) and Entry Points, as well as between Entry Points and NG-CU(s) / NG-DGU(s).

[0132] • Key Functions o Data collection requests: the NMS can request PEE data from the site equipment, power units, building control units, and BSs. o Configuration: the NMS may assign values to configurable parameters related to the PEE data and set threshold values to receive alarms when these thresholds are crossed. o Notifications: the NMS may subscribe to notifications such as alarms and event notifications related to PEE data, NG-CU(s), and NG-DGU(s).

[0133] • API Capabilities o Data sending: the NG-CU, NG-DGU, and entry points may send the PEE data to the

[0134] NMS. o Alarm issuance: the alarms are sent to subscribed NMS when configured thresholds are crossed. o Event notifications: The event notifications may be issued to subscribed NMS for configuration changes and other significant events.

[0135]

[0101] In some embodiments, the present disclosure describes common protocol for exposing the external power source information, as follows:

[0136] • Overview o Purpose: recommend state-of-the-art communication protocols for various APIs. o Protocol: a secured RESTful HTTP-based communication is recommended, with payloads in JSON or yet another markup language (Y AML).

[0137] • Integration with BS OA&M Channel o Embedding entry point in BS: In certain scenarios, the BSs can embed the entry point to ensure that PEE data from site equipment, power units, and building control units is carried to the NMS over the NMS channel of the BSs. o Encrypted data transmission: PEE data transported through the BS NMS channel may be encrypted, ensuring it is only meaningful to the NG-CU. NG-DGU, entry points, and the NMS.

[0138] • Vendor requirements o PEE data description file: Vendors of site equipment, power units, and building control units must provide a PEE data Description File to Mobile Network Operator (MNO) / Tower Companies / Master Operators, detailing the data model supported by their NG-CU / NG-DGU. o Procedure:

[0139] Vendors supply the PEE data Description File. • MNO / Tower Companies integrate the file into their NMS for control and monitoring.

[0140] • Installation and plug-and-connect procedures are triggered to recognize new equipment and units.

[0141] • The NMS can then request and collect the PEE data from the newly installed equipment.

[0142]

[0102] The present disclosure provides enhanced coordination with power sources which enables the O-RUs to report a type of power source which may be renewable power source or non-renewable power source and available capacity of the power source using a YANG model. This reporting may include detailed information such as remaining battery life. This sophisticated approach assesses whether an O-RU is powered by finite sources like batteries or sustainable sources such as wind energy or solar energy. Based on this assessment, the communication system may dynamically adjust operations, prioritize either energy savings and user experience or both energy savings and user experience. This power source information is transmitted from the O-RU to the O-DU and then to the SMO framework using an existing interface between these entities, ensuring that the communication system may make informed decisions to optimize energy consumption and operational efficiency. The present disclosure helps in environmental adaptability, monitors the variability of renewable power sources and adjusts the network’s energy consumption accordingly.

[0143]

[0103] The concept of an O-RU reporting power source information to the O-DU and the SMO framework may involve using a sophisticated approach to monitor and manage the energy / power sources powering the O-RU. The techniques provided by the present disclosure may include following aspects:

[0104] (a). Power Source Awareness and Reporting: The O-DU may handle power source information rather than the O-RU, as the O-DU may manage network-wide power consumption better. According to the present disclosure the O-RU may report power source information to the O-DU through M-Plane measurements.

[0144]

[0105] (b). Enhanced Coordination with Power Sources: According to the present disclosure the O-RU may report a type of power source and its available capacity, enabling the communication system to adjust operations based on power source reliability. Further, the power source information may be transmitted from the O-RU to the O-DU and the SMO framework or near-RT RIC.

[0145]

[0106] (c). Enhanced Coordination with Power Sources: The present disclosure emphasizes on the O-DU managing power source information and adjusting O-RU power consumption based on advanced sleep modes. Concerns about devolving this function to the O-RU, which generally lacks network-wide context is addressed by emphasizing on the O-DU.

[0146]

[0107] (d). Power Source Information Reporting: The Power Source Information Reporting may include:

[0147] • O-RU Monitoring: The O-RU may continuously monitor its power sources distinguishing between renewable (e.g., solar, wind) and non-renewable (e g., battery', grid) sources. The O-RU may assess parameters like available capacity and remaining battery' life.

[0148] • Netconf Yang Model: The O-RU may use, without limitation, the Netconf protocol with a Yang model to format and report the power source information which includes details on the ty pe of power source, its capacity, current charge level, and other relevant metrics.

[0149]

[0108] (e). Dynamic Adjustment Based on Power Source:

[0150] » O-DU’s Role: The O-DU may receive power source information from the O-RU. The O-DU may use the power source information to make real-time decisions about energy consumption and traffic management. For instance, if a battery level of the power source drops below 60%, the O-DU may activate energy-saving modes or redistribute traffic to other O-RUs with more stable power sources.

[0151] • Advanced Sleep Modes: By estimating traffic demand and considering power source characteristics, the O-DU may instruct the O-RU to enter into the advanced sleep modes to conserve energy.

[0152]

[0109] (1). Service Management and Orchestration (SMO) Integration:

[0153] • Energy Management: The SMO framework or the near-RT RIC may receive aggregated power source data from multiple O-DUs and uses the received data / information to plan and implement network-wide energy-saving strategies.

[0154] • Policy Enforcement: Based on power source data / reports, the SMO framework may enforce policies to optimize energy use across the communication system, and prioritize user experience or energy savings as needed.

[0155]

[0110] (g). Handling Power Source Variability:

[0156] • Renewable Energy Management: Renewable power sources like solar or wind may be unpredictable. The techniques of the present disclosure may continuously monitor these sources, adjust operations based on their availability. For example, during cloudy weather, solar power may be insufficient, triggering a switch to battery or grid power.

[0157] • Battery Management: The present disclosure may facilitate keeping track of battery health and charge cycles. The present disclosure ensures that batteries are used efficiently and are recharged appropriately when renewable sources are available.

[0158]

[0111] (h). Future Upgrades and Scalability:

[0159] • Adaptability: As new power sources and technologies emerge, the communication system may integrate these into the existing monitoring and control framework. • Scalability: The techniques of the present disclosure are designed to scale with the network, allowing more O-RUs and diverse power sources to be added without significant changes to the underlying infrastructure.

[0160]

[0112] (i). Detailed Information Exchange:

[0161] • Information Elements: Specific parameters to be exchanged over the Netconf Yang model include: a type of power source (renewable / non-renewable), a cunent capacity and status of the power source, remaining battery life and health indicators, environmental conditions affecting power source performance (e.g., weather for solar / wind power sources), etc.

[0162] • Extensible Markup Language (XML) / JavaScript Object Notation (JSON) formats: The information can be structured in XML or JSON formats for efficient processing and transmission.

[0163]

[0113] In the present disclosure, a PMS or ICT equipment is provided that generates required parameters to be exposed and sends as a file to O-RU. The file format may be standardized e.g., based on existing standards and the list of parameters to be exposed may be standardized. The techniques of the present disclosure discloses creation of an object in Yang model for exposing the file that is shared by the PMS to the O-RU. The file may be sent by the O-RU to the O-DU and then to the SMO framework using existing file management operation. Periodic or event based trigger may be used to retrieve the file or get the file and to post process data present in the file.

[0164]

[0114] Some advanced units may identify a type of power source they are connected to and report this information via telemetry. These units may use remote monitoring tools and network management software to check power source status. Many systems may have built-in telemetry that may report the type of power source. The O-RU may have inbuilt telemetry or the power unit to get the information about the external power source and transfer the external power source information (for e.g., battery along with status and parameters) from the advanced units to O-DU and / or the SMO framework directly. A leaf may be defined in the yang model which is read-only so that SMO / O-DU may query power source status, where this leaf may be associated with inbuilt telemetry that exposes the external power source information.

[0165]

[0115] The techniques of the present disclosure enable the O-RU to effectively monitor and report battery’ backup information, ensuring seamless integration with external power sources and management systems. Such approach ensures interoperability’, reliability, and efficient management of power resources w ithin the O-RAN ecosystem.

[0166]

[0116] Example Items:

[0167]

[0117] Item 1. A method comprising: receiving, at a Distributed Unit (DU), capability information exposed by a Radio Unit (RU) that is powered by an external power source, wherein the capability information indicates whether the RU supports an external power source coordination feature; receiving power supply statistics infonnation from the RU, wherein the power supply statistics information is associated with the external power source and is collected using a Power Management System (PMS) associated with the RU; transmitting the power supply statistics information to a management entity’ for determining one or more energy’ management policies for the RU; receiving, from the management entity’, the one or more energy management policies for the RU; and activating one or more energy’ saving features for the RU based on the received one or more energy management policies.

[0168]

[0118] Item 2. The method of item 1, further comprising: receiving an alarm when a power level of the external powder source falls below a predefined threshold level; and receiving a power supply change notification indicating that the RU switched to a new external powder source, wherein the power supply change notification is accompanied by information comprising characteristics of the new external power source.

[0169] 1119] Item 3. The method of item 2, further comprising: transmitting at least one of the alarm, the power supply change notification, or the characteristics of the new external power source along with the power supply statistics information to the management entity for determining the one or more energy management policies for the RU.

[0170]

[0120] Item 4. The method of any of items 1-3, further comprising: in response to determining that the RU supports the external power source coordination feature, identifying a type of the external power source, wherein the type of the external power source comprises one of a renewable power source, a non-renewable power source, or a battery based power source.

[0171]

[0121] Item 5. The method of any of items 1-4, wherein the one or more energy management policies comprise one or more actions to be undertaken for energy saving at the RU, and wherein the one or more actions comprise: activating at least one energy saving mode for the RU; redistributing traffic of the RU to at least one other RU; entering the RU into an advanced sleep mode; or switching the RU to an alternative power source.

[0172]

[0122] Item 6. The method of item 5, wherein activating the one or more energy saving features for the RU comprises instructing the RU to undertake at least one action of the one or more actions.

[0173]

[0123] Item 7. The method of any of items 1-6, wherein the DU and the RU are part of a Radio Access Network (RAN) and are communicatively coupled via a fronthaul interface, and wherein the RU and the DU are configured to communicate using a Network Configuration Protocol (NETCONF) Yet Another Next Generation (YANG) based data model.

[0174]

[0124] Item 8. The method of any of items 1-7, wherein the management entity comprises one of: a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) coupled with the DU over an E2 interface; or a Non-Real Time (Non-RT) RIC associated with a Service Management and Orchestration (SMO) Framework and coupled with the DU over an 01 interface.

[0175] 1125] Item 9. The method of any of items 1 -8, wherein the power supply statistics information associated with the external power source comprises at least one of a power source type, a power source status, a power source capacity, remaining battery backup, a battery charge level, a battery health status, a renewable power status, a renewable power output, an electricity board (EB) supply status, an EB supply voltage, an EB supply frequency, a power consumption, a power source priority, a power source switch time, total power availability, a power source efficiency, a power source temperature, or a power source load.

[0176]

[0126] Item 10. An apparatus configured to: receive, at a Distributed Unit (DU), capability information exposed by a Radio Unit (RU) that is powered by an external power source, wherein the capability information indicates whether the RU supports an external power source coordination feature; receive power supply statistics information from the RU, wherein the power supply statistics information is associated with the external power source and is collected using a Power Management System (PMS) associated with the RU; transmit the power supplystatistics information to a management entity for determining one or more energy management policies for the RU; receive, from the management entity, the one or more energy management policies for the RU; and activate one or more energy7saving features for the RU based on the received one or more energy- management policies.

[0177]

[0127] Item 11. The apparatus of item 10, further configured to : receive an alarm w hen a power level of the external pow er source falls below7a predefined threshold level; and receive a pow er supply change notification indicating that the RU switched to a new7external pow7er source, wherein the power supply change notification is accompanied by information comprising characteristics of the new external power source.

[0128] Item 12. The apparatus of item 11, further configured to: transmit at least one of the alarm, the power supply change notification, or the characteristics of the new external power source along with the power supply statistics information to the management entity for determining the one or more energy management policies for the RU.

[0178]

[0129] Item 13. The apparatus of any of items 10-11. further configured to: in response to determining that the RU supports the external power source coordination feature, identify a type of the external power source, wherein the type of the external power source comprises one of a renewable power source, a non-renewable power source, or a battery based power source.

[0179]

[0130] Item 14. The apparatus of any of items 10-13, wherein the one or more energy management policies comprise one or more actions to be undertaken for energy saving at the RU, and wherein the one or more actions comprise: activating at least one energy saving mode for the RU; redistributing traffic of the RU to at least one other RU; entering the RU into an advanced sleep mode; or switching the RU to an alternative power source.

[0180]

[0131] Item 15. The apparatus of item 14, wherein to activate the one or more energy saving features for the RU, the apparatus is configured to instruct the RU to undertake at least one action of the one or more actions.

[0181]

[0132] Item 16. The apparatus of any of items 10-15, wherein the DU and the RU are part of a Radio Access Network (RAN) and are communicatively coupled via a fronthaul interface, and wherein the RU and the DU are configured to communicate using a Network Configuration Protocol (NETCONF)Yet Another Next Generation (YANG) based data model.

[0182]

[0133] Item 17. The apparatus of any of items 10-16, wherein the management entity comprises one of: a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) coupled with the DU over an E2 interface; or a Non-Real Time (Non-RT) RIC associated with a Service Management and Orchestration (SMO) Framework and coupled with the DU over an 01 interface.

[0183] 1134] Item 18. The apparatus of any of items 10-17, wherein the power supply statistics information associated with the external power source comprises at least one of a power source type, a power source status, a power source capacity, remaining battery backup, a battery charge level, a battery health status, a renewable power status, a renewable power output, an electricity board (EB) supply status, an EB supply voltage, an EB supply frequency, a power consumption, a power source priority, a power source switch time, total power availability, a power source efficiency, a power source temperature, or a power source load.

[0184]

[0135] Item 19. A non-transitory computer readable media storing one or more computer executable instructions which, when executed by an apparatus, cause the apparatus to: receive, at a Distributed Unit (DU), capability information exposed by a Radio Unit (RU) that is powered by an external power source, wherein the capability infonnation indicates whether the RU supports an external power source coordination feature; receive power supply statistics infonnation from the RU, wherein the power supply statistics information is associated with the external power source and is collected using a Power Management System (PMS) associated with the RU; transmit the power supply statistics infonnation to a management entity for determining one or more energy' management policies for the RU; receive, from the management entity, the one or more energy management policies for the RU; and activate one or more energy saving features for the RU based on the received one or more energy management policies.

[0185]

[0136] Item 20. The non-transitory computer readable media of item 19, wherein the one or more computer executable instructions further cause the apparatus to: receive an alarm when a power level of the external power source falls below a predefined threshold level; receive a power supply change notification indicating that the RU switched to a new external power source, wherein the power supply change notification is accompanied by information comprising characteristics of the new external power source; and transmit at least one of the alarm, the power supply change notification, or the characteristics of the new external power source along with the power supply statistics information to the management entity for determining the one or more energy management policies for the RU.

[0186]

[0137] It may be noted here that the subj ect matter of some or all embodiments described with reference to Figures 1-5 may be relevant for the method 600 and the same is not repeated for the sake of brevity. The language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the disclosure be limited not by this detailed description, but rather by any claims that issue on an application based here on. Accordingly, the embodiments of the present disclosure are intended to be illustrative, but not limiting, of the scope of the disclosure, which is set forth in the appended claims.

Claims

What is claimed is:

1. A method comprising: receiving, at a Distributed Unit (DU), capability information exposed by a Radio Unit (RU) that is powered by an external power source, wherein the capability information indicates whether the RU supports an external power source coordination feature; receiving power supply statistics information from the RU, wherein the power supply statistics information is associated with the external power source and is collected using a Power Management System (PMS) associated with the RU; transmitting the power supply statistics information to a management entity for determining one or more energy management policies for the RU; receiving, from the management entity’, the one or more energy’ management policies for the RU; and activating one or more energy saving features for the RU based on the received one or more energy management policies.

2. The method of claim 1, further comprising: receiving an alarm yvhen a power level of the external power source falls below a predefined threshold level; and receiving a poyver supply change notification indicating that the RU syy itched to a new external poyver source, yyherein the poyver supply change notification is accompanied by information comprising characteristics of the neyv external poyver source.

3. The method of claim 2, further comprising:transmitting at least one of the alarm, the power supply change notification, or the characteristics of the new external power source along with the power supply statistics information to the management entity for determining the one or more energy management policies for the RU.

4. The method of claim 1, further comprising: in response to determining that the RU supports the external power source coordination feature, identifying a type of the external power source, wherein the type of the external power source comprises one of a renewable power source, a non-renewable power source, or a battery based power source.

5. The method of claim 1, wherein the one or more energy management policies comprise one or more actions to be undertaken for energy saving at the RU, and wherein the one or more actions comprise: activating at least one energy saving mode for the RU; redistributing traffic of the RU to at least one other RU; entering the RU into an advanced sleep mode; or switching the RU to an alternative power source.

6. The method of claim 5, wherein activating the one or more energy saving features for the RU comprises instructing the RU to undertake at least one action of the one or more actions.

7. The method of claim 1, wherein the Distributed Unit (DU) and the RU are part of aRadio Access Network (RAN) and are communicatively coupled via a fronthaul interface, andwherein the RU and the DU are configured to communicate using a Network ConfigurationProtocol (NETCONF) Yet Another Next Generation (YANG) based data model.

8. The method of claim 1, wherein the management entity comprises one of: a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) coupled with the DU over an E2 interface; or a Non-Real Time (Non-RT) RIC associated with a Service Management and Orchestration (SMO) Framework and coupled with the DU over an 01 interface.

9. The method of claim 1, wherein the power supply statistics infonnation associated with the external power source comprises at least one of a power source type, a power source status, a power source capacity, remaining battery backup, a battery charge level, a battery health status, a renewable power status, a renewable power output, an electricity board (EB) supply status, an EB supply voltage, an EB supply frequency, a power consumption, a power source priority, a power source switch time, total power availability, a power source efficiency, a pow er source temperature, or a power source load.

10. An apparatus configured to: receive, at a Distributed Unit (DU), capability information exposed by a Radio Unit (RU) that is powered by an external power source, wherein the capability information indicates whether the RU supports an external power source coordination feature; receive powder supply statistics information from the RU, wherein the power supply statistics information is associated with the external power source and is collected using a Power Management System (PMS) associated with the RU;transmit the power supply statistics information to a management entity for determining one or more energy management policies for the RU; receive, from the management entity, the one or more energy management policies for the RU; and activate one or more energy saving features for the RU based on the received one or more energy management policies.

11. The apparatus of claim 10, further configured to: receive an alarm when a power level of the external power source falls below a predefined threshold level; and receive a power supply change notification indicating that the RU switched to a new external power source, wherein the power supply change notification is accompanied by information comprising characteristics of the new external power source.

12. The apparatus of claim 11, further configured to: transmit at least one of the alarm, the power supply change notification, or the characteristics of the new external power source along with the power supply statistics information to the management entity for determining the one or more energy management policies for the RU.

13. The apparatus of claim 10, further configured to: in response to determining that the RU supports the external power source coordination feature, identify a type of the external power source, wherein the type of the external powersource comprises one of a renewable power source, a non-renewable power source, or a batery based power source.

14. The apparatus of claim 10. wherein the one or more energy management policies comprise one or more actions to be undertaken for energy saving at the RU. and wherein the one or more actions comprise: activating at least one energy saving mode for the RU; redistributing traffic of the RU to at least one other RU; entering the RU into an advanced sleep mode; or switching the RU to an alternative power source.

15. The apparatus of claim 14, wherein to activate the one or more energy saving features for the RU, the apparatus is configured to instruct the RU to undertake at least one action of the one or more actions.

16. The apparatus of claim 10, wherein the DU and the RU are part of a Radio Access Network (RAN) and are communicatively coupled via a fronthaul interface, and wherein the RU and the DU are configured to communicate using a Network Configuration Protocol (NETCONF) Yet Another Next Generation (YANG) based data model.

17. The apparatus of claim 10, wherein the management entity comprises one of: a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) coupled with the DU over an E2 interface; ora Non-Real Time (Non-RT) RIC associated with a Service Management and Orchestration (SMO) Framework and coupled with the DU over an 01 interface.

18. The apparatus of claim 10. wherein the power supply statistics information associated with the external power source comprises at least one of a power source type, a power source status, a power source capacity, remaining battery backup, a battery charge level, a battery health status, a renewable power status, a renewable power output, an electricity board (EB) supply status, an EB supply voltage, an EB supply frequency, a power consumption, a power source priority, a power source switch time, total power availability, a power source efficiency, a power source temperature, or a power source load.

19. A non-transitory computer readable media storing one or more computer executable instructions which, when executed by an apparatus, cause the apparatus to: receive, at a Distributed Unit (DU), capability information exposed by a Radio Unit (RU) that is powered by an external power source, wherein the capability information indicates whether the RU supports an external power source coordination feature; receive power supply statistics information from the RU, wherein the power supply statistics information is associated with the external power source and is collected using a Power Management System (PMS) associated with the RU; transmit the power supply statistics information to a management entity for determining one or more energy' management policies for the RU; receive, from the management entity, the one or more energy management policies for the RU; andactivate one or more energy saving features for the RU based on the received one or more energy management policies.

20. The non-transitory computer readable media of claim 19. wherein the one or more computer executable instructions further cause the apparatus to: receive an alarm when a power level of the external power source falls below a predefined threshold level; receive a power supply change notification indicating that the RU switched to a new external power source, wherein the power supply change notification is accompanied by information comprising characteristics of the new external power source; and transmit at least one of the alann, the power supply change notification, or the characteristics of the new external power source along with the power supply statistics information to the management entity for detennining the one or more energy management policies for the RU.

Images