WP Mobile PTP

W H I T E PA P E R
Joan dAustria, 112 - Barcelona - SP - 08018

Chalfont St Peter - Bucks - UK - SL9 9TR
www.albedotelecom.com
Synchronization & Mobile networks

1. INTRODUCTION
For many years the frequency synchronization requirements of GSM, 3G and
UMTS networks were satisfied by means of TDM signals such as T1 or E1. This
solution was straight forward because the infrastructure to support mobile
backhaul was made of SONET / SDH, thereby the synchronization signal could
be extracted from the PHY layer or being transported through a separate network. In any case both transport and synchronization were based on TDM technologies.
From Circuit to Packet migration
Master
However, during the last decade many things have changed, mainly because
mobile operators have been abandoning SONET/SDH circuits while adopting
Ethernet / MPLS / IP to support new mobile backhaul architectures. This is a major challenge for base stations that always require a very accurate synchronization that native Ethernet cant supply.
day
time
2014 - Jul 9th - 17:02
f0
Reference Clock (frequency)

Clock significant instants (phase)
d1
t1
2014 - Jul 9th - 17:02

d2
t2
XXX - XXXX- 17:02

d3
1 - Time/Day Synchronization
(f1=f0 ; ph1=ph0 ; t1=t0 ; d1=d0)
f1
f2
2 - Phase Synchronization
(f2=f0 ; ph2=ph0 ; t2=t0)
f3
3 - Syntonization
(f3=f0)
t3
XXX - XXXX - X:XX
4 - Asynchrony
Figure 1
Synchronization of Frequency and Phase error of a signal in relation to its Reference Clock.
All rights reserved. No part of this document may be stored, copied or transmitted, by any means, without the permission in written of the Legal Owner
2016 ALBEDO Telecom
Networking & Telecoms - S y n c h r o n i z a t i o n & M o b i l e n e t w o r k s
Why Synchronization is required?

Synchronization enables many services including assisted navigation, location, and emergency calls. Moreover, synchronization is fundamental to every cellular technology otherwise they would not even work. Base stations
must calculate permanently the distance to every single mobile operating in
their cell and the neighboring cells. Base station and mobiles have to generate exactly the up/down frequencies and have to access to transmission
time-slots. There are many reasons to keep a good synchronization:
ALBEDO Telecom - Registered in Barcelona, Book 41613, Page 155, Sheet B-390886 - VAT : ESB6523022
to calculate the distance to mobile terminals,
A L B E D O - W H I T E P A P E R
2 / 15
to support geographical localization services,

to control the transmission power,
to avoid interferences with other cells and base stations,
to manage handovers,
to get accurate access to the time-slots,
to compensate the propagation delay,
to reuse frequencies efficiently,
to plan small and micro cells,
to calculate the billing.
Then we agree that synchronization is fundamental for any basic mobile service therefore it is just impossible to get rid of it.
Some background in multiplexing & synchronization

Multiplexing and Multiple Access
Multiplexing is defined as the process by which several signals from different

channels share a channel with greater capacity. Basically, a number of channels share a common transmission medium with the aim of reducing costs
Net.Storm
Figure 2
Net.Hunter
Net.Genius
Ether.Genius is an multitechnology tester equipped with all the features to install and troubleshoot networks
based on Gigabit Ethernet, Synch Ethernet, Precision Time Protocol and E1. Net.Storm it is a compact WAN
emulator. Bandwidth control is done by means of Traffic Shaping & Policing impairments (delay, loss, jitter...),
are inserted in a 100% controlled way. Net.Hunter is a stream-to-disk appliance capable of monitoring live
traffic to capture selected TCP/IP flows at wirespeed.
Professional Telecom Solutions

TEST- LABOS - TA PS - WAN EMULATION - E1 - G BE - SYNCE - WLESS - LTE - 3G - IPTV - VoIP - QoS - SLA - ONEWAY - DATACOM - POLQ A - PT P - JITTER - WAND ER
Multiplexing
DTE-A
DTE-B
.
.
.
B1
B2
.
.
.
Multiplexer
B1
B2
.
.
.
Bn
Bi
Transmission media
Bn
DTE-n
Demultiplexer
DTE-B
.
.
.
DTE-n
Bi = bandwidth
FDMA
DTE-A
TDMA
CDMA
110100010110111001
pattern
F
A E
B D
C
B A F E D C B A
3 / 15
data
001011101110111001
signal
frequency
Figure 3
time
code
bit
bit
Multiplexing consolidates lower capacity channels into a higher channel. Frequency division multiplexing
(FMDA). Time division multiplexing (TDMA) and Code division multiplexing (CDMA).
and complexity in the network. When the sharing is carried out with respect
to a remote resource, such as a satellite, this is referred to as multiple access
rather than multiplexing (see Figure 3). Some multiplexing technologies are:
Frequency multiple access (FDMA): Assigns a portion of the total bandwidth to each of the channels.
Time division multiple access (TDMA): Assigns all the transport capacity sequentially to each of the channels.
Code-division multiplexing access (CDMA) air interface facilitates multiple

access over a channel using spread-spectrum with a code per transmitter
Polarization division multiple access (PDMA): polarization direction can be

used as a multiple access technique in installations that use microwaves.
Space division multiple access (SDMA): using directional antennas the same
frequency can be reused, provided the antennas are correctly adjusted.
Duplexing
Base stations use today three two technologies to multiplex upstream and
downstream channels: frequency division duplexing (FDD), time division duplexing (TDD) and code division multiplexing (CDM).
FDD base stations air interface uses separate frequencies for the up/downlink, then requires only a frequency synchronization.
TDD base stations air interface uses the same frequency for the up/downlink then an absolute time and phase reference is required to get access to
time slots (see Figure 4).
Syntonization and Synchronization

Are similar concepts but not exactly the same:
Syntonization is the alignment of clocks to the same frequency, as
SDH/SONET used to do

Synchronization is the alignment of clocks to the same frequency and to the

same phase
Time of day synchronization, is the alignment of clocks to the same frequency, to the same phase and to a time origin. Then all clocks are aware of
the time and date information.
2.
ALTERNATIVES FOR TIMING
4 / 15
Once mobile backhaul has been migrated to Ethernet/ IP / MPLS there are a
number of alternatives to get the synchronization. The first one is to maintain the TDM signal however it is an expensive option. The second alternative
is GPS or GLONASS that can provide an absolute time reference. Finally SyncE
and PTP facilitates are the third alternative and are based on the provision of
timing through the packet network. This is probably the most interesting for
new mobile networks and it is cost-effective solution.
The truth is that many are replacing TDM lines with Synchronous Ethernet
and packet clocks using IEEE1588v2. Both SyncE and IEEE1588v2 are additions to the Ethernet data network, and provide the timing service to the mobile networks. Backhaul networks already require syntonization, and as this
trend is continuing to include synchronization.
Syntonization with TDM

There is a number of TDM signals that are suitable to be used as timingsource:
Analog: 1,544 and 2,048 kHz;

Digital: 1,544 kbit/s (T1) and 2,048 (E1) kbit/s;
t im
t im
am t
e
m
r
lo
t
a
es
ns
tre
im
t
s
w
up
do
power
power
FDD
frequency
Figure 4
TDD
/d
up
rm
st
n
ow
tim
es
t
lo
frequency
In FDD duplexing upstream and downstream use separate frequencies, in TDD upstream and downstream
share the same frequency. FDD requires only syntonization while TDD is more and efficient on the use of the
available bandwidth but requires Phase Synchronization.

STM-n/OC-m line codes: from which one of the above-mentioned signals

can be derived, by means of a specialized circuit.
The employment of STM-n/OC-m signals has the advantage of using the S1

byte to enable synchronization status messages (SSMs) to indicate the performance of the clock with which the signal was generated. These messages
are essential in reconstructing the synchronization network automatically in
case of failure. They enable the clocks to choose the best possible reference,
and, if none is available that offers the performance required, they enter the
holdover state.
5 / 15
GPS or GLONASS synchronization

GPS has been available for many years (today also the russian GLONASS) and
often we have heard Why do not incorporate GPS at each base station? unfortunately it is vulnerable solution to jamming and interferences. Moreover,
GPS cells are everyday smaller and access to aerials is not always possible because are deployed indoors, in stadiums or shopping centers where access to
satellite signals could no be practical or it is very expensive. Even CDMA operators who traditionally have relied on GPS, do not it consider any more as
an acceptable solution due to operational and political reasons.
G.8260
Definitions
Frequency
G.826.x
Requirements
Phase
G.827.x
G.8261
G.8271
SyncE- Jitter/Wander
Time & Phase
G.8261.1
PDV limits
G.8262
Clock
SyncE Slave Clock
G.8263
Packet Based Clocks
G.8271.1
Time & Phase needs
G.8272
Primary Ref. Clock
G.8273
Master&Bound clocks
G.8264
Time Distribution
Methods
G.8265
Frequency Delivery
Profiles
Figure 5
G.8265.1
PTP frequency profile
G.8275
Phase Delivery
G.8275.1
PTP phase profile
Timing distribution through packet based networks.

Synchronous Ethernet
Synchronous Ethernet (SyncE) is an ITU-T standard that facilitates the transference of clock signals over the Ethernet physical layer. The signal should be
traceable to a unique external clock for the whole network. There are a number of ITU-T recommendations about this standard (see Figure 5):
G.8261 defines the Architecture and the wander limitations;

G.8262 specifies Synchronous Ethernet clocks for SyncE;
G.8264 describes the Ethernet Synch Messaging Channel (ESMC)
6 / 15
On many respects SyncE it is an evolution from SDH/SONET synchronization

and this is the reason because it shares many concepts including the synchronization architectures and topologies (see Figure 6).
Precision Time Protocol (PTP)

While Sync-E can provide the syntonization required by 2G and 3G networks;
PTP is indicated for those networks that also require the phase, freq. and
time synchronization.
SSU
Local osc.
4.6 ppm
ITU-T G.8262
EEC
ITU-T G.8262
EEC
Central timing card
Central timing card

Tx
ETH
ETY
Rx
SyncE
timing
Native Ethernet
ETH
SyncE
timing
SyncE card
Figure 6
ETY
Synchronization Backplane
Synchronization Backplane
Synchronous Ethernet
Local osc.
4.6 ppm
SyncE card
Tx
ETH
ETY
Rx
Local osc.
100 ppm
Ethernet card
ETY
ETH
Local osc.
100 ppm
Ethernet card
Synchronous Ethernet Architecture and comparison with conventional Ethernet.

PTP over IP
6 bytes
PTP message
Ethernet Header
Transport
Type
Reserved
Version
Length
Domain
Reserved
IPv4 or IPv6 Header
8 bytes
UDP Header
Transparent
Clock Corrections
PTP
Message
4 bytes
2 bytes
Ethernet FCS
Flags
2 bytes
Correction Fields
8 bytes
Reserved
4 bytes
Source Port
10 bytes
Sequence Id
2 bytes
7 / 15
PTP over Ethernet

6 bytes
Ethernet Header
Control
Log
PTP
Message
Sync / Delay Request
4 bytes
Figure 7
Time Stamp
8 bytes
Ethernet FCS
IP and Ethernet encapsulations for PTP messages.
PTP is a 2-way time transfer protocol with hardware time stamping to transport the timing within Ethernet frames or IP packets. In comparison with
SyncE intermediate nodes do not need to be upgraded and PTP can deliver
not only frequency but also time and day synchronization that is required for
TDD mobile networks (see Figure 1).
Interestingly PTP slaves communicate with short messages to the centralized
Grand Master Clock via native Ethernet networks. This is a very good news
indeed -the use of native networks- the unique requirement is to transmit
PTP in high priority to avoid congestion, and try to control the QoS particularly packet delay variation (see Figure 8).
3.
TIMING REQUIREMENTS OF MOBILE NETWORKS

Mobile operators are moving to a more efficient and higher capacity networks as there is more demand in terms of users and data but the available
radio frequencies already are largely allocated, then operators increasingly
use new techniques to squeeze more bandwidth from their existing spectrum allocations (see Table 1).

8 / 15
Master
Slave
native
IP
ethernet
t1
1 Sync
t2
2 Follo
w_Up
eq
3 Delay_R
Offset =
t3
t4
4 Delay_Res
Latency =
Figure 8
(t2 - t1) - (t4 - t3)

2
(t2 - t1) + (t4 - t3)

2
Delay Request-Response mechanism used by the PTP. The basic parameters of Latency and Offset are
computed from the t1, t2, t3 and t4 timestamps.
Depending on the technology Telecom Operators have different timing

requirements. Some of them running GSM and 3G may still maintain legacy
TDM links solely for syntonization and may want to eliminate that costly
equipment. Others are focus on LTE see the impending need for distributing
phase-synchronization and also want to avoid having to install GPS technology at every cell site.
GSM, 3G
GSM, 3G only require a frequency reference, it means that will be enough a

TDM or SyncE based syntonization (see Table 1).
Long Term Evolution (LTE)
LTE-FDD (Frequency Division Duplex) timing requirements are similar to GSM

and 3G. Only require a frequency reference. New LTE networks are very demanding on frequency and phase requirement, particularly those architectures that consider small cells, where the frequency reutilization is a key
factor of performance..
Table 1
Frequency & Phase requirements of wireless networks.
Wireless Architecture
GSM, 3G, LTE-FDD
CDMA-TDD
LTE-TDD
LTE-TDD
Wimax-TDD
Frequency
Base / Air
16 ppb
50 ppb
16 ppb
50 ppb
16 ppb
50 ppb
16 ppb
50 ppb
16 ppb
50 ppb
Phase
Timing Alternatives
Not required
3 s to 10 s
1.5 s to 5 s (large cells)
1 s to 1.5 s (small cells)
0.5 s to 5 s
TDM, SyncE, PTP

PTP, GPS
PTP, GPS
PTP, GPS
PTP, GPS

PTP
PTP
Read
Corrections
Write
Time-Stamps
Grandmaster
Ordinary
Boundary
Transparent
native
ethernet
enode-B
PRC
Master
Slave
Slave
+
Figure 9
Correction
Master
9 / 15
Corrections
Time-Stamps
IEEE1588 Precision Time Protocol can be transported across legacy packet switched networks and is able
to provide phase synchronization.
LTE is moving forward new timing requirements for not only frequency but
phase synchronization as well. This is the case of LTE-TDD (Time Division Duplex) that uplink and downlink share the frequency to make the system more
efficient. This scheme probes to be very flexible but it is necessary to provide
an absolute time reference to use in a flexible way the available time slots.
4.
PTP PROTOCOL DETAILS

PTP was defined in the IEEE 1588 standard that describes a master-slave architecture for timing distribution across Ethernet / IP packet network. The
standard offers some key advantages to manufacturers and operators that
can deploy PTP compliant equipment and avoid the cost of TDM and potential jamming, operational and political issues that come with deploying GPS
receivers at every base station (see Figure 9).
In IEEE 1588 system can be found several types of clocks (see Table 2):
A ordinary clock is a device with a single port connection that can play de
role of master or slave depending on its position in the network.
A master clock provides accurate time stamping to slaves clocks collocated

at the downstream side.
A grandmaster is a the master clock situated at root timing, therefore is the

clock reference, transmitting time information to the clocks of its segment.
A boundary clock has multiple network connections, works as slave upstream and as master downstream. Then it bridges synchronization from
one segment to another.
A transparent clocks pass through PTP messages adding in the correction

field the time spent packets when traversing the device (see Figure 7).

Table 2
IEEE 1588v2 Device Description
Clock
Description
Ordinary
Single-port device that can be a master or slave clock
Grandmaster
Ordinary clock that manages the reference time
Slave
Boundary
Transparent
(end-to-end)
Transparent
(peer-to-peer)
Operation
Ordinary clock that keeps synchronized to the masters and provides

synchronization to its clients
Multi-port device that can be a master or slave clock
Multi-port device that is not a master or slave clock but a bridge
between both forwarding / correcting PTP messages
Multi-port device that is not a master or slave clock but a bridge
between both forwarding / correcting Sync and Follow-up messages
Read/Write time stamps

Write time stamps and responds
time request from other clocks
Write time stamps and responds
time request from other clocks
Read/Write time stamps
Write corrections
10 / 15
Write corrections
By using boundary and transparent clock functions in the synchronization

chain, the effects of latency and packet delay variation are minimized. Master and slaves do exchange packets containing short messages to measure
and eliminate phase errors.
Using IEEE 1588v2 reduces the number of required GPS antennas and the associated cost, and it enables operators to distribute phase synchronization to
sites where GPS is difficult to deploy.
PTP Profiles
IEEE-1588 2008 introduced the Profile concept as a set of PTP optional features to support different types of applications. For instance a PTP profile
may define Path Delay Control, the transport mechanisms required, node
types, message exchange rate, unicast or multicast protocol. Profiles facilitate the interoperability between nodes and the deployment of PTP across
telecoms networks.
PTP Grandmaster
PTP Slave
native
ethernet
PRC
enode-B
e.tester
Y.1564 & RFC2544
Figure 10
e.tester
Multistream
Ether.Sync or Ether.Genius executing the ITU-T Y.1564 (eSAM) to verify the KPI that affect PTP flows.

PTP Grandmaster
PTP Slave
e.tester
native
ethernet
PRC
native
ethernet
e.tester
PTP Slave
Figure 11
11 / 15
PTP Grandmaster
PRC
ALBEDO Ether.Sync and ALBEDO Ether.Genius are testers that can emulate Master and Slaves nodes
while measuring key parameters such as time offset, phase deviation etc.
5. INSTALLATION, TURN-UP
& MAINTENANCE OF PTP
Service Activation
The first step it the analysis of KPI of the network that has to transport PTP
streams in terms of capacity and quality. They may determine the success -or
failure- of the implementation. With Ether.Genius executing eSAM can be
simulated a PTP service including the generation of background traffic with
different traffic profiles.
The basic purpose of eSAM is to check that PTP frames are transported with
the required performance in terms of Frame Total Delay (FTD), Frame Delay
Variation (FDV), Frame Loss Ratio (FLR) and Availability to make sure that the
SLA reserved for PTP messages is preserved by the network when required
to do so (see Figure 10).
PTP test and Measurements

During the installation of a IEEE 1588v2 network, PTP message connectivity
problems may occur between the master and slave units. For instance failure
to establish PTP message connectivity makes achieving synchronization impossible and disables support for services. When troubleshooting these links,
the ALBEDO Ether.Sync can be used in Terminate mode to capture PTP messaging on both the transmit and receive test ports up to 1 Gbit/s. In this
mode, the ALBEDO Ether.Sync simultaneously generates, receives, and cap-

tures PTP messages on the circuit under test. Users can quickly identify higher layer protocol issues that may be associated with PTP messages and/or
provisioning (see Figure 11).
The protocol PTP is designed to work under network conditions including

highly occupied networks. When there is a lot of contention the routing and
switching of PTP messages could therefore be affected causing potential bad
effects like packet delay variation in PTP messages will ultimately affect synchronization because it depends upon consistently timed message reception. Both ALBEDO Ether.Sync and ALBEDO Ether.Genius can emulate data
plane traffic (up to eight streams) while PTP messages are transmitted simultaneously. Under these conditions, field engineers can verify if the new or
the existing PTP network are capable to operate properly under many different load scenarios.
12 / 15
Network Impairments
PTP protocol is supported by packet networks and therefore PTP packets
may suffer the typical impairments including packet loss, packet delay, packet jitter, delay asymmetries in the paths, even out of sequence messages.
These are major inconveniences that degrade the quality of the synchronization. Fortunately Packet jitter can be compensate by boundary clocks. However path asymmetry produce different delays between upstream and
downstream, it is more difficult to filter and requires manually adjusts it is.
Despite the above mentioned difficulties clocks must remain stable minimizing these impairments and using the holdover function to keep synchronization in good shape an inside the tolerance masks (see Figure 12).
Loss
Error
Jitter
LTE
Bandwidth
Delay
async
Net.Storm
ethernet
enode-B
slave
boundary
master
PTP messages
1 - Filter PTP messages only
Figure 12
2 - Generate Impairments
Net.Storm can generate -in a 100% controlled way- packets impairments to verify how boundary clock
manage against packet lost and packet delay variation (PDV or Jitter). Net storm can also be used to
compensate delay asymmetries that cannot be filtered by boundary or slave clocks.

PTP Slave
PTP packets
pass
through
native
ethernet
PTP Grandmaster
mirror
PRC
enode-B
NHunter
NHunter
NTP
NTP
download
SDD disk
PCAP storage
13 / 15
tap
PTP
analysis
Net.Hunter Filters
Figure 13
Net.Hunter is a compact solution to manage quality, troubleshooting threats, incidents and malware.
ALBEDO Net.Storm is WAN emulator instrument that can generate network

impairments at FPGA performance (full wire-rate) over IP / TCP / UDP networks such as: latency, jitter, loss, error, duplication and modification of the
packets (see Figure 12). This the right to stress the PTP network to verify how
tolerant synchronization is under actual network conditions. It is of key importance also the ability of slave clocks to work in holdover maintaining a
good timing. With Net.Storm it is also possible to force asymmetries and
compensate them with an accuracy of nanoseconds.
PTP packet captures
Using ALBEDO Net.Hunter engineers have all the advantage of hardware tap
and overcomes those issues caused by PC based cards. It is a field handheld
tap that can filter at wirespeed PTP flows in both direction the rest of the
flows (protocols, data, etc) to pass with zero delay and no lost at all. PTP
packets that are compliant with any of the 30 programmable filters (based
on MAC, IP, TCP, Port, etc.) are copied and saved in an internal SSD disk with
in PCAP format and afterwards packets can be analyzed in the lab. Alternatively copied of PTP packet can be forwarded to a LAN in real time to be analyzed with an external device1.
An interesting feature is that Net.Hunter can be synchronized therefore the
captures of PTP packets with time-stamps can be very useful to study transparent clock performance, compensation timing, timing accuracies, etc. during the operation of LTE networks in-service and live traffic. Net.Hunter will
never drop packets, working at full wirespeed in full duplex and unlike other
capture alternatives it may also capture physical layer errors, FCS errored
frames, and non-standard frames as jabbers (see Figure 13).
1.
For instance a workstation equipped with a protocol analyzer that could be proprietary or freeware like Wireshark.

Selected Bibliography
[1] Sargento S., Valadas R., Gonalves J., Sousa H., IP-Based Access Networks for Broadband Multimedia Services,
IEEE Communications Magazine, February 2003, pp. 146-154.
[2] Ferrant J., Gilson M., Jobert S., Mayer M., Ouellette M., Montini L., Rodrigues S., Ruffini S., Synchronous Ethernet:
A Method to Transport Synchronization, IEEE Communications Magazine, September 2008, pp. 126-134.
[3] Vainshtein A., Stein YJ., Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP), IETF Request
For Comments RFC 4553, Jun. 2006.
[4] Vainshtein A., Sasson I., Metz E., Frost T., Pate P., Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over Packet Switched Network (CESoPSN), IETF Request For Comments RFC 5086, Dec. 2007.
14 / 15
[5] ITU-T Rec. Y.1413, TDM-MPLS network interworking - User plane interworking, March 2004.
[6] ITU-T Rec. Y.1453, TDM-IP interworking - User plane interworking, March 2006.
[7] ITU-T Rec. G.8261, Timing and Synchronization Aspects in Packet Networks, February 2008.
[8] ITU-T Rec. G.8262, Timing Characteristics of Synchronous Ethernet Equipment Slave Clock (EEC), August 2007.
[9] ITU-T Rec. G.8264, Distribution of Timing Through Packet Networks, February 2008.
[10] Metro Ethernet Forum Technical Specification MEF 8, Implementation Agreement for the Emulation of PDH Circuits over Metro Ethernet Networks, October 2004.
[11] Metro Ethernet Forum Technical Specification MEF 18, Abstract Test Suite for Circuit Emulation Services over
Ethernet based on MEF 8, May 2007.
[12] Considerations for Synchronization in NGN Packet-Based Mobile Backhaul Networks OSP Magazine Zeev Draer

test + measurement + WAN emulation + packet capture + synchronization + consultancy
ALBEDO Telecom
ALBEDO Tel ecom deli vers soluti ons that enable
Telecom infrastructures of all sizes to
troubleshoot, monitor, and migrate mission
critical networks.
From the deskto p to the data centre, from
Access Network, Ethernet, Sync-E, PTP, Optical
backbones, LTE, VoIP or IPTV applications.
On local segments and across distributed
networks , ALBEDO enable Telecom
Organizations, Telecom Installers, Network
Operators, Internet Servi ce Provi ders and
Co ntents Suppliers to quickly check the health
of your network, verify SLA, or find and fix
problems .
Benefits
Re sults . The ALBEDO Tel ecom to help Tel ecom
industry to make the most of the investment on
network infrastructure.
Expertise . ALBEDO trainers, auditors,
engi neers and consultants provi de
industry-leading knowledge to address the
unique needs of customers.
Integration. ALBEDO integrates disparate
telecom resources and applications, realizing
new busi ness effi cienci es.
Agility . ALBEDO increases the ability of
customers to respond quickl y to new market
opportunities and requirements.
Coverage. ALBEDO offers s oluti ons that
facilitates the mi gration and the roll-out to new
telecom archi tec tures.
in Test we Trust
Americas (US & Canada)
mjs@albedotelecom.com
+1 647 233 7353
Europe
rbt@albedotelecom.com
+34 610 292 763
India
prem.sethi@albedo.biz
+91-98110 55459
Switzerland
silvan.imhof@albedotelecom.ch
+41 (0)31 853 14 56
UK
jpr@albedotelecom.co.uk
+44 (0) 1865 601008
World Channels
sales.telecom@albedo.biz
(find out our nearest rep)
aims
+ LEARN from business models and case studies
+ UNDERSTAND the potential of interoperability with legacy services
+ EXPERIENCE specialised synchronization network solutions
+ ASSESS different solutions for installation and maintenance

WP Mobile PTP

Uploaded by

Copyright:

Available Formats

WP Mobile PTP

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WP Mobile PTP

Uploaded by

Copyright:

Available Formats

W H I T E PA P E R

Joan dAustria, 112 - Barcelona - SP - 08018

Synchronization & Mobile networks

From Circuit to Packet migration

2014 - Jul 9th - 17:02

Reference Clock (frequency)

2014 - Jul 9th - 17:02

XXX - XXXX- 17:02

XXX - XXXX - X:XX

2016 ALBEDO Telecom

Networking & Telecoms - S y n c h r o n i z a t i o n & M o b i l e n e t w o r k s

Why Synchronization is required?

to calculate the distance to mobile terminals,

to support geographical localization services,

Some background in multiplexing & synchronization

Multiplexing is defined as the process by which several signals from different

Professional Telecom Solutions

Networking & Telecoms - S y n c h r o n i z a t i o n & M o b i l e n e t w o r k s

Code-division multiplexing access (CDMA) air interface facilitates multiple

Polarization division multiple access (PDMA): polarization direction can be

Syntonization and Synchronization

Professional Telecom Solutions

Networking & Telecoms - S y n c h r o n i z a t i o n & M o b i l e n e t w o r k s

Synchronization is the alignment of clocks to the same frequency and to the

ALTERNATIVES FOR TIMING

Syntonization with TDM

Analog: 1,544 and 2,048 kHz;

Professional Telecom Solutions

Networking & Telecoms - S y n c h r o n i z a t i o n & M o b i l e n e t w o r k s

STM-n/OC-m line codes: from which one of the above-mentioned signals

The employment of STM-n/OC-m signals has the advantage of using the S1

GPS or GLONASS synchronization

Time & Phase

SyncE Slave Clock

Packet Based Clocks

Time & Phase needs

Primary Ref. Clock

PTP frequency profile

PTP phase profile

Timing distribution through packet based networks.

Professional Telecom Solutions

Networking & Telecoms - S y n c h r o n i z a t i o n & M o b i l e n e t w o r k s

G.8261 defines the Architecture and the wander limitations;

G.8264 describes the Ethernet Synch Messaging Channel (ESMC)

On many respects SyncE it is an evolution from SDH/SONET synchronization

Precision Time Protocol (PTP)

Central timing card

Central timing card

Synchronous Ethernet Architecture and comparison with conventional Ethernet.

Professional Telecom Solutions

Networking & Telecoms - S y n c h r o n i z a t i o n & M o b i l e n e t w o r k s

IPv4 or IPv6 Header

PTP over Ethernet

IP and Ethernet encapsulations for PTP messages.

TIMING REQUIREMENTS OF MOBILE NETWORKS

Professional Telecom Solutions

Networking & Telecoms - S y n c h r o n i z a t i o n & M o b i l e n e t w o r k s

(t2 - t1) - (t4 - t3)

(t2 - t1) + (t4 - t3)