MPLS Traffic Routing via IS-IS Multi-Instance Database Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current technologies lack a solution for effectively handling traffic-engineering requirements in MPLS networks that utilize IS-IS Multi-Instance as the interior gateway protocol, particularly in managing multiple databases and allocating resources across multiple IS-IS instances for efficient traffic routing.
Innovation Solution
A system with a managing entity that oversees multiple traffic engineering software agents, each associated with a unique database, allocates resources and updates databases dynamically to determine paths for traffic flow, selecting the appropriate databases and neighboring routing instances based on specific routing protocol instances for optimal traffic conveyance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple IS-IS instances are used to handle different routing topologies, then routing flexibility and network resilience are improved, but database management complexity and resource allocation difficulty increase
Solution Approach 1:
The patent segments the routing information base (RIB) into multiple instance-specific databases, where each IS-IS instance maintains its own separate database. This segmentation allows each instance to independently manage its routing topology without interference from other instances, thereby maintaining routing flexibility while organizing database management in a structured manner.
Solution Approach 2:
The patent introduces a multi-instance capable router as an intermediary element that coordinates between multiple IS-IS instances and their respective databases. This intermediary manages the complexity of multiple databases by providing a unified control plane that handles instance-specific routing requirements while maintaining overall system coherence.
2Reliability
If separate databases are maintained for each IS-IS instance, then routing isolation and instance-specific topology management are improved, but resource allocation efficiency and traffic engineering capability deteriorate
Solution Approach 1:
The patent implements a multi-functional database management system where the routing information base serves multiple purposes: it maintains instance-specific isolation for reliability while simultaneously enabling cross-instance resource allocation for efficiency. The RIB is designed to handle both isolated instance routing and coordinated multi-instance traffic engineering through unified data structures.
Solution Approach 2:
The patent merges the functionality of multiple instance-specific databases into a unified multi-instance RIB structure. This combination allows the system to maintain the benefits of separate instance management while enabling efficient resource allocation across all instances through a single coordinated database structure that shares common routing information.
3Ease of operation
If traditional routing protocols are used without multi-instance support, then system simplicity is maintained, but traffic engineering requirements and MPLS network capabilities cannot be satisfied
Solution Approach 1:
The patent introduces dynamic multi-instance capabilities into traditional routing protocols, allowing the system to adapt between simple single-instance operation and complex multi-instance traffic engineering modes. The routing protocol can dynamically adjust its behavior based on whether single-instance or multi-instance functionality is required, maintaining simplicity when possible while enabling advanced capabilities when needed.
Data Source
Figure 1~2
AI summary
A system and a method are provided for use in an MPLS network, wherein the system comprises at least one routing element configured to share one or more circuits among multiple Intermediate System to Intermediate System (IS-IS) routing protocol instances, wherein each of the multi instances is associated with a unique database, and wherein the at least one routing element comprises a managing entity configured to: manage a plurality of traffic engineering software agents each associated with a respective database, and allocate available resources to respective instances; update at least one of the plurality of databases; and for traffic that is about to be conveyed via a specific instance, determine a neighboring instance through which said traffic will be conveyed, based on information comprised in the database associated with the specific instance through which said traffic will be conveyed.