Backup Device Synchronization via Compression Context Transfer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing communication systems face challenges in maximizing bandwidth and minimizing delays, particularly during failover scenarios, where conventional compression protocols lead to congestion and packet loss due to flooding of full-headers, overwhelming devices and resulting in dropped calls and oversubscription of communication links.

Innovation Solution

A system and method for synchronizing a back-up device using a compression module that inspects data bits, determines which samples to suppress, and compresses them, coupled with an internal routing protocol like HSRP or VRRP to ensure seamless failover by transferring context information between primary and back-up devices, reducing the need for re-establishing active flows and minimizing bandwidth usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If conventional compression protocols are used during failover, then bandwidth is saved during normal operation, but full-headers flood the system causing congestion and packet loss

Engineering Contradiction:
Improvebandwidth usageVSAvoidpacket loss during failover
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The system performs preliminary synchronization of compression contexts from the primary device to the back-up device before failover occurs. This pre-positioning of context information ensures that when failover happens, the back-up device can immediately continue compression without generating full-headers, thus avoiding the flooding problem while maintaining bandwidth efficiency

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A context synchronization mechanism acts as an intermediary between the primary and back-up devices. This intermediary transfers and maintains compression context information, allowing the back-up device to assume the compression state seamlessly during failover, preventing the surge of full-headers that would otherwise congest the system

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If full-headers are transmitted during failover, then complete flow information is provided, but devices are overwhelmed causing congestion and dropped calls

Engineering Contradiction:
Improveflow information completenessVSAvoidsystem capacity during failover
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The complete flow information is preliminarily transferred to the back-up device in the form of compression contexts before failover. This pre-transfer ensures that when failover occurs, the back-up device already possesses all necessary flow information and can continue processing without needing to receive full-headers, thus avoiding device overload while maintaining information completeness

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a copy of the compression context information from the primary device and transfers it to the back-up device. This copying mechanism ensures that the back-up device has an exact replica of the flow state information needed to continue processing seamlessly, eliminating the need to transmit full-headers during failover and preventing system congestion

Inventive Principle:
Principle #26Copying

3Reliability

If compression contexts are transferred during failover, then active calls are preserved, but bandwidth is consumed for context transfer

Engineering Contradiction:
Improveactive call preservationVSAvoidbandwidth consumption for synchronization
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The context synchronization operates continuously or periodically rather than only during failover events. This continuous synchronization maintains up-to-date context information in the back-up device, ensuring that when failover occurs, the information is already available and no additional bandwidth is consumed at the critical moment, while still preserving active calls through seamless transition

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS7675851B2System and method for synchronizing a back-up device in a communications environment
Publication Date: 2010.03.09 CISCO TECHNOLOGY INC
  • US7675851B2 patent drawing
  • US7675851B2 patent drawing
  • US7675851B2 patent drawing

AI summary

An apparatus for communicating data is provided that includes a cell site element associated with a base transceiver station and comprising a compression module that is operable to receive a plurality of bits associated with a communications flow, to inspect the bits, to determine whether one or more samples included in the flow should be suppressed, and to compress the samples. The cell site element is coupled to a back-up device that is operable to assume responsibility for active flows in a case where a primary device fails. Data is exchanged between the primary device and the back-up device, the data guiding the back-up device in how to process the active flows.