Incremental MPLS VPN Topology Computation via VRF Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current techniques for determining network topology in MPLS-based VPNs are inefficient, as they require re-computation of the entire network for small changes, leading to scalability issues and inconsistencies between logical and physical topologies.
Innovation Solution
A method that computes incremental configuration changes only for affected VPNs, using a Network Management System to obtain VPN routing and forwarding details, and analyzing changes to determine newly created, modified, or deleted VRFs, thereby updating the network topology accurately.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If re-computation of entire network topology is performed for small changes, then completeness of topology information is maintained, but computational time and system scalability deteriorate
Solution Approach 1:
The patent segments the network topology computation into individual VPN instances. Instead of re-computing the entire network topology when a change occurs, the system identifies and re-computes only the affected VPN(s). This is achieved by tracking VPN routing and forwarding details separately for each VPN, allowing incremental updates without full network re-computation, thus reducing computation time while maintaining topology completeness.
2Measurement precision
If re-computation of entire network topology is performed for small changes, then topology accuracy is maintained, but system scalability deteriorates
Solution Approach 1:
The patent divides the network management system into VPN-specific computation units. Each VPN maintains its own routing and forwarding details, allowing independent computation and updates. This segmentation enables the system to scale by processing each VPN's topology changes independently, reducing the overall system complexity burden when handling large networks with multiple VPNs.
Solution Approach 2:
The patent applies local quality by computing topology changes at the local VPN level rather than globally. When a change occurs in one VPN, only that specific VPN's topology is re-computed using its local routing and forwarding details, while other VPNs remain unaffected. This localized approach maintains topology accuracy for affected areas without requiring system-wide re-computation, thereby improving scalability.
3Productivity
If incremental computation is performed only for affected VPNs, then computation speed and scalability improve, but complexity of change detection and analysis increases
Solution Approach 1:
The patent implements preliminary action by pre-collecting and storing VPN routing and forwarding details before changes occur. The system maintains a database of current VPN topology information, allowing rapid identification of affected VPNs when changes happen. This pre-prepared data enables fast change detection and targeted re-computation without requiring complex real-time analysis of the entire network, thus improving computation speed while managing detection complexity through structured data organization.
Data Source
AI summary
Presented is a method and system of determining network topology of a virtual private network in Multi Protocol Label Switching (MPLS) based Virtual Private Networks (MPLS/VPNs). The method includes obtaining VPN routing and forwarding (VRF) details of at least one virtual private network, determining any variations in network configuration and determining, from said network configuration variations, network topology of the at least one virtual private network.