Integrated Broadcast-Broadband Systems
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
IDC MUX-5012I
Flexible multiplexer for broadcast applications Fully Compliant with ISDB-T and ISDB-Tb Description Easy to use PSI/SI rebuilding, editing and gener- International Datacasting’s MUX-5012i is an extremely There is a complete set of backlit alphanumeric full- ating feature rich ISDB-T/ISDB-Tb transport stream multiplex- travel buttons on the front panel for easy configuration, Descriptor data inserting er. Up to 12 ASI inputs can be supported. The output even in the dark. The large LCD display is illuminated, yet provides high contrast for visibility in direct sunlight. Accurate PCR adjusting may be configured as two separate multiplex groups to simplify feeding different service providers with differ- Control may be via the simple front panel interface or SFN support, supporting hierarchy ent groups of services. via the integrated web browser controlled software transmission interface. Up to twelve (12) ASI inputs Ideal for converting your transport to ISDB-T per unit TSM5012i multiplexer is a TS re-multiplexer that is de- Reliable and affordable Two (2) separate TS re-multiplexed signed for ISDB-T and ISDB-Tb Digital Terrestrial Televi- The MUX-5012i multiplexer provides an industry-leading ASI outputs per unit sion broadcast video distribution. The TSM5012i sup- set of features in a highly compact, highly affordable PID Remapping ports 2 separate multiplexers which are fully complying package. The unit is designed for demanding 24 / 7 Support input 188/204 byte TS with ISDB-T/ISDB-Tb standard. This multiplexer can environments for years of reliable operation. packet transfer the head-end SPTS and MPTS to ISDB-T stand- Support IIP packet editing and gen- ard TS as required . -
PBS Engineering Technology Advisory Committee ATSC 3.0 Position Paper
PBS Engineering Technology Advisory Committee ATSC 3.0 Position Paper Introduction The PBS Engineering Technical Advisory Committee (ETAC)* has created a working group focused on the pending ATSC 3.0 broadcast transmission standard and its impact on PBS member stations. The ETAC ATSC 3.0 Working Group is made up of Public Television station technology leaders with support from PBS. The current digital broadcast technology was developed in the early 1990s by a large group of industry professionals with overall leadership from the FCC Advisory Committee on Advanced Television Service and the Advanced Television Systems Committee (ATSC).* The standard was published in 1995 and then adopted by the FCC in 1996. In July of 1996, WRAL TV in Raleigh, NC became the first North American television station to broadcast a digital service. In time, the standard we now refer to as ATSC 1.0 was introduced across the country. With the demise of analog television broadcast, it became the operating standard in 2009. ATSC 2.0 was an enhancement of ATSC 1.0, adding new technologies such as advanced video and audio coding and new features such as second screen and Conditional Access. While ATSC 2.0 did become a standard, it was not widely adopted. Many of the capabilities 2.0 enabled, however, were used and expanded on in ATSC 3.0. Technology changes rapidly and the need for an advanced broadcast standard not hampered by the backwards compatibility restraints of ATSC 1.0 is clear. Given consumers’ rapid adoption of mobile and handheld devices for video consumption, it is clear that broadcasters need to adapt to meet current consumer demands and ensure scalability for future needs. -
Tr 126 907 V14.0.0 (2017-04)
ETSI TR 126 907 V14.0.0 (2017-04) TECHNICAL REPORT Universal Mobile Telecommunications System (UMTS); LTE; HTML5 for a new presentation layer in 3GPP services (3GPP TR 26.907 version 14.0.0 Release 14) 3GPP TR 26.907 version 14.0.0 Release 14 1 ETSI TR 126 907 V14.0.0 (2017-04) Reference RTR/TSGS-0426907ve00 Keywords LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice The present document can be downloaded from: http://www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https://portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. -
WAVE Interoperability Boot Camp
Thank You to Our Sponsors WAVE Interoperability Boot Camp October 2nd, 2018 Technology & Standards Forum | Los Angeles, CA AGENDA • Introduction to WAVE – Paul Hearty, Sony Electronics • Presentations: • WAVE Technical Overview – Will Law, Akamai • WAVE Content Specification – Mike Bergman, CTA • WAVE Applications Environment – Mark Vickers, Comcast • WAVE Device Playback Capabilities – Mike Bergman, CTA • WAVE Test Suites – Mike Bergman, CTA • Q&A/Wrap-up – Paul Hearty, Moderator Overview of the WAVE Project Paul Hearty / Sony Electronics, Inc. Introduction to WAVE • What are the problems WAVE is addressing? • What are the WAVE solutions? • WAVE participating companies • WAVE work structure Supporting a fragmented OTT world • Fragmentation impacts content providers and device makers: • Multiple streaming formats (HLS, HDS, DASH, Smooth) • Multiple device types from laptops to phones to gaming consoles • Inconsistent device performance capabilities • Inconsistent device compliance to industry specifications • The result: • Content providers: Increased cost to prepare, store and support OTT • Device makers: Increased test and support costs for devices Commercial OTT Video Issues: WAVE Solution Device Playback Device HTML5 Reference Content Capabilities Platform Content Specification Testable requirements Reference application • Based on MPEG Common • covering most common framework Media Application Format playback interoperability • Based on HTML5 (CMAF) issues. • Provides functional • Compatible with DASH and guidelines for playback HLS. -
Specification for Devices 2020
Certify Devices Specification for Devices 2020 Version: 4.20-r1 Date: 2019-12-19 Specification for Devices 2020, v4.20 © Vewd Software AS 2020. All rights reserved. _____________________________________________________________________________________ CONTENTS 1. REVISION HISTORY 2. INTRODUCTION 2.1. Scope 2.2. Versions for requirements and software 2.2.1. Backward compatibility 2.3. Definitions 2.4. Compliance terminology used in this document 2.4.1. REQUIRED and CONDITIONALLY REQUIRED features 2.4.1.1. DRM 2.4.1.2. Codecs and media formats 2.4.1.3. Keys on the remote control 2.4.1.4. Resolution 3. TECHNICAL REQUIREMENTS 3.1. HTML5 <video> and <audio> 3.1.1. Media element 3.1.1.1. Requirements for video and audio media elements 3.1.1.2. Requirements for video media elements 3.1.1.3. Codec support 3.1.2. Track element 3.1.2.1. Requirements for all track elements 3.1.2.2. Requirements for text track elements 3.2. Media streaming 3.2.1. Transport protocols 3.2.2. Progressive download 3.2.3. Adaptive Bitrate streaming protocols 3.2.3.1. Apple HTTP Live Streaming (HLS) 3.2.3.1.1. Restrictions for HLS content 3.2.3.2. MPEG-DASH 3.2.3.2.1. Restrictions for MPEG-DASH content 3.2.3.3. Microsoft Smooth Streaming (MSSS) 3.2.3.3.1. Restrictions for Smooth Streaming content 3.3. Media Source Extensions (MSE) 3.4. Subtitles and Closed Captioning 3.5. DRM 3.5.1. Content Decryption Modules (CDMs) 3.5.1.1. ClearKey 3.5.1.2. -
Media Source Extensions
static void _f_do_barnacle_install_properties(GObjectClass *gobject_class) { GParamSpec *pspec; Media Source Extensions /* Party code attribute */ pspec = g_param_spec_uint64 (F_DO_BARNACLE_CODE, "Barnacle code.", "Barnacle code", on WebKit using GStreamer 0, G_MAXUINT64, G_MAXUINT64 /* default value */, G_PARAM_READABLE | G_PARAM_WRITABLE | G_PARAM_PRIVATE); g_object_class_install_property (gobject_class, F_DO_BARNACLE_PROP_CODE, Enrique Ocaña González [email protected] Motivation for MSE ● HTML5 video tag: <video src=ºmovie.mp4º type=ºvideo/mp4º /> ● Improvement: Blob URI ● Adaptive streaming and time shift limitations ● Solution: Media Source Extensions (MSE) https://w3c.github.io/media-source/ ● JavaScript can generate and feed video data ● More control on the player state How to use MSE SourceBuffer ● Append API for JavaScript: Data... ● HTMLMediaElement, Blob SourceBuffer ● MediaSource, SourceBuffer MediaSource ● Blob URL {Audio,Video,Text}Track HTMLMediaElement <audio> <video> <video id="video"></video> MediaPlayer <script> var video = document.getElementById(©video©); var ms = new MediaSource(); ms.addEventListener(©sourceopen©, function() { var videoSb = ms.addSourceBuffer(©video/mp4; codecs="avc1.640028"©); var audioSb = ms.addSourceBuffer(©audio/mp4; codecs="mp4a.40.2"©); videoSb.appendData(...); audioSb.appendData(...); }); var blobUrl = URL.createObjectURL(ms); video.src = blobUrl; </script> Design PlatformTimeRanges m_mediaSource m_mediaElement MediaSource SourceBuffer PrivateClient PrivateClient MediaPlayer m_client MediaPlayerClient -
Gearbox II ISDB-Tb 16 Tuners/IP 104Ch
Gearbox II ISDB-Tb 16 Tuners/IP104ch Broadcast Quality, Multichannel, Real Time, Standard or High Definition (up to 1080p), Integrated ISDB-Tb Receiver, and MPEG-2 to H.264 or Optional H.265 Transcoder, Scaler, and Streamer. Based on Embedded Linux®, it Boots Quickly from Flash Drive and Remembers all Settings. Easy to Use GUI Allows Full Config of Each Stream and via SNMP can Report its Status to Remote Network Operations. Will Transcode and Process Multiple Streams up to CPU Limitations. Typical Dedicated Transcodes are up to 104 SD Streams, or 26 1080i/p Streams, or 40 720p60 Streams. Supports RTMP, HTTP, and Live Streaming and Works with Atlas™, Wowza®, and Adobe® Flash® Servers. Supports 50 Simultaneous HLS Users. With Optional Atlas™ Add-on, Supports 1,000 RTMP, ISDB‐Tb DASH, and/or HLS Users Natively. Features Overview Inputs: Simultaneously receives one to 16 ISDB-Tb inputs The Gearbox™ II ISDB-Tb 16 Tuners/IP 104ch is a real time IP input (H.264, MPEG-2, or VC-1): UDP, RTP, RTSP, multichannel streamer, integrated RF receiver, and transcoder designed to HTTP, HTTP Live, RTMP (pushed from Flash server) receive up to sixteen simultaneous ISDB-Tb signals and transform them into IP output protocols: UDP, RTP, RTMP (Open Flash), IP streams that are optimized for streaming. It is designed to be scalable, HTTP, with DLNA support easily adaptable, and field upgradeable to meet the needs of streaming Supports HLS (adaptive) for output to mobile devices service users who are very comfortable with embedded Linux® based appliances. It relies on an Intel® Dual 16 Core CPU for encoding. -
Why ATSC 3.0 in Korea UHD? (1)
ATSC 3.0 base Terrestrial UHD Broadcasting in S. Korea Sung-Ik Park ETRI Contents ❖ ATSC 3.0 base Terrestrial UHD Status in S. Korea ❖ Why ATSC 3.0 in S. Korea? ❖ On-going and planned services in S. Korea – Single Frequency Network (SFN) – Mobile HD – Advanced Emergency Alert (AEA) ❖ Summary ATSC 3.0 base Terrestrial UHD Status in Korea (1) Commercial Launch ATSC 3.0 base terrestrial 4K-UHD broadcasting started in Seoul metro area (May 2017), extended to major cities (Dec. 2017), and will be nationwide by 2021 New frequency bands in 700 MHz were assigned for UHD broadcasting Existing HD (ATSC 1.0) and new UHD services must be simulcasted by 2027, and then the existing HD service will be switched off ATSC 3.0 base Terrestrial UHD Status in Korea (2) Consumer Devices TV, Set-top box, and others (dongle receiver, home gateway) are available in market TV STB Others - Dongle receiver for existing device - Home gateway for WiFi re-distribution ATSC 3.0 base Terrestrial UHD Status in Korea (3) 2018 Winter Olympics (PyeongChang) Successfully demonstrated HD mobile and 4K-UHD in a single RF channel Why ATSC 3.0 in Korea UHD? (1) ATSC 1.0 Developed in 1993 Modern Digital World WiFi 802.11ac 1300 Mbps Smart Phones Computer DOS … Windows 3.1 Cell Phone Analog 2G But, Old-fashioned TV Dial-up Modem VCR - analog 19.2 kbps • First digital broadcasting standard • HD video & 5.1 digital audio • Electronic program guides & caption Revolution in 1993 Why ATSC 3.0 in Korea UHD? (2) Enhanced TV Datacasting Convergence Mobility Navigation Updates Phones Smart -
Video Datacasting
Datacasting: NCAA Deployment in Houston Report First Responders Group July 2016 Intentionally Blank Datacasting: NCAA Deployment in Houston Report HSHQPM-15-X-00122 August 2016 Prepared The First Responders Group Office for: for Interoperability and Compatibility Prepared Johns Hopkins University Applied by: Physics Lab Publication Notice Disclaimer The views and opinions of authors expressed herein do not necessarily reflect those of the U.S. government. Reference herein to any specific commercial products, processes, or services by trade name, trademark, manufacturer, or otherwise does not necessarily constitute or imply its endorsement, recommendation, or favoring by the U.S. government. The information and statements contained herein shall not be used for the purposes of advertising, nor to imply the endorsement or recommendation of the U.S. government. With respect to documentation contained herein, neither the U.S. government nor any of its employees make any warranty, express or implied, including but not limited to the warranties of merchantability and fitness for a particular purpose. Further, neither the U.S. government nor any of its employees assume any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed; nor do they represent that its use would not infringe privately owned rights. Contact Information Please send comments or questions to: [email protected] Intentionally Blank Johns Hopkins University Applied Physics Lab Pilot After Action -
Recommendation Itu-R Bt.1833-2*, **
Recommendation ITU-R BT.1833-2 (08/2012) Broadcasting of multimedia and data applications for mobile reception by handheld receivers BT Series Broadcasting service (television) ii Rec. ITU-R BT.1833-2 Foreword The role of the Radiocommunication Sector is to ensure the rational, equitable, efficient and economical use of the radio-frequency spectrum by all radiocommunication services, including satellite services, and carry out studies without limit of frequency range on the basis of which Recommendations are adopted. The regulatory and policy functions of the Radiocommunication Sector are performed by World and Regional Radiocommunication Conferences and Radiocommunication Assemblies supported by Study Groups. Policy on Intellectual Property Right (IPR) ITU-R policy on IPR is described in the Common Patent Policy for ITU-T/ITU-R/ISO/IEC referenced in Annex 1 of Resolution ITU-R 1. Forms to be used for the submission of patent statements and licensing declarations by patent holders are available from http://www.itu.int/ITU-R/go/patents/en where the Guidelines for Implementation of the Common Patent Policy for ITU-T/ITU-R/ISO/IEC and the ITU-R patent information database can also be found. Series of ITU-R Recommendations (Also available online at http://www.itu.int/publ/R-REC/en) Series Title BO Satellite delivery BR Recording for production, archival and play-out; film for television BS Broadcasting service (sound) BT Broadcasting service (television) F Fixed service M Mobile, radiodetermination, amateur and related satellite services P Radiowave propagation RA Radio astronomy RS Remote sensing systems S Fixed-satellite service SA Space applications and meteorology SF Frequency sharing and coordination between fixed-satellite and fixed service systems SM Spectrum management SNG Satellite news gathering TF Time signals and frequency standards emissions V Vocabulary and related subjects Note: This ITU-R Recommendation was approved in English under the procedure detailed in Resolution ITU-R 1. -
W2: Encoding 2017: Codecs & Packaging for Pcs, Mobile
W2: ENCODING 2017: CODECS & PACKAGING FOR PCS, MOBILE, & OTT/STB/SMART TVS Jan Ozer www.streaminglearningcenter.com [email protected]/ 276-235-8542 @janozer Agenda •Fundamentals •Targeting your platforms •Producing and delivering your streams •Configuring your streams Shameless Plug • All tables from this book • Published 12/16 • Retail - $49.95 – print • PDF - $39.95 • Show special: • $40 • PDF included no extra charge • Limited supply available (only books bought at show) Fundamentals • Compression related • Delivery paradigms • Bitrate control (CBR/VBR) • I-, B-, and P-frames • Choosing a codec • Codecs/container formats Compression-Related Fundamentals • Delivery paradigms: Single vs. Adaptive Bitrate (ABR) • Bitrate control techniques • I-, B- and P-frames Adaptive Streaming • Adaptive streaming • Delivered adaptively based upon playback CPU and • Single input file (live or VOD) connection bandwidth • Encoded to multiple outputs • Technically complex, but optimizes experience across all platforms and connection types Illustration courtesy of www.bitmovin.net Single vs. Adaptive • Single file delivers inferior experience • Very simple to achieve via Gen 1 HTML5 (video tag) and support in mobile • This approach excludes adaptive, DRM, live, and advertising support • Resources: • Webinar: Distributing to Desktops and Mobile Devices via HTML5 (bit.ly/Ozer_MSE_EME) • Video tutorial: Supporting HTML5 with Flash Fallback in Squeeze 9 (bit.ly/squeeze_html5) • Our focus is on adaptive delivery ABR Technology Overview • Two types of systems -
Hbbtv 2.0.3 Explained” Hbbtv Specification Naming
What's new in the HbbTV Specification “HbbTV 2.0.3 Explained” HbbTV Specification Naming Informal Name Formal Name HbbTV 1.0 TS 102 796 V1.1.1 HbbTV 1.5 TS 102 796 V1.2.1 HbbTV 2.0 TS 102 796 V1.3.1 HbbTV 2.0.1 TS 102 796 V1.4.1 HbbTV 2.0.2 TS 102 796 V1.5.1 HbbTV 2.0.3 TS 102 796 V1.6.1 (tbc) ??? ??? HbbTV Association | Copyright © HbbTV 2 3 Elements to HbbTV 2.0.3 • Errata to HbbTV 2.0.1/2 – Fixing bugs in the spec • Updates to existing features – Goal for 2.0.3 was “low hanging fruit” that are easy to specify & test • No big new features – these were deferred to the next iteration – Critical updates already widely supported in practice – One small new feature • Removing unused and replaced features – Cannot keep adding features and never removing anything HbbTV Association | Copyright © HbbTV 3 What are Errata? • Fixes to bugs in the spec • HbbTV publishes >1 document for each errata – May be cosmetic release • Punctuation, cross-references, … – A list of the changes to the specification(s) – Might be language that’s unclear or hard to – A version of the specification(s) with the errata understand integrated & changes tracked – May be ambiguities • All HbbTV errata have an issue number • Something that can genuinely be interpreted in – Issue numbers can be used to cross-reference more than one way between the two documents – May be conflicts & inconsistencies – HbbTV members can use the number to lookup • Statements that actually say different things the discussion in our issue tracking system – Things that are hard or even impossible