UNLIMITED FREE ACCESS TO THE WORLD'S BEST IDEAS

SUBMIT
Already an Engineering360 user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your Engineering360 Experience

Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

ISO/IEC 29341-3-12

Information technology – UPnP Device Architecture – Part 3-12: Audio Video Device Control Protocol – Content Directory Service

active, Most Current
Buy Now
Organization: ISO
Publication Date: 1 November 2008
Status: active
Page Count: 98
ICS Code (Interface and interconnection equipment): 35.200
scope:

Overview and Scope

This service template is compliant with the UPnP Device Architecture version 1.0. It defines a service type referred to herein as Content Directory Service (CDS).

Introduction

Many devices within the home network contain various types of content that other devices would like to access (e.g. music, videos, still images, etc). As an example, a "Media Server" device might contain a significant portion of the homeowner's audio, video, and still-image library. In order for the homeowner to enjoy this content, the homeowner must be able to browse the objects stored on the Media Server, select a specific one, and cause it to be "played" on an appropriate rendering device (e.g. an audio player for music objects, a TV for video content, an Electronic Picture Frame for still-images, etc).

For maximum convenience, it is highly desirable to allow the homeowner to initiate these operations from a variety of UI devices. In most cases, these UI devices will either be a UI built into the rendering device, or it will be a stand-alone UI device such as a wireless PDA or tablet. In any case, it is unlikely that the homeowner will interact directly with the device containing the content (i.e. the homeowner won't have to walk over to the server device). In order to enable this capability, the service device needs to provide a uniform mechanism for UI devices to browse the content on the server and to obtain detailed information about individual content objects. This is the purpose of the Content Directory Service

The Content Directory Service additionally provides a lookup/storage service that allows clients (e.g. UI devices) to locate (and possibly store) individual objects (e.g. songs, movies, pictures, etc) that the (server) device is capable of providing. For example, this service can be used to enumerate a list of songs stored on an MP3 player, a list of still-images comprising various slide-shows, a list of movies stored in a DVD-Jukebox, a list of TV shows currently being broadcast (a.k.a an EPG), a list of songs stored in a CD-Jukebox, a list of programs stored on a PVR (Personal Video Recorder) device, etc. Nearly any type of content can be enumerated via this Content Directory service. For those devices that contain multiple types of content (e.g. MP3, MPEG2, JPEG, etc), a single instance of the Content Directory Service can be used to enumerate all objects, regardless of their type.

Document History

ISO/IEC 29341-3-12
November 1, 2008
Information technology – UPnP Device Architecture – Part 3-12: Audio Video Device Control Protocol – Content Directory Service
Overview and Scope This service template is compliant with the UPnP Device Architecture version 1.0. It defines a service type referred to herein as Content Directory Service (CDS). Introduction...

References

Advertisement