Route Advertisement Using Subnet Prefixes to Cut Tunnel Complexity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing cloud computing systems require a large number of tunnels or traffic engineering tunnels, leading to complexity in configuration and management due to the need for individual tunnels for each user or service, which complicates network operations.
Innovation Solution
Implementing a data processing method that utilizes subnet prefixes as destination identifiers for traffic engineering tunnels, allowing for longest match packet forwarding and reducing the number of tunnels through segment routing policies, thereby simplifying configuration and improving packet forwarding efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If individual tunnels are configured for each user or service, then tunnel connectivity is ensured, but network complexity increases significantly
Solution Approach 1:
The patent merges multiple individual tunnel configurations into a single tunnel by using subnet prefix aggregation. Instead of configuring separate tunnels for each user or service, the system aggregates multiple destination prefixes into one tunnel configuration, reducing the number of tunnels from many individual connections to a single consolidated tunnel while maintaining connectivity to all destinations.
Solution Approach 2:
The patent makes a single tunnel universal by enabling it to serve multiple destinations through prefix aggregation. The tunnel is configured with aggregated subnet prefixes that represent multiple users or services, allowing one tunnel to perform the function of multiple individual tunnels simultaneously, thereby reducing configuration complexity while ensuring reliable connectivity.
2Adaptability or versatility
If individual tunnels are configured for each user or service, then specific routing is achieved, but configuration and management complexity increases
Solution Approach 1:
The patent combines multiple specific routing configurations into a single aggregated tunnel configuration. By merging multiple subnet prefixes into one tunnel, the system maintains the ability to route traffic specifically to different destinations while eliminating the need for separate configuration procedures for each tunnel, thus reducing configuration and management complexity.
Solution Approach 2:
The patent changes the configuration parameter from individual tunnel-specific settings to aggregated prefix-based settings. Instead of configuring each tunnel with its own unique parameters, the system uses subnet prefix aggregation where a single tunnel configuration can accommodate multiple destinations through parameter consolidation, making configuration and management easier.
3Quantity of substance
If subnet prefix aggregation is used, then tunnel quantity is reduced, but forwarding precision must be maintained
Solution Approach 1:
The patent merges multiple destination prefixes into a single aggregated tunnel while maintaining forwarding precision through longest prefix matching. The aggregation reduces tunnel quantity by consolidating multiple destinations, but the forwarding precision is preserved by using prefix matching algorithms that can distinguish between aggregated destinations, ensuring packets are routed accurately even though they traverse a reduced number of tunnels.
Solution Approach 2:
The patent replaces manual tunnel configuration mechanics with automated prefix aggregation mechanics. Instead of manually configuring each tunnel with precise routing information, the system uses prefix aggregation algorithms that automatically maintain forwarding precision while reducing tunnel quantity. This substitution of mechanical configuration with algorithmic processing preserves accuracy while simplifying the system.
Data Source
AI summary
A first network device obtains a subnet prefix, where the subnet prefix is a destination identifier of a traffic engineering tunnel. The first network device performs data processing based on the subnet prefix.