This paper looks at the key considerations when testing Telecom Boundary Clocks (T-BCs), a key element in deliverying accurate Sync for LTE-A and TDD-LTE. What is a BC and why it's needed. Why a BC needs to be tested.
Technical brief acting as a primer for the G.8273.2 test plan Topics included: Introduction to Clocks, Packet-based Clocks Packet-based Clocks Packet-based Clocks, Boundary Clocks for Full Timing Support, Further reading.
A ready-made test plan for Telecom Boundary Clocks to ITU-T G.8273.2 standard. This paper details the tests available to comply with G.8273.2. Calnex makes recommendations on what tests may be appropriate.
This test plan details the test procedures specified in the ITU-T G.813 standard for wander performance of SDH equipment slave clocks (SECs). The test plan also explains how to use the Paragon-t to provide compliance to G.813.
The accuracy of Telecom Time Slave Clocks (T-TSCs) is essential to the successful roll-out of LTE-A and TDD-LTE. To meet the new G.8273.2 compliance limits, T-TSCs must meet a very stringent constant Time-Error (cTE) limit of 20 or 50 nanoseconds.
The Calnex Analysis Tool (CAT) provides a range of pre-defined ITU-T masks to verify that the performance of network devices meets the relevant standards. The CAT also lets you define your own masks; this application note shows you how.
A test plan for SyncE jitter and wander peformance to G.8261 and G.8262. This paper details the test procedures specified in the ITU-T G.8261 and G.8262 standards for Sync-E Jitter and Wander performance.