Adaptable Resiliency for Virtualized RAN Framework
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing virtualized radio access networks (vRANs) face challenges in achieving reliable performance at a cost-effective level, as conventional methods often require high monetary and non-monetary costs to ensure reliability across various services.
Innovation Solution
The implementation of a resiliency management component (RMC) that adapts resiliency based on service-aware and automatically adapting redundancy of vRAN components, allowing for tailored resiliency designs that match the specific reliability requirements of different services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional vRAN methods are used to ensure reliability across various services, then reliability is improved, but cost increases
Solution Approach 1:
The patent applies local quality by implementing service-specific resiliency policies where different services receive different levels of redundancy based on their individual reliability requirements. Instead of uniformly applying high redundancy across all services, the system tailors resiliency configurations to match each service's specific needs, thereby reducing overall cost while maintaining necessary reliability for critical services.
Solution Approach 2:
The system dynamically adjusts resiliency parameters such as redundancy levels and failover configurations based on service requirements and network conditions. By changing these parameters adaptively rather than using fixed conventional settings, the system optimizes the balance between reliability and cost, avoiding unnecessary resource consumption for services that don't require high resiliency.
2Reliability
If high redundancy levels are implemented across all services, then reliability is improved, but resource consumption increases
Solution Approach 1:
The patent implements local quality by assigning different redundancy levels to different services based on their specific reliability requirements. Critical services receive higher redundancy while less critical services operate with lower redundancy, thereby reducing overall resource consumption while maintaining reliability where it is most needed.
Solution Approach 2:
The system applies partial action by implementing redundancy only to the extent necessary for each service's reliability requirements. Instead of applying excessive redundancy uniformly across all services, the system provides just enough redundancy for each service category, optimizing resource utilization while maintaining adequate reliability.
3Ease of operation
If uniform resiliency configuration is applied to all services, then implementation simplicity is maintained, but service-specific reliability requirements are not met
Solution Approach 1:
The patent applies universality by creating a standardized resiliency management framework that can accommodate multiple service types with different requirements through a common architecture. The system uses universal policies and configurations that can be selectively applied to different services, maintaining implementation simplicity while enabling service-specific reliability optimization through parameter adjustments rather than separate custom implementations.
Data Source
AI summary
Adaptable resiliency for a virtualized radio access network (vRAN) framework is disclosed. A resiliency management component can determine vRAN topological adaptations that can reflect resiliency requirements of service instance(s). Accordingly, sufficient redundant vRAN components to satisfy the resiliency requirements can be deployed. However, unlike conventional redundancy techniques that can determine a highest level of redundancy and then apply that relative to all supported services, the disclosed subject matter can avoid over-deploying redundant vRAN components, e.g., redundant components exceeding the resiliency requirement of a service instance, resulting in lowered monetary and non-monetary costs to maintain a vRAN. Moreover, as the services change, the topology of the vRAN can be automatically adapted to purge excessive redundancies, add newly required redundancies, etc., which can facilitate propagating an adequate but lean vRAN topology that is sufficiently resilient.