User talk:Rberkoff

From Web and TV IG

Use Case: DLNA/UPnP Home Network Enabled User-Agent (Browser)

Submitter(s): Samsung Electronics (Russell Berkoff)

Description:

Need/justification:

  • UPnP/DLNA do not (by scope/tradition) standardize user interface control. However, the combination of HTML markup and Javascript allow both access to UPnP devices and access to very capable user interface resources.
  • The following use-case scenarios are divided into two sets:
    • The HTML5 User-Agent commands other home network devices. For example:
      • Controlling home-automation devices such as window shades or (HVAC) room temperature.
      • Directing a UPnP/DLNA ScheduledRecording device to record a show.
      • Directing a UPnP/DLNA MediaRending device to play content stored from a UPnP/DLNA MediaServer.
      • Directing a UPnP/DLNA MediaRendering device to play live content from a UPnP/DLNA compliant Settop Box.
      • Controlling MediaRenderer attributes: Brightness, Contrast, Volume, etc.
    • The HTML5 User-Agent acts as a UPnP/DLNA HomeNetwork device. For example:
      • Viewing available content on a UPnP/DLNA MediaServer.
      • Playing content from a UPnP/DLNA MediaServer.
      • Viewing EPG data on a UPnP/DLNA MediaServer.
      • Tuning and playing live programs from a UPnP/DLNA enabled Settop Box.
      • Viewing recording Status from a UPnP/DLNA ScheduledRecording (PVR) device.
      • Selecting and playing recorded content from a UPnP/DLNA ScheduledRecording device.
  • Why were you not able to use only existing standards to accomplish this?
    • HTML User-Agents do not provided the abstractions necessary for Javascript to issue discover and issue commands to home network devices.
    • Basic access methods to home network devices need to be standardized so that developers can implement pages to control UPnP/DLNA devices using Javascript/HTML.
  • What might you suggest could be standardized?
    • Provide generic access methods to enable a HTML5 User-Agent to discover and command home network devices.
    • Provide extensions to the HTML5 for the <video>, <audio> elements to allow HTML5 to comply with DLNA Media Transport Requirements (mainly DLNA specific headers).
    • Provide access and privacy controls for untrusted pages accessing home network devices.
    • Allow pages to control future UPnP/DLNA devices where the comand sets are not currently known.
    • Allow pages to discover functional differences (optional functionality) that may be implemented in some but not all UPnP/DLNA ecosystem devices.

Dependencies:

  • This use-case provides the basic framework for generic access to home network devices. It is "agnostic" towards the underlying functionality of the devices being controlled.