Multi-Domain Orchestrator Endpoint Resolution for QoS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-provider network infrastructures, existing technologies face challenges in accurately determining tunnel path endpoints across different domains, leading to limitations in fulfilling Quality of Service (QoS) constraints and efficient network service implementation due to reliance on pre-advertised nodes and abstract representations of complex networks.
Innovation Solution
The implementation of a Multi-Domain Orchestrator (MDO) that uses service-related descriptors to characterize tunnel endpoints, allowing the terminating domain to determine the physical location of these endpoints during path computation, enabling precise QoS compliance and flexible network service orchestration across multiple domains.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If pre-advertised nodes and abstract representations are used for tunnel endpoints, then network service implementation is simplified, but QoS constraint fulfillment and endpoint accuracy deteriorate
Solution Approach 1:
The system performs preliminary service decomposition and endpoint resolution before path computation. The MDO resolves service-related descriptors to actual tunnel endpoints in advance, and the PCE stores resolved endpoint information for subsequent path calculations, enabling both simplified service implementation and accurate QoS fulfillment
Solution Approach 2:
The patent introduces an intermediary resolution mechanism where the MDO acts as a mediator between the service description layer and the network implementation layer. The MDO resolves abstract service-related descriptors to concrete tunnel endpoints by interacting with domain orchestrators, bridging the gap between simplified service definition and precise endpoint identification
2Adaptability or versatility
If abstract service-related descriptors are used to characterize tunnel endpoints, then flexibility in network service orchestration is improved, but the ability to determine precise physical locations deteriorates
Solution Approach 1:
The system performs preliminary resolution of service-related descriptors to physical endpoint locations before path computation. The PCE stores resolved endpoint information including physical locations, ensuring that both the flexibility of abstract descriptors and the precision of physical locations are maintained at appropriate stages
Solution Approach 2:
The patent adds a temporal dimension to the resolution process, where service-related descriptors exist in an abstract dimension during service definition, and are resolved to physical location dimension during path computation. This dimensional transition allows the system to maintain both abstract flexibility and physical precision
3Reliability
If the terminating domain determines physical endpoint locations during path computation, then QoS compliance is improved, but system complexity increases
Solution Approach 1:
The system segments the endpoint resolution functionality into dedicated components within the MDO and PCE. The MDO handles service decomposition and descriptor resolution, while the PCE manages path computation using resolved endpoints. This segmentation isolates complexity to specific modules while maintaining overall system reliability for QoS compliance
Solution Approach 2:
The MDO serves as an intermediary that handles the complex task of resolving service-related descriptors to physical endpoints. By concentrating this complexity in the MDO layer, the PCE can focus on path computation with simplified input, maintaining QoS compliance while managing system complexity through layered architecture
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
A multi-provider network infrastructure is described herein where a Multi- Domain Orchestrator (MDO) is configured to assist a Path Computation Entity (PCE) in resolving a placement and location (identifier) of a tunnel path endpoint for a network service.