Device and method for implementing O-Cloud node P-state change

By controlling P-states of O-Cloud nodes through FOCOM and IMS, the method addresses inefficient power consumption in telecommunications networks, optimizing power usage based on traffic levels to enhance efficiency.

KR103043654B1Active Publication Date: 2026-11-06RAKUTEN MOBILE INC
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
KR1020247032405
Authority / Receiving Office
KR · KR
Patent Type
Patents
Current Assignee / Owner
Priority Date
2022-08-12
Filing Date
2022-11-14
Publication Date
2026-11-06
Estimated Expiration
2042-11-14

AI Technical Summary

Technical Problem

In telecommunications networks, O-Cloud nodes consume unnecessary power due to CPUs operating at full capacity even when traffic levels do not require it, leading to inefficient power usage.

Method used

A method and system for managing power consumption by controlling the P-state (CPU operating frequency) of O-Cloud nodes within the O-Cloud infrastructure, utilizing a federated O-Cloud orchestration and management module (FOCOM) and infrastructure management service module (IMS) to monitor and adjust processor states based on traffic levels.

Benefits of technology

Reduces power consumption by dynamically adjusting CPU frequencies, optimizing power usage based on actual traffic demands, thereby enhancing efficiency and reducing energy waste.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure R1020247032405_ABST
    Figure R1020247032405_ABST
Patent Text Reader

Abstract

A system and method for reducing power consumption associated with processors within an O-Cloud (open cloud) infrastructure by modifying the P-state of processors in O-Cloud nodes within an O-Cloud (open cloud) infrastructure of a telecommunications network are provided, wherein the system and method comprise: transmitting a request to an infrastructure management service module (IMS) via an O2 interface to modify the P-state of a processor in an O-Cloud node by FOCOM; receiving a request to modify the P-state of a processor in an O-Cloud node via an O2 interface by IMS; controlling the implementation of the request to modify the P-state of a processor in an O-Cloud node by IMS; and transmitting a confirmation of the modification of the P-state of a processor in an O-Cloud node to FOCOM via an O2 interface by IMS.
Need to check novelty before this filing date? Find Prior Art

Description

Technology Field

[0001] [Cross-reference to related application(s)]

[0002] This application is based on and claims priority from Singapore provisional patent application No. 10202250732B filed with the Singapore Intellectual Property Office on August 12, 2022, the entire contents of which are incorporated herein by reference.

[0003] [Technology Field]

[0004] The devices and methods according to exemplary embodiments of the present disclosure relate to methods for optimizing process power consumption in distributed network devices. Background Technology

[0005] In the relevant technology field, a radio access network (RAN) is an important component of a telecommunications system because it connects end-user devices (or user equipment) to other parts of the network. A RAN includes a combination of various network elements (NEs) that connect end-user devices to the core network. Traditionally, the hardware and / or software of a specific RAN is vendor-specific.

[0006] Open RAN (O-RAN) technology emerged to enable multiple vendors to provide hardware and / or software for telecommunications systems. To this end, O-RAN allows RAN functions to be decomposed into Centralized Units (CUs), Distributed Units (DUs), and Radio Units (RUs). A CU is a logical node for hosting the RAN's Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and / or Packet Data Convergence Protocol (PDCP) sublayers. A DU is a logical node for hosting the RAN's Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) sublayers. An RU is a physical node that converts radio signals from antennas into digital signals that can be transmitted to the DU via FrontHaul. Because these entities have open protocols and interfaces among themselves, they can be developed by different vendors.

[0007] FIG. 1 is a diagram of the O-RAN architecture of the relevant technology, FIG. 2 is a diagram of the SMO (Service Management and Orchestration) framework of the relevant technology having a NRT (non-real-time) RIC (RAN Intelligent Controller) architecture in the function view, and FIG. 3 is a diagram of the SMO framework of the relevant technology having an NRT RIC in the service view. Referring to FIG. 1 through 3, RAN functions in the O-RAN architecture are controlled and optimized by RICs. RICs are software-defined components that implement modular applications to automate and optimize RAN operations as well as to facilitate the multi-vendor operability required in O-RAN systems. RICs are divided into two types: NRT RICs and nRT RICs (near-real-time RICs).

[0008] The NRT RIC is a control point of a non-real-time control loop and operates on a timescale greater than 1 second within the SMO framework. Its functionalities are implemented through modular applications called rApps (rApp 1, ..., rApp N in FIGS. 1 to 3) and include providing policy-based guidance and enrichment over an A1 interface, which is an interface enabling communication between the NRT RIC and the nRT RIC; performing data analysis; AI / ML (Artificial Intelligence / Machine Learning) training and inference for RAN optimization; and / or recommending configuration management actions through an O1 interface, which is an interface connecting the SMO to RAN management elements (e.g., nRT RIC, O-CU (O-RAN Centralized Unit), O-DU (O-RAN Distributed Unit), etc.).

[0009] The nRT RIC operates on a timescale between 10 milliseconds and 1 second and connects to the O-DU, O-CU (decomposed into O-CU-CP (O-CU control plane) and O-CU-UP (O-CU user plane)), and O-eNB (open evolved NodeB) via the E2 interface. The nRT RIC uses the E2 interface to control the underlying RAN elements (E2 nodes / NFs (network functions)) through a near real-time control loop. The nRT RIC monitors, pauses / stops, overrides, and controls the E2 nodes (O-CU, O-DU, and O-eNB) through policies. For example, nRT sets policy parameters for the active functions of the E2 nodes. Additionally, the nRT RIC hosts xApps to implement functions such as Quality of Service (QoS) optimization, mobility optimization, slicing optimization, interference mitigation, load balancing, and security. Two types of RICs work together to optimize O-RAN. For example, the NRT RIC provides policies, data, and artificial intelligence (AI) / machine learning (ML) models that are implemented and used by the nRT RIC for RAN optimization through the A1 interface, and the nRT returns policy feedback (i.e., how the policies set by the NRT RIC are performing).

[0010] The SMO framework, in which the NRT RIC resides, manages and orchestrates RAN elements. Specifically, SMO manages and orchestrates what is referred to as the O-Cloud (O-RAN Cloud). The O-Cloud is a collection of RICs, O-CUs, and O-DUs, supporting software components (e.g., operating systems and runtime environments), and physical RAN nodes hosting SMO itself. In other words, SMO manages the O-Cloud from within. The O2 interface is the interface between SMO and the O-Cloud in which it resides. Through the O2 interface, SMO provides infrastructure management services (IMS) and deployment management services (DMS).

[0011] Each O-Cloud node typically contains one or more processors or CPUs, and each such processor consumes a given amount of power. One known method of CPU power management is the modification of the processor's C-states and P-states. More specifically, there are generally two ways of managing power consumed by a CPU: (1) removing power consumed by a specific subsystem of the CPU (e.g., one or more cores or a specific memory cache) by completely turning off the power of said subsystem (i.e., removing the voltage supply to the CPU's associated subsystems, thereby reducing or turning off specific functions); or (2) reducing power consumption by reducing the voltage and / or frequency of the CPU (or one or more of its subsystems). Of these two options, the former is achieved by modifying the processor's "C-state" (also known as "idle state" or "idle power saving state"), and the latter is achieved by modifying the "P-state" (also known as "execution power saving state").

[0012] Generally, C-states and P-states are numbered starting from zero (e.g., C0, C1... and P0, P1...). The general convention is that higher numbers represent greater power savings. C0 signifies no power saving, as everything remains turned on. Similarly, P0 represents maximum performance, and therefore maximum frequency, voltage, and power consumption. Different CPUs have different C-states and P-states.

[0013] P-states are relevant only when the CPU core is in the C0 state, because the CPU must be supplied with power to execute code. P-states allow changes in the CPU core's voltage and frequency (i.e., operating point) to reduce power consumption by the CPU. There is a set of P-states corresponding to different operating points (voltage-frequency pairs), and a given P-state refers to one such operating point. The peak (frequency and voltage) operating point is typically the maximum performance state, P0. Generally, modifications to P-states are achieved by selecting the desired CPU operating frequency (and the voltage is modified accordingly). As with C-states, different CPUs have different available P-states. Additionally, most modern CPUs have multiple cores within a single package, and the CPU's P-states can be changed at the CPU package level or at the individual core level.

[0014] Exemplary embodiments of the present disclosure provide a method and system for managing the power consumption of an O-Cloud node by controlling the P-state (i.e., CPU operating frequency) of one or more processors integrated into the node.

[0015] In the relevant technology, the CPUs included in O-Cloud nodes can operate at full capacity and full power even if the amount of traffic generated on the node does not guarantee such operating capacity or associated power consumption, resulting in unnecessary and inefficient power consumption. means of solving the problem

[0016] According to embodiments, systems and methods are provided for modifying the P-state of processors at O-Cloud nodes within the O-Cloud infrastructure of a telecommunications network in order to reduce power consumption associated with processors within the O-Cloud (open cloud) infrastructure.

[0017] According to an embodiment, a method for managing power consumption of one or more O-Cloud nodes within an O-Cloud infrastructure of a telecommunications network comprises: a step of obtaining a request to modify the P-state of a processor of an O-Cloud node within an O-Cloud infrastructure of a telecommunications network, which is performed by at least one processor and also by a federated O-Cloud orchestration and management module (FOCOM) within a service management orchestration (SMO) framework; a step of transmitting the request to modify the P-state of a processor of an O-Cloud node to an infrastructure management service module (IMS) via an O2 interface by FOCOM; a step of receiving the request to modify the P-state of a processor of an O-Cloud node by IMS via an O2 interface; a step of controlling the implementation of the request to modify the P-state of a processor of an O-Cloud node by IMS; and a step of transmitting confirmation of the modification of the P-state of a processor of an O-Cloud node to FOCOM via an O2 interface by IMS.

[0018] A method performed by at least one processor further comprises: monitoring O-Cloud data received through an O2 interface by a non-real-time radio intelligent controller (NRT RIC); analyzing O-Cloud data and, based on the analysis, identifying an O-Cloud node to be modified within the O-Cloud infrastructure; and transmitting an O-Cloud node P-state modification request to FOCOM.

[0019] A method performed by at least one processor further comprises: monitoring O-Cloud data received by a user through an O2 interface; analyzing O-Cloud data and, based on the analysis, identifying an O-Cloud node to be changed within the O-Cloud infrastructure; and transmitting an O-Cloud node P-state modification request to FOCOM.

[0020] A method performed by at least one processor may further include the step of transmitting to at least one of a user and a non-real-time radio intelligent controller (NRT RIC) by FOCOM confirmation of a P-state modification of a process of the O-Cloud node.

[0021] O-Cloud data received through the O2 interface may include at least one of processor utilization and memory utilization.

[0022] According to an embodiment, a system for managing the power consumption of one or more O-Cloud nodes within an O-Cloud infrastructure of a telecommunications network is provided, wherein the system comprises: at least one memory configured to store computer program code; and at least one processor configured to access the at least one memory and also to operate as directed by the computer program code, wherein the computer program code comprises: O-Cloud infrastructure implementation code configured to cause at least one processor to implement (i) a federated O-Cloud orchestration and management module (FOCOM) within a service management orchestration (SMO) framework, (ii) an infrastructure management service module (IMS), and (iii) an O2 interface between the SMO and the IMS; acquisition code configured to cause at least one processor to obtain, by FOCOM, a request to modify the P-state of a processor of an O-Cloud node within the O-Cloud infrastructure of the telecommunications network; and transmission code configured to cause at least one processor to transmit a request to modify the P-state of a processor of an O-Cloud node from FOCOM to the IMS through the O2 interface. It includes a control code configured to cause at least one processor to implement a request by IMS to modify the P-state of the processor of the O-Cloud node; and a transmission code configured to cause at least one processor to transmit a confirmation of the modification of the P-state of the processor of the O-Cloud node from IMS to FOCOM through the O2 interface.

[0023] The O-Cloud infrastructure implementation code may further include code configured to cause at least one processor to implement a non-real-time radio intelligent controller (NRT RIC), and the computer program code may further include: monitoring code configured to cause at least one processor to receive O-Cloud data by the NRT RIC through an O2 interface; analysis code configured to cause at least one processor to analyze O-Cloud data by the NRT RIC and to identify O-Cloud nodes to be modified within the O-Cloud infrastructure based on the analysis; and transmission code configured to cause at least one processor to transmit an O-Cloud node P-state modification request to FOCOM by the NRT RIC.

[0024] The system may additionally include a human-machine interface configured to allow the user to receive and analyze O-Cloud data through the O2 interface and to allow the user to send O-Cloud node P-state modification requests to FOCOM.

[0025] According to an embodiment, a non-transient computer-readable medium storing instructions is provided, wherein the instructions, when executed by a processor, cause the processor to execute a method for managing the power consumption of one or more O-Cloud nodes within an O-Cloud (open cloud) infrastructure of a telecommunications network, and the method comprises: obtaining a request to modify the P-state of a processor of an O-Cloud node within the O-Cloud infrastructure of a telecommunications network by a Federationed O-Cloud Orchestration and Management Module (FOCOM) within a Service Management Orchestration (SMO) framework; transmitting the request to modify the P-state of a processor of an O-Cloud node to an Infrastructure Management Service Module (IMS) by FOCOM through an O2 interface; receiving the request to modify the P-state of a processor of an O-Cloud node by IMS through an O2 interface; and controlling the implementation of the request to modify the P-state of a processor of an O-Cloud node by IMS. and includes the step of transmitting confirmation of the P-state modification of the processor of the O-Cloud node to FOCOM via the O2 interface by IMS.

[0026] As a non-transient computer-readable medium storing instructions, the instructions, when executed by a processor, may cause the processor to perform the following additional operations: monitoring O-Cloud data received through an O2 interface by a non-real-time radio intelligent controller (NRT RIC); analyzing O-Cloud data and, based on the analysis, identifying an O-Cloud node to be modified within the O-Cloud infrastructure; and sending an O-Cloud node P-state modification request to FOCOM.

[0027] As a non-transient computer-readable medium storing instructions, the instructions, when executed by a processor, may cause the processor to perform the following additional operations: monitoring O-Cloud data received by a user through an O2 interface; analyzing O-Cloud data and, based on the analysis, identifying O-Cloud nodes to be changed within the O-Cloud infrastructure; and sending an O-Cloud node P-state modification request to FOCOM.

[0028] As a non-transient computer-readable medium in which instructions are stored, the instructions, when executed by a processor, may cause the processor to perform the following additional operations: transmitting to at least one of the user and the NRT RIC (non-real-time radio intelligent controller) by FOCOM an acknowledgment of the modification of the P-state of the O-Cloud node's process.

[0029] O-Cloud data received through the O2 interface includes at least one of processor utilization and memory utilization.

[0030] Additional aspects will be presented in part in the following description, will be apparent from the description, or may be realized by the practice of the embodiments presented in this disclosure. Brief explanation of the drawing

[0031] Features, aspects, and advantages of specific exemplary embodiments of the present disclosure will be described below with reference to the accompanying drawings, in which like reference numerals denote like elements: FIG. 1 is a diagram of an O-RAN architecture according to an embodiment. Figure 2 is a diagram of the Service Management and Orchestration (SMO) framework of related technologies having a non-real-time (NRT) RIC (RAN Intelligent Controller) architecture in a functional view. Figure 3 is a diagram of the SMO framework of the related technology having NRT RIC in the service view. Figure 4 is a diagram of an O-RAN architecture according to an embodiment. FIG. 5 is a sequence diagram of a method for modifying the P-state of one or more O-Cloud node processors according to an embodiment. FIG. 6 is a flowchart of a method for power management in O-RAN according to an embodiment. FIG. 7 is a diagram of an exemplary environment in which the systems and / or methods described in this specification may be implemented. FIG. 8 is a drawing of exemplary components of a device according to an embodiment. Specific details for implementing the invention

[0032] Refer to the accompanying drawings for the following detailed description of exemplary embodiments. The foregoing disclosure is intended to be illustrative and descriptive, but is not intended to be exhaustive or to limit implementations to the exact form disclosed. Modifications and variations may be possible in light of the foregoing disclosure or may be obtained from the practice of implementations. Additionally, 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). Furthermore, it will be understood that in the flowcharts and descriptions of operations provided below, one or more operations may be omitted, one or more operations may be added, one or more operations may be performed simultaneously (at least partially), and the order of one or more operations may be switched.

[0033] It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual special control hardware or software code used to implement these systems and / or methods does not limit the implementations. Accordingly, the operation and behavior of the systems and / or methods have been 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 in this specification.

[0034] Specific combinations of features are described in the claims and / or disclosed in the specification, but such combinations are not intended to limit the disclosure of possible implementations. In practice, many of these features may be combined in ways not specifically described in the claims and / or disclosed in the specification. Each dependent claim listed below may depend directly on only one claim, but the disclosure of possible implementations includes each dependent claim combined with all other claims within the set of claims.

[0035] Any element, act, or indication used in this specification shall not be interpreted as important or essential unless explicitly stated otherwise. Additionally, as used in this specification, articles (“a” and “an”) are intended to include one or more items and may be used interchangeably with “one or more.” If only one item is intended, the term “one” or similar language is used. Also, as used in this specification, terms “has,” “have,” “having,” “include,” “including,” or similar are intended to be open-ended terms. Additionally, the phrase “based on” is intended to mean “at least partially based on” unless explicitly stated otherwise. Furthermore, expressions such as “at least one of [A] and [B]” or “at least one of [A] or [B]” should be understood to include only A, only B, or both A and B.

[0036] Exemplary embodiments provide a system (as well as methods, devices, networks, etc.) for power management in an O-RAN (open radio access network). In particular, the system can monitor the O-RAN by acquiring parameters representing traffic levels of O-Cloud (O-RAN Cloud) nodes. Parameters representing traffic levels may include the central processing unit (CPU) usage of the O-Cloud node, the current CPU operating frequency of the O-Cloud node processor, the memory usage of the O-Cloud node, the disk throughput of the O-Cloud node, etc. The system can acquire parameters from an O-Cloud server. Parameters can be collected and analyzed from O2 telemetry by an NRT RIC.

[0037] Based on the acquired parameters, the system may determine whether at least one of the collected parameters of the O-Cloud node satisfies a predetermined modification condition. The predetermined modification condition may include conditions based on the O-Cloud node's CPU usage being below a CPU usage percentage threshold, the O-Cloud node's memory usage being below a memory usage percentage threshold, the O-Cloud node's disk throughput being below a disk throughput usage percentage threshold, and / or a combination of these conditions. Based on the determination that at least one of the collected parameters satisfies the predetermined modification condition, the system may change the P-state (CPU operating frequency) of the processor within the O-Cloud node. For the purposes of this disclosure, the P-state and "CPU operating frequency" may be used interchangeably.

[0038] The system may include a federated O-Cloud orchestration and management (FOCOM) controller of the service management and orchestration (SMO) framework, and the system may determine that at least one parameter satisfies a modification condition based on a predefined modification policy configured for the FOCOM controller. Alternatively or additionally, the system may include a non-real-time RAN intelligent controller (NRT) for the SMO, and the NRT RIC may be configured to perform the aforementioned operations.

[0039] Based on the determination that at least one parameter satisfies a predetermined modification condition, and before changing the P-state of the O-Cloud node processor, the system may notify the O-Cloud node that it has been determined that the O-Cloud node will undergo a processor P-state change. In such cases, the P-state of the O-Cloud node processor may be changed after a predetermined grace period that begins when the O-Cloud node is notified. Alternatively, the system may perform a non-graceful modification of the P-state of the O-Cloud node processor so as not to provide any notification that it has been determined that the P-state of the O-Cloud node processor will be modified. Furthermore, the system may terminate at least one application running on the O-Cloud node before the O-Cloud node is deactivated.

[0040] Accordingly, by monitoring the O-RAN as disclosed in this specification, power consumption can be reduced by changing the P-state O-Cloud node processors with or without limited use.

[0041] FIG. 1 is a diagram of an O-RAN architecture (100) according to an embodiment. The O-RAN architecture (100) may include an SMO framework (102) including an NRT RIC (104) and a FOCOM controller (106). The O-RAN architecture (100) may include an nRT (near-real-time) RIC (108), an O-CU-CP (O-RAN Centralized Unit (O-CU) control plane) (110), an O-CU-UP (O-CU user plane) (112), an O-DU (O-RAN Distributed Unit) (114), an O-RU (O-RAN Radio Unit) (116), and an O-Cloud (O-RAN Cloud) server (118). The O-Cloud server (118) may include an IMS (infrastructure management service) module (120) and a DMS (deployment management services) module (122). As illustrated in FIG. 1, the FOCOM controller (106) can be configured to obtain parameters representing the traffic performance of O-Cloud nodes from the O-Cloud server (118). That is, the NRT RIC (104) can push a predefined shutdown policy to the FOCOM controller (106).

[0042] FIG. 4 is a diagram of an O-RAN architecture (400) according to an embodiment. The O-RAN architecture (400) is similar to the O-RAN architecture (100) except that the NRT RIC (404) is configured to push P-state modification actions. Furthermore, the O-RAN architecture (400) includes a fronthaul (FH) M-plane (450) including an O-CU (410) and an O-DU (414), as well as an O-RU (416) associated with the FH M-plane (450). In such embodiments, the NRT RIC (404) can obtain parameters representing the processor utilization of O-Cloud nodes directly from the O-Cloud server (418) and can be configured to determine modifications to the O-Cloud node processor P-states based on the parameters. The NRT RIC (404) can be configured to determine the modification of O-Cloud node processor P-states without implementing a policy such as the policy implemented by the FOCOM controller (406). The NRT RIC (404) can be configured to push P-state modification actions to the IMS module (420).

[0043] FIG. 5 illustrates a sequence diagram of a method for modifying the P-state of one or more O-Cloud node processors according to an embodiment. The core components of the O-RAN architecture of FIG. 5 are similar to those according to FIG. 1.

[0044] Referring to FIG. 5, a method for implementing a modification of the P-state of one or more O-Cloud node processors can be triggered by an event such as telemetry indicating that one or more O-Cloud node processors are being utilized at a level below a predetermined threshold or are being input from non-RAN sources (e.g., O1 interface and / or O2 interface data).

[0045] In FIG. 5, a method for implementing the modification of the P-state of one or more O-Cloud node processors may be initiated by a manual request to SMO by a user or by one or more rApps of NRT-RIC within SMO.

[0046] Referring to FIG. 5, the initiation is exemplified as an O-Cloud node analysis process and marks the start of an O-Cloud node reconfiguration procedure. The initiation according to the O-Cloud node analysis process is based on monitoring O-Cloud data received through an O2 interface by a user or NRT-RIC, analyzing the O-Cloud data, and determining at least one O-Cloud node processor to be reconfigured within the O-Cloud infrastructure based on the analysis.

[0047] To this end, when the NRT-RIC within the SMO initiates the method, one or more rApps within the NRT-RIC perform the O-Cloud node analysis process as previously presented.

[0048] In an exemplary embodiment, the analysis may be based on a comparison between O2 interface telemetry data (e.g., O-Cloud data such as processor load, memory usage, etc.) regarding the utilization of at least one O-Cloud node. Based on the analysis, NRT-RIC (e.g., one or more rApps of NRT-RIC) decides to reconfigure at least one O-Cloud node among a plurality of O-Cloud nodes (i.e., NRT-RIC initiates an O-Cloud reconfiguration procedure for at least one O-Cloud node).

[0049] According to the O-Cloud reconfiguration procedure, in operation (501), in one exemplary embodiment, NRT-RIC (e.g., one or more rApps of NRT-RIC) collects and analyzes O2 telemetry (e.g., O-Cloud data such as processor load, memory usage, etc.), identifies one or more O-Cloud nodes among a plurality of O-Cloud nodes that meet specific predefined criteria for processor P-state modification, and further identifies appropriate P-state modifications to be implemented for each identified C-Cloud node. In another exemplary embodiment, operation (501) is performed by a cloud maintainer (e.g., a user).

[0050] In operation (502), in one exemplary embodiment, SMO (i.e., FOCOM) obtains a request from a cloud maintainer (e.g., user) to apply a desired P-state to the processors associated with the O-Cloud nodes identified in operation (501). In operation (502), in another exemplary embodiment, FOCOM obtains a request from NRT-RIC to reconfigure at least one O-Cloud node based on the results of the O-Cloud analysis process as previously presented.

[0051] In operation (503), FOCOM transmits a reconfiguration request to IMS via the O2 interface upon a decision or clarification as previously presented. For each of the O-Cloud nodes to be reconfigured, the reconfiguration request includes the identity of each O-Cloud node to be reconfigured and the processor P-state to be applied to each such O-Cloud node. Operation (503) may be repeated for each O-Cloud node identified in operation (501).

[0052] In operation (504), when a FOCOM reconfiguration request is received via the O2 interface, IMS changes the processor P-state for each O-Cloud node to be reconfigured to a desired P-state. Changing the O-Cloud node processor P-state is usually enabled by the O-Cloud node BIOS / UEFI. However, other available methods for modifying the P-state may be utilized.

[0053] In operation (505), IMS notifies SMO that the O-Cloud node P-state modification is complete for each respective O-Cloud node. In an exemplary embodiment, IMS transmits the reconfiguration confirmation to FOCOM via the O2 interface.

[0054] Additionally, referring to operation (505), in an exemplary embodiment, if NRT-RIC subscribes to IMS notifications, IMS notifies NRT-RIC via the O2 interface regarding the status of the O-Cloud node (i.e., the status of the reconfigured O-Cloud node(s). In operation (506), SMO notifies the cloud maintainer and NRT-RIC that the O-Cloud node P-state modifications have been completed. In another exemplary embodiment, IMS may notify FOCOM and NRT-RIC via the O2 interface regarding the completion of the reconfiguration.

[0055] Referring to FIG. 5, the method for implementing the modification of the processor P-state of one or more O-Cloud nodes terminates when the P-state of all O-Cloud nodes identified in operation (501) is completed.

[0056] FIG. 6 is a flowchart of a method for power management in an O-RAN according to an embodiment. In operation (601), via an NRT RIC, a cloud maintainer (e.g., user) or rApp identifies a set of O-Cloud nodes to be placed in a low-power mode based on an analysis of O2 telemetry, such as CPU utilization, memory utilization, etc. In operation (602), via an NRT RIC, the cloud maintainer or rApp triggers a SOM (e.g., FOCOM) to place the processors of the O-Cloud nodes identified in operation (601) into a desired P-state. In operation (603), FOCOM requests that IMS change the P-state of the processors within the O-Cloud nodes identified in operation (601) using O2 IMS services. Operation (603) may be repeated for each identified O-Cloud node. In an alternative embodiment, FOCOM requests are sent to IMS in batches. In operation (604), IMS changes the P-state of the processors within the identified O-Cloud nodes to a desired P-state. In operation (605), IMS notifies SMO that the O-Cloud node P-state changes requested in operation (603) are complete. In operation (606), SMO notifies the Cloud Maintenance Manager and / or NRT RIC that the O-Cloud node P-state changes triggered in operation (602) are complete.

[0057] FIG. 7 is a diagram of an exemplary environment (700) in which the systems and / or methods described herein may be implemented. As illustrated in FIG. 7, the environment (700) may include a user device (710), a platform (720), and a network (730). The devices of the environment (700) may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections. In the embodiments, any of the functions and operations described above with reference to FIG. 7 may be performed by any combination of the elements illustrated in FIG. 7.

[0058] The user device (710) includes one or more devices capable of receiving, generating, storing, processing, and / or providing information associated with the platform (720). For example, the user device (710) may include a computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a handheld computer, a smart speaker, a server, etc.), a mobile phone (e.g., a smartphone, a cordless phone, etc.), a wearable device (e.g., a pair of smart glasses or a smart watch), or a similar device. In some implementations, the user device (710) may receive information from the platform (720) and / or transmit information to the platform (720).

[0059] The platform (720) includes one or more devices capable of receiving, generating, storing, processing, and / or providing information. In some implementations, the platform (720) may include a cloud server or a group of cloud servers. In some implementations, the platform (720) may be designed to be modular so that specific software components can be swapped in or swapped out depending on specific needs. As such, the platform (720) can be easily and / or quickly reconfigured for different uses.

[0060] In some implementations, as illustrated, the platform (720) may be hosted in a cloud computing environment (722). It is worth noting that while the implementations described herein describe the platform (720) as being hosted in a cloud computing environment (722), in some implementations, the platform (720) may not be cloud-based (i.e., may be implemented outside of a cloud computing environment) or may be partially cloud-based.

[0061] A cloud computing environment (722) includes an environment that hosts a platform (720). The cloud computing environment (722) may provide computing, software, data access, storage, and other services that do not require knowledge of the physical location and configuration of the system(s) and / or device(s) hosting the platform (720) by the end user (e.g., user device (710)). As illustrated, the cloud computing environment (722) may include a group of computing resources (724) [collectively referred to as "computing resources (724)" and individually referred to as "computing resources (724)"].

[0062] Computing resources (724) include one or more personal computers, a cluster of computing devices, workstation computers, server devices, or other types of computing and / or communication devices. In some implementations, computing resources (724) may host a platform (720). Cloud resources may include computing instances running on computing resources (724), storage devices provided to computing resources (724), data transmission devices provided by computing resources (724), etc. In some implementations, computing resources (724) may communicate with other computing resources (724) via wired connections, wireless connections, or a combination of wired and wireless connections.

[0063] As further illustrated in FIG. 7, computing resources (724) include one or more applications (“APPs”) (724-1), one or more virtual machines (“VMs”) (724-2), virtualized storage (“VSs”) (724-3), one or more hypervisors (“HYPs”) (724-4), or a group of cloud resources such as similar ones.

[0064] The application (724-1) includes one or more software applications that can be provided to or accessed by the user device (710). The application (724-1) may eliminate the need to install and run software applications on the user device (710). For example, the application (724-1) may include any other software that can be provided through software associated with the platform (720) and / or a cloud computing environment (722). In some implementations, one application (724-1) may send / receive information to / from one or more other applications (724-1) through a virtual machine (724-2).

[0065] A virtual machine (724-2) comprises a software implementation of a machine (e.g., a computer) that runs programs similar to those of a physical machine. The virtual machine (724-2) may be a system virtual machine or a process virtual machine, depending on the extent of use and correspondence with any actual machine by the virtual machine (724-2). A system virtual machine may provide a complete system platform that supports the execution of a complete operating system (OS). A process virtual machine may execute a single program and support a single process. In some implementations, the virtual machine (724-2) may run on behalf of a user (e.g., a user device (710)) and may manage the infrastructure of a cloud computing environment (722), such as data management, synchronization, or long-duration data transfers.

[0066] A virtualized storage (724-3) comprises one or more storage systems and / or one or more devices that use virtualization techniques within the storage systems or devices of the computing resources (724). In some implementations, within the context of the storage system, the types of virtualization may include block virtualization and file virtualization. Block virtualization may refer to the abstraction (or separation) of logical storage from physical storage, so that the storage system can be accessed regardless of whether it is physical storage or a heterogeneous structure. This separation may allow the administrator flexibility in how the administrator manages the storage for end users. File virtualization may eliminate dependencies between data accessed at the file level and the location where the files are physically stored. This may enable optimization of storage usage, server consolidation, and / or non-destructive file migration.

[0067] The hypervisor (724-4) can provide hardware virtualization techniques that allow multiple operating systems (e.g., "guest operating systems") to run simultaneously on a host computer such as computing resources (724). The hypervisor (724-4) can present a virtual operating platform to the guest operating system and manage the execution of the guest operating system. Multiple instances of various operating systems can share virtualized hardware resources.

[0068] The network (730) includes one or more wired and / or wireless networks. For example, the network (730) may include a cellular network (e.g., a 5G (fifth generation) network, an LTE (long-term evolution) network, a 3G (third generation) network, a CDMA (code division multiple access) network, etc.), a PLMN (public land mobile network), a LAN (local area network), a WAN (wide area network), a MAN (metropolitan area network), a telephone network (e.g., a PSTN (Public Switched Telephone Network)), a private network, an ad-hoc network, an intranet, the Internet, a fiber-optic-based network, or a similar one, and / or a combination of these or other types of networks.

[0069] The number and arrangement of devices and networks illustrated in FIG. 7 are provided as examples. In practice, there may be additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or differently arranged devices and / or networks compared to those illustrated in FIG. 7. Furthermore, two or more devices illustrated in FIG. 7 may be implemented within a single device, or a single device illustrated in FIG. 7 may be implemented as multiple distributed devices. Additionally, or alternatively, a set of devices in environment (700) (e.g., one or more devices) may perform one or more functions described as being performed by another set of devices in environment (700).

[0070] FIG. 8 is a drawing of exemplary components of a device (800). The device (800) may correspond to a user device (710) and / or a platform (720). As illustrated in FIG. 8, the device (800) may include a bus (810), a processor (820), a memory (830), a storage component (840), an input component (850), an output component (860), and a communication interface (870).

[0071] The bus (810) includes a component that allows communication between the components of the device (800). The processor (820) may be implemented in hardware, firmware, or a combination of hardware and software. The processor (820) may be a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or another type of processing component. In some implementations, the processor (820) includes one or more processors that can be programmed to perform functions. In some implementations, the processor (820) is a single processor having multiple cores. The memory (830) includes random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, and / or optical memory) that stores information and / or instructions for use by the processor (820).

[0072] The storage component (840) stores information and / or software related to the operation and use of the device (800). For example, the storage component (840) may include, together with a corresponding drive, a hard disk (e.g., magnetic disk, optical disk, magneto-optical disk, and / or solid-state disk), a CD (compact disc), a DVD (digital versatile disc), a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transient computer-readable medium. The input component (850) includes a component that allows the device (800) to receive information, for example, through user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone). In addition to or as an alternative, the input component (850) may include a sensor that detects information [e.g., a GPS (global positioning system) component, an accelerometer, a gyroscope, and / or an actuator]. The output component (860) includes a component that provides output information from a device (800) (e.g., a display, a speaker, and / or one or more light-emitting diodes (LEDs)).

[0073] A communication interface (870) includes a transceiver-type component (e.g., a transceiver and / or individual receiver and transmitter) that enables the device (800) to communicate with other devices, for example, through a wired connection, a wireless connection, or a combination of wired and wireless connections. The communication interface (870) may allow the device (800) to receive information from another device and / or provide information to another device. For example, the communication interface (870) may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, an RF (radio frequency) interface, a USB (universal serial bus) interface, a Wi-Fi interface, a cellular network interface, or something similar.

[0074] The device (800) may perform one or more processes described herein. The device (800) may perform these processes in response to the processor (820) executing software instructions stored by a non-transient computer-readable medium, such as memory (830) and / or storage component (840). A computer-readable medium is defined herein as a non-transient memory device. A memory device includes a memory space within a single physical storage device or a memory space distributed across multiple physical storage devices.

[0075] Software instructions may be read into memory (830) and / or storage component (840) from another computer-readable medium or from another device via a communication interface (870). When executed, the software instructions stored in memory (830) and / or storage component (840) may cause the processor (820) to perform one or more processes described herein.

[0076] Additionally or alternatively, hardwired circuits may be used instead of or in combination with software instructions to perform one or more processes described herein. Accordingly, the implementations described herein are not limited to any specific combination of hardware circuits and software.

[0077] The number and arrangement of components shown in FIG. 8 are provided as examples. In practice, the device (800) may include additional components, fewer components, different components, or differently arranged components compared to those shown in FIG. 8. Additionally or alternatively, a set of components of the device (800) (e.g., one or more components) may perform one or more functions described as being performed by another set of components of the device (800).

[0078] In the embodiments, any one of the operations or processes of FIGS. 5 and 6 may be implemented by or using any one of the elements illustrated in FIGS. 1 through 4 and FIGS. 7 and 8. It is understood that other embodiments may be implemented in various different architectures (e.g., bare metal architecture, any cloud-based architecture, or deployment architectures such as Kubernetes, Docker, OpenStack, etc.) and are not limited thereto.

[0079] According to exemplary embodiments, one or more O-Cloud nodes are identified as candidates for modification to low-power operation based on specific operational factors such as CPU usage, memory usage, etc. Once identified, the O-Cloud control system takes steps to change the P-state of one or more processors (or one or more cores of a single processor) within each identified O-Cloud node, thereby reducing the power consumption of the identified O-Cloud nodes.

[0080] The foregoing disclosure is for illustrative purposes only and is not intended to be exhaustive or to limit implementations to the exact form disclosed. Modifications and variations may be possible in light of the foregoing disclosure or may be obtained from the practice of the implementations.

[0081] Some embodiments may relate to systems, methods, and / or computer-readable media at any possible level of technical detail integration. Additionally, one or more of the components described above may be stored on a computer-readable medium and implemented as instructions executable by at least one processor (and / or may include at least one processor). The computer-readable medium may include a computer-readable non-transient storage medium (or media) having computer-readable program instructions to cause a processor to perform operations.

[0082] A computer-readable storage medium may be a tangible device capable of holding and storing instructions for use by an instruction execution device. A computer-readable storage medium may be, for example, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof, but is not limited thereto. A non-exclusive list of more specific examples of computer-readable storage media includes the following: portable computer diskettes, hard disks, RAM (random access memory), ROM (read-only memory), EPROM or flash memory (erasable programmable read-only memory), SRAM (static random access memory), portable CD-ROM (compact disc read-only memory), DVD (digital versatile disk), memory sticks, floppy disks, mechanically encoded devices such as punch cards or raised structures in which instructions are recorded, and any suitable combination of the foregoing. As used herein, a computer-readable storage medium should not be interpreted as being the transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., optical pulses passing through fiber optic cables), or electrical signals transmitted through wires.

[0083] The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to each computing / processing device or to an external computer or external storage device via a network, e.g., the Internet, a local area network, a wide area network, and / or a wireless network. The network may include copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions to be stored in a computer-readable storage medium within each computing / processing device.

[0084] Computer-readable program code / instructions for performing operations may be source code or object code written in any combination of one or more programming languages, including assembler instructions, ISA (instruction-set-architecture) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuits, or object-oriented programming languages ​​such as Smalltalk, C++ or similar, and procedural programming languages ​​such as the "C" programming language or similar programming languages. Computer-readable program instructions may be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer via any type of network, including a LAN (local area network) or a WAN (wide area network), or the connection may be made to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, for example, an electronic device circuit including a programmable logic circuit, a field-programmable gate array (FPGA), or a programmable logic array (PLA) can perform modes or operations by executing computer-readable program instructions by utilizing state information of computer-readable program instructions to personalize the electronic device circuit.

[0085] These computer-readable program instructions are provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing unit, so as to enable the machine to produce means for implementing functions / operations specified in blocks or blocks of a flowchart and / or block diagram, such instructions executed through the processor of the computer or other programmable data processing unit. These computer-readable program instructions may also be stored in a computer-readable storage medium capable of instructing the computer, programmable data processing unit, and / or other devices to function in a specific manner, so that the computer-readable storage medium in which the instructions are stored comprises a manufactured article containing instructions that implement aspects of functions / acts specified in blocks or blocks of a flowchart and / or block diagram.

[0086] Computer-readable program instructions can also be loaded onto a computer, another programmable data processing device, or other device to cause a series of operational steps to be performed on the computer, another programmable device, or other device, thereby producing a computer-implemented process, so that instructions executed on the computer, another programmable device, or other device implement functions / acts specified in blocks or blocks of a flowchart and / or block diagram.

[0087] The flowcharts and block diagrams in the drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer-readable media according to various embodiments. In this regard, each block within the flowcharts or block diagrams may represent a microservice(s), module, segment, or portion of instructions comprising one or more executable instructions for implementing a specified logical function(s). Methods, computer systems, and computer-readable media may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to those depicted in the drawings. In some alternative implementations, the functions mentioned in the blocks may occur out of the order mentioned in the drawings. For example, two blocks depicted consecutively may, in effect, be executed simultaneously or substantially simultaneously, or sometimes in reverse order, depending on the accompanying functionality. It should also be noted that each block of the block diagrams and / or flowcharts, and combinations of blocks within the block diagrams and / or flowcharts, may be implemented by special-purpose hardware-based systems that perform specific functions or acts or perform combinations of special-purpose hardware and computer instructions.

[0088] It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual special control hardware or software code used to implement these systems and / or methods does not limit the implementations. Accordingly, it should be understood that the operation and behavior of the systems and / or methods have been described herein without reference to specific software code, and that software and hardware may be designed to implement the systems and / or methods based on the description herein.

Claims

Claim 1 A method for managing power consumption of one or more O-Cloud nodes within an O-Cloud (open cloud) infrastructure of a telecommunications network, wherein the method is performed by at least one processor and comprises: a step of obtaining a request to modify the P-state of a processor of an O-Cloud node within the O-Cloud infrastructure of the telecommunications network by a FOCOM (federated O-Cloud orchestration and management module) within a SMO (service management orchestration) framework; a step of transmitting the request to modify the P-state of a processor of the O-Cloud node to an IMS (infrastructure management service module) via an O2 interface by the FOCOM; a step of receiving the request to modify the P-state of a processor of the O-Cloud node via the O2 interface by the IMS; a step of controlling the implementation of the request to modify the P-state of a processor of the O-Cloud node by the IMS; and a step of transmitting confirmation of the modification of the P-state of a processor of the O-Cloud node to the FOCOM via the O2 interface by the IMS. Claim 2 A method according to claim 1, further comprising: monitoring O-Cloud data received through the O2 interface by an NRT RIC (non-real-time radio intelligent controller); analyzing the O-Cloud data and, based on the analysis, identifying an O-Cloud node to be modified within the O-Cloud infrastructure; and transmitting a request to modify the O-Cloud node P-state to the FOCOM. Claim 3 A method according to claim 1, further comprising: a step of monitoring O-Cloud data received by a user through the O2 interface; a step of analyzing the O-Cloud data and, based on the analysis, identifying an O-Cloud node to be changed within the O-Cloud infrastructure; and a step of transmitting an O-Cloud node P-state modification request to the FOCOM. Claim 4 A method according to claim 1, further comprising the step of transmitting confirmation of a P-state modification of the processor of the O-Cloud node to at least one of a user and an NRT RIC (non-real-time radio intelligent controller) by means of the FOCOM. Claim 5 In paragraph 2, the O-Cloud data received through the O2 interface includes at least one of processor utilization and memory utilization. Claim 6 A method according to paragraph 2, further comprising the step of transmitting, by means of the FOCOM, to at least one of the user and the NRT RIC, confirmation of the modification of the P-state of the processor of the O-Cloud node. Claim 7 In claim 6, the O-Cloud data received through the O2 interface includes at least one of processor utilization and memory utilization. Claim 8 A system for managing the power consumption of one or more O-Cloud nodes within an O-Cloud (open cloud) infrastructure of a telecommunications network, comprising: at least one memory configured to store computer program code; and at least one processor configured to access said at least one memory and operate as directed by said computer program code, wherein the computer program code comprises: O-Cloud infrastructure implementation code configured to cause said at least one processor to implement (i) a federated O-Cloud orchestration and management module (FOCOM) within a service management orchestration (SMO) framework, (ii) an infrastructure management service module (IMS), and (iii) an O2 interface between said SMO and said IMS; acquisition code configured to cause said at least one processor to obtain, by said FOCOM, a request to modify the P-state of a processor of an O-Cloud node within the O-Cloud infrastructure of the telecommunications network; and transmission code configured to cause said at least one processor to transmit a request to modify the P-state of a processor of said O-Cloud node from said FOCOM to said IMS through said O2 interface. A system comprising: a control code configured to cause at least one processor to implement a request by the IMS to modify the P-state of the processor of the O-Cloud node; and a transmission code configured to cause at least one processor to transmit confirmation of the modification of the P-state of the processor of the O-Cloud node from the IMS to the FOCOM through the O2 interface. Claim 9 In claim 8, the O-Cloud infrastructure implementation code further comprises code configured to cause at least one processor to implement a non-real-time radio intelligent controller (NRT RIC), and the computer program code further comprises: monitoring code configured to cause at least one processor to receive O-Cloud data through the O2 interface by the NRT RIC; analysis code configured to cause at least one processor to analyze the O-Cloud data by the NRT RIC and identify an O-Cloud node to be modified within the O-Cloud infrastructure based on the analysis; and transmission code configured to cause at least one processor to transmit an O-Cloud node P-state modification request to the FOCOM by the NRT RIC. Claim 10 A system according to claim 8 further comprising a human-machine interface configured to allow a user to receive and analyze O-Cloud data through the O2 interface and to further allow the user to transmit an O-Cloud node P-state modification request to the FOCOM. Claim 11 A system according to claim 8, wherein the O-Cloud infrastructure implementation code further comprises code configured to cause at least one processor to implement a non-real-time radio intelligent controller (NRT RIC), and the computer program code further comprises transmission code configured to cause at least one processor to transmit confirmation of a P-state modification of the processor of the O-Cloud node to at least one of the user and the NRT RIC by the FOCOM. Claim 12 In claim 9, the O-Cloud data received through the O2 interface comprises at least one of processor utilization and memory utilization. Claim 13 A system according to claim 10, wherein the O-Cloud infrastructure implementation code further comprises code configured to cause at least one processor to implement a non-real-time radio intelligent controller (NRT RIC), and the computer program code further comprises transmission code configured to cause at least one processor to transmit confirmation of a P-state modification of the processor of the O-Cloud node to at least one of the user and the NRT RIC by the FOCOM. Claim 14 A non-transient computer-readable medium storing instructions that, when executed by a processor, cause said processor to execute a method for managing the power consumption of one or more O-Cloud nodes within an O-Cloud (open cloud) infrastructure of a telecommunications network, wherein the method comprises: obtaining a request to modify the P-state of a processor of an O-Cloud node within the O-Cloud infrastructure of said telecommunications network by a federated O-Cloud orchestration and management module (FOCOM) within a service management orchestration (SMO) framework; transmitting the request to modify the P-state of a processor of said O-Cloud node to an infrastructure management service module (IMS) via an O2 interface by said FOCOM; receiving the request to modify the P-state of a processor of said O-Cloud node via the O2 interface by said IMS; and controlling the implementation of the request to modify the P-state of a processor of said O-Cloud node by said IMS. A non-transient computer-readable medium comprising the step of transmitting, by the IMS, to the FOCOM via the O2 interface, confirmation of a P-state modification of the processor of the O-Cloud node. Claim 15 In claim 14, the method further comprises: a step of monitoring O-Cloud data received through the O2 interface by a non-real-time radio intelligent controller (NRT RIC); a step of analyzing the O-Cloud data and, based on the analysis, identifying the O-Cloud node to be modified within the O-Cloud infrastructure; and a step of transmitting the O-Cloud node P-state modification request to the FOCOM. Claim 16 In claim 14, the method further comprises: a step of monitoring O-Cloud data received by a user through the O2 interface; a step of analyzing the O-Cloud data and, based on the analysis, identifying an O-Cloud node to be changed within the O-Cloud infrastructure; and a non-transient computer-readable medium that transmits a request to modify the O-Cloud node P-state to the FOCOM. Claim 17 In paragraph 14, the method further comprises the step of transmitting, by the FOCOM, to at least one of a user and an NRT RIC (non-real-time radio intelligent controller) confirmation of a P-state modification of the processor of the O-Cloud node, a non-transient computer-readable medium. Claim 18 In paragraph 15, the O-Cloud data received through the above O2 interface is a non-transient computer-readable medium comprising at least one of processor utilization and memory utilization. Claim 19 In claim 16, the O-Cloud data received through the above O2 interface is a non-transient computer-readable medium comprising at least one of processor utilization and memory utilization.

Citation Information

Patent Citations

  • Resource management method for network slicing, resource management system, and work load scheduling device

    JP2022077481A

  • Resource allocation and activation / deactivation configuration of open radio access network (o-ran) network slice subnets

    US20210258866A1

  • System and Method for Managing P-States and C-States of a System

    US20140033207A1