SRAN10.1
Issue 06
Date 2017-03-25
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: http://www.huawei.com
Email: support@huawei.com
Contents
2 Time Management.........................................................................................................................4
2.1 Introduction.................................................................................................................................................................... 4
2.2 Time Sources.................................................................................................................................................................. 4
2.2.1 NTP Server.................................................................................................................................................................. 5
2.2.2 SNTP Server................................................................................................................................................................ 6
2.2.3 GPS Clock................................................................................................................................................................... 6
2.3 Time Synchronization.....................................................................................................................................................6
2.4 Time Source Switchover.................................................................................................................................................8
2.5 Time Zone.......................................................................................................................................................................9
2.6 Daylight Saving Time.....................................................................................................................................................9
3 Related Features...........................................................................................................................10
4 Network Impact........................................................................................................................... 11
5 Engineering Guidelines............................................................................................................. 12
5.1 When to Use................................................................................................................................................................. 12
5.2 Required Information................................................................................................................................................... 12
5.3 Planning........................................................................................................................................................................ 12
5.3.1 NTP Time Synchronization....................................................................................................................................... 13
5.3.2 GPS Time Synchronization....................................................................................................................................... 13
5.4 Deployment.................................................................................................................................................................. 13
5.4.1 Requirements............................................................................................................................................................. 13
5.4.2 Data Preparation........................................................................................................................................................ 13
5.4.2.1 Required Data......................................................................................................................................................... 14
5.4.2.2 Scenario-specific Data............................................................................................................................................ 16
5.4.3 Precautions.................................................................................................................................................................18
5.4.4 Hardware Adjustment................................................................................................................................................18
5.4.5 Initial Configuration.................................................................................................................................................. 18
5.4.5.1 Using MML Commands......................................................................................................................................... 19
6 Parameters..................................................................................................................................... 23
7 Counters........................................................................................................................................ 32
8 Reference Documents................................................................................................................. 33
1.1 Scope
This document describes the Time Management feature, including its technical principles,
related features, network impact, and engineering guidelines.
This document applies to macro base stations (BTS3900, BTS3900L, BTS3900A,
BTS3900AL, BTS3900C, and DBS3900), micro base stations, and DBS3900 LampSite base
stations.
Any parameters, alarms, counters, or managed objects (MOs) described herein apply only to
the corresponding software release. For future software releases, refer to the corresponding
updated product documentation.
SRAN12.1 01 (2017-03-08)
This issue does not include any changes.
IPv6 Micro base stations do not support IPv6 and therefore do not
require any IPv6-related parameter configuration. For details, see
5.4.2.2 Scenario-specific Data.
As integrated entities, micro base stations do not involve such concepts as boards, cabinets,
subracks, or slots.
2 Time Management
2.1 Introduction
All base stations in a network must synchronize their clocks with Coordinated Universal Time
(UTC) so that they can operate properly. Failure to keep time synchronized will result in the
following issues:
l Performance statistics will have inconsistent timestamps, which may cause errors in
performance reports.
l Scheduled tasks will not be executed according to the scheduled time. For example, a
license may take effect ahead of schedule.
l Base stations have inconsistent timestamps for logs and alarms, which may make fault
diagnosis confusing.
The standard time used by base stations is Universal Time Coordinated (UTC).
Different types of base stations synchronize their clocks with different time sources:
l A GBTS synchronizes its clock with a BSC's clock every 30 seconds. BSCs can only use
an SNTP server as the time source.
l An eGBTS, NodeB, or eNodeB synchronizes its clock with an NTP server or a GPS
clock.
l Each radio access technology (RAT) in a multimode base station is configured with an
independent time source.
The device that provides standard time serves as an NTP server, and the device that receives time serves
as an NTP client.
If a base station is connected to an NTP server, the NTP server can be configured as the time
source for the base station. A base station can be configured with a maximum of four NTP
servers, one of which is configured as the primary NTP server. If the synchronization with the
primary NTP server fails, the base station switches to another NTP server.
Base stations support NTP time synchronization in both plaintext and ciphertext modes.
Using ciphertext mode improves time synchronization security. If the ciphertext mode is used,
the ciphering algorithm between the base station and NTP servers can be specified. The
ciphering algorithm must comply with RFC1305.
NOTE
The NTP synchronization period is configured by setting the NTPC MO. The GPS synchronization
period is 30 minutes.
1. The base station sends a time synchronization request to an NTP/SNTP server or GPS
receiver.
2. Upon receiving the time synchronization request, the NTP/SNTP server or GPS receiver
sends the time to the base station.
3. The base station receives the time and checks its validity. If the time is valid, the base
station synchronizes its clock with the NTP/SNTP server or GPS receiver. If the time is
invalid, the base station does not synchronize its clock and waits for the next
synchronization. (When the NTP synchronization period is longer than two hours,
initiate a synchronization again two hours after the previous periodic time
synchronization failed)
Figure 2-3 shows the periodic time synchronization process.
NOTE
You can query the value of the Time Source parameter by running the DSP TIMESRC command to
determine the time source used by a base station.
l Switchover from the primary NTP server to another NTP server
If the synchronization with the primary NTP server fails, the base station attempts to
synchronize its clock with another NTP server.
l Switchover between an NTP server and a GPS clock
When the synchronization with all NTP servers fails, the base station automatically
synchronizes its clock with a GPS clock if the base station supports GPS time
synchronization.
When the synchronization with a GPS clock fails, the base station synchronizes its clock
with an NTP server if the base station supports NTP time synchronization and the NTP
server is correctly configured.
NOTE
The time source automatic switchover function is enabled by setting the Automatic Switch
parameter in the SET TIMESRC command. When Automatic Switch is set to OFF(Off), the
base station does not switch to a time source of another type if the synchronization with the current
time source fails.
3 Related Features
Prerequisite Features
N/A
Impacted Features
N/A
4 Network Impact
System Capacity
N/A
Network Performance
N/A
5 Engineering Guidelines
NOTE
Only base stations of SRAN7.0 or earlier support SNTP time synchronization. This document describes
only the basic concepts and time synchronization process of SNTP, not the engineering guidelines for
SNTP.
This section describes how to configure the time for an eGBTS, NodeB, or eNodeB. A GBTS
synchronizes its clock with that on the BSC. Therefore, only the time on the BSC needs to be
configured.
NOTE
For details about configuring the time on the BSC, see the following sections:
l BSC6900 GU Initial Configuration (MML-based) > Configuring the Equipment Data > Configuring
the Time in BSC6900 GU Initial Configuration Guide
l BSC6910 GU Initial Configuration (MML-based) > Configuring the Equipment Data > Configuring
the Time in BSC6910 GU Initial Configuration Guide
l Time zone, equation of time, and DST information about the place where the base station
is located
l (Optional) Related information about the NTP server when an NTP time source is used
5.3 Planning
RF Planning
N/A
Network Planning
Ensure that you have:
l Correctly configured the routes and virtual LANs (VLANs) between the base station and
NTP servers.
l Set up a link between the base station and an NTP server.
Hardware Planning
Make sure that a functional NTP server is available and that it provides accurate time.
5.4 Deployment
This section describes how to configure the time source for a base station. In the case of a
multimode base station, you must configure the time source for each RAT.
5.4.1 Requirements
l If a base station synchronizes its clock with a GPS clock, make sure that the GPS clock
has been configured as the time source and a GPS satellite card (functioning as a GPS
receiver) has been configured.
l If a base station synchronizes its clock with an NTP server, make sure that:
– The NTP server has been configured as the time source.
– The transmission network required by NTP time synchronization is available.
– Security requirements for NTP deployment are met.
– NTP time synchronization uses ciphertext mode when security requirements are
imposed on the transmission network.
l Network plan (negotiation not required): parameter values planned and set by the
operator
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the core network (CN) or peer transmission equipment
l User-defined: parameter values set by users
l The TIMESRC MO contains the parameter related to the time source. Table 5-1
describes this parameter.
l The OMUCURTIME MO contains the parameters related to the local time. The local
time can be set manually. Table 5-2 describes these parameters.
NOTE
A base station performs initial time synchronization to calibrate its local time. MML commands
can also be used to set the local time.
Date DATE Specifies the date to be set for the base station. Network
plan
(negotiatio
n not
required)
Time TIME Specifies the time to be set for the base station. Network
plan
(negotiatio
n not
required)
l The TZ MO contains the parameters related to the time zone and DST. Table 5-3
describes these parameters.
Time ZONET Specifies the time zone where the base station User-
Zone locates. defined
Time TIMEDIF Specify this parameter when Time Zone is set User-
Differe F to CUSTOM(Custom time zone) based on the defined
nce time zone where the base station locates.
DST ST User-
Start defined
Time
DST EM User-
End defined
Mode
DST ET User-
End defined
Time
DST TO User-
Offset defined
NOTE
If the operation and maintenance channel (OMCH) is configured, the NTP client uses the OMCH local
IP address to communicate with the NTP server. If the OMCH is not configured, the NTP client
automatically uses a device IP address based on the route information to communicate with the NTP
server.
NOTE
If both the NTP server and GPS clock have been specified as time sources, a switchover between them
occurs when the current time source is unavailable. For details, see 2.4 Time Source Switchover.
5.4.3 Precautions
None
l Required configuration
Configuration that is required for all types of time sources
l Scenario-specific configuration
Configuration that is necessary for a specific type of time source
By the main control board type, an eGBTS can be classified into the following types:
l eGBTS with the GTMUb/GTMUc functioning as the main control board: The eGBTS
does not support different RATs and is referred to as eGBTS (GTMUb)/eGBTS
(GTMUc) in this document.
l eGBTS with the UMPT functioning as the main control board: The eGBTS supports
different RATs and is referred to as eGBTS (UMPT) or co-MPT base station in this
document.
Required Configuration
To configure required settings of time synchronization, perform the following operations:
Step 1 Run the SET TZ command to set the time zone and DST.
Step 2 Run the SET TIME command to set the current time.
----End
NOTE
If the planned time source is unavailable during the initial stage of base station deployment, run the SET
TIME command to manually set the current time.
Step 2 Run the ADD NTPC command with related parameters specified to add an NTP client.
Step 3 Run the SET MASTERNTPS command to set parameters of the primary NTP server.
----End
NOTE
NTP time synchronization allows redundancy for NTP servers. When the primary NTP server is
unavailable, a switchover to an available NTP server occurs. Run the DSP NTPC command to query the
IP address of the NTP server in use. To ensure correct time, manually set the current time for the base
station.
----End
Required Configurations
//Setting the time zone and DST
SET TZ: ZONET=GMT+0800, DST=YES, SM=DATEWEEK, SMONTH=JAN, SDAY=1, SWEEK=TUE,
ST=10&49&00, EM=DATE, EMONTH=FEB, EDAY=26, ET=10&49&00, TO=30;
//Setting the current time
SET TIME: DATE=2015&01&01, TIME=12&00&00;
5.4.6 Reconfiguration
If a time source has been modified or replaced, you may need to modify related
configurations. For details, see section 5.4.2.1 Required Data.
Run the SET TIME command to set the date and time to an earlier point in time, for
example, to 2012&12&12 and 00&00&00 respectively.
Step 2 When the time synchronization period elapses, run the DSP TIME command to query the
current time of the base station.
If the value of Time in the command output is the same as the time of the time source, the
base station time is accurate.
Step 3 Run the DSP TIMESRC command to query the current time source.
If the value of Time Source in the command output is the same as the site configuration, the
time source is configured correctly.
Step 4 Run the LST LATESTSUCCDATE command to check whether the time synchronization is
successful.
If the time synchronization is successful, the Time Management feature has been successfully
activated.
----End
When the difference between the time obtained from external reference time source and local
time exceed the threshold, EVT-26360 Time Source Switchover is reported, as shown in
Table 5-5. If time hopping occurs, performance counter collection and log recording may fail.
6 Parameters
TIMES BTS390 SET None None Meaning: Indicates the external reference time source
RC 0, TIMES of the NE.
BTS390 RC GUI Value Range: NTP(NTP), GPS(GPS),
0 DSP NONE(None), SYSCLK(SYSCLK)
WCDM TIMES
A, Unit: None
RC
BTS390 Actual Value Range: NTP, GPS, NONE, SYSCLK
0 LTE LST
LATES Default Value: NTP(NTP)
TSUCC
DATE
LST
TIMES
RC
ZONET BTS390 SET TZ GBFD-1 Support Meaning: Indicates the time zone of the NE.
0, LST TZ 16101 of GUI Value Range: GMT-1200(GMT-12:00),
BTS390 Daylight GMT-1100(GMT-11:00), GMT-1000(GMT-10:00),
0 Saving GMT-0930(GMT-09:30), GMT-0900(GMT-09:00),
WCDM Time GMT-0800(GMT-08:00), GMT-0700(GMT-07:00),
A, GMT-0600(GMT-06:00), GMT-0500(GMT-05:00),
BTS390 GMT-0430(GMT-04:30), GMT-0400(GMT-04:00),
0 LTE GMT-0330(GMT-03:30), GMT-0300(GMT-03:00),
GMT-0200(GMT-02:00), GMT-0100(GMT-01:00),
GMT(GMT), GMT+0100(GMT+01:00), GMT
+0200(GMT+02:00), GMT+0300(GMT+03:00),
GMT+0330(GMT+03:30), GMT+0400(GMT+04:00),
GMT+0430(GMT+04:30), GMT+0500(GMT+05:00),
GMT+0530(GMT+05:30), GMT+0545(GMT+05:45),
GMT+0600(GMT+06:00), GMT+0630(GMT+06:30),
GMT+0700(GMT+07:00), GMT+0800(GMT+08:00),
GMT+0845(GMT+08:45), GMT+0900(GMT+09:00),
GMT+0930(GMT+09:30), GMT+1000(GMT+10:00),
GMT+1030(GMT+10:30), GMT+1100(GMT+11:00),
GMT+1130(GMT+11:30), GMT+1200(GMT+12:00),
GMT+1245(GMT+12:45), GMT+1300(GMT+13:00),
GMT+1400(GMT+14:00), CUSTOM(Custom time
zone)
Unit: None
Actual Value Range: GMT-1200, GMT-1100,
GMT-1000, GMT-0930, GMT-0900, GMT-0800,
GMT-0700, GMT-0600, GMT-0500, GMT-0430,
GMT-0400, GMT-0330, GMT-0300, GMT-0200,
GMT-0100, GMT, GMT+0100, GMT+0200, GMT
+0300, GMT+0330, GMT+0400, GMT+0430, GMT
+0500, GMT+0530, GMT+0545, GMT+0600, GMT
+0630, GMT+0700, GMT+0800, GMT+0845, GMT
+0900, GMT+0930, GMT+1000, GMT+1030, GMT
+1100, GMT+1130, GMT+1200, GMT+1245, GMT
+1300, GMT+1400, CUSTOM
Default Value: GMT+0800(GMT+08:00)
TIMED BTS390 SET TZ GBFD-1 Support Meaning: Indicates the offset of time zone. This
IFF 0, 16101 of parameter can be set to a negative value.
BTS390 Daylight GUI Value Range: -720~840
0 Saving
WCDM Time Unit: min
A, Actual Value Range: -720~840
BTS390 Default Value: 0
0 LTE
DST BTS390 SET TZ GBFD-1 Support Meaning: Indicates whether DST is enabled.
0, 16101 of GUI Value Range: NO(No), YES(Yes)
BTS390 Daylight
0 Saving Unit: None
WCDM Time Actual Value Range: NO, YES
A, Default Value: NO(No)
BTS390
0 LTE
SMON BTS390 SET TZ GBFD-1 Support Meaning: Indicates the month in which the NE DST
TH 0, 16101 of starts.
BTS390 Daylight GUI Value Range: JAN(January), FEB(February),
0 Saving MAR(March), APR(April), MAY(May), JUN(June),
WCDM Time JUL(July), AUG(August), SEP(September),
A, OCT(October), NOV(November), DEC(December)
BTS390
0 LTE Unit: None
Actual Value Range: JAN, FEB, MAR, APR, MAY,
JUN, JUL, AUG, SEP, OCT, NOV, DEC
Default Value: JAN(January)
SDAY BTS390 SET TZ GBFD-1 Support Meaning: Indicates the day on which the NE DST
0, 16101 of starts.
BTS390 Daylight GUI Value Range: 1~31
0 Saving
WCDM Time Unit: None
A, Actual Value Range: 1~31
BTS390 Default Value: 1
0 LTE
SWSEQ BTS390 SET TZ GBFD-1 Support Meaning: Indicates in which week the NE DST starts.
0, 16101 of GUI Value Range: LAST(Last), FIRST(First),
BTS390 Daylight SECOND(Second), THIRD(Third), FOURTH(Fourth)
0 Saving
WCDM Time Unit: None
A, Actual Value Range: LAST, FIRST, SECOND,
BTS390 THIRD, FOURTH
0 LTE Default Value: FIRST(First)
SWEE BTS390 SET TZ GBFD-1 Support Meaning: Indicates the week in which the NE DST
K 0, 16101 of starts.
BTS390 Daylight GUI Value Range: MON(Monday), TUE(Tuesday),
0 Saving WED(Wednesday), THU(Thursday), FRI(Friday),
WCDM Time SAT(Saturday), SUN(Sunday)
A,
BTS390 Unit: None
0 LTE Actual Value Range: MON, TUE, WED, THU, FRI,
SAT, SUN
Default Value: MON(Monday)
ST BTS390 SET TZ GBFD-1 Support Meaning: Indicates the time when the NE DST starts.
0, 16101 of The value of this parameter observes the standard
BTS390 Daylight time.
0 Saving GUI Value Range: 00:00:00~23:59:59
WCDM Time
A, Unit: None
BTS390 Actual Value Range: 00:00:00~23:59:59
0 LTE Default Value: 00:00:00
EMON BTS390 SET TZ GBFD-1 Support Meaning: Indicates the month in which the NE DST
TH 0, 16101 of ends.
BTS390 Daylight GUI Value Range: JAN(January), FEB(February),
0 Saving MAR(March), APR(April), MAY(May), JUN(June),
WCDM Time JUL(July), AUG(August), SEP(September),
A, OCT(October), NOV(November), DEC(December)
BTS390
0 LTE Unit: None
Actual Value Range: JAN, FEB, MAR, APR, MAY,
JUN, JUL, AUG, SEP, OCT, NOV, DEC
Default Value: JAN(January)
EDAY BTS390 SET TZ None None Meaning: Indicates the day on which the NE DST
0, ends.
BTS390 GUI Value Range: 1~31
0
WCDM Unit: None
A, Actual Value Range: 1~31
BTS390 Default Value: 1
0 LTE
EWSE BTS390 SET TZ GBFD-1 Support Meaning: Indicates the week in which DST ends.
Q 0, 16101 of GUI Value Range: LAST(Last), FIRST(First),
BTS390 Daylight SECOND(Second), THIRD(Third), FOURTH(Fourth)
0 Saving
WCDM Time Unit: None
A, Actual Value Range: LAST, FIRST, SECOND,
BTS390 THIRD, FOURTH
0 LTE Default Value: FIRST(First)
EWEE BTS390 SET TZ GBFD-1 Support Meaning: Indicates the week in which the NE DST
K 0, 16101 of ends.
BTS390 Daylight GUI Value Range: MON(Monday), TUE(Tuesday),
0 Saving WED(Wednesday), THU(Thursday), FRI(Friday),
WCDM Time SAT(Saturday), SUN(Sunday)
A,
BTS390 Unit: None
0 LTE Actual Value Range: MON, TUE, WED, THU, FRI,
SAT, SUN
Default Value: MON(Monday)
ET BTS390 SET TZ GBFD-1 Support Meaning: Indicates the time when the DST of the NE
0, 16101 of ends. The value of this parameter observes DST.
BTS390 Daylight GUI Value Range: 00:00:00~23:59:59
0 Saving
WCDM Time Unit: None
A, Actual Value Range: 00:00:00~23:59:59
BTS390 Default Value: 00:00:00
0 LTE
TO BTS390 SET TZ GBFD-1 Support Meaning: Indicates the DST time offset of the NE.
0, 16101 of This parameter can be set to a negative value. A
BTS390 Daylight negative value indicates that the NE time is earlier
0 Saving than the DST time, and a positive value indicates that
WCDM Time the NE time is later than the DST time.
A, GUI Value Range: -120~120
BTS390
0 LTE Unit: min
Actual Value Range: -120~120
Default Value: 0
MODE BTS390 ADD None None Meaning: Indicates the mode of the IP address of the
0, NTPC NTP server.
BTS390 MOD GUI Value Range: IPV4(IPv4), IPV6(IPv6)
0 NTPC
WCDM Unit: None
A, RMV Actual Value Range: IPV4, IPV6
BTS390 NTPC
Default Value: IPV4(IPv4)
0 LTE SET
MASTE
RNTPS
IP BTS390 ADD None None Meaning: Indicates the IPv4 address of the NTP
0, NTPC server.
BTS390 MOD GUI Value Range: Valid IP address
0 NTPC
WCDM Unit: None
A, RMV Actual Value Range: Valid IP address
BTS390 NTPC
Default Value: 0.0.0.0
0 LTE SET
MASTE
RNTPS
IPV6 BTS390 ADD None None Meaning: Indicates the IPv6 address of the NTP
0, NTPC server.
BTS390 MOD GUI Value Range: Valid IP address
0 NTPC
WCDM Unit: None
A, RMV Actual Value Range: Valid IP address
BTS390 NTPC
Default Value: 0:0:0:0:0:0:0:0
0 LTE SET
MASTE
RNTPS
AUTH BTS390 ADD None None Meaning: Indicates the encryption mode. If this
MODE 0, NTPC parameter is set to PLAIN, data is transmitted in
BTS390 MOD plaintext.
0 NTPC GUI Value Range: PLAIN(Plain), DES_S(DES_S),
WCDM DES_N(DES_N), DES_A(DES_A), MD5(MD5)
A, LST
BTS390 NTPC Unit: None
0 LTE Actual Value Range: PLAIN, DES_S, DES_N,
DES_A, MD5
Default Value: PLAIN(Plain)
KEYID BTS390 ADD None None Meaning: Indicates the server-side index of the NTP
0, NTPC authentication key. The index must be the same as the
BTS390 MOD setting on the server.
0 NTPC GUI Value Range: 1~4294967295
WCDM
A, LST Unit: None
BTS390 NTPC Actual Value Range: 1~4294967295
0 LTE Default Value: None
PORT BTS390 ADD None None Meaning: Indicates the port number of the NTP server.
0, NTPC An NTP client performs time calibration with the NTP
BTS390 MOD server through the port specified by this parameter.
0 NTPC GUI Value Range: 123~5999,6100~65534
WCDM
A, LST Unit: None
BTS390 NTPC Actual Value Range: 123~5999,6100~65534
0 LTE Default Value: 123
7 Counters
8 Reference Documents