BUTLER – iCore Integrated Common Demo

The BUTLER - iCore integrated common demo serves as a proof of concept on the semantic interoperability, seamless connectivity among heterogeneous IoT infrastructure (smart objects, mechanism, network elements, etc). The cognitive management and control of such IoT infrastructures allow several IoT project to share resources, offering enhanced services at the end user.

Intellectual property rights (IPR)

@BUTLER, @iCore

BUTLER user enters an area which is equipped with a real time location system. The BUTLER platform knows only relative positions but it knows also the existence of other IoT platforms (e.g. iCore). The BUTLER platform starts an iCore service request to retrieve mapped positions and allows control over the street lamps near the BUTLER user. The BUTLER user knows its real world position and with the help of IoT, the street lamps save energy without any loss of comfort.

The demo has 2 phases:

  • demonstrate its feasibility from technical point of view
  • user benefit of interaction

Hereinafter, VO reffers to iCore Virtual Object and CVO to iCore Composed Virtual Object.

Phase A scenario

Resources used

  • from the BUTLER project: relative positions
  • from the iCore project: absolute (GPS) positions

Expected outcome

  • a map containing the relative matched with the absolute positions

Work flow

  • a Service Request interface developed into BUTLER will trigger an iCore Service Request
  • BUTLER component sends Relative Positions through the SmartObject-SmartGateway-SmartServer chain to iCore (as a VO)
  • iCore receives Absolute Positions through a VO
  • iCore’s CVO processes the 2 information into a matched map
  • ICore’s CVO sends the matched map to the BUTLER SmartMobile application

Architecture Phase A

Phase B scenario

Resources used

  • from BULER, the relative positions were used
  • from iCore: Absolute (GPS) Positions, Luminosity Sensors, Lamps

Expected outcome

  • additionally to Phase A’s functionality the Lamp Switch ON/OFF functionality was added

Work flow

  • additionally to Phase A:
  • iCore receives Luminosity and Lamps’ State values through VOs
  • iCore’s second CVO processes the information from Relative Positions, Luminosity and Lamps’ State values
  • ICore’s second CVO turns the Lamps’ State ON/OFF/.

Architecture Phase B

The poster presentation is available on the iCore project site.

Service level

Reuse Readiness Levels

5 - Reuse is practical; the software could be reused by most users with reasonable cost and risk