GGIE TF/UseCases/User Discovery

From Web and TV IG

User Content Discovery

How these fit into GGIE

These use cases are part of a larger set of GGIE Use Cases being worked on by the GGIE taskforce. This page covers user cases from the user perspective of finding content either through search, an EPG (electronic program guide), media library, or other means.

Abstract

This document describes use cases for the glass to glass digital video ecosystem ranging from capture through to viewing

Status of this document

This is a public working in draft collection of use cases that the GGIE task force is discussing and exploring. It has no official standing of any kind and note represent the support or consensus of any standards organization or contributor. GGIE is a taskforce of the W3C Public Web & TV Interest Group

Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].


Use Cases

User Content Discovery-UC-1 User Search for Content Including Client Information

Extends

Streaming-UC-1b Basic Streamed Content Selection

Description

From Streaming-UC-1b: A user uses a search application to search for a specific content asset they wish to view by using one or more search terms (e.g. title, actors, director, language, etc.)
  1. This UC includes potential for a multihoming environment
  2. The client appends search criteria based on its capabilities (e.g. decoder(s) and formats supported, existing content licenses, DRM support, etc.).
  3. Privacy concerns beyond user criteria/settings include client criteria/settings, network settings
  4. The search application obtains a list of sources from which that content item meeting the combined user and client search criteria can be streamed. The list should include
    1. Content in any format/resolution, DRM, etc., the client supports
    2. Content from sources for which the client has a license
    3. Content from sources for which the client does not have a license should be distinguishable by the search app
    4. Each source may include a cost to stream the asset including, when available, the cost to obtain a license to content the client does not currently have a license to
  5. Streaming-UC-1b describes the balance of actions that take place.


Actors

  • All actors from Streaming-UC-1b
  • Client


Dependencies

  • Streaming-UC-1b


Gaps

  • No known standard for device profiles (client criteria) including playback capabilities, network connection capabilities, offline/online capabilities, in home/out of home capabilities, etc. DLNA may define some device profiles for in-home discovery that could be extended.
  • No known standard to transport device profiles as part of search/discovery
  • No known standard to respond to request that includes device profiles


Notes

  • This use case adds client content capabilities to the search criteria.
  • Content ID structure or its associated metadata will need to include a means to differentiate content based on client capabilities included in the search.


Author(s)

Bill Rose, brose@wjrconsulting.com


History

3-18-2015 Bill Rose created UC
4-8-2015 Bill Rose Updated
9-14-2015 Bill Rose changed UC title from "User Discovery..." to "User Content Discovery..."


User Content Discovery-UC-2 User Search for Content Using Second Screen as UI for TV

Extends

User_Content_Discovery-UC-1 User Search for Content Including Client Information
Streaming-UC-1b Basic Streamed Content Selection


Description

  1. A user uses a second screen (tablet, phone) to launch application(s) on their TV
  2. The touch screen becomes the UI for the TV search app directly controlling the TV cursor and making selections
  3. The user sets the search criteria using one or more search terms as in User Discovery-UC-1
  4. The TV client appends search criteria based on its capabilities as in User Discovery UC-1
  5. User Discovery-UC-1 describes the balance of the actions with the TV as client and display and the second screen as input device


Actors

  • User
  • TV Client
  • Second screen with DASH or equivalent application to launch TV application
  • Second screen application to forward touch screen movements/touches to the TV
  • TV search application with ability to use second screen touch UI as input
  • Content source
  • Content stream source
  • Content asset


Dependencies

User_Content_Discovery-UC-1 User Search for Content Including Client Information
Streaming-UC-1 Basic Streamed Content Viewing
Streaming-UC-1b Basic Streamed Content Selection


Gaps

  • It is unclear if there exists a method to convey second screen user input without second screen display, user/client information

Notes

  • This use case adds second screen with ability to launch TV application(s) and as input device for TV
  • It is unclear if this should remain a standalone UC, be included in another UC, or is out of scope

Author(s)

Bill Rose, brose@wjrconsulting.com

History

4-1-2015 Bill Rose created UC
4-8-2015 Bill Rose updated UC
9-14-2015 Bill Rose changed UC title from "User Discovery..." to "User Content Discovery..."; updated links

User Content Discovery-UC-3 User Search for Content For Multiple Devices With Different Client Capabilities

Extends

User_Content_Discovery-UC-1 User Search for Content Including Client Information
Streaming-UC-1 Basic Streamed Content Viewing
Streaming-UC-1b Basic Streamed Content Selection

Description

  1. A user has multiple A/V clients (collectively the “target device(s)”) with differing capabilities
  2. The user wishes to locate specific content that can be viewed on one or more of the target devices
  3. Search device and Target devices may connect in a multihoming environment (e.g. the devices may be connected to different ISPs)
  4. The user sets the search criteria using one or more search terms (e.g., title, actors, director, language etc.) (ref: Search-UC-1b)
  5. The user specifies the target A/V device(s) using friendly names (e.g. living room TV, Bob’s tablet, Sue’s smart phone)
  6. The capabilities of each client are appended to the search criteria as in User Discovery UC-1 along with its routing (connection) information
  7. The search application obtains a list of sources from which that (those) content item(s) can be streamed and that meets the user search criteria and that of each of the target device clients along with information adequate to associate the returned source(s)/content item(s) with the specific clients capable of viewing it. Each source/client combination may include a cost to stream the asset
  8. The user selects the source and content they wish to view and the device they wish to view it on. Payment, if required, may be made by
    1. the search device
    2. the target device
  9. Assuming successful conclusion of the payment, the rest of the use case picks up from step 3 of Search-UC-1 with the selected Target Device as the Viewing Device

Actors

  • User
  • Search client (connected to ISP-A)
  • Viewing client(s) (connected to ISP-A or a different ISP)
  • Search application
  • Viewing application
  • Content source
  • Content stream source
  • Content asset


Dependencies

  • User Content Discovery-UC-1
  • Search-UC-1
  • Streaming-UC-1b


Gaps

  • Search results cannot express/disambiguate different offers for the same basic content
  • Search results need to express cost options/extended cost options such as ad versus fee supported content; sponsored content (e.g. group membership); bandwidth costs, etc.


Notes

  • This use case builds on User Discovery-UC1 by appending the capabilities of multiple clients to the search criteria.
  • If filtering is to be done by the client/user then all necessary information to associate the source/asset to the search criteria must be included in the search results which may result in one or more additional gaps.


Author(s)

Bill Rose, brose@wjrconsulting.com


History

4-2-2015 Bill Rose created UC
4-8-2015 Bill Rose updated UC
9-14-2015 Bill Rose changed UC title from "User Discovery..." to "User Content Discovery..."; updated links

User Content Discovery-UC-4 User Asks for Content Recommendations

Extends

User_Content_Discovery-UC-1 User Search for Content Including Client Information

Description

From User Content Discovery-UC-1: A user uses a recommendation application to discover content assets they wish to view by using one or more search terms (e.g. title, actors, director, language, etc.), by identifying other content assets to guide a search, or based on their previous search and viewing behavior.
  1. The recommendation application can be based on the client or a remote device (or both)
  2. The recommendation application can use content-based recommendations, collaborative (user-based) recommendation, or some combination thereof
  3. Privacy concerns can arise around storage or exposure of content recommendations and content viewing/searching history
  4. User Discovery-UC-1 describes the balance of actions that take place.

Actors

  • All actors from User Content Discovery-UC-1
  • Recommendation application

Dependencies

  • User Content Discovery-UC-1
  • Search-UC-1
  • Streaming-UC-1b


Gaps

Notes

  • This use case builds on User Content Discovery-UC1 by appending the capabilities of multiple clients to the search criteria.
  • If filtering is to be done by the client/user then all necessary information to associate the source/asset to the search criteria must be included in the search results which may result in one or more additional gaps.


Author(s)

Bill Hofmann, bill.hofmann@dolby.com


History

9-14-2015 Bill Hofmann created UC

-->

Retrieved from "https://www.w3.org/2011/webtv/wiki/index.php?title=GGIE_TF/UseCases/User_Discovery&oldid=3860"