Raptorbox – the IoT platform

Application domain(s)

  • Agrifood
  • Automotive
  • Domotics (Smart Home)
  • E-Health
  • Energy Management
  • Industry 4.0
  • Smart Buildings
  • Smart Communities
  • Smart Grid
  • Telecommunication
  • Water Management

Area(s) of expertise

  • Cybersecurity
  • e-Health & well-being
  • Facilities & Labs
  • Fog and Edge Networks
  • Internet of Things (IoT)
  • Mobile Networks
  • NGI - Next Generation Internet
  • Remote Sensing
  • Telecommunication Networks

Description

Raptorbox is an open-source solution for Rapid Prototyping of application for the Internet of Things or IoT.

Raptor is a platform offering a set of tools to easily and quickly connect your devices, making data they generate accessible from the cloud and offering mechanisms to interact with them remotely in order to build your connected solutions and applications.

 

Figure  1. The Raptor platform

Raptor offers you specific tools to:

  • configure your device allowing it to communicate and interact with Raptor cloud services in a secure way
  • manage data flows produced by your devices and handle data storage, allow applications to subscribe for notifications about data changes and offer capabilities to perform actuation on your devices
  • build & deploy rapidly your applications enjoying rich tools, open restful APIs and libraries aiming at simplifying the way in which you build your next IoT application

Advantages & Applications

RaptorBox is a platform for rapid prototyping:

  • supporting the management of IoT devices, the control of how user access data and the delegation of permissions;
  • offering a real-time configurable monitoring dashboard for visual feedbacks of the data received data;
  • triggering action on devices from the Web.

Specifications

As a rapid prototyping platform, Raptor offers you a graphical web development environment and user interface simplifying the process of configuring and programming your devices in order to allow them to communicate with the cloud and (when needed) make them accessible remotely.

Figure  2. High-level view of Raptor architecture

Virtual Devices
Logically each device you want to include in your applications is represented inside Raptor as a “virtual device”, i.e. the virtual representation of your device available for identification and interaction inside your applications.

Note: Definition and creation of your devices (of their virtual representation) can be done using Raptor graphical editor or programmatically via Raptor APIs (typically, the user interface is used for rapid prototyping and testing your solutions, while APIs are used to handle device provisioning according to your specific deployment needs in a programmatic way).

Data storage
When your device produce new data (such as, for example, samples of the temperature in your room) it will use Raptor restful APIs in order to push this data into the cloud.

Data acquired by Raptor cloud will be automatically associated to the virtual representation of your device, stored into a scalable data store and made available for future usage and retrieval, business logic associated to your device in the cloud (i.e. subscriptions of applications interested in this data, workflows associated to your data flows) is automatically triggered and executed.

  • Logically each device you want to include in your applications is represented inside Raptor as a “virtual device”, i.e. the virtual representation of your device available for identification and interaction inside your applications.
  • When your device produce new data (such as, for example, samples of the temperature in your room) it will use Raptor restful APIs in order to push this data into the cloud. Data acquired by Raptor cloud will be automatically associated to the virtual representation of your device, stored into a scalable data store and so made available for future usage and retrieval, business logic associated to your device in the cloud (i.e. subscriptions of applications interested in this data, workflows associated to your data flows) is automatically triggered and executed.

Note: Definition and creation of your devices (of their virtual representation) can be done using Raptor graphical editor or programmatically via Raptor APIs (typically, the user interface is used for rapid prototyping and testing your solutions, while APIs are used to handle device provisioning according to your specific deployment needs in a programmatic way).

The real-time Dashboard
Raptor offers indeed a monitoring environment (the Raptor dashboard) where you can check the status of your connected devices and verify acquired data through historical data visualizations and queries.

Once your devices are connected with the cloud and their data flows managed by Raptor cloud, it’s time to focus on creation of your application starting from the definition of its business logic. As for device creation, Raptor offer two possible ways that you can use in order to implement your application logic:

  • use Raptor restful APIs to interact with devices and their data and build your application logic externally (using your preferred programming language and execution environment, such as, for example a java or PHP application, etc.);
  • use Raptor Workflow Visual Editor to quickly define, test and verify your application logic combining data flows with external services, data sources, events.

Workflow Visual Editor
Raptor Workflow Visual Editor is mainly aimed to support fast prototyping due to the nature of its capabilities: starting form data flows produced by your devices, the editor allow the creation of a workflow in a graphical way, according to a drag & drop paradigm, reusing existing processing capabilities configured inside existing nodes (selected from a palette of predefined nodes) offering specific functionalities to transform your data flows, combine them this other external and internal data sources, executing actions (such as, for example, actuations on your devices or on external services, such as, for example, twitting a message).

As a rapid prototyping tool, the visual editor allows users to easily customize application logic predefined inside nodes made available by the editor (using javascript language) in order to quickly adapt the logic to your specific needs and objectives, test it and verify on the fly its behaviour).

Raptor Workflow Visual Editor is based on a well-known open source solution Node Red that has been customized and adapted to this specific context.

Status

TRL 6 – System Adequacy Validated in Simulated Environment

Contacts

  • Reference person: Fabio Antonelli

    Tel. +39 0461 312447

    Email:

    Research Unit: OpenIoT – https://create-net.fbk.eu/openiot/

    Research Center: CREATE-NET https://create-net.fbk.eu/