Scalable 5G Redundancy Orchestration with Pair Pool Objects
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing container orchestration platforms, such as Kubernetes, lack support for advanced redundancy models like Scaled 1+1 redundancy, which is crucial for telephony-grade services requiring stateful redundancy and seamless failover capabilities.
Innovation Solution
Custom operators and custom-defined objects, such as pair pool and pair objects, are used within a container orchestration environment to manage and deploy stateful redundant telephony-grade nodes, ensuring seamless failover and high availability by replicating state across pairs of nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If custom operators and custom-defined objects are used to manage stateful redundant telephony-grade nodes, then reliability and seamless failover are improved, but device complexity increases
Solution Approach 1:
Custom operators act as intermediary components between the orchestration system and telephony-grade nodes, managing the complexity of stateful redundancy and failover operations. The operators monitor node health, detect failures, and coordinate failover actions, thereby improving reliability while containing system complexity within the operator layer rather than propagating it throughout the entire orchestration infrastructure.
Solution Approach 2:
The system segments redundancy management into distinct functional components: pair pool objects define redundancy configurations, pair objects represent individual redundant pairs, and custom operators handle operational logic. This segmentation allows each component to specialize in specific aspects of reliability management, improving overall system reliability while organizing complexity into manageable, modular units.
2Productivity
If stateful redundant telephony-grade nodes are deployed using containerization, then scalability is improved, but ease of manufacture deteriorates due to lack of orchestrator support
Solution Approach 1:
Pair pool objects are configured in advance with redundancy parameters and node specifications before actual deployment. This preliminary configuration establishes the redundancy model, resource requirements, and failover policies upfront, enabling automated deployment of stateful redundant nodes without manual intervention during the deployment process itself, thereby improving productivity while reducing deployment difficulty.
Solution Approach 2:
The system uses pair objects as templates that define the state and configuration of redundant telephony-grade nodes. These pair objects are replicated and instantiated automatically by custom operators, enabling scalable deployment of identical redundant node pairs across the infrastructure. The copying mechanism ensures consistency across deployments while maintaining stateful redundancy, improving both productivity and ease of manufacture.
Data Source
AI summary
A node of a 5G communications network, comprising: an orchestration component of an orchestrator of the 5G communications network; a processing unit; and a memory coupled to the processing unit and having instructions stored thereon, the instructions, when executed by the processing unit, causing the orchestration component to perform acts comprising: monitoring for the creation of a pair pool object; in response to detecting the creation of a pair pool object, creating a plurality of pair objects; using a pair operator, detecting creation of the pair objects; and in response to detecting the creation of one of the pair objects, instantiating a pair of stateful redundant telephony-grade nodes.