CES 2010 and Mobile DTV: the broadcast standard that arrived and then vanished
In January 2010 free live broadcast television on a phone looked like a solved problem. The standard was finished and the hardware was real. A retrospective on why it went nowhere.
At the start of 2010, receiving free live broadcast television on a phone looked like an engineering problem that had just been solved. The standard was ratified, chipsets existed, manufacturers were showing hardware, and hundreds of American television stations were behind it. Fifteen years later almost nobody watches television that way. The gap between those two sentences is the useful part of the story.
The short version
Mobile DTV was technically sound and commercially stranded. It needed three things to arrive together — transmitters, receivers in phones people already wanted, and a reason to watch — and they never did. By the time the ecosystem was assembled, mobile data had made the problem it solved feel less urgent. Its actual successor is not a mobile service at all: it is ATSC 3.0, which absorbed the same ambitions into the main broadcast standard.
What Mobile DTV actually was
The formal name is ATSC-M/H — Mobile/Handheld — standardised as A/153. The Advanced Television Systems Committee approved it in October 2009, a few months before the CES at which the hardware appeared.
The engineering problem it solved is real and specific. Conventional ATSC 1.0, the digital broadcast standard American stations have used since the late 1990s, is designed for a rooftop antenna that does not move. Its 8-VSB modulation is efficient for a fixed receiver and fragile for a moving one: signals reflect off buildings and arrive at slightly different times, and a receiver in a moving vehicle sees that multipath change continuously.
ATSC-M/H added a more robust, heavily error-protected data stream inside the existing broadcast, in the spare capacity of a station's signal. An ordinary television ignored it. A mobile receiver could lock onto it while moving. Critically, this did not require new spectrum or a second transmitter — a station could add Mobile DTV to what it was already sending.
- ATSC-M/Halso: Mobile DTV, A/153
- An extension to the ATSC 1.0 broadcast standard, approved in 2009, adding a signal robust enough for receivers in motion. Carried inside a station's existing transmission rather than on separate spectrum.
CES 2010: the hardware moment
The Open Mobile Video Coalition — a consortium of broadcasters formed to push free mobile broadcast television — used CES 2010 to show that the standard had become products. Devices on display came from LG, Dell, Samsung and several smaller manufacturers, spanning three categories that tell you how uncertain the form factor still was:
- Phones — prototype handsets with over-the-air tuners built in, including Mobile DTV variants of existing models
- Portable players — dedicated screens such as LG's DP570, a seven-inch portable with a built-in antenna and a DVD player attached
- Chipsets and modules — the components that would let anyone else build the above, with work underway on combining the radio and decoder into a single low-power part
Alongside the hardware, the coalition set out the deployment plan: a consumer trial in Washington, D.C., that year, with a membership that already ran into the hundreds of stations.
This is what made the moment feel settled rather than speculative. A finished standard, shipping silicon, a broadcaster coalition and a named trial city is not a technology demonstration — it is a launch plan.
Why it stalled
The receiver problem
Broadcast only works if receivers exist, and a broadcast receiver is a cost and a compromise in a phone: an extra tuner, an extra antenna, extra power draw. Phones sold with Mobile DTV tuners carried a price premium over otherwise comparable models, and the antenna was frequently something the user had to extend. Reviewers of the era reported reception breaking up when a handset moved — the exact condition the standard was designed for, which meant the practical experience did not always match the engineering claim.
That is a hard sell, because a viewer is being asked to pay more, up front, for a feature whose value depends on coverage they cannot verify in the shop.
The coverage problem
Station rollout was real but thin, and unevenly distributed. Even in large markets a viewer might find only a handful of channels available. A service offering three or four channels competes badly against a phone that can already reach every catch-up service on the internet.
The fragmentation problem
Broadcasters did not present a single front. Two commercial ventures formed around the same underlying standard — one built by a group of major network owners, which launched the Dyle-branded service, and a separate alliance of other station groups. Consumers therefore faced a technology sold under more than one name, with different channel line-ups, requiring specific handsets.
The timing problem
This is the decisive one. Mobile DTV was conceived when mobile data was slow, expensive and metered, and it arrived just as that was changing. Broadcast's genuine structural advantage — that transmitting to a million viewers costs the same as transmitting to one — matters most when the alternative is congested or capped. As mobile networks improved, viewers simply used the internet, and internet delivery came with every service rather than three local channels.
Internet-delivered live local television also appeared as a direct competitor, requiring no special handset and no antenna at all.
| Date | Event |
|---|---|
| October 2009 | ATSC approves the A/153 Mobile DTV standard |
| January 2010 | Mobile DTV devices shown at CES by LG, Dell, Samsung and others; Washington D.C. trial announced |
| 2010 | Consumer showcase trial runs; station rollout begins |
| 2011–2012 | Commercial services launch, including the Dyle-branded service backed by a group of major broadcasters |
| 1 January 2013 | The Open Mobile Video Coalition is folded into the National Association of Broadcasters |
| Mid-2010s | Services wind down; Mobile DTV does not reach scale |
| 2017 onward | ATSC 3.0 is authorised in the United States, carrying mobile reception as a core capability |
What ATSC 3.0 inherited
The clearest way to read Mobile DTV is as a prototype for the argument that produced ATSC 3.0. Nearly every capability bolted onto ATSC 1.0 in 2009 became a native property of the newer standard: robust reception for receivers in motion, efficient modern video coding, and a data layer that can carry more than a linear channel.
The structural difference is that ATSC 3.0 is not an add-on. It is built on an IP transport from the start, which means mobile reception is a configuration of the same system rather than a parallel one — and it means broadcasters are not asked to fund a separate service with its own brand, its own receivers and its own audience.
Whether that is enough is still being decided. The transition has been slow, and the regulatory framework for completing it is being settled now. That current state is covered in ATSC 3.0 and NextGen TV, explained.
What is worth taking from it
- A finished standard is not a product. A/153 was technically competent and still went nowhere, because standards do not ship receivers or fill schedules.
- Broadcast economics need scale to work. The one-to-many cost advantage is real but only pays off above an audience threshold Mobile DTV never crossed.
- Hardware you must choose in advance loses to software you already have. Requiring a specific handset put the decision months before the moment of viewing.
- Being early against a moving competitor is the same as being wrong. Mobile DTV was designed against the mobile networks of 2007, and launched against those of 2012.
The same tension is live today in a different form: broadcast still handles simultaneous mass audiences better than unicast streaming does, which is why live streams run behind broadcast television and why 5G Broadcast keeps being revisited. The problem Mobile DTV was built for did not go away. The answer it offered was simply not one viewers were asked to want.
Why this URL still exists
The original report at this address was linked from the technology press and that link is still live. Keeping the address working preserves it. The replacement is written from scratch, from sources anyone can check — the original report is not reproduced, and the current publication did not write it. See the archive for how preserved addresses are handled.
Sources and further reading
- Advanced Television Systems Committee — A/153: ATSC Mobile DTV Standard, Parts 1–10 · The standard itself, approved October 2009
- Variety — Mobile DTV standard approved · Contemporary reporting on the October 2009 approval
- Communications Daily — Variety of Mobile DTV Devices to Be Showcased at CES · Device line-up and coalition plans at CES 2010
- TV Tech — Screening CES 2010 · Trade coverage of the Mobile DTV hardware shown
- Wikipedia — Open Mobile Video Coalition · Coalition role, early station trials, and its integration into the NAB on 1 January 2013
- Society of Broadcast Engineers — ATSC M/H Mobile DTV: What, Why and How? · Engineering explanation of how the mobile stream sits inside an ATSC 1.0 broadcast
Written by
MobilizedTV Editorial Team
MobilizedTV is written and edited as a single publication rather than by named individual contributors. How we research, source and correct our work is set out in the editorial policy.
Related reading
ATSC 3.0 and NextGen TV, explained
The first American broadcast standard designed around IP rather than a fixed channel. What it actually changes, and why the switchover has taken so long.
WheelsTV, Azuki and the problem of getting video onto phones in 2008
In 2008 a niche video producer could not simply publish to phones — it needed a delivery platform. A look back at that arrangement, and at what happened to both halves of it.
HDR formats explained: HDR10, HDR10+, Dolby Vision and HLG
Four HDR formats, doing the same job in different ways. What separates them is metadata and licensing rather than picture quality — and a television that supports HDR can still show it badly.
