Professional Documents
Culture Documents
V300R003C10
Product Description
Issue 01
Date 2014-06-30
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Product Version
Table 1 Version requirements of U2000 and Synlock V3
Product Name Product Version
Intended Audience
This document describes the positioning, characteristics, system architecture, functions,
configurations, applications, device management, technical specifications, and standards
compliance of the SYNLOCK V3.
This document is intended for:
Network planning engineers
Hardware installation engineers
Installation and commissioning engineers
Field maintenance engineers
Data configuration engineers
System maintenance engineers
Application developers
Symbol Conventions
Symbols used in this document are described in the following table.
Symbol Description
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes in earlier issues.
From V300R003C00, functions that used to be provided by the CCOU board are
provided by the TSOU board.
Subracks of V300R003C00 still support TSOU and CCOU boards of historical versions.
Contents
2 Product Architecture.....................................................................................................................4
2.1 Hardware Architecture....................................................................................................................................................4
2.1.1 Appearance and Structure............................................................................................................................................4
2.1.2 Working Principle........................................................................................................................................................5
2.1.3 Power Distribution Principle.......................................................................................................................................6
2.1.4 Ventilation Principle....................................................................................................................................................6
2.1.5 Grounding....................................................................................................................................................................7
2.2 Software Architecture.....................................................................................................................................................7
3 Product Functions..........................................................................................................................9
3.1 Frequency Synchronization............................................................................................................................................9
3.2 Time Synchronization...................................................................................................................................................10
3.3 Board Functions............................................................................................................................................................11
3.3.1 LCIM Board..............................................................................................................................................................11
3.3.2 SRCU/SOCU Board..................................................................................................................................................13
3.3.3 TSOU Board..............................................................................................................................................................16
3.3.4 MITU Board..............................................................................................................................................................16
3.3.5 TODI Board...............................................................................................................................................................18
3.3.6 TDRV Board..............................................................................................................................................................18
3.3.7 PNSU Board..............................................................................................................................................................18
3.3.8 TODU Board.............................................................................................................................................................18
3.4 Characteristics..............................................................................................................................................................19
3.4.1 Compact Structure and Flexible Configuration.........................................................................................................19
5 Device Management...................................................................................................................35
5.1 Overview......................................................................................................................................................................35
5.2 Centralized Maintenance Terminal Mode....................................................................................................................36
5.2.1 Running Environment...............................................................................................................................................36
5.2.2 Management Functions.............................................................................................................................................37
5.2.3 Typical Networking...................................................................................................................................................37
5.3 CLI Mode.....................................................................................................................................................................39
5.3.1 Running Environment...............................................................................................................................................39
5.3.2 Features......................................................................................................................................................................40
5.4 iManager U2000 Management Mode...........................................................................................................................40
Time Synchronization
IEEE 1588v2
DC level shift (DCLS)
One pulse per second (1 PPS) and time of day (TOD)
Network Time Protocol (NTP)
Frequency Synchronization
Ethernet physical-layer synchronization, that is, synchronous Ethernet (Sync-E)
1588 ACR
Traditional building integrated timing supply (BITS) physical-layer synchronization
(E1(2048 kbit/s), 2048 kHz)
2 Product Architecture
Table 2-1 lists the slots for the boards of the SYNLOCK V3 and Table 2-2 lists the boards of
the SYNLOCK V3.
0 and 12 The SRCU or SOCU board can be installed in the master subrack.
The TDRV board can be installed in the extended subrack.
1 to 10 The master subrack is input/output-compatible and can accommodate
LCIM, TSOU, TODI, PNSU, and TODU boards.
TODI, PNSU, TODU, and TSOU boards can be installed in extended
subracks 1 and 2.
NOTE
Extended subracks 1 and 2 cannot be configured with time synchronization boards at
the same time.
The TSOU board can be installed in extended subrack 3.
11 Only the MITU board can be installed in the master subrack.
No board is required in the extended subrack.
The SYNLOCK V3 employs the two-level distribution control mode, which helps greatly
improve the processing capability of the entire system and fault isolation performance of the
hardware system.
Figure 2-2 shows the architecture of the SYNLOCK V3 system.
When a cabinet accommodates 1 master subrack and 2 extended subracks, no fan tray is
needed on the extended subrack. When a cabinet accommodates 1 master subrack and 1
extended subrack that supports high-precision time synchronization, a 2-U fan tray needs
to be configured in the lower part of the extended subrack to ensure proper ventilation.
2.1.5 Grounding
The SYNLOCK V3 must be grounded properly for lightning release. This also improves the
anti-electromagnetic interference capability of the entire system.
After the subrack is installed in the cabinet, the mounting ears of the subrack are in contact
with the cabinet. In this way, the device is grounded.
Figure 2-3 shows the position of the ground point.
Communicates with the boards for collecting board running status information,
configuring board running parameters, and controlling board running.
Stores various system historical data for the maintenance terminal query.
Provides TL1 and SNMP ports to connect to multiple maintenance terminals and the
NMS center concurrently for system maintenance.
The maintenance terminal software, running on the PC, has the following functions:
Maintains multiple devices concurrently using the serial port or Ethernet port.
Provides the system monitoring, maintenance, and management ports for device
maintenance engineers.
Displays various system running status in a graphical way.
Displays in curves the performance data of various boards collected by the control unit
software.
The board software, running on each board, has the following functions:
Supports the normal running of the CPU small system.
Implements the service functions of a board.
Figure 2-4 shows the software architecture of the SYNLOCK V3 system.
3 Product Functions
The SYNLOCK V3 uses integrated structure. With different boards, the SYNLOCK V3
provides various clocks required for the synchronization network and also the synchronous
clock solution for the entire network. According to actual network requirements, the
SYNLOCK V3 provides customized configurations for the international exchange, inter-
provincial long-distance office, provincial long-distance office, and especially for the tandem
office and end office. Also, the SYNLOCK V3 is applicable for sites that cannot obtain the
timing signals from transmission lines, such as the base stations and the equipment room in
the community.
The SYNLOCK V3 provides diversified frequency synchronization-related signal ports, as
shown in Table 3-2.
impedance converter is
required.
The signal type can be set on the NMS. Two adjacent LCIM boards can be configured to work
in hot backup mode or non-backup mode as required.
Timing Monitoring
Table 3-5 describes the timing monitoring function of the LCIM board.
The SYNLOCK V3 provides the function of monitoring performance of timing clocks, with
parameters flexible configured. If the measurement result exceeds the preset alarm threshold,
an alarm will be generated in real time. The measurement results are reported periodically.
The external input timing signals can be transmitted transparently to the output board without
passing through the clock board. This is to avoid adverse impact brought by clock board
abnormality.
Clock Stratum
Table 3-8 describes the clock stratums of the SRCU/SOCU board.
The SYNLOCK V3 employs advanced hardware platform technology and intelligent software
technology to achieve the high quality clock performance.
The SRCU/SOCU board needs to be configured according to the clock stratum requirements.
For the stratum-3 enhanced clock (ST3E/LNC), the crystal oscillator is configured; for the
stratum-2 enhanced clock (ST2E/TNC), the rubidium clock is configured; for the stratum-1
primary reference clock (PRC/LPR), the rubidium clock and satellite module are configured.
The SRCU/SOCU board has the online fault monitoring function. If a fault is detected, a
board switchover is performed with the phase disturbance within several nanoseconds.
Timing Monitoring
Table 3-9 describes the timing monitoring function of the SRCU/SOCU board.
Transmission quality, SSM, FREQ, TIE, For details, see the timing monitoring of the
MTIE, TDEV LCIM board.
When the LCIM board is not configured, the SRCU/SOCU board supports four input signals.
For details about the monitored items, see Table 3-10.
Frequency Synthesis
The SRCU/SOCU board selects the primary reference according to the reference source
selection principle, and outputs stable timing signals after locking and filtering. After
frequency synthesis, the SRCU/SOCU board will generate various types of timing signals
(such as E1(2048 kbit/s), 2048 kHz, 10240 kHz/5120 kHz/1024 kHz, 64 kHz, IRIG-B, and 1
PPS) required for the SYNLOCK V3 to output, and even insert the SSM information into the
E1(2048 kbit/s) signal as required.
Different backup schemes (1+1 or 1:1) can be selected for two adjacent output slots. The 20
channels of each TSOU board are independent of each other, and they can select the output
signal type. A TSOU board cannot output T1 (1544 kbit/s), 1544 kHz, E1 (2048 kbit/s), and
2048 kHz signals at the same time. The TSOU board has the online fault monitoring function.
When a fault is detected, an alarm is reported immediately and automatic switchover is
performed. Software switchover or hot swapping can be performed for output boards with
redundancy backup, with the phase disturbance no more than 10 ns.
The SYNLOCK V3 provides both low-speed and high-speed communication ports for
different networking requirements, such as the networking environment involving a large
number of synchronous digital hierarchy (SDH) transmission resources and the widely used
data communication network (DCN) (Ethernet port) networking.
Data Caching
Table 3-13 describes the data caching function of the MITU board.
System Maintenance
The local maintenance terminal or remote monitoring center (NMS center) implements online
maintenance of the SYNLOCK V3 by using the MITU board. The MITU board maintains its
continuous communication with all the other boards using the communication bus, issues the
configuration and collects the status data and measurement data of all the other boards, and
then encapsulates the data using TL1 port (or protocol port defined by the vendor). The MITU
board provides powerful data caching capability and data loss avoidance function in case of
power-off, and logs important user operations.
Provides clock source input for clock boards; receives signals output by clock boards and
outputs such signals after format conversion.
Receives input time synchronization signals; provides delay compensation.
Provide delay compensation for 1 PPS+TOD signal transmission.
Monitors and maintains input/output signals and key components.
3.4 Characteristics
This section describes the characteristics of the SYNLOCK V3.
The SYNLOCK V3 implements timing performance monitoring that features multiple ports
(eight inputs per board), high accuracy (phase resolution: 1 ns), high real-time (high-speed
sampling, periodic reporting of data or query of data at any time), multiple sampling points
(10 sampling points τI for both MTIE and TDEV), and wide range (τI range: 50 ms to 10 ks).
Selection of best clock source
The SYNLOCK V3 provides multiple principles of clock source selection (such as selection
by SSM, by priority, by alarm threshold, by majority voting, and by availability). These
principles can be used together for selecting the best primary reference source.
Majority voting achieves voting to abnormal sources with the participation of multiple
primary reference sources. This is to discover in time the degradation of the primary reference
source, deterioration of the clock oscillator, and GPS timing degradation.
3.4.4 Ease-of-Maintenance
The SYNLOCK V3 uses the TL1 protocol for monitoring and management, and it also
supports the SMMP protocol for monitoring and management. The SYNLOCK V3 can be
connected to Huawei TL1 centralized maintenance terminal special for BITS equipment,
Huawei iManager U2000, or a third-party NMS.
The maintenance terminal, using the user-friendly man-machine interface of the Windows
operating system (OS), efficiently monitors and manages the SYNLOCK V3 and the entire
system with mouse-clicks on menus. By analyzing and processing its collected statistical data,
the maintenance terminal efficiently evaluates the synchronization performance of the
communication network to master the network running status in real time. Such information
facilitates optimization of synchronization networks.
PRC/LPR
PRC/LPR is used for the core node or importance node in a network. Table 4-1 lists its typical
configuration.
ST2E (TNC)
ST2E (TNC) is used for the service convergence node. Table 4-2 lists its typical
configuration.
ST3E (LNC)
ST3E (LNC) is used for the local node. Table 4-3 lists its typical configuration.
(Optional) LCIM configuration: To facilitate the configuration of the PNSU or TODU board
in the future, it is recommended that the LCIM board not be configured in slot 1 or 2. Instead,
the four expansion inputs of the SRCU/SOCU board are used to achieve the synchronous
frequency input. Alternatively, the LCIM board is configured for the synchronous frequency
input.
For details about the time synchronization requirement of the LTE TDD base station, see the
ESTI TS 125.105 [B5].
When configured as a stratum-1 time server, the SYNLOCK V3 requires two SRCU boards,
2-20 TODU/PNSU boards, and one MITU board. A satellite card is required for both SRCU
boards.
When configured as a stratum-1 time server, the SYNLOCK V3 requires 1-2 SOCU/SRCU
boards, 2-20 TODI boards, and one MITU board. A satellite card is required for the
SOCU/SRCU board.
When configured as a stratum-2 time server, the SYNLOCK V3 requires 1 to 2 SOCU/SRCU
boards, 1 to 20 TODI boards, and 1 MITU board.
Network Topology
Figure 4-3 shows 1588v2 networking.
Boundary clock (BC) and ordinary clock (OC) are working device modes defined in IEEE 1588v2.
BC: clock device in an intermediate network node. This device provides multiple 1588 ports, with
one functioning as a slave port and the others master ports. The slave port synchronizes the
frequency and time of the system clock to the upper-layer device, and the master ports implement
layer-by-layer time transfer.
OC: start or end clock device in the network. This device provides only one 1588 port, either slave
or master.
Network Description
As a time server, the SYNLOCK V3 supports 1588v2 networking mode in the entire network.
All devices in the network implement time synchronization. Devices at the convergence
layer lock BITS, device at the access layer lock devices at the convergence layer, and
devices in base stations lock the access devices.
Time information can be transmitted to base stations that do not support PTP ports in 1
PPS+TOD mode.
The BITS transmits time information to devices in the bearer network in 1 PPS+TOD
mode.
This networking mode supports protection of clock sources. When the working BITS is
faulty, the other BITS (protection BITS) switches to work. To achieve this, the best
master clock (BMC) algorithm needs to be enabled in the network.
The BC networking scheme for the bearer network is a recommended scheme, which
features highest accuracy, good source protection, and good line protection.
Table 1.1 Mapping relationship between LCIM boards and input ports on the front panel
Slot for the LCIM Board SMB Connectors on the Chassis Port Area
1 A1-A8
2 A9-A16
3 B1-B8
4 B9-B16
5 C1-C8
6 C9-C16
7 D1-D8
8 D9-D16
9 E1-E8
10 E9-E16
In the clock monitoring system, the test port of the BITS device is used to lead in signals
output from the service device. These signals are compared with the BITS clock signals and
TIE is tested to calculate MTIE and TDEV. The test result and calculation result are then
reported, through the maintenance port of the BITS device, to the monitoring center for
centralized processing. In this way, the monitoring center is able to monitor the timing quality
of service devices in the entire network.
5 Device Management
5.1 Overview
You can manage, maintain, and monitor the SYNLOCK V3 using the centralized maintenance
terminal, U2000, and command-line interface (CLI).
Centralized maintenance terminal
The SYNLOCK centralized maintenance terminal (based on the TL1 language) provides
GUIs to manage Huawei BITS synchronization devices. It is compact, provides
extensive functions, and is easy to use. Besides, it can run in common Windows OSs,
having a low requirements on the hardware and software of the operating system (OS).
The basic software package of the SYNLOCK centralized maintenance terminal can
function as a local craft terminal (LCT) that can manage a local BITS device. The basic
software package together with the extended software package can function as a mini
network management system (NMS) that can manage up to 255 BITS devices,
applicable for regular time synchronization management on small or medium networks.
CLI
Among the three management modes, CLI has the lowest requirements on operating
environments. Instead of using dedicated software, you can access the SYNLOCK V3
for management and maintenance using the CLI program of the Windows OS (serial port
mode) or through remote login (network port mode). CLI is not as intuitive as GUI and
therefore is commonly used for temporary maintenance and management.
U2000
The iManager U2000 is a unified GUI NMS platform of Huawei and is implemented
using the SNMP language. It can manage a wide set of mainstream devices in the access
and transport domains, but has high requirements on OS (such as Windows, Linux, and
UNIX) hardware and software. U2000s with different software and hardware
configurations support different management capacities (ranging from 2,000 to 20,000
BITS devices) and are generally used on large networks for time synchronization
management. The U2000 differs from the SYNLOCK centralized maintenance terminal
in that the U2000 supports the client/server working mode, active/standby server
protection, and northbound interfaces (NBIs).
Software Requirement
Table 5-2 lists the configuration of the software requirement for the centralized maintenance
NMS.
SYNLOCK V3s are able to be monitored and managed in a centralized manner. Figure 5-1
shows the network topology.
E1 Bridging Networking
This networking is based on E1 bridges and transmission links. There is an E1 bridge between
each SYNLOCK V3 node and the centralized maintenance terminal. The E1 bridge is
connected to the transmission device through E1 circuits, and to the SYNLOCK V3 or
centralized maintenance terminal through the Ethernet, as shown in Figure 5-2.
5.3.2 Features
The CLI mode has the following features:
Provides multiple methods for both local and remote maintenance.
Provides different operation permissions of configuration commands for users of
different rights to prevent illegal intrusion of unauthorized users or incorrect operation.
Provides abundant commands for configuration, maintenance and debugging, as well as
detailed command prompt messages.
The iManager U2000 of a version between V100R005 and V100R006C02, although able to manage the
SYNLOCK V3, is not recommended because its management features are not as comprehensive as the
iManager U2000 of V100R600C02. Patch V100R006C02SPC300+CP3203,
V100R006C02SPC300SPC302, or higher is recommended.
The iManager U2000 V100R006C02 or a later version can well manage the SYNLOCK V3.
It supports the client/server mode, access/transport cross-domain management, and
northbound interfaces. For details, see the iManager U2000 Product Documentation.
A user can use the U2000 to log in to a BITS device by using the user name and password of the
device. The BITS devices support the administration, maintenance, and monitoring rights for users.
Passwords for administration users, default maintenance users, and maintenance users created by
administration users need to be changed periodically to ensure password security. For how to change
passwords, see section 4.4.3 Setting a BITS User Password in SYNLOCK V3 BITS V300R003C10
Operation Manual.
The iManager U2000 of a version between V100R005 and V100R006C02, although able to manage
the SYNLOCK V3, is not recommended because its management features are not as comprehensive
as the iManager U2000 of V100R600C02.
N66-22Cabinet 2200 mm x 600 mm x 600 mm (86.81 in. x 23.62 in. x 23.62 in.)
(19-inch 2600 mm x 600 mm x 600 mm (102.36 in. x 23.62 in. x 23.62 in.)
standard cabinet) (An upper enclosure frame with a height of 400 mm is required.)
N63E-22Cabinet 2200 mm x 600 mm x 600 mm (86.81 in. x 23.62 in. x 23.62 in.)
(ETSI cabinet) 2600 mm x 600 mm x 600 mm (102.36 in. x 23.62 in. x 23.62 in.)
(An upper enclosure frame with a height of 400 mm is required.)
Subrack Without mounting ears: 575 mm x 436 mm x 253 mm (22.64 in. x
17.17 in. x 9.96 in.)
With mounting ears for the 19-inch cabinet: 575 mm x 482.6 mm x
Item Dimensions (H x W x D)
Weight
Master subrack in full configuration: 18 kg
Extended subrack in full configuration: 18 kg
Operating Environment
1. Long-term operating
− Temperature: 0 °C to 40 °C
− Humidity: 5%-90% RH
2. Short-term operating (within 24 hours)
− Temperature: -5 °C to +55 °C
− Humidity: 5%-95% RH
Power Consumption
Maximum power consumption of the master subrack: 298 W.
Maximum power consumption of the fan tray: 70 W (N63E-22)
Power consumption when the fan tray is running normally: 15 W (N83E-22)
Maximum power consumption of the fan tray: 150 W (N66-22)
Power consumption when the fan tray is running normally: 30 W (N66-22)
Maximum power consumption of the extended subrack: 182 W.
LCIM 13.6
SRCU 120.3
SOCU 86.1
PNSU 17.7
TODU 11.5
TSOU 6.26
TODI 13.6
TDRV 26.1
MITU 14.1
PRC/LPR performance
Wander generation MTIE See Figure 6-1. See Figure 6-1.
(satellite locking)
Wander generation TDEV See Figure 6-2. See Figure 6-2.
(satellite locking)
Frequency accuracy < 1E-11 < 4E-12
Output jitter 24.4 ns Typical value: 5 ns
Phase discontinuity 1/8UI (61 ns) Less than 15 ns
Holdover performance 1E-10 per day 5E-11 per day, 1E-10 per 3 days,
3E-10 per 7 days
ST2E (TNC) and ST3E (LNC)
Free-run frequency ST2E: 1.6E-8 ST2E: 5E-10 per year
accuracy ST3E: 4.6E-6 ST3E: 2E-7 per year
Wander generation See Figure 6-3, Figure 6-4, ST2E: see Figure 6-3 and Figure
Figure 6-6, or Figure 6-7. 6-4.
Figure 1.2 ITU-T requirement and SYNLOCK vendor requirement for wander generation MTIE
of PRC/LPR
Figure 1.3 ITU-T requirement and SYNLOCK vendor requirement for wander generation TDEV
of PRC/LPR
Figure 1.4 ITU-T requirement and SYNLOCK vendor requirement for wander generation MTIE
of ST2E (TNC)
Figure 1.5 ITU-T requirement and SYNLOCK vendor requirement for wander generation TDEV
of ST2E (TNC)
Figure 1.6 ITU-T requirement and SYNLOCK vendor requirement for wander transfer TDEV of
ST2E (TNC)
Figure 1.7 ITU-T requirement and SYNLOCK vendor requirement for wander generation MTIE
of ST3E (LNC)
Figure 1.8 ITU-T requirement and SYNLOCK vendor requirement for wander generation TDEV
of ST3E (LNC)
Figure 1.9 ITU-T requirement and SYNLOCK vendor requirement for wander transfer TDEV of
ST3E (LNC)
Figure 1.10 ITU-T requirement and SYNLOCK vendor requirement for phase transient of ST2E
(TNC)
Figure 1.11 ITU-T requirement and SYNLOCK vendor requirement for phase transient of ST3E
(LNC)
Parameter description:
1. The time span (tx in Figure 6-11) in from the time (t1 in Figure 6-11) for the clock to
obtain the good reference to the time (t2 in Figure 6-11) for the clock to confirm the
reference validity (for example, no LOS, OOF, or AIS) meets the requirements specified
in Table 6-5.
2. The time span (tx in Figure 6-11) from the time (t1 in Figure 6-11) for the clock
reference to recover from frequency offset to the time (t2 in Figure 6-11) for the clock to
confirm the reference validity meets the requirements specified in Table 6-6.
The maximum time (ty in Figure 6-11) for locking meets the requirements specified in
Table 6-7.
3. The maximum wander (tz in Figure 6-11) for obtaining locking meets the requirements
specified in Table 6-8.
tz NA MTIE ≤ 1 μs MTIE ≤ 1 μs
Phase change rate ≤ 61 Phase change rate ≤ 61 ns/1 ms
ns/1 ms
LAN 1-30 ms
MAN 10-500 ms
WAN (Internet) 100-1000 ms
Maximum number of access and monitoring 400 x 20 (20 TODI boards, each supporting
clients supported by each server a maximum of 400 clients)
Time synchronization accuracy When the GPS is locked, the absolute time
accuracy of the PTP port is within ±150 ns.
When the 1 PPS is locked, the relative time
accuracy of the PTP port is within ±150 ns.
ity
Signa GPS, 64 kbit/s T1 (1544 1544 kHz E1 (2048 2048 10240
l type GLONASS, CC kbit/s) kbit/s) kHz kHz/51
or BeiDou 20
kHz/10
24 kHz
Redu Channel Separate use of adjacent slots or mutual backup of adjacent slots
ndan backup
cy
back
up
Port Satellite 110 ohms 75 ohms
type antenna
Signa GPS L1: ITU-T ITU-T - ITU-T ITU- ≤ 3.0
l 1.5 GHz G.703 G.703 G.703 T Vpp
stand GLONAS G.70
ard S L1: 1.6 3
GHz
BeiDou:
2.6 GHz
Meas N/A ≤ –24dB ≤ –24dB ≤ –6dB ≤ –24dB ≤ -6 ≤ -6 dB
urem dB
ent
thres
hold
Onlin Real-time monitoring of all input ports
e
moni
torin
g
y
Red Mutual backup of adjacent slots (1:1 or 1+1)
und
anc
y
bac
kup
Sig 64 kbit/s T1 (1544 1544 kHz E1 (2048 2048 kHz 10240 kHz/5120
nal CC kbit/s) kbit/s) kHz/1MHz
typ
e
Por 110 ohms 75 ohms
t
typ
e
Sig ITU-T ITU-T - ITU-T ITU-T -
nal G.703 G.703 G.703 G.703
typ
e
6.1.7 MTBF
Table 6-15 lists the MTBF of different boards.
LCIM > 20
SRCU/SOCU > 20
PNSU > 20
TODU > 20
TSOU > 20
TODI > 20
MITU > 20
TDRV > 20
Entire system > 20
6.1.8 EMC
The EMC performance of the SYNLOCK V3 passes the ETSI EN 300 386 (2000) test and
complies with the IEC 61000-4 (1993, 1994, 1995, 1996, and 2000) series, CISPR22 (1997),
ETS EN 300 386, EN55024 (1998), and EN55022 (1998). It also passes the CE certificate.
A
ACR adaptive clock recovery
AP access preamble
B
BITS building integrated timing supply
BTS base transceiver station
C
CPU central processing unit
D
DCLS DC level shift
DCN data communication network
DDS direct digital synthesizer
G
GPS global positioning system
I
IP Internet Protocol
L
LNC Local Node Clock
LPR Local Primary Reference
M
MSC mobile switching center
MTBF mean time between failure
N
NTP Network Time Protocol
P
PDF power distribution frame
PDH plesiochronous digital hierarchy
PPS pulse per second
PSBU packet synchronization backplane unit
PSIU packet synchronization interface unit
PSOU packet synchronization ocxo clock unit
PSRU packet synchronization rubidium clock unit
PTP precision time protocol
R
RNC radio network controller
RTC real time clock
S
SDH synchronous digital hierarchy
T
TD-SCDMA time division-synchronous code division multiple access
TL1 transaction language 1
TNC transit node clock
U
UDP User Datagram Protocol
UTC coordinated universal time
W
WCDMA wideband code division multiple access