| ID | 3.0.1 |
| Title | SPICE Terminal and Device requirements |
| Expert | Matthieu Boussard (ALCATEL-LUCENT) |
| Priority | mandatory |
| Description | A SPICE device is a basic device, that the SPICE platform can use to some extent (e.g. for multimodal rendering), preferably in a trusted manner. A SPICE terminal is a special device, that embeds more SPICE software (in particular Dynamic Desktop), so that one can use it to access to the SPICE platform, get recommendations and launch services. a) To be eligible as a SPICE device, a device MUST be able to advertise its existence to the SPICE platform and therefore it MUST have a unique identifier in the SPICE world. The SPICE device MUST be able to provide information about its capabilities and status in the knowledge format of SPICE and it MUST be connected to the SPICE platform to provide this information. b) To be usable in a trusted manner, a device MUST be authenticable by the platform, i.e. it MUST have an IMS subscription and a GBA smartcard. If IMS is used, the SPICE device MUST run a SIP stack. c) To be eligible as a SPICE device usable in a multimodal delivery environment, a device MUST support services called activators or renderers. Activators are services that catch user inputs and renderers are services that are capable of rendering multimedia elements. If DRM support is needed for the delivery, the device MUST also run a SPICE DRM agent. d) To be eligible as a SPICE terminal, a SPICE device that is owned by a user (e.g. mobile phone, PDA, laptop) MUST support the installation and execution of SPICE foundation software (e.g. Dynamic Desktop, terminal SEE, etc.). e) In order to run the Dynamic Desktop in a SPICE terminal, this SPICE terminal MUST provide a screen output modality and a keyboard or a touch screen input modality. Moreover, the SPICE terminal MUST have a permanent connection to the SPICE platform to communicate with the Dynamic Desktop server part. |
| Rationale | Minimal requirements for devices to be candidate for being SPICE devices or terminals need to be set, as these terminals have to have some advanced features to be able to interact with the SPICE platform. |
| Type | non-functional |
| Depends on | 3.1.1 - Communication Model building and notification of its updates 5.2.2 - Service Execution Environment must support an execution environment on the terminal 6.2.1 - SPICE user authentication based upon the Generic Bootstrapping Architecture |
| Child dependencies | |
| Environment | |
| Other_info | |
| Category | device;technical |
| Subcategory | |
| Subcategory2 | |
| Scenario_scene | |
| SPICE_value | (seamless) service adaptation |
| Demo | |
| Keywords | terminal;device;Dynamic Desktop;terminal SEE;render;activator;DRM;IMS subscription;GBA smartcard |
| Home |