Synchronization architecture

Slides:



Advertisements
Similar presentations
Geneva, Switzerland, 13 July 2013 Ethernet Protection and Packet Synchronization Seminars/ethernet/201307/Pages/default.aspx.
Advertisements

Geneva, 27 May 2010 Types and Characteristics of Packet Transport Network (PTN) Equipment (Draft Recommendation - G.ptneq) Jia He and Hilmar Hofmann G.ptneq.
IEEE-1588 TM Profiles. [Page 1] Synchronization Categories Frequency synchronization (or syntonization) –Clocks are aligned in frequency Phase synchronization.
1588V2 Telecom Profile Framework
1 1588v2 modules of time synchronization with frequency layer support draft-su-tictoc-1588v2-time-sync-modules-00 IETF 75 th, Stockholm TICTOC WG
1 Introducing the Specifications of the Metro Ethernet Forum.
Geneva, 28 May 2010 Q13 Activities on Time Synchronization Jean-Loup Ferrant, Calnex, Q13 Rapporteur Stefano Ruffini Ericsson, Q13 Associated Rapporteur.
G.8275.x telecom time profiles
Synchronization architecture
1 Objective of today’s lesson S oftware engineering occurs as a consequence of a process called system engineering. Instead of concentrating solely on.
Abstraction and Control of Transport Networks (ACTN) BoF
Related work in other SDOs Silvana Rodrigues System Architect Phone:
Geneva, Switzerland, 13 July 2013 IEEE 1588 revision Silvana Rodrigues, Director of System Engineering, IDT Joint IEEE-SA and.
Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets.
Geneva, Switzerland, 13 July 2013 Welcome Stephen J. Trowbridge, Chairman, ITU-T Study Group 15 Joint IEEE-SA and ITU Workshop on Ethernet.
ITU-T SG16 and JCA-IoT activities
Colombo, Sri Lanka, 7-10 April 2009 Need of Interoperability “within” an NGN – An approach Rajeshwar Dayal, Director Dept. of Telecommunications, India.
Related Work: TMForum and ITU
Management Requirements for Packet-based Timing Distribution draft-frost-tictoc-management-00.txt IETF 78, Maastricht, July 2010 Tim Frost, Greg Dowd –
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Geneva, Switzerland, 13 July G (PTPprofileFrequency) G (PTPprofile1Time/phase) Basics Clock Methods Profiles Frequency: G.826xTime/Phase:G.827x.
Using European Component Oriented Architecture (ECOA™) on a CDE phase-1 project Dstl Platform Systems Division 9 September 2016 Dstl Document Reference:
Time Sync Network Limits: Status, Challenges
Goals and objectives Project(s): MBH IA Phase 4 Transport for 5G Networks Purpose of the contribution: Input to MBH IA Phase 4 Abstract: Overview on the.
Marc Holness, Product Line Architect, Ciena
PTP version 3 in FTI? Øyvind Holmeide/Markus Schmitz by 01/13/2016.
Review of new Question descriptions under ITU-T SG11
Report from Session #2: SDN/NFV
Direct Attached Storage and Introduction to SCSI
G.8275.x telecom time profiles
Global Standards Collaboration (GSC) 14
P802.1CM Time-Sensitive Networking for Fronthaul
Packet Based Methods: Standardization Framework
How Packet Based Methods are addressed by Q13
Results of San-Jose meeting March 16-20
Global Standards Collaboration (GSC) GSC-15
QOS Requirements for Real-Time Services over IP
The Open Group Architecture Framework (TOGAF)
Next Generation Networks: What, When, How: Highlights & Conclusions
Presented by Fabio Bigi Workshop Coordinator
Protocols and the TCP/IP Suite
Glenn Parsons, GTSC-9 Chair, ISACC
Session Moderator Ghassem Koleyni
ITU-T Workshop on Next Generation Networks: What, When & How?
Brief Introduction to IEEE P802.1CF
Overview of Q13 recommendations
ITU-T Study Group 2 Operational aspects of service provision and telecommunications management WTSA-12 Marie-Thérèse Alajouanine.
Roger Marks (Huawei) capable 5 November 2018
E-health standardization activities in ITU-T SG16
Systems Analysis and Design in a Changing World, 6th Edition
Reference Material ITU-T ASON and Transport Recommendations
ITU-T Special Study Group IMT-2000 and Beyond
IP and NGN Projects in ITU-T Jean-Yves Cochennec France Telecom SG13 Vice Chair Workshop on Satellites in IP and Multimedia - Geneva, 9-11 December 2002.
ITU-T Workshop on Next Generation Networks: What, When & How?
Stephen J. Trowbridge, Chairman, ITU-T Study Group 15
An Introduction to Software Architecture
Good Morning 1/17/2019.
ITU-T IPTV standards development
Network Architecture By Dr. Shadi Masadeh 1.
NGN Interoperability TIA DEL DOCUMENT #:
XRAN (eCPRI) S-Plane Sync Update
Protocols and the TCP/IP Suite
Report from Session #2: SDN/NFV
Reinhard Scholl, GTSC-7 Chairman
Session 7 Highlights & Conclusions
Related work in other SDOs
Glenn Parsons, GTSC-9 Chair, ISACC
Wayne Zeuch, GTSC-6 Chair Nicole Butler, ATIS Staff
Joint ITU-WHO Workshop on e-Health Standards and Interoperability (Geneva, Switzerland, April 2012) Session 7 chair’s notes from session 7 open.
Consideration on Joint Transmission
Presentation transcript:

Synchronization architecture Joint IEEE-SA and ITU Workshop on Ethernet Synchronization architecture Michael Mayer, Editor, G.8265, G.8275 Geneva, Switzerland, 13 July 2013

Overview Architecture in ITU General aspects of architecture in ITU-T 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 Geneva, Switzerland,13 July 2013

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 Geneva, Switzerland,13 July 2013

Next generation synchronization input 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 Geneva, Switzerland,13 July 2013

Formal models based on G.805 Functional Model for CES From G.8264 Network Element Model E1 Switch Switch E1 CES CES Geneva, Switzerland,13 July 2013

Individual functions may be specified in different recommendations 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 Geneva, Switzerland,13 July 2013

Ethernet Synchronization detail Inputs Outputs ETYn_AP: ETYn_AI_Data ETYn_AI_Clock ETYn_AI_TSF ETYn_AI_TSFrdi ETYn_AI_TSFfdi ETH_PP: ETH_PI_Data ETYn/ETH_A_Sk_MP: ETYn/ETH_A_Sk_MI_FilterConfig ETYn/ETH_A_Sk_MI_MAC_Lengt h Holdover control MI ETH_FP and ETH_TFP: ETH_CI_Data ETH_CI_Clock ETH_CI_SSF ETH_CI_SSFrdi ETH_CI_SSFfdi ETH_FP: ETH_CI_ESMC ETYn/ETH_A_Sk_MP: ETYn/ETH_A_Sk_MI_pErrors ETYn/ETH_A_Sk_MI_pFramesReceived OK ETYn/ETH_A_Sk_MI_pOctetsReceived OK From Ethernet equipment specification: G.8021 7 Geneva, Switzerland,13 July 2013

…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 Geneva, Switzerland,13 July 2013

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 Geneva, Switzerland,13 July 2013

New Options become available 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 Geneva, Switzerland,13 July 2013

Architecture results in flexibility Physical layer: Service owner provides timing Physical layer: Intermediate carrier provides timing Packet layer: Service owner provides timing Geneva, Switzerland,13 July 2013

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 Geneva, Switzerland,13 July 2013