Hub Device Bridge for Latency Reduction in Data Transactions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing hub devices require host involvement for data transactions between initiator controllers and target devices on different ports, leading to complex processes and significant latency due to buffer operations.
Innovation Solution
A hub device with a hub controller that receives a target device address, sets the clock line to busy, transmits the address, enables a bridge between the initiator controller and target device, releases the clock line, and facilitates seamless data communication without host involvement, using a bridge with clock and data lines to connect different voltage domains.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If host involvement is required for data transactions between initiator controllers and target devices on different ports, then data transmission can be achieved, but the process becomes complex and latency increases due to buffer operations
Solution Approach 1:
The hub controller acts as an intermediary that enables direct peer-to-peer communication between initiator controllers and target devices on different ports. It manages the transaction process, address routing, and data flow without requiring host involvement, thereby simplifying the transaction process while maintaining reliable data transmission through coordinated control of clock lines and data pathways.
2Reliability
If host involvement is required for data transactions, then data can be transmitted, but significant latency occurs due to buffer operations
Solution Approach 1:
The invention extracts the host from the data transaction process entirely, allowing initiator controllers to communicate directly with target devices through the hub controller. This removal of the host intermediary eliminates the buffer operations that cause significant latency, while the hub controller ensures reliable transmission through its coordination of clock lines and data pathways.
3Productivity
If a bridge is enabled between initiator controller and target device on different ports, then quick data transaction is achieved, but voltage domain compatibility must be ensured
Solution Approach 1:
The hub controller serves as a voltage domain intermediary that bridges different voltage domains between initiator controllers and target devices. It manages voltage level translation and compatibility through its I/O blocks, enabling fast direct data transactions while handling the complexity of voltage domain management internally without affecting the speed of data transfer.
Data Source
AI summary
A hub device comprising: a first port, a second port and a hub controller. The first port is configured to be connected to an initiator controller. The second port is configured to be connected to a target device, and wherein the target device has an address. The hub controller is configured to receive the target device address from the initiator controller via the first port, and in response: set a first-port-clock-line of the first port to busy; transmit the received target device address to the second port, to which the target device is connected; enable a bridge between the initiator controller and the target device, via the first port and the second port; release the first-port-clock-line of the first port from busy; communicate an acknowledgement message from the target device to the initiator controller via the bridge; and communicate a data transmission between the initiator controller and the target device via the bridge.