LCA14: LCA14-305: Introduction to LHG
Upcoming SlideShare
Loading in...5
×
 

LCA14: LCA14-305: Introduction to LHG

on

  • 418 views


Resource: LCA14
Name: LCA14-305: Introduction to LHG
Date: 05-03-2014
Speaker: Mark Gregotski

Statistics

Views

Total Views
418
Views on SlideShare
418
Embed Views
0

Actions

Likes
0
Downloads
11
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

LCA14: LCA14-305: Introduction to LHG LCA14: LCA14-305: Introduction to LHG Presentation Transcript

  • Wed 5 March, 11:15am, Mark Gregotski LCA14-305: Introduction to LHG
  • • State of digital home media technologies • Past • Present • Future • Benefits of Open Source software and Standards for the digital home • Motivation to form the Linaro Digital Home Group • LHG mission and goals Outline
  • • Home devices used to view TV content: • Set-top boxes • Services • live, on-demand, DVR • EPG -basic grid guide • simple applications in a “walled garden” environment • content sharing from DVR HDD to set-tops via MoCA • Content delivery • video and data networks - cable (HFC), satellite, telco (DSL, fibre) • Video codec/container • MPEG2 encoded video carried via MPEG Transport Stream Past
  • Basic EPG
  • • Security • Cable Set-tops: Conditional Access (MediaCipher/PowerKey duopoly) • IPTV: Windows DRM • Software • set-tops ran proprietary software with proprietary RTOS - Vrtx; VxWorks; WinCE • OCAP platforms ran Linux with proprietary stacks • new feature releases were very slow, sometimes >1 year Past
  • • Multitude of video capable devices • service provider set-top boxes, OTT IP boxes (Roku, AppleTV, Netgear, etc.), Smart TVs, HDMI ‘sticks’ (chromecast), SlingBox, gaming consoles • smartphones, tablets - powered by ARM Present
  • • Services • TV Everywhere - on anyscreen • cloud-based services for DVR, content lockers • EPGs are feature rich JS/HTML programming guides • Applications: Netflix, Hulu, YouTube, FB, Twitter • content sharing: WiFi, AirPlay, Miracast, etc. • Content delivery • leverage the Internet and Web technologies to deliver video: Over- the-top (OTT) IP, CDN, HTTP/Web delivery • Video codec/container • H264, MPEG2, VP8, Ogg Theora • mp4, fmp4, mkv Present
  • EPG Today
  • On Demand UI
  • • Protocols • Multi-bitrate Adaptive Streaming for OTT: HLS, SS, HDS, DASH • HTTP, DLNA • Security • multiple DRMs: PlayReady, Widevine, Primetime, Verimatrix, etc. • DTCP-IP • ARM TrustZoneTM , Trusted Execution Environment (TEE) • Set-top Software • Cable has moved to open source with Reference Design Kit (RDK) • Linux-based operating systems: Android, RDK • Migration of Android from mobile to PayTV • Proprietary software components replaced by open source components: Qt, WebKit, Chromium, GStreamer, OpenMax, etc. Present
  • • Video formats • 4K Ultra HD, 10-bit, 3840x2160 • new codecs H265 (HEVC), VP9 • Operators continue move to open source • Leverage mobile media frameworks for TV • RDK is expanding global footprint • Security • more stringent security required for the next wave of premium content • Software • HTML5: application framework • extensions for encrypted media and media sources • Chromium browser • Opera, Digia (Qt) moving to Chromium Future
  • • There are many non-interoperable, proprietary media technology elements • Multiplicity of: • video formats • adaptive streaming protocols • software DRM solutions • media frameworks • web browsers • trusted execution environments • There is a need for interoperability and common interfaces to reduce complexity and improve portability Fragmentation still exists
  • • W3C HTML5 • video tags: display video without browser plug-ins • Encrypted Media Extensions: handle HTML playback of protected content • Media Source Extensions: generation of media streams for playback; effective for adaptive streaming video • MPEG Common Encryption (CENC): specifies standard encryption and key handling methods for DRM systems • encrypt media asset once and deliver to many DRM clients • MPEG DASH - consolidate adaptive streaming protocols and manifests • DLNA CVP-2: Secure in home content streaming using HTML5 RUI, HTTP-AD, Authentication on DTCP-IP Key Standards
  • • Benefits of Open Source software are evident • Leverage software work done in the community • Faster time to market and features/fixes added • Greater rate of innovation • Greater diversity of solutions for operators • The move to ARM processors is recognition that ARM led the mobile revolution and this innovation can be leveraged in the home set-top/TV market • lower power requirements • less costly development • best power to performance ratio • ARM & Linux are the best way to future proof-applications Open Source and ARM in the digital home
  • Tablet SoCs & IP STB SoCs Converging High Performance GPU Home Networking (802.11) Content Security (DRM) Dual-Quad Core CPU Video Decode Mobile Tablet Silicon Functions High Performance GPU WAN I/O (DOCSIS, xDSL, PON) Content Security (CA) Dual-Quad Core CPU Video Decode STB Silicon Functions Home Networking (MoCA, 802.11G.Hn) • Key subsystems (CPU, GPU) are common between tablets and STB: • content security - HDCP 1.2 is already implemented • 2014 SoCs with ARM TrustZoneTM • Key benefits of using Tablet SoCs for IP STBs: • substantial choice of devices across multiple form factors and price points • leverage latest in ARM technology, e.g., 64-bit, big.LITTLE, GP GPU, OpenGL ES 3.0, TrustZoneTM
  • • Against the backdrop of all these technological advancements, ARM’s partners want to bring innovation to the home segment • Discussions between a large contingent of ARM partners and Linaro concluded with a recommendation to create a digital home segment group • A separate project kicked off last summer with Linaro, Comcast, and 3 SoC vendors to completely redesign the RDK build process using Yocto Project/Open Embedded - the effort resulted in a vastly improved build system for RDK on IP clients Motivation for the Linaro Digital Home Group
  • • Mission: Accelerate adoption of the ARM architecture in the digital home (entertainment) segment by working collaboratively on core Linux-based software platforms, delivering media via optimized and secure video frameworks. • Goals: • Reduce fragmentation through reference implementations on Android and RDK • Optimize media frameworks: e.g., GStreamer, OpenMax IL • Implement standardized interfaces for greater portability • Content Decryption Module interfaces to DRM systems Linaro Digital Home Group
  • • Deliver Linaro RDK to the ARM platform (IP clients & gateways) • Integrate RDK media framework (RMF) into TrustZoneTM (secure video path and DRM framework) • W3C Encrypted Media Extensions (EME): build a generic Content Decryption Module (CDM) on ARM platforms • Standardize Media Framework on OpenMax IL • Migration from Qt WebKit to Qt WebEngine • Reference implementations of DLNA CVP-2 • Compliant client and server device implementations, integration of DLNA HTML5 Remote User Interface (RUI) LHG Projects
  • • Over the last few months there have been a number of investigations underway in LHG: • 1. Integration of media frameworks with TrustZoneTM • collaborate with Security Working Group • discussions with TEE vendors • Global Platform TEE Client API review • 2. Collaboration with W3C members on EME • architecture of secure Content Decryption Modules • comparison of CDM implementations from Google, Microsoft • investigation of main interfaces: browser interface to DRM; DRM interface to secure module • review of Chromium source code Pepper CDM wrapper LHG Work to Date
  • • 3. Investigation into the Comcast Crypto+ API specification and how it relates to other crypto API specifications. • Collaboration with SWG. • 4. Comparison of merits of Qt5 and Android for UI framework. Also Qt-Android integration approaches. • Looking forward: • Continuation of initial work items listed above + • Standardizing media framework on Open Max • Integration issues with GStreamer (collaboration with Graphics working group) • DLNA CVP-2 reference implementation • HTML5 RUI work done by ARM and CableLabs • compliant CVP-2 implementation for DMS and DMR devices • Migration to Qt WebEngine on RDK • Chromium/Blink LHG Work to Date & near term plans
  • More about Linaro Connect: http://connect.linaro.org More about Linaro: http://www.linaro.org/about/ More about Linaro engineering: http://www.linaro.org/engineering/ Linaro members: www.linaro.org/members