Jump to content

Plesiochronous system

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Stevenmitchell (talk | contribs) at 12:41, 2 July 2010 (missing word). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

The term Plesiochronous is derived from the Greek plesio, meaning near, and chronos, time, and refers to the fact that plesiochronous systems run in a state where different parts of the system are almost, but not quite perfectly, synchronised.

According to ITU-T standards, corresponding signals are plesiochronous if their significant instants occur at nominally the same rate, with any variation in rate being constrained within specified limits. In general, plesiochronous systems behave similarly to synchronous systems, except that they must have some means 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 well known Asynchronous serial communication is asynchronous only on the byte level, but plesiochronous on the bit level.[why?]

The modern tendency in systems engineering is towards using systems that are either fundamentally asynchronous (such as Ethernet), or fundamentally synchronous (such as Synchronous optical networking), and layering these where necessary, rather than using a mixture between the two in a single technology.

A sender and receiver operate plesiosynchronously if they operate at the same nominal frequency but may have a slight frequency mismatch, which leads to a drifting phase[1][2]

See also

References

  1. ^ P. Teehan, M. Greenstreet, G. Lemieux: A Survey and Taxonomy of GALS Design Styles, IEEE Design & Test of Computers September-October 2007, p.419
  2. ^ S. Johnson, S. Scott: A Supercomputer System Interconnect and Scaleble IOS, 14th IEEE Symposium on Mass Storage Systems, 1995, Footnote on p.358

Contains material from FOLDOC, used with permission