US 2012/0072757 A1 · Session Redundancy Using a Replay Model

Abstract

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.

Claims1

Dependent claims

An apparatus comprising:

a first processor comprising a first plurality of components;
and
a second processor, coupled to the first processor, comprising a second plurality of components, wherein
the first and second processors are configured to synchronize state information of each component of the first processor with counterpart components of the second processor,
said synchronizing comprises transmitting information used to establish states of a first subset of the first plurality of components from the first processor to counterpart components of the second processor, and
the first subset comprises less than all of the components of the first plurality of components.

3 more elements

Dependencies are inferred from the claim text.

Facts

Application

13/307,120Filed 30 Nov 2011

Priority

30 Jun 2007

Published

22 Mar 2012

Term ends

Not estimatedThe source records don’t support an estimate.

Classification11 codes

G06F 9/52
Multiprogramming arrangements: program synchronisation; Mutual exclusion, e.g. by means of semaphores
H04L 45/02
Routing or path finding of packets in data switching networks: topology update or discovery
H04L 45/021
Topology update or discovery: ensuring consistency of routing table updates, e.g. by using epoch numbers
H04L 45/308
Route determination based on requested QoS: route determination based on user's profile, e.g. premium users

Family

Application60/947,405Us provisional application · filed 30 Jun 2007

Application11/841,025Continuation · filed 20 Aug 2007

Application13/307,120Continuation

US 2009/0006879 A1Published application

US 8,074,094 B2Related patent

US 8,677,169 B2Related patent

US 2012/0072757 A1This patent

From the US filing history. Foreign family members aren’t listed.

Session Redundancy Using a Replay Model

Life of this patent

Session Redundancy Using a Replay Model

Life of this patent

Abstract

Claims1