Distributed Orchestrator Segmentation for Network Policy Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network management systems face scaling limitations and challenges in federating independent orchestration authorities due to their centralized architecture, which hinders efficient distribution of network resource configuration and management.
Innovation Solution
The implementation of an intent-based YANG model (IB-YANG) that enables decentralized configuration of network resources by extending YANG models to include abstract configuration objects and foreign designators, allowing for abstraction, inter-device sharing, and scheduling information, thereby facilitating distributed orchestration and reducing dependency on a central orchestrator.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a centralized orchestrator is used to manage network resources, then configuration control is simplified, but scaling limitations and federation difficulty arise
Solution Approach 1:
The patent segments the centralized orchestrator into multiple distributed orchestrator instances that can independently manage network resources. Each orchestrator instance maintains the same configuration control capabilities but operates autonomously, enabling horizontal scaling and federation across multiple domains without a single point of failure.
Solution Approach 2:
The patent introduces a new dimension of orchestration by adding hierarchical levels and multi-domain support. Instead of a single flat orchestrator, the system implements a multi-dimensional orchestration framework where orchestrators can operate at different hierarchical levels and across multiple administrative domains simultaneously.
2Ease of operation
If a centralized orchestrator is used, then network management is simplified, but latency and efficiency degrade
Solution Approach 1:
The patent extracts the orchestration function from a single centralized entity and distributes it across multiple network nodes. By taking out the orchestration logic from the central point and placing it at the edge nodes and intermediate routers, the system reduces the distance that configuration commands must travel, thereby reducing latency while maintaining simplified management through standardized interfaces.
Solution Approach 2:
The patent enables network nodes to perform self-service orchestration by implementing local orchestrator instances that can autonomously make configuration decisions without constantly querying a central orchestrator. This self-service capability reduces round-trip communication delays and enables faster local optimization while maintaining overall network coherence.
3Device complexity
If centralized network architecture is used, then control is simplified, but resilience and scalability are reduced
Solution Approach 1:
The patent segments the monolithic centralized control architecture into modular distributed orchestrator instances deployed across multiple network nodes. This segmentation maintains control simplicity through standardized interfaces and protocols while dramatically improving resilience, as the failure of any single orchestrator instance does not compromise the entire network management system.
Solution Approach 2:
The patent changes the fundamental parameter of orchestrator deployment from centralized to distributed across multiple nodes. This parameter change transforms the system from a single point of failure architecture to a resilient distributed architecture while maintaining control simplicity through consistent orchestration protocols and state synchronization mechanisms.
Data Source
AI summary
A network of routers configure resource nodes connected to the network in accordance with a configuration model including configuration objects that imply resources. A router device among the network of router devices receives, from forwarding paths in the network relative to the router device, originated at the resource nodes and that indicate resources supported by the resource nodes. The router device creates mappings of the resources as advertised to the forwarding paths. The router device receives from the network an Intent request to create a configuration object among the configuration objects, and determines whether the configuration object matches a resource in the mappings. If the configuration object matches a resource in the mappings, the router device generates a new Intent request that identifies the resource, specifically, and forwards the new Intent request along the forwarding path mapped to the resource.