Why IPTV? Interactivity, Technologies and Services Johan Hjelm Ericsson A John Wiley and Sons, Ltd, Publication Why IPTV? Written by people in the know, the Telecoms Explained Series for Telecoms Professionals will • Demystify the jargon of wireless and communication technologies • Provide insight into new and emerging technologies • Explore associated business and management applications • Enable you to get ahead of the game in this fast-moving industry Written in a concise and easy-to-follow format, titles in the series include the following: Convergence: User Expectations, Communications Enablers and Business Opportunities Saxtoft ISBN: 978-0-470-72708-9 Triple Play: Building the Converged Network for IP, VoIP and IPTV Hens & Caballero ISBN: 978-0-470-75367-5 Why IPTV? Interactivity, Technologies and Services Johan Hjelm Ericsson A John Wiley and Sons, Ltd, Publication This edition first published 2008 © 2008 Johan Hjelm Registered office John Wiley & Sons Ltd, The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ, United Kingdom For details of our global editorial offices, for customer services and for information about how to apply for permission to reuse the copyright material in this book please see our website at www.wiley.com The right of the author to be identified as the author of this work has been asserted in accordance with the Copyright, Designs and Patents Act 1988 All rights reserved No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, except as permitted by the UK Copyright, Designs and Patents Act 1988, without the prior permission of the publisher Wiley also publishes its books in a variety of electronic formats Some content that appears in print may not be available in electronic books Designations used by companies to distinguish their products are often claimed as trademarks All brand names and product names used in this book are trade names, service marks, trademarks or registered trademarks of their respective owners The publisher is not associated with any product or vendor mentioned in this book This publication is designed to provide accurate and authoritative information in regard to the subject matter covered It is sold on the understanding that the publisher is not engaged in rendering professional services If professional advice or other expert assistance is required, the services of a competent professional should be sought This book expresses solely the opinion and position of the author It does not necessarily represent the opinion of his past, current, or future employers And the author recognizes that he should know better than trying to tell the complete story of a moving target Library of Congress Cataloging-in-Publication Data Hjelm, Johan Why IPTV? : interactivity, technologies, and services / Johan Hjelm p cm Includes bibliographical references and index ISBN 978-0-470-99805-2 (pbk.) Internet television I Title TK5105.887.H58 2008 384.550285 4678—dc22 2008021444 A catalogue record for this book is available from the British Library ISBN 978-0-470-99805-2 (PB) Set in 10/12pt Optima by Integra Software Services Pvt Ltd Pondicherry, India Printed in Singapore by Fabulous Printers Pte Ltd Contents Acknowledgments ix Preface xi Chapter 1: Chapter 2: Interactive, Personal, IPTV: From TV over Internet and Web TV to Interactive Video Media Introduction to IPTV The Value Chain Business Models and the Value Chain Interactivity in Reality: The British Red Button How IPTV Services Work What is Next for IPTV Users? Shape-Shifting Television: New Media for a New Millennium Project LIVE: Interactive Sports Events Me on TV: Five Minutes of Fame for Everyone with a Mobile Phone IPTV Standards and Solutions Standardization of IPTV The Open ITPV Forum Architecture The ETSI IPTV Standard Applying Standards to IPTV: An Implementation Chapter 3: The Next-Generation Consumer Electronics and Interactive, Personal, IPTV Home Connectivity: Ethernet, WiFi and Beyond Making Home Devices Work Together: UPnP and DLNA What is UPnP? Connecting the Home to the Outside: the Home Router The Set-top Box Meets the Internet Model The Browser in the Set-top Box XML and Style Sheets – Format and Structure for Metadata How does the Multimedia Home Platform Work? 1 13 16 21 23 28 31 33 34 37 42 49 53 55 58 59 66 72 79 80 86 vi Contents Channel Switching Speeding Up Channel Switching IPTV in Japan IPTV in the Mobile Chapter 4: Chapter 5: Chapter 6: Chapter 7: 89 91 92 96 Designing Interactive IPTV Applications Dynamic Creation of Interactive Television Integrating Interaction in the Script Using Profiles to Adapt the Show Design of Interaction Objects How to Handle Colors Generic Interaction Models Designing Menus and Text Testing Interactive Applications Quick and Dirty User Testing Making Mashups in IMS-Controlled Interactive IPTV User-Provided Content 99 101 103 105 107 109 110 113 116 118 119 123 Monetizing IPTV: Advertising and Interaction An IPTV Toolbox for Advertisers The IPTV Advertising Design Project Splicing Advertising into the Media – Or Putting it in the IPTV Set? Inserting Advertising 127 134 137 P2P, TV on the Web, VoD and (n)PVR Getting Paid for VoD: Advertising Getting Paid for VoD: Charging for the Service User-Provided Content The Network and User-Provided Content Peer-to-Peer Versus Central Server P2P in the European Broadcasting Union and EU 143 148 151 155 156 156 Digital Rights Management and Next-Generation IPTV Exceptions to Copyright Attaching Strings to Copyright Gifts: Creative Commons Legal Constraints on User-Provided Content Digital Rights Management DRM: Simple Philosophy, Complicated Mechanism Standards for DRM Designing Copyright Policy 139 140 159 163 166 168 171 174 175 177 182 Contents Chapter 8: Chapter 9: Identities, Subscriptions, User Profiles and Presence Managing and Federating User Profiles: XDMS and PGM Presence in IMS Presence Data Format, Lists and Profiles The Presence Document Lists in XDMS IPTV Profiles Advertising and Presence Measuring Advertising in IPTV vii 185 187 187 193 193 199 201 204 205 Beyond the EPG – Metadata in Interactive IPTV Recommender Systems, Social Software, Presence and Personalized EPGs Filtering and Personalizing IPTV Content Metadata Types and Models IPTC News Codes, NewsML and SportsML Dublin Core P/Meta SMPTE Metadata Dictionary, MXF and UMID Metadata and the EPG: TV-Anytime TV-Anytime Document Structure Identifying the Data: the CRID Metadata for Production: MPEG-7 and MPEG-4 Drawing Conclusions from Metadata 211 Chapter 10: Protocols for Interaction The HyperText Transfer Protocol HTTP for IPTV Signaling Caching in HTTP Video on Demand: RTSP SIP for IPTV Signaling SIP MESSAGE SIP SUBSCRIBE and NOTIFY SDP in SIP and RTSP 253 255 258 260 265 273 277 279 281 Chapter 11: Next-Generation IPTV Encoding – MPEG-2, MPEG-4 and beyond Transporting the MPEG Stream RTP MPEG-2 Transport Stream and the MPEG-4 File Format Forward Error Correction 215 218 219 220 222 224 224 225 226 234 237 244 285 291 292 294 295 viii Contents Chapter 12: Next-Generation IPTV Networking and Streaming with IMS What is IMS? Registering in IMS How IMS works with SIP SIP INVITE SIP SUBSCRIBE and NOTIFY Forking and Redirecting Sessions Identity in IMS: the SIP URI, PUID and PSI SDP Setting Up and Tearing Down the IPTV Multicast IMS Communications Services Handling Quality of Service Service Discovery Control Function NPVR Function Connecting Application Servers: the ISC Interface 297 301 307 307 308 308 308 309 310 312 314 317 320 320 320 325 Developing and Deploying IPTV It’s life, Jim, but not as we know it Enhancing Voting Automating Scriptwriting Inserting Advertising Personalizing Television Electronic Program Guides Using the IPTV Technology 329 330 331 333 336 341 343 344 References 349 Index 355 Chapter 13: 344 Why IPTV? Usually displayed as a table of the current time and the show, EPGs have developed a lot – through the use of XML, and the inclusion of video They are not yet personal, though, but making a personal EPG once you have the profile information available in an IMS-based IPTV system (the history of the user’s interaction, his demographic profile, and the metadata describing the shows) is easy – no more difficult than creating a personalized web page Whether the system actually uses the web as the base for the EPG (e.g., with cookies triggering the retrieval of the interaction log and personal profile) or whether it uses the session as the trigger is merely a matter of taste and familiarity from the developer The original purpose of the metadata accompanying a show was to create the EPG, but today the EPG can be used to refine the presentation – and also to generate more revenue for the service provider (not necessarily by including advertising) Program guides were originally listings of what was available in the different television channels at different times, but once electronic, there is no need to confine the presentation only to that Including recommendations in an EPG is simple, since the user’s profile and previous actions are known Recommender engines is a field in itself, both of research and development, and they not have to be directly included in the IPTV system The result of the EPG is a set of personalized recommendations These recommendations can be based on the preferences of the individual user, or a group that the user belongs to The service provider, however, has another opportunity: to sell a media asset to the user If someone likes 24, they might like Lost And if they like Lost, they may want to watch the movie Castaway on video on demand; it is free, but also available without advertising for 10 dollars per view Leveraging such opportunities becomes possible in IPTV, but it not only requires a recommender system which knows about the relations between different media properties from an editorial perspective; the system also has to be programmed with the sales opportunities and prices available The relations between different media properties can be derived from the log files (someone who watched Lost also saw Castaway) This is what metadata is for, the only problem being that it cannot determine why Understanding the plot, and why someone who likes one show might like another, is still beyond the reasoning of recommender systems That is where the producer has to step in, and tell the system what is relevant, and related Using the IPTV Technology We have already discussed the principles of how interaction can affect programs, and talked a little about how this can become (indeed, has already become) a revenue stream for the broadcaster However, it is clear that the servers that leverage the IMS system (the application servers) will be crucial Chapter 13: Developing and Deploying IPTV 345 There are a number of components in the IPTV system, and by now their roles should be clear Table 13-1 lists what they are, and their role in relation to each others What it is How it works Why it is needed Television set/Media renderer Receives the IPTV signal and renders it on the screen Makes it possible to see the video content Set-top box/Interaction device Captures user input and sends it to a central interaction server Makes sure the user’s interactions get to the IPTV service provider, and can be used to change the content of the show Home network Connects the different types of equipment in the home together Makes it possible for different media stores, renderers and interaction devices to interact with each other, and services on the global network (Internet) Home gateway Manages addressing in the home, registration with the service provider, and filtering of content (the last two functions can also be performed by the set-top box) As a firewall and address management system, and to ensure that the user’s actions are authorized IMS proxy Captures the request for the video service and makes sure it gets to the right receivers, including the QoS system Interconnects the network and signaling planes of the system, and makes sure the service requests get to the right nodes Also connects to the profile management system QoS system Instructs routers in the network how their queuing mechanisms should be set up Without QoS, video can be delayed and result in degraded user experience IMS identity management Makes sure the user is who he claims he is, and connects the use of the identity to the relevant subscriptions (and hence charging) Without identity management, anyone could use anyone else’s services; the charging systems would have to work offline and with special tokens to keep track of who should pay for what (as it is now, actually) Table 13-1 The components of an interactive IPTV system 346 Why IPTV? What it is How it works Why it is needed IMS presence and profile management Keeps track of what the user does and has done; makes sure this is registered in the system Makes it possible to personalize content, and to know what other users are watching (if allowed) IPTV streaming service control Manages the video stream, including switching to a different video stream when the user selection demands Note that this is not the same as channel switching Makes sure that the program starts when requested, and eventually creates programs from different video sources automatically on the fly IPTV streaming service delivery Handles the streaming of the content over the network Interacts with the QoS management Makes sure content gets where it is supposed to go Advertising insertion At selected points in the media stream, pastes in video sequences which contain commercial messages (although this could be a generic mechanism) Puts advertising in the right place in the program Interactivity server Captures the interactivity requests (from the user’s IPTV session), collates them (if required), and sends to the appropriate server(s), such as charging, profile management and streaming service control Interactions coming from more than one user need to be collated and coordinated, otherwise they will not result in anything Table 13-1 (Continued) From the perspective of an IPTV system, applications can be realized in two ways: locally, in the terminal; or remotely, in the IPTV system This puts different requirements on how the applications communicate with the service provider server But either way, the application is a function of the protocols used, since protocols both determine what can be done with the application; and applications put requirements on protocols Providing video on demand is not difficult nowadays It used to be the apex of development, and at the end of the 1980s, video servers were all the craze Moore’s law and the expanding bandwidth made it much easier Just, hook up a number of network connections to a really big server, find a way to make people pay, load a library of movies, and run with it There are two Chapter 13: Developing and Deploying IPTV 347 hurdles, however The service provider has to pay for the content; and the server has to be really, really big if the model is to be successful Charging is easy to if you have one big server It is simple to connect a user database to a server system, and many small servers can be used instead of one big one – hundreds, or thousands, even Connecting them directly to each other, while maintaining control over the directory, is how peer-to-peer file sharing works The technology has been around since the 1980s, and broadcasters are now becoming interested, especially those that are publicly funded This makes it possible for users to view programs again, without the broadcaster having to provide the resources The issue is how to maintain control over the distribution – also there is no way of getting paid, at least not at the moment Once the signaling is done (whether between peers, or between client and server), the media should be delivered It is not just a matter of pushing a button on the TV set, as even when broadcast in digital formats, media has to be encoded There is no “one size fits all” when it comes to encoding and media transport How the encoding is done affects how efficiently the distribution can be done, as well as how the video can be mixed with others Encoding the video stream in a way that makes it possible to send over the wire is one thing, and this is a well-known technology Making sure it is sent at the right time, and in the right way, is another The signaling, confirming that the user is allowed to view the video and that interactivity is working is the core of what is new in IPTV There are three protocols which are particularly important for the IPTV signaling: SIP, HTTP and RTSP The Session Initiation Protocol (SIP) is used in IMS – but also handles the crucial presence information, and enables the interactivity communication The Real Time Streaming Protocol (RTSP) is actually a control protocol for “remote video players” – in other words, video on demand And the HyperText Transfer Protocol (HTTP) is a way to send documents, such as metadata, around on the network These protocols, especially SIP and HTTP, suffer from “feature creep”, however They have been extended, and the methods defined in the protocols were misused (at least compared to the original intentions) to create new services and ways of doing old services This is especially true for HTTP This is a bad idea for several reasons (even if HTTP is extensible in a completely different way from other protocols) An especially bad idea is to use HTTP for data transport as well as signaling This is a very tempting idea from the perspective of developers, since HTTP is probably the most well-known protocol in the industry today, and it was initially intended for data transport, but later was extended to handle signaling Using IMS and the functions it offers, such as the signaling, the presence, the profiles and other mechanisms, provides a number of possibilities for the service provider Current IPTV systems not provide those possibilities – not without adding functionality IMS-based IPTV does offer such functions, and as IMS-based IPTV is now being standardized and deployed, it makes sense for developers to prepare References The references in this chapter refer to the entire book They are ordered by chapter – but mostly they cover everything Since the market is developing so fast, market reports are not trustworthy Standards are also not static – they continue to develop and change as the market changes As far as possible, the documents quoted here are the final versions, however, note that standards bodies often start a second version as soon as they have finished the first Standards are not the only important documents, of course, but so far, guidelines from real deployments of IPTV are few and far between To the extent that they are available and usable outside the particular system of the provider in question, they have been cited here A book is a snapshot, but a website can continue to develop; so I have put up a website at www.interactive-iptv.com Please refer to that for a list of references with hyperlinks, which I will update occasionally Chapter The NM2 (New Millennium, New Media) Project: http://www.ist-nm2.org/ The LIVE project: http://www.ist-live.org/ Ericsson MeOnTV: http://www.ericsson.com/ Chapter The standard that describes how IPTV will work with IMS comes from Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN), available from http://portal.etsi.org/Portal_Common/home.asp IPTV Architecture; Dedicated subsystem for IPTV functions, ETSI TS 182 028 V2.0.0 (2008-01) IPTV Architecture; IPTV functions supported by the IMS subsystem, ETSI TS 182 027 V2.0.0 (2008-02) Service Layer Requirements to Integrate NGN Services and IPTV, ETSI TS 181 016 V2.0.0 (2007-11) Requirements for network transport capabilities to support IPTV services, ETSI TS 181 014 V2.0.0 (2007-11) Open IPTV Forum architecture specification: Open IPTV Forum – Functional Architecture –V 1.1, Approved Jan 15, 2008 Available at http://www.openiptvforum.org/ docs/OpenIPTV-Functional_Architecture-V1_1-2008-01-15_APPROVED.pdf Frauenhofer Fokus Kompetenzzentren NGNI, available from http://www.fokus fraunhofer.de/ngni/topics/IPTV.php?lang=de#enabler Why IPTV? Interactivity, Technologies and Services c 2008 Johan Hjelm Johan Hjelm 350 References Chapter Consumer Electronics Association: CEA-2014 Web-based Protocol and Framework for Remote User Interface on UPnP™ Networks and the Internet (Web4CE), Document number: CEA-2014 Available from http://www.fokus.fraunhofer.de/ngni/ topics/IPTV.php?lang=de#enabler The DLNA Networked Device Interoperability Guidelines, available from http://www dlna.org/industry/certification/guidelines/ UPnP Forum specifications, available from http://www.upnp.org/standardizeddcps/ default.asp DVB Multimedia Home Platform (MHP), specifications available from http://www mhp.org/mhp_technology/mhp_1_2/ Chapter BBC Interactive TV standards and guidelines, available from http://www.bbc.co.uk/ commissioning/interactive/ Sky Interactive TV standards and guidelines, available from http://www.skyinteractive com/sky/home/default.htm Chapter Interactive Advertising Bureau, Broadband Video Commercial Measurement Guidelines, available from http://www.iab.net/iab_products_and_industry_services/1421/ 1443 ANSI/SCTE 35 2004, Digital Program Insertion Cueing Message for Cable Available from http://www.scte.org/documents/pdf/ANSISCTE352004.pdf Chapter BBC Interactive Media Player, available from http://www.bbc.co.uk/iplayer/ EBU P2P Media Portal, available at http://www.ebu.ch/members/EBU_Media_portal_ Trial_1.php Chapter Marlin Developer Community, available at http://www.marlin-community.com/ Creative Commons, http://creativecommons.org/ Chapter The XDMS is documented in a large number of documents from the OMA, available from http://member.openmobilealliance.org/ The most important are: XML Document Management Architecture XML Document Management (XDM) Specification References 351 Presence and Group Management are partly created by OMA, partly by IETF The OMA documents are: Presence SIMPLE Architecture SIP/SIMPLE Presence Specification Presence XDM Specification Presence SIMPLE Specification Presence Content XDM Specification Resource List Server (RLS) XDM Specification IETF, the Internet Engineering Task Force, defines the basics for presence in a collection of RFCs (Requests for Comment, but actually standards documents) They are available from http://www.ietf.org/rfc.html The most relevant for this chapter are: RFC 4662, A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists RFC 4661, An Extensible Markup Language (XML)-Based Format for Event Notification Filtering RFC 4660, Functional Description of Event Notification Filtering RFC 4480, RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF) RFC 3903, Session Initiation Protocol (SIP) Extension for Event State Publication RFC 3863, Presence Information Data Format (PIDF) RFC 3857, A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP) RFC 3856, A Presence Event Package for the Session Initiation Protocol (SIP) RFC 3265, Session Initiation Protocol (SIP)-Specific Event Notification RFC 2779, Instant Messaging / Presence Protocol Requirements RFC 2778, A Model for Presence and Instant Messaging RFC 3859, Common Profile for Presence (CPP) Chapter XML is the mother of all metadata formats The standard itself is documented in several W3C Recommendations available from http://www.w3.org/XML/Core/ #Publications OWL, the Web Ontology Language, is documented in a series of W3C Recommendations at http://www.w3.org/2004/OWL/#specs The TV-Anytime standard is well documented in a large number of documents, available from ETSI, http://portal.etsi.org/Portal_Common/home.asp IETF RFC 4078, The TV-Anytime Content Reference Identifier (CRID), available from http://www.ietf.org/rfc.html IPTC news codes is available from http://www.iptc.org/NewsCodes/ NewsML is available from http://www.newsml.org/ SportsML is available from http://www.sportsml.org/ The latest version includes a curling plugin Dublin Core Metadata Initiative, http://dublincore.org/ SMPTE-RA Metadata Dictionary is available at http://www.smpte-ra.org/mdd/index html MXF, the Material Exchange Format, is available at http://www.ebu.ch/en/technical/ trev/trev_291-devlin.pdf 352 References Document number Name Contents ETSI TS 102 822-1 V1.3.1 (2006-01) Part 1: Benchmark Features Essentially a set of requirements for TV-Anytime, which the standard is measured against to determine if it has fulfilled its goals ETSI TS 102 822-2 V1.3.1 (2006-01) Part 2: System Description The overall description of how the TV-Anytime system is intended to work ETSI TS 102 822-3-2 V1.3.1 Part 3: Metadata Metadata elements, schemas, vocabulary, and structure ETSI TS 102 822-4 V1.1.2 Part 4: Content Referencing How the CRID (the URI used in TV-Anytime) works ETSI TS 102 822-5-2 V1.2.1 Part 5: Rights Management and Protection (RMP) How metadata is applied to create content protection ETSI TS 102 822-6-1 V1.3.1 Part 6: Delivery of Metadata over a Bidirectional Network Defines a format for SOAP/HTTP bidirectional data transport ETSI TS 102 822-7 V1.1.1 Part 7: Bidirectional Metadata Delivery Protection Security and transmission protection for bidirectional data transport ETSI TS 102 822-8 V1.1.1 Part 8: Phase – Interchange Data Format Defines retrieval of TV-Anytime data from “alternative sources”, essentially website download ETSI TS 102 822-9 V1.1.1 Part 9: Phase – Remote Programming Defines how to program a recorder, for instance a PVR, using TV-Anytime UMID, the SMPTE 330M Unique Material Identifier, available from http://www.smpte org/standards/smpte_ra/metadata_registries MPEG-7 is standardized by the Motion Pictures Expert Group, and the standards are approved by ISO The official MPEG documentation is available from ISO or http://www.chiariglione.org/mpeg/ Chapter 10 Hypertext Transfer Protocol – HTTP/1.1, is documented in RFC 2616, available from http://www.ietf.org/rfc.html HTTP State management mechanism (aka cookies), RFC 2965, available from http://www.ietf.org/rfc.html References 353 SIP: Session Initiation Protocol, RFC 3261, available from http://www.ietf.org/rfc.html RTSP: the Real Time Streaming Protocol (RTSP), RFC 2326, available from http:// www.ietf.org/rfc.html SOAP, standardized by the W3C at http://www.w3.org/2000/xp/Group/ SDP: Session Description Protocol, standardized in RFC 2327 Chapter 11 MPEG-2 and MPEG-4 are standardized by the Motion Pictures Expert Group, and the standards are approved by ISO The official MPEG documentation is available from ISO or http://www.chiariglione.org/mpeg/ RTP: A Transport Protocol for Real-Time Applications, RFC 3550, available from http://www.ietf.org/rfc.html Chapter 12 Internet Group Management Protocol, Version (IGMP), RFC 3376, available from http://www.ietf.org/rfc.html IMS is standardized by the 3GPP There are several specifications relating to IMS, the architecture is documented in TS 23.228, IP Multimedia Subsystem (IMS); Stage 2, available at http://www.3gpp.org/ftp/Specs/html-info/23228.htm The best IMS reference is however: The 3G IP Multimedia Subsystem (IMS): Merging the Internet and the Cellular Worlds, Second Edition by Gonzalo Camarillo and Miguel-Angel García-Martín, John Wiley& Sons, Ltd, 2006, ISBN 978-0470018187 Index ADSL, see Asynchronous Digital Subscriber Line Advertisements and copyright 175 and presence 204–10 Advertising 9, 10, 101–2, 127–42, 149, 204–10 insertion 20, 140–2, 149, 336–7 statistics and feedback 139 Alternative distribution media 14, 15 Application Gateway (AG) 39 Application Server (AS) 20 Asynchronous Digital Subscriber Line (ADSL) 57, 67 ATIS 35 Authentication 40, 51, 304–6 Authorization 40, 51, 304–6 BBC 13 BBC IMP 160 Broadcast over IPTV BskyB 13 43 Cable-TV 54, 73 Caching in HTTP 260–4 Cascading Style Sheets 81, 107 CEA-2014–A 39, 80–6 CE4HTML 83 Channel switching 41, 42, 89–92 Charging 51, 151–5 functions in IMS 153–5 Colors 109 Consumer electronics 52–98 ContentDirectory in UpnP 64–6 Content filtering 218–19 Content issuer (in OMA DRM) 180 Content management in ETSI TISPAN architecture 48 Content Reference Identfier 230, 234–6 Copyright 163–75 and advertisements 175 exceptions to 166–7 Why IPTV? Interactivity, Technologies and Services c 2008 Johan Hjelm infringement 165 policy 182–4 Creative Commons 168–73 CRID, see Content Reference Identfier CSS, see Cascading Style Sheets DAVIC, see Digital Audio Video Council De jure and de facto standards 33, 36 Derivative works 124, 166 Design for interactive TV 107–12, 137–8 DHCP, see Dynamic Host Configuration Protocol Digital Audio Video Council (DAVIC) 89 Digital Living Network Alliance (DLNA) 35, 58–9, 63–6 Digital Rights Management (DRM) 11, 76, 163, 175–84 Digital Versatile Disc (DVD) 54 DLNA, see Digital Living Network Alliance Downloading files 157 DRM, see Digital Rights Management DRM Agent 179 DRM Rights Object 179 DRM standards 178 Dublin Core 222–4 DVB Forum 35 DVD, see Digital Versatile Disc Dynamic Host Configuration Protocol (DHCP) 60 ECMAScript 39 Electronic Program Guide (EPG) 43, 82–3, 150, 225, 231, 343–4 Electronic Service Guide (ESG) 43 Encryption 186 Endemol 7, 31 Enhanced interaction 329–44 EPG, see Electronic Program Guide EPG in XML 82–3 Johan Hjelm 356 Index Ericsson 31 ESG, see Electronic Service Guide ETSI, see European Telecommunications Standardization Instiute EU 7th Framework Program 21, 22 European Broadcasting Union 162 European Commission 21 European Telecommunications Standardization Instiute (ETSI) 35, 42 eXtensible Markup Language 80–4, 213–57 FEC, see Forward Error Correction Feedback channel for advertising 206 Folksonomy 244 Forward Error Correction (FEC) 295 FP 7, see EU 7th Framework Program Fraud in IPTV advertising 209 Frauenhofer Fokus 49 GENA, see General Event Notification Architecture General Event Notification Architecture 60, 62 Graphics for interactive TV 112–15 Holographic television 93 Home gateway 19 Home network 19, 55–6 Home router, see Residential gateway Home Subscriber Server 301 HSS, see Home Subscriber Server HTML, see HyperText Markup Language HTTP, see HyperText Transfer Protocol for media streaming 63 methods 255–6 as signaling protocol 62, 255–64 and streaming 153–9 HyperText Markup Language 82 HyperText Transfer Protocol (HTTP) 58, 60–6 Identity management 19, 40, 51 IETF, see Internet Engineering Task Force IMS 293 –327, 9, 12 IMS Application Server 325–7 IMS authentication and authorization 304–6 IMS Communications Services 50, 314–17 IMS Core 49, 302–3 IMS Gateway Function (IG) 39 IMS identity management 19, 304–5 IMS profile management 19 IMS, see Internet Multimedia Subsystem IMS and SIP 307–13 Information Interchange Model (IIM) 221 Interaction models 110–12 Interactive applications, testing of 116–19 Interactive TV 2, 101, 132 commerce 132 graphics 112–13 and IMS 102 menus 113–16 user experience 103 Interactivity 13, 14, 99–126 Interactivity Server 20, 106 Interface design rules 116 International Press Telecommunications Council 221 Internet Engineering Task Force (IETF) 34 Internet Gateway Device,see UPnP Internet Gateway Device (IGD) Internet Multimedia Subsystem (IMS) 15–18 IPTC, see International Press Telecommunications Council IPTV Application Server (IPTV AS) 20 applications in ETSI TISPAN 45 business model 5, 10, 12 content production ecosystem 3, in Japan 92–6 in the mobile 96–8 Reference Architecture 38, 43 signaling 253–84 Standardization 34–8 technology 16, 19, 344–7 value chain 3, –5, ISC interface 325 ITU-T 34, 35 JavaScript, see ECMAScript Java in the settop box 86–9 Layered system view 16, 17 Linear television 41, 43 LIVE Project 15, 28–31, 248–9 Marlin DRM 180–2 Mashups 119–23 Media Delivery Function 46 Media Renderer in UPnP 61–6 Media Resource Function (MRF) 51 Media Server in UPnP 61–6 Index Menus for interactive TV 113–16 Metadata 174, 211–52 generation 220 vocabularies 213 Methods in HTTP 255–6 Methods in RTSP 267–70 Methods in SIP 276–83 Me on TV (application) 31–2 MHP, see Multimedia Home Platform Motion Pictures Expert Group (MPEG) 286 MPEG-2 294–295, 287 MPEG-4 78, 237, 287–91 MPEG-7 237–44 MPEG BIFS 289–90 MPEG Description Definition Language (DDL) 238 MPEG Description Schemas (DS) 241–2 MPEG, see Motion Pictures Expert Group (MPEG) MRF, see Media Resource Function Multicast 19, 20, 41, 67, 90–3, 293, 299, 312–13 Multimedia Home Platform 86–9 NAT, see Network Address Translation Near video on demand 145 Network Address Translation (NAT) 57 NewsCodes 221 News Industry Text Format (NITF) 221 NewsML 221 Next Generation Network (NGN) 42 NGN, see Next Generation Network (NGN) NM2 Project 23–7 NPVR, see Personal Video Recorder NTSC 34, 93 NTT “New Generation Network” 95–7 OITF 38 OMA DRM 179–81 OMA Presence 189–98 Ontologies 245, 250–2 Open IMS Playground 50 Open IPTV Forum 34, 37 PAL 34 Parental control 187 PC, see Personal Computer Peer-to-peer filesharing 144, 156–63 Personal Computer (PC) 54 Personal Video Recorder (PVR) 41, 43, 145 P/meta 224 357 Presence 19, 46, 187–99 Presence and advertising 204–10 Presence document for IPTV 197–8 Presence enabled phone book 192 Presence information 194–8 Privacy 4, 186–7 Profile management 19, 46 Profiles in IPTV 201–4 Program design 101 PVR, see Personal Video Recorder QoS 19, 317–19 RDF, see Resource Description Framework Real-Time Streaming Protocol 51, 145, 265–73 Real-time Transport Protocol (RTP) 51, 58, 63, 292–4 Recommender system 150, 216–18 Red button 13, 131 Requirements on metadata generation 248–9 Residential gateway 66–72 Resource Description Framework 223–4 Resource List Server 199 RLS, see Resource List Server RTP, see Real-time Transport Protocol RTSP, see Real-Time Streaming Protocol RTSP and URI:s 266 Scripting interactive television 101–5, 333–6 SCTE 35 SDP, see Session Description Protocol SECAM 34 Security functions 40 Service Control Function 46 Service discovery 40 Session Description Protocol (SDP) 281–3, 301–12 Session Initiation Protocol (SIP) 51, 58, 273–81, 307–12 Session Management 51, 267 Sessions in HTTP 258–60 Settop box 19, 69, 72–9, 176 7th Framework Program, see EU 7th Framework Program Shape-shifting television 23 SIP/IMS-DLNA Gateway 69 SIP for IPTV signaling 273–81 SIP presence 188–93 SIP, see Session Initiation Protocol SIP SUBSCRIBE and NOTIFY 279–80 358 Index SMPTE, see Society of Motion Pictures and Television Engineers Society of Motion Pictures and Television Engineers (SMPTE) Metadata Dictionary 224 Stateless vs stateful protocols 258, 266 Streaming video 18, 19, 20 Subscription management 186–7 Superdistribution 176 Taxonomies 221 Telescoping advertisements 131 Testing of interactive applications 116–19 TR-069 82 Transport control in ETSI TISPAN 49 Triple Play 50 TV-Anytime 225–36 UDP, see User Datagram Protocol Universally Unique Identifier (UUID) 60 Universal Plug and Play (UPnP) 59–66 UPnP device control 61 UPnP device description 62 UPnP device discovery 60–2 UPnP Internet Gateway Device (IGD) 70 UPnP QoS 71–2 UPnP, see Universal Plug and Play User Datagram Protocol (UDP) 59, 298 User profiles 10, 45–6, 51, 77, 201–4 and interactivity 104, 341–3 User provided content 123–6, 155–6 copyright on 156–72 UUID, see Universally Unique Identifier VCR, see Video Cassette Recorder Video Cassette Recorder (VCR) 143 Video on Demand (VoD) 41, 51, 143–9 advertising in 148–9 charging for 151–4 constraints on 146–7 user experience of 147 VoD, see Video on Demand Voting in IPTV 15, 331–3 Watermarking 177 Web 2.0 9, 119 Web browser in television set 79–87 XDMS, see XML Document Management Server XHTML 80–4 XML, see EXtensible Markup Language XML Document Management Server (XDMS) 39, 46, 189–204 XML lists 193 YouTube 143, 172, 245–6 .. .Why IPTV? Interactivity, Technologies and Services Johan Hjelm Ericsson A John Wiley and Sons, Ltd, Publication Why IPTV? Written by people in the know, the... Opportunities Saxtoft ISBN: 978-0-470-72708-9 Triple Play: Building the Converged Network for IP, VoIP and IPTV Hens & Caballero ISBN: 978-0-470-75367-5 Why IPTV? Interactivity, Technologies and Services. .. things happening in the story as the program progresses, Why IPTV? Interactivity, Technologies and Services c 2008 Johan Hjelm Johan Hjelm Why IPTV? works when you rely on the participants As in a