It's UWAweek 16 (1st semester, week 7)

help3002

This forum is provided to promote discussion amongst students enrolled in CITS3002 Computer Networks.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message. How do I ask a good question?

Displaying selected article
Showing 1 of 199 articles.
Currently 1 other person reading this forum.


 UWA week 10 (1st semester, week 2) ↓
SVG not supported

Login to reply

👍?
helpful
9:24am Thu 7th Mar, Christopher M.

ANONYMOUS wrote:
> Why NRZ-L and NRZ-I offer no possible synchronization? What do we mean by synchronization here?
The sender and receiver of messages need to agree of two things: - what data is being exchanged (the 1s and 0s), and - how many bits are arriving The 1st requirement is met by using encoding schemes that use the amplitude, or change in amplitude, to represent the values of the data. However if, for example, a long sequence of bits was transmitted (e.g. a long sequence of 0s with NRZ-L), then the receiver can find/determine the beginning and ending of that sequence, but not how many (seemingly identical) bits there were. Senders and receivers use clocks (oscillators on the network interface card, not the OS) to know the passage of time (from their perspective) and the receiver uses the anticipated transmission speed and the elapsed time to determine how many bits were transmitted. To achieve this, the sender and receive need very similar clock rates, to agree on the rate at which they are communicating. The endpoints are agreeing/synchronising their perception of the speed involved. Hope this helps,

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  5:07AM Sep 06 2023
Privacy policy