Sync Solutions for LTE_2

7/14/2019 Sync Solutions for LTE_2

1/67

Confidential Copyright 2012

Charlie Ferreira

February 2013

Synchronization Solutions for LTENetworks


2/67

2Confidential Copyright 2012

Agenda

Standards and Requirements

Synchronisation in 3G networks

Evolution and relationship between Mobile networks andsynchronisation Migrating to sync to support LTE requirements

Synchronization Distribution Architecture for LTE

Symmetricom Solutions


3/67


Standards and Requirements


4/67


The Basic Question

How should I synchronize my LTE networks?

The answer is driven by service delivery network fundamentals:

Selection of LTE technology (LTE-FDD, LTE-TDD, LTE-Advanced)

drives the synchronization requirements

Mobile network equipment selection and cell site locations

(particularly for small cells) define what can and cannot be done

Backhaul network technologies, topology and performance drive

decisions for sync equipment selection and deployment locations


5/67


TA=1/fA

TB=1/fB

fA=fB

Frequency Synchronization

A

B t

t

Frequency, Time and Phase Synchronization

TA=1/fA

TB=1/fB

fA

=fB

Phase Synchronization

A

B t

t

01:00:00TA=1/fA

TB=1/fB

fA=fB

Time Synchronization01:00:10

01:00:00 01:00:10

A

B

t

t


6/67


FrequencyG.8261: Timing and Synchronization Aspects in Packet

Networks (Frequency)

Time/phaseG.8271: Time and Phase Synchronization Aspects in

Packet Networks

G.8273: Packet-Based Equipment Clocks for

Time/Phase: Framework

Structure of ITU-T Sync. Recommendations

G.8265.1: Precision Time Protocol Telecom

Profile for Frequency Synchronization

G.8275.1: PTP Profile for Time and Phase

Synchronization (full timing support)

Basic Aspects

Clocks

Methods

Profiles

G.8265.2 PTP Telecom Profile for Frequency #2

G.8261.1: PDV Network Limits Applicable to Packet-

Based Methods (Frequency)G.8271.1: Network Requirements for Time/PhaseNetwork

Requirements

G.8273.1: Telecom Grandmaster (T-GM)

G.8262: Timing Characteristics of a Synchronous

Ethernet Equipment Slave Clock (EEC)

G.8263: Timing Characteristics of Packet-Based

Equipment Clocks (PEC)

G.8264: Distribution of Timing Information through

Packet Networks

G.8271.2: Reserved for future use

Definitions /

Terminology

G.8260: Definitions and Terminology for

Synchronization in Packet Networks

G.8261.2: Reserved for future use

G.8272: Timing Characteristics of a Primary

Reference Time Clock (PRTC)

G.8273.2: Telecom Boundary Clock (T-BC)

G.8273.3: Telecom Transparent Clock (T-TC)

G.8273.4: Telecom Time Slave Clock (T-TSC)

G.8274: Reserved for future use

Completed 1st version published

G.8275: Architecture and Requirements for

Packet-Based Time and Phase Delivery

G.8265: Architecture and Requirements for Packet-

Based Frequency Delivery

optionsUnder development

G.8275.2: PTP Profile for Time and Phase

Synchronization (partial timing support)

New!


7/677Confidential Copyright 2012

Mobile Network Requirements

Mobile Standard

G.8261.1

network limits

for trafficinterfaces

Frequency

sync for the air

Interface

Phase Sync Standards

2G - GSM 16ppb 0.05ppm

No requirements

3GPP

TS25.104(FDD) and

TS25.105(TDD)

3G - UMTS/WCDMA

Wide area BS

Medium Range BS

Local Area BS

Home BS

16ppb

0.05ppm

0.1ppm

0.1ppm

0.25ppm

3G Femtocells N/A 0.25ppm

LTE (FDD)

Wide Area BSHome BS

16ppb

N/A

0.05ppm

0.25ppm

LTE (FDD) Local Area & Medium

Range BS0.1ppm No requirements (but see hetnets for LTE-Advanced) 3GPP TS36.104

LTE (TDD) Wide Area BS 16ppb 0.05ppm 3usec - small cell (3km radius)

3GPP TS36.133 &

TS36.922LTE (TDD) Home BS

N/A 0.25ppm

3usec small cell (< 500m radius)

1.33 + Tpropagation s, for large cell (> 500m radius),

Tpropagation: propagation delay between the Home BS and

the cell selected as the network listening synchronization

source

LTE-Advanced (Release 11)

Optional features*:

MBSFN

CoMP

Carrier Aggregation

Hetnets with eICIC

16ppb 0.05ppm1s proposed

0.5s proposed

?

5s proposed

TBA

* As shown in the table, LTE-FDD local area base stations (Pico cells and small cells) do not require phase sync. However, when we get to LTE-A hetnets, there will be interference

control between cells, which will place a 5 s phase sync requirement. The phase sync figures for these have been proposed bu t have yet to be fully agreed by the standards bodies.



Why is Synchronization Required?

Application Why You Need toComply

Impact ofNon-compliance

Call Initiation

Time slot alignment

Proper time alignment

of video signal decoding

from multiple BTSs

Coordination of signals

to/from multiple

base stations

Interference coordination

Call Interference

Dropped calls

Packet loss/collisions

Spectral efficiency

Video broadcast

interruption

Poor signal quality

at edge of cells, LBS

accuracy

Spectral inefficiency &

Service degradation

LTE (FDD)

LTE (TDD)

LTE MBSFN

LTE-A MIMO/COMP

LTE-A eICIC

Needs and Impacts are cumulative: plus all of the above



Synchronisation in 3G networks



AIRI

NTERFACE

3G Synchronisation Requirements

USER EQUIPMENT BASE STATION RADIO ACCESS

NETWORK

BASE STATION

CONTROLLERS

MASTER

CONTROLLERS

PUBLIC

SERVICE NETWORKS

BTS

Femtocell

OLT

Ethernet

DSLAM

TDM/

ATM

Microwave/

WiMAX

BSC

RNC

MSC GMSC

SGSN GGSN

AGW

(LTE)

AGW

(LTE)

Core

IP Service

Network

G.811 PRC for

TDM Transport

G.811 Traceable

G.812 Holdover

ETSI TS 125 402

G.811 PRC for

TDM Transport

G.811 Traceable+/- 50ppb

ETSI TS 125 104

+/- 50 ppb Macro/Microcell

+/- 100 ppb (PicoCell)

3GPP

250 ppb Accuracy

ITU-T G.823

Compliant TDM

NTP Overlay for event recording, Call Data Records & Femtocell Sync

NodeB

eNode

B

TDM TransportsSynchronisation

Timing Chain

Interrupted


11/67


3G Synchronisation in an all IP RAN using

IEEE1588 PTP

Each RNC has a fully redundant TP5000 GrandMaster

Hop count between the GrandMaster and clients should be kept to 10 max.Each TP5000 GM supports up to 1000 PTP clients

Additional units may be considered should the number of PTP clients exceed 1000.

SyncE is provided from the TP5000 E1/2MHz outputs which will connect to the

router/switch BITS IN port.

ITU-T specifies the number of hops in SyncE as 20. However, in practice, the

number of hops from the GM to the end points should be kept to around 10.NOTE: If PTP is used to deliver sync to the RBS, it is not necessary to use SyncE.

The TP5000s receive their main reference from built-in GPS.

As an option, the TP5000 can receive a clock reference derived from another

source such as Cesium clocks

TP5000 Grandmaster

Packet

NetworkGPS SyncE

PTP

RNC

PTP ClientPTP Flow


12/67


Evolution and relationship between Mobile

networks and synchronisation


13/67


Evolution and relationship between Mobile

networks and synchronisation

As the TDM platform is replaced by all IP networks, it is no longerpossible to distribute sync in the same way as TDM

Packet network cannot pass sync in the traditional TDM way

New sync methods are required to achieve sync delivery

New sync methods include: IEEE15888v2 (or PTP)

SyncE

NTP

The current BSNL sync architecture is well planned andimplemented

However, sync delivery in TDM is completely different to sync

delivery in the IP world, with the exception of SyncE which is

similar in nature


14/67


How to migrate existing Sync to NG to meet

LTE requirement

Planning Objectives & Rules The migration plan must allow seamless upgrade and support

introduction of new applications

IP MBH

LTE (TDD, LTE-A, etc) The synchronisation platform must support all sync requirements

SyncE, IEEE1588 (PTP), NTP and TDM (E1/2MHz)

The packet network elements shall be able to deliver or support

the new synchronisation technologies SyncE, PTP, NTP


15/67


How to migrate existing Sync to NG to meet

LTE requirement

Planning Objectives & Rules Identify the requirements of each application (2G/3G/4G) and

transport media to that application to determine the type of

synchronisation to be used

For example:

2G/3G base station needs 16ppb frequency sync

Transport is CE

Use SyncE if it is supported by the transmission path

Use PTP if SyncE is not possible


16/67


Synchronisation in the TDM Network

SDH

The PRC reference is distributedthrough the SDH network

SSUs are used to regenerate the

reference

Ultimately, the reference is

delivered to the BTS/NodeBsSDH

SDH

SDH

SDH SSU/PRC

SSU

SSU

SSU

TDM Sync flow

TDM

Access


17/67


Access

Access

Aggr

Aggr

Aggr

IP Core

Migrating to a Hybrid Network

TDM & IP with SyncE

SSU

SSU

SSU

SDH

SDH

SDH

SDH SSU/PRC

SSU

SSU

SSU

TDM Sync flow

TDM

Access

SyncE flow


18/67



TDM & IP with SyncE

Sync in the SDH portion remains unchanged

Sync from the PRC is fed to the IP network as an E1/2MHz reference (into the

NE BITS port)

SyncE works in the same way as SDH sync

Physical layer

Same planning rules PRC, SSU regeneration, 5 to 10 hops

Delivers high quality sync, traceable to PRC

According to G.8261

However

Each NE is the chain has to support SyncE not always possible

Only delivers frequency sync, no phase/time sync

The cell site device (CSS, CSR) must be able to convert SyncE to E1 to

synchronise the 2G/3G base station


19/67


Access

Access

Aggr

Aggr

Aggr

IP Core


TDM & IP with PTP (optionally over SyncE)

SSU

1588

SSU

1588

SSU

1588

SDH

SDH

SDH

SDHSSU/PRC

(PTP GM)

SSU

SSU

SSU

TDM Sync flow

TDM

Access

PTP flowSyncE flow


20/67


Synchronisation in a Hybrid Network

TDM & IP with PTP (optionally over SyncE)

Sync in the SDH portion remains unchanged

IEEE1588 GMs are added at the aggregation layer

GM ports connect to Ethernet ports on the routers

PTP flows are distributed to the base stations

Uses Unicast mode, telecom profile according to ITU-T G.8265.1

NOTE

The transmission network does not need to support PTP (on-path support)

This method is highly suitable for delivery of frequency sync to 2G/3G

10 hops between GM and the clients

Either the base station has a PTP client or the cell site device (CSS, CSR)

must be able to convert PTP to E1 to synchronise the 2G/3G base station


21/67


ITU standardising use of PTP + SyncE

Running PTP Only

Phase drift off as t2

during holdover when losing PTP

without PTP

NO PPS control

Frequency

Phase

with PTP

actively

controlling

PPS

Running PTP + SyncE

with PTP

actively

controlling

PPS

without PTP

NO PPS control

Frequency

Phase

Phase drift off linearly

during holdover when losing PTP


22/67


Current Architecture Directions


23/67


MBH Synchronisation in all IP

LTE - TDD

G.8275.1 Submission

Led by China Mobile with support from Huawei and ZTE

G.8275.2 Submission

Led by Symmetricom, AT&T, Cisco with support from Sprint,Verizon, T-Mobile, NSN, Juniper, and Ericsson.


24/67


PTP

Slave

PTP

SlaveDSLAM

DSL

modem

PTP

SlaveOLT ONU

PTP

Slave

CMCC Architecture (pre G.8275.1 )

PTPoL2 + Multicast + SyncE + BC at every node

PTPGM

Primary

PTP GM

PTPGM

Secondary

PTP GM

Edge Packet Network Access Network

PRTC

PRTC

Boundary Clock

(packet time and frequency distribution)

End Equipment

(e.g. Base stations)


25/67


Managing Asymmetry in BC Everywhere

(China Mobile)

Perfectly symmetrical network time propagation is relatively easy

Asymmetrical network time propagation is difficult

a

b

a = b

T = a+b/2

T

a =/= b

T = a+b/2 > T

T

a

b

T


26/67


Issues: Managing Asymmetry in BC

in Every Node (China Mobile)

The only solution to the problem of network asymmetry is to

measure the delay on downstream and upstream for every fiber

and every potential PTP path and put that compensation offset

into every BC this has to be done Manually today

Asymmetrical network Manual offset calibration required

T

a

b

OFFSET

injected


27/67


Other Issues: Managing Asymmetry in BC

in Every Node

Legacy MPLS / CE networks do not have BC support in NE

Not backward compatible -

it is difficult or impossible to upgrade a network without massive

new investment in switches/routers

BC everywhere requires syncE Legacy Ethernet networks so not usually support syncE

Multicast does not solve problems inherent in asymmetry when

distributing time

Currently operator has to measure the time offset on every linkmanually and put a compensation factor into every BC in an

attempt to manage time distribution

h hi f i / h


28/67


Why new architectures for Time/Phase

G.8275.2

The G.8275.1 scheme is only suitable for green field networks

Many Service Providers need an upgrade path from currently

deployed G.8265.1 (Frequency) networks to Phase

Introducing Boundary clocks in every node is not practical

Layer 3 operation is needed Manual asymmetry compensation is not practical

New architectures are being tested by many operators and

introduced at the ITU


29/67


G.8275.2 - Segmented Architecture

Divides the macro network into smaller sectorseach capable

of accurate time transfer using G.8265.1 PTPoL3 Unicast , combined with SyncE

TC possible in Access NEs for Asymmetry resolutionPTP

Slave

PTP

SlaveDSLAM

DSL

modem

PTP

SlaveOLT ONU

PTP

Slave

PTPGM

Primary

PTP GM

PTPGM

Secondary

PTP GM

PRTC

PRTC

PTP Timing

Flows

Protection

Timing Flows

Edge Packet Network Access Network

(packet time and frequency distribution)

Edge

GM

Edge

GM

Edge

GM

Edge

GM

End Equipment

(e.g. Base stations)


30/67


G.8275.2 - Segmented Architecture

PTP

GM

PTP

BC

PTP

BC

PTP

Slave

Strategically-placed BCs break timing path into segments

Simple network upgrade from Frequency Profile

Uses intelligent syntonized boundary clocks (EM)

Combine sync from any available source: PTP, SyncE, SDH, GPS etc.

Effectively a multi-source sync clean-up and re-generation SSUfunction

Implemented as a Standalone box - Edge GM

Design rules

No more than 3 switch/routers between BCs No more than 10 network elements between GM and Slave

ITU T S b i i G 8275 2 A C t Eff ti


31/67


No change out for network hardware

Can run time/phase services overexisting MPLS / CE network

Preserves MPLS value proposition

No change to back office engineering

and operations processes Removes BC engineering

Stand alone sync not dependent onembedded NE

Quality of BC design not an issue

ITU-T Submission G.8275.2: A Cost Effective

Alternative to BC in every NE

Leverages existing investmentmade in GPS at eNodeB sites

Leverages any existing PTPdeployments for FDD architectures

Deploys highest quality PTP client

Compliant to all existing FDD andTDD standards

Driving the standards forward

Simple and easy to deploy for allLTE architectures

eNodeB

PRTC

GM

PTPSlave

Edge GM


32/67


Guidelines

2. Protect your sync for service assurance GNSS, PTP & Stable frequency source

High performance holdover

3. Deploy a PTP master where the network needs it for accuracy

Network supports accuracy: PTP GMs in aggregation network

Uncertain network: PTP Grandmaster at or near the edge

1. Use an independent source for syncBest in class solutions

Efficient operation in a multi-vendor network


33/67


Basic Network Scenarios

3. LTE phase, retrofitted or new Ethernet backhaul

SyncE and Boundary Clocks in every network element

2. LTE frequency, high PDV, noisy backhaul

Diverse transport technologies, 3rd Parties, many hops

4. LTE phase, existing backhaul, possibly high PDV, noisy

No BC, probably no SyncE, diverse transport, 3rd party

1. LTE frequency, managed Ethernet backhaulConsistent, known backhaul performance

Setting and Holding


34/67


Setting and HoldingTwo aspects of synchronization

Frequency Phase

Deliver and set

frequencyHold

frequency

Deliver and set

phase

Hold

phase


35/67


1. LTE Frequency: G.8265.1 Architecture

Managed Ethernet backhaul

consistent, known performance

Set frequency with PTP (GNSS primary source)

Hold frequency with high quality oscillator

CORE ACCESSAGGREGATION

Macro eNodeB

Small Cell

Agg.

Metro Small Cells

PTP GM

PTP GM


36/67


1. LTE Frequency: G.8265.1 Architecture

Synchronization Distribution Architecture

Sync equipment and deployment

Macro agg. site: high capacity PTP grandmaster,

redundant equip. configuration and networkprotected

Macro eNodeB: PTP client & high quality oscillator

(or GPS/GNSS)

Metro Small Cell: PTP client (softGPS) PTP delivery: engineered QoS/CoS or EVC/VPN,

shortest path

PTP profile: G.8265.1, layer 3, unicast

1 or 2-step clock

Pros

Fully protected synchronization

Proven in networks worldwide

Fully standards based

Managed Ethernet backhaul

consistent, known performance


37/67


2. LTE Frequency: Edge Overlay Architecture

Uncertain performance, noisy backhaul

Multiple technologies, many hops/paths, high delay variation,

alternate access vendors, etc.

Set frequency with PTP or GNSS

Hold frequency with PTP or GNSS


Macro eNodeB

Small CellAgg.

Metro Small Cells

PTP GM

PTP GM

PONONUOLT

Microwave

DSLmodemDSLAM

High PDV / 3rd Party

edge GM

edge GM

Consistent with G.8265.1


38/67


2. LTE Frequency: Edge Overlay Architecture



Macro agg. site: high capacity PTP grandmaster,redundant equip. configuration and network

protected

Macro eNodeB site: PTP Master with GNSS

Metro Small Cell: PTP client (softGPS)

PTP delivery: engineered QoS/CoS or EVC/VPN,

shortest path

PTP profile: G.8265.1, layer 3, unicast

1 or 2-step clock

Pros


Mobile network sync is unaffectedby backhaul technology or quality

Proven technology, fully standards

based

Uncertain performance, noisy backhaul




39/67


CORE AGGREGATION

Retrofit existing equip. or build new networkManaged Ethernet, synchronous Ethernet, boundary clocks

ACCESS

Set time/phase with PTP (GNSS at primary source)

Hold time/phase with rubidium

3. LTE Phase: Pre-stand G.8275.1 Architecture

BC

BCBC

BC

SyncE

SyncE

SyncE

SyncE

BC

SyncE

Macro eNodeB

RbBC

SyncE

BC BC BC

PTP GM

SyncE

PTP GM

SyncE Small Cell

Agg.

Metro Small Cells

BC

SyncE

SyncE

SyncE SyncE

BC

SyncE

BC

SyncE


40/67


3. LTE Phase: Pre-stand G.8275.1 Architecture




SyncE, redundant equip. configuration andnetwork protected

Macro eNodeB: PTP client and Rb

Metro Small Cell: PTP client (softGPS) PTP delivery:

SyncE and boundary clocks, possibly with

segmented architecture

PTP profile: pre-G.8275.1, layer 2 multicast

1-step clock

Cautions

Asymmetry may require hop by hop,

manual adjustments to time offset

Quality of PTP client affectsperformance

No upgrade path from G.8265

frequency architecture

Design Rules SyncE through entire transmissionpath for stability

Boundary clock on all transmission

network elements

Retrofit existing equip. or build new networkManaged Ethernet, synchronous Ethernet, boundary clocks


41/67


4a. LTE Phase: Hybrid GPS/PTP Arch.

Existing backhaul, good performanceLast mile of network supports accuracy needed for phase to macro

Set time/phase with PTP

Hold time/phase with PTP or Rb

Pre-G.8275.2 (consistent with G.8265.1)

Requires high quality PTP slave

Once set, asymmetry is not an issue


Macro eNodeB

Small Cell

Agg.

Metro Small Cells

PTP GM

PTP GM

edge GM

edge GM

Rb

Microwave



42/67


4a. LTE Phase: Hybrid GPS/PTP Arch.




redundant equip. configuration and network

protected

Access network site: PTP master/ BC with

GPS/GNSS

Macro eNodeB: high quality PTP client and Rb

Metro Small Cell: high quality PTP client (softGPS)

PTP delivery: engineered QoS/CoS or EVC/VPN,

shortest path

PTP profile: pre8275.2 (G.8265.1), layer 3

unicast

1 or 2-step clock

Pros

Saves deploying master at the cell

site


No network retrofit: mobile

network sync is unaffected by

backhaul technology or quality

Asymmetry not an issue

Proven technology, standardsbased

Existing backhaul, good performanceLast mile of network supports accuracy needed for phase to macro


43/67


4b. LTE Phase: Edge Overlay Architecture

Existing backhaul, diverse tech and/or noisy

Multiple technologies, many hops/paths, high PDV, 3rd party, etc.

Set time/phase with GNSS

Hold time/phase with PTP


Requires intelligent, high quality implementations

of BC at aggregation site and PTP slave at macro


Macro eNodeB

Small CellAgg.

Metro Small Cells

PTP GM

PTP GM

edge GM

Microwave

PTP BC



44/67


4b. LTE Phase: Edge Overlay Architecture




redundant equip. configuration and network

protected

Access network site: high quality PTP BC

Macro eNodeB: high quality PTP client & GNSS/GPS

Metro Small Cell: high quality PTP client (softGPS) PTP delivery: engineered QoS/CoS or EVC/VPN,

shortest path

PTP profile: pre-8275.2 (G.8265.1), layer 3 unicast

1 or 2-step clock

Pros


No network retrofit: mobile networksync is unaffected by backhaul

technology or quality

Asymmetry not an issue

Proven technology, fully standards

based





45/67




Core: high capacity, carrier grade NTP server (or PTP grandmaster);

redundant equip. configuration and network protected

High quality embedded clients in the small cell; with or without softGPS

Residential and Enterprise Indoor Small Cells

Wireline network backhaulDSL, PON, Cable, Metro Ethernet

WIRELINE ACCESS NETWORKINTEROFFICE FACILITIES

PONONUOLT

NTP Server

PTP GM

NTP Server

PTP GM

DSL modemDSLAM

CablemodemCMTS


46/67


Summary

LTE technologies drive new requirements for synchronization

Backhaul network technologies, topology and performance

drives synchronization equipment and deployment decisions

Emerging boundary clock solutions will work for somescenarios but not all

GPS/GNSS requires back up and is not feasible for some

deployment scenarios

An alternative architecture that places a PTP master at or

near the edge is the solution for many of these situations


47/67


Symmetricom Solutions for LTE Networks


48/67


NGN Product Family

Primary Reference Source

ITU-T G.811 compliant

12 year warranty tube

TimeCesium

Full FCAPS

Platform independent

PTP Performance monitoring

Resiliency, northbound interfaces and much more

TimePictra Next Gen EMS TP10

Carrier Class Performance, G.811 compliant

PTP GrandMaster Modules

NTP Modules

GNSS support, SyncE outputs

SSU2000


49/67


NGN Product Family

G.811 Compliance

Timing Distribution System (TDM, 1588, SyncE, NTP)

Management software

Time Provider 5000 (TP5000) PTP GM

Delivers G.8272 PRTC time/phase accuracy within 100ns of UTC

Boundary Clock function

PTP, SyncE, TDM interfaces

GNSS support

Rubidium or OCXO holdover

EdgeMaster - TimeProvider 2000 Series

Stand-alone client

PTP input - E1/2MHz, 1pps and 10MHz outputs

Time Provider 500 (TP500)

TimeCesium


50/67


TimeCesium

Primary Reference Source (PRS)

Primary Reference Clock By Definition

Cesium PRS designed for Telecommunication

applications.

Install and forget autonomous technology

with no antenna installation.

Compliant with G.811 accuracy requirements Single chassis for NEBS (rear access) or ETSI

(front access)

Field Changeable Panels for Reversible

front/rear access.

CE Mark, ETSI and NEBS certified.

Dual -48 volt DC Power Inputs.

Standard 12 Year Warranty on the Cesium

Tube.
http://www.mts.ca/aboutmtsallstreamhttp://www.mts.ca/aboutmtsallstreamhttp://www.mts.ca/aboutmtsallstream


51/67


Precision Time Protocol (PTP)

PROVEN

Deployed in over 100 networks globally

IEEE 1588-2008 (also called v.2) approved in 2008

Introduction of PTP Profile concept

ITU-T PTP Telecom Profile for frequency (G.8265.1)

Approved in 2010

STANDARDIZED

SyncWorld EcoSystem Program

INTEROPERABLEDeployed in over 150 networks globally
http://www.t-mobile.co.uk/Dispatcher?menuid=menu_item_00http://www.allstream.com/


52/67


SSU blades support yournetwork when:

An SSU is installed on site

When the BSC/RNC is

co-located at Mobile

Switching Centers.

For applications beyond theCentral Office, a cost-effective

stand-alone GM is available:

At remote BSC/RNCs, POPs

and offices without an existingSSU2000 / where TDM port

count does not require an SSU

Added carrier class NTP

SSU PTP Blade TimeProvider 5000

Flexible PTP Grandmaster Platforms

i id l


53/67


TimeProvider 5000 Release 2.0

TP 5000

TPE10

TPE30

TimeProvider Expansion

1RU Rack-and-Stack with TP

5000 PTP GM

Up to 10 expansion shelves,

Flexible, NGN Building Blocks

TimeProvider Expansion10:

SyncE and PTP (L2 multicast)

TimeProvider Expansion30: E1

and 1PPS/TOD

Rel. 2.0 new SW features

Expansion shelf support,

new IMC required

Input priority switching

NTP Server (optional

SW license)

500 VLAN support

(optional SW license)

PTP probe (optional SW

license)

Carrier grade NTP server

Ultra high capacity

High precision

Hardware

redundancy

Two versions to sell

Dedicated NTP server

Dual PTP/NTP (TP5k option)

S i P E bli h M bil Ed


54/67


Strategic Program Enabling the Mobile Edge

WHAT

Deploy the PTP master to edge aggregation sitesVALUE

Delivers PTP closer to edge of the network

Enables precise sync for LTE-Adv and Small Cells

SYMM Advantage

Performance assurance for LTE phase delivery

Not dependant on full on-path support

Metro

IEEE 1588 (PTP)

Small CellsEdgeAggregationCore

Metro

PTP/SyncE PTP/SyncE

Enabling the Mobile Edge
http://sjc-sharepoint/CorpMkt/Product%20Images/Communications/TimeProvider_5000/High_Rez/TimeProvider5000_RevG_LtoR.jpghttp://sjc-sharepoint/CorpMkt/Product%20Images/Communications/TimeProvider_5000/High_Rez/TimeProvider5000_RevG_LtoR.jpghttp://sjc-sharepoint/CorpMkt/Product%20Images/Communications/TimeProvider_5000/High_Rez/TimeProvider5000_RevG_LtoR.jpg


55/67


Enabling the Mobile Edge

Introducing Time Provider 2000 Series

Precise network timing solutions optimized for small cells

Accelerates adoption of cost-effective partial-path PTP sync (G.8275.2)

Delivers frequency & phase timing services for up to 64 clients

Time Provider 2700 PTP Grandmaster Clock Delivers G.8272 PRTC time/phase accuracy within 100ns of UTC

Delivers G.811 PRC frequency accuracy to within 1 x 10 -11

1588v2 PTP support for 1-step, 2-step methods (unicast, multicast*)

GNSS support with GPS and optional GLONASS

Time Provider 2300 PTP Carrier-Grade Boundary Clock Best-in-class PTP client provides outstanding performance in noisy networks Converts PTP to L1 Frequency Sync (G.8265.1 Telecom Profile) and/or T1/E1

Used available frequency inputs (Sync-E or E1/T1) to reduce system recovery time

Both 2700 and 2300 employ a common PTP SW architecture, our most

advanced PTP timing algorithms, and high quality oscillators (OCXO or

Rubidium) that together deliver excellent operational performance.

Target

AvailabilityQ2 2013

*Future

Time Provider 2700


56/67


Hardware Features

Model 2700 Grand Master PTP Clock

GNSS (GPS) L1 input

2 oscillator options: OCXO, Rubidium

2 x 100/1000 Copper (RJ45) Ethernet Interfaces (PTP, Sync-E)

PTP Output (with 8 clients, upgradeable to 64)

Sync-E (Input / Output)

1 x 10MHz or 1PPS programmable BNC output

Redundant-DC Power, 1RU, 19 rack, 224mm deep Model 2750 Grand Master PTP Clock with Legacy TDM Support

Same hardware features as Model 2700

E1/T1 Frequency Support (input/output)

2 x 100/1000 Optical SFP Ethernet Interfaces (PTP, Sync-E)

1 x PPS+TOD (RJ45, RS422) Interfaces (output)

AC Power Option NEBS-compliant

SW License Options

PTP Input License (alternate or backup to GPS, provides asymmetry compensation)

PTP Output Capacity Upgrades (16, 32, 64)

GLONASS GNSS Upgrade

Time Provider 2700


57/67


Hardware Features

Model 2700 Grand Master PTP Clock

Model 2750 Grandmaster Clock with Legacy TDM Support

Time Provider 2300


58/67


Hardware Features

Model 2300 Carrier Grade Boundary Clock

2 oscillator options: OCXO, Rubidium

2 x 100/1000 Copper (RJ45) Ethernet Interfaces (PTP, Sync-E)

PTP (Input and Output with 8 clients, upgradeable to 64)

Sync-E (Input / Output)

1 x 10MHz or 1PPS programmable BNC output

Redundant-DC Power, 1RU, 19 rack, 224mm deep

Model 2350 Carrier Grade Boundary Clock with Legacy TDM Support

Same hardware features as Model 2300

Legacy E1/T1 Frequency Support (input/output)

2 x 100/1000 Optical SFP Ethernet Interfaces (PTP, Sync-E)

1 x PPS+TOD (RJ45, RS422) Interfaces (output)

AC Power Option NEBS-Compliant

SW License Options

PTP Output Capacity Upgrades (16, 32, 64)

Time Provider 2300


59/67


Hardware Variants

Model 2300 PTP Boundary Clock

Model 2350 Boundary Clock with Legacy TDM Support

TimeProvider 2000 Series


60/67


Flexible Deployment Options

TP2000 can be deployed in a wide range of environments.

Wide temperature range -40C to +60C* allows deployment in many

non-air conditioned cabinets

Dual DC Power feeds simplify connecting to battery backup systems

AC Power option** helps with deployment in enterprise locations

NEBS compliance** enables deployment in central office locations

* OCXO Oscillator only, Rubidium is -5 to +55C.

Outdoor Enclosures Indoor Data Centers

** Models 2350 and 2750.

Platform positioning based on network location


61/67


Platform positioning based on network location

AggregationCore

SSU2000

TP2700 / TP 2300

TP5000

Metro Outdoor

Large Venues

Enterprise

Up to 1000 Clients

GM

Indoor

TDM, PTP, Sync-E

Up to 64 clients

GM or BC

Indoor / Outdoor

TDM, PTP, Sync-E

Edge

Up to 8 Clients

GM or BC

Indoor / Outdoor

PTP, Sync-E

Small Cells


62/67

TimeProvider 2000 Series


63/67


Use Cases


Multiple technologies, many hops/paths, high PDV, 3rd party, etc.

Set time/phase with GNSS

Hold time/phase with PTP


Requires intelligent, high quality implementations

of BC in access network and PTP slave at macro


Macro eNodeB

Small CellAgg.

Metro Small Cells

PTP GM

PTP GM

edge GM

Microwave

PTP BC


Use Cases


64/67


Deploy a 2700 Grandmaster near the Edge

Allows adoption of G.8275.2 sync approaches

Cost effective standards-compliant GM at edge aggregation sites Ensures 1.5 us phase accuracy required for LTE network evolution

Outputs Time/Phase w/accuracy under 100ns when locked to GPS

Outputs Frequency (Sync-E) and/or T1/E1

Fully protected input reference suite

If GPS fails, system can fall back seamlessly to other input clock sources:

PTP 1588v2 (Boundary Clock Mode) with automatic asymmetry path compensation

based on GPS measurement history

Sync-E, T1/E1

Robust oscillator options (high quality OCXO and Rubidium) Ensures the best quality boundary clock operation for backup

Provides outstanding hold-over

Hardware acceleration (such as time stamping) delivers optimal performance

Wide temperature range enables flexible deployment options

Use Cases


65/67


Deploy a 2300 Carrier Grade Boundary Clock

Use in locations where GNSS is not available or not robust.

Use to boost PTP reliability at sites where embedded boundary clocks, offeredby Cell Site Routers (CSR), are not delivering sufficient performance.

TP2300 Carrier Grade Boundary Clock Advantage

External compact solution ensures predicable performance across the network

Advanced clock algorithms & hardware acceleration deliver optimized performance

High phase accuracy delivers robust LTE network operation and enables networkevolution to advanced LTE features (eICIC, COMP).

Optimized hybrid mode operation leverages available frequency inputs such as

Sync-E and/or T1/E1*

Robust oscillator options (high quality OCXO and Rubidium)

Provides outstanding hold-over if the northbound PTP fails

Ensures the best quality boundary clock operation

* If available

Deployment of a TP2750 at an mobile


66/67


Solution is deployed out-of-band from bearer traffic

network aggregation site

IP A IP B (OC)IP C (GM)

VLAN 3

Main Bearer Traffic (VLAN5, VLAN6)

South Bound PTP Traffic and/or Sync-E (4500 GM to BS OC)

North Bound: PTP Traffic and/or Sync-E (TP5000 GM to 4500 OC)

VLAN 3

Management Traffic

Cell Site Router

TP2750 (GM, w/BC Backup)

OC

OC

OC

OC

BS

OC

VLAN 6

VLAN 5

MPLS /Ethernet

LTE EPC

VLAN 3

GPS(required for GM operation)

VLAN 8

TP5000 or SSU2000 (GM)

Thank You


67/67

Symmetricom, Inc.

2300 Orchard Parkway

San Jose, CA 95131-1017

Tel: +1 408-428-7907

Thank You

Synchronization Solutions for LTE Networks

Charlie [email protected]
mailto:[email protected]:[email protected]

Date post:	29-Oct-2015
Category:	Documents
Upload:	shejin-raghavan
View:	281 times
Download:	0 times

Sync Solutions for LTE_2

Documents