# US 2024/0205688 A1 · Dynamically updating ran applications 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/0205688 A1
- Document ID: US20240205688A1
- Status: Published application
- Kind: A1
- Application number: 18/101,552
- Filed: 2023-01-25
- Published: 2024-06-20
- Earliest claimed: 2022-12-19
- Assignees: VMware, Inc.
- Applicants: VMware LLC
- Inventors: Gauresh Dilip Vanjare; Aniket Charuchandra Patni; Alpesh Darji
- Web page: https://patentgrep.com/patent/US20240205688A1

## 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 of operating RAN (Radio Access Network) applications in a RAN system that comprises a RAN intelligent controller (RIC) and a RIC management system (RMS) that manages the RIC, the method comprising:
at the RMS:
receiving a CR (custom resource) that defines a RAN application based on a first set of key value pairs from a data schema that is supported by the RMS;
displaying, through a UI (user interface) of the RMS, a set of attributes of the RAN application as a collection of key value pairs that are part of the first set of key value pairs that define the RAN application; and
modifying one or more values of one or more key value pairs of the RAN application based on a set of user input received through the RMS UI.

### Claim 2 (depends on 1)

The method of claim 1, wherein before displaying, through the UI of the RMS, the set of attributes of the RAN application, the method comprises:
receiving, through the UI of the RMS, a request to display the set of attributes of the RAN application;
in response to the request, retrieving (i) the collection of key value pairs and (ii) a configuration schema that is associated with the RAN application and that defines a structure for displaying the collection of key value pairs; and
combining the collection of key value pairs and the configuration schema for displaying the set of attributes through the UI of the RMS.

### Claim 3 (depends on 1)

The method of claim 1, wherein:
the set of user input received through the RMS UI comprises a set of user input in a first format;
modifying the one or more values of the one or more key value pairs of the RAN application based on the set of user input received through the RMS UI comprises (i) converting the set of user input from the first format to a second format and (ii) sending the set of user input in the second format to a particular RIC for implementation; and
the first format is easier to review by a user of the UI than the second format.

### Claim 4 (depends on 3)

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

### Claim 5 (depends on 1)

The method of claim 1, wherein receiving the CR comprises receiving, from the RIC, a set of parsed CR data that defines the RAN application.

### Claim 6 (depends on 5)

The method of claim 5, wherein the RIC receives and parses CRs that are defined based on a RAN application custom resource definition (CRD).

### Claim 7 (depends on 5)

The method of claim 5, wherein receiving, from the RIC, the set of parsed CR data that defines the RAN application further comprises:
interacting with the RIC to deploy the RAN application; and
storing a configuration of the RAN application in a configuration datastore of the RMS, the configuration defined based on the first set of key value pairs.

### Claim 8 (depends on 7)

The method of claim 7, wherein modifying the one or more values of the one or more key value pairs of the RAN application based on the set of user input comprises:
interacting with the RIC to direct the RIC to implement modifications to the one or more values of the one or more key value pairs of the RAN application;
receiving, from the RIC, an acknowledgement that the modifications have been implemented; and
based on the acknowledgement, (i) updating the configuration for the RAN application that is stored in the RMS configuration datastore and (ii) displaying the acknowledgement through the RMS UI.

### Claim 9 (depends on 8)

The method of claim 8, wherein when the acknowledgement from the RIC indicates that the modifications have not been implemented, the method comprises displaying through the RMS UI the acknowledgement that the modifications have not been implemented without updating the configuration for the RAN application that is stored in the RMS configuration datastore.

### Claim 10 (depends on 9)

The method of claim 9, wherein displaying through the RMS UI the acknowledgement that the modifications have not been implemented further comprises providing a set of selectable UI items for (i) cancelling the modifications and (ii) retrying to implement the modifications.

### Claim 11 (depends on 1)

The method of claim 1, wherein the UI comprises a set of selectable UI items for providing in-line modifications to the set of attributes displayed through the RMS UI.

### Claim 12 (depends on 11)

The method of claim 11, wherein the UI further comprises sets of selectable UI items for (i) importing files comprising modifications to the set of attributes for the RAN application and (ii) exporting files comprising a plurality of attributes of the RAN application.

### Claim 13 (depends on 1)

The method of claim 1, wherein the set of attributes of the RAN application is one of a plurality of sets of attributes of a plurality of RAN applications that are available for display through the RMS UI.

### Claim 14 (depends on 13)

The method of claim 13, wherein RAN applications are one of a plurality of RIC components for which attributes are available for display through the RMS UI.

### Claim 15 (depends on 1)

The method of claim 1, wherein:
the data schema comprises a set of data structures;
the set of data structures comprise (i) at least one supported configuration data first structure that is supported by the RMS and that defines one or more supported key value pairs that define the RAN application and (ii) a generic key value second structure that is supported by the RMS and that defines one or more custom key value pairs that define the RAN application and that supplement the one or more supported key value pairs; and
each custom key value pair defines a custom attribute of the RAN application.

### Claim 16 (depends on 15)

The method of claim 15, wherein:
the CR is a first CR;
modifications to the one or more custom key value pairs that do not add to or remove the one or more custom key value pairs are received through the RMS UI; and
modifications to the one or more custom key value pairs that add new custom key value pairs to the one or more custom key value pairs are received through a second CR.

### Claim 17

A non-transitory machine readable medium storing a program for execution by a set of processing units, the program for a RIC (Radio Access Network (RAN) intelligent controller) management system (RMS) to operate RAN applications in a RAN system that comprises a RAN intelligent controller (RIC) and the RMS that manages the RIC, the program comprising sets of instructions for:
receiving a CR (custom resource) that defines a RAN application based on a first set of key value pairs from a data schema that is supported by the RMS;
displaying, through a UI (user interface) of the RMS, a set of attributes of the RAN application as a collection of key value pairs that are part of the first set of key value pairs that define the RAN application; and
modifying one or more values of one or more key value pairs of the RAN application based on a set of user input received through the RMS UI.

### Claim 18 (depends on 17)

The non-transitory machine readable medium of claim 17, wherein before displaying, through the UI of the RMS, the set of attributes of the RAN application, the program comprises sets of instructions for:
receiving, through the UI of the RMS, a request to display the set of attributes of the RAN application;
in response to the request, retrieving (i) the collection of key value pairs and (ii) a configuration schema that is associated with the RAN application and that defines a structure for displaying the collection of key value pairs; and
combining the collection of key value pairs and the configuration schema for displaying the set of attributes through the UI of the RMS.

### Claim 19 (depends on 17)

The non-transitory machine readable medium of claim 17, wherein:
the set of user input received through the RMS UI comprises a set of user input in a first format;
the set of instructions for modifying the one or more values of the one or more key value pairs of the RAN application based on the set of user input received through the RMS UI comprises a set of instructions for (i) converting the set of user input from the first format to a second format and (ii) sending the set of user input in the second format to a particular RIC for implementation; and
the first format is easier to review by a user of the UI than the second format.

### Claim 20 (depends on 19)

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