System and method for providing cloud resource optimization policies in a telecommunications system

Abstract

To provide a system, a method and a recording medium for implementing an open cloud (O-Cloud) optimization policy by an application hosted in a quasi-real time radio access network intelligent controller (nRT-RIC) of a telecommunication network.SOLUTION: The system includes a memory storing instructions, and at least one processor implementing the nRT-RIC in an open radio access network (O-RAN) architecture, wherein the processor executes the instructions to receive O-Cloud optimization policies from a non-real-time radio access network intelligent controller (nRT-RIC) in a service management and orchestration (SMO) framework of the telecommunications network, and control to implement the O-Cloud optimization policies in an O-Cloud computing environment in the O-RAN.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority from Singapore Provisional Patent Application No. 10202250828F, filed with the Singapore Patent Office on August 25, 2022, the disclosure of which is incorporated herein by reference in its entirety.

[0002] Systems and methods consistent with example embodiments of the present disclosure relate to providing an open radio access network (O-RAN) architecture for near real-time (nRT-RIC) open cloud (O-Cloud) resource optimization. Specifically, the systems and methods relate to implementing O-Cloud optimization policies of a non-real-time (NRT-RIC) radio access network (RAN) intelligent controller by an application hosted in a near real-time (nRT-RIC) radio access network intelligent controller of the telecommunications network within a Service Management and Orchestration (SMO) framework of the telecommunications network. [Background technology]

[0003] The Radio Access Network (RAN) is a critical component in telecommunications systems because it connects end-user devices (or user equipment) to the rest of the network. The 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 particular RAN is vendor-specific.

[0004] Open RAN (O-RAN) technology has emerged to enable multiple vendors to provide hardware and / or software for telecommunication systems. To this end, O-RAN divides RAN functions into a centralized unit (CU), a distributed unit (DU), and a radio unit (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 the antenna into digital signals that can be transmitted to the DU via the fronthaul. These entities have open protocols and interfaces between them so that they can be developed by different vendors.

[0005] Figure 1 illustrates a prior art O-RAN architecture. 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 to facilitate the multi-vendor operability required in O-RAN systems and to automate and optimize RAN operations. RICs are divided into two types: non-real-time RICs (NRT-RICs) and near-real-time RICs (nRT-RICs).

[0006] The NRT-RIC is the control point for non-real-time control loops, operating on sub-second timescales within a Service Management and Orchestration (SMO) framework. Its functionality is implemented through modular applications called rApps. The functions include providing policy (i.e., a set of rules used to manage and control the change and / or maintenance of the state of one or more managed objects) based on guidance and enrichment over the A1 interface, which is an interface that enables communication between the NRT-RIC and the nRT-RIC (i.e., A1 policy, which is a type of declarative policy expressed using formal descriptions that enable the NRT-RIC in the SMO to guide the nRT-RIC, and therefore the RAN, towards better fulfillment of RAN intent, according to the prior art); performing data analysis, Artificial Intelligence / Machine Learning (AI / ML) training and inference for RAN optimization; and / or recommending configuration management actions over the O1 interface to manage operations and maintenance (OAM), which is an interface that connects the SMO to RAN managed elements (e.g., nRT-RIC, O-RAN Centralized Unit (O-CU), O-RAN Distributed Unit (O-DU), etc.).

[0007] The nRT-RIC is located at the edge of the RAN and operates on a timescale of 10 milliseconds to 1 second. The nRT-RIC connects to the O-DU, O-CU (divided into the O-CU Control Plane (O-CU-CP) and O-CU User Plane (O-CU-UP)), and Open evolved NodeB (O-eNB) via the E2 interface. The nRT-RIC uses the E2 interface to control the underlying RAN elements (E2 nodes / Network Functions (NFs)) via near-real-time control loops. The nRT-RIC monitors, pauses / stops, overrides, and controls the E2 nodes (O-CU-CP, O-CU-UP, O-DU, and O-eNB) via policies. The O-DU connects to the O-RU via fronthaul, including the Control User Synchronization (CUS) and Management (M) planes. For example, the nRT sets policy parameters for activated features of the E2 node. Additionally, the nRT-RIC hosts xApps to implement features such as Quality of Service (QoS) optimization, mobility optimization, slice optimization, interference mitigation, load balancing, and security. The two types of RICs work together to optimize O-RAN. For example, the NRT-RIC provides policies, data, and AI / ML models that are enforced and used by the nRT-RIC for RAN optimization via the A1 interface, and the nRT returns policy feedback (i.e., how the policies set by the NRT-RIC are working).

[0008] The SMO framework manages and orchestrates RAN elements. Specifically, the 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 an OAM as part of the SMO that manages and orchestrates what is called the O-Ran Cloud (O-Cloud). The O-Cloud is a collection of physical RAN nodes that host the RIC, O-CU, and O-DU, supporting software components (e.g., operating systems and runtime environments), and the SMO itself. In other words, the SMO manages the O-Cloud from within. The O2 interface is the interface between the SMO and the O-Cloud in which it resides. Through the O2 interface, SMO provides Infrastructure Management Services (IMS) and Deployment Management Services (DMS).

[0009] According to the prior art as illustrated in Figure 1, the NRT-RIC creates a RAN optimization policy (i.e., an A1 policy for RAN optimization to satisfy the RAN intent). The NRT-RIC then passes the policy (i.e., the A1 policy) to the nRT-RIC over the A1 interface. Upon receiving the A1 policy, the nRT-RIC controls to implement the policy and enforces it in the control loop according to the policy guidance.

[0010] Furthermore, according to the prior art, there is no near-real-time interface for connecting the nRT-RIC to the O-Cloud (i.e., the interface between the nRT-RIC and O2 management services such as the IMS and / or DMS). As a result, prior art A1 policy management is limited to RAN optimization and does not provide O-Cloud optimization policies for the nRT-RIC. This lack of a near-real-time interface prevents the nRT-RIC from controlling O-Cloud resources in near real-time as described above, which can lead to high latency responses and disproportionate utilization of O-Cloud computational and hardware resources. Summary of the Invention

[0011] According to embodiments, systems and methods are provided for implementing an Open Cloud (O-Cloud) optimization policy in a Non-Real-Time Radio access network Intelligent Controller (NRT-RIC) within a Service Management and Orchestration (SMO) framework of a telecommunications network by an application hosted in a near real-time radio access network Intelligent Controller (nRT-RIC) of the telecommunications network, where the nRT-RIC receives the O-Cloud optimization policy from the NRT-RIC and controls implementation of the O-Cloud optimization policy in an O-Cloud computing environment within the O-RAN via a direct interface between the nRT-RIC and the O-Cloud computing environment. In particular, the systems and methods provide an O-RAN architecture for O-Cloud resource optimization via the nRT-RIC by including an interface between the nRT-RIC and the O-Cloud that enables a defined response time of 10 ms to 1 s and reduces O-Cloud resource control latency. Low latency O-Cloud resource control results in faster implementation of O-Cloud optimization policies, which has the advantage of being able to achieve energy-efficient network operation of the O-Cloud computing environment.

[0012] According to an embodiment, a system for implementing an Open Cloud (O-Cloud) optimization policy by an application hosted in a Near Real-Time Radio Access Network Intelligent Controller (nRT-RIC) of a telecommunications network includes a memory storing instructions and at least one processor configured to implement the nRT-RIC within an Open Radio Access Network (O-RAN) architecture, the at least one processor configured to execute the instructions to receive an O-Cloud optimization policy from a Non-Real-Time Radio Access Network Intelligent Controller (NRT-RIC) within a Service Management and Orchestration (SMO) framework of the telecommunications network and control implementation of the O-Cloud optimization policy in an O-Cloud computing environment within the O-RAN.

[0013] The at least one processor may be further configured to execute instructions to receive an O-Cloud optimization policy from an NRT-RIC within the SMO framework via an A1 interface.

[0014] The at least one processor may be further configured to execute instructions to control implementation of the O-Cloud optimization policy in an O-Cloud computing environment within the O-RAN via an O2 interface.

[0015] The at least one processor may be further configured to execute instructions to receive data comprising at least one of performance data and event data from at least one physical host in the O-Cloud computing environment in the O-RAN via the O2 interface.

[0016] The at least one processor may be further configured to execute instructions to send and receive data for at least one O2 managed service in the O-Cloud computing environment via the O2 interface.

[0017] The at least one processor may be further configured to execute instructions to control implementation of the O-Cloud optimization policy via at least one O2 management service in the O-Cloud computing environment via an O2 interface.

[0018] The performance data of the at least one physical host may include processor load, memory usage, and hard disk drive usage of the at least one physical host.

[0019] According to an embodiment, a method for implementing an Open Cloud (O-Cloud) optimization policy by an application hosted in a Near Real-Time Radio Access Network Intelligent Controller (nRT-RIC) of a telecommunications network includes receiving, by the nRT-RIC, an O-Cloud optimization policy from a Non-Real-Time Radio Access Network Intelligent Controller (NRT-RIC) within a Service Management and Orchestration (SMO) framework of the telecommunications network, and controlling, by the nRT-RIC, implementation of the O-Cloud optimization policy in an O-Cloud computing environment within the O-RAN.

[0020] The method may include receiving, by the nRT-RIC, an O-Cloud optimization policy from the NRT-RIC within the SMO framework via an A1 interface.

[0021] The method may include controlling, by the nRT-RIC, to implement an O-Cloud optimization policy in an O-Cloud computing environment within the O-RAN via an O2 interface.

[0022] The method may include receiving, by the nRT-RIC, data including at least one of performance data and event data from at least one physical host in an O-Cloud computing environment in the O-RAN via an O2 interface.

[0023] The method may include transmitting and receiving, by the nRT-RIC, data for at least one O2 managed service in the O-Cloud computing environment via an O2 interface.

[0024] The method may include controlling, by the nRT-RIC, to implement the O-Cloud optimization policy via at least one O2 management service in the O-Cloud computing environment via an O2 interface.

[0025] The performance data of the at least one physical host may include processor load, memory usage, and hard disk drive usage of the at least one physical host.

[0026] According to an embodiment, a non-transitory computer-readable storage medium has stored thereon instructions executable by at least one processor configured to perform a method for implementing a near real-time radio access network intelligent controller (nRT-RIC) within an open radio access network (O-RAN) architecture to implement an open cloud (O-Cloud) optimization policy by an application hosted on the nRT-RIC, the method including receiving, by the nRT-RIC, an O-Cloud optimization policy from a non-real-time radio access network intelligent controller (NRT-RIC) within a service management and orchestration (SMO) framework of a telecommunications network, and controlling, by the nRT-RIC, implementation of the O-Cloud optimization policy in an O-Cloud computing environment within the O-RAN.

[0027] The method may include receiving, by the nRT-RIC, an O-Cloud optimization policy from the NRT-RIC within the SMO framework via an A1 interface.

[0028] The method may include controlling, by the nRT-RIC, to implement an O-Cloud optimization policy in an O-Cloud computing environment within the O-RAN via an O2 interface.

[0029] The method may include receiving, by the nRT-RIC, data including at least one of performance data and event data from at least one physical host in an O-Cloud computing environment in the O-RAN via an O2 interface.

[0030] The method may include transmitting and receiving, by the nRT-RIC, data for at least one O2 managed service in the O-Cloud computing environment via an O2 interface.

[0031] The method may include controlling, by the nRT-RIC, to implement the O-Cloud optimization policy via at least one O2 management service in the O-Cloud computing environment via an O2 interface.

[0032] Additional aspects will be set forth in part in the description that follows, and in part will be apparent from the description, or may be realized by practice of illustrated embodiments of the present disclosure. [Brief explanation of the drawings]

[0033] Features, aspects, and advantages of certain exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which like reference numerals refer to like elements.

[0034] [Figure 1] FIG. 1 illustrates an O-RAN architecture according to the prior art. [Figure 2] FIG. 1 illustrates a system for O-Cloud resource optimization via nRT-RIC in an O-RAN architecture, according to one or more embodiments. [Figure 3] FIG. 1 is a flowchart of a method for implementing an open cloud (O-Cloud) optimization policy using an interface between an nRT-RIC and an O-Cloud, according to an embodiment. [Figure 4] FIG. 1 is a diagram of an example environment in which the systems and / or methods described herein may be implemented. [Figure 5] FIG. 2 is a diagram of exemplary components of a device, according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0035] The following detailed description of the exemplary embodiments refers to the accompanying drawings, in which the same reference numbers in different drawings may identify the same or similar elements.

[0036] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations. Furthermore, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, in the flowcharts and descriptions of operations provided below, it should be understood that one or more operations may be omitted, one or more operations may be added, one or more operations may be performed (at least partially) concurrently, and the order of one or more operations may be rearranged.

[0037] 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 is not limiting of the implementation. Thus, the operation and behavior of the present systems and / or methods are described herein without reference to specific software code. It should be understood that software and hardware may be designed to implement the present systems and / or methods based on the description herein.

[0038] Although particular combinations of features are recited in the claims and / or disclosed herein, these combinations are not intended to limit the disclosure of possible implementations. Indeed, many of these features may be combined in ways not specifically recited in the claims and / or disclosed herein. Although each dependent claim listed below may depend directly on only one claim, the disclosure of possible implementations includes each dependent claim in combination with all other claims in the claim set.

[0039] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles "a" and "an" are intended to include one or more items and may be used synonymously with "one or more." Where only one item is intended, the term "one" or similar phrases are used. Also, as used herein, terms such as "has," "have," "having," "include," and "including" are intended to be open-ended terms. Furthermore, the phrase "based on" is intended to mean "based, at least in part, on," unless specifically stated otherwise. Furthermore, phrases such as "at least one of [A] and [B]" or "at least one of [A] or [B]" should be understood to include A only, B only, or both A and B.

[0040] 2 illustrates a system for O-Cloud resource optimization via nRT-RIC in an O-RAN architecture, according to one or more embodiments. Referring to FIG. 2, the key components of the O-RAN architecture are similar to FIG. 1.

[0041] In FIG. 2, the nRT-RIC connects to E2 nodes (i.e., O-CU-CP, O-CU-UP, O-DU, etc.) via an E3 interface. The nRT-RIC includes multiple applications, so-called xApps, and services required to support the execution of the xApps. An xApp may be one or more microservices that can be used to perform radio resource management through the interface and service model. The prior art xApp receives data from the RAN (e.g., Key Performance Indicators (KPIs) of the E2 node) and, if necessary, calculates and sends back (e.g., to the E2 node) control actions according to A1 policies for RAN optimization received from the nRT-RIC via the A1 interface.

[0042] The nRT-RIC is deployed at the edge of the RAN and operates control loops and analysis functions with a defined periodicity of 10 ms to 1 s. This defined response time periodicity (i.e., defined latency) allows the nRT-RIC to realize RAN analysis and control functions in near real time. Furthermore, the defined latency of the nRT-RIC has an upper limit latency that is equal to or less than the latency of the NRT-RIC in the SMO (i.e., the minimum response time of the NRT-RIC is 1 second, and there is no defined upper latency limit).

[0043] Furthermore, since the nRT-RIC is located at the edge of the O-RAN network, it is also closer to the O-Cloud compute and hardware resources that host E2 node applications (i.e., applications such as O-CU-CP, O-CU-UP, O-DU, etc. that are launched in the O-Cloud).

[0044] Referring to FIG. 2, the nRT-RIC includes one or more xApps that receive data (i.e., performance data and / or event data) from the O-Cloud computing environment and, if necessary, calculate and send back control actions to implement Open Cloud (O-Cloud) optimization policies (e.g., O-Cloud resource optimization policies, O-Cloud infrastructure optimization policies, etc.) in the O-Cloud computing environment.

[0045] To this end, the O2 interface extends to or terminates at the nRT-RIC. In another exemplary embodiment, the O2 interface may branch to the nRT-RIC.

[0046] According to one embodiment, the O2 interface between the nRT-RIC and the O-Cloud computing environment enables low latency data communication between the nRT-RIC and the O-Cloud computing environment (i.e., the O-Cloud computing resources that host the applications of the E2 nodes).

[0047] In an example embodiment, the nRT-RIC (e.g., one or more xApps of the nRT-RIC) may obtain O2 interface data via an Application Programming Interface (API) of the O2 interface. The O2 interface data may include O-Cloud resource data, such as O-Cloud infrastructure data of the O-Cloud environment from O2 management services (i.e., Infrastructure Management Services (IMS) and Deployment Management Services (DMS)).

[0048] For example, the IMS connects with the nRT-RIC, and the O2 interface provides functionality responsible for deploying and managing cloud infrastructure resources (i.e., the IMS orchestrates the O-Cloud infrastructure).

[0049] In another example, the DMS may interface with the nRT-RIC, and the O2 interface provides a set of interface functions responsible for managing virtualized / containerized deployments on the O-Cloud infrastructure (i.e., the DMS orchestrates virtualized / containerized deployments of E2 node applications).

[0050] As a result, one of the two service-based interfaces (SBIs) of the O2 interface (IMS and / or DMS) between the SMO framework and the O-Cloud platform (FOCOM-IMS and NFO-DMS) via the O2 interface in Figure 2 communicates with and / or terminates at the nRT-RIC.

[0051] Still referring to FIG. 2, the NRT-RIC in the SMO provides A1 policies for optimization of the O-Cloud (e.g., O-Cloud resource policies, O-Cloud infrastructure policies, etc.) in addition to A1 policies to guide the nRT-RIC towards better fulfilling the RAN intent (i.e., RAN optimization policies).

[0052] For this purpose, the NRT-RIC according to FIG. 2 provides the A1 policy to guide the nRT-RIC towards optimizing the O-Cloud computing environment in the O-RAN (i.e., O-Cloud optimization policy), and the nRT-RIC, based on receiving the A1 policy, acts on the policy to control the implementation of the O-Cloud resource optimization policy in the O-Cloud computing environment via the O2 interface with the O2 management service in the O-Cloud (e.g., the nRT-RIC may start acting on the policy and implement a control loop for the implementation of the O-Cloud resource optimization policy for the O-Cloud computing resources).

[0053] In an exemplary embodiment, the interface between the nRT-RIC and the O-Cloud computing environment according to FIG. 2 (i.e., the O2 management service orchestrates either the virtualized / containerized deployment of physical hosts, such as servers or server clusters, or the E2 node applications of the O-RAN) may be a bidirectional interface that allows the nRT-RIC to control the implementation of O-Cloud optimization policies in the O-Cloud computing environment within the O-RAN. The nRT-RIC receives data, including at least one of performance data and event data, from at least one physical host in the O-Cloud computing environment within the O-RAN via the O2 interface. In an exemplary embodiment, the performance data and event data of the at least one physical host in the O-Cloud computing environment may include O-Cloud infrastructure data, such as processor load, memory usage, hard disk drive usage, etc., of the at least one physical host.

[0054] Furthermore, the interface between the nRT-RIC and the O-Cloud computing environment according to Figure 2 allows the SMO framework (e.g., NRT-RIC) to more efficiently apply the O-Cloud optimization policy (i.e., A1 policy received from the NRT-RIC).

[0055] The technical advantage of the O2 interface according to Figure 2 as described above over the O2 interface according to the prior art is that it enables O-Cloud optimization policy implementation in the nRT-RIC, thereby achieving a significant reduction in response time latency (i.e., periodicity of the control loop) by interfacing the nRT-RIC with the O-Cloud computing environment (i.e., management services orchestrating O-Cloud resources).

[0056] In particular, the O2 interface according to the O-RAN architecture of Figure 2 allows the nRT-RIC to access the O2 interface data (i.e., non-RAN data) and take action (or implement) on the A1 policy (i.e., O-Cloud resource optimization policy) received from the nRT-RIC.

[0057] The defined response latency of the nRT-RIC has the technical effect that changes (i.e., optimizations) in the O-Cloud can be achieved between 10 ms and 1 s, where 1 s is the maximum period of the nRT-RIC control loop for implementing the A1 policy (i.e., the O-Cloud resource optimization policy) in the O-Cloud computing environment in near real time.

[0058] As a result, the interface between nRT-RIC and O-Cloud with the O-RAN architecture for O-Cloud resource optimization via nRT-RIC (i.e., management services orchestrate O-Cloud resources) enables a significant reduction in O-Cloud resource control latency. Low-latency O-Cloud resource control results in faster implementation of O-Cloud optimization policies, which has the advantage of achieving energy-efficient network operation of the O-Cloud computing environment.

[0059] FIG. 3 is a diagram of a flowchart of a method for implementing O-Cloud optimization policies using an interface between an nRT-RIC and an O-Cloud, according to an embodiment.

[0060] 3, in operation 301, the NRT-RIC creates an O-Cloud optimization policy (i.e., an A1 policy for optimizing the O-Cloud). To this end, the NRT-RIC in the SMO framework controls the O-Cloud strategy through AI / ML learning from network data (e.g., performance data and event data from at least one physical host in the O-Cloud computing environment received via the O2 interface, performance data and / or event data from the O-RAN function via the O1 interface, etc.).

[0061] In operation 302, the nRT-RIC receives an O-Cloud optimization policy from the NRT-RIC. For example, the nRT-RIC receives the O-Cloud optimization policy in the form of an A1 policy.

[0062] In operation 303, upon receiving the policy for O-Cloud optimization, the nRT-RIC begins acting based on the policy. In an example embodiment of FIG. 3, the nRT-RIC may control implementation of the O-Cloud optimization policy to the O-Cloud computing environment in the O-RAN. For example, one or more xApps in the nRT-RIC may connect to an O2 management service (i.e., IMS and / or DMS) that orchestrates the O-Cloud computing environment, and the xApps via the O2 interface API may receive data from the O2 management service (i.e., performance data and / or event data, such as non-RAN data) and, if necessary, calculate and send back control actions to implement the O-Cloud optimization policy in the O-Cloud computing environment.

[0063] In operation 304, the O-Cloud computing environment in the O-RAN (i.e., the O2 management service (IMS and / or DMS) that orchestrates the O-Cloud computing environment) implements the O-Cloud optimization policy. For example, the O2 management service may implement auto-scaling of O-Cloud instances (i.e., auto-scaling of virtualized / containerized deployments of E2 node applications) according to the O-Cloud optimization policy, and the IMS orchestrates resource management policies according to the use cases manifested in the O-Cloud optimization policy provided by the NRT-RIC.

[0064] In operation 305, the nRT-RIC receives data including at least one of performance data and event data from at least one physical host in the O-Cloud computing environment in the O-RAN to control implementation of O-Cloud optimization policies as requested (e.g., O2 management services (IMS and / or DMS) may provide non-RAN data to the nRT-RIC).

[0065] For example, operations 303, 304, and 305 of FIG. 3 may be performed via the O2 interface of FIG. 2, and may be performed sequentially, simultaneously, or in a different order, continuously, periodically, etc.

[0066] According to the embodiment of FIG. 3, access to the O2 interface allows the nRT-RIC to control adaptation to various scenarios and objectives; in particular, the fast response time of the nRT-RIC via the O2 interface allows RAN operators (i.e., Mobile Network Operators (MNOs)) to specify different objectives for network function placement according to a wide variety of scenarios, allowing for more flexible configuration of optimization policies within the SMO.

[0067] 4 is a diagram of an example environment 400 in which the systems and / or methods described herein may be implemented. As shown in FIG. 4, environment 400 may include a user device 410, a platform 420, and a network 430. The devices in environment 400 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections. In an embodiment, any of the functions and operations described with reference to FIG. 1 above may be performed by any combination of the elements illustrated in FIG. 4.

[0068] User device 410 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information related to platform 420. For example, user device 410 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 wireless phone, etc.), a wearable device (e.g., smart glasses or a smart watch), or similar device. In some implementations, user device 410 may receive information from and / or transmit information to platform 420.

[0069] Platform 420 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information. In some implementations, platform 420 may include a cloud server or a collection of cloud servers. In some implementations, platform 420 may be designed to be modular, such that certain software components can be swapped in or out depending on particular needs. Thus, platform 420 can be easily and / or quickly reconfigured for different uses.

[0070] In some implementations, as shown, platform 420 may be hosted in a cloud computing environment 422. Notably, although the implementations described herein describe platform 420 as being hosted within cloud computing environment 422, in some implementations platform 420 may not be cloud-based (i.e., may be implemented outside of a cloud computing environment) or may be partially cloud-based.

[0071] Cloud computing environment 422 includes an environment that hosts platform 420. Cloud computing environment 422 may provide services such as computing, software, data access, storage, etc. that do not require end-user (e.g., user device 410) knowledge of the physical location and configuration of the systems and / or devices that host platform 420. As shown, cloud computing environment 422 may include a collection of computational resources 424 (collectively referred to as “computational resources 424” and individually referred to as “computational resource 424”).

[0072] Computational resources 424 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, computational resources 424 may host platform 420. Cloud resources may include compute instances executing within computational resources 424, storage devices provided within computational resources 424, data transfer devices provided by computational resources 424, etc. In some implementations, computational resources 424 may communicate with other computational resources 424 via wired connections, wireless connections, or a combination of wired and wireless connections.

[0073] As further shown in FIG. 4, the computing resources 424 include a group of cloud resources such as one or more applications (“APP”) 424-1, one or more virtual machines (“VM”) 424-2, virtualized storage (“VS”) 424-3, and one or more hypervisors (“HYP”) 424-4.

[0074] Applications 424-1 include one or more software applications that may be provided to or accessed by user device 410. Applications 424-1 may eliminate the need to install and run software applications on user device 410. For example, applications 424-1 may include software associated with platform 420 and / or any other software that may be provided via cloud computing environment 422. In some implementations, one application 424-1 may send information to or receive information from one or more other applications 424-1 via virtual machine 424-2.

[0075] Virtual machine 424-2 includes a software-implemented machine (e.g., a computer) that executes programs like a physical machine. Virtual machine 424-2 can be either a system virtual machine or a process virtual machine, depending on the intended use and the degree to which virtual machine 424-2 resembles any real machine. 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, virtual machine 424-2 may run on behalf of a user (e.g., user device 410) and manage the infrastructure of cloud computing environment 422, such as data management, synchronization, or long-term data transfer.

[0076] Virtualized storage 424-3 includes one or more storage systems and / or one or more devices that use virtualization technology within the storage systems or devices of computing resources 424. In some implementations, types of virtualization in the context of storage systems may include block virtualization and file virtualization. Block virtualization may refer to the abstraction (or separation) of logical storage from physical storage, such that the storage system may be accessed regardless of the physical storage or heterogeneous structure. The separation may allow administrators flexibility in how they manage the storage for end users. File virtualization may eliminate the dependency between data accessed at the file level and where the file is physically stored. This may enable optimization of storage usage, server consolidation, and / or non-disruptive file movement.

[0077] The hypervisor 424-4 may provide hardware virtualization technology that allows multiple operating systems (e.g., "guest operating systems") to run simultaneously on a host computer, such as the computing resource 424. The hypervisor 424-4 may present a virtual operating platform to the guest operating systems and may manage the execution of the guest operating systems. Multiple instances of different operating systems may share virtualized hardware resources.

[0078] Network 430 may include one or more wired and / or wireless networks. For example, network 430 may be a cellular network (e.g., a Fifth Generation (5G) network, a Long-Term Evolution (LTE) network, a Third Generation (3G) network, a Code Division Multiple Access (CDMA) network, etc.), a Public Land Mobile Network (PLMN), a Local Area Network (LAN), a Wide Area Network (WAN), a Metropolitan Area Network (MAN), a telephone network (e.g., a Public Switched Telephone Network (PSTN)), a private network, an ad-hoc network, an intranet, the Internet, an optical fiber-based network, etc., and / or any of these or other types of networks.

[0079] It may include a combination of networks.

[0080] The number and arrangement of devices and networks shown in Figure 4 are provided as an example. In practice, there may be more, fewer, different, or differently arranged devices and / or networks than those shown in Figure 4. Furthermore, two or more devices shown in Figure 4 may be implemented within a single device, or a single device shown in Figure 4 may be implemented as multiple distributed devices. Additionally, or instead, a set of devices in environment 400 (e.g., one or more devices) may perform one or more functions that are described as being performed by another set of devices in environment 400.

[0081] 5 is a diagram of example components of a device 500. The device 500 may correspond to a user device 510 and / or a platform 520. As shown in FIG. 5, the device 500 may include a bus 510, a processor 520, a memory 530, a storage component 540, an input component 550, an output component 560, and a communication interface 570.

[0082] The bus 510 includes components that enable communication between the components of the device 500. The processor 520 may be implemented in hardware, firmware, or a combination of hardware and software. The processor 520 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 520 includes one or more processors that can be programmed to perform functions. Memory 530 may include 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 processor 520.

[0083] The storage component 540 stores information and / or software related to the operation and use of the device 500. For example, the storage component 540 may include a hard disk (e.g., a magnetic disk, optical disk, magneto-optical disk, and / or solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, magnetic tape, and / or another type of non-transitory computer-readable medium, along with a corresponding drive. The input component 550 includes components that enable the device 500 to receive information, such as via user input (e.g., a touchscreen display, a keyboard, a keypad, a mouse, buttons, switches, and / or a microphone). Additionally or alternatively, the input component 550 may include sensors for sensing information (e.g., a Global Positioning System (GPS) component, an accelerometer, a gyroscope, and / or an actuator). Output components 560 include components that provide output information from device 500, such as a display, a speaker, and / or one or more Light-Emitting Diodes (LEDs).

[0084] Communications interface 570 includes transceiver-like components (e.g., a transceiver and / or a separate receiver and transmitter) that allow device 500 to communicate with other devices via wired connections, wireless connections, or a combination of wired and wireless connections, etc. Communications interface 570 may allow device 500 to receive information from and / or provide information to another device. For example, communications interface 570 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a Radio Frequency (RF) interface, a Universal Serial Bus (USB) interface, a Wi-Fi interface, a cellular network interface, etc.

[0085] Device 500 may perform one or more processes described herein. Device 500 may perform these processes in response to processor 520 executing software instructions stored by a non-transitory computer-readable medium, such as memory 530 and / or storage component 540. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.

[0086] The software instructions may be loaded into memory 530 and / or storage component 540 from another computer-readable medium or from another device via communication interface 570. When executed, the software instructions stored in memory 530 and / or storage component 540 may cause processor 520 to perform one or more processes described herein.

[0087] Additionally, or instead, hardwired circuitry may be used in place of or in combination with software instructions to implement one or more processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.

[0088] The number and arrangement of components shown in Figure 5 are provided as an example. In practice, device 500 may include more, fewer, different, or differently arranged components than those shown in Figure 5. Additionally or alternatively, a set of components (e.g., one or more components) of device 500 may include:

[0089] One or more functions described as being performed by another set of components of device 500 may be performed.

[0090] In an embodiment, any one of the operations or processes of Figures 1, 2, and 3 may be implemented by or using any one of the elements illustrated in Figures 4 and 5.

[0091] According to an embodiment, a system and method for implementing an O-Cloud optimization policy are provided, in which an nRT-RIC controls the implementation of the O-Cloud optimization policy in an O-Cloud computing environment in an O-RAN via a direct interface between the nRT-RIC and the O-Cloud computing environment. The direct interface nRT-RIC and O-Cloud reduces latency to near real-time. As a result, low-latency resource control enables energy-efficient network operation of the RAN.

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

[0093] Some embodiments may relate to systems, methods, and / or computer-readable media at any possible level of technical detail. Furthermore, one or more of the components described above may be implemented as instructions stored on a computer-readable medium and executable by at least one processor (and / or may include at least one processor). A computer-readable medium may include one or more computer-readable non-transitory recording media having computer-readable program instructions thereon for causing a processor to perform operations.

[0094] A computer-readable storage medium may be a tangible device that can hold and store instructions for use by an instruction-execution device. The computer-readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of computer-readable storage media includes 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 Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disk (DVD), memory sticks, floppy disks, mechanically encoded devices such as punch cards or ridge structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. Computer-readable storage medium, as used herein, should not be construed as being, per se, a transitory signal such as an electric wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., a light pulse passing through a fiber optic cable), or an electrical signal transmitted through a wire.

[0095] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to an individual computing / processing device or to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network may comprise copper transmission cables, optical transmission fiber, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the individual computing / processing device.

[0096] The computer-readable program code / instructions for performing operations may be either source code or object code written in any combination of one or more programming languages, including assembler instructions, Instruction-Set-Architecture (ISA) 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++, and procedural programming languages ​​such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partially on the user's computer, as a stand-alone 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 may be connected to an external computer (e.g., through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuits, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), may execute computer-readable program instructions by utilizing state information of the computer-readable program instructions to personalize the electronic circuitry to perform aspects or operations.

[0097] These computer-readable program instructions may be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, whereby the instructions executing on the processor of the computer or other programmable data processing apparatus create means for implementing the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams. These computer-readable program instructions may also be stored on a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and / or other device to function in a particular manner, whereby the computer-readable storage medium having instructions stored therein comprises an article of manufacture containing instructions that implement aspects of the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.

[0098] The computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device and cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device to generate a computer-implemented process, whereby the instructions executing on the computer, other programmable apparatus, or other device implement the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.

[0099] The flowcharts and block diagrams in the figures 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 in the flowcharts or block diagrams may represent a module, segment, or portion of instructions, comprising one or more executable instructions for implementing the specified logical function(s). The methods, computer systems, and computer-readable media may include more, fewer, different, or differently arranged blocks than those depicted in the figures. In some alternative implementations, the functions noted in the blocks may occur in a different order than noted in the figures. For example, two blocks shown in succession may actually be executed concurrently or substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending on the functionality involved. It should also be noted that each block of the block diagrams and / or flowchart diagrams, and combinations of blocks in the block diagrams and / or flowchart diagrams, may be implemented by special-purpose hardware-based systems that perform the specified functions or actions or execute a combination of special-purpose hardware and computer instructions.

[0100] 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 is not intended to limit the implementation. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, and it will be understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.

Claims

1. An interface between a near real-time radio access network intelligent controller (nRT-RIC) and an open cloud (O-Cloud); The nRT-RIC is communicatively connected to the O-Cloud via the interface within the O-RAN; The system, wherein O-Cloud related data is received by the nRT-RIC from the O-Cloud via the interface.

2. The system of claim 1 , wherein the O-Cloud related data includes event data received by the nRT-RIC from the O-Cloud.

3. The system of claim 1 , wherein the O-Cloud related data includes O-Cloud infrastructure status data received by the nRT-RIC from the O-Cloud.

4. The system of claim 1 , wherein the O-Cloud related data includes O-Cloud infrastructure resource data received by the nRT-RIC from the O-Cloud.

5. The system of claim 1 , wherein the interface interacts with an O2 interface to provide communication between the O-Cloud and the nRT-RIC via an API.

6. The system of claim 1 , wherein the interface provides bidirectional communication between the nRT-RIC and the O-Cloud.

7. The system of claim 1, wherein the nRT-RIC is configured to control implementation of policies for the O-Cloud via the interface, the policies being at least one of an O-Cloud optimization policy, a Quality of Service (QoS) optimization policy, a mobility optimization policy, a slice optimization policy, an interference mitigation policy, a load balancing policy, and a security policy.

8. The system of claim 1 , wherein the nRT-RIC receives an A1 policy from a non-real-time (NRT) RIC and controls implementation of the A1 policy using RAN functions hosted by the O-Cloud.

9. Communicatively connecting a near real-time radio access network intelligent controller (nRT-RIC) and an open cloud (O-Cloud) via an interface between the nRT-RIC and the open cloud (O-Cloud); receiving O-Cloud related data from the O-Cloud via the interface by the nRT-RIC; A method comprising:

10. The method of claim 9 , wherein the O-Cloud related data includes event data received by the nRT-RIC from the O-Cloud.

11. The method of claim 9 , wherein the O-Cloud related data includes O-Cloud infrastructure status data received by the nRT-RIC from the O-Cloud.

12. The method of claim 9 , wherein the O-Cloud related data includes O-Cloud infrastructure resource data received by the nRT-RIC from the O-Cloud.

13. The method of claim 9, wherein the interface interacts with an O2 interface to provide communication between the O-Cloud and the nRT-RIC via an API.

14. The method of claim 9 , wherein the interface provides bidirectional communication between the nRT-RIC and the O-Cloud.

15. The method of claim 9, wherein the nRT-RIC receives an A1 policy from a non-real-time (NRT) RIC and controls implementation of the A1 policy using RAN functions hosted by the O-Cloud.

16. 1. A non-transitory computer-readable storage medium having stored thereon instructions for performing a method executable by a near real-time radio access network intelligent controller (nRT-RIC) in an open radio access network (O-RAN) architecture, the method comprising: Communicating between the nRT-RIC and an open cloud (O-Cloud) via an interface between the nRT-RIC and the open cloud (O-Cloud); receiving O-Cloud related data from the O-Cloud via the interface by the nRT-RIC; 1. A non-transitory computer-readable recording medium comprising:

17. The non-transitory computer-readable medium of claim 16, wherein the O-Cloud related data includes event data received by the nRT-RIC from the O-Cloud.

18. The non-transitory computer-readable storage medium of claim 16, wherein the O-Cloud related data includes O-Cloud infrastructure status data or O-Cloud infrastructure resource data received by the nRT-RIC from the O-Cloud.

19. 17. The non-transitory computer-readable medium of claim 16, wherein the interface interacts with an O2 interface to provide communication between the O-Cloud and the nRT-RIC via an API.

20. 17. The non-transitory computer-readable medium of claim 16, wherein the interface provides bidirectional communication between the nRT-RIC and the O-Cloud.

Images