Routing Engine Session State Synchronization via Selective Data Extraction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current broadband aggregation services face limitations in availability, performance, and scalability, particularly in providing high-quality, reliable, and dynamic connectivity at the edge of service provider networks, where complex session management and synchronization of routing engines are time-consuming and resource-intensive.

Innovation Solution

The implementation of a mechanism to synchronize the state of components in a standby routing engine by transferring only state-related information associated with components that receive external stimuli from the active routing engine, allowing the standby engine to process and recreate the entire session state efficiently, thereby reducing synchronization time and resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If complete session state synchronization is performed between active and standby routing engines, then reliability is improved, but synchronization time and resource consumption increase

Engineering Contradiction:
Improvesession continuityVSAvoidsynchronization time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts and transmits only the essential session state information from the active routing engine to the standby routing engine, rather than synchronizing complete session states. This selective extraction of critical state data reduces synchronization overhead while maintaining sufficient reliability for session continuity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The session state information is segmented into critical and non-critical components. Only the critical session state information necessary for maintaining service continuity is synchronized to the standby engine, while non-critical information is omitted or deferred, thereby reducing synchronization time and resource consumption.

Inventive Principle:
Principle #1Segmentation

2Manufacturing precision

If comprehensive session state information is transferred to standby engine, then session recreation accuracy is improved, but data transmission volume and processing resources increase

Engineering Contradiction:
Improvesession state accuracyVSAvoiddata transmission volume
Core Design Contradiction:
Manufacturing precisionVSQuantity of substance

Solution Approach 1:

The patent applies extraction by identifying and transmitting only the essential session state information elements that are critical for session recreation. Non-essential state information is excluded from the synchronization data stream, reducing data transmission volume while preserving sufficient accuracy for session restoration.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements partial action by transferring a subset of session state information that is sufficient for practical session recreation purposes, rather than transmitting the complete session state. This partial synchronization approach achieves adequate precision while significantly reducing the quantity of data transmitted and processed.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS8677169B2Session redundancy using a replay model
Publication Date: 2014.03.18 CISCO TECHNOLOGY INC
  • US8677169B2 patent drawing
  • US8677169B2 patent drawing
  • US8677169B2 patent drawing

AI summary

A mechanism for synchronizing states of components in a first routing engine to corresponding components in a second routing engine is provided. In order to reduce the amount of data required to synchronize the state of the components and the time and resources required to perform the synchronization, the state-related information transmitted from the first routing engine to the second routing engine is limited to information used to build states of a subset of the components associated with the first routing engine. That subset of components is limited to those components that receive stimuli (e.g., data streams or data packets) from sources external to the routing engine. Other components on the second routing engine synchronize state by receiving information from those components on the second routing engine that received the external stimuli information.