• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
T05-FG.IPTV-IL-0042!!MSW-E.doc
 

T05-FG.IPTV-IL-0042!!MSW-E.doc

on

  • 576 views

 

Statistics

Views

Total Views
576
Views on SlideShare
576
Embed Views
0

Actions

Likes
0
Downloads
2
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft Word

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

    T05-FG.IPTV-IL-0042!!MSW-E.doc T05-FG.IPTV-IL-0042!!MSW-E.doc Document Transcript

    • INTERNATIONAL TELECOMMUNICATION UNION FOCUS GROUP ON IPTV TELECOMMUNICATION FG IPTV-IL-0042 STANDARDIZATION SECTOR STUDY PERIOD 2005-2008 English only WG(s): 6 3rd FG IPTV meeting: Mountain View, USA, 22-26 January 2007 INCOMING LIAISON STATEMENT DVB Project (www.dvb.org) Source: Liaison Officer : Mark Jeffrey (mark.jeffrey@microsoft.com) Contact : Bill Foote (bill.foote@sun.com) Title: GEM-IPTV White Paper GEM-IPTV white paper Friday, 12 January 2007 Prepared by: Paul Bristow, Osmosys With assistance from Bill Foote, Sun Microsystems Jon Piesing, Philips Damien Alliez, NDS Please send any feedback to p.bristow@osmosys.tv Attention: This is a document submitted to the work of ITU-T and is intended for use by the participants to the activities of ITU-T's Focus Group on IPTV, and their respective staff and collaborators in their ITU-related work. It is made publicly available for information purposes but shall not be redistributed without the prior written consent of ITU. Copyright on this document is owned by the author, unless otherwise mentioned. This document is not an ITU-T Recommendation, an ITU publication, or part thereof.
    • -2- FG IPTV-IL-0042 What is GEM and why should I care? GEM stands for “Globally Executable MHP” and it specifies the core of Blu-ray’s BD-J, OCAP and MHP. For broadcast, it can best be thought of as the overlap between the MHP and OCAP standards for interactive television. It’s a formally standardised Java-based platform for interactive content and applications. GEM has been standardised by DVB, and adopted by ETSI, the ITU, CableLabs, ARIB, ACAP, and the Blu-ray Disc Association. MHP, OCAP & GEM MHP GEM OCAP The differences between MHP and OCAP essentially come down to the support necessary for the differences in network signalling between the DVB world, and the US cable world. The GEM specification is sufficiently high level, for example talking about services without worrying about exactly how those services are carried, that it makes it very useful for writing iTV or web-2.0 style applications that don’t need to know anything specific about the network it is carried on. The fact that GEM is essentially network independent makes it particularly useful in an IPTV environment.
    • -3- FG IPTV-IL-0042 GEM-IPTV The IPTV profile of GEM is formally a subset of the MHP 1.2 specification which includes IPTV support. MHP, GEM & DVB-IPTV GEM-IPTV MHP-IPTV DVB-IPTV In a little more detail: MHP, GEM & DVB-IPTV GEM-IPTV Mandatory Optional Protocol independent Broadband DVB Content SD&S Guide MHP-IPTV APIs APIs DVB-IPTV Optional Broadband Uses MPEG-2 TS with various AV codecs Content Defines DVB version of RTSP protocol, Guide also DVB Service Discovery & Selection protocols
    • -4- FG IPTV-IL-0042 Existing Networks Where GEM-IPTV scores over its non-standardised competitors is that this standard can be used in a proprietary network either to break the single supplier lock, or to provide a migration path away from the proprietary solution without having to replace huge amounts of back office infrastructure. You can maintain existing deployments of proprietary consumer devices, add GEM-IPTV devices and use GEM-IPTV applications to provide an identical or even better user experience. Because the GEM-IPTV application paradigm is Java-based using local processing, you benefit from enhanced scalability and reduced network loading. GEM-IPTV in an existing network GEM-IPTV RTSP, IGMP & UDP protocol mapping Protocol support for talking to Proprietary IPTV systems e.g. MSTV, OMP, Minerva etc Even better, GEM has DVR APIs available, which can be used to manage either HDD-based or network based storage.
    • -5- FG IPTV-IL-0042 Hybrid devices For hybrid markets, you have the choice. MHP + GEM-IPTV for a combination of satellite, terrestrial or cable + IPTV in a proprietary network Hybrid: MHP + GEM-IPTV MHP GEM-IPTV MHP support for broadcast networks RTSP, IGMP & Any version of MHP UDP protocol mapping DVB Broadcast Network support Protocol support for talking to Proprietary IPTV systems Satellite e.g. MSTV, OMP, Minerva etc or Cable or Terrestrial
    • -6- FG IPTV-IL-0042 MHP + MHP-IPTV for a combination of satellite, terrestrial or cable + IPTV in a fully standardised DVB network Hybrid: MHP + MHP-IPTV MHP GEM-IPTV Optional Broadband Content MHP support for broadcast networks Mandatory Guide DVB RTSP, IGMP & APIs Any version of MHP SD&S APIs UDP protocol mapping To DVB-IPTV DVB Broadcast DVB-IPTV Network support Optional Broadband Uses MPEG-2 TS with various AV codecs Satellite Defines DVB version of RTSP protocol, Content or also DVB Service Discovery & Selection protocols Guide Cable or Terrestrial OCAP + GEM-IPTV for a combination of US Cable plus IPTV Hybrid: OCAP + GEM-IPTV OCAP GEM-IPTV OCAP support for digital cable networks RTSP, IGMP & Any version of OCAP UDP protocol mapping OCAP Cable Network support Protocol support for talking to Proprietary IPTV systems e.g. MSTV, OMP, Minerva etc Cable only
    • -7- FG IPTV-IL-0042 All these are valid combinations.
    • -8- FG IPTV-IL-0042 GEM Applications GEM applications for IPTV can support VOD, nVOD, network DVR, broadcast TV – all the standard IPTV services. In addition, a wealth of GEM applications are available for more traditional iTV applications, such as EPGs, ESGs, email, chat, SMS, enhanced TV, news weather, ticker. These java-based GEM applications can be run directly from standard web servers and can easily support web 2.0 features like RSS feeds, P2P, user-contributed content etc etc. An application is a pure GEM app IF • It doesn’t use any MHP-specific APIs • It doesn’t use any OCAP-specific APIs Such an application will run across • MHP, OCAP,and GEM-IPTV Extending this, not using any broadcast APIs will allow the use of single applications across MHP, OCAP, GEM-IPTV and Blu-ray BD-J. With GEM at the core of Blu-Ray's BD-J specification, interactive features and extras for a movie title originally written for an optical disc can be easily moved to a VOD network via Cable or Broadband.
    • -9- FG IPTV-IL-0042
    • - 10 - FG IPTV-IL-0042 Standardisation Status MHP-IPTV is a part of the MHP 1.2 specification which has been approved by the DVB Technical Module and will be sent to ETSI soon. GEM-IPTV is formally a subset of the MHP 1.2 specification above and will be approved by the DVB Technical module in January (it already has preliminary approval) and sent to ETSI for formal standardisation shortly afterwards. In parallel, it will be submitted to the ITU IPTV Working Group, and to CableLabs in the US. It is certain that GEM-IPTV applications will be binary compatible with MHP-IPTV. It is likely that GEM-IPTV will be chosen by CableLabs for OCAP, and hence GEM-IPTV applications should be binary compatible with OCAP-IPTV, when it exists. Conclusion GEM-IPTV provides a way out of the proprietary confusion that is being created in IPTV, without abandoning investment in head-end infrastructure. You can use standardised applications, in line with the standards being deployed in the digital TV landscape, and have the option of moving to an end-to-end standardised solution whenever you choose. ___________