You are on page 1of 24

3GTPL - Synchronisation

Nokia Siemens Networks

RU20 for Network Planners 2009

RAN1254 Timing Over Packet (TOP)

Nokia Siemens Networks

RU20 for Network Planners 2009

RAN1254 Timing over Packet Feature


Timing over Packet (ToP) provides the means to provide a
synchronization reference for base stations in Ethernet/packet transport networks
No need for separate TDM links for providing a synchronization
reference for base stations No need for GPS based synchronization sources at the base station sites Applicable for Iub/IP and packet-based backhaul with Pseudowire

The Master Clock is implemented as a dedicated network

element at the RNC site. Slave Clocks are integrated into the Ethernet interface units of the base stations ToP solution is based on the use of IEEE 1588 v2 protocol
This protocol is also called Precision Time Protocol (PTP).

Nokia Siemens Networks

RU20 for Network Planners 2009

ToP Solution Overview

At the RNC site there is a Master Clock The Master Clock has a timing reference traceable to a Primary

Reference Clock (PRC) ToP can be used as synchronization alternative in packet networks having no other possibility to synchronize the base station. RNC can not be synchronised with ToP

Nokia Siemens Networks

RU20 for Network Planners 2009

Timing over Packet Operating Principle

The Master Clock sends Sync messages to the Slave Clocks The Slave Clocks recovers the synchronization reference by
using the Sync messages received from the Master Clock The Master and Slave Clocks communicate by using IEEE 1588 v2 protocol Used is communication mode is unicast
Unicast discovery (preconfiguration of slave clocks with the
address of the master clock) and unicast negotiation are supported

Sync messages and signaling messages are supported


Sync messages are time stamped event messages Signaling messages are used for unicast negotiation signaling messages are not time stamped

Nokia Siemens Networks

RU20 for Network Planners 2009

ToP Messages
There are three types of Messages supported by NodeB: Announce Announce and Signaling messages are not time stamped, general

messages. Announce messages are needed for maintaining thesynchronization hierarchy. A slave clock tries to lock to a master only if it receives Announce messages from the master.

Signalling
Signaling messages are used for unicast negotiation.

Sync
Sync messages are time stamped event messages. A slave
clockrecovers the timing reference based on the Sync messages sent by the master clock.

With the unicast options of IEEE 1588 v2, all slave clocks arepreconfigured
with the address of the master clock. By using unicast negotiation, a slave requests the master to send Announce or Sync messages. As a response, the master sends a grant in a signaling message, and after grant it starts to send Announce or Sync messages.
Nokia Siemens Networks RU20 for Network Planners 2009

ToP QoS Requirements Low network Utilisation


Low network utilization (< 50%)
it is possible to introduce ToP without any additional measures in networks
with less than 50% bandwidth utilization even as BE traffic. This Requires

Maximum 50% link loading in the network No frame loss Maximum queue length 10 frames (preferably 3 frames)

Nokia Siemens Networks

RU20 for Network Planners 2009

ToP QoS Requirements High network Utilisation


High network utilization (< 90-95%)
If the network utilization is larger than 50% it is necessary to use Classes of
Services (CoS) in the network to ensure proper Quality of Service (QoS) for the ToP packets.

The load on the CoS containing the ToP traffic needs to be lower
than the whole network utilization

The high load scenario is discused further in the slides below


in terms of

Priorisation Classification Policing Queuing Scheduling and shaping

Nokia Siemens Networks

RU20 for Network Planners 2009

ToP in High load network Classification


The classification function at the ingress of each network

element identifies the received packet or frame and assign it to the correct flow and the corresponding CoS for the further handling in the network element. The ToP packets or frames are identified
UDP port plus the DSCP value VLAN ID plus the user_priority Note that the TP 5000 supports only 16 VLANS so a pure layer 2 solution for Iub with VLANs needs a router for ToP master for creating the VLANs.

Nokia Siemens Networks

RU20 for Network Planners 2009

ToP in High load network Policing and Bandwidth Assignment


Bandwidth has to be reserved for each connection with QoS
guarantees in a network supporting QoS better than just BE. The bandwidth needed per ToP connections between Master and Slave with 16 synch messages per second:
Direction from Master to Slave: On IP level: 9.3 kbps per connection On Ethernet level : 12.1 kbps per connection Direction from Slave to Master: On IP level: 0.005 kbps per connection On Ethernet level : 0.006 kbps per connection

Bandwidth can be reserved by CAC or by manual

configuration depending on the network. Policing functions at networks boundaries may be necessary

10

Nokia Siemens Networks

RU20 for Network Planners 2009

ToP in High load network Queuing


The support of ToP requires that the network is designed in such a way
that for ToP frames queues are only needed for rate adaptation between ingress and egress. Only short queues of less than 100 frames are needed for this purpose in the ideal case it should be even less than 10 frames. Queues for handling of traffic bursts and congestion requiring longer queue length should be avoided for ToP flows. . A frame loss of < 2% is acceptable for ToP. Queues for ToP flows should be short even with the risk of slightly higher frame losses. Tail Discard, RED or WRED do not make a difference to ToP Sophisticated drop mechanism can lead to lower network load benefiting also ToP messages.

11

Nokia Siemens Networks

RU20 for Network Planners 2009

Scheduling and shaping


Scheduling mechanisms
ToP or voice are sensitive to delay and jitter but these connections
typically have low bandwidth requirements compared to other services. These services should be served with highest strict user priority. WRR or WFQ may suit the other traffic in the interface better so an optimal scheduler is a combination of WRR/WFQ and Strict Priority.

Shaping
ToP load is relatively constant and quite low Shaping is not necessary as compared to e.g. TCP/IP data traffic Shapers introduce additional delay and also under some
circumstances additional jitter and this is harmful for ToP messages.

12

Nokia Siemens Networks

RU20 for Network Planners 2009

AXC & FTM

Timing over Packet Parameters


AXC C5.0 FTM C5.0

13

Nokia Siemens Networks

RU20 for Network Planners 2009

ToP Parameters

FTM

Check this box to activate ToP (License needed)

Timing over Packet the only choice if there is only Ethernet interface activated

18

Nokia Siemens Networks

RU20 for Network Planners 2009

ToP: DSCP and PHB

FTM

DSCP and PHB for ToP DSCP - 46 and PHB - EF recommended

19

Nokia Siemens Networks

RU20 for Network Planners 2009

Activating ToP

FTM

In the rare case that the ToP Master is in a different network than the Transport interface, it is necessary to configure routes under BTS Routing, not under BTS Routing.

20

Nokia Siemens Networks

RU20 for Network Planners 2009

Master clock options (aligned with RU10)


Option 1: dedicated master / slave

Symmetricom TimeProvider 5000 New product based on NSN requirements for mobile backhaul Cost efficient solution for RNC sites and hub sites Dual power supply, dual I/O card, 1:1 node redundancy

Option 2: upgrade of existing SSU



Symmetricom SSU2000, large installed base Can be upgraded with an IEEE1588v2 blade Fully redundant node with various I/O options

21

Nokia Siemens Networks

RU20 for Network Planners 2009

Master clock options (aligned with RU10)


Release 1.0
IEEE 1588v2 GM GPS and/or E1 Inputs 10MHz/1pps Outputs
The RNC supports 2.048 MHz, 2.048
Mbit/s and 1.544 MHz external synchronization interfaces

VLAN Support (up to 16 VLANs) SNMP and CLI Management One IOC interface module 2 x 100/1000Base-T SFPs More than 10 000 Timing packets per second
Rel 1.1 will have optional IOC slot
giving two additional Ethernet ports

Supports VLAN p-bits and DSCP


marking

22

Nokia Siemens Networks

RU20 for Network Planners 2009

RAN1708 BTS Synchronous Ethernet

23

Nokia Siemens Networks

RU20 for Network Planners 2009

BTS Synchronous Ethernet

quality synchronization reference for base stations - the quality is comparable to that of SDH

The main advantage of Synchronous Ethernet is that it can provide a high

Contrary to packet based synchronization techniques (e.g. ToP) the

stability of the recovered frequency does not depend on network load or network impairments like delay variation

24

Nokia Siemens Networks

RU20 for Network Planners 2009

BTS Synchronous Ethernet

BTS Synchronous Ethernet (SyncE) provides a mechanism for timing


synchronization over Ethernet of Flexi/Ultra BTS with Primary Reference Clock according to ITU G.8261spec

The Ethernet transport interface of a BTS shall be SyncE capable SyncE as specified in RAN1708 is considered as an alternative to Timing
over Packet (ToP) BTS synchronization, as specified in RAN1254

25

Nokia Siemens Networks

RU20 for Network Planners 2009

BTS Synchronous Ethernet


Impact to UTRAN Transport dimensioning:

IP-based Iub dimensioning requires a selection of the


synchronization type: SyncE, ToP, none.

SyncE contributes with an additional capacity on IP-based Iub at


the BTS side (Iub last mile), due to SSM message flow terminated at BTS. Bandwidth requirement of the SSM flow is around 6.4 kbps. Note: this is specified only in the Ethernet layer, and not in the IP layer.

26

Nokia Siemens Networks

RU20 for Network Planners 2009

BTS Synchronous Ethernet


The basic principle of Synchronous Ethernet (SyncE) is that at transmitting side Ethernet physical layer signal is timed by using a network reference

At receiving side the clock signal is recovered from the physical layer signal, in this way SyncE is capable of carrying network synchronization reference from one network element to another
27 Nokia Siemens Networks RU20 for Network Planners 2009

BTS Synchronous Ethernet


Interdependencies between features: BTS Synchronous Ethernet can only be used for IP enabled Flexi or UltraSite WCDMA BTS. One of the following features is a prerequisite: RAN74: IP based Iub for Flexi WCDMA BTS RAN1634: IP based Iub for UltraSite WCDMA BTS RAN1142: ATM over Ethernet (only with Flexi WCDMA BTS) RAN1449: Dual Iub for Flexi WCDMA BTS RAN1633: Dual Iub for UltraSite WCDMA BTS System Impact: Iub requires 1Gb SyncE capable interface card 2 Alarms SSM* mismatch; SSM missing 2 Parameters SSM enbling flag; SSM message timeout
*) - Synchronization Status Message
28 Nokia Siemens Networks RU20 for Network Planners 2009

You might also like