Professional Documents
Culture Documents
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).
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
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
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
Maximum 50% link loading in the network No frame loss Maximum queue length 10 frames (preferably 3 frames)
The load on the CoS containing the ToP traffic needs to be lower
than the whole network utilization
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.
configuration depending on the network. Policing functions at networks boundaries may be necessary
10
11
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
13
ToP Parameters
FTM
Timing over Packet the only choice if there is only Ethernet interface activated
18
FTM
19
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
21
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
22
23
quality synchronization reference for base stations - the quality is comparable to that of SDH
stability of the recovered frequency does not depend on network load or network impairments like delay variation
24
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
26
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