1 / 12

Synchronization architecture

Joint IEEE-SA and ITU Workshop on Ethernet. Synchronization architecture. Michael Mayer, Editor, G.8265, G.8275. Overview. Architecture in ITU Why? Requirements Synchronization recommendation structure General aspects of architecture in ITU-T Formal model example

xavierh
Download Presentation

Synchronization architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Joint IEEE-SA and ITU Workshop on Ethernet Synchronization architecture Michael Mayer, Editor, G.8265, G.8275

  2. Overview • Architecture in ITU • Why? • Requirements • Synchronization recommendation structure • General aspects of architecture in ITU-T • Formal model example • Overview of key Synchronization architecture recommendations • G.8264, Physical layer frequency (SyncE) • G.8265, Packet based frequency • G.8275, Packet based time/phase

  3. Architecture development Start here Requirements Development of architecture starts with Requirements A network model is then developed Which constrains equipment specifications Ensuring that deployed components meet all functional requirements for the network application Network Model Equipment specifications Deployment

  4. Next generation synchronizationinput constraints • Key aspects of NGN synchronization • Packet network infrastructure • Moving away from SONET/SDH • But can’t throw out existing network • New synchronization requirements • wireless backhaul requirements • Air interface requirements • New methods • CES, PTP, Synchronous Ethernet • New clock structures • BC, TC, GM • Architecture helps see how all pieces fit together

  5. Formal models basedon G.805 G.805 Functional Model for CES From G.8264 Network Element Model E1 Switch Switch E1 CES CES

  6. Details of functions • Individual functions may be specified in different recommendations • May include other aspects related to basic transport, in addition to synchronization • Some blocks may contain significant detail • Sync functions in G.781 • Clocks in G.8262 (e.g. EEC) • Transport functions in G.8021 (Ethernet) • Not all functions developed by Q13/15

  7. Ethernet Synchronization detail From Ethernet equipment specification: G.8021 7

  8. …More detail can be illustrated • Description of functional block will specify as much detail as necessary to define implementation requirements • Ensures a high degree of interoperability is achievable using standards provided by both IEEE and ITU

  9. Current versions • G.8264/Y.1364: Distribution of timing information through packet networks • G.8264/Y.1364 (10/2008) • G.8264/Y.1364 (2008) Amd. 1 (09/2010) • G.8264/Y.1364 (2008) Cor. 1 (11/2009) • G.8264/Y.1364 (2008) Amd. 2 (02/2012) • G.8264/Y.1364 (2008) Cor. 2 (02/2012) • G.8265/Y.1365 : Architecture and requirements for packet-based frequency delivery • G.8265/Y.1365 (10/2010) • G.8265/Y.1365 (2010) Amd. 1 (04/2011) • G.8265/Y.1365 (2010) Amd. 2 (10/2012) • G.8275: Architecture and requirements for packet-based time and phase delivery • Consented July 12, 2013

  10. New Options becomeavailable • The development of a coordinated architecture allows • Network to evolve • Understand limitations • Allow new capabilities to become available • Example follows: • Multiple frequency distribution options for wireless backhaul timing over multiple networks

  11. Architecture resultsin flexibility Physical layer: Service owner provides timing Physical layer: Intermediate carrier provides timing Packet layer: Service owner provides timing

  12. Summary • Architecture recommendations are important • Developed to provide an overall framework for how technology can be deployed in a network • Provide a framework for controlled technology evolution • Synchronization related architecture documents • Provide controlled evolution of technology • Ensure high degree of interoperability of different synchronization technologies • Guidance for developing equipment recommendations to support telecom specific requirements • Synchronization solutions must fit with packet traffic functions of NEs • Strong linkage to Hypothetical Reference Model (HRM) development • Provide guidance to other SDO’s

More Related