It's UWAweek 47

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 the 2 articles in this topic
Showing 2 of 503 articles.
Currently 40 other people reading this forum.


 UWA week 14 (1st semester, non-teaching week) ↓
SVG not supported

Login to reply

👍?
helpful
12:49pm Thu 4th Apr, ANONYMOUS

For this question, I understand the difference between the NZR and Manchester but am unsure at 2 distinct reasons as I have just one primary reason. Local area networks (LANs) employ sophisticated signal encoding techniques, in preference to the naive (0=low, 1=high) encoding technique. List 2 distinct reasons for employing the sophisticated encoding techniques. My answer: Manchester encoding (or differential Manchester encoding) have bit transitions in the middle of each bit period which act as a reference point for clock synchronisation so the signal is interpreted properly at the receiver, whereas in the naive approach the clock at the receiver may drift further apart. This prevents data interpretation errors. Is the above a correct reason, and what would be another reason?


SVG not supported

Login to reply

👍?
helpful
2:19pm Thu 4th Apr, Ryan M.

Im guessing the other reason would be built in collision detection. As a collision of signals would result in destructive / constructive interference, which would likely remove some of the mid-bit transitions. The receiver can detect this inconsistency and assume a collision has occurred. I believe this idea was explored in the first tutorial

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  8:08AM Aug 25 2024
Privacy policy