Difficulty: Easy
Correct Answer: The clocking is derived from or embedded in the data stream in synchronous transmission.
Explanation:
Introduction / Context:
Serial links move bits sequentially. The receiver must know when to sample each bit. Two classic approaches exist: synchronous transmission, where timing is shared or recovered continuously, and asynchronous transmission, where timing is inferred per character with start/stop framing. Understanding this distinction is crucial for selecting link encapsulations and hardware interfaces.
Given Data / Assumptions:
Concept / Approach:
In synchronous transmission, the receiver stays aligned with the sender’s bit timing—either via an explicit clock or by recovering the clock from the encoded data stream. In asynchronous transmission, each character begins with a start bit and ends with a stop bit, allowing the receiver to re-synchronize for each character without a separate continuous clock.
Step-by-Step Solution:
Verification / Alternative check:
Examples: HDLC/SDLC, Ethernet PHYs, and many WAN links are synchronous; classic RS-232 terminal connections are asynchronous with start/stop framing. Oscilloscope traces show continuous timing in synchronous lines versus character-framed bursts in asynchronous lines.
Why Other Options Are Wrong:
Common Pitfalls:
Confusing encoding schemes (e.g., NRZ, Manchester) with sync/async categories; assuming async always wastes large bandwidth—overhead depends on character size and stop bits chosen.
Final Answer:
The clocking is derived from or embedded in the data stream in synchronous transmission.
Discussion & Comments