Isochrony and Synchronization.ppt

May 17, 2000 USB 2.0 Core Team Isochrony and Synchronization Geert Knapen Philips ITCL-USA Agenda What is the problem? Synchronization Implementation in USB2.0 Conclusions Isochrony Implies... Data transport requirements Synchronization Latency considerations Buffer requirements Host responsibilities Data error detection … The Synchronization Problem Establish data connection between source and sink In general, data is synchronous in nature at both ends Source and sink potentially run off independentsample clocks Source and sink have their private stream characteristics Sampling rate Synchronization type Data format The Synchronization Problem USB is used to interconnect both devices No support for synchronous streams Isochronous is next best thing Source sampling rate gets lost To establish connection, proper conversionsmust take place From synchronous to isochronous Sampling rate conversion (SRC) Synchronization Data format translation From Synchronous to Isochronous on USB Back to Synchronous Agenda What is the problem? Synchronization Implementation in USB2.0 Conclusions Synchronization Provides the solution for the missing sample clock Source sample clock is ‘reconstructed’ at the sink side Different synchronization types needed, depending on source and sink nature Asynchronous Sample clock locked to external or free-running internal clock Synchronous Sample clock slaved to SOF Adaptive Sample clock derived from average desired data rate Synchronization Requires additional data rate information exchange between source and sink Feedback Rate info sent against the direction of the data flow Feedforward Rate info sent in the direction of the data flow Rate info can be conveyed explicitly or implicitly Explicit A dedicated isochronous pipe is used Implicit Rate info is extracted from the data stream or derived from SOF Synchronization Characteristics Agenda What is the problem? Synchronization Implementation in USB2.0 Conclusions Implementation in USB2.0 For Ada