26.03.2015 Views

19SafQB

19SafQB

19SafQB

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

6.3 The iCore Functional Architecture 255<br />

(Input) — Comprehension (Processing) — Adaptation (Response) tuned to<br />

specific goals.<br />

Specific CVOs are devoted to the particular task of observation of events<br />

though CVO processing, as particularly meaningful and relevant to the ‘situation’<br />

that a particular person or service is in. These CVOs are called Situation<br />

Observers (SO). The SOs are considered to provide runtime input to the Situation<br />

Awareness through the Queried Fast Collector.<br />

The Queried Fast Collector is used to aggregate the subscribed event<br />

streams and to deliver the outcome to the Situation Detection of the Situation<br />

Awareness, having the latter to create the RWK. The information (about<br />

specific RW instances) captured through the event streams is stored in the<br />

Real World Information (RWinfo) Database. Finally the Real World Knowledge<br />

Model is used for the internal data representation of RWK and we assume<br />

that ‘knowledge’ can be captured in RDF graphs, and so an RWK Model Store<br />

can be used to memorise the reflection of the real world’s rules of behaviour<br />

in the iCore system.<br />

6.3.3.2 CVO Level<br />

The CVO level receives from the Service level a Service Execution Request.<br />

The first point of contact in the CVO level is the CVO Management Unit<br />

which comprises the CVO Lifecycle Manager an intelligent monitoring unit<br />

keeping track of the changing states of the collection of running CVOs. At the<br />

time of a Service Execution Request, the lifecycle manager needs to check<br />

if CVO instances for a specific CVO template are already running and could<br />

be reused, and otherwise needs to instantiate a new CVO through the CVO<br />

Factory. When CVOs are used in the context of multiple service execution<br />

requests the potentially different service objectives must be coordinated for<br />

potential conflict resolution (Coordination functional block). The Performance<br />

Management intends to guarantee the proper performance of the CVO Level<br />

in terms of satisfying specific Key Performance Indicators (KPIs) thresholds.<br />

The Quality Assurance targets mainly at the satisfaction of the SLAs as delivered<br />

by the Service Level. Both the Performance Management and the Quality<br />

Assurance may trigger reconfiguration actions in order to improve the performance<br />

and the quality of service respectively.<br />

CVO Factory: While the CVO Management Unit is more about the<br />

execution/runtime aspects of resource management, the CVO factory is

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!