ATSC 3.0 and 5G Broadcast share one RF channel
Joonyoung Park details the technical configuration and parameter settings for time-division multiplexing ATSC 3.0 and 5G Broadcast signals on a single RF channel, facilitated by the new CAS-muting feature in 5G Broadcast Rel-19 and ATSC 3.0's coexistence capabilities. The article explains how to reconcile timing parameters across different systems, highlighting the `min_time_to_next` field in ATSC A/321 and `L1B_frame_length_mode` in A/322, and references the newly revised ATSC A/327:2026-04 as the authoritative guideline.
Key Takeaways
- 5G Broadcast Rel-19 added CAS-muting, letting the 5GB cell stay quiet on Cell Acquisition Subframes for a programmed pattern.
- ATSC 3.0 A/321 §6 uses a 5-bit `min_time_to_next` field to promise when the next bootstrap arrives, with values such as 1100, 1200, 1300, and 1500 ms.
- A/322 §9.2 offers two ATSC frame modes: symbol-aligned mode and time-aligned mode, where `L1B_frame_length` is signaled in 5 ms units from 50 ms to 5000 ms.
- In the Las Vegas trial, a 1280 ms CAS cycle used an 80 ms ATSC frame and `min_time_to_next` set to 1300 ms after 1200 ms caused buffer growth and periodic transmitter restarts.
- A/327:2026-04 is now the authoritative Recommended Practice for ATSC TDM coexistence, replacing the earlier amendment draft.
Why It Matters
This turns ATSC 3.0 plus 5G Broadcast coexistence from a concept into a timing exercise with specific fields, units, and failure modes. The practical issue is not RF sharing in the abstract; it is aligning a 1 ms 3GPP CAS cycle with ATSC’s 5 ms frame timing and A/321’s sliding `min_time_to_next` table. The article also shows that misconfiguration can produce buffer growth and periodic transmitter restarts, which makes the signaling details operationally important for integrators. Watch for field trials that report their CAS cycle, ATSC frame length, and chosen `min_time_to_next` values, since those determine whether the link stays stable.
Read full article at joon.upthere.ai