5G DU/RU Performance Checks with Parallel Execution and Cleanup

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing 5G networks face challenges in efficiently performing regular health checks on Distributed Units (DUs) and Radio Units (RUs) to detect and resolve performance issues in a timely manner.

Innovation Solution

A system utilizing a jump server and performance server to execute a wrapper script that simultaneously runs performance checks on multiple DUs and RUs, with memory cleanup mechanisms to optimize server performance by deleting unnecessary files after checks are completed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If performance checks are performed on multiple DUs and RUs simultaneously, then the speed of performance checking is improved, but the memory space consumption on servers increases

Engineering Contradiction:
Improveperformance checking speedVSAvoidmemory space consumption
Core Design Contradiction:
SpeedVSVolume of stationary object

Solution Approach 1:

The patent segments the performance checking process into distinct phases: execution phase where performance scripts run on multiple DUs and RUs simultaneously consuming memory, and cleanup phase where intermediate files are deleted. The wrapper script manages multiple performance script copies independently for each target, allowing parallel execution while controlling resource usage through systematic file management.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by creating performance script copies in advance on the server before distributing them to multiple targets. The wrapper script prepares the environment by copying necessary performance checking scripts to temporary locations, ensuring that when simultaneous checks are executed, all necessary resources are already in place and can run in parallel without additional overhead.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If performance check files are retained on servers, then data integrity is improved, but server performance deteriorates due to memory space occupation

Engineering Contradiction:
Improvedata integrityVSAvoidserver performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements a discarding and recovering mechanism where intermediate files (performance script copies and log files) are systematically deleted after their purpose is fulfilled. The wrapper script monitors the completion of performance checks and automatically removes temporary files from server memory, thereby recovering space while maintaining the reliability of the performance checking process through proper file management.

Inventive Principle:
Principle #34Discarding and recovering

Solution Approach 2:

The system extracts and removes unnecessary intermediate files from the server environment after performance checks are completed. By separating the essential performance data (which needs to be retained) from temporary working files (which can be discarded), the system maintains data integrity while freeing up server memory space for continued operations.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If regular health checks are performed on DUs and RUs, then network reliability is improved, but the time required for checking increases

Engineering Contradiction:
Improvenetwork reliabilityVSAvoidchecking time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent enables continuous performance monitoring by allowing simultaneous execution of multiple performance checks across different DUs and RUs. Rather than performing checks sequentially which would consume more time, the system runs multiple performance script copies in parallel, maintaining continuous monitoring coverage while reducing total checking time through concurrent operation.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The system performs partial actions by running performance checks on selected subsets of DUs and RUs simultaneously rather than requiring all checks to complete before moving forward. The wrapper script manages multiple independent check operations that can proceed in parallel, providing sufficient monitoring coverage without requiring exhaustive sequential checking of every component.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS12363570B2Checking performance related to distributed units (DU) and radio units (RU) in a 5th generation (5G) network
Publication Date: 2025.07.15 DISH WIRELESS LLC
  • US12363570B2 patent drawing
  • US12363570B2 patent drawing
  • US12363570B2 patent drawing

AI summary

A jump server receives a command to check performance of one or more Distributed Units (DUs) or one or more Radio Units (RUs) at one or more cell sites. In response, the jump server executes a wrapper script that logs into a performance server, copies at least one input file that identifies the one or more DUs or the one or more RUs and a performance script to a user-specific directory at the performance server and initiates execution of the performance script at the performance server. The execution of the performance script causes the performance server to run a set of performance checking procedures on the one or more DUs or the one or more RUs identified in the input file, generate an output log file that comprises results of running the set of performance procedures, and store the output log file in the user specific directory.