# US 2024/0201962 A1 · Use of crds as descriptors for application ui in an o-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/0201962 A1
- Document ID: US20240201962A1
- Status: Published application
- Kind: A1
- Application number: 18/084,466
- Filed: 2022-12-19
- Published: 2024-06-20
- Earliest claimed: 2022-12-19
- Assignees: VMware, Inc.
- Applicants: VMware LLC
- Inventors: Vamseedhar Reddy Palapati; Levon Kirakosyan; Giridhar Subramani Jayavelu
- Web page: https://patentgrep.com/patent/US20240201962A1

## CPC

- G06F 8/38: for implementing user interfaces
- G06F 9/451: Execution arrangements for user interfaces
- G06F 9/541: {via adapters, e.g. between incompatible applications}
- H04W 24/02: Arrangements for optimising operational condition
- 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 use one or more CRDs (custom resource definitions), and Custom Resource (CR) instances based on these CRDs, to dynamically generate a unified user interface (UI) to display information (e.g., operational metrics) regarding different applications (xApps, rApps, etc.) in the O-RAN system. Using such CRDs and CR instances, frees up the application developers from having to define the UI programs for generating the UIs for their RAN applications. It also allows the O-RAN system to provide one unified approach for generating a UI to display information about O-RAN applications developed by different application developers.

## Claims

### Claim 1

A method of displaying information about an application in a RAN (Radio Access Network) system, the method comprising:
receiving an API (Application Programming Interface) request that defines a Custom Resource (CR) instance for the RAN application based on a Custom Resource Definition (CRD) for RAN visualization;
defining, based on the CR instance, a visualization object for display in a user interface (UI) of the RAN system to display information about the RAN application;
using the visualization object to display information about the RAN application in the UI of the RAN system.

### Claim 2 (depends on 1)

The method of claim 1 further comprising:
defining the RAN visualization CRD; and
distributing the RAN visualization CRD to a developer of the RAN application.

### Claim 3 (depends on 1)

The method of claim 1, wherein the RAN visualization CRD defines a custom visualization resource in a software defined datacenter (SDDC).

### Claim 4 (depends on 3)

The method of claim 3, wherein the SDDC includes Kubernetes workloads and managers.

### Claim 5 (depends on 3)

The method of claim 3, wherein the visualization object includes a display area of the UI, and the CR instance specifies a set of one or more attributes of the UI display area for displaying information about the RAN application.

### Claim 6 (depends on 5)

The method of claim 5, wherein the receiving, defining and using are operations performed by a UI generation process.

### Claim 7 (depends on 6)

The method of claim 6, wherein UI display area is a dashboard that is dynamically generated for the RAN application by the UI generation process.

### Claim 8 (depends on 6)

The method of claim 6, wherein the RAN application is a first RAN application, the API request is a first API request, the CR instance is a first CR instance and the display area is a first display area, the method further comprising:
at the UI generation process:
receiving a second API request that defines a second CR instance for a second RAN application on the RAN visualization CR;
defining, based on the second CR instance, a second display area for the UI to display information about the second RAN application;
displaying the second display area in the UI to display information about the second RAN application.

### Claim 9 (depends on 8)

The method of claim 8, wherein the first and second RAN applications are developed by first and second application developers respectively, and the first and second CR instances are defined by the first and second application developers respectively.

### Claim 10 (depends on 1)

The method of claim 1, wherein the application is one of an xApp or rApp in the RAN system.

### Claim 11

A non-transitory machine readable medium storing a program which when executed by at least one processing unit displays information about an application in a RAN (Radio Access Network) system, the program comprising sets of instructions for:
receiving an API (Application Programming Interface) request that defines a Custom Resource (CR) instance for the RAN application based on a Custom Resource Definition (CRD) for RAN visualization;
defining, based on the CR instance, a visualization object for display in a user interface (UI) of the RAN system to display information about the RAN application;
using the visualization object to display information about the RAN application in the UI of the RAN system.

### Claim 12 (depends on 11)

The non-transitory machine readable medium of claim 11 further comprising sets of instructions for:
defining the RAN visualization CRD; and
distributing the RAN visualization CRD to a developer of the RAN application.

### Claim 13 (depends on 11)

The non-transitory machine readable medium of claim 11, wherein the RAN visualization CRD defines a custom visualization resource in a software defined datacenter (SDDC).

### Claim 14 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein the SDDC includes Kubernetes workloads and managers.

### Claim 15 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein the visualization object includes a display area of the UI, and the CR instance specifies a set of one or more attributes of the UI display area for displaying information about the RAN application.

### Claim 16 (depends on 15)

The non-transitory machine readable medium of claim 15, wherein the sets of instructions for receiving, defining and using are operations performed by a UI generation process.

### Claim 17 (depends on 16)

The non-transitory machine readable medium of claim 16, wherein UI display area is a dashboard that is dynamically generated for the RAN application by the UI generation process.

### Claim 18 (depends on 16)

The non-transitory machine readable medium of claim 16, wherein the RAN application is a first RAN application, the API request is a first API request, the CR instance is a first CR instance and the display area is a first display area, the program further comprising sets of instructions for:
at the UI generation process:
receiving a second API request that defines a second CR instance for a second RAN application on the RAN visualization CR;
defining, based on the second CR instance, a second display area for the UI to display information about the second RAN application;
displaying the second display area in the UI to display information about the second RAN application.

### Claim 19 (depends on 18)

The non-transitory machine readable medium of claim 18, wherein the first and second RAN applications are developed by first and second application developers respectively, and the first and second CR instances are defined by the first and second application developers respectively.

### Claim 20 (depends on 11)

The non-transitory machine readable medium of claim 11, wherein the application is one of an xApp or rApp in the RAN system.
