# US 2024/0205865 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/0205865 A1
- Document ID: US20240205865A1
- Status: Published application
- Kind: A1
- Application number: 18/101,549
- 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/US20240205865A1

## 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 updating configurations for RAN (Radio Access Network) applications deployed in a RAN system, the method comprising:
at a RIC (RAN intelligent controller) deployed in the RAN system:
parsing a first CR (custom resource) that defines a RAN application to be deployed in the RAN system;
interacting with a RIC management system (RMS) to deploy a first instance of the RAN application in the RAN system and to define, for the RAN application, at least one datapath through the RIC to base station components; and
receiving, from the RMS, a first set of one or more updates to a first set of one or more attributes of the RAN application that are defined in the first CR, said RMS receiving from a network administrator the set of updates through a user interface (UI) of the RMS.

### Claim 2 (depends on 1)

The method of claim 1 further comprising:
at the RIC:
before parsing the first CR, receiving the first CR from a network administrator through an interface of the RIC;
after deploying the RAN application, receiving, from the network administrator through the RIC interface, a second CR that defines a second set updates to the RAN application, the second set of updates adding or removing a second set of one or more attributes to the RAN application; and
interacting with the RMS to replace the deployed current first instance of the RAN application with a newer second instance of the RAN application that includes the second set of updates.

### Claim 3 (depends on 1)

The method of claim 1, wherein the RMS receives from the network administrator the first set of updates through the RMS UI in a first format, wherein receiving the first set of one or more updates from the RMS comprises receiving, the first set of one or more updates in a second format that is different from the first format.

### Claim 4 (depends on 3)

The method of claim 3, wherein the RMS converts the first set of updates from the first format to the second format for sending the first set of updates to the RIC.

### Claim 5 (depends on 4)

The method of claim 4, wherein:
the first format is easier to review by a network operator that uses the UI than the second format; and
the second format is a format of telephony-based standards body communications sent from the RMS to the RIC via a telephony-based standards body protocol.

### Claim 6 (depends on 5)

The method of claim 5, wherein the first format comprises a JSON format, the second format comprises an XML-encoded format, and the telephony-based standards body protocol comprises Netconf.

### Claim 7 (depends on 4)

The method of claim 4 further comprising:
converting the received first set of updates from the second format to a third format that is different from the first and second formats;
distributing the first set of updates in the third format to the RAN application for processing;
receiving an acknowledgement from the RAN application that the first set of updates have been successfully processed; and
sending the acknowledgement to the RMS to notify the RMS that the first set of updates have been successfully processed by the RAN application.

### Claim 8 (depends on 7)

The method of claim 7, wherein the RMS updates a configuration of the RAN application stored in a configuration datastore of the RMS using the first set of updates based on receipt of the notification that the first set of updates have been successfully processed.

### Claim 9 (depends on 8)

The method of claim 8, wherein the configuration of the RAN application is stored by the RMS in the RMS configuration datastore in the first format for easy display through the RMS UI.

### Claim 10 (depends on 7)

The method of claim 7, wherein the RMS displays the acknowledgement through the RMS UI to notify the network administrator that the first set of updates have been successfully processed by the RAN application.

### Claim 11 (depends on 8)

The method of claim 8, wherein when the acknowledgement indicates that the first set of updates have not been successfully processed by the RAN application, the RMS displays the acknowledgement through the RMS UI without updating the configuration of the RAN application in the RMS configuration datastore.

### Claim 12 (depends on 1)

The method of claim 1, wherein receiving, from the RMS, the first set of one or more updates comprises receiving, from the RMS, a request to update the RAN application with the first set of one or more updates.

### Claim 13 (depends on 1)

The method of claim 1, wherein the RAN comprises an O-RAN (open RAN).

### Claim 14

A non-transitory machine readable medium storing a program for execution by a set of processing units, the program for a RIC (RAN (Radio Access Network) intelligent controller) that updates configurations for RAN applications deployed in a RAN system that includes the RIC, the program comprising sets of instructions for:
parsing a first CR (custom resource) that defines a RAN application to be deployed in the RAN system;
interacting with a RIC management system (RMS) to deploy a first instance of the RAN application in the RAN system and to define, for the RAN application, at least one datapath through the RIC to base station components; and
receiving, from the RMS, a first set of one or more updates to a first set of one or more attributes of the RAN application that are defined in the first CR, said RMS receiving from a network administrator the set of updates through a user interface (UI) of the RMS.

### Claim 15 (depends on 14)

The non-transitory machine readable medium of claim 14, wherein the program further comprises sets of instructions for:
at the RIC:
before parsing the first CR, receiving the first CR from a network administrator through an interface of the RIC;
after deploying the RAN application, receiving, from the network administrator through the RIC interface, a second CR that defines a second set updates to the RAN application, the second set of updates adding or removing a second set of one or more attributes to the RAN application; and
interacting with the RMS to replace the deployed current first instance of the RAN application with a newer second instance of the RAN application that includes the second set of updates.

### Claim 16 (depends on 14)

The non-transitory machine readable medium of claim 14, wherein:
the RMS receives from the network administrator the first set of updates through the RMS UI in a first format;
the set of instructions for receiving the first set of one or more updates from the RMS comprises a set of instructions for receiving the first set of one or more updates in a second format that is different from the first format; and
the RMS converts the first set of updates from the first format to the second format for sending the first set of updates to the RIC.

### Claim 17 (depends on 16)

The non-transitory machine readable medium of claim 16, wherein:
the first format is easier to review by a network operator that uses the UI than the second format; and
the second format is a format of telephony-based standards body communications sent from the RMS to the RIC via a telephony-based standards body protocol.

### Claim 18 (depends on 17)

The method of claim 17, wherein the first format comprises a JSON format, the second format comprises an XML-encoded format, and the telephony-based standards body protocol comprises Netconf.

### Claim 19 (depends on 16)

The non-transitory machine readable medium of claim 16, wherein the program further comprises sets of instructions for:
converting the received first set of updates from the second format to a third format that is different from the first and second formats;
distributing the first set of updates in the third format to the RAN application for processing;
receiving an acknowledgement from the RAN application that the first set of updates have been successfully processed; and
sending the acknowledgement to the RMS to notify the RMS that the first set of updates have been successfully processed by the RAN application.

### Claim 20 (depends on 19)

The non-transitory machine readable medium of claim 19, wherein:
the RMS updates a configuration of the RAN application stored in a configuration datastore of the RMS using the first set of updates based on receipt of the notification that the first set of updates have been successfully processed; and
the configuration of the RAN application is stored by the RMS in the RMS configuration datastore in the first format for easy display through the RMS UI.
