Views
3 years ago

Contract: 027617 SPICE WP 2 Deliverable 2.5 Exposure ... - ist-spice

Contract: 027617 SPICE WP 2 Deliverable 2.5 Exposure ... - ist-spice

Contract: 027617Deliverable ReportPeriod covered: M00 – M18AbbreviationsAcronymAASIdPIMSKMFPAPPDPPEPRDFSCSESEGSLAUMLUPMURIXACMLXMLXSLXSLTSignificationAuthentication and Authorization SupportIdentity ProviderIP Multimedia SubsystemKnowledge Management FrameworkPolicy Administration PointPolicy Decision PointPolicy Enforcement PointResource Description Framework, http://www.w3.org/RDF/Service ComponentSPICE ElementSecurity GatewayService Level AgreementUnified Modelling LanguageUser Privacy ManagementUniform Resource IdentifierAccess Control Markup LanguageExtensible Markup LanguageExtensible Style sheet LanguageXSL TransformationsID: SPICE_D2.5_Ericsson Date: 28/06/2007Revision: d0.16Security: CONFIDENTIAL – Consortium onlyPage 8/34

Contract: 027617Deliverable ReportPeriod covered: M00 – M181 Introduction1.1 Purpose of this documentThis document describes what is necessary to make it possible that third party servicesaccess SPICE components. The impact both on the SPICE platform side and the thirdpart service side is described. As illustrations of SPICE enablers the interfaces of anumber of SPICE enablers are provided.A third party service, i.e. a service outside SPICE, that wants to use one of the SPICEenablers, need to follow at least the following two steps.1. Establish that the wanted service can actually be provided by the availableenablers within SPICE.2. Access the functional interfaces of the enablers selected as providers of thewanted service.Figure 1 shows the actual use of the functional interfaces of the respective services.external interface3rd partyEEserviceenabler1enabler2access controlSPICEEEFigure 1: The use of functional interfacesFor the matching of wanted services with provided services, SPICE offers the DiscoveryFacility that allows discovery of service component meta-information, including its accessmechanisms. The challenge for the SPICE platform is to be able to handle as manydifferent service requests as possible. Or, in other words, the challenge is to reject as fewservice requests as possible when the basic functionality is offered by one of theID: SPICE_D2.5_Ericsson Date: 28/06/2007Revision: d0.16Security: CONFIDENTIAL – Consortium onlyPage 9/34

SPICE WP N°: 1 Deliverable N°: 1.6 Title: Legal and ... - Bad Request
D1.7 Title: Revised business analysis and models - ist-spice
Addressing the challenges of Beyond 3G service delivery ... - ist-spice
Deliverable 2.1b, TAMES-2, IST Project 2001-34283 Version 1.0 ...