One-Way Routing Synchronization for Network Resource Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current routing protocols, such as EIGRP, perform unnecessary two-way transfers of routing table data during synchronization, which burdens network resources and affects performance, even when only specific neighbors' data needs to be updated.
Innovation Solution
Implementing a one-way transfer mechanism for synchronizing routing table data, where an initiating router determines a subset of neighbors and sends an EIGRP UPDATE message indicating one-way direction, reducing processing and communication bandwidth consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If two-way synchronization of routing table data is performed among all neighboring routers, then routing information consistency is maintained, but network resource consumption increases and performance deteriorates
Solution Approach 1:
The patent segments the routing synchronization process by introducing a bit field in the EIGRP UPDATE message that indicates whether one-way or two-way transfer is required. This allows the system to divide the synchronization approach based on specific conditions (inbound filter changes vs. outbound filter changes), performing one-way transfer when sufficient and two-way transfer when necessary, thereby reducing unnecessary network resource consumption while maintaining routing consistency
Solution Approach 2:
The patent applies partial action by implementing one-way transfer as a simplified version of the traditional two-way synchronization. When the initiating router's outbound filter changes, only the affected neighbors need to receive updates (partial action), rather than all routers performing full two-way synchronization. This reduces the excessive resource consumption associated with complete two-way transfers while maintaining sufficient routing information consistency
2Loss of information
If two-way transfer of routing table data is performed during re-synchronization, then all neighbors receive updated information, but processing overhead and bandwidth consumption increase unnecessarily
Solution Approach 1:
The patent applies local quality by making the transfer mode (one-way or two-way) dependent on the specific type of filter change and the local needs of the initiating router. When only the initiating router's outbound filter changes, one-way transfer to affected neighbors is sufficient (local solution). When inbound filters change, two-way transfer is performed locally at the initiating router to receive necessary updates. This localized approach maintains information completeness where needed while improving network performance by avoiding unnecessary global synchronization
3Reliability
If full routing table data is exchanged with all neighbors, then routing synchronization is ensured, but communication bandwidth and processing time are wasted
Solution Approach 1:
The patent introduces dynamics into the routing synchronization process by making the transfer mode adaptive based on the type of filter change detected. The system dynamically selects between one-way and two-way transfer modes using a bit field indicator in the EIGRP UPDATE message. This dynamic adaptation allows the system to use the more efficient one-way transfer when possible (reducing time and bandwidth) while switching to two-way transfer when synchronization accuracy requires it, thereby resolving the contradiction between reliability and time loss
Data Source
Figure 1A
Figure 1B
Figure 2A~2B
AI summary
Techniques for synchronizing routing data include determining whether conditions are satisfied for one-way transfer with an adjacent router. If it is determined that conditions are satisfied for one-way transfer of routing table data with the adjacent router, then a refresh-notice message is sent from the initiating router to the adjacent router. The refresh-notice message includes data that indicates a particular direction for transfer of routing table data. If the particular direction is inbound, then a copy of an adjacent routing table is received without sending a copy of the initiating router's own routing table. If the particular direction is outbound, then a copy of the own routing table is sent without receiving a copy of the adjacent routing table.