160 likes | 295 Views
Audio Video Update. John Ritchie Intel Co-Chair Audio Video Committee. Overview. UPnP ™ AV Architecture (v1.0) v2.0 Extensions Demo Questions. UPnP ™ AV (v1.0) Architecture (Completed June 2002). Content Distribution (a.k.a. Playing available content anytime, anywhere).
E N D
Audio Video Update John Ritchie Intel Co-Chair Audio Video Committee
Overview • UPnP™ AV Architecture (v1.0) • v2.0 Extensions • Demo • Questions
UPnP™ AV (v1.0) Architecture(Completed June 2002) Content Distribution (a.k.a. Playing available content anytime, anywhere)
UPnP™ AV ArchitectureContent Playback Scenarios • Various User Scenarios • Watch a video on a television • Listen to music on a stereo system • Show digital photos on (Electronic Picture Frame) • One Common Theme • Content on Device A • Rendered on Device B • Control remotely by user Browse - Select - Play
UPnP™ AV ArchitectureDevice Interaction Model (Playback) VCR Camcorder STB Digital Camera Control Point Standard UPnP Actions Standard UPnP Actions Home LAN Media Server Media Renderer DVD Player CD Player Tuner PC TV MP3 Player EPF Speakers Stereo Clock Radio PC Content Directory Rendering Control Connection Manager Connection Manager AV Transport (Optional) AV Transport (Optional) Scheduled Recording Out-of-band Transfer Protocol
UPnP™ AV ArchitectureUPnP AV Services (Playback) • Content Directory • Browse/search content items and containers • Includes content meta-data (title, creator, resolution, …) • Manage content (e.g. create playlists, add new items,…) • Rendering Control • Control rendering characteristics (volume, brightness, …) • Connection Manager • Enumerate supported transfer protocols and data formats • Enumerate existing UPnP AV streams • AV Transport • Control content movement/position (play, pause, seek,…) • Provided by Server or Renderer based on selected protocol
UPnP™ AV ArchitectureTypical Control Algorithm (Playback) Discover AV devices UPnP™ SSDP Locate desired content Content DirectoryService Identify a common transfer protocol and data format Connection ManagerService Initiate and control the transfer AV TransportService Rendering ControlService Control how content is rendered
UPnP™ AV v2.0 Highlights • Full backward compatibility with UPnP AV v1.0 • Existing v1.0 Control Points still work with new V2 devices • Editorial clarifications to existing v1.0 functionality • CDS::ImportResource() • CM::PrepareForConnection(), ConnectionID=0 • Various improvements to many v1.0 features. • Standardized usage rules for the 4th field of “protocolInfo” • New features • Automatic recording of content available in the future • Support for premium (DRM protected) content • Changing AV Renderers
UPnP™ AV Architecture EPG-based Content Creation (a.k.a. Recording programs that will be available in the future)
UPnP™ AV ArchitectureDevice Interaction Model (Recording) Control Point Standard UPnP Actions Media Server Home LAN Content Directory Connection Manager Media Renderer AV Transport (Optional) Scheduled Recording Out-of-band Transfer Protocol
UPnP™ AV ArchitectureUPnP AV Services (Recording) • Scheduled Recording Service • Create individual recording schedules • Each “Record Schedule” generates one or more “Record Tasks” • Browse current Record Schedules/Tasks • Modify current Record Schedules/Tasks • Updated status event to interested Control Points
UPnP™ AV v2.0 SpecificationsProjected Schedule • “Preliminary Design Complete” status (v0.80) • November 2004 • “Design Complete” status (v0.90) • December 2004 • Final adoption • Q1 2005
Moving Forward • UPnP™ AV v3.0 • Start defining AV v3.0 content in January 2005 • Continue to grow UPnP™ AV v1.0/v2.0 momentum • Periodic Plugfests 2 to 4 times per year • Next Plugfest in Q2 ’05 – Location TBD • Getting Involved • UPnP™ AV WC mail list: av@forum.upnp.org • Participate in the next Plugfest • Telecons: Twice per week (Tues and Thurs) • Face-to-Face meetings: Every 4 to 6 weeks • Individual contacts: • John Ritchie (Intel) at john.g.ritchie@intel.com • Geert Knapen (Philips) at geert.knapen@philips.com