11/15/23, 12:56 AM HedEx Startpage

5G RAN Feature Documentation

Product Version: 5G RAN1.0
Library Version: 02
Date: 2018-10-25

For any question, please contact us.

Copyright © Huawei Technologies Co., Ltd. 2018. All rights reserved.

Synchronization
Contents
5.3.1 Synchronization

5G RAN
Synchronization Feature Parameter Description
Issue 01

Date 2018-07-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2018. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 1/38

11/15/23, 12:56 AM HedEx Startpage
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.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website: http://www.huawei.com

Email: support@huawei.com

3.1 Contents
1 Change History
1.1 5G RAN1.0 01 (2018-07-30)
1.2 5G RAN1.0 Draft B (2018-06-30)
1.3 5G RAN1.0 Draft A (2018-03-30)

2 About This Document

2.1 General Statements
2.2 Features in This Document

3 General Principles
3.1 Frequency Synchronization
3.2 Time Synchronization
3.3 Difference Between Time Synchronization and Frequency Synchronization
3.4 Clock Quality Levels
3.5 Clock Startup Mode
3.5.1 Cold Startup
3.5.2 Warm Startup
3.6 Clock Working Mode
3.6.1 Free Running
3.6.2 Fast Tracking
3.6.3 Locked
3.6.4 Holdover
3.6.5 Working Mode Transition
3.7 Locking Duration
3.8 Common Synchronization Sources Supported by NR
3.9 gNodeB Requirements for Synchronization Accuracy

4 Synchronization Source Switching

4.1 Principles
4.2 Network Analysis
4.2.1 Benefits
4.2.2 Impacts
4.3 Requirements
4.3.1 Licenses
4.3.2 Software
4.3.3 Hardware
4.3.4 Networking
4.3.5 Others
4.4 Operation and Maintenance
4.4.1 Activation and Performance Optimization
4.4.1.1 Data Preparation
4.4.1.2 Using MML Commands
4.4.1.3 Using the CME
4.4.2 Activation Verification
4.4.3 Network Monitoring

5 Synchronization with GPS

5.1 Principles
5.2 Network Analysis
5.2.1 Benefits

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 2/38

11/15/23, 12:56 AM HedEx Startpage
5.2.2 Impacts
5.3 Requirements
5.3.1 Licenses
5.3.2 Software
5.3.3 Hardware
5.3.4 Networking
5.3.5 Others
5.4 Operation and Maintenance
5.4.1 Activation and Performance Optimization
5.4.1.1 Data Preparation
5.4.1.2 Using MML Commands
5.4.1.3 Using the CME
5.4.2 Activation Verification
5.4.3 Network Monitoring
5.4.4 Reconfiguration

6 Synchronization with BeiDou

6.1 Principles
6.2 Network Analysis
6.2.1 Benefits
6.2.2 Impacts
6.3 Requirements
6.3.1 Licenses
6.3.2 Software
6.3.3 Hardware
6.3.4 Networking
6.3.5 Others
6.4 Operation and Maintenance
6.4.1 Activation and Performance Optimization
6.4.1.1 Data Preparation
6.4.1.2 Using MML Commands
6.4.1.3 Using the CME
6.4.2 Activation Verification
6.4.3 Network Monitoring
6.4.4 Reconfiguration

7 IEEE1588 V2 Clock Synchronization

7.1 Principles
7.1.1 Time Synchronization
7.1.1.1 Network Clock Architecture
7.1.1.2 Delay Measurement
7.1.1.3 Applications
7.1.2 Frequency Synchronization
7.1.2.1 Network Clock Architecture
7.1.2.2 Encryption Process
7.1.2.3 Applications
7.1.3 Hybrid Synchronization
7.1.4 Interworking Between IEEE1588 V2-compliant Equipment from Different Manufacturers
7.2 Network Analysis
7.2.1 Benefits
7.2.2 Impacts
7.3 Requirements
7.3.1 Licenses
7.3.2 Software
7.3.3 Hardware
7.3.4 Networking
7.3.5 Others
7.4 Operation and Maintenance
7.4.1 Activation and Performance Optimization
7.4.1.1 Data Preparation
7.4.1.2 Using MML Commands
7.4.1.3 Using the CME
7.4.2 Activation Verification
7.4.3 Network Monitoring
7.4.4 Reconfiguration

8 Synchronous Ethernet
8.1 Principles
8.1.1 Network Clock Architecture
8.1.2 Applications
8.2 Network Analysis

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 3/38

11/15/23, 12:56 AM HedEx Startpage
8.2.1 Benefits
8.2.2 Impacts
8.3 Requirements
8.3.1 Licenses
8.3.2 Software
8.3.3 Hardware
8.3.4 Networking
8.3.5 Others
8.4 Operation and Maintenance
8.4.1 Activation and Performance Optimization
8.4.1.1 Data Preparation
8.4.1.2 Using MML Commands
8.4.1.3 Using the CME
8.4.2 Activation Verification
8.4.3 Network Monitoring
8.4.4 Reconfiguration

9 Combined Synchronization Sources

9.1 Principles
9.2 Network Analysis
9.2.1 Benefits
9.2.2 Impacts
9.3 Requirements
9.3.1 Licenses
9.3.2 Software
9.3.3 Hardware
9.3.4 Networking
9.3.5 Others
9.4 Operation and Maintenance
9.4.1 Activation and Performance Optimization
9.4.1.1 Data Preparation
9.4.1.2 Using MML Commands
9.4.1.3 Using the CME
9.4.2 Activation Verification
9.4.3 Network Monitoring
9.4.4 Reconfiguration

10 Comparison of Synchronization Technologies

11 Synchronization-related Alarms

12 Parameters

13 Counters

14 Glossary

15 Reference Documents

1 Change History

This section describes changes not included in the "Parameters", "Counters", "Glossary", and "Reference Documents" chapters. These changes include:

Technical changes
Changes in functions and their corresponding parameters

Editorial changes
Improvements or revisions to the documentation

5G RAN1.0 01 (2018-07-30)
This issue does not include any changes.

5G RAN1.0 Draft B (2018-06-30)

This issue introduces the following changes to 5G RAN1.0 Draft A (2018-03-30).

chnical Changes

Change Description Parameter Change

Added the reconfiguration of the clock synchronization mode from frequency None
synchronization to time synchronization. For details, see the following sections:
5.4.4 Reconfiguration
6.4.4 Reconfiguration
7.4.4 Reconfiguration

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 4/38

11/15/23, 12:56 AM HedEx Startpage
itorial Changes

None

5G RAN1.0 Draft A (2018-03-30)

This is the first release of this document.

2 About This Document

General Statements

rpose

Feature Parameter Description documents are intended to acquaint readers with:

The technical principles of features and their related parameters

The scenarios where these features are used, the benefits they provide, and the impact they have on networks and functions
Requirements of the operating environment that must be met before feature activation
Parameter configuration required for feature activation, verification of feature activation, and monitoring of feature performance

NOTE:
This document only provides guidance for feature activation. Feature deployment and feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve the desired gains, contact Huawei professional service engineers.

ftware Interfaces

Any parameters, alarms, counters, or managed objects (MOs) described in Feature Parameter Description documents apply only to the corresponding software release. For future
software releases, refer to the corresponding updated product documentation.

al Features

Trial features are features that are not yet ready for full commercial release for certain reasons. For example, the industry chain (terminals/CN) may not be sufficiently compatible.
However, these features can still be used for testing purposes or commercial network trials. Anyone who desires to use the trial features shall contact Huawei and enter into a
memorandum of understanding (MoU) with Huawei prior to an official application of such trial features. Trial features are not for sale in the current version but customers may try
them for free.
Customers acknowledge and undertake that trial features may have a certain degree of risk due to absence of commercial testing. Before using them, customers shall fully
understand not only the expected benefits of such trial features but also the possible impact they may exert on the network. In addition, customers acknowledge and undertake that
since trial features are free, Huawei is not liable for any trial feature malfunctions or any losses incurred by using the trial features. Huawei does not promise that problems with trial
features will be resolved in the current version. Huawei reserves the rights to convert trial features into commercial features in later R/C versions. If trial features are converted into
commercial features in a later version, customers shall pay a licensing fee to obtain the relevant licenses prior to using the said commercial features. If a customer fails to purchase
such a license, the trial feature(s) will be invalidated automatically when the product is upgraded.

Features in This Document

This document describes the following features.

Feature ID Feature Name Section

FBFD-010020 Synchronization 3 General Principles

4 Synchronization Source Switching
5 Synchronization with GPS
6 Synchronization with BeiDou

FOFD-010070 Network Synchronization 7 IEEE1588 V2 Clock Synchronization

8 Synchronous Ethernet

3 General Principles

Clock synchronization maintains a certain relationship between two or more signals in terms of frequency or time. In a digital communications network, synchronization ensures that
the clock frequency or time difference among communications equipment across the entire network is within a reasonable error range. In this way, synchronization prevents the
transmission performance deterioration caused by the incorrect timing of receiving or transmitting signals in the transmission system.
Clock synchronization consists of frequency synchronization and time synchronization. TDD networks adopt time division multiplexing and therefore require time synchronization to
minimize inter-base station and inter-UE interference.

Frequency Synchronization
Frequency synchronization means that the change frequencies of two signals are the same or maintain a fixed ratio. The phases or frequencies of the signals can be different. Figure
3-1 shows a frequency synchronization example, in which signals A, B, and C are frequency synchronization signals.

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 5/38

11/15/23, 12:56 AM HedEx Startpage
Figure 3-1 Frequency synchronization

NOTE:
In frequency synchronization, clock signals change periodically and do not contain time information.

Time Synchronization
Time signals are clock signals that contain time information, including year, month, date, hour, minute, and second. Currently, the Coordinated Universal Time (UTC) is used to
represent time information. It is a universal timing standard.
Time synchronization is also known as moment synchronization and implies the synchronization of the absolute time. It requires that the starting time of the clock signals for a device
keeps consistent with that of the UTC time. Figure 3-2 shows a time synchronization example, in which signals A and B are time synchronization signals while signals A, C, and D are
not.
Figure 3-2 Time synchronization

Difference Between Time Synchronization and Frequency Synchronization

Figure 3-3 shows an example of the difference between time synchronization and frequency synchronization.

Figure 3-3 Difference between time synchronization and frequency synchronization

As shown in Figure 3-3:

If the time of clock A and clock B is the same at every moment, they are in time synchronization.
If the time of clock A and clock B is different but the time difference maintains a fixed value (for example, six hours), they are in frequency synchronization.

Clock Quality Levels

Clocks can be classified into level-1 reference clock, level-2 clock, and level-3 clock based on the clock quality level. Clock equipment is layered according to the clock quality level
and constitutes a hierarchical clock synchronization network through transmission links, as shown in Figure 3-4.

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 6/38

11/15/23, 12:56 AM HedEx Startpage
Figure 3-4 Clock quality levels

As shown in Figure 3-4:

Level-1 reference clock: primary reference clock (PRC)/local primary reference (LPR) clock
PRC: usually a cesium or hydrogen clock to provide a high-accuracy clock source
LPR clock: usually a rubidium clock plus GPS satellite synchronization to provide a high-accuracy clock source

Level-2 clock: synchronization supply unit (SSU). A level-2 clock is equipped with a digital phase locked loop (DPLL) based on a rubidium clock, providing excellent tracing,
filtering, and holding performance. The level-2 clock is divided into:
Tandem office slave clock in SSU-A (primary SSU) level.
End office slave clock in SSU-B (second-level SSU) level.

Level-3 clock: Synchronous Digital Hierarchy (SDH) equipment clock (SEC). A level-3 clock is equipped with a DPLL based on a high-performance crystal oscillator. The
holding performance of the level-3 clock is lower than that of the level-2 clock. Clocks provided by network equipment are in SEC level.

Transmission equipment is usually connected as a ring. To prevent the clock of a higher-level node from tracing the clock of a lower-level node, reference clocks use Synchronization
Status Messages (SSMs) to indicate their clock quality levels.
The clock server uses level-1 reference clock. The base station clock is level-3 clock, and its upper-level clock must meet the requirements of level-2 clock. In principle, a lower-level
device must synchronize with its upper-level device to achieve clock synchronization.

Clock Startup Mode

Depending on whether the crystal oscillator of the clock source needs to be warmed up before it works normally, the clock startup modes are classified into the following:

Cold startup
Warm startup

3.5.1 Cold Startup

In cold startup mode, the crystal oscillator needs some time to warm up before working normally after the system clock enters the startup mode. When the system clock starts up:

If there are available reference clocks, the system clock enters the locked mode after the warm-up.
If there are no available reference clocks, the system clock enters the free running mode after the warm-up.

3.5.2 Warm Startup

In warm startup mode, the system clock immediately enters the locked mode after the system restarts without the need of turning off power supply. Warm startup is available only
when the system clock works in locked mode before the warm startup.

Clock Working Mode

After the crystal oscillator warms up, the clock enters one of the following working modes:

Free running
Fast tracking
Locked
Holdover

3.6.1 Free Running

A clock enters the free running mode in the following scenarios:

There are no available reference clocks after the crystal oscillator warms up.
Network reference clocks become unavailable and the unavailability duration exceeds the threshold specified by the holdover mode.

No clock source is configured for a base station before delivery, and therefore the base station directly enters the free running mode.
When the base station re-obtains and locks a network reference clock, the base station clock exits the free running mode.
An FDD base station can work properly in free running mode for 90 days in frequency synchronization.
A TDD base station cannot work in free running mode. After the base station enters the free running mode, cells served by the base station are automatically deactivated. These cells
are automatically activated only after the base station re-enters the locked mode.

3.6.2 Fast Tracking

A clock enters the fast tracking mode if the base station obtains a reference clock or if reference clocks become available but the phase offset exceeds a specified threshold.

If reference clocks become unavailable, the clock switches to the free running mode.
When the frequency offset of reference clocks is less than the traceable threshold but exceeds the locking threshold, the clock remains in fast tracking mode.
When the frequency offset of reference clocks is less than the locking threshold, the clock switches to locked mode.

3.6.3 Locked

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 7/38

11/15/23, 12:56 AM HedEx Startpage
The clock enters the locked mode in either of the following scenarios:

The base station obtains reference clocks and the frequency offset is less than the locking threshold.
The reference clocks become available when the base station clock runs in holdover mode, and the phase offset is less than the frequency offset threshold.

The locked mode is the normal working mode of the clock for gNodeBs. When the clock enters the locked mode, its jitter, frequency offset, and accuracy meet the requirements for
the normal operation of the system. In addition, the frequency control values of the crystal oscillator are updated only when the frequency of reference clock signals is within the
normal range. If the frequency is beyond the normal range, the update process stops.

3.6.4 Holdover
A clock enters the holdover mode when reference clocks become unavailable, or the phase offset or frequency offset exceeds the locking threshold.
In time synchronization mode, the period of time during which a base station can work properly in holdover mode is related to the crystal oscillator type.
An FDD base station can work properly in holdover mode for 90 days in frequency synchronization.

3.6.5 Working Mode Transition

The clock working mode can be switched when certain conditions are met. Figure 3-5 shows the transition of the gNodeB clock working modes.
Figure 3-5 Transition of the clock working modes

1. When there are no available reference clocks after the crystal oscillator warms up, the clock enters the free running mode.
2. When a base station receives available clock signals or reference clocks become available, the clock switches from the free running mode to the fast tracking mode.
3. When the frequency offset of the reference clocks for the base station is less than the locking threshold, the clock switches from the fast tracking mode to the locked mode.
4. The clock enters the holdover mode when either of the following conditions is true:
The clock source is faulty.
The phase offset exceeds the locking threshold.
The frequency offset exceeds the locking threshold.

5. When the duration for the clock in holdover mode exceeds the specified threshold, the clock switches from the holdover mode to the free running mode.
6. When reference clocks become available and the phase offset is less than the locking threshold, the clock switches from the holdover mode to the locked mode.
7. When reference clocks become available but the phase offset exceeds the locking threshold, the clock switches from the holdover mode to the fast tracking mode.
8. When the base station detects that the frequency offset is greater than the frequency offset threshold, the clock switches from the locked mode to the fast tracking mode.
9. When the base station detects that the reference clocks become unavailable, the clock switches from the fast tracking mode to the free running mode.
10. When the base station detects that the frequency offset is less than the traceable threshold but greater than the locking threshold, the clock remains in fast tracking mode.
11. When the base station detects that the frequency offset is less than the locking threshold, the clock remains in locked mode.
12. When the duration for the clock in holdover mode does not exceed the specified threshold, the clock remains in holdover mode.

Locking Duration
If the crystal oscillator frequency of a gNodeB is significantly deviated from that of a reference clock or the quality of the transport network is poor, the maximum fast tracking
durations for reference clocks are described as follows:

For IEEE1588 V2 clock: Considering jitters in IP transport networks, a reference clock can be locked within 30 minutes in normal cases. If the reference clock cannot be
locked within 3200 minutes, the gNodeB reports ALM-26262 External Clock Reference Problem.
For GPS, BeiDou, or other clocks: The reference clock can be locked within 2 minutes in normal cases. If the reference clock cannot be locked within 6 minutes, the gNodeB
reports ALM-26262 External Clock Reference Problem.

Common Synchronization Sources Supported by NR

Table 3-1 lists the common synchronization sources available to gNodeBs. TDD gNodeBs support only time synchronization.

Table 3-1 Reference clocks available to gNodeBs

Synchronization Source Supported Synchronization Mode Description

Synchronization with GPS Frequency synchronization and time synchronization For details, see 5 Synchronization with GPS.

Synchronization with BeiDou Frequency synchronization and time synchronization For details, see 6 Synchronization with BeiDou.

IEEE1588 V2 clock Frequency synchronization and time synchronization For details, see 7 IEEE1588 V2 Clock Synchronization.

Synchronous Ethernet Frequency synchronization For details, see 8 Synchronous Ethernet.

IEEE1588 V2 clock+Synchronous Frequency synchronization and time synchronization For details, see 9 Combined Synchronization Sources.
Ethernet

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 8/38

11/15/23, 12:56 AM HedEx Startpage
gNodeB Requirements for Synchronization Accuracy
The clock accuracy denotes the maximum offset of a gNodeB clock from a reference clock. 3GPP specifications define the following clock accuracy requirements of gNodeB
synchronization:

If time synchronization is used, gNodeBs must be time-synchronized within the accuracy of ±1.5 µs.
If frequency synchronization is used, gNodeBs (macro base stations) must be frequency-synchronized within the accuracy of ±0.05 ppm. FDD gNodeBs support frequency
synchronization. If a gNodeB works in frequency synchronization mode, services dependent on time synchronization cannot take effect on FDD networks. For details about
time synchronization requirements, see related feature documents.

4 Synchronization Source Switching

Principles
When TASM.MODE is set to MANUAL, gNodeBs work in manual clock source switchover mode. When TASM.MODE is set to AUTO, gNodeBs work in automatic clock source
switchover mode.
When clock sources are normal, the clock source with the highest priority works as the master clock source, and other clock sources work as backup clock sources. If the master
clock source becomes abnormal (due to insufficient GPS satellites searched, excessive clock source frequency offsets, or clock link interruption), the backup clock source with the
highest priority is manually or automatically switched to the master state, and the abnormal clock source becomes a backup clock source after it recovers.

NOTE:
In time synchronization mode, the GPS clock is more reliable than the IEEE1588 V2 clock. In dual-reference-clock mode of GPS+IEEE1588 V2, the GPS clock has a higher priority
than the IEEE1588 V2 clock. When the GPS clock becomes faulty, gNodeBs automatically switch to the IEEE1588 V2 clock. When the GPS clock recovers, gNodeBs automatically
switch back to the GPS clock, regardless of whether the IEEE1588 V2 clock is normal.

A gNodeB in automatic clock source switchover mode cannot share clock sources with other gNodeBs.
A gNodeB in manual clock source switchover mode will lose the reference clock if the link to the manually selected reference clock becomes faulty.
If the reference clock is not locked before the reference clock becomes unavailable, the clock in the gNodeB works in the free running state after the reference clock
becomes unavailable.
If the reference clock is locked before the reference clock becomes unavailable, the clock in the gNodeB works in the holdover state after the reference clock becomes
unavailable.
If the link to the reference clock is not restored for a long time, the clock in the gNodeB finally enters the free running state.

In dual-reference-clock mode involving IEEE1588 V2, the clock sources cannot be automatically switched to another time reference source or frequency reference source.

Both manual and automatic clock source switchovers are supported in time synchronization mode. The supported clock sources are as follows:

Clock sources supporting manual clock source switchovers

GPS
IEEE1588 V2

Clock sources supporting automatic clock source switchovers

GPS and IEEE1588 V2

Both manual and automatic clock source switchovers are supported in frequency synchronization mode. The supported clock sources are as follows:

Clock sources supporting manual clock source switchovers

GPS
IEEE1588 V2
Synchronous Ethernet

Clock sources supporting automatic clock source switchovers

GPS and Synchronous Ethernet
Synchronous Ethernet and IEEE1588 V2
GPS and IEEE1588 V2

Network Analysis

4.2.1 Benefits
If the configured reference clock becomes unavailable, it can be switched to another available reference clock.

4.2.2 Impacts

twork Impacts

None

nction Impacts

None

Requirements

4.3.1 Licenses
None

4.3.2 Software

erequisite Functions

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 9/38

11/15/23, 12:56 AM HedEx Startpage

Function Name Function Switch

Clock sources such as GPS and IEEE1588 V2 None

utually Exclusive Functions

None

4.3.3 Hardware

se Station Models

5900 series base stations

oards

Board requirements vary depending on the clock source in use. For details, see board requirements for each clock.

F Modules

N/A

4.3.4 Networking
Before you set the clock working mode, ensure that a reference clock is available and the networking mode matches the clock source.
The manual mode is used in either of the following situations:

A clock source needs to be specified or there is only one available clock source. The specified reference clock must have been configured. In manual mode, base stations
cannot automatically select another clock source.
In a separate-MPT multimode base station, each RAT supports only one clock source type.

4.3.5 Others
None

Operation and Maintenance

4.4.1 Activation and Performance Optimization

4.4.1.1 Data Preparation

This section describes the parameter configuration for clock source switching from an IEEE1588 V2 clock to a GPS clock.
The details about how to configure a GPS clock and specify the clock priority are described in 5.4.1.1 Data Preparation.
The details about how to configure an IEEE1588 V2 clock link and specify the clock priority are described in 7.4.1.1 Data Preparation.
Configure the clock working mode, reference clock source, and reference clock source No. by running the SET CLKMODE command.
Configure the clock synchronization mode by running the SET CLKSYNCMODE command.
Table 4-1 Key parameters in the TASM MO

Parameter Name Parameter ID Setting Notes

Clock Working Mode TASM.MODE It is recommended that this parameter be set to AUTO in time
synchronization mode and to MANUAL in frequency synchronization
mode. TDD gNodeBs support only time synchronization.

Selected Clock Source TASM.CLKSRC Set this parameter to GPS.

Clock Source No. TASM.SRCNO Set this parameter to the link number specified when the clock link was
created.

Clock Synchronization Mode TASM.CLKSYNCMODE Set this parameter based on network requirements.

4.4.1.2 Using MML Commands

//Adding an IP clock link
ADD IPCLKLINK: LN=0, ICPT=PTP, SN=7, CNM=L2_MULTICAST, DELAYTYPE=E2E, PRI=1, MACMODE=NO, PROFILETYPE=1588V2;
//Adding a GPS clock link
ADD GPS:GN=0,CN=0,SRN=0,SN=7,CABLE_LEN=1000,MODE=GPS,PRI=2;
//(Optional) Setting the clock working mode to automatic
SET CLKMODE:MODE=AUTO;
//(Optional) Setting the clock working mode to manual
SET CLKMODE:MODE=MANUAL,CLKSRC=GPS,SRCNO=0;
//Setting the clock synchronization mode
SET CLKSYNCMODE:CLKSYNCMODE=TIME;

4.4.1.3 Using the CME

For detailed operations, see CME-based Feature Configuration.

4.4.2 Activation Verification

Before activating this function, run the DSP CLKSTAT command to query the clock source status. If the value of Current Clock Source is IP Clock and the value of PLL Status is
Locked, this function has taken effect.
After this function is enabled, if the IP clock is unavailable due to an IP clock server fault or a transmission link interruption, the clock source is switched to a GPS clock. Wait about 15
minutes. (The wait time varies depending on the clock source after the switchover.) 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, this function has taken effect.

4.4.3 Network Monitoring

None

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 10/38

11/15/23, 12:56 AM HedEx Startpage

5 Synchronization with GPS

Principles
The GPS clock sources in this document include:

GPS
Remote Global Positioning System (RGPS)

GPS is a global satellite navigation system provided by the USA. It provides precise positioning, navigation, and timing services to objects on the earth around the world. The GPS
clock source is accurate to the microsecond. It supports both frequency synchronization and time synchronization.

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.

The GPS antenna system receives GPS signals at 1575.42 MHz and transmits the signals to the GPS satellite card. A gNodeB can simultaneously trace up to three or four satellites.
The GPS satellite card processes the signals and transmits them to the main clock module.
GPS synchronization supports both time synchronization and frequency synchronization, but requires investing in GPS, which is added during gNodeB deployment. For details on the
GPS signal receiving conditions and engineering requirements for gNodeB sites, see GPS Satellite Antenna System Quick Installation Guide in 5900 Series Base Station Product
Documentation.
The Global Navigation Satellite System (GLONASS) is provided by Russia and has similar implementation principles and functions as GPS. gNodeBs must be configured with a
board equipped with a GLONASS satellite card to support the GLONASS synchronization.

tworking Solution

Figure 5-1 shows the GPS or RGPS synchronization solution.

Figure 5-1 GPS or RGPS synchronization solution

nchronization Based on Signals from One to Three GPS Satellites

To implement GPS synchronization, a gNodeB requires signals from at least four GPS satellites. In special geographical environment such as densely populated urban areas, the
gNodeB may be able to receive signals from only one to three GPS satellites. In this case, you can enable GPS or RGPS synchronization based on signals from only one to three
GPS satellites. This synchronization mode requires accurate longitude, latitude, and altitude configuration of the gNodeB (for GPS synchronization) or RGPS device (for RGPS
synchronization).

Network Analysis

5.2.1 Benefits
Wired networks do not affect the synchronization with GPS or RGPS clocks. These clocks are recommended when the wired network bandwidth is limited, or when wired networks
frequently experience delay variation or packet loss.

5.2.2 Impacts

twork Impacts

None

nction Impacts

None

Requirements

5.3.1 Licenses

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 11/38

11/15/23, 12:56 AM HedEx Startpage
None

5.3.2 Software

erequisite Functions

None

utually Exclusive Functions

None

5.3.3 Hardware

se Station Models

5900 series base stations

oards

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 BBU
Hardware Description.

F Modules

None

5.3.4 Networking
For details, see the networking solution in 5.1 Principles.

5.3.5 Others
Other requirements are as follows:

gNodeBs must be configured with a GPS or an RGPS receive device to support the GPS or RGPS clock.
An external GPS or RGPS antenna must be available at the site from which the GPS or RGPS signals are received.
The external GPS or RGPS antenna should be located in a sparsely populated area, or on the tallest buildings in a specified area, because at least four satellites are required
for synchronization with the GPS or RGPS clock. This clock source is not recommended for low spots in urban high-density building areas or mountainous areas.
The GPS clock source is not recommended in rainy or foggy areas because the GPS signals are susceptible to bad weather.
If a TDD gNodeB synchronizes with the GPS or RGPS clock using signals from only one to three GPS satellites, the longitude, latitude, and altitude information for the
gNodeB GPS or RGPS device must be accurately configured. Otherwise, the synchronization accuracy is affected.

Operation and Maintenance

5.4.1 Activation and Performance Optimization

5.4.1.1 Data Preparation

The following tables describe the key parameters that must be set for synchronization with a GPS or an RGPS clock.

1. Configure a GPS or an RGPS clock.

Table 5-1 Key parameters in the GPS MO

Parameter Name Parameter ID Setting Notes

Cabinet No. GPS.CN Set these parameters based on the board to which the GPS or RGPS
feeder is connected. Before configuring a GPS or RGPS clock, ensure
Subrack No. GPS.SRN that the board to which the GPS or RGPS feeder is connected has been
configured.
Slot No. GPS.SN

GPS Clock No. GPS.GN If only one GPS or RGPS clock source is required, set this
parameter to 0.
If two GPS or RGPS clock sources are required, set this
parameter to 0 for one clock source and to 1 for the other.

Cable Length GPS.CABLE_LEN If the feeder length cannot be measured, the difference between the value
of this parameter and the actual length must be less than or equal to 20
m. Otherwise, the clock accuracy is affected.

GPS Work Mode GPS.MODE Set this parameter based on the type of a satellite card.

Priority GPS.PRI When two or more clock sources are used, a smaller value of this
parameter indicates a higher priority.

2. Configure the clock working mode, reference clock source, and reference clock source No. by running the SET CLKMODE command.
Configure the clock synchronization mode by running the SET CLKSYNCMODE command.

Table 5-2 Key parameters in the TASM MO

Parameter Name Parameter ID Setting Notes

Clock Working Mode TASM.MODE It is recommended that this parameter be set to AUTO in time
synchronization mode and to MANUAL in frequency synchronization
mode. TDD gNodeBs support only time synchronization.

Selected Clock Source TASM.CLKSRC Set this parameter to GPS.

Clock Source No. TASM.SRCNO Set this parameter to the link number specified when the clock link was
created.

Clock Synchronization Mode TASM.CLKSYNCMODE Set this parameter as required.

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 12/38

11/15/23, 12:56 AM HedEx Startpage
3. Configure the longitude, latitude, and altitude information for the gNodeB GPS or RGPS device if a TDD gNodeB obtains signals from only one to three GPS satellites.

Table 5-3 Key parameters in the GPS MO for synchronization based on signals from one to three GPS satellites

Parameter Name Parameter ID Setting Notes

Way to Get Position GPS.WPOS Set this parameter to USER_CONFIG.

Antenna Longitude GPS.LONG Set these parameters based on the longitude, latitude, and altitude of
the gNodeB GPS or RGPS device.
Antenna Latitude GPS.LAT

Antenna Altitude GPS.ALT

Antenna Angle GPS.AGL

5.4.1.2 Using MML Commands

//Setting the clock synchronization mode (time synchronization is used as an example)
SET CLKSYNCMODE: CLKSYNCMODE=TIME;
//Adding a GPS clock source
ADD GPS: SRN=0, SN=7;
//Setting the clock working mode to AUTO
SET CLKMODE: MODE=AUTO;
//(Optional) Configuring the longitude, latitude, and altitude of the GPS or RGPS device of a TDD gNodeB when the TDD gNodeB obtains signals from on
MOD GPSPOS: WPOS=USER_CONFIG, LONG=10, LAT=10, ALT=10;

5.4.1.3 Using the CME

For detailed operations, see CME-based Feature Configuration.

5.4.2 Activation Verification

FDD:

1. After configuring a GPS clock as the gNodeB clock source, 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, this
function has taken effect.

TDD:

1. After configuring a GPS clock as the gNodeB clock source, 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, this
function has taken effect. Wait 30 minutes until the cell establishment is complete.

5.4.3 Network Monitoring

None

5.4.4 Reconfiguration
Some features require the gNodeB to use time synchronization. If the gNodeB reference clock source uses frequency synchronization, you must change the synchronization mode
from frequency synchronization to time synchronization before enabling these features.
Frequency synchronization configured for the following reference clock sources can be changed to GPS time synchronization:

Synchronization with GPS

Synchronization with BeiDou
IEEE1588 V2 clock synchronization
Synchronous Ethernet

Changing the synchronization mode causes gNodeB frame numbers and frame phases to change, leading to temporary service interruptions. Therefore, you are advised to change
the synchronization mode during off-peak hours.
When the synchronization mode is changed to time synchronization, KPIs slightly deteriorate on a network with no load or a light load due to PCI Mod3 interference. It is
recommended that the synchronization mode be changed to time synchronization only when necessary.

The reconfiguration procedure is as follows:

1. Perform network plan and data preparations for GPS time synchronization. For details, see 5.3 Requirements and 5.4.1.1 Data Preparation.
2. Reconfigure the gNodeB clock working mode. Run the SET CLKMODE command with Clock Working Mode set to FREE.
3. Remove the original clock link by running the RMV IPCLKLINK command.
4. Configure GPS time synchronization. Run the SET CLKSYNCMODE command with Clock Synchronization Mode set to TIME.
5. Observe the activation of GPS time synchronization. For details, see 5.4.2 Activation Verification.

6 Synchronization with BeiDou

Principles

verview

BeiDou Navigation Satellite System (BDS) is a global satellite navigation system developed by China. It is the third mature navigation satellite system following the GPS developed
by the USA and the GLONASS developed by Russia. The working principles and functions of BDS are similar to those of GPS.
If the BeiDou clock is used for synchronization, gNodeBs connect to the BeiDou satellite antenna system through a BeiDou-capable board to obtain synchronization signals from the
synchronous satellite system.

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 13/38

11/15/23, 12:56 AM HedEx Startpage
The BeiDou antenna system receives BeiDou signals and transmits them to the BeiDou satellite card. The BeiDou satellite card then processes the signals and transmits them to the
main clock module of the main control board. gNodeBs can simultaneously trace three or four satellites.
This function provides frequency synchronization and time synchronization, but requires additional investments in BeiDou during base station deployment. gNodeB sites must meet
the BeiDou signal receiving conditions and engineering requirements. For details, see GPS Satellite Antenna System Quick Installation Guide in 5900 Series Base Station Product
Documentation.

tworking Solution

Figure 6-1 shows the BeiDou synchronization solution.

Figure 6-1 BeiDou synchronization solution

nchronization Based on Signals from One to Three BeiDou Satellites

To implement BeiDou synchronization, gNodeBs require signals from at least four BeiDou satellites. In special geographical environment such as densely populated urban areas,
gNodeBs may be able to receive signals from only one to three BeiDou satellites. In this case, you can enable BeiDou synchronization based on signals from only one to three
BeiDou satellites. This synchronization mode requires accurate longitude, latitude, and altitude configuration of gNodeBs.

Network Analysis

6.2.1 Benefits
Wired networks do not affect the synchronization with the BeiDou clock. This clock is recommended when the wired network bandwidth is limited, or when wired networks frequently
experience delay variations or packet losses.

6.2.2 Impacts

twork Impacts

None

nction Impacts

None

Requirements

6.3.1 Licenses
None

6.3.2 Software

erequisite Functions

None

utually Exclusive Functions

None

6.3.3 Hardware

se Station Models

5900 series base stations

oards

A board configured with a BeiDou satellite card is required. For details on the satellite cards supported by BBU boards, see BBU Hardware Description.

F Modules

None

6.3.4 Networking
For details, see the networking solution in 6.1 Principles.

6.3.5 Others
If the BeiDou clock source is required, a BeiDou satellite antenna system must be configured.
Other requirements are the same as those of the GPS clock. For details, see 5.3.5 Others.

Operation and Maintenance

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 14/38

11/15/23, 12:56 AM HedEx Startpage
6.4.1 Activation and Performance Optimization

6.4.1.1 Data Preparation

The following tables describe the key parameters that must be set for synchronization with BeiDou.

1. Add a BeiDou clock.

Table 6-1 Key parameters in the GPS MO

Parameter Name Parameter ID Setting Notes

Cabinet No. GPS.CN Set these parameters based on the board to which the BeiDou feeder is
connected. Before configuring a BeiDou clock, ensure that the board to
Subrack No. GPS.SRN which the BeiDou feeder is connected has been configured.

Slot No. GPS.SN

GPS Clock No. GPS.GN If only one BeiDou clock source is required, set this parameter to
0.
If two BeiDou clock sources are required, set this parameter to 0
for one clock source and to 1 for the other.

Cable Length GPS.CABLE_LEN If the feeder length cannot be measured, the difference between the value
of this parameter and the actual length must be less than or equal to 20
m. Otherwise, the clock accuracy is affected.

GPS Work Mode GPS.MODE Set this parameter based on the type of a satellite card.

Priority GPS.PRI When two or more clock sources are used, a smaller value of this
parameter indicates a higher priority.

2. Configure the clock working mode, reference clock source, and reference clock source No. by running the SET CLKMODE command.
Configure the clock synchronization mode by running the SET CLKSYNCMODE command.

Table 6-2 Key parameters in the TASM MO

Parameter Name Parameter ID Setting Notes

Clock Working Mode TASM.MODE It is recommended that this parameter be set to AUTO in time
synchronization mode and to MANUAL in frequency synchronization
mode. TDD gNodeBs support only time synchronization.

Selected Clock Source TASM.CLKSRC Set this parameter to GPS.

Clock Source No. TASM.SRCNO Set this parameter to the link number specified when the clock link was
created.

Clock Synchronization Mode TASM.CLKSYNCMODE Set this parameter as required.

3. Configure the longitude, latitude, and altitude information for the gNodeB if a TDD gNodeB obtains signals from only one to three BeiDou satellites.

Table 6-3 Key parameters in the GPS MO for synchronization based on signals from one to three BeiDou satellites

Parameter Name Parameter ID Setting Notes

Way to Get Position GPS.WPOS Set this parameter to USER_CONFIG.

Antenna Longitude GPS.LONG Set these parameters based on the longitude, latitude, and altitude of the
gNodeB.
Antenna Latitude GPS.LAT

Antenna Altitude GPS.ALT

Antenna Angle GPS.AGL

6.4.1.2 Using MML Commands

//Setting the clock synchronization mode
SET CLKSYNCMODE: CLKSYNCMODE=TIME;
//Adding a BeiDou clock source
ADD GPS: GN=0,CN=0, SRN=0, SN=6, CABLE_LEN=5, MODE=BDS, PRI=4;
//Setting the clock working mode
SET CLKMODE: MODE=AUTO;
//(Optional) Configuring the longitude, latitude, and altitude of a TDD gNodeB when the TDD gNodeB obtains signals from only one to three BeiDou sat
MOD GPSPOS: WPOS=USER_CONFIG, LONG=10, LAT=10, ALT=10;

6.4.1.3 Using the CME

For detailed operations, see CME-based Feature Configuration.

6.4.2 Activation Verification

FDD:

1. After configuring a BeiDou clock as the gNodeB clock source, wait about 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, this
function has taken effect.

TDD:

1. After configuring a BeiDou clock as the gNodeB clock source, wait about 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, this
function has taken effect. Wait 30 minutes until the cell establishment is complete.

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 15/38

11/15/23, 12:56 AM HedEx Startpage
6.4.3 Network Monitoring
None

6.4.4 Reconfiguration
Some features require the gNodeB to use time synchronization. If the gNodeB reference clock source uses frequency synchronization, you must change the synchronization mode
from frequency synchronization to time synchronization before enabling these features.
Frequency synchronization configured for the following reference clock sources can be changed to BeiDou time synchronization:

Synchronization with GPS

Synchronization with BeiDou
IEEE1588 V2 clock synchronization
Synchronous Ethernet

Changing the synchronization mode causes gNodeB frame numbers and frame phases to change, leading to temporary service interruptions. Therefore, you are advised to change
the synchronization mode during off-peak hours.
When the synchronization mode is changed to time synchronization, KPIs slightly deteriorate on a network with no load or a light load due to PCI Mod3 interference. It is
recommended that the synchronization mode be changed to time synchronization only when necessary.

The reconfiguration procedure is as follows:

1. Perform network plan and data preparations for BeiDou time synchronization. For details, see 6.3 Requirements and 6.4.1.1 Data Preparation.
2. Reconfigure the gNodeB clock working mode. Run the SET CLKMODE command with Clock Working Mode set to FREE.
3. Remove the original clock link by running the RMV IPCLKLINK command.
4. Configure BeiDou time synchronization. Run the SET CLKSYNCMODE command with Clock Synchronization Mode set to TIME.
5. Observe the activation of BeiDou time synchronization. For details, see 6.4.2 Activation Verification.

7 IEEE1588 V2 Clock Synchronization

Principles
IEEE1588 V2 synchronization is one of the clock solutions for IP networks and applies to the Ethernet transport network.
IEEE1588 V2 supports both frequency synchronization and time synchronization. IEEE1588 V2 messages are transferred between primary and secondary equipment. To achieve
frequency or time synchronization between the equipment, accurate time stamps are used to calculate the offset of time and frequency to the microsecond.
gNodeBs support IEEE1588 V2 in layer 3 unicast and layer 2 multicast modes.

In layer 3 unicast mode, IEEE1588 V2 packets are contained in IPv4 User Datagram Protocol (UDP) packets.
In layer 2 multicast mode, IEEE1588 V2 packets are contained in media access control (MAC) packets.

Whether to use layer 3 unicast mode or layer 2 multicast mode is specified by the IPCLKLNK.CNM parameter.
Table 7-1 lists the profile types complying with IEEE1588 V2.

Table 7-1 IEEE1588 V2 profile types

Profile Type Synchronization Mode

IEEE1588 V2 (Huawei proprietary) layer 3 unicast Time synchronization and frequency synchronization

IEEE1588 V2 16.1 layer 3 unicast Time synchronization and frequency synchronization

IEEE1588 V2 layer 2 multicast Time synchronization

ITU-T G.8275.2 layer 3 unicast Time synchronization

ITU-T G.8275.1 layer 2 multicast Time synchronization

ITU-T G.8265.1 layer 3 unicast Frequency Synchronization

The IEEE1588 V2 clock is selected as the system clock of a gNodeB by setting the IPCLKLNK.ICPT parameter to PTP.

7.1.1 Time Synchronization

The IEEE1588 V2 time synchronization solution requires that all intermediate transmission equipment on the data bearer network supports the Boundary Clock (BC) or Transparent
Clock (TC) function defined in IEEE1588 V2. You are advised to use the BC and layer 2 multicast mode networkwide. The layer 3 unicast mode also requires that all intermediate
transmission equipment on the data bearer network supports the BC or TC function defined in IEEE1588 V2.

7.1.1.1 Network Clock Architecture

Figure 7-1 shows the network clock architecture defined in IEEE1588 V2. From the perspective of network clock architecture, the layer 3 unicast and layer 2 multicast modes are
identical.

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 16/38

11/15/23, 12:56 AM HedEx Startpage
Figure 7-1 Network clock architecture defined in IEEE1588 V2

IEEE1588 V2 defines the following basic network components:

Master port
Used by the upstream equipment to distribute clock signals to the downstream equipment.
Slave port
Used by the downstream equipment to obtain clock signals from the upstream equipment.
Ordinary clock (OC)
OC is a clock with only one PTP communication port. The port can be used as the master port for distributing clock signals to the downstream equipment or as the slave port
for obtaining clock signals from the upstream equipment. An OC restores the clock for frequency or time synchronization. The gNodeBs shown in Figure 7-1 are used as OCs.
BC
BC is a clock with more than one PTP communication port. A complete BC has one slave port and one or more master ports. It restores the upstream clock (for example, GPS
clock) at the slave port by using the OC function and then distributes the clock signals through one or more master ports. The clock server shown in Figure 7-1 is used as the
BC.
The BC is a point-to-point clock solution. The layer 2 multicast mode does not require negotiation, which facilitates interconnection between devices. If the BC solution is used
for IEEE1588 V2 time synchronization, each BC node synchronizes with the upper-level equipment. When a synchronization issue occurs, it is easy to locate the issue.
TC
The TC supports the mechanism of link delay measurement of the IEEE1588 V2 clock and is located in the transmission equipment, as shown in Figure 7-1. Frequency
synchronization and time synchronization can be implemented through TC after reconfiguration of all the transmission equipment on the path.
If the TC is used for IEEE1588 V2 time synchronization, intermediate nodes compensate for only TC processing delay. When a synchronization issue occurs, it is difficult to
locate the issue.

7.1.1.2 Delay Measurement

Delay measurement and delay compensation must be performed for all transmission interfaces of all intermediate transmission equipment including layer 3 and layer 2 equipment.
Delay is inevitable during the transmission of clock signals. Such delay needs to be measured and compensated to ensure clock accuracy. The compensation value must be set
again if routes or transmission paths change.
IEEE1588 V2 network clock delay measurement is classified into end-to-end (E2E) and point-to-point (P2P) delay measurement. The type of delay measurement is specified by the
IPCLKLNK.DELAYTYPE parameter.

ckground Information

The main messages involved in the delay measurement are as follows:

Sync message
The Sync message contains the standard time information, such as year, month, date, hour, minute, second, and nanosecond. gNodeBs record T2, the arrival time of the
Sync message at gNodeBs. The time for sending or receiving the message needs to be measured and recorded at the underlying physical layer or the position close to the
physical layer to improve the clock accuracy.
In the IEEE1588 standard, the optional hardware assisted techniques are designed to improve the clock accuracy. If the Sync message is generated through the hardware
assisted techniques, the message can also contain the timestamp T1, at which the message is sent. When an E2E TC (for example, transmission equipment) exists between
the clock server and the gNodeB, the processing delay Δt on the transmission equipment is calculated and compensated in the Sync message.
Follow_UP message
In layer 3 unicast mode, if the delay of sending the Sync message is uncertain in the clock server, the clock server generates a Follow_UP message, which contains
the timestamp T1. The Follow_UP message is optional.
In layer 2 multicast mode, the Follow_UP message is not supported.

Delay_resp message
The delay of the Delay_resp message does not affect the value of T4. Therefore, this message does not need to be processed in real time.

E Delay Measurement

E2E delay measurement is used to calculate the processing delay at the intermediate transmission equipment between the upstream system clock and gNodeBs.
Figure 7-2 uses the E2E delay measurement between the clock server and a gNodeB as an example.

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 17/38

11/15/23, 12:56 AM HedEx Startpage
Figure 7-2 E2E delay measurement of the IEEE1588 V2 clock

1. The clock server periodically sends a Sync message to the gNodeB at the time point T1.
2. The gNodeB receives the Sync message at the time point T2.
3. The gNodeB sends a Delay_req message to the clock server at the time point T3.
4. The clock server receives the Delay_req message at the time point T4, and sends a Delay_resp message that contains T4 to the gNodeB.
5. The gNodeB stores the complete information about time points T1, T2, T3, and T4. The processing delay between the clock server and the gNodeB is calculated using the
following formula:

P Delay Measurement

P2P delay measurement is used to calculate the link delay between adjacent TCs, between a TC and an OC, or between a TC and a BC. Figure 7-3 uses the P2P delay measurement
between the clock server and the transmission equipment as an example.

Figure 7-3 P2P delay measurement of the IEEE1588 V2 network clock

1. The clock server periodically sends a Sync message to the transmission equipment.
2. The transmission equipment calculates the processing delay Δt and compensates for the delay in the Sync message.
3. The transmission equipment generates a Pdelay_req message and sends the message to the clock server at T1.
4. The clock server receives the Pdelay_req message at T2, generates a Pdelay_resp message, and sends the message to the transmission equipment at T3. The
Pdelay_resp message contains the deviation between T2 and T3, that is, the value of T3 minus T2.
5. The transmission equipment records the time the Pdelay_resp message is received as T4.
6. The transmission equipment stores the information about T1, T4, and the deviation between T2 and T3. The processing delay between the clock server and the
transmission equipment is calculated as follows:

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 18/38

11/15/23, 12:56 AM HedEx Startpage

NOTE:
The delay measurement between the transmission equipment and the gNodeB is the same as that between the clock server and the transmission equipment.

ymmetrical Delay Compensation

In principle, the absolute time of the slave port is equal to the standard time contained in the Sync message plus the delay if the uplink and downlink physical paths between the
master port and the slave port are symmetrical. If the uplink and downlink physical paths are asymmetrical, the asymmetrical delay compensation is required.
For the asymmetrical delay compensation, the asymmetry of uplink and downlink physical paths (for example, fiber optic cables) results in the asymmetry of IEEE1588 V2 packets on
uplink and downlink physical paths. As a result, the existing absolute time of the slave port is deviated and a fixed deviation generated due to the asymmetry of uplink and downlink
physical paths must be compensated on the slave port.
Through the comparison between the IEEE1588 V2 clock and a standard clock such as the GPS clock, the deviation is directly compensated for the IEEE1588 V2 clock. Alternatively,
a device is used to test the difference between the transmission distances on the uplink and downlink physical paths, and then the deviation is compensated after being calculated.
The deviation is specified by the IPCLKLNK.CMPST parameter.

7.1.1.3 Applications

ngle-Reference-Clock Mode of IEEE1588 V2

Figure 7-4 shows the single-reference-clock mode of IEEE1588 V2.

Figure 7-4 Single-reference-clock mode of IEEE1588 V2

As shown in Figure 7-4, each blue line depicts a clock link, that is, an IEEE1588 V2 synchronization session. The clock server (for example, the IPCLK1000) periodically sends a Sync
message to the associated routers or Ethernet switches. Each gNodeB obtains the reference clock from the connected router or Ethernet switch. In this mode, each gNodeB has only
one reference clock. If the reference clock becomes unavailable, the master clock of the gNodeB switches from the locked mode, to the holdover mode, and then to the free running
mode. The clock does not enter the locked mode until the external reference clock becomes available again.

al-Reference-Clock Backup Mode of IEEE1588 V2

In this mode, two clock servers are deployed on the network to enhance the reliability of reference clocks. Each gNodeB is directly connected to the router or Ethernet switch through
independent IEEE1588 V2 clock links. If the clock link of the master clock server is disconnected, the gNodeB can still implement time synchronization through the backup clock link.
Figure 7-5 shows the dual-reference-clock backup mode of IEEE1588 V2 for time synchronization.

NOTE:
In layer 2 multicast mode, the network-level master/backup solution is used. With this solution, master and backup clock servers are used, but gNodeBs do not require master and
backup clock links.

Figure 7-5 Dual-reference-clock backup mode of IEEE1588 V2

Each gNodeB can be configured with two IP clock links, as depicted by the blue and red lines in Figure 7-5.

In manual mode, you need to manually specify the clock link to be used.
In automatic mode, the gNodeB determines which clock link to be used based on the link status.
If one clock link works properly while the other does not, the gNodeB selects the functional clock link.
If both clock links work properly, the gNodeB selects one based on the best master clock (BMC) algorithm. For details on the BMC algorithm, see section 9.3.2 "BMC
algorithm" in IEEE_Std_1588-2008[1] or section 6.7.3 "Master selection process" in T-REC-G[1].8265.1-201010.

7.1.2 Frequency Synchronization

When IEEE1588 V2 is used for frequency synchronization, the layer 3 unicast mode is recommended, because clock servers and gNodeBs are connected through the transport
network. In layer 3 unicast mode, the mechanism for packet transmission is simple and there are no special requirements for the transport network. IEEE1588 V2 frequency
synchronization does not require delay measurement.

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 19/38

11/15/23, 12:56 AM HedEx Startpage
FDD gNodeBs support frequency synchronization. When an evolved multimedia broadcast/multicast service (eMBMS) or inter-site coordination function (such as inter-site CA and
inter-site CoMP based on BBU interconnection or relaxed backhaul) is used on FDD gNodeBs, the gNodeBs must support time synchronization.

7.1.2.1 Network Clock Architecture

IEEE1588 V2 frequency synchronization involves gNodeBs, clock servers, and intermediate transmission equipment between gNodeBs and clock servers. One or two clock servers
constitute an independent clock domain, as shown in Figure 7-6.
Figure 7-6 IEEE1588 V2 frequency synchronization solution

NOTE:
When IEEE1588 V2 frequency synchronization is used, the intermediate transmission equipment does not need to support the IEEE1588 V2 standard.
The configuration of two clock servers implements reference clock backup, improving the reliability. The clock servers can use the GPS clock or line clock as the reference clock.

The clock server sends clock packets to gNodeBs through the intermediate data bearer network.
When a hub gNodeB is configured, the hub gNodeB routes the clock packets to leaf gNodeBs. A data forwarding device, such as router or Ethernet switch, is allowed between the
hub gNodeB and leaf gNodeBs.
If the QoS of the network between gNodeBs and clock servers cannot be ensured, the clock servers and the hub gNodeB can be co-sited. In this case, the clock servers can directly
provide clock signals for the hub gNodeB and leaf gNodeBs. This reduces the dependence on the quality of the bearer network.
gNodeBs using the IEEE1588 V2 clock synchronization support clock quality levels identified by clock classes that are specified in ITU-T G.8265.1. If the IEEE1588 V2 clock is used
as the high-accuracy reference clock for a gNodeB, the clock quality level cannot be lower than QL-SSU-B.

7.1.2.2 Encryption Process

Frequency synchronization can be achieved between a gNodeB and an IP clock server by using IEEE1588 V2 layer 3 unicast packets.
In a trusted transport network, the network ensures the security of IEEE1588 V2 clock packets. Non-trusted transport networks require higher-level security measures to protect the
gNodeB and IP clock server from being attacked by unauthorized packets. The gNodeB encrypts clock packets by using IP Security (IPsec), and the security gateway (SeGW) uses
IPsec to encrypt clock packets for the clock server. IEEE1588 V2 over IPsec supports only frequency synchronization.
The SeGW encrypts all packets by using IPsec. The arrival time of all encrypted packets is recorded by the gNodeB. After decrypting the packets by using IPsec, the gNodeB
identifies the IEEE1588 V2 clock packets from all the packets based on UDP port numbers, and then recovers the clock frequency by using the adaptive clock recover (ACR)
algorithm. Figure 7-7 shows the detailed procedure.
Figure 7-7 IPsec encryption process

1. The gNodeB performs an Internet Key Exchange (IKE) negotiation to set up an IPsec tunnel with the SeGW.
2. The IP clock server sends the SeGW an IEEE1588 V2 clock packet with a timestamp attached.
3. The SeGW encrypts the IEEE1588 V2 clock packet through the established IPsec tunnel.
4. The SeGW transmits the encrypted clock packet to the gNodeB.

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 20/38

11/15/23, 12:56 AM HedEx Startpage
5. After receiving the encrypted clock packet, which cannot be identified by the gNodeB, the gNodeB records the arrival time of the clock packet and sends the timestamp to
the upper layer together with the encrypted packet.
6. The gNodeB decrypts the clock packet by using IPsec and reads the time information from PTP packets.
7. The gNodeB recovers the clock frequency by using the ACR algorithm.

7.1.2.3 Applications

ngle-Reference-Clock Mode of IEEE1588 V2

Figure 7-8 shows the single-reference-clock mode of IEEE1588 V2.

Figure 7-8 Single-reference-clock mode of IEEE1588 V2

As shown in Figure 7-8, each blue line depicts a clock link, that is, an IEEE1588 V2 synchronization session. The clock server (for example, the IPCLK1000) periodically sends a Sync
message to the associated gNodeBs for clock synchronization. In this mode, each gNodeB has only one reference clock. If the reference clock becomes unavailable, the master
clock of the gNodeB switches from the locked mode, to the holdover mode, and then to the free running mode. The clock does not enter the locked mode until the external reference
clock becomes available again.

al-Reference-Clock Backup Mode of IEEE1588 V2

In this mode, two clock servers are deployed on the network to enhance the reliability of reference clocks. Each gNodeB is connected to these two clock servers through independent
IEEE1588 V2 clock links. If the clock link of the master clock server is disconnected, the gNodeB can still implement frequency or time synchronization through the backup clock
server and clock link. Figure 7-9 shows the dual-reference-clock backup mode of IEEE1588 V2.
Figure 7-9 Dual-reference-clock backup mode of IEEE1588 V2

Each gNodeB can be configured with two IP clock links, as depicted by the blue and red lines in Figure 7-9. The two clock servers can be manually or automatically switched.

In manual mode, you need to manually specify the clock server to be used.
In automatic mode, the gNodeB determines the clock server to be used based on the status of clock links.
If the clock link of one clock server works properly while the clock link of the other clock server does not, the gNodeB selects the clock server whose clock link is
working properly.
If the clock links of both clock servers work properly, the gNodeB selects one based on the BMC algorithm. For details on the BMC algorithm, see section 9.3.2 "BMC
algorithm" in IEEE_Std_1588-2008[1] or section 6.7.3 "Master selection process" in T-REC-G[1].8265.1-201010.
If the clock link of one clock server becomes faulty, the gNodeB switches to the clock link of the other clock server and reports a reference clock switchover event.

7.1.3 Hybrid Synchronization

In hybrid synchronization, two IEEE1588 V2 IP clock links are configured for a gNodeB, one using time synchronization and the other using frequency synchronization.

The time synchronization link has the same requirements for intermediate transmission equipment on the bearer network as IEEE1588 V2 time synchronization. For details,
see 7.1.1 Time Synchronization.
The frequency synchronization link has the same requirements for intermediate transmission equipment as IEEE1588 V2 frequency synchronization. For details, see 7.1.2
Frequency Synchronization.

When the time synchronization link is faulty or the clock level does not meet the requirement, the gNodeB switches to the frequency synchronization link to implement frequency
synchronization. When the faulty link recovers, the gNodeB switches back to the time synchronization link to implement time synchronization. Hybrid synchronization can be
implemented by performing the following operations:

Set the TASM.CLKSYNCMODE parameter to HYBRID.

Add two IEEE1588 V2 IP clock links. Set the IPCLKLNK.IPSYNCMODE parameter to TIME for one link and to FREQ for the other link.

7.1.4 Interworking Between IEEE1588 V2-compliant Equipment from Different Manufacturers

The IEEE1588 protocol supports accurate time synchronization in the industrial automation field, which allows for clock synchronization in distributed networks. The IEEE1588
protocol also applies to the wide area network (WAN). The concept of "profile" was proposed in the IEEE1588 V2 protocol released in 2008. Manufacturers choose different
IEEE1588 V2 feature subsets (representing different profiles) to achieve clock synchronization based on different requirements. As a result, IEEE1588 V2-compliant equipment from
different manufacturers cannot interwork with each other.
As an extension of the concept of "profile", the ITU proposes G.8265.1 and G.8275.1 for the telecommunications industry. G.8265.1 and G.8275.1 define interconnection standards
for different vendors. ITU-T G.8265.1 applies to interworking between a gNodeB and a clock server when IEEE1588 V2 layer 3 unicast frequency synchronization is implemented.
ITU-T G.8275.1 applies to interworking between a gNodeB and transmission equipment when IEEE1588 V2 layer 2 multicast time synchronization is implemented.

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 21/38

11/15/23, 12:56 AM HedEx Startpage
IEEE1588 V2 16.1 applies to interworking between a gNodeB and third-party clock servers when IEEE1588 V2 time synchronization is implemented. For details on IEEE1588 V2
16.1, see the optional section 16.1 in the IEEE1588 V2 standard.
ITU-T G.8265.1 is preferentially used in interworking between a gNodeB and a third-party clock server. G.8265.1 applies to interworking between an FDD gNodeB and a third-party
clock server when IEEE1588 V2 frequency synchronization is implemented.
Table 7-2 lists application scenarios of profile types complying with IEEE1588 V2 in interworking between IEEE1588 V2-compliant equipment from different manufacturers.

Table 7-2 Application scenarios of profile types complying with the IEEE1588 V2 standard

Profile Type Synchronization Mode Application Scenario

IEEE1588 V2 (Huawei proprietary) layer 3 unicast Time synchronization and frequency Interworking between gNodeBs and a clock server provided by
synchronization Huawei

IEEE1588 V2 16.1 layer 3 unicast Time synchronization and frequency Interworking between gNodeBs and a clock server provided by a
synchronization third party

ITU-T G.8275.2 layer 3 unicast Time synchronization Interworking between gNodeBs and a clock server
provided by Huawei
Interworking between gNodeBs and a clock server
provided by a third party

ITU-T G.8265.1 layer 3 unicast Frequency synchronization Interworking between gNodeBs and a clock server
provided by Huawei
Interworking between gNodeBs and a clock server
provided by a third party

IEEE1588 V2 layer 2 multicast Time synchronization Interworking between gNodeBs and transmission
equipment provided by Huawei
Interworking between gNodeBs and third-party
transmission equipment

ITU-T G.8275.1 layer 2 multicast Time synchronization Interworking between gNodeBs and transmission
equipment provided by Huawei
Interworking between gNodeBs and third-party
transmission equipment

The IPCLKLNK.PROFILETYPE parameter specifies a profile type used for interworking between IEEE1588 V2-compliant equipment from different manufacturers. The gNodeB and
equipment interconnected with the gNodeB (for example, a clock server or transmission equipment) must use the same profile type for interworking.
When gNodeBs use IEEE1588 V2 time synchronization, set the IPCLKLNK.PROFILETYPE parameter as follows:

If a Huawei clock server is used, set this parameter to 1588V2.

If a third-party clock server is used, set this parameter to 1588V2_16.1 or G8275.2.
If the gNodeB and transmission equipment are interconnected, set this parameter to 1588V2 or G.8275.1.

When FDD gNodeBs use IEEE1588 V2 frequency synchronization, set the IPCLKLNK.PROFILETYPE parameter as follows:

If a Huawei clock server is used, set this parameter to 1588V2 or G.8265.1.

If a third-party clock server is used, set this parameter to G.8265.1 preferentially or to 1588V2_16.1.

If a gNodeB interworks with a third-party clock server, the IPCLKLNK.ANNFREQ and IPCLKLNK.NEGDURATION parameters can be set to specify the frequency at which the clock
server sends announcement packets to the gNodeB and the interval at which negotiations are performed between them, respectively. It is recommended that parameters
IPCLKLNK.ANNFREQ and IPCLKLNK.NEGDURATION be set to their default values 1/2 and 300, respectively. The two parameters can also be set to other values supported by the
clock server that interworks with the gNodeB.
When a gNodeB interworks with a third-party transmission equipment, the IPCLKLNK.DSTMLTMACTYPE parameter specifies the destination MAC type of G.8275.1 clock
synchronization packets sent by the gNodeB. The destination MAC type is used to match the MAC type of multicast packets that the transmission equipment receives. The gNodeB
can adaptively match the destination MAC type of clock packets received from the transmission equipment. The IPCLKLNK.DSTMLTMACTYPE parameter is used to match the clock
packets for all types of transmission equipment.
When interworking with a Huawei clock server, a gNodeB supports the priority clock class function. To enable this function, run the SET CLASSIDENTIFY command with the
IPCLKLNK.CLASSIDENTIFY parameter set to ON, and then run the SET PRICLASS command to set the priority clock class of the specified IP clock link. If this function is enabled,
the gNodeB selects an available clock source with the highest priority clock class as the gNodeB reference clock. If this function is disabled, the gNodeB does not select the
reference clock based on the priority clock class.

Network Analysis

7.2.1 Benefits
The IEEE1588 V2 clock is a cost-effective option for networks using IP transmission.

7.2.2 Impacts

twork Impacts

None

nction Impacts

None

Requirements

7.3.1 Licenses

Feature ID Feature Name Model Sales Unit

FOFD-010070 Network Synchronization NR0S00STTN00 per gNodeB

7.3.2 Software

erequisite Functions

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 22/38

11/15/23, 12:56 AM HedEx Startpage
None

utually Exclusive Functions

None

7.3.3 Hardware

se Station Models

5900 series base stations

oards

Only the UMPTe supports this function.

F Modules

None

7.3.4 Networking
The networking requirements of the IEEE1588 V2 clock source are as follows:

IEEE1588 V2 applies only to IP over FE/GE links.

When the dual-reference-clock backup mode of IEEE1588 V2 synchronization is used, the two clock links must use the same type of protocol and the same transmission
mode. In addition, parameters specifying the clock topology, domain, compensation value, and delay type must be set to the same values for the two clock links.
The layer 3 unicast mode cannot coexist with the layer 2 multicast mode. If the layer 2 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 transport network frequently experiences delay variations or packet losses.
IEEE1588 V2 clock distribution can be used only in gNodeB cascading scenarios.

If the IEEE1588 V2 time synchronization is used, the following extra networking requirements must be met:

The frequency at which the upper-level reference clock transmits Sync packets must be greater than or equal to 0.5 packet per second. This ensures fast entrance to the
locked mode and high clock accuracy.
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 layer 3 and layer 2
routers. The compensation value must be set again if routes or transmission paths change.

It is recommended that FDD gNodeBs use hybrid synchronization only on an IEEE1588 V2 frequency synchronization network to protect the existing investment.

7.3.5 Others
None

Operation and Maintenance

7.4.1 Activation and Performance Optimization

7.4.1.1 Data Preparation

Add an IP clock link. The IP clock link can be configured on the main control board or UTRPc of a Huawei gNodeB. Before configuring an IP clock link, ensure that the required board
has been configured.

Table 7-3 Key parameters in the IPCLKLNK MO

Parameter Name Parameter ID Setting Notes

Link No. IPCLKLNK.LN In single-reference-clock mode of IEEE1588 V2, set this parameter to 0.
In dual-reference-clock backup mode of IEEE1588 V2, two clock links are required. Set
this parameter to 0 for one clock link and to 1 for the other.

Client IPv4 IPCLKLNK.CIP Set this parameter to the IP address of the IP clock link between the eNodeB and IP
clock server. The IP address must have been specified on the DevIPPattern page or
must have been added by running the ADD DEVIP command. Otherwise, this parameter
is invalid.

Server IPv4 IPCLKLNK.SIP Set this parameter to the IP address of the IP clock server that provides clock signals.
In dual-reference-clock backup mode of IEEE1588 V2, the two clock links must have
different server IP addresses.

Domain IPCLKLNK.DM Set this parameter to the same value as the domain of the IP clock server in use.
In dual-reference-clock backup mode of IEEE1588 V2, the two clock links must use the
same clock protocol type, clock topology mode, domain, compensation value, and delay
type. The two clock links must be configured on the same board. For details, see the
online help of the ADD IPCLKLINK command.

Priority IPCLKLNK.PRI When two or more clock sources are used, a smaller value of this parameter indicates a
higher priority.
In dual-reference-clock backup mode of IEEE1588 V2, the two clock links must have the
same priority.

Protocol Type IPCLKLNK.ICPT Set this parameter to PTP.

Clock Net Mode IPCLKLNK.CNM Set this parameter as required.

Compensation IPCLKLNK.CMPST Set this parameter as required in time synchronization mode.

Delay Type IPCLKLNK.DELAYTYPE Set this parameter as required in time synchronization mode.

Profile Type IPCLKLNK.PROFILETYPE When an FDD gNodeB is interconnected with a clock server:
Set this parameter to 1588V2 or G.8265.1 if a Huawei IP clock server is used.

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 23/38

11/15/23, 12:56 AM HedEx Startpage

Parameter Name Parameter ID Setting Notes

Set this parameter to G.8265.1 preferentially or to 1588V2_16.1 if a third-party IP
clock server is used.
If an FDD gNodeB is interconnected with transmission equipment, set this parameter to
1588V2 or G.8275.1.
When a TDD gNodeB is interconnected with a clock server:
Set this parameter to 1588V2 if a Huawei clock server is used.
Set this parameter to 1588V2_16.1 if a third-party clock server is used.
If a TDD gNodeB is interconnected with transmission equipment, set this parameter to
G.8275.1.

Destination Multicast MAC IPCLKLNK.DSTMLTMACTYPE Set this parameter when IPCLKLNK.PROFILETYPE is set to G.8275.1. This parameter is
Address Type used to match the type of multicast MAC addresses in packets that can be received by
transmission equipment.

Master Priority IPCLKLNK.MASTERPRIO This parameter is valid only when IPCLKLNK.CNM is set to UNICAST and
IPCLKLNK.PROFILETYPE is set to G.8265.1.

Configure the clock working mode, reference clock source, and reference clock source No. by running the SET CLKMODE command.
Configure the clock synchronization mode and low-precision frame No. synchronization switch by running the SET CLKSYNCMODE mode.

Table 7-4 Key parameters in the TASM MO

Parameter Name Parameter ID Setting Notes

Clock Working Mode TASM.MODE It is recommended that this parameter be set to AUTO in time synchronization mode
and to MANUAL in frequency synchronization mode. TDD gNodeBs support only time
synchronization.

Selected Clock Source TASM.CLKSRC Set this parameter to IPCLK.

Clock Source No. TASM.SRCNO Set this parameter to the link number specified when the clock link was created.

Clock Synchronization Mode TASM.CLKSYNCMODE Set this parameter as required. For TDD gNodeBs, set this parameter to TIME.

7.4.1.2 Using MML Commands

//Setting the clock synchronization mode
SET CLKSYNCMODE: CLKSYNCMODE=TIME;
//Adding an IP clock link (unicast mode)
ADD IPCLKLINK: ICPT=PTP, SN=6, CNM=UNICAST, IPMODE=IPV4, CIP="177.12.11.175", SIP="10.70.20.100", DELAYTYPE=E2E, PROFILETYPE=1588V2;
//Adding an IP clock link (L2 multicast mode)
ADD IPCLKLINK:ICPT=PTP,SN=6,CNM=L2_MULTICAST,DELAYTYPE=E2E,MACMODE=NO,PROFILETYPE=1588V2;
//Setting the clock working mode
SET CLKMODE:MODE=AUTO;

7.4.1.3 Using the CME

For detailed operations, see CME-based Feature Configuration.

7.4.2 Activation Verification

FDD:

1. After configuring an IEEE1588 V2 clock as the gNodeB clock source, wait about 30 minutes in scenarios where the transmission quality is good.
2. Run the DSP CLKSTAT command to query the clock source status. If the value of Current Clock Source is IP Clock and the value of PLL Status is Locked, this function
has taken effect.

TDD:

1. After configuring an IEEE1588 V2 clock as the gNodeB clock source, wait about 30 minutes in scenarios where the transmission quality is good.
2. Run the DSP CLKSTAT command to query the clock source status. If the value of Current Clock Source is IP Clock and the value of PLL Status is Locked, this function
has taken effect.

7.4.3 Network Monitoring

None

7.4.4 Reconfiguration
Some features require the gNodeB to use time synchronization. If the gNodeB reference clock source uses frequency synchronization, you must change the synchronization mode
from frequency synchronization to time synchronization before enabling these features.
Frequency synchronization configured for the following reference clock sources can be changed to IEEE1588 V2 time synchronization:

Synchronization with GPS

Synchronization with BeiDou
IEEE1588 V2 clock synchronization
Synchronous Ethernet

Changing the synchronization mode causes gNodeB frame numbers and frame phases to change, leading to temporary service interruptions. Therefore, you are advised to change
the synchronization mode during off-peak hours.
When the synchronization mode is changed to time synchronization, KPIs slightly deteriorate on a network with no load or a light load due to PCI Mod3 interference. It is
recommended that the synchronization mode be changed to time synchronization only when necessary.

The reconfiguration procedure is as follows:

1. Perform network plan and data preparations for IEEE1588 V2 time synchronization. For details, see 7.3 Requirements and 7.4.1.1 Data Preparation.
2. Reconfigure the gNodeB clock working mode. Run the SET CLKMODE command with Clock Working Mode set to FREE.

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 24/38

11/15/23, 12:56 AM HedEx Startpage
3. Remove the original clock link by running the RMV IPCLKLINK command.
4. Configure IEEE1588 V2 time synchronization. Run the SET CLKSYNCMODE command with Clock Synchronization Mode set to TIME.
5. Observe the activation of IEEE1588 V2 time synchronization. For details, see 7.4.2 Activation Verification.

8 Synchronous Ethernet

Principles
Similar to the SDH and plesiochronous digital hierarchy (PDH) technologies, the synchronous Ethernet technology enables a downstream node to obtain and trace the upstream
clock by restoring clock signals from the serial data bit streams received from the physical layer. The detailed definition of synchronous Ethernet is specified in ITU-T G.8262.
Because the clock signals are directly extracted from the physical layer of the Ethernet, clock synchronization is irrelevant to specific services implemented at upper layers.
Synchronous Ethernet is an optional feature. It is supported only by FDD gNodeBs and complies with ITU-T G.8261, G.8262, and G.8264.

8.1.1 Network Clock Architecture

Figure 8-1 shows the network clock architecture of the synchronous Ethernet. The system clock of the upstream clock module serves as the reference clock for the upstream Ethernet
chip. The clock information is encoded at the physical layer of the Ethernet and travels over the physical link to the Ethernet port of a gNodeB. Afterwards, the Ethernet physical chip
recovers the Ethernet packets and line clock from the modulated code streams and distributes the line clock signals to the other modules in the gNodeB through the clock signal
distribution module.
Figure 8-1 Network clock architecture of the synchronous Ethernet

If the synchronous Ethernet clock serves as the gNodeB clock source, its frequency accuracy must be ±0.016 ppm or higher.
gNodeBs support Synchronization Status Messages (SSMs) when synchronizing with a synchronous Ethernet. Table 8-1 lists clock quality levels identified by SSMs.

Table 8-1 Clock quality levels identified by SSMs

Clock Quality Level Identified by SSMs Description Whether the Clock Source Is
Available

QL-PRC A clock source at the PRC level is used. Yes

QL-SSU-A A tandem office slave clock at the SSU-A level is used. Yes

QL-SSU-B An end office slave clock at the SSU-B level is used. Yes

QL-SEC/QL-EEC1/QL-EEC2 A reference clock at the SEC/EEC1/EEC2 level is used. No

NOTE:
Only a clock source whose clock quality level meets the gNodeB requirement can be used as the reference clock.

The quality levels of clocks used by a gNodeB in descending order are as follows: QL-PRC > QL-SSU-A > QL-SSU-B > QL-SEC/QL-EEC1/QL-EEC2.
The default clock quality level is QL-SSU-B for a gNodeB. A gNodeB can only use a reference clock whose quality level is greater than or equal to QL-SSU-B.
Ethernet Equipment Clock (EEC) is defined in ITU-T G.8262. Two types of EECs, EEC1 and EEC2, are defined, and the accuracy of both EEC1 and EEC2 is ±4.6 ppm. The
accuracy of an SEC is also ±4.6 ppm. The clock accuracy required by a gNodeB is ±0.05 ppm, and therefore gNodeBs cannot use a reference clock at the QL-SEC/QL-EEC1/QL-
EEC2 level.

8.1.2 Applications

nchronous Ethernet Clock Recovery at the gNodeB Acting as the Client

As shown in Figure 8-2, an FE or GE port can be configured for the gNodeB to support synchronous Ethernet. The gNodeB serves as the client to recover the clock that is received
from the upstream clock device. The clock serves as the reference clock of the entire gNodeB.

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 25/38

11/15/23, 12:56 AM HedEx Startpage
Figure 8-2 Synchronous Ethernet clock recovery

If the synchronous Ethernet clock is used as the high-accuracy reference clock for a gNodeB, the frequency accuracy of the clock must not be lower than the accuracy required for
the SSU-B level. gNodeBs synchronizing with the synchronous Ethernet clock support SSMs for indicating clock quality levels.

NOTE:
Each gNodeB can be configured with only one synchronous Ethernet reference clock, that is, only one FE/GE link for the reference clock.
A gNodeB does not support synchronous Ethernet if the gNodeB is connected to the Ethernet using an optical-to-electrical conversion module.
If the gNodeB has negotiated with the peer equipment that the FE/GE link uses a 1000 Mbit/s electrical port, ensure that the clock synchronization mode of the peer
equipment is not slave mode to protect the FE/GE link from being interrupted.

nchronous Ethernet Clock Signal Transmission from the gNodeB Acting as the Reference Clock

The gNodeB can send its system clock signals to the downstream synchronous Ethernet clock tracing equipment through the FE/GE link, as shown in Figure 8-3.
Figure 8-3 Synchronous Ethernet clock signal transmission from the reference clock

Network Analysis

8.2.1 Benefits
Synchronous Ethernet extracts clock signals from the physical layer, and clock synchronization does not affect upper-layer services. This technology is irrelevant to delay variations
or packet losses, and does not occupy transmission bandwidth.

8.2.2 Impacts

twork Impacts

Synchronous Ethernet supports only frequency synchronization. Therefore, it cannot be used if time synchronization is required.

nction Impacts

None

Requirements

8.3.1 Licenses
The following lists the license requirement for this function.

Feature ID Feature Name Model Sales Unit

FOFD-010070 Network Synchronization NR0S00STTN00 per gNodeB

8.3.2 Software

erequisite Functions

None

utually Exclusive Functions

None

8.3.3 Hardware

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 26/38

11/15/23, 12:56 AM HedEx Startpage
se Station Models

5900 series base stations

oards

Only the UMPTe supports this function.

F Modules

None

8.3.4 Networking
To implement synchronous Ethernet, all the intermediate transmission equipment, such as hubs and LAN switches, must be capable of transparent transmission or regeneration of
clock signals at the physical layer.

8.3.5 Others
None

Operation and Maintenance

8.4.1 Activation and Performance Optimization

8.4.1.1 Data Preparation

Add a synchronous Ethernet clock link. Before configuring a synchronous Ethernet clock link, ensure that the required board has been configured.

Table 8-2 Key parameters in the SyncEth MO

Parameter Name Parameter ID Setting Notes

SyncEth Clock No. SyncEth.LN Set this parameter to 0.

Port No. SyncEth.PN Set this parameter to the port number of the board where a synchronous Ethernet
clock link is configured. Ensure that the port and the synchronous Ethernet clock are
connected to the same network.

SSM Selection SyncEth.SSM Set this parameter to the same value as that for the Ethernet clock server.

Priority SyncEth.PRI When two or more clock sources are used, a smaller value of this parameter
indicates a higher priority.
If only the synchronous Ethernet clock is used, use the default value of this
parameter.

Configure the clock working mode, reference clock source, and reference clock source No. by running the SET CLKMODE command.
Configure the clock synchronization mode by running the SET CLKSYNCMODE command.
Table 8-3 Key parameters in the TASM MO

Parameter Name Parameter ID Setting Notes

Clock Working Mode TASM.MODE Set this parameter to MANUAL.

Selected Clock Source TASM.CLKSRC Set this parameter to SYNCETH.

Clock Source No. TASM.SRCNO Set this parameter to the link number specified when the clock link was created.

Clock Synchronization Mode TASM.CLKSYNCMODE Set this parameter to FREQ as the synchronous Ethernet clock supports only
frequency synchronization.

8.4.1.2 Using MML Commands

//Setting the clock synchronization mode
SET CLKSYNCMODE:CLKSYNCMODE=FREQ;
//Adding a synchronous Ethernet clock link
ADD SYNCETH:LN=0,SN=7,PN=0;
//Setting the clock working mode
SET CLKMODE:MODE=MANUAL,CLKSRC=SYNCETH;

8.4.1.3 Using the CME

For detailed operations, see CME-based Feature Configuration.

8.4.2 Activation Verification

1. After configuring a synchronous Ethernet clock as the gNodeB clock source, wait about 5 minutes in scenarios where the transmission quality is good.
2. Run the DSP CLKSTAT command to query the clock source status. If the value of Current Clock Source is SyncEth Clock and the value of PLL Status is Locked, this
function has taken effect.

8.4.3 Network Monitoring

None

8.4.4 Reconfiguration
None

9 Combined Synchronization Sources

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 27/38

11/15/23, 12:56 AM HedEx Startpage
Principles
gNodeBs support combined synchronization sources, which can be a combination of synchronous Ethernet with IEEE1588 V2. IEEE1588 V2 and synchronous Ethernet implement
time synchronization and frequency synchronization, respectively. The use of combined synchronization sources enhances time synchronization robustness and improves time
holdover performance. If the IEEE1588 V2 clock becomes faulty, synchronous Ethernet retains the current phase and the clock stays in the locked mode. The gNodeB clock enters
the holdover mode only when both clock sources are unavailable. Figure 9-1 shows an example of the combination of IEEE1588 V2 and synchronous Ethernet
Figure 9-1 Example combination of IEEE1588 V2 and synchronous Ethernet

For details on IEEE1588 V2 synchronization, see 7 IEEE1588 V2 Clock Synchronization.

For details on synchronous Ethernet synchronization, see 8 Synchronous Ethernet.

Network Analysis

9.2.1 Benefits
The use of combined synchronization sources enhances time synchronization robustness and improves time holdover performance.

9.2.2 Impacts

twork Impacts

None

nction Impacts

None

Requirements

9.3.1 Licenses
The following lists the license requirement for this function.

Feature ID Feature Name Model Sales Unit

FOFD-010070 Network Synchronization NR0S00STTN00 per gNodeB

9.3.2 Software

erequisite Functions

None

utually Exclusive Functions

None

9.3.3 Hardware

se Station Models

When a combination of IEEE1588 V2 and synchronous Ethernet is used, base stations must support both IEEE1588 V2 synchronization and synchronous Ethernet.

For details on the types of base stations supporting IEEE1588 V2, see 7.3.3 Hardware.
For details on the types of base stations supporting synchronous Ethernet, see 8.3.3 Hardware.

oards

If a combination of IEEE1588 V2 and synchronous Ethernet is used, boards need to support both IEEE1588 V2 synchronization and synchronous Ethernet.

For details on boards supporting IEEE1588 V2 synchronization, see 7.3.3 Hardware.

For details on boards supporting synchronous Ethernet, see 8.3.3 Hardware.

F Modules

None

9.3.4 Networking
The networking requirements of the combination of IEEE1588 V2 and synchronous Ethernet are as follows:

The IEEE1588 V2 server and synchronous Ethernet must extract clock signals from the same clock source and connect to the gNodeB using the same port.
The networking requirements of the IEEE1588 V2 clock are described in 7.3.4 Networking.
The networking requirements of synchronous Ethernet are described in 8.3.4 Networking.

9.3.5 Others

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 28/38

11/15/23, 12:56 AM HedEx Startpage
None

Operation and Maintenance

9.4.1 Activation and Performance Optimization

9.4.1.1 Data Preparation

Add an IP clock link. For details, see 7.4.1.1 Data Preparation.
Add a synchronous Ethernet clock link. For details, see 8.4.1.1 Data Preparation.
Configure the clock working mode, reference clock source, and reference clock source No. by running the SET CLKMODE command.
Configure the clock synchronization mode by running the SET CLKSYNCMODE command.
Table 9-1 Key parameters in the TASM MO

Parameter Name Parameter ID Setting Notes

Clock Working Mode TASM.MODE Set this parameter to MANUAL.

Selected Clock Source TASM.CLKSRC Set this parameter to SYNCETH+IPCLK.

Clock Source No. TASM.SRCNO Set this parameter to the link number specified when the clock link was
created.

Clock Synchronization Mode TASM.CLKSYNCMODE Set this parameter to TIME.

9.4.1.2 Using MML Commands

//Setting the clock synchronization mode
SET CLKSYNCMODE: CLKSYNCMODE=TIME;
//Configuring synchronous Ethernet as the clock source
ADD SYNCETH: LN=0, SN=7, PN=0;
//Configuring the IP clock as the clock source
ADD IPCLKLINK: LN=0, ICPT=PTP, SN=7, CNM=L2_MULTICAST, DM=0, DELAYTYPE=E2E, PRI=4, MACMODE=NO, PROFILETYPE=1588V2;
//Setting the clock working mode
SET CLKMODE: MODE=MANUAL, CLKSRC=SYNCETH+IPCLK;

9.4.1.3 Using the CME

For detailed operations, see CME-based Feature Configuration.

9.4.2 Activation Verification

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.
2. Run the DSP CLKSTAT command to query the clock source status. If the value of Current Clock Source is SyncEth Clock+IP Clock and the value of PLL Status is
Locked, this function has taken effect.

9.4.3 Network Monitoring

None

9.4.4 Reconfiguration
None

10 Comparison of Synchronization Technologies

Table 10-1 compares the common synchronization solutions for gNodeBs. TDD gNodeBs support only time synchronization.

Table 10-1 Advantages and disadvantages of common synchronization solutions

Synchronization Solution Frequency Time Advantage Disadvantage

Synchronization Synchronization

GPS and RGPS Supported Supported Each gNodeB is configured with a GPS Costs in the GPS satellite card or RGPS device
satellite card or RGPS device, and does not and their installation and maintenance are
require support of the network. required.

BeiDou Supported Supported Each gNodeB is configured with a BeiDou Costs in the BeiDou device and its installation
device, and does not require support of the and maintenance are required.
network.

IEEE1588 V2 Supported Supported 1. When IEEE1588 V2 is used only for 1. To achieve time synchronization, all
frequency synchronization, this technology intermediate transmission equipment must be
supports transparent transmission across the upgraded to support IEEE1588.
data bearer network and has low requirements 2. The clock recovery quality is susceptible to
for the intermediate transmission equipment. the delay, jitter, and packet loss on the data
2. This solution supports both frequency bearer network.
synchronization and time synchronization and
meets the clock requirements of the TDD
mode.
3. IEEE1588 V2 is a standard protocol.
Different profiles complying with IEEE1588 V2
support interworking between IEEE1588 V2-
compliant equipment of different
manufacturers.

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 29/38

11/15/23, 12:56 AM HedEx Startpage

Synchronization Solution Frequency Time Advantage Disadvantage

Synchronization Synchronization

Synchronous Ethernet Supported Not supported 1. Clock signals are extracted from the 1. This solution does not support time
physical layer and are not related to upper synchronization.
layer services. Therefore, the interworking 2. In the network, besides gNodeBs, the
performance is satisfactory. intermediate transmission equipment such as
2. The clock recovery quality is satisfactory. hubs and LAN switches must be capable of
This solution is mature and not susceptible to transparent transmission or regeneration of
packet losses and jitter. clock signals at the physical layer.
3. The transmission of clock signals does not
occupy transmission bandwidth.

11 Synchronization-related Alarms

The following table lists the alarms related to synchronization. For details on how to handle these alarms, see 3900 & 5900 Series Base Station Alarm Reference.

Alarm ID Alarm Name

ALM-26120 GPS Clock Output Unavailable

ALM-26121 GPS Antenna Fault

ALM-26122 GPS Locked Satellites Insufficient

ALM-26123 GPS Maintenance Link Failure

ALM-26260 System Clock Failure

ALM-26261 External Clock Reference Not Configured

ALM-26262 External Clock Reference Problem

ALM-26264 System Clock Unlocked

ALM-26265 Base Station Frame Number Synchronization Error

ALM-26266 Time Synchronization Failure

12 Parameters

Table 12-1 Parameters

MO Parameter ID MML Feature ID Feature Name Description

Command

TASM MODE SET CLKMODE MRFD-210501 BTS Clock Meaning: Indicates the working mode of the system clock. Manual indicates
DSP CLKSTAT LBFD-003005 Synchronization that a clock source must be specified by the user. Auto indicates that the
LST CLKMODE
LBFD- Clock Source system automatically selects a clock source based on the priority and
00300501 Switching availability of the clock source. Free indicates that the system clock works in
Manually or free-running mode, that is, the system clock does not trace any reference clock
LBFD- source.
00300502 Automatically
Free-running GUI Value Range: AUTO(Auto), MANUAL(Manual), FREE(Free)
LBFD-
00300503 Mode Unit: None
LBFD- Synchronization Actual Value Range: AUTO, MANUAL, FREE
00300504 with GPS Default Value: FREE(Free)
LBFD- Synchronization
00300505 with BITS
LBFD- Synchronization
00300506 with 1PPS
LOFD-003013 Synchronization
LOFD- with E1/T1
00301301 Enhanced
LOFD- Synchronization
00301302 Synchronization
LOFD- with Ethernet
00301303 (ITU-T G.8261)
LOFD-003023 IEEE1588 V2
Clock
MRFD-121117 Synchronization
MRFD-121127 Clock over IP
MRFD-121137 (Huawei
MRFD-121147 proprietary)
MRFD-121157 IEEE 1588v2
over IPv6

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 30/38

11/15/23, 12:56 AM HedEx Startpage

MO Parameter ID MML Feature ID Feature Name Description

Command
Multi-mode BS
Common
Reference
Clock(GBTS)
Multi-mode BS
Common
Reference
Clock(NodeB)
Multi-mode BS
Common
Reference
Clock(eNodeB)
Multi-mode BS
Common
Reference
Clock (LTE
TDD)
Multi-mode BS
Common
Reference
Clock(NB-IoT)

TASM CLKSRC SET CLKMODE MRFD-210501 BTS Clock Meaning: Indicates the type of the user-selected clock source.
LST CLKMODE LBFD-003005 Synchronization GUI Value Range: GPS(GPS Clock), BITS(BITS Clock), IPCLK(IP Clock),
LBFD- Clock Source SYNCETH(SyncEth Clock), LINECLK(Line Clock), TOD(TOD Clock),
00300501 Switching PEERCLK(Peer Clock), SYNCETH+IPCLK(SyncEth Clock+IP Clock),
LBFD- Manually or GPS+SYNCETH(GPS Clock+SyncEth Clock), INTERCLK(Inter Clock)
00300503 Automatically Unit: None
LBFD- Synchronization Actual Value Range: GPS, BITS, IPCLK, SYNCETH, LINECLK, TOD,
00300504 with GPS PEERCLK, SYNCETH+IPCLK, GPS+SYNCETH, INTERCLK
LBFD- Synchronization Default Value: GPS(GPS Clock)
00300505 with BITS
LBFD- Synchronization
00300506 with 1PPS
LOFD-003013 Synchronization
LOFD- with E1/T1
00301301 Enhanced
LOFD- Synchronization
00301302 Synchronization
LOFD- with Ethernet
00301303 (ITU-T G.8261)
LOFD-003023 IEEE1588 V2
Clock
Synchronization
Clock over IP
(Huawei
proprietary)
IEEE 1588v2
over IPv6

TASM SRCNO SET CLKMODE MRFD-210501 BTS Clock Meaning: Indicates the clock link number of the reference clock source. When
DSP CLKSRC LBFD-003005 Synchronization the Selected Clock Source parameter is set to GPS+SYNCETH, this parameter
DSP PHASEDIFF
LBFD- Clock Source indicates the number of the GPS clock link. When the Selected Clock Source
LST CLKMODE 00300501 Switching parameter is set to SYNCETH+IPCLK, this parameter indicates the number of
Manually or the IP clock link. When this parameter is set to AUTO, the system selects an
LBFD- available clock link from those of the specified reference clock source. If there
00300503 Automatically
is more than one clock link and the selected clock link fails, another available
LBFD- Synchronization clock link will be used.
00300504 with GPS
GUI Value Range: 0(0), 1(1), 2(2), 3(3), 4(4), 5(5), 6(6), 7(7), 8(8), 9(9), 10(10),
LBFD- Synchronization 11(11), 12(12), 13(13), 14(14), 15(15), 16(16), 17(17), AUTO(AUTO)
00300505 with BITS
Unit: None
LBFD- Synchronization
with 1PPS Actual Value Range: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17,
00300506 AUTO
LOFD-003013 Synchronization
with E1/T1 Default Value: 0(0)
LOFD-
00301301 Enhanced
LOFD- Synchronization
00301302 Synchronization
LOFD- with Ethernet
00301303 (ITU-T G.8261)
LOFD-003023 IEEE1588 V2
Clock
MRFD-121117
Synchronization
MRFD-121127
Clock over IP
MRFD-121137 (Huawei
MRFD-121147 proprietary)
MRFD-121157 IEEE 1588v2
over IPv6
Multi-mode BS
Common
Reference
Clock(GBTS)
Multi-mode BS
Common

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 31/38

11/15/23, 12:56 AM HedEx Startpage

MO Parameter ID MML Feature ID Feature Name Description

Command
Reference
Clock(NodeB)
Multi-mode BS
Common
Reference
Clock(eNodeB)
Multi-mode BS
Common
Reference
Clock (LTE
TDD)
Multi-mode BS
Common
Reference
Clock(NB-IoT)

TASM CLKSYNCMODE SET MRFD-210501 BTS Clock Meaning: Indicates the clock synchronization mode of a BS, which can be
CLKSYNCMODE frequency synchronization or time synchronization.
MRFD-121117 Multi-mode BS
DSP CLKSTAT
LBFD-003005 Common GUI Value Range: FREQ(FREQ), TIME(TIME), HYBRID(HYBRID)
LST Reference
CLKSYNCMODE LBFD- Unit: None
00300501 Clock(GBTS) Actual Value Range: FREQ, TIME, HYBRID
LBFD- Synchronization Default Value: FREQ(FREQ)
00300503 Clock Source
LBFD- Switching
00300504 Manually or
Automatically
LBFD-
00300505 Synchronization
with GPS
LBFD-
00300506 Synchronization
with BITS
LOFD-003013
Synchronization
LOFD- with 1PPS
00301301
Synchronization
LOFD- with E1/T1
00301302
Enhanced
LOFD- Synchronization
00301303
Synchronization
LOFD-003023
with Ethernet
TDLBFD- (ITU-T G.8261)
003005
IEEE1588 V2
TDLBFD- Clock
00300501 Synchronization
TDLBFD- Clock over IP
00300502 (Huawei
TDLBFD- proprietary)
00300503 IEEE 1588v2
TDLBFD- over IPv6
00300505 Synchronization
TDLBFD- Clock Source
111102 Switching
TDLOFD- Manually or
003013 Automatically
TDLOFD- Free-running
00301302 Mode
Synchronization
with GPS
Synchronization
with 1PPS
Synchronization
with BeiDou
Enhanced
Synchronization
IEEE1588 V2
Clock
Synchronization

GPS CN ADD GPS None None Meaning: Indicates the cabinet number of the board where the satellite card is
LST GPS attached.
GUI Value Range: 0~7
Unit: None
Actual Value Range: 0~7
Default Value: 0

GPS SRN ADD GPS None None Meaning: Indicates the subrack number of the board where the satellite card is
LST GPS attached.
GUI Value Range: 0~1,60~254
Unit: None
Actual Value Range: 0~1,60~254
Default Value: 0

GPS SN ADD GPS None None Meaning: Indicates the slot number of the board where the satellite card is
LST GPS attached.
GUI Value Range: 0~7

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 32/38

11/15/23, 12:56 AM HedEx Startpage

MO Parameter ID MML Feature ID Feature Name Description

Command
Unit: None
Actual Value Range: 0~7
Default Value: 7

GPS GN ADD GPS MRFD-210501 BTS Clock Meaning: Indicates the number of the GPS clock link.
DSP GPS LBFD- Synchronization GUI Value Range: 0~17
MOD GPS 00300503 with GPS Unit: None
RMV GPS TDLBFD- Synchronization Actual Value Range: 0~17
RST SATCARD 00300503 with GPS
LST GPS
Default Value: 0
TDLBFD- Synchronization
111102 with BeiDou

GPS CABLE_LEN ADD GPS MRFD-210501 BTS Clock Meaning: Indicates the length of the GPS feeder. The actual feeder length is
MOD GPS TDLBFD- Synchronization the one between the GPS antenna and the board connected to the GPS
LST GPS 00300503 with GPS antenna. Based on the feeder length, the feeder delay is calculated to ensure
TDLBFD- Synchronization the clock accuracy. When the actual feeder length is less than 20 m (66 ft), this
111102 with BeiDou parameter is optional. When the actual feeder length is greater than or equal to
20 m (66 ft), this parameter is mandatory. If this parameter is not specified in
LBFD- Synchronization this case, the clock accuracy will be affected and services may be affected.
00300503 with GPS
GUI Value Range: 0~1000(metric system);0~3281(imperial system)
TDLBFD- Synchronization
00300503 with GPS Unit: m(metric system);ft(imperial system)
TDLBFD- Synchronization Actual Value Range: 0~1000(metric system);0~3281(imperial system)
111102 with BeiDou Default Value: 0(metric system);0(imperial system)

GPS MODE ADD GPS MRFD-210501 BTS Clock Meaning: Indicates the working mode of the satellite card. Satellite cards are
MOD GPS LBFD- Synchronization classified into dual-mode satellite cards and single-mode satellite cards. A dual-
DSP GPS 00300503 with GPS mode satellite card supports two satellite searching modes. For example, the
LST GPS TDLBFD- Synchronization working mode of a BDS/GPS satellite card can be BDS prioritized or GPS
00300503 with GPS prioritized. In BDS prioritized mode, the satellite card processes signals from
BDS satellites only. In GPS prioritized mode, the satellite card processes
TDLBFD- Synchronization
signals from GPS satellites only. In addition, some satellite cards such as the
111102 with BeiDou
UBOLX8M do not prioritize the BDS or GPS but process signals from both BDS
satellites and GPS satellites. A single-mode satellite card supports only one
satellite searching mode. For example, a satellite card working in GPS mode.
GUI Value Range: GPS(GPS), GLONASS(GLONASS),
GPS/GLONASS(GPS/GLONASS with GPS Prioritized), BDS(BDS),
BDS/GPS(BDS/GPS with BDS Prioritized), GPS/BDS(GPS/BDS with GPS
Prioritized)
Unit: None
Actual Value Range: GPS, GLONASS, GPS/GLONASS, BDS, BDS/GPS,
GPS/BDS
Default Value: GPS(GPS)

GPS PRI ADD GPS None None Meaning: Indicates the priority of the clock source. The value 1 indicates the
MOD GPS current clock source has the highest priority, and the value 4 indicates the
LST GPS current clock source has the lowest priority.
GUI Value Range: 1~4
Unit: None
Actual Value Range: 1~4
Default Value: 4

GPS WPOS MOD GPSPOS MRFD-210501 BTS Clock Meaning: Indicates the mode to obtain the position of the GPS satellite.
LST GPSPOS LBFD- Synchronization GUI Value Range: USER_CONFIG(User Config),
00300503 with GPS SEARCH_WITH_DURATION(Search with duration),
TDLBFD- Synchronization SEARCH_WITH_PRECISION(Search with precision), AUTO_SEARCH(Auto
00300503 with GPS Search)
TDLBFD- Synchronization Unit: None
111102 with BeiDou Actual Value Range: USER_CONFIG, SEARCH_WITH_DURATION,
SEARCH_WITH_PRECISION, AUTO_SEARCH
Default Value: AUTO_SEARCH(Auto Search)

GPS LONG MOD GPSPOS MRFD-210501 BTS Clock Meaning: Indicates the longitude of the GPS antenna. A negative value
DSP GPS LBFD- Synchronization indicates the west longitude, and a positive value indicates the east longitude.
LST GPSPOS 00300503 with GPS GUI Value Range: -180000000~180000000
TDLBFD- Synchronization Unit: 1e-6 degree
00300503 with GPS Actual Value Range: -180~180, step: 1e-6
TDLBFD- Synchronization Default Value: 0
111102 with BeiDou

GPS LAT MOD GPSPOS MRFD-210501 BTS Clock Meaning: Indicates the latitude of the GPS antenna. A negative value indicates
DSP GPS LBFD- Synchronization the south latitude, and a positive value indicates the north latitude.
LST GPSPOS 00300503 with GPS GUI Value Range: -90000000~90000000
TDLBFD- Synchronization Unit: 1e-6 degree
00300503 with GPS Actual Value Range: -90~90, step: 1e-6
TDLBFD- Synchronization Default Value: 0
111102 with BeiDou

GPS ALT MOD GPSPOS MRFD-210501 BTS Clock Meaning: Indicates the altitude of the GPS antenna. A negative value indicates
DSP GPS TDLBFD- Synchronization that the GPS antenna is below the sea level, and a positive value indicates that
LST GPSPOS 00300503 with GPS the GPS antenna is above the sea level.
TDLBFD- Synchronization GUI Value Range: -1000~10000(metric system);-3281~32808(imperial system)
111102 with BeiDou Unit: m(metric system);ft(imperial system)

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 33/38

11/15/23, 12:56 AM HedEx Startpage

MO Parameter ID MML Feature ID Feature Name Description

Command
LBFD- Synchronization Actual Value Range: -1000~10000(metric system);-3281~32808(imperial
00300503 with GPS system)
TDLBFD- Synchronization Default Value: 0(metric system);0(imperial system)
00300503 with GPS
TDLBFD- Synchronization
111102 with BeiDou

GPS AGL MOD GPSPOS MRFD-210501 BTS Clock Meaning: Indicates the antenna angle, which is the angle with the horizontal
DSP GPS TDLBFD- Synchronization line. If the clock source has not been activated, the value NULL will be
LST GPSPOS 00300503 with GPS displayed. If the clock source has been activated, the value NULL indicates that
TDLBFD- Synchronization this parameter is not supported by the hardware or the hardware is faulty.
111102 with BeiDou GUI Value Range: 0~89
LBFD- Synchronization Unit: degree
00300503 with GPS Actual Value Range: 0~89
TDLBFD- Synchronization Default Value: 5
00300503 with GPS
TDLBFD- Synchronization
111102 with BeiDou

IPCLKLNK CNM ADD IPCLKLINK WRFD- Clock Sync on Meaning: Indicates the networking type for the IP clock. The LTE currently does
LST IPCLKLINK 050501 Ethernet in not support L3 Multicast function.
GBFD-118620 NodeB GUI Value Range: UNICAST(Unicast), L3_MULTICAST(L3 Multicast),
LOFD- Clock over IP L2_MULTICAST(L2 Multicast)
00301301 support 1588v2 Unit: None
LOFD- Synchronization Actual Value Range: UNICAST, L3_MULTICAST, L2_MULTICAST
00301302 with Ethernet Default Value: UNICAST(Unicast)
LOFD- (ITU-T G.8261)
00301303 IEEE1588 V2
LOFD-003023 Clock
Synchronization
Clock over IP
(Huawei
proprietary)
IEEE 1588v2
over IPv6

IPCLKLNK ICPT ADD IPCLKLINK WRFD- Clock Sync on Meaning: Indicates the type of the IP clock protocol, which can be PTP or
LST IPCLKLINK 050501 Ethernet in Huawei proprietary protocol. PTP includes IEEE1588 V2, G.8265.1,
GBFD-118606 NodeB 1588V2_16.1, G.8275.1 and G.8275.2. IEEE1588 V2, defined by the IEEE,
GBFD-118620 Clock over IP supports both time synchronization and frequency synchronization. G.8265.1
Clock over IP supports frequency synchronization only. 1588 V2_16.1 supports both time
LOFD- synchronization and frequency synchronization. G.8275.1 supports time
00301301 support 1588v2
synchronization only. G.8275.2 supports time synchronization only. Huawei
LOFD- Synchronization proprietary protocol, which is the Huawei-defined IP clock protocol, applies to
00301302 with Ethernet the interconnection between Huawei equipment and supports frequency
LOFD- (ITU-T G.8261) synchronization only.
00301303 IEEE1588 V2 GUI Value Range: HW_DEFINED(HuaWei Defined Protocol), PTP(PTP)
LOFD-003023 Clock
Synchronization Unit: None
TDLOFD- Actual Value Range: HW_DEFINED, PTP
00301302 Clock over IP
(Huawei Default Value: PTP(PTP)
proprietary)
IEEE 1588v2
over IPv6
IEEE1588 V2
Clock
Synchronization

IPCLKLNK DELAYTYPE ADD IPCLKLINK WRFD- Clock Sync on Meaning: Indicates the compensation mechanism for the transmission delay
LST IPCLKLINK 050501 Ethernet in between the clock server and the NE. The E2E mode uses the Delay-Request-
GBFD-118620 NodeB Response mechanism to measure the average delay between the primary and
LOFD- Clock over IP secondary devices. The P2P mode uses the Peer-Delay mechanism to
00301301 support 1588v2 measure the average delay between two devices.
LOFD- Synchronization GUI Value Range: E2E(E2E), P2P(P2P)
00301302 with Ethernet Unit: None
LOFD- (ITU-T G.8261) Actual Value Range: E2E, P2P
00301303 IEEE1588 V2 Default Value: E2E(E2E)
LOFD-003023 Clock
Synchronization
Clock over IP
(Huawei
proprietary)
IEEE 1588v2
over IPv6

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 34/38

11/15/23, 12:56 AM HedEx Startpage

MO Parameter ID MML Feature ID Feature Name Description

Command

IPCLKLNK CMPST ADD IPCLKLINK WRFD- Clock Sync on Meaning: Indicates the compensation for asymmetry of IP clock links.
LST IPCLKLINK 050501 Ethernet in GUI Value Range: -100000~100000
GBFD-118620 NodeB Unit: ns
LOFD- Clock over IP Actual Value Range: -100000~100000
00301301 support 1588v2
Default Value: 0
LOFD- Synchronization
00301302 with Ethernet
LOFD- (ITU-T G.8261)
00301303 IEEE1588 V2
LOFD-003023 Clock
Synchronization
Clock over IP
(Huawei
proprietary)
IEEE 1588v2
over IPv6

IPCLKLNK IPSYNCMODE ADD IPCLKLINK None None Meaning: Indicates the IP clock synchronization mode. This parameter is
LST IPCLKLINK applicable only when Clock Synchronization Mode is set to HYBRID.
GUI Value Range: FREQ(FREQ), TIME(TIME)
Unit: None
Actual Value Range: FREQ, TIME
Default Value: FREQ(FREQ)

IPCLKLNK PROFILETYPE ADD IPCLKLINK WRFD- Clock Sync on Meaning: Indicates the type of protocol supported by the IEEE 1588 V2-
LST IPCLKLINK 050501 Ethernet in compliant IP clock link, which can be ITU-T G.8265.1, IEEE 1588 V2,
GBFD-118620 NodeB IEEE1588V2_16.1, ITU-T G.8275.1 or ITU-T G.8275.2. ITU-T G.8265.1 is
LOFD- Clock over IP defined by the International Telecommunication Union (ITU) for frequency
00301301 support 1588v2 synchronization of an IEEE 1588 V2-compliant IP clock link with the networking
Synchronization type of UNICAST. An IP clock link in compliant with ITU-T G.8265.1 supports
LOFD- interconnection with servers from other vendors. An IP clock link in compliant
00301302 with Ethernet
(ITU-T G.8261) with IEEE 1588 V2 supports interconnection with clock service devices from
LOFD- other vendors only in L2 or L3 multicast networking. IEEE1588V2_16.1 can
00301303 IEEE1588 V2 also be used for interconnection with clock service devices from other vendors
LOFD-003023 Clock when the other vendors do not support ITU-T G.8265.1.The contents of
Synchronization IEEE1588V2_16.1 refers to the optional section 16.1 of IEEE1588V2 protocol.
TDLOFD-
00301302 Clock over IP ITU-T G.8275.1 is defined by the International Telecommunication Union (ITU)
(Huawei for time synchronization of an IEEE 1588 V2-compliant IP clock link with the
proprietary) networking type of L2 multicast. An IP clock link in compliant with ITU-T
IEEE 1588v2 G.8275.1 supports interconnection with clock service devices from other
over IPv6 vendors.ITU-T G.8275.2 is defined by the International Telecommunication
IEEE1588 V2 Union (ITU) for time synchronization of an IEEE 1588 V2-compliant IP clock
Clock link with the networking type of L3 unicast. An IP clock link in compliant with
Synchronization ITU-T G.8275.2 supports interconnection with clock service devices from other
vendors.
GUI Value Range: 1588V2(1588V2), G.8265.1(G.8265.1),
1588V2_16.1(1588V2_16.1), G.8275.1(G.8275.1), G.8275.2(G.8275.2)
Unit: None
Actual Value Range: 1588V2, G.8265.1, 1588V2_16.1, G.8275.1, G.8275.2
Default Value: 1588V2(1588V2)

IPCLKLNK ANNFREQ ADD IPCLKLINK WRFD- Clock Sync on Meaning: Indicates the frequency at which the clock source sends
LST IPCLKLINK 050501 Ethernet in announcement packets based on its negotiation with the NE.
GBFD-118620 NodeB GUI Value Range: 1/16(1/16), 1/8(1/8), 1/4(1/4), 1/2(1/2), 1.0(1.0), 2.0(2.0),
LOFD- Clock over IP 4.0(4.0), 8.0(8.0)
00301301 support 1588v2 Unit: Hz
LOFD- Synchronization Actual Value Range: 1/16, 1/8, 1/4, 1/2, 1.0, 2.0, 4.0, 8.0
00301302 with Ethernet Default Value: 1/2(1/2)
LOFD- (ITU-T G.8261)
00301303 IEEE1588 V2
LOFD-003023 Clock
Synchronization
TDLOFD-
00301302 Clock over IP
(Huawei
proprietary)
IEEE 1588v2
over IPv6
IEEE1588 V2
Clock
Synchronization

IPCLKLNK NEGDURATION ADD IPCLKLINK WRFD- Clock Sync on Meaning: Indicates the interval at which negotiations are performed between
LST IPCLKLINK 050501 Ethernet in the NE and IP clock server. After the interval elapses, the NE initiates another
GBFD-118620 NodeB negotiation with the IP clock server.
LOFD- Clock over IP GUI Value Range: 60~1000
00301301 support 1588v2 Unit: s
LOFD- Synchronization Actual Value Range: 60~1000
00301302 with Ethernet Default Value: 300
LOFD- (ITU-T G.8261)
00301303 IEEE1588 V2
LOFD-003023 Clock
Synchronization
TDLOFD-
00301302 Clock over IP
(Huawei

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 35/38

11/15/23, 12:56 AM HedEx Startpage

MO Parameter ID MML Feature ID Feature Name Description

Command
proprietary)
IEEE 1588v2
over IPv6
IEEE1588 V2
Clock
Synchronization

IPCLKLNK DSTMLTMACTYPE ADD IPCLKLINK WRFD- Clock Sync on Meaning: Indicates the type of the destination multicast MAC address to which
LST IPCLKLINK 050501 Ethernet in an NE sends G.8275.1 clock synchronization packets. Forwardable Multicast
GBFD-118620 NodeB MAC Address (FMAC) means that the destination MAC address to which the
LOFD- Clock over IP NE sends clock synchronization packets is 01-1B-19-00-00-00. Non-
00301302 support 1588V2 Forwardable Multicast MAC Address (NFMAC) means that the destination
IEEE1588 V2 MAC address to which the NE sends clock synchronization packets is 01-80-
TDLOFD-
Clock C2-00-00-0E. The NE can handle clock synchronization packets from both
00301302
Synchronization FMAC and NFMAC.
IEEE1588 V2 GUI Value Range: FMAC(Forwardable Multicast MAC Address), NFMAC(Non-
Clock Forwardable Multicast MAC Address)
Synchronization Unit: None
Actual Value Range: FMAC, NFMAC
Default Value: FMAC(Forwardable Multicast MAC Address)

IPCLKLNK CLASSIDENTIFY SET WRFD- Clock Sync on Meaning: Indicates whether the BMC (Best Master Clock) algorithm is enabled
CLASSIDENTIFY 050501 Ethernet in or not. ON indicates that the BMC algorithm is enabled, and OFF indicates that
DSP PRICLASS NodeB the BMC algorithm is disabled.
GBFD-118620
LOFD- Clock over IP GUI Value Range: OFF(OFF), ON(ON)
00301302 support 1588v2 Unit: None
LOFD-003023 IEEE1588 V2 Actual Value Range: OFF, ON
Clock Default Value: ON(ON)
Synchronization
IEEE 1588v2
over IPv6

IPCLKLNK LN ADD IPCLKLINK WRFD- Clock Sync on Meaning: Indicates the number of the IP clock link.
DSP IPCLKLINK 050501 Ethernet in GUI Value Range: 0~2
DSP PRICLASS GBFD-118606 NodeB Unit: None
RMV IPCLKLINK GBFD-118620 Clock over IP Actual Value Range: 0~2
SET Clock over IP
CLASSIDENTIFY
LOFD- Default Value: 0
00301301 support 1588v2
SET PRICLASS
LOFD- Synchronization
LST IPCLKLINK
00301302 with Ethernet
LST PRICLASS
LOFD- (ITU-T G.8261)
00301303 IEEE1588 V2
LOFD-003023 Clock
Synchronization
TDLOFD-
00301302 Clock over IP
(Huawei
proprietary)
IEEE 1588v2
over IPv6
IEEE1588 V2
Clock
Synchronization

IPCLKLNK CIP ADD IPCLKLINK WRFD- Clock Sync on Meaning: Indicates the client IPv4 address of the IP clock link.
DSP IPCLKLINK 050501 Ethernet in GUI Value Range: Valid IP address
LST IPCLKLINK GBFD-118606 NodeB Unit: None
GBFD-118620 Clock over IP Actual Value Range: Valid IP address
LOFD- Clock over IP Default Value: 0.0.0.0
00301301 support 1588v2
LOFD- Synchronization
00301302 with Ethernet
LOFD- (ITU-T G.8261)
00301303 IEEE1588 V2
LOFD-003023 Clock
Synchronization
TDLOFD-
00301302 Clock over IP
(Huawei
proprietary)
IEEE 1588v2
over IPv6
IEEE1588 V2
Clock
Synchronization

IPCLKLNK SIP ADD IPCLKLINK WRFD- Clock Sync on Meaning: Indicates the server IPv4 address of the IP clock link.
LST IPCLKLINK 050501 Ethernet in GUI Value Range: Valid IP address
GBFD-118606 NodeB Unit: None
GBFD-118620 Clock over IP Actual Value Range: Valid IP address
LOFD- Clock over IP Default Value: 0.0.0.0
00301301 support 1588v2
LOFD- Synchronization
00301302 with Ethernet
LOFD- (ITU-T G.8261)
00301303

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 36/38

11/15/23, 12:56 AM HedEx Startpage

MO Parameter ID MML Feature ID Feature Name Description

Command
LOFD-003023 IEEE1588 V2
TDLOFD- Clock
00301302 Synchronization
Clock over IP
(Huawei
proprietary)
IEEE 1588v2
over IPv6
IEEE1588 V2
Clock
Synchronization

IPCLKLNK DM ADD IPCLKLINK WRFD- Clock Sync on Meaning: Indicates the domain to which the IP clock link belongs. The setting
LST IPCLKLINK 050501 Ethernet in of this parameter must be the same as the setting of the clock server.
GBFD-118620 NodeB GUI Value Range: 0~255
LOFD- Clock over IP Unit: None
00301301 support 1588v2 Actual Value Range: 0~255
LOFD- Synchronization Default Value: 0
00301302 with Ethernet
LOFD- (ITU-T G.8261)
00301303 IEEE1588 V2
LOFD-003023 Clock
Synchronization
TDLOFD-
00301302 Clock over IP
(Huawei
proprietary)
IEEE 1588v2
over IPv6
IEEE1588 V2
Clock
Synchronization

IPCLKLNK PRI ADD IPCLKLINK WRFD- Clock Sync on Meaning: Indicates the priority of the clock source. The value 1 indicates that
LST IPCLKLINK 050501 Ethernet in the current clock source has the highest priority, and the value 4 indicates that
GBFD-118606 NodeB the current clock source has the lowest priority.
GBFD-118620 Clock over IP GUI Value Range: 1~4
LOFD- Clock over IP Unit: None
00301301 support 1588v2 Actual Value Range: 1~4
LOFD- Synchronization Default Value: 4
00301302 with Ethernet
LOFD- (ITU-T G.8261)
00301303 IEEE1588 V2
LOFD-003023 Clock
Synchronization
TDLOFD-
00301302 Clock over IP
(Huawei
proprietary)
IEEE 1588v2
over IPv6
IEEE1588 V2
Clock
Synchronization

IPCLKLNK MASTERPRIO ADD IPCLKLINK WRFD- Clock Sync on Meaning: Indicates the priority of the IP clock server. The value 0 indicate the
LST IPCLKLINK 050501 Ethernet in highest priority, and the value 255 indicates the lowest priority. If two IP clock
GBFD-118620 NodeB servers are required, the value of this parameter is used to identify the active
LOFD- Clock over IP and standby IP clock servers. The IP clock server with a higher priority serves
00301301 support 1588v2 as the active server and the IP clock server with a lower priority serves as the
Synchronization standby server.
LOFD-
00301302 with Ethernet GUI Value Range: 0~255
LOFD- (ITU-T G.8261) Unit: None
00301303 IEEE1588 V2 Actual Value Range: 0~255
LOFD-003023 Clock Default Value: 255
Synchronization
Clock over IP
(Huawei
proprietary)
IEEE 1588v2
over IPv6

SYNCETH LN ADD SYNCETH WRFD- Clock Sync on Meaning: Indicates the number of the synchronous-Ethernet clock link. A
DSP SYNCETH 050502 Ethernet maximum of two links can be configured currently.
MOD SYNCETH GBFD-118202 Synchronous GUI Value Range: 0~1
RMV SYNCETH LOFD-003013 Ethernet Unit: None
LST SYNCETH Enhanced
LOFD- Actual Value Range: 0~1
00301301 Synchronization Default Value: 0
Synchronization
with Ethernet
(ITU-T G.8261)

SYNCETH PN ADD SYNCETH WRFD- Clock Sync on Meaning: Indicates the number of the port where the synchronous-Ethernet
LST SYNCETH 050502 Ethernet clock link is configured.
GBFD-118202 Synchronous GUI Value Range: 0~5
LOFD-003013 Ethernet Unit: None

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 37/38

11/15/23, 12:56 AM HedEx Startpage

MO Parameter ID MML Feature ID Feature Name Description

Command
LOFD- Enhanced Actual Value Range: 0~5
00301301 Synchronization Default Value: 0
Synchronization
with Ethernet
(ITU-T G.8261)

SYNCETH SSM ADD SYNCETH WRFD- Clock Sync on Meaning:

MOD SYNCETH 050502 Ethernet Indicates whether handling of SSM frames is supported. The setting of this
DSP SYNCETH GBFD-118202 Synchronous parameter is consistent with the setting on the Ethernet clock server.
LST SYNCETH LOFD-003013 Ethernet The synchronization status message(SSM)carries clock quality information,
LOFD- Enhanced which is specified in ITU-T.
00301301 Synchronization This parameter is valid only when the synchronous-Ethernet clock link is of the
Synchronization input type.
with Ethernet GUI Value Range: DISABLE(DISABLE), ENABLE(ENABLE)
(ITU-T G.8261) Unit: None
Actual Value Range: DISABLE, ENABLE
Default Value: DISABLE(DISABLE)

SYNCETH PRI ADD SYNCETH WRFD- Clock Sync on Meaning: Indicates the priority of the clock source. The value 1 indicates that
MOD SYNCETH 050502 Ethernet the current clock source has the highest priority, and the value 4 indicates that
LST SYNCETH GBFD-118202 Synchronous the current clock source has the lowest priority.
LOFD-003013 Ethernet GUI Value Range: 1~4
LOFD- Enhanced Unit: None
00301301 Synchronization Actual Value Range: 1~4
Synchronization Default Value: 4
with Ethernet
(ITU-T G.8261)

13 Counters

There are no specific counters associated with this feature.

14 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

15 Reference Documents

1. IEEE 1588 V2, "Precision Clock Synchronization Protocol for Networked Measurement and Control Systems"
2. ITU-T G.8261, "Timing and Synchronization aspects in Packet Networks"
3. ITU-T G.8262, "Timing characteristics of synchronous Ethernet equipment slave clock (EEC)"
4. ITU-T G.8264, "Distribution of timing through packet networks"
5. ITU-T G. 8265.1, Precision time protocol telecom profile for frequency synchronization
6. ITU-T G.8275.1, Precision time protocol telecom profile for phase/time synchronization with full timing support from the network
7. GPS Satellite Antenna System Quick Installation Guide

localhost:7890/printtopics.html?time=Wed Nov 15 2023 00:56:25 GMT+0500 (Pakistan Standard Time) 38/38