System and method for shutting down O-CLOUD nodes during idle times to save energy consumption

By draining and shutting down O-Cloud nodes during idle times based on telemetry data analysis, the method addresses the energy consumption issue of underutilized nodes, improving energy efficiency in O-RAN systems.

KR103046050B1Active Publication Date: 2026-11-10RAKUTEN MOBILE INC
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
KR1020247020905
Authority / Receiving Office
KR · KR
Patent Type
Patents
Current Assignee / Owner
Priority Date
2022-04-22
Filing Date
2022-11-10
Publication Date
2026-11-10
Estimated Expiration
2042-11-10

AI Technical Summary

Technical Problem

Underutilized Open Radio Access Network (O-RAN) Cloud (O-Cloud) nodes consume significant energy during idle periods due to being in normal or maximum power states, despite hosting a small number of network functions.

Method used

Implement a method and system to drain and shut down O-Cloud nodes during idle times by analyzing O2 telemetry data, utilizing Federated O-Cloud Orchestration and Management (FOCOM) to control Infrastructure Management Services (IMS) for node shutdown, optimizing energy consumption.

Benefits of technology

This approach conserves energy by shutting down underutilized O-Cloud nodes during idle times, enhancing the energy efficiency of O-RAN systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure R1020247020905_ABST
    Figure R1020247020905_ABST
Patent Text Reader

Abstract

A method and system for shutting down an Open Radio Access Network (O-RAN) cloud (O-Cloud) node are provided. The method comprises: receiving a first request by FOCOM to drain an O-Cloud node, —the first request is received from a user terminal or a non-real-time (non-RT) RAN intelligent controller (RIC) based on an analysis of O2 telemetry data—; transmitting a second request by FOCOM to drain an O-Cloud node based on the received first request to an IMS via an O2 interface; receiving a third request by FOCOM to shut down the drained O-Cloud node, —the third request is received from a user terminal or a non-RT RIC—; transmitting a fourth request by FOCOM to shut down an O-Cloud node based on the received third request to an IMS; and receiving a notification from the IMS that the O-Cloud node has been shut down.
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 to Singapore provisional application No. 10202204268W filed with the Singapore Intellectual Property Office on April 22, 2022, the entire disclosure of which is incorporated herein by reference.

[0003] field

[0004] Systems and methods according to exemplary embodiments of the present disclosure relate to draining and shutting down an Open Radio Access Network (O-RAN) Cloud (O-Cloud) node during idle times to save energy consumption. Background Technology

[0005] 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 has emerged, enabling multiple vendors to provide hardware and / or software for communication systems. To this end, O-RAN breaks down RAN functions into Centralized Units (CU), Distributed Units (DU), and Radio Units (RU). The CU is a logical node for hosting the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and / or Packet Data Convergence Protocol (PDCP) sublayers of the RAN. The DU is a logical node for hosting the Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) sublayers of the RAN. The 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 possess open protocols and interfaces between them, they can be developed by different vendors.

[0007] Figure 1 illustrates the O-RAN architecture of the relevant technology. Referring to Figure 1, RAN functions in the O-RAN architecture are controlled and optimized by RICs. RICs are software-defined components that implement modular applications, facilitating the multi-vendor operability required in O-RAN systems, as well as automating and optimizing RAN operations. RICs are classified into two types: Non-RT RICs and Near-RT RICs.

[0008] The non-RT RIC is a control point of the non-real-time control loop and operates on a time scale greater than 1 second within the Service Management and Orchestration (SMO) framework. These functions are implemented through modular applications called rApps (rApp 1, ..., rApp N in FIG. 1) and include providing policy-based guidance and reinforcement through an A1 interface, which is an interface enabling communication between the non-RT RIC and the quasi-RT RIC; performing data analysis; artificial intelligence / machine learning (AI / ML) training and inference for RAN optimization; and / or recommending configuration management measures through an O1 interface, which is an interface connecting the SMO to RAN managed elements (e.g., quasi-RT RIC, O-RAN centralized unit (O-CU), O-RAN distributed unit (O-DU), etc.).

[0009] The quasi-RT RIC operates on a time scale of 10 milliseconds to 1 second and connects to the O-DU, O-CU (decomposed into the O-CU Control Plane (O-CU-CP) and O-CU User Plane (O-CU-UP)), and Open Evolved NodeB (O-eNB) via E2 interfaces. The quasi-RT RIC controls underlying RAN elements (E2 nodes / Network Functions (NFs)) through a quasi-real-time control loop using the E2 interfaces. The quasi-RT RIC monitors, suspends / stops, overrides, and controls E2 nodes (O-CU, O-DU, and O-eNB) through policies. For example, the quasi-RT sets policy parameters regarding the active functions of the E2 nodes. Additionally, the quasi-RT 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, a non-RT RIC provides policies, data, and AI / ML models that are executed and used by a quasi-RT RIC for RAN optimization through an A1 interface, and the quasi-RT returns policy feedback (i.e., how the policies set by the non-RT RIC are operating).

[0010] The SMO framework, where non-RT RICs reside, manages and orchestrates RAN elements. Specifically, SMO includes Federated O-Cloud Orchestration and Management (FOCOM), a Network Function Orchestrator (NFO) that manages Virtual Machine (VM)-based Virtual Network Functions (VNFs) and Container (i.e., Instance)-based VNFs, and OAM as part of SMO that manages and orchestrates what is referred to as the O-Ran Cloud (O-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 that host the SMO itself. In other words, SMO manages the O-Cloud internally. The O2 interface is the interface between the SMO and the O-Cloud where the SMO resides. Through the O2 interface, SMO provides Infrastructure Management Services (IMS) and Deployment Management Services (DMS). The O2 interface can also transmit O2 telemetry data to SMO, such as O-Cloud configuration or arbitrary logical function data, energy consumption, node health status, etc.

[0011] E2 nodes (i.e., virtualized / containerized instantiations of network functions) are deployed (i.e., hosted) on O-Cloud infrastructure (i.e., one or more O-Cloud nodes). However, when only a small number of network functions are deployed on O-Cloud or during idle periods, these network functions may be spread across multiple nodes, and several underutilized nodes consume a relatively large amount of energy by being in normal or maximum power states. means of solving the problem

[0012] According to embodiments, systems and methods are provided for draining and shutting down one or more O-Cloud nodes within the O-Cloud infrastructure of a communication network, wherein the draining of one or more O-Cloud nodes is based on determining and analyzing the performance of at least one O-Cloud node or at least one virtual network function hosted thereon. The systems and methods are provided to, upon receiving a request to drain at least one O-Cloud node, to request an IMS to process the drain request within the SMO and to control the implementation of the drain request, wherein the IMS controls the O-Cloud infrastructure to drain at least one O-Cloud node and reports the status of the drained O-Cloud node to the SMO. Subsequently, the drained at least one O-Cloud node can be shut down to conserve energy. Monitoring and analyzing O2 telemetry data of the O-Cloud infrastructure has the advantage that O-Cloud nodes can be drained and shut down during idle time to provide more energy-efficient functionality of the O-RAN.

[0013] According to one embodiment, a method for shutting down an Open Radio Access Network (O-RAN) cloud (O-Cloud) node comprises: receiving a first request to drain an O-Cloud node by Federated O-Cloud Orchestration and Management (FOCOM) — said first request is received from a user terminal or from a non-real-time (non-RT) RAN intelligent controller (RIC) based on the analysis of O2 telemetry data —; transmitting a second request to drain the O-Cloud node by the FOCOM to Infrastructure Management Services (IMS) via an O2 interface based on the received first request; receiving a third request to shut down the drained O-Cloud node by the FOCOM — said third request is received from the user terminal or from the non-RT RIC —; transmitting a fourth request to shut down the O-Cloud node by the FOCOM to shut down the O-Cloud node via the O2 interface based on the received third request; and includes the step of receiving a notification from the IMS that the O-Cloud node has been shut down.

[0014] According to one embodiment, a system for shutting down an Open Radio Access Network (O-RAN) Cloud (O-Cloud) node comprises: at least one first memory storing first instructions; and at least one processor implementing FOCOM, wherein the at least one processor executes the stored first instructions to: receive a first request to drain an O-Cloud node, —the first request being received from a user terminal or from a non-real-time (non-RT) RAN intelligent controller (RIC) based on the analysis of O2 telemetry data—; transmit a second request to drain the O-Cloud node based on the received first request to Infrastructure Management Services (IMS) via an O2 interface; receive a third request to shut down the drained O-Cloud node, —the third request being received from the user terminal or from the non-RT RIC—; transmit a fourth request to shut down the O-Cloud node based on the received third request to the IMS via the O2 interface; It is configured to receive a notification from the above IMS that the above O-Cloud node has been shut down.

[0015] According to one embodiment, at least one non-transient computer-readable recording medium storing instructions executable by at least one processor for performing a method for shutting down an Open Radio Access Network (O-RAN) Cloud (O-Cloud) node, the method comprising: receiving a first request to drain an O-Cloud node by FOCOM (Federated O-Cloud Orchestration and Management), —the first request being received from a user terminal or from a non-real-time (non-RT) RAN Intelligent Controller (RIC) based on an analysis of O2 telemetry data—; transmitting a second request to drain the O-Cloud node by FOCOM based on the received first request to Infrastructure Management Services (IMS) via an O2 interface; and receiving a third request to shut down the drained O-Cloud node by FOCOM, —the third request being received from the user terminal or from the non-RT RIC—; The method includes the step of transmitting a fourth request to shut down the O-Cloud node based on the received third request by the FOCOM through the O2 interface to the IMS; and the step of receiving a notification from the IMS that the O-Cloud node has been shut down.

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

[0017] Features, aspects, and advantages of certain exemplary embodiments of the present disclosure will be described below with reference to the attached drawings, where identical reference numbers represent identical elements, and where: FIG. 1 shows an O-RAN architecture according to the prior art; FIG. 2 is a flowchart of a method for draining and shutting down an O-Cloud node using an O2 interface between FOCOM and O-Cloud according to one embodiment; FIG. 3 is a diagram of an exemplary environment in which the systems described herein according to one embodiment can be implemented for draining and shutting down an O-Cloud node; FIG. 4 is a diagram of an exemplary environment in which the systems described herein according to one embodiment can be implemented for the drain procedure of an O-Cloud node. FIG. 5 is a diagram of an exemplary environment in which the systems and / or methods described herein may be implemented; FIG. 6 is a drawing of exemplary components of a device according to one embodiment. Specific details for implementing the invention

[0018] The following detailed description of exemplary embodiments refers to the attached drawings. Identical reference numbers in different drawings may identify identical or similar elements.

[0019] The foregoing disclosures are for illustrative purposes only and are not intended to enumerate in their entirety or to limit implementations to the form disclosed. Modifications and changes may be made or acquired from the practice of implementations in light of the foregoing disclosures. 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 should 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.

[0020] 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 specialized 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 should be understood that software and hardware may be designed to implement the systems and / or methods based on the description in this specification.

[0021] Even if specific combinations of features are described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of possible implementations. In fact, several 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 in combination with all other claims within the set of claims.

[0022] The elements, actions, or guidelines used herein shall not be interpreted as important or essential unless explicitly stated otherwise. Additionally, the articles “a” and “an” used herein 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. Furthermore, terms used herein such as “have,” “have,” “having,” “include,” “include,” etc. are intended to be open-ended terms. Also, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Additionally, 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.

[0023] Embodiments of the present disclosure provide a method and system for draining and shutting down O-Cloud nodes during idle times to save energy consumption. In particular, when there are only a few network functions deployed in the O-Cloud, the network function deployment is optimized to a limited number of O-Cloud nodes on the O-Cloud, and the remaining O-Cloud nodes can be shut down and redeployed to save energy consumption during O-Cloud node idle times.

[0024] FIG. 2 is a flowchart of a method for draining and shutting down an O-Cloud node using an O2 interface between FOCOM and O-Cloud according to one embodiment. The method of FIG. 2 (at least operations 202 to 206) is performed by FOCOM.

[0025] Referring to FIG. 2, the drain and shutdown of the O-Cloud node(s) may be initiated by a user via a user terminal (e.g., one that includes an application for managing network functions and / or is subscribed to receive alarm events, notifications, etc. from the SMO) or by one or more rApps of a non-RT RIC within the SMO in 201. The components of the O-RAN architecture in FIG. 2, FIG. 3, and FIG. 4 are similar to those according to FIG. 1.

[0026] As shown in FIGS. 2, 3, and 4, prior to the initiation of drain and shutdown of the O-Cloud node(s), the availability of SMO and O-Cloud is assumed. Additionally, the non-RT RIC or the aforementioned user terminal is configured to subscribe to receive notifications from SMO and receive O2-IMS alarm event notifications. Accordingly, the non-RT RIC and / or user terminal (e.g., an application installed on the user terminal) can receive and analyze O2 telemetry data to determine the O-Cloud nodes for hardware drain and hardware shutdown.

[0027] According to one embodiment, the decision to drain and subsequently shut down an O-Cloud node may be based on O2 data (or O2 telemetry data) received through an O2 interface, such as O-Cloud configuration information (e.g., a single node or cluster, the number of microservices or network functions running on each node, etc.), energy consumption (e.g., CPU load, power consumption, etc.), and hardware usage (e.g., memory usage). According to another embodiment, the decision to drain and subsequently shut down an O-Cloud node may be based on both O1 data (or O1 telemetry data) and O2 data received through an O1 interface, such as traffic data (or traffic pattern data), physical resource block (PRB) usage, and the number of users. For example, the decision may be based on a prediction of the number of microservices or network functions required over a subsequent predetermined period (e.g., the next time period), and a policy may be generated accordingly. In operation 201, a user (via an application running on a user terminal), an application within a user terminal, or an rApp within a non-RT RIC decides to and requests to drain one or more O-Cloud nodes based on received O2 and / or O1 data (e.g., based on analysis thereof). The request (or service request) is transmitted to FOCOM from the user terminal or non-RT RIC and includes the identifier of each O-Cloud node to be drained.

[0028] In operation 202, FOCOM receives a request (first request) to drain one or more O-Cloud nodes, and in operation 203, FOCOM requests IMS to drain one or more O-Cloud nodes based on the received first request (second request). Here, FOCOM may request IMS to drain one or more O-Cloud nodes through an O2 interface, for example, by using O2ims services. Operation 203 may be looped or performed repeatedly for each of the one or more O-Cloud nodes identified in the first request. Additionally, FOCOM may determine an order for draining one or more O-Cloud nodes according to predetermined criteria or randomly, and may transmit second requests corresponding to each of the one or more O-Cloud nodes according to this determined order. Then, FOCOM may receive a status update notification from IMS indicating the status of the drain request(s), for example, that the drain is completed. Here, user terminals (i.e., applications installed therein) and / or non-RT RICs (i.e., rApps) can also receive status update notifications.

[0029] In operation 204, FOCOM receives a request (third request) to shut down one or more O-Cloud nodes drained from a user terminal or a non-RT RIC (i.e., rApp), and in operation 205, FOCOM requests IMS to shut down one or more O-Cloud nodes based on the received third request (fourth request). The third request may include identifiers of one or more O-Cloud nodes to be shut down. Operation 205 may be looped or performed repeatedly for each of the one or more O-Cloud nodes to be shut down. Additionally, FOCOM may determine an order for shutting down one or more O-Cloud nodes according to a predetermined criterion or randomly, and may transmit fourth requests corresponding to each of the one or more O-Cloud nodes according to this determined order.

[0030] In operation 206, FOCOM receives a notification from IMS that one or more O-Cloud nodes have been shut down. Here, user terminals (i.e., applications installed inside) and / or non-RT RICs (i.e., rApps) may also receive the notification.

[0031] FIG. 3 illustrates a detailed method for implementing a drain procedure of O-Cloud node(s) according to one embodiment. The method of FIG. 3 is performed by FOCOM and IMS as well as by a user terminal (i.e., an application installed inside) and / or a non-RT RIC (rApp).

[0032] Referring to FIG. 3, a method for implementing a drain procedure (300) of an O-Cloud node may be triggered by or based on an input from an O2 interface (e.g., O2 telemetry data). According to another embodiment, this method may consider both O2 telemetry data received through the O2 interface and O1 telemetry data received through the O1 interface.

[0033] A user, the aforementioned application installed on the user terminal, or a non-RT RIC (rApp) analyzes received O2 telemetry data and / or O1 telemetry data and determines whether to drain and shut down the O-Cloud node based thereon. For example, telemetry data indicating an idle state or a low number of instantiated network functions may be determined as a basis for draining and shutting down the O-Cloud node(s). In one embodiment, this analysis may include a comparison between at least one key performance indicator (KPI) related to the performance of at least the O-Cloud node and its corresponding threshold. Based on the comparison, the user terminal or the non-RT RIC (e.g., one or more rApps of the non-RT RIC) determines whether to drain and shut down the O-Cloud node(s).

[0034] In operation 301, the user terminal or non-RT RIC transmits a first request to FOCOM to drain the O-Cloud node(s) determined to be shut down, as described above. The first request may include identifiers of the O-Cloud node(s).

[0035] In operation 302, FOCOM receives a first request from a non-RT RIC or user terminal to drain the O-Cloud node(s).

[0036] In operation 303, through the O2 interface, FOCOM sends a second request to IMS to drain the O-Cloud node(s) based on the received first request.

[0037] In operation 304, IMS drains each specified node. To do this, IMS can determine whether any network functions (NFs) placed on the specific O-Cloud node to be drained and shut down need to be relocated to another node, or if they can simply be terminated without relocation. If the NFs are still needed, IMS controls the relocation of the NFs to another O-Cloud node that will not be shut down, and notifies FOCOM, non-RT RICs, and / or user terminals (applications) of the relocation.

[0038] In operation 305, in one exemplary embodiment, IMS transmits a notification of confirmation of the completed drain procedure to FOCOM via the O2 interface. IMS may also (or alternatively), transmit a notification to a non-RT RIC (rApp) and / or user terminal (application), for example, based on whether it is subscribed to notifications from IMS.

[0039] FIG. 4 illustrates a detailed method for implementing a shutdown procedure (400) of O-Cloud node(s) according to one embodiment. The method of FIG. 4 is performed by FOCOM and IMS as well as by a user terminal (i.e., an application installed inside) and / or a non-RT RIC (rApp).

[0040] Referring to FIG. 4, in operation 401, a user terminal (application) or a non-RT RIC (rApp) requests FOCOM to shut down the O-Cloud node(s) (third request).

[0041] In operation 402, FOCOM receives a third request to shut down the O-Cloud node(s). This request may be sent via the O2 interface.

[0042] In operation 403, FOCOM sends a fourth request to IMS to shut down the specified O-Cloud node(s).

[0043] In operation 404, IMS shuts down the specified O-Cloud node(s) based on the fourth request. Here, the O-Cloud nodes were previously drained according to the method of FIG. 3.

[0044] In operation 405, IMS transmits a notification of confirmation of the completed shutdown procedure to FOCOM via the O2 interface. IMS may also (or alternatively), transmit a notification to a non-RT RIC (rApp) and / or user terminal (application), for example, based on whether it is subscribed to notifications from IMS.

[0045] FIG. 5 is a diagram of an exemplary environment (500) in which the systems and / or methods described herein may be implemented. As illustrated in FIG. 5, the environment (500) may include a user device (510), a platform (520), and a network (530). The devices of the environment (500) 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 with reference to FIG. 2 through 4 above may be performed by any combination of the elements shown in FIG. 5.

[0046] The user device (510) includes one or more devices capable of receiving, generating, storing, processing, and / or providing information associated with the platform (520). For example, the user device (610) 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 (610) may receive information from the platform (520) and / or transmit information to the platform (520).

[0047] The platform (520) includes one or more devices capable of receiving, generating, storing, processing, and / or providing information. In some implementations, the platform (520) may include a cloud server or a group of cloud servers. In some implementations, the platform (520) may be designed modularly so that certain software components can be swapped in or swapped out as needed. Thus, the platform (520) can be easily and / or quickly reconfigured for different uses.

[0048] In some implementations, as illustrated, the platform (520) may be hosted in a cloud computing environment (522). In particular, while the implementations described herein describe the platform (520) as being hosted in a cloud computing environment (522), in some implementations, the platform (520) may not be cloud-based (i.e., may be implemented outside a cloud computing environment) or may be partially cloud-based.

[0049] A cloud computing environment (522) includes an environment that hosts a platform (620). The cloud computing environment (522) may provide services such as computing, software, data access, and storage that do not require end-user (e.g., user device (510)) knowledge of the physical location and configuration of the system(s) and / or device(s) hosting the platform (520). As illustrated, the cloud computing environment (522) may include a group of computing resources (524) (collectively referred to as "computing resources (524)" and individually referred to as "computing resources (524)").

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

[0051] As additionally illustrated in FIG. 5, computing resources (524) include a group of cloud resources such as one or more applications ("APP") (524-1), one or more virtual machines ("VM") (524-2), virtualized storage ("VS") (524-3), and one or more hypervisors ("HYP") (524-4).

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

[0053] A virtual machine (524-2) includes a software implementation of a machine (e.g., a computer) that executes programs such as those of a physical machine. Depending on the extent of use by the virtual machine (524-2) and the correspondence to any actual machine, the virtual machine (524-2) may be a system virtual machine or a process virtual machine. A system virtual machine may provide a whole system platform that supports the execution of an entire operating system ("OS"). A process virtual machine may execute a single program and support a single process. In some implementations, the virtual machine (524-2) may run on behalf of a user (e.g., a user device (510)) and may manage the infrastructure of a cloud computing environment (522), such as data management, synchronization, or long-term data transmission.

[0054] Virtualized storage (524-3) includes one or more storage systems and / or one or more devices that utilize virtualization technologies within the storage systems or devices of the computing resources (524). In some implementations, within the context of the storage system, types of virtualizations 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. Separation may allow administrators flexibility in how they manage storage for end users. File virtualization may eliminate dependencies between data accessed at the file level and where the files are physically stored. This may enable optimization of storage utilization, server consolidation, and / or non-disruptive file migration performance.

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

[0056] The network (530) includes one or more wired and / or wireless networks. For example, the network (530) may include cellular networks (e.g., 5th generation (5G) networks, LTE (long-term evolution) networks, 3rd generation (3G) networks, Code Division Multiple Access (CDMA) networks, etc.), public terrestrial mobile networks (PLMN), local area networks (LAN), wide area networks (WAN), metropolitan area networks (MAN), telephone networks (e.g., public switched telephone network (PSTN)), private networks, ad-hoc networks, intranets, the Internet, fiber-optic-based networks, etc., and / or combinations of these or other types of networks.

[0057] The number and arrangement of devices and networks shown in FIG. 5 are provided as an example. In practice, unlike those shown in FIG. 5, there may be additional devices and / or networks, a smaller number of devices and / or networks, different devices and / or networks, or devices and / or networks arranged differently. Additionally, two or more devices shown in FIG. 5 may be implemented within a single device, or a single device shown in FIG. 5 may be implemented as multiple distributed devices. Additionally, or alternatively, a set of devices (e.g., one or more devices) of the environment (500) may perform one or more functions described as being performed by another set of devices of the environment (500).

[0058] FIG. 6 is a drawing of exemplary components of a device (600). The device (600) may correspond to a user device (510) and / or a platform (520). As illustrated in FIG. 6, the device (600) may include a bus (610), a processor (620), a memory (630), a storage component (640), an input component (650), an output component (660), and a communication interface (670).

[0059] The bus (610) includes a component that allows communication between the components of the device (600). The processor (620) may be implemented in hardware, firmware, or a combination of hardware and software. The processor (620) 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 other types of processing components. In some implementations, the processor (320) includes one or more processors that can be programmed to perform functions. The memory (330) 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 to be used by the processor (620).

[0060] The storage component (640) stores information and / or software related to the operation and use of the device (600). For example, the storage component (640) may include 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 media, along with a corresponding drive. The input component (650) includes a component that allows the device (600) to receive information through user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, buttons, switches, and / or a microphone). Additionally or alternatively, the input component (650) may include a sensor for detecting information (e.g., a Global Positioning System (GPS) component, an accelerometer, a gyroscope, and / or an actuator). The output component (660) includes a component that provides output information from a device (600) (e.g., a display, a speaker, and / or one or more light-emitting diodes (LEDs)).

[0061] A communication interface (670) includes a transceiver-like component (e.g., a transceiver and / or a separate receiver and transmitter) that enables the device (600) to communicate with another device via a wired connection, a wireless connection, or a combination of wired and wireless connections. The communication interface (670) may allow the device (600) to receive information from another device and / or provide information to another device. For example, the communication interface (670) 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, etc.

[0062] The device (600) may perform one or more of the processes described herein. The device (600) may perform these processes in response to the processor (620) executing software instructions stored in a non-transient computer-readable medium, such as memory (630) and / or storage component (640). 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.

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

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

[0065] The number and arrangement of components shown in FIG. 6 are provided as an example. In reality, the device (600) may include additional components, a smaller number of components, different components, or differently arranged components, unlike those shown in FIG. 6. Additionally or alternatively, a set of components of the device (600) (e.g., one or more components) may perform one or more functions described as being performed by another set of components of the device (600).

[0066] In the embodiments, any of the operations or processes of FIGS. 2, FIGS. 3, and FIGS. 4 may be implemented by or using any of the elements shown in FIGS. 5 and FIGS. 6. It will be understood that other embodiments are not limited thereto and 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.).

[0067] According to exemplary embodiments, energy savings are achieved by draining and shutting down O-Cloud nodes during idle times. For example, when there are only a few network functions deployed or need to be deployed in the O-Cloud, the deployment of network functions on the O-Cloud is optimized to a limited number of O-Cloud nodes, and the remaining O-Cloud nodes are shut down to save energy consumption during O-Cloud node idle times. O-Cloud resources may also be drained to move network functions to other O-Cloud nodes. The foregoing disclosure is for illustrative and descriptive purposes only, but is not intended to enumerate in its entirety or to limit implementations in the form disclosed. Modifications and changes may be possible or derived from the practice of implementations in light of the foregoing disclosure.

[0068] Some embodiments may relate to systems, methods, and / or computer-readable media at any possible level of technical detail of integration. Additionally, one or more of the aforementioned components may be implemented as instructions stored in a computer-readable medium and 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 medium) having computer-readable program instructions for causing a processor to execute operations.

[0069] 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-limiting list of more specific examples of computer-readable storage media includes the following: portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable CD-ROM (compact disc read-only memory), digital versatile disk (DVD), memory sticks, floppy disks, punch-cards, or mechanically encoded devices such as raised structures within grooves on which instructions are recorded, and any suitable combination thereof. A computer-readable storage medium, when used herein, must not be interpreted as being a transient signal in itself, 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.

[0070] 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 transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface of each computing / processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions to be stored on a computer-readable storage medium within each computing / processing device.

[0071] Computer-readable program code / instructions for executing 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++, etc., 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 through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), 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 circuit comprising a programmable logic circuit, field programmable gate arrays (FPGAs) or programmable logic arrays (PLAs) can execute computer-readable program instructions by using state information of computer-readable program instructions that personalize the electronic circuit to perform modes or operations.

[0072] These computer-readable program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to create a machine that generates means for implementing functions / operations specified in blocks or blocks of a flowchart and / or block diagram, wherein instructions executed using the processor of the computer or other programmable data processing device. These computer-readable program instructions may also be stored in a computer-readable storage medium capable of directing a computer, a programmable data processing device, and / or other devices to function in a specific manner, such that the computer-readable storage medium storing the instructions comprises a manufactured article containing instructions that implement modes of function / operation specified in blocks or blocks of a flowchart and / or block diagram.

[0073] These computer-readable program instructions may also be loaded onto a computer, other programmable data processing device, and / or other device so that instructions executed on a computer, other programmable data processing device, and / or other device implement functions / operations specified in blocks or blocks of a flowchart and / or block diagram, and a series of operation steps may be performed on the computer, other programmable data processing device, or other device to create a computer-implemented process.

[0074] The flowcharts and block diagrams in the drawings illustrate the architecture, functions, and operations of systems, methods, and computer-readable media possible implementations according to various embodiments. In this regard, each block in a flowchart or block diagram may represent a microservice(s), module, segment, or part of instructions containing one or more executable instructions for implementing a specified logical function(s). The method, computer system, and computer-readable media may include additional blocks, a smaller number of blocks, different blocks, or blocks arranged differently from those shown in the drawings. In some alternative implementations, the functions indicated in the blocks may occur in an order different from the order indicated in the drawings. For example, two consecutively depicted blocks may, in fact, be executed simultaneously or substantially simultaneously depending on the functions included, or the blocks may sometimes be executed in reverse order. It will also be noted that each block of the block diagrams and / or flowchart examples, and combinations of blocks of the block diagrams and / or flowchart examples, may be implemented by special-purpose hardware-based systems that perform the specified functions or operations, or execute a combination of special-purpose hardware and computer instructions.

[0075] 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 specialized 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 should be understood that software and hardware may be designed to implement the systems and / or methods based on the description in this specification.

Claims

Claim 1 A method for shutting down an Open Radio Access Network (O-RAN) cloud (O-Cloud) node, comprising: receiving a first request to drain an O-Cloud node by Federated O-Cloud Orchestration and Management (FOCOM) — said first request is received from a user terminal or from a non-real-time (non-RT) RAN intelligent controller (RIC) based on an analysis of O1 data and O2 telemetry data —; transmitting a second request to drain the O-Cloud node by said FOCOM to Infrastructure Management Services (IMS) via an O2 interface based on said received first request; and receiving a third request to shut down the drained O-Cloud node by said FOCOM — said third request is received from said user terminal or from the non-RT RIC —; A method comprising: transmitting a fourth request to shut down the O-Cloud node based on the received third request by the FOCOM through the O2 interface to the IMS; and receiving a notification from the IMS that the O-Cloud node has been shut down. Claim 2 A method according to claim 1, further comprising: receiving the O1 data and the O2 telemetry data; and deciding to shut down the O-Cloud node based on the received O1 data and the received O2 telemetry data. Claim 3 In paragraph 2, the determining step comprises receiving a user input by the user terminal to shut down the O-Cloud based on the received O1 data and the received O2 telemetry data. Claim 4 A method according to claim 2, wherein the determining step comprises: analyzing the received O1 data and the received O2 telemetry data by the non-RT RIC; and determining the O-Cloud node to be shut down based on the received O1 data and the received O2 telemetry data by the non-RT RIC. Claim 5 A method according to claim 1, further comprising: a step of controlling the O-Cloud node to drain based on the second request by the IMS; and a step of controlling the drained O-Cloud node to shut down based on the fourth request by the IMS. Claim 6 A method according to claim 5, further comprising the step of controlling the network function deployed in the O-Cloud node to be redeployed to another O-Cloud node by the IMS. Claim 7 A method according to claim 1, further comprising the step of receiving a notification from the IMS that the O-Cloud node has been drained by at least one of the FOCOM and the non-RT RIC. Claim 8 A system for shutting down an Open Radio Access Network (O-RAN) cloud (O-Cloud) node comprises: at least one first memory storing first instructions; and at least one first processor implementing Federated O-Cloud Orchestration and Management (FOCOM), wherein the at least one first processor executes the stored first instructions to: receive a first request to drain an O-Cloud node—the first request is received from a user terminal or from a non-real-time (non-RT) RAN intelligent controller (RIC) based on an analysis of O1 data and O2 telemetry data—; transmit a second request to drain the O-Cloud node based on the received first request to Infrastructure Management Services (IMS) via an O2 interface; and receive a third request to shut down the drained O-Cloud node—the third request is received from the user terminal or from the non-RT RIC—; A system configured to transmit a fourth request to shut down the O-Cloud node based on the received third request to the IMS via the O2 interface; and to receive a notification from the IMS that the O-Cloud node has been shut down. Claim 9 A system according to claim 8, further comprising: at least one second memory storing second instructions; and at least one second processor implementing the non-RT RIC, wherein the at least one second processor is configured to execute the second instructions to: receive the O1 data and the O2 telemetry data; analyze the received O1 data and the received O2 telemetry data; and determine an O-Cloud node to shut down based on the received O1 data and the received O2 telemetry data. Claim 10 In paragraph 8, the system, wherein the first request is received from the user terminal based on user input to the user terminal for shutting down the O-Cloud node. Claim 11 A system according to claim 8, further comprising: at least one third memory storing third instructions; and at least one third processor implementing the IMS, wherein the at least one third processor is configured to execute the third instructions to: control the O-Cloud node to drain based on the second request; and control the drained O-Cloud node to shut down based on the fourth request. Claim 12 In claim 11, the system is configured such that at least one third processor executes the third instructions to control the redeployment of network functions deployed in the O-Cloud node to another O-Cloud node. Claim 13 In claim 8, the above at least one first processor is configured to execute the above first instructions to receive a notification from the above IMS that the O-Cloud node has been drained, a system. Claim 14 At least one non-transient computer-readable recording medium storing instructions executable by at least one processor for performing a method for shutting down an Open Radio Access Network (O-RAN) cloud (O-Cloud) node, the method comprising: receiving a first request to drain an O-Cloud node by Federated O-Cloud Orchestration and Management (FOCOM) — said first request is received from a user terminal or from a non-real-time (non-RT) RAN intelligent controller (RIC) based on an analysis of O1 data and O2 telemetry data —; transmitting a second request to drain the O-Cloud node by said FOCOM to Infrastructure Management Services (IMS) via an O2 interface based on said received first request; receiving a third request to shut down the drained O-Cloud node by said FOCOM — said third request is received from said user terminal or from the non-RT RIC —; At least one non-transient computer-readable recording medium comprising: the step of transmitting a fourth request to shut down the O-Cloud node based on the received third request by the FOCOM through the O2 interface to the IMS; and the step of receiving a notification from the IMS that the O-Cloud node has been shut down. Claim 15 In claim 14, the method further comprises the step of receiving the O1 data and the O2 telemetry data; and the step of deciding to shut down the O-Cloud node based on the received O1 data and the received O2 telemetry data, at least one non-transient computer-readable recording medium. Claim 16 In claim 15, the determining step comprises receiving a user input by the user terminal to shut down the O-Cloud based on the received O1 data and the received O2 telemetry data, at least one non-transient computer-readable recording medium. Claim 17 In claim 16, the determining step comprises: analyzing the received O1 data and the received O2 telemetry data by the non-RT RIC; and determining the O-Cloud node to be shut down by the non-RT RIC based on the received O1 data and the received O2 telemetry data, at least one non-transient computer-readable recording medium. Claim 18 In claim 15, the method further comprises the step of controlling the O-Cloud node to be drained based on the second request by the IMS; and the step of controlling the drained O-Cloud node to be shut down based on the fourth request by the IMS, at least one non-transient computer-readable recording medium. Claim 19 In paragraph 18, the method further comprises the step of controlling the relocation of network functions deployed in the O-Cloud node to another O-Cloud node by the IMS, at least one non-transient computer-readable recording medium. Claim 20 In claim 19, the method further comprises receiving a notification from the IMS that the O-Cloud node has been drained by at least one of the FOCOM and the non-RT RIC, at least one non-transient computer-readable recording medium.

Citation Information

Patent Citations

  • Cluster node control method, device and equipment and readable storage medium

    CN111147565A

  • Method adn device for o-ran based performance optimization and configuration

    KR1020210117960A

  • Dynamic Selection of Server States

    US20110016339A1

  • Traffic Control Within an IP Multimedia Subsystem

    US20140192773A1

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

    US20210258866A1