# US 2025/0159491 A1 · Centralized unit (cu) deployment and management

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

- Number: US 2025/0159491 A1
- Document ID: US20250159491A1
- Status: Published application
- Kind: A1
- Application number: 18/506,581
- Filed: 2023-11-10
- Published: 2025-05-15
- Earliest claimed: 2023-11-10
- Assignees: DISH Wireless L.L.C.
- Applicants: DISH Wireless L.L.C.
- Inventors: Valois Gonzalez; Bernie Lehman; Orlando Cuavas; Prakash Srinivasan
- Web page: https://patentgrep.com/patent/US20250159491A1

## CPC

- H04W 16/18: Network planning tools
- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- H04L 41/0869: Validating the configuration within one network element
- H04W 88/085: {Access point devices with remote components}
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods for CU deployment is provided. An example method includes receiving, by one or more processors, a request to deploy one or more CUs; determining, by the one or more processors, parameters used to deploy the CUS; obtaining, by the one or more processors, the parameters; generating, by the one or more processors, CU deployment data that includes the parameters; and causing, by the one or more processors, an automatic deployment of the CUs within one or more computing environments based, at least in part, on parameters.

## Claims

### Claim 1

A method for centralized unit (CU) deployment for one or more cell sites, the method, comprising:
receiving, by one or more processors, a request to deploy one or more CUs;
determining, by the one or more processors, parameters used to deploy the CUS;
obtaining, by the one or more processors, the parameters;
generating, by the one or more processors, CU deployment data that includes the parameters; and
causing, by the one or more processors, an automatic deployment of the CUS within one or more computing environments based, at least in part, on the parameters.

### Claim 2 (depends on 1)

The method of claim 1, wherein causing the automatic deployment of the CUs within a cloud network comprises executing one or more workflows to deploy the one or more CUs, wherein the one or more workflows cause operations to execute to deploy the one or more CUs.

### Claim 3 (depends on 2)

The method of claim 2, wherein the operations comprise first operations to instantiate the CUs within one or more networks, and second operations to provision individual ones of the CUs after instantiation.

### Claim 4 (depends on 3)

The method of claim 3, wherein obtaining the CU deployment data comprises querying an inventory management component that includes data related to a planned deployment of the one or more CUs, and wherein the CU deployment data identifies IP addresses to be used by the one or more CUs.

### Claim 5 (depends on 2)

The method of claim 2, wherein the operations comprise first operations to configure one or more computing environments, wherein the first operations, when executed by the one or more processors, perform one or more of configuring computer hosts including operations, hypervisor changing operations, firmware changing operations, BIOS changing operations, driver changing operations, inventory verification operations, or reserving IP addresses operations.

### Claim 6 (depends on 2)

The method of claim 2, further comprising:
accessing, via the one or more processors, validation data associated with the execution of the one or more workflows;
determining, via the one or more processors and based on the validation data, an occurrence of an error;
determining, via the one or more processors, that the error is resolved; and
causing the one or more workflows to resume execution.

### Claim 7 (depends on 6)

The method of claim 6, further comprising causing a validation app to perform a validation, wherein the validation is one or more of a pre-check validation of the workflow that validates a data readiness before performing operations to deploy the CUS, a validation that validates the deployment of the CUS, or a post-check validation that validates a successful completion of the one or more workflows.

### Claim 8 (depends on 2)

The method of claim 2, wherein execution of the one or more workflows is orchestrated by a workflow engine that executes in a network separately from the one or more computer environments.

### Claim 9

A computer system including one or more electronic processors configured to perform CU deployment associated with cell sites, wherein the system comprises:
an orchestrator configured to:
determine one or more workflows to deploy one or more CUs, wherein the one or more workflows cause operations to execute to deploy the one or more CUs; and
orchestrate execution of the one or more workflows to perform the CU deployment; and
one or more processors configured to
determine parameters to deploy the one or more CUs;
generate CU deployment data that includes the parameters; and
cause the orchestrator to begin the orchestration of the execution of the one or more workflows to perform the CU deployment.

### Claim 10 (depends on 9)

The computer system of claim 9, wherein the operations comprise first operations to instantiate the CUs within one or more networks, and second operations to provision individual ones of the CUs after instantiation.

### Claim 11 (depends on 9)

The computer system of claim 9, further comprising an inventory management component that stores data related to a planned deployment of the one or more CUs; and wherein determining the parameters to deploy the one or more CUs comprises querying the inventory management component that includes data related to a planned deployment of the one or more CUs, and wherein the CU deployment data identifies IP addresses to be used by the one or more CUs, and one or more DUs assigned to report to the one or more CUs.

### Claim 12 (depends on 9)

The computer system of claim 9, wherein the operations comprise first operations to configure one or more computing environments, wherein the first operations, when executed by the one or more processors, perform one or more of configuring computer hosts including operations, hypervisor changing operations, firmware changing operations, BIOS changing operations, driver changing operations, inventory verification operations, or reserving IP addresses operations.

### Claim 13 (depends on 9)

The computer system of claim 9, further comprising:
accessing, via the one or more processors, validation data associated with the execution of the one or more workflows;
determining, via the one or more processors and based on the validation data, an occurrence of an error;
determining, via the one or more processors, that the error is resolved; and
causing the one or more workflows to resume execution.

### Claim 14 (depends on 9)

The computer system of claim 9, further comprising a validation app to perform a validation, wherein the validation is one or more of a pre-check validation of the workflow that validates a data readiness before performing operations to deploy the CUS, a validation that validates an instantiation of the CUs, or a post-check validation that validates a successful completion of the one or more workflows.

### Claim 15

A non-transitory computer-readable medium configured to perform CU deployment associated with cell sites, and wherein the non-transitory computer-readable medium, when executed by a computer, causes the computer to:
receive a request to deploy one or more CUs;
determine parameters used to deploy the CUS;
generate CU deployment data that includes the parameters;
cause an automatic deployment of the CUs within one or more computing environments based, at least in part, on the parameters.

### Claim 16 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein causing the automatic deployment of the CUs within a cloud network comprises executing one or more workflows to deploy the one or more CUs, wherein the one or more workflows cause operations to execute to deploy the one or more CUs.

### Claim 17 (depends on 16)

The non-transitory computer-readable medium of claim 16, wherein the operations comprise first operations to instantiate the CUs within one or more networks, and second operations to provision individual ones of the CUs after instantiation.

### Claim 18 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein determining the parameters comprises querying an inventory management component that includes data related to a planned deployment of the one or more CUs, and wherein the CU deployment data identifies IP addresses to be used by the one or more CUs.

### Claim 19 (depends on 16)

The non-transitory computer-readable medium of claim 16, wherein the non-transitory computer-readable medium, when executed by a computer, further causes the computer to
access validation data associated with the execution of the one or more workflows;
determine, based on the validation data, an occurrence of an error;
determine that the error is resolved; and
cause the one or more workflows to resume execution.

### Claim 20 (depends on 16)

The non-transitory computer-readable medium of claim 16, wherein the operations further comprise other operations to associate individual ones of the CUs with one or more DUs.
