Intelligent Radio Access Network (RAN) Optimization Framework and Methodology

Abstract

1. An intelligent radio access network (RAN) optimization framework. In the case of an E2 node, an optimization service is initiated for processing by a near real-time RAN intelligent controller (RIC) (near-RT RIC). The E2 node compares performance to a first predetermined threshold. In response to performance falling below the first predetermined threshold, the E2 node takes over optimization for the E2 node. Otherwise, the near-RT RIC continues optimization. The E2 node compares performance of the E2 node to a second predetermined threshold. In response to performance falling below the second predetermined threshold, the near-RT RIC takes over optimization. Otherwise, the E2 node continues processing optimization for the E2 node's performance. In the case of an open RAN radio unit (O-RU) node, the O-RU node can perform local optimization of time-critical functions, and a non-RT RIC can perform optimization of non-time-critical functions.

Description

[Technical Field]

[0001] The present specification relates to providing an intelligent Radio Access Network (RAN) optimization framework and methods for using the same. [Background technology]

[0002] Network owners, network operators, service and application developers can evaluate how certain applications and services will perform on a particular network based on a configuration using specific parameters or under specific operating conditions. In existing deployments, whether 2G, 3G, or 4G, there are algorithms that run locally in the eNB or base station. The algorithms provide various optimizations such as energy consumption, throughput, latency, and other KPIs. Network optimization can have a significant impact on network performance.

[0003] As 5G and radio access networks (RANs) become open or virtualized, previous monolithic nodes are being separated or split into multiple components. 5G RANs are expected to be deployed with the algorithms responsible for optimizing the network located in a central controller called the RAN Intelligent Controller (RIC). Moving the optimization to the RIC provides a holistic end-to-end view of the network. Artificial intelligence (AI) / machine learning (ML) frameworks located on the RIC platform can help improve optimization. However, providing AI / ML to local nodes is very expensive.

[0004] In Open RAN (O-RAN), functionality is decomposed into the O-RAN Central Unit (O-CU), O-RAN Distributed Unit (O-DU), and O-RAN Radio Unit (O-RU). The O-CU is further divided into the O-CU Control Plane (O-CU-CP) and O-CU User Plane (O-CU-UP). These RAN functionalities are connected to an intelligent controller through open interfaces that can stream telemetry and deploy control actions and policies. The O-RAN architecture includes two RAN intelligent controllers (RICs) that manage and control the network: the near-real time RIC (NRT RIC) and the non-real time RIC (NRT RIC). The RICs provide an end-to-end view of the network and apply AI / ML. The quasi-RT RIC communicates with E2 nodes via the E2 interface and handles functions that operate in near real time (e.g., timescales of 10 milliseconds to 1 second). The non-RT RIC handles functions that operate in non-real time (e.g., timescales greater than 1 second). Optimization can be provided based on the quasi-RT RIC exchanging messages with RAN nodes. E2 nodes terminate at the E2 termination and include the O-DU, O-CU-CP, and O-CU-UP, as well as Next Generation Node B (O-gNB) and O-evolved Node B (O-eNB). The O-RU communicates with the non-RT RIC via the open fronthaul (FH) management plane (M-Plane) and with the O-DU via the open FH Control, User, and Synchronization (CUS) and M-Plane.

[0005] For example, agreements are performed between next generation Node Bs (gNBs) and service subscriptions are established between RAN nodes and the quasi-RT RIC. The quasi-RT RIC determines which parameters and procedural changes to implement in the RAN nodes. The problem with this model is that the quasi-RT RIC cannot provide the best optimization solution. Summary of the Invention [Means for solving the problem]

[0006] In at least an embodiment, a method for providing intelligent Radio Access Network (RAN) optimization includes provisioning one or more Radio Access Network (RAN) nodes; initiating an optimization subscription service to handle optimization of E2 node performance of the one or more RAN nodes by a near real-time RAN intelligent controller (RIC) (near-RT RIC); determining whether performance of the E2 node as a result of the optimization of the E2 node performance by the near-RT RIC is below a first predetermined threshold; and in response to determining that the performance of the E2 node is below the first predetermined threshold, switching to optimization of the E2 node performance by the E2 node; and otherwise continuing to handle optimization of the E2 node performance by the near-RT RIC.

[0007] In at least one embodiment, a Radio Access Network (RAN) node includes a memory storing computer-readable instructions and a processor coupled to the memory, the processor configured to execute the computer-readable instructions to perform operations including: providing RAN functionality to one or more RAN nodes in a mobile network; initiating an optimization subscription service to handle optimization of E2 node performance of the one or more RAN nodes by a near real-time RAN intelligent controller (RIC) (near-RT RIC); determining whether performance of the E2 node as a result of the optimization of E2 node performance by the near-RT RIC is below a first predetermined threshold; and, in response to determining that the performance of the E2 node is below the first predetermined threshold, switching to optimization of E2 node performance by the E2 node; and otherwise continuing to handle optimization of E2 node performance by the near-RT RIC.

[0008] In at least one embodiment, a non-transitory computer-readable medium stores computer-readable instructions that, when executed by a processor, cause the processor to perform operations including provisioning one or more Radio Access Network (RAN) nodes; initiating an optimization subscription service to handle optimization of E2 node performance of the one or more RAN nodes by a near real-time RAN intelligent controller (RIC) (near-RT RIC); determining whether performance of the E2 node as a result of the optimization of E2 node performance by the near-RT RIC is below a first predetermined threshold; and, in response to determining that the performance of the E2 node is below the first predetermined threshold, switching to optimization of E2 node performance by the E2 node; and otherwise continuing to handle optimization of E2 node performance by the near-RT RIC.

[0009] Aspects of the present disclosure are best understood from the following detailed description when read in conjunction with the accompanying drawings. It should be noted that, according to standard industry practice, various features have not been drawn to scale. In fact, the dimensions of various features may be increased or decreased for clarity of illustration. [Brief explanation of the drawings]

[0010] [Figure 1] 1 illustrates a mobile network according to at least one embodiment. [Figure 2] FIG. 1 is a functional block diagram of an O-RAN architecture for implementing an intelligent RAN optimization framework by using RIC or local services to provide RAN optimization, according to at least one embodiment. [Figure 3] FIG. 1 is a block diagram of an architecture for a quasi-RT RIC, according to at least one embodiment. [Figure 4] FIG. 1 is a flow diagram of an E2 subscription process, according to at least one embodiment. [Figure 5] 1 illustrates information elements of a RIC subscription suspend message, according to at least one embodiment. [Figure 6] 10 illustrates information elements of a RIC Subscription Suspend Acknowledgement message, according to at least one embodiment. [Figure 7] 1 illustrates information elements of a RIC subscription resume message, according to at least one embodiment. [Figure 8] 1 is a flowchart of a method for providing RAN optimization using RIC or local services, according to at least one embodiment. [Figure 8C] 1 is a flowchart of a method for providing RAN optimization using RIC or local services, according to at least one embodiment. [Figure 9] FIG. 1 illustrates a high-level functional block diagram of a processor-based system according to at least one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] The embodiments described herein illustrate examples for implementing various features of the provided subject matter. To simplify the disclosure, example components, values, actions, materials, arrangements, and the like are described below. Of course, these are examples and are not intended to be limiting. Other components, values, actions, materials, arrangements, and the like are contemplated. For example, the formation of a first feature on or over a second feature in the following description includes embodiments in which the first and second features are formed in direct contact with each other, and also includes embodiments in which an additional feature is formed between the first and second features such that the first and second features are not in direct contact with each other. Additionally, the present disclosure repeats reference numerals and / or letters in various examples. This repetition is for the purposes of brevity and clarity and does not dictate a relationship between the various embodiments and / or configurations described.

[0012] Additionally, spatially relative terms such as "beneath," "below," "lower," "above," and "upper" are used herein for ease of description to describe the relationship of one element or feature to another element(s) or feature(s), as illustrated in the figures. Spatially relative terms are intended to encompass different orientations of the device in use or action in addition to the orientation shown in the figures. If the device is otherwise oriented (rotated 90 degrees or pointed in another direction), the spatially relative descriptors used herein will be interpreted accordingly.

[0013] Terms such as "user equipment," "mobile station," "mobile," "mobile device," "subscriber station," "subscriber equipment," "access terminal," "terminal," "handset," and similar terms refer to wireless devices utilized by subscribers or users of wireless communication services to receive or transmit data, control, voice, video, sound, games, data streaming, or signaling streaming. The foregoing terms are used interchangeably in this specification and related drawings. Terms such as "access point," "base station," "Node B," "evolved Node B (eNode B)," next generation Node B (gNB), enhanced gNB (en-gNB), home Node B (HNB), "home access point (HAP)," and similar terms refer to wireless network components or devices that provide and receive data, control, voice, video, sound, games, data streaming, or signaling streaming to and from UEs.

[0014] In at least one embodiment, an intelligent Radio Access Network (RAN) optimization framework is used to either use a near-real-time (near-RT or NRT) RAN intelligent controller (RIC) for centralized optimization or switch to using an algorithm supported locally, for example, in a RAN node (gNB), which can provide better performance. The framework determines whether the Radio Access Network (RAN) node is an E2 node or an open RAN radio unit (O-RU) node. An optimization subscription service is initiated to handle E2 node performance optimization by the near-real-time RAN intelligent controller (RIC) (near-RT RIC). In response to the performance falling below a first threshold, the E2 node performance optimization is switched to the E2 node. Having the near-RT RIC suspend processing of E2 performance optimization is based on sending a subscription suspend message to the near-RT RIC. The optimization subscription service processed by the near-RT RIC is resumed in response to the E2 performance falling below a second threshold. In response to determining that the RAN node is an O-RU node, a determination is made as to whether the function is a time-critical O-RU function or a non-critical O-RU function. Based on whether the function is a time-critical O-RU function, the O-RU node processes the optimization process. Based on whether the function is a non-time-critical O-RU function, the quasi-RT RIC / non-RT RIC processes the optimization process via the E2 termination at the O-DU.

[0015] Embodiments described herein provide methods that provide one or more advantages. For example, an intelligent radio access network (RAN) optimization framework provides performance improvements by using methods that achieve optimal performance, whether the methods are centralized optimization controlled by a RAN intelligent controller (RIC) or local optimization controlled by RAN nodes over the E2 interface. The intelligent radio access network (RAN) optimization framework provides improved handling of delay-sensitive use cases and RAN optimization functions. The intelligent radio access network (RAN) optimization framework also involves and uses the RIC as needed for RAN optimization functions.

[0016] FIG. 1 illustrates a mobile network 100 according to at least one embodiment.

[0017] In Figure 1, User Equipment (UE) 1 110, UE2 112, UE3 114, and UE4 116 communicate with Radio Units (RU) 1 121, RU2 123, RU3 125, and RU4 127, respectively. Although a one-to-one correspondence between UE1 110, UE2 112, UE3 114, and UE4 116 and RU1 121, RU2 123, RU3 125, and RU4 127 is shown in Figure 1, those skilled in the art will appreciate that the embodiments are not meant to be so limited. For example, more UEs may be connected to RU1 121, RU2 123, RU3 125, and RU4 127. Additionally, additional RUs may be implemented.

[0018] RU1 121, RU2 123, RU3 125, and RU4 127 are located in towers 120, 122, 124, and 126, respectively. RU1 121 is shown in communication with Distributed Unit (DU) 1 130. RU2 123 and RU3 125 are shown in communication with DU2 132. RU4 127 is shown in communication with DU3 134. DU1 130 and DU2 132 communicate with Centralized Unit (CU) 1 140. DU3 134 communicates with CU 142. CU1 140 is shown having a control plane 142 and a user plane 144. Although not shown in FIG. 1, those skilled in the art will understand that CU2 146 also includes a control plane and a user plane. Towers 120, 122, 124, 126, RU1 121, RU2 123, RU3 125, RU4 127, DU1 130, DU2 132, DU3 134, and CU1 140 and CU2 142 represent one or more radio access networks (RANs) 120.

[0019] RU1 121, RU2 123, RU3 125, RU4 127 communicate with DU1 130, DU2 132, DU3 134 via a fronthaul interface 150. DU1 130, DU2 132, DU3 134 communicate with CU1 140 and CU2 142 via a midhaul interface 152. CU1 140 and CU2 142 are coupled by an Xn interface 156.

[0020] CU1 140 and CU2 142 communicate with 5G Core 160 via backhaul interface 154. 5G Core 160 provides UE1 110, UE2 112, UE3 114, and UE4 116 with access to a data network 170, such as the Internet, and a voice network, such as a public switched telephone network 172.

[0021] A network management system and orchestration system 180 can control, manage, and configure the mobile network 100. The network management system and orchestration system 180 is shown coupled to the 5G core 160. An intelligent RAN optimization framework 182 interfaces directly with the RAN 120 to provide intelligent RAN optimization to E2 nodes such as the O-DU 220, O-CU-CP 221, O-CU-UP 222, O-gNB 223, and O-eNB 224. According to at least one embodiment, the network management system and orchestration system 180 can implement the intelligent RAN optimization framework 182 by using RIC services or local services to provide RAN optimization.

[0022] FIG. 2 is a functional block diagram of an O-RAN architecture 200 for implementing an intelligent RAN optimization framework by using RIC or local services to provide RAN optimization, according to at least one embodiment.

[0023] In FIG. 2, a near-real-time (RT) RAN intelligent controller (RIC) 210 executes the optimization procedure. The near-RT RIC 210 and RAN nodes, such as E2 nodes 220, 221, 222, 223, and 224, have an agreement for centralized optimization control by the near-RT RIC 210. The E2 nodes include an ORAN distributed unit (O-DU) 220, an O-centralized unit control plane (O-CU-CP) 221, an O-CU user plane (O-CU-UP) 222, an O-next-generation node B (O-gNB) 223, and an O-eNB 224. The near-RT RIC 210 is coupled to the O-DU 220, the O-CU-CP 221, the O-CU-UP 222, the O-gNB 223, and the O-eNB 224 by an E2 interface 230. The E2 nodes are logical nodes that terminate using the E2 interface 230.

[0024] The Next Generation NodeB (O-gNB) 223 is a radio base station in a 5G NR network. The O-gNB 223 includes independent network functions that implement 3rd Generation Partnership Project (3GPP®)-compliant 5G New Radio (NR) radio access network (RAN) protocols, such as Physical (PHY), Media Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), and Radio Resource Control (RRC). The NR RAN protocols can run together or independently and can be deployed on either physical (e.g., small cell chipsets) or virtual resources (e.g., dedicated Commercial Off-The-Shelf (COTS) servers or shared cloud resources).

[0025] The Evolved Node B (eNB) 224 is an Evolved-UMTS Terrestrial Radio Access Network (E-UTRAN) Node B, an element in LTE, which is an evolution of the Node B element in the Universal Mobile Telecommunications System (UMTS) UTRA. The O-eNB 224 is connected to the mobile phone network and communicates directly and wirelessly with mobile handsets.

[0026] The service management and orchestration framework 240 includes a non-real-time RIC (non-RT RIC) 242. The quasi-RT RIC 210 communicates with the service management and orchestration framework 240 and the non-RT RIC 242 via an A1 interface 244. The service management and orchestration framework 240 and the non-RT RIC 242 communicate with the O-DU 220, the O-CU-CP 221, the O-CU-UP 222, the O-gNB 223, and the O-eNB 224 using an O1 interface 250. The O-DU 220 is coupled to the ORAN Radio Unit (O-RU) 260 using an open fronthaul M-plane interface 270. The open fronthaul M-plane interface 270 also enables communication between the O-RU 260 and the service management and orchestration framework 240 and the non-RT RIC 242.

[0027] In FIG. 2, the N-RT RIC 210 is the service provider, and the E2 nodes 220-224 are service consumers. Most RAN vendors provide local algorithms that can perform data collection and logging and process data locally in the E2 nodes 220-224 to achieve RAN optimization. Sometimes, algorithms supported locally in the E2 nodes, such as the O-DU 220, O-CU-UP 221, O-CU-CP 222, O-gNB 223, and O-eNB 224, can provide better performance. Therefore, using algorithms supported locally in the E2 nodes for service optimization, rather than following commands from the N-RT RIC 210, can provide improved performance for the E2 nodes 220-224.

[0028] One or more of the E2 nodes 220-224 monitor locally collected performance parameters and compare the optimization provided by the quasi-RT RIC 210 to a local optimization, such as may be provided by the E2 node 220. While the optimization may be provided to any of the E2 nodes 220-224, the optimization herein is described using the O-DU 220. A predetermined performance threshold may be used to compare the performance provided by the quasi-RT RIC 210. The E2 node 220 determines that the optimization command provided by the quasi-RT RIC 210 results in performance below the predetermined threshold. For example, the optimization command provided by the quasi-RT RIC 210 may generate an error or fail to meet performance indicators such as latency, load balancing, or energy efficiency. The E2 node 220 may be configured with the local algorithm or with a newer or updated local algorithm that provides better performance optimization.

[0029] In response to an optimization command provided by the quasi-RT RIC 210 that results in performance below a predetermined threshold, the E2 node 220 suspends optimization by the quasi-RT RIC 210 of the E2 node 220, and the E2 node 220 begins performance optimization using a local algorithm of the E2 node 220. The E2 node 220 can also resume or restore having the quasi-RT RIC 210 handle optimization for the E2 node 220 by resuming subscription to the optimization command provided by the quasi-RT RIC 210.

[0030] FIG. 3 is a block diagram 300 of an architecture for a quasi-RT RIC, according to at least one embodiment.

[0031] In FIG. 3, the quasi-RT RIC 310 is shown as a logical network node located between the Service Management & Orchestration layer 370 and the E2 node 380. The Service Management & Orchestration (SMO) layer 370 hosts the non-RT RIC 372. The SMO 370 oversees the orchestration aspects, management, and automation of RAN elements. The SMO 370 supports an O1 interface 374 and an A1 interface 376. The non-real-time RAN intelligent controller (Non-RT RIC) 372 is a logical function that enables non-real-time control and optimization of RAN elements and resources, AI / ML workflows including model training and updates, and policy-based guidance of applications / functions within the quasi-RT RIC 310.

[0032] The quasi-RT RIC 310 is a logical function that enables near real-time control and optimization of O-RAN elements and resources through granular data collection and action over the E2 interface 320 terminating at the E2 termination 322. The quasi-RT RIC 310 provides policy interpretation and enforcement from the non-RT RIC 372 and supports enrichment information to optimize control functions.

[0033] The quasi-RT RIC 310 includes an A1 termination 312 and an O1 termination 314. The A1 termination 312 terminates an A1 interface 376 from the non-RT RIC 372. The A1 interface 376 is used for policy guidance. The SMO 370 provides fine-grained policy guidance, such as forcing user equipment to change frequencies, and other data enrichment to the RAN functions via the A1 interface 376. The O1 termination 312 terminates an O1 interface 374 from the SMO 370. The O1 interface 374 supports operation and maintenance (OAM) management of multi-vendor open RAN functions, including fault, configuration, accounting, performance and security management, software management, and file management capabilities.

[0034] The quasi-RT RIC API for xApp 324 allows RRM control functionality to be executed in the quasi-RT RIC 310 and enforced at the E2 node 380 via the E2 interface 320. The quasi-RT RIC API for xApp 324 includes xApp1 326, xApp2 327, and xAppN 328. A messaging infrastructure 329 allows message interaction between the internal functions of the quasi-RT RIC 310.

[0035] Conflict Mitigation 330 resolves potentially overlapping or conflicting requests from multiple xApps. xApp Subscription Management 331 merges subscriptions from different xApps and provides unified data delivery to the xApps. Management Functions 332, as a service producer, provides fault management, configuration management, and performance management to SMO 370, captures, monitors, and collects status internal to Quasi-RT RIC 310, and provides logging, tracing, and metric collection that is forwarded to external systems for further evaluation.

[0036] Security 334 provides security mechanisms for xApps. AI / ML 335 provides data pipelining, training, and performance monitoring for xApps. xApp repository functionality 336 enables selection of xApps for A1 message routing based on A1 policy type and operator policies. Quasi-RT RIC 310 provides an API isolated from specific implementation solutions, including a Shared Data Layer (SDL) 340 that acts as an overlay for the underlying database 342 and enables simplified data access. E2 termination 322 terminates the E2 interface 320 from the E2 node 380.

[0037] The E2 node 380 is a logical function that supports the protocol layers and interfaces defined by the 3GPP RAN (eNB for E-UTRAN and gNB / ng-eNB for NG-RAN). One quasi-RT RIC 310 can connect to one or more E2 nodes 380 via transport functions, while an E2 node 380 can connect to the quasi-RT RIC 310. The quasi-RT RIC 310 receives policies, enrichment data, and ML models from the non-RT RIC 372 using the A1 interface 376 and collects near-real-time information from the E2 node 380 using the E2 interface 320 to perform fine-grained Radio Resource Management (RRM) actions on the E2 node 380. Functions hosted by xApps 326, 327, and 328 enable services to be executed on the quasi-RT RIC 310 and results to be sent to the E2 node 380 via the E2 interface 320. The API enablement 350 supports capabilities related to API operations of the semi-RT RIC 310, such as API repository / registry, authentication, discovery, and generic event subscription.

[0038] FIG. 4 is a flow diagram 400 of an E2 subscription process according to at least one embodiment.

[0039] In Figure 4, the subscription process between the RAN node 410 and the quasi-RT RIC 420 includes processes for RIC service start 430, RIC service suspend 450, and RIC service resume 470. The purpose of the subscription process in the quasi-RT RIC 420 is to allow an xApp to request a subscription for REPORT, INSERT, and / or POLICY service(s) from the RAN node 410 over an interface such as the E2 interface for an E2 node or the open fronthaul M-plane interface for an O-RU node, and to ensure that validated, non-duplicate subscriptions are maintained by the quasi-RT RIC 420 over the interface to the RAN node 410 and that duplicate subscription request messages from the xApp are handled appropriately.

[0040] The RAN node 410 initiates the subscription procedure by sending a setup request message 432 containing appropriate data to the quasi-RT RIC 420. For example, the setup request message 432 may include a RAN capability definition that defines the RAN capabilities supported by the RAN node 410, node identifier (ID) information, configurations supported by the RAN node 410, etc.

[0041] The quasi-RT RIC 420 responds with a setup response message 434 containing appropriate data, such as a list of accepted RAN capabilities and associated RAN capability IDs, and a list of rejected RAN capabilities, associated RAN capability IDs, and reasons for rejection. The RAN capability ID is an indicator of a network capability. The subscription is associated with the network capability associated with the RAN capability ID.

[0042] The quasi-RT RIC 420 may also send to the RAN node a RIC subscription request message 436. The RIC subscription request message 436 is used to create a new subscription in the RAN node 410 at the request of the quasi-RT RIC 420 and includes one or more of a RIC request ID, a RAN capability ID, a RIC subscription details, a RIC event trigger definition, a sequence of actions, a RIC action ID, a RIC action type, a RIC action definition, and a RIC follow-on action.

[0043] The RAN node 410 responds by sending a RIC subscription response message 438 to the quasi-RT RIC 420, accepting the request from the quasi-RT RIC 420 to create a new event in the RAN node 410. The RIC subscription response message 438 includes one or more of the following: a RIC request ID, a RAN capability ID, a RIC action approval list and associated RIC action IDs, and a RIC action disapproval list and associated RIC action IDs, and a cause. Thus, messages 1-4 of the RIC service initiation process 430 are part of the existing interface connection establishment. Messages 1-4 of the RIC service initiation process 430, i.e., 432, 434, 436, 438, expose optimization capabilities, network capabilities, etc.

[0044] The RAN node 410 continues to monitor performance. The RAN node 410 determines whether the centralized optimization provided by the quasi-RT RIC 420 is acceptable. The RAN node 410 determines that a local algorithm can provide better performance optimization based, for example, on determining whether the performance optimization of the RAN node 410 by the quasi-RT RIC 420 is below a first predetermined threshold.

[0045] In response to the RAN node 410 determining that the performance optimization of the RAN node is not below the first predetermined threshold, the RAN node 410 continues to monitor the performance optimization of the functions of the RAN node 410 via the quasi-RT RIC 420.

[0046] In response to the RAN node 410 determining that a local algorithm can provide better performance optimization, for example, based on the performance of the quasi-RT RIC 420 optimization being below a predetermined threshold, the RAN node 410 executes a RIC service suspension process 450. The RAN node 410 sends a RIC subscription suspension message 452 to the quasi-RT RIC 420.

[0047] In response, the quasi-RT RIC 420 can send a RIC subscription suspend acknowledgement message 454 to the RAN node 410. The RAN node 410 can then take over performance optimization of the RAN node 410 using a local optimization algorithm. For example, the RAN node 410 may determine that subscriptions for X, Y, and Z exist and that there is a problem with subscription X, but not with Y and Z. Thus, the RAN node 410 can suspend subscription X. The RIC subscription suspend message 452 can provide the quasi-RT RIC 420 with an identification of the reason the RAN node 410 is attempting to suspend subscription X. Thus, through the RIC subscription suspend message 452 and the RIC subscription suspend acknowledgement message 454, the RAN node 410 and the quasi-RT RIC 420 can reach an agreement on how to optimize performance of the RAN node 410.

[0048] The RAN node 410 continues to monitor performance. The RAN node 410 determines whether the performance optimization by the RAN node 410 is below a second predetermined threshold. In response to the performance optimization not being below the second threshold, the RAN node 410 continues to monitor the performance of the RAN node 410.

[0049] In response to the performance optimization being below the second threshold, the RAN node 410 may cause the quasi-RT RIC 420 to begin processing the performance optimization. For example, in response to a change in performance, such as improved coverage or fewer routine outages, the RAN node 410 may communicate with the quasi-RT RIC 420 / non-RT RIC to cause the quasi-RT RIC 420 to resume performance optimization of the RAN node 410.

[0050] The RIC service resume process 470 is used to resume RIC service. The RAN node 410 sends a RIC subscription resume message 472 to the quasi-RT RIC 420. For example, the RAN node 410 sends the RIC subscription resume message 472 identifying subscription X to be processed again by the quasi-RT RIC 420.

[0051] In response, the quasi-RT RIC 420 responds to the RAN node 410 with a RIC subscription request message 474. Again, the RIC subscription request message 474 is used to create a subscription, for example, to resume subscription X, and includes one or more of a RIC request ID, a RAN capability ID, a RIC subscription details, a RIC event trigger definition, a sequence of actions, a RIC action ID, a RIC action type, a RIC action definition, and a RIC follow-on action.

[0052] The RAN node 410 responds to the subscription request message 474 from the quasi-RT RIC 420 by sending a RIC subscription response message 476 to the quasi-RT RIC 420 accepting the request from the quasi-RT RIC 420 to have the quasi-RT RIC 420 resume subscription X. Thus, via the RIC subscription resume message 472, the RIC subscription request message 474, and the RIC subscription response message 476, the RAN node 410 and the quasi-RT RIC 420 can reach an agreement that the quasi-RT RIC 420 will resume handling performance optimization for the RAN node 410, including agreement on the parameters of subscription X. The RAN node 410 returns to monitoring the performance optimization by the quasi-RT RIC 420.

[0053] In at least one embodiment, the RIC service suspend process 450 and the RIC service resume process 470 may be repeated. However, the cycle between the RIC service suspend process 450 and the RIC service resume process 470 should not be performed too frequently. Therefore, a timer may be used to control the frequency of transitions between the RIC service suspend process 450 and the RIC service resume process 470. For example, a timer may be used to cause the RAN node 410 to wait a predetermined period of time, e.g., 1 hour, 4 hours, 10 hours, etc., before performing the RIC service suspend process 450 again. The timer may depend on the network functions involved.

[0054] FIG. 5 illustrates information elements of a RIC subscription suspend message 500, according to at least one embodiment.

[0055] In Figure 5, a RIC Subscription Suspend message 500 is sent from an E2 node to a quasi-RT RIC 510. The RIC Subscription Suspend message 500 includes a Message Type Information Element (IE) 520 that uniquely identifies the type of message being sent. The RIC Request ID 530 includes a RIC Requestor ID and a RIC Instance ID. The RAN Function ID 540 indicates a RAN Function ID number that is unique within a given E2 node.

[0056] Suspend reason 550 reports information obtained at the network level for suspending subscriptions with quasi-RT RICs for performance optimization. The suspend reason provides the quasi-RT RIC with reasons why the E2 node is attempting to suspend the subscription. For example, the E2 node may identify, for example, a message failure at E2 node 552, an error at E2 node 554, and performance degradation at E2 node 556.

[0057] Thus, the E2 node identifies problems related to message failures, message errors, performance degradation, etc. due to the optimization functions applied by the quasi-RT RIC. While the quasi-RT RIC is provided with log information regarding performance parameters, the quasi-RT RIC does not have direct access to the information that the E2 node can access. Therefore, the E2 node can send a RIC subscription pause message 500 to the quasi-RT RIC to take over performance optimization at the local level, i.e., the E2 node level.

[0058] FIG. 6 illustrates information elements of a RIC Subscription Suspend Acknowledgement message 600, according to at least one embodiment.

[0059] 6, a RIC Subscription Suspend Acknowledgement message 600 is sent from the quasi-RT RIC to an E2 node 610. The RIC Subscription Suspend Acknowledgement message 600 includes a Message Type information element 620, a RIC Request ID information element 630, and a RAN Capability ID information element 640.

[0060] The Message Type Information Element (IE) 520 uniquely identifies the type of message being sent. The RIC Request ID 630 includes the RIC Requestor ID and the RIC Instance ID. The RAN Function ID 640 indicates a RAN Function ID number that is unique within a given E2 node.

[0061] The E2 node can then take over the performance optimization of the E2 node using a local optimization algorithm. Through the RIC Subscription Suspend message 500 and the RIC Subscription Suspend Acknowledgement message 600, the E2 node and the quasi-RT RIC can reach an agreement on how to optimize the performance of the E2 node.

[0062] FIG. 7 illustrates information elements of a RIC subscription resume message 700, according to at least one embodiment.

[0063] 7, a RIC Subscription Resume message 700 is sent from the E2 node to the quasi-RT RIC 710. The RIC Subscription Resume message includes a Message Type Information Element (IE) 720 that uniquely identifies the type of message being sent.

[0064] The RIC Request ID 730 includes a RIC Requestor ID and a RIC Instance ID. The RAN Function ID 740 indicates a RAN Function ID number that is unique within a given E2 node.

[0065] The resume reason 750 reports information obtained at the network level for resuming a subscription with a quasi-RT RIC for performance optimization. The resume reason identifies to the quasi-RT RIC the reason why the E2 node is attempting to resume the subscription. For example, the E2 node may identify a suspension reason based on a message failure at the E2 node due to local optimization 752, an error at the E2 node due to local optimization 754, and a performance degradation at the E2 node due to local optimization 756. Thus, the E2 node identifies issues related to message failures, message errors, performance degradation, etc., due to optimization functions applied by the E2 node. The E2 node may send a RIC subscription resume message 700 to the quasi-RT RIC so that the quasi-RT RIC resumes performance optimization with the quasi-RT RIC.

[0066] The same framework described above can be extended to non-RT RIC nodes.

[0067] 2, the O-Radio Unit (O-RU) 260 is coupled to the O-DU 220 via an open fronthaul M-plane interface 270. The O-RU 260 converts radio signals transmitted to and from the antennas into digital signals that can be transmitted to the O-DU 220 via the fronthaul. The O-RU 260 includes synchronization and fronthaul transport, lower physical layer baseband processing, a digital front end (DFE), and an RF front end (RF FE).

[0068] RIC services are not supported by the O-RU 260, and due to the time-critical nature of the O-RU 260's functionality, there is no E2 interface between the O-RU 260 and the quasi-RT RIC 210 or non-RT RIC 242. Functionality can be divided into time-critical and non-time-critical functions. In at least one embodiment, the O-RU 260 can perform local optimization of time-critical functions, enabling optimization of non-time-critical functions performed by the quasi-RT RIC / non-RT RIC 242 via E2 termination in the O_DU.

[0069] The non-RT RIC 242 is coupled to the quasi-RT RIC 210 via an A1 interface 244. The service management and orchestration framework 240 collects data using the FCAPS (Fault Management, Configuration Management, Accounting, Performance Management, Security) interface.

[0070] The O1 interface 250 and the open fronthaul M-plane interface 270 provide an FCAPS interface with the exchange of configuration, reconfiguration, registration, security, performance, and monitoring aspects with individual nodes such as the O-DU 220, O-CU-UP 221, O-CU-CP 222, O-RU 260, and non-RT RIC 242 and RAN nodes, e.g., O-gNB 223 and O-eNB 224.

[0071] The service management and orchestration framework 240 collects data and sets policies that are provided to the non-RT RIC 242. For example, a policy may be developed that the number of users should not exceed 100 connected users for a particular node, such as the O-CU-CP node 222. The policy is based on the collected data regarding performance parameters. The policy is then provided by the non-RT RIC 242 to the quasi-RT RIC 210 to optimize some network functions. For example, a policy may be set that limits the number of connected users to 100, which is a key parameter for optimal network operation.

[0072] However, a policy regarding a limit of 100 connected users may not result in optimal performance because the O-CU-CP node 222's view is a limit of 80 connected users. The O-CU-CP node 222 may determine on its own that 80 connected users is the limit because the O-CU-CP node 222 experiences a performance degradation in response to having 100 connected users. Alternatively, the O-CU-CP node 222 may determine that the limit is 120 connected users because the O-CU-CP node 222's resources are underutilized and the resource allocation is underutilized. The quasi-RT RIC 210 notifies the non-RT RIC 242 that the quasi-RT RIC 210 can make the decision because the quasi-RT RIC 310 is better positioned than the non-RT RIC 242. However, this decision does not involve a time-critical function, but rather a non-time-critical function.

[0073] In at least another embodiment, the intelligent RAN optimization framework allows the O-RU 260 to handle time-critical and non-time-critical functions, as described below, despite the lack of a link between the quasi-RT RIC 210. The O-RU 260 operates, for example, at a 50-200 nanosecond level, compared to the 1-100 millisecond level of the quasi-RT RIC 210. O-RU 260 functions do not operate at the 50-200 nanosecond level. There are certain functions that can operate at the 50 millisecond level.

[0074] The O-RU 260 determines whether the O-RU functions are time-critical or non-time-critical. The intelligent RAN optimization framework allows the O-RU 260 to offload non-time-critical functions to the quasi-RT RIC 210 / non-RT RIC 242 via E2 termination at the O-DU, while the O-RU 260 processes the time-critical functions. For example, time-critical functions are sensitive to latency, and using the quasi-RT RIC 210 / non-RT RIC 242 for time-critical functions impacts the performance of the O-RU 260. Therefore, the O-RU 260 functions are divided into time-critical functions that are optimized locally by the O-RU 260 and non-time-critical functions that are optimized centrally by the quasi-RT RIC 210 / non-RT RIC 242. The decision of whether a function is time-critical and should be processed by the O-RU 260 or non-time-critical and should be processed by the non-RT RIC 242 is made by the O-RU node 260. In response to the O-RU 260 function being a non-critical function, non-RT RIC service(s) are initiated for the non-critical RAN function of the O-RU node 260 so that the non-critical RAN function of the O-RU node 260 is handled by the quasi-RT RIC 210 / non-RT RIC 242. The O-RU 260 oversees performance optimization of the function being optimized by the quasi-RT RIC 210 / non-RT RIC 242.

[0075] 8 and 8C (continued) are a flowchart 800 of a method for providing RAN optimization using RIC or local services, according to at least one embodiment.

[0076] 8 and 8C, the method begins at S802, where one or more RAN nodes are provisioned at S810. Referring to FIG. 2, the E2 node includes RAN nodes such as an ORAN distributed unit (O-DU) 220, an O-centralized unit control plane (O-CU-CP) 221, an O-CU user plane (O-CU-UP) 222, an O-next generation node B (O-gNB) 223, and an O-evolved node B (O-eNB) 224. The O-DU 220 is coupled to an ORAN radio unit (O-RU) 260 using an open fronthaul M-plane interface 270. The open fronthaul M-plane interface 270 also enables communication between the O-RU 260 and the service management and orchestration framework 240 and non-RT RIC 242.

[0077] The one or more RAN nodes may be E2 nodes S814 or O-RU nodes S866. An optimization subscription service is initiated S818 to process optimization of E2 node performance of one or more RAN nodes by a quasi-real-time RAN intelligent controller (RIC) (quasi-RT RIC). Referring to FIG. 4, the RAN node 410 initiates the subscription procedure by sending a setup request message 432 containing appropriate data to the quasi-RT RIC 420. For example, the setup request message 432 includes a RAN capability definition that defines the RAN capabilities supported by the RAN node 410, node identifier (ID) information, configurations supported by the RAN node 410, etc. The quasi-RT RIC 420 responds with a setup response message 434 containing appropriate data, such as a list of accepted RAN capabilities and associated RAN capability IDs, and a list of rejected RAN capabilities and associated RAN capability IDs, as well as the reason for the rejection. The RAN capability ID is an indicator of a network capability. The subscription is associated with the network capability associated with the RAN capability ID. The quasi-RT RIC 420 may also send a RIC subscription request message 436 to the RAN node. The RIC subscription request message 436 is used to create a new subscription in the RAN node 410 at the request of the quasi-RT RIC 420 and includes one or more of a RIC request ID, a RAN capability ID, a RIC subscription details, a RIC event trigger definition, a sequence of actions, a RIC action ID, a RIC action type, a RIC action definition, and a RIC follow-on action. The RAN node 410 responds by sending a RIC subscription response message 438 to the quasi-RT RIC 420 to accept the request from the quasi-RT RIC 420 to create a new event in the RAN node 410. The RIC subscription response message 438 includes one or more of a RIC request ID, a RAN capability ID, a RIC action approval list and associated RIC action IDs, and a RIC action non-approval list and associated RIC action IDs, and a cause.Thus, messages 1-4 of the RIC service initiation process are part of the existing interface connection establishment. Messages 1-4 of the RIC service initiation process 430, ie, 432, 434, 436, 438, expose optimization capabilities, network capabilities, etc.

[0078] The RAN node, such as the E2 node determined in S814, monitors S822 the performance of the functionality optimized by the quasi-RT RIC. Referring to Figure 4, the RAN node 410 continues to monitor the performance.

[0079] A determination is made S826 whether the performance optimization of the RAN node by the near real-time RIC is below a first predetermined threshold. Referring to Figure 4, the RAN node 410 determines whether the centralized optimization provided by the near real-time RIC 420 is acceptable.

[0080] In response to the performance optimization by the near real-time RIC not being less than the first predetermined threshold S830, the process returns to having the RAN node, e.g., the E2 node, continue to monitor the performance of the function optimized by the near real-time RIC S822. Referring to Figure 4, the RAN node 410 determines that a local algorithm can provide better performance optimization, for example, based on determining whether the performance optimization of the RAN node 410 by the near real-time RIC 420 is less than the first predetermined threshold.

[0081] In response to the performance optimization by the near real-time RIC being below a predetermined threshold S834, the RAN node, e.g., the E2 node, suspends the subscription to the near-RT RIC service(s) S838. Referring to Figure 4, in response to the RAN node 410 determining that a local algorithm can provide better performance optimization based, for example, on the performance of the near-RT RIC 420 optimization being below a predetermined threshold, the RAN node 410 executes a RIC service suspension process 450. The RAN node 410 sends a RIC subscription suspension message 452 to the near-RT RIC 420.

[0082] The E2 node receives a quasi-RT RIC pause acknowledgement S842 from the quasi-RT RIC. Referring to FIG. 4, in response, the quasi-RT RIC 420 can send a RIC subscription pause acknowledgement message 454 to the RAN node 410. The RAN node 410 can then take over performance optimization of the RAN node 410 using a local optimization algorithm. For example, the RAN node 410 may determine that subscriptions for X, Y, and Z exist and that there is a problem with subscription X but not with Y and Z. Thus, the RAN node 410 can pause subscription X. The RIC subscription pause message 452 can provide the quasi-RT RIC 420 with information identifying the reason the RAN node 410 is attempting to pause subscription X. Thus, through the RIC subscription pause message 452 and the RIC subscription pause acknowledgement message 454, the RAN node 410 and the quasi-RT RIC 420 can reach an agreement on how to optimize performance of the RAN node 410.

[0083] The E2 node monitors S846 the performance of the RAN node, e.g., the functionality optimized by the E2 node. Referring to Figure 4, the RAN node 410 continues to monitor the performance.

[0084] A determination is made S850 whether the performance optimization by the RAN node, for example the E2 node, is below a second predetermined threshold. Referring to Figure 4, the RAN node 410 determines whether the performance optimization by the RAN node 410 is below a second predetermined threshold.

[0085] In response to the performance optimization by the RAN node, e.g., the E2 node, not being below the second predetermined threshold S854, the process returns to having the RAN node, e.g., the E2 node, continue to monitor the performance of the function optimized by the E2 node S846. Referring to Figure 4, in response to the performance optimization not being below the second threshold, the RAN node 410 continues to monitor the performance of the RAN node 410.

[0086] In response to the performance optimization by the E2 node being less than a second predetermined threshold S858, the RAN node, e.g., the E2 node, initiates quasi-RT RIC subscription resumption S862. Referring to FIG. 4, in response to the performance optimization being less than the second threshold, the RAN node 410 can cause the quasi-RT RIC 420 to begin processing the performance optimization. For example, in response to a change in performance, such as improved coverage or fewer routine outages, the RAN node 410 can communicate with the quasi-RT RIC 420 to cause the quasi-RT RIC 420 to resume performance optimization for the RAN node 410. A RIC service resumption process 470 is used to resume RIC service. The RAN node 410 sends a RIC subscription resume message 472 to the quasi-RT RIC 420. For example, the RAN node 410 sends the RIC subscription resume message 472 identifying subscription X to be processed again by the quasi-RT RIC 420. In response, the quasi-RT RIC 420 responds with a RIC subscription request message 474 to the RAN node 410. Again, the RIC subscription request message 474 is used to create a subscription, for example, to resume subscription X, and includes one or more of a RIC request ID, a RAN capability ID, a RIC subscription details, a RIC event trigger definition, a sequence of actions, a RIC action ID, a RIC action type, a RIC action definition, and a RIC follow-on action. The RAN node 410 responds to the subscription request message 474 from the quasi-RT RIC 420 by sending a RIC subscription response message 476 to the quasi-RT RIC 420 to accept the request from the quasi-RT RIC / non-RT RIC 420 to have the quasi-RT RIC 420 resume subscription X.Thus, via the RIC Subscription Resume message 472, the RIC Subscription Request message 474, and the RIC Subscription Response message 476, the RAN node 410 and the quasi-RT RIC 420 can reach an agreement that the quasi-RT RIC 420 will resume processing performance optimization for the RAN node 410, including agreement on the parameters of subscription X.

[0087] The process returns to S822, having the RAN node, e.g., the E2 node, monitor the performance of the functionality optimized by the RIC, e.g., the quasi-RT RIC. Referring to FIG. 4, the RAN node 410 returns to monitoring the performance optimization by the quasi-RT RIC 420. The RIC service suspension process 450 and the RIC service resume process 470 may be repeated. However, the cycle between the RIC service suspension process 450 and the RIC service resume process 470 should not be performed too frequently. Therefore, a timer may be used to control the frequency of transitions between the RIC service suspension process 450 and the RIC service resume process 470. For example, a timer may be used to cause the RAN node 410 to wait a predetermined period of time, e.g., 1 hour, 4 hours, 10 hours, etc., before performing the RIC service suspension process 450 again. The timer may depend on the network functionality involved.

[0088] Based on whether the RAN node is an O-RU node S866, it is determined whether optimizing the performance of the O-RU node of one or more RAN nodes involves optimizing time-critical O-RU functions or non-critical O-RU functions S870. Referring to FIG. 2, the same intelligent RAN optimization framework can be extended to non-RT RIC nodes. RIC services are not supported by the O-RU 260, and due to the time-critical nature of the O-RU 260's functions, there is no E2 interface between the O-RU 260 and the quasi-RT RIC 210 or non-RT RIC 242. The intelligent RAN optimization framework allows the O-RU 260 to offload non-time-critical functions to the quasi-RT RIC 210 / non-RT RIC 242 via E2 termination at the O-DU, while the O-RU 260 handles the time-critical functions. For example, time-critical functions are sensitive to latency, and using the quasi-RT RIC 210 / non-RT RIC 242 for time-critical functions impacts the performance of the O-RU 260. Thus, the functionality of O-RU 260 is divided into time-critical functions that are optimized locally by O-RU 260 and non-time-critical functions that are optimized centrally by quasi-RT RIC 210 / non-RT RIC 242. The decision as to whether a function is time-critical and should be processed by O-RU 260 or non-time-critical and should be processed by quasi-RT RIC 210 / non-RT RIC 242 is made by O-RU node 260.

[0089] In response to S874 that the functionality of a RAN node, e.g., an O-RU, is non-time critical, the non-time critical functionality of the O-RU is managed by quasi-RT RIC / non-RT RIC services via the E2 interface and E2 termination at the O-DU S878. Referring to FIG. 2 , in response to the functionality of the O-RU 260 being non-time critical, non-RT RIC service(s) are initiated for the non-critical RAN functionality of the O-RU node 260 so that the non-critical RAN functionality of the O-RU node 260 is handled by the quasi-RT RIC 210 / non-RT RIC 242. The O-RU 260 monitors performance optimization of the functionality being optimized by the quasi-RT RIC 210 / non-RT RIC 242.

[0090] The process returns to processing at the other RAN node S812.

[0091] In response to the O-RU node functionality being time-critical S882, the O-RU processes S886 optimization service(s) for the O-RU node's time-critical RAN functionality. Referring to Figure 2, the intelligent RAN optimization framework enables the O-RU 260 to process time-critical functionality.

[0092] The process returns to processing at the other RAN node S812.

[0093] In at least one embodiment, a method for providing intelligent Radio Access Network (RAN) optimization includes provisioning one or more Radio Access Network (RAN) nodes; initiating an optimization subscription service to handle E2 node performance optimization of the one or more RAN nodes by a near real-time RAN intelligent controller (RIC) (near-RT RIC); determining whether performance of the E2 node as a result of the E2 node performance optimization by the near-RT RIC is below a first predetermined threshold; and in response to determining that the E2 node performance is below the first predetermined threshold, switching to the E2 node performance optimization by the E2 node; and otherwise continuing to handle the E2 node performance optimization by the near-RT RIC.

[0094] FIG. 9 is a high-level functional block diagram of a processor-based system 900 according to at least one embodiment.

[0095] In at least one embodiment, the processing circuit 900 provides an intelligent RAN optimization framework. The processing circuit 900 implements the intelligent RAN optimization framework using a processor 902. The processing circuit 900 also includes a non-transitory computer-readable storage medium 904 used to implement the intelligent RAN optimization framework. The non-transitory computer-readable storage medium 904 is encoded with, i.e., stores, among other things, instructions 906, i.e., computer program code, that are executed by the processor 902 to cause the processor 902 to perform operations to provide RAN optimization using RIC services or local services. Execution of the instructions 906 by the processor 902 represents (at least in part) an application that implements at least a portion of a methodology described herein (hereinafter, the described process and / or methodology) in accordance with one or more embodiments.

[0096] The processor 902 is electrically coupled to a non-transitory computer-readable storage medium 904 via a bus 908. The processor 902 is electrically coupled to an input / output (I / O) interface 910 by the bus 908. A network interface 912 is also electrically connected to the processor 902 via the bus 908. The network interface 912 is connected to a network 914 such that the processor 902 and the non-transitory computer-readable storage medium 904 connect to external elements via the network 914. The processor 902 is configured to execute instructions 906 encoded in the non-transitory computer-readable storage medium 904 to enable the processing circuit 900 to perform at least a portion of a process and / or method. In one or more embodiments, the processor 902 is a central processing unit (CPU), a multiprocessor, a distributed processing system, an application specific integrated circuit (ASIC), and / or other suitable processing unit.

[0097] Processing circuit 900 includes an I / O interface 910. I / O interface 910 is coupled to external circuitry. In one or more embodiments, I / O interface 910 includes a keyboard, keypad, mouse, trackball, trackpad, touch screen, and / or cursor direction keys for communicating information and commands to processor 902.

[0098] The processing circuit 900 also includes a network interface 912 coupled to the processor 902. The network interface 912 enables the processing circuit 900 to communicate with a network 914 to which one or more other computer systems are connected. The network interface 912 includes a wireless network interface such as Bluetooth, Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX), General Packet Radio Service (GPRS), or Wideband Code Division Multiple Access (WCDMA), or a wired network interface such as Ethernet, Universal Serial Bus (USB), or Institute of Electrical and Electronics Engineers (IEEE) 864.

[0099] The processing circuit 900 is configured to receive information via an I / O interface 910. The information received via the I / O interface 910 includes one or more of instructions, data, design rules, libraries of cells, and / or other parameters for processing by the processor 902. The information is transferred to the processor 902 via the bus 908. The processing circuit 900 is configured to receive information related to a user interface (UI) 920 via the I / O interface 910. The information is stored in the non-transitory computer-readable storage medium 904 as the UI 920.

[0100] In one or more embodiments, one or more non-transitory computer-readable storage media 904 store instructions 906 (in compressed or uncompressed format) that can be used to program a computer, processor, or other electronic device to perform the processes or methods described herein. The one or more non-transitory computer-readable storage media 904 include one or more of an electronic storage medium, a magnetic storage medium, an optical storage medium, a quantum storage medium, etc.

[0101] For example, the non-transitory computer-readable storage medium 904 may include, but is not limited to, a hard drive, a floppy diskette, an optical disk, read-only memories (ROMs), random access memories (RAMs), erasable programmable ROMs (EPROMs), electrically erasable programmable ROMs (EEPROMs), flash memory, a magnetic or optical card, a solid-state memory device, or any other type of physical medium suitable for storing electronic instructions. In one or more embodiments using an optical disk, the one or more non-transitory computer-readable storage media 904 include a Compact Disk-Read Only Memory (CD-ROM), a Compact Disk-Read / Write (CD-R / W), and / or a Digital Video Disc (DVD).

[0102] In one or more embodiments, the non-transitory computer-readable storage medium 904 stores instructions 906 configured to cause the processor 902 to perform at least a portion of a process and / or method for implementing intelligent RAN optimization 922 by using RIC services or local services to provide RAN optimization. In one or more embodiments, the non-transitory computer-readable storage medium 904 also stores information, such as algorithms, that facilitate performing at least a portion of a process and / or method for implementing intelligent RAN optimization 922 by using RIC services or local services to provide RAN optimization.

[0103] In at least one embodiment, the processor 902 is configured to provide Radio Access Network (RAN) functionality to a mobile network, provide RAN functionality to one or more RAN nodes in the mobile network, initiate an optimization subscription service to handle optimization of E2 node performance of the one or more RAN nodes by a near real-time RAN intelligent controller (RIC) (near-RT RIC), determine whether performance of the E2 node as a result of the optimization of E2 node performance by the near-RT RIC is below a first predetermined threshold, and in response to determining that the performance of the E2 node is below the first predetermined threshold, switch to optimization of E2 node performance by the E2 node; and otherwise continue to handle optimization of E2 node performance by the near-RT RIC. The processor 902 is further configured to: determine whether performance of the E2 node by the E2 node is below a second predetermined threshold; and in response to the performance of the E2 node being below the second predetermined threshold, resume an optimization subscription service for processing optimization of the performance of the E2 node by the quasi-RT RIC; receive a subscription request from the quasi-RT RIC for causing the quasi-RT RIC to resume processing optimization of the performance of the RAN function; and resume the optimization subscription service for processing optimization of the performance of the RAN function by the quasi-RT RIC by sending a subscription resume message to the quasi-RT RIC, receiving a subscription request from the quasi-RT RIC for causing the quasi-RT RIC to resume processing optimization of the performance of the RAN function; and sending a subscription response to the quasi-RT RIC confirming that the quasi-RT RIC resumes processing optimization of the performance of the RAN function.The processor 902 is further configured to initiate an optimization subscription service for processing the optimization of the performance of the RAN function by the quasi-RT RIC by sending a setup request to the quasi-RT RIC identifying at least one function of the RAN function to be optimized, receiving a setup response from the quasi-RT RIC confirming the at least one function of the RAN function to be optimized, receiving a subscription request for having the quasi-RT RIC process the optimization of performance of the at least one function of the RAN function, and sending a subscription response to the quasi-RT RIC confirming that the quasi-RT RIC processes the optimization of the at least one function. The processor 902 is further configured to switch to the optimization of the performance of the RAN function by sending a subscription pause message to the quasi-RT RIC instructing the quasi-RT RIC to pause processing the optimization of the performance of the RAN function by the quasi-RT RIC and receiving a subscription pause acknowledgement message from the quasi-RT RIC. The processor 902 is further configured to determine whether the optimization of the performance of the RAN function involves optimization of a time-critical RAN function or a non-critical RAN function in response to determining that the RAN function is for an O-RU node. The processor 902 is further configured to process the optimization of the time-critical RAN function by the processor in response to determining that the optimization of the performance of the RAN function involves optimizing the time-critical RAN function, and to process the optimization of the non-time-critical RAN function by the non-real-time RIC in response to determining that the optimization of the performance of the RAN function involves optimizing the non-time-critical RAN function.

[0104] Embodiments described herein provide methods that provide one or more advantages. For example, an intelligent radio access network (RAN) optimization framework provides performance improvements by using methods that achieve optimal performance, whether the methods are centralized optimization controlled by a RAN intelligent controller (RIC) or local optimization controlled by RAN nodes over the E2 interface. The intelligent radio access network (RAN) optimization framework provides improved handling of delay-sensitive use cases and RAN optimization functions. The intelligent radio access network (RAN) optimization framework also involves and uses the RIC as needed for RAN optimization functions.

[0105] In accordance with at least one embodiment, a method for providing intelligent Radio Access Network (RAN) optimization includes provisioning one or more Radio Access Network (RAN) nodes; initiating an optimization subscription service to handle E2 node performance optimization of the one or more RAN nodes by a near real-time RAN intelligent controller (RIC) (near-RT RIC); determining whether performance of the E2 node as a result of the E2 node performance optimization by the near-RT RIC is below a first predetermined threshold; and in response to determining that the E2 node performance is below the first predetermined threshold, switching to E2 node performance optimization by the E2 node; otherwise, continuing to handle E2 node performance optimization by the near-RT RIC.

[0106] In a method according to at least one embodiment, the method further includes determining whether performance of the E2 node by the E2 node is below a second predetermined threshold, and in response to the performance of the E2 node being below the second predetermined threshold, resuming an optimization subscription service for processing optimization of performance of the E2 node by the quasi-RT RIC, and otherwise continuing to process optimization of performance of the E2 node by the E2 node.

[0107] In a method according to at least one embodiment, resuming an optimization subscription service for processing performance optimization of an E2 node by a quasi-RT RIC includes sending a subscription resume message to the quasi-RT RIC, receiving a subscription request from the quasi-RT RIC for the quasi-RT RIC to resume processing performance optimization of the E2 node, and sending a subscription response to the quasi-RT RIC confirming that the quasi-RT RIC will resume processing performance optimization of the E2 node.

[0108] In a method according to at least one embodiment, initiating an optimization subscription service for processing performance optimization of an E2 node by a quasi-RT RIC includes sending a setup request to the quasi-RT RIC identifying at least one function of the E2 node to be optimized, receiving a setup response from the quasi-RT RIC confirming the at least one function of the E2 node to be optimized, receiving a subscription request for having the quasi-RT RIC process optimization of the at least one function of the E2 node, and sending a subscription response to the quasi-RT RIC confirming that the quasi-RT RIC will process performance optimization of the at least one function of the E2 node.

[0109] In a method according to at least one embodiment, switching to E2 node performance optimization by the E2 node includes sending a subscription pause message to the quasi-RT RIC instructing the quasi-RT RIC to pause processing of E2 node performance optimization by the quasi-RT RIC, and receiving a subscription pause acknowledgement message from the quasi-RT RIC.

[0110] A method according to at least one embodiment determines whether optimizing O-RU node performance of one or more RAN nodes involves optimizing time-critical O-RU functions or non-critical O-RU functions based on the one or more RAN nodes being O-RU nodes.

[0111] In a method according to at least one embodiment, the method further includes, in response to determining that optimizing the performance of the O-RU function involves optimizing the time-critical O-RU function, processing the optimization of the time-critical O-RU function by the O-RU, and, in response to determining that optimizing the performance of the O-RU function involves optimizing the non-time-critical O-RU function, processing the optimization of the non-time-critical O-RU function by the non-real-time RIC.

[0112] In at least one embodiment, a Radio Access Network (RAN) node includes a memory that stores computer-readable instructions and a processor coupled to the memory, the processor configured to execute the computer-readable instructions to perform operations including: providing RAN functionality to one or more RAN nodes in a mobile network; initiating an optimization subscription service to handle optimization of E2 node performance of the one or more RAN nodes by a near real-time RAN intelligent controller (RIC) (near-RT RIC); determining whether performance of the E2 node as a result of the optimization of E2 node performance by the near-RT RIC is below a first predetermined threshold; and in response to determining that the performance of the E2 node is below the first predetermined threshold, switching to optimization of E2 node performance by the E2 node; and otherwise continuing to handle optimization of E2 node performance by the near-RT RIC.

[0113] In at least one embodiment, the processor is further configured to determine whether performance of the E2 node by the E2 node is below a second predetermined threshold, and in response to the performance of the E2 node being below the second predetermined threshold, resume an optimization subscription service for processing optimization of performance of the E2 node by the quasi-RT RIC, and otherwise continue processing optimization of performance of the E2 node by the E2 node.

[0114] In at least one embodiment, the processor is further configured to resume an optimization subscription service for processing optimization of performance of the RAN function by the quasi-RT RIC by sending a subscription resume message to the quasi-RT RIC, receiving a subscription request from the quasi-RT RIC for the quasi-RT RIC to resume processing optimization of performance of the RAN function, and sending a subscription response to the quasi-RT RIC confirming that the quasi-RT RIC will resume processing optimization of performance of the RAN function.

[0115] In at least one embodiment, the processor is further configured to initiate an optimization subscription service for processing the optimization of performance of the RAN function by the quasi-RT RIC by sending a setup request to the quasi-RT RIC that identifies at least one function of the RAN function to be optimized, receiving a setup response from the quasi-RT RIC confirming the at least one function of the RAN function to be optimized, receiving a subscription request for having the quasi-RT RIC process the optimization of performance of the at least one function of the RAN function, and sending a subscription response to the quasi-RT RIC confirming that the quasi-RT RIC will process the optimization of the at least one RAN function.

[0116] In at least one embodiment, the processor is further configured to switch to optimizing the performance of the RAN function by sending a subscription pause message to the quasi-RT RIC instructing the quasi-RT RIC to pause processing of the optimization of the performance of the RAN function and receiving a subscription pause acknowledgement message from the quasi-RT RIC.

[0117] In at least one embodiment, the processor is further configured to, in response to the one or more RAN nodes being O-RU nodes, determine whether optimizing the performance of the O-RU involves optimizing a time-critical RAN function or a non-critical RAN function.

[0118] In at least one embodiment, the processor is further configured to process the optimization of the time-critical RAN function by the processor in response to determining that optimizing the performance of the RAN function involves optimizing the time-critical RAN function, and to process the optimization of the non-time-critical RAN function by the non-real-time RIC in response to determining that optimizing the performance of the RAN function involves optimizing the non-time-critical RAN function.

[0119] In at least one embodiment, a non-transitory computer-readable medium stores computer-readable instructions that, when executed by a processor, cause the processor to perform operations including provisioning one or more Radio Access Network (RAN) nodes; initiating an optimization subscription service to handle optimization of E2 node performance of the one or more RAN nodes by a near real-time RAN intelligent controller (RIC) (near-RT RIC); determining whether performance of the E2 node as a result of the optimization of E2 node performance by the near-RT RIC is below a first predetermined threshold; and, in response to determining that the performance of the E2 node is below the first predetermined threshold, switching to optimization of E2 node performance by the E2 node; and otherwise continuing to handle optimization of E2 node performance by the near-RT RIC.

[0120] In the non-transitory computer-readable medium according to at least one embodiment, the operations further include determining whether performance of the E2 node by the E2 node is below a second predetermined threshold, and in response to the performance of the E2 node being below the second predetermined threshold, resuming an optimization subscription service for processing optimization of performance of the E2 node by the quasi-RT RIC, and otherwise continuing to process optimization of performance of the E2 node by the E2 node.

[0121] In at least one embodiment, in a non-transitory computer-readable medium, resuming an optimization subscription service for processing performance optimization of an E2 node by a quasi-RT RIC includes sending a subscription resume message to the quasi-RT RIC, receiving a subscription request from the quasi-RT RIC for the quasi-RT RIC to resume processing performance optimization of the E2 node, and sending a subscription response to the quasi-RT RIC confirming that the quasi-RT RIC will resume processing performance optimization of the E2 node.

[0122] In a non-transitory computer-readable medium according to at least one embodiment, initiating an optimization subscription service for processing performance optimization of an E2 node by a quasi-RT RIC includes sending a setup request to the quasi-RT RIC identifying at least one function of the E2 node to be optimized, receiving a setup response from the quasi-RT RIC confirming the at least one function of the E2 node to be optimized, receiving a subscription request for having the quasi-RT RIC process optimization of the at least one function of the E2 node, and sending a subscription response to the quasi-RT RIC confirming that the quasi-RT RIC will process performance optimization of the at least one function of the E2 node.

[0123] In at least one embodiment of a non-transitory computer-readable medium, switching to optimizing performance of the E2 node by the E2 node includes sending a subscription pause message to the quasi-RT RIC instructing the quasi-RT RIC to pause processing of performance optimization of the E2 node by the quasi-RT RIC, and receiving a subscription pause acknowledgement message from the quasi-RT RIC.

[0124] In the non-transitory computer-readable medium according to at least one embodiment, the operations further include, in response to the one or more RAN nodes being O-RU nodes, determining whether optimizing performance of the O-RU node involves optimizing a time-critical O-RU function or a non-critical O-RU function; in response to determining that optimizing performance of the O-RU function involves optimizing the time-critical O-RU function, processing the optimization of the time-critical O-RU function by the O-RU; and in response to determining that optimizing performance of the O-RU function involves optimizing the non-time-critical O-RU function, processing the optimization of the non-time-critical O-RU function by the non-real-time RIC.

[0125] Separate instances of these programs may run on or be distributed on any number of separate computer systems. Thus, although certain steps may be described as being performed by a particular device, software program, process, or entity, this is not necessarily the case. Various alternative implementations will be appreciated by those skilled in the art.

[0126] Moreover, those skilled in the art will readily recognize that the above-described techniques can be utilized in a variety of devices, environments, and contexts. Although the embodiments have been described in language specific to structural features or methodological acts, the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claims.

Claims

1. 1. A method for providing intelligent radio access network (RAN) optimization, comprising: Provisioning one or more radio access network (RAN) nodes; Initiating an optimization subscription service for handling optimization of E2 node performance of the one or more RAN nodes by a near real-time RAN intelligent controller (RIC) (near-RT RIC); determining whether the performance of the E2 node as a result of the optimization of the performance of the E2 node by the quasi-RT RIC is below a first predetermined threshold; in response to determining that the performance of the E2 node is below the first predetermined threshold, switching to optimizing the performance of the E2 node by the E2 node, and otherwise continuing to process the optimization of the performance of the E2 node by the quasi-RT RIC.

2. 2. The method of claim 1, further comprising: determining whether the performance of the E2 node by the E2 node is below a second predetermined threshold; and in response to the performance of the E2 node being below the second predetermined threshold, restarting the optimization subscription service for processing the optimization of the performance of the E2 node by the quasi-RT RIC; and otherwise continuing to process the optimization of the performance of the E2 node by the E2 node.

3. 3. The method of claim 2, wherein resuming an optimization subscription service for processing the optimization of the performance of the E2 node by the quasi-RT RIC comprises: sending a subscription resume message to the quasi-RT RIC; receiving a subscription request from the quasi-RT RIC to cause the quasi-RT RIC to resume processing the optimization of the performance of the E2 node; and sending a subscription response to the quasi-RT RIC confirming that the quasi-RT RIC will resume processing the optimization of the performance of the E2 node.

4. 2. The method of claim 1, wherein initiating the optimization subscription service for processing the optimization of the performance of the E2 node by the quasi-RT RIC comprises: sending a setup request to the quasi-RT RIC identifying at least one function of the E2 node to be optimized; receiving a setup response from the quasi-RT RIC confirming the at least one function of the E2 node to be optimized; receiving a subscription request to have the quasi-RT RIC process the optimization of the at least one function of the E2 node; and sending a subscription response to the quasi-RT RIC confirming that the quasi-RT RIC will process the optimization of the performance of the at least one function of the E2 node.

5. 2. The method of claim 1, wherein switching to the optimization of the performance of the E2 node by the E2 node comprises: sending a subscription pause message to the quasi-RT RIC instructing the quasi-RT RIC to pause processing of the optimization of the performance of the E2 node by the quasi-RT RIC; and receiving a subscription pause acknowledgement message from the quasi-RT RIC.

6. 2. The method of claim 1, further comprising: determining, based on the one or more RAN nodes being O-RU nodes, whether the optimization of the performance of the O-RU nodes of the one or more RAN nodes involves optimizing time-critical O-RU functions or non-critical O-RU functions.

7. In response to determining that the optimization of the performance of the O-RU functionality involves the optimization of a time-critical O-RU functionality, processing the optimization of the time-critical O-RU functionality by the O-RU; In response to determining that the optimization of the performance of the O-RU function involves the optimization of a non-time-critical O-RU function, processing the optimization of the non-time-critical O-RU function by a non-real-time RIC; The method of claim 6 further comprising:

8. a memory storing computer readable instructions; a processor, coupled to the memory, operable to execute the computer-readable instructions, providing RAN functionality to one or more RAN nodes in a mobile network; Initiating an optimization subscription service for handling optimization of E2 node performance of the one or more RAN nodes by a near real-time RAN intelligent controller (RIC) (near-RT RIC); determining whether the performance of the E2 node as a result of the optimization of the performance of the E2 node by the quasi-RT RIC is below a first predetermined threshold; a processor configured to perform operations including: in response to determining that the performance of the E2 node is below the first predetermined threshold, switching to optimizing the performance of the E2 node by the E2 node; and otherwise continuing to process the optimization of the performance of the E2 node by the quasi-RT RIC; A radio access network (RAN) node comprising:

9. 9. The RAN node of claim 8, further configured: the processor determines whether the performance of the E2 node by the E2 node is below a second predetermined threshold; and in response to the performance of the E2 node being below the second predetermined threshold, resumes the optimization subscription service for processing the optimization of the performance of the E2 node by the quasi-RT RIC; and otherwise, the processor continues to process the optimization of the performance of the E2 node by the E2 node.

10. 10. The RAN node of claim 9, wherein the processor is further configured to resume an optimization subscription service for processing the optimization of the performance of the RAN function by the quasi-RT RIC by sending a subscription resume message to the quasi-RT RIC, receiving from the quasi-RT RIC a subscription request for causing the quasi-RT RIC to resume processing the optimization of the performance of the RAN function, and sending to the quasi-RT RIC a subscription response confirming that the quasi-RT RIC will resume processing the optimization of the performance of the RAN function.

11. 10. The RAN node of claim 8, wherein the processor is further configured to initiate the optimization subscription service for processing the optimization of the performance of the RAN function by the quasi-RT RIC by sending a setup request to the quasi-RT RIC identifying at least one function of the RAN function to be optimized, receiving a setup response from the quasi-RT RIC confirming the at least one function of the RAN function to be optimized, receiving a subscription request to have the quasi-RT RIC process the optimization of the performance of the at least one function of the RAN function, and sending a subscription response to the quasi-RT RIC confirming that the quasi-RT RIC will process the optimization of the at least one function.

12. 9. The RAN node of claim 8, wherein the processor is further configured to switch to the optimization of the performance of the RAN function by sending to the quasi-RT RIC a subscription pause message instructing the quasi-RT RIC to pause processing of the optimization of the performance of the RAN function by the quasi-RT RIC, and receiving a subscription pause acknowledgement message from the quasi-RT RIC.

13. 9. The RAN node of claim 8, wherein the processor is further configured to, in response to the one or more RAN nodes being O-RU nodes, determine whether the optimization of the performance of the O-RU involves optimizing time-critical RAN functions or non-critical RAN functions.

14. In response to the processor determining that the optimization of the performance of the RAN function involves the optimization of a time-critical RAN function, processing the optimization of the time-critical RAN function by the processor; 14. The RAN node of claim 13, further configured to, in response to determining that the optimization of the performance of the RAN function involves the optimization of a non-time-critical RAN function, process the optimization of the non-time-critical RAN function with a non-real-time RIC.

15. When executed by a processor, the processor: Provisioning one or more radio access network (RAN) nodes; Initiating an optimization subscription service for handling optimization of E2 node performance of the one or more RAN nodes by a near real-time RAN intelligent controller (RIC) (near-RT RIC); determining whether the performance of the E2 node as a result of the optimization of the performance of the E2 node by the quasi-RT RIC is below a first predetermined threshold; a non-transitory computer-readable medium storing computer-readable instructions to perform operations including: in response to determining that the performance of the E2 node is below the first predetermined threshold, switching to optimizing the performance of the E2 node by the E2 node; and otherwise continuing to process the optimization of the performance of the E2 node by the quasi-RT RIC.

16. 16. The non-transitory computer-readable medium of claim 15, further comprising: determining whether the performance of the E2 node by the E2 node is below a second predetermined threshold; and in response to the performance of the E2 node being below the second predetermined threshold, restarting the optimization subscription service for processing the optimization of the performance of the E2 node by the quasi-RT RIC; and otherwise continuing to process the optimization of the performance of the E2 node by the E2 node.

17. 17. The non-transitory computer-readable medium of claim 16, wherein resuming the optimization subscription service for processing the optimization of the performance of the E2 node by the quasi-RT RIC comprises: sending a subscription resume message to the quasi-RT RIC; receiving a subscription request from the quasi-RT RIC to cause the quasi-RT RIC to resume processing the optimization of the performance of the E2 node; and sending a subscription response to the quasi-RT RIC confirming that the quasi-RT RIC will resume processing the optimization of the performance of the E2 node.

18. 16. The non-transitory computer-readable medium of claim 15, wherein initiating the optimization subscription service for processing the optimization of the performance of the E2 node by the quasi-RT RIC comprises: sending a setup request to the quasi-RT RIC identifying at least one function of the E2 node to be optimized; receiving a setup response from the quasi-RT RIC confirming the at least one function of the E2 node to be optimized; receiving a subscription request to have the quasi-RT RIC process the optimization of the at least one function of the E2 node; and sending a subscription response to the quasi-RT RIC confirming that the quasi-RT RIC will process the optimization of the performance of the at least one function of the E2 node.

19. 16. The non-transitory computer-readable medium of claim 15, wherein switching to the optimization of the performance of the E2 node by the E2 node comprises: sending a subscription pause message to the quasi-RT RIC instructing the quasi-RT RIC to pause processing the optimization of the performance of the E2 node by the quasi-RT RIC; and receiving a subscription pause acknowledgement message from the quasi-RT RIC.

20. In response to the one or more RAN nodes being O-RU nodes, determining whether the optimizing of the performance of the O-RU node involves optimizing time-critical O-RU functions or non-critical O-RU functions; In response to determining that the optimization of the performance of the O-RU functionality involves the optimization of a time-critical O-RU functionality, processing the optimization of the time-critical O-RU functionality by the O-RU; In response to determining that the optimization of the performance of the O-RU function involves the optimization of a non-time-critical O-RU function, processing the optimization of the non-time-critical O-RU function by a non-real-time RIC; 16. The non-transitory computer-readable medium of claim 15, further comprising:

Images