WCDMA

Synchronization
simplified
introduction

• General
This document describes the different synchronization functions within the
WCDMA Radio Access Network (RAN), providing a general overview of
Network Synchronization, Node Synchronization, Frame Synchronization, and
Radio Interface Synchronization.

The purpose of the synchronization functions is to provide timing of user

data and control signaling within the WCDMA RAN. A well functioning
synchronization is essential for the performance of the WCDMA RAN.
› RAN Overview
The WCDMA RAN is the radio access network providing the connection
between the Core Network (CN) and the User Equipment (UE). The WCDMA
RAN can be divided into two parts:
• The Transport Network Layer (TNL), which enables communication
between the different network elements in the WCDMA RAN and between
the WCDMA RAN and the CN.
• The Radio Network Layer (RNL), which is the interface between the
WCDMA RAN and the UE.
• Synchronization Functions
There are four different synchronization functions in the WCDMA RAN:
• Network Synchronization
• Node Synchronization
• Frame Synchronization
• Radio Interface Synchronization
› Dependence Among Synchronization Functions
Network Synchronization is responsible for the distribution of clocks, and allows the clocks to operate at the
same frequency in different nodes. Note that clock in this context does not deal with the time of day, but with
frequency only.

Node Synchronization is the basis for the numbering of frames between the RNC and RBS nodes, and for frame
timing. The correct operation of Node Synchronization is dependent on the proper operation of Network
Synchronization.

Frame Synchronization is responsible for the numbering of user frames, and for the transmission and reception
of frames to and from the RNC node at the correct times, to compensate for transfer and processing delay in the
RNC-RBS path. The correct operation of Frame Synchronization in the Intra-RNS case is dependent on the proper
operation of the Node Synchronization.

Radio Interface Synchronization is responsible for the alignment of radio frames between the RBS and the UE.
› Network Synchronization
The synchronization network provides timing reference signals to
telecommunications traffic networks. The objective of the traffic networks is to
transport information without impairments and distortion. Poor synchronization
often leads to loss of information. A properly planned and implemented
synchronization network is a necessary condition for the proper functioning of a
transport network. In WCDMA RAN the RBS radio frequencies are generated
from the network clocks.

Poor synchronization causes loss of information in varying degrees. It can

result in the following:
• Inhibition of call setup due to retransmission
• Dropping of calls at soft handover due to sliding Frame Synchronization
windows
• Degraded speech quality
• Freeze-frames on video
• Radio carriers out of range interferes with neighboring cells
› Network Synchronization in WCDMA RAN
Network Synchronization deals with the stability of the clocks (oscillators) in the
WCDMA RAN and the requirements of the Iub and Iu interfaces.
The purpose of Network Synchronization is to synchronize the RNC, RXI, and
RBS network elements in the WCDMA RAN, either to the transport network or
to an external high-stability timing reference that is not framed, and to distribute
synchronization references in a master-slave approach within the WCDMA
RAN.
• The RNC, RXI, and RBS nodes need to synchronize the frequency of their
• internal Timing Units (TUs) to a common and traceable clock reference. The
• RBS, RXI, and RNC all have stable clocks, which besides synchronizing internal
• functions, also generate synchronization to the outgoing PDH/SDH/SONET
• links and to the radio interface. In case of Iub IP transport, the RXI and the RNC
• also generates time stamped IP packets, whose time stamps are traceable
• to the node clock.
• The Network Synchronization function offers several services including the
• following:
• • Selection of the synchronization reference
• • Generation of clocks, for example, the system clock
• • Holdover capability
• • Distribution of the system clock within the WCDMA RAN node
• Network Synchronization for ATM Connected RBSs
• For ATM over PDH/SDH/SONET, the Network Synchronization function supports the master-slave
synchronization method. The master clock is provided by a Primary Reference Clock (PRC) to which all the
nodes are slaved. The synchronization reference is transmitted through the transport
• network or through the dedicated synchronization network. Cascading is used especially for RBSs and RXIs to
save transmission link costs. In terms of network synchronization, it is possible to have the WCDMA RAN
nodes in cascade.

• Transport signals provided by a WCDMA RAN node are usable for network synchronization by other nodes.
When an SDH transport network is being used to synchronize the WCDMA RAN nodes, the effects from the
pointer justifications are included in the requirements for the traffic interfaces..

• In conclusion, a WCDMA RAN node can be synchronized directly from the Core Network using Iu interface as
the synchronization source, from another WCDMA RAN node, from the SDH transport nodes, or from some
dedicated source such as a GPS or a Stand Alone Synchronization Equipment (SASE).
• The timing reference must be traceable to a clock of G.811 quality. There is an absolute need for a dedicated
source (GPS or SASE) at RBS and RXI nodes in ring structures (of four or more nodes) using unprotected dark
fibers or microwave links to avoid out-of synchronization and timing loops in case of link failures. It is however
not supported to connect a GPS synchronization source directly into the RNC since the GPS port is reserved
for the Assisted GPS (A-GPS) feature.
• Network Synchronization for IP connected RBSs
• Network synchronization for an IP connected RBS is achieved by aligning the frequency of the RBS to the
frequency of an SNTP server with traceability to a G.811 source. The SNTP server is integrated into the RNC or
RXI, but a stand-alone SNTP server may also be used as long as it meets the required performance
characteristics. For availability reasons, at least two servers should be configured. The RBS implements the
synchronization client part.

• Network Synchronization over IP is supported in RBS nodes equipped with CBU or TUB2 hardware.
• Note: An ordinary SNTP server based on a commercial computer platform does not provide enough accuracy.
• If the Packet Delay Variation (PDV) for the NTP packets used for Synchronization over IP (SoIP) fulfils either of
the following three conditions the network synchronization will lock within 16 minutes:

• 1 The PDV for the 1% packets having the lowest delay is maximum 20 μs during 16 minutes periods.

• 2 The interface characteristics comply with the tolerance for IP synchronization references in G.8261

• 3 The PDV has an approximately time invariant Gaussian distribution, with PDV for 99% of the packets of
maximum 0.3 ms.
› Timing Unit
The TU is the central functional block in the synchronization implementation of the WRAN nodes.
The purpose of the TU is to select and regenerate a reference clock signal and to provide a number of low noise
output clock signals for Network, Node, and Frame Synchronization. The TU also handles the Node
Synchronization frame counter.

› The TU distributes synchronization signals to the circuit boards in the node, and receives synchronization
signals from ET boards or SoIP servers. It also has connections on the front for a dedicated synchronization
signal and for GPS.
› The TU holds two clock systems; the System Clock aimed for transport network synchronization, and the Radio
BB clock aimed for the Radio NW part.

› The TU is physically housed either on the TUB or a CBU. RNC and RXI uses the TUB. RBS hardware of WRAN
release up to P3 also uses the TUB, while RBS hardware from WRAN release P4 uses the CBU.
› System Clock
The system clock is defined as a stable clock that works as a slave clock locked to the synchronization reference.
The system clock is of type SDH Equipment slave clock (SEC) and fulfills the requirements for the quality G.813

The system clock generates an accurate and stable clock signal that is distributed within the WCDMA RAN node,
where it provides a clock reference signal to the transmission network interfaces and for the internal switching
and transport of data.
The system clock is locked to the selected synchronization reference and regains the frequency of the selected
active reference in conditions when the reference is fault free.

A fault free synchronization reference is when the jitter and wander characteristics of the reference are within
the limits of the specifications and there are no signal interruptions or phase discontinuity. If synchronization
reference is changed, the synchronization of the system clock to the original reference is lost, and the
synchronization to the new reference is performed.
› List of Working Modes and States
› The system clock can work in different states and also in different modes.

States:
› • Cold Start/Restart state
› • Warm Restart state (when the TU is restarted and the previous mode of the clock is either Locked or
Holdover mode)

› Modes:
› • Start-Up mode (warm-up, including the oscillator warm-up time)
› • Locked mode (normal working mode when the clock is locked to the
› reference)
› • Holdover mode (no reference available but there is stored data to control the outputs)
› • Free Running mode (no reference available)
› • Failure mode (when a hardware fault is detected)
› • Loss of Tracking mode (when the clock can not trace the reference)
• Radio BB Clock
• The Radio BB clock is a stable clock that is needed in the RBS node to maintain the +/- 50 ppb frequency
accuracy of the air interface. The Radio BB clock works as a slave clock locked to the synchronization
reference.
• The Radio BB clock handles the radio network part providing a reference for carrier frequency generation and
acting as timing reference for baseband processing in the RBS.
• For the CBU hardware, the Radio BB clock is frequency locked to the selected synchronization reference (PDH,
SDH/SONET, or SoIP server). In case of the TUB, the Radio BB clock is phase locked to the same reference as
the system clock. (PDH, SDH/SONET, or SoIP server)

• The Radio BB clock handles the following:

• • Synthesizing of an accurate and stable clock signal, acting as reference for the carrier frequency generation
• • Generation and distribution of a Frame Synchronization signal with a period of 10 ms and a 12 bit frame
counter value; the RFN and BFN counters.

• Working Modes and Accuracy

• The Radio BB clock can work in the following modes: The accuracy given for the Locked and Holdover modes
requires that the frequency accuracy of the source is better than +/- 16 ppb.
Mode Minimum Clock Accuracy

Warm-Up mode
Synchronizing mode 1
Synchronizing mode 2
Synchronizing mode 3
Locked mode ± 50 ppb
Holdover mode ± 50 ppb
Free Running mode ± 4.6 ppm
Failure mode
Loss of Tracking mode