|
|
1 |
(% class="row" %) |
|
|
2 |
((( |
|
|
3 |
(% class="col-xs-12 col-sm-8 test-report-content" %) |
|
|
4 |
((( |
|
|
5 |
---- |
|
|
6 |
|
|
|
7 |
In real-world synchronization environments, it is common to encounter multiple PTP profiles operating side by side, particularly in mobile transport and xHaul networks. |
|
|
8 |
The decision on which profile to deploy typically depends on the network’s design, the hardware used, and the specific accuracy requirements of each segment. |
|
|
9 |
For instance, access and fronthaul segments often rely on ITU-T G.8275.1, since these areas require high-precision phase and time delivery with Full Timing Support (FTS). In contrast, aggregation or IP-based segments may utilize Partial Timing Support (PTS), as routers in these parts of the network frequently lack FTS compliance, making PTS the only viable option for time synchronization with PTP. |
|
|
10 |
Running both profiles at the same time in a single network is not unusual, and, traditionally, Profile Interworking Functions (IWFs) are implemented: one T-BC accepts ITU-T G.8275.1 input, translates it to ITU-T G.8275.2, and sends it downstream to its client(s). |
|
|
11 |
However, it is also feasible for a PTS T-BC to communicate directly with the Grandmaster and receive PTP packets, rather than requiring FTS T-BCs to convert from G.8275.1 to G.8275.2, which can introduce additional time error. |
|
|
12 |
This test was designed to confirm that T-BCs can function as boundary clocks according to G.8275.1 while, at the same time, transparently forwarding G.8275.2 PTP packets as regular data traffic, without processing them, changing timestamps, or altering correction fields. |
|
|
13 |
|
|
|
14 |
[[~[~[Figure 99: ITU-T G.8275.2 Packet Forwarding - general topology~>~>image:487254657526136833_packet_forwarding.png~|~|alt="Figure 99"~]~]>>attach:487254657526136833_packet_forwarding.png||target="_blank"]] |
|
|
15 |
|
|
|
16 |
The setup consisted of one Telecom Grandmaster (T-GM), one Full Timing Support (ITU-T G.8275.1; FTS) Telecom Boundary Clock (T-BC-1), and one Partial Timing Support (ITU-T G.8275.2; PTS) T-BC-2, with both T-BCs being connected to a Frequency/Phase Analyzer. |
|
|
17 |
To allow T-BC-2 to communicate with the T-GM through T-BC-1, either ISIS or static routes were configured. The T-GM would then send both FTS and PTS PTP packets downstream over a single link; T-BC-1 would process its own FTS PTP packets while transparently forwarding the PTS packets to T-BC-2. |
|
|
18 |
We verified transparent forwarding of the PTS packets by checking the StepsRemoved counter on T-BC-2. Since T-BC-1 should not have processed the PTS packets, T-BC-2 should see StepsRemoved = 1, as it is logically the first T-BC to receive them. This functionality was executed and verified in 11 different vendor combinations. |
|
|
19 |
Additionally, we applied the Network limits at reference point C at the end of the chain, as per ITU-T G.8271.1 for the max|TE,,L,,| (1100 ns) and the dynamic Time Error (dTE) Maximum Time Interval Error (MTIE) low-pass filtered. Unsurprisingly, every test combination was well within those limits, with all combinations within the class-level accuracy 6C (+/- 65 ns), as per ITU-T G.8271. |
|
|
20 |
Verifying this functionality was important because it means that IWFs may not be required in certain cases, thereby avoiding the time error and operational complexity they could introduce. |
|
|
21 |
|
|
|
22 |
{{container cssClass="tc-role-table"}} |
|
|
23 |
(% class="table-bordered" %) |
|
|
24 |
|=Telecom Grandmaster|=Telecom Boundary Clock - 1 - Transparent G.8275.1 Node|=Telecom Boundary Clock - 2 - ITU-T G.8275.2|=Frequency/Phase Analyzer |
|
|
25 |
|Microchip Time Provider 4500|Ciena 5164|Cisco 8711-32FH-M|Calnex Paragon neo |
|
|
26 |
|Microchip Time Provider 4500|Ciena 5164|Ericsson RAN Connect 6682|Calnex Paragon neo |
|
|
27 |
|Microchip Time Provider 4500|Ericsson Router 6676|ZTE ZXCTN 6120H-S|Keysight Time Sync Analyzer |
|
|
28 |
|Microchip Time Provider 4500|Ericsson Router 6671|Raisecom iTN8800-A|Keysight Time Sync Analyzer |
|
|
29 |
|Microchip Time Provider 4500|Raisecom RAX721-T-4C24|Ciena 5164|Calnex Paragon neo-A |
|
|
30 |
|Microchip Time Provider 4500|HPE ACX 7024|ZTE ZXR10 M6000-4SE|Calnex Paragon neo |
|
|
31 |
|Microchip Time Provider 4500|Cisco 8011-4G24Y4H-I|ZTE ZXR10 M6000-2S16|Keysight Time Sync Analyzer |
|
|
32 |
|Microchip Time Provider 4500|HPE ACX 7332|Ciena 5164|Keysight Time Sync Analyzer |
|
|
33 |
|Microchip Time Provider 4500|Ericsson RAN Connect 6682|ZTE ZXCTN 6120H-E|Calnex Paragon neo-A |
|
|
34 |
|Microchip Time Provider 4500|Ericsson Router 6676|Cisco 8011-4G24Y4H-I|Keysight Time Sync Analyzer |
|
|
35 |
|Microchip Time Provider 4500|Cisco 8011-4G24Y4H-I|HPE ACX 7024|Calnex Paragon neo |
|
|
36 |
|
|
|
37 |
{{/container}} |
|
|
38 |
|
|
|
39 |
Table 78: ITU-T G.8275.2 Packet Forwarding - Test combinations |
|
|
40 |
|
|
|
41 |
(% id="prev-next-links" %) |
|
|
42 |
|[[< Previous>>doc:Telecom Boundary Clock Class D Holdover Chain with Negative Leap Second]]|[[Next ~>>>doc:Upperside World Congress 2026 - Time Synchronization Demonstration]] |
|
|
43 |
))) |
|
|
44 |
|
|
|
45 |
(% class="col-xs-12 col-sm-4 test-report-sidebar" %) |
|
|
46 |
((( |
|
|
47 |
{{box}} |
|
|
48 |
{{include reference="Main.EANTC Transport & Cloud Networks Interop Test Report 2026.Sidebar Nav"/}} |
|
|
49 |
{{/box}} |
|
|
50 |
))) |
|
|
51 |
))) |
