Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Plesiochronous system
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{Short description|System synchronized to a nominal rate}} In [[telecommunications]], a '''plesiochronous system''' is one where different parts of the system are almost, but not quite, perfectly [[synchronization|synchronised]]. According to [[ITU-T]] standards, a pair of signals are plesiochronous if their significant instants occur at nominally the same rate, with any variation in rate being constrained within specified limits. A sender and receiver operate '''plesiosynchronously''' if they operate at the same nominal clock frequency but may have a slight clock frequency mismatch, which leads to a drifting phase.<ref>P. Teehan, M. Greenstreet, G. Lemieux: A Survey and Taxonomy of GALS Design Styles, IEEE Design & Test of Computers September鈥揙ctober 2007, p.419</ref><ref>S. Johnson, S. Scott: A Supercomputer System Interconnect and Scalable IOS, 14th IEEE Symposium on Mass Storage Systems, 1995, Footnote on p.358</ref> The mismatch between the two systems' clocks is known as the '''plesiochronous difference'''. In general, plesiochronous systems behave similarly to [[synchronous system]]s, except they must employ some means in order to cope with "sync slips", which will happen at intervals due to the plesiochronous nature of the system. The most common example of a plesiochronous system design is the [[plesiochronous digital hierarchy]] networking standard. The [[asynchronous serial communication]] protocol is [[asynchronous system|asynchronous]] on the byte level, but plesiochronous on the bit level. The receiver detects the start of a byte by detecting a transition that may occur at a random time after the preceding byte. The indefinite wait and lack of external synchronization signals makes byte detection asynchronous. Then the receiver samples at predefined intervals to determine the values of the bits in the byte; this is plesiochronous since it depends on the transmitter to transmit at roughly the same rate the receiver expects, without coordination of the rate while the bits are being transmitted. The modern tendency in [[systems engineering]] is towards using systems that are either fundamentally [[asynchronous serial communication|asynchronous]] (such as [[Ethernet]]), or fundamentally [[Synchronization|synchronous]] (such as [[synchronous optical networking]]), and layering these where necessary, rather than using a mixture between the two in a single technology. The term ''plesiochronous'' comes from the [[Greek language|Greek]] [[:wikt:蟺位畏蟽委慰蟼|蟺位畏蟽委慰蟼]] ''plesios'' ("near") and [[:wikt:蠂蟻蠈谓慰蟼|蠂蟻蠈谓慰蟼]] ''chr贸nos'' ("time"). ==See also== * [[Buffer (telecommunication)]] * [[Clock drift]] * [[Isochronous timing]] * [[Jitter]] * [[Mesochronous network]] * [[Synchronization in telecommunications]] ==References== {{reflist}} [[Category:Network architecture]] [[Category:Synchronization]]
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)
Pages transcluded onto the current version of this page
(
help
)
:
Template:Reflist
(
edit
)
Template:Short description
(
edit
)