External power source coordination

Abstract

A method, disclosed in the present disclosure, comprises receiving external power source information from one or more external power sources. It further comprises transmitting, to a Service Management and Orchestration (SMO), the external power source information and capabilities of an O-RAN Radio Unit (O-RU) to support external power source coordination. It further comprises receiving, from the SMO, one or more configuration and / or one or more policies for energy saving based on the external power source information and the capabilities of the O- RU. It further comprises performing at least one of, switching to the one or more external power sources and enabling one or more Energy Saving (ES) methods based on the one or more configuration and the one or more policies.

Description

EXTERNAL POWER SOURCE COORDINATIONCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to India Provisional Application No. 202541029689, filed on March 28, 2025, India Provisional Application No. 202541067380, filed on July 15, 2025, India Provisional Application No. 202541069976, filed on July 23, 2025, and India Non-Provisional Application No. 202541029689, filed on March 16, 2026, the entire contents of which are incorporated herein by reference.FIELD

[0002] The present disclosure relates to external power source coordination through Open Radio Unit (O-RU) or Open Distributed Unit (O-DU).BACKGROUND

[0003] Open-Radio Access Network (O-RAN) allows interoperation between cellular network equipment provided by different vendors. O-RAN enables intelligent RAN control by using RAN Intelligent Controllers (RICs). The RICs include Near-Real Time (RT) and Non-RT RICs. The applications such as xApps (Extended application) and rApps (here 'r' stands for RAN) are implemented in Near-RT RIC and Non-RT RIC, respectively. These applications expand the intelligent RAN control capabilities of O-RAN.

[0004] The feature "Co-ordination between O-RU Power Consumption and External Power Source" focuses on optimizing use of energy more efficiently in O-RAN networks. It does this through integrating data on the type of power source (renewable or non-renewable) and its available capacity, such as remaining battery life, to make informed decisions about energy consumption. It uses a sophisticated approach to assess whether an O-RU is powered by a finite source like a battery or a sustainable one like wind or solar energy. Depending on this assessment, the network can dynamically adjust its operations by prioritizing energy savings or user experience.

[0005] 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.SUMMARY

[0006] In an embodiment, the present disclosure discloses a method. The method comprises receiving external power source information from one or more external power sources. Further, the method comprises transmitting, to a Service Management and Orchestration (SMO), the external power source information and capabilities of an Open Radio Unit (O-RU) to support external power source coordination. Thereafter, the method comprises receiving, from the SMO, one or more configuration and / or one or more policies for energy saving based on the external power source information and the capabilities of the O-RU. Finally, the method comprises performing at least one of, switching to the one or more external power sources and enabling one or more Energy Saving (ES) methods based on the one or more configuration and the one or more policies.

[0007] In an embodiment, the present disclosure discloses an Open Radio Unit (O-RU). The O-RU is configured to receive external power source information from one or more external power sources. Further, the O-RU is configured to transmit, to a Service Management and Orchestration (SMO), the external power source information and capabilities of an O-RU to support external power source coordination. Thereafter, the O-RU is configured to receive, from the SMO, one or more configuration and one or more policies for energy saving based on the external power source information and / or the capabilities of the O-RU. Finally, the O-RU is configured to perform at least one of, switching to the one or more external power sources and enabling one or more Energy Saving (ES) methods based on the one or more configuration and the one or more policies.

[0008] In an embodiment, the present disclosure discloses a non-transitory computer readable medium including instructions for performing operations comprising receiving external power source information from one or more external power sources. Further, the operations comprising transmitting, to a Service Management and Orchestration (SMO), the external power source information and capabilities of an Open Radio Unit (O-RU) to support external power source coordination. Thereafter, the operations comprising receiving, from the SMO, one or moreconfiguration and / or one or more policies for energy saving based on the external power source information and the capabilities of the O-RU. Finally, the operations comprising performing at least one of, switching to the one or more external power sources and enabling one or more Energy Saving (ES) methods based on the one or more configuration and the one or more policies.

[0009] In an embodiment, the present disclosure discloses a method. The method comprises receiving, from an Open Radio Unit (O-RU), external power source information and capabilities of the O-RU to support external power source coordination. Further, the method comprises analyzing the external power source information and the capabilities, to determine one or more configurations and / or one or more policies for enabling energy saving at the O-RU. Finally, the method comprises transmitting the one or more configurations and the one or more policies triggering at least one of, switching to one or more external power sources and enabling one or more Energy Saving (ES) methods in the O-RU.

[0010] In an embodiment, the present disclosure discloses a Service Management and Orchestration (SMO). The SMO is configured to receive, from an Open Radio Unit (O-RU), external power source information and capabilities of the O-RU to support external power source coordination. Further, the SMO is configured to analyze the external power source information and / or the capabilities, to determine one or more configurations and one or more policies for enabling energy saving at the O-RU. Finally, the SMO is configured to transmit the one or more configurations and one or more policies triggering at least one of, switching to one or more external power sources and enabling one or more Energy Saving (ES) methods in the O-RU.

[0011] In an embodiment, the present disclosure discloses a non-transitory computer readable medium including instructions for performing operations comprising receiving, from an Open Radio Unit (O-RU), external power source information and capabilities of the O-RU to support external power source coordination. Further, the operations comprising analyzing the external power source information and the capabilities, to determine one or more configurations and / or one or more policies for enabling energy saving at the O-RU. Finally, the operations comprising transmitting the one or more configurations and the one or more policies triggering at least one of, switching to one or more external power sources and enabling one or more Energy Saving (ES) methods in the O-RU.BRIEF DESCRIPTION OF THE DRAWINGS

[0012] 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:

[0013] FIG. 1 illustrates an exemplary architecture illustrating external power source coordination through an Open Radio Unit (O-RU) and / or Service Management and Orchestration (SMO), in accordance with some embodiments of the present disclosure;

[0014] FIG. 2A shows an exemplary call flow diagram illustrating external power source coordination through an Open Radio Unit (O-RU) and / or Service Management and Orchestration (SMO), in accordance with some embodiments of the present disclosure;

[0015] FIG. 2B shows an exemplary call flow diagram illustrating Front Haul (FH) use case during external power source coordination, in accordance with some embodiments of the present disclosure;

[0016] FIG. 3 shows a flowchart illustrating a method of external power source coordination through an Open Radio Unit (O-RU), in accordance with some embodiments of the present disclosure;

[0017] FIG. 4 shows a flowchart illustrating a method of external power source coordination through a Service Management and Orchestration (SMO), in accordance with some embodiments of the present disclosure;

[0018] FIG. 5 shows a diagram of example components of an apparatus for triggering On Demand-Synchronization Signal Block (ODSSB) transmission in Network Energy Saving (NES) cell from a neighboring cell, in accordance with embodiments of the present disclosure;

[0019] FIG.6 shows external power source coordination based energy saving, which is a potential addition to O-RAN.WG1.TR as Figure 4.21.3.X-1;

[0020] FTG. 7 shows external power source coordination based energy saving (method #2): AI / ML inference via Non-RT RIC, which is a potential addition to O-RAN.WGl.TS.Use-Cases-Detailed-Specification-R004-vl8.00.00 as Figure 4.21.3.x.2-1; and

[0021] FIG. 8 shows external power source coordination based energy saving (method #1): AI / ML inference via Non-RT RIC, which is a potential addition to O-RAN.WGl.TS.Use-Cases-Detailed-Specification-R004-vl8.00.00 as Figure 4.21.3.x.1-1.DETAILED DESCRIPTION

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

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

[0024] 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 directlydepend on only one claim, the disclosure of implementations includes each dependent claim in combination with every other claim in the claim set.

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

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

[0027] As discussed in background section, feature “Co-ordination between 0-RU Power Consumption and External Power Source” focuses on optimizing use of energy more efficiently in 0-RAN networks. It does this through integrating data on the type of power source (renewable or non-renewable) and its available capacity, such as remaining battery life, to make informed decisions about energy consumption. It uses a sophisticated approach to assess whether an O-RU is powered by a finite source like a battery or a sustainable one like wind or solar energy. Depending on this assessment, the network can dynamically adjust its operations by prioritizing energy savings or user experience. The present disclosure relates to how external power source information can be standardized in the 0-RAN Alliance.

[0028] FIG. 1 illustrates an exemplary environment illustrating external power source coordination through an Open Radio Unit (0-RU) and / or Service Management and Orchestration (SMO), in accordance with some embodiments of the present disclosure.

[0029] Exemplary environment 100 includes an Open Radio Unit (0-RU) 101, an Open Distributed unit (O-DU) 103, Service Management and Orchestration (SMO) 105, external powersource 107i to external power source 107N (also referred as one or more external power sources 107) and a controller 109. In an embodiment, the O-RU 101 may be connected with the one or more external power sources 107. The external power sources may provide power supply for functioning of the O-RU 101. As an example, the one or more external power sources 107 may include, without limitation, renewable power sources such as solar power, hydroelectric power, wind power, rechargeable batteries charged using renewable power sources and the like, and nonrenewable power sources such as grid power generated from fossil fuels. The O-RU 101 may continuously draw power from the one or more external power sources 107 based on power requirement. The one or more external power sources 107 may be controlled using the controller 109 (also referred as control panel or external power sources controller 109). In an embodiment, an Input / Output (I / O) unit may be used to facilitate the connection between the controller 109 and the O-RU 101. In some embodiments, the I / O unit may be present external to the O-RU 101. In some embodiments, the I / O unit may be present within the O-RU 101. The following description is discussed from perspective of both hierarchical architecture and hybrid architecture.

[0030] In an embodiment, the O-RU 101 may be configured to receive external power source information from the one or more external power sources 107. In other words, the O-RU 101 collects the external power source information, which may include, without limitation power source type and power source capacity. As an example, the power source type may include solar, grid, battery backup, and renewable energy sources. As an example, the power source capacity may include, available power, voltage, current. Table A below shows exemplary external power source information. The external power source information may be received using at least one vendor-specific protocols and standardized interface. As an example, the vendor-specific protocols and standardized interface may include, without limitation, REpresentational State Transfer Application Programming Interface (REST APIs), Message Queuing Telemetry Transport (MQTT) for integrated loT based data collection. In an embodiment, the O-RU 101 may expose the external power source information in Comma-Separated Values (CSV) or extensible Markup Language (XML) formats either using file management or through Network Configuration Protocol (NETCONF) Yet Another Next Generation (YANG) models, where the information may be exposed as a list for each power category by using an external I / O object to the O-DU 103 and / or the SMO 105. However, a person skilled in the art may appreciate that well-known protocols and standardized interface may be used to transmit and receive the external power source information.The external power source information may be transmitted in one or more predefined formats using one or more data exposure mechanisms. In some embodiments, the O-RU 101 may also utilize a built-in telemetry device for receiving the external power source information.Parameter Description Unit Example Name Value **Power Source Type of power source (e.g., Battery, Solar, String "Battery" Type** EB)**Power Source Current status of the power source (e.g., String "Active" Status** Active, Standby, Fault)**Battery Total capacity of the battery Ampere- 100 Ah Capacity** Hours (Ah) **Remaining Remaining battery backup time Hours 5 Hours BatteryBackup****Battery Current charge level of the battery Percentage 75% Charge Level** (%)**Battery Health Health status of the battery (e.g., Good, Fair, String "Good" Status** Poor)**Renewable Status of renewable power source (e.g., Solar, String "Active" Power Status** Wind)**Renewable Current output from renewable power source Watts (W) 500 W Power Output****EB Supply Status of the electricity board supply (e.g., String "Available" Status** Available, Unavailable)**EB Supply Voltage level of the electricity board supply Volts (V) 230 V Voltage****EB Supply Frequency of the electricity board supply Hertz (Hz) 50 Hz Frequency*** *Power Current power consumption of the O-RU Watts (W) 150 W Consumption****Power Source Priority level of the power source (e.g., String "Primary" Priority** Primary, Secondary)**Power Source Time taken to switch between power sources Seconds (s) 2 s Switch Time**** Total Power Total available power from all sources Watts (W) 1000 w Availability****Power Source Efficiency of the power source Percentage 90% Efficiency** (%)** Temperature Temperature of the power source (if Degrees 35°C of Power applicable) CelsiusSource** (°C)**Power Source Current load on the power source Percentage 60% Load** (%)Table A

[0031] An exemplary use of yang model constructs / objects to expose power source information as notification or other methods is provided below:Extend existing O-RAN WG4 YANG modules to include:grouping ext-power-sources-information-grouppower-source-type: battery*power-source-state: normal / low / highPower-input-status: true / false (availability of main power)battery-soc: battery state-of-charge (%)battery-autonomy-time: remaining runtime (min)power-input-status: true / false (availability of main power)voltage, current, power-consumption: real-time metricspower-source-type: solar*power-source-state: available / unavailable / low-power / high-power Power-input-status: true / false (availability of solar power)solar-soc: battery state-of-charge (%)battery-autonomy-time: remaining runtime (min)power-input-status: true / false (availability of main power)voltage, current, power-consumption: real-time metrics

[0032] In the above example, power-source-type: battery* and power-source-type: solar* may be a list to indicate the status of each power source. Other parameters may be exposed for each power source.

[0033] In an embodiment, the 0-RU 101 may discover and expose external power info at following stages:On boot (or periodic refresh), Control Panel Adapter queries the site control panel (Ethernet / RS-485 / CAN or GPIO) for: source_id, type (grid, PV, wind, battery), capacity, SOC / SOH, availability, cost hint, carbon intensity hint, etc.0-RU packages this plus PMBus-based electrical telemetry (per-source VIN, UN, PIN, energy) into the 0-RU Capabilities file and exposes it to SMO over FH; live changes go as VES events and PM counters.SMO evaluates policy (NES) and can instruct “prefer renewable”, “preserve battery”, or “force grid”.0-RU accepts and either continues on current source or initiates switchover (I2C / PMBus to HSCs) with optional warm reboot depending on site constraints; design below supports hitless switching so reboots are generally unnecessary. PMBus / I2C hot-swap controllers provide direct GATE control, status readback, and latched-fault clear via standard PMBus OPERATION and STATUS * commands — ideal for this use case.

[0034] A proposed extension of file capabilities is provided below:{"externalPower": {"sources": [{ "id": "gridA", "type": "grid", "capacity _W":2000, "present" :true},{ "id": "pvl", "type" / 'renewable", "capacity _W": 1200, "present" :true},{ "id": "batl", "type" :"battery", "capacity _Wh":4000,"soc_pct":65, "present" :true} ],"supportsAutoSwitch": true,"supportsHitlessCutover": true,"telemetry": ["vin","iin","p", "energy", "source_state","switch_count"]Runtime KPIs and alarms (VES / FM):- KPI: PowerSource Curld & EnergyBySource(gridA,pvl,batl)Alarms: LowPowerWarning, SourceUnavailable, CutoverSuccess, CutoverRollback, HSC FaultControl (OAM / M-Plane):setPowerSource(source_id, mode={auto, manual})setThresholds(uv, ov, dvdt_limit, min_soc, max_ripple)setPolicy(preferRenewable, preserveBattery, lowestCost, operatorOverride)

[0035] In an embodiment, upon receiving the external power source information, the 0-RU 101 may be configured to transmit to the SMO 105, the external power source information and capabilities of the O-RU 101 to support external power source coordination. In other words, the 0-RU 101 may advertise to the SMO 105, its capability to support external power source coordination feature along with required parameters for feature enablement. In an embodiment, in a hierarchical deployment, the O-RU 101 may transmit the capabilities to the SMO 105 via the O-DU 103. In some embodiments, in a hybrid deployment the SMO 105 may transmit the capabilities of the O-RU 101 directly to the SMO 105.

[0036] In an embodiment, the SMO 105 may receive the external power source information and the capabilities. Upon receiving, the SMO 105 may analyze the external power source information and the capabilities, to determine one or more configurations and / or one or more policies for enabling energy saving at the O-RU 101. The SMO 105 may analyze analyzing Fault, Configuration, Accounting, Performance and Security (FCAPS) data associated with the O-RU 101, to determine the one or more configuration and one or more policies. The SMO 105 may determine the configurations and / or policies for activating energy saving depending on the external power sources and capabilities of the O-RU 101. As an example, if a site of the O-RU 101 is running on a battery, the SMO 105 may reduce Transmission power, offload traffic. However, if the site is running on solar, the SMO 105 may maintain or enhance capacity of the O-RU 101.

[0037] In an embodiment, upon analyzing the external power source information and the capabilities, the SMO 105 may be configured to transmit the one or more configurations and the one or more policies triggering at least one of, switching to one or more external power sources 107 and enabling one or more Energy Saving (ES) methods in the O-RU 101. In an embodiment,the SMO 105 may transmit the one or more configurations to the O-DU 103 and the O-RU 101 in both the hierarchical deployment and the hybrid deployment. In some embodiments, the SMO 105 may transmit the one or more policies to the O-DU 103 based on the deployment. The O-DU 103 may be capable to perform actions for the O-RU energy saving. However, the power source switching command is transmitted from the SMO 105 as the SMO 105 is aware about the overall network.

[0038] In an embodiment, the O-RU 101 may receive from the SMO 105, the one or more configuration and / or the one or more policies for energy saving based on the external power source information and the capabilities of the O-RU 101. Upon receiving the one or more configuration and / or the one or more policies, the O-RU 101 may be configured to perform at least one of, switching to the one or more external power sources 107 and enabling one or more Energy Saving (ES) methods based on the one or more configuration and the one or more policies. In other words, the O-RU 101 may switch the external power source from an existing power source to another external power source. As an example, the O-RU 101 may switch the external power source from grid power supply to solar power supply or battery backup in case of power shutdown or disaster. Further, the O-RU 101 may also enable one or more Energy Saving (ES) methods. The one or more ES methods may include, without limitation, reducing transmission power and offloading traffic when the O-RU 101 is operating on battery power, and enhancing operating capacity when the O-RU 101 is operating on renewable power source. In an embodiment, the O-RU 101 may transmit a power source switching command to the external power sources controller 109 associated with the one or more external power sources 107 for switching the power source. In an embodiment, the SMO 105 may transmit the power source switching command to the external power source controller 109 through the O-RU 101 via the O-DLT103 in the hierarchical deployment. Both 01 interface and FH M-Plane interface are involved in the hierarchical deployment. In some embodiments, the SMO 105 may transmit the power source switching command to the external power source controller 109 through the O-RU 101 over FH M-Plane interface in the hybrid deployment. In an embodiment, the O-RU 101 may periodically update the external power source information to at least one of the SMO 105 and the O-DU 103.

[0039] In an embodiment, use cases of the present disclosure are provided below:A. Enables Context- Aware Energy Saving• rApps or xApps can make real-time energy management decisions:o If site is on battery: reduce Tx power, offload traffic.o If site is on solar: maintain or enhance capacity.• Example rApps: Battery Saver, Green Energy Prioritizer, Predictive Outage rAppB. Enhances Network Resilience• During power cuts, RU / DU can notify SMO of remaining battery life.• rApps can preemptively reroute traffic or initiate graceful service degradation to maximize uptime.C. Enables Carbon and Energy Optimization• When power source type is known (e.g., renewable vs. grid), operators can:o Optimize scheduling to use greener energy first.o Delay non-critical functions when on fossil-powered backup.D. Supports Regulatory Reporting & ESG Compliance• Standardized reporting enables easier audit of:o Backup power usageo Carbon footprint per base stationo Energy intensity KPI (e.g., Joules per MB transferred)E. Operator may use the power supply statistics information to switch to appropriate power source.

[0040] FIG. 2 shows an exemplary call flow diagram illustrating external power source coordination through an Open Radio Unit (0-RU) 101 and / or Service Management and Orchestration (SMO) 105, in accordance with some embodiments of the present disclosure.

[0041] In an embodiment, preconditions are 0-RU 101 establishes a connection with the external power sources control unit 109 and external control panel collects power source information and exposes it to 0-RU 101. In a hierarchical deployment, at step la, the 0-RU 101 exposes the external power source coordination feature capability and associated parameters to O-DU 103 via FH M-Plane interface. At step lb, the O-DU 103 forwards the feature capability to SMO 105 via 01 interface. In a hybrid deployment, at step 2, the 0-RU 101 exposes the external power source coordination feature capability and associated parameters to SMO 105 directly via FH M-Plane interface. At step 3, the 0-RU 101 collects the external power source information from externalentity. In a hierarchical deployment, at step 4a, the O-RU 101 exposes information about the external power source either through file management or NETCONF Yang to 0-DU 103 via FH M-Plane interface. At step 4b, the 0-DU 103 forwards the above information to SMO 105 via 01 interface. In a hybrid deployment, at step 5, the O-RU 101 exposes information about the external power source either through file management or NETCONF Yang to SMO 105 via FH M-Plane interface. At step 6, SMO 105 analyzes the exposed external power source coordination feature capabilities exposed by O-RU 101 and collected information in Step 3, and decide which power source is appropriate for O-RU 101 needs and accordingly choose ES method. At step 7a, the SMO 105 provides policy information to 0-DU 103 to configure the O-RU 101 and prepare it for power switching requests. In a hierarchical deployment, at step 7b, on receiving the policy and / or configuration update from the SMO 105 , the O-DU 103 may analyze the policy or configuration / trigger for switching to the requested power source (e.g., external power source) and / or activating appropriate energy saving in O-RU 101 via FH M-Plane interface. In a hybrid deployment, at step 8a, the SMO 105 informs the O-DU 103 about the impacted O-RU 101 with external power source coordination feature activation via 01 interface. At step 8b, the SMO 105 configures the O-RU 101 for switching to the requested power source (e.g., external power source) and / or for activating appropriate energy saving in O-RU 101 via FH M-Plane interface. At step 9, the O-RU 101 forward the power source switching command to external entity to switch the power source (proprietary implementation) by leveraging the External IO implementation defined in WG4 M-Plane Specification. The O-RU 101 periodically updates the external power source status and shares relevant details with other components (e.g., 0-DU 103, SMO 105).

[0042] FIG. 2B shows an exemplary call flow diagram illustrating Front Haul (FH) use case during external power source coordination, in accordance with some embodiments of the present disclosure.

[0043] In an embodiment, preconditions are O-RU 101 establishes a connection with the external power sources control unit 109 and external control panel collects power source information and exposes it to O-RU 101. At step 1, the O-RU 101 Expose the external power source coordination feature capability and associated parameters to O-DU 103 via FH M-Plane interface. At step 2, SMO 105 provides the policy or send trigger / configuration command to O-DU 103 via 01 interface. At step 3, O-RU 101 collects the external power source information from external entity.The O-RU 101 exposes information about the external power source to O-DU 103 viaFHM-Plane interface either using Existing file management (for e.g., CSV format) (step 4a) or NETCONF Yang models (for e.g., notification) (step 4b). At step 5, the O-DU 103 sends an RPC command to activate the external power source coordination feature with associated parameters in O-RU 101 via FH M-Plane interface (o-ran-uplane-conf.yang). At step 6, O-DU 103 gets RPC reply for the successful reception of above command. At step 7, the O-DU 103 gets RPC reply for the successful reception of above command. At step 8, ES feature activation depending on the power source configured (i.e., power source being active) in Step 5. At step 9, O-DU 103 schedules the PRBs according to the current power source (Step 5 / 7) and / or ES feature(s) activated (Step 8). Once external power source coordination feature is deactivated, O-RU 101 enters the default operation and O-DU 103 schedule the PRBs with default capacity. The O-RU 101 periodically updates the external power source status and shares relevant details to O-DU 103.

[0044] FIG. 3 shows a flowchart illustrating a method of external power source coordination through an Open Radio Unit (O-RU) 101, in accordance with some embodiments of the present disclosure.

[0045] As illustrated in FIG. 3, the method 300 may include one or more blocks illustrating a method of external power source coordination through an Open Radio Unit (O-RU) 101. The method 300 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform specific functions or implement specific abstract data types.

[0046] The order in which the method 300 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.

[0047] At block 301, the method 300 includes, receiving external power source information from one or more external power sources 107. The external power source information may include at least one of power source type and power source capacity. The external power source informationmay be received using at least one vendor-specific protocols and standardized interface. The external power source information may be transmitted in one or more predefined formats using one or more data exposure mechanisms.

[0048] At block 303, the method 300 includes, transmitting, to a Service Management and Orchestration (SMO) 105, the external power source information and capabilities of an Open Radio Unit (O-RU) 101 to support external power source coordination.

[0049] At block 305, the method 300 includes, receiving, from the SMO 105, one or more configuration and / or one or more policies for energy saving based on the external power source information and the capabilities of the O-RU 101.

[0050] At block 307, the method 300 includes, performing at least one of, switching to the one or more external power sources and enabling one or more Energy Saving (ES) methods based on the one or more configuration and the one or more policies. The one or more ES methods may include, without limitation, reducing transmission power and offloading traffic when the O-RU 101 is operating on battery power, and enhancing operating capacity when the O-RU 101 is operating on renewable power source. In an embodiment, a power source switching command may be transmitted to one or more external power sources controller 109 associated with the external power source for switching the power source. In an embodiment, transmitting the external power source information and the capabilities includes transmitting the capabilities to the SMO 105 via the O-DU 103 in a hierarchical deployment. Further, transmitting the capabilities of the O-RU 101 directly to the SMO 105 in a hybrid deployment. In an embodiment, the external power source information may be periodically updated to at least one of the SMO 105 and an Open Distributed Unit (O-DU 103).

[0051] FIG. 4 shows a flowchart illustrating a method of external power source coordination through a Service Management and Orchestration (SMO) 105, in accordance with some embodiments of the present disclosure.

[0052] As illustrated in FIG. 4, the method 400 may include one or more blocks illustrating a method of external power source coordination through a Service Management and Orchestration (SMO) 105. The method 400 may be described in the general context of computer executableinstructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform specific functions or implement specific abstract data types.

[0053] The order in which the method 400 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.

[0054] At block 401, the method 400 includes, receiving, from an Open Radio Unit (O-RU) 101, external power source information and capabilities of the O-RU 101 to support external power source coordination.

[0055] At block 403, the method 400 includes, analyzing the external power source information and the capabilities, to determine one or more configurations and / or one or more policies for enabling energy saving at the O-RU 101. In an embodiment, analyzing further includes analyzing Fault, Configuration, Accounting, Performance and Security (FCAPS) data associated with the O-RU 101, to determine the one or more configuration and one or more policies.

[0056] At block 405, the method 400 includes, transmitting the one or more configurations and the one or more policies triggering at least one of, switching to one or more external power sources 107 and enabling one or more Energy Saving (ES) methods in the O-RU 101. In an embodiment, transmitting the one or more configurations and the one or more policies includes transmitting the one or more configurations to an Open Distributed Unit (O-DU) 103 and the O-RU 101 in a hierarchical deployment and a hybrid deployment. Further, transmitting the one or more policies to the O-DU 103 based on a deployment.

[0057] FIG. 5 illustrates an embodiment of an apparatus 500. As shown in FIG. 5, the apparatus 500 comprises a processor 502, a memory 504, a storage component 506, an input component 508, an output component 510, a communication interface 512, and a bus 514. In one embodiment, the apparatus 500, in accordance with various embodiments of the present disclosure, may be implemented as an Open Radio Unit (O-RU). In another embodiment, the apparatus 500, inaccordance with various embodiments of the present disclosure, may be implemented as a Service Management and Orchestration (SMO).

[0058] The processor 502, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 502 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 502 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.

[0059] The memory 504 includes a non-transitory computer readable medium. Memory 504 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 memory, a magnetic memory, and / or an optical memory) that stores information and / or instructions for use by processor 502. The memory 504 comprises machine-readable instructions which are executable by the processor 502. These machine-readable instructions when executed by the processor 502 cause the processor 502 to perform one or more method steps of an embodiment described above.

[0060] The storage component 506 stores information and / or software related to the operation and use of the apparatus 500. For example, the storage component 506 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 type of non-transitory computer-readable medium, along with a corresponding drive.

[0061] The input component 508 is configured to receive information, such as user input. For example, the input component 508 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 508 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gyroscope, and / or an actuator).

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

[0063] The communication interface 512 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 512 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 500 and other devices. In other words, the standard of the communication interface 512 is not limited.

[0064] The bus 514 acts as an interconnect between the processor 502, the memory 504, the storage component 506, the input component 508, the output component 510, and the communication interface 512 of the apparatus 500. The bus 514 may include a wired interconnection or a wireless interconnection.

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

[0066] Example embodiments introduces new parameters, attributes, mechanisms, and features that supplement and enhance the disclosures of one or more standard specifications. As a nonlimiting example, example embodiments supplement and enhance at least one technical specification associated with the 3GPP and O-RAN Alliance, as detailed blow (the supplementations and enhancements provided by example embodiments are presented in table and / or bold format).

[0067] The following is a potential addition to O-RAN standards.4.21 Network energy saving4.21.1 Background informationEnergy Consumption (EC) of RAN is an important topic for network operators, especially for 5G network. RAN Energy Saving (ES) depends on rigorous planning and configuration. Due to the varying nature of traffic load and to user mobility, the optimization of EC of the RAN is complex and can be applied to different network layers and in different time scales. There is a risk that RAN equipment consumes much energy while serving low traffic, or even no traffic at all.Different ES features are investigated in industry, some of which are deployed in operational networks. Examples are deep sleep mode (e.g., shut down of a base station of a given technology), carrier shut down, and RF channels’ switch off / on). More recently, short time scales ES mechanisms have been proposed, at symbol-, subframe- and frame-levels, known as Advanced Sleep Modes (ASM).O-RU is responsible for a major part of tire mobile network EC. EC of VNFs have not yet been standardized in Release 17 of 3GPP and can be only estimated, e.g , based on mean vCPU usage of the underlying VMs. EC measurements will be further addressed in release 18 In O-RAN O-Cloud, the only’ feature with relation to ES is scale in / out that is mentioned in the use case document [i.22] . Sub-use cases involving scale-in / scale-out processes, workload placement or HW processors’ sleep modes are not defined in the present document4.21.2 MotivationES for legacy and 5G networks can be carried out using manual configuration or SON functions. 3GPP defines both centralized and distributed ES features [i.13], which are mainly targeting intra- or inter-RAT cell on / off switching The motivation of the ES use case is to leverage on O-RAN AI / ML services and open interfaces in order to introduce optimized ES and EE solutions involving switching off / on of different network components at different time scale. Will be considered off / on switching solutions supported by 3 GPP configurations or supported by propriety’ implementations that require additional standardization.4.21.3 Proposed solutionThe ES use cases is divided into three sub-use cases, according to the time scale of the control and tire controlled system involved:1. Carrier and cell switch off / on ES Time scale: non-real-time for both control and controlled system. The feature aims at reducing O-CU / DU / RU power consumption by switching off / on one or more carriers or a cell of a given technology’. AI / ML assisted solutions in the Non-RT RIC can be used to control tire traffic load of the carriers and the cell, and to automatically decide when to switch off / on one or more carriers or a cell using 01 and / or open fronthaul M-plane parameter configurations. Off / on switching is accompanied with adequate traffic steering, guided by policies, to ensure service continuity’ and quality of service. Carrier switch off / on has two modes of operation: (i) hibernate mode in which the radio’s power amplifiers remain with minimum current draw, and (ii) complete switch off.2. RF channel switch off / on ES. Time scale: non- or near-real-time are possible for both control and controlled system. This feature aims at reducing power consumption of 0-RU with massive MIMO deployment by switching off / on certain RF channels [i.8] . Using AI / ML assisted solutions. rApp or xApp will trigger switching off / on certain RF channels, based on traffic information such as load, user location and mobility. As example, one can switch off 32 out of 64 RF channels in digital M-MIMO architecture or reduce the number of layers and / or number of multi-user scheduled UEs in a hybrid architecture. The 0-RU reconfiguration can be performed using the open fronthaul M-plane from E2 node or SMO. 3. Advanced sleep mode ES. Time scale for control: near-real-time. Time scale for tire controlled system:real-time and near-real-time. This feature is expected to reduce power consumption by partially switching off 0-RU components. The impact of ASMs on 0-DU and 0-CU EC is not defined in the present document. Using multi-dimensional data, e.g., traffic load, user service type, energy efficiency measurements, etc., the Near-RT RIC can configure cell parameters, such as the SSB periodicity neededfor the operation of ASMs.4. External power source coordination based energy saving. Time scale for control: non-real-time is possible for both control and controlled system. The feature aims at reducing power consumption of O-RU byutilizing the energy source and supply information in a deployment where the O-RU is powered by renewable energy source. Using AI / ML assisted solutions. rApp will trigger to activate appropriate energy saving methods depending on the energy source and supply information.4.21.3.x ES sub-use case x: External power source coordination based energy savingExternal power source coordination based energy saving is for SMO framework to collect the energy source and supply information (either by operator input or exposed via O-RU by energy supplier in an operator specific implementation) along with other network datas and configure appropriate energy saving method in O-RU according to the type of energy source and its supply information. For example, when O-RU power source switched from grid supply to either battery or solar power (or any other renewable energy- source) with limited energy supply. The SMO framework may analyze energy sources and their supply information like capacity and then activate the appropriate energy- saving in O-RU to prolong its services. Two types of solutions are described in the following sub clauses.The concept of external power coordination based energy saving sub-use case is given in figure 4.21.3.X-1.4,21,4 Benefits of O-RAN architectureThe proposed solutions will support the AI / ML assisted solutions at both Non-RT RIC and Near-RT RIC as inference hosts, to efficiently- optimize ES and EE at different time scales The ES solutions will leverage on 0- RAN open interfaces to support the use case in a multi-vendor disaggregated RAN.4,21,4 Required data4.21.4.x External power source coordination based energy saving4.21.4.X.1 Solution: rApp-based solutionThe data requirements for this solution are specified below. The input data specified in table 4.21.4.x.1-1 shall be supported by the associated interfaces specified in the table.Table 4.21.4.X.1-1: Required input data for energy saving use case Category Parameters I Measurements Source Reference Interface Energy supply 3GPP TSinformation energySupplyMode Operator 28.310 [xx], O1clause 8.3.1 2Energy supply 3GPP TSinformation energySourceList Operator 28 310 [xx], O1clause 8.3.1 2Energy source 3GPP TSinformation energySourceType Operator 28.310 [xx], O1clause 8.3.22Energy source 3GPP TSinformation energySourceCef Operator 28 310 [xx], O1clause 8.3.22Energy source 3GPP TSinformation renewableEnergy Operator 28.310 [xx], O1clause 8.3.22Energy source 3GPP TSinformation energyCompositionPercentage Operator 28.310 [xx], 01clause 8.3.22Energy 3GPP TSinformation energySupplyModeRefList Operator 28.310 [xx], 01 group clause 8.3.32Energy 3GPP TSinformation memberDNList Operator 28.310 [xx], O1 group clause 8.3.32Energy Energy consumption O-DU, 0- 3GPP TS O1, consumption RU 28.552 [6], Open FH clause M-plane 5 1.1.19.3Energy Power consumed by physical O-DU, 0- 3GPP TS O1, consumption network function & its components RU 28.552 [6], Open FH clause M-plane 5 1.1.19.2 andin 0- RAN.WG4.MP

[0028] , clausesB.1, B.5Energy Transmit power O-RU 0- O1, consumption RAN.WG4.MP Open FH

[0028] , clauses M-plane B.1, B.2.1Configuration cell State O-DU 3GPP TS O128.541 [5],clause 4.4.1The output data specified in table 4.21.4.x.1-2 shall be supported by the associated interfaces specified in the table.Table 4.21.4.X.1-2: Required output data for 01-based solution Category Parameters / Measurements Target Reference Interface NES Policy NESPolicy O-DU WG100AM O1Architecture,clause 5.2.1NES NES configuration changes O-DU WG100AM O1 configuration Architecture,clause 5.2.1==================Changes end==================================== 4.21.3.X.2 Solution: rApp-based solution (Ol-based) - Energy source and supply information configured by operator and / or exposed through O-RUThe following entities are applicable to this solution: Energy saving rApp, Non-RT RIC / SMO framework, O-DU(s) and O-RU node(s).A solution for external power source coordination based energy saving: use case through rApp- based solution with energy source and supply information configured by operator and / or exposed through O-RU is captured in table 4.21.3.X.2-1.Table 4.21.3.X.2-1 : External power source coordination based energy saving _ (method #2): AI / ML inference via Non-RT RIC _Use Case Stage Evolution / Specification Related use Enable external power source coordination based energy savingfunctions in the network by means of configuration parameterGoal change and actions controlled by Non-RT RIC and allow for AI / ML- based solutions1) Energy saving rApp2) Non-RT RIC / SMO frameworkActors and Roles3) O-DU node4) O-RU node• 01 interface connectivity is established between NetworkFunctions (O-DU) and SMO.• Open FH M-plane interface is established between O-DU and OFH M-Plane O-RU and / or SMO and O-RU directly.

[0028] , clause 20; Assumptions • Network is operational. OFH CUS Plane • External control panel (energy supplier) can expose the energy

[0029] , clause 16; supply and energy source information to operator and O-RU. Use case• O-DU and O-RU support one of the energy saving methodsdescribed in clause 16 of OFH C-Plane and clause 20 of OFHM-Plane.Pre-conditions Operator has set the targets for external power source coordinationbased energy saving functions in the Non-RT RIC.Operator enables the optimization functions for external powerBegins when source coordination based energy saving functions and NFs (O-DUand O-RU) under operational.Hierarchical deploymentStep 1a (Alt) O-RU exposes capabilities related to the external power sourcecoordination based energy saving feature via OFH M-Plane.O-DU exposes its capabilities along with associated O-RUStep 1b (M) capabilities to RAN NF OAM SMOS of SMO framework via 01interface.Hybrid deploymentStep 2a (Alt) O-RU exposes capabilities related to the external power sourcecoordination based energy saving feature via OFH M-Plane.Energy supplier exposes the energy source and supply informationStep 3 (M) to O-RU using operator specific implementation.Step 4a (Alt) Hierarchical deployment0-RU exposes the energy source and supply information (that it got from energy supplier as in Step 3) to 0-DU via OFH M-PlaneO-DU forward the energy source and supply information (that itStep 4b (M) received from O-RU via OFH M-Plane in Step 4a) to RAN NF 0AMSMOS of SMO framework via 01 interface.Hybrid deploymentStep 5 (Alt)O-RU exposes capabilities related to the external power sourcecoordination based energy saving feature via OFH M-PlaneOperator configures the external power source information (energy 3GPP TS 28.310 Step 6a (Alt) source and supply information) through a dedicated rApp that is V19.1.0, Clauses responsible for external power source coordination. 5.1 6.2, 5.2.5.1,8.3 1, 8.3.2, and Step 6b (Alt) Operator configures the external power source information (Energy 8.33 and Annex source and supply information) to the RAN NF OAM SMOS C.1 [xx] Step 7a (M) SMO framework uses appropriate SMOS to analyze the externalpower source informations.SMO framework uses appropriate SMOS to prepare the energyStep 7b (M) saving policy and / or configuration changes for the external powersource coordination based energy saving.SMO framework may decide to switch power sources depending onStep 7c (O) various KPIs and then activate appropriate energy saving method(s)in O-RU.Alt SMO configures the O-DU via 01 interface, to enable O-RU toStep 8a (0) forward the energy source switching command.Step 8b (0) O-DU sends an appropriate RPC command to the O-RU via OFHM-Plane for switching the energy source.The O-RU forwards the command that it received from O-DU in StepStep 8c (0) 8b to the energy supplier control panel to switch the energy sourcebased on the operator specific implementationEnergy saving rApp constantly monitors the following by leveragingthe SMO framework,(i) performance and energy consumption of the O-DUs(ii) energy consumption of O-RU(s)(iii) cell utilization and throughput metrics(iv) External power source(s) and capacity i.e , energy supplyand energy source informationrApp determines policy and / or configuration changes for externalpower source coordination based energy saving use case AI / ML OAM Architecture Alt inference may be used to make the decision.

[0027] , clause 5.2.1; Step 9a (M) 01 Interface [yy] rApp may provision the policy through PMI SMOS to RAN NF OAMSMOS. Alternatively, the operator may use the PMI SMOS toprovision the energy saving policy based on the performance datamentioned in Step 2a and energy supply and energy sourceinformationHierarchical DeploymentSMO uses the RAN NF OAM SMOS to provide energy saving policyor the configuration changes to O-DU via 01 interface.OFH M-Plane O-DU configures the O-RU via Fronthaul C-Plane and / or M-Plane

[0028] , clause 20; Step 9b (M) with an appropriate energy saving method supported by O-RU. For OFH CUS Plane example, Advanced sleep mode, TRx Control, Deep hibernate etc..

[0029] , clause 16;Use case Alt Hybrid DeploymentStep 10a (M)SMO sends an appropriate RPC command to the O-RU via OFH M- Plane for switching the energy sourceThe O-RU forwards the command that it received from O-DU in StepStep 10b (M) 8b to the energy supplier control panel to switch the energy sourcebased on the operator specific implementation.Step 11a (M) SMO updates the O-DU about the energy saving feature activationin the specific O-RUSMO configures the O-RU via Fronthaul M-Plane with anappropriate energy saving method supported by O-RU. For OFH M-Plane Step 11b (M) example, the energy saving features such as M-Plane controlled

[0028] , clause 20;TRx Control and Deep hibernate. Use case Energy supply information is not available and O-RU becomes non- Ends when operational or when the operator disables the optimization functionsfor external power source coordination based energy saving.Exceptions None.Non-RT RIC continues close loop monitoring of external powersources, energy supply information, and energy saving function atPost Conditions O-DU and O-RU. O-DU (s) and O-RU(s) operate using theconfiguration provided by the energy saving rapp via Non-RTRIC / SMO framework.The flow diagram of the external power source coordination based energy saving using 01 -based solution with energy source and supply information configured by operator and exposed through 0-RU is given in figure 4.21.3.x.2-1.Change#!2 References2.1 Normative referencesReferences are either specific (identified by date of publication and / or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. In the case of a reference to a 3GPP document, a non-specific reference implicitly refers to the latest version of that document in Release 18, or the latest 3GPP release prior to Release 18 that includes that document.NOTE: While any hyperlinks included in this clause were valid at the time of publication, 0-RAN cannot guarantee their long-term validity.The following referenced documents are necessary for the application of the present document.[xx] 3GPP TS 28.310: “Management and orchestration; Energy efficiency of 5G”, V19.1.0 (2025- 06)[yy] 0-RAN. WG10.01 -Interface: “0-RAN 01 Interface Specification”.Change#!4.21 Netyvork energy savingThis clause provides the motivations, descriptions, and proposed solutions for different energy efficiency and energy saving features (sub-use cases). While there are energy savings by improving base station hardware efficiency and by the evolution of radio access technologies, the EE / ES use case primarily addresses enhancements in software efficiency and optimized configuration / control of various elements and functions, which are often AI / ML based.4,21 , 1 Background and goal of the use caseThe RAN is responsible for a major part of the Energy Consumption (EC) of a mobile network, and the O-RU accounts for the largest part of the energy consumption of the RAN. The rarefication of fossil fuel-based energy resources and the urgent need to reduce CO2 emissions make the EC a strategic topic for network operators, in addition to being a significant component of the operators’ OPEX.EC can be reduced by improving the Energy Efficiency (EE) of the network, and by introducing different Energy Saving (ES) mechanisms. Several ES mechanisms are related to switching off certain components in the network and differ from one another by their scope, time scale and network area. Applicable ES methods are for instance strongly load dependent. Optimization efficiency might be further improved by AI / ML based configuration thereof.RAN functions related to network energy saving solutions have been studied in 3 GPP RAN3 in Rel.17 as part of the Study on Enhancement for Data Collection for NR and EN-DC. The outcome is documented in 3GPP TR 37.817 [i.2], 3GPP RAN2 and RAN3 might specify enhancements for the Minimization of Drive Tests (MDT) procedures and / or signaling procedures that rely on Xn signaling in Rel.18. While 3GPP RAN WGs work on solutions with ML model inference within the gNB, O-RAN specifies solutions that benefit from ML model inference in the Near-RT or Non-RT RIC (e.g., optimizing the network in larger service areas). For EE related network management, use cases, requirements and solutions are specified in 3GPP TS 28.310 [3], Furthermore, EC measurements and KPIs for 5G networks, network functions, NG-RAN and gNBs such as energy efficiency and energy consumption KPIs and performance measurements are specified in 3GPP TS 28.554 [7], Centralized and distributed ES management functions are specified in 3GPP TS 28.541 [5],EE can be considered for the whole network (i.e., end-to-end), for a sub-network or per single network element. Within a network element it could be applicable per specific radio resource management mechanism or per radio or transport network link. Network wise EE is defined as the ratio between the data volume delivered in the network and the network EC observed during the time-period required to deliver such data, with possible adaptations to account for different deployment scenarios and load situations (ETS ES 203 228 [i.5], 3GPP TR 38.913 [i.4]). 3GPP has launched a study item within Rel- 18 (RP-213554: “Study on network energy saving for NR”) that will include among others, an evaluation methodology and KPIs for EC and ES gains and their impact on network and UE performance and EE. To assess EE and ES associated to radio resource management mechanisms and links, appropriate KPIs are necessary.In a timescale of minutes, hours and above, and when the cell load is low, ES can be achieved by switching off one or more carriers or the cell. In a timescale from seconds to minutes, ES can be achieved by switching off RF channels (including possibly antennas) of a massive MIMO system. Tx and Rx parts might be switched independently. In a very short timescale corresponding to a symbol, subframe or frame, Advanced Sleep Modes (ASM) can beconsidered. RF channel on / off switching can be used at medium load and ASM might be usableeven at high load. Lastly, ES solutions can be applied to the O-Cloud, namely to the O-CU and O-DU, and can cover mechanisms such as scale in / out processes, workload placement or hardware processors’ sleep modes etc. AI / ML is useful for all the above mechanisms with the important role of determining the switch off / on time that maximizes ES gain.Furthermore, the energy source and supply information can be used as an input data for SMO framework. This framework, leveraging a non-RT RIC platform with rApps, can use the energy source and supply information to analyze and prepare a policy and / or configuration changes to activate the appropriate energy saving methods in the O-RU, thereby minimizing power consumption.4.21.2 Entities / resources involved in the use caseEditor ’s note: If possible, single common description for all sub-use cases.4.21.3 SolutionsEditor’s note: Sub-use case specific solutions with detailed descriptions in fully separate clauses.The following is an exhaustive list of entities across all the identified solutions for this use case. All the entities may not be applicable for every solution.1) Energy saving rApp:a) Collect configurations, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE / EC measurement reports, geolocation information, and energy source and supply information configured by either operator or exposed via O-RAN networks) from Non-RT R1C / SM0 framework.b) Utilize the collected data for EE / ES optimization (e.g., if carriers or cells need to be switched off / on), and initiate 01 configuration updates, Al policy updates, and / or open FH M-plane configuration updates through R1 interface.2) Non-RT RIC / SMO framework:a) Collect configurations, performance indicators, measurement reports, and energy source and supply information from network functions via 01 and optionally via open FH M- plane from 0-RUs and provide this information to energy saving rApp.b) Determine and signal updated configuration or policy for network energy saving use case (provided by energy saving rApp) toE2 nodes, and / or Near-RT RIC, and optionally 0-RU.3) NF node:a) Report cell configuration, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE / EC measurement reports).b) Perform actions required for EE / ES optimization per the configuration updates or policies received from Non-RT RIC / rApp and / or Near-RT RIC / xApp.4) 0-RU node:a) Report EC and EE related information.b) Perform actions required to perform EE / ES optimization per the configuration updates or policies received from Non-RT RIC / rApp and / or Near-RT RIC / xApp.c) Receives the energy source and supply information from energy supplier in an operator specific implementation and forward the same to SMO through O-DU.5) Near-RT RIC:a) Collect configurations, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE / EC measurement reports) from E2 nodes. b) Receive EE / ES related policies via Al interface for consideration during optimization. c) Determine and signal updated configuration or policy for network energy saving use case to E2 nodes.4.21.3.x External power source coordination based energy savingExternal power source coordination based energy saving is for SMO framework to collect the energy source and supply information (either by operator input or exposed via O-RU by energy supplier in an operator specific implementation) along with other network data. The SMO framework may use those data to configure appropriate energy saving method in O-RU according to the type of energy source and its supply. For example, when O-RU power source switched from grid supply to either battery or solar power (or any other renewable energy source) with limited energy supply. The SMO framework may analyze energy source and supply information and then activate the appropriate energy saving in O-RU to prolong its services. Two types of solutions are described in the following sub clauses.4.21.3.X.1 Solution: rApp-based solution (Ol-based) - Energy source and supply information configured by the operatorThe following entities are applicable to this solution: Energy saving rApp, Non-RT RIC / SMO framework, O-DU node(s) and O-RU node(s).A solution for external power source coordination based energy saving: use case through rApp- based solution is captured in table 4.21.3.x.1-1.Table 4.21.3.X.1-1: External power source coordination based energy saving (method #1): AI / ML inference via Non-RT RICUse Case Stage Evolution / Specification Related use Enable external power source coordination based energy savingfunctions in the network by means of configuration parameterGoal change and actions controlled by Non-RT RIC and allow for AI / ML- based solutions1) Energy saving rApp2) Non-RT RIC / SMO frameworkActors and Roles 3) O-DU node4) O-RU node• 01 interface connectivity is established between Network OFH M-Plane Assumptions Functions (for example, O-DU) and SMO.

[0028] , clause 20;• Open FH M-plane interface is established between O-DU and OFH CUS PlaneO-RU and / or SMO and O-RU directly.

[0029] , clause 16;• Network is operational. Use case• External control panel (energy supplier) can expose the energysupply and energy source information to the operator.• O-DU and O-RU support one of the energy saving methodsdescribed in clause 16 of OFH C-Plane and clause 20 of OFHM-Plane.Pre-conditions Operator has set the targets for external power source coordinationbased energy saving functions in the Non-RT RIC.Operator enables the optimization functions for external powerBegins when source coordination based energy saving functions and NFs (O-DUand O-RU) under operational.Operator configures the external power source information (EnergyStep 1a (Alt) supply and source information) through a dedicated rApp that is 3GPP TS 28.310 responsible for external power source coordination. V19.1.0, Clauses Operator configures the external power source information (Energy 5.1 6.2, 5.2.5.1, Step 1b (Alt) 8.3 1, 8.3.2, and supply and source information) to the RAN NF OAM SMOS. 8.33 and Annex Operator uses the external producer termination of Decoupled SMOStep 1c (Alt) C.1 [xx]framework to supply the Energy supply and source information. s Energy saving rApp constantly monitors the following by leveragingthe SMO framework,(i) performance and energy consumption of the O-DUs(ii) energy consumption of O-RU(s)(iii) cell utilization and throughput metrics(iv) external power source(s) and capacity i.e , energy supplyStep 2a (Alt) and energy source information. Use case rApp determines policy and / or configuration changes for externalpower source coordination based energy saving use case AI / MLinference may be used to make the decision.rApp may provision the policy through PMI SMOS to RAN NF OAMSMOS.Operator may use the PMI SMOS to provision the energy savingStep 2b (Alt) policy based on the performance data mentioned in Step 2a and Use case energy supply and energy source information.Hierarchical Deployment OAM Architecture Step 3a (Alt)

[0027] , clause 5.2.1;SMO uses the RAN NF OAM SMOS to provide energy saving policy 01 Interface [yy] or the configuration changes to O-DU via 01 interface.If the conditions mentioned in the policy or configuration changes OFH M-Plane provided in Step 3a are met, the O-DU configures the O-RU via OFH

[0028] , clause 20; Step 3b (Alt) C-Plane and / or M-Plane with an appropriate energy saving method OFH CUS Plane supported by O-RU. For example, Advanced sleep mode, TRx

[0029] , clause 16; Control, Deep hibernate etc... Use case Hybrid Deployment OAM Architecture Step 4a (Alt)SMO uses the RAN NF OAM SMOS to configure the O-DU to make

[0027] ;Use case it aware of energy saving activation in O-RU via 01 interface.OFH M-Plane SMO configures the O-RU via Fronthaul C-Plane and / or M-Plane

[0028] , clause 20; Step 4b (Alt) with appropriate energy saving methods. For example, Advanced OFH CUS Plane sleep mode, TRx Control, Deep hibernate etc

[0029] , clause 16;Use case Energy supply information is not available and O-RU becomes non- Ends when operational or when the operator disables the optimization functionsfor external power source coordination based energy saving.Exceptions None.Non-RT RIC continues close loop monitoring of external powerPost Conditions sources, energy supply information and energy saving function atO-DU and O-RU. O-DU (s) and O-RU(s) operate using theconfiguration provided by the energy saving rapp via Non-RTRIC / SMO frameworkThe flow diagram of the external power source coordination based energy saving using 01 -based solution with energy source and supply information configured by the operator is given in figure 4.21.3.x.1-1.Claimable aspects:1. In an embodiment, a method is disclosed in an aspect. The method includes receiving external power source information from one or more external power sources. Further, the method includes transmitting, to a Service Management and Orchestration (SMO), the external power source information and capabilities of an Open Radio Unit (O-RU) to support external power source coordination. Thereafter, the method includes receiving, from the SMO, one or more configuration and / or one or more policies for energy saving based on the external power source information and the capabilities of the O-RU. Finally, the method includes performing at least one of, switching to the one or more external power sources and enabling one or more Energy Saving (ES) methods based on the one or more configuration and the one or more policies.2. In an embodiment, the method as described in preceding aspect 1, wherein the external power source information comprises at least one of: power source type and power source information.3. In an embodiment, the method as described in preceding aspect 1, wherein the external power source information is received using at least one of, vendor-specific protocols and standardized interface.4. In an embodiment, the method as described in preceding aspect 1, the external power source information is transmitted in one or more predefined formats using one or more data exposure mechanisms.5. In an embodiment, the method as described in preceding aspect 1, further comprises periodically updating the external power source information to at least one of the SMO and an O-RAN Distributed Unit (O-DU).6. In an embodiment, the method as described in preceding aspect 1, wherein the one or more ES methods comprises, reducing transmission power and offloading traffic when the O-RU is operating on battery power, and enhancing operating capacity when the O-RU is operating on renewable power source.7. In an embodiment, the method as described in preceding aspect 1, switching to the one or more external power sources comprises transmitting a power source switching command to an externalpower source controller associated with the one or more external power sources for switching the power source.8. In an embodiment, the method as described in preceding aspect 1, transmitting the external power source information and the capabilities comprises transmitting the capabilities to the SMO via the O-DU in a hierarchical deployment, and transmitting the capabilities of the O-RU directly to the SMO in a hybrid deployment.9. In an embodiment, a method is disclosed in an aspect. The method includes receiving, from an Open Radio Unit (O-RU), external power source information and capabilities of the O-RU to support external power source coordination. Further, the method includes analyzing the external power source information and the capabilities, to determine one or more configurations and / or one or more policies for enabling energy saving at the O-RU. Finally, the method includes transmitting the one or more configurations and the one or more policies triggering at least one of, switching to one or more external power sources and enabling one or more Energy Saving (ES) methods in the O-RU.10. In an embodiment, the method as described in preceding aspect 9, wherein analyzing further comprises analyzing Fault, Configuration, Accounting, Performance and Security (FCAPS) data associated with the O-RU, to determine the one or more configuration and one or more policies.11. In an embodiment, the method as described in preceding aspect 9, wherein transmitting the one or more configuration and one or more policies comprises transmitting the one or more configurations to an O-RAN Distributed Unit (O-DU) and the O-RU in a hierarchical deployment and a hybrid deployment, and transmitting the one or more policies to the O-DU based on a deployment.12. In an embodiment, an Open Radio Unit (O-RU) is disclosed in an aspect. The O-RU is configured to receive external power source information from one or more external power sources. Further, the O-RU is configured to transmit, to a Service Management and Orchestration (SMO), the external power source information and capabilities of an O-RU to support external power source coordination. Thereafter, the O-RU is configured to receive, from the SMO, one or more configuration and one or more policies for energy saving based on the external power source information and / or the capabilities of the O-RU. Finally, the O-RU is configured to perform at least one of, switching to the one or more external power sources and enabling one or more Energy Saving (ES) methods based on the one or more configuration and the one or more policies.13. In an embodiment, the O-RU as described in preceding aspect 12, wherein the O-RU is further configured to periodically update the external power source information to at least one of the SMO and an O-RAN Distributed Unit (O-DU).14. In an embodiment, the O-RU as described in preceding aspect 12, wherein to switch to the one or more external power sources, the O-RU is configured to transmit a power source switching command to an external power source controller associated with the one or more external power sources for switching the power source.15. In an embodiment, the O-RU as described in preceding aspect 12, wherein to transmit the external power source information and the capabilities, the O-RU is configured to transmit the capabilities to the SMO via the O-DU in a hierarchical deployment, and transmit the capabilities of the O-RU directly to the SMO in a hybrid deployment.16. In an embodiment, a Service Management and Orchestration (SMO) is disclosed in an aspect. The SMO is configured to receive, from an Open Radio Unit (O-RU), external power source information and capabilities of the O-RU to support external power source coordination. Further, the SMO is configured to analyze the external power source information and / or the capabilities, to determine one or more configurations and one or more policies for enabling energy saving at the O-RU. Finally, the SMO is configured to transmit the one or more configurations and one or more policies triggering at least one of, switching to one or more external power sources and enabling one or more Energy Saving (ES) methods in the O-RU.17. In an embodiment, the O-RU as described in preceding aspect 16, wherein the SMO is further configured to analyze Fault, Configuration, Accounting, Performance and Security (FCAPS) data associated with the O-RU, to determine the one or more configuration and one or more policies.18. In an embodiment, the O-RU as described in preceding aspect 16, wherein to transmit the one or more configuration and one or more policies, the SMO is configured to transmit the one or more configurations to an O-RAN Distributed Unit (O-DU) and the O-RU in a hierarchical deployment and a hybrid deployment, and transmit the one or more policies to the O-DU based on a deployment.19. In an embodiment, a non-transitory computer readable medium including instructions for performing operations comprising receiving external power source information from one or more external power sources. Further, the operations comprising transmitting, to a Service Management and Orchestration (SMO), the external power source information and capabilities of an Open Radio Unit (O-RU) to support external power source coordination. Thereafter, the operations comprising receiving, from the SMO, one or more configuration and / or one or more policies forenergy saving based on the external power source information and the capabilities of the O-RU. Finally, the operations comprising performing at least one of, switching to the one or more external power sources and enabling one or more Energy Saving (ES) methods based on the one or more configuration and the one or more policies.20. In an embodiment, a non-transitory computer readable medium including instructions for performing operations comprising receiving, from an Open Radio Unit (O-RU), external power source information and capabilities of the O-RU to support external power source coordination. Further, the operations comprising analyzing the external power source information and the capabilities, to determine one or more configurations and / or one or more policies for enabling energy saving at the O-RU. Finally, the operations comprising transmitting the one or more configurations and the one or more policies triggering at least one of, switching to one or more external power sources and enabling one or more Energy Saving (ES) methods in the O-RU.

Claims

We claim:

1. A method comprising:receiving external power source information from one or more external power sources;transmitting, to a Service Management and Orchestration (SMO), the external power source information and capabilities of an O-RAN Radio Unit (O-RU) to support external power source coordination;receiving, from the SMO, one or more configuration and / or one or more policies for energy saving based on the external power source information and the capabilities of the O-RU; andperforming at least one of, switching to the one or more external power sources and enabling one or more Energy Saving (ES) methods based on the one or more configuration and the one or more policies.

2. The method as claimed in claim 1, wherein the external power source information comprises at least one of: power source type and power source information.

3. The method as claimed in claim 1, wherein the external power source information is received using at least one of vendor-specific protocols and standardized interface.

4. The method as claimed in claim 1, wherein the external power source information is transmitted in one or more predefined formats using one or more data exposure mechanisms.

5. The method as claimed in claim 1, further comprises:periodically updating the external power source information to at least one of the SMO and an O-RAN Distributed Unit (O-DU).

6. The method as claimed in claim 1, wherein the one or more ES methods comprises, reducing transmission power and offloading traffic when the O-RU is operating on battery power, and enhancing operating capacity when the O-RU is operating on renewable power source.

7. The method as claimed in claim 1, wherein switching to the one or more external power sources comprises:transmitting a power source switching command to an external power source controller associated with the one or more external power sources for switching the power source.

8. The method as claimed in claim 1, wherein transmitting the external power source information and the capabilities comprises:transmitting the capabilities to the SMO via the O-DU in a hierarchical deployment, andtransmitting the capabilities of the O-RU directly to the SMO in a hybrid deployment.

9. A method comprising:receiving, from an O-RAN Radio Unit (O-RU), external power source information and capabilities of the O-RU to support external power source coordination;analyzing the external power source information and the capabilities, to determine one or more configurations and / or one or more policies for enabling energy saving at the O-RU; andtransmitting the one or more configurations and the one or more policies triggering at least one of, switching to one or more external power sources and enabling one or more Energy Saving (ES) methods in the O-RU.

10. The method as claimed in claim 9, wherein analyzing further comprises analyzing Fault, Configuration, Accounting, Performance and Security (FCAPS) data associated with the O-RU, to determine the one or more configuration and one or more policies.

11. The method as claimed in claim 9, wherein transmitting the one or more configuration and one or more policies comprises:transmitting the one or more configurations to the O-RAN Distributed Unit (O-DU) and O-RU in a hierarchical deployment and a hybrid deployment, andtransmitting the one or more policies to the O-DU based on a deployment.

12. An O-RAN Radio Unit (O-RU) configured to:receive external power source information from one or more external power sources; transmit, to a Service Management and Orchestration (SMO), the external power source information and capabilities of an O-RU to support external power source coordination;receive, from the SMO, one or more configuration and one or more policies for energy saving based on the external power source information and / or the capabilities of the O-RU; andperform at least one of, switching to the one or more external power sources and enabling one or more Energy Saving (ES) methods based on the one or more configuration and the one or more policies.

13. The O-RU as claimed in claim 12, wherein the O-RU is further configured to:periodically update the external power source information to at least one of the SMO and an O-RAN Distributed Unit (O-DU).

14. The O-RU as claimed in claim 12, wherein to switch to the one or more external power sources, the O-RU is configured to:transmit a power source switching command to an external power source controller associated with the one or more external power sources for switching the power source.

15. The O-RU as claimed in claim 12, wherein to transmit the external power source information and the capabilities, the O-RU is configured to:transmit the capabilities to the SMO via the O-DU in a hierarchical deployment, andtransmit the capabilities of the O-RU directly to the SMO in a hybrid deployment.

16. A Service Management and Orchestration (SMO) configured to:receive, from an O-RAN Radio Unit (O-RU), external power source information and capabilities of the O-RU to support external power source coordination;analyze the external power source information and / or the capabilities, to determine one or more configurations and one or more policies for enabling energy saving at the O- RU; andtransmit the one or more configurations and one or more policies triggering at least one of, switching to one or more external power sources and enabling one or more Energy Saving (ES) methods in the O-RU.

17. The SMO as claimed in claim 16, wherein the SMO is further configured to analyze Fault, Configuration, Accounting, Performance and Security (FCAPS) data associated with the O-RU, to determine the one or more configuration and one or more policies.

18. The SMO as claimed in claim 16, wherein to transmit the one or more configuration and one or more policies, the SMO is configured to:transmit the one or more configurations to an O-RAN Distributed Unit (O-DU) and the O-RU in a hierarchical deployment and a hybrid deployment, andtransmit the one or more policies to the O-DU based on a deployment.

19. A non-transitory computer readable medium including instructions for performing operations comprising:receiving external power source information from one or more external power sources;transmitting, to a Service Management and Orchestration (SMO), the external power source information and capabilities of an O-RAN Radio Unit (O-RU) to support external power source coordination;receiving, from the SMO, one or more configuration and one or more policies for energy saving based on the external power source information and / or the capabilities of the O-RU; andperforming at least one of, switching to the one or more external power sources and enabling one or more Energy Saving (ES) methods based on the one or more configuration and one or more policies.

0. A non-transitory computer readable medium including instructions for performing operations comprising:receiving, from an 0-RAN Radio Unit (O-RU), external power source information and capabilities of the O-RU to support external power source coordination;analyzing the external power source information and / or the capabilities, to determine one or more configurations and one or more policies for enabling energy saving at the O-RU; andtransmitting the one or more configurations and one or more policies triggering at least one of, switching to one or more external power sources and enabling one or more Energy Saving (ES) methods in the O-RU.

Images