Common Clock (SRAN18.1 - Draft A)
Common Clock (SRAN18.1 - Draft A)
Issue Draft A
Date 2021-12-30
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.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: https://www.huawei.com
Email: [email protected]
Contents
1 Change History.........................................................................................................................1
1.1 SRAN18.1 Draft A (2021-12-30)........................................................................................................................................ 1
5 Parameters.............................................................................................................................. 80
6 Counters.................................................................................................................................. 82
7 Glossary................................................................................................................................... 83
8 Reference Documents...........................................................................................................84
1 Change History
Technical Changes
None
Editorial Changes
Revised descriptions in this document.
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 optimal gains, contact Huawei professional service engineers.
Software 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.
NOTE
● In this document, GBTS/eGBTS, NodeB, eNodeB, and gNodeB correspond to the GSM,
UMTS, LTE, and NR modes of a multimode base station, respectively.
● Unless otherwise specified, in this document, LTE and eNodeB always include FDD, TDD,
and NB-IoT.
● Unless otherwise specified, in this document, NR and gNodeB always include FDD and
TDD.
For definitions of base stations described in this document, see section "Base
Station Products" in SRAN Networking and Evolution Overview.
NR MRFD-151 Multi-mode BS
166 Common Reference
Clock(NR)
3.1 Principles
3.1.1 Overview
In Common Clock, all RATs of a multimode base station share a clock source. In
common clock mode, a multimode base station requires only one clock source,
and all RATs synchronize with this clock source. This reduces the number of clock
sources to be deployed and helps cut costs.
The following clock sources can be shared in multimode base stations: GPS/
BeiDou/Galileo/GLONASS clock, BITS clock, E1/T1 clock, IEEE 1588V2 clock,
synchronous Ethernet (SyncE) clock, 1PPS+TOD clock, IEEE 1588V2+SyncE clock,
and GNSS+SyncE clock. The IEEE 1588V2 clock and SyncE clock are feature
enhancements. Each RAT has separate license control items for these two types of
clocks. When Common Clock is activated, the license of IEEE 1588V2 clock or
SyncE clock for a single RAT can be shared by other RATs.
Separate-MPT Scenarios
For a separate-MPT multimode base station, each RAT can be connected to an
external clock source or use the clock source provided by another RAT. To reduce
configuration conflicts, save clock sources, and simplify configurations, it is
recommended that a multimode base station use the common clock. The main
control board of a RAT may provide a clock source to be shared or use a clock
source that is shared by the main control board of another RAT. If all RATs in a
multimode base station are configured in the same BBU, common clock is
implemented with clock signals transmitted through the BBU backplane. If the
RATs of a multimode base station are configured in two BBUs, common clock is
implemented with clock signals transmitted through BBU interconnection cables.
GSM, UMTS, LTE, and NR can provide a clock source to other RATs or use a clock
source provided by another RAT. The synchronization mode is configured and
controlled on the main control board of the local RAT, regardless of whether the
RAT provides the clock source or not. For example, if the LTE mode requires
frequency synchronization, the LTE main control board must be configured with
frequency synchronization. For a newly deployed separate-MPT multimode base
station, the common reference clock is introduced to the main control board of
each RAT in descending order of priority as follows: UMPT > GTMU. If all the RATs
use the UMPT boards, the common reference clock is introduced to one of the
UMPT boards. When common clock reconstruction is involved, the main control
board to which the common reference clock is introduced is selected based on the
principle of minimum impact on services on the live network.
The following restrictions apply to Common Clock in separate-MPT scenarios:
● If frequency synchronization or hybrid synchronization is configured for the
RAT providing a clock source to be shared, only frequency synchronization can
be configured for the RATs using the shared clock source.
● If time synchronization is configured for the RAT providing a clock source to
be shared, either time synchronization or frequency synchronization can be
configured for the RATs using the shared clock source. If time synchronization
is configured, services must meet the requirements of loose time
synchronization.
● If loose time synchronization is configured for the RAT providing a clock
source to be shared, only loose time synchronization or frequency
synchronization can be configured for the RATs using the shared clock source.
● If IEEE 1588V2 hybrid synchronization in time and frequency backup mode, or
hybrid synchronization in GNSS time and IEEE 1588V2 frequency backup
mode is configured for the RAT providing a clock source to be shared, only
the frequency can be synchronized to the RATs using the shared clock source.
Hybrid synchronization cannot be configured for the RATs using the shared
clock source.
● If low-precision frame synchronization is configured for the RAT providing a
clock source to be shared, only frequency synchronization can be configured
for the RATs using the shared clock source.
● If a multimode base station uses the USCU board for clock synchronization,
other clock sources cannot be configured. The main control boards of various
RATs use the shared USCU clock for synchronization.
● On a multimode base station, if a RAT is configured with a GNSS+SyncE clock
source, other RATs can be configured with only the IEEE 1588V2 reference
clock. The GNSS+SyncE reference clock cannot be shared.
● On a multimode base station, if two RATs are configured with an IEEE
1588V2+SyncE clock source, the GNSS clock source cannot be configured as a
backup clock source, and inter-RAT clock sharing is not supported.
● On a multimode base station, if a RAT is configured with an IEEE
1588V2+SyncE clock source, the GNSS clock source can be configured as a
backup clock source. The other RAT cannot be configured with the IEEE
1588V2+SyncE clock source. In addition, the GNSS, SyncE, ToD, and LineCLK
clock sources are not recommended. It is recommended that the other RAT
receive clock signals from the RAT configured with the IEEE 1588V2+SyncE
clock source.
● In Cloud BB scenarios, the GNSS+SyncE and IEEE 1588V2+SyncE clock sources
cannot be configured, and the USCU board cannot be used to configure clock
sources.
NOTE
To achieve BBU interconnection in different scenarios, you can connect one UCIU board to
one UMPT board or connect two UMPT boards. The configurations in the two scenarios are
the same. This document uses one interconnection scenario as an example. The BBU3910A/
BBU3910C does not support BBU interconnection. For details about the RAT deployment
supported in BBU interconnection scenarios, see the "Application Scenarios" sections in BBU
Interconnection.
In inter-subrack interconnection SDR scenarios, it is not permitted to configure frequency
synchronization for the RAT in the primary BBU or time synchronization for the RAT in the
secondary BBU at the same time.
The clock source PeerCLK at the local end cannot be shared with the peer end. This
restriction is to prevent a clock synchronization loop.
Co-MPT Scenarios
The clock source configured for the shared main control board is shared by each
RAT and Common Clock is supported by default. Both frequency synchronization
and time synchronization are supported. If LTE TDD or NR TDD is involved, the
clock sources of the RATs sharing a main control board must support and use time
synchronization. In this case, GSM, UMTS, and LTE FDD sharing a main control
board passively use the time synchronization mode, which affects basic service
performance. For details about the impact and workarounds, see Synchronization.
Hybrid-MPT Scenarios
A single RAT uses a separate main control board, and the other RATs share a main
control board.
● Common Clock is supported by default for the RATs that share the main
control board. The clock source supports frequency synchronization and time
synchronization. If LTE TDD or NR TDD is involved, the clock source of the co-
MPT board must support and use time synchronization.
● The RAT that uses a separate main control board shares a clock source with
the RATs that use the shared main control board. The restrictions in this
scenario are the same as those in separate-MPT scenarios.
NOTE
Figure 3-3 Common GPS clock in the primary BBU of a GU+LN base station
Figure 3-4 Common GPS clock in the secondary BBU of a GU+LN base station
In this scenario, the common RGPS reference clock has the following restrictions:
● The RGPS clock must be configured for the major standard for clock lock. For
example, in inter-BBU scenarios, the RGPS clock must be configured in the
primary BBU.
● All NR-capable AAUs with AUX ports for RGPS support the common RGPS
clock function. For details, see the hardware description of the related AAUs
in 3900 & 5900 Series Base Station Product Documentation.
● When multimode RF modules are used, RGPS cannot be configured for
multiple modes at the same time.
● The external RGPS clock source of RF modules and the external GPS clock
source of the BBU cannot be configured at the same time.
● If the RGPS clock needs to be shared with other modes, the base station must
be upgraded to SRAN17.0 or later.
Figure 3-7 Common RGPS clock in an LN separate-MPT base station when the NR
side receives RGPS clock signals
Figure 3-8 Clock lock in an LN separate-MPT base station when the NR side
receives RGPS clock signals
Figure 3-10 Common RGPS clock in an LN separate-MPT base station with BBU
interconnection
Figure 3-12 Co-RF RGPS clock on the NR side of clock lock in an LN separate-MPT
base station with BBU interconnection
Figure 3-14 Common RGPS clock in a ULN hybrid-MPT multimode base station
The BITS clock source must be configured on the USCU board, which occupies an
extra slot. In addition, the BITS clock source cannot be transmitted over the
transport network, which increases costs. Therefore, the BITS clock source is not
recommended.
The sharing modes of the BITS clock source are similar to those of the GNSS clock
source.
Common E1/T1 When the Abis interface uses E1/T1 transmission and the
clock over the Abis Iub/S1 interface uses IP over FE/GE transmission, the
interface NodeB/eNodeB can obtain E1/T1 clock signals from an
E1/T1 link over the Abis interface.
Common E1/T1 When the Abis interface on the multimode base station
clock over the Iub side uses IP co-transmission or IP hybrid transmission, the
interface eGBTS/GBTS can obtain E1/T1 clock signals from an E1/T1
link over the Iub interface.
NOTE
For details about the Common Transmission feature, see Common Transmission.
Figure 3-17 Common E1/T1 clock in the primary BBU of a GU+L base station
Figure 3-18 Common E1/T1 clock in the secondary BBU of a GU+L base station
IEEE1588 V2 16.1 L3
unicast
ITU-T G.8275.2 L3
unicast
Table 3-3 describes the typical application scenarios for common 1588 V2 clock.
Common 1588 V2 When the Iub interface uses IP transmission and the
clock over the Iub NodeB is configured with a 1588 V2 clock source over the
interface Iub interface, the eGBTS/GBTS can obtain clock signals
from the UMPT of the NodeB through the BBU backplane.
Generally, the NodeB does not require time synchronization. UMTS supports the
IEEE1588 V2 clock source for the sake of providing the time synchronization source to
other RATs.
Figure 3-23 Common IEEE1588 V2 clock in the primary BBU of a GULN base
station
Figure 3-24 Common IEEE1588 V2 clock in the secondary BBU of a GULN base
station
Table 3-4 describes the typical application scenarios for a common synchronous
Ethernet clock.
Table 3-4 Typical application scenarios for a common synchronous Ethernet clock
Common synchronous When the Iub interface on the multimode base station
Ethernet clock over side uses IP transmission and the IP network supports
the Iub interface the synchronous Ethernet clock, the eGBTS/GBTS/
eNodeB can obtain clock signals from the NodeB's
UMPT, or UTRP (supporting FE/GE transmission)
managed by the UMTS mode, through the BBU
backplane.
Figure 3-29 Common synchronous Ethernet clock in the primary BBU of a GUL
base station
Figure 3-30 Common synchronous Ethernet clock in the secondary BBU of a GUL
base station
Figure 3-31 Common synchronous Ethernet clock in a GUL co-MPT base station
Figure 3-33 Common 1PPS+TOD clock in a GUL co-MPT multimode base station
The BBU is connected to the RGPS clock source through the USCU. The USCU
outputs 1PPS+TOD clock signals and transmits these clock signals to the main
control board in the same BBU. The USCU can also provide the clock signals for
lower-level BBUs to implement inter-BBU clock sharing.
In the latter case, the 1PPS+TOD clock source provides either frequency
synchronization or time synchronization for lower-level BBUs and supports a
maximum of five cascaded BBUs. The following figure shows an example.
The 1PPS+TOD clock source configurations for level-2 through level-5 BBUs are
the same as those shown in Figure 3-33. For details, see Synchronization.
Figure 3-34 Common 1PPS+TOD clock in the primary BBU of a GUL base station
Figure 3-35 Common 1PPS+TOD clock in the secondary BBU of a GUL base
station
Figure 3-36 Common IEEE1588 V2+SyncE clock in a GUL co-MPT base station
Figure 3-37 Common IEEE1588 V2+SyncE clock in the primary BBU of a GUL base
station
Figure 3-38 Common IEEE1588 V2+SyncE clock in the secondary BBU of a GUL
base station
Figure 3-44 Common IEEE1588 V2+SyncE clock in the primary BBU of a GUL base
station
Figure 3-45 Common IEEE1588 V2+SyncE clock in the secondary BBU of a GUL
base station
configured with the GNSS+IEEE1588 V2&SyncE clock source, other modes can only
use the shared clock source but cannot be configured with this clock source. The
clock sharing process is as follows:
● In an LN+U separate-MPT base station, as shown in Figure 3-50, when the
GNSS+IEEE1588 V2&SyncE clock source is located in the primary BBU, the RAT
that accesses the GNSS+IEEE1588 V2&SyncE clock source is synchronized with
the GNSS, or serves as an IEEE1588 V2&SyncE client to terminate IEEE1588
V2&SyncE packets, and generates synchronized 1PPS clock signals. Then, the
1PPS clock signals are sent to the secondary BBU through the BBU
interconnection port on the UMPT. The other RAT in the primary BBU obtains
1PPS clock signals through the BBU backplane.
● In an LN+U separate-MPT base station, as shown in Figure 3-51, when the
GNSS+IEEE1588 V2&SyncE clock source is located in the secondary BBU, the
RAT that accesses the GNSS+IEEE1588 V2&SyncE clock source is synchronized
with the GNSS, or serves as an IEEE1588 V2&SyncE client to terminate
IEEE1588 V2&SyncE packets, and generates synchronized 1PPS clock signals.
Then, the 1PPS clock signals are sent to the primary BBU through the BBU
interconnection port on the UMPT. The other RAT in the primary BBU obtains
1PPS clock signals through the BBU backplane.
3.2.1 Benefits
The Common Clock feature can be used for co-site multimode base stations to
reduce the OPEX and CAPEX.
3.2.2 Impacts
Network Impacts
None
Function Impacts
Functio Function Reference Description
n Name Switch
3.3 Requirements
3.3.1 Licenses
None
3.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
Prerequisite Functions
RAT Function Name Function Reference Description
Switch (GBSS Feature
Documentatio
n)
Prerequisite Functions
RAT Function Name Function Reference Description
Switch (RAN Feature
Documentatio
n)
Prerequisite Functions
RAT Function Name Function Reference Description
Switch (eRAN Feature
Documentatio
n)
Prerequisite Functions
RAT Function Name Function Reference Description
Switch (eRAN Feature
Documentatio
n)
Prerequisite Functions
RAT Function Name Function Reference Description
Switch (eRAN Feature
Documentatio
n)
Prerequisite Functions
RAT Function Name Function Reference (5G Description
Switch RAN Feature
Documentatio
n)
3.3.3 Hardware
NR ● 3900 and 5900 series base stations. 3900 series base stations
must be configured with the BBU3910.
● DBS3900 LampSite and DBS5900 LampSite. DBS3900
LampSite must be configured with the BBU3910.
Boards
If common BITS clock is used, a USCU must be installed in the BBU.
If common BeiDou clock is used, a board supporting and configured with the
BeiDou satellite card must be installed in the BBU. For details, see the satellite
card types supported by boards in Hardware Description of the BBU in 3900 &
5900 Series Base Station Product Documentation.
If common IEEE1588 V2+SyncE clock is used, the main control board configured
with the shared clock source must be the UMPT.
When a USCU is managed by multiple RATs and the clock synchronization mode
needs to be time synchronization, only one RAT can use time synchronization at a
time.
RF Modules
This function does not depend on RF modules.
3.3.4 Others
Requirements for LTE TDD are as follows:
● The TDD eNodeB can only use the GPS clock provided by the GBTS that uses
time synchronization. Other types of clock sources are not supported.
● The TDD eNodeB can only use the GPS/BeiDou clock source provided by the
eGBTS/NodeB/gNodeB/co-MPT base station that uses time synchronization.
Other types of clock sources are not supported.
● If a multimode base station includes LTE TDD, a clock source that supports
time synchronization must be used, for example, GPS clock, BeiDou clock,
IEEE1588 V2 clock, or 1PPS+TOD clock. In addition, the clock source must use
time synchronization.
● A gNodeB can share only the GPS or BeiDou clock source provided by an
eNodeB that uses time synchronization. Other types of clock sources are not
supported.
● If a multimode base station includes NR TDD, a clock source that supports
time synchronization must be used, for example, GPS clock, BeiDou clock,
IEEE1588 V2 clock, or 1PPS+TOD clock. In addition, the clock source must use
time synchronization.
3.4.2 Precautions
For the GBTS/eGBTS, pay attention to the following points if the GPS, BeiDou, or
IEEE1588 V2 clock source is used, regardless of whether the GBTS/eGBTS shares
the clock source with other modes or uses the clock source provided by other
modes:
● When the GBTS uses time synchronization, if the GBTS does not require inter-
site frame number synchronization, set BTSCLK.FRAMESYNCSW to OFF. If
the GBTS requires inter-site frame number synchronization, set
BTSCLK.FRAMESYNCSW to ON. Before setting BTSCLK.FRAMESYNCSW to
ON, plan FN offset and TSC for GSM to avoid interference between
neighboring GSM cells. The recommended value is OFF.
● When the eGBTS uses time synchronization, if the eGBTS does not require
inter-site frame number synchronization, run the SET CLKSYNCMODE
command with TASM.GSMFRAMESYNCSW set to OFF. If the eGBTS requires
inter-site frame number synchronization, run the SET CLKSYNCMODE
command with TASM.GSMFRAMESYNCSW set ON. Before setting
TASM.GSMFRAMESYNCSW to ON, plan FN offset and TSC for GSM to avoid
interference between neighboring GSM cells. The recommended value is OFF.
● When a co-MPT base station involves GSM and GSM uses time
synchronization, if GSM does not require inter-site frame number
synchronization, run the SET CLKSYNCMODE command with
TASM.GSMFRAMESYNCSW set to OFF. If GSM requires inter-site frame
number synchronization, run the SET CLKSYNCMODE command with
TASM.GSMFRAMESYNCSW set to ON. Before setting
TASM.GSMFRAMESYNCSW to ON, plan FN offset and TSC for GSM to avoid
interference between neighboring GSM cells. The recommended value is OFF.
For details about GBTS/eGBTS inter-site frame number synchronization, see
Synchronization in GBSS Feature Documentation.
source (any of the clock sources listed above except BeiDou and IEEE1588
V2+SyncE) for a GBTS must be performed on the BSC. Therefore, the clock source
data configuration for a GBTS is different from that for an eGBTS/NodeB/eNodeB/
gNodeB/co-MPT base station. For details, see 3.4.3.1.2 GBTS Providing the Clock
Source.
Step 2 Run the SET CLKMODE command to activate the GNSS reference clock. Set the
key parameters according to the descriptions in the following table.
Parameter Name Parameter ID Setting Notes
----End
----End
Step 2 Run the SET CLKMODE command to activate the E1/T1 reference clock. Set the
key parameters according to the descriptions in the following table.
----End
NOTE
If the 1588 V2 clock server is not on the same network segment as the eGBTS/NodeB/
eNodeB/gNodeB/co-MPT base station, run the ADD IPRT command to configure a route
between the 1588 V2 clock server and the eGBTS/NodeB/eNodeB/gNodeB/co-MPT base
station.
Step 2 Run the SET CLKMODE command to activate the 1588 V2 reference clock. Set the
key parameters according to the descriptions in the following table.
Parameter Name Parameter ID Setting Notes
----End
Step 2 Run the SET CLKMODE command to activate the synchronous Ethernet reference
clock. Set the key parameters according to the descriptions in the following table.
Parameter Name Parameter ID Setting Notes
----End
Step 2 Run the ADD IPCLKLINK command to add an IEEE1588 V2 clock link. Set the key
parameters according to the descriptions in the following table.
Parameter Name Parameter ID Setting Notes
NOTE
If the IEEE1588 V2 clock server is not on the same network segment as the eGBTS/NodeB/
eNodeB/gNodeB/co-MPT base station, run the ADD IPRT command to configure a route
between the IEEE1588 V2 clock server and the eGBTS/NodeB/eNodeB/gNodeB/co-MPT base
station.
Step 3 Run the SET CLKMODE command to activate the IEEE1588 V2+SyncE reference
clock. Set the key parameters according to the descriptions in the following table.
Parameter Name Parameter ID Setting Notes
----End
Step 2 Run the SET BTSCLK command with ClkType set to TRCGPS_CLK(Trace GPS
Clock).
----End
----End
----End
Step 2 Run the SET BTSIPCLKPARA command to configure parameters for an IEEE1588
V2 clock link. Set the key parameters according to the descriptions in the following
table.
----End
----End
Step 1 Run the ADD PEERCLK command to add a peer reference clock link.
Step 2 Run the SET CLKMODE command to configure the working mode of the reference
clock.
Step 3 Run the SET CLKSYNCMODE command to configure the clock synchronization
mode of the RAT that uses the clock source provided by another RAT.
----End
Set STANDARD to the value of Peer Standard queried through the DSP
BTSSTATUS command.
----End
The reference clock type is the same as Configuring the reference clock
the configured one succeeds.
The reference clock type is different Configuring the reference clock fails.
from the configured one
----End
● The reference clock types conflict. That is, the current RAT does not support
this type of reference clock. In this case, check the configuration file of the
RAT that provides the clock source. Then change the conflicting reference
clock to a reference clock that can be shared by the current RAT.
● The clock synchronization mode of the RAT that provides the clock source
does not match that of the current RAT. In this case, change the clock
synchronization mode of the RAT that provides the clock source to ensure
that the clock synchronization modes match between the local and peer ends.
● The clock source provided by the RAT is faulty if the clock synchronization
mode is set to HYBRID for the RAT that provides the clock source. In this case,
check and rectify the faulty clock source.
If the shared clock source is correctly configured but the base station cannot lock
the clock source within 30 minutes after startup, check for the clock source fault.
For details, see "Possible Issues" in Synchronization for GSM/UMTS/LTE/NR.
4.1 Principles
4.1.1 Overview
After a clock source is introduced to a base station, the clock system of the base
station performs phase locking and frequency dividing on clock signals and then
generates the system clock. The system clock is the working clock of the
transmission, baseband, and RF subsystems of the base station.
If a separate-MPT multimode base station uses the dual-star or CPRI MUX
networking and is enabled with the GU@5 MHz or GSM and LTE Spectrum
Concurrency feature, the clock of each standard must strictly follow frequency
synchronization and phase synchronization. That is, the system clocks among all
RATs must be strictly synchronized. To achieve this, the system clocks among all
RATs in a multimode base station must be mutually locked. After clock lock is
enabled on the multimode base station, one RAT serves as the major standard.
Upon receiving clock source signals, the major standard generates the system
clock and provides the system clock for itself and other RATs. Other RATs are idle
and do not provide clock reference for services of local RATs. The major standard
is negotiated automatically on a multimode base station and can be viewed using
the DSP CLKMUTULOCLK command. For example, on a GL separate-MPT base
station, LTE serves as the major standard for clock lock and is connected to the RF
module through the baseband processing unit. GSM serves as the minor standard,
uses the system clock of LTE, and is directly connected to the RF module. See
Figure 4-1.
NOTE
For an RF module configured with multiple modes or enabled with the CPRI MUX feature, if
clock lock is not enabled, the RRU/AAU randomly selects the system clock of one mode. If
no clock of any mode is selected, UEs may fail to access the network. In addition, services
on the multimode RF module are unavailable.
● The configurations that are related to clock lock are adjusted, such as the
working standard of the RF module, and CPRI MUX. In this case, the separate-
MPT multimode base station performs renegotiation according to the
adjusted configurations. After the renegotiation, the minor standard switches
from the local system clock to the system clock of the major standard.
● The configurations that affect the decision of major and minor standards are
adjusted. The configurations include system clock lock optimization switch
and synchronization mode. (For selection of the major standard in clock lock,
see 4.1.3.1 System Clock Lock of a Separate-MPT Base Station Including
GBTS and 4.1.3.2 System Clock Lock of a Separate-MPT Base Station
Excluding GBTS.)
● The major standard for clock lock is upgraded, reset, powered off, or removed
and inserted. This causes the minor standard to switch back to the local
system clock.
● Inter-subrack interconnection is interrupted. This causes the minor standard in
the secondary BBU to switch back to the local system clock.
If the clock lock mode changes, services of the involved standards will be
interrupted. When GSM serves as the major standard for clock lock, the
interruption lasts no more than 8 minutes. When GSM does not serve as the
major standard for clock lock, the interruption lasts no more than 3 minutes in
intra-subrack scenarios and no more than 5 minutes in inter-subrack scenarios.
When LTE or NR serves as the major standard for clock lock, the service
interruption duration does not exceed 3 minutes. In intra-BBU scenarios, the
service interruption duration does not exceed 1 minute. In inter-BBU scenarios, the
service interruption duration does not exceed 3 minutes. During the clock lock
mode switching, the following alarms may be generated for the involved
standards. After the switching is complete, these alarms are cleared.
● ALM-26262 External Clock Reference Problem
● ALM-26264 System Clock Unlocked
● ALM-26265 Base Station Frame Number Synchronization Error
● ALM-26106 Board Clock Input Unavailable
● ALM-26234 BBU CPRI Interface Error
● ALM-26235 RF Unit Maintenance Link Failure
● ALM-26215 Inter-Board Service Link Failure
● ALM-26314 Inter-BBU Port Failure
● ALM-28302 Board BFN Abnormal
● ALM-26504 RF Unit CPRI Interface Error
● ALM-26538 RF Unit Clock Problem
● EVT-26361 Forcible Synchronization with Reference Clock Phase
● ALM-26324 BBU IR Interface Error
● ALM-26508 RF Unit IR Interface Error
● ALM-29870 NR DU Cell TRP Unavailable
NOTE
In the preceding scenarios, the impacts of resource sharing such as common clock, co-
transmission, and CPRI MUX are not considered and only the impacts of the system clock
switching are considered.
When the RAT in the primary BBU works properly, the clock lock relationship is
established. The major standard for clock lock is the RAT in the primary BBU. If
the clock of the major standard for clock lock is not locked or the clock quality is
poor and the minor standard for clock lock is LTE TDD or NR, the cell cannot be
activated. To reduce the impact of the clock of the RAT in the primary BBU on the
RAT in the secondary BBU, the following clock lock requirements must be met:
● If LTE TDD or NR is deployed in the secondary BBU and the clock in the
primary BBU is normal and uses time synchronization, then the clock lock
relationship is established between primary and secondary BBUs after the
clock in the primary BBU is locked. If the clock in the primary BBU is
abnormal for a long time, the clock lock relationship is established between
primary and secondary BBUs 10 minutes after the attempt to establish the
relationship is initiated.
● If LTE TDD or NR is deployed in the secondary BBU, the clock lock relationship
is established between primary and secondary BBUs only when the RAT in the
secondary BBU is not started (in maintenance mode and no external clock
source is available). In other cases, the clock lock relationship is not
established.
If the system clock lock optimization function is enabled and each RAT has been
deployed, the major standard for clock lock is selected according to rules described
in the following tables.
Table 4-1 Major standard selection for clock lock of a GU/GL/G&U*L/G&L*N base
station using a single BBU
Note: a indicates that the air interface soft synchronization function is enabled
for the corresponding RAT. No mark indicates that the air interface soft
synchronization function is not enabled for the corresponding RAT. If both soft-
synchronized network and system clock lock optimization are enabled, system
clock lock optimization takes effect as if soft-synchronized network is disabled.
Table 4-2 Major standard selection for clock lock of a GU+L/GL+U/GU+LN (GSM
in the primary BBU) base station using interconnected BBUs
Synchronization Synchronization Synchronization Major Standard
Mode (G) Mode (U/L in the Mode (U/L/LN in for Clock Lock
Primary BBU) the Secondary
BBU)
Note: a indicates that the air interface soft synchronization function is enabled
for the corresponding RAT. No mark indicates that the air interface soft
synchronization function is not enabled for the corresponding RAT. If both soft-
synchronized network and system clock lock optimization are enabled, system
clock lock optimization takes effect as if soft-synchronized network is disabled.
The following common clock deployment modes are recommended for a GL+N
base station in which BBUs are interconnected, LTE serves as the major standard
for clock lock, and the synchronization mode is time synchronization: (common
GPS clock is used as an example)
● As shown in Figure 4-2, the clock source is deployed on LTE in the primary
BBU. GSM and NR use the clock signals provided by LTE. The secondary BBU
uses the clock signals through the BBU interconnection ports on the UMPT
boards. Co-SDR is used for GSM, LTE, and NR.
● As shown in Figure 4-3, the clock source is deployed on NR in the secondary
BBU. GSM and LTE use the clock signals provided by NR. The primary BBU
uses the clock signals through the BBU interconnection ports on the UMPT
boards. Co-SDR is used for GSM, LTE, and NR.
Figure 4-2 Common GPS clock in the primary BBU of a GL+N base station
Figure 4-3 Common GPS clock in the secondary BBU of a GL+N base station
Table 4-3 Major standard selection for clock lock of a N+GL base station with
BBUs interconnected (UMPT+UMPT interconnection, GL in the secondary BBU, and
N in the primary BBU)
Synchronization Synchronization Synchronization Major Standard
Mode (N) Mode (L) Mode (G) for Clock Lock
Note: In this scenario, the air interface soft synchronization function is enabled
for none of the RATs.
NOTE
● The system clock lock optimization function is supported only when GSM uses the
GTMUb or GTMUc and other RATs use the UMPT as the main control board.
● For details about the Uu based Soft Synchronization feature, see Uu based Soft
Synchronization in GBSS Feature Documentation.
● NB-IoT uses low-precision frame synchronization to calculate the hyper frame number
and frame number. In clock lock scenarios, if the RAT of NB-IoT is a minor standard, the
calculated hyper frame number and frame number are based on the clock reference of
the major standard. If frequency synchronization is configured for the major standard,
the hyper frame number and frame number are incorrect. Therefore, it is recommended
that the RAT of NB-IoT be configured as the major standard in the primary BBU. If a
separate-MPT multimode base station includes GBTS, it is recommended that the
system clock lock optimization feature be enabled for the GBTS.
Table 4-4 Major standard selection for clock lock of a UL/NL base station using a
single BBU
Time Time No
synchronization synchronization
NOTE
For details about Cloud BB, see Cloud BB Overview in eRAN Feature Documentation.
When the configuration of the forcible major standard for clock lock does not take
effect, the base station reports ALM-26245 Configuration Data Inconsistency. If
the forcible major standard for clock lock is configured on both the LTE and NR
main control boards and the configured major standards are inconsistent, the
earlier configuration takes effect on one base station, and ALM-26276 Inter-
System Site-Level Configuration Conflict is reported on the other base station.
NOTE
When the NODE.WMEXTENSION (5G gNodeB, LTE eNodeB) parameter setting takes
effect, the forcible major standard for clock lock cannot be set on the base station.
It is recommended that the function of configuring the forcible major standard for clock
lock be enabled only when one of the two main control boards for clock lock is faulty. This
prevents base station services from being affected by the faulty main control board. After
the function of configuring the forcible major standard for clock lock is enabled, the base
station no longer performs clock switching based on the clock status of the major and
secondary standards for clock lock. Therefore, clock switching is not triggered when the
major standard for clock lock is unlocked.
If both main control boards are normal, the value AUTO is recommended.
● When clock lock is enabled for LTE and NR and LTE is the major standard, the
precision and holdover capability of the NR clock decrease.
● The upgrade, reset, startup, or fault of any mode in a multimode base station
affects other modes.
In eCPRI scenarios (currently, only LTE and NR support eCPRI interfaces), the clock
single-source soft lock solution (clock unlock) can be used to resolve the
preceding problem. After clock unlock is enabled, the clocks of different modes are
synchronized with the reference clock. This ensures that the synchronization
relationship between modes meets the synchronization requirement that the delay
difference between services of different modes is within a certain range. In
addition, the clocks of different modes are decoupled. Each mode obtains its own
system clock. The multimode AAU selects the clock of one mode as the master
clock and the clock of the other mode as the backup clock. When the master clock
is faulty, the backup clock is used, as shown in Figure 4-4. This function supports
both co-BBU and inter-BBU scenarios. In inter-BBU interconnection scenarios, the
clock does not depend on inter-BBU CI interconnection.
Table 4-5 Impacts of eCPRI clock unlock and clock lock on wireless services
eCPRI Clock Unlock eCPRI Clock Lock
The modes do not affect each other. Services on the single-mode AAU on
Especially in the single-mode AAU the BBU involved in clock lock are
networking scenario, wireless services greatly affected.
are affected only by the devices of the When the main control board of the
local mode. major standard for clock lock is
upgraded and reset, services of the
single-mode AAU of the minor
standard for clock lock are affected.
After clock lock is disabled, services are
intermittently interrupted.
A link fault causes a clock switchover. A link fault causes a clock switchover.
The impact of the switchover is the The clock switchover requires re-lock.
same as that in the clock lock scenario. The impact lasts about 30 seconds.
As shown in the preceding table, the difference between eCPRI clock unlock and
eCPRI clock lock is that eCPRI clock lock has a great impact on wireless services in
single-mode AAU scenarios.
NOTICE
After the clock unlock switch is turned on, the clock changes from the lock mode
to the unlock mode. In this case, the eCPRI clock on the AAU side may be
switched. For example, the AAU obtains clock signals from the LTE mode instead
of from the NR mode. Clock switching causes clock phase difference and service
loss.
If a clock switchover occurs on the clock link traced by the AAU due to a clock or
port exception, services will be interrupted when the clock is re-traced and locked.
4.2.1 Benefits
When system clock lock optimization is enabled, the major standard for clock lock
can be preferentially determined based on the clock quality to ensure the optimal
clock performance.
4.2.2 Impacts
Network Impacts
None
Function Impacts
None
4.3 Requirements
4.3.1 Licenses
None
4.3.2 Software
Prerequisite Functions
None
4.3.3 Hardware
Base Station Models
RAT Base Station Model
NR ● 3900 and 5900 series base stations. 3900 series base stations
must be configured with the BBU3910.
● DBS3900 LampSite and DBS5900 LampSite. DBS3900
LampSite must be configured with the BBU3910.
Boards
GSM must use the GTMUb or GTMUc as the main control board.
The UMTS/LTE/NR/co-MPT side must use the UMPT as the main control board.
RF Modules
This function does not depend on RF modules.
4.3.4 Others
None
4.4.2 Precautions
When inter-RAT clock lock is applied, the following are true:
● In BBU interconnection scenarios, the major standard for clock lock must be
located in the primary BBU.
● If the GBTS is deployed first and only the hardware installation of the peer
RAT is complete, GSM serves as the major standard for clock lock.
● The type of the main control board where the major standard for clock lock is
located determines the holdover duration in which the system can work
properly. For example, in GL clock lock scenarios, if the GTMU serves as the
main control board for the major standard for clock lock and the reference
source is lost, the holdover duration of LTE TDD services depends on the
GTMU holdover capability, which is 8 hours. For details about the holdover
duration, see Synchronization.
If... Then...
If... Then...
----End
If... Then...
The major standard for clock lock does The configuration is successful.
not exist, and NULL is displayed.
The major standard for clock lock The configuration does not take effect.
exists and is not displayed as NULL. There may be constraints described in
4.1.4 Clock Unlock in eCPRI
Scenarios.
Step 3 On the LTE/NR/co-MPT side, run the DSP CLKSTAT command with the cabinet
number, subrack number, and slot number of the AAU specified to query the AAU
clock status.
If... Then...
----End
ALM-28020 Site Configuration Error The GTMU does not support the
is generated with the value of system clock lock optimization
Configuration Item being Clock function.
Mutual Lock Optimization
Configuration
If this alarm is reported, check the GTMU hardware type. If it is not GTMUb or
GTMUc, replace the GTMU in use with a GTMUb or GTMUc board.
● On the base station:
If... Then...
5 Parameters
NOTE
You can find the EXCEL files of parameter reference and used reserved parameter list for
the software version used on the live network from the product documentation delivered
with that version.
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID.
Step 3 Click OK. All parameters related to the feature are displayed.
----End
Step 1 Open the EXCEL file of the used reserved parameter list.
Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter, which may be only a bit of a parameter.
View its information, including the meaning, values, impacts, and product version
in which it is activated for use.
----End
6 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● eNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
● gNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.
----End
7 Glossary
8 Reference Documents