Open RAN Hardware Compatibility Scoring Under Stress Load
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The challenge in Open RAN environments is the poor compatibility of hardware components from different suppliers, leading to performance issues, field failures, and poor Quality of Experience (QoE) for end subscribers due to untested interworking.
Innovation Solution
A method to determine a compatibility metric for hardware platforms by stress testing individual components using operational parameters, recording failure points, and combining scores to assess overall compatibility.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If hardware components from different suppliers are integrated in Open RAN environments, then vendor diversity and supply chain resilience are improved, but compatibility issues and performance problems occur
Solution Approach 1:
The patent applies preliminary action by conducting compatibility testing of hardware components before they are deployed in the Open RAN environment. The system pre-evaluates potential hardware combinations to identify compatibility issues in advance, preventing field failures and ensuring reliable operation before the components are integrated into the network.
2Reliability
If comprehensive compatibility testing is performed for all hardware combinations, then hardware compatibility is improved, but testing complexity and time requirements increase
Solution Approach 1:
The patent applies segmentation by dividing the comprehensive compatibility testing into modular components. Instead of testing all possible hardware combinations simultaneously, the system segments the testing process into individual hardware element evaluations and combines results to determine overall platform compatibility. This reduces testing complexity while maintaining thoroughness.
Solution Approach 2:
The patent applies parameter changes by evaluating hardware compatibility across multiple operational parameters and stress conditions. The system tests hardware components under varying load conditions, operational modes, and performance thresholds to comprehensively assess compatibility. By changing test parameters systematically, the system achieves thorough compatibility validation without requiring exhaustive testing of every possible configuration.
3Productivity
If hardware components are selected without thorough testing, then deployment speed is improved, but field failures and poor QoE increase
Solution Approach 1:
The patent applies preliminary action by implementing compatibility testing before hardware deployment. The system evaluates potential hardware combinations in advance and identifies compatibility issues prior to field installation, preventing failures from occurring in the first place. This preliminary evaluation ensures that only compatible hardware components are deployed, eliminating the need for post-deployment troubleshooting and replacements.
4Measurement precision
If hardware components are stress tested to failure points, then compatibility assessment accuracy is improved, but testing time and resource consumption increase
Solution Approach 1:
The patent applies parameter changes by systematically varying operational parameters during stress testing to identify compatibility boundaries. Instead of merely pushing components to failure, the system evaluates performance across multiple parameter thresholds and operational modes. This approach provides comprehensive compatibility assessment by understanding how hardware behaves under different conditions, enabling more accurate compatibility predictions without requiring exhaustive failure testing.
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
A method of determining a compatibility metric of a hardware platform for running an Open Radio Access Network, Open RAN, application is provided. The hardware platform comprises a plurality of hardware elements. The method comprises, for each of the plurality of hardware elements, increasing an operational load on the hardware element by adjusting a value of one or more operational parameters selected from a plurality of operational parameters, and for each of the one or more operational parameters, either: detecting that the hardware element has failed and storing the value of the operational parameter when failure of the hardware element is detected; or storing the value of the operational parameter when the operational load on the hardware element is greatest. The method further comprises, for each of the plurality of hardware elements, determining a compatibility score for the hardware element based on the stored value of each of the one or more operational parameters. The method further comprises determining a compatibility metric for the hardware platform by combining the compatibility scores for each of the hardware elements.