Device Description Repository Requirements 1.0

2.1.1 Overview

This use case describes a basic scenario where an end-user consumes web content from their device. Prior to delivery, the requesting device (or the end-user) provides the means for a Content Provider to identify the device, accurately determine the supported properties of that device by utilizing the device description contained by the device repository. The Content Provider can then deliver content in a form most suitable for that device.

2.1.2 Actors

End User: The end-user uses their device to consume content or services that they request. The end-user expects a good user experience when consuming content from different Content Providers, e.g. served content is displayed correctly on the device.

Content Provider: The Content Provider provides content and services for end-user consumption. The Content Provider has the ability to determine the capabilities of an end-user's device and to tailor the content appropriately for that device. The Content Provider utilizes the available device description information to provide a good experience for end-users consuming their content;

Device Vendors: The Device Vendor develops device descriptions for their devices. These device descriptions typically describe the supported capabilities of a device, e.g. screen size, camera capabilities, markup languages etc). The Device Vendor makes available and maintains for accuracy device descriptions for public usage, e.g. by Content Providers.

2.1.3 Pre-conditions

Device Description Repository: A DDR is accessible and allows for queries and retrievals of device description information. The DDR contains device descriptions that are accurate and a true representation of a devices capabilities;

End-user: The end-user has a device for which a device description is available and which can be queried from the DDR.

Content Provider: The Content Provider has the ability to identify the end-user's device and is able to query the DDR to retrieve device description information for that device. The Content Provider utilizes the resulting device description information for the tailoring of their content and services.

Device Vendor: The Device Vendor develops, manages (e.g. updates existing device profiles when devices are upgraded) and makes available through the DDR accurate device descriptions for their devices.

2.1.4 Post-conditions

End-User: The end-user consumes a tailored service optimized for the capabilities of their device and has good user experience.

Device Vendor: The Device Vendor provides device descriptions for their devices allowing, for example, Content Providers to accurately tailor content utilizing the capabilities of the device. In essence the Device Vendor provides added value to the Content Provider's services

Content Provider: Through the available device description the Content Provider determines a device's supported capabilities. The Content Provider serves content that is tailored appropriately for the capabilities of the end-user's device.

2.1.5 Normal Flow

1. The end-user launches the browser from their device, navigates available Content Provider services, then selects a link (URL) that initiates a request for a particular service;

2. During the request for service the end-user's device provides its identity (e.g. through the supported User Agent Header) to the Content Provider;

3. The Content Provider receives the request for service and the identity of the requesting device;

4. Using the identity of the device the Content Provider queries the DDR to determine one or more capabilities supported by the device;

5. When the DDR receives the query it performs a look-up of available device descriptions;

6. The DDR returns the results of the query, which are used by the Content Provider to tailor the content in a manner best suited for the device;

7. The Content Provider then serves tailored content to the end-user;

8. The user consumes the served content and receives good user experience.

2.1.6 Alternative Flow 1: Device Description not available

1. Same as Normal flows 1 to 5;

2. The DDR is unable to identify the appropriate device description and is therefore unable to return a result following the query;

3. The Content Provider needs to take appropriate course of action, e.g. either serves default content that is adequate for the range of devices;

4. The user consumes the served content and may not receive the best user experience;

2.1.7 Alternative Flow 2: Capability not identified within a device description

1. Same as Normal flows 1 to 5;

2. The DDR identifies the appropriate device description but it unable to determine the requested capability information (e.g. the DDR is unable to determine the support of a specific streaming media format) and is therefore unable to return a result following the query;

3. Same as Alternative flow 1 steps 1 and 2;

2.1.8 Alternative Flow 3: Utilizing available device description to allow content subscription

1. The end-user attempts to subscribe to a service offered by the Content Provider;

2. Same as Normal flows 1 to 5;

3. The Content Provider authorizes end-user subscription and serves tailored content to the end-user;

4. Same as Normal flows 8;

2.1.9 Alternative Flow 4: Utilizing the device repository for tailoring pushed content

1. Before delivering content (e.g. news update) via a Push message to an end-user (i.e. consumer of the content), the Content Provider queries the DDR to determine one or more capabilities supported by the device, which is already known to the Content Provider;

2. Same as Normal flows 2 to 6;

3. The Content Provider then pushes the tailored content to the end-user.

2.2.1 Overview

This use case describes a basic scenario where a Content Adaptor tailors single representation of content (i.e. content that has not been specifically adapted or tailored) for a specific range of devices. The Content Adaptor requests from the DDR a device description information for a specific range of device and based on results of the request tailors the content accordingly.

2.2.2 Actors

Content Developer: The Content Developer develops and makes available a primary source of content for end-user consumption. The Content Developer develops content that is not tailored or best suited for particular devices but relies on third parties such as Content Adaptors to perform the required content tailoring

Content Adaptor: The Content Adaptor utilizes device descriptions as part of their content adaptation processes. The Content Adaptor has the ability to determine the capabilities of a range of devices and tailor and adapt primary source of content in a manner appropriate for the capabilities associated with different ranges of device. The Content Adaptor needs to be confidant that the results to their query is accurate (i.e. the device descriptions represent the exact capabilities of a device) and provides enough information to allow for quality adaptations.

2.2.3 Pre-conditions

Device Description Repository: A DDR is accessible and allows for queries and retrievals of device description information. The DDR contains device descriptions that are accurate and a true representation of a devices capabilities;

Content Adaptor: The Content Adaptor queries the DDR and utilizes the resulting device description information to tailor and adapt Content Developer's primary sources of content. The Content Adaptor has the ability to request (and retrieve) from the DDR information pertaining either individual devices or a specific device range. The Content Adaptor has the ability to make a request pertaining to either the whole of a specific device description range or part (e.g. screen size) of a device description range.

2.2.4 Post-conditions

Content Adaptor: Using the results of the DDR query the Content Adaptor tailors the Content Developer's primary source of content in a manner suitable for a specific range of devices.

End-user: The end-user consumes a tailored service optimized for the capabilities of their device and has good user experience.

2.2.5 Normal Flow

1. The Content Adaptor initiates a query to the DDR requesting a device description for a specific range of device;

2. When the DDR receives the query it performs a look-up of available device descriptions;

3. When the appropriate device description has been identified the DDR returns the device description to the Content Adaptor;

4. The Content Adaptor receives the device description and tailors the content in a manner best suited for that range of device;

5. The Content Adaptor may either provide the tailored content back to the Content Developer or provide the tailored content to third party service provider, e.g. Mobile Operator.

6. The tailored content is consumed by end-users and they receive good user experience.

2.2.6 Alternative Flow: Query of device description

1. The Content Adaptor initiates a query to the DDR requesting specific information pertaining to a device description for a specific range of device, e.g. to determine whether a device range supports streaming or video camera;

2. Same as Normal flow 2;

3. When the appropriate device description has been identified the DDR returns the requested information as determined by a query of the appropriate device description;

4. Same as Normal flows 1 to 6.

2.3.1 Overview

This use case describes the scenario where a Device Vendor (or other appropriate actors such as an open-source Framework Provider) creates and makes available a new device description, which is an accurate description of the supported capabilities of a device. The creation of the new device description may be because of the development of a new device or because of the version of an existing device has upgraded.

2.3.2 Actors

Device Vendor: The Device Vendor develops device descriptions for their devices. These device descriptions typically describe the supported capabilities of a device, e.g. screen size, camera capabilities, markup languages etc). The Device Vendor makes available and maintains for accuracy device descriptions for public usage, e.g. by Content Providers.

2.3.3 Pre-conditions

Device Vendor: The Device Vendor develops, manages (i.e. updates existing device profiles when devices are upgraded) and makes available through the DDR accurate device descriptions for their devices.

Device Description Repository: A DDR is accessible and allows for queries and retrievals of device description information. The DDR provides the ability for authorized users to upload new device descriptions and also provides the ability for existing device descriptions to be managed (e.g. extended, modified, archived).

2.3.4 Post-conditions

Device Vendor: The Device Vendor generates an accurate device description and has uploaded the device description to the DDR

Device Description Repository: The [DDR] has stored and is made aware of the device description (i.e. the [DDR] is able to query the information), which is now available for public consumption, e.g. Content Adaptors and Mobile Operator's can query the information.

2.3.5 Normal Flow

1. A Device Vendor creates a new device description and uploads it to the DDR;

2. The DDR receives the new device description and stores the device description in the appropriate folder (e.g. Vendor specific folder, Validated folder etc);

3. The DDR may also manage existing device descriptions during the upload of the new device description (e.g. the DDR may manage existing device descriptions and folders by archiving old versions of the same device repository;

4. The DDR then makes available the new device description for public consumption;

5. The Content Provider (or any actor requiring device description information) is able to query the new available device description.

2.3.6 Alternative Flow 1: Replacement of existing device description

1. The Device Vendor wishes to update one of their existing device descriptions (e.g. existing device description updated to indicate the support of new MIME type);

2. The Device Vendor creates a new version of an existing device description and uploads it to the DDR

3. The DDR replaces the old version with the new version of the device description. For backwards compatibility purposes the DDR applies version control including change history to each device description and each version of the device description;

4. Same as normal flows 2 to 5.

2.3.7 Alternative Flow 2: Modification and updating of existing device description

1. Same as Alternative flow 1 step 1;

2. The Device Vendor issues a request to the [DDR] to update an existing device description (e.g. a request to indicate the support of new MIME type);

3. When authorized (e.g. the actor requesting an update may need to submit personal details for audit and non-repudiation type purposes) the Device Vendor updates the existing device repository indicating support for the new MIME type;

4. Same as Alternative flow 1 steps 3 and 4

2.4.1 Overview

This use case describes the ability for a Content Adaptor (or any other actor within the device description ecosystem such as a Mobile Operator) to query the DDR for the purpose of obtaining information from the available device descriptions. Queries can be used to determine, for example, the number of devices that support video cameras, are members of defined sets (e.g. PDA) or other specific features. Information from queries can be used to assist content authors, marketing or other analysis such as determining the number of devices supporting certain types of markup.

2.4.2 Actors

Content Adaptor The Content Adaptor needs the ability to query the DDR to determine the number of devices in the market place that support one or more device capabilities to identify the number of primary source content adaptations they need to perform. The Content Adaptor expects the results of their query to be both accurate and trust worthy.

2.4.3 Pre-conditions

Content Adaptor: The Content Adaptor has the ability to query the DDR and receive the results of the query.

Device Description Repository: A DDR is accessible and allows for queries and retrievals of device description information.

2.4.4 Post-conditions

Content Adaptor: The Content Adaptor queries the DDR requesting information for number of devices that support, e.g. SVG-T. The Content Adaptor receives the results of their query and utilizes the results for their own purposes.

Device Description Repository: The DDR receives the request for information and queries all available device descriptions to identify the necessary capabilities. The DDR returns the results to the requesting actor.

2.4.5 Normal Flow

1. The Content Adaptor initiates query to the [DDR] to determine the number of devices that support XHTML;

2. When the [DDR] receives the request it performs a query of all available device descriptions;

3. When the query is complete the [DDR] returns the results (e.g. a list of device types that support XHTM) to the Content Adaptor;

4. The Content Adaptor receives and utilizes the results for their own purpose.

2.5.1 Overview

This use case describes a basic scenario where a Content Provider adapts content for delivery to a client device on the basis of information selected from two sources. The Device Description Repository Administrator determines that information within a specific concept domain shall be obtained from a source other than the default source. A Repository Provider makes the domain specific information available to the Content Provider. In this use case the domain specific information relates to menu layouts on devices.

2.5.2 Actors

End User: The End-User uses a device to consume content or services requested from the Content Provider. A good experience is expected when using the device. The End-User is particularly interested in the ease with which the content can be navigated.

Content Provider: The Content Provider provides content and services for end-user consumption. The content and services are tailored according to the capabilities of the end-user device. To enhance the quality of presentation for some end-users, the Content Provider has additional information about menu layouts on a particular set of devices, which is employed during adaptation.

Repository Provider: The Repository Provider provides a repository of device descriptions that are specific to a certain domain. In this use case, the domain relates to recommended menu layouts for each device, based on hands-on evaluations. The Repository Provider may offer access to this domain-specific repository on a commercial basis.

Device Description Repository Administrator: The DDRA provides an access point to developers to facilitate queries of the Device Repository. The DDRA can configure the access point to route specific queries (or subsets thereof) to specific sources of information.

2.5.3 Pre-conditions

End-user: The End-User has a device for which a description is available.

Content Provider: The Content Provider has the ability to identify the end-user's device and is able to associate an available device with a description for that device. The description for each device is obtained by merging information obtained from a public device repository with additional information from a private repository.

Repository Provider: The Repository Provider has provided a device repository to the Content Provider that contains a description appropriate to the End-User's device.

Device Description Repository Administrator: The DDRA has configured the Content Provider's Device Description Repository to access information from a default source, except for information relating to menu layouts, which will be obtained from an alternate source.

2.5.4 Post-conditions

Content Provider: The Content Provider serves content to the End-User's device that is tailored appropriately for the capabilities of the device. Navigation features of the content are tailored according to the information available in the private repository.

End-user: The End-User consumes tailored content optimized for the capabilities of the End-User's device. Navigation features are optimized for the device.

2.5.5 Normal Flow

1. The End-User launches the browser, navigates available Content Provider services, and then selects a link (URL) that initiates a request for a particular service.

2. During the request for service the end-user's device provides its identity to the Content Provider;

3. The Content Provider receives the request for service and the included identity of the device;

4. Using the identity of the device, the Content Provider obtains the device capabilities from a public available repository;

5. Using the identity of the device, the Content Provider obtains the optimal menu layouts from a private repository;

6. The Content Provider utilizes the retrieved device information to tailor the content in a manner best suited for the device, including the choice of menu layout (e.g. linear, hierarchical, animated, popup, softkey etc.).

7. The Content Provider then serves content to the end-user.

8. The End-User consumes the served content and receives good user experience