Domain Segment Identifiers for Inter-Domain Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current multi-domain network technologies, such as inter-domain MPLS, face challenges in providing end-to-end or any-to-any reachability while minimizing state information propagation across domain boundaries, leading to wastage of computing and networking resources in large networks.
Innovation Solution
Implementing domain segment identifiers for inter-domain shortest path segment routing, where ingress network devices receive and store core domain and location data to route traffic efficiently across multi-domain networks, reducing the need for detailed state information propagation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If inter-domain MPLS is used to provide end-to-end reachability in multi-domain networks, then connectivity between domains is improved, but state information propagation across domain boundaries increases, leading to wastage of computing and networking resources
Solution Approach 1:
The patent segments the multi-domain network into distinct domains, each with its own routing autonomy. Domain segment identifiers are used to represent entire domains rather than propagating detailed state information about individual nodes and links across all domains. This segmentation allows end-to-end reachability to be achieved through domain-level routing while minimizing the propagation of detailed state information across domain boundaries.
Solution Approach 2:
The patent introduces domain segment identifiers as intermediaries that represent domains in the routing process. Instead of directly propagating detailed state information about network topology and node states across all domains, the domain segment identifiers act as abstract representations that enable routing decisions without requiring full state information propagation. This intermediary mechanism resolves the contradiction by providing reachability through abstraction rather than direct state sharing.
2Measurement precision
If detailed state information is propagated across all domain boundaries to ensure routing accuracy, then routing precision is improved, but computing and networking resources are wasted
Solution Approach 1:
The patent extracts only the essential routing information needed for inter-domain routing by using domain segment identifiers. Instead of propagating complete detailed state information about all nodes and links across domain boundaries, the system extracts and propagates only the domain-level identification data that is sufficient for routing decisions. This extraction approach maintains routing precision at the domain level while significantly reducing the computational and networking resources required compared to full state information propagation.
3Loss of energy
If domain segment identifiers are used for inter-domain routing, then resource efficiency is improved, but device complexity increases due to segment routing implementation
Solution Approach 1:
The patent implements domain segment identifiers that can be used across multiple domains and routing scenarios, providing a universal routing mechanism. The segment routing infrastructure, while adding some device complexity, enables a single versatile routing approach that can handle inter-domain routing, intra-domain routing, and various routing policies uniformly. This multi-functionality justifies the increased device complexity by providing a resource-efficient universal routing solution that eliminates the need for separate routing mechanisms for different scenarios.
Data Source
AI summary
An ingress network device may receive a core domain network segment identifier associated with a core domain network of the multi-domain network. The ingress network device may receive location data of an egress network device associated with a second leaf domain network of the multi-domain network, wherein the location data may include data identifying the core domain network segment identifier, a second leaf domain network segment identifier associated with the second leaf domain network, and an egress network device segment identifier associated with the egress network device. The ingress network device may store the core domain network segment identifier and the location data, and may utilize the core domain segment identifier and the location data to route traffic to the egress network device.