DisplayPort Packet Transport Layer for Multi-Destination Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing DisplayPort specification lacks a transport layer to identify the target sink device for uncompressed visual information packets, limiting communication to only a direct link between a single source and sink pair, and does not support communication to multiple destinations.
Innovation Solution
Adding unique identification information from the sink device's EDID, specifically bytes 8 through 15, to each uncompressed visual information packet, allowing packets to be routed or switched to a targeted sink device through a network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If DisplayPort packets are structured according to the original specification without transport layer, then device complexity is reduced and ease of manufacture is improved, but adaptability is limited to direct link only
Solution Approach 1:
The packet structure is segmented into distinct functional layers: the original DisplayPort packet structure is preserved for visual information transmission, while a separate transport layer is added with routing tags and destination identifiers. This segmentation allows the visual data path to remain simple while the transport mechanism gains complexity only where needed for routing functionality.
Solution Approach 2:
A transport layer acts as an intermediary between the DisplayPort packet structure and the network routing infrastructure. This intermediary layer includes routing tags and destination identifiers that enable network switches and routers to handle DisplayPort packets without requiring modifications to the core DisplayPort protocol, thus maintaining compatibility while enabling network communication.
2Adaptability or versatility
If DisplayPort specification maintains original packet structure, then ease of operation is improved, but adaptability to multiple destinations is lost
Solution Approach 1:
The solution adds a new dimension to the DisplayPort packet structure by introducing a transport layer that operates parallel to the existing visual information layer. This additional dimension includes routing tags and destination identifiers that enable multi-destination capability without interfering with the original packet structure or operational simplicity of the DisplayPort protocol.
3Adaptability or versatility
If transport layer is added to DisplayPort packets, then adaptability and routing capability are improved, but device complexity increases
Solution Approach 1:
The packet structure is segmented into distinct functional layers: the original DisplayPort packet structure is preserved for visual information transmission, while a separate transport layer is added with routing tags and destination identifiers. This segmentation allows the visual data path to remain simple while the transport mechanism gains complexity only where needed for routing functionality.
Solution Approach 2:
The transport layer is designed to be universal and compatible with existing DisplayPort infrastructure. It uses standardized routing tag formats and destination identifier structures that can be implemented across different devices and network switches, allowing the same transport mechanism to handle various routing scenarios without requiring device-specific complexity.
Data Source
AI summary
DisplayPort micropackets of uncompressed visual information are adapted for communication across a network by stuffing packets with sink device identification information. For example, a packet stuffer adds selected portions of sink device EDID information to DisplayPort packets, such as EDID bytes 8 through 15, to a predetermined portion of the DisplayPort packets, such as between symbols FS and FE. Adding sink device identification information to each DisplayPort packet supports routing or switching of the packets to the identified sink device.