ATSC 3.0 Field Tests Report, Part 1
It was easier to be distracted by more pixels and ways to manipulate them than to thoroughly investigate the imminent future of local TV.
Commercial and Public TV broadcasting is on track for a future Next Gen TV world, with ongoing ATSC 3.0 test transmissions. What broadcasters do inside the new framework that makes money will be the big news at future NAB Shows.
The most exciting TV action sometimes takes place behind the scenes and the 2019 NAB Show was no exception. There were the obligatory new bells, whistles, dogs and ponies across the exhibit halls that offered better solutions, but only a few displays focused on parts of the plan for the future of local TV broadcasting.
The most impressive picture at the Show was the momentum of the future local TV as it was unveiled during weekend NAB BEIT ATSC 3.0 Track sessions. The format is being framed by ongoing engineering field tests and on-air ATSC 3.0 broadcast experiments to confirm every signal in every pipe performs and responds as expected under real-world conditions, and fixing what doesn't. The future is rehearsing for primetime. Engineers will make it seamless.
ATSC 3.0 and Next Gen TV is not a solution. It is a new TV operating system that enables a better, broader and more personal relationship with each broadcast TV viewer, perhaps as significant as GUIs were to DOS. Think of it as the early days of the ATSC 1.0 DTV bonus of '.2, .3, .4' digital subchannel broadcasting, before anyone figured out how to make more money with them.
Approximately 0.2% of those registered for the 2019 NAB Show attended the ATSC 3.0 Track BEIT sessions. Not that anyone but an experienced broadcast engineer would have understood what was being said. I was among the 0.2% and surveyed the meetings. All were serious broadcast TV engineering leaders and managers, many of distinction, either presenting information or taking notes and photos.
The people presenting ATSC 3.0 Track sessions were the experts on the ground doing the experiments. They shared and explained the results of many technical experiments in progress across the country in an organized quest to perfect the ATSC 3.0 standard and finalize it with all due diligence. That moment will mark the spark that ignited Next Gen TV.
ATSC 3.0 has grown from a blip on the horizon to a coming tsunami of Next Gen TV receivers, likely to sweep the US sometime in 3-4Q 2020. Testing is providing the necessary data to lock-down the format specs and begin mass production of ATSC 3.0 chips and TVs. The CE industry is anxious to make and sell lots of Next Gen TVs as soon as the broadcast industry can ensure perfection.
What's the difference between ATSC 3.0 and Next Gen TV? ATSC 3.0 describes a transmission method and format standard. A Next Gen TV receiver decodes the OTA ATSC 3.0 signal, automatically aggregates the RF data with IP data, synchronizes it when necessary, and seamlessly displays the results.
Confirming the ATSC 3.0 momentum, a unified coalition of local TV station network O&Os, affiliates and public broadcasters announced plans during 2019 NAB Show week to begin the transition to Next Gen TV in the top 40 US TV markets before the end of 2020. The list doesn't include every station the top 40 markets but the participating station owner list is impressive. Most are already involved in experimental ATSC 3.0 testing.
TV engineering managers visiting NAB were looking for answers to the big three ATSC 3.0 questions: What must I budget for and when will I need it? How will my station and group benefit from it? What’s the transition plan in my market? The most important question every broadcast engineer must ask is "What can I do to help make it work?"
Peter Van Peenen of Pearl TV shared a great deal of new information with a technically hungry audience.
ATSC 3.0 Track Sunday Sessions
The ATSC 3.0 Track sessions began at 10:40 with “Practical Implementation and Launch Profiles for ATSC 3.0.” Peter Van Peenen of Pearl TV and Robert Seidel VP, Engineering and Advanced Technology at CBS TV discussed their experiences and learning in the Phoenix tests.
At 11:00 Dennis Wallace and Robert Seidel presented the “Results of Field Tests in Cleveland of ATSC 3.0 Using Layer Division Multiplexing (LDM).” At 11:20 a “Practical Model for ATSC 3.0 SFN Deployment – Lessons from Dallas Trial” was presented by Pete Starke with American Tower and Robert Seidel of CBS. At 11:40, “Implementation and test results for ATSC 3.0 hybrid services at ‘Chicago 3.0’,” was presented by Jean Macher of Harmonic and Robert Seidel of CBS.
At 13: 30, “Networking for ATSC 3.0” was presented by Wayne Pecena, Director of Engineering at KAMU TV-FM, Texas A&M University and Jerry Whittaker of ATSC. A 13:50 session covered “Practical Aspects of ATSC 3.0 Interactive Content Deployment,” presented by Mark Corl Triveni SVP Emergent Technology Development and Jerry Whittaker. At 14:10 was “NextGen Broadcast is OTT Over-The-Air, Converged Broadcast/Broadband Platform” presented by Mark Aitken, VP Advanced Technology and President, One Media, Sinclair Broadcast Group and Jerry Whittaker.
At 14:30 was “The Brave New World of Application TV (Dynamic content replacement techniques and implementations for broadcast, Broadband and Beyond),” presented by Jim DeChant, VP of Technology at News-Press & Gazette Broadcasting. The 15:20 presentation of “Transitioning TV Markets to Next Gen TV is a Team Sport,” was by Skip Pizzi of NAB and Jeff Andrew, Director of Broadcast Communications at Osborn Engineering.
Peter Van Peenen and Robert Seidel provided enough information about the Phoenix Model Market Initiative to fill this entire Part 1 article.
The experimental Lighthouse station demodulates and rebroadcasts OTA signal sources in ATSC 3.0.
Pearl TV Partners Experiment in Phoenix
There are 12 TV stations in the Phoenix market participating in the test model, representing 10 station groups and affiliates of virtually all the major TV networks. Univision's KFPH-CD 3.0 is the Lighthouse Station. It signed on with ATSC 3.0 test signals on 5 April 2018.
The goals of the Phoenix tests are to build an open, collaborative testbed to develop basic ATSC 3.0 TV services, develop an industry framework to support it, and explore and develop additional business opportunities. Participants are also testing audience data & addressable advertising, modern application experiences, MVPD enhanced content integration, content protection and various consumer propositions.
The trials are also to prove the concept of the Lighthouse operational paradigm including spectrum clearing, design a broadcaster application user experience using an application framework, and to create an ATSC 3.0 launch service profile.
Block diagram shows how Phoenix Lighthouse station KFPH-CD 3.0 builds its ATSC 3.0 test broadcast.
In 2Q18, the Phoenix partners set out to validate 3.0 transmission, test prototype receivers, and test signal protection. The goals for 3/4Q18 were to test the broadcast application framework, test content security, viewer focus-group testing and to define receiver requirements. Planned 2019 testing includes content security, precommercial receivers, MVPD integration, and automotive collaboration.
Lessons learned
Equipment implementations are in progress and versioning is still an issue.
Common Media Application Format (CMAF) is being considered to improve splicing (content replacement) and reduce channel change delay. More work is needed to study impact on channel change times by segment length, frame rate, cod/cods used as well as CMAF.
DASH timeline media segments are recommended for content replacement as opposed to indexing. Push in DASH/Route from packager & encapsulator is best for live, linear OTA. Broadband servers will pull.
The concept behind many tests in Phoenix is to identify the common needs of networks, affiliate TV stations, MVPDs and consumers.
Audio features scored high in audience testing and will require implementation care by broadcasters and receiver manufacturers to help with viewer understanding.
Statistical multiplexing is now available with HEVC and has provided more efficient Lighthouse operation.
DRM has been tested and works but requires a complete and thorough infrastructure. Protecting the MPD or parts of the MPD would seem necessary for hiding ad avails.
Use of single box solutions such as virtual machines provide potentially lower costs, better integration of functionality and lower latencies but adds complexity in troubleshooting.
Equipment and receivers are generally still in early prototype and vary in feature support such as all AC/4 features.
The quality of receiver broadcast app cache is still an open question, as is caching multiple broadcaster apps. The availability of conformant test streams are critical to consistent receiver implementations.
Looking Ahead
• Phoenix Pearl TV partners have locked-down their initial launch configurations.
• Signal protection and DRM needs to be finalized and operationalized.
• Preproduction CE receiver implementation and testing will occur later this year.
• A second Lighthouse in Phoenix will be in service later this spring.
• Building a SFN in Phoenix to discover optimal coverage configuration.
• Developing a common application framework and starter UI.
• Developing a beta audience data collection system.
• Consumer marketing branding and messaging with receiver manufacturers.
• MVPD testing to find features that resonate in cable setting.
Part 2 of this report will cover ATSC 3.0 field test data from Chicago, Cleveland, and Dallas, and a discussion on the synchronization and latency of the two ATSC 3.0 paths.
You might also like...
Designing IP Broadcast Systems - The Book
Designing IP Broadcast Systems is another massive body of research driven work - with over 27,000 words in 18 articles, in a free 84 page eBook. It provides extensive insight into the technology and engineering methodology required to create practical IP based broadcast…
Demands On Production With HDR & WCG
The adoption of HDR requires adjustments in workflow that place different requirements on both people and technology, especially when multiple formats are required simultaneously.
If It Ain’t Broke Still Fix It: Part 2 - Security
The old broadcasting adage: ‘if it ain’t broke don’t fix it’ is no longer relevant and potentially highly dangerous, especially when we consider the security implications of not updating software and operating systems.
Standards: Part 21 - The MPEG, AES & Other Containers
Here we discuss how raw essence data needs to be serialized so it can be stored in media container files. We also describe the various media container file formats and their evolution.
NDI For Broadcast: Part 3 – Bridging The Gap
This third and for now, final part of our mini-series exploring NDI and its place in broadcast infrastructure moves on to a trio of tools released with NDI 5.0 which are all aimed at facilitating remote and collaborative workflows; NDI Audio,…