Method and system for obtaining a configuration schema for RAPP

Abstract

A method and system for managing a configuration schema for an rApp are provided. The method may include receiving, by a RAN OAM-related function, a get configuration schema request. The get configuration schema request originates from the rApp, the get configuration schema request indicating a requested configuration schema of a network element. The method may further include determining, by the RAN OAM-related function, whether the get configuration schema request is valid, and sending, by the RAN OAM-related function, a get configuration schema response to the get configuration schema request to the rApp.

Description

[Technical Field]

[0001] Systems and methods according to example embodiments of the present disclosure relate to providing a method for obtaining a configuration schema for an rApp from a radio access network (RAN) operation and maintenance (OAM) function. [Background technology]

[0002] The Radio Access Network (RAN) is a key component in telecommunications systems because it connects end-user devices (or user equipment (UE)) to the rest of the network. The RAN includes a combination of various network elements (NEs) that connect end-user devices to the core network. Traditionally, the hardware and / or software of a particular RAN is vendor-specific.

[0003] In recent years, advances in telecommunications technology have made it possible to virtually realize many telecommunications services in software. For example, RANs, such as the Open RAN (O-RAN) architecture, decompose a single network component into multiple functional elements. For example, a baseband unit (BBU) or base station (i.e., eNB or gNB) may be decomposed into several functional elements, including a distributed unit (DU) and a centralized unit (CU), and the CU may be further decomposed into a centralized unit control plane (CU-CP) and a centralized unit user plane (CU-UP). This functional decomposition of network elements allows telecommunications services and related functions to be defined and provided in software-based forms or virtual network services, such as virtualized network functions (VNFs), cloud-native network functions (CNFs), or software-defined networking (SDN), among others.

[0004] RAN functions in the O-RAN architecture are controlled and optimized by RICs. RICs are software-defined components that implement modular applications to facilitate the multi-vendor operability required in O-RAN systems and to automate and optimize RAN operations. RICs are divided into two types: non-real-time RICs (Non-RT RICs) and near-real-time RICs (Near-RT RICs).

[0005] The non-RT RIC is the control point for non-real-time control loops and operates on sub-second timescales within a Service Management and Orchestration (SMO) framework. Its functionality is implemented via modular applications called rApps and includes providing policy-based guidance and reinforcement over the A1 interface, which is the interface that enables communication between the non-RT RIC and the quasi-RT RIC; performing data analysis, artificial intelligence / machine learning (AI / ML) training and inference for RAN optimization; and / or recommending configuration management actions over the O1 interface, which is the interface that connects the SMO to RAN managed elements (e.g., quasi-RT RIC, O-RAN Centralized Unit (O-CU), O-RAN Distributed Unit (O-DU), etc.).

[0006] The SMO framework manages and orchestrates RAN elements. Specifically, SMO includes Federated O-Cloud Orchestration and Management (FOCOM), a Network Function Orchestrator (NFO) that manages Virtual Machine (VM)-based VNFs and container (i.e., instance)-based VNFs, and Operations and Management (OAM) as part of SMO that manages and orchestrates what is called the O-Ran Cloud (O-Cloud).

[0007] Additionally, the SMO may include an operational support system (OSS) and an element management system (EMS), each of which may be configurable to perform one or more of fault management operations, configuration management operations, account management operations, performance management operations, and security management operations (FCAPS operations) for one or more services hosted or deployed on the server. In some embodiments, the service management system may include multiple EMSs, each of which may be configured to manage a single service or a group of services associated with a particular vendor / service provider, and the OSS is the OSS interface between the monitoring system, the orchestrator, and the multiple EMSs. Thus, the SMO may provide a single point of control for managing multiple services (associated with multiple vendors / network service providers) through only one monitoring system and one orchestrator system (i.e., one monitoring system and one orchestrator system can be utilized to manage services associated with multiple vendors / service providers).

[0008] In the prior art, an rApp in a non-RT RIC may be implemented as a service consumer. A situation may arise in which the rApp wants to obtain configuration schemas (e.g., a set of configuration schemas indicating readable and / or writable parameters of network functions such as CUs and DUs) from an OAM function, especially data related to management entities from associated service producers. However, the related art does not describe any procedures for the above. Therefore, it is necessary to be able to obtain configuration schemas from the OAM function of the rApp. Summary of the Invention

[0009] Exemplary embodiments of the present disclosure provide a method and system for an rApp implemented as a service consumer to obtain configuration schemas from RAN OAM-related functions, particularly data related to management entities from associated service producers. In particular, according to embodiments, the rApp may send a get configuration schema request to the RAN OAM-related function. The RAN OAM-related function may verify whether the get configuration schema request is valid and then send a get configuration schema response to the rApp.

[0010] Thus, embodiments of the present disclosure may provide an optimized method for obtaining a configuration schema while avoiding data validation errors and the like.

[0011] According to an embodiment, a method for managing a configuration schema for an rApp may be provided. The method may be executed by at least one processor. The method includes receiving, by a RAN OAM-related function, a get configuration schema request. The get configuration schema request originates from an rApp, and the get configuration schema request indicates a desired configuration schema for a network element. The method also includes determining, by the RAN OAM-related function, whether the get configuration schema request is valid; and sending, by the RAN OAM-related function, a get configuration schema response to the rApp based on the get configuration schema request.

[0012] The get configuration schema response may include the desired configuration schema.

[0013] The get configuration schema request may include the identifier (ID) of the rApp and the query criteria.

[0014] The get configuration schema request may further include information about the management entity of the service producer.

[0015] Determining whether the get configuration schema request is valid may include determining whether the rApp is authorized by the RAN OAM-related functionality to request the configuration schema.

[0016] Determining whether the get configuration schema request is valid may include determining, by the RAN OAM-related function, whether the get configuration schema request is valid based on the query criteria, based on a determination that the rApp is authorized to request the desired configuration schema.

[0017] The get configuration schema response indicates whether the get configuration schema request was successful or unsuccessful.

[0018] According to an embodiment, an apparatus for managing a configuration schema for an rApp may be provided, the apparatus comprising: at least one memory storing computer-executable instructions; and at least one processor, the at least one processor configured to execute computer-executable instructions to receive, by the RAN OAM-related function, a get configuration schema request, the get configuration schema request originating from an rApp, the get configuration schema request indicating a requested configuration schema of the network element; The at least one processor is configured to execute computer-executable instructions to determine, by the RAN OAM-related function, whether the get configuration schema request is valid, and to send, by the RAN OAM-related function, a get configuration schema response to the rApp in response to the get configuration schema request.

[0019] The at least one processor may be further configured to determine whether the get configuration schema request is valid by executing computer-executable instructions to determine whether the rApp is authorized by the RAN OAM-related functionality to request the configuration schema.

[0020] The at least one processor may be further configured to execute the computer-executable instructions to determine, based on a determination that the rApp is authorized to request the configuration schema, whether the get configuration schema request is valid by determining, by the RAN OAM-related function, whether the get configuration schema request is valid based on the query criteria.

[0021] Additional aspects will be set forth in part in the description that follows, and in part will be apparent from the description, or may be learned by practice of presented embodiments of the present disclosure.

[0022] Features, aspects, and advantages of certain exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which like reference numerals refer to like elements. [Brief explanation of the drawings]

[0023] [Figure 1] 1 is a flowchart of a method for obtaining a configuration schema, according to one embodiment.

[0024] [Figure 2] FIG. 1 illustrates a call flow for obtaining a configuration schema according to one embodiment.

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

[0026] [Figure 4] FIG. 2 is a diagram of exemplary components of a device according to one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0027] The following detailed description of the exemplary embodiments refers to the accompanying drawings.

[0028] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of implementations. Furthermore, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, in the flowcharts and descriptions of operations provided below, it should be understood that one or more operations may be omitted, one or more operations may be added, one or more operations may occur (at least partially) concurrently, or the order of one or more operations may be rearranged.

[0029] 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 specialized control hardware or software code used to implement these systems and / or methods is not limiting of the implementation. Accordingly, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It should be understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.

[0030] Although particular combinations of features are recited in the claims and / or disclosed herein, these combinations do not limit the disclosure of possible implementations. Indeed, many of these features can be combined in ways not specifically recited in the claims and / or disclosed herein. Although each dependent claim listed below may depend directly on only one claim, the disclosure of possible implementations includes each dependent claim in combination with all other claims within its scope.

[0031] As used herein, no element, act, or instruction should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles "a" and "an" are intended to include one or more items (compositions, objects, elements, parts) and may be used interchangeably with "one or more." Where only one item is intended, the term "one" or similar language is used. Also, as used herein, terms such as "has," "have," "having," "include," and "including" are intended to be open-ended terms. Furthermore, the phrase "based on" is intended to mean "based at least in part on," unless specifically stated otherwise. Furthermore, phrases such as "at least one of A and B" or "at least one of A or B" should be understood to include only A, only B, or both A and B.

[0032] Furthermore, the described features, advantages, and characteristics of the present disclosure may be combined in any suitable manner in one or more embodiments. Those skilled in the art will recognize, in light of the description herein, that the present disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other cases, additional features and advantages may be recognized in particular embodiments that may not be present in all embodiments of the present disclosure.

[0033] Exemplary embodiments of the present disclosure provide a method and system for an rApp implemented as a service consumer to obtain a configuration schema from a RAN OAM-related function, particularly to obtain data related to a management entity from an associated service producer. In particular, according to embodiments, the rApp may send a get-configuration-schema request to the RAN OAM-related function. The RAN OAM-related function may verify whether the get-configuration-schema request is valid and then send a get-configuration-schema response to the rApp.

[0034] Thus, embodiments of the present disclosure may provide an optimized method for obtaining a configuration schema while avoiding data validation errors and the like.

[0035] 1 illustrates a flowchart of an example method 100 for obtaining a configuration schema, according to one embodiment. While the operations in example method 100 may be performed by a RAN OAM-related function that is a non-fixed function in an SMO / non-RT RIC framework, it should be understood that method 100 may nevertheless be performed by other types of functions in an SMO / non-RT RIC framework, according to other embodiments. According to one embodiment, the RAN OAM-related function may be capable of communicating with one or more rApps in the non-RT RIC (e.g., via an R1 interface).

[0036] At operation S110, a RAN OAM-related function (which may be implemented as a service consumer) may receive a get configuration schema request originating from an rApp (which may be implemented as a service producer). According to one embodiment, the get configuration schema request may include a desired configuration schema, i.e., it may specify which configuration schema the rApp wants to retrieve from the RAN OAM-related function. According to one embodiment, the get configuration schema request may further include an rApp identifier (ID) and, possibly, query criteria and information about the managed entities of the service producer. When read by the RAN OAM-related function, the get configuration schema request may enable the RAN OAM-related function to determine the requested result set for the configuration schema. It should be understood that, according to an embodiment, the get configuration schema request may be in any suitable data format.

[0037] In operation S120, the RAN OAM-related function may verify whether the get configuration schema request received in operation S110 is valid. According to one embodiment, this may include first determining, by the RAN OAM-related function, whether the rApp is authorized to request the configuration schema. For example, the RAN OAM-related function may check whether the rApp is part of an authorized rApp list by checking the rApp ID. Such authorization may be checked in cooperation with the SME function. Nevertheless, it should be understood that any suitable method may be used to verify whether an rApp is authorized. In one embodiment, once the RAN OAM-related function determines that the rApp is authorized, it may further determine whether the get configuration schema request is valid based on the query criteria. For example, the RAN OAM-related function may check whether the query criteria request an unavailable configuration schema (i.e., the query criteria are out of range). The RAN OAM-related function may then determine whether the get configuration schema request was successful or failed.

[0038] In operation S130, the RAN OAM-related function may send a get configuration schema response back to the rApp based on the result of the get configuration schema request in operation S120. The get configuration schema response may include the requested / desired configuration schema. According to one embodiment, the get configuration schema response may include the configuration schema only if the get configuration schema request was successful. In another embodiment, the get configuration schema response may indicate whether the get configuration schema request was successful or failed.

[0039] 2 illustrates an exemplary call flow for obtaining a configuration schema according to one embodiment. The rApp 200 and RAN-OAM related functions 210 are provided in a non-RT RIC framework and may be similar to the rApp and RAN-OAM related functions described with respect to FIG. 1 above.

[0040] In operation S220, the rApp 200 may send a get configuration schema request to the RAN OAM related function 210. This may be similar to operation S110 described in FIG. 1 above.

[0041] In operation S221, the RAN OAM-related function 210 may perform an authorization procedure to check whether the get configuration schema request is from an authorized rApp, which may be similar to the portion of operation S120 described above with respect to FIG. 1 regarding determining whether the get configuration schema request is authorized.

[0042] In operation S222, the RAN OAM-related function 210 may perform a verify request procedure to check whether the get configuration schema request is valid, which may be similar to the portion of operation S120 described above with respect to FIG. 1 regarding determining whether the get configuration schema request is valid based on query criteria.

[0043] In operation S223, the RAN OAM-related function 210 may send a get configuration schema response back to the rApp 200. This may be similar to operation S130 described in FIG. 1 above.

[0044] Therefore, the above embodiment can provide an optimized method for obtaining a configuration schema while avoiding any data validation errors and the like.

[0045] 3 is a diagram of an example environment 300 in which the systems and / or methods described herein may be implemented. As shown in FIG. 3, environment 300 may include a user device 310, a platform 320, and a network 330. The devices in environment 300 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections. In embodiments, any of the functions and operations described with reference to FIGS. 6-7 above may be performed by any combination of the elements illustrated in FIG. 3.

[0046] The user device 310 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information associated with the platform 320. For example, the user device 310 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 smart watch), or a similar device. In some implementations, the user device 310 may receive information from and / or transmit information to the platform 320.

[0047] Platform 320 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information. In some implementations, platform 320 may include a cloud server or a group of cloud servers. In some implementations, platform 320 may be designed to be modular, such that certain software components can be swapped in or out depending on particular needs. Thus, platform 320 can be easily and / or quickly reconfigured for different uses.

[0048] In some implementations, as shown (in the figure), platform 320 may be hosted in a cloud computing environment 322. Notably, although the implementations described herein describe platform 320 as being hosted within cloud computing environment 322, in some implementations platform 320 may not be cloud-based (i.e., may be implemented outside of a cloud computing environment) or may be partially cloud-based.

[0049] Cloud computing environment 322 includes an environment that hosts platform 320. Cloud computing environment 322 may provide services such as computation, software, data access, and storage, without requiring end-user (e.g., user device 310) knowledge of the physical location and configuration of the systems and / or devices hosting platform 320. As shown, cloud computing environment 322 may include computing resources 324 (collectively referred to as "computing resources 324" and individually as "computing resource 324").

[0050] Computing resources 324 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, computing resources 324 may host platform 320. Cloud resources may include compute instances executing within computing resources 324, storage devices included within computing resources 324, data transfer devices provided by computing resources 324, etc. In some implementations, computing resources 324 may communicate with other computing resources 324 via wired connections, wireless connections, or a combination of wired and wireless connections.

[0051] As further shown in FIG. 3, the computing resources 324 include cloud resources such as one or more applications (APPs) 324-1, one or more virtual machines (VMs) 324-2, virtualized storage (VS) 324-3, and one or more hypervisors (HYPs) 324-4.

[0052] The application 324-1 includes one or more software applications that may be provided to or accessed by the user device 310. The application 324-1 may eliminate the need for a software application to be installed and run on the user device 310. For example, the application 324-1 may include software associated with the platform 320 and / or any other software that may be provided via the cloud computing environment 322. In some implementations, one application 324-1 may send information to or receive information from one or more other applications 324-1 via a virtual machine 324-2.

[0053] The virtual machine 324-2 includes a software-implemented machine (e.g., a computer) that executes programs like a physical machine. The virtual machine 324-2 can be either a system virtual machine or a process virtual machine, depending on the application and the degree to which the virtual machine 324-2 matches any real machine. 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 support a single process. In some implementations, the virtual machine 324-2 may run on behalf of a user (e.g., the user device 310) and manage the infrastructure of the cloud computing environment 322, such as data management, synchronization, or long-term data transfer.

[0054] Virtualized storage 324-3 includes one or more storage systems and / or one or more devices that use virtualization technology within the storage systems or devices of computing resources 324. In some implementations, for storage systems, types of virtualization may include block virtualization and file virtualization. Block virtualization may refer to the abstraction (or separation) of logical storage from physical storage so that the storage system can be accessed regardless of the physical storage or heterogeneous structure. Separation may provide storage system administrators with flexibility in how they manage storage for end users. File virtualization may eliminate the dependency between data accessed at the file level and where the file is physically stored. This may enable optimization of storage usage, server consolidation, and / or non-disruptive file migration.

[0055] Hypervisor 324-4 may provide hardware virtualization technology that allows multiple operating systems (e.g., guest operating systems) to run simultaneously on a host computer, such as computing resource 324. Hypervisor 324-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 different operating systems may share virtualized hardware resources.

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

[0057] The number and arrangement of devices and networks shown in Figure 3 are provided as an example. In practice, there may be more devices and / or networks than those shown in Figure 3, fewer devices and / or networks, different devices and / or networks than those shown in Figure 3, or differently arranged devices and / or networks. Furthermore, two or more devices shown in Figure 3 may be implemented within a single device, or a single device shown in Figure 3 may be implemented as multiple distributed devices. Additionally or alternatively, a set of devices (e.g., one or more devices) of environment 300 may perform one or more functions described as being performed by another set of devices of environment 300.

[0058] 4 is a diagram of example components of a device 400. The device 400 may correspond to a user device 310 and / or a platform 320. As shown in FIG. 4, the device 400 may include a bus 410, a processor 420, a memory 430, a storage component 440, an input component 450, an output component 460, and a communication interface 470.

[0059] The bus 410 includes components that enable communication between the components of the device 400. The processor 420 may be implemented in hardware, firmware, or a combination of hardware and software. The processor 420 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 another type of processing component. In some implementations, the processor 420 includes one or more processors that can be programmed to perform functions. The memory 430 includes random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, and / or optical memory) that stores information and / or instructions for use by the processor 420.

[0060] Storage component 440 stores information and / or software related to the operation and use of device 400. For example, storage component 440 may include a hard disk (e.g., a magnetic disk, optical disk, magneto-optical disk, and / or solid-state disk), a compact disk (CD), a digital versatile disk (DVD), a floppy disk, a cartridge, magnetic tape, and / or another type of non-transitory computer-readable medium, along with a corresponding drive. Input component 450 includes components (e.g., a touchscreen display, a keyboard, a keypad, a mouse, buttons, switches, and / or a microphone) that enable device 400 to receive information, such as via user input. Additionally or alternatively, input component 450 may include sensors for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, and / or an actuator). Output component 460 includes components (e.g., a display, a speaker, and / or one or more light-emitting diodes (LEDs)) that provide output information from device 400.

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

[0062] Device 400 may perform one or more processes described herein. Device 400 may perform these processes in response to processor 420 executing software instructions stored by a non-transitory computer-readable medium, such as memory 430 and / or storage component 440. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space across multiple physical storage devices.

[0063] Software instructions may be loaded into memory 430 and / or storage component 440 from another computer-readable medium or from another device via communication interface 470. The software instructions stored in memory 430 and / or storage component 440, when executed, may cause processor 420 to perform one or more processes described herein.

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

[0065] The number and arrangement of components shown in Figure 4 are provided as an example. In practice, device 400 may include more, fewer, different, or differently arranged components than those shown in Figure 4. Additionally or alternatively, a set of components (e.g., one or more components) of device 400 may perform one or more functions that are described as being performed by another set of components of device 400.

[0066] In embodiments, any one of the operations or processes of Figures 1 and 2 may be implemented by or using any one of the elements illustrated in Figures 3 and 4. It will be appreciated that other embodiments are not limited thereto and may be implemented in a variety of different architectures (e.g., bare metal architectures, any cloud-based or deployment architectures such as Kubernetes, Docker, OpenStack, etc.).

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

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

[0069] A computer-readable storage medium may be a tangible device that can hold and store instructions used by an instruction execution device. The computer-readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of computer-readable storage media includes 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 disc (DVD), memory stick, floppy disk, mechanically encoded devices such as punch cards or ridge-in-groove structures with instructions recorded thereon, and any suitable combination of the foregoing. The term computer-readable storage medium as used herein should not be construed as a transitory signal itself, such as an electric wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., a light pulse passing through a fiber optic cable), or an electrical signal transmitted through an electrical wire.

[0070] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to each computing / processing device or to an external computer or 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 include copper transmission cables, optical fiber transmissions, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface within 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 the respective computing / processing device.

[0071] The computer-readable program code / instructions for carrying out operations may be either source code or object code written in any combination of one or more programming languages, including assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, configuration schema for integrated circuits, or 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 execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and 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 via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry including, for example, a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA) may execute computer-readable program instructions and personalize the electronic circuitry by utilizing state information of the computer-readable program instructions to perform aspects or operations.

[0072] 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 create a machine, whereby the instructions, executed by the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams. These computer-readable program instructions may also be stored on a computer-readable storage medium that can instruct a computer, programmable data processing apparatus, and / or other device to function in a particular manner, whereby a computer-readable storage medium having instructions stored therein includes an article of manufacture containing instructions that implement aspects of the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.

[0073] The computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device and cause the computer, other programmable apparatus, or other device to perform a series of operational steps to generate a computer-implemented process, such that the instructions executing on the computer, other programmable apparatus, or other device perform the function(s) / act(s) specified in a block or blocks of the flowcharts and / or block diagrams.

[0074] The illustrated flowcharts and block diagrams illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer-readable media according to various embodiments. In this regard, each block in a flowchart or block diagram may represent a portion of a microservice(s), module, segment, or instruction set, which includes one or more executable instructions for implementing the specified logical function(s). The methods, computer systems, and computer-readable media may include more, fewer, different, or differently arranged blocks than shown in the figures. In some alternative implementations, the functions noted in the blocks may occur out of the order depicted. For example, two blocks shown in succession may actually be executed concurrently or substantially concurrently, or the blocks may be executed in the reverse order, depending on the functionality involved. It should also be noted that each block of the block diagrams and / or flowchart diagrams, and combinations of blocks in the block diagrams and / or flowchart diagrams, may be implemented by a dedicated hardware-based system that performs the specified functions or operations or executes a combination of dedicated hardware and computer instructions.

[0075] 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 specialized control hardware or software code used to implement these systems and / or methods is not limiting of the implementation. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, and it will be understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.

[0076] Various aspects of the embodiments

[0077] Various further respective aspects and features of embodiments of the present disclosure may be defined by the following clauses: Item [1]: A method for managing a configuration schema for an rApp, executed by at least one processor, comprising: receiving, by a RAN OAM-related function, a get configuration schema request, wherein the get configuration schema request originates from the rApp, and the get configuration schema request indicates a desired configuration schema of a network element; determining, by a RAN OAM-related function, whether the get configuration schema request is valid; and sending, by the RAN OAM-related function, a get configuration schema response to the rApp based on the get configuration schema request. Item [2]: The method according to item [1], wherein the get configuration schema response includes the desired configuration schema. Item [3]: The method described in Item [2], wherein the get configuration schema request includes an identifier (ID) of the rApp and query criteria. Item [4]: ​​The method according to Item [3], wherein the get configuration schema request further includes information about the managed entities of the service producer. Item [5]: A method according to any one of items [3] and [4], wherein the step of determining whether the get configuration schema request is valid includes a step of determining whether the rApp is authorized by the RAN OAM-related function to request the configuration schema. Item [6]: The method described in Item [5], wherein the step of determining whether the get configuration schema request is valid includes a step of determining, by the RAN OAM-related function, whether the get configuration schema request is valid based on query criteria, based on a determination that the rApp is authorized to request the desired configuration schema. Item [7]: A method according to any one of items [1] to [6], in which the get configuration schema response indicates whether the get configuration schema request was successful or failed. Item [8]: An apparatus for managing a configuration schema for an rApp, at least one memory storing computer-executable instructions; at least one processor; the at least one processor is configured to execute computer-executable instructions to receive, by the RAN OAM-related function, a get configuration schema request, the get configuration schema request originating from the rApp, the get configuration schema request indicating a requested configuration schema of the network element; The at least one processor is configured to execute computer-executable instructions to determine, by the RAN OAM-related function, whether the get configuration schema request is valid; The apparatus, wherein the at least one processor is configured to execute computer-executable instructions to send, by the RAN OAM-related function, a get configuration schema response to the rApp in response to the get configuration schema request. Item [9]: The device described in Item [8], wherein the get configuration schema response includes the requested configuration schema. Item

[10] : The device described in Item [9], wherein the get configuration schema request includes an identifier (ID) of the rApp and query criteria. Item

[11] : The device described in Item

[10] , wherein the get configuration schema request further includes information about the managed entities of the service producer. Item

[12] : The device described in Item

[10] or

[11] , wherein the at least one processor is further configured to execute computer-executable instructions to determine whether the get configuration schema request is valid by determining whether the rApp is authorized by the RAN OAM-related function to request the configuration schema. Item

[13] : The device described in Item

[12] , wherein the at least one processor is further configured to execute computer-executable instructions to determine, based on a determination that the rApp is authorized to request the configuration schema, whether the get configuration schema request is valid by determining, by the RAN OAM-related function, whether the get configuration schema request is valid based on query criteria. Item

[14] : The device described in any of items [8] to

[13] , wherein the get configuration schema response indicates whether the get configuration schema request was successful or failed. Item

[15] : A non-transitory computer-readable recording medium having stored thereon instructions executable by at least one processor, the instructions causing the at least one processor to perform a method, the method including the steps of: receiving, by a RAN OAM-related function, a get configuration schema request, the get configuration schema request originating from an rApp, the get configuration schema request indicating a requested configuration schema of a network element; determining, by the RAN OAM-related function, whether the get configuration schema request is valid; and sending, by the RAN OAM-related function, a get configuration schema response to the rApp in response to the get configuration schema request. Item

[16] : The non-transitory computer-readable storage medium described in Item

[15] , wherein the get configuration schema response includes the requested configuration schema. Item

[17] : A non-transitory computer-readable storage medium as described in Item

[16] , wherein the get configuration schema request includes an identifier (ID) of the rApp and query criteria. Item

[18] : The non-transitory computer-readable storage medium described in Item

[17] , wherein the get configuration schema request further includes information about the managed entities of the service producer. Item

[19] : A non-transitory computer-readable recording medium described in either of Items

[17] and

[18] , wherein the step of determining whether the get configuration schema request is valid includes a step of determining whether the rApp is authorized by the RAN OAM-related function to request the configuration schema. Item

[20] : A non-transitory computer-readable recording medium as described in Item

[19] , wherein the step of determining whether the get configuration schema request is valid includes determining, by the RAN OAM-related function, whether the get configuration schema request is valid based on query criteria, based on a determination that the rApp is authorized to request the configuration schema.

[0078] It can be appreciated that many modifications and variations of the present disclosure are possible in light of the above teachings. It will be apparent that, within the scope of the appended clauses, the present disclosure may be practiced otherwise than as specifically described herein.

Claims

1. 1. A method, executed by at least one processor, for managing a configuration schema for an rApp, the method comprising: receiving, by a RAN OAM-related function, a get configuration schema request, the get configuration schema request originating from the rApp, the get configuration schema request indicating a requested configuration schema of a network element; determining, by the RAN OAM-related function, whether the get configuration schema request is valid; sending, by the RAN OAM-related function, a get configuration schema response to the rApp in response to the get configuration schema request.

2. The method of claim 1 , wherein the get configuration schema response includes the requested configuration schema.

3. The method of claim 2 , wherein the get configuration schema request includes an identifier (ID) of the rApp and a query criterion.

4. The method of claim 3 , wherein the get configuration schema request further includes information about managed entities of a service producer.

5. The step of determining whether the get configuration schema request is valid comprises:

4. The method of claim 3, comprising determining, by the RAN OAM-related function, whether the rApp is authorized to request the configuration schema.

6. The step of determining whether the get configuration schema request is valid comprises:

6. The method of claim 5, further comprising: determining, by the RAN OAM-related function, whether the get configuration schema request is valid based on the query criteria, based on a determination that the rApp is authorized to request the configuration schema.

7. The method of claim 1 , wherein the get configuration schema response indicates whether the get configuration schema request was successful or failed.

8. 1. An apparatus for managing a configuration schema for a rApp, the apparatus comprising: at least one memory storing computer-executable instructions; at least one processor, wherein the at least one processor is configured to execute the computer-executable instructions to receive, by a RAN OAM-related function, a get configuration schema request, the get configuration schema request originating from the rApp, the get configuration schema request indicating a requested configuration schema of a network element; the at least one processor is configured to execute the computer-executable instructions to determine, by the RAN OAM-related functionality, whether the get configuration schema request is valid; the at least one processor is configured to execute the computer-executable instructions to cause the RAN OAM-related function to send a get configuration schema response to the rApp in response to the get configuration schema request.

9. The apparatus of claim 8 , wherein the get configuration schema response includes the requested configuration schema.

10. The apparatus of claim 9 , wherein the get configuration schema request includes an identifier (ID) of the rApp and a query criterion.

11. The apparatus of claim 10 , wherein the get configuration schema request further includes information about managed entities of a service producer.

12. The at least one processor executes the computer-executable instructions to:

11. The apparatus of claim 10, further configured by the RAN OAM-related function to determine whether the get configuration schema request is valid by determining whether the rApp is authorized to request the configuration schema.

13. The at least one processor executes the computer-executable instructions to:

13. The apparatus of claim 12, further configured, based on a determination that the rApp is authorized to request the configuration schema, to determine, by the RAN OAM-related function, whether the get configuration schema request is valid by determining whether the get configuration schema request is valid based on the query criteria.

14. The apparatus of claim 8 , wherein the get configuration schema response indicates whether the get configuration schema request was successful or failed.

15. 1. A non-transitory computer-readable storage medium having stored thereon instructions executable by at least one processor, the instructions causing the at least one processor to perform a method, the method comprising: receiving, by a RAN OAM-related function, a get configuration schema request, the get configuration schema request originating from the rApp, the get configuration schema request indicating a requested configuration schema of a network element; The method further comprises: determining, by the RAN OAM-related function, whether the get configuration schema request is valid; and sending, by the RAN OAM-related function, a get configuration schema response to the rApp in response to the get configuration schema request. A non-transitory computer-readable recording medium.

16. The non-transitory computer-readable medium of claim 15 , wherein the get configuration schema response includes the requested configuration schema.

17. 17. The non-transitory computer-readable medium of claim 16, wherein the get configuration schema request includes an identifier (ID) of the rApp and a query criterion.

18. 20. The non-transitory computer-readable medium of claim 17, wherein the get configuration schema request further includes information about managed entities of a service producer.

19. The step of determining whether the get configuration schema request is valid comprises:

20. The non-transitory computer-readable medium of claim 17, further comprising determining, by the RAN OAM-related function, whether the rApp is authorized to request the configuration schema.

20. The step of determining whether the get configuration schema request is valid comprises:

20. The non-transitory computer-readable storage medium of claim 19, further comprising: determining, by the RAN OAM-related function, whether the get configuration schema request is valid based on the query criteria, based on a determination that the rApp is authorized to request the configuration schema.

Images