Training Course - 5G RAN3.0 Time Source & Clock Source Design

04/10/2024 Security Level:
5G RAN3.0
Time Source & Clock
Source Design
www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Objectives
After completing this course, you should be able to:
1. Understand the design rules for time and clock sources.
2. Understand the concepts of time synchronization and frequency
synchronization.
3. Understand related configurations.
4. Understand the characteristics and recommended policies of each
NR synchronization solution.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2

Contents
 Time Management
 Concept
 Selection and Configuration
 Clock Synchronization
 Requirements and Characteristics
 Basic Concepts and Principles
 Deployment Solution and Deployment
 Cases

Time Management Concepts
During the normal operation, wireless base stations are required to maintain an accurate NE time.
If NE time on the network is not synchronized, the impacts on network O&M are as follows:
 Problem location: When the NE reports alarms, the time is inconsistent with the log time. This may cause
confusion in problem location and dependency analysis.
 Accuracy of performance statistics: Inconsistency of the performance statistics collection time occurs.
This may lead to confusion between performance report and traffic-related analysis.
 Wrong or missing triggering of scheduled tasks: For example, a license may take effect ahead of
schedule.
Currently, base stations use Universal Time Coordinated (UTC).

 Design criteria: 1. Customer requirements for time sources
2. Type of available time synchronization server onsite
 If a customer has no special requirement, the time source is selected in the following sequence:
1. GPS
2. Dedicated NTP server provided by the customer
3. U2020 (which can be set and used as the NTP server. An NTP server of the customer
is preferred. Use the U2020 only if the customer does not have an NTP server.)

GPS Time Source Design
GPS Time Source Overview
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 NTP
signals and collect the UTC-based standard time packet
information, with precision to nanosecond. This U2020

Base
time source is more accurate than the NTP and station
Base
SNTP time sources. station
The base station time is set to synchronize with
the GPS time every 30 minutes.
Base
station
Advantages and Disadvantages

 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.

GPS Time Source Configuration
1. Set a time source.
2. Add a GPS clock.
Script examples:
SET TZ: ZONET=GMT+0800, DST=NO;//Setting a time zone
SET TIMESRC: TIMESRC=GPS; //Setting 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;//Adding a GPS clock

NTP Time Source Design
The Network Time Protocol is a protocol (RFC1305) 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 device or the lower-layer server is
connected to the upper-layer server.
Recommended
Time Synchronization Parameter
NTP server Value
Time synchronization server NTP/U2020
U2020 or NTP client as a Time synchronization period

360 minutes
medium-level NTP server. (configurable)
Number of ports for the time
123
synchronization (configurable)
NTP client as a NTP client as a
medium-level medium-level
NTP server NTP server If an NTP server connects to a gNodeB on the network, the
NTP server can be configured as the time source to keep
NEs synchronized with the network. An gNodeB can be
configured with a maximum of 4 NTP servers. One of them
serves as the master server. If it fails to perform time
synchronization, the gNodeB can still synchronize time with
gNodeB gNodeB gNodeB gNodeB
another NTP server, enhancing reliability.

NTP Time Source Configuration
1. Set a time source.
2. Add an NTP client.
Script examples:
SET TZ: ZONET=GMT+0800, DST=NO;//Setting a time zone
SET TIMESRC: TIMESRC=NTP; //Setting the NTP server as the clock source
ADD NTPC: MODE=IPV4, IP= "10.10.10.1", PORT=123, SYNCCYCLE=60, AUTHMODE=PLAIN;//Adding an NTP client
In remote U2020 dual-server backup scenarios, each of the master and standby U2020 uses one IP address. For security reasons, both the master and
standby U2020 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;//Adding an NTP client
SET MASTERNTPS: MODE=IPV4, IP= "10.10.10.1"; //Setting 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.

Contents
 Time Management
 Concept
 Cases

Why Do Wireless Devices Need Clock Synchronization?
Wireless services require that the clock frequency or time difference between base stations
be within a proper range. However, internal crystal oscillators in wireless devices cannot
meet this requirement.
Internal crystal
Crystal Oscillator Level on RAN side oscillators in wireless Clock Synchronization Requirements of Basic
Clock Level Lowest Maximum
devices cannot meet Services on RAN Side
service requirements.
Precision Frequency Offset Devices on Synchronization Requirements
3 ±4.6 ppm 0.02 ppm/day RAN side Frequency Time
Synchronization Synchronization
Base station ±0.05 ppm ±1.5 us
Purpose of clock synchronization on base stations:

 For an FDD system, frequency synchronization is maintained between base stations to ensure
minimum power consumption of UEs during movement.
 For a TDD system, if the time is not synchronized, the interference between UEs and between
base stations may affect the KPIs of wireless services.
 Coordination among multiple base stations or reducing inter-site interference can improve
system capacity.

What Is Clock Synchronization?
Clock synchronization:
 There is a local clock reference source, but offset will occur. Clock synchronization is a process of calibrating the offset.
 Our watch needs to be manually calibrated after a period of time.
 The time on our mobile phone automatically follows the current time when the network is available.
 Clock synchronization is classified into time synchronization and frequency synchronization.
 During time synchronization, the absolute time of clock A is the same as that of clock B.
 During frequency synchronization, the absolute time of clock A is different from that of clock B, but the time difference
between clock A and clock B is always the same, for example, 6 hours.
Time synchronization: The clock speed is the Frequency synchronization: The clock speed
same and the start time is the same. is the same but the start point is different.
A A
3:00 4:00 7:00 10:00 3:00 4:00 9:00 10:00
B B
3:00 4:00 7:00 10:00 9:00 10:00 15:00 16:00
Time synchronization, also known as time-of-day Frequency synchronization: Two signals have
the same frequency or maintain a fixed ratio.
synchronization, refers to synchronization in absolute
Phases and frequencies may be different.
time. It requires that the start time of the clock signals for
a device keeps consistent with that of the UTC time.

Contents
 Time Management
 Concept
 Cases

Support for 5G Clock Synchronization
Synchronization Source Synchronization Mode

GPS Frequency and time synchronization are supported.
BeiDou Frequency and time synchronization are supported.
IEEE1588 V2 Frequency and time synchronization are supported.
Synchronous Ethernet Frequency synchronization is supported.
(SyncE)
IEEE1588 V2 + SyncE Frequency and time synchronization are supported.

Synchronization with GPS
GPS includes: United States' GPS, Russia's GLONASS, and China's BeiDou. The GPS can provide accurate
positioning, navigation, and timing services for ground targets around the world. Huawei gNodeB supports the GPS,
GLONASS, second-generation BeiDou. A gNodeB can simultaneously trace up to 3 or 4 satellites.
 If a gNodeB synchronizes with the GPS clock, it

obtains synchronization signals from the satellite
synchronization system by connecting a board
equipped with a satellite card to the external GPS
antenna system.
 If a gNodeB synchronizes with the RGPS clock, it
obtains synchronization signals from the satellite
synchronization system by connecting the USCU
board to the external RGPS antenna system.
Advantages and disadvantages:

 Advantages:
 Accurate UTC time information, time synchronization, and frequency synchronization are supported.
 Disadvantages:
 The GPS receiver needs to be configured, leading to high costs.
 The GPS antennas require excellent air horizon. The antenna location is difficult to select. gNodeBs must meet
the GPS signal receive conditions and engineering requirements. For details, see the GPS Satellite Antenna
System Quick Installation Guide.

Synchronization with IEEE 1588v2
IEEE 1588v2 is a protocol of precise time synchronization defined by IEEE and ITU. It is called "A Precision Clock
Synchronization Protocol for Networked Measurement and Control Systems", and also referred to as PTP. IEEE1588
V2 applies to Ethernet transport networks. IEEE1588 messages are transferred between primary and secondary clock
equipment. To achieve frequency or time synchronization between the equipment, accurate time stamps are used to
calculate the offset of time and frequency.
The main NEs involved in an IEEE 1588v2 network include the gNodeB, clock server, and intermediate transmission
device. The clock servers can use the GPS clock, BITS clock, or line clock as the clock source.
The following table lists the profile types complying with IEEE 1588v2.
Profile Type Sync Mode Description
1588v2 (Huawei Time and Huawei proprietary protocol

proprietary) L3 frequency
unicast synchronization
1588v2 16.1 L3 Time and If the interconnected equipment does not support
unicast frequency G.8265.1, this protocol can be used.
synchronization
1588 v2 L2 Time The IEEE standard mainly applies to the industrial
multicast synchronization control field.
ITU-T G.8275.2 Time Used for FDD base stations

L3 unicast synchronization
ITU-T G.8275.1 Time A profile for TDD and defined by the ITU-T. This
L2 multicast synchronization 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.8265.1 Frequency In this profile, the intermediate network does not
L3 unicast synchronization need to support 1588v2, and timing packets are
transmitted transparently. Only the devices on both
ends need to support 1588v2. For LTE FDD, this
profile requires inter-site time synchronization.

Synchronization with SyncE
SyncE is a synchronization technology that carries and recovers frequency information based on physical
layer code streams. SyncE is not supported by FDD gNodeBs and
complies with the ITU-T G.8261, ITU-T G.8262, and ITU-T G.8264 protocols.
gNodeBs support clock quality levels identified by SSMs.
Clock Quality Description Whether

Levels the Clock
Identified by Source Is
SSMs Available
QL-PRC A clock source at the Yes
PRC level is used.
QL-SSU-A A tandem office slave Yes
clock at the SSU-A level
is used.
QL-SSU-B An end office slave clock Yes
at the SSU-B level is
used.
QL-SEC/QL- A reference clock at the No
EEC1/QL-EEC2 SEC/EEC1/EEC2 level
is used.
Advantages and Disadvantages

 Advantages: No extra devices are required, saving networking costs. High reliability, not affected by network load changes
 Disadvantages: The synchronization precision depends on the synchronization performance of the entire network. Time
synchronization is not provided.

Synchronization with 1588v2+SyncE
A base station accesses both the IEEE 1588v2 and SyncE clock sources at the same time. 1588v2
provides time synchronization and SyncE provides frequency synchronization. The SyncE
frequency stability is used to enhance the robustness and holding capability of time synchronization.
When the 1588v2 clock is faulty, the SyncE clock is used to maintain the current phase. The clock
can remain in locked mode (duration ≤ 24 hours). The gNodeB clock enters the holdover mode only
when both clock sources are unavailable.

Contents
 Time Management
 Concept
 Cases

Recommended 5 GHz Clock Deployment Solution
Suggestions on clock deployment in typical scenarios:
 Based on whether there are existing time synchronization resources, deployment scenarios
are classified into:
 An existing GPS is available.
 An existing GPS is unavailable and a new clock source is required.
 Suggestions on clock deployment in typical scenarios:
Second-Choice
Scenario First-Choice Solution Description
Solution
GPS is mainly used, Only deploy a GPS if customers are concerned about
With an existing
and 1588v2 is used as GPS high investment and long period for enabling IEEE
GPS
a supplement. 1588v2.
Consider the second-choice solution if

Dual 1588v2 1. Customers are sensitive to security.
GPS is mainly used, 2. The 1588v2 network is mature.

Without an existing
and 1588v2 is used as
GPS Consider the second-choice solution if
a supplement.
1. Customers are not sensitive to security.
GPS
2. Customers are concerned about high investment
and long period of deployment.

GPS Configuration
 Hardware Requirements
 gNodeBs must be configured with a UMPTe board that is equipped with a GPS satellite
card, or USCU. For details on the satellite cards supported by BBU boards, see BBU5900
Hardware Description.
 The GPS has been installed as required.
 GPS Configuration
1. Add a GPS clock source.
2. Set Time Source to GPS.

GPS Configuration
3. Set the clock synchronization mode. Time synchronization is used as an example. (Time
Synchronization Mode must be set to TIME in a TDD system. Otherwise, system clock signals
cannot work properly.)
4. Set the clock working mode.
Note:
Clock Working Mode indicates the working mode of the system clock. MANUAL indicates that a clock source
must be specified by the user. AUTO indicates that the system automatically selects a clock source based on the
priority and availability of the clock source. FREE indicates that the system clock works in free-running mode, that
is, the system clock does not trace any reference clock source. AUTO is recommended. If MANUAL is required,
you need to select an available clock source.

GPS Configuration [Confidential]
5. Set the clock holdover time.
Run the following command to change the holdover duration to 8 hours (the
default value is 24 hours).
MOD GNODEBPARAM: GpsFailLfHoldoverDuration=8;
Note:
For the China region:
• Retain the default value without changing it.
For regions outside China:

• If the UMPTe board is used, you are advised to change the value to 8 hours as the UMPTe board
ensures 8-hour normal operation of the base station in holdover mode. If the value is not changed,
inter-site interference may occur due to clock deviation after the base station has stayed in
holdover mode for eight hours.
• If the UMPTg board is used, you are advised to retain the default value 24 hours.

Page 22
GPS Configuration
 Activation Verification
- FDD:
1. After configuring a GPS clock for the gNodeB, wait approximately 5 minutes.
2. Run the DSP CLKSTAT command to query the clock source status. If the value of Current
Clock Source is GPS Clock and the value of PLL Status is Locked, the GPS has been
activated.
- TDD:
1. After configuring a GPS clock for the gNodeB, wait approximately 5 minutes.
Clock Source is GPS Clock and the value of PLL Status is Locked, the GPS has been
activated. Wait 30 minutes until the cell establishment is complete.

1588v2 Configuration
 Networking Requirements
 The L3 unicast mode cannot coexist with the L2 multicast mode. If the L2 multicast mode is used, all
intermediate equipment between gNodeBs and an IEEE1588 V2 server must support this mode.
 The IEEE1588 V2 clock is not recommended if the transmission network frequently experiences delay variation
or packet loss.
Additional requirements for time synchronization:
 All intermediate equipment between gNodeBs and an IEEE1588 V2 clock server must support the BC or TC
function defined in IEEE1588 V2.
 Delay measurement and delay compensation must be performed for all transmission interfaces of all
intermediate transmission equipment including L3 and L2 routers. The compensation value must be set again if
routes or transmission paths change.
 1588v2 Deployment Configuration

1. Add an IP clock link.

2. Set the clock synchronization mode (time synchronization as an example)
3. Set the clock synchronization mode.
Note:
Clock Working Mode indicates the working mode of the system clock. MANUAL indicates that a clock source
must be specified by the user. AUTO indicates that the system automatically selects a clock source based on the
priority and availability of the clock source. FREE indicates that the system clock works in free-running mode, that
is, the system clock does not trace any reference clock source. AUTO is recommended. If MANUAL is required,
you need to select an available clock source.

- FDD:
1. After configuring an IEEE1588 V2 clock as the gNodeB clock source, wait about 30 minutes
in scenarios with good transmission quality.
Clock Source is IP Clock and the value of PLL Status is Locked, the 1588v2 has been
activated.
- TDD:
1. After configuring an IEEE1588 V2 clock as the gNodeB clock source, wait about 30 minutes
in scenarios with good transmission quality.
Clock Source is IP Clock and the value of PLL Status is Locked, the 1588v2 has been
activated.

SyncE Configuration
 All the intermediate transmission devices, such as hubs and LAN switches, must be capable of
transparent transmission or regeneration of clock signals at the physical layer.
 SyncE Configuration
1. Set the clock working mode (SyncE supports only frequency synchronization).
2. Add a SyncE clock link.

SyncE Configuration
1. After configuring a SyncE clock for the gNodeB, wait about 5 minutes in scenarios with
good transmission quality.
Clock Source is SyncEth Clock and the value of PLL Status is Locked, the feature has
been activated.

1588+SyncE Configuration
 All requirements for enabling IEEE 1588 and SyncE are met.
 The IEEE1588 V2 server and SyncE must extract clock signals from the same clock source and connect
to the gNodeB using the same port.
 1588+SyncE Configuration
1. Set the clock working mode (only time synchronization is supported).
2. Add a SyncE clock link by referring to SyncE configuration.

3. Add an IP clock link by referring to 1588v2 configuration.

1588+SyncE Configuration
1. After configuring the combination of IEEE1588 V2 and synchronous Ethernet as the
gNodeB clock source, wait about 30 minutes in scenarios where the transmission quality is
good.
Clock Source is SyncEth Clock+IP Clock and the value of PLL Status is Locked, the
feature has been activated.

Contents
 Time Management
 Concept
 Cases

GPS Cases
GPS
1588 not activated 1588 not activated
1588 not activated
Each gNodeB is deployed with a GPS one after another.

For details about how to configure the GPS, see the preceding sections.

1588 Cases
ePRTC 1588 is used to provide time synchronization.
±30 ns
ePRTC ePRTC
Step 1: Deploy the time server on the CO900
ePRTC ePRTC and connect to the GPS clock source.
CO11
Ensure that the time server is available.
OTN OTN Step 2: The high-precision time server
(terrestrial clock source) is deployed on the
1588
CO11 to provide backup for the CO900
GPS
clock source.
OTN OTN
Step 3: The CO11 high-precision time server
OTN
is connected to the network to support
mutual monitoring and independent
±100 ns
±200 ns
PRTC OSC/BC
CO900 operation. This enables a clock source
1588
ASG
backup group to ensure stability and
reliability.
1588
Switch
For details about how to configure 1588 on
Base station Base station the base station side, see the preceding
sections.

Handling NR Clock Faults
If a base station does not have an internal clock reference and an external clock source is available, the
base station unconditionally trusts and uses the external clock source. When the clock source is faulty, the
base station is in the clock holdover state.
When a typical clock fault occurs, a clock alarm is reported. The following three methods are available to handle the fault:
1. Run the DSP command to check whether the clock configuration and clock status are correct.
Run the DSP CLKSTAT command to check the status of the current clock source. If the status is normal, the clock signals are
normal. Other abnormal states include: loss, unavailable, jitter, unknown, excessive frequency deviation, large phase deviation,
different clock reference sources, and mismatch between the current clock source and the BTS clock synchronization mode.
2. Check whether the clock counter values are normal.

Traced GNSS Satellites Measurement: This counter provides the number of GNSS satellites that can be traced. It helps users
identify GNSS cards that can trace few satellites. (In normal cases, at least 3-4 satellites are traced. Otherwise, the alarm "GPS
Locked Satellites Insufficient" is reported.)
1593835641 VS.GNSS.SatellitesTraced.0: Number of times no GNSS satellites are traced
1593835642 VS.GNSS.SatellitesTraced.1: Number of times one to three GNSS satellites are traced
1593835643 VS.GNSS.SatellitesTraced.2: Number of times four GNSS satellites are traced
1593835644 VS.GNSS.SatellitesTraced.3: Number of times five GNSS satellites are traced
1593835645 VS.GNSS.SatellitesTraced.4: Number of times more than five GNSS satellites are traced
1593835646 VS.GNSS.SatellitesTraced.Mean: Average number of traced GNSS satellites
Base Station Clock DA Measurement: This measurement unit measures the frequency offset of the external clock source.
1593835647 VS.Node.ClockDA.CurrentDA.Max: Maximum Current DA Value of the Base Station Clock
1593835648 VS.Node.ClockDA.CurrentDA.Min: Minimum Current DA Value of the Base Station Clock
1593835649 VS.Node.ClockDA.CenterDA: Center DA Value of the Base Station Clock
3. Perform a clock quality test by running the STR CLKTST command (for over 5 minutes) and then running the STP
CLKTST command).
This test is very important. You can observe the difference between the clock source and the 10 MHz crystal oscillator of the board.

Contents
 Clock Out-of-Synchronization Detection over the Uu Interface

 Background and Scenario
 Deployment Requirements and Constraints
 Procedure
 Troubleshooting

Background
 Requirements
 5G TDD requires strict time synchronization between base stations. Otherwise, severe
interference is caused to neighboring base stations.
 When a base station is connected to an external clock source, out of synchronization caused by
a large deviation in clock quality cannot be detected due to a lack of detection mechanism or
benchmark for comparison. If out of synchronization occurs, interference is caused.
 The interference caused by an out-of-synchronization base station has a large impact, but the
out-of-synchronization base station cannot be easily identified. The clock out-of-synchronization
detection function detects the synchronization between base stations over the Uu interface after
interference occurs, thereby quickly identifying out-of-synchronization base stations for manual
handling.
 Benefits
 Timely detects out-of-synchronization base stations to avoid quality incidents on the live
network.

Solution Introduction
Overall process:
Selection of Base
Interference Reporting Sequence Detection Silence Detection
Stations to Be Detected
The base station monitors the To narrow down the detection A suspected base station Silence detection is
uplink interference, and reports an range, suspected base stations to sends sequences during the performed in the downlink of
alarm to the U2020 to trigger the be detected are selected based on guard period (GP). If the a suspected base station to
clock out-of-synchronization the characteristics of the neighboring base stations can confirm whether the
detection procedure if the uplink interference symbols, strength, receive the sequence during suspected base station is an
interference exceeds a threshold. and quantity. the GP, the suspected base interference source base
station is synchronized. station based on the
Otherwise, the suspected base interference change of the
station may be out of neighboring base station.
synchronization. In this way,
the range of suspected base
stations is further narrowed
down.
• For all base stations on the entire network, interference triggering and cross detection are used to
improve detection accuracy and reduce false detection and missing detection.

Solution Introduction – Interference Reporting
Principles
Once clock out-of-synchronization occurs, the last symbol in uplink subframes of the synchronized
or out-of-synchronization base station is interfered. If a base station detects interference in the last
symbol of a subframe, clock out-of-synchronization may occur, and the base station needs to
initiate the handling process.
Out-of- In advance
synchronization
base station A
DL
35.7 us x 2 Interference
GAP
Reference base
station DL S UL DL
13 us
Interference
TAoffset
Lagging
Out-of- DL
synchronization TAoffset is far less than the GAP,
base station B
which is a bottleneck.
• The base station periodically checks whether the average interference of the last symbol in the last uplink subframe
reaches the threshold.
• The interference may increase in heavy-traffic scenarios, and the base station does not report interference in this
scenario by using algorithms.
Note 1: A higher threshold leads to a higher probability of missing detection but a lower probability of false detection. The threshold should
be set based on maintenance engineers' suggestions.
Note 2: The thresholds should be set to the same value for all base stations managed by the same EMS. You are not advised to separately
change the threshold of a single base station.

Solution Introduction – Selection of Base Stations to
Be Detected
Principles
The base station that reports interference may be an out-of-synchronization base station or a
neighboring base station. Therefore, the to-be-detected base stations selected on the U2020 must
include the base station with the strongest interference and the neighboring base station that has
the most intra-frequency neighboring cells of the interfering base station.
Region 1: Number of
interfered base stations Region 2: Number of Region 3: Number of
<= Minimum number of interfered base stations < interfered base stations >
base stations to be Half of the number of base Half of the number of base
detected stations to be detected stations to be detected
• If only one interfering base station exists, the base station is considered isolated and needs to be detected.
• If the number of the aggregated interfered base stations is small, the interfering base station and its neighboring base
stations are to be checked.
• If the number of aggregated interfered base stations exceeds the number of to-be-detected base stations, select the
base station with the strongest interference and the neighboring base stations with the most intra-frequency
neighboring cells of the interfering base station as the to-be-detected base stations.

Solution Introduction – Sequence Detection
• According to the principle of strict clock synchronization required by TDD systems, the to-be-detected
base station sends the characteristic sequence in the S subframe.
• If the neighboring base stations of the to-be-detected base station can normally receive the
characteristic sequence, the to-be-detected base station is synchronized.
• If the neighboring base stations cannot receive the characteristic sequence, the to-be-detected base
station is out of synchronization.
Assumption: The special detection sequence is transmitted in the GP of the

SA = 2 special subframe SSP.
The special detection sequence is received in the GP of the
special subframe SSP.

Solution Introduction – Silence Detection
Interference is caused when the out-of-synchronization base station transmits data in an incorrect
timing. If the interference to the neighboring base stations is eliminated after all downlink subframes are
silenced by the base station suspected to be out-of-synchronization, this suspected base station is
considered out-of-synchronization. If the interference persists, the suspected base station is considered
synchronized.
Silence Silence Silence
Silent base station
To-be-detected base station
To-be-detected base station
• If the silent base station keeps silent as indicated in the graph and the detected interference of
neighboring base stations also fluctuates as implied in the graph, the interference comes from the
silent base station and the silent base station is considered out-of-synchronization.

Hardware Dependency
Base station models

• 5900 series base stations
• 3910 series base stations
Boards
• Main control boards: UMPTe and UMPTg
• Baseband processing units: UBBPfw1, UBBPfw2, and UBBPg
RF modules
• The following RF modules support clock out-of-synchronization detection:
• AAU5310, AAU5313, AAU5613, AAU5324, AAU5270, AAU5619, AAU5272, AAU5634, AAU5331, and
AAU5636.
Note:
1. The 8T8R RRU does not support this function.
2. Micro and LampSite base stations do not support this function.

Main Constraints
• This function must be simultaneously enabled on both the U2020 and base stations.
• This function does not apply to scenarios where multiple base stations managed by the same
EMS are out-of-synchronization.
Reason: According to the feedback from the live network, clock out-of-synchronization does not occur on
multiple base stations at the same time. If this does occur, the interference is very complex, the base stations
to be detected cannot be effectively selected, and the detection cannot be performed normally. Therefore, this
scenario is not supported.
• This function does not apply to the scenario where a base station serves both synchronized
and out-of-synchronization cells.
Reason: Currently, clock out-of-synchronization detection is a base station-level function, and therefore does
not apply to this scenario.
• Out-of-synchronization base stations do not generate any interference to other base stations
or the interference does not reach a threshold.
Reason: Interference is too small for detection. For example, if an out-of-synchronization base station is far
away from other base stations, it may not interfere neighboring base stations and trigger the detection.
• This function does not apply to the scenario where out-of-synchronization base stations are
not configured with intra-frequency neighboring cells.
Reason: No intra-frequency neighboring base stations can be selected for joint detection.

Scenarios Prone to Missing or Incorrect Detection
The clock out-of-synchronization detection function includes sequence detection and
silence detection. The sequence detection identifies suspected out-of-synchronization base
stations, and silence detection locates the out-of-synchronization base station. The
sequence detection and silence detection become unavailable in the following scenarios:
 Sequence detection:
 The base station to be detected is far away from neighboring base stations to be detected. The
neighboring base stations cannot receive the detection sequence. The base station is suspected
to be out-of-synchronization.
Enable the clock out-of-synchronization detection only on base stations in a continuous coverage
area.
 If some base stations use different special subframe configurations, the sequences locate in
different positions in special subframe configurations. As a result, the neighboring base stations
cannot receive the sequences.
 Sequence detection cannot be performed on cells operating on the same frequency but with
different bandwidths, such as 10 MHz + 20 MHz.
 Silence detection:
 If interference caused by other faults is stronger than that caused by clock out-of-synchronization
during the silence detection, the silence detection cannot locate the out-of-synchronization base
station.

Overview of Configuration Operations
 Clock out-of-synchronization detection automatically monitors interference, triggers detection,

identifies out-of-synchronization base stations or base stations suspected to be out of
synchronization, and generate alarms.
 Maintenance or service personnel need to manually handle the alarm. If the alarm is not handled, the
alarm cannot be automatically cleared.
 The operation consists of three parts:

 Manual feature deployment
 Automatic detection and alarm reporting
 Manual post-alarm processing

Feature Activation – Operating Environment Requirements
 Clock synchronization must be achieved between the U2020 server and base stations.
 When the base station uses NTP time synchronization, no alarm related to NTP time
synchronization is reported.
 Log in to the U2020 client and view the system time, as shown in the preceding figures. Run the
DSP TIME command to query the time of any base station. If the time deviation between the
U2020 and the base station does not exceed 5s, time synchronization requirements are met.
(This step is optional and used to confirm whether the first requirement is met.)
 The base station for which this function is enabled serves at least one cell and is configured with
at least five intra-frequency neighboring cells that are served by different base stations. This
function is enabled for at least two neighboring base stations.

Feature Activation – Activation
 Clock out-of-synchronization detection takes effect only when it is enabled on both the U2020 and
base stations.
 Activation on the U2020 (this function is enabled by default on the U2020):
Log in to the U2020, choose SON > Clock Out-of-Sync Check > Parameter Settings, and select Clock out-of-
sync check, Send out-of-sync alarm, and Send suspicious out-of-sync alarm.
 Activation on the gNodeB (this function needs to be manually enabled. Running the following MML command
does not affect services):
• For detailed operations, see CME-based Feature Configuration.
• Using the MML command: Run the MOD GNODEBPARAM command to set ClkOutofsyncDetSwitch to
CLK_DETECT_SW-1 and set the detection thresholds to recommended values.
Example: MOD GNODEBPARAM: ClkOutofsyncDetSwitch =CLK_DETECT_SW-1, ClkOutofsyncIntrfRptThld = -
95, SilDetIntrfDiffThld =6;

Feature Activation – Activation Verification
 After this function is activated, wait 5 minutes, log in to the U2020, and choose SON > Clock Out-of-
Sync Check > Sequence Check. Perform manual sequence check (which does not affect services),
wait 3 to 13 minutes, and check the results. If the base station reports a message indicating
successful detection, this function has been successfully activated.
For details about the manual sequence detection, see the following pages.

Automatic Detection – Description
 The clock out-of-synchronization detection function automatically detects the out-of-synchronization
base station and reports an alarm. Operators need to perform subsequent operations manually.
Viewing Alarm information
• When the interference meets certain
conditions, this function is automatically
triggered to identify an out-of-
synchronization base station or a suspected
base station, and reports an alarm.
• If there is an out-of-synchronization or
suspected base station in the alarm list, view
the base station information on the U2020.
Viewing Out-of-Synchronization
Base Stations
• The base stations in the out-of-
synchronization base station list are
basically determined as out-of-
synchronization base stations.
• An alarm is reported as long as the list
contains a base station. After the base
station recovers and is manually removed
from the list, the alarm is automatically
cleared. The records in the list need to be
manually deleted by right-clicking them.
Viewing Suspected Out-of-

Synchronization Base Stations
• The base stations in the suspected list may
be out-of-synchronization.
• An alarm is reported as long as the list
contains a base station. After the base
station recovers and is manually removed
from the list, the alarm is automatically
cleared. The records in the list need to be
manually deleted by right-clicking them.

Manually Sequence Detection
Manual sequence detection is used to manually detect specific suspected base stations. It is recommended that a
maximum of 20 to-be-detected base stations be selected at a time. Sequence detection does not affect services.
Sequence detection

Manual Silence Detection
Manual silence detection is used to manually detect specific suspected base stations. Only one base station can be
detected at a time. Silence detection does not affect services.
Silence detection

Post-alarm Processing – Basic Processing Method
 The alarms for out-of-synchronization base stations and suspected base stations need to be cleared
manually.
 The procedure is as follows:
 Check whether interference occurs and KPIs deteriorate.
 Block the interference source base station to isolate the fault.
 Contact R&D engineers to locate and troubleshoot the faults.
 Activate the interference source base station after the fault is rectified.

Post-alarm Processing – Handling Out-of-
Synchronization Base Stations
 Check whether interference occurs and KPIs deteriorate due to air interface issues on the live
network. If not, automatic detection is triggered incorrectly.
 If interference occurs and then is eliminated automatically, the fault may be rectified due to the satellite card reset.
 In this case, the alarm is automatically cleared after the base station is manually removed from the out-of-
synchronization base station list.
 If the interference persists and KPIs continuously deteriorate, take the measures listed below.
 Start interference monitoring for the interfered base stations. Block all cells served by out-of-
synchronization base stations and then check whether the interference is eliminated.
Note: navigation path: Monitor -> Signaling Trace -> Signaling Trace Management -> NR -> Cell Performance
Monitoring -> Interference Detect Monitoring
 Isolate the base station that is out of synchronization. Then, check whether an alarm is reported
indicating a clock fault, and rectify the clock fault. If the fault is not related to hardware, cable
connections, external environments, or configuration errors, contact Huawei R&D engineers.
 Activate all cells served by the out-of-synchronization base station after the fault is rectified, and
check whether the interference increases.
 Manually remove the base station from the out-of-synchronization base station list. The alarm is
automatically cleared.

Post-alarm Processing – Handling Suspected Base
Stations
 Check whether interference occurs and KPIs deteriorate due to air interface issues on the live
network. If not, automatic detection is triggered incorrectly.
 If interference occurs and then is eliminated automatically, the fault may be rectified due to the satellite card reset.
 In this case, the alarm is automatically cleared after the base station is manually removed from the suspected
base station list.
 If the interference persists and KPIs continuously deteriorate, take the measures listed below.
 A suspected base station needs to be further confirmed based on alarms or events. Alternatively,
block the base station for isolation purposes.
 Export the alarm logs and event logs of the suspected base station and check whether clock-related alarms and
events are reported before and after the gNodeB Out of Clock Synchronization alarm is reported at the major
severity. If clock-related alarms and events are reported, the clock may be faulty. Perform the operations listed
below.
 After the preceding operations are complete, isolate the suspected base station by following the
instructions provided below.
 Start interference monitoring for the interfered base stations. Block all cells served by the suspected base station
and then check whether the interference is eliminated.
 After the fault is rectified, check the clock fault. If the fault is not related to hardware, cable connections, external
environments, or incorrect configurations, contact Huawei R&D engineers.
 Start all cells served by the out-of-synchronization base station after all faults are rectified, and check whether the
interference increases.
 Manually remove the base station from the suspected base station list. The alarm is automatically cleared.

Common Cases: Manual Sequence Detection –
No Available Frequencies
After selecting a base station to be

detected, click OK and select a
frequency in the displayed dialog box.
If there is no frequency available, the
selected base station is not configured
with intra-frequency neighboring cells.
In this case, check the neighboring
cell configurations.

Common Cases: Manual Sequence Detection – Others
 The Check Result column of the Silence Check Result table shows whether the base station is
synchronized or not. Data reported by the base stations in the joint detection is displayed in the Base
Station Report Result tab page. If the U2020 cannot determine whether the base stations are
synchronized or not, you need to determine the status by analyzing the data reported by the base
stations.
 When the execution result reported by the base station indicates timeout, there are two cases:
 If only one to-be-detected base station reports timeout, the base station may be an out-of-
synchronization base station. Timeout occurs because of asynchronization. In this case, select
only the base station, and perform detection again. If the execution is successful this time, and
that of all neighboring base stations time out, the base station is probably out-of-synchronization.
Silence detection needs to be performed for further confirmation.
 If the execution of multiple to-be-detected base stations timed out, the NTP time synchronization
is not achieved between the U2020 and NEs. Contact maintenance engineers for troubleshooting.
 The execution results reported by a base station indicate no suitable cells: All cells of the base
station do not support sequence detection. Try silence detection.

Common Cases: Manual Silence Detection –
No Interference Rejection Entry
 Silence detection can be completed only when interference changes. If the interference is lower than
a threshold, silence detection is not performed. Contact maintenance engineers to rectify the fault.

References
 Time Management Feature Parameter

Description
 Synchronization Feature Parameter Description

Thank you
www.huawei.com

Training Course - 5G RAN3.0 Time Source & Clock Source Design

Uploaded by

Copyright:

Available Formats

Training Course - 5G RAN3.0 Time Source & Clock Source Design

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Training Course - 5G RAN3.0 Time Source & Clock Source Design

Uploaded by

Copyright:

Available Formats

04/10/2024 Security Level:

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

Currently, base stations use Universal Time Coordinated (UTC).

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 4

information, with precision to nanosecond. This U2020

Advantages and Disadvantages

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 5

2. Add a GPS clock.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6

U2020 or NTP client as a Time synchronization period

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 7

2. Add an NTP client.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 8

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 9

Purpose of clock synchronization on base stations:

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 10

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12

Synchronization Source Synchronization Mode

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13

 If a gNodeB synchronizes with the GPS clock, it

Advantages and disadvantages:

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 14

1588v2 (Huawei Time and Huawei proprietary protocol

ITU-T G.8275.2 Time Used for FDD base stations

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15

gNodeBs support clock quality levels identified by SSMs.

Clock Quality Description Whether

Advantages and Disadvantages

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 16

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 17

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 18

Consider the second-choice solution if

GPS is mainly used, 2. The 1588v2 network is mature.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 19

2. Set Time Source to GPS.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 20

4. Set the clock working mode.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 21

5. Set the clock holdover time.

For regions outside China:

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 22

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 23

 1588v2 Deployment Configuration

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 24

3. Set the clock synchronization mode.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 25

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 26

2. Add a SyncE clock link.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 27

3. Set the clock working mode.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 28

2. Add a SyncE clock link by referring to SyncE configuration.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 29

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 30

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 31

1588 not activated 1588 not activated