System and method for providing cloud resource optimization policies in telecommunication system

Abstract

A system for enforcing 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. The system includes: a memory storing instructions; and at least one processor configured to implement nRT-RIC within an open radio access network (O-RAN) architecture, the at least one processor configured to execute instructions to: receive an O-Cloud optimization policy from a non-real-time radio access network intelligence controller (NRT-RIC) within a service management and orchestration (SMO) framework of a telecommunications network; and controlling an O-Cloud optimization strategy to be implemented in an O-Cloud computing environment in the O-RAN.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based on and claims priority from the 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. Technical Field

[0003] Systems and methods consistent with example embodiments of the present disclosure relate to providing an open radio access network (O-RAN) architecture for open cloud (O-Cloud) resource optimization via near real-time (nRT-RIC). In particular, the systems and methods relate to implementing an open cloud (O-Cloud) optimization strategy of a non-real-time radio access network (RAN) intelligent controller (NRT-RIC) within a service management and orchestration (SMO) framework of a telecommunications network, the open cloud optimization strategy being implemented by an application hosted in a near real-time radio access network intelligent controller (nRT-RIC) of the telecommunications network. Background Art

[0004] The Radio Access Network (RAN) is an important component in a telecommunication system as it connects the end-user devices (or user equipment) to the rest of the network. The RAN comprises a combination of various network elements (NEs) that connect the end-user devices to the core network. Traditionally, the hardware and / or software of a particular RAN is vendor-specific.

[0005] Open RAN (O-RAN) technology has emerged to enable multiple vendors to provide hardware and / or software to telecommunication systems. To this end, O-RAN decomposes RAN functionality 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 that hosts the radio link control (RLC), medium access control (MAC), and physical (PHY) sublayers of the RAN. The RU is a physical node that converts the radio signals from the antenna into digital signals that can be sent to the DU via fronthaul. Because there are open protocols and interfaces between these entities, they can be developed by different vendors.

[0006] Figure 1 The figure shows the O-RAN architecture of the related technology. Figure 1, RAN functions in the O-RAN architecture are controlled and optimized by RIC. RIC is a software-defined component that implements modular applications to facilitate multi-vendor operability required in O-RAN systems, as well as to automate and optimize RAN operations. RIC is divided into two types: non-real-time RIC (NRT-RIC) and near real-time RIC (nRT-RIC).

[0007] NRT-RIC is the 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. Its functionality is implemented through modular applications called rApps. This functionality includes: providing policies (i.e., a set of rules used to manage and control changes and / or maintenance of the state of one or more managed objects) based on guidance and enrichment across the A1 interface, the A1 interface being an interface that enables communication between the NRT-RIC and the nRT-RIC (i.e., according to the relevant technology, the A1 policy is a declarative policy expressed using formal statements that enables the NRT-RIC within the SMO to guide the nRT-RIC, thereby guiding the RAN to better implement the RAN intent); performing data analysis; artificial intelligence / machine learning (AI / ML) training and reasoning for RAN optimization; and / or recommending configuration management actions through the O1 interface to manage operations and maintenance (OAM), which is an interface that connects the SMO to RAN management elements (e.g., nRT-RIC, O-RAN centralized unit (O-CU), O-RAN distributed unit (O-DU), etc.).

[0008] The nRT-RIC is located at the edge of the RAN and operates at a time scale between 10 milliseconds and 1 second. The nRT-RIC is connected to the O-DU, O-CU (decomposed into the O-CU control plane (O-CU-CP) and the O-CU user plane (O-CU-UP)) and the open evolved node B (O-eNB) via the E2 interface. The nRT-RIC uses the E2 interface to control the underlying RAN elements (E2 nodes / network functions (NFs)) in a near real-time control loop. The nRT-RIC monitors, suspends / stops, covers, and controls the E2 nodes (O-CU-CP, O-CU-UP, O-DU, and O-eNB) via policies, where the O-DU is connected to the O-RU via a fronthaul connection including a control user synchronization (CUS) plane and a management (M) plane. For example, nRT sets policy parameters for the activation function of the E2 node. Further, the nRT-RIC hosts xApps to implement functions such as quality of service (QoS) optimization, mobility optimization, slice optimization, interference mitigation, load balancing, security, etc. These two types of RICs work together to optimize O-RAN. For example, NRT-RIC provides policies, data, and AI / ML models through the A1 interface, which are implemented and used by nRT-RIC for RAN optimization, and nRT returns policy feedback (i.e., how the policies set by NRT-RIC are working).

[0009] The SMO framework manages and orchestrates RAN elements. Specifically, SMO includes the Federal O-Cloud Orchestration and Management (FOCOM), the Network Function Orchestrator (NFO) that manages virtual machine (VM)-based virtual network functions (VNFs) and container-based (i.e., instance) VNFs, and OAM, which is part of SMO, manages and orchestrates the so-called O-Ran Cloud (O-Cloud). O-Cloud is a collection of: physical RAN nodes that host RIC, O-CU, and O-DU, supporting software components (e.g., operating systems, and runtime environments), and SMO itself. In other words, SMO manages O-Cloud from the inside. The O2 interface is the interface between SMO and the O-Cloud where it resides. Through the O2 interface, SMO provides infrastructure management services (IMS) and deployment management services (DMS).

[0010] according to Figure 1 In the illustrated related art, NRT-RIC creates a RAN optimization policy (i.e., an A1 policy for RAN optimization to achieve RAN intent). NRT-RIC then passes the policy (i.e., A1 policy) to nRT-RIC via the A1 interface. After receiving the A1 policy, nRT-RIC controls to implement the policy and executes in a control loop according to the policy guidance.

[0011] Moreover, according to the related art, there is no near real-time interface connecting nRT-RIC to O-Cloud (i.e., an interface between nRT-RIC and O2 management services (such as IMS and / or DMS)). Therefore, A1 policy management according to the related art is limited to RAN optimization, and no O-Cloud optimization policy is provided for nRT-RIC. The lack of such a near real-time interface prevents nRT-RIC from controlling O-Cloud resources in near real time as stated above, and may result in high latency responses and unbalanced utilization of O-Cloud computing and hardware resources. Summary of the invention

[0012] According to an embodiment, a system and method for implementing an open cloud (O-Cloud) optimization strategy of a non-real-time radio access network intelligent controller (NRT-RIC) within a service management and orchestration (SMO) framework of a communication network is provided, wherein the open cloud optimization strategy is implemented by an application hosted in a near real-time radio access network intelligent controller (nRT-RIC) of a telecommunications network, wherein the nRT-RIC receives the O-Cloud optimization strategy from the NRT-RIC and controls the implementation of the O-Cloud optimization strategy in the 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 system and method provide an O-RAN architecture for O-Cloud resource optimization by including an interface between the nRT-RIC and the O-Cloud, which is capable of achieving a defined response time between 10ms and 1s and allows for a reduction in O-Cloud resource control latency. Low-latency O-Cloud resource control results in faster implementation of the O-cloud optimization strategy, which has the advantage of enabling energy-saving network operation of the O-cloud computing environment.

[0013] 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 instructions to: receive the 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 the implementation of the O-Cloud optimization policy in an O-Cloud computing environment within the O-RAN.

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

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

[0016] The at least one processor may also be configured to execute instructions to receive data from at least one physical host in an O-cloud computing environment within the O-RAN via an O2 interface, the data comprising at least one of: performance data, and event data.

[0017] The at least one processor may also be configured to execute instructions to send and receive data of at least one O2 management service in the O-cloud computing environment via the O2 interface.

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

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

[0020] 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, the 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, the implementation of the O-Cloud optimization policy in an O-Cloud computing environment within the O-RAN.

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

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

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

[0024] The method may include sending and receiving, by the nRT-RIC, data of at least one O2 management service in an O-cloud computing environment via an O2 interface.

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

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

[0027] According to an embodiment, a non-transitory computer-readable recording medium has instructions stored thereon, which can be executed by at least one processor, and the at least one processor is configured to implement a near real-time radio access network intelligent controller (nRT-RIC) within an open radio access network (O-RAN) architecture to perform a method for implementing an open cloud (O-Cloud) optimization policy by an application hosted in the nRT-RIC, the method comprising: 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, the implementation of the O-Cloud optimization policy in an O-Cloud computing environment within the O-RAN.

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

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

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

[0031] The method may include sending and receiving, by the nRT-RIC, data of at least one O2 management service in an O-cloud computing environment via an O2 interface.

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

[0033] Additional aspects will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be achieved by practice of the presented embodiments of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Features, aspects, and advantages of certain exemplary embodiments of the present disclosure will be described below with reference to the accompanying drawings, in which like reference numerals represent like elements, and in which:

[0035] Figure 1 An O-RAN architecture according to the related art is illustrated;

[0036] Figure 2 illustrates a system for O-Cloud resource optimization via nRT-RIC within an O-RAN architecture according to one or more embodiments;

[0037] Figure 3 is a flow chart of a method for implementing an open cloud (O-Cloud) optimization strategy using an interface between nRT-RIC and O-Cloud according to an embodiment;

[0038] Figure 4 is a diagram of an example environment in which the systems and / or methods described herein may be implemented; and

[0039] Figure 5 is a diagram of example components of a device according to an embodiment. DETAILED DESCRIPTION

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

[0041] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementation mode to the disclosed precise form. In view of the above disclosure, modifications and variations are possible, or modifications and variations can be obtained from the practice of the implementation mode. Further, one or more features or components of an embodiment can be incorporated into another embodiment (or one or more features of another embodiment), or combined with another embodiment (or one or more features of another embodiment). Additionally, in the flow chart and the operation description provided below, it is to be understood that one or more operations can be omitted, one or more operations can be added, one or more operations can be performed (at least in part) simultaneously, and the order of one or more operations can be switched.

[0042] It will be apparent that the systems and / or methods described herein can be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the implementation. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software codes. It is to be understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.

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

[0044] Unless explicitly described as such, the elements, actions or instructions used herein should not be interpreted as critical or essential. Moreover, as used herein, the articles "one" and "an" are intended to include one or more items and can be used interchangeably with "one or more". In the case of only one item, the term "one" or similar language is used. Moreover, as used herein, the terms "having", "having", "having", "having", "including", "comprising", etc. are intended to be open terms. Further, unless otherwise explicitly stated, the phrase "based on" is intended to mean "based at least in part". In addition, 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.

[0045] Figure 2 A system for O-Cloud resource optimization via nRT-RIC within an O-RAN architecture according to one or more embodiments is illustrated. Figure 2 , the key components of O-RAN architecture are similar to Figure 1 .

[0046] exist Figure 2 In the present invention, the nRT-RIC is connected to the E2-node (i.e., O-CU-CP, O-CU-UP, O-DU, etc.) via the E3 interface. The nRT-RIC includes multiple applications (so-called xApps) and the services required to support the execution of the xApps. The xApp can be one or more microservices, which can be used to perform radio resource management through interfaces and service models. The xApp according to the related art receives data from the RAN (e.g., key performance indicators (KPIs) of the E2 node) and, when necessary, calculates and sends back control actions (e.g., to the E2 node) based on the A1 policy for RAN optimization received from the NRT-RIC through the A1 interface.

[0047] The nRT-RIC is deployed at the edge of the RAN and operates the control loop and analysis functions with a defined periodicity between 10ms and 1s. This defined response time periodicity (i.e., defined latency) allows the nRT-RIC to implement the analysis and control functions of the RAN in near real time. Moreover, the defined latency of the nRT-RIC has an upper bound latency that is equal to or less than the latency of the NRT-RIC within the SMO (i.e., in the absence of a defined upper bound latency, the minimum response time of the NRT-RIC is 1 second).

[0048] In addition, since the nRT-RIC is located at the edge of the O-RAN network, it is also closer to the O-Cloud computing and hardware resources that host the applications of the E2 nodes (i.e., applications of O-CU-CP, O-CU-UP, O-DU, etc. running in O-Cloud).

[0049] Reference Figure 2 , 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 control actions back to implement Open Cloud (O-Cloud) optimization policies (e.g., O-Cloud resource optimization policies, O-Cloud infrastructure optimization policies, etc.) into the O-Cloud computing environment.

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

[0051] According to an embodiment, the O2 interface between the nRT-RIC and the O-Cloud computing environment allows low-latency data communication between the nRT-RIC and the O-Cloud computing environment (ie, the O-Cloud computing resources hosting the applications of the E2 nodes).

[0052] In an example embodiment, nRT-RIC (e.g., one or more xApps of 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 an O-Cloud environment from an O2 management service (i.e., an infrastructure management service (IMS) and a deployment management service (DMS)).

[0053] For example, the IMS is connected to the nRT-RIC, where the O2 interface provides the functionality responsible for deploying and managing cloud infrastructure resources (ie, the IMS orchestrates the O-Cloud infrastructure).

[0054] In another example, the DMS may be connected to the nRT-RIC, where the O2 interface provides an interface function set responsible for managing virtualized / containerized deployment on the O-Cloud infrastructure (ie, the DMS orchestrates the virtualized / containerized deployment of E2 node applications).

[0055] Therefore, according to Figure 2 The O2 interface in the O-Cloud platform (FOCOM-IMS and NFO-DMS), either of the two service-based interfaces (SBI) of the O2 interface (IMS and / or DMS) communicates with the nRT-RIC and / or terminates at the nRT-RIC.

[0056] Still refer to Figure 2 ,In addition to guiding nRT-RIC to better implement the A1 policy (i.e., RAN optimization policy) for RAN intentions, NRT-RIC within SMO also provides A1 policies for optimizing O-Cloud (e.g., O-Cloud resource policy, O-cloud infrastructure policy, etc.).

[0057] To this end, according to Figure 2 The NRT-RIC provides an A1 policy to guide the nRT-RIC towards optimization of the O-Cloud computing environment (i.e., the O-Cloud optimization policy) within the O-RAN, and based on receiving the A1 policy, the nRT-RIC 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 using the O2 management service in the O-Cloud (e.g., the nRT-RIC can start acting on the policy and execute a control loop for the implementation of the O-Cloud resource optimization policy on the O-Cloud computing resources).

[0058] In an example embodiment, according to Figure 2 , the interface between the nRT-RIC and the O-Cloud computing environment (i.e., the O2 management services that orchestrate the following items: physical hosts such as servers or server clusters, or virtualized / containerized deployments of E2 node applications of O-RAN) can be a bidirectional interface, allowing 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 from at least one physical host in the O-cloud computing environment within the O-RAN via the O2 interface, the data including at least one of the following: performance data, and event data. In an example embodiment, the performance data and event data of at least one physical host in the O-Cloud computing environment may include O-Cloud infrastructure data, such as processor load, memory usage, hard drive usage, etc. of the at least one physical host.

[0059] Moreover, according to Figure 2 The interface between the nRT-RIC and the O-Cloud computing environment enables the SMO framework (e.g., NRT-RIC) to more effectively apply the O-Cloud optimization policy (i.e., the A1 policy received from NRT-RIC).

[0060] As stated above, compared with the O2 interface according to the related art, Figure 2 The technical advantage of the O2 interface is the ability to enable O-Cloud optimization policy enforcement at the nRT-RIC, thereby achieving a significant reduction in response time latency (i.e., the periodicity of the control loop) by interfacing the nRT-RIC with the O-Cloud computing environment (i.e., with the management service that orchestrates O-Cloud resources).

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

[0062] The defined response latency of nRT-RIC has the following technical effect, namely, changes (i.e., optimization) of O-Cloud can be implemented between 10ms and 1s, where 1s is the maximum periodicity of the nRT-RIC control loop to implement the A1 policy (i.e., O-Cloud resource optimization policy) in near real time in the O-Cloud computing environment.

[0063] Therefore, according to the O-RAN architecture, the interface between nRT-RIC and O-Cloud (i.e., utilizing the management service that orchestrates O-Cloud resources) allows for significant reduction in O-Cloud resource control latency via nRT-RIC. Low-latency O-Cloud resource control leads to faster implementation of O-cloud optimization policies, which has the advantage of enabling energy-efficient network operation of the O-cloud computing environment.

[0064] Figure 3 is a flow chart of a method for implementing an O-Cloud optimization strategy using an interface between nRT-RIC and O-Cloud according to an embodiment.

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

[0066] In operation 302, the nRT-RIC receives the 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.

[0067] In operation 303, after receiving the O-Cloud optimized policy, nRT-RIC starts to act on the policy. Figure 3 In an example embodiment of the nRT-RIC, the nRT-RIC may control the implementation of the O-Cloud optimization policies into the O-Cloud computing environment within the O-RAN. For example, one or more xApps of the nRT-RIC may be connected to an O2 management service (i.e., IMS and / or DMS) that orchestrates the O-Cloud computing environment, wherein the xApp may receive data (i.e., performance data and / or event data, such as non-RAN data) from the O2 management service via an O2 interface API, and if necessary, calculate and send control actions back to implement the O-Cloud optimization policies in the O-Cloud computing environment.

[0068] In operation 304, the O-Cloud computing environment within 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 automatic scaling of O-Cloud instances (i.e., automatic scaling of virtualized / containerized deployments of E2 node applications) according to the O-Cloud optimization policy, where the IMS orchestrates the resource management policy according to the use case embodied in the O-Cloud optimization policy provided by the NRT-RIC.

[0069] 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 within the O-RAN to control the implementation of the O-Cloud optimization policy upon request (e.g., the O2 management service (IMS and / or DMS) may provide non-RAN data to the nRT-RIC).

[0070] For example, Figure 3 Operations 303, 304 and 305 can be performed via Figure 2The O2 interface is executed, and can be executed sequentially, simultaneously or in different orders, and can be executed continuously, periodically, etc.

[0071] according to Figure 3 In the embodiments, access to the O2 interface enables nRT-RIC to control the adaptation of various scenarios and goals. In particular, the fast response time of nRT-RIC via the O2 interface allows RAN operators (i.e., mobile network operators MNOs) to specify different goals for network function layout depending on various scenarios, and allows more flexible configuration of optimization strategies within the SMO.

[0072] Figure 4 4 is a diagram of an example environment 400 in which the systems and / or methods described herein may be implemented. Figure 4 As shown, environment 400 may include user device 410, platform 420, and network 430. The devices of environment 400 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections. Figure 1 Any functions and operations described can be performed by Figure 4 The invention may be performed by any combination of the elements illustrated in the figure.

[0073] User device 410 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information associated with 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 smart phone, a wireless phone, etc.), a wearable device (e.g., a pair of smart glasses, or a smart watch), or the like. In some embodiments, user device 410 can receive information from platform 420 and / or send information to platform 420.

[0074] The platform 420 includes one or more devices capable of receiving, generating, storing, processing and / or providing information. In some embodiments, the platform 420 may include a cloud server or a group of cloud servers. In some embodiments, the platform 420 may be designed to be modular so that certain software components may be swapped in or out depending on specific needs. Therefore, the platform 420 may be easily and / or quickly reconfigured for different purposes.

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

[0076] Cloud computing environment 422 includes an environment hosting platform 420. Cloud computing environment 422 may provide computing, software, data access, storage, etc. services that do not require end users (e.g., user devices 410) to be aware of the physical location and configuration of the system(s) and / or device(s) hosting platform 420. As shown, cloud computing environment 422 may include a set of computing resources 424 (collectively, “computing resources 424,” and individually, “computing resource 424”).

[0077] The computing resources 424 include one or more personal computers, computing device clusters, workstation computers, server devices, or other types of computing and / or communication devices. In some embodiments, the computing resources 424 can host the platform 420. Cloud resources can include computing instances executed in the computing resources 424, storage devices provided in the computing resources 424, data transmission devices provided by the computing resources 424, etc. In some embodiments, the computing resources 424 can communicate with other computing resources 424 via wired connections, wireless connections, or a combination of wired and wireless connections.

[0078] like Figure 4 As further shown, the computing resources 424 include a set of cloud resources, such as one or more applications ("APP") 424-1, one or more virtual machines ("VM") 424-2, virtualized storage devices ("VS") 424-3, one or more hypervisors ("HYP") 424-4, etc.

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

[0080] Virtual machine 424-2 includes a software implementation of a machine (e.g., a computer) that executes programs like a physical machine. Virtual machine 424-2 can be a system virtual machine or a process virtual machine, depending on the use and correspondence of virtual machine 424-2 to any real machine. System virtual machines can provide a complete system platform that supports the execution of a complete operating system ("OS"). Process virtual machines can execute a single program and can support a single process. In some embodiments, virtual machine 424-2 can execute on behalf of a user (e.g., user device 410) and can manage the infrastructure of cloud computing environment 422, such as data management, synchronization, or long-duration data transmission.

[0081] The virtualized storage device 424-3 includes one or more storage systems and / or one or more devices using virtualization technology within the storage system or device of the computing resource 424. In some embodiments, within the context of the storage system, the type of virtualization may include block virtualization and file virtualization. Block virtualization may refer to the abstraction (or separation) of a logical storage device to a physical storage device, so that the storage system can be accessed without considering the physical storage device or heterogeneous structure. Separation may allow the storage system to be managed flexibly in terms of how the administrator manages the storage device of the end user. File virtualization may eliminate the dependency between the data accessed at the file level and the location of the file being physically stored. This may achieve optimization of storage usage, server consolidation, and / or non-disruptive file migration performance.

[0082] Hypervisor 424-4 may provide hardware virtualization technology that allows multiple operating systems (e.g., "guest operating systems") to execute concurrently on a host computer such as computing resource 424. 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 various operating systems may share virtualized hardware resources.

[0083] The network 430 includes one or more wired and / or wireless networks. For example, the network 430 may include 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, a fiber-based network, etc., and / or a combination of these or other types.

[0084] Network.

[0085] Figure 4 The number and arrangement of devices and networks shown are provided as examples. Figure 4There may be additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or differently arranged devices and / or networks than those shown. Figure 4 Two or more of the devices shown may be implemented in a single device, or Figure 4 The single device shown may be implemented as multiple distributed devices. Additionally or alternatively, a set of devices (eg, one or more devices) of environment 400 may perform one or more functions described as being performed by another set of devices of environment 400.

[0086] Figure 5 5 is a diagram of example components of a device 500. Device 500 may correspond to user device 510 and / or platform 520. Figure 5 As shown, 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 .

[0087] Bus 510 includes components that allow communication between components of device 500. Processor 520 is implemented in hardware, firmware, or a combination of hardware and software. Processor 520 can 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 embodiments, processor 520 includes one or more processors that can be programmed to perform functions. Memory 530 includes random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, and / or optical memory) that stores information and / or instructions for use by processor 520.

[0088] Storage component 540 stores information and / or software related to the operation and use of device 500. For example, storage component 540 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optical disk, and / or a solid state disk), a compact disk (CD), a digital versatile disk (DVD), a floppy disk, a cassette, a magnetic tape, and / or another type of non-transient computer-readable medium, and a corresponding drive. Input component 550 includes components that allow device 500 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone). Additionally or alternatively, input component 550 may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, and / or an actuator). Output component 560 includes components that provide output information from device 500 (e.g., a display, a speaker, and / or one or more light emitting diodes (LEDs)).

[0089] The communication interface 570 includes transceiver-like components (e.g., a transceiver and / or a separate receiver and transmitter) that enable the device 500 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. The communication interface 570 can allow the device 500 to receive information from another device and / or provide information to another device. For example, the communication 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.

[0090] Device 500 can perform one or more processes described herein. Device 500 can perform these processes in response to processor 520 executing software instructions stored by non-transient computer-readable media (such as memory 530, and / or storage component 540, etc.). Computer-readable media is defined herein as non-transient memory devices. Memory devices include memory space within a single physical storage device, or memory space spread across multiple physical storage devices.

[0091] The software instructions may be read 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.

[0092] Additionally or alternatively, hardwired circuitry may be used in place of, or in combination with, software instructions to perform one or more of the processes described herein.Thus, the embodiments described herein are not limited to any specific combination of hardware circuitry and software.

[0093] Figure 5The number and arrangement of components shown are provided as examples. Figure 5 The device 500 may include additional components, fewer components, different components, or components that are arranged differently than the components shown. Additionally or alternatively, a set of components (e.g., one or more components) of the device 500 may include:

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

[0095] In an embodiment, Figure 1 , 2 , 3. Any of the operations or processes can be performed by or using Figure 4 and 5 It can be implemented by any one of the elements shown in the figure.

[0096] According to an embodiment, a system and method for implementing O-Cloud optimization policies are provided, wherein nRT-RIC control implements O-Cloud optimization policies into an O-Cloud computing system within an O-RAN via a direct interface between nRT-RIC and the O-Cloud computing environment. The direct interface between nRT-RIC and O-Cloud reduces latency to near real time. Thus, low latency resource control allows energy-efficient network operation of the RAN.

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

[0098] Some embodiments may relate to a system, method and / or computer-readable medium at any possible level of technical detail integration. Further, one or more of the above 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). The computer-readable medium may include a computer-readable non-transient storage medium (or multiple media) having computer-readable program instructions thereon for causing a processor to perform operations.

[0099] Computer readable storage medium can be a tangible device that can retain and store instructions for use by instruction execution devices. Computer readable storage medium can be, for example, but not limited to, electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of computer readable storage medium includes the following: portable computer disk, hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disk read-only memory (CD-ROM), digital versatile disk (DVD), memory stick, floppy disk, mechanical encoding device (such as a punch card or a convex structure in a groove, on which instructions are recorded) and any suitable combination of the foregoing. As used herein, computer readable storage medium should not be interpreted as a transient signal itself, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagated by a waveguide or other transmission medium (such as a light pulse passing through a fiber optic cable), or an electrical signal sent by a wire.

[0100] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to a corresponding computing / processing device, or downloaded 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, transmission optical fibers, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The 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 corresponding computing / processing device.

[0101] The computer readable program code / instruction for performing the operation can be an assembly instruction, an instruction set architecture (ISA) instruction, a machine instruction, a machine-related instruction, a microcode, a firmware instruction, a state setting data, the configuration data of an integrated circuit system, or a source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​(such as Smalltalk, C++, etc.) and process programming languages ​​(such as "C" programming languages ​​or similar programming languages). The computer readable program instruction can be executed completely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer and partially on a remote computer, or completely on a remote computer or server. In the latter scenario, the remote computer can 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 can be connected to an external computer (for example, by using the Internet of an Internet service provider). In certain embodiments, the electronic circuit system including, for example, a programmable logic circuit system, a field programmable gate array (FPGA), or a programmable logic array (PLA) can be executed by using the state information of the computer readable program instruction to personalize the electronic circuit system and execute the computer readable program instruction, so as to perform various aspects or operations.

[0102] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create components for implementing the functions / actions specified in one or more boxes of the flow chart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium (which can instruct a computer, a programmable data processing device, and / or other equipment to operate in a particular manner), so that the computer-readable storage medium having instructions stored therein includes an article of manufacture, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes of the flow chart and / or block diagram.

[0103] These computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable apparatus, or other device implement the functions / actions specified in one or more boxes of the flowchart and / or block diagram.

[0104] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality and operation of possible implementations of the system, method and computer-readable medium according to various embodiments. In this regard, each box in the flowchart or block diagram can represent a module, segment or instruction portion, which includes one or more executable instructions for implementing the specified (multiple) logical functions. Compared with the boxes depicted in the accompanying drawings, the method, computer system and computer-readable medium may include additional boxes, fewer boxes, different boxes or boxes arranged differently. In some alternative embodiments, the functions mentioned in the box may not occur in the order mentioned in the accompanying drawings. For example, in fact, depending on the functionality involved, the two boxes shown in succession can be executed concurrently or substantially concurrently, or these boxes can sometimes be executed in reverse order. It will also be mentioned that each box in the block diagram and / or flowchart illustration and the combination of boxes in the block diagram and / or flowchart illustration can be implemented by a system based on special hardware, which performs a specified function or action or performs a combination of special hardware and computer instructions.

[0105] It will be apparent that the systems and / or methods described herein can be implemented in various forms of hardware, firmware, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the implementation. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code - it is to be understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.

Claims

1. A system for implementing an open cloud (O-Cloud) optimization strategy implemented by an application hosted in a near real-time radio access network intelligent controller (nRT-RIC) of a telecommunications network, the system comprising: a memory storing instructions; as well as 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: receiving the 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 telecommunication network; Controlling implementation of the O-Cloud optimization strategy in the O-Cloud computing environment within the O-RAN.

2. The system of claim 1 , wherein the at least one processor is configured to execute the instructions to: The O-Cloud optimization strategy is received from the NRT-RIC within the SMO framework via an A1 interface.

3. The system of claim 2, wherein the at least one processor is configured to execute the instructions to: Controlling implementation of the O-Cloud optimization policy in the O-Cloud computing environment within the O-RAN via an O2 interface.

4. The system of claim 3, wherein the at least one processor is further configured to execute the instructions to: Data is received from at least one physical host in the O-cloud computing environment within the O-RAN via the O2 interface, the data comprising at least one of: performance data, and event data.

5. The system of claim 4, wherein the at least one processor is further configured to execute the instructions to: Data of at least one O2 management service is sent and received in the O-cloud computing environment via the O2 interface.

6. The system of claim 2, wherein the at least one processor is further configured to execute the instructions to: Controlling implementation of the O-Cloud optimization policy via an O2 interface via at least one O2 management service in the O-Cloud computing environment.

7. The system of claim 4, wherein the performance data of the at least one physical host comprises: Processor load, memory usage, and hard drive usage of the at least one physical host.

8. A method for implementing an open cloud (O-Cloud) optimization strategy implemented by an application hosted in a near real-time radio access network intelligent controller (nRT-RIC) of a telecommunications network, the method comprising: Receiving, by the nRT-RIC, the 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 telecommunication network; The nRT-RIC controls the implementation of the O-Cloud optimization strategy in the O-Cloud computing environment within the O-RAN.

9. The method according to claim 8, wherein the method comprises: The O-Cloud optimization strategy is received by the nRT-RIC from the NRT-RIC within the SMO framework via the A1 interface.

10. The method according to claim 9, wherein the method comprises: The nRT-RIC controls the implementation of the O-Cloud optimization strategy in the O-Cloud computing environment within the O-RAN via the O2 interface.

11. The method according to claim 10, wherein the method comprises: Data is received by the nRT-RIC from at least one physical host in the O-cloud computing environment within the O-RAN via the O2 interface, the data comprising at least one of the following: performance data, and event data.

12. The method according to claim 11, wherein the method comprises: Data of at least one O2 management service is sent and received by the nRT-RIC via the O2 interface in the O-cloud computing environment.

13. The method according to claim 9, wherein the method comprises: The O-Cloud optimization policy is implemented by the nRT-RIC via an O2 interface and via at least one O2 management service in the O-Cloud computing environment.

14. The method according to claim 11, wherein the performance data of the at least one physical host comprises: Processor load, memory usage, and hard drive usage of the at least one physical host.

15. A non-transitory computer-readable recording medium having recorded thereon instructions executable by at least one processor, the at least one processor being configured to implement a near real-time radio access network intelligent controller (nRT-RIC) within an open radio access network (O-RAN) architecture to perform a method for implementing an open cloud (O-Cloud) optimization strategy, the open cloud optimization strategy being implemented by an application hosted in the nRT-RIC, the method comprising: Receiving, by the nRT-RIC, the 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 telecommunication network; The nRT-RIC controls the implementation of the O-Cloud optimization strategy in the O-Cloud computing environment within the O-RAN.

16. The non-transitory computer readable recording medium of claim 15, wherein the method comprises: The O-Cloud optimization strategy is received by the nRT-RIC from the NRT-RIC within the SMO framework via the A1 interface.

17. The non-transitory computer readable recording medium of claim 16, wherein the method comprises: The nRT-RIC controls the implementation of the O-Cloud optimization strategy in the O-Cloud computing environment within the O-RAN via the O2 interface.

18. The non-transitory computer readable recording medium of claim 17, wherein the method comprises: Data is received by the nRT-RIC from at least one physical host in the O-cloud computing environment within the O-RAN via the O2 interface, the data comprising at least one of the following: performance data, and event data.

19. The non-transitory computer readable recording medium of claim 18, wherein the method comprises: Data of at least one O2 management service is sent and received by the nRT-RIC via the O2 interface in the O-cloud computing environment.

20. The non-transitory computer readable recording medium of claim 16, wherein the method comprises: The O-Cloud optimization policy is implemented by the nRT-RIC via an O2 interface and via at least one O2 management service in the O-Cloud computing environment.

Images