PTP SYNC

IEEE 1588 Time and Phase SynchronizationFAJ 121 2022

This feature provides the capability to recover time/phase synchronization from a PTP
master. The feature uses packet-based synchronization and the Precision Timing Protocol
(PTP).
FAJ 121 2022
The PTP synchronization reference consists of an PTP Slave in the node and an
associated PTP master in another node.
Main requirement for PTP
Below features need to be activated in the node to use PTP sync:

IEEE 1588 Boundary Clock

The function introduces a Boundary Clock according to the Telecom Profile for time synchronization, thereby providing additional
flexibility when implementing time synchronization of RAN.
FAJ 121 4755 R2
Mandatory MO’s in E-NodeB
10620 Transport=1,Synchronization=1
10621 Transport=1,Synchronization=1,RadioEquipmentClock=1
10622 Transport=1,Synchronization=1,RadioEquipmentClock=1,RadioEquipmentClockReference=1

10525 Transport=1,Ptp=1
10526 Transport=1,Ptp=1,BoundaryOrdinaryClock=1
10527 Transport=1,Ptp=1,BoundaryOrdinaryClock=1,PtpBcOcPort=1
10528Transport=1,Ptp=1,BoundaryOrdinaryClock=1,PtpBcOcPort=2
When the Radio equipment Clock is locked to a synchronization reference, the Holdover
Capability is trained. When none of the references are selectable, the Holdover Capability
keeps the latest known properties of the Radio equipment Clock algorithm in Holdover
Modes. If the Radio Equipment Clock was Time Locked, the Holdover capability can keep a
Time Holdover Mode for a limited time. If a time synchronization reference has not become
"selectable" within this time, the Holdover Capability goes to the Frequency Holdover Mode.
If the Holdover Capability has been trained, the Frequency Holdover mode can be kept for
the rest of the lifetime of the node.
The described holdover capability relies on the stability of the oscillator and the training of
the synchronization algorithm.
Clock state should be Time locked
ADG5312-L21> get Transport=1,Synchronization=1,RadioEquipmentClock=1

180613-10:44:54 14.222.125.44 17.0m MSRBS_NODE_MODEL_18.Q1_358.27843.38_8d5b stopfile=/tmp/822

$ssh_pid = 8450

Connected to 14.222.125.44 (SubNetwork=ONRM_ROOT_MO,SubNetwork=RadioNodeTDD,MeContext=ADG5312-L21,ManagedElement=ADG5312-L21)

=================================================================================================================
11641 Transport=1,Synchronization=1,RadioEquipmentClock=1
=================================================================================================================
clockOperQuality 15 (QL_UNKNOWN)
clockSettledQuality 15 (QL_UNKNOWN)
currentAssistingReference
currentRadioClockReference Synchronization=1,RadioEquipmentClock=1,RadioEquipmentClockReference=1
minQualityLevel Struct{3}
>>> 1.qualityLevelValueOptionI = 1 (PRC)
>>> 2.qualityLevelValueOptionII = 2 (STU)
>>> 3.qualityLevelValueOptionIII = 1 (UNK)
nodeGroupRole 0 (NOT_ACTIVATED_AS_NODE_GROUP_MEMBER)
radioClockPriorityTable [1] =
>>> radioClockPriorityTable = Transport=1,Synchronization=1,RadioEquipmentClock=1,RadioEquipmentClockReference=1
radioClockState 6 (RNT_TIME_LOCKED)
radioEquipmentClockId 1
selectionProcessMode 2 (QL_DISABLED)
timeSyncAssistanceState 1 (FEATURE_NOT_ACTIVATED)
=================================================================================================================
Total: 1 MOs
Clock Reference Should Have No Fault
ADG5312-L21> get Transport=1,Synchronization=1,RadioEquipmentClock=1,RadioEquipmentClockReference=1

180613-10:47:23 14.222.125.44 17.0m MSRBS_NODE_MODEL_18.Q1_358.27843.38_8d5b stopfile=/tmp/822

$ssh_pid = 10252

Connected to 14.222.125.44 (SubNetwork=ONRM_ROOT_MO,SubNetwork=RadioNodeTDD,MeContext=ADG5312-L21,ManagedElement=ADG5312-L21)

=================================================================================================================
11642 Transport=1,Synchronization=1,RadioEquipmentClock=1,RadioEquipmentClockReference=1
=================================================================================================================
adminQualityLevel Struct{3}
>>> 1.qualityLevelValueOptionI = 2 (SSU_A)
>>> 2.qualityLevelValueOptionII = 2 (STU)
>>> 3.qualityLevelValueOptionIII = 1 (UNK)
administrativeState 1 (UNLOCKED)
availabilityStatus i[0] =
encapsulation Ptp=1,BoundaryOrdinaryClock=1
holdOffTime 1000
operQualityLevel 18 (PRTC)
operationalState 1 (ENABLED)
priority 1
radioEquipmentClockReferenceId 1
receivedQualityLevel 18 (PRTC)
referenceStatus 1 (NO_FAULT)
syncRefType 4 (PTP_TIME)
useQLFrom 1 (RECEIVED_QL)
waitToRestoreTime 60
Inter-communication

• Network synchronization using

timestamps in packets
• Precision Time Protocol (PTP)
• Messages are transmited
between Master and Slave
• Communication mode used:
Multicast
Alarm names:
Alarms & Counters
SyncPTPTimePDVProblem

SyncPTPTimeAvailability

SyncPTPTimeReliabilityAlarm

SyncPTPTimeReachabilityAlarm

Counters:
Counters to check if packets are transmitted & recieved by E-nodeB

 ptpAnnounceRx: number of received Announce messages.

 ptpAnnounceTx: number of transmitted Announce messages.

 ptpSyncRx: number of received Sync messages.

 ptpSyncTx: number of transmitted Sync messages.

 ptpFollowUpRx: number of received Follow Up messages.

 ptpFollowUpTx: number of transmitted Follow Up messages.

 ptpDelayReqRx: number of received Delay Request messages.

 ptpDelayReqTx: number of transmitted Delay Request messages.

 ptpDelayRspRx: number of received Delay Response messages.

 ptpDelayRspTx: number of transmitted Delay Response messages.

 ptpPacketsRx: number of all received PTP packets.

 ptpPacketsTx: number of all transmitted PTP packets.

Counters to check delay

◾ptpMeanPathDelayAvg: Average value of measured mean path delay.

◾ptpMeanPathDelayMax: Maximum value of measured mean path delay.

◾ptpMeanPathDelayMin: Minimum value of measured mean path delay.

◾ptpDownLinkDelayAvg: Average value of measured downlink delay.

◾ptpDownLinkDelayMax: Maximum value of measured downlink delay.

◾ptpDownLinkDelayMin: Minimum value of measured downlink delay.

◾ptpUpLinkDelayAvg: Average value of measured uplink delay.

◾ptpUpLinkDelayMax: Maximum value of measured uplink delay.

◾ptpUpLinkDelayMin: Minimum value of measured uplink delay.

There are other counters also to measure uplink & downlink delay separately.
Counters comparison during problem time
• 0001: completed at 2018-06-16 08:36:43

• 0001: show radio equipment clock state changes history

• 0001: row | timeStamp | duration | radioClockState

• 0001: ------------------------------------------------------------------------------------

• 0001: #1 | 2018-06-16 02:15:18.329107827 | 0 sec | UNKNOWN

• 0001: #2 | 2018-06-16 02:15:18.329770437 | 3 min, 13 sec | WARMUP

• 0001: #3 | 2018-06-16 02:19:13.088331102 | 6 sec | FREQUENCY_LOCKED

• 0001: #4 | 2018-06-16 02:19:19.390143187 | 7 sec | TIME_OFFSET_LOCKED

• 0001: #5 | 2018-06-16 02:19:25.693670609 | 4 hh, 20 min, 23 sec | RNT_TIME_LOCKED ###SYNC RECOVERED AFTER NODE RESTART – 4 hours was fine

• 0001: #6 | 2018-06-16 06:39:48.713776703 | 6 min, 27 sec | RNT_TIME_HOLDOVER ## TOGGLING OF SYNC STARTED at 06:39 (ROP)

• 0001: #7 | 2018-06-16 06:46:15.875272078 | 6 sec | RNT_TIME_LOCKED

• 0001: #8 | 2018-06-16 06:46:22.306586281 | 4 min, 59 sec | RNT_TIME_HOLDOVER

• 0001: #9 | 2018-06-16 06:51:21.306459312 | 7 sec | RNT_TIME_LOCKED

• 0001: #10 | 2018-06-16 06:51:27.630742765 | 21 sec | TIME_OFFSET_LOCKED

• 0001: #11 | 2018-06-16 06:51:48.636648547 | 4 min, 13 sec | RNT_TIME_LOCKED

• 0001: #12 | 2018-06-16 06:56:01.456768234 | 1 hh, 40 min, 41 sec | RNT_TIME_HOLDOVER

• 0001: ------------------------------------------------------------------------------------

• Report from 2018-06-16 05:30 UTC to 2018-06-16 08:29 UTC (12 ropfiles)

• Node SW: CXP9024418/6_R34C90 (18.Q1)

• Date: 2018-06-16

• Object Counter 05:30 05:45 06:00 06:15 06:30 06:45 07:00 07:15 07:30 07:45 08:00 08:15

• ManagedElement=BKK3247-L23,Transport=1,Ptp=1,BoundaryOrdinaryClock=1,PtpBcOcPort=1 ptpAnnounceForeignMasterRx 0 0 0 0 0 0 0 0 0 0 0 0

• ManagedElement=BKK3247-L23,Transport=1,Ptp=1,BoundaryOrdinaryClock=1,PtpBcOcPort=1 ptpAnnounceRx 7200 7200 7200 7200 7171 7192 7200 7025 7161 7185 7201 7200

• ManagedElement=BKK3247-L23,Transport=1,Ptp=1,BoundaryOrdinaryClock=1,PtpBcOcPort=1 ptpAnnounceTx 0 0 0 0 0 0 0 9 0 0 0 0

• ManagedElement=BKK3247-L23,Transport=1,Ptp=1,BoundaryOrdinaryClock=1,PtpBcOcPort=1 ptpDelayReqRx 0 0 0 0 0 0 0 0 0 0 0 0

• ManagedElement=BKK3247-L23,Transport=1,Ptp=1,BoundaryOrdinaryClock=1,PtpBcOcPort=1 ptpDelayReqTx 7113 7215 7193 7204 7132 7264 7141 7036 7079 7133 7165 7149

• ManagedElement=BKK3247-L23,Transport=1,Ptp=1,BoundaryOrdinaryClock=1,PtpBcOcPort=1 ptpDelayRspRx 7113 7215 7193 7204 7132 7264 7141 7027 7079 7133 7165 7149

• ManagedElement=BKK3247-L23,Transport=1,Ptp=1,BoundaryOrdinaryClock=1,PtpBcOcPort=1 ptpDelayRspTx 0 0 0 0 0 0 0 0 0 0 0 0

• ManagedElement=BKK3247-L23,Transport=1,Ptp=1,BoundaryOrdinaryClock=1,PtpBcOcPort=1 ptpDownLinkDelayAvg 72 72 73 71 555059378 819968963 89304306 89304335 26125592 54950533 89304437 89304462
Time & phase deviation by coli commands

Phase deviation:
Command : syncptpcentral info clock

- Example with stable phase:

$ syncptpcentral info clock

...
ClockStatus Changes:
2017-07-26 08:45:49 Slave port configured on TN_A with port number: 1 clockStatus: NO_FAULT
2017-07-26 08:45:30 No slave port configured clockStatus: NO_FAULT

- Example with unstable phase:

$ syncptpcentral info clock

...
ClockStatus Changes:
2017-07-26 11:01:57 Slave port configured on TN_A with port number: 1 clockStatus: PHASE UNSTABLE
2017-07-26 10:52:46 Slave port configured on TN_A with port number: 1 clockStatus: NO_FAULT
2017
Command : syncptplocal info settings

- Example with stable phase:

$ syncptplocal info settings

...
**************************************Phase unstable history*************************************
time | firstJump | refId | unstableRef | timer | offset (sec & fraction)
-------------------------------------------------------------------------------------------------
*************************************************************************************************

- Example with unstable phase:

$ syncptplocal info settings

...
**************************************Phase unstable history*************************************
time | firstJump | refId | unstableRef | timer | offset (sec & fraction)
-------------------------------------------------------------------------------------------------
07-26 10:56:17 | true | 11 | false | false | 0 2.217400427717564e-07
07-26 11:01:57 | true | 11 | true | true | 0 9.537369156875641e-06
*************************************************************************************************
Time delay measurement
Command : /netsync/syncptpcentral info all
/netsync/synclocal info all

show radio equipment clock state changes history

====================================================================================
row | timeStamp | duration | radioClockState
------------------------------------------------------------------------------------
#1 | 2018-06-04 08:28:10.042673632 | 0 sec | UNKNOWN
#2 | 2018-06-04 08:28:10.043162773 | 3 min, 15 sec | WARMUP
#3 | 2018-06-04 08:32:06.676193062 | 6 sec | FREQUENCY_LOCKED
#4 | 2018-06-04 08:32:12.978042203 | 7 sec | TIME_OFFSET_LOCKED
#5 | 2018-06-04 08:32:19.279881328 | 2 dd, 2 hh, 10 min | RNT_TIME_LOCKED
#6 | 2018-06-06 10:42:39.478131625 | 1 min, 8 sec | RNT_TIME_HOLDOVER
#7 | 2018-06-06 10:43:47.476129453 | 1 hh, 53 min, 45 sec | RNT_TIME_LOCKED
#8 | 2018-06-06 12:37:32.476868015 | 1 min, 6 sec | RNT_TIME_HOLDOVER
#9 | 2018-06-06 12:38:38.477295843 | 4 dd, 21 hh, 56 min | RNT_TIME_LOCKED
#10 | 2018-06-11 10:35:01.476862922 | 2 min, 2 sec | RNT_TIME_HOLDOVER
#11 | 2018-06-11 10:37:03.477222093 | 1 dd, 0 hh, 1 min | RNT_TIME_LOCKED
#12 | 2018-06-12 10:38:25.476090734 | 1 min, 1 sec | RNT_TIME_HOLDOVER
#13 | 2018-06-12 10:39:26.477572968 | 1 dd, 0 hh, 21 min | RNT_TIME_LOCKED
#14 | 2018-06-13 11:00:38.480135906 | 1 min, 59 sec | RNT_TIME_HOLDOVER
#15 | 2018-06-13 11:02:37.477115562 | 2 hh, 54 min, 18 sec | RNT_TIME_LOCKED

t_acc : 2 [ns] means sync accuracy = 2 nanoseconds

t_acc_with_error : 1000 [ns] sync accuracy with error means some intermediate equipment error
meanPathDelay: 11010048 (168 ns) delay in Path
PDV Limit & measurement

************************DefectEval******************************
refId: 11 defectDownlink defectUplink highPdvLimit lowPdvLimit pktRate windowSize
0x0 0x0 1.000000e-04 2.500000e-07 128 10
Status: downlink uplink
buff_isfull: TRUE TRUE
buff_length: 1280 1280
buff_pointer: 213 450
init_sample_cnt: 2 2
outlierFlag: FALSE FALSE
outlierLimit: 1.000000e-03 1.000000e-03
var: 1.989332e-17 5.440141e-18
Measured_PDV: 2.296999e-08 1.201192e-08
x0: 1.840000e-07 1.850000e-07
x1: 1.850000e-07 1.850000e-07
x2: 1.940000e-07 1.890000e-07

Unit of this is second. So basically this means 0,1 ms = 100 mS(microseconds).

Parameters we can set to minimize Time delay impact

180620-12:35:50 14.222.125.44 17.0m MSRBS_NODE_MODEL_18.Q1_358.27843.38_8d5b stopfile=/tmp/28747

####################################################################################################################################

MO Class Attribute Type Flags

####################################################################################################################################

Lrat.ENodeBFunction timePhaseMaxDeviation derivedRef:Lrat.Lrat_ENodeBFunction_timePhaseMaxDeviation

------------------------------------------------------------------------------------------------------------------------------------

Defines the maximum allowed time/phase deviation for time/phase synchronization of the eNodeB.

Dependencies: This parameter is relevant when the parameter timeAndPhaseSynchCritical has the value true.

Disturbances: Changing this attribute can cause loss of traffic.

Default=100

Range: 9 to 100

Unit: 0.1 microseconds

************************************************************************************************************************************

180620-12:44:54 14.222.125.44 17.0m MSRBS_NODE_MODEL_18.Q1_358.27843.38_8d5b stopfile=/tmp/28747

####################################################################################################################################

MO Class Attribute Type Flags

####################################################################################################################################

Lrat.ENodeBFunction timeAndPhaseSynchCritical boolean

------------------------------------------------------------------------------------------------------------------------------------

If set to true, the cell will be disabled if the time and phase synchronization accuracy of the eNodeB is not fulfilled.

Default=false

************************************************************************************************************************************

Total: 1 MOs, 1 attributes