Skip to content

TR 101 290

media.probe.tr101290

The tables map identifiers from ETSI TR 101 290 V1.3.1, §5.2 to Sapsan counters. Extended MPEG-TS counters do not imply that every standard check is implemented. Related fields are marked explicitly and must not be presented as exact ETSI indicators.

Priority 1

ID ETSI Sapsan counters Coverage
1.1 TS_sync_loss — No dedicated counter.
1.2 Sync_byte_error — No dedicated counter.
1.3 PAT_error errors_ts_pat Related diagnostics; not a complete TR 101 290 check.
1.3.a PAT_error_2 errors_ts_pat Related diagnostics; not a complete TR 101 290 check.
1.4 Continuity_count_error errors_ts_cc Continuity counter violations per PID.
1.5 PMT_error errors_ts_pmt Related diagnostics; not a complete TR 101 290 check.
1.5.a PMT_error_2 errors_ts_pmt Related diagnostics; not a complete TR 101 290 check.
1.6 PID_error errors_pid_lost Related diagnostics; not a complete TR 101 290 check.

Priority 2

ID ETSI Sapsan counters Coverage
2.1 Transport_error errors_ts_tei Packets with TEI per PID.
2.2 CRC_error errors_ts_psi_checksum CRC errors in parsed PSI tables.
2.3 PCR_error pcr_resync Related diagnostics; not a complete TR 101 290 check.
2.3a PCR_repetition_error — No dedicated counter.
2.3b PCR_discontinuity_indicator_error pcr_resync Related diagnostics; not a complete TR 101 290 check.
2.4 PCR_accuracy_error pcr_jitter_fail_500us, pcr_jitter_fail Related diagnostics; not a complete TR 101 290 check.
2.5 PTS_error — No dedicated counter.
2.6 CAT_error — No dedicated counter.

Priority 3

ID ETSI Sapsan counters Coverage
3.1 NIT_error — No dedicated counter.
3.1.a NIT_actual_error — No dedicated counter.
3.1.b NIT_other_error — No dedicated counter.
3.2 SI_repetition_error — No dedicated counter.
3.3 Buffer_error hrd_buffer_min, hrd_buffer_max, hrd_buffer_underrun Related diagnostics; not a complete TR 101 290 check.
3.4 Unreferenced_PID — No dedicated counter.
3.4.a Unreferenced_PID — No dedicated counter.
3.5 SDT_error — No dedicated counter.
3.5.a SDT_actual_error — No dedicated counter.
3.5.b SDT_other_error — No dedicated counter.
3.6 EIT_error — No dedicated counter.
3.6.a EIT_actual_error — No dedicated counter.
3.6.b EIT_other_error — No dedicated counter.
3.6.c EIT_PF_error — No dedicated counter.
3.7 RST_error — No dedicated counter.
3.8 TDT_error — No dedicated counter.
3.9 Empty_buffer_error — No dedicated counter.
3.10 Data_delay_error — No dedicated counter.

PCR / HRD

Per-PID PCR histogram: pcr_jitter_ok_0 is zero; pcr_jitter_ok_500ns is up to 500 ns; pcr_jitter_fail_500us is over 500 ns through 500 µs; pcr_jitter_fail is over 500 µs. pcr_resync counts clock resynchronizations, not every condition of 2.3b. HRD reports minimum and maximum headroom in bits and model-buffer underruns; it is not a full model of every T-STD buffer in 3.3.

Counters outside TR 101 290

Counters Meaning
errors_ts_scrambled Scrambled packets; this does not check CAT presence (2.6).
errors_adaptation_broken, broken_pes_count, broken_pes_sum Broken adaptation fields, number and size of broken PES packets.
errors_ts_service_lost Selected service disappearing from transport signaling.
empty_packets, packets, frames, bytes, sync_bytes Packet, frame and byte accounting, including empty packets and synchronization-search bytes. These are not indicators 1.1/1.2.
dts_goes_backwards, dts_jump_forward, too_large_dts_jump, time_corrections, corrected_backward_pts Timeline violations and corrections; not the PTS repetition check (2.5).
discarded_buffer_count, discarded_buffer_sum, fillers_count, fillers_sum Number and size of discarded buffers and inserted fillers.
unpaired_fields, warning_invalid_sibling_frames, padding_pes_count, padding_pes_sum, orphan_pes_count Unpaired fields, invalid sibling frames, padding PES and orphan PES.
recv_buffer_granted_bytes, recv_buffer_requested_bytes, recv_buffer_required_bytes, recv_buffer_drops, low_recv_buffer_secs UDP socket buffer sizes, kernel drops and seconds with insufficient buffer headroom.

Usage and limits

Compare per-PID error increments over equal intervals. A zero counter cannot validate a check without a dedicated field. RF level and BER require receiving-hardware measurements. Detailed series depend on the license; see monitoring.