# US 2024/0205808 A1 · Multi-component configurations 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/0205808 A1
- Document ID: US20240205808A1
- Status: Published application
- Kind: A1
- Application number: 18/101,556
- Filed: 2023-01-25
- Published: 2024-06-20
- Earliest claimed: 2022-12-19
- Assignees: VMware, Inc.
- Applicants: VMware LLC
- Inventors: Gauresh Dilip Vanjare; Amit Singh
- Web page: https://patentgrep.com/patent/US20240205808A1

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

A method for configuring RAN (Radio Access Network) applications deployed in a RAN system comprising at least one RAN intelligent controller (RIC) and at least one RIC management system (RMS) for managing the RIC, the method comprising:
at a configuration service of the RIC:
receiving, from the RMS, a request to modify a configuration of each RAN application in a plurality of RAN applications;
forwarding a configuration update to each RAN application in the plurality of RAN applications;
after receiving a first acknowledgement from each RAN application that the configuration update is accepted for processing, instructing each RAN application in the plurality of RAN applications to process the configuration update in order to modify at least one operation performed by the RAN application; and
in response to receiving a second acknowledgement from each RAN application that the configuration update has been processed by the RAN application, sending a notification to the RMS to notify the RMS that the plurality of RAN applications have performed the requested modification.

### Claim 2 (depends on 1)

The method of claim 1, wherein receiving the request comprises receiving configuration data in a first format through a first communication protocol, the configuration data comprising the configuration update, the method further comprising:
converting the configuration data into a second format; and
using a second network communication protocol to distribute the configuration data to the plurality of RANs.

### Claim 3 (depends on 2)

The method of claim 2, wherein the first communication protocol is Netconf and the first format is an encoded XML format, and the second communication protocol is gRPC and the second format is protobuf.

### Claim 4 (depends on 2)

The method of claim 2, wherein using the second network communication protocol to distribute the configuration data comprises forwarding the configurations in the second format to each RAN application when the RAN application polls the RIC for new configurations during regular polling intervals.

### Claim 5 (depends on 1)

The method of claim 1, wherein a state of the configurations is updated in response to each acknowledgement sent by the set of RAN applications to reflect each acknowledgement sent by the set of RAN applications.

### Claim 6 (depends on 5)

The method of claim 5, wherein before sending the notification to the RMS to notify the RMS that the plurality of RAN applications have processed the updated configurations, the method comprises:
checking the state of the configurations to determine that the second acknowledgement that the configuration update has been processed by the RAN application has been received from each RAN application in the plurality of RAN applications; and
storing the updated configurations in a running datastore of the configuration service.

### Claim 7 (depends on 1)

The method of claim 1, wherein the configuration update comprises an update to at least one of a log level configured for the plurality of RAN applications, an absolute radio frequency channel number assigned to the plurality of RAN applications, a request timeout period configured for the plurality of RAN applications, and whether replay for messages is enabled for the plurality of RAN applications.

### Claim 8 (depends on 1)

The method of claim 1, wherein the request to modify a configuration of each RAN application in the plurality of RAN applications further comprises a request to modify a configuration of one or more other RAN components that are not RAN applications.

### Claim 9 (depends on 8)

The method of claim 8, wherein the one or more other RAN component comprises at least one of (i) one or more datapath pods that manage and assign datapaths to the plurality of RAN applications and (ii) one or more interfaces of one or more RAN applications.

### Claim 9 (depends on 8)

The method of claim 8, wherein:
the particular RIC is one of a plurality of RICs deployed in the RAN system; and
each of the plurality of RICs includes a respective FCAPS management machine.

### Claim 10 (depends on 1)

The method of claim 1, wherein the configuration service is implemented by an FCAPS (fault, configuration, accounting, performance, and security) management machine.

### Claim 10 (depends on 9)

The method of claim 9, wherein receiving the configurations from the RMS comprises receiving the configurations from a configuration manager of the RMS that communicates with at least one other FCAPS management machine of at least one other RIC of the plurality of RICs deployed in the RAN system.

### Claim 11 (depends on 8)

The method of claim 8, wherein the FCAPS management machine is an FCAPS management virtual machine (VM) or an FCAPS management Pod.

### Claim 12 (depends on 1)

The method of claim 1, wherein:
receiving the configurations comprises receiving the configurations in a first format; and
before forwarding the configurations to the set of applications, the method further comprises (i) validating the configurations against a particular schema that defines a required structure of configurations for RAN applications and (ii) parsing the configurations into a second format.

### Claim 13

A non-transitory machine readable medium storing a program for execution by a set of processing units, the program for a configuration service of a RAN intelligent controller (RIC) that configures RAN (Radio Access Network) applications deployed in a RAN system that comprises the RIC and a RIC management system (RMS) for managing the RIC, the program comprising sets of instructions for:
receiving, from the RMS, a request to modify a configuration of each RAN application in a plurality of RAN applications;
forwarding a configuration update to each RAN application in the plurality of RAN applications;
after receiving a first acknowledgement from each RAN application that the configuration update is accepted for processing, instructing each RAN application in the plurality of RAN applications to process the configuration update in order to modify at least one operation performed by the RAN application; and
in response to receiving a second acknowledgement from each RAN application that the configuration update has been processed by the RAN application, sending a notification to the RMS to notify the RMS that the plurality of RAN applications have performed the requested modification.

### Claim 14 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein the set of instructions for receiving the request comprises a set of instructions for receiving configuration data in a first format through a first communication protocol, the configuration data comprising the configuration update, the program further comprising sets of instructions for:
converting the configuration data into a second format; and
using a second network communication protocol to distribute the configuration data to the plurality of RANs.

### Claim 15 (depends on 14)

The non-transitory machine readable medium of claim 14, wherein the first communication protocol is Netconf and the first format is an encoded XML format, and the second communication protocol is gRPC and the second format is protobuf.

### Claim 16 (depends on 14)

The non-transitory machine readable medium of claim 14, wherein the set of instructions for using the second network communication protocol to distribute the configuration data comprises a set of instructions for forwarding the configurations in the second format to each RAN application when the RAN application polls the RIC for new configurations during regular polling intervals.

### Claim 17 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein a state of the configurations is updated in response to each acknowledgement sent by the set of RAN applications to reflect each acknowledgement sent by the set of RAN applications, wherein before sending the notification to the RMS to notify the RMS that the plurality of RAN applications have processed the updated configurations, the program comprises sets of instructions for:
checking the state of the configurations to determine that the second acknowledgement that the configuration update has been processed by the RAN application has been received from each RAN application in the plurality of RAN applications; and
storing the updated configurations in a running datastore of the configuration service.

### Claim 18 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein the configuration update comprises an update to at least one of a log level configured for the plurality of RAN applications, an absolute radio frequency channel number assigned to the plurality of RAN applications, a request timeout period configured for the plurality of RAN applications, and whether replay for messages is enabled for the plurality of RAN applications.

### Claim 19 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein;
the request to modify a configuration of each RAN application in the plurality of RAN applications further comprises a request to modify a configuration of one or more other RAN components that are not RAN applications; and
the one or more other RAN component comprises at least one of (i) one or more datapath pods that manage and assign datapaths to the plurality of RAN applications and (ii) one or more interfaces of one or more RAN applications.

### Claim 20 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein:
the set of instructions for receiving the configurations comprises a set of instructions for receiving the configurations in a first format; and
before forwarding the configurations to the set of applications, the program further comprises a set of instructions for (i) validating the configurations against a particular schema that defines a required structure of configurations for RAN applications and (ii) parsing the configurations into a second format.
