|
|
1 |
(% class="row" %) |
|
|
2 |
((( |
|
|
3 |
(% class="col-xs-12 col-sm-7 test-report-content" %) |
|
|
4 |
((( |
|
|
5 |
---- |
|
|
6 |
|
|
|
7 |
In production networks, there might be special cases and exceptions for which using Full Timing Support (FTS; ITU-T G.8275.1) throughout the entire network is not an option, and using Partial Timing Support (PTS; ITU-T G.8275.2) for the entire network is also not desirable. |
|
|
8 |
In such cases, it is necessary to configure both PTP profiles in the same network, requiring a Boundary Clock (T-BC) to be able to translate between the two profiles while complying with each profile's specifications. Such capability is known as an Interworking Function, IWF. |
|
|
9 |
|
|
|
10 |
These tests, therefore, aim to validate the ability of the Boundary clocks to translate from FTS to PTS and from PTS to FTS. |
|
|
11 |
|
|
|
12 |
For all these test cases, the Microchip TimeProvider®****4500 was acting as the Telecom Grandmaster (T-GM), sending either FTS traffic or PTS traffic downstream to T-BC-1. The Calnex Paragon-Neo PAM4 and the Keysight Time Sync Analyzer were used as the measurement tools. |
|
|
13 |
We had six different Telecom Boundary Clock (T-BC)/Telecom Slave Clock (T-SC) combinations for the FTS to PTS tests and seven different T-BC/T-SC pairs for PTS to FTS, with the T-BCs taking the role of the interworking translation from FTS to PTS/PTS to FTS. |
|
|
14 |
|
|
|
15 |
[[Figure 116: Interworking Protocol and Performance - Setup>>image:434720489329197057_5.09-5.10.png||alt="Figure 116" width="550"]] |
|
|
16 |
|
|
|
17 |
For the ITU-T G.8275.1 to ITU-T G.8275.2 (Full Timing Support to Partial Timing Support), the T-GM provided ITU-T G.8275.1 traffic towards the T-BC. The T-BC then translated FTS traffic to PTS traffic and sent it to the T-SC, where its output was measured. |
|
|
18 |
For the ITU-T G.8275.2 to ITU-T G.8275.1 (Partial Timing Support to Full Timing Support), it was the opposite way; The T-GM sent PTS traffic to the T-BC, which translated the traffic to FTS and sent it towards the T-SC, where the output was once again measured. |
|
|
19 |
|
|
|
20 |
For the limits of both test cases, we applied the constant time error (cTE) Class C limits for the FTS T-BCs, as defined in ITU-T G.8273.2, and Class B limits for the PTS T-BCs, as only Class A and Class B are specified for PTS T-BCs in ITU-T G.8273.4, section 8.2.2, table 8-1. Class C cTE is defined as +/- 10 nanoseconds (ns), and Class B cTE is defined as +/-20ns, giving us an accumulated total limit of +/- 30ns for the IWF network. |
|
|
21 |
|
|
|
22 |
All ITU-T G.8275.1 to ITU-T G.8275.2 and ITU-T G.8275.2 to ITU-T G.8275.1 test combinations passed this year, proving that a network's time synchronization performance should not be heavily impacted by the interworking function of the two different PTP profiles. |
|
|
23 |
|
|
|
24 |
{{container cssClass="tc-role-table"}} |
|
|
25 |
(% class="table-bordered" %) |
|
|
26 |
|=T-GM-A|=T-BC-1|=T-SC-1|=Timing Test Equipment |
|
|
27 |
|Microchip TimeProvider® 4500|Ericsson Router6671|Ciena 5134|Calnex Paragon-neo PAM4 |
|
|
28 |
|Microchip TimeProvider® 4500|Huawei ATN 910D-A|H3C S12500R-48Y8C|Calnex Paragon-neo PAM4 |
|
|
29 |
|Microchip TimeProvider® 4500|Huawei ATN 910D-A|Ciena 5134|Keysight Time Sync Analyzer |
|
|
30 |
|Microchip TimeProvider® 4500|Arrcus S9600-72XC|Ciena 5134|Keysight Time Sync Analyzer |
|
|
31 |
|Microchip TimeProvider® 4500|Arrcus S9600-72XC|Ericsson Router6671|Keysight Time Sync Analyzer |
|
|
32 |
|Microchip TimeProvider® 4500|Microchip TimeProvider® 4500|Ericsson Router6676|Calnex Paragon-neo PAM4 |
|
|
33 |
|
|
|
34 |
Table 66: T-BC Interworking Protocol and Performance - ITU-T G.8275.1 - to - ITU-T G.8275.2 T-T-BC performance |
|
|
35 |
{{/container}} |
|
|
36 |
|
|
|
37 |
{{container cssClass="tc-role-table"}} |
|
|
38 |
(% class="table-bordered" %) |
|
|
39 |
|=T-GM-A|=T-BC-1|=T-SC-1|=Timing Test Equipment |
|
|
40 |
|Microchip TimeProvider® 4500|Ciena 5134|Huawei ATN 910D-A|Keysight Time Sync Analyzer |
|
|
41 |
|Microchip TimeProvider® 4500|H3C S12500R-48Y8C|Ericsson Router6676|Keysight Time Sync Analyzer |
|
|
42 |
|Microchip TimeProvider® 4500|Arrcus S9600-72XC|Juniper ACX7348|Keysight Time Sync Analyzer |
|
|
43 |
|Microchip TimeProvider® 4500|Ciena 5134|Ericsson Router6671|Keysight Time Sync Analyzer |
|
|
44 |
|Microchip TimeProvider® 4500|Ericsson Router6676|H3C S12500R-48Y8C|Keysight Time Sync Analyzer |
|
|
45 |
|Microchip TimeProvider® 4500|Ericsson Router6671|Microchip TimeProvider® 4500|Calnex Paragon-neo PAM4 |
|
|
46 |
|Microchip TimeProvider® 4500|Microchip TimeProvider® 4500|Juniper ACX7024|Calnex Paragon-neo PAM4 |
|
|
47 |
|
|
|
48 |
Table 67: T-BC Interworking Protocol and Performance - ITU-T G.8275.2 - to - ITU-T G.8275.1 T-T-BC performance |
|
|
49 |
{{/container}} |
|
|
50 |
(% id="prev-next-links" %) |
|
|
51 |
|[[< Previous>>doc:Holdover with Enhanced Sync-E Support]]|[[Next ~>>>doc:Passive port monitoring]] |
|
|
52 |
))) |
|
|
53 |
|
|
|
54 |
(% class="col-xs-12 col-sm-5 test-report-sidebar" %) |
|
|
55 |
((( |
|
|
56 |
{{box}} |
|
|
57 |
{{include reference="Main.Multi-Vendor MPLS & SDN Interoperability Test Report 2025.Sidebar Nav"/}} |
|
|
58 |
{{/box}} |
|
|
59 |
))) |
|
|
60 |
))) |
