| 1.4.1 | User's Privacy rules (Open market) |
| 1.4.2 | Support Seamless handover between operators, devices and platforms |
| 1.4.3 | Portability of user profile |
| 1.4.4 | Flexible operation, administration and management of the SPICE platform |
| 1.4.5 | Offering user-generated content over the SPICE platform |
| 1.4.6 | Dynamic, real-time creation of business networks |
| 1.4.7 | Transparency and ease of use of content and service creation and deployment tools to all parties on the platform |
| 1.4.8 | Steering of payment options in checkout module |
| 1.4.9 | Enable Clear Tariff Structure |
| 1.4.10 | Allow open access for multiple portals |
| 1.5.0 | General Legal requirement-completeness and comprehensiveness of regulatory requirement is impossible. |
| 1.5.1 | Legal requirements Privacy - Permission to process private data by law or by declaring consent |
| 1.5.2 | Legal requirements Privacy - Sensitive data |
| 1.5.3 | Legal requirements Privacy - Key Principles of Data Processing |
| 1.5.4 | Legal requirements Privacy - Rights of the Data Subject and Obligantions to the Data Controller |
| 1.5.5 | Legal requirements Privacy - Transferring data to third countries |
| 1.5.6 | The right holder's authorisation in case of use of copyrighted content |
| 1.5.7 | Respect for exceptions to the exclusive copyrights as provided under national laws. |
| 1.5.8 | Extraction or reutilisation of substantial parts of the content of the database requires the authorisation of the right-holder. |
| 1.5.9 | Usage of the trade mark (or corporate name) in the course of trade (e.g. advertising) might require conformity check with the EU and national trade mark laws. |
| 1.5.10 | Conditions for the lawfulness of commercial communication. |
| 2.1.1 | An integrated and technology-neutral methodology for development, lifecyle management and publication of middleware components. |
| 2.1.2 | Generic Service Enabling Interfaces. |
| 2.1.3 | Lifecycle and performance management. |
| 2.2.1 | Service Repository for Semantically Described Services |
| 2.2.2 | Service Description |
| 2.2.3 | Query Evaluation by the Service Description Repository |
| 2.2.4 | Multi-domain Service Repository Architecture |
| 2.3.1 | Service experience depending on environment conditions |
| 2.3.2 | The user is assisted in service selection |
| 2.3.3 | Service creators are involved in the service adaptation process |
| 2.4.1 | Seamless Service Delivery |
| 2.4.2 | Operator Service Control flexibility |
| 2.4.3 | Seamless Service Provisioning |
| 3.0.1 | SPICE Terminal and Device requirements |
| 3.1.1 | Communication Model building and notification of its updates |
| 3.1.3 | User rules |
| 3.1.4 | Terminal Synchronization |
| 3.2.1 | Group management |
| 3.2.2 | Dynamic Desktop features |
| 3.2.3 | Dynamic Desktop context-aware service push |
| 3.3.1 | Multimodal and multi-device delivery of services |
| 4.0.1 | Mobile Ontology |
| 4.1.5 | Management and Provision of Service and Situation-dependent User Data |
| 4.2.1 | Discovery and Exchange of Distributed Context Information; subscription and polling |
| 4.2.2 | Gathering, Aggregation and Interpretation from Multiple Distributed Context Sources, derivation of knowledge |
| 4.2.3 | Context Queries based on Semantic Context Schema and QoC |
| 4.2.7 | Learning and Recommending Algorithms |
| 4.2.8 | Prioritized List of Alternatives, plausibility and dealing with imperfect situations |
| 4.2.10 | Access, Storage, Processing and Distribution Rights |
| 4.3.4 | Message Push and pro-activeness |
| 4.3.5 | Prediction |
| 5.1.1 | Description language allows expression of synchronous and asynchronous interaction |
| 5.1.2 | Single Description language for defining and orchestrating SPICE services |
| 5.2.1 | Service Execution Environment support execution engines for event-oriented services, process-oriented services, and composed services |
| 5.2.2 | Service Execution Environment must support an execution environment on the terminal |
| 5.2.3 | Service Execution Environment must support various capabilities and enablers such as HTTP, WebServices, IMS, Streaming |
| 5.3.1 | Mechanisms for design-time and run-time dynamic service composition |
| 5.3.2 | Service Publication & Discovery with syntactical, semantical and pragmatic annotations |
| 5.4.1 | Tools for end-user and professional service creation |
| 5.4.2 | Toolchain for analysing and testing service before deploying them |
| 5.4.3 | Packaging and Deployment Tool |
| 6.1.1 | Support of a Uniform Identity Management for Multiple Access Networks |
| 6.1.2 | User privacy and Single Sign-on within the SPICE Platform for Users with Different Identities per Service |
| 6.2.1 | SPICE user authentication based upon the Generic Bootstrapping Architecture |
| 6.2.2 | Service Creator authentication |
| 6.2.3 | Offline Accounting Record storage |
| 6.3.1 | User privacy management |
| 6.3.2 | Privacy rules for special cases |
| 6.4.1 | Controlling access to services and service level agreements (SLA) using policies |
| 6.4.2 | Policy Management System |
| 6.4.3 | Automatic Contracting |
| 6.6.1 | Charging support of the SPICE services. |
| 6.6.2 | Payment method determination for given user and service. |
| 6.6.3 | Charging of composite service. |
| 7.1.1 | Use of Metadata for Multimedia Content organization |
| 7.1.2 | Content Flow Organization |
| 7.2.1 | Content purchase and access |
| 7.2.2 | Protected Content backup |
| 7.2.3 | Overall content protection |
| 7.2.4 | End user content protection |
| 7.3.1 | User Policies and Provider Policies |
| 7.3.2 | Adaptation Decisions |
| 7.3.3 | Description Languages for Multimedia Content and Resources |
| 7.3.4 | Changing the Presentation Modality and Interactive Modality |
| 8.1.1 | Restricted and parametrizable access to user profile/ data |
| 8.1.2 | Limited push-behaviour of Spice |
| 8.1.3 | Non-biased recommendations and queries results |
| 8.1.4 | Easy and intuitive session transfer among devices |
| 8.1.5 | No user location tracking w/o user's explicit consent |
| 8.1.6 | Users' rating of consumed services |
| 8.1.7 | Ergonomics |
| 8.1.8 | End user feedback during the service prototyping phase |
| 8.1.9 | Copyright management when prototyping between multiple parties |
