Providing virtualization infrastructure information through the R1 interface

Abstract

A radio access network control device 1 is provided with at least one processor for executing: acquisition, by means of a virtualization infrastructure information acquiring unit 11, of virtualization infrastructure information from an O-Cloud that virtually manages a set of a plurality of radio access network nodes; and provision, by a virtualization infrastructure information providing unit 12, of the virtualization infrastructure information to an rApp through an R1 interface of a Non-Real Time RAN Intelligent Controller (Non-RT RIC) of an O-RAN. The virtualization infrastructure information acquiring unit 11 is provided in a Service Management and Orchestration (SMO) including the Non-RT RIC, and acquires the virtualization infrastructure information from the O-Cloud through an O2 interface. The virtualization infrastructure information includes at least one of the O-Cloud configuration and information relating to telemetry (Fig. 4).

Description

[Technical Field]

[0001] This disclosure relates to providing virtualization infrastructure information through an R1 interface. [Background technology]

[0002] With the aim of opening up radio access networks (RANs) in mobile communication systems, studies are underway on concepts such as "Open RAN," "O-RAN," and "vRAN." In this specification, "O-RAN" is used as a comprehensive term to refer to these various "open radio access networks." Therefore, "O-RAN" in this specification should not be interpreted as being limited to the standards and specifications of the same name established by the O-RAN Alliance. O-RAN provides a virtualization platform known as O-Cloud (hereinafter referred to as O-Cloud for convenience) that virtually manages a collection of multiple radio access network nodes (RAN nodes). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-83058 Summary of the Invention [Problem to be solved by the invention]

[0004] The O-RAN control unit comprises a Non-RT RIC (Non-Real Time RAN Intelligent Controller) with a relatively long control cycle (e.g., one second or more) that executes application software called rApp, and a Near-RT RIC (Near-Real Time RAN Intelligent Controller) with a relatively short control cycle (e.g., less than one second) that executes application software called xApp. Of these, the Non-RT RIC is responsible for overall control of the O-RAN, but in conventional O-RAN, the mechanism for providing information from the virtualization platform (O-Cloud) to the Non-RT RIC's rApp was not fully defined.

[0005] The present disclosure has been made in consideration of these circumstances, and aims to provide a radio access network control device and the like that can provide information from a virtualization infrastructure to an rApp of a Non-RT RIC. [Means for solving the problem]

[0006] In order to solve the above problem, a radio access network control device according to an embodiment of the present disclosure includes at least one processor that executes the following: acquiring, via a virtualization infrastructure information acquisition unit, virtualization infrastructure information from a virtualization infrastructure that virtually manages a set of multiple radio access network nodes; and providing, via a virtualization infrastructure information provision unit, the virtualization infrastructure information to an rApp via an R1 interface in a Non-Real Time RAN Intelligent Controller (Non-RT RIC) of the O-RAN.

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

[0008] Another aspect of the present disclosure is a radio access network control method, which includes: acquiring virtualization infrastructure information from a virtualization infrastructure that virtually manages a set of multiple radio access network nodes; and providing the virtualization infrastructure information to an rApp through an R1 interface in a Non-Real Time RAN Intelligent Controller (Non-RT RIC) of an O-RAN.

[0009] Yet another aspect of the present disclosure is a storage medium storing a radio access network control program that causes a computer to acquire virtualization infrastructure information from a virtualization infrastructure that virtually manages a set of multiple radio access network nodes, and provide the virtualization infrastructure information to an rApp through an R1 interface in a Non-Real Time RAN Intelligent Controller (Non-RT RIC) of an O-RAN.

[0010] Any combination of the above components, or any conversion of these expressions into methods, devices, systems, recording media, computer programs, etc., are also encompassed within the present disclosure. [Effects of the Invention]

[0011] According to the present disclosure, information from the virtualization infrastructure can be provided to an rApp in a Non-RT RIC. [Brief explanation of the drawings]

[0012] [Figure 1] 1 shows a schematic overview of a radio access network control device. [Figure 2] Schematic diagram of various functions realized by SMO and / or Non-RT RIC and O-Cloud. [Figure 3] 1 shows a schematic diagram of the internal structure and / or function of the SMO and / or Non-RT RIC. [Figure 4] FIG. 2 is a functional block diagram illustrating a radio access network control device. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, this embodiment will be described in accordance with "O-RAN," which is a standard and specification established by the O-RAN Alliance. Therefore, this embodiment will use well-known terms defined by "O-RAN" for convenience, but the technology disclosed herein can also be applied to other existing radio access networks such as "Open RAN" and "vRAN," as well as similar radio access networks that may be developed in the future.

[0014] FIG. 1 shows a schematic overview of a radio access network control device according to this embodiment. This radio access network control device is a RAN control device that controls a radio access network compliant with O-RAN. The SMO (Service Management and Orchestration) controls the entire RAN control device or the entire O-RAN, causing each unit to operate in a coordinated manner. The SMO includes 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 period (e.g., one second or longer), issues guidelines, policies, guidance, etc. regarding the operation of each RAN node (O-CU and / or O-DU, described below). Specifically, the Non-RT RIC runs application software called rApp and issues operation guidelines for each RAN node to the Near-RT RIC (Near-Real Time RAN Intelligent Controller) via the A1 interface. The Near-RT RIC, which has a relatively short control period (for example, less than one second), runs application software called xApp to control each RAN node (O-CU / O-DU) itself and general-purpose hardware in the radio unit (O-RU) connected to each RAN node through the E2 interface.

[0015] The illustrated RAN node includes 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 that constitutes the control plane (CP) and an O-CU-UP that constitutes the user plane (UP). The O-CU and O-DU may be integrated into a single baseband processing unit. Alternatively, the RAN node may include an O-eNB, which is a base station compliant with O-RAN and the fourth-generation mobile communication system (4G). One or more O-RUs are connected to each RAN node (O-CU / O-DU), and are controlled by a Near-RT RIC via the RAN node. A communication device (UE: User Equipment) within a communication cell provided by each O-RU can be connected to each O-RU and can perform mobile communication with a 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 operation data of each RAN node, each O-RU, and each UE to the SMO via the O1 interface for so-called FCAPS (Fault, Configuration, Accounting, Performance, Security). Based on the operation data obtained via the O1 interface, the SMO updates the operation guidelines of each RAN node issued by the Non-RT RIC to the Near-RT RIC via the A1 interface as needed. Note that the O-RU may be connected to the SMO for FCAPS via the O1 interface or another interface (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 multiple RAN nodes (O-CU / O-DU) obtained from O-Cloud via the O2 interface, SMO generates resource allocation guidelines for resource allocation of the multiple RAN nodes and load management guidelines for workload management, and issues them to O-Cloud via the O2 interface.

[0018] Figure 2 shows a schematic diagram of the various functions realized by SMO and / or Non-RT RIC and O-Cloud. SMO mainly realizes three functions: FOCOM (Federated O-Cloud Orchestration and Management), NFO (Network Function Orchestrator), and OAM Function. O-Cloud mainly realizes two functions: IMS (Infrastructure Management Services) and DMS (Deployment Management Services).

[0019] FOCOM manages resources in the O-Cloud while receiving services from the IMS of the O-Cloud through the O2 interface (O2ims). NFO realizes the coordinated operation of a collection of Network Functions (NFs) through multiple NF deployments in the O-Cloud while receiving services from the DMS of the O-Cloud through the O2 interface (O2dms). The NFO may use an OAM function to access deployed NFs through the O1 interface. The OAM function is responsible for FCAPS management of O-RAN managed entities such as RAN nodes. In this embodiment, the OAM function can be a function block that provides callbacks to receive data on faults and operational status of multiple RAN nodes virtually managed by the O-Cloud by monitoring the procedures or procedures of O2ims and / or O2dms. The IMS is responsible for managing O-Cloud resources (hardware) and the software used to manage them, and provides services mainly to FOCOM in the SMO. One or more DMSs are responsible for managing multiple NF deployments in the O-Cloud, specifically starting, monitoring, terminating, etc., and provide services primarily to the SMO's NFO.

[0020] Figure 3 shows a schematic diagram of 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 Non-RT RIC is internally divided into the Non-RT Framework or Non-RT RIC Framework and rApp. The solid lines in this diagram represent functional blocks and connections defined in O-RAN. The dashed lines in this diagram represent functional blocks and connections that can be implemented in this embodiment.

[0021] In the SMO framework, the area excluding the Non-RT RIC is provided with an O1 termination, O1 related functions, O2 termination, O2 related functions, and other SMO framework functions. The O1 termination is the termination of the O1 interface in the SMO framework. As shown in FIG. 1, Near-RT RICs and / or E2 nodes (RAN nodes such as O-CU / O-DU, 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 RIC, E2 nodes, etc. The O2 termination is the termination of the O2 interface in the SMO framework. As shown in FIG. 1, the 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 the O1-related functions and O2-related functions. The other SMO framework functions are connected to the A2 terminal (described later) in the Non-RT RIC via the A2 interface. Various functions of the SMO framework, such as the O1-related functions, O2-related functions, and other SMO framework functions, are connected to the main bus MB, which also extends inside 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, includes A1 Termination, A1 Related Functions, A2 Termination, A2 Related Functions, R1 Termination, R1 Service Exposure Functions, External Terminations, Data Management & Exposure Functions, Artificial Intelligence / Machine Learning Workflow Functions, and Other Non-RT RIC Framework Functions.

[0023] The A1 terminal is the terminal of the A1 interface in the Non-RT framework. As shown in Figure 1, the Near-RT RIC is connected to the A1 terminal via the A1 interface. The A1-related functions directly connected to the A1 terminal provide various functions related to the A1 interface, Near-RT RIC, etc. The A2 terminal is the terminal of the A2 interface in the Non-RT framework. Other SMO framework functions of the SMO framework are connected to the A2 terminal via the A2 interface. The A2-related functions directly connected to the A2 terminal 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. An rApp running on a Non-RT RIC is 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 association with the R1 termination provides the function of disclosing data related to services such as the R1 interface and rApp to the main bus MB, etc., and / or the function of disclosing data from the main bus MB, etc. to the R1 termination, etc., for services such as the R1 interface and rApp, etc. The external termination is the termination of various external interfaces (not shown) in the Non-RT framework.

[0025] The data management / disclosure function manages various data on the main bus MB and provides a function to disclose it in a manner according to the access privileges of each functional block. The artificial intelligence / machine learning workflow function provides a function to manage workflows executed using the artificial intelligence (AI) and / or machine learning (ML) capabilities implemented in the Non-RT RIC and / or Near RT RIC. The other Non-RT RIC framework functions provide functions other than the functions of the various Non-RT frameworks described above. Various functions of the Non-RT framework, 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 that extends outside the Non-RT RIC. Each of these functional blocks can exchange data with other functional blocks inside and outside the Non-RT RIC through the main bus MB.

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

[0027] The radio 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 by the cooperation of hardware resources such as a processor, such as a central processing unit of a computer, a memory, an input device, an output device, and peripheral devices connected to the computer, and software executed using these. Regardless of the type of computer or the installation location, each of the above functional blocks may be realized by the hardware resources of a single computer, or may be realized by combining hardware resources distributed among multiple computers. In particular, in this embodiment, some or all of the functional blocks of the radio access network control device 1 may be realized by a processor provided in the SMO and / or Non-RT RIC, or may be realized in a distributed or centralized manner by computers or 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 a virtualization infrastructure. Specifically, the virtualization infrastructure information acquisition unit 11 is provided in an SMO including a Non-RT RIC, and acquires virtualization infrastructure information from O-Cloud through the O2 interface. A specific example will be described later, but the virtualization infrastructure information includes at least one of information regarding the configuration of O-Cloud and telemetry. In FIG. 4, the virtualization infrastructure information acquisition unit 11 is schematically illustrated as spanning both the inside and outside of the Non-RT framework on the main bus MB. However, the virtualization infrastructure information acquisition unit 11 may be provided entirely or partially within the SMO framework outside the Non-RT framework. Furthermore, the virtualization infrastructure information acquisition unit 11 need only be able to access related functional blocks within the SMO, specifically, the O2 termination, O2-related functions, the virtualization infrastructure information provision unit 12, and the like, and need not necessarily be directly connected to the main bus MB. Of these related function blocks, it is preferable to realize some or all of the functions of the virtualization infrastructure information acquisition unit 11 in the O2 related function within the most related SMO framework (outside the Non-RT framework).

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

[0030] As shown schematically by the arrows in Figure 4, the virtualization infrastructure information acquisition unit 11 in the SMO framework acquires virtualization infrastructure information from O-Cloud via the O2 interface, O2 termination, O2-related functions, main bus MB, etc. The virtualization infrastructure information provision unit 12 in the Non-RT framework provides the virtualization infrastructure information acquired by the virtualization infrastructure information acquisition unit 11 to the rApp via 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 the rApp via the R1 interface in the Non-RT RIC.

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

[0032] In the first specific example, the virtualization infrastructure information acquisition unit 11, which is realized by an O2-related function within the SMO framework (outside the Non-RT framework), acquires virtualization infrastructure information from the IMS of O-Cloud by making a query to the IMS via the O2 interface ("O2ims" in Figure 2). By using various O2ims queries (Query O2ims) specifically exemplified below, the virtualization infrastructure information acquisition unit 11 can acquire virtualization infrastructure information related to the configuration and telemetry of O-Cloud from the IMS, and provide it to the rApp via the virtualization infrastructure information provision unit 12 and 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 infrastructure resource inventory and management services of O-Cloud from the IMS of O-Cloud through the O2 interface (O2ims). This virtualization infrastructure information is related to the configuration of O-Cloud.

[0034] According to the second O2ims query “Query O2ims_InfrastructureMonitoring related Services”, the virtualization infrastructure information acquisition unit 11 can acquire information about telemetry reports from the IMS of O-Cloud through the O2 interface (O2ims). This virtualization infrastructure information is related to telemetry of O-Cloud.

[0035] According to the third O2ims query, “Query O2ims_InfrastructureProvisioningServices,” the virtualization infrastructure information acquisition unit 11 can acquire information about the provisioning services of O-Cloud from the IMS of O-Cloud through the O2 interface (O2ims). This virtualization infrastructure information is related 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 acquire information about procedural support for automating lifecycle events of O-Cloud from the IMS of O-Cloud through the O2 interface (O2ims). This virtualization infrastructure information is related to the configuration of O-Cloud.

[0037] In the second specific example, the virtualization infrastructure information acquisition unit 11, which is realized by an O2-related function within the SMO framework (outside the Non-RT framework), acquires virtualization infrastructure information from the DMS of O-Cloud by making a query to the DMS through the O2 interface ("O2dms" in Figure 2). By using various O2dms queries (Query O2dms) specifically exemplified below, the virtualization infrastructure information acquisition unit 11 can acquire virtualization infrastructure information related to the configuration and telemetry of O-Cloud from one or more DMSs, and provide it to the rApp via the virtualization infrastructure information provision unit 12 and the R1 interface.

[0038] According to the first O2dms query “Query O2dms_Deployment Inventory related Services”, the information about the inventory details of various NF Deployments can be obtained from the DMS of O-Cloud through the O2 interface (O2dms) by the virtualization infrastructure information acquisition unit 11. This virtualization infrastructure information is related 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 acquire information about the telemetry reports of each NF Deployment from the DMS of O-Cloud through the O2 interface (O2dms). This virtualization infrastructure information is related to the telemetry of O-Cloud.

[0040] According to the third O2dms query, “Query O2dms_InfrastructureLifecycleManagement Services,” the virtualization infrastructure information acquisition unit 11 can acquire information about procedural support for automating lifecycle events of NF Deployment from the DMS of O-Cloud through the O2 interface (O2dms). This virtualization infrastructure information is related to the configuration of O-Cloud.

[0041] The present disclosure has been described above based on the embodiments. Various modifications are possible to the combinations of the components and processes in the exemplary embodiments, and it will be obvious to those skilled in the art that such modifications are included within 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, software resources, or a combination of hardware and software resources. Examples of hardware resources include processors, ROMs, RAMs, and various integrated circuits. Examples of software resources include operating systems, applications, and other programs.

[0043] This disclosure may be expressed in the following terms:

[0044] Item 1: acquiring, by a virtualization infrastructure information acquisition unit, virtualization infrastructure information from a virtualization infrastructure that virtually manages a set of multiple radio access network nodes; A virtualization infrastructure information providing unit provides the virtualization infrastructure information to the rApp through an R1 interface in a Non-Real Time RAN Intelligent Controller (Non-RT RIC) of the O-RAN; A radio access network controller comprising at least one processor executing: Item 2: The radio access network control device described in item 1, wherein the virtualization infrastructure information acquisition unit is provided in an SMO (Service Management and Orchestration) including the Non-RT RIC and acquires the virtualization infrastructure information from the virtualization infrastructure via an O2 interface. Item 3: 3. The radio access network control device according to item 1 or 2, wherein the virtualization infrastructure information includes at least one of information relating to the configuration of the virtualization infrastructure and information relating to telemetry. Item 4: 4. The radio access network control device according to any one of items 1 to 3, wherein the virtualization platform is an O-Cloud of an O-RAN. Item 5: Item 5. The radio access network control device according to item 4, wherein the virtualization infrastructure information acquisition unit acquires the virtualization infrastructure information from an Infrastructure Management Services (IMS) of the O-Cloud through an inquiry to the IMS. Item 6: 6. The radio access network control device according to item 4 or 5, wherein the virtualization infrastructure information acquisition unit acquires the virtualization infrastructure information from a Deployment Management Services (DMS) of the O-Cloud through an inquiry to the DMS. Item 7: Acquiring virtualization infrastructure information from a virtualization infrastructure that virtually manages a set of multiple radio access network nodes; Providing the virtualization infrastructure information to the rApp through an R1 interface in a Non-Real Time RAN Intelligent Controller (Non-RT RIC) of the O-RAN; A radio access network control method comprising: Item 8: Acquiring virtualization infrastructure information from a virtualization infrastructure that virtually manages a set of multiple radio access network nodes; Providing the virtualization infrastructure information to the rApp through an R1 interface in a Non-Real Time RAN Intelligent Controller (Non-RT RIC) of the O-RAN; A storage medium storing a radio access network control program that causes a computer to execute the above. [Industrial Applicability]

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

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

Claims

1. acquiring, by a virtualization infrastructure information acquisition unit, virtualization infrastructure information from a virtualization infrastructure that virtually manages a set of multiple radio access network nodes; A virtualization infrastructure information providing unit provides the virtualization infrastructure information to the rApp through an R1 interface in a Non-Real Time RAN Intelligent Controller (Non-RT RIC) of the O-RAN; at least one processor executing The virtualization infrastructure information includes at least one of information regarding the configuration of the virtualization infrastructure and information regarding telemetry.

2. The radio access network control device according to claim 1, wherein the virtualization infrastructure information acquisition unit is provided in an SMO (Service Management and Orchestration) including the Non-RT RIC, and acquires the virtualization infrastructure information from the virtualization infrastructure via an O2 interface.

3. The radio access network control device according to claim 1 , wherein the virtualization platform is an O-Cloud of an O-RAN.

4. A method for implementing a method of managing a wireless access network node by a virtualization infrastructure information acquisition unit, comprising: acquiring virtualization infrastructure information from a virtualization infrastructure that virtually manages a set of multiple wireless access network nodes; A virtualization infrastructure information providing unit provides the virtualization infrastructure information to the rApp through an R1 interface in a Non-Real Time RAN Intelligent Controller (Non-RT RIC) of the O-RAN; at least one processor executing The virtualization platform is O-Cloud of O-RAN, The virtualization infrastructure information acquisition unit is a radio access network control device that acquires the virtualization infrastructure information from an Infrastructure Management Services (IMS) of the O-Cloud through an inquiry to the IMS.

5. A method for managing a wireless access network node by a virtualization infrastructure information acquisition unit, comprising: acquiring virtualization infrastructure information from a virtualization infrastructure that virtually manages a set of multiple wireless access network nodes; A virtualization infrastructure information providing unit provides the virtualization infrastructure information to the rApp through an R1 interface in a Non-Real Time RAN Intelligent Controller (Non-RT RIC) of the O-RAN; at least one processor executing The virtualization platform is O-Cloud of O-RAN, The virtualization infrastructure information acquisition unit is a radio access network control device that acquires the virtualization infrastructure information from Deployment Management Services (DMS) of the O-Cloud through an inquiry to the DMS.

6. Acquiring virtualization infrastructure information from a virtualization infrastructure that virtually manages a set of multiple radio access network nodes; Providing the virtualization infrastructure information to the rApp through an R1 interface in a Non-Real Time RAN Intelligent Controller (Non-RT RIC) of the O-RAN; Equipped with A radio access network control method, wherein the virtualization infrastructure information includes at least one of information regarding the configuration of the virtualization infrastructure and information regarding telemetry.

7. Acquiring virtualization infrastructure information from a virtualization infrastructure that virtually manages a set of multiple radio access network nodes; Providing the virtualization infrastructure information to the rApp through an R1 interface in a Non-Real Time RAN Intelligent Controller (Non-RT RIC) of the O-RAN; on the computer, The virtualization infrastructure information is a storage medium that stores a radio access network control program that includes at least one of information regarding the configuration of the virtualization infrastructure and information regarding telemetry.

Images