# US 2004/0001443 A1 · Controlled exception-based routing protocol validation

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2004/0001443 A1
- Document ID: US20040001443A1
- Status: Published application
- Kind: A1
- Application number: 10/184,039
- Filed: 2002-06-26
- Published: 2004-01-01
- Earliest claimed: 2002-06-26
- Assignees: SBC Properties, L.P.
- Inventors: Shih Chung Soon; Larry Katzeff; Michael F. Martincello; Geethakumari P.M. Nair; Teong Yee Tan
- Web page: https://patentgrep.com/patent/US20040001443A1

## CPC

- H04L 43/50: Testing arrangements
- H04L 45/00: Routing or path finding of packets in data switching networks (routing or path finding in wireless networks H04W40/00)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

An implementation of a routing protocol in a device is tested by testing how the device reacts to messages and message sequences having potentially adverse conditions. Examples include messages either having a specified message size which is intentionally out-of-conformance with the routing protocol, having a repeated protocol field, absent a mandatory protocol field, or having an incorrect order of protocol fields. Examples also include message sequences having either a specific playback delay between at least one pair of adjacent protocol messages in the first sequence of protocol messages, a specific playback rate for the second sequence of protocol messages, or a modified message order.

## Claims

### Claim 1

A method of testing an implementation of a routing protocol in a device, the method comprising:
generating a message having a specified message size which is intentionally out-of-conformance with the routing protocol; and
testing how the device reacts to the message.

### Claim 2 (depends on 1)

The method of claim 1 wherein the message size is not equal to a protocol data unit (PDU) length of the message.

### Claim 3

A method of testing an implementation of a routing protocol in a device, the method comprising:
providing a sequence of protocol messages;
introducing a specific playback delay between at least one pair of adjacent protocol messages in the sequence of protocol messages; and
testing how the device reacts to the sequence of protocol messages with the specific playback delay.

### Claim 4 (depends on 3)

The method of claim 3 wherein the specific playback delay is introduced for a specific message in the sequence of protocol messages.

### Claim 5 (depends on 3)

The method of claim 3 wherein the specific playback delay is to cause a protocol state transition in the device which differs from an expected protocol state transition absent the specific playback delay.

### Claim 6 (depends on 3)

The method of claim 3 wherein the specific playback delay is introduced between a protocol state change in the device.

### Claim 7 (depends on 3)

The method of claim 3 wherein the specific playback delay is introduced during a protocol state change in the device.

### Claim 8

A method of testing an implementation of a routing protocol in a device, the method comprising:
providing a plurality of sequences of protocol messages;
introducing a specific playback delay between adjacent sequences in the plurality of sequences of protocol messages; and
testing how the device reacts to the plurality of sequences with the specific playback delay.

### Claim 9 (depends on 8)

The method of claim 8 wherein the specific playback delay is to cause a protocol state transition in the device which differs from an expected protocol state transition absent the specific playback delay.

### Claim 10 (depends on 8)

The method of claim 8 wherein the specific playback delay is introduced between a protocol state change in the device.

### Claim 11 (depends on 8)

The method of claim 8 wherein the specific playback delay is introduced during a protocol state change in the device.

### Claim 12

A method of testing an implementation of a routing protocol in a device, the method comprising:
providing a sequence of protocol messages; and
testing how the device reacts to a specific playback rate for the sequence of protocol messages.

### Claim 13 (depends on 12)

The method of claim 12 wherein the specific playback rate is to cause a protocol state transition in the device which differs from an expected protocol state transition absent the specific playback delay.

### Claim 14 (depends on 12)

The method of claim 12 wherein the specific playback rate is introduced between a protocol state change in the device.

### Claim 15 (depends on 12)

The method of claim 12 wherein the specific playback rate is introduced during a protocol state change in the device.

### Claim 16

A method of testing an implementation of a routing protocol in a device, the method comprising:
generating a message having a repeated protocol field; and
testing how the device reacts to the message.

### Claim 17

A method of testing an implementation of a routing protocol in a device, the method comprising:
generating a message absent a mandatory protocol field; and
testing how the device reacts to the message.

### Claim 18

A method of testing an implementation of a routing protocol in a device, the method comprising:
generating a message having an incorrect order of protocol fields; and
testing how the device reacts to the message.

### Claim 19

A method of testing an implementation of a routing protocol in a device, the method comprising:
recording a sequence of protocol messages exchanged between the device and a network node;
modifying an order of the protocol messages in the sequence to form a test sequence of the protocol messages; and
testing how the device reacts to the test sequence.

### Claim 20

A method of testing an implementation of a routing protocol in a device, the method comprising:
generating a first message having a specified message size which is intentionally out-of-conformance with the routing protocol;
testing how the device reacts to the first message;
generating a second message having a repeated protocol field;
testing how the device reacts to the second message;
generating a third message absent a mandatory protocol field;
testing how the device reacts to the third message;
generating a fourth message having an incorrect order of protocol fields;
testing how the device reacts to the fourth message;
providing a first sequence of protocol messages;
introducing a specific playback delay between at least one pair of adjacent protocol messages in the first sequence of protocol messages;
testing how the device reacts to the first sequence of protocol messages with the specific playback delay;
providing a second sequence of protocol messages;
testing how the device reacts to a specific playback rate for the second sequence of protocol messages;
recording a third sequence of protocol messages exchanged between the device and a network node;
modifying an order of the protocol messages in the third sequence to form a test sequence of the protocol messages;
testing how the device reacts to the test sequence;
providing a plurality of sequences of protocol messages;
introducing a specific playback delay between adjacent sequences in the plurality of sequences of protocol messages; and
testing how the device reacts to the plurality of sequences with the specific playback delay.

### Claim 21

A system for testing an implementation of a routing protocol in a device, the system comprising:
a playout manager to generate a message having a specified message size which is intentionally out-of-conformance with the routing protocol; and
a message capture component to test how the device reacts to the message.

### Claim 22 (depends on 21)

The system of claim 21 wherein the message size is not equal to a protocol data unit (PDU) length of the message.

### Claim 23

A system for testing an implementation of a routing protocol in a device, the system comprising:
a playout manager to introduce a specific playback delay between at least one pair of adjacent protocol messages in a sequence of protocol messages; and
a message capture component to test how the device reacts to the sequence of protocol messages with the specific playback delay.

### Claim 24 (depends on 23)

The system of claim 23 wherein the specific playback delay is introduced for a specific message in the sequence of protocol messages.

### Claim 25 (depends on 23)

The system of claim 23 wherein the specific playback delay is to cause a protocol state transition in the device which differs from an expected protocol state transition absent the specific playback delay.

### Claim 26 (depends on 23)

The system of claim 23 wherein the specific playback delay is introduced between a protocol state change in the device.

### Claim 27 (depends on 23)

The system of claim 23 wherein the specific playback delay is introduced during a protocol state change in the device.

### Claim 28

A system for testing an implementation of a routing protocol in a device, the system comprising:
a playout manager to introduce a specific playback delay between adjacent sequences in a plurality of sequences of protocol messages; and
a message capture component to test how the device reacts to the plurality of sequences with the specific playback delay.

### Claim 29 (depends on 28)

The system of claim 28 wherein the specific playback delay is to cause a protocol state transition in the device which differs from an expected protocol state transition absent the specific playback delay.

### Claim 30 (depends on 28)

The system of claim 28 wherein the specific playback delay is introduced between a protocol state change in the device.

### Claim 31 (depends on 28)

The system of claim 28 wherein the specific playback delay is introduced during a protocol state change in the device.

### Claim 32

A system for testing an implementation of a routing protocol in a device, the system comprising:
a playout manager to generate a sequence of protocol messages with a specific playback rate; and
a message capture component to test how the device reacts to the specific playback rate for the sequence of protocol messages.

### Claim 33 (depends on 32)

The system of claim 32 wherein the specific playback rate is to cause a protocol state transition in the device which differs from an expected protocol state transition absent the specific playback delay.

### Claim 34 (depends on 32)

The system of claim 32 wherein the specific playback rate is introduced between a protocol state change in the device.

### Claim 35 (depends on 32)

The system of claim 32 wherein the specific playback rate is introduced during a protocol state change in the device.

### Claim 36

A system for testing an implementation of a routing protocol in a device, the system comprising:
a playout manager to generate a message having a repeated protocol field; and
a message capture component to test how the device reacts to the message.

### Claim 37

A system for testing an implementation of a routing protocol in a device, the system comprising:
a playout manager to generate a message absent a mandatory protocol field; and
a message capture component to test how the device reacts to the message.

### Claim 38

A system for testing an implementation of a routing protocol in a device, the system comprising:
a playout manager to generate a message having an incorrect order of protocol fields; and
a message capture component to test how the device reacts to the message.

### Claim 39

A system for testing an implementation of a routing protocol in a device, the system comprising:
a message exchange recorder to record a sequence of protocol messages exchanged between the device and a network node;
an editor to modify an order of the protocol messages in the sequence to form a test sequence of the protocol messages;
a playout manager to generate the test sequence of the protocol messages; and
a message capture component to test how the device reacts to the test sequence.

### Claim 40

A system for testing an implementation of a routing protocol in a device, the system comprising:
a first testing device which couples the device to a first network, the first testing device including:
a message exchange recorder to record a first sequence of protocol messages exchanged between the device and the first network;
a synchronization component;
a playout manager to generate a first test sequence of messages based on the first sequence, wherein the messages in the first test sequence are generated with a timing based on the synchronization component; and
a message capture component to test how the device reacts to the first test sequence;
a second testing device which couples the device to a second network, the second testing device including:
a message exchange recorder to record a second sequence of protocol messages exchanged between the device and the second network contemporaneously with the first sequence of protocol messages;
a synchronization component whose timing is influenced by the synchronization component of the first testing device;
a playout manager to generate a second test sequence of messages based on the second sequence, wherein the messages in the second test sequence are generated with a timing based on the synchronization component; and
a message capture component to test how the device reacts to the second test sequence.

### Claim 41 (depends on 40)

The system of claim 40 wherein the first network and the second network are in communication, and wherein the first and second sequences of protocol messages are correlated.

### Claim 42 (depends on 40)

The system of claim 40 wherein the first test sequence and the second test sequence are generated to non-coherently provide the recorded messages to the device.

### Claim 43 (depends on 40)

The system of claim 40 wherein the first test sequence and the second test sequence are generated to provide conflicting messages to the device.

### Claim 44 (depends on 40)

The system of claim 40 wherein the first test sequence and the second test sequence are generated to introduce an expected event to the device after an unexpected delay.

### Claim 45 (depends on 40)

The system of claim 40 wherein the first test sequence and the second test sequence are generated to introduce incorrect topology information to the device.

### Claim 46

A method of testing an implementation of a routing protocol in a device, the method comprising:
recording a first sequence of protocol messages exchanged between the device and a first network;
recording a second sequence of protocol messages exchanged between the device and a second network contemporaneously with the first sequence of protocol messages;
contemporaneously generating a first test sequence of messages based on the first sequence and a second test sequence of messages based on the second sequence; and
testing how the device reacts to the first test sequence and the second test sequence.

### Claim 47 (depends on 46)

The method of claim 46 wherein the first network and the second network are in communication, and wherein the first and second sequences of protocol messages are correlated.

### Claim 48 (depends on 46)

The method of claim 46 wherein the first test sequence and the second test sequence are generated to non-coherently provide the recorded messages to the device.

### Claim 49 (depends on 46)

The method of claim 46 wherein the first test sequence and the second test sequence are generated to provide conflicting messages to the device.

### Claim 50 (depends on 46)

The method of claim 46 wherein the first test sequence and the second test sequence are generated to introduce an expected event to the device after an unexpected delay.

### Claim 51 (depends on 46)

The method of claim 46 wherein the first test sequence and the second test sequence are generated to introduce incorrect topology information to the device.

### Claim 52

A method of testing an implementation of a routing protocol in a device, the method comprising:
generating a plurality of messages having a duplicated message identification field; and
testing how the device reacts to the messages.

### Claim 53

A system for testing an implementation of a routing protocol in a device, the system comprising:
a playout manager to generate a plurality of messages having a duplicated message identification field; and
a message capture component to test how the device reacts to the messages.
