Architectural issues in the IoT.est ProjectPayam BarnaghiCentre for Communication Systems ResearchUniversity of SurreyGuildford, UKIoT Architecture @ IoT Week 201219 June, 2012, Venice, Italy
Consortium• 8 partners, 7 countries• Project Lead:CCSR, University of Surrey• Duration:36 monthsIndustry PTIN, ATOS, SIESME TT, AIResearch Centre NICTHigher Education UNIS, UASO
IoT.est – a quick snapshot• IoT.est will develop a test-driven service creation environment (SCE)for Internet of Things enabled business services.• The SCE will enable the acquisition of data and control/actuation ofsensors, objects and actuators.• The project will provide the means and tools to define and instantiateIoT services that exploit data across domain boundaries;• IoT.est will facilitate run-time monitoring and will enable autonomousservice adaptation to environment/context and network parameter(e.g. QoS) changes.
IoT.est architecture- requirements fromexisting platforms• Common interfaces to access low-level IoTresources (O&M data, service and managementdata access)• Control and management of resources• Resource handling, co-current and multipleaccess,• Security and privacy mechanisms• Discovery, directory, and publish/subscribeservices
A layered viewGreen circles:directlyaddressedIn IoT.estRed Circles:To be used fromexisting IoTplatforms
IoT.est project: Internet of Things Environment for ServiceCreation and Testinghttp://ict-iotest.eu/iotest/