There is a current trend in the IoT domain to redefine the role of the IoT Gateway - once a simple communication relay with some application specific processing - into a generic purpose edge device supporting diverse device protocols, multiple applications, a variety of cloud connections, and sometimes even multi-tenant situations. In fact, recent low-cost hardware based on multi-core ARM and Intel SoCs (such as the Raspberry Pi 3, the Odroid-C2, or the UP board) seems to have the required capabilities.
One of the basic requirement to enable big-data analytics is a rational and effective approach to data ingestion. In long running projects the need arises to evolve the domain model and this potentially affects data quality. As a consequence, the concept of versioning is crucial to keep data centric systems consistent: the importance of service dynamicity and good modularity support in a sound data ingestion workflow implementation cannot be easily overestimated.
Data can be like water flowing along the river. Its a stream never ends.
Especially the many IoT devices can produce such endless flow of data, pushing it using various asynchonous messaging protocols like e.g. MQTT, Websockets, JMS, STOMP, XMPP or whatever you imagine. The OSGi frameowrk provides a lot of stuff to get such streams handled!
Smart home setups are as heterogenous as their users, whose desires, expectations and habits are highly individual. Eclipse SmartHome addresses this situation at various levels. It is a very flexible framework to build tailored smart home solutions that are easily extensible and customizable. End users of such solutions have the possibility to set up personal automation logic to cover their specific use cases.
T-Labs and Orange Labs are showcasing with some of their respective partners a community prototype around standard cloud APIs. In the Smart Home domain, the oneM2M standard restful interfaces are emerging as a unique service layer API standard at the cloud level backed by a worldwide organization and open source communities. Showcased partner applications use standard APIs implemented by Deutsche Telekom and Orange. T-Labs and Orange Labs have implemented identical oneM2M cloud interfaces on their respective platform prototype. Each of the two implementations integrates part of their respective industrial product – Qivicon, Orange Datavenue - and part of Eclipse OM2M open source artefacts.
Eclipse Kapua is modular micro service-based IoT cloud platform that provides management for Internet of Things (IoT) gateways and smart edge devices. Kapua bridges the gap between Operation Technology with Information Technology, between the complex and fragmented world of the IoT devices with the enterprise IT infrastructure. This session introduces the Eclipse Kapua project focusing on its architecture, service model and blueprint, modularity, and deployment options.
Whether you are developing smart products, enabling new connected services, or instrumenting factory production lines you face the challenges of designing, building, and deploying an IoT solution. This session will first summarize the leading reference architectures and blue prints for Industrial IoT and then, it will map those architectural components onto the activities of the Eclipse IoT community.
IoT solutions are becoming more and more common in the market and new devices and gadgets are showing up on a daily basis. Additionally, the networks and protocols used by the devices can be highly specialized for use cases such as minimal energy consumption or for long range connectivity. If you want your IoT system to be future proof while being able to take advantage of new technologies without having to change your system every time, then the OSGi Device Abstraction Layer can help. It provides IoT APIs independent of the underlying technology.