LTE Network

Synchronisation
Timing a Connected World

Designed  by  Creativeart  -­‐ Freepik.com 18  Nov  2016

LTE Synchronization Challenge
◼LTE Sync requirements depend on
the service delivery & media:
◼LTE technology (LTE-FDD, LTE-TDD,
LTE-Advanced) requires
synchronization

◼Sync method & technology depend

on
! Type of mobile network equipment
deployed
! Cell site location
! Architecture
! Media

2
The LTE Synchronization Solution
One solution does not fit every network

◼Small cells have different synchronization

requirements depending on environment
where they will be deployed
◼LTE TDD has frequency and phase
requirements where phase is very
stringent.
◼eICIC also has a very stringent phase
sync requirement.
◼CoMP sync must be ±1.5µs (phase) and
within 1-10ms (latency) for edge
scheduling purposes.

3
LTE Synchronization Requirements
LTE  (FDD) ±50  ppb N/A ±16ppb   (G.8261.1)
±1.5µs  (< 3km  radius) ±16ppb (G.8261.1)
LTE  (TDD) ±50  ppb
±5µs  (>  3km radius) ±1.1μs (G.8271.1)
LTE-­A  MBSFN ±50  ppb  
LTE-­A CoMP   ±0.5  to  5µs
±50  ppb   ±16ppb (G.8261.1)
Network  MIMO implementation  
±1.1μs (G.8271.1)
LTE-­A eICIC   dependent
±50  ppb  
HetNet  Coordination
N/A  (FDD)
±33ppb
Small  Cells ±100  ppb   ±1.5µs  (TDD)
±1.1μs (G.8271.1)
±0.5  to  5µs   (eICIC)

N/A  (FDD) ±100ppb

Home  Cells ±250  ppb  
±1.5µs  (TDD) ±1.1μs (G.8271.1)

µs  phase  and  latency  timing  requirements  encourage  GM  clock  deployment  very  close  to  
base  stations  (small  cells,  macro  cells,  DAS  controllers)  to  reduce  the  risk  of  network  
impairments  affecting  service  quality 4
Why is Synchronization Required?
Why    Compliance   Impact  of
Application
is  needed Non-­‐compliance
Call  Interference  
LTE  -­‐FDD Call  Initiation dropped  calls  due to  
handover  interruption

EnodeB phase  &  time  slot   Packet loss/retransmission

LTE  -­‐TDD alignment Spectral  efficiency

Proper time alignment  

Video broadcast  
LTE-­‐A  MBSFN   of video  signal  decoding    
interruption  
from  multiple  BTSs

Coordination  of    signals

Service  affecting  bandwidth  
LTE-­‐A  MIMO/COMP to/from  multiple  
degradation,  LBS  accuracy
base  stations

Call  drops  among small  cells  

LTE-­‐A  eICIC Interference  coordination and  between  small  cells  and  
Macros

Inter  Cell  Interference  Coordination  is  extremely  difficult  to  implement.    Deploying  a  local  GM  to  assure  adequate  precision  
for  small  cells  is  one  of  the  most  important  factors  service  providers  must  implement  to  assure  QoS.
5
Guidelines
1. Use an independent source for sync
Best in class solutions
Standards Compliance. Efficient operation in a multi-vendor network

2. Protect sync for service assurance

Multi frequency, multi constellation GNSS, redundancy
High performance holdover

3. Deploy PTP GM close to cells where needed for accuracy

High PDV and network asymmetry: requires deployment “at or near the edge”

6
Coordinated Multi Point (CoMP)
Coordination  Area
• Data  is  transmitted  to  the  UE  simultaneously  from  a  number  of  
different  eNBs using  the  same  frequency.  
• By  coordinating  between  the  different  eNBs it  is  possible  to  form  
a  virtual  antenna  array  so  the  UE  perceives  all  signals  as  if  they  
were  one  signal.
• To  achieve  CoMP joint  transmission,  the  signals  from  all  
coordinated  eNBs must  be  frequency  &  phase  aligned.
• The  aim  is  to  improve  the  received  signal  quality  and  strength  at  
the  UE.    
• CoMP has  shown  that  power  savings  at  the  UE  can  be  up  to  80%
Backhaul

• CoMP places    high  demand  onto  the  backhaul  network  because  the  data  to  be  transmitted  to  the  UE  needs  to  be  
sent  to  each  eNB that  will  be  transmitting  to  the  UE.  This  may  easily  double  or  triple  the  amount  of  data  in  the  
network  depending  on  how  many  eNBs will  be  sending    data  to  each  UE.  

• This  technique  allows  for  signals  that  are  very  low  in  strength,  or  masked  by  interference  in  some  areas  to  be  
received  with  improved  quality  and  few  errors.
Sync essential for eICIC Cell  edge  Tx
**  Is  defined  in  release  10  if  the  3GPP  LTE  specification
Almost  Blank  
Subframes (ABS)
Interference Radio  Frame  (10  subframes)
High  Tx only   f
macro  cell   Low  Tx only  
communication small  cell  
communication

t
f

t
Subframe

◼ Used with small cells inside macro cell coverage area. Macro cells emit long range high power signals, small cells only emit a low power signal over
short distances.
◼ Coordinates the blanking of subframes or ABS (Almost Blank Subframes) in the time domain in the macro cell.
◼ Coordination assures there is no interference in those subframes from the macro cell, thus data transmission is much faster.
◼ Small cell usage in the coverage area of a macro cell increases overall system capacity as each small cell can use the empty subframes without
interference from the other cells.
◼ Downside is that the macro cell capacity is diminished as it can't use all subframes.
◼ Methods exist to dynamically increase or decrease the number of subframes that are assigned for exclusive use of small cells when traffic patterns
change.
◼ Frequency and Phase (Time) synchronization are critical to ensure eICIC works at optimal levels.
Sync is essential for MBMS
◼Multimedia Broadcast Multicast services - also known as MBSFN
(Multimedia Broadcast Single Frequency Network)
◼Multiple eNBs broadcast the same data to all UE in a coverage area at
the same time on the same frequency. BM-­‐SC

◼MBSFN enables transmission of synchronized “real time” data so that the

same data is transmitted to all UEs at the same time.
◼Enables mobile operators to broadcast live events the same way a cable
TV operator or an over the air broadcaster would.

◼Both eNBs and UEs must support MBSFN.

◼UEs are able to be served by two or more eNBs to improve signal
reception / transmission and increase throughput, mobility and QoS.
◼Transmission of data from multiple eNBs must be received by UEs at the
same time.
◼MBMS can only be achieved by tight synchronization between the UEs
and the eNBs, and between the eNBs and the BM-SC (Broadcast
Multicast Service Center) in the network.
Carrier Aggregation
LTE Real  world  testing  shows  the  
significant  improvements  in  
throughput  when  CA  is  implemented  
in  an  LTE  network
20  MHz

LTE-­‐A  w  CA
20  MHz
20  MHz
20  MHz 100  
MHz
20  MHz
20  MHz

Source  4G  Americas

Types of carrier aggregation
◼ CA is divided into intra-band (contiguous and non-contiguous) and inter-band

• Aggregated  carriers  (component  

carriers)  can  be  adjacent  or  
nonadjacent  within  different   Frequency  
Band  A
Frequency  
Band  B

frequency  bands Intra  Band  

Contiguous
• Non  contiguous  CA  is  a  more  
flexible  solution  given  that  most  
operators  do  not  have  spectrum  
that  is  necessarily  contiguous. Intra  Band  
Non  

• CC  frequencies  must  have  guard   Contiguous

bands  of  ~  300kHz  or  multiples  

thereof  to  ensure  no  interference   Inter  
Band  
due  to  frequency  proximity  or  
overlap.  

Guard  bands
Network Scenarios
Frequency Synchronization
G.8265.1 Basic Architecture
Managed  Ethernet  backhaul
consistent,  known  performance,  low  packet  delay  variation
CORE AGG ACCESS

Macro  eNodeB

Small  Cell
Aggregation
Metro  Small  Cells

• Central  deployment  of  PTP  grandmaster

• Requires  engineering  and  monitoring  to  assure  performance
• Suitable  for  FDD  environments 13
Frequency Synchronization
G.8265.1 Edge Architecture
Multiple  technologies,  many  hops/paths,  3rd party  access  vendors.    Network  
impairments  can  be  eliminated  by  deploying  GM  close  or  at  the  base  station  location

CORE AGG ACCESS

High  PDV  /  3rd Party

Microwave Macro  eNodeB

PON
OLT ONU

DSL modem
DSLAM

Small  Cells

14
Phase Synchronization
G.8275.1 Full On-Path Support
Managed  Ethernet,  SyncE,  boundary  clocks  
CORE AGG ACCESS

BC Router  w  BC
BC BC BC BC

Macro  BS

BC

BC BC Cell  site
BC Router  w  BC
Aggregation Small  Cells

• Rebuild  to  include  boundary  clocks  in  every  network  element

• Possible    MPLS  network  re-­‐design
• Presents  enormous  challenges  for  networks  with  legacy  devices 15
Cost Effective Alternative Architecture
◼No change out for network hardware ◼Complements existing investment made in
GPS at eNodeB sites
◼Can run time/phase services over existing
MPLS / CE network ◼Leverages any existing PTP deployments for
! Preserves MPLS architecture FDD architectures
◼No change to existing engineering and ◼Deploy highest quality PTP client
operations processes ◼Compliant to all existing FDD and TDD
! Removes BC engineering standards
◼Eliminates asymmetry issue ! Uses legacy and current generation standards

◼Stand alone sync not dependent on embedded ◼Simple and easy to deploy for all LTE
NE architectures

GM  “at  the  edge”  for  phase

eNodeB
Phase Synchronization
G.8275.2 Partial On-Path Support or Edge GM
Existing  backhaul,  diverse  tech  and/or  noisy  multiple  technologies,  many  hops/paths,  
high  PDV,  3rd party  transport

CORE AGG ACCESS

GM  w  BC

Macro  eNodeB

Cell  site  agg

High  PDV  /  3rd Party
Small  Cells

• Provide  partial  on-­‐path  support  with  advanced  boundary  clock  (not  recommended)
• Deploy  PTP  grandmaster  “at  or  near  the  edge”  with  PTP  backup  to  GM  
further  back  in  the  network 17
Residential and Enterprise Indoor Small Cells
Wireline  network  backhaul    DSL,  PON,  Cable,  Metro  Ethernet
AGG WIRELINE  ACCESS  NETWORK

PON
OLT ONU
PTP

DSL
DSLAM modem

Cable
CMTS modem NTP  
NTP  

Synchronization  Distribution  Architecture

• Sync  equipment  and  deployment
– 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  “GPS  assist” 18
Summary
◼LTE technologies drive new requirements for synchronization
◼Backhaul network technologies, topology and performance drive
synchronization equipment and deployment decisions
◼Emerging boundary clock-based solutions will work for some scenarios but
not recommended – costly and complex
◼GNSS redundancy a good strategy
◼Architecture that places a PTP master “at or near the edge” is the best
solution for most network scenarios

19