Data transfer management in a network

Abstract

An apparatus, method, and device for automatically managing data transfer in a network are provided. According to an embodiment, the apparatus may be configured to receive, from an rApp or other SMO function, at least one of a request to obtain configuration data of an O-RAN network element and a request to update the configuration of the O-RAN network element, and in response to receiving the request to obtain the configuration data of the O-RAN network element, to obtain the configuration data using a read storage, and in response to receiving the request to update the configuration of the O-RAN network element, to update the configuration of the O-RAN network element using a write storage different from the read storage based on the configuration provided in the request, wherein the write storage and the read storage may be included in the apparatus.

Description

[Technical Field]

[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 448,893, entitled "A DUAL CACHE AND ASYNCHRONIZED APPROACH FOR SMO / NON-RT RIC CM READ AND WRITE CONFIGURATION DATA OPERATIONS," filed with the U.S. Patent and Trademark Office on February 28, 2023, the disclosure of which is incorporated herein by reference in its entirety.

[0002] Systems, methods, and computer programs consistent with example embodiments of the present disclosure relate to telecommunications networks, and more particularly, to managing data transfers in telecommunications networks. [Background technology]

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

[0004] Open RAN (O-RAN) technology is emerging to allow multiple vendors to provide hardware and / or software for telecommunication systems. Because different vendors are involved, the types of hardware and / or software provided may also vary. That is, different types of NEs may be provided by different vendors, and depending on the specific service, the NEs may be virtualized in software form (e.g., virtual machine (VM)-based) or in physical hardware form (e.g., non-VM-based).

[0005] To this end, O-RAN divides RAN functions into a centralized unit (CU), a distributed unit (DU), and a radio unit (RU). The CU may be a logical node for hosting the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and / or Packet Data Convergence Protocol (PDCP) sublayers of the RAN. The DU may be a logical node for hosting the Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) sublayers of the RAN. The RU may be a physical node that converts radio signals from the antenna into digital signals that can be transmitted to the DU via the fronthaul. These entities can be developed by different vendors because they have open protocols and interfaces between them.

[0006] Figure 1 shows an O-RAN architecture in the related art. RAN functions in the O-RAN architecture can be controlled and optimized by a RAN Intelligent Controller (RIC). The RIC can be a software-defined component that implements modular applications to facilitate multi-vendor operability required in an O-RAN system and to automate and optimize RAN operations. As shown in Figure 1, the RIC can be divided into two types: non-real-time RIC (Non-RT RIC) 120 and near-real-time RIC (Near-RT RIC) 130.

[0007] The non-RT RIC 120 may be the control point for non-real-time control loops and may operate on timescales greater than one second within the Service Management and Orchestration (SMO) framework 110. Its functionality may be implemented via modular applications called rApps and may include: providing policy-based guidance and enrichment over the A1 interface, which is an interface that enables communication between non-RT RICs and quasi-RT RICs; performing data analytics; artificial intelligence / machine learning (AI / ML) training and inference for RAN optimization; and / or recommending configuration management actions via the O1 interface, which may be an interface that connects the SMO to RAN managed elements (e.g., quasi-RT RIC 130, O-RAN Centralized Units (O-CUs) 140, 150, O-RAN Distributed Units (O-DUs) 170, etc.).

[0008] The quasi-RT RIC 130 can operate on a timescale between 10 milliseconds and 1 second and can be coupled to the O-DU 170, the O-CU (split into the O-CU control plane (O-CU-CP) 140 and the O-CU user plane (O-CU-UP) 150), and the open evolved NodeB (O-eNB) 160 via an E2 interface. The quasi-RT RIC 130 can control the underlying RAN elements (E2 nodes / network functions (NFs)) via near-real-time control loops using the E2 interface. The quasi-RT RIC 130 can monitor, suspend / stop, override, and control the E2 nodes (O-CU 140, 150, O-DU 170, and O-eNB 160) via policies. For example, the quasi-RT RIC 130 can set policy parameters regarding activated functions of the E2 nodes. Additionally, the quasi-RT RIC 130 can host xApps to implement functions such as quality of service (QoS) optimization, mobility optimization, slicing optimization, interference mitigation, load balancing, and security.

[0009] Here, the O-CU-CP 140 and the O-CU-UP 150 may be coupled to each other via an E1 interface, and may be coupled to the O-DU 170 via an F1-c interface and an F1-u interface, respectively. Furthermore, the O-RU 180 may be coupled to the O-DU 170 via an open fronthaul (OF) control (C) plane, user (U) plane, synchronization (S) plane, and management (M) plane, and may be coupled to the SMO 110 via the OF M plane.

[0010] The two types of RICs work together to optimize O-RAN. For example, the non-RT RIC 120 can provide policies, data, and AI / ML models that are implemented and used by the quasi-RT RIC 130 for RAN optimization, and the quasi-RT RIC 130 can return policy feedback (i.e., how the policies set by the non-RT RIC 120 are performing).

[0011] As mentioned above, the non-RT RIC 120 may be located within the SMO framework 110, which manages and orchestrates RAN elements. Specifically, the SMO 110 may manage and orchestrate what is referred to as the O-Ran Cloud (O-Cloud) 190. The O-Cloud 190 may be a collection of physical RAN nodes that host the RIC, O-CU, and O-DU, supporting software components (e.g., operating systems and runtime environments), and the SMO 110 itself. In other words, the SMO 110 may manage the O-Cloud 190 from within. The O2 interface may be an interface between the SMO 110 and the O-Cloud 190 on which it resides. Through the O2 interface, the SMO 110 may provide infrastructure management services (IMS) and deployment management services (DMS). Summary of the Invention [Problem to be solved by the invention]

[0012] Exemplary embodiments of the present disclosure automatically manage data transfer using at least two storages, thus enabling data transfer within a network while avoiding unnecessary signaling load, bandwidth overhead, and delays, improving network scalability. [Means for solving the problem]

[0013] According to an embodiment, an apparatus is provided, which may be configured to receive, from an rApp or other SMO function, at least one of a request to obtain configuration data of an O-RAN network element and a request to update a configuration of the O-RAN network element, and in response to receiving the request to obtain the configuration data of the O-RAN network element, obtain the configuration data using a read storage, and in response to receiving the request to update the configuration of the O-RAN network element, update the configuration of the O-RAN network element using a write storage different from the read storage based on the configuration provided in the request, wherein the write storage and the read storage may be comprised in the apparatus.

[0014] According to an embodiment, an apparatus is provided, wherein the apparatus may be configured to receive, from an rApp or other SMO function, at least one of a request to obtain configuration data of an O-RAN network element and a request to update the configuration of the O-RAN network element, and in response to receiving the request to obtain the configuration data of the O-RAN network element, obtain the configuration data using a first digital twin, and in response to receiving the request to update the configuration of the O-RAN network element, update the configuration of the O-RAN network element using a second digital twin different from the first digital twin based on the configuration provided in the request, wherein the first digital twin and the second digital twin may be comprised in the apparatus, and wherein the first digital twin and the second digital twin may comprise complete digital replicas of the O-RAN network element.

[0015] According to an embodiment, a method is provided, which may include receiving, from an rApp or other SMO function, at least one of a request to obtain configuration data of an O-RAN network element and a request to update a configuration of the O-RAN network element, in response to receiving the request to obtain the configuration data of the O-RAN network element, obtaining the configuration data using a read storage, and in response to receiving the request to update the configuration of the O-RAN network element, updating the configuration of the O-RAN network element based on the configuration provided in the request using a write storage different from the read storage, wherein the write storage and the read storage may be comprised in an apparatus that performs the method.

[0016] According to an embodiment, a method is provided that may include receiving, from an rApp or other SMO function, at least one of a request to obtain configuration data of an O-RAN network element and a request to update the configuration of the O-RAN network element, obtaining the configuration data using a first digital twin in response to receiving the request to obtain the configuration data of the O-RAN network element, and updating the configuration of the O-RAN network element using a second digital twin, different from the first digital twin, based on the configuration provided in the request in response to receiving the request to update the configuration of the O-RAN network element, wherein the first digital twin and the second digital twin may be comprised in an apparatus that performs the method, and wherein the first digital twin and the second digital twin may comprise complete digital replicas of the O-RAN network element.

[0017] According to an embodiment, there is provided a non-transitory computer-readable recording medium having stored thereon instructions executable by an apparatus, the instructions causing the apparatus to perform a method including receiving, from an rApp or other SMO function, at least one of a request to obtain configuration data of an O-RAN network element and a request to update the configuration of the O-RAN network element, in response to receiving the request to obtain the configuration data of the O-RAN network element, obtaining the configuration data using a read storage, and in response to receiving the request to update the configuration of the O-RAN network element, updating the configuration of the O-RAN network element using a write storage different from the read storage based on the configuration provided in the request, wherein the write storage and the read storage may be included in the apparatus.

[0018] 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.

[0019] The features, advantages, and significance of exemplary embodiments of the present disclosure will now be described with reference to the accompanying drawings, in which like reference numerals refer to like elements. [Brief explanation of the drawings]

[0020] [Figure 1] 1 shows the O-RAN architecture in the related art.

[0021] [Figure 2] 1 shows the architecture of a service management and orchestration framework in the related art.

[0022] [Figure 3A] 1 illustrates an exemplary flow of data in a system for managing data transfers in a network, according to one or more embodiments.

[0023] [Figure 3B]1 illustrates an exemplary flow of data in a system for managing data transfers in a network, according to one or more embodiments.

[0024] [Figure 4] 1 illustrates a flow diagram of an exemplary method for managing data transfers, according to one or more embodiments.

[0025] [Figure 5] 1 illustrates a block diagram of an example interaction between an rApp or other SMO function and RAN OAM-related functions, according to one or more embodiments.

[0026] [Figure 6A] 1 illustrates an exemplary flow of data in a system for managing data transfers in a network, according to one or more embodiments.

[0027] [Figure 6B] 1 illustrates an exemplary flow of data in a system for managing data transfers in a network, according to one or more embodiments.

[0028] [Figure 7] 1 illustrates a flow diagram of an exemplary method for obtaining configuration data using read storage, according to one or more embodiments.

[0029] [Figure 8A] A call flow is disclosed for an rApp to obtain configuration data using read storage within a RAN OAM-related function, according to one or more embodiments.

[0030] [Figure 8B] A call flow is disclosed for other SMO Functions (SMOFs) to obtain configuration data using read storage in RAN OAM related functions, according to one or more embodiments.

[0031] [Figure 9A] Disclose the call flow for an rApp to retrieve configuration data without using read storage.

[0032] [Figure 9B] Discloses the call flow for other SMO functions (SMOFs) to retrieve configuration data without using read storage.

[0033] [Figure 10] FIG. 1 illustrates a flow diagram of an example method for updating a configuration of an O-RAN network element using write storage, according to one or more embodiments.

[0034] [Figure 11A] A call flow is disclosed for an rApp to update the configuration of an O-RAN network element using write storage, according to one or more embodiments.

[0035] [Figure 11B] A call flow is disclosed for other SMO Functions (SMOFs) to update the configuration of an O-RAN network element using write storage, according to one or more embodiments.

[0036] [Figure 12A] Disclose a call flow for an rApp to update the configuration of an O-RAN network element without using write storage.

[0037] [Figure 12B] Discloses a call flow for other SMO Functions (SMOFs) to update the configuration of an O-RAN network element without using write storage.

[0038] [Figure 13] 1 illustrates a diagram of an example environment in which the systems and / or methods described herein may be implemented. DETAILED DESCRIPTION OF THE INVENTION

[0039] The following detailed description of the exemplary embodiments refers to the accompanying drawings, in which the same reference numbers in different drawings may identify the same or similar elements.

[0040] 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 the 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 description of operations provided below, it is understood that one or more operations may be omitted, one or more operations may be added, one or more operations may be performed (at least partially) concurrently, and the order of one or more operations may be permuted.

[0041] 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 intended to limit the implementation. Accordingly, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It will be understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.

[0042] Although particular combinations of features are disclosed herein, these combinations are not intended to limit the disclosure of possible implementations, and in fact many of these features may be combined in ways not specifically disclosed herein.

[0043] No element, act, or instruction used herein should be construed as critical or required unless explicitly described as such. 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." 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 A only, B only, or both A and B.

[0044] 2 shows the architecture of a service management and orchestration framework in the related art. As shown in FIG. 2, a service management and orchestration framework (SMO) 210 can include a non-real-time RIC (Non-RT RIC) 220 and RAN operation and maintenance (OAM) related functions 240. The non-RT RIC 220 provides a software framework for running applications, such as rApps.

[0045] The rApp 230 may refer to software applications configured to run on the non-RT RIC 220. The RAN OAM-related functions 240 may refer to functions within the SMO 210 related to operations and maintenance. The one or more O-RAN network elements 250 may refer to O-RAN network elements within the O-RAN architecture. For example, the one or more O-RAN network elements 250 may include an O-RAN Centralized Unit Control Plane (O-CU-CP), an O-RAN Centralized Unit User Plane (O-CU-UP), an O-RAN Distributed Unit (O-DU), etc.

[0046] The one or more rApps 230 may be configured to perform read (operations to retrieve data) and write (operations to update data) Configuration Management (CM) configuration data operations to one or more O-RAN network elements 250. For example, the one or more rApps 230 may read / write CM configuration data from / to one or more O-RAN network elements 250 via an R1 service API of an R1 service 250 that exposes the Configuration Management (CM) service provided by the RAN OAM-related functions 240 in the SMO 210.

[0047] In the related art, to perform read and write operations, one or more rApps 230 can send requests to the RAN OAM-related functions 240 via the R1 interface, and the RAN OAM-related functions 240 can simply forward the requests directly to one or more O-RAN network elements 250 via the O1 or Open Fronthaul (O-FH) interface to retrieve (read) or modify (write) Managed Object Instance (MOI) attributes from / to one or more O-RAN network elements 250 as requested.

[0048] In this regard, the above-described approach for performing read and write operations in the related art may have the following problems: Because the RAN OAM-related function 240 in the SMO 210 simply and transparently forwards information to and from the rApps, one or more rApps 230 essentially directly access one or more O-RAN network elements 250 for each MOI read and write request in a stateless, directly mediated manner. Accordingly, as the system scales up and the number of rApps and O-RAN network elements increases, many rApps may attempt to read and write CM configuration data simultaneously, which may easily overload the R1, O1, and O-FH interfaces, resulting in significant message drops and unacceptable signaling delays.

[0049] Accordingly, the systems, methods, devices, etc. provided in the exemplary embodiments of the present disclosure automatically manage data transfer using at least two storages.

[0050] According to an embodiment, to perform a read operation to obtain configuration data of an O-RAN network element, the system may use a read storage to obtain the configuration data. Further, to perform a write operation to update the configuration of the O-RAN network element, the system may use a write storage different from the read storage to update the configuration of the O-RAN network element based on the configuration provided in the request.

[0051] Ultimately, exemplary embodiments of the present disclosure automatically manage data transfer using at least two storages, thereby enabling data to be transferred within a network while avoiding unnecessary signaling load, bandwidth overhead, and delays, improving network scalability.

[0052] The features, advantages, and significance of the above exemplary embodiments are intended to be only a part of the present disclosure and are not intended to be exhaustive or to limit the scope of the present disclosure.

[0053] Further descriptions of the features, components, configuration, operation, and implementation of the threshold adjustment system of the present disclosure, according to one or more embodiments, are provided below.

[0054] System Architecture FIG. 3A illustrates an exemplary flow of data in a system 300A for managing data transfers in a network, according to one or more embodiments.

[0055] As shown in FIG. 3A , the system 300A may include an SMO 360, a non-RT RIC 350, an R1 service 340, an rApp 310, RAN OAM-related functions 320 including a read storage 322 and a write storage 324, and an O-RAN network element 330.

[0056] In step 1, to perform a write operation to update the O-RAN network element 330, the rApp 310 may send configuration data (hereinafter, “write data”) that the O-RAN network element 330 should be updated based on the R1 configuration change write operation to the RAN OAM-related function 320, and the write data may be stored in the write storage 324.

[0057] In step 2, when the write data is received and stored in the write storage 324, the RAN OAM-related function 320 retrieves the write data and updates the O-RAN network element 330 based on the write data stored in the write storage 324, so that the write data is retrieved into the O-RAN network element 330.

[0058] The above process using write storage 324 allows rApp 310 to simply provide write data to RAN OAM related function 320 via the R1 service API of R1 service 340 without having to wait for the update to complete, and be free to perform other tasks while the write data is being taken into O-RAN network element 330 and O-RAN network element 330 is updated based on the write data. As a result, the above process prevents too many rApps or other SMO functions from being held up simultaneously waiting for their update requests to complete, which could lead to platform overload in the event of a signaling spike.

[0059] In step 3, once the O-RAN network element 330 has been updated based on the write data, the RAN OAM-related function 320 may update the read storage 322 so that the data stored in the read storage 322 correctly reflects the data in the updated O-RAN network element 330. In this regard, since the RAN OAM-related function 320 has already stored the write data (based on which the O-RAN network element 330 was updated) in the write storage 324, the RAN OAM-related function 320 may update the read storage 322 based on the write data stored in the write storage 324.

[0060] The above process allows the read storage 322 to be updated so that the data stored in the read storage 322 correctly reflects the configuration in the O-RAN network element 330, without having to directly communicate with the O-RAN network element to retrieve the configuration again from the O-RAN network element 330. This avoids unnecessary signaling load, bandwidth overhead, and delays associated with communicating directly with the O-RAN network element 330. As a result, the above process reduces the processing and memory load on the SMO and RIC platforms and improves network scalability.

[0061] According to an embodiment, in addition to step 3, in step 3.5, the RAN OAM related function 320 may further update the read storage 322 if there are any configuration updates in the O-RAN network element by other entities outside the SMO 360, to ensure that the data stored in the read storage 322 correctly reflects the configuration in the O-RAN network element 330. According to an embodiment, the RAN OAM related function 320 may update the read storage 322 by periodically checking the latest configuration in the O-RAN network element 330 or by being notified by the O-RAN network element in case of a configuration change by other entities outside the SMO.

[0062] In step 4, to perform a read operation to obtain data from the O-RAN network element 330, the rApp 310 can obtain data (hereinafter "read data") from the read storage 322 in the RAN OAM-related function 320 based on the R1 configuration data read operation.

[0063] The above process using the read storage 322 allows the rApp 310 to obtain read data from the RAN OAM related function 320 without having to communicate with the O-RAN network element 330 to fetch the data directly from the O-RAN network element, thereby avoiding unnecessary signaling load, bandwidth overhead, and delays associated with communicating with the O-RAN network element 330. As a result, the above process reduces the processing and memory load on the SMO and RIC platforms and improves network scalability.

[0064] According to an embodiment, in step 4.5, if the read data that rApp310 intends to obtain is not stored in read storage 322, rApp310 can obtain the read data directly from O-RAN network element 330.

[0065] According to an embodiment, when an rApp attempts to retrieve current configuration data from an O-RAN network element based on an R1 configuration data read operation, whether the read data is provided from a read storage within the RAN OAM-related function or is newly fetched from the O-RAN network element by the RAN OAM-related function via the O1 / O-FH interface is determined by the RAN OAM-related function. The rApp that sends the R1 configuration data read request simply retrieves the current configuration data in the O-RAN network element after sending the R1 configuration read request, regardless of whether the configuration data is obtained from a read storage within the RAN OAM-related function or is fetched from the O-RAN network element by the RAN OAM-related function via the O1 / O-FH interface.

[0066] From the above, it can be seen that the above process involving two separate storages (read storage 322 and write storage 324) allows read data to be obtained from, and write data to, the O-RAN network element 330 without interfering with each other.

[0067] For example, a first rApp may send write data to write storage 324 during step 1. However, a second rApp may obtain read data from read storage 322 during step 4 before the read storage is updated based on the write data during steps 2 and 3.

[0068] In this regard, because the read data obtained by the second rApp is data stored in read storage 322 and not data stored in write storage 324, the read data obtained by the second rApp will be data that correctly reflects the actual configuration data in the (currently valid) O-RAN network element 330 and not write data that has not yet been applied to the O-RAN network element 330.

[0069] Furthermore, because the write data is sent to and stored in the write storage 324 rather than the read storage 322, the write data does not inadvertently overwrite data in the read storage 322 (which correctly reflects the data in the O-RAN network element 330). Accordingly, it will be appreciated that the rApp 310 may not have access rights to write (send) data to the read storage 322.

[0070] It can be understood that the configuration shown in FIG. 3A is simplified for illustrative purposes and does not limit the scope of the present disclosure in any way. Specifically, in practice, the number of rApps 310 and the number of O-RAN network elements 330 can be any number. Furthermore, the number labels of steps 1 through 4 are for labeling purposes only and do not limit the order. For example, the rApp 310 may first perform a read operation and step 4, and then perform a write operation and step 1. Furthermore, the arrows depicted in FIG. 3A do not represent the actual O-RAN interfaces (virtual / physical) between the different elements in the diagram, but rather represent the flow of configuration data, i.e., read / write data, across the different elements in the diagram. The actual O-RAN interfaces are represented by dotted boxes surrounding the O-RAN interface names.

[0071] Additionally, it will be understood that while the examples described in this disclosure are provided in the context of a non-RT RIC, they are equally applicable to a quasi-RT RIC, in which case the R1 interface would be the quasi-RT RIC API and the O1 / O-FH interface would be the E2 interface.

[0072] FIG. 3B illustrates an exemplary flow of data in a system 300B for managing data transfers in a network, according to one or more embodiments.

[0073] As shown in FIG. 3B, the configuration of system 300B may be similar to the configuration of system 300A of FIG. 3A, with operations related to read and write data being performed by other SMO functions 370 via RAN OAM-related service APIs / RAN NF CM / PM / FM service APIs instead of rApp 310 via R1 interface / R1 service APIs and R1 services 340.

[0074] Accordingly, it will be appreciated that other SMO functions 370 may perform write operations to update the O-RAN network elements 330, as well as read operations to retrieve data from the O-RAN network elements 330, in a manner similar to rApp 310.

[0075] Exemplary Operations for Managing Data Transfer in the Present Disclosure Hereinafter, some exemplary operations of the present disclosure will be described with reference to FIGS.

[0076] 4 illustrates a flow diagram of an example method 400 for managing data transfers, according to one or more embodiments. One or more operations in method 400 may be performed by at least one processor.

[0077] 4, in operation S410, the at least one processor may be configured to receive at least one of a request to obtain configuration data of an O-RAN network element and a request to update a configuration of the O-RAN network element. It will be understood that a request to obtain configuration data of an O-RAN network element may refer to a request to perform a read operation. Similarly, it will be understood that a request to update a configuration of an O-RAN network element may refer to a request to perform a write operation. According to an embodiment, the request to obtain configuration data of an O-RAN network element and the request to update a configuration may be received from an rApp or other SMO function.

[0078] According to an embodiment, the configuration data may include configuration data of the O-RAN network element that the rApp or other SMO function wishes to retrieve for a read operation. For example, the configuration data may include CM configuration data of the O-RAN network element that the rApp wishes to read. According to an embodiment, the request to update the configuration of the O-RAN network element may include the configuration that the rApp or other SMO function wishes to update the O-RAN network element for a write operation. For example, the request may include CM configuration data that the rApp wishes to write to the O-RAN network element. The method then proceeds to operation S420.

[0079] At operation S420, in response to receiving a request to retrieve configuration data of the O-RAN network element, the at least one processor may be configured to retrieve the configuration data using a read storage. According to an embodiment, the read storage may be included in the SMO. According to an embodiment, the read storage may be configured to store data of the O-RAN network element to be retrieved for the read operation. For example, the read storage may be configured to store CM configuration data of the O-RAN network element that may be retrieved for the read operation. An example operation of retrieving configuration data using the read storage is described below with reference to FIG. 7. The method then proceeds to operation S430.

[0080] At operation S430, in response to receiving a request to update the configuration of the O-RAN network element, the at least one processor may be configured to update the configuration of the O-RAN network element using write storage based on the configuration provided in the request. According to an embodiment, the write storage may be included in the SMO. According to an embodiment, the write storage may be different from the read storage. According to an embodiment, the write storage may be configured to store data based on which the O-RAN network element is updated for the write operation. For example, the write storage may be configured to store CM configuration data to be written to the O-RAN network element. Example operations for updating the configuration of the O-RAN network element using write storage based on the configuration provided in the request are described below with reference to FIG. 10 .

[0081] Upon performing operations S420 and / or S430, method 400 may end. Alternatively, method 400 may return to operation S410, such that at least one processor may be configured to repeatedly perform receiving at least one of the requests (at operation S410), obtaining the configuration data (at operation S420), and / or updating the configuration of the O-RAN network element (at operation S430) for at least a predetermined period of time. For example, the at least one processor may continuously (or periodically) receive requests to obtain configuration data and then resume receiving at least one of the requests (operation S410) and obtaining the configuration data (operation S420).

[0082] Further, for example, the at least one processor may receive (at operation S410) a request to obtain configuration data and obtain (at operation S420) the configuration data. The at least one processor may then receive (at operation S410) a request to update a configuration of the O-RAN network element and update (at operation S430) the configuration of the O-RAN network element.

[0083] According to embodiments, in addition to receiving a request to obtain configuration data of an O-RAN network element, the at least one processor may be configured to receive another request to obtain configuration data of another O-RAN network element. For example, the at least one processor may be configured to receive a request to obtain configuration data of a first O-RAN network element and a request to obtain configuration data of a second O-RAN network element that is different from the first O-RAN network element. Similarly, according to embodiments, in addition to receiving a request to update the configuration of an O-RAN network element, the at least one processor may be configured to receive another request to update the configuration of another O-RAN network element. For example, the at least one processor may be configured to receive a request to update the configuration of a first O-RAN network element and a request to update the configuration of a second O-RAN network element that is different from the first O-RAN network element. The above requests may be received from the same or different rApps or other SMO functions.

[0084] According to an embodiment, two or more of the above requests to different O-RAN network elements may be bundled into a single Application Programming Interface (API) call.

[0085] For example, as shown in Figure 5, which illustrates a block diagram of an example interaction between an rApp or other SMO function and RAN OAM-related functions, according to one or more embodiments, a request to obtain configuration data for a first O-RAN network element (Request 1) and a request to obtain configuration data for a second O-RAN network element (Request 2) may be bundled into a single application programming interface (API) call (API Call 1). Similarly, a request to update the configuration of a first O-RAN network element (Request 3) and a request to update the configuration of a second O-RAN network element (Request 4) may be bundled into a single application programming interface (API) call (API Call 2).

[0086] The above configuration can further reduce the signaling load on the interface between an rApp or other SMO function and a RAN OAM-related function, for example, the signaling load on the R1 interface between an rApp and a non-RT RIC.

[0087] According to an embodiment, the read storage and write storage may be configured to store all CM configuration data (Managed Object Instance (MOI) attributes) of all O-RAN network elements in the network. According to an embodiment, the read storage and write storage may be configured to store at least the CM configuration data (MOI attributes) most frequently accessed by rApps in the network to reduce size and improve efficiency. According to an embodiment, the read storage and write storage may be replaced with digital twins (DTs), which are complete digital replicas of the O-RAN network element, including not only the O-RAN network element configuration but also all other execution states in the protocol stack of the O-RAN network element / function. In this case, the read storage is replaced with a DT1 that replicates the current state of the O-RAN network element, and the write storage is replaced with a DT2 that represents the future state of the O-RAN network element in the digital domain assuming a given configuration change is applied.

[0088] For example, refer to FIG. 6A, which illustrates another exemplary flow of data in a system 600A for managing data transfers in a network, according to one or more embodiments. As shown in FIG. 6A, the configuration and steps associated with the system 600A may be similar to those associated with the system 300A described above in connection with FIG. 3A. However, the read storage 322 is now replaced with a DT1 622, which is a replica of the O-RAN network element 630 for configuration data read operations. Similarly, the write storage 324 is now replaced with a DT2 624, which represents the future state of the O-RAN network element 630 (assuming a given configuration is applied), for configuration change write operations. The DT1 622, which represents a replica of the current state of the O-RAN network element 630, is still updated to represent the true current configuration of the O-RAN network element 630 based on steps 3 and 3.5 described above in connection with FIG. 3A. The configuration in DT2 624 representing the future state of the O-RAN network element 630 is still loaded into the O-RAN network element 630 based on step 2 described above in connection with FIG. 3A.

[0089] FIG. 6B illustrates an exemplary flow of data in a system 600B for managing data transfers in a network, according to one or more embodiments.

[0090] As shown in FIG. 6B, the configuration of system 600B may be similar to the configuration of system 600A of FIG. 6A, with operations related to read and write data being performed by other SMO functions 670 via RAN OAM-related service APIs / RAN NF CM / PM / FM service APIs instead of rApp 610 via R1 interface / R1 service APIs and R1 services 640.

[0091] Accordingly, it will be appreciated that other SMO functions 670 may perform write operations to update the O-RAN network element 630 and read operations to retrieve data from the O-RAN network element 630 in a manner similar to rApp 610.

[0092] Exemplary Operations for Obtaining Configuration Data Using Read Storage in the Present Disclosure 7 shows a flow diagram of an example method 700 for obtaining configuration data using read storage, according to one or more embodiments. One or more operations of method 700 may be part of operations S410 and S420 of method 400 and may be performed by at least one processor.

[0093] 7, at operation S710, the at least one processor may be configured to receive a request to obtain configuration data for an O-RAN network element. It will be appreciated that the request to obtain configuration data for the O-RAN network element may be received from an rApp or other SMO function in a manner similar to that described above in connection with method 400. According to an embodiment, the read storage may be synchronized with the network before operation S710 so that the read storage correctly reflects the current configuration of the O-RAN network element. The method then proceeds to operation S720.

[0094] At operation S720, the at least one processor may be configured to determine whether the configuration data is stored in the read storage. Accordingly, based on determining that the configuration data is stored in the read storage, the at least one processor may determine that there is no need to obtain the configuration data from the O-RAN network element, and the method proceeds to operation S730. On the other hand, based on determining that the configuration data is not stored in the read storage, the at least one processor may determine that there is a need to obtain the configuration data from the O-RAN network element, and the method proceeds to operation S740.

[0095] At operation S730, the at least one processor may be configured to send the configuration data from the read storage to the rApp or other SMO function. For example, the at least one processor may be configured to send the CM configuration data from the read storage to the rApp over the R1 interface without having to obtain the CM configuration data from an O-RAN network element over the O1 or O-FH interface.

[0096] At operation S740, the at least one processor may be configured to obtain configuration data from the O-RAN network element and send it to the rApp or other SMO function. For example, the at least one processor may be configured to obtain CM configuration data from the O-RAN network element over an O1 or O-FH interface and send the CM configuration data to the rApp over an R1 interface.

[0097] Accordingly, the above process for obtaining configuration data using read storage allows an rApp or other SMO function to obtain configuration data without having to communicate with an O-RAN network element, thereby avoiding unnecessary signaling load, bandwidth overhead, and delays associated with communicating with an O-RAN network element. As a result, the above process reduces the processing and memory load on the SMO and RIC platforms and improves network scalability.

[0098] O-RAN interface message flow for reading configuration data FIG. 8A discloses a call flow for an rApp to obtain configuration data using read storage within a RAN OAM-related function, according to one or more embodiments.

[0099] 8A , the RAN-OAM-related function 802 may first synchronize the read-storage with the O-RAN network element to obtain the current MOI attributes (i.e., CM configuration data) of the network element 803. To synchronize the read-storage with the network, the RAN-OAM-related function 802 may communicate with the O-RAN network element 803 over the O1 interface using the network management protocols NETCONF read-config, edit-config create, and replace or delete. Once the current MOI attributes of the O-RAN network element 803 have been obtained, the RAN-OAM-related function 802 may store the retrieved configuration data in the read-storage such that the configuration data of the O-RAN network element 803 stored in the read-storage correctly reflects the current configuration of the O-RAN network element 803.

[0100] The RAN-OAM related function 802 may then receive a configuration read request from the rApp 801 requesting to obtain (read) the configuration of the O-RAN network element 803. The configuration read request may include data such as the rApp id and query Criteria related to the request and is received over the R1 interface.

[0101] In response, the RAN-OAM related function 802 may perform authentication (authorization: AuthZ) and validation on the received request.

[0102] Once the received request is authenticated and validated, the RAN-OAM related function 802 can determine whether the configuration data of the requested O-RAN network element 803 is stored in read storage.

[0103] If the configuration data of the requested O-RAN network element 803 is stored (present) in the read storage, the RAN-OAM related function 802 can send a configuration read response to the rApp 801 providing the requested configuration data of the target O-RAN network element 803. The configuration read response can include data such as ConfigurationData related to the request and can be sent over the R1 interface.

[0104] If the requested configuration data of the target O-RAN network element 803 is not stored in the read storage, the RAN-OAM related function 802 may obtain the requested configuration of the O-RAN network element 803 from the O-RAN network element 803. To obtain the requested configuration data of the O-RAN network element 803 from the O-RAN network element 803, the RAN-OAM related function 802 may communicate with the O-RAN network element 803 over the O1 interface using the network management protocol NETCONF read-config. Once the requested configuration data of the O-RAN network element 803 is obtained from the O-RAN network element 803, the RAN-OAM related function 802 may send a Read Configuration Response to the rApp 801 in the same manner as described above.

[0105] FIG. 8B discloses a call flow for other SMO functions (SMOFs) to obtain configuration data using read storage in RAN OAM-related functions, according to one or more embodiments.

[0106] As shown in FIG. 8B, the call flow shown in FIG. 8B may be similar to the call flow shown in FIG. 8A, with the operations related to obtaining configuration data being performed by another SMOF 804 via the RAN NF CM service API instead of the rApp 801 via the R1 interface.

[0107] Accordingly, it will be appreciated that other SMOFs 804 may perform read operations to obtain configuration data from O-RAN network elements 803 in a similar manner as rApp 801.

[0108] FIG. 9A discloses the call flow for an rApp to obtain configuration data without using read storage.

[0109] As shown in FIG. 9A, the disclosed call flow for obtaining configuration data without using read storage (in certain implementations of RAN OAM-related functions, there may be no read storage at all) may be similar to the call flow for obtaining configuration data using read storage described above in connection with FIG. 8A.

[0110] However, as shown in FIG. 9A, in this case, when the RAN-OAM related function 902 receives, authenticates, and validates the Read Configuration Request, it retrieves the requested configuration data of the target O-RAN network element 903 directly from the O-RAN network element 903 and sends a Read Configuration Response to the rApp 901 with the configuration data retrieved from the O-RAN network element.

[0111] It will be appreciated that in the above process, when rApp 901 attempts to obtain the requested configuration data of O-RAN network element 903, the requested configuration data may need to be fetched from the O1 interface by the RAN OAM related functions every time, which will increase the signaling load, bandwidth overhead, and latency as the network scales up and more rApps and O-RAN network elements operate in the network.

[0112] FIG. 9B discloses the call flow for other SMO functions (SMOFs) to obtain configuration data without using read storage.

[0113] As shown in FIG. 9B, the call flow shown in FIG. 9B may be similar to the call flow shown in FIG. 9A, with the operations related to obtaining configuration data being performed by another SMOF 904 via the RAN NF CM service API instead of the rApp 901 via the R1 interface.

[0114] Accordingly, it will be appreciated that other SMOFs 904 may perform read operations to obtain configuration data from O-RAN network elements 903 in a manner similar to rApp 901.

[0115] Example Operations for Updating Configuration of an O-RAN Network Element Using Write Storage of the Present Disclosure 10 illustrates a flow diagram of an example method 1000 for updating a configuration of an O-RAN network element using write storage, according to one or more embodiments. One or more operations of method 1000 may be part of operations S410 and S430 of method 400 and may be performed by at least one processor.

[0116] 10 , at operation S1010, at least one processor may be configured to receive a request to update the configuration of the O-RAN network element. It will be appreciated that the request to update the configuration of the O-RAN network element may be received from an rApp or other SMO function in a manner similar to that described above in connection with method 400. The method then proceeds to operation S1020.

[0117] At operation S1020, the at least one processor may be configured to receive a configuration. According to an embodiment, the request received from the rApp or other SMO function may include a configuration based on which the configuration of the O-RAN network element is to be updated. For example, CM configuration data may be received from the rApp via an R1 interface. The method then proceeds to operation S1030.

[0118] In operation S1030, the at least one processor may be configured to store the received configuration in a write storage, after which the method proceeds to operation S1040.

[0119] At operation S1040, the at least one processor may be configured to send a first write response to the rApp or other SMO function. According to an embodiment, the at least one processor may be configured to send the first write response to the rApp or other SMO function after storing the received configuration in write storage. According to an embodiment, the first write response may be configured to notify the rApp or other SMO function that the received configuration has been stored in write storage. The method then proceeds to operation S1050.

[0120] At operation S1050, the at least one processor may be configured to update a configuration of the O-RAN network element based on the received configuration stored in the write storage. For example, CM configuration data of the O-RAN network element may be updated based on CM configuration data stored in the write storage via the O1 or O-FH interface (i.e., CM configuration data received from the rApp), such that the CM configuration data stored in the write storage is written to the O-RAN network element via the O1 or O-FH interface.

[0121] As a further example, the at least one processor may perform a ModifyMOI operation on the O1 or O-FH interface to update the configuration of the O-RAN network element based on the received configuration (writing the received configuration to the O-RAN network element). Once the ModifyMOI operation is complete and the O-RAN network element is updated, the at least one processor may receive a ModifyMOI response from the O-RAN network element indicating that the configuration changes were successfully received and applied at the O-RAN network element. The method then proceeds to operation S1060.

[0122] At operation S1060, the at least one processor may be configured to send a second write notification to the rApp or other SMO function. According to an embodiment, the at least one processor may be configured to send the second write notification to the rApp or other SMO function after the configuration of the O-RAN network element is updated based on the received configuration stored in the write storage. For example, the at least one processor may be configured to send the second write notification to the rApp after receiving a ModifyMOI response from the O-RAN network element.

[0123] According to an embodiment, the second write notification may be configured to notify the rApp or other SMO function that the configuration of the O-RAN network element has been updated based on the received configuration stored in the write storage, after which the method proceeds to operation S1070.

[0124] At operation S1070, the at least one processor may be configured to update the read storage. According to an embodiment, the at least one processor may be configured to update the read storage based on the received configuration stored in the write storage. For example, the CM configuration data of the O-RAN network element stored in the read storage may be updated based on the CM configuration data stored in the write storage (based on which the configuration of the O-RAN network element has already been updated), such that the CM configuration data stored in the read storage is updated to correctly reflect the updated O-RAN network element, without the need to communicate with the O-RAN network element over the O1 and O-FH interfaces.

[0125] According to an embodiment, the at least one processor may be configured to update the read storage based on the received configuration stored in the write storage after the configuration of the O-RAN network element is updated based on the received configuration stored in the write storage. For example, the at least one processor may be configured to update the read storage based on the received configuration stored in the write storage after receiving a ModifyMOI response from the O-RAN network element.

[0126] According to an embodiment, the at least one processor may further be configured to update the read storage based on updated O-RAN network elements. According to an embodiment, the read storage may be periodically updated based on updated O-RAN network elements to ensure that the data stored in the read storage correctly reflects the data in the O-RAN network elements. For example, the read storage may be periodically updated based on updated O-RAN network elements via the O1 or O-FH interface.

[0127] Accordingly, the above process for updating an O-RAN network element using write storage allows an rApp or other SMO function to simply send the configuration without having to wait for the update to complete, and is free to perform other tasks while the configuration of the O-RAN network element is being updated based on the sent configuration. As a result, the above process prevents too many rApps or other SMO functions from being held up simultaneously waiting for their respective update requests to complete, which could lead to platform overload in the event of a signaling spike.

[0128] Furthermore, the above process of updating the read storage based on the configuration stored in the write storage enables the data stored in the read storage (used for the read operation) to correctly reflect the data in the O-RAN network element without directly communicating with the O-RAN network element, thereby avoiding unnecessary signaling load, bandwidth overhead, and delays associated with directly communicating with the O-RAN network element. As a result, the above process further reduces the processing and memory load on the SMO and RIC platforms and improves network scalability.

[0129] Furthermore, the above process for retrieving configuration data and updating the configuration of an O-RAN network element using two separate storages allows data to be retrieved / sent from / to the O-RAN network element without interfering with each other.

[0130] O-RAN interface message flow for writing configuration data FIG. 11A discloses a call flow for an rApp to update the configuration of an O-RAN network element using write storage, according to one or more embodiments.

[0131] 11A, the RAN-OAM related function 1102 may receive a configuration change write request from the rApp 1101 requesting to update (write) configuration attributes of the target O-RAN network element 1103. This request may include the rApp id and configuration change information associated with the request and may be received over the R1 interface.

[0132] In response, the RAN-OAM related function 1102 may perform authentication (AuthZ) and validation on the received request.

[0133] Once the received request has been authenticated (authorized) and validated, the RAN-OAM related function 1102 can modify the write storage so that the configuration attributes of the O-RAN network element 1103 to be updated are stored in the write storage.

[0134] Once the write storage is modified, the RAN-OAM related function 1102 can send a configuration change writing response to the rApp 1101 indicating that the request has been accepted and the configuration change has been stored in the write storage, but that the actual process to update the O-RAN network element 1103 is still pending. The configuration change writing response can include the return code 202:ACCEPTED in the case of an HTTP / REST API operation.

[0135] Then, the RAN-OAM related function 1102 sends the network management protocol NETCONF edit-config create, replace, or delete, and RPC-reply <ok>or<rpc.error> The O-RAN network element 1103 may be updated based on the stored configuration attributes by communicating with the O-RAN network element 803 over the O1 interface utilizing the O1 interface. In response, the configuration / MOI attributes of the network element 1103 may be modified (updated) based on the configuration attributes stored in the write storage.

[0136] Once the O-RAN network element 1103 is updated, the RAN-OAM related function 1102 can send a configuration change notification to the rApp 1101 indicating that the O-RAN network element 1103 was successfully updated and that the provided configuration changes are effective in the network. The configuration change notification may include a status indicating that the operation on the O1 interface is completed, along with result information indicating which configuration attributes were successfully configured in the O-RAN network element 1103, which is not configured in the case of a partial success scenario.

[0137] FIG. 11B discloses a call flow for other SMO Functions (SMOFs) to update the configuration of an O-RAN network element using write storage, according to one or more embodiments.

[0138] As shown in FIG. 11B, the call flow shown in FIG. 11B may be similar to the call flow shown in FIG. 11A, with the operations related to updating the configuration of the O-RAN network element being performed by another SMOF 1104 via the RAN NF CM service API instead of the rApp 1101 via the R1 interface.

[0139] Accordingly, it will be appreciated that other SMOFs 1104 may perform write operations to update the configuration of the O-RAN network element 1103 in a similar manner to the rApp 1101.

[0140] FIG. 12A discloses a call flow for an rApp to update the configuration of an O-RAN network element without using write storage.

[0141] As shown in Figure 12A, the call flow for updating the configuration of an O-RAN network element 1203 without using write storage may be similar to the call flow for updating the configuration of an O-RAN network element using write storage described above in connection with Figure 11A. However, as shown in Figure 12A, in this case, once the RAN-OAM-related function 1202 receives, authenticates, and validates the configuration change write request, the RAN-OAM-related function 1202 may directly update the O-RAN network element 1203 based on the received configuration attributes. Once the O-RAN network element 1203 is updated, the RAN-OAM-related function 1202 may send a configuration change write response to the rApp 1201 indicating that the O-RAN network element 1203 was successfully updated and that the provided configuration attributes are valid in the network. The configuration change write response may include the response code 200:OK in the case of an HTTP / REST API operation.

[0142] It will be appreciated that in the above process, the RIC may block rApp 1201 and hold the context of the configuration write request until all O-RAN network elements 1203 have been updated. Furthermore, rApp 1201 may not be aware of the update process of the O-RAN network elements 1203 until the update is complete and a configuration change write response is received. Accordingly, as the network scales up and more rApps and O-RAN network elements operate within the network, the RIC may block and hold too many rApps and contexts simultaneously while waiting for the update process to complete on the O1 and O-FH interfaces, which may lead to platform overload and signaling spikes.

[0143] FIG. 12B discloses a call flow for other SMO Functions (SMOFs) to update the configuration of an O-RAN network element without using write storage.

[0144] As shown in FIG. 12B, the call flow shown in FIG. 12B may be similar to the call flow shown in FIG. 12A, with the operations related to updating the configuration of the O-RAN network element being performed by another SMOF 1204 via the RAN NF CM service API instead of the rApp 1201 via the R1 interface.

[0145] Accordingly, it will be appreciated that other SMOFs 1204 may perform write operations to update the configuration of the O-RAN network element 1203 in a similar manner to the rApp 1201.

[0146] Example Implementation 13 illustrates a diagram of an example environment 1300 in which the systems and / or methods described herein may be implemented. As shown in FIG. 13, environment 1300 may include a device 1310, a platform 1320, and a network 1330. The devices in environment 1300 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections. In some embodiments, any of the functions and operations described with reference to FIGS. 3-12 above may be performed by any combination of the elements illustrated in FIG. 13.

[0147] According to embodiments, the systems described herein may be stored, hosted, or deployed on a cloud computing platform 1320. In this regard, device 1310 may include devices, systems, equipment, etc. utilized by users (e.g., users on a marketing team, users on a network planning team, etc.) to access the system. In this case, device 1310 may include one or more devices capable of receiving, generating, storing, processing, and / or providing information related to platform 1320.

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

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

[0150] Cloud computing environment 1322 includes an environment that hosts platform 1320. Cloud computing environment 1322 can provide services such as computation, software, data access, and storage, without requiring end-user (e.g., user device 1310) knowledge of the physical location and configuration of the systems and / or devices that host platform 1320. As shown, cloud computing environment 1322 may include a group of computing resources 1324 (collectively referred to as “computing resources 1324” and individually referred to as “computing resource 1324”).

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

[0152] As further shown in FIG. 13 , computing resources 1324 include a group of cloud resources, such as one or more applications ("APPs") 1324-1, one or more virtual machines ("VMs") 1324-2, virtualized storage ("VSs") 1324-3, and one or more hypervisors ("HYPs") 1324-4. While the present exemplary embodiment relates to virtualized network functions, it is understood that one or more other embodiments may be implemented in at least one of, but not limited to, containers, cloud-native services, one or more container platforms, and the like. For example, in one or more other exemplary embodiments, any of the above components may be software-based components deployed or hosted on a server cluster, such as, for example, a hybrid cloud server, a data center server, or the like. The software-based components may be containerized and deployed and controlled by one or more addressable machines called "nodes" that operate or execute the containerized O-RAN network elements. In this regard, a server cluster may include at least one master node and multiple worker nodes, where the master node(s) control and manage a set of associated worker nodes.

[0153] Applications 1324-1 include one or more software applications that may be provided to or accessed by user device 1310. Applications 1324-1 may obviate the need to install and run software applications on user device 1310. For example, applications 1324-1 may include software associated with platform 1320 and / or any other software that may be provided via cloud computing environment 1322. In some implementations, one application 1324-1 may send information to or receive information from one or more other applications 1324-1 via virtual machine 1324-2.

[0154] Virtual machine 1324-2 includes a software-implemented machine (e.g., a computer) that executes programs like a physical machine. Virtual machine 1324-2 can be either a system virtual machine or a process virtual machine, depending on the application and the degree to which virtual machine 1324-2 represents an actual machine. A system virtual machine can provide a complete system platform that supports the execution of a complete operating system (“OS”). A process virtual machine can execute a single program and support a single process. In some implementations, virtual machine 1324-2 can run on behalf of a user (e.g., user device 1310) and manage the infrastructure of cloud computing environment 1322, such as data management, synchronization, or long-term data transfer.

[0155] Virtualized storage 1324-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 1324. In some implementations, in the context of 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. The 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 can enable performance optimization of storage usage, server consolidation, and / or non-disruptive file migration.

[0156] The hypervisor 1324-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 1324. The hypervisor 1324-4 may provide a virtual operating platform for the guest operating systems and may manage the execution of the guest operating systems. Multiple instances of various operating systems may share virtualized hardware resources.

[0157] Network 1330 may include one or more wired and / or wireless networks. For example, network 1330 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.

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

[0159] Various aspects of the embodiments 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 the implementations.

[0160] Some embodiments may relate to systems, methods, and / or computer-readable media at any possible level of technical detail. Furthermore, one or more of the above components described above 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 computer-readable non-transitory storage medium(s) having computer-readable program instructions for causing a processor to perform operations.

[0161] A computer-readable storage medium may be any tangible device capable of retaining and storing instructions for use by an instruction-execution device. A 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 disk (DVD), memory sticks, floppy disks, mechanically encoded devices such as punch cards or ridge structures in grooves on which instructions are recorded, and any suitable combination of the foregoing. Computer-readable storage media as used herein should not be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., light pulses passing through a fiber optic cable), or electrical signals transmitted through wires.

[0162] The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to each computing / processing device or to an external computer or storage device over 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.

[0163] 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, integrated circuit configuration data, 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 stand-alone 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) can execute computer-readable program instructions by utilizing state information of the computer-readable program instructions to personalize the electronic circuitry to perform aspects or operations.

[0164] 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, executed by the processor of the computer or other programmable data processing apparatus, form 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, such that a computer-readable storage medium having instructions stored therein comprises 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.

[0165] The computer-readable program instructions may also be loaded into a computer, other programmable data processing apparatus, or other device, causing the computer, other programmable apparatus, or other device to perform a series of operational steps to create 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 one or more blocks of the flowcharts and / or block diagrams.

[0166] The flowcharts and block diagrams in the figures 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 the flowcharts or block diagrams may represent a portion of a microservice(s) module, segment, or instruction, which comprises one or more executable instructions for implementing the specified logical function(s). The methods, computer systems, and computer-readable media may include additional, fewer, different, or differently arranged blocks than those shown in the figures. In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may actually be executed concurrently or substantially concurrently, or the blocks may sometimes 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 special-purpose hardware-based system that performs the specified functions or actions or executes a combination of special-purpose hardware and computer instructions.

[0167] 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 intended to limit 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.

[0168] Various further respective aspects and features of embodiments of the present disclosure can be defined by the following clauses. Item 1: An apparatus that may be configured to receive, from an rApp or other SMO function, at least one of a request to obtain configuration data of an O-RAN network element and a request to update the configuration of the O-RAN network element; in response to receiving the request to obtain the configuration data of the O-RAN network element, obtain the configuration data using a read storage; and in response to receiving the request to update the configuration of the O-RAN network element, update the configuration of the O-RAN network element using a write storage different from the read storage based on the configuration provided in the request, wherein the write storage and the read storage may be included in the apparatus. Item 2: The device described in Item 1, wherein the device may be configured to obtain configuration data using read storage by determining whether configuration data is stored in the read storage; and in response to determining that the configuration data is stored in the read storage, sending the configuration data from the read storage to an rApp or other SMO function. Item 3: The device of item 1 or 2, wherein the device may be configured to: receive a configuration from an rApp or other SMO function; store the received configuration in a write storage; and update the configuration of the O-RAN network element using the write storage based on the configuration provided in the request by updating the configuration of the O-RAN network element based on the received configuration stored in the write storage. Item 4: The apparatus of item 3, wherein the apparatus may be further configured to update the configuration of the O-RAN network element using the write storage based on the configuration provided in the request by updating the read storage based on the received configuration stored in the write storage after updating the configuration of the O-RAN network element based on the received configuration stored in the write storage. Item 5: The apparatus of item 3 or 4, wherein the apparatus may be further configured to update the configuration of the O-RAN network element using the write storage based on the configuration provided in the request by: after storing the received configuration in the write storage, sending to the rApp or other SMO function a first response that may be configured to notify the rApp or other SMO function that the received configuration has been stored in the write storage; and after updating the configuration of the O-RAN network element based on the received configuration stored in the write storage, sending to the rApp or other SMO function a second notification that may be configured to notify the rApp or other SMO function that the configuration of the O-RAN network element has been updated based on the received configuration stored in the write storage. Item 6: The O-RAN network element may be a first O-RAN network element; the device may be further configured to receive, from an rApp or other SMO function, a request to obtain configuration data of a second O-RAN network element different from the first O-RAN network element; and the request to obtain configuration data of the first O-RAN network element and the request to obtain configuration data of the second O-RAN network element may be bundled into a single application programming interface (API) call. Item 7: The O-RAN network element may be a first O-RAN network element; the device may be further configured to receive, from an rApp or other SMO function, a request to update the configuration of a second O-RAN network element, different from the first O-RAN network element, based on a configuration provided in the request to update the configuration of the second O-RAN network element, wherein the request to update the configuration of the first O-RAN network element and the request to update the configuration of the second O-RAN network element may be bundled into a single application programming interface (API) call. Item 8: An apparatus that may be configured to receive, from an rApp or other SMO function, at least one of a request to obtain configuration data of an O-RAN network element and a request to update the configuration of the O-RAN network element; in response to receiving the request to obtain the configuration data of the O-RAN network element, obtain the configuration data using a first digital twin; and in response to receiving the request to update the configuration of the O-RAN network element, update the configuration of the O-RAN network element using a second digital twin that is different from the first digital twin based on the configuration provided in the request, wherein the first digital twin and the second digital twin may be provided in the apparatus, and the first digital twin and the second digital twin may include a complete digital replica of the O-RAN network element. Item 9: A method that may include receiving, from an rApp or other SMO function, at least one of a request to obtain configuration data of an O-RAN network element and a request to update the configuration of the O-RAN network element; in response to receiving the request to obtain the configuration data of the O-RAN network element, obtaining the configuration data using a read storage; and in response to receiving the request to update the configuration of the O-RAN network element, updating the configuration of the O-RAN network element using a write storage different from the read storage based on the configuration provided in the request, wherein the write storage and the read storage may be provided in a device that performs the method. Item 10: The method of item 9, wherein obtaining configuration data using read storage may include: determining whether the configuration data is stored in the read storage; and in response to determining that the configuration data is stored in the read storage, transmitting the configuration data from the read storage to an rApp or other SMO function. Item 11: The method of item 9 or 10, wherein updating the configuration of the O-RAN network element using write storage based on the configuration provided in the request may include: receiving a configuration from an rApp or other SMO function; storing the received configuration in write storage; and updating the configuration of the O-RAN network element based on the received configuration stored in the write storage. Item 12: The method of item 11, wherein updating the configuration of the O-RAN network element using the write storage based on the configuration provided in the request may further include updating the configuration of the O-RAN network element based on the received configuration stored in the write storage, and then updating the read storage based on the received configuration stored in the write storage. Item 13: The method of item 11 or 12, wherein updating the configuration of the O-RAN network element using the write storage based on the configuration provided in the request may further include: after storing the received configuration in the write storage, sending to the rApp or other SMO function a first response that may be configured to notify the rApp or other SMO function that the received configuration has been stored in the write storage; after updating the configuration of the O-RAN network element based on the received configuration stored in the write storage, sending to the rApp or other SMO function a second notification that may be configured to notify the rApp or other SMO function that the configuration of the O-RAN network element has been updated based on the received configuration stored in the write storage. Item 14: The O-RAN network element may be a first O-RAN network element; the method may further include receiving a request from an rApp or other SMO function to obtain configuration data of a second O-RAN network element different from the first O-RAN network element; the request to obtain configuration data of the first O-RAN network element and the request to obtain configuration data of the second O-RAN network element may be bundled into a single application programming interface (API) call. Item 15: The O-RAN network element may be a first O-RAN network element; the method may further include receiving, from an rApp or other SMO function, a request to update the configuration of a second O-RAN network element different from the first O-RAN network element based on a configuration provided in the request to update the configuration of the second O-RAN network element; the request to update the configuration of the first O-RAN network element and the request to update the configuration of the second O-RAN network element may be bundled into a single application programming interface (API) call. Item 16: A method that may include receiving, from an rApp or other SMO function, at least one of a request to obtain configuration data of an O-RAN network element and a request to update the configuration of the O-RAN network element; obtaining the configuration data using a first digital twin in response to receiving the request to obtain the configuration data of the O-RAN network element; and updating the configuration of the O-RAN network element using a second digital twin that is different from the first digital twin based on the configuration provided in the request in response to receiving the request to update the configuration of the O-RAN network element, wherein the first digital twin and the second digital twin may be included in an apparatus that performs the method, and the first digital twin and the second digital twin may include complete digital replicas of the O-RAN network element. Item 17: A non-transitory computer-readable storage medium having stored thereon instructions executable by an apparatus, the instructions causing the apparatus to perform a method including receiving, from an rApp or other SMO function, at least one of a request to obtain configuration data of an O-RAN network element and a request to update the configuration of the O-RAN network element; in response to receiving the request to obtain the configuration data of the O-RAN network element, obtaining the configuration data using a read storage; and in response to receiving the request to update the configuration of the O-RAN network element, updating the configuration of the O-RAN network element using a write storage different from the read storage based on the configuration provided in the request, wherein the write storage and the read storage are provided in the apparatus. Item 18: A non-transitory computer-readable recording medium as described in Item 17, wherein obtaining configuration data using read storage may include: determining whether the configuration data is stored in the read storage; and in response to determining that the configuration data is stored in the read storage, transmitting the configuration data from the read storage to an rApp or other SMO function. Item 19: The non-transitory computer-readable storage medium of item 17 or item 18, wherein updating the configuration of the O-RAN network element using the write storage based on the configuration provided in the request may include: receiving a configuration from an rApp or other SMO function; storing the received configuration in the write storage; and updating the configuration of the O-RAN network element based on the received configuration stored in the write storage. Item 20: The non-transitory computer-readable storage medium of Item 19, wherein updating the configuration of the O-RAN network element using the write storage based on the configuration provided in the request may further include, after updating the configuration of the O-RAN network element based on the received configuration stored in the write storage, updating the read storage based on the received configuration stored in the write storage.

[0169] 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.< / ok>

Claims

1. receiving at least one of a request to obtain configuration data of an O-RAN network element and a request to update the configuration of an O-RAN network element from the rApp or other SMO function; In response to receiving the request to obtain the configuration data of the O-RAN network element, obtain the configuration data using a read storage; and 1. An apparatus configured to: in response to receiving the request to update the configuration of the O-RAN network element, update the configuration of the O-RAN network element based on a configuration provided in the request using a write storage different from the read storage, The write storage and the read storage are provided in the device. Device.

2. The device, determining whether the configuration data is stored in the read storage; and In response to determining that the configuration data is stored in the read storage, transmitting the configuration data from the read storage to the rApp or other SMO function. configured to retrieve the configuration data using the read storage; 10. The apparatus of claim 1.

3. The device receives the configuration from the rApp or other SMO function; storing the received configuration in the write storage; and updating the configuration of the O-RAN network element based on the received configuration stored in the write storage, thereby configured to update the configuration of the O-RAN network element using the write storage based on the configuration provided in the request.

10. The apparatus of claim 1.

4. the device updates the configuration of the O-RAN network element based on the received configuration stored in the write storage, and then updates the read storage based on the received configuration stored in the write storage, whereby and further configured to update the configuration of the O-RAN network element using the write storage based on the configuration provided in the request.

4. The apparatus of claim 3.

5. After the device stores the received configuration in the write storage, sending a first response to the rApp or other SMO function, the first response being configured to notify the rApp or other SMO function that the received configuration has been stored in the write storage; and after updating the configuration of the O-RAN network element based on the received configuration stored in the write storage, sending to the rApp or other SMO function a second notification configured to notify the rApp or other SMO function that the configuration of the O-RAN network element has been updated based on the received configuration stored in the write storage; and further configured to update the configuration of the O-RAN network element using the write storage based on the configuration provided in the request.

4. The apparatus of claim 3.

6. the O-RAN network element is a first O-RAN network element; The apparatus is further configured to receive, from an rApp or other SMO function, a request to obtain configuration data of a second O-RAN network element different from the first O-RAN network element; and the request to obtain the configuration data of the first O-RAN network element and the request to obtain the configuration data of the second O-RAN network element are bundled into a single Application Programming Interface (API) call.

10. The apparatus of claim 1.

7. the O-RAN network element is a first O-RAN network element; the device is further configured to receive, from an rApp or other SMO function, a request to update the configuration of the second O-RAN network element, the second O-RAN network element being different from the first O-RAN network element, based on a configuration provided in the request to update the configuration of the second O-RAN network element; and the request to update the configuration of the first O-RAN network element and the request to update the configuration of the second O-RAN network element are bundled into a single Application Programming Interface (API) call.

10. The apparatus of claim 1.

8. receiving at least one of a request to obtain configuration data of an O-RAN network element and a request to update the configuration of an O-RAN network element from the rApp or other SMO function; In response to receiving the request to obtain the configuration data of the O-RAN network element, obtain the configuration data using a first digital twin; and 1. An apparatus configured to: in response to receiving the request to update the configuration of the O-RAN network element, update the configuration of the O-RAN network element using a second digital twin different from the first digital twin based on a configuration provided in the request, the first digital twin and the second digital twin are provided in the device; the first digital twin and the second digital twin include complete digital replicas of the O-RAN network elements; Device.

9. receiving at least one of a request to obtain configuration data of an O-RAN network element and a request to update the configuration of an O-RAN network element from the rApp or other SMO function; In response to receiving the request to obtain the configuration data of the O-RAN network element, obtaining the configuration data using a read storage; and responsive to receiving the request to update the configuration of the O-RAN network element, updating the configuration of the O-RAN network element based on a configuration provided in the request using a write storage different from the read storage; the write storage and the read storage are provided in an apparatus that performs the method; method.

10. Retrieving the configuration data using the read storage includes: determining whether the configuration data is stored in the read storage; and In response to determining that the configuration data is stored in the read storage, transmitting the configuration data from the read storage to the rApp or other SMO function.

10. The method of claim 9.

11. updating the configuration of the O-RAN network element using the write storage based on the configuration provided in the request, the write storage comprising: receiving the configuration from the rApp or other SMO function; storing the received configuration in the write storage; and updating the configuration of the O-RAN network element based on the received configuration stored in the write storage; 10. The method of claim 9.

12. updating the configuration of the O-RAN network element using the write storage based on the configuration provided in the request; and after updating the configuration of the O-RAN network element based on the received configuration stored in the write storage, updating the read storage based on the received configuration stored in the write storage. The method of claim 11.

13. updating the configuration of the O-RAN network element using the write storage based on the configuration provided in the request, the write storage comprising: After storing the received configuration in the write storage, sending a first response to the rApp or other SMO function configured to notify the rApp or other SMO function that the received configuration has been stored in the write storage; and After updating the configuration of the O-RAN network element based on the received configuration stored in the write storage, sending a second notification to the rApp or other SMO function configured to notify the rApp or other SMO function that the configuration of the O-RAN network element has been updated based on the received configuration stored in the write storage. The method of claim 11.

14. the O-RAN network element is a first O-RAN network element; The method further includes receiving a request from an rApp or other SMO function to obtain configuration data for a second O-RAN network element different from the first O-RAN network element; and the request to obtain the configuration data of the first O-RAN network element and the request to obtain the configuration data of the second O-RAN network element are bundled into a single Application Programming Interface (API) call.

10. The method of claim 9.

15. the O-RAN network element is a first O-RAN network element; The method further includes receiving, from an rApp or other SMO function, the request to update the configuration of the second O-RAN network element, the second O-RAN network element being different from the first O-RAN network element, based on the configuration provided in the request to update the configuration of the second O-RAN network element; and the request to update the configuration of the first O-RAN network element and the request to update the configuration of the second O-RAN network element are bundled into a single Application Programming Interface (API) call.

10. The method of claim 9.

16. receiving at least one of a request to obtain configuration data of an O-RAN network element and a request to update the configuration of an O-RAN network element from the rApp or other SMO function; In response to receiving the request to obtain the configuration data of the O-RAN network element, obtaining the configuration data using a first digital twin; and responsive to receiving the request to update the configuration of the O-RAN network element, updating the configuration of the O-RAN network element based on a configuration provided in the request using a second digital twin different from the first digital twin; the first digital twin and the second digital twin are provided in an apparatus that performs the method; the first digital twin and the second digital twin include complete digital replicas of the O-RAN network elements; method.

17. A non-transitory computer-readable medium having stored thereon instructions executable by a device, the instructions causing the device to: receiving at least one of a request to obtain configuration data of an O-RAN network element and a request to update the configuration of an O-RAN network element from the rApp or other SMO function; In response to receiving the request to obtain the configuration data of the O-RAN network element, obtaining the configuration data using a read storage; and in response to receiving the request to update the configuration of the O-RAN network element, updating the configuration of the O-RAN network element based on a configuration provided in the request using a write storage different from the read storage; The write storage and the read storage are provided in the device. A non-transitory computer-readable recording medium.

18. Retrieving the configuration data using the read storage includes: determining whether the configuration data is stored in the read storage; and In response to determining that the configuration data is stored in the read storage, transmitting the configuration data from the read storage to the rApp or other SMO function.

20. The non-transitory computer-readable storage medium of claim 17.

19. updating the configuration of the O-RAN network element using the write storage based on the configuration provided in the request, the write storage comprising: receiving the configuration from the rApp or other SMO function; storing the received configuration in the write storage; and updating the configuration of the O-RAN network element based on the received configuration stored in the write storage; 20. The non-transitory computer-readable storage medium of claim 17.

20. updating the configuration of the O-RAN network element using the write storage based on the configuration provided in the request; and after updating the configuration of the O-RAN network element based on the received configuration stored in the write storage, updating the read storage based on the received configuration stored in the write storage.

20. The non-transitory computer-readable storage medium of claim 19.

Images