Network Traffic Replay System for Defect Identification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Troubleshooting and debugging complex network configurations and interactions between network protocols and components are challenging due to distributed nature of network components and complex interactions between software and hardware, making it difficult to identify and repair network defects effectively.

Innovation Solution

A method involving the recording and replaying of selected network traffic subsets to replicate and identify network defects, allowing for fine-grained control and observation in a controlled environment, enabling operators to focus on relevant subparts and vary input traces to locate root causes of errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If network traffic is recorded and replayed to replicate defects, then network defect identification capability is improved, but system complexity and resource consumption increase

Engineering Contradiction:
Improvenetwork defect identification capabilityVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system segments network traffic into control plane traffic and data plane traffic, allowing selective recording and replay of specific traffic types. This segmentation enables focused defect analysis on particular network layers or protocols without overwhelming the system with all traffic, thus improving defect identification while managing complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system creates copies of recorded network traffic for replay purposes, enabling defect replication without affecting the original live network operation. This copying approach allows multiple analysis scenarios to be tested simultaneously while preserving the production network's stability, improving measurement precision without proportionally increasing system complexity.

Inventive Principle:
Principle #26Copying

2Reliability

If all network traffic is recorded for analysis, then complete network defect detection is improved, but storage requirements and processing overhead increase

Engineering Contradiction:
Improvenetwork defect detection completenessVSAvoidstorage requirements
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system extracts and records only control plane traffic separately from data plane traffic, focusing on the control plane where many network defects originate. This extraction approach captures essential routing, signaling, and management traffic needed for defect detection while significantly reducing the volume of traffic that must be stored and processed compared to recording all network traffic.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system implements partial recording by selectively capturing control plane traffic rather than all network traffic. This partial action provides sufficient information for detecting control plane defects, protocol interactions, and configuration issues while avoiding the excessive storage and processing requirements of complete traffic capture.

Inventive Principle:
Principle #16Partial or excessive action

3Ease of operation

If network debugging is performed on individual components, then debugging focus is improved, but distributed network problems are missed

Engineering Contradiction:
Improvedebugging focusVSAvoiddistributed problem detection
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The replay system is designed to handle multiple traffic types and can replay traffic to multiple network components simultaneously. This multi-functionality allows the same replay infrastructure to debug individual protocol implementations, inter-protocol interactions, and distributed network behaviors, maintaining ease of operation while improving comprehensive problem detection.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system introduces a replay traffic generator as an intermediary component that can inject recorded traffic into the network at controlled points. This intermediary enables systematic testing of distributed interactions by mediating between recorded traffic and network components, allowing focused debugging while maintaining visibility into distributed problem patterns.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9054975B2Virtualization and replay-based system for network debugging
Publication Date: 2015.06.09 DEUTSCHE TELEKOM AG
  • US9054975B2 patent drawing
  • US9054975B2 patent drawing
  • US9054975B2 patent drawing

AI summary

A method and system of analyzing a network to identify a network defect allows user selection of traffic subset to be recorded. After recording the selected traffic subset of the network traffic during network operation, the recorded traffic is then replayed at least in part to the network to replicate, and thus assist in identifying, the network defect.