Beruflich Dokumente
Kultur Dokumente
Introduction
Frequency Synchronization
Once a routine network function, timing TA=1/fA Leading edge of the pulses
and synchronization requirements are A t are at same pace, but not
changing rapidly as mobile network and at the identical moment.
backhaul technologies evolve. Carriers TB=1/fB
successfully solved the problem of B t
distributing frequency synchronization fA=fB
Page 1 of 9
WHITE PAPER
signals, and the synchronization equipment Application Frequency Network /Air Phase Note
then uses it as a reference for network
timing. The best timing and sync equipment GSM, UMTS, WCDMA, LTE –
16 ppb / 50 ppb -- --
FDD
will also use additional frequency inputs such
as Synchronous Ethernet or E1/T1 signals ± 3 µs to ± 10
CDMA2000 16 ppb / 50 ppb --
which enable the solution to converge more µs
quickly on the precise and accurate time, ± 1.5 µs ≤ 3 km cell radius
and improve holdover when the GNSS LTE – TDD 16 ppb / 50 ppb
± 5 µs > 3 km cell radius
signals are impaired or only available
LTE MBMS inter-cell time
intermittently. 16 ppb / 50 ppb ± 10 µs
difference
(LTE-FDD & LTE-TDD)
It is essential that the time and phase ± 1.5 µs to ± In discussion by
LTE- Advanced 16 ppb / 50 ppb
5 µs members of the 3GPP
reference in LTE-TDD and LTE-A networks
is traceable to Coordinated Universal Time .. Figure 3: Frequency and Phase Synchronization Requirements
(UTC). ITU-T G.8272 defines requirements .
for a Primary Reference Time Clock LTE-Advanced Type of Coordination Phase
(PRTC); a time and phase advancement
eICIC enhanced Inter-cell Interference Coordination ± 1.5 to ± 5µs
compared to the long established
standards for the Primary Reference CoMP Moderate to UL coordinated scheduling ± 5 µs
Clocks (PRC) and Primary Reference tight DL coordinated scheduling ± 5 µs
Sources (PRS) used for frequency DL coordinated beamforming ± 1.5 µs
synchronization. Without the common UTC
DL non-coherent joint transmission ± 5 µs
time reference cell sites cannot operate
as intended. It must be emphasized that CoMP Very tight UL joint processing ± 1.5 µs
SyncE is only a frequency reference, and UL selection combining ± 1.5 µs
cannot be used by a PTP clock (such
UL joint reception ± 1.5 µs
as a Boundary Clock) as a primary time ..
reference. .. Figure 4: LTE-Advanced Synchronization Requirements
LTE-Advanced requirements are a work-in- LTE -FDD Time slot alignment Packet loss/collisions and spectral inefficiency
progress in the standards bodies. Though
not consented at this time (mid-2013) it is LTE-A Proper time alignment of video Video broadcast interruption
MBSFN signal decoding from multiple BTSs
probable that the requirements will be ±1.5
µs or ±5 µs depending on the application; LTE-A MIMO/ Coordination of signals to/from Poor signal quality at edge of cells, LBS
though some of the discussion indicates COMP multiple base stations accuracy
that 500 nanoseconds (±.5 µs) may be LTE-A eICIC Interference coordination Spectral inefficiency and service
required for some service situations. LTE-A degradation
covers multiple techniques rather than a Needs and Impacts are cumulative, that is: “plus all of the above”.
single technology. Not all features will be ..
.. Figure 5: Why Synchronization is Important
deployed everywhere, leading to differences
Page 2 of 9
WHITE PAPER
GNSS Everywhere
A seemingly simple approach is to deploy
CORE AGGREGATION ACCESS
a GNSS receiver with every mobile base
station. The GNSS receiver can be a
standalone device or embedded into the
base station. A GNSS receiver can also
be integrated into a collocated or nearby
cell site router (CSR) or network interface
device (NID) if they also support sync
distribution to the base station, typically
using PTP. Though straight forward, this
approach is not economically or technically
feasible at every location, and it will also
leave the eNodeBs vulnerable to GNSS
signal interference.
..
.. Figure 6: GNSS for Every Base Station, Cell Site Router or NID
.
Page 3 of 9
WHITE PAPER
The IEEE 1588 Precision Time Protocol to support a given application. For support. Usually embedded in network
(PTP) was developed in response to example a profile may specify layer elements, Boundary Clocks function as
broad industry and government need to 2 or layer 3, unicast or multicast, the a PTP client in the upstream direction
enable accurate distribution of time and message exchange rate, and whether and as a grandmaster to other Boundary
frequency over packet-based networks. on-path support is required. The Clocks and clients in the downstream
“Telecom Profile” (recommendation direction. By compensating for delays
IEEE 1588 employs a client/server ITU-T G.8265.1) is intended to address in the switch and refreshing the PTP
architecture to maintain precise the application of PTP to the frequency packets, Boundary Clocks help to
synchronization across all network synchronization of telecommunication maintain accuracy and are still traceable
components. The server (PTP systems, primarily cellular base stations. to the original Grandmaster clock with a
Grandmaster Clock) is the primary ITU-T G.8275.1 and G.8275.2 are primary UTC reference.
reference source for all of the PTP works-in-progress to address time and
clients within its network domain. It phase synchronization. IEEE 1588 also defines Transparent
continuously sends out sync, follow-up Clocks as a technique to support
and delay response messages to all of The PTP standard includes provisions accuracy across a network. Transparent
its clients. Clients continuously send to maintain accuracy across a network Clocks are not currently provided for in
delay request messages to the server (refer also to the sidebar Packet Delay the PTP profiles for telecom industry,
to maintain synchronization through the Variation and Asymmetry). Boundary and need not be covered here.
packet-based network. Using the time Clocks are one option for this on-path
stamped packets, clients determine
frequency and calculate accurate
time that is traceable to the primary Server Client
IEEE 1588 processor Master Network Slave IEEE 1588 processor
reference of the Grandmaster.
t1 Sync
Network protocol Network protocol
The IEEE standard is designed broadly stack & OS t2 stack & OS
follow_up
to serve a great variety of applications.
To enable ease of deployment and Sync detector & t3 Sync detector &
timestamp generator timestamp generator
equipment interoperability while t4
delay_req.
meeting the requirements of specific Physical layer Physical layer
applications, IEEE 1588-2008 delay_resp.
Page 4 of 9
WHITE PAPER
PTP GM ~
BC BC BC BC BC
BC
Rb
SyncE SyncE SyncE SyncE SyncE
SyncE
Macro eNodeB
BC BC BC BC BC ~
BC
SyncE
SyncE
SyncE SyncE SyncE SyncE
~
~ ~
Small Cell
Aggregation
Metro Small Cells
PTP GM
..
. Figure 7: Backhaul network using the ITU-T G.8275.1 profile for phase synchronization
Page 5 of 9
WHITE PAPER
Timing and synchronization, load which can be highly asymmetric in Time accuracy is affected by both
fundamental in all mobile networks, is nature. As the amount of traffic in the the magnitude of the packet delay
even more critical as small cells are network increases, the delay variation variation and how effective the client is
added and networks evolve to LTE- is also likely to increase. Asymmetry is at removing this noise. Synchronization
TDD and LTE-A technologies. Backhaul also introduced by the physical topology elements deployed in the network vary
network performance can dramatically of the network as packets travel different in how effectively they filter this noise.
impact PTP timing accuracy, and and changing paths in the upstream and Embedded Boundary Clocks adjust only
thereby the mobile network itself— downstream directions. for the switch delay variation in its host
affecting service quality and customer switch; it cannot adjust for variations or
satisfaction. asymmetries in other network switches
and it cannot compensate at all for
The problem is Packet Delay Variation Sources of Asymmetry network path asymmetry. Network timing
(PDV) which represents the change 1. Switch delay variation: elements with a GNSS reference can
in latency from packet to packet. - Switch transit: packet processing, compensate for all variations, including
Packet delay itself has no effect on the buffering and queuing network path asymmetry.
accuracy of the clock: constant delay
- Payload variation increases
would allow an accurate time offset Comparing a PTP input from a
variation in switch delay
calculation by the PTP client. Variable centralized grandmaster and a local
delay, however, induces noise in the 2. Network path variation: GNSS reference; an Edge Grandmaster
PTP client’s perception of the time at - Variation between upstream and can determine the typical offset and
the master which can result in variation downstream paths in the network apply it to provide superior accuracy
in time calculations based on the - Path asymmetry alone can when the GNSS reference is not
timestamps in the PTP packets. cause timing performance to be available. Superior designs learn
out of spec. multiple offset for different backhaul
Delay can vary as PTP packets are network paths and continue to provide
- An out-of-phase cell can impact
processed, buffered and queued along accurate performance even through
services on overlapping cells
with the payload traffic through the backhaul network rearrangements.
network switches and routers, and
it tends to be correlated to network
Page 6 of 9
WHITE PAPER
PTP Profile with Partial On-path In simple terms, this approach endorses Edge Grandmasters ensure accuracy
Support and/or Edge Grandmaster two solutions that can be employed by deploying closer to the clients, and
(G.8275.2) separately or in combination to provide thereby reducing the hops and putting
the best synchronization architecture for a problem parts of the backhaul network
Responding to the need for a phase
wide range of network scenarios. behind them. Edge Grandmasters include
timing solution that is more feasible in
a GNSS reference to meet G.8272 PRTC
non-Greenfield, real-world scenarios, “Partial on-path support” is deployment of requirements and perform much the like
another PTP profile (G.8275.2) has been advanced boundary clocks at intermittent centralized PTP Grandmaster equipment
proposed to the ATIS/ITU standards locations through the network. In a commonly deployed today, except they are
bodies: “a new profile to support time and managed Ethernet network it may be scaled and cost optimized for deployment
phase distribution over existing deployed possible to locate an advanced boundary closer to the network edge.
networks…compatible with the PTP clock at selected locations and maintain
profile for frequency distribution defined timing within spec at the base stations. Figure 8 depicts some of the many network
in G.8265.1”. This proposal will require Key to this approach is to limit the number scenarios that can be solved with partial
considerable more work before it becomes of hops and path asymmetry between the on-path support and/or Edge Grandmaster
a standard, but in practice, it can be grandmaster and the client. Advanced deployment.
deployed in networks today. boundary clocks have superior oscillators
and can leverage additional inputs such as
SyncE and E1/T1 circuits as a frequency
reference to maintain high accuracy
timestamps to the next clients in the path.
Boundary Clock ~
~
PTP GM
Macro eNodeB
PON
OLT ONU
Edge GM ~
DSL
DSLAM modem
~
~ ~
Microwave
Edge GM
Boundary Clock ~
PTP GM
~
~ ~
Page 7 of 9
WHITE PAPER
Rb ..
.. Figure 10: Edge Grandmasters provide backup to each other.
Edge GM or BC Timing and synchronization are a critical this architecture, is that relatively nearby
with rubidium oscilla-
tor component to LTE-TDD and LTE-Advanced Edge Grandmasters can backup each other
network operations, and therefore protecting (shown in figure 10), as opposed to requiring
this function is more essential than ever. PTP clients to re-sync with a centralized
Enhanced holdover is one protection grandmaster that may be so many hops
alternative. Another alternative, enabled by away that accurate timing is not possible.
Page 8 of 9
WHITE PAPER
Edge Grandmaster and/or partial on-path Conclusion: Finding the Right Solution Full on-path support is most feasible in
support with advanced Boundary Clocks for Your Network Greenfield situations where every new
provide many advantages: The important and difficult question: switch and router can include SyncE and
“How should I synchronize my LTE-TDD Boundary Clock support. Network path
• Tremendous flexibility to work in diverse and LTE-Advanced networks?” does not asymmetry and sync protection remain
network scenarios provides network have a single easy answer. The stringent as issues.
planners with the tools for every situation requirements for phase and time cannot
Edge Grandmasters deployments or
• Enables small cell deployments where be met using the typical “frequency
advance Boundary Clock offer the flexibility
GNSS/GPS is not economically or synchronization distributed over the
to fit a wide range of network scenarios
technically feasible backhaul network” techniques in
and offer solutions for sync protection and
practice today, and so new solutions must
• Cost savings by avoiding backhaul can compensate for all switch and path
be adopted.
network upgrades for embedded asymmetry.
Boundary Clocks (and possibly also The right answer for your network is
upgrade for SyncE) driven by your service delivery network Microsemi® is a leader in PTP
• Avoids issues related to high packet fundamentals: Grandmaster deployments for mobile
delay variation, asymmetry and/or 3rd networks and stands ready to help analyze
• The mobile network technology and
party backhaul and recommend the right solution for your
services determines the timing and
• Timing and synchronization protection operation. Additional technical information,
synchronization requirements: LTE-
techniques to maintain high mobile test results, recommended best practices,
TDD, LTE-A, eICIC requirements, CoMP
network availability and performance cost comparison aid, equipment
requirements, etc.
demonstration, lab test procedures
• Synchronization reliability is not • Mobile network equipment selection and and network sync audit aids can all be
threatened by failure of one of many cell site locations (particularly for small made available to help plan the best
embedded Boundary Clock (where cells) define what can and cannot be synchronization distribution architecture for
failure of one BC breaks the timing chain done. your network. And, of course, Microsemi
to the downstream clocks) supplies and supports best-in-class PTP
• Backhaul network technologies,
• Makes extended holdover possible as topologies, performance and control Grandmaster, Edge Grandmaster, and
cost of a superior rubidium oscillator is drive decisions for synchronization advanced Boundary Clock equipment, to
leveraged across multiple base stations equipment and deployment locations. network operators around the world.
• Leverages existing investment in Once the technical limits and possibilities
centralized PTP grandmaster and are understood, the solution alternatives
SyncE, preserves practices put in place and their relative costs can be assessed.
for frequency synchronization
Simply deploying GNSS receivers and
• Preserves MPLS network and
antennas everywhere is not economically
engineering practices (operates at layer 3)
or technically feasible for all situations, and
GNSS alone exposes the base stations
to the vulnerabilities of the satellite signal
based systems. Network distributed time,
using the IEEE 1588 Precision Time
Protocol, will be part of virtually every
mobile network operator’s network.
Microsemi Corporation (Nasdaq: MSCC) offers a comprehensive portfolio of semiconductor and system solutions for communications, defense &
security, aerospace and industrial markets. Products include high-performance and radiation-hardened analog mixed-signal integrated circuits,
Symmetricom Microsemi Corporate Headquarters FPGAs, SoCs and ASICs; power management products; timing and synchronization devices and precise time solutions, setting the world’s
is Now One Enterprise, Aliso Viejo, CA 92656 USA standard for time; voice processing devices; RF solutions; discrete components; security technologies and scalable anti-tamper products;
Tel: 408.433.0910 Power-over-Ethernet ICs and midspans; as well as custom design capabilities and services. Microsemi is headquartered in Aliso Viejo, Calif., and
Fax: 408.428.7896 has approximately 3,000 employees globally. Learn more at www.microsemi.com<http://www.microsemi.com>
www.symmetricom.com
www.microsemi.com
©2014 Microsemi Corporation. All rights reserved. Microsemi and the Microsemi logo are trademarks of Microsemi Corporation. All other
E-mail: Sales.Support@Microsemi.com trademarks and service marks are the property of their respective owners.
WP_TIMESYNCLTE_020714