18
Making Sense for Society Werkgroep Standaarden Bijeenkomst 4 juni 2014 NSO Den Haag Erik van der Zee ([email protected]) Thijs Brentjens ([email protected]) JanDirk Bulens ([email protected])

IoT Standardisatie werkgroepbijeenkomst 4 juni 2014

Embed Size (px)

DESCRIPTION

Als onderdeel van de 2e plenaire bijeenkomst van de Geonovum Pilot Making Sense for Society namens de IoT Standaardisatie werkgroep een presentatie gehouden over het belang van standaardisatie en de beschikbaarheid en mogelijkheden van de OGC Sensor Web Enablement (SWE) standaardenset.

Citation preview

Page 1: IoT Standardisatie werkgroepbijeenkomst 4 juni 2014

Making Sense for Society Werkgroep Standaarden

Bijeenkomst 4 juni 2014 NSO Den Haag

Erik van der Zee ([email protected])

Thijs Brentjens ([email protected])

JanDirk Bulens ([email protected])

Page 2: IoT Standardisatie werkgroepbijeenkomst 4 juni 2014

IoT Domains (Beecham)

Page 3: IoT Standardisatie werkgroepbijeenkomst 4 juni 2014

Need for Standarization

Internet of Things is a holistic concept (cross domain / cross platforms)

Currently many vendor specific hardware and software protocols used in IoT solutions

Standardization (technical & semantic) over different domains, and on all levels of the OSI stack, is needed to make machines talk (“1001001110”) to each other (Machine2Machine or “M2M” communication)

Standardization efforts by W3C (SSN), OGC (SWE) and other mayor standardization organizations

Page 4: IoT Standardisatie werkgroepbijeenkomst 4 juni 2014

Machine Communication (the OSI model)

Focus in Geonovum Pilot on the top level of OSI Stack

Page 5: IoT Standardisatie werkgroepbijeenkomst 4 juni 2014

OSI model Main Protocols

Page 6: IoT Standardisatie werkgroepbijeenkomst 4 juni 2014
Page 7: IoT Standardisatie werkgroepbijeenkomst 4 juni 2014

What is a Smart Thing (IoT-A)

Page 8: IoT Standardisatie werkgroepbijeenkomst 4 juni 2014

Sense – Analyse – Act(uate)

Page 9: IoT Standardisatie werkgroepbijeenkomst 4 juni 2014

Standardization in Event Processing

Page 10: IoT Standardisatie werkgroepbijeenkomst 4 juni 2014

OGC and Standardization

SWE standaarden overzicht http://www.opengeospatial.org/ogc/markets-technologies/swe – SOS Sensor Observation Service (Sensing)

– SPS Sensor Planning Service (Actuating)

– SES Sensor Event Service (Event Stream Processing)

– SIR/SOR Sensor Catalogue (extension on CSW)

– SW for IoT (new light weight version of SWE for IoT devices)

– PUCK (plug and play devices)

– …(see A0 overview)

OWS Demonstrations (usage of SWE standards) http://www.opengeospatial.org/projects/initiatives/ows-5

Page 11: IoT Standardisatie werkgroepbijeenkomst 4 juni 2014

OGC SWE Standards

Page 12: IoT Standardisatie werkgroepbijeenkomst 4 juni 2014

OGC Sensor Web for IoT

Workgroup http://www.opengeospatial.org/projects/groups/sweiotswg

The initial scope of the SWIOT SWG seeks to make observations captured by IoT devices easily available to applications and users through data aggregation portals (e.g. data broker platforms like Xively, Thingworx, Thingspeak, Se)

Page 13: IoT Standardisatie werkgroepbijeenkomst 4 juni 2014

OGC Puck Protocol

Figure 1 illustrates how PUCK complements other OGC SWE standard components. SWE services must sometimes interact with an actual physical sensor in order to carry out client requests; e.g. the Sensor Planning Service Submit operation ultimately requires that data acquisition be triggered from a physical sensor. Many of today's sensors are not themselves network-capable; instead they are connected to the network through a sensor host machine's serial port. Moreover most sensors themselves do not implement a standard protocol; instead the SWE service must access the device through a sensor driver, which runs on the sensor host and translates the service request to the appropriate sensor protocol command. The driver may also transform the sensor's response to a standard format, e.g. it may transform the sensor's "raw" data to an OGC Observation and Measurement object. Moreover, the OGC services also need access to the sensor's SensorML document, which may also reside on the sensor host. These critical sensor specific components - sensor driver and SensorML document - can be stored in the sensor itself and automatically retrieved and installed with PUCK protocol by a component on the host (not shown) when the sensor is physically plugged in.

Page 14: IoT Standardisatie werkgroepbijeenkomst 4 juni 2014

IoT (real-time) Data Broker Platforms

Real-time data broker for networked objects and environments

Voorbeeld https://xively.com (aka Pachube)

Collects and distributes data streams of sensors registered at the platform

Can also alert, notify (actuate)

Page 15: IoT Standardisatie werkgroepbijeenkomst 4 juni 2014

Goals Standardization Workgroup

Short term – Create overview of relevant IoT Standards in Netherlands

(A0 Overview and WIKI pages) – Promote use of OGC SWE standards in the Making Sense 4

Society case studies – Register Pilot services in a OGC Sensor Catalogue

(SIR/SOR)

Mid term – Promote / Use of OGC standards in Governmental IoT

projects (e.g. SOS) – Extent Nationaal Georegister with a Sensor Catalog (based

on SWE SIR/SOR standards) – Dissemination of sensor data through PDOK using SWE

Standards – Role of PDOK as a IoT data broker platform for

Governmental use

Page 16: IoT Standardisatie werkgroepbijeenkomst 4 juni 2014

Pilot Results of the workgroup

Results of the workgroup will be published on the Making Sense for Society - Living Lab for the Internet website http://www.senseforsociety.nl under the topic “Standards”

A0 Overview

WIKI pages

Page 17: IoT Standardisatie werkgroepbijeenkomst 4 juni 2014

A0 Overview of use of standards in the Pilot (first draft)

Page 18: IoT Standardisatie werkgroepbijeenkomst 4 juni 2014

Barchman Wuytierslaan 10, 3818 LH Amersfoort, NL

Postbus 508, 3800 AM Amersfoort, NL

+ 31 (0) 334 604 100

[email protected]

www.geonovum.nl

@geonovum.nl