USB Device Initialization on Shared Bus for Network Testing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current testing solutions for content-aware network devices are inadequate, failing to rigorously test performance and security under real-world conditions, especially at line speeds, due to their focus on traditional IP network testing and lack of consideration for Layers 4-7 attributes, leading to deployment challenges and potential failures.

Innovation Solution

A network testing system that initializes programmable devices on a shared bus, allowing for the simulation of realistic application workloads and security attacks at line speed, encompassing Layers 4-7 testing through a hardware- and software-based platform with interconnected subsystems for high-performance measurements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional IP network testing approaches are used, then testing simplicity is maintained, but testing capability for content-aware devices is insufficient

Engineering Contradiction:
Improvetesting capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The testing system is divided into distinct functional modules including a control plane for test orchestration and data planes for actual traffic generation and analysis. This segmentation allows the system to handle complex content-aware device testing through specialized subsystems while maintaining overall system manageability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A control plane acts as an intermediary between the test operator and the data planes, managing test scenarios, coordinating traffic generation, and aggregating results. This intermediary layer enables complex testing capabilities while shielding users from underlying system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If comprehensive content-aware device testing is implemented, then testing thoroughness is improved, but testing speed decreases

Engineering Contradiction:
Improvetesting thoroughnessVSAvoidtesting speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

Test scenarios, traffic patterns, and evaluation criteria are pre-configured and validated before actual device testing begins. This preliminary preparation ensures comprehensive testing coverage is ready to execute at full speed without requiring complex real-time decision-making during the test run.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system maintains continuous test execution with multiple data planes generating and analyzing traffic simultaneously without interruption. This continuous operation enables thorough content-aware device testing while maximizing testing throughput and minimizing idle time between test phases.

Inventive Principle:
Principle #20Continuity of useful action

3Adaptability or versatility

If multiple programmable devices are connected to a shared bus, then system integration is improved, but initialization conflicts occur

Engineering Contradiction:
Improvesystem integrationVSAvoidinitialization reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary detection of device presence and readiness states before attempting to program or initialize devices on the shared bus. This advance detection prevents initialization conflicts by ensuring only ready devices are programmed, maintaining reliable system integration.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Each programmable device autonomously manages its own initialization state and signals readiness to the controller when prepared for programming. This self-service approach eliminates the need for complex centralized arbitration, allowing multiple devices to be reliably integrated on a shared bus without initialization conflicts.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8706921B2Software initialization of USB devices on a single bus
Publication Date: 2014.04.22 KEYSIGHT TECH SINGAPORE (SALES) PTE LTD
  • US8706921B2 patent drawing
  • US8706921B2 patent drawing
  • US8706921B2 patent drawing

AI summary

A method of initializing programmable devices on a shared bus, comprises, on power up, loading control instructions on a processor from an attached tangible, non-transient computer-readable medium, automatically allowing a first programmable device on a common bus to exit its reset state and enter a read-to-program state as the computer system powers up, automatically holding a second programmable device on the common bus in its reset state, querying the common bus by the processor to identify the first programmable device, copying the contents of a program image file by the processor from the computer-readable medium across the common bus to the first programmable device, and once the first programmable device has been programmed with the contents of the program image file, signaling the first programmable device to release the reset hold on the second programmable device.