Docs/ATSC3 Primer
Educational

ATSC 3.0 Primer

A comprehensive introduction to NextGen TV technology, protocols, and signaling.

1. What is ATSC 3.0?

ATSC 3.0 (Advanced Television Systems Committee 3.0), also known as NextGen TV, is the next-generation broadcast television standard in the United States. It represents a complete redesign of over-the-air television broadcasting, built on an all-IP foundation.

Unlike its predecessor ATSC 1.0 (which has been in use since 1996), ATSC 3.0 uses modern Internet Protocol (IP) for all data delivery, enabling unprecedented flexibility and capabilities for broadcasters and viewers alike.

Key Advantages of ATSC 3.0

  • 4K Ultra HD & HDR: Support for 4K resolution with High Dynamic Range
  • Immersive Audio: Dolby AC-4 and MPEG-H for object-based audio
  • Mobile Reception: Robust signal for portable and mobile devices
  • Emergency Alerts: Advanced Emergency Information (AEA) with rich media
  • Interactivity: Two-way communication via broadband return channel
  • Targeted Advertising: Personalized ad insertion capabilities

2. Protocol Stack

The ATSC 3.0 protocol stack is organized in layers, each responsible for specific functions in the broadcast chain. Understanding this stack is essential for stream analysis.

┌─────────────────────────────────────────────────┐
│            Application Layer                     │
│    (HTML5, HELD, DRM, Interactive Services)      │
├─────────────────────────────────────────────────┤
│            Presentation Layer                    │
│         (HEVC, AC-4, IMSC1 Captions)            │
├─────────────────────────────────────────────────┤
│            Transport Layer                       │
│           (ROUTE / DASH  or  MMT)               │
├─────────────────────────────────────────────────┤
│            Signaling Layer                       │
│    (LLS: SLT, RRT, SystemTime, AEA, CDT)        │
│    (SLS: USBD, S-TSID, MPD, HELD)               │
├─────────────────────────────────────────────────┤
│              Link Layer (ALP)                    │
│        (ATSC Link-layer Protocol)               │
├─────────────────────────────────────────────────┤
│            Physical Layer (PHY)                  │
│      (OFDM, LDPC/BCH, LDM, MIMO, PLP)          │
└─────────────────────────────────────────────────┘

3. Physical Layer (PHY)

The ATSC 3.0 physical layer uses OFDM (Orthogonal Frequency Division Multiplexing) with advanced error correction, enabling robust reception in challenging conditions.

Key PHY Technologies

PLPs (Physical Layer Pipes)

Multiple independent data streams within a single RF channel, each with configurable robustness and data rate. Enables mixing HD and mobile services.

LDM (Layered Division Multiplexing)

Transmits two signal layers at different power levels simultaneously, allowing robust mobile service alongside high-bitrate fixed service.

LDPC + BCH Coding

Concatenated error correction using Low-Density Parity-Check and Bose-Chaudhuri-Hocquenghem codes for near-Shannon-limit performance.

MIMO (Optional)

Multiple-Input Multiple-Output antenna technology can double throughput using cross-polarized antennas.

5. Signaling (LLS & SLS)

ATSC 3.0 uses a two-tier signaling architecture: LLS (Low Level Signaling) for bootstrap information, and SLS (Service Layer Signaling) for detailed service descriptions.

LLS (Low Level Signaling)

LLS tables are carried in dedicated ALP signaling packets on a well-known multicast address (224.0.23.60:4937). They provide the entry point for service discovery.

TableIDPurpose
SLT0x01Service List Table - Lists all services in the broadcast
RRT0x02Rating Region Table - Content rating information
SystemTime0x03Current time and leap second information
AEA0x04Advanced Emergency Alert - CAP-based alerts
CDT0x06Certificate Data Table - Security certificates

SLS (Service Layer Signaling)

SLS provides detailed information about each service's components, delivery, and presentation. It's delivered via ROUTE/DASH or MMT on service-specific multicast addresses.

USBD (User Service Bundle Description)

Top-level service description linking to all other SLS documents. Contains service name, language, and component references.

S-TSID (Service-based Transport Session Instance Description)

Maps content components to ROUTE sessions and LCT channels. Defines multicast addresses and TSI values.

MPD (Media Presentation Description)

DASH manifest describing media segments, representations, codecs, and timing. Standard MPEG-DASH format.

HELD (HTML Entry pages Location Description)

Describes interactive application entry points and associated resources for the receiver.

6. Media Delivery (ROUTE & MMT)

ATSC 3.0 supports two media delivery protocols: ROUTE/DASH (the primary method in the US) and MMT (used primarily in other regions).

ROUTE (Real-time Object Delivery over Unidirectional Transport)

ROUTE extends the FLUTE protocol for real-time streaming. It delivers DASH segments over UDP multicast using LCT (Layered Coding Transport).

ROUTE/LCT Delivery Flow:
ROUTE Session
    │
    ├── LCT Channel (TSI=0) ─── SLS Signaling
    │                              ├── USBD.xml
    │                              ├── S-TSID.xml
    │                              └── MPD.xml
    │
    ├── LCT Channel (TSI=1) ─── Video Segments
    │                              ├── init.mp4
    │                              ├── segment_1.m4s
    │                              └── segment_2.m4s
    │
    └── LCT Channel (TSI=2) ─── Audio Segments
                                   ├── init.mp4
                                   └── segment_1.m4s

MMT (MPEG Media Transport)

MMT is an alternative delivery protocol standardized by ISO/IEC 23008-1. It uses MPUs (Media Processing Units) instead of DASH segments.

ROUTE vs MMT Comparison

Feature
ROUTE/DASH
MMT
Origin
IETF/MPEG
ISO/IEC
Segment Format
CMAF/fMP4
MPU/MFU
Manifest
MPD (XML)
MMT-SI (Binary)
Primary Region
USA
Korea, Brazil

7. Service Discovery

Service discovery in ATSC 3.0 follows a hierarchical process, starting from the bootstrap signaling and drilling down to individual media components.

Service Discovery Flow:
1. Tune to RF Channel
         │
         ▼
2. Receive ALP Packets on PLP0
         │
         ▼
3. Parse LLS on 224.0.23.60:4937
         │
         ├──► SLT (Service List Table)
         │        │
         │        ├── Service ID: 5001
         │        ├── Short Name: "WKBW"
         │        ├── Major.Minor: 7.1
         │        └── SLS Multicast: 239.255.1.1:5001
         │
         ▼
4. Join Service Multicast (239.255.1.1:5001)
         │
         ▼
5. Parse SLS (USBD → S-TSID → MPD)
         │
         ▼
6. Join Component Multicasts
         │
         ├──► Video: 239.255.2.1:5001
         └──► Audio: 239.255.2.2:5001

Service Identification

Each service is uniquely identified by its Global Service ID (a URI likeurn:atsc:serviceid:wkbw.com:5001) and can be tuned using its Major.Minor channel number (e.g., 7.1).

8. Audio & Video Codecs

ATSC 3.0 mandates modern, efficient codecs to deliver high-quality content within available bandwidth.

Video Codecs

CodecStandardStatusFeatures
HEVC/H.265ISO/IEC 23008-2RequiredUp to 4K@60fps, HDR10, HLG
AVC/H.264ISO/IEC 14496-10OptionalLegacy support, HD only
VVC/H.266ISO/IEC 23090-3Future50% better compression than HEVC

Audio Codecs

CodecStandardStatusFeatures
AC-4ETSI TS 103 190RequiredDolby audio, object-based, immersive
MPEG-HISO/IEC 23008-3RequiredObject-based, personalization
AACISO/IEC 14496-3OptionalLegacy compatibility

9. Interactivity & Applications

ATSC 3.0 supports interactive applications using standard web technologies (HTML5, JavaScript, CSS), enabling rich viewer experiences.

Broadcast Apps

HTML5 applications delivered via broadcast, running in the receiver's app environment. Can overlay video with interactive content.

Companion Apps

Second-screen experiences on mobile devices, synchronized with broadcast content via ATSC 3.0 watermarking or network.

Hybrid Delivery

Combines broadcast and broadband for enhanced experiences. App resources can come from either path.

Targeted Advertising

Dynamic ad insertion based on viewer demographics, location, or preferences using ATSC 3.0's addressable advertising framework.

Application Signaling

Applications are signaled via the HELD (HTML Entry pages Location Description) document in SLS. The receiver uses this to locate and launch interactive content.

<HELD xmlns="tag:atsc.org,2016:XMLSchemas/ATSC3/AppSignaling/HELD/1.0/">
  <HTMLEntryPackage appContextId="app1" appRendering="true">
    <ContentInfo>
      <MediaUrl>app/index.html</MediaUrl>
    </ContentInfo>
  </HTMLEntryPackage>
</HELD>

Further Reading

  • A/300: ATSC 3.0 System Standard
  • A/322: Physical Layer Protocol
  • A/330: Link-Layer Protocol (ALP)
  • A/331: Signaling, Delivery, Synchronization, and Error Protection
  • A/332: Service Announcement
  • A/336: Content Recovery in Redistribution Scenarios
  • A/344: Application Signaling
  • View all ATSC standards at atsc.org →