Ir para o conteúdo

TV 3.0 Architecture

Brazilian TV has become a network stack.

TV 3.0 cheat sheet for application developers and broadcast headend operators. Concepts in reading order, with eight animated infographics where sequence matters, and the normative reference backing every claim.

PhysicalTransportSignalingApplicationAlert

Five parts, in reading order:

  1. The system — What changed from TV 2.X and how the layers fit together
  2. Broadcast — Physical layer, the chain to the antenna, IP transport, and test assets
  3. Signaling — LLS and SLS table by table, service discovery, and service guide
  4. Applications — The model, the two languages, delivery, lifecycle, APIs, and middleware
  5. Cross-cutting services — Emergency alerting, accessibility, and privacy

Part 1 · The system

TV 3.0 is not an upgrade to SBTVD: it is a new system, defined by nine standards published in 2025 and marketed commercially as DTV+. Fundamentally, transport has shifted from a TV multiplex to an IP network, and the primary component of a service is no longer a video stream — it is an application.

1.1 What changed from TV 2.X to TV 3.0

If you know SBTVD, the table below is the shortest path across. Every row is a replacement, not an add-on.

Layer TV 2.X · SBTVD, ISDB-Tb TV 3.0 · DTV+
Physical layer ISDB-T, 13-segment division ATSC A/322 with MIMO, LDM, and TxID
Transport MPEG-2 Transport Stream IP multicast, ROUTE/DASH — MMT/MMTP excluded
Signaling SI, PSI, AIT LLS and SLS in XML, with BAMT, TBSAT, BALD, and PRRD
Video H.264 VVC, with HEVC, AVC, and LCEVC; HDR and up to 8K
Audio AAC MPEG-H Audio, with AAC, AC-4, and E-AC-3 JOC
Captions ARIB closed caption IMSC1 and WebVTT
Sign language open window, burned into video Closed signing: Libras video, gloss, and motion streams, toggleable by the viewer
Applications Ginga-NCL and Ginga-J, optional to the service TV 3.0 Ginga-NCL and Ginga-HTML5. The application is the service — Service Type 30 is literally named Service Based on Bootstrap Application
Alerting EWBS, simple notice AEA: rich, area-targeted message capable of waking a receiver from standby
Viewer data no model PRRD: purpose-specific consent declared prior to any data collection
Broadband accessory part of the service: components can arrive over the air and over the internet within the same program

1.2 How the layers fit together

The figure below is identical across all standards in the suite. Notice the asymmetry: application coding is not a layer sitting atop the stack — it is a band embracing video, audio, captions, sign language, and emergency alerting. Everything the viewer sees passes through it.

FIGURE 1 identical across five standards

Layered architecture

The stack as drawn by the standard: application coding wraps around the five media and alert coding blocks from above; transport sits underneath; over-the-air and broadband form the base. NBR 25609 (receivers) is not in the standard's drawing — it spans everything. Select a block.

Figure 1 of ABNT NBR 25601 through 25608, reproduced structurally; the receivers column is an addition of this page.

NBR 25601–25609:2025, Figure 1
  • PhysicalMIMO, LDM, TxID, PLP, RF
  • TransportROUTE, IP, UDP, DASH, HLS
  • SignalingLLS, SLS, BALD, BAMT, PRRD
  • Applicationapps, catalog, AoP, media
  • AlertAEA, AEAT, wake-up

Every term across this guide is color-coded by this key — in both figures and tables.

Part 2 · Broadcast

From the file leaving the encoder to the radiated wave, and the reverse path inside the receiver. This is the part that changes least for application authors and most for broadcast engineers: the TV multiplex has become a network.

2.1 Physical layer: three tools

NBR 25601 spans seven pages and cites a single normative reference, ATSC A/322. It adopts ATSC 3.0 and names the three tools Brazil specifically chose to combine: MIMO and LDM to maximize spectral and energy efficiency, and TxID to enable geographic targeting of content and emergency alerts. Everything else — OFDM, guard intervals, pilot patterns — lives in A/322, not in the Brazilian standard.

FIGURE 3 NBR 25601

The three physical layer tools

Three continuous-motion mini-figures — here the loop is the message: the carrier never stops. The electric field is drawn as vectors along propagation; horizontal polarization is shown in perspective, vertical upright.

Scroll horizontally to view the full figure.

MIMOlayered MIMOTxID NBR 25601, 3.1NBR 25601, 3.2.1 and 3.2.2NBR 25601, 3.5 · 25602, 8.3 PLP HV The opposite is SISO: one path, one antenna. Here, one PLP feeds two. power CoreEnhanced LDM HV SISO WGS 84 polygon · ≥ 4 coordinate pairs 1st txId · H2nd txId · V 13 bits · 0 to 8191 · example values
  • MIMO

    A PLP configured to create two signal paths feeding a pair of cross-polarized antennas — one horizontal, one vertical. The opposite is SISO.

  • layered MIMO

    MIMO and LDM active simultaneously. Type A: MIMO applied to both Core and Enhanced layers. Type B: MIMO on Enhanced only, with Core in SISO.

  • TxID

    txid_address is a 13-bit identifier, unique per transmitter on a given RF channel, from 0 to 8191. In MIMO there may be one per polarization: the first txId is horizontal, the second vertical. TBSAT maps each to a WGS 84 polygon of at least four coordinate pairs where that transmitter is the best server.

  • Left to national regulation

    Operating band from 44 MHz to 960 MHz in 6, 7, or 8 MHz channels; frequency offset, carrier stability, and spectrum mask are defined by each country — in Brazil, by Anatel.

  • What the application sees

    A Broadcaster Application queries physical layer parameters through TV 3.0 WebServices. The robustness of the chosen PLP determines whether the application package arrives intact, and how quickly.

  • PLP, the service unit

    A signal can carry up to 64 PLPs, but a single service uses at most four. With LDM, Core-layer PLPs consume receiver PLP processors to decode Enhanced layers, even when they do not belong to the tuned service.

2.2 From file to air

Five stages, and at each one the payload changes shape. The key lab takeaway: the test suite PCAP is captured at the scheduler output, in ATSC A/324 STLTP format — before the modulator. That is why a TV 3.0 test artifact is a PCAP rather than a Transport Stream.

FIGURE 2 NBR 25601, Annex A

Broadcast transmission chain

Above, the equipment room with the signal flowing across racks; below, the microscope: the internal structure of what passes through the active stage. The test suite PCAP taps off the scheduler — not the modulator.

Scroll horizontally to view the full figure.

EQUIPMENT ROOM ROUTE STLTP RF PCAP NTP videoaudioapps · AEA ROUTE · ALP PLP · ModCod Bootstrap · TxID PA GPS SourcesMultiplexerSchedulerModulatorAmplifier & antenna HV INSIDE THE STAGE Sources videoaudiocaptionsLibrasappsAEA DASH segmentDASH segmentIMSC1 · WebVTTvideo · gloss · motion NBR 25608 packages AEA-MF NBR 25607 messages sameentrypoint ROUTE session LCT · videoLCT · audioLCT · app Data and signaling become objects, one LCT channel per component. one ALP packet ALPIPUDPROUTE — ALC/LCTobject · TOI LMT · Link Mapping Table PLPIDIP addressport 0……1…… which IP flowrides in whichPLP PLP 0PLP 1 ModCodModCod multiplexinglayered MIMO TDMFDMLDMtype Atype B Either TDM, FDM, or LDM — with layered MIMO type A or B. STLTP · ATSC A/324 PCAP · test suite recorded here, before the modulator A/321A/322 BootstrapPreamblePLP 0 · CorePLP 0 · EnhancedPLP 1 · CorePLP 1 · Enhanced TxID NTP · timeGPS · frequency encoder, mux, scheduler, and modulatormodulator only HV In MIMO, a pair of cross-polarized antennas. txid_address 17txid_address 18txid_address 19txid_address 20 SFN · best-server polygons in TBSAT

.

NBR 25601, Annex A, Figures A.1 and A.2
  • Synchronization is mandatory

    Encoder, multiplexer, scheduler, and modulator must be synchronized in time (e.g., via NTP), and the modulator also in frequency (e.g., via GPS). Without it, an SFN cannot hold together.

  • Where each protocol enters

    The ROUTE session originates at the multiplexer per NBR 25602. The ALP link layer and LMT come from ATSC A/330; STLTP from A/324; Bootstrap from A/321; TxID from A/322.

  • SFN and geolocation

    Every transmitter broadcasts its txid_address — 13 bits, 0 to 8191. TBSAT binds each one to a WGS 84 best-server polygon, giving receivers location directly from the RF signal without GPS or internet.

2.3 Transport: everything is IP

The core transport technology is ATSC A/331 ROUTE/DASH. Over the air travels ROUTE; over broadband, DASH or HLS. A single service can split components across both paths, and the receiver stitches them together. TV 3.0's most decisive move here was pruning options.

What was pruned from ATSC

  • MMT/MMTP cannot be used. Every reference to it in A/331 is disregarded — there is a single OTA transport path.
  • No table digital signatures, in either LLS or SLS. SignedMultiTable is excluded.
  • EME/CENC on broadband only. The DRM Data Service Type is not used in broadcast configurations.
  • No XLink for content replacement or ad insertion; Alternative MPD mechanisms are used instead.
  • Fast Service Scan only. Full-Service Scan is not used.

25602, 6.2, 8.1, 9.2, and Annexes A and B

The four remaining Service Types

Code Service Type
30 Service Based on Bootstrap Application — the primary TV 3.0 service
31 Additional Linear A/V — exists only bound to a Type 30 service
32 Additional Linear Audio-Only — likewise
4 ESG — associated exclusively with Type 30

Types 1, 2, and 3 from A/331 were excluded. The third octet of a service's multicast IP derives from center frequency divided by channel bandwidth; majorChannelNo and minorChannelNo apply only to Type 30. 25602, 8.1

2.4 Encapsulation, layer by layer

The same DASH segment steps down gaining one wrapper per layer at the broadcaster and steps back up shedding all of them inside the receiver. Over-the-air delivery has no return channel — hence the need for FEC and repetition, which reappears in Part 4 as the NRT carousel.

FIGURE 4 NBR 25602 and 25601

Encapsulation and decapsulation

A DASH segment steps down gaining one header per layer and climbs back up in the receiver shedding them all. From IP downward, TV broadcasting is indistinguishable from a data network — with one catch: there is no return path.

Scroll horizontally to view the full figure.

OTT · HTTP · TCP — EME/CENC permitted here only DASH segmentISOBMFF ROUTE — ALC/LCT UDP IP ALP + LMT physical layer player BROADCASTER · STEPS DOWN ADDING HEADERS RECEIVER · CLIMBS UP SHEDDING ALL

.

NBR 25602, Annex B · NBR 25601, 4

2.5 Headend and test assets

A PCAP is a frozen scenario — signaling, media, and applications, deterministically reproducible. It lets a manufacturer rerun a conformance test months later and get the exact same result.

  • PCAP, not TS

    The suite captures the STLTP stream handed from scheduler to modulator. Identifiers follow ST3_<F|C>_PCAP_XXX for TV 3.0 and ST3_<F|C>_TS_XXX for TV 2.X.

  • XMLs remain standalone artifacts

    The source XMLs that built the PCAP remain individually identified and versioned: ST3_BALD_XXX, ST3_BAMT_XXX, ST3_PRRD_XXX, ST3_AEAT_XXX, plus the three ESG XMLs — service, schedule, and content.

  • Media classes

    ST3_AUDIO, ST3_VIDEO, ST3_SUBTITLE, ST3_IMAGE, ST3_TEXT, ST3_FONT, ST3_MMEDIA, and ST3_HSTREAM — the latter being packaged adaptive streaming (DASH or HLS manifest plus segments).

  • Operational pitfalls

    The BALD validity window must cover the actual test execution date. Swapping PCAPs live at the modulator is how DESTROY, KILL, and PRRD updates are tested. In broadband mode, the package must be reachable at the declared URL.

Part 3 · Signaling

Everything the receiver needs to know arrives in XML across two tiers. LLS applies to the entire RF channel, uses a fixed multicast IP address and port, and is read first — with zero prior discovery. SLS describes one service at a time and is pointed to by the SLT. In TV 3.0, neither uses table digital signatures.

3.1 LLS and SLS, table by table

Eight tables in LLS, ten fragments in SLS. The biggest mental shift coming from TV 2.X: an application never parses transport — it requests pre-parsed XML from TV 3.0 WebServices. Signaling is a programmable API surface, not just internal receiver plumbing.

Low-Level Signaling

Service Layer Signaling

LLS_table_id values per Table 2 of NBR 25602. CDT comes from ATSC A/360 and is absent from that table. RSAT appears as optional in Tables A.1 and A.2 of NBR 25602.

3.2 Service discovery: Fast Service Scan

Eleven steps from the first RF lock to the stored channel map. Four parsers work in parallel, and the SLT parser outputs what is essential to build the Application Catalog — the broadcaster grid presented to the viewer once scanning finishes. Full-Service Scan is not used in TV 3.0.

FIGURE 7 NBR 25602, 9.1 and 9.2

Fast Service Scan

Above, the tuner sweeping the predefined frequency list. Below, the sequence diagram from the standard: from Preamble L1 signaling to the Application Catalog and channel map. Full-Service Scan is not used in TV 3.0.

Scroll horizontally to view the full figure.

PREDEFINED FREQUENCY LIST 44 MHz960 MHz tunerbasebandmiddleware Application Catalog LMTBAMT0x90TBSAT0x91SLT0x01 signal detected Preamble L1 PLP with Link LayerSignaling & LLS dispatches to functional modules PLPIDIPaddressport manifests areas services essential stored in channel map channel map Full-Service Scan: not used in TV 3.0

.

NBR 25602, 9.1 and 9.2, Figure 7 · Table 2

3.3 Service guide: ESG, EPG, and ECG

The service guide data model follows ATSC A/332, with Brazilian extensions in Annex D of NBR 25602. Delivered in SGDD and SGDU fragments, it feeds two distinct surfaces on the receiver.

  • EPG — on-air schedule

    Title, schedule, synopsis, genre, and content rating for what is currently airing and coming up next. Selecting an on-air program in the EPG launches the corresponding service's Bootstrap Application. Service Type 4 (ESG) is associated exclusively with Type 30.

  • ECG — on-demand content

    The rich content guide with an intermediate detail view prior to playback. This is where the TV 3.0 extensions come into play.

  • Brazilian extensions

    Inside tv30ContentExtension, two mutually exclusive elements: initialMediaURL, pointing directly to an MPD or M3U8, and broadcasterApplicationDeepLinkURL, opening a Broadcaster Application at a specific deep link. 25602, Annex D, Table D.1

Part 4 · Applications

The heart of TV 3.0. In TV 2.X an interactive application was an optional add-on to a video channel; here, the primary service is an application — Service Type 30 is literally called Service Based on Bootstrap Application. This part covers the five-piece model, the two languages, how packages arrive, what drives the lifecycle, and what APIs the platform exposes.

4.1 The model: five pieces

Keep one replacement chain in mind before diving into details: channel scan → Application Catalog → Bootstrap Application → Broadcaster Application → another Broadcaster Application. Across every handoff, audio and video must never glitch.

  • Application Catalog

    The broadcaster launcher grid built during channel scan from SLT and BAMT. Shown in exclusive full screen, reachable from the manufacturer platform's input-list function, and providing entry points to EPG and ECG.

  • Bootstrap Application

    The broadcaster's default app, declared in the BAM manifest inside BAMT. It launches upon entering a Type 30 service and serves as the failsafe fallback whenever a Broadcaster Application exits or fails.

  • Broadcaster Application

    The interactive application controlled by the broadcaster via BALD. It replaces the Bootstrap Application and can in turn be replaced by another Broadcaster Application.

  • Persistent Media Player

    Guarantees continuous, uninterrupted playback of the broadcaster's audiovisual stream, including across transitions between applications within the same service context. Continuity is a normative requirement, not a nice-to-have.

  • Access Panel

    The viewer's drawer: available applications, accessibility preferences, and the Privacy Manager. Applications signaled with PRESENT wait here until opened by the viewer.

4.2 Two languages, one lifecycle

BALD's @appType, formatted as TV30-Ginga-…, tells the receiver which presentation engine to invoke. Everything else — validity windows, caching, control codes, platform APIs — is identical across both.

  • TV 3.0 Ginga-NCL

    NCL 4.0 with NCLua. Declarative media synchronization model with live editing commands, private base, and persistent variables. Natural path for SBTVD veterans and tightly timed audiovisual experiences.

  • TV 3.0 Ginga-HTML5

    Packaged HTML5, CSS, and JavaScript. Natural path for web teams, reusing standard front-end skills and tooling. Platform APIs are identical, exposed over local REST.

  • What stays the same

    The Application Lifecycle Manager is language-agnostic: it reads BALD, applies @controlCode, enforces @validFrom and @validUntil, and manages cache entries keyed by @appContextId.

4.3 How the application arrives

There is no on-demand download over the air. The application package is sliced into objects, each tagged with a TOI, and broadcast repeatedly in a non-real-time carousel over ROUTE. Tuning in mid-rotation means waiting for the next pass to complete the set — an acquisition latency every developer must design around. Alternatively, via a broadband entry point, the exact same package is fetched over HTTP.

FIGURE 5 NBR 25608

How the application reaches the receiver

On the left, the mechanism: the NRT carousel spinning beneath the receiver's read head. On the right, the same timeline lane by lane. Tuning in mid-cycle means finishing the package at the same point on the next rotation.

123456789101112 NRT carousel ROUTE receiver
tune-in ray 1st BALD ray cache 0/12 arc: remaining

Scroll horizontally to view the timeline.

ROUTE · NRT objects by TOI SLS · BALD cache @appContextId broadband HTTP receiver audiovisual 12/120 cycle ncycle n+1cycle n+2 123456 789 101112 123456789 101112 123456789101112 BALDBALDBALDBALDBALDBALDBALDBALDBALD GET @bbandEntryPointUrl Bootstrap Application Broadcaster Application · AUTOSTART Persistent Media Player · seamless tune-in 1st BALD complete package ready via broadband OTA acquisition latency ≈ wait for BALD + one full cycle 7, 8, and 9 passed before 1st BALD

.

NBR 25608, 10.1 and A.3.22 · NBR 25602, 4

BALD attributes

Broadcaster Application Location Description — the SLS fragment that declares each application, replacing ATSC's HELD. Without it, cached files remain inert data rather than an application.

Attribute What it declares
@appId Application identifier
@appType Presentation language, using TV30-Ginga-… values
@bcastEntryPointUrl Broadcast entry point — package delivered via NRT carousel over ROUTE
@bbandEntryPointUrl Broadband entry point — the same package over HTTP
@appContextId Identifies the Application Context Cache where files accumulate
@controlCode What to do with the application right now. If omitted, defaults to AUTOSTART
@validFrom · @validUntil Validity window. During testing, must cover the actual execution date
@clearAppContextCacheDate Invalidates the cache starting from a given date

25608, 10.1 and A.3.22 · mandatory in Type 30 services whenever an application is present, per Tables A.1 and A.2 of NBR 25602

4.4 Lifecycle: who is in charge

BALD is the broadcaster's remote control over the application. Seven control codes, two of which persist the package in receiver non-volatile memory and one of which purges it. Try the simulator below: fire a control code and watch the state machine and TV screen respond.

FIGURE 6 NBR 25608, 10.1

Application lifecycle

The state machine and TV screen act as one: each @controlCode arriving in BALD lights an edge, transitions the state, and updates what the viewer sees. Below, BALD repeated over time — lifecycle is signaling-driven, not one-shot event-driven.

Scroll horizontally to view the full figure.

AUTOSTARTSTORED_AUTOSTART DESTROYKILL PRESENT STORED_AUTOSTARTSTORED_PRESENT STORED_REMOVE viewer Application Catalog Bootstrap Applicationrunning Broadcaster Applicationrunning available, not startedwaiting in Access Panel non-volatile memory Bootstrap Application Broadcaster Application shutting down… immediate kill Access Panelavailable REPEATED BALD · @controlCode

.

NBR 25608, 10.1 and A.3.22
Code Effect Storage
AUTOSTART Downloads and launches immediately upon receipt, replacing Bootstrap —
PRESENT Remains available without launching; appears in Access Panel awaiting the viewer —
STORED_AUTOSTART Like AUTOSTART, and subsequent launches run from persistent storage writes
STORED_PRESENT Downloaded and persisted in storage, without launching automatically writes
STORED_REMOVE Purges from storage; does not affect a running instance deletes
DESTROY Controlled shutdown: cleans up, frees resources, falls back to Bootstrap —
KILL Immediate termination without cleanup; nothing is saved by the app —

25608, 10.1 · roughly analogous to TV 2.X's AIT, but with explicit persistence and cache semantics

4.5 TV 3.0 WebServices: the API surface

A local REST API specified in Annex C of NBR 25608 and detailed in NBR 15606-11. Rule of thumb: nearly everything an application needs to know about the outside world arrives through these endpoints, never via raw stream parsing. That is what makes the application layer testable largely in isolation from broadcast transport.

  • Signaling and guide

    Any LLS table or SLS fragment, pre-parsed. Service guide for the tuned channel and others. Subscription-based event notifications.

  • Emergency alerting

    AEAT notification subscriptions, with showEmergencyAlert controlling whether the application takes over alert rendering in place of the native UI.

  • Platform

    Receiver platform capabilities and attributes, including PRP version and AoP implementation version; physical layer parameters; geolocation, with tbsat alongside gnss, wifi, mobileNetwork, zip, and ip.

  • State and persistence

    Application Context Cache, persistent storage, and viewer profile attributes — the latter gated by consent declared in the PRRD.

  • Media

    Persistent Media Player control, track selection, and urn:sbtvd:dash:component-tag for controlling the same stream across different MPD Periods.

  • Beyond the screen

    Audience measurement, multimodal interaction, remote devices and companion apps, sensory effects, and 360° content.

4.6 Middleware: where your app runs

The Receiver Platform (RP) has two halves. The AoP is standardized and your application can rely on every piece of it. The PRP — Proprietary Receiver Platform, not Primary — belongs to the manufacturer: home screen, system menus, tuner hardware. You only reach the PRP through the capabilities and attributes exposed via WebServices. Click any component below.

TV 3.0 AoP · APPLICATION-ORIENTED PLATFORM
PRP · PROPRIETARY RECEIVER PLATFORM
RF

Up to 64 PLPs in the RF signal, at most four per service — hence the recommendation of four PLP processors in the receiver.

4.7 Receivers and profiles

Three receiver classes and nine profiles. Manufacturers certify against a profile, which defines what baseline capabilities your application can assume on the device.

  • BDR

    Built-in display receiver: integrated screen, no video output. TV sets, portable receivers, and in-vehicle displays.

  • STB

    Set-top box: requires an external display, providing audio and video output interfaces.

  • GTW

    Gateway: receives TV 3.0 over the air and serves it over Wi-Fi to client devices via a streaming companion app.

  • Nine profiles

    Each receiver class in three tiers: 4K@60fps, 4K@120fps, and 8K@60fps, defined in Annexes A through I of NBR 25609.

  • Required decoding

    Video: VVC, HEVC, AVC, LCEVC. HDR: HDR10, SL-HDR1, SL-HDR2, HLG, SMPTE ST 2094-10 and 2094-40. Volumetric: V3C. Audio: MPEG-H, AAC, AC-4, E-AC-3 JOC. Captions: IMSC1 and WebVTT.

  • The 5 s restart budget

    If Bootstrap, L1-Basic, or L1-Detail changes, the receiver must resume demodulation within 5 s — with explicit exceptions including ea_wake_up_1 and ea_wake_up_2, which must never trigger a restart. Without that exception, emergency wake-up would fail.

  • Also in NBR 25609

    The receiver standard mandates TV 3.0 Ginga-NCL, Ginga-HTML5, WebServices, and NCLua in Section 13, alongside RF reception, sensitivity, and selectivity in Section 15.

Part 5 · Cross-cutting services

Three domains that cut across every layer and that, in TV 2.X, either did not exist or were bolted on externally: emergency alerting, accessibility, and personal data protection. In all three, applications play an active — and accountable — role.

5.1 Emergency alerting

Public authorities publish in CAP; the broadcaster converts to AEA-MF and transmits in AEAT inside the LLS. Even if the receiver is in standby, the wake-up bits in the Bootstrap wake it up. And the UI ultimately rendering the alert on screen can be your application.

FIGURE 8 NBR 25607

Emergency alerting

The alert leaves public authorities as CAP, becomes AEA-MF inside AEAT, and wakes a sleeping receiver — but only one whose location, derived directly from TBSAT, falls inside the alert polygon.

Scroll horizontally to view the full figure.

ORIGINBROADCASTERTRANSMISSION CAP authorities XML · CAP CAP → AEA-MF AEAT · LLS + wake-up rich media via NRT signaling module ROUTE COVERAGE AREA · TBSAT Location@type polygon txid_address 17txid_address 18txid_address 19txid_address 20 outside area this receiver AEA-MF Met via TBSAT native app Broadcaster Application standby · tuner monitoring RF signal showEmergencyAlert = true native UI suppressed; events still delivered wake-up

.

NBR 25607, Annex A and Table A.1 · NBR 25602, 8.3
  • Twelve CAP categories

    Geo Met Safety Security Rescue Fire Health Env Transport Infra CBRNE Other

  • Where the alert applies

    AEA.Header.Location@type accepts ZIP_BR (8-digit Brazilian postal code), polygon, and circle. Receiver location can come straight from TBSAT over the air, with no GPS and no internet.

  • When no tuner is free

    Monitoring prioritizes OTA. If no tuner is available, the receiver falls back to the OTT URL declared in BAM's emergencyWarningTransmission tag (@ota and @url).

  • Monitoring rules

    Broadcasters declare alert transmission in BAM's emergencyWarningTransmission tag (@ota and @url). OTA takes priority; without a free tuner, OTT is used. Wake-up triggers when AEA@wakeup is true or when a CAP alert carries maximum-equivalent priority.

  • Who renders the alert

    An application subscribes to event notifications via WebServices and sets showEmergencyAlert to true: it takes over rendering and the native UI stays silent, while events continue arriving regardless.

  • When not to display

    If an OSN carries KeepScreenClear associated with the active service, the receiver must not display the alert overlay. Broadcasters should avoid signaling KeepScreenClear during an active alert unless the same information is already burned into the video.

5.2 Accessibility

Four accessibility features across three standards, bound by a single thread: all of them are viewer preferences stored in the user profile and queryable by applications. They are not optional receiver chrome — your application must honor them and, during emergency alerts, actively trigger them.

  • Captions

    IMSC1 and WebVTT. Over HLS, MPEG-2 TS, Packed Audio, and IMSC Subtitles are prohibited — only fragmented MP4 and WebVTT are permitted. 25605 · 25602, Annex C

  • Closed signing

    Viewer-toggleable sign language: Libras video stream, gloss stream, and motion stream. Burned-in sign-language windows are no longer required. 25606

  • Audio description and dialogue enhancement

    Selectable audio components inside MPEG-H. The receiver's native MPEG-H audio management UI may be disabled while an application controls presentation. 25604

  • Mandatory in emergency alerts

    When lang is a recognized gloss code such as bzs, alert content must be rendered in Libras per Annex B of NBR 25606. For pt-BR at maximum priority, text must be spoken via speech synthesis — after any alert audio or video finishes playing. 25607, Table A.1

The baseline viewer profile attributes are precisely these five: audio language, captions, closed signing, audio description, and dialogue enhancement.

5.3 Privacy and personal data

PRRD — Privacy Record Request Description — is the SLS fragment where a broadcaster declares, purpose by purpose, which data it requests and on what legal basis. Without explicit consent to the PRRD, an application cannot touch profile attributes or personal data. The model was designed specifically for Brazil's LGPD.

  • 01 First entry

    Upon entering a service for the first time, consent is requested with PRRD details clearly shown — prior to any data processing.

  • 02 Refusal

    If declined, data access does not proceed. The application must degrade gracefully and the receiver must remain stable.

  • 03 Update

    A new PRRD requires fresh consent. Until granted, prior consent rules — and blocks — remain in force.

  • 04 Record

    Consent decisions are stored per broadcaster and can be reviewed or revoked by the viewer in the Privacy Manager.

  • Audience measurement

    A specific instance of the same consent model: collection is delegated to the AoP upon request under the dpv:ServiceUsageAnalytics purpose declared in the PRRD, configured via BAM.

  • For test engineers

    The precondition is almost always no prior consent. Two PCAPs carrying distinct PRRDs exercise the update flow (test suite group ST3_F_G_008).

  • Further reading

    The standards reference the SBTVD Forum's Data Access and Privacy Guide and Usability Guide, which detail expected consent UI behavior.

Cheat sheet originally authored by Carlos Eduardo Coelho Batista (UFPB), built upon ABNT NBR 25601, 25602, 25607, 25608, and 25609:2025, alongside normative references ATSC A/321, A/322, A/324, A/330, A/331, A/332, and A/360, ISO/IEC 23009-1, IETF RFC 8216 and 1952, ITU-T X.1303 bis, and ABNT NBR 15606-11.

ABNT standards are copyrighted documents: this guide cites clauses, terms, and identifiers without reproducing normative text. In case of discrepancy, the published standard prevails; in interpreting English translations of the Brazilian standards, the original Portuguese text governs.