Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.



Published on

  • Be the first to comment

  • Be the first to like this


  1. 2. Next Generation IPTV Sebastian Kramer CEO Quative (Kudelski Group Company) Stephen Reeder Product Strategy ANT
  2. 3. Agenda <ul><li>Introduction </li></ul><ul><li>First and Second Generation IPTV Solutions </li></ul><ul><li>Key issues on current generation IPTV solutions </li></ul><ul><li>Evolution towards the third generation of IPTV solutions </li></ul><ul><li>SW client technology options </li></ul><ul><li>Summary </li></ul>
  3. 4. Little History in IPTV Solutions <ul><li>First Generation IPTV Solutions: Started Year 2000 </li></ul><ul><li>Low performance MPEG2 STBs with less <150 MIPs for apps - two client models: </li></ul><ul><ul><li>Native model: presentation and logic programmed specific to STB: </li></ul></ul><ul><ul><ul><li>Colourisation only, No true customisation possible </li></ul></ul></ul><ul><ul><ul><li>Relavely fast UI rendering and response times </li></ul></ul></ul><ul><ul><ul><li>Long STB porting times </li></ul></ul></ul><ul><ul><li>Web client model: HTML presentation layer and logic from server (pull model) </li></ul></ul><ul><ul><ul><li>UI customiation in HTML possible, apps logic not </li></ul></ul></ul><ul><ul><ul><li>Did not scale: less then 5K subs per apps and DB server processor </li></ul></ul></ul><ul><ul><ul><li>Slow UI rendering and response times </li></ul></ul></ul><ul><li>Second Generation IPTV Solutions: Started Year 2002/3 </li></ul><ul><li>Higher performance MPEG2 STBs >300 MIPs for apps – evolution of client models: </li></ul><ul><ul><li>Native Model: Keeping EPG Grid native and extensibility for other applications in HTML </li></ul></ul><ul><ul><ul><li>Custom of native Grid not possible, no seamless client model for other apps </li></ul></ul></ul><ul><ul><ul><li>Long STB porting times </li></ul></ul></ul><ul><ul><li>Web client model: Both local presentation and logic on STB in HTML and Javascript </li></ul></ul><ul><ul><ul><li>Full customisation of presentation layer and local logic possible but not server side data model </li></ul></ul></ul><ul><ul><ul><li>Slow UI rendering and response times </li></ul></ul></ul>
  4. 5. Current Key IPTV Solution Issues <ul><li>Customisability of UI, apps logic, service data model </li></ul><ul><ul><li>Not only look and feel but also bespoke service ergonomy are key for service providers to differentiate their offering: „One size fits all does not work“ </li></ul></ul><ul><ul><ul><li>Successful IPTV deployments like FT, Telefonica, TI, Fastweb, PCCW, CHT all have bespoke base TV apps like EPG, VOD. </li></ul></ul></ul><ul><li>Moving from multiple 10K Subs to multiple 100K Subs requires scalable application headend solutions </li></ul><ul><ul><li>Need to support more then 20K subscribers per server processor </li></ul></ul><ul><ul><li><3$ per subs server HW cost point incl. OS/DB/Web server licenses </li></ul></ul><ul><li>Moving beyond EPG, PVR, VOD with support for synchronised download applications: voting, betting, gaming... („red button services“) </li></ul><ul><ul><li>Requires scheduling capabilities of triggers in the broadcast stream and local application management </li></ul></ul><ul><li>Endorsing standards </li></ul><ul><ul><li>Service discovery: DVB-IPI </li></ul></ul><ul><ul><li>Web client / browser: W3C </li></ul></ul><ul><li>True multi device support </li></ul><ul><ul><li>STB, PC, mobile devices </li></ul></ul>
  5. 6. Service Oriented SW Architecture Principal: Next Generation IPTV Server Side Solution <ul><li>Segment all server functions into „base services“ utilised by specific „application services“ which are changeable via an SDK </li></ul><ul><ul><li>Base services: Authentication, service discovery, purchase, subscribe/un-subscribe... </li></ul></ul><ul><ul><li>Application services: Broadcast TV, VOD, SVOD, PPV, Messaging, Mail, Video Conf... </li></ul></ul><ul><li>Allow the definition of additional/different base services if needed </li></ul><ul><ul><li>Extensible server side data model </li></ul></ul><ul><li>Allow full personalisation of application services </li></ul><ul><ul><li>E.g. Personal channel creation, personal look and feel... </li></ul></ul><ul><li>Detect different type of devices </li></ul><ul><ul><li>Provide device specific services: different type of STBs, Mobiles, PC </li></ul></ul>
  6. 7. Client SW Technologies Pros/Cons (Selection) „ If you could run a native like, graphical rich experience of an EPG in a micro browser on a STB, it provides you the best compromise of portability / customisabilty / performance“ Very Good Good Very Good Good Good Performance (Rendering or Data Fetching) Not Good Not Good Very Good Very Good Very Good Customisation Flexibility & Cost STB Specific Fast (not mature) Fast (not mature) Very Fast Very Fast STB Porting Time x x x Application Logic Low x Native (e.g. C) Medium x Java (opt. JVM Browser Plugin) Very High x Flash Macromedia (opt. Browser Plugin) Medium Javascript ( µ Browser) Medium x HTML/CSS ( µ Browser) CPU/Memory Requirements Application Presentation
  7. 8. IPTV Service Delivery Platform Concept (SDP)
  8. 9. Generic IPTV Solution
  9. 10. Reference Client Software <ul><li>The ANT Galio Client </li></ul><ul><ul><li>TV Application Manager concept: Toolbox for triple play service creation </li></ul></ul><ul><ul><li>Integrated ANT Galio Browser as solid foundation </li></ul></ul><ul><ul><li>Consistent & extensible platform </li></ul></ul><ul><ul><li>Modularization of common functions </li></ul></ul><ul><ul><ul><li>Shared resources & functions </li></ul></ul></ul><ul><ul><ul><li>Fast introduction of new capabilities </li></ul></ul></ul><ul><ul><ul><li>Lightweight applications </li></ul></ul></ul>ANT Solution ANT Galio Client ANT Galio Application Backplane ANT Portability Environment (APE) ANT Galio OTDK Create Debug Profile Optimise ANT Galio Browser <ul><li>Optional plug-in Engines : </li></ul><ul><ul><li>IPTV & DVB </li></ul></ul><ul><ul><li>PVR </li></ul></ul><ul><ul><li>Connected Device Framework Personal Communications </li></ul></ul>… PVR Engine IPTV Engine DVB Engine Connected Device Framework Personal Comms Engine
  10. 11. Enabling Rapid Service Innovation Content Creation Guide “ Writing for TV” Create – Evolve - Innovate Develop Application Use Favourite Editors & Tools Use Windows Build for first pass test “ Dot for dot the same as STB” Deploy on STB, debug from Windows - Code Debugger - View Memory Usage - Structure (DOM) Interrogation - Performance Measurement Debug – Profile - Optimise Extremely Fast Turn-around for true Service Innovation
  11. 12. Summary <ul><li>IPTV industry will move to open SDP based architectures for next generation server side solutions </li></ul><ul><ul><li>Providing SDKs for „bottom up“ application service creation </li></ul></ul><ul><ul><li>Enabling true differentiated multi device support </li></ul></ul><ul><li>Next generation TV browser technologies enable native like graphical rich applications: </li></ul><ul><ul><li>Full customisability with general low cost knowhow base everywhere </li></ul></ul><ul><ul><li>Supporting on target testing and debugging of interactive applications </li></ul></ul><ul><li>IPTV service providers need to keep ownership on „their own“ TV applications </li></ul><ul><ul><li>Not „hand them over“ to vendors providing fixed native client apps with fixed client/server side architectures </li></ul></ul><ul><ul><li>Use lowest cost technologies to create bespoke base and advanced IPTV applications </li></ul></ul><ul><ul><li>Need to move beyond base TV apps and start to focus on true interactive apps </li></ul></ul><ul><li>(See us on Nagravision booth: #SU1976) </li></ul>