| 1.4.4 | Flexible operation, administration and management of the SPICE platform |
| Above: filter by 'platform' using Keywords field. Below: filter by 'platform' using other requirements fields. |
| 1.4.1 | User's Privacy rules (Open market) |
| 1.4.2 | Support Seamless handover between operators, devices and platforms |
| 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. |
| 2.1.1 | An integrated and technology-neutral methodology for development, lifecyle management and publication of middleware components. |
| 2.1.3 | Lifecycle and performance management. |
| 2.2.1 | Service Repository for Semantically Described Services |
| 2.2.4 | Multi-domain Service Repository Architecture |
| 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.3 | Dynamic Desktop context-aware service push |
| 3.3.1 | Multimodal and multi-device delivery of services |
| 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.2.3 | Service Execution Environment must support various capabilities and enablers such as HTTP, WebServices, IMS, Streaming |
| 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.3.1 | User privacy management |
| 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.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.2 | Limited push-behaviour of Spice |
| 8.1.3 | Non-biased recommendations and queries results |
| 8.1.5 | No user location tracking w/o user's explicit consent |
| 8.1.6 | Users' rating of consumed services |
