Verification of rApp indications in SMO
By introducing an instruction verification and distribution unit into the SMO of O-RAN, the resource waste caused by the indiscriminate distribution of instructions generated by rApp is solved, and efficient instruction distribution and O-RAN performance are improved.
Patent Information
- Application Number
- CN202280093797.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-09-16
- Publication Date
- 2024-11-12
AI Technical Summary
In the SMO of O-RAN, the instructions generated by rApp are indiscriminately published outside the SMO, resulting in conflicting instructions between rApps of different tasks and wasting resources.
The introduction of an instruction verification department and an instruction release department ensures efficient instruction release by verifying instructions generated by rApp within the SMO and performing priority allocation, release scheduling, and cancellation processing before release.
This effectively avoids contradictions between instructions generated by rApp, improves the performance and efficiency of O-RAN, and reduces resource waste.
Smart Images

Figure CN118947169A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to verification of rApp indication in SMO of O-RAN. Background Art
[0002] With the goal of so-called openness of the radio access network (RAN) in a mobile communication system or MOBILE communication system, discussions on "Open RAN", "O-RAN", "vRAN", etc. are ongoing. In this specification, "O-RAN" is used as a term that inclusively represents various "open radio access networks". Therefore, "O-RAN" in this specification is not to be interpreted as a restrictive standard or specification of the same name established by the O-RAN Alliance.
[0003] The control unit of O-RAN includes a Non-RT RIC (Non-Real Time RAN Intelligent Controller) with a relatively long control cycle (e.g., more than 1 second) 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 1 second) that executes application software called xApp. In addition, in O-RAN, a virtualized infrastructure (hereinafter referred to as O-Cloud for convenience) is provided, which virtually manages a collection of multiple radio access network nodes (RAN nodes) and is also called O-Cloud (Open Cloud).
[0004] Prior art literature
[0005] Patent Literature
[0006] Patent Document 1: Japanese Patent Application Publication No. 2021-83058 Summary of the invention
[0007] Problems to be solved by the invention
[0008] Non-RT RIC is set in SMO (Service Management and Orchestration), and various instructions are generated to RAN nodes, O-Cloud, Near-RT RIC, etc. outside SMO through the execution of rApp. These instructions are released to the outside of SMO through various interfaces such as O1 interface, O2 interface, A1 interface, etc. In the existing SMO, regardless of the object (RAN node, O-Cloud, Near-RT RIC, etc.) and interface (O1 interface, O2 interface, A1 interface, etc.), the instructions generated by rApp are released to the outside of SMO almost as is. Therefore, there is a risk that rApps that perform different tasks and operations will issue contradictory instructions to the outside of SMO, and the resources of SMO itself and outside SMO are wasted for their execution, resolution, adjustment, etc.
[0009] The present disclosure is an invention made in view of such a situation, and an object of the present invention is to provide a radio access network control device and the like that can efficiently issue an instruction to generate an rApp to outside the SMO.
[0010] Solutions to Solve Problems
[0011] In order to solve the above-mentioned problem, a radio access network control device of one aspect of the present disclosure includes at least one processor, and the at least one processor executes: an indication verification unit of an SMO (Service Management and Orchestration) set in O-RAN verifies the indication to the outside of the SMO generated by the rApp executed by the Non-RT RIC (Non-Real Time RAN Intelligent Controller) in the SMO; and an indication issuing unit set in the SMO issues the verified indication to the outside of the SMO.
[0012] In this aspect, before the instruction issuing unit provided in the SMO issues the instruction of the rApp to the outside of the SMO, the instruction verification unit provided in the SMO verifies the instruction. Therefore, among the instructions generated by the rApp, the instructions verified by the instruction verification unit are efficiently issued to the outside of the SMO by the instruction issuing unit.
[0013] Another aspect of the present disclosure is a radio access network control method. The method includes: at the O-RAN SMO (Service Management and Orchestration), verifying the indication to the outside of the SMO generated by the rApp executed by the Non-RT RIC (Non-Real Time RAN Intelligent Controller) in the SMO; and at the SMO, issuing the verified indication to the outside of the SMO.
[0014] Another aspect of the present disclosure is a storage medium. The storage medium stores a radio access network control program, which causes a computer to execute: at the O-RAN's SMO (Service Management and Orchestration), verify an indication to the outside of the SMO generated by the rApp executed by the Non-RT RIC (Non-Real Time RAN Intelligent Controller) in the SMO; and at the SMO, issue the verified indication to the outside of the SMO.
[0015] Furthermore, any combination of the above constituent elements, and any combination of expressions thereof converted into methods, apparatuses, systems, recording media, computer programs, etc. are also included in the present disclosure.
[0016] Effects of the Invention
[0017] According to the present disclosure, instructions generated by rApp can be efficiently released to the outside of SMO. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] Figure 1 An overview of a radio access network control device is schematically shown.
[0019] Figure 2 The various functions implemented by the SMO and / or Non-RT RIC and O-Cloud are schematically shown.
[0020] Figure 3 The internal structure and / or function of a SMO and / or Non-RT RIC are schematically shown.
[0021] Figure 4 is a functional block diagram schematically showing a radio access network control device. DETAILED DESCRIPTION
[0022] The present embodiment is described below in accordance with "O-RAN" which is a standard and specification established by the O-RAN Alliance. Therefore, in this embodiment, for the sake of convenience, well-known terms defined by "O-RAN" are used, but the technology involved in the present disclosure can also be applied to other existing radio access networks such as "Open RAN" and "vRAN", and similar radio access networks that may be developed in the future.
[0023] Figure 1 The outline of the radio access network control device involved in this embodiment is schematically shown. The radio access network control device is a RAN control device that controls a radio access network that conforms to O-RAN. SMO (Service Management and Orchestration) controls the entire RAN control device or the entire O-RAN so that each part can work in coordination. SMO includes Non-RT RIC (Non-Real Time RAN Intelligent Controller), which functions as an overall control processor that assumes overall control. The Non-RT RIC with a relatively long control cycle (for example, more than 1 second) issues guidelines, policies, instructions related to the operation of each RAN node (O-CU and / or O-DU described later), and structural change instructions related to structural changes outside the SMO such as each RAN node, O-Cloud, Near-RT RIC (Near-Real Time RAN Intelligent Controller), etc. Specifically, the Non-RT RIC executes application software called rApp to issue operation guidelines for each RAN node of the Near-RT RIC through the A1 interface, and to issue structural change instructions outside the SMO through the O1 interface, O2 interface, etc. The Near-RT RIC with a relatively short control cycle (for example, less than 1 second) executes application software called xApp to control each RAN node (O-CU / O-DU) itself, the common hardware in the radio unit (O-RU) connected to the RAN node, etc. through the E2 interface.
[0024] The illustrated RAN node is an O-CU as a central unit (CU: Central Unit) conforming to O-RAN and / or an O-DU as a distributed unit (DU: Distributed Unit) conforming to O-RAN. O-CU and O-DU are both responsible for baseband processing in O-RAN, O-CU is set on the core network side not shown, and O-DU is set on the O-RU side as a radio unit (RU: Radio Unit) conforming to O-RAN. O-CU can be divided into O-CU-CP constituting a control plane (CP: Control Plane) and O-CU-UP constituting a user plane (UP: User Plane). In addition, O-CU and O-DU can be integrally constituted as a baseband processing unit. In addition, as a RAN node, an O-eNB as a base station conforming to O-RAN and a fourth-generation mobile communication system (4G) can be set. One or more O-RUs are connected to each RAN node (O-CU / O-DU), which is controlled by Near-RT RIC via each RAN node. A communicator (UE: User Equipment) within a communication cell provided by each O-RU can be connected to the O-RU and can perform mobile communication with a core network (not shown) via each RAN node (O-CU / O-DU).
[0025] For the so-called FCAPS (Fault, Configuration, Accounting, Performance, Security), each RAN node (O-CU / O-DU) and Near-RT RIC provide the SMO with the operation data of each RAN node, each O-RU, and each UE through the O1 interface. Based on the operation data obtained through the O1 interface, the SMO updates the operation guide of each RAN node issued by the Non-RT RIC to the Near-RT RIC through the A1 interface, and the structural change instructions outside the SMO issued by the Non-RTRIC through the O1 interface and the O2 interface, etc. for FCAPS. In addition, for FCAPS, the O-RU can be connected to the SMO through the O1 interface and other interfaces (Open Fronthaul M-Plane, etc.).
[0026] O-Cloud, as a virtualized infrastructure, is connected to SMO through the O2 interface. The virtualized infrastructure virtually manages a collection of multiple RAN nodes (O-CU / O-DU). Based on the operating status of multiple RAN nodes (O-CU / O-DU) obtained from O-Cloud through the O2 interface, SMO generates resource allocation guidelines related to resource allocation of the multiple RAN nodes and load management guidelines related to workload management, and publishes them to O-Cloud through the O2 interface.
[0027] Figure 2 The various functions implemented by SMO and / or Non-RT RIC and O-Cloud are schematically shown. In SMO, the three main functions implemented are FOCOM (Federated O-Cloud Orchestration and Management), NFO (Network Function Orchestrator), and OAM function (OAMFunction). In O-Cloud, the two main functions implemented are IMS (Infrastructure Management Services) and DMS (Deployment Management Services).
[0028] FOCOM receives service provision from IMS of O-Cloud through O2 interface (O2ims) and manages resources in O-Cloud. NFO receives service provision from DMS of O-Cloud through O2 interface (O2dms) and implements the coordinated action of a collection of network functions (NF) through multiple NF Deployments in O-Cloud. In order to access the deployed NF through O1 interface, NFO can also use OAM function. OAM function is responsible for FCAPS management of O-RAN management entities such as RAN nodes. The OAM function in this embodiment can be a functional block, which provides a callback for receiving data related to the failure and operation status of multiple RAN nodes virtually managed by O-Cloud by monitoring the process or steps of O2ims and / or O2dms. IMS is responsible for the management of O-Cloud resources (hardware) and software used to manage them, and mainly provides services to FOCOM of SMO. One or more DMSs are responsible for the management of multiple NF Deployments in the O-Cloud. Specifically, they are responsible for starting, monitoring, and ending NF Deployments, and mainly provide services for the NFO of the SMO.
[0029] Figure 3 The internal structure and / or function of SMO and / or Non-RT RIC is schematically shown. SMO or SMO Framework includes Non-RT RIC. The interior of Non-RT RIC is divided into Non-RT Framework or Non-RT RIC Framework and rApp. The solid lines in this figure represent functional blocks and connections defined by O-RAN. In addition, the dotted lines in this figure represent functional blocks and connections that can be installed in this embodiment.
[0030] In the area other than Non-RT RIC in the SMO framework, set O1 Termination, O1 Related Functions, O2 Termination, O2 Related Functions and Other SMO Framework Functions. O1 Termination is the terminal of O1 interface in SMO framework. Figure 1As shown, the O1 terminal is connected to the Near-RT RIC and / or E2 node (RAN node such as O-CU / O-DU, O-RU, etc.) via the O1 interface. The O1-related functions directly connected to the O1 terminal provide various functions related to the O1 interface, Near-RT RIC, E2 node, etc. The O2 terminal is the terminal of the O2 interface in the SMO framework. Figure 1 As shown, the O2 terminal is connected to O-Cloud via the O2 interface. The O2-related functions directly connected to the O2 terminal provide various functions related to the O2 interface, O-Cloud, etc. Other SMO framework functions provide other functions other than O1-related functions and O2-related functions. Other SMO framework functions are connected to the A2 interface (not shown) via the A2 terminal (not shown) 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 that also extends to the inside of the Non-RT RIC. These functional blocks can exchange data with other functional blocks inside and outside the SMO framework (or inside and outside the Non-RTRIC) through the main bus MB.
[0031] In the Non-RT Framework, which is an area other than rApp in the Non-RT RIC, A1 termination, A1 related functions, not-shown A2 termination, not-shown A2 related functions, R1 termination, R1 service exposure functions, external terminations, data management / exposure functions, AI / ML workflow functions, policy / conflict management functions, and other Non-RT RIC framework functions are set.
[0032] The A1 terminal is the terminal of the A1 interface in the Non-RT framework. Figure 1As shown, the A1 terminal is connected to the Near-RT RIC 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 not shown is a terminal of the A2 interface not shown in the Non-RT framework. The A2 terminal is connected to other SMO framework functions of the SMO framework via the A2 interface. The A2-related functions not shown directly connected to the A2 terminal provide various functions related to the A2 interface, other SMO framework functions, etc.
[0033] The R1 terminal is a terminal of the R1 interface in the Non-RT framework. The rApp executed on the Non-RT RIC is connected to the R1 terminal via the R1 interface. That is, the R1 interface constitutes the API (Application Programming Interface) of the rApp. The R1 service opening function provided with the R1 terminal provides the following functions: the function of opening data related to the services of the R1 interface, rApp, etc. to the main bus MB, etc., and / or the function of opening data from the main bus MB, etc. to the R1 terminal, etc. for the services of the R1 interface, rAPP, etc. The external terminal is a terminal of various external interfaces not shown in the figure in the Non-RT framework.
[0034] The data management / opening function provides a function to manage various data on the main bus MB and open it in a form corresponding to the access rights of each functional block. The artificial intelligence / machine learning workflow function provides a function to manage workflows that are executed using artificial intelligence (AI: Artificial Intelligence) and / or machine learning (ML: Machine Learning) capabilities installed in the Non-RT RIC and / or Near RT RIC. As described later, the policy / conflict management function constitutes an instruction verification unit that verifies instructions (operation guides, structural change instructions) generated by rApp to the outside of SMO.
[0035] Other Non-RT RIC framework functions provide other functions beyond the above various Non-RT framework functions. Various functions of the Non-RT framework, such as A1-related functions, A2-related functions, R1 terminals, R1 service open functions, external terminals, data management / open functions, artificial intelligence / machine learning workflow functions, policy / conflict management functions, and other Non-RT RIC framework functions, are connected to the main bus MB that also extends to the outside of the Non-RT RIC. These functional blocks can exchange data with other functional blocks inside and outside the Non-RT RIC through the main bus MB.
[0036] Figure 42 is a functional block diagram schematically showing a radio access network control device 1 according to the present embodiment. The radio access network control device 1 is provided at Figure 3 In the SMO framework and / or Non-RT framework in this figure, Figure 3 Illustration of some functional blocks in the RIC framework (specifically, R1 service exposure function, external terminal, data management / open function, artificial intelligence / machine learning workflow function, and other Non-RT RIC framework functions).
[0037] The radio access network control device 1 includes an O1 / O2 information acquisition unit 11, an O1 / O2 information provision unit 12, an operation guide generation unit 13, a configuration change instruction generation unit 14, an instruction verification unit 15, and an instruction issuance unit 16. These functional blocks are implemented by the cooperation of hardware resources such as a processor of 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 and location of the computer, the above-mentioned functional blocks can be implemented by the hardware resources of a single computer, or by combining the hardware resources distributed in a plurality of computers. In particular, in the present embodiment, part or all of the functional blocks of the radio access network control device 1 can be implemented by a processor provided in an SMO and / or a Non-RT RIC, or can be implemented in a distributed or centralized manner by a computer or a processor provided outside the SMO and / or the Non-RT RIC.
[0038] The O1 information acquisition unit included in the O1 / O2 information acquisition unit 11 acquires O1 information related to at least one of the Near-RT RIC and the E2 node (RAN node) from the O1 interface. Specifically, the O1 information acquisition unit is set in the SMO and / or the Non-RT RIC, and acquires the O1 information from the Near-RT RIC and / or the E2 node through the O1 interface. As the O1 information, various control information indicating the control state of the Near-RT RIC and operation data specifically measured for each E2 node are exemplified. The operation data of each E2 node is various data that can be detected by a general mobile communication base station, such as the communication volume per hour, the communication speed, the number and category of the connected UE (communicator), the strength and mode of the communication radio wave from the UE, the quality of the channel between the UE and the O-RU, the coverage of the communication cell provided by the O-RU, the available frequency band, the performance and status of the hardware of the E2 node and the O-RU, etc. are exemplified. In this way, the O1 information acquisition unit constitutes an operation data acquisition unit, which acquires the operation data measured from the RAN node.
[0039] Figure 4The O1 information acquisition unit in the is schematically shown in a manner that it spans inside and outside the Non-RT frame on the main bus MB. However, the whole or part of the O1 information acquisition unit only needs to be set in the SMO framework outside the Non-RT frame. In addition, the O1 information acquisition unit only needs to be able to access the relevant functional blocks in the SMO, specifically the O1 terminal, O1 related functions, O1 / O2 information providing unit 12 (especially the O1 information providing unit), policy / conflict management function (especially the instruction verification unit 15), R1 terminal, rApp (operation guide generation unit 13 and / or structure change instruction generation unit 14), etc., and it does not need to be directly connected to the main bus MB. Preferably, part or all of the functions of the O1 information acquisition unit are implemented in the O1 related functions in the SMO framework (outside the Non-RT framework) with the highest correlation among these related functional blocks.
[0040] The O2 information acquisition unit included in the O1 / O2 information acquisition unit 11 constitutes a virtualized infrastructure information acquisition unit, which acquires O2 information as virtualized infrastructure information related to O-Cloud from the O2 interface. Specifically, the O2 information acquisition unit is set in the SMO and / or the Non-RT RIC, and acquires O2 information from the O-Cloud through the O2 interface. As O2 information, information related to the structure and telemetry of the O-Cloud and / or the failure and operating status of each E2 node (each RAN node) virtually managed by the O-Cloud are exemplified. As the operating status of each E2 node, the resource usage and communication load status in each E2 node are exemplified. These O2 information can be, for example, obtained from the IMS in the O-Cloud by the FOCOM in the SMO through the O2ims interface, or obtained from the O-Cloud by the OAM function in the SMO through the O2 interface. In this way, the O2 information acquisition unit constitutes an operating status acquisition unit, which acquires the operating status of the RAN node from the O-Cloud that virtually manages the RAN node.
[0041] Figure 4The O2 information acquisition unit in is schematically shown in a manner that spans inside and outside the Non-RT frame on the main bus MB. However, the whole or part of the O2 information acquisition unit only needs to be set in the SMO framework outside the Non-RT frame. In addition, the O2 information acquisition unit only needs to be able to access the relevant functional blocks in the SMO, specifically, the O2 terminal, O2 related functions, O1 / O2 information providing unit 12 (especially the O2 information providing unit), policy / conflict management function (especially the instruction verification unit 15), R1 terminal, rApp (operation guide generation unit 13 and / or structure change instruction generation unit 14), etc., and it does not need to be directly connected to the main bus MB. Preferably, part or all of the functions of the O2 information acquisition unit are implemented in the O2 related functions in the SMO framework (outside the Non-RT framework) with the highest correlation among these related functional blocks.
[0042] The O1 / O2 information providing unit 12 provides the rApp with the O1 information and / or O2 information acquired by the O1 / O2 information acquiring unit 11 through the R1 interface in the Non-RT RIC. The O2 information providing unit included in the O1 / O2 information providing unit 12 constitutes a virtualization infrastructure information providing unit, which provides the rApp with virtualization infrastructure information (O2 information) through the R1 interface as an interface with the rApp. Figure 4 The O1 / O2 information providing unit 12 is schematically shown on the main bus MB in the Non-RT framework. However, the whole or part of the O1 / O2 information providing unit 12 only needs to be set in the Non-RT framework. In addition, the O1 / O2 information providing unit 12 only needs to be able to access the relevant functional blocks in the SMO, specifically, the O1 / O2 information acquisition unit 11, the policy / conflict management function (especially the instruction verification unit 15), the R1 terminal, the R1 service open function (not shown), the rApp (the operation guide generation unit 13 and / or the structure change instruction generation unit 14), etc., and it does not need to be directly connected to the main bus MB. Preferably, part or all of the functions of the O1 / O2 information providing unit 12 are implemented in the R1 service open function (not shown) in the Non-RT framework with the highest correlation among these related functional blocks.
[0043] The operation guide generation unit 13 implemented by rApp generates an operation guide related to the operation of each RAN node based on the operation status and operation data of each RAN node obtained by the O1 / O2 information acquisition unit 11 and provided by the O1 / O2 information provision unit 12. As the operation guide generated by the operation guide generation unit 13 and issued to the O-Cloud through the O2 interface by the instruction issuance unit 16 described later, a resource allocation guide and / or load management guide related to resource allocation and / or load management of multiple RAN nodes are exemplified. In addition, as the operation guide generated by the operation guide generation unit 13 and issued to the Near-RT RIC and each RAN node through the A1 interface and the O1 interface by the instruction issuance unit 16 described later, a service control guide related to the service control of each RAN node is exemplified.
[0044] The Near-RT RIC receives the operation guide and / or service control guide through the A1 interface, based on the guides, and transmits the guide through the E2 interface ( Figure 1 ) controls each RAN node. For example, when the aforementioned service control guide is a guide for reducing services in a specific RAN node, the Near-RT RIC performs the following processing on the RAN node itself and the UEs in the communication cell provided by the O-RU connected to it: guiding the UEs currently connected to the RAN node to other available RAN nodes, limiting the communication speed and communication volume of the UEs currently connected to the RAN node, limiting the connection of new UEs to the RAN node, and other service restriction processing.
[0045] The operation guide generation unit 13 may also use a machine learning model provided by an artificial intelligence / machine learning workflow function (not shown) to generate an operation guide including the aforementioned resource allocation guide, load management guide, and service control guide. The machine learning model can derive a group of operation guides from a group of failures and operation conditions of multiple RAN nodes and specific operation data for each RAN node. The failures and operation conditions of the multiple RAN nodes are acquired from the O-Cloud via the O2 interface by the O2 information acquisition unit (O1 / O2 information acquisition unit 11) constituting the operation condition acquisition unit, and the specific operation data for each RAN node is acquired via the O1 interface, etc. by the O1 information acquisition unit (O1 / O2 information acquisition unit 11) constituting the operation data acquisition unit. Specifically, the machine learning model is based on machine learning, and outputs a group of operation guidelines, such as resource allocation guidelines, load management guidelines, and service control guidelines issued to each RAN node through the A1 interface and the O1 interface for O-Cloud. The machine learning model is input with a group of operation status from the O2 information acquisition unit (operation status acquisition unit) and operation data from the O1 information acquisition unit (operation data acquisition unit). The machine learning is pre-learning using comprehensive training data or teacher data that establishes an association between input and output.
[0046] Thus, the machine learning model of the present embodiment is a machine learning model that establishes a correspondence between a group of inputs from the O-Cloud (operation status) and inputs from each RAN node (operation data) and a group of outputs for the O-Cloud (resource allocation guide, load management guide, etc.) and outputs for each RAN node (service control guide, etc.). Compared to a simple case where inputs from the O-Cloud are specifically associated with outputs for the O-Cloud, and inputs from each RAN node are specifically associated with outputs for each RAN node, the machine learning model of the present embodiment can comprehensively or comprehensively consider the correlation between inputs and outputs of the O-Cloud and each RAN node, and thus can effectively utilize operation guides for efficiently operating each RAN node from both the O-Cloud and each RAN node perspectives.
[0047] The structure change indication generating unit 14 implemented by rApp generates a structure change indication related to the structure change outside the SMO based on the various O1 information and / or O2 information (including the operation status and operation data of each RAN node mentioned above) acquired by the O1 / O2 information acquiring unit 11 and provided by the O1 / O2 information providing unit 12. The structure change indication generated by the structure change indication generating unit 14 is a structure change indication indicating the change of at least part of the software and / or hardware in the structure outside the SMO in O-RAN, such as O-RU, RAN node, O-Cloud, Near-RT RIC.
[0048] Structural change instructions related to hardware such as O-RU and RAN nodes may include so-called hardware accelerated execution instructions (or stop instructions). Hardware acceleration is a technology that supports general-purpose processors such as CPU (Central Processing Unit) through hardware, and the hardware includes circuits with structures dedicated to specific processing, purposes or customized, such as FPGA (Field-Programmable Gate Array), GPU (Graphics Processing Unit), ASIC (Application Specific Integrated Circuit), DSP (Digital Signal Processor), etc. In software processing performed by a general-purpose processor, even complex processing that requires more time and power can be executed at high speed and efficiently if it is a dedicated processor implemented in hardware.
[0049] The structural change instruction generation unit 14 can also generate structural change instructions using a machine learning model provided by an artificial intelligence / machine learning workflow function (not shown). The machine learning model can derive a group of structural change instructions from a group of various O1 information and / or O2 information, and the group of various O1 information and / or O2 information is obtained by the O1 / O2 information acquisition unit 11 through the O1 interface and / or the O2 interface. Specifically, the machine learning model outputs a group of structural change instructions that are published to the outside of the SMO through the O1 interface, the O2 interface, the A1 interface, etc. based on machine learning. The machine learning model inputs various O1 information and groups of O2 information from the O1 / O2 information acquisition unit 11, and the machine learning is pre-learned using comprehensive training data or teacher data that associates input and output. The machine learning model is a machine learning model that establishes a correspondence between a group of inputs (O1 information and O2 information) from outside the SMO and a group of outputs (structural change instructions) to outside the SMO.
[0050] As described above, the Non-RT RIC set in the SMO generates various instructions (especially operation guides and structural change instructions) to the RAN nodes, O-Cloud, Near-RT RIC, etc. outside the SMO through the execution of rApp. These instructions are released to the outside of the SMO through various interfaces such as the O1 interface, the O2 interface, and the A1 interface. In the existing SMO, regardless of the object (RAN node, O-Cloud, Near-RT RIC, etc.) and the interface (O1 interface, O2 interface, A1 interface, etc.), the instructions generated by the rApp are almost released to the outside of the SMO as is. Therefore, there is a risk that rApps that perform different tasks and operations will release contradictory instructions to the outside of the SMO, and the resources of the SMO itself and the outside of the SMO are wasted for their execution, resolution, adjustment, etc. According to the radio access network control device 1 (especially the instruction verification unit 15 and the instruction issuing unit 16) involved in the present embodiment described below, the instructions generated by the rApp can be efficiently released to the outside of the SMO.
[0051] The instruction verification unit 15 provided in the SMO verifies the instructions to the outside of the SMO generated by the rApp executed by the Non-RT RIC in the SMO. Specifically, the instruction verification unit 15 verifies the operation guide related to the operation of the RAN node generated by the operation guide generation unit 13 in the rApp and the structure change instruction related to the structure change outside the SMO generated by the structure change instruction generation unit 14 in the rApp. For example, the instruction verification unit 15 implements at least one of the priority allocation processing, the release scheduling processing, the cancellation processing, and the change processing for each instruction (each operation guide and each structure change instruction) generated by the rApp. The priority allocation processing is the processing of assigning priorities to multiple instructions generated by the rApp. The release scheduling processing is the processing of specifying the release timing performed by the instruction issuing unit 16 for each instruction generated by the rApp. The cancellation processing is the processing of canceling the instructions generated by the rApp that are inconsistent or conflicting with other instructions, and the instructions that have the risk of deteriorating the performance and efficiency of the O-RAN. The change processing is the processing of applying various changes to the instructions generated by the rApp that will become the object of the cancellation processing if they remain as they are. In addition, the rApp may perform the change process on behalf of the instruction verification unit 15 for the instruction recognized as a target of the cancellation process by the instruction verification unit 15 .
[0052] The instruction verification unit 15 is set at any position in the SMO in a manner that enables access to instructions (operation guides and structural change instructions) generated by the rApp. However, in order to efficiently access substantially all instructions generated by the rApp, at least a portion of the instruction verification unit 15 is preferably set in the Non-RT RIC, and more preferably in the R1 interface that is an interface with the rApp. For example, it is preferred that at least a portion of the instruction verification unit 15 is set in an R1 terminal that is a terminal of the R1 interface that constitutes the API of the rApp, or an R1 service open function (not shown) that is provided in conjunction with the R1 terminal.
[0053] The instruction issuing unit 16 provided in the SMO issues the instruction of the rApp verified by the instruction verifying unit 15 to the outside of the SMO. Specifically, the instruction issuing unit 16 issues the operation guide related to the operation of the RAN node generated by the operation guide generating unit 13 in the rApp and the configuration change instruction verified by the instruction verifying unit 15 among the configuration change instructions related to the configuration change outside the SMO generated by the configuration change instruction generating unit 14 in the rApp to the outside of the SMO.
[0054] The instruction issuing unit 16 issues the operation guide verified by the instruction verification unit 15 to at least any one of the RAN node, the O-Cloud that virtually manages the RAN node, and the Near-RT RIC. Specifically, the instruction issuing unit 16 issues the operation guide verified by the instruction verification unit 15 to the Near-RTRIC through the A1 interface, issues the operation guide verified by the instruction verification unit 15 to the O-Cloud through the O2 interface, and issues the operation guide verified by the instruction verification unit 15 to the RAN node and the O-RU through the O1 interface and the OpenFronthaul M-Plane. In addition, the instruction issuing unit 16 issues the structural change instruction verified by the instruction verification unit 15 to at least any one of the RAN node, the O-Cloud that virtually manages the RAN node, and the Near-RT RIC. Specifically, the indication issuing unit 16 issues the structural change indication verified by the indication verification unit 15 to the O-Cloud through the O2 interface, and issues the structural change indication verified by the indication verification unit 15 to the RAN node, O-RU, Near-RT RIC, etc. through the O1 interface, open fronthaul M-Plane, A1 interface, etc.
[0055] For instructions that are processed by the instruction verification unit 15 to implement priority allocation, the instruction publishing unit 16 publishes the instructions outside the SMO according to the assigned priority. Therefore, important instructions with high priority, urgency, applicable frequency, and impact are preferentially published outside the SMO (in addition, instructions with high applicable frequency and impact require careful verification, so the priority can be lowered in turn). In addition, for instructions that are processed by the instruction verification unit 15 to implement release scheduling, the instruction publishing unit 16 publishes the instructions outside the SMO according to the specified schedule and / or release timing. In this way, by appropriately determining the release order and release timing of rApp instructions according to the conditions of O-RAN (especially outside the SMO), the performance and efficiency of O-RAN can be improved.
[0056] In addition, the instruction issuing unit 16 does not issue instructions for canceling the instructions by the instruction verification unit 15 to the outside of the SMO. In addition, for instructions for changing the instructions by the instruction verification unit 15 and / or the rApp, the instruction issuing unit 16 issues the instructions with changes to the outside of the SMO according to the priority and schedule. Therefore, it is possible to effectively prevent instructions generated by the rApp from being issued as is to the outside of the SMO that are inconsistent or conflicting with other instructions or that have the risk of deteriorating the performance and efficiency of the O-RAN.
[0057] The instruction issuing unit 16 is set at any position in the SMO so that the instruction verifying unit 15 can access the A1 interface, O1 interface, and O2 interface as the instruction issuing position to the outside of the SMO, and the instruction verifying unit 15 can obtain the verification result of the instruction of the rApp. However, in order to quickly issue instructions to the outside of the SMO, it is preferred that at least a part of the instruction issuing unit 16 is set at at least any one of the A1 interface, O1 interface, and O2 interface as the interface to the outside of the SMO. For example, the functions in the instruction issuing unit 16 related to the issuance of operation guides, etc. through the A1 interface are preferably set in the A1 terminal which is the terminal of the A1 interface, and the A1-related functions provided with the A1 terminal. The functions in the instruction issuing unit 16 related to the issuance of structural change instructions, etc. through the O1 interface are preferably set in the O1 terminal which is the terminal of the O1 interface, and the O1-related functions provided with the O1 terminal. The functions in the instruction issuing unit 16 related to the issuance of structural change instructions, etc. through the O2 interface are preferably set in the O2 terminal which is the terminal of the O2 interface, and the O2-related functions provided with the O2 terminal.
[0058] As described above, the instruction issuing unit 16 issues various instructions (operation guides, structural change instructions, etc.) generated by rApp for various structures outside the SMO (O-RU, RAN node, O-Cloud, Near-RT RIC, etc.) through various interfaces (A1 interface, O1 interface, O2 interface, etc.). Therefore, the relevant functions of the instruction issuing unit 16 are efficiently installed in a distributed manner on each interface that serves as the location for issuing instructions outside the SMO. Similarly, by also installing the relevant functions of the instruction verification unit 15 in a distributed manner on each interface (A1 interface, O1 interface, O2 interface, etc.), the policy / conflict management functions including the instruction verification unit 15 and the instruction issuing unit 16 can be optimized for each interface that serves as the location for issuing instructions outside the SMO.
[0059] For example, regarding the A1 interface that is mainly responsible for issuing an operation guide for the Near-RT RIC, the function of the instruction verification unit 15 that verifies the operation guide for the Near-RT RIC generated by the operation guide generation unit 13 is set in the A1 terminal and the A1 related functions, and the function of the instruction issuance unit 16 that issues the verified operation guide for the Near-RT RIC through the A1 interface is set in the A1 terminal and the A1 related functions. Similarly, regarding the O1 interface that is mainly responsible for issuing a structure change instruction for the RAN node, the function of the instruction verification unit 15 that verifies the structure change instruction for the RAN node generated by the structure change instruction generation unit 14 is set in the O1 terminal and the O1 related functions, and the function of the instruction issuance unit 16 that issues the verified structure change instruction for the RAN node through the O1 interface is set in the O1 terminal and the O1 related functions. In addition, regarding the O2 interface that is mainly responsible for issuing structural change instructions to O-Cloud, the function of verifying the structural change instructions for O-Cloud generated by the structural change instruction generation unit 14 in the indication verification unit 15 is set in the O2 terminal and O2 related functions, and the function of issuing the verified structural change instructions to O-Cloud through the O2 interface in the indication issuing unit 16 is set in the O2 terminal and O2 related functions.
[0060] In addition, similar to the operation guide generation unit 13 and / or the structure change instruction generation unit 14, the above instruction verification unit 15 and / or instruction issuing unit 16 can also utilize the artificial intelligence / machine learning workflow function in SMO ( Figure 3) to verify and / or publish the instructions of the rApp. In addition, when the same function as the artificial intelligence / machine learning workflow function is also set in the Near-RT RIC, by setting part of the functions of the instruction verification unit 15 and / or the instruction publishing unit 16 in the Near-RT RIC, the verification and / or publication of the instructions of the rApp can be performed more efficiently based on the information available in the Near-RT RIC (for example, the actions started by the Near-RT RIC for each RAN node) and the machine learning model. Alternatively, various data generated by the machine learning model in the Near-RT RIC can be provided or aggregated to the instruction verification unit 15 and / or the instruction publishing unit 16 in the SMO through the O1 interface and the A1 interface, thereby uniformly verifying and / or publishing the instructions of the rApp in the SMO.
[0061] According to the above embodiment, before the instruction issuing unit 16 provided in the SMO issues the instructions of the rApp to the outside of the SMO, the instruction verification unit 15 provided in the SMO uniformly verifies the instructions. Therefore, among the instructions generated by the rApp, the instructions verified by the instruction verification unit 15 are efficiently issued by the instruction issuing unit 16 to the outside of the SMO.
[0062] The present disclosure has been described above based on the embodiments. It is obvious to those skilled in the art that various modifications may be made in the combinations of the constituent elements and processes in the embodiments as examples, and such modifications are included in the scope of the present disclosure.
[0063] In addition, the structures, functions, and features of each device and method described in the embodiments can be implemented by hardware resources or software resources, or by the collaboration of hardware resources and software resources. As hardware resources, for example, a processor, ROM (read-only memory), RAM (random access memory), and various integrated circuits can be used. As software resources, for example, programs such as operating systems and applications can be used.
[0064] The present disclosure can be expressed as the following items.
[0065] Project 1:
[0066] A radio access network control device comprises at least one processor, wherein the at least one processor executes:
[0067] An instruction verification unit of an SMO (Service Management and Orchestration) provided in O-RAN verifies an instruction to the outside of the SMO generated by an rApp executed by a Non-RT RIC (Non-Real Time RAN Intelligent Controller) in the SMO; and
[0068] The instruction issuing unit provided in the SMO issues the verified instruction to outside the SMO.
[0069] Project 2:
[0070] The radio access network control device according to item 1,
[0071] the instruction verification unit verifies the operation guide related to the operation of the radio access network node generated by the rApp,
[0072] The instruction issuing unit issues the verified operation guide to at least any one of the radio access network node, a virtualized infrastructure that virtually manages the radio access network node, and a Near-RT RIC (Near-Real Time RAN Intelligent Controller).
[0073] Project Three:
[0074] The radio access network control device according to item 1 or 2,
[0075] the instruction verification unit verifies the structure change instruction generated by the rApp and related to the structure change outside the SMO,
[0076] The instruction issuing unit issues the verified configuration change instruction to at least any one of a radio access network node, a virtualized infrastructure that virtually manages the radio access network node, and a Near-RT RIC (Near-Real Time RAN Intelligent Controller).
[0077] Project 4:
[0078] The radio access network control device according to item 2,
[0079] the instruction verification unit verifies the structural change instruction generated by the rApp and related to the structural change outside the SMO together with the operation manual,
[0080] The instruction issuing unit issues the verified operation guide and / or the structure change instruction to at least any one of the radio access network node, the virtualized infrastructure, and the Near-RTRIC.
[0081] Project Five:
[0082] According to the radio access network control device described in any one of items 1 to 4, the instruction verification unit performs at least any one of priority allocation processing, release scheduling processing, cancellation processing, and change processing on the instruction generated by the rApp.
[0083] Project 6:
[0084] According to the radio access network control device described in any one of items 1 to 5, at least a part of the instruction verification unit is set in the Non-RT RIC.
[0085] Project 7:
[0086] According to the radio access network control device of item 6, at least a part of the instruction verification unit is provided in an R1 interface which is an interface with the rApp.
[0087] Project Eight:
[0088] According to the radio access network control device described in any one of items 1 to 7, at least a part of the aforementioned instruction issuing unit is connected to at least any one of the A1 interface, O1 interface, and O2 interface which are interfaces provided outside the aforementioned SMO.
[0089] Project Nine:
[0090] The radio access network control device according to any one of items 1 to 8,
[0091] The at least one processor executes:
[0092] acquiring, by a virtualized infrastructure information acquisition unit, virtualized infrastructure information from a virtualized infrastructure that virtually manages the radio access network node; and
[0093] The virtualization infrastructure information providing unit provides the virtualization infrastructure information to the rApp via the R1 interface which is an interface with the rApp.
[0094] The instruction verification unit verifies the instruction generated by the rApp based on the virtualization infrastructure information.
[0095] Project 10:
[0096] The radio access network control device according to any one of items 1 to 9,
[0097] The at least one processor executes:
[0098] The operating status acquisition unit acquires the operating status of the radio access network node from a virtualized infrastructure that virtually manages the radio access network node.
[0099] The operation data acquisition unit acquires the operation data measured from the radio access network node; and
[0100] generating an operation guide related to the operation of the radio access network node based on the operation status and the operation data by the operation guide generating unit through the rApp;
[0101] The instruction verification unit verifies the operation guide.
[0102] Project 11:
[0103] A radio access network control method, comprising:
[0104] At the O-RAN Service Management and Orchestration (SMO), verifying the indication to the outside of the SMO generated by the rApp executed by the Non-RT RIC (Non-Real Time RAN Intelligent Controller) in the SMO; and
[0105] At the aforementioned SMO, the verified aforementioned indication is issued outside the aforementioned SMO.
[0106] Project 12:
[0107] A storage medium stores a radio access network control program, wherein the radio access network control program causes a computer to execute:
[0108] At the O-RAN Service Management and Orchestration (SMO), verifying the indication to the outside of the SMO generated by the rApp executed by the Non-RT RIC (Non-Real Time RAN Intelligent Controller) in the SMO; and
[0109] At the aforementioned SMO, the verified aforementioned indication is issued outside the aforementioned SMO.
[0110] Industrial Applicability
[0111] The present disclosure relates to verification of rApp indication in SMO of O-RAN.
[0112] Reference numerals
[0113] 1 radio access network control device, 11 O1 / O2 information acquisition unit, 12 O1 / O2 information provision unit, 13 operation guide generation unit, 14 configuration change instruction generation unit, 15 instruction verification unit, 16 instruction issuance unit.
Claims
1. A radio access network control device, comprising at least one processor, wherein the at least one processor executes: An indication verification unit provided in a service management and orchestration (SMO) of the O-RAN verifies an indication to the outside of the SMO generated by a rApp executed by a non-real-time RAN intelligent controller (Non-RT RIC) in the SMO; and The verified instruction is issued to the outside of the SMO by an instruction issuing unit provided in the SMO.
2. The radio access network control device according to claim 1, The instruction verification unit verifies the operation guide generated by the rApp and related to the operation of the radio access network node. The instruction issuing unit issues the verified operation guide to at least any one of the radio access network node, a virtualized infrastructure that virtually manages the radio access network node, and a near real-time RAN intelligent controller (Near-RT RIC).
3. The radio access network control device according to claim 1, The instruction verification unit verifies the structure change instruction generated by the rApp and related to the structure change outside the SMO, The instruction issuing unit issues the verified configuration change instruction to at least any one of a radio access network node, a virtualized infrastructure that virtually manages the radio access network node, and a near real-time RAN intelligent controller (Near-RT RIC).
4. The radio access network control device according to claim 2, The instruction verification unit verifies the structure change instruction generated by the rApp and related to the structure change outside the SMO together with the operation manual, The instruction issuing unit issues the verified operation guide and / or the structure change instruction to at least any one of the radio access network node, the virtualization infrastructure, and the Near-RT RIC. 5 . The radio access network control device according to claim 1 , wherein the instruction verification unit performs at least any one of a priority assignment process, a release scheduling process, a cancellation process, and a change process on the instruction generated by the rApp. 6 . The radio access network control device according to claim 1 , wherein at least a part of the instruction verification unit is provided in the Non-RT RIC. 7 . The radio access network control device according to claim 6 , wherein at least a part of the instruction verification unit is provided in an R1 interface which is an interface with the rApp.
8. The radio access network control device according to claim 1, wherein at least a part of the instruction issuing unit is provided in at least any one of an A1 interface, an O1 interface, and an O2 interface which are interfaces with the outside of the SMO.
9. The radio access network control device according to claim 1, The at least one processor executes: acquiring, by a virtualized infrastructure information acquisition unit, virtualized infrastructure information from a virtualized infrastructure that virtually manages the radio access network node; and The virtualization infrastructure information providing unit provides the virtualization infrastructure information to the rApp through the R1 interface which is an interface with the rApp. The instruction verification unit verifies the instruction generated by the rApp based on the virtualization infrastructure information.
10. The radio access network control device according to claim 1, The at least one processor executes: Acquiring, by an operating status acquisition unit, an operating status of the radio access network node from a virtualized infrastructure that virtually manages the radio access network node; Acquiring, by an operation data acquisition unit, operation data measured from the radio access network node; as well as generating, by the rApp-based operation guide generating unit, an operation guide related to the operation of the radio access network node based on the operation status and the operation data, The instruction verification unit verifies the operation manual.
11. A radio access network control method, comprising: At a Service Management and Orchestration (SMO) of the O-RAN, verifying an indication out of the SMO generated by a rApp executed by a Non-Real-Time RAN Intelligent Controller (Non-RT RIC) in the SMO; as well as At the SMO, the verified indication is published outside the SMO.
12. A storage medium storing a radio access network control program, wherein the radio access network control program causes a computer to execute: At a Service Management and Orchestration (SMO) of the O-RAN, verifying an indication out of the SMO generated by a rApp executed by a Non-Real-Time RAN Intelligent Controller (Non-RT RIC) in the SMO; and At the SMO, the verified indication is published outside the SMO.
Citation Information
Patent Citations
Control device, control method, and program
JP2021083058A
