19SafQB

References 257
with VO Lifecycle Manager, VO Factory/Template Repository/Registry and
the Coordination functional blocks have similar roles to their CVO Level
counterparts.
The Resource Optimization optimizes by means of cognition the operation
of the underlying sensors, actuators and resources e.g. by reducing the energy
consumption. The Data Manipulation/Reconciliation takes care of the data
management and ensures the quality of the data.
Similarly to its CVO counterpart, the VO Container is the execution environment
of the VO instances monitored, controlled and managed by the CVO
Management Unit through the VO Management Unit. Each VO comprises two
parts: the Front End and the Back End. The Front End is the abstract part of
the VO making it interoperable. It comprises the VO template filled with the
specific to the VO instance information. The front-end helps also checking the
access rights and communicating with the IoT based on IETF protocols on top
of IP. The Back End calls Device Manufacturer/vendor provided libraries for
communicating with the RWO.
Acknowledgments
The authors would like to acknowledge all the contributors of the deliverable
D1.4 of the project IoT-A, in alphabetical order: Martin Bauer (NEC), Mathieu
Boussard (ALBLF), Nicola Bui (CFR), Francois Carrez (UniS), Pierpaolo-
Giacomin (HEU), Edward Ho (HSG), Christine Jardak (SIEMENS), Jourik
De Loof (ALUBE), CarstenMagerkurth (SAP), Stefan Meissner (UniS),
Andreas Nettsträter (FhG IML), Alexis Olivereau (CEA), Alexandru Serbanati
(CATTID), Matthias Thoma (SAP), Joachim W. Walewski (SIEMENS)
Frank Berkers (TNO), Matti Eteläperä (VTT), Darminder Ghataoura (University
of Surrey), Stephane Menoret (Thales), Roberto Minerva (Telecom
Italia), Septimiu Nechifor (SIEMENS), Abdur Rahim (CREATE-NET), Marc
Roelands (Alcatel Lucent) Vera Stavroulaki (UPRC), and Filippo Visintainer
(CRF).
References
[1] www.iot-a.eu
[2] www.iot-butler.eu
[3] www.iot-icore.eu
[4] www.iot6.eu
[5] www.ict-iotest.eu