Network energy saving implementation using o1 interface

Abstract

An apparatus (203) is disclosed. The apparatus (203) is configured to receive one or more policies for an Open Radio Access Network (ORAN)-Radio Unit (O-RU) (230) from a Management Service (MnS) consumer (210). The apparatus (203) is configured to check one or more conditions associated with the O-RU (230) based on the one or more policies. Upon successful checking of the one or more conditions, the apparatus (203) is configured to apply the one or more policies at the O-RU (230). The apparatus (203) is configured to receive one of an acknowledgement message and a non-acknowledgement message from the O-RU (230) based on execution of the applied one or more policies. The apparatus (203) is configured to send a policy utilization status to the MnS consumer (210) based on the received one of the acknowledgement message and the non-acknowledgement message.

Description

Cross-references to (multiple) related applications

[0001] This application claims priority to IN provisional application 202411000750, filed January 4, 2024, and IN provisional application 202411004452, filed January 23, 2024, the entire contents of which are incorporated herein by reference. Technical Field This disclosure relates to network power saving (NES) implementation using the O1 interface. Background Technology

[0002] The information disclosed in this background section is intended only to enhance the understanding of the general background of this disclosure and should not be considered as confirmation or any form of advice. This information forms prior art known to those skilled in the art.

[0003] The Radio Access Network (RAN) is a crucial component of telecommunications systems and comprises multiple network entities or components that facilitate connectivity with end-user equipment (User Equipment). In recent years, the Open RAN (O-RAN) architecture has been developed, which decomposes the RAN's functionality through various logical nodes. Figure 1 The diagram illustrates the O-RAN architecture 100 based on conventional technology.

[0004] The O-RAN architecture 100 includes a Service Management and Orchestration (SMO) framework, which manages and orchestrates various services within the network, such as resource allocation and network optimization. Furthermore, the O-RAN architecture 100 includes logical nodes such as O-RAN Radio Units (O-RUs), O-RAN Centralized Units (O-CUs), and O-RAN Distributed Units (O-DUs). The O-CU can also be decomposed into the O-CU Control Plane (O-CU-CP) and the O-CU User Plane (O-CU-UP).

[0005] The O-RAN architecture 100 can be associated with a Radio Intelligent Controller (RIC). RICs can be categorized into non-real-time (NRT) and near-real-time (NRT) components. NRT-RICs are elements of SMO, while near-real-time (NRT) RICs can reside at the telecom edge or in the regional cloud and typically enable network optimization actions that require between 10 milliseconds and 1 second to complete.

[0006] O-Cloud can be a collection of physical RAN nodes that carry RIC, O-CU, and O-DU, support software components (e.g., operating system and runtime environment), and SMO. Furthermore, various components of the O-RAN architecture can communicate through corresponding interfaces such as O1, O2, A1, and E2.

[0007] In traditional architectures, data is exchanged (sent and received) among various components in the O-RAN based on certain strategies. However, given the implementation of Network Energy Saving (NES), there is a need to optimize the Transmission (TRx) strategy. Summary of the Invention

[0008] This summary introduces a series of concepts in a simplified format, which are further described in the detailed description of this disclosure. This summary is not intended to identify key or essential inventive concepts of this disclosure, nor is it intended to define the scope of this disclosure.

[0009] This paper discloses a system and method for implementing network energy saving (NES) using the O1 interface.

[0010] According to one embodiment of this disclosure, an apparatus is disclosed. The apparatus is configured to receive one or more policies for an Open Radio Access Network (ORAN) - Radio Unit (O-RU) from an MnS consumer. The apparatus is configured to check one or more conditions associated with the O-RU based on the one or more policies. Then, the apparatus is configured to apply the one or more policies at the O-RU after successfully checking the one or more conditions. The apparatus is further configured to receive one of an acknowledgment message or a non-acknowledgment message from the O-RU based on the execution of the applied one or more policies. The acknowledgment message or non-acknowledgment message is received from the O-RU. The apparatus is further configured to send a policy utilization status to the MnS consumer based on one of the received acknowledgment message or non-acknowledgment message.

[0011] According to another embodiment of this disclosure, an apparatus is disclosed. The apparatus is configured to receive transmission (TRx) control-related capability information corresponding to an Open Radio Access Network (ORAN) - Radio Unit (O-RU) and an MnS producer. The apparatus is further configured to send one or more policies for the O-RU to the MnS producer based on the received TRx control-related capability information corresponding to the O-RU and the MnS producer. The apparatus is configured to receive a policy utilization status from the MnS producer, the policy utilization status indicating the implementation of at least one of the one or more policies at the O-RU.

[0012] According to another embodiment of this disclosure, a method is disclosed. The method includes: receiving transmission (TRx) control-related capability information corresponding to an Open Radio Access Network (ORAN) - Radio Unit (O-RU) and an MnS producer. The TRx control-related capability information is received from the MnS producer by a Management Service (MnS) consumer. The method further includes: based on the received TRx control-related capability information corresponding to the O-RU and the MnS producer, sending one or more policies for the O-RU. The one or more policies are sent to the MnS producer by the MnS consumer. The method further includes: receiving a policy utilization status, which indicates the implementation of at least one of the one or more policies at the O-RU. The policy utilization status is received from the MnS producer by the MnS consumer.

[0013] According to another embodiment of this disclosure, a non-transitory computer-readable medium is disclosed. The computer-readable medium stores instructions. The instructions include one or more instructions executable by a Management Service (MnS) consumer. The MnS consumer includes one or more processors. The one or more instructions cause the one or more processors to receive from the MnS producer transmission (TRx) control-related capability information corresponding to the Open Radio Access Network (ORAN) - Radio Unit (O-RU) and the MnS producer. The one or more instructions cause the one or more processors to send one or more policies for the O-RU to the MnS producer based on the received TRx control-related capability information corresponding to the O-RU and MnS producer 220. The one or more instructions cause the one or more processors to receive a policy utilization state from the MnS producer, the policy utilization state indicating the implementation of at least one of the one or more policies at the O-RU.

[0014] According to another embodiment of this disclosure, a non-transitory computer-readable medium is disclosed. The computer-readable medium stores instructions. The instructions include one or more instructions executed by a Management Service (MnS) producer. The MnS producer includes one or more processors. The one or more instructions cause the one or more processors to receive from an MnS consumer one or more policies for Open Radio Access Network (ORAN) - Radio Unit (O-RU). The one or more instructions cause the one or more processors to check one or more conditions associated with the O-RU based on the received one or more policies. The one or more instructions cause the one or more processors to apply one or more policies at the O-RU after successfully checking the one or more conditions. The one or more instructions cause the one or more processors to receive one of an acknowledgment message and a non-acknowledgment message from the O-RU based on the execution of the applied one or more policies. The one or more instructions cause the one or more processors to send a policy utilization status to the MnS consumer based on one of the received acknowledgment message and non-acknowledgment message.

[0015] To further illustrate the advantages and features of this disclosure, a more specific description of the disclosure will be presented with reference to specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings depict only typical embodiments of the disclosure and are therefore not intended to limit its scope. The disclosure will be described and explained with additional specificity and detail in conjunction with the accompanying drawings. Attached Figure Description

[0016] The features, aspects, and advantages of embodiments of the present disclosure will be described below with reference to the accompanying drawings, wherein like reference numerals denote like elements, and wherein: Figure 1 The diagram illustrates the O-RAN architecture based on relevant technologies; Figure 2 An example block diagram depicting the configuration of a network management system according to an embodiment of the present disclosure is shown; Figures 3A to 3B The illustration shows the processing flow among MN consumers, MN producers, and O-RUs according to embodiments of the present disclosure; Figures 4A to 4B The illustration shows the processing flow among the MN consumer, MN producer, and O-RU according to another embodiment of the present disclosure; Figure 5A An information model for policy processing using a file management process is illustrated according to an embodiment of the present disclosure; Figure 5B An information model for policy processing of Yang-based network Netconf is illustrated according to an embodiment of the present disclosure; Figure 6 The illustration shows a flowchart of an example method according to an embodiment of the present disclosure; and Figure 7 An embodiment of an example device according to an embodiment of the present disclosure is illustrated. Detailed Implementation

[0017] The following example embodiments are described in detail with reference to the accompanying drawings. This disclosure provides illustration and description, but is not intended to be exhaustive or to limit implementation to the precise forms disclosed. Modifications and variations are possible in light of this disclosure, or may be obtained from the practice of implementation. Furthermore, 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 flowcharts and descriptions of operation provided below relate to at least one embodiment of the embodiments in this disclosure. It should be noted that other embodiments that do not precisely match the flowcharts and their descriptions are possible. It should be understood that in other embodiments, one or more operations may be omitted (at least in part), one or more operations may be added, or one or more operations may be performed simultaneously.

[0018] It will be apparent that the systems and / or methods described herein can be implemented in various forms, including hardware, software, or a combination of both. The actual dedicated control hardware or software code used to implement these systems and / or methods should not limit their implementation. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to any specific software code. It should be understood that software and hardware can be designed to implement the systems and / or methods described herein.

[0019] Even if a particular combination of features is stated in the claims and / or disclosed in the specification, that particular combination is not intended to limit the disclosure of implementation methods. In fact, many of these features can be combined in ways not specifically stated in the claims and / or disclosed in the specification. Even if a dependent claim depends only directly on one claim, this disclosure may indicate that the dependent claim is subordinate to other claims in that set of claims.

[0020] Elements, actions, or instructions used herein should not be construed as essential or necessary unless explicitly described as such. Furthermore, as used herein, the articles “a” and “one” (in other words, a noun not mentioned in the plural) are intended to include one or more items and may be used interchangeably with “one or more”. Furthermore, as used herein, the terms “have,” “possess,” “include,” “include,” etc., are intended to be open-ended terms. Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, expressions such as “at least one of [A] and [B],” “[A] and / or [B],” or “at least one of [A] or [B]” should be understood to include only A, only B, or both A and B.

[0021] The terms “control-related capability information”, “control-related capability”, “transmission (TRx) control-related capability information”, “TRx control-related capability” and / or other similar variations may be used interchangeably throughout the description of this disclosure.

[0022] Figure 2 An example block diagram is shown depicting the configuration of a network management system 200 (hereinafter referred to as "system 200") according to an embodiment of the present disclosure.

[0023] System 200 may include a Management Service (MnS) consumer 210, an MnS producer 220, and an O-RU 230. The MnS consumer 210 can be configured to communicate with the MnS producer 220, such as... Figure 2As depicted. MnS consumer 210 can be configured to provide one or more network energy policies and / or configurations to MnS producer 220. MnS consumer 210 and / or MnS producer 220 may correspond to O-RAN management functions (MnF). Figure 2 The disclosed configuration can be understood as part of the configuration of MnS consumer 210 and MnS producer 220. In the following, it should be understood that terms including "unit" or "module" at the end can refer to a unit for processing at least one function or operation and can be implemented in hardware, software, or a combination of hardware and software. In embodiments, MnS consumer 210 may correspond to Service Management and Orchestration (SMO), and MnS producer 220 may correspond to Open Radio Access Network (ORAN) - Distributed Unit (O-DU). For example, the SMO acts as the provider for MnS consumer 210, and the O-DU acts as the provider for MnS producer 220. MnS consumer 210 and MnS producer 220 can be configured to provide management services to system 200 and / or O-RU 230. In one embodiment, MnS producer 220 can provide capabilities for network and service management and orchestration. MnS consumer 210 can interact with MnS producer 220 to utilize the capabilities provided by MnS producer 220. In the following text, it should be understood that a term including “unit” or “module” at the end can refer to a unit for performing at least one function or operation, and can be implemented in hardware, software or a combination of hardware and software.

[0024] Reference Figure 2 The MnS consumer 210 may include a device 201, which includes one or more processors 202 (also referred to as processor 202), a storage unit (e.g., memory 204), and a communication unit 206 (e.g., a communicator or communication interface). The communication unit 206 may perform functions such as sending and receiving signals. The memory 204 may include executable instructions that, when executed by the processor 202, cause the device 201 to perform reference... Figures 3A to 3B and Figure 6 The steps described above.

[0025] As an example, processor 202 can be a single processing unit or multiple units, all of which can include multiple computing units. Processor 202 can be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuit systems, and / or any device that manipulates signals based on operating instructions. Among other capabilities, processor 202 is configured to fetch and execute computer-readable instructions and data stored in memory 204. Processor 202 can include one or more processors. In this case, one or more processors 202 can be general-purpose processors (such as central processing units (CPUs), application processors (APs), etc.) and AI-specific processors (such as neural processing units (NPUs)). Processor 202 can control the processing of input data according to predefined operating rules or artificial intelligence (AI) models stored in non-volatile memory and volatile memory (i.e., memory 204). Predefined operating rules or AI models can be provided through training or learning.

[0026] The memory 204 may include any non-transitory computer-readable medium known in the art, including, for example, volatile memory (such as static random access memory (SRAM) and dynamic random access memory (DRAM)) and / or non-volatile memory (such as read-only memory (ROM), erasable programmable ROM, flash memory, hard disk, optical disk and magnetic tape).

[0027] The communication unit 206 may include communication devices / components (such as antennas, transmitters, receivers, communication interfaces, etc.).

[0028] In some embodiments, device 201 may be implemented as a dedicated hardware unit. In some embodiments, device 201 may be implemented as a virtualized software unit in a hardware or cloud environment.

[0029] Furthermore, the MnS producer 220 may also include a device 203. Device 203 may include one or more processors 212 (also referred to as processor 212), storage units (e.g., memory 214), and communication units 216 (e.g., a communicator or communication interface). The functions and features of processor 212, communication unit 216, and memory 214 may be similar to those of processor 202, communication unit 206, and memory 204 of the MnS consumer 210, respectively. Therefore, for the sake of brevity, detailed descriptions thereof are omitted herein.

[0030] Reference Figures 3A to 3BThe diagram illustrates the processing flow in MnS consumer 210, MnS producer 220, and O-RU 230. MnS consumer 210 may correspond to an SMO or a non-real-time RAN intelligent controller (non-RT-RIC). MnS producer 220 may correspond to an O-DU and is therefore interchangeably referred to as O-DU 220. MnS consumer 210, MnS producer 220, and O-RU 230 can be configured to implement radio frequency (RF) channel reconfiguration and / or sleep modes for transmission (TRx) control to facilitate network energy saving (NES). This processing flow can be implemented based on the following preconditions: • A connection was successfully established between the MnS producer 220 and the MnS consumer 210 of the O-DU via the O1 interface. • A connection was successfully established between O-DU 220 and O-RU 230 via the forward M-plane (FH-M-Plane). • In a tiered deployment, the O-DU 220 is aware of the TRx control capabilities of the O-RU 230. MnS consumer 210 has subscribed to Configuration Management (CM) notifications.

[0031] Figures 3A to 3B The processing flow described in the text illustrates the changes to the TRx-based NES implementation using the O1 interface.

[0032] At step 302a, the MnS consumer 210 sends a request to the MnS producer 220 using the O1 interface to obtain capabilities associated with the O-DU 220. In this embodiment, the request may be for TRx control capabilities received by the O-DU 220 from the MnS consumer 210. <rpc> <get>Order. <rpc> <get>The command requests information about the capabilities of the O-DU 220.

[0033] MnS consumer 210 can also be configured to retrieve TRx control-related information associated with O-RU 230, which is connected to MnS producer 220. In a hierarchical architecture, MnS consumer 210 can retrieve capability information of O-RU 230 via the O1 interface, as shown in step 302b. In this embodiment, MnS producer 220 can send a request to O-RU 230 to obtain information related to the TRX control-related capabilities of O-RU 230. This request can be sent by MnS producer 220 via the FH M-plane interface. <rpc> <get>Order.

[0034] In the hybrid architecture, the MnS consumer 210 can directly retrieve the TRx control-related capabilities of the O-RU 230 via the FH-M plane, as shown in step 302c. In this embodiment, the MnS consumer 210 can send a request to the O-RU 230 to obtain information related to the TRX control-related capabilities of the O-RU 230.

[0035] In one embodiment, the O-RU 230 may send a response indicating the capability parameters of the O-RU 230 to the MnS consumer 210 and / or the MnS producer 220. The capability parameters may refer to TRx control-related capabilities or TRx control-related network configuration (Netconf) capabilities. The response may contain the capability parameters. <rpc-reply>information. <rpc-reply>Messages can be sent via the FH M-plane interface.

[0036] In the layered architecture, when receiving from O-RU 230 <rpc-reply>When this is the case, the MnS producer 220 can announce the capabilities of the O-RU 230 and / or the capabilities of the MnS producer 220 to the MnS consumer 210. In this embodiment, the MnS producer 220 can send data to the MnS consumer 210 via the O1 interface. <rpc-reply>information. <rpc-reply>The message can indicate the TRx control-related capabilities of both MnS producer 220 and O-RU 230.

[0037] In some embodiments, the MnS consumer 210 may subscribe to notifications from the MnS producer 220 and / or the O-RU 230 to receive TRx control-related capabilities from the MnS producer 220 and / or the O-RU 230. In some embodiments, the MnS producer 220 may subscribe to notifications from the O-RU 230 to receive TRx control-related capabilities from the O-RU 230.

[0038] Next, a TRx-based energy-saving process can be implemented. Specifically, at step 304, the MnS consumer 210 can provide one or more policy / configuration information to the MnS producer 220 to implement a TRx-based energy-saving process. In one embodiment, the MnS consumer 210 can send specific configuration policy details or triggers to the MnS producer 220 to perform energy saving at the O-RU 230. In one embodiment, the MnS producer 220 can receive policy(s) via the O1 interface through one or more of a file management system or a Netconf yang model. The file management system can include the processes described in Sections 10.6 and 6.5.3 of O-RAN.WG10.OAM-architecture-R003-v11.0. In one embodiment, the policy / configuration details can include certain conditions related to antenna masking and / or sleep mode. In one embodiment, the MnS consumer 210 can use the O1 interface... <rpc> <edit-config> <policydetails>Commands are used to provide policy / configuration information. In one embodiment, the policy / configuration received from the MnS consumer 210 may correspond to one or more power-saving features and / or methods, such as, but not limited to, antenna masking, sleep mode, etc.

[0039] In one embodiment, in response to received policy / configuration information, the MnS producer 220 can perform policy processing. Specifically, at step 306, the MnS producer 220 can check one or more conditions associated with the received policy / configuration information. In one embodiment, the MnS producer 220 can check one or more conditions to perform TRx control. At step 308.1, the MnS producer 220 can be configured to monitor / collect relevant data based on one or more conditions / thresholds provided in the received policy / configuration. In particular, the MnS producer 220 can determine whether the conditions / thresholds provided in the received policy / configuration are met. In one embodiment, the conditions / thresholds can be based on physical resource block (PRB) usage or traffic KPI thresholds, etc. The SMO can monitor conditions / thresholds by consuming PM counters from O-DU and O-CU, as well as O-RU. The SMO analyzes PM counters, notifications, and alarms, and generates policies and / or triggers or provides configuration details to O-DU for TRx control and advanced sleep mode use cases.

[0040] At step 308.2, the MnS producer 220 can send a specific antenna mask and / or sleep mode to be activated to the O-RU 230 via control plane (C-plane) messages. For example, the MnS producer 220 can use the FH-C-plane to communicate appropriate antenna mask values ​​and / or sleep modes to the O-RU. In an embodiment, the specific antenna mask and / or sleep mode can be based on a policy / configuration received from the MnS consumer 210 via the O1 interface. In one embodiment, the MnS producer 220 can send one or more NES commands to the O-RU 230 based on the received policy / configuration information. One or more NES commands can be sent to activate one or more power-saving features, such as, but not limited to, TRx control, advanced sleep mode, deep sleep mode, etc.

[0041] Upon receiving a C-plane message from MnS producer 220, O-RU 230 can subsequently process the C-plane message and activate the corresponding specific antenna mask and / or sleep mode, as shown in step 308.3. Furthermore, at step 310, MnS producer 220 can receive an acknowledgment (ACK) or non-ACK (NACK) message from O-RU 230. The ACK or non-ACK message can be based on the execution of one or more applied strategies. In an embodiment, O-RU 230 can send ACK / NACK messages to MnS producer / O-DU 220 via the FH-C plane.

[0042] At step 312, the MnS producer 220 may notify the MnS consumer 210 of the policy utilization status based on the ACK or NACK message received from the O-RU 230.

[0043] At step 314, the MnS consumer 210 can analyze the received policy utilization status.

[0044] Alternatively, at step 316, the MnS producer 220 can perform periodic performance monitoring (PM) reporting. In one embodiment, the MnS producer 220 can generate a PM counter report. The MnS producer 220 can send the generated PM counter report to the MnS consumer 210 via the O1 interface. The PM counter report can be based on an ACK or NACK message from the O-RU 230. At step 318, the MnS consumer 210 can analyze the PM data (i.e., the PM counter report) received from the MnS producer 220.

[0045] In one embodiment, at step 320, MnS consumer 210 can remove one or more policies / configurations by sending a policy removal message to MnS producer 220. MnS consumer 210 can remove one or more policies based on analyzed policy utilization status and / or PM data. In another embodiment, MnS consumer 210 can update one or more policies / configurations based on analyzed policy utilization status and / or PM data. MnS consumer 210 can update one or more policies / configurations by sending a policy update message to MnS producer 220. In response to the sent policy removal message and / or policy update message, at step 322, MnS consumer 210 can receive notifications related to policy removal and / or update status.

[0046] Figures 4A to 4B The illustration shows a processing flow 400 in an MnS consumer 210, an MnS producer 220, and an O-RU 230 according to another embodiment of this disclosure. The MnS consumer 210 may correspond to an SMO or a non-real-time RAN intelligent controller (non-RT-RIC). The MnS producer 220 may correspond to an O-DU, and is therefore interchangeably referred to as O-DU 220. Figures 4A to 4B In this configuration, the MnS consumer 210, MN producer 220, and O-RU 230 can be configured to reconfigure the radio frequency (RF) channels to enable advanced sleep modes in order to promote network energy saving (NES).

[0047] Steps 402.a to 408.1 are similar to 302.a to 308.1, as referenced. Figure 3A As explained, however, in steps 402a to 402c, the MnS consumer 210 may receive advanced sleep mode related capabilities instead of TRx control related capabilities. The MnS consumer 210 may retrieve this advanced sleep mode related capability based on steps similar to those performed to retrieve TRx control related capabilities. Therefore, for the sake of brevity, a detailed implementation of this step is omitted.

[0048] When retrieving advanced sleep mode-related capabilities from the O-RU 230, an energy-saving process based on the advanced sleep mode is implemented. Specifically, at step 404, the MnS consumer 210 can provide one or more policy / configuration information to the MnS producer 220 to implement the energy-saving process based on the advanced sleep mode. In one embodiment, the MnS consumer 210 can send specific configuration policy details or triggers from the O-RU 230 to the MnS producer 220 to perform energy saving. In one embodiment, the MnS producer 220 can receive one or more policy lists via the O1 interface through a file management system or the Netconf yang model, as discussed above. Then, the O-DU 220 can provide / apply and / or implement policies related to the advanced sleep mode at the O-RU 230. Specifically, at step 406, the MnS producer 220 can check one or more conditions related to the advanced sleep mode. At step 408.1, the MnS producer 220 can monitor / collect relevant data. Next, at step 408.2, the MnS producer 220 can activate or deactivate the appropriate advanced sleep mode in the O-RU 230 via the FH-C plane or M plane, respectively, using C-plane or M-plane messages. Specifically, at step 408.3, the O-RU 230 can activate / deactivate a specific deep sleep mode based on commands / instructions and / or triggers received from the MnS producer 220. In an alternative embodiment, if deactivation via the C-plane is unavailable, the MnS producer 220 can utilize the M-Plane to deactivate the advanced sleep mode. Thereafter, the O-RU 230 can process C-plane or M-plane messages and activate / deactivate the corresponding advanced sleep mode.

[0049] Steps 410 to 422 are similar Figures 3A to 3B Steps 310 to 322 are explained in the text, so for the sake of brevity, the specific implementation of steps 410 to 422 is omitted.

[0050] Figure 5A An O-DU information model is described using a file management process for TRx control (NESPolicy) containment and advanced sleep mode (NESPolicy) containment. If any policy parameter(s) need to be changed, the O-DU 220 can download a list of the entire policy or a specific policy file once the MnS consumer 210 indicates file availability. In some embodiments, this can be a completely vendor-specific implementation. In some embodiments, the MnS consumer 210 pushes a read-only policy file to the O-DU 220, and the way the MnS consumer 210 prepares the policy and the O-DU 220 reads and implements the policy is a proprietary implementation because a standardized process does not exist. A standardized policy framework is beneficial for ensuring consistency and interoperability because some policy parameters can be reused from the FH specification.

[0051] Figure 5B An O-DU information model for policy processing based on the Netconf Yang network is described, which is common to both TRx control (NESPolicy) containment and advanced sleep mode (NESPolicy) containment. Figure 5B Part (a) relates to network energy conservation (NESPolicy) containment, while Figure 5B Part (b) involves the inheritance of Network Energy Conservation (NESPolicy).

[0052] As described above, the MnS consumer 210 (SMO / non-RT RIC) pushes policy or configuration details to the O-DU 220 and / or sends triggers / requests to the O-DU 220 to activate or deactivate TRx control in the O-RU 230. In this embodiment, the Network Configuration Protocol (NETCONF) scheme for pushing policies to the O-DU 220 is as follows:

[0053] In the embodiment, since each cell may have a corresponding policy or a list of policies, trxCtrlPolicyList can be sent by MnS consumer 210 (SMO / non-RRIC) for a given cell in the network (given the various granularities in the FH implementation (for each array for TRx control and for each carrier / array / O-RU for ASM)).

[0054] In this embodiment, the policy configuration example is mentioned below:

[0055] According to one or more embodiments of this disclosure, details of the policy (configuration) parameters are provided in Table 1. Table 1

[0056] In this embodiment, the pattern for deleting or modifying the list of TRx control policies with ID "0" from the runtime configuration is as described below:

[0057] In this embodiment, the pattern for deleting or modifying a specific TRx control policy from the specified list of TRx control policies with ID "0" in the runtime configuration is as described below:

[0058] In one embodiment, the pattern for removing or modifying one or more parameters of a TRx policy in a specified list of TRx control policies with ID "1111" from the runtime configuration is as described below:

[0059] In one or more embodiments, this disclosure discloses an O-DU data model related to network power saving and an associated Netconf Yang implementation. A tree view of the O-DU data model specifically for network power saving implementation is provided below:

[0060] In one or more embodiments, a complete tree view of the GNBDU functional data model is provided below:

[0061] In this embodiment, the Netconf Yang data model for O-DU specifically designed for network power saving is provided below:

[0062] Details regarding the attributes are mentioned in Table 2 below: Table 2

[0063] Details regarding the attributes are mentioned in Table 3 below: Table 3

[0064] In some embodiments, because the O-RU 230 can support any antenna mask, the isNullable value for the attribute "antennaMask" being "true" allows the SMO (MnS producer 210) to instruct the O-DU 220 to use any mask.

[0065] Details regarding attribute constraints are mentioned in Table 4 below: Figure 4

[0066] Figure 6 A flowchart of an example method 600 according to another embodiment of the present disclosure is illustrated. Method 600 can be performed by MnS consumer 210 and / or associated device 201.

[0067] At step 602, the MnS consumer 210 can receive TRx control-related capability information corresponding to the O-RU 230 and the MnS producer 220 from the MnS producer 220. In one embodiment, the MnS producer 220 can receive the TRx control-related capability information from the O-RU 230. The MnS producer 220 can receive the TRx control-related capability information from the O-RU 230 via the M-plane. Then, the MnS producer 220 can send the received TRx control-related capability information from the O-RU 230 to the MnS consumer 210 via the O1 interface.

[0068] At step 604, the MnS consumer 210 may send one or more policies and / or configurations for the O-RU 230 based on the received TRx control-related capability information corresponding to the O-RU 230 and the MnS producer 220. One or more policies and / or configurations may be sent by the MnS consumer 210 to the MnS producer 220. In some non-limiting embodiments, the MnS consumer 210 may send one or more policies and / or configurations via one or more of the Network Configuration Protocol (NETCONF), a file management system, or Remote Procedure Call (RPC) commands. One or more policies and / or configurations may correspond to one or more Network Energy Saving (NES) policies to be implemented at the O-RU 230.

[0069] At step 606, MnS consumer 210 may receive a policy utilization status indicating the implementation of at least one policy and / or configuration among one or more policies at O-RU 230. MnS consumer 210 may receive the policy utilization status from MnS producer 220. In one embodiment, upon receiving the policy utilization status, MnS consumer 210 may determine, based on the received policy utilization status, whether there is a need to remove or update at least one of the one or more policies. In one embodiment, MnS consumer 210 may receive a notification or a performance monitoring (PM) counter report at O-RU 230 that includes the policy utilization status of at least one of the one or more policies. MnS consumer 210 may receive a notification or a PM counter report from MnS producer 220. In one embodiment, MnS producer 220 may check one or more conditions associated with O-RU 230 based on one or more policies and / or configurations. After successfully checking one or more conditions, MnS producer 220 may apply and / or implement one or more policies at O-RU 230. One or more policies are applied by activating one or more TRX control configurations and advanced sleep mode configurations in O-RU 230. In one embodiment, MnS producer 220 can apply policies by activating one or more TRx control configurations and advanced sleep modes in O-RU 230. The one or more policies can be one input from MnS consumer 210; additionally, MnS consumer 210 can provide configuration details or configure MnS generator 220 to activate a specific TRx control configuration and / or advanced sleep mode. Based on the execution of one or more policies applied at O-RU 230, MnS producer 220 can receive one of an acknowledgment message or an unacknowledgment message from O-RU 230. Based on the received acknowledgment or unacknowledgment message, MnS producer 220 can send a policy utilization status to MnS consumer 210.

[0070] Furthermore, after determining the need to remove or update at least one of one or more policies, the MnS consumer 210 can send a policy removal or update command for the determined at least one policy. In an embodiment, the MnS consumer 210 can send the policy removal or update command to the MnS producer 220.

[0071] Figure 7 An embodiment of device / apparatus 700 is illustrated. (As shown) Figure 7 As shown, device 700 includes a processor 710, a memory 720, a storage component 730, an input component 740, an output component 750, a communication interface 760, and a bus 770. Device 700 may be associated with MnS consumer 210, MnS producer 220, or O-RU 230. In one embodiment, device 700 may correspond to device 201 and / or device 203.

[0072] As used herein, processor 710 refers to any type of computing circuitry that may include hardware and software elements. 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, etc. 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.

[0073] Memory 720 includes a non-transitory computer-readable medium. Memory 720 includes random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic storage, and / or optical storage) that stores information and / or instructions for use by processor 710. Memory 720 includes machine-readable instructions executable by processor 710. When executed by processor 710, these machine-readable instructions cause processor 710 to perform one or more method steps of the embodiments described above.

[0074] Storage component 730 stores information and / or software related to the operation and use of device 700. For example, storage component 730 may include hard disks (e.g., magnetic disks, optical disks, magneto-optical disks, and / or solid-state disks), compact discs (CDs), digital versatile discs (DVDs), floppy disks, cassette tapes, magnetic tapes, and / or another type of non-transitory computer-readable media, as well as corresponding drives.

[0075] Input component 740 is configured to receive information, such as user input. For example, input component 740 may include, but is not limited to, a touchscreen display, keyboard, keypad, mouse, button, switch, and / or microphone. Additionally or alternatively, input component 740 may include sensors for sensing information (e.g., Global Positioning System (GPS), accelerometer, gyroscope, and / or actuator).

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

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

[0078] Bus 770 serves as an interconnect between the processor 710, memory 720, storage component 730, input component 740, output component 750, and communication interface 760 of device 700. Bus 770 may include wired or wireless interconnection.

[0079] Figure 7 The number and arrangement of components shown are provided as an example. In practice, device 700 may include components related to... Figure 7 The components shown may be additional components, fewer components, different components, or components with different arrangements compared to the components shown. Additionally or alternatively, a set of components of device 700 (e.g., one or more components) may perform one or more functions described as being performed by another set of components of device 700. Furthermore, multiple devices 700 communicating with each other may be used to perform one or more method steps described in any embodiment.

[0080] This disclosure describes systems and methods for implementing network power saving using the O1 interface. This disclosure also discloses O-DU information models and O-DU data models related to network power saving implementation using the O1 interface. Furthermore, the disclosed systems and methods enable changes to TRx control and / or network power saving based on advanced sleep modes via the O1 interface and other associated interfaces, such as the Fronthaul interface between the O-DU and O-RU. [1] An apparatus configured to: Receive one or more policies for Open Radio Access Network (ORAN) - Radio Unit (O-RU) from the Management Service (MnS) consumer; Based on one or more strategies, examine one or more conditions associated with the O-RU; After successfully checking one or more conditions, apply one or more policies at the O-RU; Based on the execution of one or more applied strategies, receive one of an acknowledgment message or a non-acknowledgment message from the O-RU; and Based on one of the received acknowledgment or unacknowledgment messages, the policy utilization status is sent to the MnS consumer. [2] According to the apparatus of [1], wherein one or more strategies indicate at least one of an antenna mask value or a sleep mode to be implemented at the O-RU, and in order to apply one or more strategies, the apparatus is configured to: Based on one or more strategies, send at least one of the following to the O-RU: antenna mask value or sleep mode. [3] The apparatus according to any one of [1] to [2], wherein, in order to apply one or more strategies at the O-RU, the apparatus is configured to: Based on one or more policies received, send one or more Network Energy Saving (NES) commands to the O-RU. [4] The apparatus according to any one of [1] to [3], wherein the apparatus is configured to: Send transmission (TRx) control-related capability information corresponding to MnS producers and O-RUs to MnS consumers. [5] The apparatus according to any one of [1] to [4], wherein the apparatus is implemented at the MnS producer. [6] An apparatus configured to: Receive TRx control-related capability information corresponding to the MnS producer or O-RU from at least one of the MnS producer or O-RU; Based on the received TRx control-related capability information corresponding to the O-RU and MnS producers, one or more policies for the O-RU are sent to the MnS producers; and Receive policy utilization status from the MnS producer, which indicates the implementation of at least one of one or more policies at the O-RU. [7] According to the apparatus of [6], the apparatus is configured to, after receiving the policy utilization state: Based on the received policy utilization status, determine whether there is a need to remove or update at least one of one or more policies; and After determining the need to remove or update at least one of one or more strategies, remove or update at least one of the determined strategies. [8] The apparatus according to any one of [6] to [7], wherein in order to receive the strategy utilization status, the apparatus is configured to receive a notification or performance monitoring (PM) counter report from the MnS producer, the notification or PM counter report including the strategy utilization status of at least one of one or more strategies. [9] The apparatus according to any one of [6] to [8], wherein, in order to transmit one or more strategies, the apparatus is configured to: Send one or more policies to MnS producer 220 via at least one of the following: Network Configuration Protocol (NETCONF), file management system, or Remote Procedure Call (RPC) commands.

[10] The apparatus according to any one of [6] to [9], wherein, in order to receive the strategy utilization state, the apparatus is configured to: Receive a notification or performance monitoring (PM) counter report from the MnS producer, which includes the policy utilization status of at least one of one or more policies at the O-RU.

[11] The device according to any one of [6] to

[10] , wherein the device is configured as one of the following: Receive TRx control-related capability information corresponding to the O-RU from the MnS producer via the O1 interface; or The TRx control-related capability information corresponding to the O-RU is received from the O-RU via the management plane (M-plane).

[12] The apparatus according to any one of [6] to

[11] , wherein the apparatus is implemented at a managed service (MnS) consumer.

[13] The apparatus according to any one of [6] to

[12] , wherein the apparatus is based on a communication interface corresponding to one of: Service Management and Orchestration (SMO) or Near Real-Time Radio Access Network (RAN) Intelligent Controller (Near RT RIC).

[14] A method comprising: The MnS consumer receives TRx control-related capability information corresponding to the O-RU and MnS producer from at least one of the MnS producer or O-RU; Based on the received TRx control-related capability information corresponding to the O-RU and MnS producers, the MnS consumer sends one or more policies for the O-RU to the MnS producer; and The MnS consumer receives a policy utilization status from the MnS producer, which indicates the implementation of at least one of one or more policies at the O-RU.

[15] According to the method of

[14] , the method further includes, after receiving the policy utilization state: Based on the received policy utilization status, the MnS consumer determines whether there is a need to remove or update at least one of one or more policies; and After determining the need to remove or update at least one of one or more policies, the MnS consumer removes or updates at least one of the determined policies.

[16] The method according to any one of

[14] to

[15] , wherein the state utilized by the MnS consumer receiving strategy includes: Receive a notification or performance monitoring (PM) counter report from the MnS producer, the notification or PM counter report including the strategy utilization status of at least one of one or more strategies.

[17] The method according to any one of

[14] to

[16] , wherein sending one or more strategies includes: One or more policies are sent from the MnS consumer to the MnS producer via at least one of the following: Network Configuration Protocol (NETCONF), file management system, or Remote Procedure Call (RPC) commands.

[18] The method according to any one of

[14] to

[17] , wherein receiving TRx control-related capability information by the MnS consumer includes: The MnS producer receives TRx control-related capability information from the O-RU via the M-plane; The MnS generator sends the received TRx control-related capability information to the MnS consumer via the O1 interface.

[19] The method according to any one of

[14] to

[18] , wherein receiving TRx control-related capability information by the MnS consumer includes: The MnS consumer receives the corresponding TRx control-related capability information from the O-RU via the M-plane.

[20] The method according to any one of

[14] to

[19] , wherein one or more policies correspond to one or more energy-saving network (NES) policies to be implemented at the O-RU.

[21] The method of claim 14, wherein, for a receiving policy utilization state, the method includes: Based on one or more strategies, the MnS producer checks one or more conditions associated with the O-RU; After successfully checking one or more conditions, the MnS producer applies one or more policies at the O-RU. Based on the execution of one or more applied strategies, the MnS producer receives one of an acknowledgment message or an unacknowledgment message from the O-RU; and Based on either the received acknowledgment message or the unacknowledgment message, the MnS producer sends the policy utilization status.

[22] A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions, which, when executed by a Management Service (MnS) consumer, the MnS consumer including one or more processors, cause the one or more processors to: Receive transmission (TRx) control-related capability information corresponding to Open Radio Access Network (ORAN) - Radio Unit (O-RU) and MnS producer from MnS producer; Based on the TRx control-related capability information received corresponding to the O-RU and MnS producers, one or more policies for the O-RU are sent to the MnS producer; and Receive policy utilization status from MnS producer, which indicates the implementation of at least one of one or more policies at O-RU.

[23] A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions, which, when executed by a Management Service (MnS) producer, the MnS producer including one or more processors, cause the one or more processors to: Receive one or more policies from MnS consumers for Open Radio Access Network (ORAN) - Radio Unit (O-RU); Based on one or more policies received, examine one or more conditions associated with the O-RU; After successfully checking one or more conditions, apply one or more policies at the O-RU; Based on the execution of one or more applied strategies, receive one of an acknowledgment message or a non-acknowledgment message from the O-RU; and Based on one of the received acknowledgment or unacknowledgment messages, the policy utilization status is sent to the MnS consumer.

[0081] The embodiments disclosed herein can be implemented by at least one software program that runs on at least one hardware device and performs network management functions to control elements. An element can be at least one of a hardware device or a combination of a hardware device and a software module.

[0082] While specific language has been used to describe this disclosure, it is not intended to create any limitation. It will be apparent to those skilled in the art that various working modifications can be made to the method in order to realize the inventive concepts taught herein.

[0083] The accompanying drawings and the foregoing description provide examples of embodiments. Those skilled in the art will understand that one or more of the described elements can be well combined into a single functional element. Alternatively, certain elements may be divided into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, the processing order described herein may be changed, and the methods are not limited to those described herein.

[0084] Furthermore, the actions in any flowchart need not be performed in the order shown; nor is it necessary to execute all actions. Similarly, actions that are independent of other actions can be performed in parallel with other actions. The scope of the embodiments is by no means limited to these specific examples. Many variations are possible, such as differences in structure, dimensions, and materials used, whether or not explicitly given in the specification. The scope of the embodiments is at least as wide as given by the appended claims.

[0085] The benefits, other advantages, and solutions to problems have been described above with reference to specific embodiments. However, the benefits, advantages, solutions to problems, and any components that may make any benefit, advantage, or solution occur or become more significant should not be construed as key, necessary, or essential features or components of any or all claims.

[0086] The foregoing description of specific embodiments will fully reveal the general nature of the embodiments herein, enabling others to readily modify and / or adapt various applications of such specific embodiments by applying present knowledge without departing from the general concept. Therefore, such adaptations and modifications should and are intended to be understood within the meaning and scope of equivalents of the disclosed embodiments. It should be understood that the wording or terminology used herein is for descriptive purposes and not for limitation. Thus, although embodiments herein have been described according to at least one embodiment, those skilled in the art will recognize that modifications can be made to practice the embodiments herein within the spirit and scope of the embodiments described herein.< / policydetails> < / edit-config> < / rpc> < / get> < / rpc> < / get> < / rpc> < / get> < / rpc>

Claims

1. An apparatus (203) configured to: Receive one or more policies from the Management Service MnS consumer (210) for the Open Radio Access Network (ORAN) Radio Unit (O-RU) (230); Based on the one or more strategies, examine one or more conditions associated with the O-RU (230); After successfully checking one or more of the conditions, apply one or more of the strategies at the O-RU (230); Based on the execution of the one or more policies applied, receive one of an acknowledgment message and a non-acknowledgment message from the O-RU (230); as well as Based on one of the received confirmation message and the non-confirmation message, the policy utilization status is sent to the MnS consumer (210).

2. The apparatus (203) of claim 1, wherein the one or more strategies indicate at least one of an antenna mask value or a sleep mode to be implemented at the O-RU (230), and in order to apply the one or more strategies, the apparatus (203) is configured to: Based on one or more of the strategies, the antenna mask value or at least one of the sleep modes is sent to the O-RU (230).

3. The apparatus (203) according to claim 1, wherein, in order to apply the one or more strategies at the O-RU (230), the apparatus (203) is configured to: Based on the received one or more policies, send one or more Network Energy Saving (NES) commands to the O-RU (230).

4. The apparatus (203) according to claim 1, wherein the apparatus (203) is configured to: prior to receiving the one or more strategies for the O-RU (230) Send the transmission TRx control related capability information corresponding to the MnS producer (220) and the O-RU (230) to the MnS consumer (210).

5. The apparatus (203) according to claim 1, wherein the apparatus (203) is implemented at the MnS producer (220).

6. An apparatus (201) configured to: Receive TRx control-related capability information corresponding to the MnS producer (220) and the O-RU (230) from at least one of the MnS producer (220) and the O-RU (230); Based on the received TRx control-related capability information corresponding to the O-RU (230) and the MnS producer (220), one or more policies for the O-RU (230) are sent to the MnS producer (220); and Receive policy utilization status from the MnS producer (220), the policy utilization status indicating the implementation of at least one of the one or more policies at O-RU (230).

7. The apparatus (201) according to claim 6, wherein after receiving the strategy utilization state, the apparatus (201) is configured to: Based on the received policy utilization status, determine whether there is a need to remove or update at least one of the one or more policies; and After determining the need to remove or update at least one of the one or more strategies, the determined at least one strategy is removed or updated.

8. The apparatus (201) of claim 6, wherein, in order to receive the strategy utilization status, the apparatus (201) is configured to receive from the MnS producer (220) a notification or a performance monitoring PM counter report, the notification or PM counter report including the strategy utilization status of at least one of the one or more strategies.

9. The apparatus (201) according to claim 6, wherein in order to send the one or more strategies, the apparatus (201) is configured to: The one or more policies are sent to the MnS producer (220) via at least one of the following: network configuration protocol NETCONF, file management system, or remote procedure call (RPC) command.

10. The apparatus (201) according to claim 6, wherein, in order to receive the strategy utilization state, the apparatus (201) is configured to: Receive a notification or a performance monitoring PM counter report from the MnS producer (220), the notification or PM counter report including the strategy utilization status of at least one of the one or more strategies at the O-RU (230).

11. The apparatus (201) according to claim 6, wherein the apparatus (201) is configured as one of the following: Receive TRx control-related capability information corresponding to the O-RU (230) from the MnS producer (220) via the O1 interface; or The TRx control-related capability information corresponding to the O-RU (230) is received from the O-RU (230) via the management-plane M-plane.

12. The apparatus (201) according to claim 6, wherein the apparatus (201) is implemented at the management service MnS consumer (210).

13. The apparatus (201) of claim 6, wherein the apparatus (201) is based on a communication interface corresponding to one of the following: Service Management and Orchestration (SMO) or Near Real-Time Radio Access Network (RAN) Intelligent Controller (Near RT RIC).

14. A method (600) comprising: The MnS consumer (210) receives (602) TRx control-related capability information corresponding to the O-RU (230) and the MnS producer (220) from at least one of the MnS producer (220) or the O-RU (230); Based on the received TRx control-related capability information corresponding to the O-RU (230) and the MnS producer (220), the MnS consumer (210) sends (604) one or more policies for the O-RU (230) to the MnS producer (220); as well as The MnS consumer (210) receives (606) a strategy utilization status from the MnS producer (220), the strategy utilization status indicating the implementation of at least one of the one or more strategies at the O-RU (230).

15. The method (600) of claim 14, wherein after receiving the policy utilization state, the method (600) further comprises: Based on the received policy utilization status, the MnS consumer (210) determines whether there is a need to remove or update at least one of the one or more policies; as well as After determining the need to remove or update at least one of the one or more policies, the MnS consumer (210) removes or updates the determined at least one policy.

16. The method (600) of claim 14, wherein receiving the policy utilization state by the MnS consumer (210) comprises: The MnS producer (220) receives a notification or a performance monitoring PM counter report, the notification or PM counter report including the strategy utilization status of at least one of the one or more strategies.

17. The method (600) of claim 14, wherein sending the one or more strategies comprises: The MnS consumer (210) sends one or more policies to the MnS producer (220) via at least one of the following: NETCONF (Network Configuration Protocol), file management system, or remote procedure call (RPC) command.

18. The method (600) of claim 14, wherein receiving the TRx control-related capability information by the MnS consumer (210) comprises: The MnS producer (220) receives the TRx control-related capability information from the O-RU (230) via the M-plane; The MnS generator (220) sends the received TRx control-related capability information to the MnS consumer (210) via the O1 interface.

19. The method (600) of claim 14, wherein receiving the TRx control-related capability information by the MnS consumer (210) comprises: The MnS consumer (210) receives the corresponding TRx control-related capability information from the O-RU (230) via the M-plane.

20. The method (600) of claim 14, wherein the one or more strategies correspond to one or more network energy saving (NES) strategies to be implemented at the O-RU (230).

21. The method (600) of claim 14, wherein, in relation to receiving the policy utilization state, the method (600) comprises: Based on the one or more strategies, the MnS producer (220) checks one or more conditions associated with the O-RU (230); After successfully checking one or more of the conditions, the MnS producer (220) applies one or more strategies at the O-RU (230); Based on the execution of the one or more strategies applied, the MnS producer (220) receives one of an acknowledgment message and a non-acknowledgment message from the O-RU (230); as well as Based on one of the received confirmation message and the non-confirmation message, the MnS producer (220) sends the policy utilization status.

22. A non-transitory computer-readable medium, the non-transitory computer-readable medium storing instructions, the instructions comprising: One or more instructions, which, when executed by a management service MnS consumer (210), the MnS consumer (210) includes one or more processors, such that the one or more processors: Receive transmission TRx control related capability information corresponding to the Open Radio Access Network (ORAN)-Radio Unit (O-RU) (230) and the MnS producer (220) from the MnS producer (220); Based on the received TRx control-related capability information corresponding to the O-RU (230) and the MnS producer (220), one or more policies for the O-RU (230) are sent to the MnS producer (220); as well as Receive policy utilization status from the MnS producer (220), the policy utilization status indicating the implementation of at least one of the one or more policies at O-RU (230).

23. A non-transitory computer-readable medium, the non-transitory computer-readable medium storing instructions, the instructions comprising: One or more instructions, which, when executed by a management service MnS producer (220), the MnS producer (220) includes one or more processors, such that the one or more processors: Receive one or more policies from the MnS consumer (210) for the Open Radio Access Network (ORAN) Radio Unit (O-RU) (230); Based on the received one or more policies, examine one or more conditions associated with the O-RU (230); After successfully checking one or more of the conditions, apply one or more of the strategies at the O-RU (230); Based on the execution of the one or more policies applied, receive one of an acknowledgment message and a non-acknowledgment message from the O-RU (230); as well as Based on one of the received, confirmed, and unconfirmed messages, the policy utilization status is sent to the MnS consumer (210).

Images