Documents
Resources
Learning Center
Upload
Plans & pricing Sign in
Sign Out

MOBILE TV

VIEWS: 6 PAGES: 17

									Developers guidelines




 January 2009

 Dynamic presentation of
 streamed mobile TV content
 in Sony Ericsson phones
             Developers guidelines | Dynamic presentation of streamed mobile TV content




Preface

Purpose of this document
This document describes the solution for dynamic presentation of streamed mobile TV content integrated
into the Media application, and the complete setup of the server solution needed to deliver streaming
video to the application.

Note: The mobile TV solution presented here is a customisation offering and is not generally available in
Sony Ericsson phone models mentioned in this document.

People who can benefit from this document are:

• Operators and service providers

• Content providers

It is assumed that the reader is familiar with streaming media and the RSS and OPML standards.




     These Developers guidelines are published by:           This document is published by Sony Ericsson
                                                             Mobile Communications AB, without any
     Sony Ericsson Mobile Communications AB,                 warranty*. Improvements and changes to this text
                                                             necessitated by typographical errors, inaccuracies
     SE-221 88 Lund, Sweden                                  of current information or improvements to
                                                             programs and/or equipment, may be made by
     www.sonyericsson.com/                                   Sony Ericsson Mobile Communications AB at any
                                                             time and without notice. Such changes will,
                                                             however, be incorporated into new editions of this
     © Sony Ericsson Mobile Communications AB,               document. Printed versions are to be regarded as
     2007. All rights reserved. You are hereby granted       temporary reference copies only.
     a license to download and/or print a copy of this
     document.                                               *All implied warranties, including without limitation
     Any rights not expressly granted herein are             the implied warranties of merchantability or fitness
                                                             for a particular purpose, are excluded. In no event
     reserved.                                               shall Sony Ericsson or its licensors be liable for
                                                             incidental or consequential damages of any
     Sixth edition (January 2009)                            nature, including but not limited to lost profits or
     Publication number: 1205-3598.6                         commercial loss, arising out of the use of the
                                                             information in this document.




                                                         2                                              January 2009
            Developers guidelines | Dynamic presentation of streamed mobile TV content



Sony Ericsson Developer World
At www.sonyericsson.com/developer, developers find the latest technical documentation and
development tools such as phone White papers, Developers guidelines for different technologies, Getting
started tutorials, SDKs (Software Development Kits) and tool plugins. The Web site also features news
articles, go-to-market advice, moderated discussion forums offering free technical support and a Wiki
community sharing expertise and code examples.

For more information about these professional services, go to the Sony Ericsson Developer World Web
site.




Document conventions

Products
Sony Ericsson mobile phones are referred to in this document using generic names:

Generic names               Sony Ericsson mobile phones
Series

C702                        C702, C702c, C702a

C902                        C902, C902c

C905                        C905, C905c, C905a

T700                        T700

W595                        W595

W760                        W760i, W760c

W902                        W902

W980                        W980i

Z770                        Z770i

Z780                        Z780i, Z780a




                                                  3                                       January 2009
             Developers guidelines | Dynamic presentation of streamed mobile TV content



Terminology and abbreviations

DSL              Dynamic Streaming Links

HTTP             Hypertext Transfer Protocol

itunes:          prefix for XML namespace of ITunes RSS extensions

media:           prefix for XML namespace of Yahoo Media RSS extensions

OMA              Open Mobile Alliance

OPML             Outline Processor Markup Language

RSS              Really Simple Syndication

URL              Uniform Resource Locator


"Streamed mobile TV content" or "TV content" consists of "Live TV" and "On-demand TV".

"TV service provider" is the provider of the TV service and can be a mobile operator, any content provider
or Sony Ericsson.

"DSL" is a protocol defined by Sony Ericsson to handle dynamic presentation of TV content in the Media
application.




Typographical conventions
Code is written in Courier font: <opml version="1.0">...</opml>




                                                    4                                       January 2009
         Developers guidelines | Dynamic presentation of streamed mobile TV content



Document history
 Change history
 2007-11-06           Doc. no. 1205-3598.1       First version published on Developer World

 2008-06-17           Doc. no. 1205-3598.2       Second version. Information about the C702,
                                                 C902, C905, W760, W980, Z770 and Z780
                                                 series added

 2008-07-22           Doc. no. 1205-3598.3       Third version. Information about the T700,
                                                 W595 and W902 series added

 2008-09-09           Doc. no. 1205-3598.4       Fourth version.

 2008-10-17           Doc. no. 1205-3598.4       Fourth revised version. New document layout
                      (rev. B)

 2008-11-11           Doc. no. 1205-3598.5       Fifth version.

 2009-01-09           Doc. no. 1205-3598.6       Sixth version. Minor changes




                                             5                                      January 2009
                   Developers guidelines | Dynamic presentation of streamed mobile TV content




Contents
Overview ......................................................................................................................7
 Introduction ...............................................................................................................7
 Architecture ...............................................................................................................7
    Presentation of TV content ....................................................................................7

Implementation ...........................................................................................................9
  HTTP server for OPML files .......................................................................................9
    HTTP interactions ..................................................................................................9
    OPML files .............................................................................................................9
  HTTP server for RSS files ........................................................................................11
    HTTP interactions ................................................................................................11
    RSS files ..............................................................................................................11
  Streaming server .....................................................................................................13
  Provisioning (optional) .............................................................................................13
  DSL traffic separated from other data traffic (optional) ...........................................13
  Security handling (optional) .....................................................................................13
  Subscription handling (optional) ..............................................................................14
  Customising the settings .........................................................................................15

Appendix ....................................................................................................................16
  OPML file example ..................................................................................................16
  RSS file example .....................................................................................................17




                                                                             6                                                     January 2009
             Developers guidelines | Dynamic presentation of streamed mobile TV content




Overview

Introduction
SonyEricsson offers the possibility to present and consume streamed mobile TV content directly from the
Media application in the phone, without the need for Web browser solutions or 3rd party applications.

The solution is based on open standard syndication technologies and enables the user to browse and
consume TV content in the same matter as any local content with the same instant user experience.

Value for users:

• Find and experience TV content in the Media application, the same way as local content.
• Fast off-line browsing of available TV content.
• A constantly updated TV offer adapted to the needs for the time.

Value for operators:

•   Easily modify the offered TV content according to time or events.
•   Modify the way TV content is presented in a fast and flexible way.
•   More usage of the TV service due to easy user access.
•   No need for specific 3rd party applications or Web pages.




Architecture
The Sony Ericsson solution is built on two parts:

• Presentation of TV content

• Delivery of TV content.




Presentation of TV content
The phone user finds TV content in the Media application. TV content is presented in a multi-level tree
structure. Each level is described with a name, a description and an icon.

The principle is that the phone downloads files with information about structure, names, descriptions,
references to icons and information about how to start consuming the TV content. The phone downloads
the files according to a configurable scheme using the Sony Ericsson DSL protocol.




                                                    7                                        January 2009
             Developers guidelines | Dynamic presentation of streamed mobile TV content



Sony Ericsson DSL protocol




The DSL protocol is designed by Sony Ericsson to handle dynamic presentation of TV content in the
Media application. The protocol is entirely built on the open technologies RSS, OPML and HTTP, with
some minor extensions.

OPML files define the top logical levels in the tree structure, Menus, when applicable. Menu levels are
optional but can also exist in several levels, menu in menu. OPML files also include references to valid
RSS files, defining the lower levels. A menu is a group of menus or channels, that is, one menu includes
one or several menus or channels. The same OPML file can include both references to RSS files that are
grouped in menus and references to RSS files not grouped in menus.

The OPML files are retrieved using HTTP. References to OPML files are configurable, see “Provisioning
(optional)” on page 13 and “Customising the settings” on page 15. A maximum of 10 OPML files can be
referenced from a phone.

RSS files describe the two lower levels, Channels and Items, in the logical tree structure in which TV
content is presented in the Media application. Items are the actual TV content. Each item contains a
reference to a video stream. A channel is a group of items, that is, one channel includes one or several
Items. One RSS file describes one or several channels. RSS files are retrieved using HTTP.

OPML and RSS files are updated according to a configurable time interval, set in configuration
parameters.

Delivery of TV content
Delivery of TV content is based on the 3GPP PSS (Packet Switched Streaming) standard using RTSP.




                                                    8                                        January 2009
              Developers guidelines | Dynamic presentation of streamed mobile TV content




Implementation
The following configurations need to be managed by the TV service provider:

Mandatory configurations:

•   HTTP server for OPML files
•   HTTP server for RSS files
•   Streaming server
•   Customising the settings.

Optional configurations:

•   Provisioning (optional)
•   DSL traffic separated from other data traffic (optional)
•   Security handling (optional)
•   Subscription handling (optional).




HTTP server for OPML files
One or several HTTP servers hold the OPML files.

The TV service provider has to set up a mechanism to compile correct OPML files specifying the presently
available TV content for each user. Depending on the used business model, it might be required to have
an individual OPML file for each user or group of users.




HTTP interactions
The HTTP server shall respond to HTTP GET requests from the phone. The server expects requests from
the phone according to the value of the MIN-UPDATE-INTERVAL configuration parameter. However, an
application may request updates more often.

OPML files are retrieved through an HTTP GET with the URL stored in the phone. The URLs used for
OPML files are specified in configurable parameters “Mobile TV DSL server 1” … “Mobile TV DSL server
10”.




OPML files
OPML files are OPML 1.0 compliant with a few extensions. The OPML files must use UTF-8 character
encoding.




                                                      9                                    January 2009
             Developers guidelines | Dynamic presentation of streamed mobile TV content



Only what is inside the <body> element of the OPML file is used. When several OPML files are referenced,
the result is equivalent to concatenating what is inside the <body> elements of all the OPML files into one
single <body> element.

If specifying a menu, which is optional, the attributes type, url and text are used in the <outline>
element:

• type is set to “menu”.
• url specifies the URL to the image to be used as icon in the list of menus. The image can have gif, jpg
  or png file format and has a maximum size of 25kB. The image is rescaled to fit the lists in the Media
  application.
• text specifies the descriptive text for the menu in plain text.

For subscription purposes the outline type purchaselink can be used. It has the following (required)
attributes:

• type: Should be “purchaselink”
• text: Specifies the title of the purchaselink
• htmlurl: A link to an html page where it is possible to become a subscriber of TV service (not
  required):
• url: Links to an icon connected with the purchaselink.

When specifying a channel, the attributes type and xmlUrl are used in the <outline> element:

• type is set to "rss".
• xmlUrl specifies the URL to the RSS file.

Note that the channel name, description and icon are always defined in the RSS file and not in the OPML
file.

Elements and attributes specified in the OPML files other than these specified above are disregarded in
DSL.

Example of OPML defining one channel:

      <outline type="rss" xmlUrl="http://www.channel.com/list.rss"/>

Example of OPML defining a menu named "Channels" including a purchaselink and two channels:

     <outline text="Channels" type="menu" url="http://www.channels.com/
chl.gif">
          <outline type="purchaselink" text=”Subscribe now!” htmlurl="http://
www.channels.com/Subscribe.html" url="http://www.channels.com/Sub_icon.gif"/>
          <outline type="rss" xmlUrl="http://www.channel.com/list.rss"/>
          <outline type="rss" xmlUrl="http://www.channellive.com/list.rss"/>
     </outline>




                                                    10                                       January 2009
             Developers guidelines | Dynamic presentation of streamed mobile TV content



HTTP server for RSS files
One or several HTTP servers hold the RSS files. It can be the same server which holds the OPML files or it
can be a different server. HTTP servers for RSS files can be maintained by the TV service provider, other
content providers or a combination of both.




HTTP interactions
The HTTP servers for RSS files shall respond to HTTP-GET requests from the phone. The servers expect
RSS file update requests from the phone according to the value of the MIN-UPDATE-INTERVAL
configuration parameter. However, an application may request updates more often.

RSS files are retrieved through HTTP-GET with the URLs specified in OPML files.




RSS files
RSS files in DSL must follow the RSS 2.0 specification, with the exception of allowing RTSP content. The
RSS files must use UTF-8 character encoding.

RSS 2.0 is extendable using namespace modules. The following modules are allowed in DSL:

• Media RSS module (http://search.yahoo.com/mrss). This is defined with the namespace
  <rss version="2.0" xmlns:media="http://search.yahoo.com/mrss/">

• iTunes. This is defined with the namespace <rss version="2.0" xmlns:itunes="http://
  www.itunes.com/dtds/podcast-1.0.dtd/">

Channels are described in the <channel> element:

• To specify the name of the channel, the subelement <title> is used.
• For specifying the image to be used as icon the subelement <image/url> is used. The image can
  have gif, jpg or png file format and a maximum size of 25kB. The image is rescaled to fit the lists in the
  Media application.
• There are three alternative subelements that can be used to specify the description of a channel, either
  <media:description type="plain">, <iTunes:summary> or <description>.

An item is described in an <item> element, which is a subelement of <channel>:

• The name of the item is either specified with <media:title type="plain"> or <title>, which
  both are subelements to <item>.
• For specifying the image to be used as icon, the subelement <media:thumbnail url = "..."> is
  used. The image can have gif, jpg or png file format and a maximum size of 25kB. The image is
  rescaled to fit the lists in the Media application.
• For the description of an item, one of the following three alternative elements can be used:
  <media:description type ="plain">, <iTunes:summary> or <description>. All of them
  are subelements to <item>.




                                                    11                                        January 2009
            Developers guidelines | Dynamic presentation of streamed mobile TV content



• The URL to the stream is specified in either of the following subelements of <item>:
  <media:content url="...">, <media:player url="..."> or <enclosure url="...">.

Other subelements and attributes specified in RSS files are disregarded in DSL.

HTML format is not supported in DSL. If any element includes HTML, either as entity encoded HTML or
within a CDATA block, the field is not presented.

Example of RSS defining one channel (used elements marked with bold text):

<channel>
     <title>Channel 1</title>
     <link>http://channel1.com/rss/global/mobiletv.rss</link>
     <image>
          <url>http://channel1.com/img/pic_logo_123x63.gif</url>
          <link>http://channel1.com</link>
          <title>Channel1</title>
          <height>63</height>
          <width>123</width>
     </image>
     <description>Channel 1</description>
     <item>
     .
     .

Example of RSS defining one item (used elements marked with bold text):

     <item>
          <author>rss@channel1.com</author>
          <title>Live</title>
          <link>rtsp://rtsp.channel1.com/videos/ihhEp3uTZck/video.3gp</link>
          <description>Live Item</description>
          <guid isPermaLink="true">rtsp://rtsp.channel1.com/videos/ihhEp3uTZck/
video.3gp</guid>
          <pubDate>Wed, 31 Jan 2007 02:34:27 -0800</pubDate>
          <media:player url="rtsp://rtsp.channel1.com/videos/ihhEp3uTZck/
video.3gp" />
          <media:thumbnail url=http://channel1.com/img/pic_live_logo_123x63.gif
width="123" height="63" />
          <media:title>Live Item</media:title>
          <enclosure url="rtsp://rtsp.channel1.com/videos/ihhEp3uTZck/
video.3gp" length="185" type="video/3gpp" />
     </item>




                                                  12                                    January 2009
             Developers guidelines | Dynamic presentation of streamed mobile TV content



Streaming server
One or several streaming servers hold and deliver the TV content using RTSP streaming according to
3GPP PSS. Streaming servers for TV content can be maintained by the TV service provider, other content
providers or a combination of both. For more details about how to set up the server and formats of the TV
content, see Developers guideline – Music and video in Sony Ericsson phones.




Provisioning (optional)
OMA Client Provisioning is used to:

• set and update URLs for OPML files

• set the time interval between updates of RSS and OPML files

• initiate an immediate update of the RSS and OPML files.

A detailed description of provisioning the Mobile TV application is described in Developers guideline –
OMA Client Provisioning and Device Management.




DSL traffic separated from other data
traffic (optional)
In case it is necessary to separate TV streaming and traffic caused by OPML and RSS file updates from
other data traffic in terms of charging due to the used business model, this must be handled by the
operator network.

The traffic caused by updates of OPML and RSS files is a product of the update frequency and the size of
the files and the images used for icons. Typically the size of an OPML file is 3 kB and an RSS file 5-10 kB.
The size of an image is dependent on its resolution and file format. Images are updated with the same
frequency as the RSS and OPML files.




Security handling (optional)
All mechanisms to secure that only valid phones and/or subscriptions use the service must be be handled
by the operator network.




                                                    13                                        January 2009
            Developers guidelines | Dynamic presentation of streamed mobile TV content



Subscription handling (optional)
All mechanisms to check valid subscriptions and provide correct OPML files for the user must be handled
by the operator network.




                                                  14                                      January 2009
            Developers guidelines | Dynamic presentation of streamed mobile TV content



Customising the settings
In generic Sony Ericsson phones, the Mobile TV application is disabled. When customising phones for an
operator, the Mobile TV application can be enabled, URLs to OPML files configured, and OPML/RSS
update interval specified.




                                                 15                                      January 2009
            Developers guidelines | Dynamic presentation of streamed mobile TV content




Appendix
This appendix contains examples of OPML and RSS files.




OPML file example
Example of a valid complete OPML file for DSL:

<?xml version="1.0" encoding="UTF-8" ?>
<opml version="1.0">
     <head>
          <title>Mobile TV</title>
          <dateCreated>Thu, 27 Jul 2006 01:20:06 GMT</dateCreated>
     </head>
     <body>
          <outline text="Dummy Channels" type="menu" url="http://
www.dummychannel.com/dummygif.gif">
               <outline type="purchaselink" text=”Subscribe now!”
htmlurl="http://www.dummychannel.com/Subscribe.html" url="http://
www.dummychannel.com/icon.gif"/>
               <outline type="rss" xmlUrl="http://dummychannel1.com/rss/global/
mobiletv.rss" />
               <outline type="rss" xmlUrl="http://dummychannel2.com/rss/global/
mobiletv.rss" />
               <outline text="Nested Dummy channels" type="menu" url="http://
www.dummychannel.com/dummygif.gif">
                    <outline type="rss" xmlUrl="http://dummychannel31.com/rss/
global/mobiletv.rss" />
                    <outline type="rss" xmlUrl="http://dummychannel32.com/rss/
global/mobiletv.rss" />
               </outline>
          </outline>
     </body>
</opml>




                                                 16                        January 2009
            Developers guidelines | Dynamic presentation of streamed mobile TV content



RSS file example
Example of a valid complete RSS file for DSL using RSS Media namespace extension:

<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:media="http://search.yahoo.com/mrss">
     <channel>
          <title>Channel 1</title>
          <link>http://channel1.com/rss/global/mobiletv.rss</link>
          <image>
               <url>http://channel1.com/img/pic_logo_123x63.gif</url>
               <link>http://channel1.com</link>
               <title>Channel1</title>
               <height>63</height>
               <width>123</width>
          </image>
          <description>Channel 1</description>
          <item>
               <author>rss@channel1.com</author>
               <title>Live</title>
               <link>rtsp://rtsp.channel1.com/videos/ihhEp3uTZck/video.3gp</
link>
               <description>Live Item</description>
               <guid isPermaLink="true">rtsp://rtsp.channel1.com/videos/
ihhEp3uTZck/video.3gp</guid>
               <pubDate>Wed, 31 Jan 2007 02:34:27 -0800</pubDate>
               <media:player url="rtsp://rtsp.channel1.com/videos/ihhEp3uTZck/
video.3gp" />
               <media:thumbnail url=http://channel1.com/img/
pic_live_logo_123x63.gif width="123" height="63" />
               <media:title>Live Item</media:title>
               <enclosure url="rtsp://rtsp.channel1.com/videos/ihhEp3uTZck/
video.3gp" length="185" type="video/3gpp" />
          </item>
          <item>
               <author>rss@channel1.com</author>
               <title>News</title>
               <link>rtsp://rtsp.channel1.com/videos/qdasjdhasd34/video.3gp</
link>
               <description>News Item</description>
               <guid isPermaLink="true"> rtsp://rtsp.channel1.com/videos/
qdasjdhasd34/video.3gp </guid>
               <pubDate>Sat, 03 Feb 2007 13:57:46 -0800</pubDate>
               <media:player url=" rtsp://rtsp.channel1.com/videos/
qdasjdhasd34/video.3gp" />
               <media:thumbnail url=" http://channel1.com/img/
pic_news_logo_123x63.jpg" width="123" height="63" />
               <media:title>News Item</media:title>
               <enclosure url=" rtsp://rtsp.channel1.com/videos/qdasjdhasd34/
video.3gp" length="232" type="video/3gpp"/>
          </item>
     </channel>
</rss>




                                                17                                  January 2009

								
To top