US6330600B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
System for synchronizing configuration information of a network element if received trap sequence number is out-of-sequence
Assignee: Cisco Technology Inc
•
Filing: 1998-12-08
•
Granted: 2001-12-11
•
Expires: 2018-12-08
Abstract
Abstract A system for updating a memory storing configuration information of a network element includes a network element and a network manager coupled to the network element using a communication network. The network manager receives selected configuration information from the network element to update a selected part of the memory if a received state variable does not match a stored state variable.
Inventors
- 👤 Marco J. Matchefts
- 👤 Robert C. Taylor
- 👤 Ronald A. Pleshek
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-05 19:51
CPC Classifications
H; H04; H04L; H04L41/00; H04L41/08; H04L41/085; H04L41/0853; H04L41/0803; H04L41/0813; H04L41/0816; H04L41/02; H04L41/0213; H04L41/06; H04L41/22
Claims Analysis
Total Claims: 34
Claim 1
Independent Claim
85 words
A communication system, comprising: a network clement operable to generate a plurality of traps; and a network manager coupled to the network element and operable to receive a trap having a trap sequence number, the network manager further operable to determine if the received trap is out-of-sequence by comparing the trap sequence number to an expected trap sequence number, the network manager further operable to initiate a database synchronization process for configuration information of the network clement in response to the received trap being out-of-sequence.
Claim 2
Dependent Claim
85 words
A communication system, comprising: a network clement operable to generate a plurality of traps; and a network manager coupled to the network element and operable to receive a trap having a trap sequence number, the network manager further operable to determine if the received trap is out-of-sequence by comparing the trap sequence number to an expected trap sequence number, the network manager further operable to initiate a database synchronization process for configuration information of the network clement in response to the received trap being out-of-sequence.
Claim 3
Dependent Claim
31 words
The communication system of claim 1 , wherein the network manager generates the expected trap sequence number using a trap sequence number of a last trap received from the network element.
Claim 4
Dependent Claim
18 words
The communication system of claim 1 , wherein the network element comprises a digital subscriber line access multiplexer.
Claim 5
Dependent Claim
25 words
The communication system of claim 1 , wherein the trap identifies a selected one of an alarm, an alarm clear, or a module insertion event.
Claim 6
Dependent Claim
37 words
The communication system of claim 1 , wherein the network manager comprises a missing trap list operable to store at least one missing trap sequence number between the expected trap sequence number and the trap sequence number.
Claim 7
Dependent Claim
32 words
The communication system of claim 1 , wherein the network manager comprises a missing trap list, the network manager further operable to remove the trap sequence number from the missing trap list.
Claim 8
Dependent Claim
47 words
The communication system of claim 1 , wherein the network manager comprises: a missing trap list; and a missing trap timer operable to initiate the database synchronization process if the missing trap list stores a missing trap sequence number for longer than a predetermined period of time.
Claim 9
Dependent Claim
16 words
The system of claim 1 , wherein the database synchronization process comprises a partial database synchronization.
Claim 10
Dependent Claim
86 words
A network manager, comprising: a network interface operable to receive a plurality of traps from a network element; and a processor coupled to the network interface and operable to receive a trap having a trap sequence number, the processor further operable to determine if the received trap is out-of-sequence by comparing the trap sequence number to an expected trap sequence number, the processor further operable to initiate a database synchronization process for configuration information of the network element in response to the received trap being out-of-sequence.
Claim 11
Dependent Claim
86 words
A network manager, comprising: a network interface operable to receive a plurality of traps from a network element; and a processor coupled to the network interface and operable to receive a trap having a trap sequence number, the processor further operable to determine if the received trap is out-of-sequence by comparing the trap sequence number to an expected trap sequence number, the processor further operable to initiate a database synchronization process for configuration information of the network element in response to the received trap being out-of-sequence.
Claim 12
Dependent Claim
30 words
The network manager of claim 9 , wherein the processor generates the expected trap sequence number using a trap sequence number of a last trap received from the network element.
Claim 13
Dependent Claim
25 words
The network manager of claim 9 , wherein the trap identifies a selected one of an alarm, an alarm clear, or a module insertion event.
Claim 14
Dependent Claim
34 words
The network manager of claim 9 , further comprising a missing trap list operable to store at least one missing trap sequence number between the expected trap sequence number and the trap sequence number.
Claim 15
Dependent Claim
29 words
The network manager of claim 9 , further comprising a missing trap list, the network manager further operable to remove the trap sequence number from the missing trap list.
Claim 16
Dependent Claim
44 words
The network manager of claim 9 , further comprising: a missing trap list; and a missing trap timer operable to initiate the database synchronization process if the missing trap list stores a missing trap sequence number for longer than a predetermined period of time.
Claim 17
Dependent Claim
18 words
The network manager of claim 9 , wherein the database synchronization process comprises a partial database synchronization process.
Claim 18
Independent Claim
65 words
A method for receiving a plurality of traps from a network element, comprising: receiving a trap having a trap sequence number; comparing the trap sequence number to an expected trap sequence number; determining, in response to the comparison, if the received trap is out-of-sequence; and initiating a database synchronization process for configuration information of the network element in response to the received trap being out-of-sequence.
Claim 19
Independent Claim
65 words
A method for receiving a plurality of traps from a network element, comprising: receiving a trap having a trap sequence number; comparing the trap sequence number to an expected trap sequence number; determining, in response to the comparison, if the received trap is out-of-sequence; and initiating a database synchronization process for configuration information of the network element in response to the received trap being out-of-sequence.
Claim 20
Dependent Claim
31 words
The method of claim 16 , further comprising the step of generating the expected trap sequence number using a trap sequence number of a last trap received from the network element.
Claim 21
Dependent Claim
24 words
The method of claim 16 , wherein the trap identifies a selected one of an alarm, an alarm clear, or a module insertion event.
Claim 22
Dependent Claim
35 words
The method of claim 16 , further comprising the step of storing in a missing trap list at least one missing trap sequence number between the expected trap sequence number and the trap sequence number.
Claim 23
Dependent Claim
21 words
The method of claim 16 , further comprising the step of removing the trap sequence number from a missing trap list.
Claim 24
Dependent Claim
43 words
The method of claim 16 , further comprising: storing in a missing trap list at least one missing trap sequence number between the expected trap sequence number and the trap sequence number; and setting a missing trap timer in response to the storing.
Claim 25
Dependent Claim
102 words
The method of claim 16 , wherein initiating a database synchronization process for configuration information of the network element in response to the received trap being out-of-sequence comprises: storing in a missing trap list at least one missing trap sequence number between the expected trap sequence number and the trap sequence number; setting a missing trap timer; removing the missing trap timer if a last missing trap sequence number is removed from the missing trap list; and initiating the database synchronization process if the missing trap timer expires before the last missing trap sequence number is removed from the missing trap list.
Claim 26
Dependent Claim
17 words
The method of claim 16 , wherein the database synchronization process comprises a partial database synchronization process.
Claim 27
Independent Claim
73 words
An apparatus for receiving a plurality of traps from a network element comprising: means for receiving a trap having a trap sequence number; means for comparing the trap sequence number to an expected trap sequence number; means for determining, in response to the comparison, if the received trap is out-of-sequence; and means for initiating a database synchronization process for configuration information of the network element in response to the received trap being out-of-sequence.
Claim 28
Independent Claim
73 words
An apparatus for receiving a plurality of traps from a network element comprising: means for receiving a trap having a trap sequence number; means for comparing the trap sequence number to an expected trap sequence number; means for determining, in response to the comparison, if the received trap is out-of-sequence; and means for initiating a database synchronization process for configuration information of the network element in response to the received trap being out-of-sequence.
Claim 29
Dependent Claim
46 words
The apparatus of claim 24 further comprising: means for storing in a missing trap list at least one missing trap sequence number between the expected trap sequence number and the trap sequence number; and means for setting a missing trap timer in response to the storing.
Claim 30
Dependent Claim
112 words
The apparatus of claim 24 wherein the means for initiating a database synchronization process for configuration information of the network element in response to the received trap being out-of-sequence comprises: means for storing in a missing trap list at least one missing trap sequence number between the expected trap sequence number and the trap sequence number; means for setting a missing trap timer; means for removing the missing trap timer if a last missing trap sequence number is removed from the missing trap list; and means for initiating the database synchronization process if the missing trap timer expires before the last missing trap sequence number is removed from the missing trap list.
Claim 31
Dependent Claim
70 words
Logic encoded in media for receiving a plurality of traps from a network element, the logic operable to: receive a trap having a trap sequence number; compare the trap sequence number to an expected trap sequence number; determine, in response to the comparison, if the received trap is out-of-sequence; and initiate a database synchronization process for configuration, information of the network element in response to the received trap being out-of-sequence.
Claim 32
Dependent Claim
70 words
Logic encoded in media for receiving a plurality of traps from a network element, the logic operable to: receive a trap having a trap sequence number; compare the trap sequence number to an expected trap sequence number; determine, in response to the comparison, if the received trap is out-of-sequence; and initiate a database synchronization process for configuration, information of the network element in response to the received trap being out-of-sequence.
Claim 33
Dependent Claim
51 words
The logic encoded in media of claim 27 , wherein the logic is further operable to: store in a missing trap list at least one missing trap sequence number between the expected trap sequence number and the trap sequence number; and set a missing trap timer in response to the storing.
Claim 34
Dependent Claim
113 words
The logic encoded in media of claim 27 , wherein in order to initiate a database synchronization process for configuration information of the network element in response to the received trap being out-of-sequence, the logic is further operable to: store in a missing trap list at least one missing trap sequence number between the expected trap sequence number and the trap sequence number; set a missing trap timer; remove the missing trap timer if a last missing trap sequence number is removed from the missing trap list; and initiate the database synchronization process if the missing trap timer expires before the last missing trap sequence number is removed from the missing trap list.
References Cited (Backward Citations)
US4941089A
Cited
US5210530A
Cited
US6032183A
Cited
US5651006A
Cited
US5621721A
Cited
US5678006A
Cited
US6104868A
Cited
US5867659A
Cited
US5889470A
Cited
US6052724A
Cited
US6128656A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2004-12-10 | 2005-06-11 | 2005-12-11 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2008-12-10 | 2009-06-11 | 2009-12-11 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2012-12-10 | 2013-06-11 | 2013-12-11 | $7700.00 | Window Closed / Lapsed |