Apparatus and method for implementing an R1 - O1 data model for O1 - related services within a communication network

Abstract

An apparatus for a Non-Real-Time Radio Access Network Intelligence Controller (NRT-RIC) framework in O-RAN, comprising a memory storing instructions, and at least one processor configured to implement the NRT-RIC framework of the NRT-RIC by executing the instructions to: receive a first request from an rApp, the first request for obtaining a configuration schema of a network element in O-RAN, the first request comprising a first R1-O1 Configuration Management (CM) data model for identifying the network element, the first request being received via an R1 interface; send a first response to the requested configuration schema, the first response identifying a Configuration Management (CM) attribute of the network element and comprising a second R1-O1 CM data model for identifying the network element, the first response being sent from the NRT-RIC framework; wherein the R1 interface enables the NRT-RIC framework and the rApp to generate and consume at least one O1 interface-related R1 service in the NRT-RIC.

Description

Technical Field

[0001] [Cross - Reference to Related Applications] This application claims priority based on U.S. Provisional Patent Application No. 63 / 413,392, filed on October 5, 2022, the entire disclosure of which is incorporated herein by reference.

[0002] [Technical Field] Apparatuses and methods consistent with embodiments of the present disclosure relate to an R1 - O1 data model for configuration management (CM) of at least one network element in an Open Radio Access Network (O - RAN), implemented in a Non - Real - Time Radio Access Network Intelligence Controller (NRT - RIC) framework within a Service Management and Orchestration (SMO) framework of a communication network.

Background Art

[0003] A Radio Access Network (RAN) is an important component in a communication system that connects end - user devices (or user equipment) to other parts of the network. The RAN includes a combination of various network elements (NEs) that connect end - user devices to the core network. Conventionally, the hardware and / or software of a specific RAN was vendor - specific.

[0004] With the emergence of Open Radio Access Network (O-RAN) technology, multiple vendors can provide hardware and / or software for communication systems. For this purpose, O-RAN decomposes RAN functions into a Centralized Unit (CU), a Distributed Unit (DU), and a Radio Unit (RU). The CU is a logical node for hosting the RAN sublayers of Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and / or Packet Data Convergence Protocol (PDCP). The DU is a logical node for hosting the RAN sublayers of Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY). The RU is a physical node that converts radio signals from the antenna into digital signals that can be transmitted to the DU over the fronthaul. Since these entities have open protocols and interfaces between them, they can be developed by different vendors.

[0005] Figure 1 illustrates the O-RAN architecture in the related art. Referring to Figure 1, the RAN functions in the O-RAN architecture are controlled and optimized by the RIC.

[0006] The RIC is a software-defined component that implements modular applications to achieve the multi-vendor operability required in the O-RAN system and to automate and optimize RAN operations. The RIC is divided into two types: Non-Real-Time RIC (NRT-RIC) and Near-Real-Time RIC (nRT-RIC).

[0007] The NRT-RIC is a control point for non-real-time control loops and operates on a time scale longer than 1 second within the Service Management and Orchestration (SMO) framework. Its functions are implemented through modular applications called rApps (rApp 1, …, rApp N), and include providing policy-based guidance and enrichment across the A1 interface, which is the interface enabling communication between the NRT-RIC and the nRT-RIC, performing data analytics, AI / ML training and inference for RAN optimization, and / or recommending configuration management actions on the O1 interface, which is the interface connecting the SMO to RAN management elements (e.g., nRT-RIC, O-RAN Centralized Unit (O-CU), O-RAN Distributed Unit (O-DU), etc.).

[0008] The nRT-RIC operates on time scales between 10 milliseconds and 1 second and connects via the E2 interface to the O-DU, O-CU (which is decomposed into an O-CU control plane (O-CU-CP) and an O-CU user plane (O-CU-UP)), and the open evolved NodeB (O-eNB). The nRT-RIC uses the E2 interface to control the underlying RAN elements (E2 nodes / network functions (NFs)) on a near-real-time control loop. The nRT-RIC monitors, suspends / stops, overrides, and controls the E2 nodes (O-CU, O-DU, and O-eNB) via policies. For example, nRT sets policy parameters on the functions activated in the E2 nodes. Further, the nRT-RIC hosts xApps for implementing functions such as quality of service (QoS) optimization, mobility optimization, slicing optimization, interference mitigation, load balancing, security, etc. Two types of RICs cooperate to optimize O-RAN. For example, the NRT-RIC provides the policies, data, and AI / ML models enabled and used by the nRT-RIC for RAN optimization on the A1 interface, and the nRT returns policy feedback (i.e., how the policies set by the NRT-RIC work).

[0009] The SMO framework in which the NRT-RIC is located manages and coordinates the RAN elements. Specifically, the SMO manages and coordinates what is represented as the O-RAN cloud (O-Cloud). The O-Cloud is a set of physical RAN nodes that host the RIC, O-CU, and O-DU, support software components (e.g., operating systems and runtime environments), and the SMO itself. In other words, the SMO manages the O-Cloud from within. The O2 interface is the interface between the SMO and the O-Cloud in which it resides. The SMO provides infrastructure management services (IMS) and deployment management services (DMS) via the O2 interface.

[0010] On the one hand, O-Cloud is a cloud computing platform comprising a set of physical infrastructure nodes that meet the O-RAN specifications for hosting related O-RAN functions (nRT-RIC, O-CU-CP, O-CU-UP, O-DU, etc.), support software components (operating system, virtual machine monitor, container runtime, etc.), and appropriate management and orchestration functions.

[0011] The SMO framework where the NRT-RIC is located manages and coordinates RAN elements. SMO performs these services (i.e., management and orchestration of RAN elements) for O-RAN elements through four key interfaces (A1 interface for RAN optimization between NRT-RIC and nRT-RIC in SMO; O1 interface for FCAPS support between SMO and O-RAN network functions; open front-haul M plane interface for FCAPS support between SMO and O-RU in the case of a hybrid model; O2 interface for platform resource and workload management between SMO and O-Cloud).

Summary of the Invention

Problems to be Solved by the Invention

[0012] According to an embodiment, there is provided an apparatus and a method for implementing a Non-Real-Time Radio Access Network Intelligent Controller (NRT-RIC) that transmits a plurality of requests and responses thereto, including a plurality of R1-O1 CM data models for at least one network element in an Open Radio Access Network (O-RAN). In particular, the apparatus and method are implemented in a Non-Real-Time Radio Access Network Intelligence Controller (NRT-RIC) framework of the NRT-RIC within a Service Management and Orchestration (SMO) framework of a communication network. The apparatus and method enable the NRT-RIC platform to communicate with at least one network element in the O-RAN based on an R1-O1 CM data model specified via an R1 interface. In particular, the specified R1-O1 CM data model includes first and second R1-O1 CM data models for obtaining a CM data schema of at least one network element, third and fourth R1-O1 CM data models for reading CM data from at least one network element, and fifth and sixth R1-O1 data models for writing CM data to at least one network element. The plurality of R1-O1 CM data models enable a network operator to effectively manage (standardize) rApp applications from a plurality of vendors in order to define specifications for the NRT-RIC platform.

Means for Solving the Problems

[0013] According to one embodiment, an apparatus for an Open Radio Access Network (O-RAN) Non-Real-Time Radio Access Network Intelligence Controller (NRT-RIC) framework is provided. The apparatus includes a memory storing instructions, and at least one processor configured to implement the NRT-RIC framework of the NRT-RIC by executing the instructions to: receive a first request from a memory storing instructions and an rApp hosted by the NRT-RIC, the first request being for obtaining a configuration schema of at least one network element in the O-RAN, the first request including a first R1-O1 Configuration Management (CM) data model identifying the at least one network element and being received via an R1 interface between the rApp and the NRT-RIC framework within the O-RAN architecture; and transmit, via the R1 interface, a first response to the requested configuration schema to the rApp from the NRT-RIC framework, the first response including a second R1-O1 CM data model identifying the at least one network element and identifying at least one CM attribute of the at least one network element. The R1 interface enables the NRT-RIC framework and the rApp to generate and consume at least one O1 interface-related R1 service in the NRT-RIC.

[0014] The first R1-O1 CM data model may include a message type parameter identifying the type of the first request and at least one network element parameter including a network element identifier (ID).

[0015] The second R1-O1 CM data model may include a message type parameter identifying the type of the first response and a supported Information Object Class (IOC) entity parameter including one or more related entity items identifying one or more CM attributes for each of the at least one network element.

[0016] At least one processor may be further configured to execute instructions to receive, from the rApp, a second request for reading configuration data of one CM attribute among at least one CM attribute specified in the first response, the second request being received via the R1 interface and including a 3R1 - O1 CM data model for specifying a network element and the CM attribute; and transmit, via the R1 interface, a second response including a 4R1 - O1 CM data model for specifying a CM attribute corresponding to the second request, from the NRT - RIC framework to the rApp.

[0017] The 3R1 - O1 CM data model may include a message type parameter for specifying the type of the second request, an rApp identifier (ID) for specifying the rApp, a request identifier (ID) for the second request, a network element parameter including a network element ID of the network element, and a first name - inclusive IOC entity parameter including a first related entity item for specifying an IOC entity name and the CM attribute.

[0018] The 4R1 - O1 CM data model may include a message type parameter for specifying the type of the second response, an rApp ID for specifying the rApp, a network element parameter including a network element identifier (ID), and a second name - inclusive IOC entity parameter including a second related entity item for specifying an IOC entity name and the CM attribute.

[0019] The second related entity item may further include a CM attribute value for specifying a value of the CM attribute.

[0020] At least one processor may be further configured to execute instructions to receive, from the rApp, a third request for writing configuration data of one of at least one CM attribute, the third request being received via the R1 interface and comprising a 5R1-O1 CM data model that identifies a network element and the CM attribute; and transmit, via the R1 interface, to the rApp from the NRT-RIC framework, a third response comprising a 6R1-O1 CM data model for identifying the CM attribute changed in response to the third request.

[0021] The 5R1-O1 CM data model may include a message type parameter that identifies the type of the third request, an rApp ID that identifies the rApp, a network element parameter that includes a network element identifier (ID) of the network element, and a third name-including IOC entity parameter that includes an IOC entity name and a third related entity item that identifies the CM attribute changed in response to the third request.

[0022] The 6R1-O1 CM data model may include a message type parameter that identifies the type of the third response, an rApp ID, a network element parameter that includes a network element identifier (ID), an attribute status that verifies a configuration status, and a fourth name-including IOC entity parameter that includes an IOC entity name and a fourth related entity item that identifies the CM attribute and the status of the writing.

[0023] Based on the writing being not permitted, the fourth related entity item may further include a cause parameter that identifies the cause for the writing being not permitted.

[0024] According to one embodiment, a method for an Open Radio Access Network (O-RAN) Non-Real-Time Radio Access Network Intelligence Controller (NRT-RIC) framework is provided. The method includes receiving, at an NRT-RIC, a first request from an rApp hosted by the NRT-RIC, the first request being for obtaining a configuration schema of at least one network element in the O-RAN, the first request including a first R1-O1 CM data model that identifies at least one network element and being received via an R1 interface between the rApp and the NRT-RIC framework within the O-RAN architecture; and transmitting, via the R1 interface, a first response to the requested configuration schema from the NRT-RIC framework to the rApp, the first response including a second R1-O1 CM data model that identifies at least one network element and that identifies at least one configuration management (CM) attribute of the at least one network element. The R1 interface enables the NRT-RIC framework and the rApp to generate and consume at least one O1 interface-related R1 service at the NRT-RIC.

[0025] The first R1-O1 CM data model may include a message type parameter that identifies the type of the first request and at least one network element parameter that includes a network element identifier (ID).

[0026] The first R1-O1 CM data model may include a message type parameter that identifies the type of the first request and at least one network element parameter that includes a network element identifier (ID).

[0027] The 2R1-O1 CM data model may include a message type parameter that identifies the type of the first response, and a supported information object class (IOC) entity parameter that includes one or more related entity items that identify one or more CM attributes for each of at least one network element.

[0028] The method may further include receiving, from the rApp, a second request for reading configuration data of one CM attribute among at least one CM attribute identified in the first response, the second request comprising a 3R1-O1 CM data model that identifies a network element and a CM attribute, and transmitting, via the R1 interface, a second response comprising a 4R1-O1 CM data model that identifies a CM attribute corresponding to the second request, from the NRT-RIC framework to the rApp.

[0029] The method may further include receiving, from the rApp, a third request for writing configuration data of one CM attribute among at least one CM attribute, the third request comprising a 5R1-O1 CM data model that identifies a network element and a CM attribute, and transmitting, via the R1 interface, a third response comprising a 6R1-O1 CM data model that identifies a CM attribute changed in response to the third request, from the NRT-RIC framework to the rApp.

[0030] According to one embodiment, there is provided a non-transitory computer-readable recording medium having instructions recorded thereon that are executable by at least one processor configured to execute a method for an Open Radio Access Network (O-RAN) Non-Real-Time Radio Access Network Intelligence Controller (NRT-RIC) framework. The method includes receiving, via an R1 interface between an rApp hosted by the NRT-RIC and the NRT-RIC framework in the O-RAN architecture, a first request from the rApp for obtaining a configuration schema of at least one network element in the O-RAN, the first request comprising a first R1-O1 CM data model identifying the at least one network element; and transmitting, via the R1 interface, a first response to the rApp from the NRT-RIC framework for the requested configuration schema, the first response comprising a second R1-O1 CM data model identifying the at least one network element and identifying at least one configuration management (CM) attribute of the at least one network element. The R1 interface enables the NRT-RIC framework and the rApp to generate and consume at least one O1 interface-related R1 service in the NRT-RIC.

[0031] The method may further include receiving, via the R1 interface, a second request from the rApp for reading configuration data of one of the at least one CM attributes identified in the first response, the second request comprising a third R1-O1 CM data model identifying the network element and the CM attribute; and transmitting, via the R1 interface, a second response to the rApp from the NRT-RIC framework, the second response comprising a fourth R1-O1 CM data model identifying the CM attribute corresponding to the second request.

[0032] The method may further include receiving, from the rApp, a third request for writing configuration data of one of at least one CM attribute, the third request comprising a 5R1-O1 CM data model that identifies a network element and the CM attribute, and transmitting, via the R1 interface, to the rApp from the NRT-RIC framework, a third response comprising a 6R1-O1 CM data model for identifying the CM attribute that is changed in response to the third request.

[0033] Additional aspects are presented partially in the following description, become apparent partially from the description, or may be realized by practicing the presented embodiments of the disclosure.

Brief Description of the Drawings

[0034] Features, aspects, and advantages of specific exemplary embodiments of the disclosure are described below with reference to the accompanying drawings in which like reference numerals represent like elements.

[0035] FIG. 1 illustrates an O-RAN architecture in the related art.

[0036] FIG. 2 is a diagram of an example environment in which the systems and / or methods described herein may be implemented.

[0037] FIG. 3 is a diagram of an example of components of a device according to an embodiment.

[0038] FIG. 4 illustrates an NRT-RIC framework within an O-RAN according to an embodiment.

[0039] FIG. 5 illustrates a flow of requests and responses via an R1 interface from the rApp to the NRT-RIC framework of the NRT-RIC, referring to multiple 5R1-O1 CM data models for at least one network element according to an embodiment.

[0040] Figures 6A - 6D depict the first R1 - O1 CM data model of the first request (i.e., the initial message) "CM SCHEMAS REQUEST" and the second R1 - O1 CM data model of the first response "GET CM SCHEMAS RESPONSE" or "GET CM SCHEMAS FAILURE" according to one embodiment.

[0041] Figures 7A - 7C depict the third R1 - O1 CM data model of the second request "GET (READ) CM DATA REQUEST" according to one embodiment.

[0042] Figures 8A - 8C depict the fourth R1 - O1 CM data model of the second response "GET CM DATA REQUEST RESPONSE" or "GET PM DATA REQUEST FAILURE" according to one embodiment.

[0043] Figures 9A - 9C depict the fifth R1 - O1 CM data model of the third request "WRITE CM REQUEST" according to one embodiment.

[0044] Figures 10A - 10C depict the sixth R1 - O1 CM data model of the third response "WRITE CM REQUEST RESPONSE" or "WRITE CM REQUEST FAILURE" according to one embodiment.

[0045] Figure 11 shows an embodiment of the third R1 - O1 CM data model for the second request "GET (READ) CM DATA REQUEST".

DETAILED DESCRIPTION OF THE INVENTION

[0046] The following detailed exemplary embodiments are described with reference to the accompanying drawings. The same reference numerals in different figures may identify the same or similar elements.

[0047] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit implementations to the exact forms disclosed. Changes and modifications are possible in light of the foregoing disclosure or may be obtained from practice of the implementations. Further, one or more features or components of one implementation may be integrated with or combined with those of other implementations (or one or more features of other implementations). Additionally, in the flowcharts and operation descriptions provided below, one or more operations may be omitted, one or more operations may be added, one or more operations may be executed simultaneously (at least in part), and the order of one or more operations may be interchanged.

[0048] It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual special control hardware or software code used to implement these systems and / or methods is not a limitation of the implementation. For this reason, the operations and behavior of the systems and / or methods are described herein without reference to specific software code. It is understood that software and hardware may be designed based on the description herein to implement the systems and / or methods.

[0049] Even if specific combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of possible implementations. In fact, many of these features may be combined in different manners than specifically recited in the claims and / or specifically disclosed in the specification. Each of the dependent claims listed below may depend directly on only one claim, but the disclosure of possible implementations includes each dependent claim in combination with all other claims in the claim group.

[0050] None of the elements, acts, or instructions used herein should be construed as important or essential unless explicitly described. Also, as used herein, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more." If only one item is intended, the term "one" or a similar term is used. Also, as used herein, the terms "has," "have," "having," "include," "including," etc. are intended to be open-ended terms. Further, the phrase "based on" is intended to mean "at least in part, based on" unless explicitly stated otherwise. Further, expressions such as "at least one of A and B" or "at least one of A or B" are understood to include only A, only B, or both A and B.

[0051] Figure 2 is a diagram of an example of an environment 200 in which the systems and / or methods described herein may be implemented. As shown in Figure 2, the environment 200 may include a user device 210, a platform 220, and a network 230. The devices of the environment 200 may be interconnected via a wired connection, a wireless connection, or a combination of wired and wireless connections. In an embodiment, any of the functions and operations described hereinafter with reference to Figures 4-11 may be performed by any combination of the elements illustrated in Figure 2.

[0052] The user device 210 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information related to the platform 220. For example, the user device 210 may include a computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a handheld computer, a smart speaker, a server, etc.), a mobile phone (e.g., a smartphone, a wireless phone, etc.), a wearable device (e.g., smart glasses or a smartwatch), or a similar device. In some implementations, the user device 210 may receive information from the platform 220 and / or transmit information to the platform 220.

[0053] The platform 220 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information. In some implementations, the platform 220 may include a cloud server or a group of cloud servers. In some implementations, the platform 220 may be designed to be modular such that specific software components may be swapped (in or out) according to specific needs. Thus, the platform 220 may be easily and / or quickly reconfigured for different uses.

[0054] In some implementations, as shown, the platform 220 may be hosted in a cloud computing environment 222. Note that the implementations described herein describe the platform 220 as being hosted in the cloud computing environment 222, but in some implementations, the platform 220 may not be cloud-based (i.e., may be implemented outside of a cloud computing environment) or may be partially cloud-based.

[0055] The cloud computing environment 222 includes an environment that hosts the platform 220. The cloud computing environment 222 may provide services that do not require knowledge of the physical location and configuration of the system and / or device that hosts the platform 220, such as computing, software, data access, storage, etc., to an end user (e.g., the user device 210). As shown, the cloud computing environment 222 may include a group of computing resources 224 (collectively referred to as "computing resources 224" and individually referred to as "computing resource 224").

[0056] The computing resources 224 include one or more personal computers, clusters of computing devices, workstation computers, server devices, or other types of computing and / or communication devices. In some implementations, the computing resources 224 may host the platform 220. The cloud resources may include computing instance executed in the computing resources 224, storage devices provided in the computing resources 224, data transfer devices provided by the computing resources 224, etc. In some implementations, the computing resources 224 may communicate with other computing resources 224 via a wired connection, a wireless connection, or a combination of wired and wireless connections.

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

[0058] Application 224-1 includes one or more software applications that may be provided to user device 210 or accessed by user device 210. Application 224-1 may obviate the need to install and execute software applications on user device 210. For example, Application 224-1 may include software associated with platform 220 and / or any other software that may be provided via cloud computing environment 222. In some implementations, one Application 224-1 may communicate information with one or more other Applications 224-1 via virtual machine 224-2.

[0059] Virtual machine 224-2 includes a software implementation of a device (e.g., a computer) that executes programs as if they were physical devices. Virtual machine 224-2 may be a system virtual machine or a process virtual machine, depending on the degree of use by virtual machine 224-2 and correspondence with any actual devices. A system virtual machine may provide a complete system platform that supports the execution of a complete operating system ("OS"). A process virtual machine may execute a single program and may support a single process. In some implementations, virtual machine 224-2 may execute on behalf of a user (e.g., user device 210) and may manage the infrastructure of cloud computing environment 222, such as data management, synchronization, or long-duration data transfers.

[0060] The virtualized storage 224-3 includes one or more storage systems and / or devices of one or more devices or computing resources 224 that use virtualization technology within the storage system. In some implementations, within the context of the storage system, the types of virtualization may include block virtualization and file virtualization. Block virtualization may represent the abstraction (or separation) of logical storage from physical storage so that the storage system may be accessed without considering the physical storage or heterogeneous structure. The separation may provide flexibility to the storage system administrator when managing storage for end users. File virtualization may remove the dependency between the data accessed at the file level and the location where the files are physically stored. This may enable optimization of storage usage, server consolidation, and / or performance of non-disruptive file migration.

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

[0062] Network 230 includes one or more wired and / or wireless networks. For example, network 230 may include a cellular network (e.g., a fifth-generation (5G) network, a long-term evolution (LTE) network, a third-generation (3G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., a Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber-optic-based network, etc., and / or combinations of these or other types of networks.

[0063] The number and arrangement of devices and networks shown in FIG. 2 are provided as an example. In fact, there may be additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or devices and / or networks with different arrangements compared to those shown in FIG. 2. Further, two or more devices shown in FIG. 2 may be implemented within a single device, and a single device shown in FIG. 2 may be implemented as multiple distributed devices. Additionally or alternatively, a set of devices (e.g., one or more devices) in environment 200 may perform one or more functions described as being performed by another set of devices in environment 200.

[0064] FIG. 3 is a diagram of an example of components of device 300. Device 300 may correspond to user device 210 and / or platform 220. As shown in FIG. 3, device 300 may include bus 310, processor 320, memory 330, storage component 340, input component 350, output component 360, and communication interface 370.

[0065] Bus 310 includes components that enable communication between components of device 300. Processor 320 may be implemented in hardware, firmware, or a combination of hardware and software. Processor 320 may be a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or other type of processing component. In some implementations, processor 320 includes one or more programmable processors for executing functions. Memory 330 includes random access memory (RAM), read-only memory (ROM), and / or other types of dynamic or static storage devices (e.g., flash memory, magnetic memory, and / or optical memory) for storing information and / or instructions for use by processor 320.

[0066] The storage component 340 stores information and / or software related to the operation and use of the device 300. For example, the storage component 340, together with the corresponding drive, may include a hard disk (e.g., magnetic disk, optical disk, magneto-optical disk, and / or solid state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or other types of non-transitory computer-readable media. The input component 350 includes components that enable the device 300 to receive information via user input (e.g., touch screen display, keyboard, keypad, mouse, button, switch, and / or microphone), etc. Additionally or alternatively, the input component 350 may include sensors (e.g., global positioning system (GPS) component, accelerometer, gyroscope, and / or actuator) for measuring information. The output component 360 includes components that provide output information from the device 300 (e.g., display, speaker, and / or one or more light emitting diodes (LEDs)).

[0067] The communication interface 370 includes components such as a transceiver (e.g., transceiver and / or separate receiver and transmitter) that enable the device 300 to communicate with other devices via a wired connection, a wireless connection, or a combination of wired and wireless connections, etc. The communication interface 370 enables the device 300 to receive information from other devices and / or provide information to other devices. For example, the communication interface 370 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, etc.

[0068] Device 300 may execute one or more of the processes described herein. Device 300 may execute these processes in response to a processor 320 that executes software instructions stored by a non-transitory computer-readable medium such as a memory 330 and / or a storage component 340. The computer-readable medium is defined herein as a non-transitory memory device. The memory device includes a memory space within a single physical storage device or a memory space distributed across multiple physical storage devices.

[0069] The software instructions may be read into the memory 330 and / or the storage component 340 from another computer-readable medium or from another device via a communication interface 370. When executed, the software instructions stored in the memory 330 and / or the storage component 340 may cause the processor 320 to execute one or more of the processes described herein.

[0070] In addition or alternatively, instead of software instructions or in combination with software instructions, a wired circuit may be used to execute one or more of the processes described herein. Thus, the implementations described herein are not limited to a particular combination of hardware circuits and software.

[0071] The number and arrangement of the components shown in FIG. 3 are provided as an example. In fact, device 300 may include additional components, fewer components, different components, or components in a different arrangement than those shown in FIG. 3. In addition or alternatively, a set of components of device 300 (e.g., one or more components) may execute one or more functions described as being performed by another set of components of device 300.

[0072] In an embodiment, any operation or process of FIGS. 4 to 11 may be implemented by or using any element illustrated in FIGS. 1 to 3.

[0073] FIG. 4 illustrates an NRT-RIC framework (or platform) within an SMO framework system architecture and an rApp for an R1 interface hosted by the NRT-RIC, and O1, O2, and A1 interfaces within O-RAN, according to one embodiment.

[0074] Referring to FIG. 4, the NRT-RIC represents a subset of the functions of the SMO framework. The NRT-RIC can access other SMO framework functions and can affect (i.e., control and / or execute) what is executed across the O1 and O2 interfaces (e.g., performing configuration management (CM) and / or performance management (PM)).

[0075] The NRT-RIC includes an NRT-RIC framework. The NRT-RIC framework includes an R1 service exposer function that handles R1 services provided according to the embodiments, in addition to a plurality of other functions. Generally, the NRT-RIC functions within the NRT-RIC framework support, for the rApp, authorization, authentication, registration, discovery, communication support, etc.

[0076] An NRT-RIC application (rApp) is an application that utilizes functions available in the NRT-RIC framework and / or the SMO framework to provide value-added services related to RAN operation and optimization. The scope of the rApp includes, but is not limited to, wireless resource management, data analytics, etc., and enrichment of information.

[0077] For this purpose, the NRT-RIC framework generates and / or consumes R1 services according to the embodiments via the R1 interface. The R1 interface terminates at the R1 termination of the NRT-RIC framework. The R1 termination connects to the NRT-RIC framework and rApps via the R1 interface and enables the NRT-RIC framework and rApps to exchange messages / data (i.e., requests and responses with data models) in order to access R1 services via the R1 interface.

[0078] Furthermore, the NRT-RIC framework has A1-related functions. The A1-related functions of the NRT-RIC framework support, for example, A1 logical termination, A1 policy coordination and catalog, A1-EI coordination and catalog, etc.

[0079] The data management and exposure services within the NRT-RIC framework deliver data generated or collected by a data generator to a data consumer according to needs (e.g., function management (FM) / consumption management (CM) / production management (PM) data for rApps or CM changes from rApps to O-RAN via the O1 interface).

[0080] The NRT-RIC framework further has external terminations. The external terminations support, for example, the exchange of data between the NRT-RIC framework and external AI / ML functions, enrichment information (EI) sources, or external oversight.

[0081] Within the NRT-RIC framework, the AI / ML workflow service provides access to the AI / ML workflow. For example, the AI / ML workflow service may assist in model training, monitoring of AI / ML models deployed in NRT-RIC, etc.

[0082] Furthermore, the NRT-RIC framework includes A2-related functions, such as A2 logical termination, A2 policy coordination, and catalog, etc.

[0083] Still referring to FIG. 4, within the NRT-RIC, the R1 interface is an open logical interface within the O-RAN architecture between the rApp and the NRT-RIC framework of the NRT-RIC. The R1 interface supports the exchange of control signaling information and the collection and delivery of data between endpoints. The R1 interface enables, for example, a multi-vendor rApp to consume and / or generate R1 services.

[0084] The R1 interface is independent of the specific implementation of the SMO and the NRT-RIC framework of the NRT-RIC. The R1 interface is defined in an extensible way that allows new services and data types to be added without the need to change the protocol or procedure.

[0085] In particular, the R1 interface enables the interconnection between rApps and NRT-RIC frameworks supplied by different vendors (i.e., enables interconnection in a multi-vendor environment). For this purpose, the R1 interface provides a level of abstraction between the rApp and the NRT-RIC framework and / or the SMO framework.

[0086] In the related art, the definition of the R1-O1 CM data model and data types for O1-related services in the NRT-RIC framework of the NRT-RIC is not specified.

[0087] The framework of R1 interface telemetry data TD according to an embodiment specifies a data model and types. The data model may include an R1 Service Management and Exposure (SME) data model, an R1 Data Management and Exposure (DME) data model, an R1-A1 data model, an R1-O2 data model, an R1-AIML data model, and an R1-O1 data model. The R1-O1 data model may include an O1-CM data model, an O1-NI data model, an O1-PM data model, and an O1-FM data model. Hereinafter, the CM data model according to the embodiment will be described.

[0088] On the other hand, the data types may include an R1-SME data type, an R1-DME data type, an R1-A1 data type, an R1-O2 data type, an R1-AIML data type, and an R1-O1 data type. The R1-O1 data type may include an O1-CM data type, an O1-NI data type, an O1-PM data type, and an O1-FM data type.

[0089] FIG. 5 illustrates a flow of requests and responses via the R1 interface from an rApp to the NRT-RIC framework of the NRT-RIC with reference to multiple R1-O1 CM data models for at least one network element according to an embodiment.

[0090] Referring to FIG. 5, the R1 interface telemetry data TD for O1-related R1 services comprises multiple R1-O1 CM data models for multiple requests and responses.

[0091] In Operation 1, among multiple requests and responses, the rApp hosted by the NRT-RIC sends a first request, "GET CM SCHEMAS REQUEST", for obtaining a configuration schema to the NRT-RIC framework via the R1 interface. The NRT-RIC framework (i.e., the O1-related function of the NRT-RIC framework) obtains the first request and constructs a first R1-O1 CM data model that identifies at least one network element (e.g., CU, DU, etc.) within the O-RAN architecture according to FIG. 1 or 4.

[0092] The first request, "GET CM SCHEMAS REQUEST", is an initial message for requesting the CM schema of the O1-related service from at least one network element in O-RAN. The CM schema may depend on the vendor of the O1-related service or the vendor of at least one network element. For this purpose, based on the first request (i.e., the initial "GET CM SCHEMAS REQUEST"), the rApp requests the NRT-RIC framework to identify the CM schema of at least one network element in O-RAN by identifying at least one CM attribute of at least one network element.

[0093] Based on at least one CM attribute of at least one network element, the rApp identifies the CM schema for at least one network element. For this purpose, the rApp obtains a first response, "GET CM SCHEMAS RESPONSE", for the requested CM schema from the NRT-RIC framework via the R1 interface.

[0094] The first response comprises a second R1-O1 data model that identifies at least one network element and at least one configuration management (CM) attribute of the at least one network element. In particular, the rApp identifies at least one configuration management (CM) attribute based on supported information object class (IOC) entity parameters that include one or more related entity items that identify one or more CM attributes (i.e., identify the CM schema of vendor-dependent O1-related services).

[0095] As a result, the rApp may select the structure (i.e., syntax) of a plurality of R1-O1 CM data models according to the identification of the CM schema of vendor-dependent O1-related services.

[0096] The identification of one or more CM attributes enables the rApp to select the data structure (i.e., syntax) of a plurality of R1-O1 CM data models that fits the data structure (i.e., syntax) of at least one network element.

[0097] As a result, the identification of one or more CM attributes enables the NRT-RIC framework and the rApp to generate and / or consume at least one O1-related R1 service in the NRT-RIC.

[0098] Still referring to Operation 1, in one embodiment, if the "GET CM SCHEMAS REQUEST" fails, the first response may be "GET CM SCHEMAS FAILURE".

[0099] In Operation 2, when the schema for at least one network element is identified, the NRT-RIC framework of the NRT-RIC receives, from the rApp, a second request for reading the configuration data of one of at least one CM attribute. The second request comprises a 3R1-O1 data model that identifies the network element and the CM attribute, and is received via the R1 interface.

[0100] The 3R1-O1 CM data model includes a message type parameter that identifies the type of the second request. For example, the second request is a "GET CM DATA REQUEST" for reading the configuration data of the CM attribute. In response to the second request, the NRT-RIC framework of the NRT-RIC sends a second response "GET CM DATA REQUEST RESPONSE" comprising a 4R1-O1 CM data model. The 4R1-O1 data model identifies the name and / or the value of the CM attribute.

[0101] In one embodiment, the 3R1-O1 CM data model of the second request includes at least one test condition for testing (i.e., comparing the CM attribute according to the test condition) the CM attribute in order to obtain a comparison value (e.g., checking a correct release version, correct maintenance parameters, etc.).

[0102] For this purpose, the 3R1-O1 CM data model of the second request includes an attribute name that identifies the CM attribute. Further, based on the attribute name, the 3R1-O1 CM data model of the second request may comprise at least one test condition for the CM attribute (e.g., the 3R1-O1 CM data model of the second request includes at least one test condition for testing the CM attribute (e.g., checking whether the CM attribute is updated correctly, whether the CM attribute exists, etc.)). For this purpose, in one embodiment, the 3R1-O1 data model may include a comparison parameter and a logical OR parameter. Here, the logical OR parameter may be listed as true or false.

[0103] Referring to Operation 2, in one embodiment, if "GET CM SCHEMAS REQUEST" fails, the second response may be "GET PM DATA REQUEST FAILURE".

[0104] In Operation 3, the NRT-RIC framework of the NRT-RIC receives, from the rApp, a third request "WRITE CM REQUEST" for writing the configuration data of one of at least one CM attribute. The third request "WRITE CM REQUEST" includes a 5R1-O1 CM data model that identifies the network element and the CM attribute, and is received via the R1 interface. In the third request "WRITE CM REQUEST", the CM attribute name and / or CM attribute value for at least one network element within O-RAN may be pushed to the NRT-RIC framework of the NRT-RIC.

[0105] Upon obtaining a third request for writing the configuration data of the CM attribute, the NRT-RIC framework of the NRT-RIC transmits a third response "WRITE CM REQUEST RESPONSE" that includes a 6R1-O1 CM data model for identifying the CM attribute to be changed in response to the third request, to the rApp via the R1 interface (for example, the third response may include a confirmation of the CM attribute name or CM attribute value for confirming the write request). The CM attribute name may be a generic name for the CM attribute. For example, the CM attribute name may be a generic name such as "energy saving control".

[0106] Referring to Operation 3, in one embodiment, if "WRITE CM REQUEST" fails, the third response may be "WRITE CM FAILURE".

[0107] Figures 6A to 6D depict the first R1 - O1 CM data model of the first request (i.e., the initial message) "CM SCHEMAS REQUEST" and the second R1 - O1 CM data model of the first response "GET CM SCHEMAS RESPONSE" or "GET CM SCHEMAS FAILURE" according to an embodiment.

[0108] Referring to Figure 6A, the first request (i.e., the initial message) "CM SCHEMAS REQUEST" includes the first R1 - O1 CM data model for each network element. The first R1 - O1 CM data model includes at least one of the following parameters: message type, a list of network elements with network element items IE (i.e., at least one network element), and element IDs for each of one or more network elements. Here, the presence of the message type and network element ID may be mandatory. In one embodiment, the network element list nests the number <max. of network elements> of network element items each having a network element ID.

[0109] Referring to FIG. 6B, the first response "GET CM SCHEMAS RESPONSE" includes the 2R1-O1 CM data model for each network element. The 2R1-O1 CM data model includes at least one of the following parameters: message type, a list of network elements with network element items IE (i.e., at least one network element), and for each of one or more network elements, an element ID parameter, the IOC type of the network element, a list of related entities, related entity items IE that nest one or more related entities. Here, the presence of the message type, network element ID, and one or more related entities may be mandatory. The presence of the IOC type of the network element parameter may be optional.

[0110] In one embodiment, the list of network elements may comprise <max. of network elements> number of network element items IE. In other embodiments, the related entity item IE may comprise <max. no. of Entities> number of one or more related entities.

[0111] Referring to FIG. 6C, the 2R1-O1 CM data model for each related entity further includes at least one of the following parameters: selected entity type, attribute, attribute name, attribute definition, IOC parameter including supported IOC entities. Here, the presence of the selected entity type, attribute name, and supported IOC entities may be mandatory. The presence of the attribute definition may be optional.

[0112] Referring to FIG. 6D, the second R1-O1 CM data model for each supported IOC entity further includes at least one of the following parameters: IOC name, a list of related entities with related entity item IE (i.e., one or more related entities), and related entity parameters for each of the one or more related entities. Here, the presence of the IOC name and related entity parameters may be optional. In one embodiment, the list of related entities may include a number of related entity items IE <max. of network elements>.

[0113] FIGS. 7A-7C depict the third R1-O1 CM data model "GET (READ) CM DATA REQUEST" of the second request according to one embodiment.

[0114] Referring to FIG. 7A, the second request "GET (READ) CM DATA REQUEST" requests the reading of configuration data of one or more network elements (NEs). The second request includes the third R1-O1 CM data model. The third R1-O1 CM data model includes at least one of the following parameters: message type, rApp ID, request ID, network element ID, managed object instance ID, a list of related entities with related entity item IE (i.e., one or more related entities), and related entity parameter item IE for each of the one or more related entities. Here, the presence of the message type, rApp ID, request ID, network element ID, and one or more related entities may be optional. The presence of the managed object instance ID may also be optional.

[0115] In one embodiment, the list of related entities may include a number of related entity items IE <max. no. of Entities>.

[0116] Referring to FIG. 7B, the 3R1 - O1 CM data model for each of one or more related entities comprises at least one of the following parameters: selected entity type, attribute, attribute name, selected attribute type (i.e., the attribute type based on the selection of an attribute), query attribute based on the selected attribute type, a list of test conditions comprising test condition items IE (i.e., one or more test conditions), and for each of the one or more test conditions, test condition parameters, comparison parameters for the one or more test conditions, comparison value, logical OR combination logic for the comparison, IOC parameter, name inclusion IOC entity. Here, the presence of the selected entity type, attribute, test condition, comparison parameter, and comparison value may be essential. The presence of the selected attribute type and the logical OR combination logic may be optional.

[0117] For example, the test condition may be tested to check the version or configuration status according to the CM attribute for each related entity.

[0118] In one embodiment, the list of test conditions may comprise the number of test condition items IE <max. no. of Test Conditions>. In other embodiments, the logical OR combination logic of the comparison values may be listed as true, false, etc.

[0119] Referring to FIG. 7C, the 3R1 - O1 CM data model for requesting to read the configuration data of one or more name inclusion IOC entities comprises at least one of the following parameters: IOC name, managed object instance ID, a list of related entities comprising related entity items IE (i.e., one or more related entities), and for each of the one or more related entities, related entity parameters. Here, the presence of the IOC name parameter and the one or more related entities may be essential. The managed object instance ID parameter may be optional.

[0120] In one embodiment, a list of related entities may comprise the number <max. of network elements> of one or more related entity items IE.

[0121] Figures 8A - 8C depict the 4R1 - O1 CM data model of the second response "GET CM DATA REQUEST RESPONSE" or "GET PM DATA REQUEST FAILURE" according to one embodiment.

[0122] Referring to Figure 8A, the 4R1 - O1 CM data model of the second response "GET (READ) CM DATA REQUEST RESPONSE" for one or more NEs includes at least one of the following parameters: message type, rApp ID, subscription ID, network element ID, managed object instance ID, a list of related entities comprising one or more related entity items IE (i.e., one or more related entities), and related entity parameters for each of the one or more related entities. Here, the presence of the message type, rApp ID, subscription ID, network element ID, and one or more related entities may be mandatory. The presence of the managed object instance ID data may be optional. According to one or more embodiments, at least the network element ID, the managed object instance ID, and the list of related entities may be included for each of the plurality of network elements.

[0123] In one embodiment, a list of related entity data may comprise the number <max. no. of Entities> of one or more related entity items IE.

[0124] Referring to FIG. 8B, the 4R1-O1 CM data model for one or more related entities comprises at least one of the following parameters: selected entity type, attribute, attribute name, attribute value, IOC parameter, and name-included IOC entity. Here, the existence of the selected entity type, attribute name, and name-included IOC entity may be mandatory. The existence of the attribute value may be optional.

[0125] Referring to FIG. 8C, the 4R1-O1 CM data model for one or more name-included IOC entities comprises at least one of the following parameters: IOC name, managed object instance ID, a list of related entities (i.e., one or more related entities) having a related entity item IE parameter, and related entity parameters for each of the one or more related entities. Here, the existence of the IOC name and one or more related entities may be mandatory. The managed object instance ID may be optional.

[0126] In one embodiment, the list of related entities may comprise a number <max. of network elements> of related entity items IE.

[0127] FIGS. 9A-9C depict the 5R1-O1 CM data model of the 3rd request "WRITE CM REQUEST" according to one embodiment.

[0128] Referring to FIG. 9A, the 5R1-O1 CM data model for one or more NEs includes at least one of the following parameters: message type, rApp ID, subscription ID, network element ID, managed object instance ID, a list of related entities with one or more related entity items IE (i.e., one or more related entities), and related entity parameters for each of the one or more related entities. Here, the presence of the message type, rApp ID, subscription ID, network element ID, and one or more related entities may be mandatory. The presence of the managed object instance ID data may be optional. According to one or more embodiments, at least the network element ID, the managed object instance ID, and the list of related entities may be included for each of the plurality of network elements.

[0129] In one embodiment, the list of related entities may comprise the number <max. no. of Entities> of one or more related entity items IE.

[0130] Referring to FIG. 9B, the 5R1-O1 CM data model for one or more related entities includes at least one of the following parameters: selected entity type, attribute, attribute name, attribute value, and name inclusion IOC entity. Here, the presence of the selected entity type, attribute name, and name inclusion IOC entity may be mandatory. The presence of the attribute value may be optional.

[0131] Referring to FIG. 9C, the 5R1-O1 CM data model for the name-inclusive IOC entity comprises at least one of the following parameters: an IOC name, a managed object instance ID, a list of related entities (i.e., one or more related entities) comprising related entity items IE, and related entity parameters for each of the one or more related entities. Here, the presence of the IOC name parameter and the one or more related entities may be mandatory. The managed object instance ID may be optional. In one embodiment, the list of related entities may comprise a number <max. of network elements> of related entity items IE.

[0132] FIGS. 10A - 10C depict the 6R1-O1 CM data model of the 3rd response "WRITE CM REQUEST RESPONSE" or "WRITE CM REQUEST FAILURE" according to one embodiment.

[0133] Referring to FIG. 10A, the 6R1 - O1 CM data model for the third response "WRITE CM REQUEST RESPONSE" or "WRITE CM REQUEST FAILURE" to write configuration changes for one or more NEs includes at least one of the following parameters: message type, rApp ID, subscription ID, network element ID, managed object instance ID, a list of related entities with one or more related entity item IEs (i.e., one or more related entities), and related entity parameters for each of the one or more related entities. Here, the presence of the message type, rApp ID, subscription ID, network element ID, and one or more related entities may be mandatory. The presence of the managed object instance ID may be optional. According to one or more embodiments, at least the network element ID, the managed object instance ID, and the list of related entities may be included for each of the plurality of network elements.

[0134] In one embodiment, the list of related entities may comprise the number of related entity items IEs <max. no. of Entities>.

[0135] Referring to FIG. 10B, the 6R1 - O1 data model for one or more related entities includes at least one of the following parameters: selected entity type, attribute, attribute name, status (i.e., the status parameter may be a confirmation of the status or a status change), cause (i.e., a description of the cause leading to the status), name - inclusion IOC entity parameter. Here, the presence of the selected entity type, attribute name, and name - inclusion IOC entity may be mandatory. The presence of the cause may be optional.

[0136] Referring to FIG. 10C, the 6R1-O1CM data model for one or more name-inclusive IOC entities comprises at least one of the following parameters: IOC name, managed object instance ID, a list of related entities comprising related entity items IE (i.e., one or more related entities), and related entity parameters for each of the one or more related entities. Here, the presence of the IOC name and one or more related entities may be mandatory. The managed object instance ID data may be optional.

[0137] In one embodiment, the list of related entities may comprise a number <max. of network elements> of related entity items IE.

[0138] FIG. 11 shows an example of the 3R1-O1 CM data model for the second request "GET (READ) CM DATA REQUEST".

[0139] Referring to FIG. 11, an example of the third request "GET CM DATA REQUEST" is similar to that presented in FIG. 7. "GET CM DATA REQUEST" includes, respectively, the 3R1-O1 CM data model for one or more network elements, the 3R1-O1 CM data model for one or more related entities, and the 3R1-O1 CM data model for one or more name-inclusive IOC entities.

[0140] In particular, the third request "GET CM DATA REQUEST" according to the embodiment indicates the message type "GET CM DATA REQUEST for an rApp ID: 1 with a Subscription ID: x1232323".

[0141] Referring to FIG. 11, the network element list contains one network element. The network element item IE parameter of this network element is set to "0 IEs". The single network element has a network element ID of "10001001 (gNB ID)".

[0142] Furthermore, according to the example, the list of related entities contains two related entities. According to the embodiment, each of the first, second, and third related entities nests one name-containing IOC entity. In this example, the fourth related entity at the bottom of FIG. 11 does not nest a name-containing IOC entity.

[0143] The first related entity is set to "0 IEs". The first name-containing IOC entity has an IOC name of "gNBCUCPFunction". The list of related entities nested in the IOC with the name "gNBCUCPFunction" contains one related entity. This related entity is set to "0 IE" respectively. Furthermore, according to the embodiment, the related entity includes a CM attribute with an attribute name of "PLMN ID (Plane Management Identifier)".

[0144] The second related entity is set to "1 IEs". The second name-containing IOC entity has an IOC name of "NRCellCU". The list of related entities nested in the IOC with the name "NRCellCU" contains one related entity. This related entity is set to "0 IE" respectively. Furthermore, according to the embodiment, the related entity includes a CM attribute with an attribute name of "cellLocalID (Cell Location Identifier)".

[0145] The third related entity is set to "1 IEs". The third name-inclusive IOC entity has the IOC name "CESManagementFunc". The list of related entities nested in the IOC with the name "CESManagementFunc" contains one related entity. This related entity is set to "0 IE" respectively. Further, according to the embodiment, the related entity includes a CM attribute with the attribute name "energySavingState".

[0146] The fourth related entity is set to "1 IEs". The fourth related entity does not include a name-inclusive IOC entity. According to the embodiment, the related entity includes a CM attribute with the attribute name "energySavingState".

[0147] The above disclosure provides examples and descriptions, but is not intended to be exhaustive or to limit the implementation to the exact form disclosed. Changes and modifications are possible in light of the above disclosure or may be obtained from the practice of the implementation.

[0148] Some embodiments may relate to systems, methods, and / or computer-readable media at any possible level of technical detail of integration. Further, one or more of the above-described components may be stored on a computer-readable medium and implemented as instructions executable by at least one processor (and / or may include at least one processor). The computer-readable medium may include a computer-readable non-transitory storage medium (or medium) storing computer-readable program instructions for causing the processor to execute operations.

[0149] A computer-readable storage medium may be a tangible device that can hold and store instructions for use by an instruction execution device. The computer-readable storage medium may be, for example, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof, but is not limited thereto. A non-exhaustive list of more specific examples of computer-readable storage media includes the following: portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital versatile discs (DVDs), memory sticks, floppy disks, punch cards, or mechanically encoded devices such as raised structures in grooves in which instructions are recorded, and any suitable combination thereof. As used herein, a computer-readable storage medium is not to be construed as being a transient signal per se, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., an optical pulse passing through an optical fiber cable), or an electrical signal transmitted through a wire.

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

[0151] The computer-readable program code / instructions for performing the operation may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting parameters, configuration data for integrated circuits, or source code or object code written in any combination of one or more programming languages including object-oriented programming languages such as Smalltalk, C++, and procedural programming languages such as the "C" programming language or similar programming languages. The computer-readable program instructions may be executed entirely on the user's computer as a stand-alone software package, partially on the user's computer, partially on the user's computer, partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (e.g., through the Internet using an Internet service provider). In some embodiments, for example, an electronic circuit including a programmable logic circuit, a field-programmable gate array (FPGA), or a programmable logic array (PLA) may execute the computer-readable program instructions by utilizing the state information of the computer-readable program instructions to personalize the electronic circuit for performing the aspect or operation.

[0152] These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, implement the functions / acts specified in the flowchart and / or block diagram (one or more blocks). These computer-readable program instructions may be stored in a computer-readable storage medium that, when containing instructions that implement aspects of the functions / acts specified in the flowchart and / or block diagram (one or more blocks), causes a computer, programmable data processing apparatus, and / or other device to function in a particular manner.

[0153] The computer-readable program instructions may be loaded onto a computer, other programmable apparatus, or other device to produce a computer-implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions / acts specified in the flowchart and / or block diagram (one or more blocks) by causing a series of operational steps to be performed on the computer, other programmable apparatus, or other device.

[0154] The flowcharts and block diagrams shown illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer-readable media according to various embodiments. Here, each block in the flowchart or block diagram may represent a module, segment, or portion of instructions that includes one or more executable instructions for implementing a particular logical function. The methods, computer systems, and computer-readable media may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those shown in the figures. In some alternative implementations, the functions shown in the blocks may occur out of the order shown in the figures. For example, two blocks shown in succession may, in fact, be executed simultaneously or substantially simultaneously, depending on the functions involved, or the blocks may be executed in the reverse order. Note that each block of the illustrations of the block diagrams and / or flowcharts, and combinations of blocks in the illustrations of the block diagrams and / or flowcharts, can be implemented by a system based on dedicated hardware for performing a particular function or action, or by a combination of dedicated hardware and computer instructions.

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

Claims

1. An apparatus for a non-real-time radio access network intelligence controller (NRT-RIC) framework in an open radio access network (O-RAN), comprising: a memory storing instructions; a first request for obtaining a configuration schema of at least one network element in the O-RAN from an rApp hosted by the NRT-RIC, the first request comprising a first R1-O1 configuration management (CM) data model for identifying the at least one network element, and being received via an R1 interface between the rApp within the O-RAN architecture and the NRT-RIC framework; a first response to the requested configuration schema, which comprises a second R1-O1 CM data model for identifying the at least one network element and for identifying at least one CM attribute of the at least one network element, and is transmitted from the NRT-RIC framework to the rApp via the R1 interface; at least one processor configured to implement the NRT-RIC framework of the NRT-RIC by executing the instructions for performing the above; and the R1 interface is a device that enables the NRT-RIC framework and the rApp to generate and consume at least one O1 interface-related R1 service in the NRT-RIC.

2. The first R1-O1 CM data model comprises: a message type parameter for identifying the type of the first request; at least one network element parameter comprising a network element identifier (ID); The apparatus according to claim 1.

3. The second R1-O1 CM data model comprises: a message type parameter for identifying the type of the first response; a supported information object class (IOC) entity parameter including one or more related entity items for identifying one or more CM attributes for each of the at least one network element; The apparatus according to claim 2.

4. The at least one processor A second request for reading configuration data of one CM attribute out of the at least one CM attribute specified in the first response from the rApp, the second request comprising a third R1-O1 CM data model that identifies a network element and the CM attribute, and receiving the second request received via the R1 interface. Sending, via the R1 interface, a second response comprising a fourth R1-O1 CM data model that identifies the CM attribute corresponding to the second request, from the NRT-RIC framework to the rApp. The apparatus according to claim 1, further configured to execute the instructions for executing the above.

5. The third R1-O1 CM data model includes a message type parameter that identifies the type of the second request, an rApp identifier (ID) that identifies the rApp, a request identifier (ID) for the second request, a network element parameter that includes a network element ID of the network element, a first name-including IOC entity parameter that includes an IOC entity name and a first related entity item that identifies the CM attribute. The apparatus according to claim 4, comprising the above.

6. The fourth R1-O1 CM data model includes a message type parameter that identifies the type of the second response, an rApp ID that identifies the rApp, a network element parameter that includes a network element identifier (ID), a second name-including IOC entity parameter that includes an IOC entity name and a second related entity item that identifies the CM attribute. The apparatus according to claim 4, comprising the above.

7. The apparatus according to claim 5, wherein the second related entity item further includes a CM attribute value that identifies the value of the CM attribute.

8. The at least one processor receives, from the rApp, a third request for writing configuration data of one CM attribute out of the at least one CM attribute, the third request comprising a fifth R1-O1 CM data model that identifies a network element and the CM attribute, and receives the third request received via the R1 interface. Transmit a third response comprising a sixth R1-O1 CM data model for identifying the CM attributes changed in response to the third request from the NRT-RIC framework to the rApp via the R1 interface, The apparatus according to claim 1, further configured to execute the instructions to execute the same. **Claim 9** The fifth R1-O1 CM data model, A message type parameter for identifying the type of the third request, An rApp ID for identifying the rApp, A network element parameter comprising a network element identifier (ID) of the network element, A third name-including IOC entity parameter including an IOC entity name and a third related entity item for identifying the CM attributes changed in response to the third request, The apparatus according to claim 8, comprising: **Claim 10** The sixth R1-O1 CM data model, A message type parameter for identifying the type of the third response, rApp ID, A network element parameter comprising a network element identifier (ID), An attribute status for checking a configuration status, A fourth name-including IOC entity parameter including an IOC entity name and a fourth related entity item for identifying the CM attributes and the status of the writing, The apparatus according to claim 8, comprising: **Claim 11** Based on the writing being not permitted, the fourth related entity item further includes a cause parameter for identifying the cause of the writing being not permitted, the apparatus according to claim 10. **Claim 12** A method for a non-real-time radio access network intelligence controller (NRT-RIC) framework in an open radio access network (O-RAN), Receiving a first request for obtaining a configuration schema of at least one network element in the O-RAN from an rApp hosted by the NRT-RIC, the first request comprising a first R1-O1 CM data model for identifying the at least one network element and being received via an R1 interface between the rApp within the O-RAN architecture and the NRT-RIC framework, Comprising a second R1-O1 CM data model for identifying the at least one network element, and transmitting, via the R1 interface, a first response to the requested configuration schema to the rApp from the NRT-RIC framework, the first response identifying at least one configuration management (CM) attribute of the at least one network element. Comprising The R1 interface enables the NRT-RIC framework and the rApp to generate and consume at least one O1 interface-related R1 service in the NRT-RIC. **Claim 13** The first R1-O1 CM data model A message type parameter identifying the type of the first request, and At least one network element parameter comprising a network element identifier (ID). The method according to claim 12, comprising **Claim 14** The first R1-O1 CM data model A message type parameter identifying the type of the first request, and At least one network element parameter comprising a network element identifier (ID). The method according to claim 12, comprising **Claim 15** The second R1-O1 CM data model A message type parameter identifying the type of the first response, and A supported information object class (IOC) entity parameter including one or more related entity items identifying one or more CM attributes for each of the at least one network element. The method according to claim 12, comprising **Claim 16** Receiving, from the rApp, a second request for reading configuration data of one CM attribute among the at least one CM attribute identified in the first response, the second request comprising a third R1-O1 CM data model identifying a network element and the CM attribute, and receiving the second request received via the R1 interface; and Transmitting, via the R1 interface, a second response to the rApp from the NRT-RIC framework, the second response comprising a fourth R1-O1 CM data model identifying the CM attribute in response to the second request. The method according to claim 12, further comprising.

17. From the rApp, a third request for writing configuration data of one of the at least one CM attribute, comprising a fifth R1 - O1 CM data model that identifies a network element and the CM attribute, and receiving the third request received via the R1 interface; Sending, via the R1 interface, a third response comprising a sixth R1 - O1 CM data model for identifying the CM attribute changed in response to the third request, from the NRT - RIC framework to the rApp; The method according to claim 12, further comprising.

18. A non - transitory computer - readable recording medium having recorded thereon instructions executable by at least one processor configured to execute a method for a non - real - time radio access network intelligence controller (NRT - RIC) framework in an open radio access network (O - RAN), The method comprising: A first request for obtaining a configuration schema of at least one network element in the O - RAN from an rApp hosted by the NRT - RIC, comprising a first R1 - O1 CM data model that identifies the at least one network element, and receiving the first request received via an R1 interface between the rApp within the O - RAN architecture and the NRT - RIC framework; Sending, via the R1 interface, a first response to the requested configuration schema, comprising a second R1 - O1 CM data model that identifies the at least one network element and identifies at least one configuration management (CM) attribute of the at least one network element, from the NRT - RIC framework to the rApp; Comprising, The R1 interface is a non - transitory computer - readable recording medium that enables the NRT - RIC framework and the rApp to generate and consume at least one O1 - interface - related R1 service in the NRT - RIC.

19. The method comprises: A second request for reading configuration data of one of the at least one CM attribute specified in the first response from the rApp, the second request comprising a third R1-O1 CM data model that identifies a network element and the CM attribute, and receiving the second request received via the R1 interface. Sending, via the R1 interface, a second response comprising a fourth R1-O1 CM data model that identifies the CM attribute corresponding to the second request, from the NRT-RIC framework to the rApp. The non-transitory computer-readable recording medium according to claim 18, further comprising the above.

20. The method includes: Receiving, from the rApp, a third request for writing configuration data of one of the at least one CM attribute, the third request comprising a fifth R1-O1 CM data model that identifies a network element and the CM attribute, and receiving the third request received via the R1 interface. Sending, via the R1 interface, a third response comprising a sixth R1-O1 CM data model for identifying the CM attribute changed in response to the third request, from the NRT-RIC framework to the rApp. The non-transitory computer-readable recording medium according to claim 18, further comprising the above.

Images