Training Documentation-Time Source & Clock Source Design 5G RAN1.0

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 27

2018-04-02 Security Level:

Time Source & Clock


Source Design
5G RAN1.0
www.huawei.com

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential


Objectives
After completing this course, you will be able to
1. Learn the rules for designing clock or time sources.
2. Learn the concepts of time synchronization and
frequency synchronization.
3. Learn related configurations.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2


Reference Documents

 Synchronization Feature Parameter Description

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3


Time Synchronization
 Overview of Time Sources
 Selection and Configuration of a Time Source
Clock Synchronization
 Overview of Clock Sources
 Clock Precision Requirements
 Clock Sources
 Clock Deployment Solutions
 Clock Faults
 MBTS Clock Deployment Solutions
 Selection and Configuration of a Clock Source

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 4


Time Synchronization

During the normal operation, the base station is required to maintain an accurate NE time. Otherwise,
the impacts on network O&M are as follows:
Problem location: The NE time on the network is not synchronized. Therefore, when the NE reports
alarms, the time is inconsistent with the log time, which may cause confusion in problem location and
dependency analysis.
Accuracy of performance statistics: The NE time on the network is not synchronized, resulting in
inconsistency of the performance statistics collection time and confusion between performance report
and traffic-related analysis.
Wrong triggering of the timing service: The inaccuracy of the time may result in wrong or missed
triggering of the timing service. For example, the license is activated in advance.
Currently, a base station uses Universal Time Coordinated (UTC).
Design criteria:
1. Type of available time synchronization server onsite
2. Customer's requirements for time sources
To ensure the O&M time accuracy, the synchronization server is selected in the following
sequence:
1. GPS (On the U2000, the NTPC time must be consistent with the GPS time.)
2. Dedicated NTP server provided by the customer
3. U2000 (which can be set and used as the NTP server. An NTP server of the customer is
preferred. Use the U2000 only if the customer does not have an NTP server. The time
precision of the U2000 is 1s, while that of a dedicated NTP server is 50 ms.)
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 5
GPS Time Source Design

Overview of the GPS time source:


The NE time is synchronized with the GPS time
source if the base station uses the GPS as the time
synchronization source. The GPS receivers installed
in the base station receive several GPS signals and
collect the UTC-based standard time information,
with a precision to nanosecond. The time source is NTP
more accurate than the NTP and SNTP time packet
sources. U2000
Base
The base station time is set to synchronize with the station
Base
station
GPS time every 30 minutes.

To use the GPS clock for synchronization, you need


to invest on the GPS signal receive devices and the Base
station
eNodeB site must meet the GPS signal receiving
requirements and related engineering requirements.
For details, see the quick installation guide to the
GPS satellite antenna system.

Advantages: high precision to nanoseconds, higher than that of NTP and SNTP time sources
Disadvantages: The site location must meet the GPS signal reception requirements.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6


GPS Time Source Synchronization Configuration

1. Set a time source.

2. Add a GPS clock link.

Script examples:
SET TZ: ZONET=GMT+0800, DST=NO; //Set the time zone.
SET TIMESRC: TIMESRC=GPS; //Set the GPS clock as the clock source.
ADD GPS: GN=0, CN=0, SRN=0, SN=7, CABLETYPE=TWISTED-PAIR, CABLE_LEN=30, MODE=GPS,
PRI=1; //Add a GPS clock link.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 7


NTP Time Source Synchronization Design
The Network Time Protocol is a protocol applying to WAN and LAN for time synchronization between PCs
and servers or clock sources such as quartz clocks and GPS. The NTP provides an adjustment accuracy with
a deviation of less than one millisecond on LAN and less than dozens of milliseconds on WAN compared with
the standard time. The synchronization can also be encrypted to prevent malicious protocol attacks.
The NTP is an application-layer protocol based on UDP packet transmission. The NTP is a mature time
synchronization mode. The time can be synchronized as long as the terminal or the lower layer server is
connected to the upper layer server.
Time Synchronization
Recommended Value
Parameter
NTP server
Time synchronization server NTP/U2000

U2000 or NTP client Time synchronization period


360 minutes
as a medium-level (configurable)
NTP server
Number of ports for time
123
synchronization (configurable)
NTP client as a NTP client as a If an NTP server connects to an eNodeB on the
medium-level medium-level
NTP server NTP server network, the NTP server for the eNodeB can be set to
keep NE time consistent with the network. eNodeB can
be configured with a maximum of four NTP servers.
One of them serves as the primary server. If it fails to
perform time synchronization, the eNodeB can still
gNodeB gNodeB gNodeB gNodeB synchronize the time with other NTP servers, ensuring
the reliability of the time synchronization function.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 8


NTP Synchronization
1. Select a time source.

2. Add an NTP client.

Script examples:
SET TZ: ZONET=GMT+0800, DST=NO; //Set the time zone.
SET TIMESRC: TIMESRC=NTP; //Set the NTP server as the clock source.
ADD NTPC: MODE=IPV4, IP="10.10.10.1", PORT=123, SYNCCYCLE=60, AUTHMODE=PLAIN; //Add an NTP
client.
In remote U2000 dual-server backup scenarios, each of the master and standby U2000 uses one IP address. For
security reasons, both the master and standby U2000 must be configured as NTP servers, and the master NTP
server must be specified.
ADD NTPC: MODE=IPV4, IP=“10.10.10.2”, PORT=123, SYNCCYCLE=60, AUTHMODE=PLAIN; //Add an NTP
client.
SET MASTERNTPS: MODE=IPV4, IP="10.10.10.1"; //Set the master NTP server.
Notes: The OM NTP time synchronization function of gNodeBs is RAT-independent. NTP clock packets can be
interpreted correctly between a customer's NTP server and a gNodeB without NTP server upgrades.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 9


Time Synchronization
 Overview of Time Sources
 Selection and Configuration of a Time Source
Clock Synchronization
 Overview of Clock Sources
 Clock Precision Requirements
 Clock Sources
 Clock Deployment Solutions
 Clock Faults
 MBTS Clock Deployment Solutions
 Selection and Configuration of a Clock Source

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 10


Concepts Related to Clock Synchronization
The transport network needs to be synchronized with clock reference signals, that is, synchronization sources, to ensure that transmitted information is
not lost or distorted. A complete and effective synchronization mechanism is essential for a transmission network to work normally. The gNodeB needs
to obtain the precise frequency from the clock signal provided by the transport network. Without clock synchronization, the eNodeB cannot perform
handovers. Clock synchronization is classified into frequency synchronization, phase synchronization, and time synchronization.

Frequency synchronization: Two signals have the same


number of bursts in the same period. Frequency
Signal 1
synchronization has nothing to do with the sequence of burst
occurrence and the start and end time of each burst. Signal 2

Phase synchronization: Two signals have the same


frequency and the same start and end time of each burst.
Phase synchronization has nothing to do with the sequence of Signal 1
burst occurrence.
Signal 2

Time synchronization: Two signals have the same


frequency, phase, and burst sequence. The origin of the
timescale for a signal needs to be synchronized with the
Universal Time Coordinated (UTC). Therefore, time
Signal 1
synchronization implies synchronization in absolute time. The
Signal 2
UTC is a universal timing standard, in which the atomic clock
is maintained accurately to ensure time synchronization
across the world, with the precision to microseconds.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11


Precision Requirements for NR Time Synchronization
1. Basic 5G services require inter-BBU 2. 5G collaboration services have different time
time synchronization. synchronization requirements.
Symbol from cell 1
Adjacent eNodeB DDSUDD
d1

Adjacent eNodeB DDSUDD Interference


Symbol from cell 2

d0

Faulty eNodeB DDDSUD CP

Symbol
Most 5G NR frequency bands are LTE TDD frequency bands. Basic 5G services require
Time synchronization requirements for 5G coordination services:
inter-BBU time synchronization.
•The synchronization specifications are subject to the CP length.
For interference avoidance, inter-BBU time out-of-synchronization leads to inter-BBU
TD 1 + TD 2 + TD 3 = Total TD ≤ CP
uplink interference caused by downlink transmission and inter-UE downlink interference Total TD TD 1 TD 2 TD 3
caused by uplink transmission. Delay
Time difference Time difference Synchronization
difference
The time synchronization precision between cells that perform basic NR services Description
when the UE between the air
caused by
precision
receiver interface and a between air
is 3 µs (±1.5 µs). This precision meets the time synchronization requirements of multi-path
receives signals UE interfaces
propagation
basic 5G NR basic services in TDD mode in cells with a typical coverage radius.
15 kHz ≤ 4.7 µs ≤ 1 µs ≤ 0.6 µs ≤ 3 µs
For details about the derivation process, see the 3GPP proposal (R4-1706734 R4-
1700208 R4-1700209 R4-1706715). 30 kHz ≤ 2.3 µs ≤ 1 µs ≤ 0.6 µs ≤ 0.7 µs
For details about the proposal regarding synchronization precision, see R4-1706608
120 kHz ≤ 0.6 µs ≤ 0.3 µs ≤ 0.06 µs ≤ 0.19 µs
Section 1.2.
For the 3GPP conclusion, see 3GPP TS 38.133 (V0.2.0). This table lists the synchronization requirements for coordination features based on
intra-frequency CoMP, such as SMP, DMP, DPS, and UL CoMP. Coordination
features not based on intra-frequency CoMP, such as DC, downlink CA, and CBF, do
not have these requirements.

For high-frequency bands, it is recommended that coordination services be


deployed within one BBU. If inter-site deployment is required, a GPS clock must be
deployed to ensure time synchronization. If the GPS synchronization precision decreases,
coordination may fail, or coordination performance may deteriorate.
For low-frequency bands, it is recommended that coordination services be
deployed within one BBU or across BBUs (multiple timers). In inter-site deployment
scenarios, a GPS clock is recommended for time synchronization for 30 kHz, and either a
GPS or IEEE1588 clock can be used for 15 kHz.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12


NR Clock Sources
Category LTE NR GPS
GPS satellite card GPS satellite card
• Time synchronization: GPS/BeiDou/GLONASS, 1588v2, + antenna + antenna
antenna

Synchronization and 1PPS+TOD


Supported
source • Frequency synchronization: 1588, synchronous Ethernet, Satellite
card
BITS, and E1/T1 line clock (Customized)

Signal
Customized Not transmission
BBU RGPS, RRU RGPS, and CGPS (see the right figure)
GPS supported + power
Signal supply
• Time synchronization supports automatic switchover transmission (about 15 m) CPRI (optional)
+ power
between GPS and IEEE1588v2, and between GPS and supply
Synchronization 1PPS+TOD.
source • Frequency synchronization supports automatic switchover Supported No satellite card No satellite card No satellite card
switchover between GPS and synchronous Ethernet, between on the MPT on the MPT on the MPT
synchronous Ethernet and IEEE1588v2, and between 1PPS
and IEEE1588v2.

Hybrid
Combination of IEEE1588v2 and synchronous Ethernet, and of
synchronization Supported
GPS and synchronous Ethernet
source

Notes:
RRU RGPS: RRU interfaces are customized based on the requirements of customers' NR sites.
CPRI GPS: NR supports CPRI GPS. Verify and deliver CPRS GPS based on site requirements. 20 ms to 200 ms

The NR clock module inherits the functions of the LTE clock module. In eRAN13.1, NR supports only
the TDD mode. TDD uses the mature satellite synchronization (GPS) or 1588v2 technology to
implement time synchronization. 1PPS+TOD, which requires additional interfaces, is seldom used.
TOD
1PPS+TOD uses both pulse per second (1PPS) and time of day (TOD) for time synchronization. TOD messages

signals transmit time information, reference clock types, and working statuses of reference clocks. TOD
< 500 ms
protocol packets are sent once per second. 1PPS+TOD adopts a solution similar to the time interface of > 1 ms

a GPS satellite.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13


Clock Source: GPS
The GPS time synchronization process is as follows:
1. The base station is equipped with a UMPT board with a satellite card and a GPS antenna.
2. Upon receiving GPS signals, the antenna amplifies and de-noises the signals, and then transmits them GPS
to the receiver in the base station through antenna feeders.
3. Upon receiving the GPS signals, the receiver calculates the time information and base station
coordinate information. The time information is sent to the CPU through TOD, and 1PPS signals are
sent to the module X.
4. The module X compares the received 1PPS signals with the local 1PPS signals of the MPT to obtain a gNodeB gNodeB
phase discrimination value delPha. delPha indicates the difference between the local time and standard
time. The clock algorithm calculates the voltage of the crystal for voltage control based on delPha, and
then adjusts the output frequency of the crystal to achieve frequency synchronization. gNodeB
5. After frequency synchronization, the CPU interprets the time information in TOD signals to achieve FE/GE link
GPS time synchronization. Clock synchronization signal

The GPS antenna system receives GPS signals at 1575.42 MHz and sends the signals to the GPS MPT in the BBU
card of the gNodeB. When the satellite card initially locks the GPS signal source, at least four satellites
need to be traced.

A gNodeB must meet the GPS signal reception conditions and engineering requirements. For details,
see eNodeB_GPS Satellite Antenna System_Hardware Installation_Quick Installation Guide.
Interference caused by GPS clock out-of-synchronization has severe and wide impacts. A large
number of gNodeBs adjacent to the gNodeB suffering from GPS clock out-of-synchronization may be
interfered. As a result, UEs in the coverage of these adjacent gNodeBs cannot perform services or
even cannot access the network despite good RSRP. The uplink RSSI of these adjacent gNodeBs is
generally 10 dB to 20 dB higher than normal values, or even higher. Install two GPS antennas at a distance greater than 0.5 m.
Possible causes of GPS out-of-lock:
1.The GPS device is not installed according to the standards. As a result, not enough satellites can be
traced.
2.The GPS clock is interfered. GPS GPS
3.The satellite card is abnormal. antenna antenna
You can run the DSP GPSSNR command to query the number of satellites traced by the GPS and the
SINR of the satellite signals. If the GPS clock is out-of-lock, the gNodeB generates an alarm.
However, if non-Huawei devices are used on the network, GPS out-of-lock may cause interference to
Huawei devices.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 14


Clock Source: IEEE1588v2
IEEE1588v2 is a protocol of precise time synchronization defined by IEEE. It is called "A Precision Clock Synchronization Protocol for
Networked Measurement and Control Systems", and it can also be referred to as PTP.
IEEE1588v2 applies to the scenario where all nodes in a distributed network must be precisely synchronized in terms of time. This protocol
provides a mechanism that all network nodes synchronize to a unified time reference. Physical ports use hardware-assisted timestamping
to achieve accuracy within the nanosecond range.
IEEE1588v2 supports L3 unicast and L2 multicast.
If L2 multicast is used, IEEE1588v2 packets are carried by MAC packets.
If L3 unicast is used, IEEE1588v2 packets are carried by IPv4 UDP packets.

Profile Type Synchronization Mode Description


1588v2 (Huawei proprietary) L3 Time and frequency A Huawei proprietary protocol
unicast synchronization
IEEE1588v2 16.1 L3 unicast Time and frequency If the interconnection equipment does not support G.8265.1, this protocol
synchronization can be used.
IEEE1588v2 L2 multicast Time synchronization A standard IEEE protocol applicable to the field of industrial control
ITU-T G.8265.1 L3 unicast Frequency A profile for FDD. Only devices on both ends of a link must support this
(R&D internal name: adaptive synchronization profile.
clock recovery [ACR])
ITU-T G.8275.1 L2 multicast Time synchronization A profile for TDD and defined by the ITU-T. This profile is applicable to
telecom networks and requires that each hop of device on the transmission
link supports this profile and each device on the synchronization link
supports 1588v2. This profile is difficult to deploy.
ITU-T G.8275.2 L3 unicast Time synchronization In this profile, the intermediate network does not need to support 1588v2,
(R&D internal name: adaptive and timing packets are transmitted transparently. Only the devices on both
time recovery [ATR]) ends need to support 1588v2. For LTE FDD, this profile requires inter-site
time synchronization.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15


Hybrid Clock Source: 1588v2 + Synchronous Ethernet
A base station accesses both the 1588v2 and synchronous Ethernet clock sources at the same time to obtain
1588v2 phase information and use the frequency stability of the synchronous Ethernet clock source to achieve phase
synchronization.
In a combination of 1588v2 + synchronous Ethernet, the 1588v2 provides phase and time synchronization, while the
synchronous Ethernet provides frequency synchronization. If the 1588v2 clock is faulty, the base station traces the
synchronous Ethernet clock for time synchronization.

GNSS satellite

s
1588 packets ket
pac
88
s

Transport network 15
et
ck

Synchronous
ck s
pa

s
pa ou
et

ts
88

et n

Ethernet packets
cke
rn hro

Ethe nous
15

he c

8 pa
Et Syn

pack et
ets

158
hro
rn
158

Eth

8
Syn net p
Sync

158
8 pa

pac
c ke er
chr acke
Syn ts

ket
Ethe chrono
rnet u ono ts

s
pac s
kets us

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 16


Combined Clock Source: GPS + Synchronous Ethernet
A base station accesses both the GNSS and synchronous Ethernet clock sources at the same time to obtain GNSS phase
information and use the frequency stability of the synchronous Ethernet clock source to achieve phase synchronization.
In a combination of GNSS + synchronous Ethernet, the GNSS provides phase and time synchronization, while the
synchronous Ethernet provides frequency synchronization. If the GNSS clock is faulty, the base station traces the
synchronous Ethernet clock for time synchronization.
GNSS satellite

GNSS satellite

Synchronous
Ethernet packets

Transport network

GNSS satellite
Synchronous
Ethernet packets

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 17


Clock Source: Free Running
The clock enters the free running mode in the following two scenarios:
•The system traces no clock source after warming-up.
•The system loses the network clock source and the specified duration for the holdover mode expires.
If the system loses the external clock source, the free running mode ensures that gNodeBs in TDD mode can work properly within 4 to 8
hours (8 hours for 5G low-frequency bands and 4 hours for 5G high-frequency bands). When the system re-obtains and locks a network
clock source, the clock exits the free running mode.
The 10 MHz crystal oscillator on the main control board of gNodeBs can reach a precision of 0.01 ppm and meets the requirement of the
gNodeB on clock precision (±0.05 ppm) in a short period. Free running can be used in the following scenarios:
1. The transmission equipment is not ready during site deployment. No external reference clock source is available.
2. There are few gNodeBs at some sites, such as trial or demonstration sites, or there is no external clock resource temporarily.
3. The external clock source is faulty.
Frequency adjustment on free running is required during initial deployment. Onsite adjustment is not required because the adjustment is
done before the delivery of the equipment. The adjustment must be performed every 90 days later on, which is heavy workload. However,
the gNodeB clock precision is affected by the aging of the internal clock. It is recommended that an external reference clock source be
used, instead of free running on the gNodeB.
• Calculating the theoretical holdover specifications
The holdover time is determined by the reserved specifications and the frequency drift specifications of
the clock source or the internal clock of the gNodeB after the gNodeB enters the holdover mode.
A indicates the tolerant value that does not affect gNodeB services. Holdover specifications
B indicates the frequency drift of the clock source or internal crystal oscillator.
Holdover time in normal circumstances X = A/B
The following table lists the holdover specifications and time when a clock link is disconnected without signal
quality deterioration (no extra phase or frequency deviation).

LTE TDD 5G NR Low Frequency 5G NR High Frequency Holdover


Holdover Initial phase time
10 µs 4 µs 2 µs deviation
specifications
Holdover time 24 hours 8 hours 4 hours

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 18


Handling Faulty NR Clocks
When a gNodeB does not have a clock reference and an external clock source is available, the
gNodeB will trust and trace the external clock source unconditionally. A gNodeB can only detect the
loss of a clock source or significant changes to clock signal quality. The following table lists clock
source fault modes. When the clock source is faulty, a gNodeB enters the clock holdover mode.
Fault Mode Symptom Can Be Detected and Isolated or Not

Invalid No clock signal is available. A gNodeB can detect these faults. Once
these faults are detected, the gNodeB
Large phase disconnects the clock source, and the
A single phase deviation > *Threshold internal clock enters the holdover mode.
deviation

A single phase deviation < *Threshold A gNodeB cannot detect these faults or
Slow phase
deviation generate any alarm for them. A gNodeB
Accumulated phase deviation > Threshold will always trace the clock source even if
Initial phase these faults occur and interfere with
Fixed deviation during initial synchronization services.
deviation

Clock alarms will be reported when typical clock faults occur. The maintenance and test methods for
clock alarms are as follows:
1. Run the LST/DSP command to check whether the clock configuration and clock status are correct.
2. Check whether the clock traffic statistics are normal.
3. Conduct a clock source quality test (run the STR CLKTST command for more than five
minutes and then run the STP CLKTST command).
This test is important. You can directly observe the difference between the clock source and the 10
MHz crystal oscillator of the board. The clock of a gNodeB may be locked even if the differences
detected during clock tests in a certain period are 0. Thus, you need to perform a clock quality test to
determine whether the clock source is abnormal.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 19


NR Time Synchronization Deployment Solutions and Policies
Suggestions:
1. The gNodeB supports two both GPS and 1588v2 clock sources.
2. If no synchronization measure has been taken on the live network (neither a GPS clock nor a 1588 clock is deployed), the GPS synchronization solution is
recommended. This is because the 1588 clock is commercially immature and 1588 fault demarcation is difficult.
3. If a 1588 clock has been deployed on the customer's live network and the customer insists on using the 1588 clock for time synchronization, use the 1588
clock as long as the precision meets the gNodeB requirements and the 1588 clock does not affect the deployment of Huawei gNodeBs.

Item GPS 1588+BITS 1588+GPS Remarks


Network Deployed on the RAN side and independent
Bearer network upgrades are required.
readiness of other networks GPS is preferred (because it is
Network independent of the bearer
No planning is required. 1588 path planning/configuration (automatic)
planning network and is deployed with the
Solution Deployment of the bearer network (XX months) in gNodeB).
Installed together with the gNodeB
deployment advance
Fault locating Interference problems are difficult to locate. Difficult fault demarcation Not much difference
The GPS fault rate is high, and the Multiple clock sources and multiple paths on the 1588 is slightly better (with
Reliability
interference is uncontrollable. bearer network ensure reliability. greater technological potential).
Areas without legacy GPS clocks Areas with legacy GPS clocks

X months, USD X x 100/site


1588 clock deployment X hours, USD X x 10/site
For outdoor sites GPS
on the bearer network Maintenance
Case 1 gNodeB Maintenance (fault deployment
(upgrade/planning/config
uration/acceptance) deployment demarcation)

For outdoor sites X hours, USD X x 100/site


Case 2 1588 clock
GPS For a few indoor sites deployment in
Maintenance these areas
gNodeB
Maintenance
deployment deployment
For a few
indoor sites 1588 clock
deployment in gNodeB
Maintenance
these areas deployment
Time to start 5G base station deployment

Time to start 5G base station deployment


1. In areas with legacy 1588 clocks deployed on the bearer network, the 1588 clocks are 1. Use GPS clocks in both new and legacy outdoor sites.
recommended to minimize RAN costs. 2. In a few indoor sites where GPS cannot be deployed, deploy 1588 clocks.
2. In areas without any 1588 clock on the bearer network, GPS clock is recommended to optimize
the deployment pace. If there are a few indoor sites, deploy 1588 clocks for these sites.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 20


MBTS Clock Deployment Solutions
In eRAN13.1, NR works in TDD mode. TDD requires time synchronization technologies GPS and 1588v2. Timing loop is required when the NR, GSM,
and LTE share the 1.8 GHz band.
Clock deployment policies:
1. In all scenarios, RATs of an MBTS can use independent external clock sources or share a
clock source. Clock source sharing is recommended for a new MBTS. If 5G is added to a Non-timing Single BBU
loop scenarios subrack
legacy MBTS, 5G can use a new independent clock source or share the clock source of other
MBTS
RATs.
Timing loop
2. If all RATs share an external clock source, it is recommended that the NR connects to the scenarios Inter-BBU
interconnection
clock source (because NR boards have the highest clock precision).
3. In the case of timing loop, the GTMUb must be locked if GSM is deployed and the GSM
version is earlier than SingleRAN13.1. If there is no GSM or the GSM is of SingleRAN13.1,
4G BBU + 5G BBU
use a non-GSM mode as the primary mode for timing loop.
BBU39x0 BBU5900

RRU (1.8 GHz) AAU (3.5 GHz)


4G and 5G co-BBU
BBU5900
RRU AAU UBBP (NR)
(1.8 GHz) (3.5 GHz)
GTMU
UBBP (NR) UMPT
UBBP UMPT (L)
(NR)

UBBP (L) CI interconnection


UMPT (L) UMPT (NR) GPS/1588 clock
1. In GLN inter-BBU interconnection scenarios, where 1.8 GHz is shared and GSM is a legacy RAT:
1. In LTE and NR co-BBU scenarios: GPS/1588 clock
• If LTE is also a legacy RAT, NR can share the clock source of GSM and LTE or use an independent
• If LTE is a legacy RAT, NR can share the LTE clock source or use an independent
clock source.
clock source.
• If both LTE and NR are newly deployed, it is recommended that GSM, LTE and NR share a clock
• If both LTE and NR are newly deployed, it is recommended that LTE and NR share source, with NR boards connected to the clock source. When they share a clock source, the master
a clock source, with NR boards connected to the clock source.
BBU can share the clock source of slave BBUs.
2. If LTE and NR share a BBU, it is recommended that NR be configured as the 2. If an RAT in the master BBU is used as the primary mode for timing loop, use policy 3 for GSM.
primary mode for timing loop.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 21


GPS Clock Source Configuration

Run the ADD GPS command to add a GPS clock source.

Notes:
Feeder type: Select COAXIAL.
Feeder length: Indicates the length of a GPS feeder. Calculate the feeder delay based on the length
of the GPS feeder to improve the clock precision. When the feeder exceeds 20 m, the precision will
decrease. When the feeder is shorter than 20 m, you do not need to specify the feeder type, which is
set to COAXIAL by default, and this parameter is set to 0 by default. If the distance exceeds 20 m,
set this parameter to the actual length.
GPS work mode: Set this parameter based on the locating system in use.
Clock source priority: Indicates the priority of a clock source. The value 1 indicates the highest
priority. The value 4 indicates the lowest priority.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 22


GPS Clock Source Configuration

Run the SET CLKMODE command to set the clock working mode.

Notes:
The MODE parameter indicates the working mode of the system clock. The value MANUAL indicates that a clock source
must be specified by the user. The value AUTO indicates that the system automatically selects a clock source based on
the priority and availability of the clock source. The value FREE indicates that the system clock works in free running
mode, that is, the system clock does not trace any clock source.
The value AUTO is recommended. If this parameter is set to MANUAL, you must specify an available clock source.

Run the SET CLKSYNCMODE command to set the clock synchronization mode.

Note:
TIME must be selected in the LTE TDD mode. Otherwise, the system clock signal cannot work properly.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 23


1588 Clock Source Configuration

Run the ADD IPCLKLINK command to add an IP clock link.

To achieve time synchronization for 5G NR in TDD mode, set Clock Net Mode to L2_MULTICAST
and Profile Type to G.8275.1.

Priority: Indicates the priority of a clock source. The value 1 indicates the highest priority. The value
4 indicates the lowest priority.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 24


1588 Clock Source Configuration
Run the SET CLKMODE command to set the clock working mode.

Notes:
The MODE parameter indicates the working mode of the system clock. The value MANUAL indicates that a clock source
must be specified by the user. The value AUTO indicates that the system automatically selects a clock source based on
the priority and availability of the clock source. The value FREE indicates that the system clock works in free running
mode, that is, the system clock does not trace any clock source.
The value AUTO is recommended. If this parameter is set to MANUAL, you must specify an available clock source.

Run the SET CLKSYNCMODE command to set the clock synchronization mode.

Note:
TIME must be selected in the LTE TDD mode. Otherwise, the system clock signal cannot work properly.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 25


HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential
Thank you
www.huawei.com

You might also like