Provision of virtualization infrastructure information via the R1 interface

Abstract

This invention provides a wireless access network control device and method that can provide information from a virtualization infrastructure to a Non-RT RIC rApp. [Solution] The wireless access network control device includes at least one processor that performs the following: acquiring virtualization infrastructure information from an O-Cloud that virtually manages a collection of multiple wireless access network nodes by a virtualization infrastructure information acquisition unit, and providing the virtualization infrastructure information to rApp through the R1 interface in the Non-RT RIC of the O-RAN by a virtualization infrastructure information provision unit. The virtualization infrastructure information acquisition unit is provided in the SMO including the Non-RT RIC and acquires virtualization infrastructure information from the O-Cloud through the O2 interface. The virtualization infrastructure information includes at least one of the configuration and telemetry information of the O-Cloud.

Description

Technical Field

[0001] This disclosure relates to the provision of virtualization infrastructure information through the R1 interface.

Background Art

[0002] For the purpose of so-called open networking of radio access networks (RANs) in mobile communication systems or wireless access networks, studies such as "Open RAN," "O-RAN," and "vRAN" are underway. In this specification, the term "O-RAN" is used as a comprehensive term to represent such various "open radio access networks." Therefore, "O-RAN" in this specification is not limited to the standards and specifications of the same name established by the O-RAN Alliance. In O-RAN, a virtualization infrastructure (hereinafter also referred to as O-Cloud for convenience), also called O-Cloud, which virtually manages a set of multiple radio access network nodes (RAN nodes), is provided.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The O-RAN control unit includes a Non-RT RIC (Non-Real Time RAN Intelligent Controller) with a relatively long control cycle (e.g., more than 1 second) for executing application software called rApps, and a Near-RT RIC (Near-Real Time RAN Intelligent Controller) with a relatively short control cycle (e.g., less than 1 second) for executing application software called xApps. Although the Non-RT RIC is responsible for overall O-RAN control, conventional O-RANs lacked a well-defined mechanism for providing information from the virtualization infrastructure (O-Cloud) to the Non-RT RIC's rApps.

[0005] This disclosure is made in light of these circumstances and aims to provide a wireless access network control device, etc., that can provide information from a virtualization infrastructure to a Non-RT RIC rApp. [Means for solving the problem]

[0006] To solve the above problems, a wireless access network control device in one aspect of the present disclosure includes at least one processor that performs the following: a virtualization infrastructure information acquisition unit acquires virtualization infrastructure information from a virtualization infrastructure that virtually manages a collection of multiple wireless access network nodes; and a virtualization infrastructure information provision unit provides the virtualization infrastructure information to rApp through the R1 interface in the Non-RT RIC (Non-Real Time RAN Intelligent Controller) of the O-RAN.

[0007] According to this embodiment, virtualization infrastructure information from the virtualization infrastructure can be provided to rApp through the R1 interface in the Non-RT RIC.

[0008] Another aspect of this disclosure is a method for controlling a wireless access network. This method comprises obtaining virtualization infrastructure information from a virtualization infrastructure that virtually manages a set of multiple wireless access network nodes, and providing the virtualization infrastructure information to rApp through the R1 interface in the Non-RT RIC (Non-Real Time RAN Intelligent Controller) of the O-RAN.

[0009] Another aspect of this disclosure is a storage medium. This storage medium stores a radio access network control program that causes a computer to perform the following actions: acquire virtualization infrastructure information from a virtualization infrastructure that virtually manages a collection of multiple radio access network nodes, and provide the virtualization infrastructure information to rApp through the R1 interface in the Non-RT RIC (Non-Real Time RAN Intelligent Controller) of the O-RAN.

[0010] Furthermore, any combination of the above components, as well as any representations thereof converted into methods, apparatus, systems, recording media, computer programs, etc., are also included in this disclosure. [Effects of the Invention]

[0011] According to this disclosure, information from the virtualization infrastructure can be provided to the Non-RT RIC rApp. [Brief explanation of the drawing]

[0012] [Figure 1] A schematic diagram of a wireless access network control device is shown. [Figure 2] This diagram schematically illustrates the various functions implemented by SMO and / or Non-RT RIC and O-Cloud. [Figure 3] A schematic diagram illustrates the internal configuration and / or functions of the SMO and / or Non-RT RIC. [Figure 4] This is a schematic functional block diagram illustrating a wireless access network control device. [Modes for carrying out the invention]

[0013] In the following, this embodiment will be described in accordance with "O-RAN," which is a standard and specification developed by the O-RAN Alliance. For this purpose, in this embodiment, known terms defined in "O-RAN" will be used for convenience, but the technology relating to this disclosure can also be applied to other existing wireless access networks such as "Open RAN" and "vRAN," as well as similar wireless access networks that may be developed in the future.

[0014] Figure 1 schematically shows an overview of the wireless access network control device according to this embodiment. This wireless access network control device is a RAN control device that controls a wireless access network compliant with O-RAN. The SMO (Service Management and Orchestration) controls the entire RAN control device or the entire O-RAN to coordinate the operation of each part. The SMO is equipped with a Non-RT RIC (Non-Real Time RAN Intelligent Controller) which functions as an overall control processor responsible for overall control. The Non-RT RIC, which has a relatively long control cycle (e.g., 1 second or more), issues guidelines, policies, guidance, etc., regarding the operation of each RAN node (O-CU and / or O-DU described later). Specifically, the Non-RT RIC executes application software called rApp and issues operational guidelines for each RAN node to the Near-RT RIC (Near-Real Time RAN Intelligent Controller) via the A1 interface. Near-RT RICs with relatively short control cycles (e.g., less than 1 second) run application software called xApp to control general-purpose hardware in each RAN node (O-CU / O-DU) itself and the wireless units (O-RU) connected to each RAN node via the E2 interface.

[0015] The illustrated RAN node comprises an O-CU, which is an O-RAN compliant Central Unit (CU), and / or an O-DU, which is an O-RAN compliant Distributed Unit (DU). Both the O-CU and O-DU are responsible for baseband processing in O-RAN, but the O-CU is located on the core network side (not shown), and the O-DU is located on the O-RU side, which is an O-RAN compliant Radio Unit (RU). The O-CU may be divided into an O-CU-CP, which constitutes the control plane (CP), and an O-CU-UP, which constitutes the user plane (UP). The O-CU and O-DU may also be configured integrally as a single baseband processing unit. Furthermore, an O-eNB, which is a base station compliant with O-RAN and the fourth-generation mobile communication system (4G), may be provided as a RAN node. One or more O-RUs are connected to each RAN node (O-CU / O-DU), and are controlled by the Near-RT RIC via each RAN node. The communication devices (UE: User Equipment) within the communication cells provided by each O-RU can connect to the respective O-RU and communicate with the core network (not shown) via each RAN node (O-CU / O-DU).

[0016] Each RAN node (O-CU / O-DU) and Near-RT RIC provides operational data for each RAN node, O-RU, and UE to the SMO via the O1 interface for FCAPS (Fault, Configuration, Accounting, Performance, Security). Based on the operational data obtained via the O1 interface, the SMO updates the operational guidelines for each RAN node issued by the Non-RT RIC to the Near-RT RIC via the A1 interface as needed. Note that O-RUs may also be connected to the SMO and FCAPS via the O1 interface or other interfaces (such as Open Fronthaul M-Plane).

[0017] O-Cloud, a virtualization platform that virtually manages a collection of multiple RAN nodes (O-CU / O-DU), is connected to SMO via the O2 interface. Based on the operational status of the multiple RAN nodes (O-CU / O-DU) obtained from O-Cloud via the O2 interface, SMO generates resource allocation guidelines and load management guidelines for the allocation of resources to the multiple RAN nodes, and issues them to O-Cloud via the O2 interface.

[0018] Figure 2 schematically illustrates the various functions implemented by SMO and / or Non-RT RIC and O-Cloud. SMO primarily implements three functions: FOCOM (Federated O-Cloud Orchestration and Management), NFO (Network Function Orchestrator), and OAM Function. O-Cloud primarily implements two functions: IMS (Infrastructure Management Services) and DMS (Deployment Management Services).

[0019] FOCOM manages the resources in the O-Cloud while receiving service provision from the IMS of the O-Cloud through the O2 interface (O2ims). NFO realizes the coordinated operation of a set of network functions (NFs) by multiple NF Deployments in the O-Cloud while receiving service provision from the DMS of the O-Cloud through the O2 interface (O2dms). NFO may utilize the OAM Function to access the deployed NFs through the O1 interface. The OAM Function is responsible for the FCAPS management of O-RAN managed entities such as RAN nodes. The OAM Function in this embodiment can be a functional block that provides a callback for receiving data on the failures and operating conditions of multiple RAN nodes virtually managed by the O-Cloud by monitoring the procedures or steps of O-2ims and / or O-2dms. The IMS is responsible for managing the resources (hardware) of the O-Cloud and the software used to manage them, and mainly provides services to FOCOM of the SMO. One or more DMSs are responsible for the management of multiple NF Deployments in the O-Cloud, specifically starting, monitoring, ending, etc., and mainly provide services to NFO of the SMO.

[0020] Figure 3 schematically shows the internal configuration and / or functions of the SMO and / or Non-RT RIC. The SMO or SMO Framework includes the Non-RT RIC. The interior of the Non-RT RIC is divided into the Non-RT Framework or Non-RT RIC Framework and the rApp. The solid lines in this figure represent the functional blocks and connections defined in the O-RAN. Also, the dashed lines in this figure represent the functional blocks and connections that can be implemented in this embodiment.

[0021] The SMO framework, excluding the Non-RT RIC, includes O1 Termination, O1 Related Functions, O2 Termination, O2 Related Functions, and Other SMO Framework Functions. The O1 Termination is the end of the O1 interface in the SMO framework. As shown in Figure 1, Near-RT RICs and / or E2 nodes (RAN nodes such as O-CU / O-DU and O-RU, etc.) are connected to the O1 Termination via the O1 interface. The O1 Related Functions, directly connected to the O1 Termination, provide various functions related to the O1 interface, Near-RT RICs, E2 nodes, etc. The O2 Termination is the end of the O2 interface in the SMO framework. As shown in Figure 1, O-Cloud is connected to the O2 Termination via the O2 interface. The O2 Related Functions, directly connected to the O2 Termination, provide various functions related to the O2 interface, O-Cloud, etc. Other SMO framework functions provide functions other than O1-related and O2-related functions. These other SMO framework functions are connected via the A2 termination and A2 interface described later in the Non-RT RIC. Various functions of the SMO framework, such as O1-related functions, O2-related functions, and other SMO framework functions, are connected to the main bus MB, which extends into the Non-RT RIC. Each of these function blocks can exchange data with other function blocks inside and outside the SMO framework (or inside and outside the Non-RT RIC) via the main bus MB.

[0022] The Non-RT Framework, which is the area of the Non-RT RIC excluding rApp, is provided with A1 Termination, A1 Related Functions, A2 Termination, A2 Related Functions, R1 Termination, R1 Service Exposure Functions, External Terminations, Data Management & Exposure Functions, AI / ML Workflow Functions, and Other Non-RT RIC Framework Functions.

[0023] The A1 Termination is the termination of the A1 interface in the Non-RT Framework. As shown in Figure 1, the Near-RT RIC is connected to the A1 Termination via the A1 interface. The A1 Related Functions directly connected to the A1 Termination provide various functions related to the A1 interface, Near-RT RIC, etc. The A2 Termination is the termination of the A2 interface in the Non-RT Framework. Other SMO Framework Functions of the SMO Framework are connected to the A2 Termination via the A2 interface. The A2 Related Functions directly connected to the A2 Termination provide various functions related to the A2 interface, other SMO Framework Functions, etc.

[0024] The R1 termination is the termination of the R1 interface in the Non-RT framework. rApps running on the Non-RT RIC are connected to the R1 termination via the R1 interface. In other words, the R1 interface constitutes the API (Application Programming Interface) of the rApp. The R1 service disclosure function, provided in conjunction with the R1 termination, provides the functionality to disclose data related to services such as the R1 interface and rApps to the main bus MB, and / or to disclose data from the main bus MB to the R1 termination for the R1 interface, rApps, and other services. External terminations are the terminations of various external interfaces (not shown) in the Non-RT framework.

[0025] The data management / disclosure function manages various types of data on the main bus MB and provides the functionality to disclose them in a manner appropriate to the access rights of each functional block. The artificial intelligence / machine learning workflow function provides the functionality to manage workflows executed using artificial intelligence (AI) and / or machine learning (ML) capabilities implemented in Non-RT RIC and / or Near RT RIC. Other Non-RT RIC framework functions provide functions other than those described above for the various Non-RT framework functions. Various Non-RT framework functions such as A1-related functions, A2-related functions, R1 termination, R1 service disclosure function, external termination, data management / disclosure function, artificial intelligence / machine learning workflow function, and other Non-RT RIC framework functions are connected to the main bus MB, which extends outside of Non-RT RIC. Each of these functional blocks can exchange data with other functional blocks inside and outside of Non-RT RIC via the main bus MB.

[0026] Figure 4 is a schematic functional block diagram showing the wireless access network control device 1 according to this embodiment. The wireless access network control device 1 is provided in the SMO framework and / or Non-RT framework in Figure 3. Note that in this figure, some functional blocks in Figure 3 (specifically, external termination, data management / disclosure functions, artificial intelligence / machine learning workflow functions, and other Non-RT RIC framework functions) are omitted from the illustration.

[0027] The wireless access network control device 1 includes a virtualization infrastructure information acquisition unit 11 and a virtualization infrastructure information provision unit 12. These functional blocks are realized through the cooperation of hardware resources such as a processor (such as a central processing unit of a computer), memory, input devices, output devices, and peripheral devices connected to the computer, and software executed using them. Regardless of the type or location of the computer, each of the above functional blocks may be realized with the hardware resources of a single computer, or with a combination of hardware resources distributed across multiple computers. In particular, in this embodiment, some or all of the functional blocks of the wireless access network control device 1 may be realized with processors provided in the SMO and / or Non-RT RIC, or they may be realized in a distributed or centralized manner with computers and processors provided outside the SMO and / or Non-RT RIC.

[0028] The virtualization infrastructure information acquisition unit 11 acquires virtualization infrastructure information from O-Cloud, which serves as the virtualization infrastructure. Specifically, the virtualization infrastructure information acquisition unit 11 is located in the SMO, which includes a Non-RT RIC, and acquires virtualization infrastructure information from O-Cloud via the O2 interface. Specific examples will be described later, but the virtualization infrastructure information includes at least one of the following: O-Cloud configuration and telemetry information. In Figure 4, the virtualization infrastructure information acquisition unit 11 is schematically shown spanning both inside and outside the Non-RT framework on the main bus MB. However, the virtualization infrastructure information acquisition unit 11 only needs to be located in the SMO framework outside the Non-RT framework, either entirely or partially. Furthermore, the virtualization infrastructure information acquisition unit 11 only needs to be able to access relevant functional blocks within the SMO, specifically, O2 termination, O2-related functions, the virtualization infrastructure information provision unit 12, etc., and does not necessarily need to be directly connected to the main bus MB. It is preferable to implement some or all of the functions of the virtualization infrastructure information acquisition unit 11 in the O2-related functions within the SMO framework (outside the Non-RT framework) that are most relevant among these related functional blocks.

[0029] The virtualization infrastructure information provision unit 12 provides the virtualization infrastructure information acquired by the virtualization infrastructure information acquisition unit 11 to rApp via the R1 interface in the Non-RT RIC. In Figure 4, the virtualization infrastructure information provision unit 12 is schematically shown on the main bus MB within the Non-RT framework. However, the virtualization infrastructure information provision unit 12 only needs to be provided in whole or in part within the Non-RT framework. Furthermore, the virtualization infrastructure information provision unit 12 only needs to be able to access related functional blocks within the SMO, specifically the virtualization infrastructure information acquisition unit 11, R1 termination, R1 service disclosure function, etc., and does not necessarily need to be directly connected to the main bus MB. It is preferable that some or all of the functions of the virtualization infrastructure information provision unit 12 be implemented in the R1 service disclosure function within the Non-RT framework, which is the most relevant of these related functional blocks.

[0030] As schematically shown by the arrows in Figure 4, the virtualization infrastructure information acquisition unit 11 within the SMO framework acquires virtualization infrastructure information from O-Cloud through the O2 interface, O2 termination, O2-related functions, main bus MB, etc. The virtualization infrastructure information provision unit 12 within the Non-RT framework provides the virtualization infrastructure information acquired by the virtualization infrastructure information acquisition unit 11 to rApp through the main bus MB, R1 service disclosure function, R1 termination, R1 interface, etc. According to this embodiment, virtualization infrastructure information from O-Cloud can be provided to rApp through the R1 interface in Non-RT RIC.

[0031] Next, we will show a specific example of virtualization infrastructure information that the virtualization infrastructure information acquisition unit 11 can acquire from O-Cloud via the O2 interface.

[0032] In the first specific example, the virtualization infrastructure information acquisition unit 11, implemented by O2-related functions within the SMO framework (outside the Non-RT framework), acquires virtualization infrastructure information from the O-Cloud's IMS by querying the IMS through the O2 interface ("O2ims" in Figure 2). Through various O2ims queries (Query O2ims) specifically illustrated below, the virtualization infrastructure information acquisition unit 11 can acquire virtualization infrastructure information related to the O-Cloud configuration and telemetry from the IMS, and provide it to the virtualization infrastructure information provision unit 12 and rApp via the R1 interface.

[0033] According to the first O2ims query, "Query O2ims_Infrastructure Inventory related Services," the virtualization infrastructure information acquisition unit 11 can obtain information about the O-Cloud's infrastructure resource inventory and management services from the O-Cloud's IMS via the O2 interface (O2ims). This virtualization infrastructure information relates to the configuration of the O-Cloud.

[0034] According to the second O2ims query, "Query O2ims_InfrastructureMonitoring related Services," the virtualization infrastructure information acquisition unit 11 can obtain information related to telemetry reporting from the O-Cloud's IMS via the O2 interface (O2ims). This virtualization infrastructure information pertains to O-Cloud's telemetry.

[0035] According to the third O2ims query, "Query O2ims_InfrastructureProvisioning Services," the virtualization infrastructure information acquisition unit 11 can obtain information about O-Cloud's provisioning services from O-Cloud's IMS via the O2 interface (O2ims). This virtualization infrastructure information relates to the configuration of O-Cloud.

[0036] According to the fourth O2ims query, "Query O2ims_InfrastructureLifecycleManagement Services," the virtualization infrastructure information acquisition unit 11 can obtain information regarding procedural support for automating O-Cloud lifecycle events from the O-Cloud's IMS via the O2 interface (O2ims). This virtualization infrastructure information relates to the configuration of O-Cloud.

[0037] In the second specific example, the virtualization infrastructure information acquisition unit 11, implemented by O2-related functions within the SMO framework (outside the Non-RT framework), acquires virtualization infrastructure information from the O-Cloud's DMS by querying the DMS through the O2 interface ("O2dms" in Figure 2). Through various O2dms queries (Query O2dms) specifically illustrated below, the virtualization infrastructure information acquisition unit 11 can acquire virtualization infrastructure information regarding the O-Cloud configuration and telemetry from one or more DMSs and provide it to the virtualization infrastructure information provision unit 12 and rApp via the R1 interface.

[0038] According to the first O2dms query, "Query O2dms_Deployment Inventory related Services," the virtualization infrastructure information acquisition unit 11 can obtain information regarding the inventory details of various NF Deployments from the O-Cloud's DMS via the O2 interface (O2dms). This virtualization infrastructure information relates to the configuration of O-Cloud.

[0039] According to the second O2dms query, "Query O2dms_Deployment Monitoring related Services," the virtualization infrastructure information acquisition unit 11 can obtain information regarding the telemetry reports of each NF Deployment from the O-Cloud's DMS via the O2 interface (O2dms). This virtualization infrastructure information pertains to O-Cloud's telemetry.

[0040] According to the third O2dms query, "Query O2dms_InfrastructureLifecycleManagement Services," the virtualization infrastructure information acquisition unit 11 can obtain information regarding procedural support for automating NF Deployment lifecycle events from the O-Cloud's DMS via the O2 interface (O2dms). This virtualization infrastructure information pertains to the O-Cloud configuration.

[0041] The present disclosure has been described above based on embodiments. Various modifications are possible for each component and each combination of processes in the exemplary embodiments, and it will be obvious to those skilled in the art that such modifications are included in the scope of the present disclosure.

[0042] The configuration, operation, and function of each device and method described in the embodiments can be realized by hardware resources or software resources, or by the cooperation of hardware resources and software resources. Hardware resources include, for example, processors, ROMs, RAMs, and various integrated circuits. Software resources include, for example, operating systems and application programs.

[0043] This disclosure may be expressed as follows:

[0044] Item 1: The virtualization infrastructure information acquisition unit acquires virtualization infrastructure information from a virtualization infrastructure that virtually manages a collection of multiple wireless access network nodes, The virtualization infrastructure information provision unit provides the virtualization infrastructure information to rApp through the R1 interface in the Non-RT RIC (Non-Real Time RAN Intelligent Controller) of the O-RAN, A wireless access network control device comprising at least one processor that performs the following. Item 2: The wireless access network control device described in item 1, wherein the virtualization infrastructure information acquisition unit is provided in the SMO (Service Management and Orchestration) including the Non-RT RIC and acquires the virtualization infrastructure information from the virtualization infrastructure via the O2 interface. Item 3: The wireless access network control device according to item 1 or 2, wherein the virtualization infrastructure information includes at least one of the configuration of the virtualization infrastructure and information regarding telemetry. Item 4: The virtualization infrastructure is an O-RAN O-Cloud, a wireless access network control device as described in any of items 1 to 3. Item 5: The wireless access network control device described in item 4, wherein the virtualization infrastructure information acquisition unit acquires the virtualization infrastructure information from the Infrastructure Management Services (IMS) of the O-Cloud through a query to the IMS. Item 6: The wireless access network control device described in item 4 or 5, wherein the virtualization infrastructure information acquisition unit acquires the virtualization infrastructure information from the Deployment Management Services (DMS) of the O-Cloud through a query to the DMS. Item 7: This involves obtaining virtualization infrastructure information from a virtualization infrastructure that virtually manages a collection of multiple wireless access network nodes, The virtualization infrastructure information is provided to rApp through the R1 interface in the Non-RT RIC (Non-Real Time RAN Intelligent Controller) of the O-RAN, A wireless access network control method comprising: Item 8: This involves obtaining virtualization infrastructure information from a virtualization infrastructure that virtually manages a collection of multiple wireless access network nodes, The virtualization infrastructure information is provided to rApp through the R1 interface in the Non-RT RIC (Non-Real Time RAN Intelligent Controller) of the O-RAN, A storage medium that stores a wireless access network control program that causes a computer to execute it. [Industrial applicability]

[0045] This disclosure relates to the provision of virtualization infrastructure information through the R1 interface. [Explanation of symbols]

[0046] 1 Wireless access network control device, 11 Virtualization infrastructure information acquisition unit, 12 Virtualization infrastructure information provision unit.

Claims

1. A method used for mobile communication systems and implemented in at least one of SMO (Service Management and Orchestration) and Non-RT RIC (Non-Real Time RAN Intelligent Controller), It provides an O2 deployment management service that supports information queries that give rApps access to information about the O-Cloud deployment management service, The aforementioned O2 deployment management service is (i) O2ims deployment inventory related information queries that enable querying information about O-Cloud deployment resource inventory and event notification services. (ii) O2ims deployment monitoring related information queries that enable querying information related to telemetry reporting, (iii) O2ims deployment provisioning information query that enables querying information about the O-Cloud provisioning service, (iv) O2ims Deployment Lifecycle Management Information Query, which enables querying information about support for procedures for automating O-Cloud lifecycle events. A method comprising at least one of the following.

2. SMO (Service Management and Orchestration), It provides an O2 deployment management service that supports information queries that give rApps access to information about the O-Cloud deployment management service, The aforementioned O2 deployment management service is (i) O2ims deployment inventory related information queries that enable querying information about O-Cloud deployment resource inventory and event notification services. (ii) O2ims deployment monitoring related information queries that enable querying information related to telemetry reporting, (iii) O2ims deployment provisioning information query that enables querying information about the O-Cloud provisioning service, (iv) O2ims Deployment Lifecycle Management Information Query, which enables querying information about support for procedures for automating O-Cloud lifecycle events. An SMO equipped with at least one of the following.

3. Non-RT RIC (Non-Real Time RAN Intelligent Controller), It provides an O2 deployment management service that supports information queries that give rApps access to information about the O-Cloud deployment management service, The aforementioned O2 deployment management service is (i) O2ims deployment inventory related information queries that enable querying information about O-Cloud deployment resource inventory and event notification services. (ii) O2ims deployment monitoring related information queries that enable querying information related to telemetry reporting, (iii) O2ims deployment provisioning information query that enables querying information about the O-Cloud provisioning service, (iv) O2ims Deployment Lifecycle Management Information Query, which enables querying information about support for procedures for automating O-Cloud lifecycle events. Non-RT RIC comprising at least one of the following.

Images