MediaServer:1 Device Template Version 1.01 Date: June 25, 2002 For UPnP™ Version 1.0 Status: Standardized DCP File from: MediaServer1.0.pdf Author: John.

Slides:



Advertisements
Similar presentations
CEA 2014 Overview Presented to the ATIS ITU-T FG IPTV Interoperability Forum January 24, 2007 Mt. View, CA Mark R. Walker PhD Sr. Viiv TM Planning Architect.
Advertisements

UPnP Device Architecture. Networking is easy, except… Ad hoc networks don't have resources just for the sake of the network E.g., DHCP, DNS, directory,
UPnP AV WC Status Update (UPnP Summit 2002) John Ritchie UPnP AV Co-Chair Intel Corporation.
UPnP AV WC Status Update (UPnP Summit 2003) John Ritchie – Intel Geert Knapen – Philips UPnP AV Co-chairs.
UPnP* AV: Easy Sharing of Digital Media Joe C. Pitarresi Business Development Intel Research & Development.
Web Service Ahmed Gamal Ahmed Nile University Bioinformatics Group
Global MP3 Geoffrey Beers Deborah Ford Mike Quinn Mark Ridao.
Media Transfer Protocol supported. 2 Session Outline Overview Overview Why use a class protocol? Why use a class protocol? Core scenarios & functionality.
Digital Living Network Alliance: Building out the Digital Network Bob Taylor Member, DLNA Board of Directors March 2006.
Quality of Service Update
Audio Video Update John Ritchie Intel Co-Chair Audio Video Committee.
Web Services Nasrullah. Motivation about web service There are number of programms over the internet that need to communicate with other programms over.
B. Fairman Sony US Advanced Technologies Center 1 Ubiquitous Video W3C Video on the Web Workshop
The Real Time Streaming Protocol (RTSP)
Depositing e-material to The National Library of Sweden.
II. Middleware for Distributed Systems
SMN 1.0 Smart Media Network Auburn University COMP7970 Richard Chapman 19 Sept 2002.
Chapter 4 Adding Images. Inserting and Aligning Images Using CSS When you choose graphics to add to a web page, it’s important to use graphic files in.
Universal Plug and Play (UPnP) Presented by: Kamal Kamal Kamal Kamal Mohammad Atieh Mohammad Atieh.
The Computer Communication Lab (236340) Spring 2005 Universal Plug and Play on Mobile Phone With Qualcomm - Device -
Printing & Imaging Update John Ritchie Intel Staff Engineer.
RSS RSS is a method that uses XML to distribute web content on one web site, to many other web sites. RSS allows fast browsing for news and updates.
RSS Sharing pictures with family and friends at home Sharing pictures with family and friends worldwide.
Course :: Certificate in Basic Computers Applications for End Users Introducing Window 7.
Processing of structured documents Spring 2003, Part 6 Helena Ahonen-Myka.
UPnP AV Media Server support for VLC player Student’s name: Shaleen Shah Date: November 5, 2007 Advisor’s name: Dr. Chung-E-Wang Prof. Dick Smith Department.
11 Games and Content Session 4.1. Session Overview  Show how games are made up of program code and content  Find out about the content management system.
DLNA Confidential Who Owns the Home Network? Glen Stone Director, Standards & Strategy Sony Electronics Inc. Chair: DLNA Technical Committee Glen Stone.
Project 1 Online multi-user video monitoring system.
Home Control Protocol for Smart Devices Hojin Park WG!-N1505.
Rally Technologies Spring 2008, Redmond, Washington DLNA Device Implementation Edwin Heredia Program Manager Windows Devices &
Getting to Know TiVo: The Home Media Engine (HME SDK) Eric M. Upchurch CS 525 Spring 2008.
Enabling Workflow in UPnP Networks Andreas BobekUniversity of Rostock Faculty of Computer Science and Electrical Engineering Andreas Bobek, Hendrik Bohn,
An Overview of MPEG-21 Cory McKay. Introduction Built on top of MPEG-4 and MPEG-7 standards Much more than just an audiovisual standard Meant to be a.
Metadata Xiangming Mu. What is metadata? What is metadata? (cont’) Data about data –Any data aids in the identification, description and location of.
Product Feeds. What is a Product? In marketing terms, a product is an item, service or idea that is for sale Examples are: A flight with set dates and.
ScreenPlay Director Training By Erik Collett
Lecture 15 Introduction to Web Services Web Service Applications.
Approaches to Home Connectivity T Research Seminar on Telecommunications Business Marko Berg.
ScreenPlay TV Link Training By Erik Collett
XML Web Services Architecture Siddharth Ruchandani CS 6362 – SW Architecture & Design Summer /11/05.
FILES AND ASSETS PANELS
UPnP Introduction 教授 : 逄愛君 組員 : 資訊三 張弘霖 資訊四 陳錦翰 資訊四 蔡旻諧.
Windows Media Connect and PlaysForSure for Network Devices Jason Flaks Program Manager Digital Media Division microsoft.com Microsoft Corporation.
1 PL\SQL Dev Templates. 2 TEMPLATE DEFINITION Whenever you create a new program unit, its initial contents are based upon a template which contains pre-defined.
OAI Overview DLESE OAI Workshop April 29-30, 2002 John Weatherley
UPnP AV Architecture - Generic Interface Design And Java Implementation Andreas BobekUniversity of Rostock Faculty of Computer Science and Electrical Engineering.
Basic Device Definition Version 1.0 Date: For UPnP™ Version 1.0 (Status: Template Design Complete) File from: BasicDevice-1.0.pdf Author: Scott.
XP Tutorial 7 Creating a Flash Web Site. XP New Perspectives on Macromedia Flash 82 Objectives Plan and create a Flash Web site Create a Flash template.
JDF – An Overview.
Module: Software Engineering of Web Applications Chapter 2: Technologies 1.
.NET Mobile Application Development XML Web Services.
Introduction to Web Services Presented by Sarath Chandra Dorbala.
Slide 1 2/22/2016 Policy-Based Management With SNMP SNMPCONF Working Group - Interim Meeting May 2000 Jon Saperia.
F2F April 7, Enumeration & Connection Management presented by Chris Pane.
DEVELOPING WEB SERVICES WITH JAVA DESIGN WEB SERVICE ENDPOINT.
CEA 2014 Overview April 18, 2007 Mark R. Walker PhD Sr. Viiv TM Planning Architect Digital Home Group Intel.
Sharing makes life beautiful ARKUDA STB SOLUTION.
SOAP, Web Service, WSDL Week 14 Web site:
Understanding the Value and Importance of Proper Data Documentation 5-1 At the conclusion of this module the participant will be able to List the seven.
Preview of Universal Plug and Play RTLAB 배대호
  Computer Fundamentals Training   Windows 8 Intermediate.
Java Web Services Orca Knowledge Center – Web Service key concepts.
Sabri Kızanlık Ural Emekçi
Sharing makes life beautiful
An Overview of MPEG-21 Cory McKay.
Network Connected Devices
Real Time Streaming Protocol
Enhancements to Mesh Discovery
Digital television systems - (DTS)
Presentation transcript:

MediaServer:1 Device Template Version 1.01 Date: June 25, 2002 For UPnP™ Version 1.0 Status: Standardized DCP File from: MediaServer1.0.pdf Author: John Ritchie (Intel)

Overview and Scope (I) The MediaServer template defines a general-purpose device that can be used to instantiate any Consumer Electronic (CE) device that provides AV content (e.g. media) to other UPnP devices on the home network. It is based on the UPnP AV Architecture Framework (described in another document). –It exposes its content via the Content Directory service (refer to the Content Directory Service Template for details). –As such, the MediaServer can handle any specific type of media, any data format, and transfer protocol. Example instances of a MediaServer include –traditional devices such as VCRs, CD Players, DVD Players, audio-tape players, still-image cameras, camcorders, radios, TV Tuners, and set- top boxes. –Additional examples of a MediaServer also include new digital devices such as MP3 servers, PVRs, and Home Media Servers such as the PC.

Overview and Scope (II) A full-featured MediaServer device provides clients with the following capabilities: –Enumerate and query any of the content that the MediaServer can provide to the home network. –Negotiate a common transfer protocol and data format between the MediaServer and target device. –Control the flow of the content (e.g. FF, REW, etc). –Copy (import) content to the MediaServer from another device. This device template does not provide: –The ability to renderer AV content.

MediaServer Device MediaServer:1 Functional Diagram – The un-shaded blocks represent the UPnP services that are contained by a MediaServer device. The shaded blocks represent various device-specific modules that the UPnP services might interact with. However, the internal architecture of a MediaServer device is vendor specific.

Device Definitions (I) Device Type –urn:schemas-upnp-org:device:MediaServer:1 Device Model –MediaServer:1 products must implement minimum version numbers of all required embedded devices and services specified in the table below. DeviceTypeRootReq. or Opt. [1] ServiceTypeReq. or Opt. [1] Service ID [2] MediaServer:1YESRContentDirectory:1.0RContentDirectory ConnectionManager:1.0RConnectorManager AVTransport:1.0OAVTransport Non-standard services embedded by an UPnP vendor go here. XTBD Non-standard devices embedded by a UPnP vendor go here. TBDX [1] R = Required, O = Optional, X = Non-standard. [2] Prefixed by urn:upnp-org:serviceId:.

Device Definitions (II) Description of Device Requirements –Each implementation of the MediaServer requires a Content Directory and ConnectionManager service. The Content Directory service allows Control Points to discover information about the AV content that is available from the device. The Connection Manager is used to enumerate and select a particular transfer protocol and data format to be used for transferring the content. –Additionally, the Connection Manager also allows Control Points, such as a home network management application, to discover useful information about the content transfers that the device is actively participating in. –Such information could be useful to a Quality Of Service capability, which may be defined in the future. –The existence of the AVTransport service depends on the transfer protocols that are supported the device. –The Connection Manager specification includes a table that identifies which transfer protocols require an AVTransport to be implemented on the MediaServer. If an implementation of the MediaServer supports any of these transfer protocols, then it must implement the AVTransport service. However, no AVTransport instances will be instantiated until a connection is made using one of those transfer protocol.

Device Definitions (III) Relationships Between Services –The Connection Manager’s PrepareForConnection() action provides the trigger point for creating new instances of the AVTransport service. –When a new connection is established (one that requires an instance of the AVTransport on the MediaServer, which is determined by the selected transfer protocol), the PrepareForConnection() action returns the InstanceId of the AVTransport that is bound to that connection. This instance is used by the Control Point to control the flow (e.g. Play, FF, REW, Seek, etc) of the content to the network. As described in the AVTransport specification, each instance of the AVTransport service operates independently.

Theory of Operation (I) MediaServer devices are used in conjunction with one or more MediaRenderer device(s) to allow a Control Point to discover entertainment (AV) content (e.g. video, music, images, etc) on the MediaServer and to render that content on any appropriate MediaRenderer within the home network. In general terms, the process begins with the Control Points discovering MediaServer and MediaRenderer devices within the home network. The Control Point interacts with a MediaServer(s) to locate a desired piece of content (e.g. a movie, a song, a playlist, a photo album, etc). After the content has been identified, the Control point needs to identify a common transfer protocol and data format that can be used to transfer the content from the MediaServer to the desired MediaRenderer.

Theory of Operation (II) After these transfer parameters have been established, the Control Point controls the flow of the content (e.g. Play, Pause, Stop, Seek, etc.). –Depending on the selected transfer protocol, these flow control operations are sent either to the MediaServer or MediaRenderer, but not both. The actual transfer of the content is performed directly by the MediaServer and MediaRenderer. The content transfer happens independently from the Control Point and does not involve UPnP itself at all. The Control Point uses UPnP to setup the transfer of the content, but the transfer is performed using a transfer protocol other than UPnP.

Theory of Operation (III) Discovery –Control Points can discover MediaServer devices using the standard UPnP SSDP-based device discovery mechanism to search for any device that is a “MediaServer” device class including root devices and/or embedded devices.

Theory of Operation (IV) Locating Desired Content: –Control Points use the MediaServer’s ContentDirectory service to locate desired content. –The ContentDirectory service exposes both a search capability and a browse capability. Searching is useful when the Control Point (via the end-user) knows something about the content it wants to find (e.g. its name, artist, type, date created, etc). Browsing is useful for blindly discovering what content the device has to offer. Each content item that is referenced by the ContentDirectory service includes various information about that content including the transfer protocol(s) and file format(s) that the MediaServer can use to transfer the content to the MediaRenderer.

Theory of Operation (V) Preparing to Transfer the Content –After the desired content has been identified, the Control Point needs to determine which transfer protocol and data format should be used to transfer the content from the MediaServer to the MediaRenderer. Transfer protocol examples include –IEEE-1394, HTTP GET, RTSP/RTP, etc. Data format examples include –MPEG2, MPEG4, MP3, WMA, JPEG, etc. –The Control Point makes this determination by comparing the content’s protocol/format information (obtained via the MediaServer’s ContentDirectory Service) with the protocol/format information obtained via the MediaRenderer’s ConnectionManager::GetProtocolInfo() action.

Theory of Operation (VI) Preparing to Transfer the Content (cont’d) –After the transfer protocol and data format have been identified, the Control Point uses the ConnectionManager::PrepareForConnection() action on each device to inform the device that the specified protocol/format are about to be used. –Depending on which transfer protocol was selected, the PrepareForConnection() action on either the MediaServer or MediaRenderer will return an AVTransport InstanceID to the Control Point. This AVTransport InstanceID is used by the Control Point to control the transfer of the content (e.g. Play, Pause, Stop, Seek, etc).

Theory of Operation (VII) Preparing to Transfer the Content (cont’d) –Depending on which transfer protocols are supported by the device (e.g. devices that only support HTTP GET), a MediaServer and/or MediaRenderer may choose to NOT implement the PrepareForConnection() action. In this case, the Control Point may not have been able to obtain an AVTransport InstanceID from either device. When this happens, the Control Point uses an AVTransport InstanceID of 0 (zero). If the MediaRenderer has implemented the AVTransport Service, the Control Point should use it for all AVTransport actions. Otherwise, AVTransport actions should be sent to the MediaServer device. Refer to the ConnectionManager Service for more information.

Theory of Operation (VIII) Controlling the Transfer of the Content –Regardless of which device provided the AVTransport InstanceID, the Control Point uses the AVTranport Service on that device to control the flow of the content. For example, to begin transferring the content, the Control Point invokes the AVTransport::Play() action. To skip to a specific location within the content, the Control Point invokes the AVTransport::Seek() action. In most cases, the choice of AVTransport actions that are actually invoked will likely be directed by the end-user as they interact with the Control Point’s UI. Refer to the AVTransport Service for additional details of these and other AVTransport actions.

XML Service Description (I) 1 0 base URL for all relative URLs urn:schemas-upnp-org:device:MediaServer:1 short user-friendly title manufacturer name URL to manufacturer site long user-friendly title model name model number URL to model site manufacturer's serial number uuid:UUID Universal Product Code

XML Service Description (II) image/format /horizontal pixels vertical pixels color depth URL to icon XML to declare other icons, if any, go here urn:schemas-upnp-org:service:ContentDirectory:1 urn:upnp-org:serviceId:ContentDirectory URL for control URL for eventing

XML Service Description (III) urn:schemas-upnp-org:service:ConnectionManager:1 urn:upnp-org:serviceId:ConnectionManager URL to service description URL for control URL for eventing urn:schemas-upnp-org:service:AVTransport:1 urn:upnp-org:serviceId:AVTransport URL for control URL for eventing Declarations for other services added by UPnP vendor (if any) go here

XML Service Description (IV) urn:schemas-upnp-org:service:ConnectionManager:1 urn:upnp-org:serviceId:ConnectionManager URL to service description URL for control URL for eventing urn:schemas-upnp-org:service:AVTransport:1 urn:upnp-org:serviceId:AVTransport URL for control URL for eventing Declarations for other services added by UPnP vendor (if any) go here Description of embedded devices added by UPnP vendor (if any) go here URL for presentation