# US 2022/0286915 A1 · Distributed ric

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0286915 A1
- Document ID: US20220286915A1
- Status: Published application
- Kind: A1
- Application number: 17/376,817
- Filed: 2021-07-15
- Published: 2022-09-08
- Earliest claimed: 2021-03-05
- Assignees: VMware, Inc.
- Applicants: VMware, Inc.
- Inventors: Aditya Gudipati; Amit Singh; Rakesh Misra; Giridhar Subramani Jayavelu
- Web page: https://patentgrep.com/patent/US20220286915A1

## CPC

- H04L 41/122: of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
- G06F 8/60: Software deployment
- G06F 9/3877: {using a secondary processor, e.g. coprocessor (peripheral processor G06F13/12)}
- G06F 9/4411: {Configuring for operating with peripheral devices; Loading of device drivers}
- G06F 9/45533: {Hypervisors; Virtual machine monitors}
- G06F 9/45545: {Guest-host, i.e. hypervisor is an application program itself, e.g. VirtualBox}
- G06F 9/4881: {Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues}
- G06F 9/5044: {considering hardware capabilities}
- G06F 9/5077: {Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455)}
- G06F 9/541: {via adapters, e.g. between incompatible applications}
- G06F 9/544: {Buffers; Shared memory; Pipes}
- G06F 9/546: {Message passing systems or structures, e.g. queues}
- G06F 11/3006: {where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50)}
- G06F 11/3409: {for performance assessment}
- G06F 11/3466: {Performance evaluation by tracing or monitoring}
- G06F 30/331: with hardware acceleration, e.g. by using field programmable gate array [FPGA] or emulation
- G06N 20/00: Machine learning
- H04B 7/0452: Multi-user MIMO systems
- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 41/5054: Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/125: involving control of end-device applications over a network
- H04L 67/535: {Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34)}
- H04L 67/565: Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561)
- H04L 67/60: Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70)
- H04L 67/61: taking into account QoS or priority requirements
- H04L 69/324: in the data link layer [OSI layer 2], e.g. HDLC
- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- H04W 8/18: Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W 8/186: {Processing of subscriber group data}
- H04W 8/20: Transfer of user or subscriber data
- H04W 12/037: of the control plane, e.g. signalling traffic
- H04W 12/08: Access security
- H04W 24/02: Arrangements for optimising operational condition
- H04W 28/06: Optimizing {the usage of the radio link}, e.g. header compression, information sizing {, discarding information (system modifying transmission characteristic according to link quality by modifying frame length H04L1/0007; dynamic adaptation of the packet size for flow control or congestion control H04L47/365)}
- H04W 28/0865: {of different Radio Access Technologies [RATs], e.g. LTE® or Wi-Fi®}
- H04W 28/16: Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
- H04W 40/246: {Connectivity information discovery}
- H04W 48/14: using user query {or user detection}
- H04W 72/02: Selection of wireless resources by user or terminal
- H04W 72/0453: Resources in frequency domain, e.g. a carrier in FDMA
- H04W 72/046: {the resource being in the space domain, e.g. beams}
- H04W 72/20: Control channels or signalling for resource management
- H04W 72/29: between an access point and the access point controlling device
- H04W 72/51: based on terminal or device properties
- H04W 72/52: based on load
- H04W 72/542: using measured or perceived quality
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 2009/4557: {Distribution of virtual machine instances; Migration and load balancing}
- G06F 2009/45579: {I/O management, e.g. providing access to device drivers or storage}
- G06F 2009/45583: {Memory management, e.g. access or allocation}
- G06F 2009/45595: {Network integration; Enabling network access in virtual machine instances}
- G06F 2209/548: Queue
- H04B 7/0634: {Antenna weights or vector/matrix coefficients}
- H04L 5/0048: {Allocation of pilot signals, i.e. of signals known to the receiver (allocation of control signalling H04L5/0053; use of control signalling H04L5/0091)}
- H04L 2212/00: Encapsulation of packets
- H04W 36/10: Reselecting an access point controller
- H04W 72/121: for groups of terminals or users
- H04W 84/042: {Public Land Mobile systems, e.g. cellular systems}
- H04W 88/085: {Access point devices with remote components}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- H04B: TRANSMISSION
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Some embodiments provide a method of performing control plane operations in a radio access network (RAN). The method deploys several machines on a host computer. On each machine, the method deploys a control plane application to perform a control plane operation. The method also configures on each machine a RAN intelligent controller (RIC) SDK to serve as an interface between the control plane application on the same machine and a set of one or more elements of the RAN. In some embodiments, the RIC SDK on each machine includes a set of network connectivity processes that establish network connections to the set of RAN elements for the control plane application. These RIC SDK processes allow the control plane application on their machine to forego having the set of network connectivity processes. In some embodiments, the set of network connectivity processes of each RIC SDK of each machine establishes and maintains network connections between the machine and the set of RAN elements used by the control plane application of the machine, and handles data packet transport to and from the set of RAN elements for the control plane application.

## Claims

### Claim 1

A method of control plane applications to communicate in a radio access network (RAN), the method comprising:
deploying a plurality of control plane applications to execute on a plurality of host computers;
deploying a plurality of RAN intelligent controllers (RICs) to execute on the plurality of host computers to implement a distributed RIC that serves as communication interface between the control plane applications.

### Claim 2 (depends on 1)

The method of claim 1 further comprising configuring a first RIC to receive application programming interface (API) calls from at least a first control plane application and to forward the API calls to at least a second control plane application.

### Claim 3 (depends on 2)

The method of claim 2, wherein the first and second control plane applications execute on the same host computer.

### Claim 4 (depends on 2)

The method of claim 2, wherein the first RIC and the first control plane application execute on a first host computer, and the second control plane application executes on a second host computer, and configuring the first RIC comprises configuring the first RIC to forward the API calls from the first control plane application to a second RIC executing on the second computer for the second RIC to forward to the second control plane application.

### Claim 5 (depends on 2)

The method of claim 2, wherein the first and second control plane applications are developed by two different application developers that use a common set of RIC APIs to communicate with each other through the distributed RIC.

### Claim 6 (depends on 2)

The method of claim 2, wherein configuring the first RIC comprises configuring the first RIC to add one or more parameters to the API calls as the first RIC forwards the API calls from the first control application to the second control application.

### Claim 7 (depends on 2)

The method of claim 2, wherein the first and second control plane applications execute on first and second machines execute of which executes on one host computer, the method further comprising configuring a MC SDK on each machine to receive and forward API calls between the distributed MC and the first and second control plane applications.

### Claim 8 (depends on 7)

The method of claim 7, wherein on each machine, the RIC SDK comprising a set of network connectivity processes that establish network connections to the set of RAN elements for the control plane application, and allowing the control plane application on that machine to forego having the set of network connectivity processes.

### Claim 9 (depends on 8)

The method of claim 8, wherein the set of network connectivity processes of each RIC SDK of each machine establishes and maintains network connections between the machine and the set of RAN elements used by the control plane application of the machine, and handles data packet transport to and from the set of RAN elements for the control plane application.

### Claim 10 (depends on 7)

The method of claim 7, wherein the control plane application on each machine communicates with the set of RAN elements through high-level API (application program interface) calls that the RAN SDK converts into low-level API calls, wherein at least a subset of the low-level API calls are specified by a standard specifying body.

### Claim 11 (depends on 7)

The method of claim 7, wherein the control plane application on each machine communicates with the set of RAN elements through high-level API (application program interface) calls that the RAN SDK converts into low-level API calls, wherein the high-level API calls are made in a high-level programming language, while the low-level API calls comprise low-level calls that establish and maintain network connections and pass data packets through these connections.

### Claim 12

A non-transitory machine readable medium storing a program which when executed by at least one processing unit of control plane applications to communicate in a radio access network (RAN), the program comprising sets of instructions for:
deploying a plurality of control plane applications to execute on a plurality of host computers;
deploying a plurality of RAN intelligent controllers (RICs) to execute on the plurality of host computers to implement a distributed RIC that serves as communication interface between the control plane applications.

### Claim 13 (depends on 12)

The non-transitory machine readable medium of claim 12, wherein the program further comprises a set of instructions for configuring a first RIC to receive application programming interface (API) calls from at least a first control plane application and to forward the API calls to at least a second control plane application.

### Claim 14 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein the first and second control plane applications execute on the same host computer.

### Claim 15 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein the first RIC and the first control plane application execute on a first host computer, and the second control plane application executes on a second host computer, and the set of instructions for configuring the first RIC comprises a set of instructions for configuring the first RIC to forward the API calls from the first control plane application to a second RIC executing on the second computer for the second RIC to forward to the second control plane application.

### Claim 16 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein the first and second control plane applications are developed by two different application developers that use a common set of RIC APIs to communicate with each other through the distributed RIC.

### Claim 17 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein the set of instructions for configuring the first RIC comprises a set of instructions for configuring the first RIC to add one or more parameters to the API calls as the first RIC forwards the API calls from the first control application to the second control application.

### Claim 18 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein the first and second control plane applications execute on first and second machines execute of which executes on one host computer, the program further comprises a set of instructions for configuring a RIC SDK on each machine to receive and forward API calls between the distributed RIC and the first and second control plane applications.

### Claim 19 (depends on 18)

The non-transitory machine readable medium of claim 18, wherein on each machine, the RIC SDK comprising a set of network connectivity processes that establish network connections to the set of RAN elements for the control plane application, and allowing the control plane application on that machine to forego having the set of network connectivity processes.

### Claim 20 (depends on 19)

The non-transitory machine readable medium of claim 19, wherein the set of network connectivity processes of each MC SDK of each machine establishes and maintains network connections between the machine and the set of RAN elements used by the control plane application of the machine, and handles data packet transport to and from the set of RAN elements for the control plane application.
