1. 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 level 2-5 20 pt © Ericsson AB 20082008-06-101 How Packet Based Methods are addressed by Q13 Frequency SyncTime/Phase Sync Application Packet based methods Arrangement Basic Requirements (Independent from protocols) CES (“traffic masks”) PNT (“x ppb”) Phase/Time (e.g. “0.1-1 ms”) Accurate Phase/Time (e.g. “0.5 – 3  s” ) Specific requirements (dependent on protocols) Protocols Definition General Requirements With support from Network Nodes End-to-end With support from Network Nodes End-to-end PNT (“sync mask”) Requirements Protocols details Work flow Implementations with PTP, NTP, Others (“Telecom Profiles”) (G.8264) - Performance related aspects (G.8264, G.8263?, G.8261? ) Network Architecture (G.8261) Network Modelling (G.8264) Clock Spec. (G.8263 ) Equipment Functions (G.8261, G.8264) Inputs from other standardization bodies Study area tecnhically relevant Study area could be technically relevant but probably is of lower interest Study area relates to a challenging scenario (technically possible in special cases) Target Requirements (G.8261) Sync Methods (G.8261) Network Limits (G.8261) Outside Q13 scope (e.g. IETF, IEEE) Traditional ToD (e.g. “10-100 ms”) Network Architecture (G.8265) Network Modelling (8265) Clock Spec. (G.paclock-ter) Equipment Functions (G.8265) Implementations with PTP, NTP, Others (“Telecom Profiles”) (G.8265) - Performance related aspects (G.8265) Target Requirements (G.pactiming- bis) Sync Methods (G.pactiming-bis) Network Limits (G.pactiming-bis) Performance Related aspects

2. 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 level 2-5 20 pt © Ericsson AB 20082008-06-102 Applications Requirements: Frequency synchronization Application Class Example applications Strandard/Speciif cations/Recomme ndations Main Sync Methods Identified or Under discussion “Long Term Accuracy” GSM, WCDMA FDD, LTE FDD 50 ppb 100 ppb (Pico) 100-250 ppb (Home) Packet based (no “on- path-support”). Note: PDV controlled and/or stable oscillator (OCXO) “Traffic Masks” CES (Adaptive methods)ITU-T G.8261 CES Budget (application case 1 and 2) ITU-T G.823, G.824 traffic masks Packet based (no “on- path-support”). Note: PDV controlled and suitable oscillator “Synch Masks” Support for CES (Network synchronous, Differential) ITU-T G.823, G.824 synchronization mask G.8261 (EEC network limits) Timing over Physical layer (e.g. SDH, syncE) GPS

3. 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 level 2-5 20 pt © Ericsson AB 20082008-06-103 Applications Requirements: Time synchronization Application Class Example applications Strandard/Specif ications/Recom mendations Main Sync Methods Identified or Under discussion ToD Traditional (10-500 ms) Billing, Alarming, etc.Packet based (no support from the network). Tens of microseconds- hundreds of microseconds IP delay monitoring; LTE TDD (some configurations) Y.1541 3GPP Packet based ( no “on-path- support”). Note: PDV controlled and suitable oscillator 0.5 – 3 microseconds MBSFN WCDMA TDD TD-SCDMA CDMA2000 LTE TDD (some configurations) GPS Packet based (with path support) Main focus for TICTOC ?

4. 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 level 2-5 20 pt © Ericsson AB 20082008-06-104 Q13 Frequency Sync Recommendations Recc.Main ContentsWhat is missing G.8261 Target Requirements Network Limits Sync Methods Detailed model to clarify where the PDV limits apply. PDV metrics and related network limits G.8262 SyncE Clockscompleted G.8263 Packet based clocks specClock model PSC, PEC, specifications New Clocks? G.8264 Modelling Functional blocks Equipment functions Details on use of protocols: for syncE (i.e. SSM) and for packet based (e.g. “IEEE1588 Telecom Profiles”: these could be handled in Annexes, one per application) Details on packet based methods incl. profiles

5. 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 level 2-5 20 pt © Ericsson AB 20082008-06-105 Q13 Time-Phase Sync, Planned Recommendations Recc.Main Contents G.pactiming-bis Target Requirements Network Limits Sync Methods G.paclock-ter Time-Phase clocks spec (e.g. Boundary clock) G.8265 Functional blocks Modelling Equipment functions Details on use of protocols (e.g. “IEEE1588 Telecom Profiles”, NTP implementations; these could be handled in Annexes, one per application)