SPICE Logo

Requirements grouped by scenarios and scenes

unified scenario

unified.scene1

1.4.4Flexible operation, administration and management of 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
2.1.1An integrated and technology-neutral methodology for development, lifecyle management and publication of middleware components.
2.1.2Generic Service Enabling Interfaces.
5.1.2Single Description language for defining and orchestrating SPICE services
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
8.1.8End user feedback during the service prototyping phase
8.1.9Copyright management when prototyping between multiple parties

unified.scene2

1.4.7Transparency and ease of use of content and service creation and deployment tools to all parties on the platform
2.1.1An integrated and technology-neutral methodology for development, lifecyle management and publication of middleware components.
2.1.2Generic Service Enabling Interfaces.
2.2.1Service Repository for Semantically Described Services
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.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

unified.scene3

1.4.4Flexible operation, administration and management of the SPICE platform
1.4.10Allow open access for multiple portals
2.1.1An integrated and technology-neutral methodology for development, lifecyle management and publication of middleware components.
2.1.3Lifecycle and performance management.
2.2.1Service Repository for Semantically Described 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.4.3Packaging and Deployment Tool
6.2.2Service Creator authentication

unified.scene4

2.1.3Lifecycle and performance management.
2.2.3Query Evaluation by the Service Description Repository
2.2.4Multi-domain Service Repository Architecture
5.3.2Service Publication & Discovery with syntactical, semantical and pragmatic annotations
8.1.2Limited push-behaviour of Spice

unified.scene5

1.5.1Legal requirements Privacy - Permission to process private data by law or by declaring consent
1.5.2Legal requirements Privacy - Sensitive data
2.2.2Service Description
2.2.3Query Evaluation by the Service Description Repository
2.3.2The user is assisted in service selection
3.2.2Dynamic Desktop features
4.2.3Context Queries based on Semantic Context Schema and QoC
4.2.8Prioritized List of Alternatives, plausibility and dealing with imperfect situations
4.3.5Prediction
5.3.2Service Publication & Discovery with syntactical, semantical and pragmatic annotations
8.1.7Ergonomics

unified.scene6

1.4.5Offering user-generated content over the SPICE platform
2.1.3Lifecycle and performance management.
2.3.3Service creators are involved in the service adaptation process
5.2.2Service Execution Environment must support an execution environment on the terminal
5.4.3Packaging and Deployment Tool
8.1.6Users' rating of consumed services

unified.scene7

2.2.2Service Description
2.2.3Query Evaluation by the Service Description Repository
2.3.1Service experience depending on environment conditions
3.2.1Group management
3.2.2Dynamic Desktop features
3.2.3Dynamic Desktop context-aware service push
4.0.1Mobile Ontology
4.1.5Management and Provision of Service and Situation-dependent User Data
4.2.2Gathering, Aggregation and Interpretation from Multiple Distributed Context Sources, derivation of knowledge
4.2.7Learning and Recommending Algorithms
4.2.8Prioritized List of Alternatives, plausibility and dealing with imperfect situations
4.3.5Prediction
6.1.2User privacy and Single Sign-on within the SPICE Platform for Users with Different Identities per Service
6.2.3Offline Accounting Record storage
6.4.3Automatic Contracting
6.6.1Charging support of the SPICE services.
6.6.2Payment method determination for given user and service.
7.2.1Content purchase and access
7.3.2Adaptation Decisions
8.1.2Limited push-behaviour of Spice
8.1.3Non-biased recommendations and queries results
8.1.6Users' rating of consumed services

unified.scene8

1.4.1User's Privacy rules (Open market)
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.5.10Conditions for the lawfulness of commercial communication.
2.3.1Service experience depending on environment conditions
4.0.1Mobile Ontology
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.3.4Message Push and pro-activeness
4.3.5Prediction
5.1.1Description language allows expression of synchronous and asynchronous interaction
5.2.1Service Execution Environment support execution engines for event-oriented services, process-oriented services, and composed services
5.2.3Service Execution Environment must support various capabilities and enablers such as HTTP, WebServices, IMS, Streaming
8.1.1Restricted and parametrizable access to user profile/ data
8.1.2Limited push-behaviour of Spice
8.1.3Non-biased recommendations and queries results
8.1.6Users' rating of consumed services

unified.scene9

1.4.8Steering of payment options in checkout module
3.2.1Group management
6.1.1Support of a Uniform Identity Management for Multiple Access Networks
6.2.3Offline Accounting Record storage
6.6.1Charging support of the SPICE services.

unified.scene10

1.4.5Offering user-generated content over the SPICE platform
1.4.10Allow open access for multiple portals
3.1.3User rules
3.1.4Terminal Synchronization
5.2.3Service Execution Environment must support various capabilities and enablers such as HTTP, WebServices, IMS, Streaming
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
7.2.4End user content protection

unified.scene11

1.4.1User's Privacy rules (Open market)
1.5.10Conditions for the lawfulness of commercial communication.
2.3.1Service experience depending on environment conditions
2.4.1Seamless Service Delivery
4.2.1Discovery and Exchange of Distributed Context Information; subscription and polling
4.2.7Learning and Recommending Algorithms
4.3.4Message Push and pro-activeness
8.1.1Restricted and parametrizable access to user profile/ data
8.1.3Non-biased recommendations and queries results

unified.scene12

1.4.1User's Privacy rules (Open market)
3.2.1Group management
6.3.1User privacy management
8.1.1Restricted and parametrizable access to user profile/ data
8.1.5No user location tracking w/o user's explicit consent

unified.scene13

1.4.2Support Seamless handover between operators, devices and platforms
1.4.5Offering user-generated content over the SPICE platform
3.1.1Communication Model building and notification of its updates
3.3.1Multimodal and multi-device delivery of services
6.1.1Support of a Uniform Identity Management for Multiple Access Networks
7.2.4End user content protection
7.3.2Adaptation Decisions
8.1.4Easy and intuitive session transfer among devices

unified.scene14

1.4.2Support Seamless handover between operators, devices and platforms
1.4.8Steering of payment options in checkout module
1.5.6The right holder's authorisation in case of use of copyrighted content
3.1.1Communication Model building and notification of its updates
3.3.1Multimodal and multi-device delivery of services
4.2.10Access, Storage, Processing and Distribution Rights
4.3.5Prediction
6.1.1Support of a Uniform Identity Management for Multiple Access Networks
6.2.3Offline Accounting Record storage
6.6.1Charging support of the SPICE services.
6.6.3Charging of composite service.
7.1.2Content Flow Organization
7.2.1Content purchase and access
7.2.2Protected Content backup
7.2.3Overall content protection
7.3.1User Policies and Provider Policies
7.3.2Adaptation Decisions
7.3.3Description Languages for Multimedia Content and Resources
7.3.4Changing the Presentation Modality and Interactive Modality
8.1.4Easy and intuitive session transfer among devices

Home