# US 2022/0286536 A1 · Ric and ric framework communication

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

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

## 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

To provide a low latency near RT RIC, some embodiments separate the RIC's functions into several different components that operate on different machines (e.g., execute on VMs or Pods) operating on the same host computer or different host computers. Some embodiments also provide high speed interfaces between these machines. Some or all of these interfaces operate in non-blocking, lockless manner in order to ensure that critical near RT RIC operations (e.g., datapath processes) are not delayed due to multiple requests causing one or more components to stall. In addition, each of these RIC components also has an internal architecture that is designed to operate in a non-blocking manner so that no one process of a component can block the operation of another process of the component. All of these low latency features allow the near RT RIC to serve as a high speed IO between the E2 nodes and the xApps.

## Claims

### Claim 1

A method of communicating between a RAN (Radio Access Network) Intelligent Controller (MC) and a MC SDK serving as an interface between an application and the MC, the method comprising:
receiving a data message to forward to the MC SDK; and
encapsulating the data message with an encapsulating header storing data needed by the MC SDK for efficient processing of the data message, said encapsulating comprising reducing a size of at least one data tuple stored in the data message before sending the data message to the MC SDK;
forwarding the encapsulated data message to the MC SDK for processing.

### Claim 2 (depends on 1)

The method of claim 1, wherein the received data message is associated with a base station component, and the data tuple that is reduced in size is an identifier identifying the base station component.

### Claim 3 (depends on 1)

The method of claim 1, wherein the received data message has an encrypted header and payload, the method further comprising decrypting the data message header but not the data message payload before encapsulating the data message with the encapsulating header and forwarding the encapsulating data message to the MC SDK with the decrypted message header and the encrypted message payload.

### Claim 4 (depends on 1)

The method of claim 1, wherein the received data message has an encrypted header and payload, the method further comprising decrypting both the data message header and the data message payload before encapsulating the data message with the encapsulating header and forwarding the encapsulating data message to the MC SDK with the decrypted message header and message payload.

### Claim 5 (depends on 1)

The method of claim 1, wherein the RIC SDK and the application execute on one machine that executes on one host computer, the MC SDK decapsulates the data message, processes the data stored in the encapsulating header, and forwards the decapsulated data message to the application.

### Claim 6 (depends on 1)

The method of claim 1, wherein the encapsulating header has an optional control information field with a variable length size.

### Claim 7 (depends on 1)

The method of claim 1, wherein the encapsulating header has a payload field with a variable length size, and the encapsulating header has a message length field that specifies a message length equal to a fixed sized encapsulating header value, plus the variable size of the optional control information field, plus the variable size of the payload field of the encapsulating data message.

### Claim 8 (depends on 7)

The method of claim 7, wherein payload field is for storing any combination of the received data message header and payload in an encoded or decoded format.

### Claim 9 (depends on 1)

The method of claim 1, wherein the RIC SDK comprises a set of network connectivity processes that establish network connections to the RIC for the application, and allowing the application to forego having the set of network connectivity processes.

### Claim 10 (depends on 9)

The method of claim 9, wherein the set of network connectivity processes of the RIC SDK establishes and maintains network connections between the RIC SDK and the RIC, and handles data packet transport to and from the RIC for the application.

### Claim 11 (depends on 1)

The method of claim 1, wherein the application communicates with the RIC through high-level API (application program interface) calls that the RIC SDK converts into low-level API calls.

### Claim 12 (depends on 12)

The method of claim 12, wherein at least a subset of the low-level API calls are specified by a standard specifying body.

### Claim 13

A non-transitory machine readable medium storing a program for facilitating communications between a RAN (Radio Access Network) Intelligent Controller (MC) and a MC SDK (software development kit) serving as an interface between an application and the MC, the program comprising sets of instructions for:
receiving a data message to forward to the MC SDK; and
encapsulating the data message with an encapsulating header storing data needed by the MC SDK for efficient processing of the data message, said encapsulating comprising reducing a size of at least one data tuple stored in the data message before sending the data message to the MC SDK;
forwarding the encapsulated data message to the MC SDK for processing.

### Claim 14 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein the received data message is associated with a base station component, and the data tuple that is reduced in size is an identifier identifying the base station component.

### Claim 15 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein the received data message has an encrypted header and payload, the program further comprising a set of instructions for decrypting the data message header but not the data message payload before encapsulating the data message with the encapsulating header and forwarding the encapsulating data message to the RIC SDK with the decrypted message header and the encrypted message payload.

### Claim 16 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein the received data message has an encrypted header and payload, the program further comprising a set of instructions for decrypting both the data message header and the data message payload before encapsulating the data message with the encapsulating header and forwarding the encapsulating data message to the RIC SDK with the decrypted message header and message payload.

### Claim 17 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein the RIC SDK and the application execute on one machine that executes on one host computer, the RIC SDK decapsulates the data message, processes the data stored in the encapsulating header, and forwards the decapsulated data message to the application.

### Claim 18 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein the encapsulating header has an optional control information field with a variable length size.

### Claim 19 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein the encapsulating header has a payload field with a variable length size, and the encapsulating header has a message length field that specifies a message length equal to a fixed sized encapsulating header value, plus the variable size of the optional control information field, plus the variable size of the payload field of the encapsulating data message.

### Claim 20 (depends on 19)

The non-transitory machine readable medium of claim 19, wherein payload field is for storing any combination of the received data message header and payload in an encoded or decoded format.
