|
|
1 |
(% class="row" %) |
|
|
2 |
((( |
|
|
3 |
(% class="col-xs-12 col-sm-7 test-report-content" %) |
|
|
4 |
((( |
|
|
5 |
---- |
|
|
6 |
|
|
|
7 |
The Open Radio Access Network, commonly known as ORAN, has emerged as a significant trend in the telecommunications industry. |
|
|
8 |
Due to its vast potential, networking professionals are actively exploring, testing, and implementing O-RAN solutions. The significance of O-RAN and its components, especially its fronthaul network, cannot be ignored. |
|
|
9 |
The fronthaul network is a key component of O-RAN architecture and plays a critical role in its efficiency. It requires precise and reliable Time Synchronization to ensure the system's integrity, functionality, and performance. |
|
|
10 |
|
|
|
11 |
=== O-RAN Fronthaul LLS-C2 (Option A) === |
|
|
12 |
In our tests, we took the liberty of making one major change to the O-RAN Fronthaul LLS-C2 (Option A) topology: We exchanged the Open Distributed Unit (O-DU) for a Boundary Clock. |
|
|
13 |
Our setup consisted of one Grandmaster (T-GM), one Boundary Clock(T-BC ), and two separate timing paths branching from the T-BC. Each path had one Hub-Site Router (HSR) and one Cell-Site Router (CSR). Both CSRs were connected to a measurement tool to measure the relative time error between their outputs. |
|
|
14 |
All three test runs with different vendor combinations passed the requirements for the maximum absolute time error and the maximum relative time error, as defined in O-RAN.WG9.XTRP-TST.0-R004-v05.00, section 9.1.5; however, we were unable to test 1PPS. |
|
|
15 |
|
|
|
16 |
[[Figure 119: O-RAN Fronthaul LLS-C2 (Option A) - Setup>>image:434081707012915201_5.14.png||alt="Figure 119" width="550"]] |
|
|
17 |
|
|
|
18 |
=== O-RAN Fronthaul LLS-C3 Configuration with GM from Fronthaul === |
|
|
19 |
Additionally, we executed a test to emulate an LLS-C3 scenario as per O-RAN.WG9.XTRP-SYN.0-R003-v05.00, where the GM was at the Fronthaul. |
|
|
20 |
This test was executed once, with the Keysight Time Sync Analyzer serving as the emulated O-DU, O-CU, and O-RU and the Keysight IxNetwork as the traffic generator. The Ciena 8140 took the role of the HSR, and the Juniper ACX7100-32C of the CSR. |
|
|
21 |
The maximum absolute time error was 2.344ns for the Ciena 8150 and 4.781ns for the Juniper ACX7100-32C, both incredibly low and well within the limits of ITU-T G.8273.2 Class D media converter pairs. |
|
|
22 |
|
|
|
23 |
[[Figure 120: O-RAN Fronthaul LLS-C3 Configuration with GM from Fronthaul - Setup>>image:434865443406610433_5.13.png||alt="Figure 120" width="550"]] |
|
|
24 |
|
|
|
25 |
{{container cssClass="tc-role-table"}} |
|
|
26 |
(% class="table-bordered" %) |
|
|
27 |
|=T-GM-A|=HSR-1|=HSR-2|=CSR-1|=CSR-2|=Timing Test Equipment|=T-BC-1 |
|
|
28 |
|Microchip TimeProvider® 4500|Microchip TimeProvider® 4500|Juniper ACX7100-32C|Ericsson Router6671|H3C S12500R-48Y8C|Keysight Time Sync Analyzer|Ciena 5134 |
|
|
29 |
|Microchip TimeProvider® 4500|Microchip TimeProvider® 4500|Juniper ACX7100-32C|Ericsson Router6671|Huawei ATN 910D-A|Calnex Paragon-neo PAM4|Ciena 8140 Coherent Metro Router |
|
|
30 |
|Microchip TimeProvider® 4500|Microchip TimeProvider® 4500|Juniper ACX7100-32C|Ericsson Router6671|Huawei ATN 910D-A|Calnex Paragon-neo PAM4|Arrcus S9610-36D |
|
|
31 |
|
|
|
32 |
Table 70: O-RAN Tests - O-RAN Fronthaul LLS-C2 Option A |
|
|
33 |
{{/container}} |
|
|
34 |
|
|
|
35 |
{{container cssClass="tc-role-table"}} |
|
|
36 |
(% class="table-bordered" %) |
|
|
37 |
|=T-GM-A|=HSR-1|=CSR-1|=Timing Test Equipment|=Traffic Generator |
|
|
38 |
|Keysight Time Sync Analyzer|Ciena 8140 Coherent Metro Router|Juniper ACX7100-32C|Keysight Time Sync Analyzer|Keysight IxNetwork |
|
|
39 |
|
|
|
40 |
Table 71: O-RAN Tests - O-RAN Fronthaul LLS-C3 Configuration with GM from Fronthaul |
|
|
41 |
{{/container}} |
|
|
42 |
(% id="prev-next-links" %) |
|
|
43 |
|[[< Previous>>doc:Passive port monitoring]]|[[Next ~>>>doc:Time Synchronization Source Failover]] |
|
|
44 |
))) |
|
|
45 |
|
|
|
46 |
(% class="col-xs-12 col-sm-5 test-report-sidebar" %) |
|
|
47 |
((( |
|
|
48 |
{{box}} |
|
|
49 |
{{include reference="Main.Multi-Vendor MPLS & SDN Interoperability Test Report 2025.Sidebar Nav"/}} |
|
|
50 |
{{/box}} |
|
|
51 |
))) |
|
|
52 |
))) |