Next Hop Database Compression via Resolver Database
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Network devices face memory and resource constraints due to the large number of entries required in the next hop database for each learned IP address, leading to limited capacity for additional routes and increased memory usage.
Innovation Solution
Implementing a resolver database to point to existing next hop entries in the next hop database for unique hardware addresses, allowing only one entry per unique hardware address and reducing the number of entries needed in the next hop database, thereby conserving space and resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a separate entry is stored in the next hop database for each learned IP address, then the database can provide complete routing information for each address, but the database size increases and memory resources are consumed
Solution Approach 1:
The patent merges multiple IP address entries that share the same next hop (hardware address) into a single consolidated entry in the next hop database. The resolver database maintains the mapping between multiple IP addresses and the single next hop entry, eliminating redundant storage while preserving complete routing information.
Solution Approach 2:
The patent introduces a resolver database as an intermediary layer between the forwarding table and the next hop database. This resolver database stores mappings from IP addresses to next hop entry indices, allowing the system to resolve multiple IP addresses to a single next hop without requiring separate entries in the next hop database for each IP address.
2Adaptability or versatility
If multiple IP addresses map to the same hardware address, then the network device can support multiple logical addresses, but the next hop database requires multiple redundant entries consuming memory space
Solution Approach 1:
The patent combines multiple IP address mappings that resolve to the same hardware address into a single next hop database entry. The resolver database maintains the relationship between multiple IP addresses and the shared next hop entry, enabling multi-address support while consolidating memory usage in the next hop database.
Solution Approach 2:
The patent makes the next hop database entry universal by allowing a single entry to serve multiple IP addresses through the resolver database. This multi-functional approach enables one next hop entry to handle routing for multiple logical addresses, reducing overall memory consumption while maintaining adaptability.
3Ease of operation
If the next hop database stores one entry per IP address, then routing lookups are straightforward, but the database reaches capacity faster limiting additional routes
Solution Approach 1:
The patent segments the routing information into two parts: the forwarding table with IP address prefixes, the resolver database with IP-to-next-hop mappings, and the compressed next hop database with unique next hop entries. This segmentation allows the next hop database to store only unique entries while maintaining efficient lookup capabilities through the resolver database.
Solution Approach 2:
The patent adds a dimensional layer with the resolver database that maps IP addresses to next hop entry indices. This additional dimension allows the system to maintain straightforward routing lookups while dramatically reducing the number of entries required in the next hop database, thereby increasing route capacity.
Data Source
AI summary
A method includes receiving, by processing circuitry of a first network device, an indication of a logical address associated with an interface to a second network device and adding, by the processing circuitry, an entry to a forwarding table of the first network device, the entry in the forwarding table specifying the logical address. The method further includes adding, by the processing circuitry, an entry to a resolver database of the first network device to which the entry in the forwarding table specifying the logical address points and resolving, by the processing circuitry, the logical address to a hardware address of the second network device. In response to determining an existing next hop entry of a next hop database of the first network device corresponds to the hardware address of the second network device, the method includes pointing, by the processing circuitry, the entry in the resolver database to the existing next hop entry in the next hop database without adding an additional entry to the next hop database for the second network device.