SPICE Logo

Category: technical

1.4.2Support Seamless handover between operators, devices and platforms
1.4.3Portability of user profile
1.4.5Offering user-generated content over the SPICE platform
1.4.6Dynamic, real-time creation of business networks
1.4.7Transparency and ease of use of content and service creation and deployment tools to all parties on the platform
1.4.8Steering of payment options in checkout module
2.1.1An integrated and technology-neutral methodology for development, lifecyle management and publication of middleware components.
2.1.2Generic Service Enabling Interfaces.
2.1.3Lifecycle and performance management.
2.2.1Service Repository for Semantically Described Services
2.2.2Service Description
2.2.3Query Evaluation by the Service Description Repository
2.2.4Multi-domain Service Repository Architecture
2.3.1Service experience depending on environment conditions
2.3.2The user is assisted in service selection
2.3.3Service creators are involved in the service adaptation process
2.4.1Seamless Service Delivery
2.4.2Operator Service Control flexibility
2.4.3Seamless Service Provisioning
3.0.1SPICE Terminal and Device requirements
3.1.1Communication Model building and notification of its updates
3.1.3User rules
3.1.4Terminal Synchronization
3.2.1Group management
3.2.2Dynamic Desktop features
3.2.3Dynamic Desktop context-aware service push
3.3.1Multimodal and multi-device delivery of services
4.0.1Mobile Ontology
4.1.5Management and Provision of Service and Situation-dependent User Data
4.2.1Discovery and Exchange of Distributed Context Information; subscription and polling
4.2.2Gathering, Aggregation and Interpretation from Multiple Distributed Context Sources, derivation of knowledge
4.2.3Context Queries based on Semantic Context Schema and QoC
4.2.7Learning and Recommending Algorithms
4.2.8Prioritized List of Alternatives, plausibility and dealing with imperfect situations
4.2.10Access, Storage, Processing and Distribution Rights
4.3.4Message Push and pro-activeness
4.3.5Prediction
5.1.1Description language allows expression of synchronous and asynchronous interaction
5.1.2Single Description language for defining and orchestrating SPICE services
5.2.1Service Execution Environment support execution engines for event-oriented services, process-oriented services, and composed services
5.2.2Service Execution Environment must support an execution environment on the terminal
5.2.3Service Execution Environment must support various capabilities and enablers such as HTTP, WebServices, IMS, Streaming
5.3.1Mechanisms for design-time and run-time dynamic service composition
5.3.2Service Publication & Discovery with syntactical, semantical and pragmatic annotations
5.4.1Tools for end-user and professional service creation
5.4.2Toolchain for analysing and testing service before deploying them
5.4.3Packaging and Deployment Tool
6.1.1Support of a Uniform Identity Management for Multiple Access Networks
6.1.2User privacy and Single Sign-on within the SPICE Platform for Users with Different Identities per Service
6.2.1SPICE user authentication based upon the Generic Bootstrapping Architecture
6.2.2Service Creator authentication
6.2.3Offline Accounting Record storage
6.3.1User privacy management
6.3.2Privacy rules for special cases
6.4.1Controlling access to services and service level agreements (SLA) using policies
6.4.2Policy Management System
6.4.3Automatic Contracting
6.6.1Charging support of the SPICE services.
6.6.2Payment method determination for given user and service.
6.6.3Charging of composite service.
7.1.1Use of Metadata for Multimedia Content organization
7.1.2Content Flow Organization
7.2.1Content purchase and access
7.2.2Protected Content backup
7.2.3Overall content protection
7.2.4End user content protection
7.3.2Adaptation Decisions
7.3.3Description Languages for Multimedia Content and Resources
7.3.4Changing the Presentation Modality and Interactive Modality
8.1.1Restricted and parametrizable access to user profile/ data

Home