# US 2024/0205078 A1 · Configuring different inter- and intra- communication protocols for components in a ran system

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

- Number: US 2024/0205078 A1
- Document ID: US20240205078A1
- Status: Published application
- Kind: A1
- Application number: 18/101,551
- Filed: 2023-01-25
- Published: 2024-06-20
- Earliest claimed: 2022-12-19
- Assignees: VMware, Inc.
- Applicants: VMware LLC
- Inventors: Giridhar Subramani Jayavelu; Gauresh Dilip Vanjare
- Web page: https://patentgrep.com/patent/US20240205078A1

## CPC

- H04L 41/0803: Configuration setting
- G06F 9/4451: {User profiles; Roaming}
- G06F 16/211: {Schema design and management}
- G06F 16/288: {Entity relationship models}
- H04L 41/024: {using relational databases for representation of network management data, e.g. managing via structured query language [SQL]}
- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- H04L 41/0816: the condition being an adaptation, e.g. in response to network events
- H04L 41/082: the condition being updates or upgrades of network functionality
- H04L 41/0866: Checking the configuration
- H04L 41/0886: {Fully automatic configuration}
- H04L 41/28: Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
- H04L 63/101: {Access control lists [ACL]}
- H04L 69/08: Protocols for interworking; Protocol conversion
- H04W 16/10: Dynamic resource partitioning
- H04W 24/02: Arrangements for optimising operational condition
- H04W 28/16: Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
- H04W 48/16: Discovering, processing access restriction or access information
- H04W 48/18: Selecting a network or a communication service
- H04W 60/04: using triggered events
- H04W 76/27: Transitions between radio resource control [RRC] states
- H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
- H04L 41/14: Network analysis or design
- H04L 41/16: using machine learning or artificial intelligence
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04W 84/04: Large scale networks; Deep hierarchical networks
- H04W 88/18: Service support devices; Network management devices
- 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)
- 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 of the invention provide a method for providing automated admission control services for a RAN system. The method receives a trigger alert that includes an application identifier for an application, a dRIC identifier associated with a dRIC to which the application is to be deployed, and a set of configurations for the application that are in a first format. The method converts the set of configurations from the first format to a second format and sends the set configurations in the second format to an FCAPS management pod deployed to the dRIC. Upon receiving positive acknowledgment indicating successful implementation of the set of configurations from the FCAPS management pod, the method updates a configuration table stored in a database of the RAN with a set of admissions control information for the application. The method sends a notification to an API server for the RAN indicating the set of configurations have been successfully implemented for the application.

## Claims

### Claim 1

For a RAN (Radio Access Network) system, a method for dynamically provisioning RAN applications in a set one or more cloud datacenters, the method comprising:
deploying, in the cloud datacenter set, a RIC (RAN intelligent controller) to serve as an interface between RAN applications and base station components of the RAN;
deploying, in the cloud datacenter set, at least one RIC management server (RMS) for configuring the RIC to dynamically provision the RAN applications to operate in the RAN system;
configuring the RIC and RMS to communicate through a first set of messages that are based on a first network communication protocol defined by a telephony-based standards body; and
configuring the RMS to convert the first set of messages received from the RIC into a second set of messages that are based on a second network protocol that is more optimal for communication between modules of the RMS that are deployed in the cloud datacenter set.

### Claim 2 (depends on 1)

The method of claim 1, wherein the first network protocol is Netconf and the second network protocol is RPC.

### Claim 3 (depends on 2)

The method of claim 2, wherein the RPC protocol is gRPC.

### Claim 4 (depends on 1)

The method of claim 1, wherein the first and second network protocols use first and second transport layer protocols that are different.

### Claim 5 (depends on 4)

The method of claim 4, wherein the first transport layer protocol of the first network protocol comprises SSH (secure shell protocol) or TLS (transport layer security), and the second transport layer protocol of the second network protocol comprises HTTP (hypertext transfer protocol) or HTTPS (hypertext transfer protocol secure).

### Claim 6 (depends on 1)

The method of claim 1, wherein the first set of messages are in a first format and the second set of messages are in a second format that is different from the first format.

### Claim 7 (depends on 6)

The method of claim 6, wherein the first format comprises an XML-encoded format and the second format comprises JSON.

### Claim 8 (depends on 6)

The method of claim 6, wherein the RMS modules include an RMS user interface (UI) that receives user input in the second format.

### Claim 9 (depends on 1)

The method of claim 1, wherein the RMS converts the second set of messages into a third set of messages for sending communications to the RIC.

### Claim 10 (depends on 9)

The method of claim 9, wherein the third set of messages are in a same format as the first set of messages.

### Claim 11 (depends on 10)

The method of claim 10 further comprising configuring the RIC to convert the third set of messages received from the RMS into a fourth set of messages that are based on the second network protocol.

### Claim 12 (depends on 11)

The method of claim 11, wherein a format of the fourth set of messages is different from a format of the second set of messages.

### Claim 13 (depends on 12)

The method of claim 12, wherein the format of the fourth set of messages comprises protobuf.

### Claim 14 (depends on 1)

The method of claim 1, wherein the set one or more cloud datacenters comprises a set of one or more public cloud datacenters.

### Claim 15 (depends on 1)

The method of claim 1, wherein the set one or more cloud datacenters comprises one or more public cloud datacenters and one or more private cloud datacenters.

### Claim 16

A non-transitory machine readable medium storing a program for execution by a set of processing units, the program for dynamically provisioning RAN (Radio Access Network) applications in a set one or more cloud datacenters of a RAN system, the program comprising sets of instructions for:
deploying, in the cloud datacenter set, a RIC (RAN intelligent controller) to serve as an interface between RAN applications and base station components of the RAN;
deploying, in the cloud datacenter set, at least one RIC management server (RMS) for configuring the RIC to dynamically provision the RAN applications to operate in the RAN system;
configuring the RIC and RMS to communicate through a first set of messages that are based on a first network communication protocol defined by a telephony-based standards body; and
configuring the RMS to convert the first set of messages received from the RIC into a second set of messages that are based on a second network protocol that is more optimal for communication between modules of the RMS that are deployed in the cloud datacenter set.

### Claim 17 (depends on 16)

The non-transitory machine readable medium of claim 16, wherein the first network protocol is Netconf and the second network protocol is gRPC.

### Claim 18 (depends on 16)

The non-transitory machine readable medium of claim 16, wherein:
the first and second network protocols use first and second transport layer protocols that are different; and
the first transport layer protocol of the first network protocol comprises SSH (secure shell protocol) or TLS (transport layer security), and the second transport layer protocol of the second network protocol comprises HTTP (hypertext transfer protocol) or HTTPS (hypertext transfer protocol secure).

### Claim 19 (depends on 16)

The non-transitory machine readable medium of claim 16, wherein the first set of messages are in a first format and the second set of messages are in a second format that is different from the first format.

### Claim 20 (depends on 19)

The non-transitory machine readable medium of claim 19, wherein the first format comprises an XML-encoded format and the second format comprises JSON.
