Centralized Unit Deployment Automation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Deploying and managing cellular network components, such as Centralized Units (CUs), in a seamless and efficient manner is challenging due to the complexity of scaling networks and the need for significant time and resources.

Innovation Solution

A computer-implemented method and system for automated deployment and management of CUs, involving the receipt of deployment requests, determination of deployment parameters, generation of deployment data, and automatic execution of workflows to deploy and manage CUs within computing environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual deployment methods are used for CUs, then deployment control and monitoring are possible, but deployment time and resource consumption increase significantly

Engineering Contradiction:

Improvedeployment speedVSAvoiddeployment time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The system enables self-service deployment through automated workflows where the deployment system automatically determines parameters, generates deployment data, and executes deployment without manual intervention. The orchestrator autonomously manages the deployment process based on received requests, eliminating the need for manual deployment operations while maintaining full control and monitoring capabilities.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by pre-determining deployment parameters and generating deployment data before actual deployment execution. The orchestrator prepares workflow definitions and deployment configurations in advance, allowing the deployment process to proceed automatically without real-time manual intervention, thus reducing deployment time while maintaining control.

Inventive Principle:

Principle #10Preliminary action

2Productivity

If automated deployment is implemented, then deployment time is reduced, but system complexity increases

Engineering Contradiction:

Improvedeployment efficiencyVSAvoidsystem complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The orchestrator serves as an intermediary component that manages the complexity of automated deployment. It receives deployment requests, determines parameters, generates deployment data, and coordinates workflow execution, thereby centralizing the complexity management in a single component rather than distributing it throughout the entire system. This intermediary approach enables automation while containing system complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The deployment system is segmented into distinct functional components: the orchestrator for managing deployment workflows, the parameter determination module, the deployment data generation module, and the workflow execution engine. This segmentation allows each component to handle specific aspects of deployment independently, reducing overall system complexity while enabling automated deployment through coordinated operation of these modular components.

Inventive Principle:

Principle #1Segmentation

3Manufacturing precision

If manual parameter determination is used, then deployment accuracy is maintained, but resource consumption and time increase

Engineering Contradiction:

Improvedeployment accuracyVSAvoidoperational complexity

Core Design Contradiction:

Manufacturing precisionVSDevice complexity

Solution Approach 1:

The system replaces manual mechanical operations with automated computational processes. Instead of manual parameter determination and deployment data generation, the orchestrator automatically determines deployment parameters and generates deployment data through computational workflows. This substitution maintains deployment accuracy through systematic parameter determination while reducing operational complexity by eliminating manual intervention.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

4Reliability

If traditional deployment approaches are used, then vendor-specific solutions are provided, but scalability and flexibility are limited

Engineering Contradiction:

Improvevendor solution reliabilityVSAvoidnetwork scalability

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The orchestrator is designed as a universal deployment management system that can handle multiple vendor-specific deployment scenarios through a single unified interface. It receives deployment requests, determines appropriate parameters based on vendor requirements, generates vendor-specific deployment data, and executes workflows for different CU types and vendors. This multi-functionality enables the system to maintain reliability for vendor-specific solutions while providing scalability and flexibility for diverse deployment scenarios.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS20250159491A1Centralized unit (CU) deployment and management

Publication Date: 2025.05.15 DISH WIRELESS LLC

AI summary

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.