Company Confidential
Timing Synchronization for Mobile
Networks
MiCLK - POC Guidelines
Last Updated: January 22,2019
Doc. Version: 1.1
Doc. Owner: Hanan Tishler
Approved By:
This document contains information that is proprietary to RAD Data Communications Ltd. ("RAD"). No part of this document
may be reproduced or published or used in any form whatsoever without prior written approval by RAD Data Communications.
Right, title and interest, all information, copyrights, patents, know-how, trade secrets and other intellectual property or other
proprietary rights relating to this document and to the products described therein and any software components contained
therein are proprietary products of RAD protected under international copyright law and shall be and remain solely with RAD.
The trade names mentioned in this document are owned by RAD. No right, license, or interest to such trademark is granted
hereunder, and you agree that no such right, license, or interest shall be asserted by you with respect to such trademark. You
shall not copy, reverse compile or reverse assemble all or any portion of this document or the Product mentioned therein. You
are prohibited from, and shall not, directly or indirectly, develop, market, distribute, license, or sell any product that supports
substantially similar functionality as the product mentioned in this document, based on or derived in any way from such
products. Your undertaking in this paragraph shall survive perpetually.
``
January 22,2019 Company Confidential Page 2
``
1. Introduction ................................................................................................................ 5
1.1. Purpose ...................................................................................................................... 5
1.2. Scope .......................................................................................................................... 5
1.3. Glossary ...................................................................................................................... 5
1.4. References.................................................................................................................. 5
2. Mobile Services: Timing Synchronization for Mobile Networks ..................................... 6
3. MiCLK .......................................................................................................................... 7
3.1. Overview .................................................................................................................... 7
3.2. Features...................................................................................................................... 7
4. Equipment List ............................................................................................................. 8
5. MiCLK Physical Ports and LEDs ..................................................................................... 8
6. Typical Application and Deployment of MiCLK ............................................................. 9
7. MiCLK Web ................................................................................................................ 10
8. MiCLK – Configuration Model..................................................................................... 11
9. Mobile Services: Application Diagram ........................................................................ 11
10. IP Allocation .............................................................................................................. 12
11. Configuruing MiCLK_GM – G.8275-2........................................................................... 13
11.1. Application Diagram ................................................................................................. 13
11.2. Initial Configuration ................................................................................................. 13
11.3. Configuring the Hosting Device................................................................................ 14
11.4. MiCLK Operation Modes (DIP Switch) ..................................................................... 15
11.5. MiCLK Basic Configuration (MNG) ........................................................................... 16
11.6. MiCLK G.8275-2 Profile Configuration (GNSS) ......................................................... 17
11.7. MiCLK GNSS Status ................................................................................................... 18
11.8. MiCLK G.8275-2 Profile Configuration (Domain) ..................................................... 19
11.9. MiCLK G.8275-2 Profile Configuration (Router)....................................................... 20
11.10. MiCLK G.8275-2 Profile Configuration (Grandmaster) ............................................ 21
11.11. MiCLK G.8275-2 Profile Configuration (Optionally SyncE)....................................... 23
January 22,2019 Company Confidential Page 3
``
12. MiCLK_APTS – G.8275-2 ............................................................................................. 23
12.1. MiCLK_APTS – G.8275-2........................................................................................... 25
12.2. Clock domain – APTS clock source ........................................................................... 26
12.3. APTS – Recovered Clock ........................................................................................... 26
12.4. APTS – Bind 1588 Master to Recovered Clock (Web) .............................................. 27
12.4.1. APTS – Master Status .............................................................................................. 28
12.4.2. APTS – Recovered status ......................................................................................... 29
12.5. MiCLK_APTS – G.8275-2........................................................................................... 30
12.6. ETX-205_Slave .......................................................................................................... 30
12.6.1. ETX-205_Slave - G.8265-1 ....................................................................................... 31
12.7. Success Criteria – APTS ............................................................................................ 34
12.8. Success Criteria – APTS : CLI Log .............................................................................. 36
January 22,2019 Company Confidential Page 4
``
1. Introduction
1.1. Purpose
This document have the purpose to describe RAD Timing Synchronization for Mobile Networks
Solution, meeting high performance services standards delivering a reliable network for the customer
network.
1.2. Scope
This section serves as guidance to implementers of Timing Synchronization. The example architecture
presented here is not a requirement. It is designed with enough flexibility to allow different architectures
that suit multiple system requirements.
1.3. Glossary
BC Boundary Clock
TC Transparent Clock
PTP Precision Time Protocol
SyncE Synchronous Ethernet
1.4. References
Release Notes
https://www.rad.com/resources/miclk-ver-221-037
User Manual
https://www.rad.com/node/4525
Datasheet
https://www.rad.com/node/1521
Product Overview
https://www.rad.com/node/2443
January 22,2019 Company Confidential Page 5
``
2. Mobile Services: Timing Synchronization for Mobile
Networks
• Timing distribution based on PTP (1588) for accurate synchronization of LTE/LTE-A base
stations.
• The solution is based on distributed Grandmasters with the unique, patented form factor
of the MiCLK product
• Addressing stringent timing requirement (frequency/phase) for LTE/LTE-A macro and
small cells
• Optimized solution, distributing cost-effective PTP Grand-masters, closer towards cell
sites:
Dedicated PTP-GM device (ETX-2)
Unique SFP-based device (MiCLK), plugged into aggregation switch
• Key benefits, compared to alternatives
Saving on GPS for every cell-site
No need for supporting long BC/TC chains across the whole network
Best Timing quality with possible backup scenarios (e.g., backup from Sync-E)
January 22,2019 Company Confidential Page 6
``
3. MiCLK
3.1. Overview
• MiCLK is 1588 Grandmaster on SFP, joined to RAD Smart SPFs family
• Based on MiNID infrastructure and 1588 package from ETX
• Approved as a patent in Japan and USA (miniature Grandmaster)
• 3 ordering options (same HW, different SW load):
MiCLK supporting up to 8 1588 slaves (L3)
MiCLK supporting up to 24 1588 slaves (L3)
MiCLK supporting up to 64 1588 slaves (L3)
3.2. Features
• GNSS (Global Navigation Satellite System) Receiver supporting GPS system
• GNSS backup using Sync-E
• PTP ITU-T GM supporting the following Telecom Profiles:
G.8265.1 (IP\Unicast)
G.8275.1 (L2\Multicast)
G.8275.2 (IP\Unicast)
• VLAN tagging for G.8265.1,G.8275.2, G.8275.1 and management
• 64 IP unicast slaves @ 128 PPS (symmetric)
• DSCP/TOS marking for G.8265.1/G.8275.2 (IP/unicast) and management traffic
• Sync-E frequency distribution
• Power consumption less than 1.5W
• Full support of IPv6 for Management and PTP data.
• TACACS+ for enhanced security
• DSCP for APTS to prioritize the 1588 packets
January 22,2019 Company Confidential Page 7
``
4. Equipment List
The application has been built and tested using the following equipment.
Item Version Vendor Role
ETX-2i 6.6.0(0.22) RAD Dedicated PTP-GM device
MiCLK 2.2.1(0.37) RAD Unique SFP-based device
ETX-205 6.6.0(0.22) RAD Dedicated for Slave device
5. MiCLK Physical Ports and LEDs
• Ethernet port 1000-Base-X (GE) via MSA
• GNSS ANT via mini-BNC (front right connector)
• 1-PPS out (clock in for future phase) via mini-BNC (front left connector)
• Two LEDs:
Green – GNSS status
Red – Alarm
January 22,2019 Company Confidential Page 8
``
6. Typical Application and Deployment of MiCLK
MiCLK can be configured and deployed in 3 main synchronization methods:
• ITU-T G.8265.1 IP/unicast frequency without full timing support from the network
• ITU-T G.8275.1 L2/multicast, phase and time distribution with full timing support from the
network
• ITU-T G.8275.2 IP/unicast, time and phase with partial support from the network
As displayed below –MiCLK can be connected to any Router/Switch between the Core and
Aggregation/Access network connected. In addition, the Grandmaster can be a redundant clock
source to the MiCLK.
January 22,2019 Company Confidential Page 9
``
7. MiCLK Web
MiCLK can be managed from the Web in addition to CLI.
• 1588 Recovered block was added
• Another clock source is available in Clock Domain (APTS)
January 22,2019 Company Confidential Page 10
``
8. MiCLK – Configuration Model
The following elements should be configured in MiCLK
1588 Recovered should be configured if APTS is required
9. Mobile Services: Application Diagram
January 22,2019 Company Confidential Page 11
``
10. IP Allocation
January 22,2019 Company Confidential Page 12
``
11. Configuruing MiCLK_GM – G.8275-2
11.1. Application Diagram
11.2. Initial Configuration
1. Change MiCLK DIP Switch to “Config” Mode.
2. Insert MiCLK into the hub.
3. Access the MiCLK with a telnet/Web to its default IP
address – 192.168.205.1
4. Configure the following:
MNG
GNSS
Domain
Master PTP profile g.8275-2
Sync-E – Optional
5. Save.
6. Changed DIP switch to Normal.
7. Insert MiCLK into ETX-2i-10G (Port 0/17) or where the MNG flow is defined.
January 22,2019 Company Confidential Page 13
``
11.3. Configuring the Hosting Device
2.ETX-2i_10G_MNG.txt 3.ETX-2i_10G_MNG_MiCLK.txt
January 22,2019 Company Confidential Page 14
``
11.4. MiCLK Operation Modes (DIP Switch)
MiCLK is a member of the RAD Smart SFP family. As such, the DIP Switch configuration provides
four operational modes:
• INIT DB
• Normal
• Config
• SW Download
Mode Function
Normal Normal operation mode
Config Device response to its default IP address (192.168.205.1),
even if IP address has been changed (no host VLAN)
INIT DB Resets device database to its factory default values including reset host
parameters (IP, DGW, VLAN, etc’) during power up
SW Download Access MiCLK boot (“miBoot”) menu using SFP-CA.2
January 22,2019 Company Confidential Page 15
``
11.5. MiCLK Basic Configuration (MNG)
January 22,2019 Company Confidential Page 16
``
11.6. MiCLK G.8275-2 Profile Configuration (GNSS)
January 22,2019 Company Confidential Page 17
``
11.7. MiCLK GNSS Status
January 22,2019 Company Confidential Page 18
``
11.8. MiCLK G.8275-2 Profile Configuration (Domain)
January 22,2019 Company Confidential Page 19
``
11.9. MiCLK G.8275-2 Profile Configuration (Router)
January 22,2019 Company Confidential Page 20
``
11.10. MiCLK G.8275-2 Profile Configuration (Grandmaster)
January 22,2019 Company Confidential Page 21
``
Status of GNSS Grandmaster
January 22,2019 Company Confidential Page 22
``
11.11. MiCLK G.8275-2 Profile Configuration (Optionally SyncE)
12. MiCLK_APTS – G.8275-2
1. Change MiCLK DIP Switch to “Config” Mode
2. Insert MiCLK into the hub.
3. Access the MiCLK with Telnet to its default IP address – 192.168.205.1
4. Configure the following:
MNG
GNSS
Domain
Recovered 1 ptp profile g.8275-2 apts
Master PTP profile g.8275-2
Sync-E – Optionally
5. Save
6. Change DIP switch to Normal
7. Insert MiCLK into ETX-2i (Port 0/3)
January 22,2019 Company Confidential Page 23
``
Configuration on Web:
Application Diagram
January 22,2019 Company Confidential Page 24
``
12.1. MiCLK_APTS – G.8275-2
The following instructions are based on the previous slides??
For each group, repeat the following steps:
• MiCLK G.8275-2 Profile Configuration (GNSS).
• MiCLK G.8275-2 Profile Configuration (Domain).
• MiCLK G.8275-2 Profile Configuration (Router- set the IP per group).
January 22,2019 Company Confidential Page 25
``
12.2. Clock domain – APTS clock source
APTS should be declared as a clock source in clock Domain
12.3. APTS – Recovered Clock
Recovered IP address should be identical to the 1588 Master IP address
CLI:
MiCLK>config>clock# [no] recovered <id> ptp profile g.8275-1 apts
MiCLK>config>clock>recovered(1)# [no] revertive
MiCLK>config>clock>recovered(1)# wait-to-restore <seconds>[0..720]default 300
MiCLK>config>clock>recovered(1)# [no] ip-address <ip-address>
MiCLK>config>clock>recovered(1)# ptp-domain <domain-id>[0..127, default 24]
MiCLK>config>clock>recovered(1)# clear-network-metrics {master-to-
slave|slave-to-master|all}
MiCLK>config>clock>recovered(1)# [no] shutdown
January 22,2019 Company Confidential Page 26
``
12.4. APTS – Bind 1588 Master to Recovered Clock (Web)
The 1588 recovered entity can work opposite two 1588 Grandmasters
January 22,2019 Company Confidential Page 27
``
12.4.1.APTS – Master Status
1588 Master attached to 1588 recovered (APTS) can be observed via WEB
January 22,2019 Company Confidential Page 28
``
12.4.2.APTS – Recovered status
January 22,2019 Company Confidential Page 29
``
12.5. MiCLK_APTS – G.8275-2
For each group, repeat the following steps:
• MiCLK G.8275-2 Profile Configuration (Master).
• MiCLK G.8275-2 Profile Configuration (Master Status).
12.6. ETX-205_Slave
Configure the following Flows thru the bridge:
• MNG Configuration for ETX-205_Slave : Using VLAN 4094
• 1588 Flows From/To MiCLK: Using VLAN 200
January 22,2019 Company Confidential Page 30
``
12.6.1.ETX-205_Slave - G.8265-1
January 22,2019 Company Confidential Page 31
``
January 22,2019 Company Confidential Page 32
``
January 22,2019 Company Confidential Page 33
``
12.7. Success Criteria – APTS
Disconnect the GNSS antenna from the side where the APTS is defined
The status of the GNSS is down on the Domain
The Clock Domain manages the frequency sources.
Thus, when there is GNSS failure, the Clock Domain switches to an alternative fallback
frequency.
This fallback frequency can be from SyncE or from APTS.
As a result, the Clock Domain shows Locked status to the selected frequency source.
January 22,2019 Company Confidential Page 34
``
The PTP Master however, when GNSS fails, switches to Holdover states. This can be seen by the
clockClass in the Master screens.
When GNSS is LOCKED the transmitted clockClass is 6. When there is a GNSS failure, the
transmitted clockClass switches to 7. Depending on the frequency quality it either remains 7 or
downgrades according to Table 2 in G.8275.2 (and the corresponding table in G.8275.1).
January 22,2019 Company Confidential Page 35
``
12.8. Success Criteria – APTS : CLI Log
Configure -> Reporting -> show log
January 22,2019 Company Confidential Page 36
