| ID | 2.1.2 |
| Title | Generic Service Enabling Interfaces. |
| Expert | Bharat Bhushan (FRAUNHOFER FOKUS) Gerhard Fischer (SAGO) Alexander Flach (UOK) Stian Alapnes (TELENOR) |
| Priority | mandatory |
| Description | The requirement is to allow the developer to focus on the service-specific aspects and less on the generic aspects of middleware. Therefore there is a need to have a set of minimum interfaces or capabilities (such as lifecycle management, performance measurement, notification) that all components provide. This will require definition of those capabilities and the use of modelling artefacts such as interfaces specifications, UML information and use case models, metadata models, XML Schemas, representing the components' common and service-specific capabilities. |
| Rationale | Generic service enabling interfaces will leverage best-practice architecture of SOA to support IP-based multimedia services on networking architecture such as IMS. It will allow the various users taking part in service life cycle to have a uniform understanding of diverse service execution platforms. |
| Type | functional |
| Depends on | |
| Child dependencies | |
| Environment | "Execution Environments" |
| Other_info | |
| Category | technical;open market |
| Subcategory | SPICE Middleware Compoment |
| Subcategory2 | |
| Scenario_scene | unified.scene1 unified.scene2 |
| SPICE_value | service creation;(seamless) service adaptation;service execution |
| Demo | implemented;concept |
| Keywords | common interfaces;service-specific interfaces;lifecycle management;performance measurement;notification |
| Home |