itu t q13 15 updates
play

ITU-T Q13/15 Updates tle pt TICTOC / IETF-80 tle pt Stefano - PowerPoint PPT Presentation

ITU-T Q13/15 Updates tle pt TICTOC / IETF-80 tle pt Stefano RUffini, Ericsson; Q13/15 Associate Rapporteur Main ongoing activities of interest for itle TICTOC pt s) Packet timing performance aspects for frequency (G.826x l 1 series)


  1. ITU-T Q13/15 Updates tle pt TICTOC / IETF-80 tle pt Stefano RUffini, Ericsson; Q13/15 Associate Rapporteur

  2. Main ongoing activities of interest for itle TICTOC pt s) › Packet timing performance aspects for frequency (G.826x l 1 series) pt – PDV metrics 2-5 – Network limits pt – Packet clock specification › Time Sync in packet networks (G.827x series) ýþ – Network Limits Ķķ ťŪ Ỳ – Clocks – Architecture and Telecom Profiles ext rea

  3. itle Updated Structure of Documents pt • agreed • ongoing s) • BC Boundary Clock • Definitions / • G.8260 • TC Transparent Clock terminology (Sync Definitions) • PRTC Primary Reference Time Clock l 1 • Time/Phase: • Frequency: G. pt • Basics and G.827x 826x • G.8271 • G.8261 Network 2-5 • G.8271.1 • SyncE NetworkJitter-Wander: pt (NetworkPDV_time/phase) Included in G.8261 Requirements • G.8271.2 • G.8261.1 may be needed in future (NetworkPDV_frequency) • G.8272 PRTC • G.8273 ýþ • G.8262 Ķķ Time Clocks (Frame) ťŪ (SyncE clock) Ỳ • G.8273.1 • Clocks • G.8263 (Telecom Grandmaster) (Packet clock) • G.8273.2 (Telecom BC) • G.8273.3 (Telecom TC) • G.8264 (SyncE-architecture) • Methods/ • G.8275 • G.8265 ( Packet-architecture (Packet-architecture Architecture for frequency) for time) • G.8265.1 • Profiles • G.8275.1 (PTPprofileFrequency) (PTPprofileTime/phase) ext • G.8265.2 rea • G.8275.2 (PTPprofileFrequency 2) (PTPprofileTime/phase 2)

  4. itle pt s) › › Amendment to G.8265.1 (1588 Frequency Profile ) l 1 – Consented at last SG15 plenary (Feb 2011) pt 2-5 › G.8260 pt – Draft updated with Appendix on PDV Metrics at last SG15 meeting (Feb 2011) – Draft updated with Appendix on PDV Metrics at last SG15 meeting (Feb 2011) – Two main classes of metrics defined: – Two main classes of metrics defined: › › a) for analysing the network a) for analysing the network › › b) for defining network limits b) for defining network limits ýþ Ķķ – Planned for December 2011 ťŪ Ỳ › Initial proposals for the packet clock (G.8263) – Focus on mobile application – Focus on mobile application – Long time constant – Long time constant – Planned for December 2011 – Planned for December 2011 › Initial Proposals for network limits (G.8261.1) – Focus on mobile application – Ongoing discussion on applicable packet metric (MAFE? FFO?) – Planned for December 2011 ext rea

  5. itle Accumulation Accumulation pt s) Packet network l 1 Packet clock master slave pt clock clock N = 10 2-5 pt Packet node (e.g. Ethernet switch, IP router, MPLS router) 10 Gbit/s fiber optical link DSLA DSL modem M 1 Gbit/s fiber optical link HRM-2a ýþ Packet network Ķķ Packet Packet ťŪ ONU Ỳ master slave OLT clock clock N = 5 HRM-2b HRM-2c Packet node (e.g. Ethernet switch, IP router, MPLS router) 10 Gbit/s fiber optical link 1 Gbit/s fiber optical link ext Microwave link rea

  6. itle Network Limits for Frequency SYnc pt s) End Application End Application End Application Clock Clock Clock l 1 pt C2 C2 2-5 PNT-F PNT-F PNT-F pt PRC PRC PRC Packet Master Packet Master Packet Master Clock Clock Clock timing packets timing packets timing packets E : End Application requirements E : End Application requirements E : End Application requirements Physical Layer based Physical Layer based Physical Layer based PNT-F PNT-F PNT-F (e.g. Frequency accuracy) (e.g. Frequency accuracy) (e.g. Frequency accuracy) Packet Packet Packet Synchronization Network Synchronization Network Synchronization Network Network Network Network ýþ PEC-M PEC-M PEC-M Ķķ PEC-S PEC-S PEC-S ťŪ B : PEC-M output Packet B : PEC-M output Packet B : PEC-M output Packet Ỳ Network Limits Network Limits Network Limits A : PRC, EEC, SSU A : PRC, EEC, SSU A : PRC, EEC, SSU C1 C1 or SEC Network Limits or SEC Network Limits or SEC Network Limits PNT-F PNT-F PNT-F C : PEC-S input C : PEC-S input C : PEC-S input Packet Network Limits Packet Network Limits Packet Network Limits D : PEC-S output Network Limits D : PEC-S output Network Limits D : PEC-S output Network Limits End Application End Application End Application (deployment Case 2) (deployment Case 2) (deployment Case 2) Clock Clock Clock ext rea

  7. itle Time Sync Updates pt s) › G.8271 (Time sync requirements) l 1 – Progresses on time sync error sources and Reference model pt – Initial assumption is for a reference model with 20 BC (“Telecom- 2-5 BC”) pt – Draft updated at last SG15 meeting (February 2011) – Planned for December 2011 ýþ Ķķ ťŪ Ỳ ext rea

  8. itle Time Sync Updates (Cont.) pt s) › Starting discussions on Time Sync Profile l 1 – Initial focus on Network with only BCs pt – TC still under discussion – Need for an alternate BMCA ? 2-5 pt – Planned in 2012 › Time Sync Clocks – Discussion started on PRTC and Telecom BC performance – G.8272 (PRTC) and G.8273.2 (T-BC) Drafts updated at last SG15 meeting ýþ (Feb 2011) Ķķ ťŪ › Several related aspects Ỳ – Time sync in the access (GPON, VDSL, etc.) – Time Sync over OTN (transparent transport of PTP or with support by OTN Nodes?) – Time Sync interfaces (1 PPS, etc.) – All these items involve other SG15 Questions (mainly Q2, Q4, Q9, Q11) ext rea

  9. itle Q13 and Tictoc pt s) › Main topics in TICTOC – 1588 over MPLS l 1 pt – Security – 1588 MIB 2-5 › 1588 over MPLS pt – No specific needs in case of frequency sync (PTP carried transparently over the MPSL network); ITU-T Telecom profiles can be used – Specific tools might be required in case of time sync in order to identify and process the PTP packets (only in case of TC?) › How to use TC in Telecom still to be agreed (e.g. discussions on layer violation to ýþ Ķķ be finalized) ťŪ Ỳ › Some reference to the specific tools to address MPLS scenarios as defined by TICTOC might be added in the ITU-T Time sync Telecom profile › Security – No specific action ongoing in Q13 (details are outside of the scope of Q13). Basic requirements might be discussed together with TICTOC. – Outcome from TICTOC could be used and referenced by Q13 recommendations › Management – In general Management is in the scope of ITU-T activities (e.g. Q14) and packet timing management will also need to be addressed. – Reference to a 1588 MIB developed by TICTOC might be done in ITU-T. ext Coordination might be appropriate on this point rea

Recommend


More recommend