Blog

White Paper Preview: T-Mobile & Carrier Ethernet SOAM Reporting: A Technical Comparison

May 31, 2024|LB Networks

This is a summary of the T-Mobile & Carrier Ethernet SOAM Reporting Technical Brief. Read the complete white paper here.

T-Mobile has implemented a system to monitor Service Level Agreements (SLAs) and manage credit claims from providers, focusing on Errored Seconds (ES) caused by various factors such as packet loss, latency, or jitter. This technical brief examines the differences between T-Mobile’s reporting methodology and the standard Carrier Ethernet SOAM (Service OAM) measurement and reporting approaches.

Carrier Ethernet SOAM Based Monitoring and Reporting

The Metro Ethernet Forum specifications outline the performance monitoring of Ethernet Services, defining key terms such as test period, measurement intervals, and aggregated results. For latency, jitter, and packet loss, network devices typically provide minimum, average, and maximum values over specified measurement intervals.

T-Mobile Errored Seconds Based Monitoring and Reporting

T-Mobile’s monitoring infrastructure is centered on Errored Seconds, which differs significantly from the Carrier Ethernet SOAM methodology. While both methods conduct similar low-level test measurements, the results are summarized differently, posing challenges in reconciling reporting results generated by each approach.

Comparing The Approaches

Aligning T-Mobile’s Errored Seconds approach with Carrier Ethernet SOAM reporting presents challenges, particularly in determining unavailable seconds due to latency or jitter. Different methods are discussed for generating unavailable seconds from SOAM data, each with its advantages and disadvantages.

Case Studies

Theoretical scenarios and real-world data analysis illustrate the differences between T-Mobile’s reporting and Carrier Ethernet SOAM based reporting. See comparisons of TMO Unavailable Seconds vs Site Availability Report Average Method vs Site Availability Report Statistical Method vs Using SOAM Maximum Method.

T-Mobile’s Errored Seconds approach differs from the standard Carrier Ethernet SOAM methodology, leading to variations in reporting results. Read the full T-Mobile & Carrier Ethernet SOAM Reporting Technical Brief, including data charts, here.

Contact LB Networks for help with T-Mobile eCompliance Reporting. We’re here to help!