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 – M185 Cookbook interfaces to support5.1 IntroductionThis chapter describes which interfaces need to be supported by the third party service(or by the component in that service that invokes the SPICE component). A list offunctions described in the Cookbook as necessary to support for SPICE components isprovided first. Then there is a discussion on which interfaces are really needed.5.2 Identified Cookbook functions(The sections below come from the cookbook sections 4.1.6 -4.1.10)5.2.1 Lifecycle ManagerThe Lifecycle Manager concerns management of lifecycle of Middleware Component andimplements the flow of a process through the different components that realise it. Itcommunicates with the different Middleware Components that take part in supportingManagement Services that requires actions from them.5.2.2 Component SupervisorComponent supervisor is an entity that is responsible for monitoring the KPIs of acomponent. The component supervisor can also get component specific system metricsfrom the SEE. This entity is passive, in the sense that it does not take charge and try to fixproblems that might occur; e.g. if the throughput for a given operation drops dramatically.In such cases the component supervisor reports to the level above - the performancemanager.5.2.3 LoggingLogging management service provides detailed history of the events that have happenedto a given service. Logging supports the generation of periodical or on demand reports.Additionally it supports the diagnosis in case of problem situations. Logging events areautomatically deleted after a specified lifetime. Examples of classes of logged events arelifecycle events, usage events (e.g. login, logout), Alarm events, Security eventsLogging is targeted to be used by all SPICE actors such as Component Developer,Service Composer, Service Provider, Public and Virtual Network Operators, SystemAdministrator. These actors must be authenticated. A service should delegate the loggingoperation to the Logging, which is used by all services.5.2.4 Subscription ManagerThe Subscription Manager entity is responsible for add or removing users to or from theregistration database that system administrator uses for controlling access to a servicecomponent.ID: SPICE_D2.5_Ericsson Date: 28/06/2007Revision: d0.16Security: CONFIDENTIAL – Consortium onlyPage 30/34

Contract: 027617Deliverable ReportPeriod covered: M00 – M185.2.5 Performance ManagerThe performance manager is an entity that monitors high level performance such as QoS.I.e. it is capable of comparing negotiated QoS with the measured (or perceived) QoS.Negotiated QoS is defined in Service Level Agreements (SLA), and measured QoS isextracted from the KPIs retrieved from the component supervisor. Measured QoS isdirectly affecting the experience the user is having, it is thus logical that the performancemanager takes action if the difference between measured and negotiated QoS gets toobig.Another task of the performance manager is to keep track of system metrics, much thesame way the component supervisor is. However, the performance manager has theability to look at the overall system; e.g. what is the total CPU load, how manycomponents are active, how many users are active, etc.5.3 Enablers with a call backNote that this document is only addresses third party services that invoke SPICEservices. In this case the external services are wrapped as a SPICE component, fullyaccording to the Cookbook.However in case of enablers with a call back, in which invoked services send invocationsto the invoking entity, the execution is very similar to SPICE services invoking externalservices. Two of the three enablers, for which the interfaces are described in thisdocument, have a call back. The call control enabler has call backs for new incomingchannels (calls) and incoming events per channel. The Immediate messaging enabler hasa call back for the receiving of messages.ID: SPICE_D2.5_Ericsson Date: 28/06/2007Revision: d0.16Security: CONFIDENTIAL – Consortium onlyPage 31/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 ...