A middleware for M2M services in the IoT segment of ... · "Performance Analysis of Data Serialization Formats in M2M Wireless Sensor Networks", in Proceedings of the 12th European

A middleware for M2M services in the IoT segment of Intelligent

Transport Systems

Paolo Pagano, Matteo PetraccaNetworks of Embedded Systems

Consorzio Nazionale Inter-universitario per le Telecomunicazioni (CNIT)Laboratorio Nazionale di Reti Fotoniche, Pisa (I)

http://noes.sssup.it

Outline• The 11 billion M2M devices challenge• Interconnecting «the Things» via the Internet• IoT in the ITS domain

– IoT devices in the C‐ITS roadside to support M2M services• An M2M middleware

– The reference ICSI architecture and the IoT role– The M2M middleware: architecture, features and components– Performance evaluation in a laboratory testbed

• M2M devices:– bridging the gap from M2M and ITS– a last‐mile logistics pilot.

• Conclusions and ongoing activities

December 10, 2015 Paolo Pagano ‐‐© CNIT 2

In 2021 M2M > Cellular

• According to Ericsson (http://www.ericsson.com/mobility‐report):– in 2021 90% of the world population will be covered by mobile broadband;– in 2021 there will be more than 11 billions of M2M connected devices (non cellular).


The Future Internet (IoT is a metonym)

• Key Features:– Interoperability, break system’s isolation

– Shared infrastructures / Multiple applications


• IoT is the fourth pillar of the Future Internet;

• IoT systems will play a fundamental role in the deployment of large scale heterogeneous infrastructures:– look at the H2020.IoT‐1‐2016 call for (six) pilots by the EC

M2M

Objects can have an IP stack• 6LoWPAN: IPv6 over Low‐Power

Wireless Area Networks (RFC 4919, 6282)– Minimal use of code and memory– Direct end‐to‐end Internet integration

in multiple topology options• Energy‐efficient routing (RFC 6550)

– RPL (Low‐power lossy networks)


CoAP

UDP

6LoWPAN

802.15.4 MAC

802.15.4 PHY

• CoAP: Constrained Application Protocol (RFC 7252)– Lightweight HTTP‐like protocol

especially designed for constrained devices;

– RESTful interaction and Resource abstraction

• URI support – coap://[aaaa::202:2:2:1]/led

• Built‐in resource discovery– coap://[aaaa::202:2:2:1]/.well‐

known/core• Asynchronous model

– Observe

M2M and Intelligent Transportation

Requirements and Use Cases (TR 102 898, ETSI TC M2M, 2013)• EV Charging Stations:

– Responsive, reliable, adaptive, low latency, secure communications with localized control are required;

– [...]• Fleet Management:

– capability to receive, store, and execute scheduled measurements;

– the ability to poll and check for occurrence of events;

– the ability of devices to be able to be contacted ("called") directly by a mobile telecommunication network;

– [...]

• Vehicle to Infrastructures:– capability to interface with in‐car

sensors;– capability to interface with V2X

communication systems;– capability to autonomously establish

a connection directly with a mobile telecommunication network.


The reference Cooperative ITS architecture

Complex architecture:• done by four sub‐systems, with full addressability of devices;• centered on a OSI‐stack compliant entity (the ITS Station);• IoT devices being included in the architecture (CNIT editorship in ISO TC 204).


The ICSI M2M aware architecture for ITS

CentralSubsystem

VehicularSubsystem

PersonalSubsystem

RoadsideSubsystem

• FP7 project coordinated by Intecs SpA;

• CNIT contribution:‒ IoT

middleware‒ M2M

connectors • ETSI TS 102 690: M2M functional architecture• ETSI TR 101 607: Intelligent Transport Systems (Release 1)


M2M‐based ITS roadside sub‐system

• IoT devices sense traffic‐related variables (i.e. parking, flows);

• IoT nodes operate as D’ devices in a meshed topology;• D’ devices send aggregated data to the Gateway Service Capability Layer running on the Gateway;

• Supporting IoT standards:– 6LoWPAN– CoAP– RPL

M2M specs

ImplementationDecember 10, 2015 Paolo Pagano ‐‐© CNIT 9

M2M middleware: requirements

• Provides a system abstraction necessary to:– Hide distribution and communication details;– Deal with the limited resources (computational power, battery, network bandwidth, etc.)

• A Dynamically reconfigurable system:– Enabling in‐network event composition;– The data aggregating function can be moved from node to node at runtime.

• Based on:– RESTful design;– Virtualization techniques.


M2M middleware: basic features

• The middleware has a modular design targeted to the Use Case of any sensor (also Smart Cameras):– Parking Slots availability;– Traffic Flows.

• In‐network Data Aggregation:– False positives are filtered out;– Increased robustness;– The number of messages transferred to

the upper layers is reduced.

• Embedded ETSI M2M library:– Resource Processing Engine;– Configuration Manager:– JSON and EXI serialization.


M2M middleware: components

• The Resource Processing Engine– Use CoAP resources to represent in‐network processing tasks with a well‐defined RESTful interface

– The output message is encoded and sent to other peers

Resource Content Methods

/tasks List of installed tasks GET

/[task‐name] A specific task GET/PUT/DELETE

/is URLs of the input sources GET/PUT/POST

/od URL of the output destination GET/PUT/POST

/pf Processing function GET/PUT



• The Configuration manager, the RESTful interface allowing configuration of several system’s functions– RPE Configuration– Over‐the‐air software update

– Energy policy configuration (duty‐cycling)

– Networking and general purpose maintenance features

URI Methods

/cfg/ GET

/status GET

/battery GET

/period PUT | GET

/firmware PUT | GET

/reset PUT

/tasks GET | POST

/park POST

/pf PUT | GET

/is PUT | GET

/od PUT | GET

/sensor GET

/park_output GET



• Serialization engine:– by EXI or JSON (EXI performing better).

• Encode and decode compressed messages atop CoAP:– Applications and Containers during the startup phase– Content Instances in the monitoring phase


M2M middleware: Lab integration

• Laboratory IoT setup– Three sensor nodes with a border router– A Proxy devices

• HTTP/CoAP and EXI/XML translation

– A laptop running the GSCL


M2M middleware: Performance evaluation

• Key Performance Indicators: – The event transmission latency, including

• M2M message encoding• Transmission to the Proxy (CoAP blockwise transfer)

• Conversion on the proxy• Transmission to the GSCL using HTTP

– The memory requirements:• ROM and RAM footprints w.r.t. PIC32 resource set.

• ETSI TR 102 638: ITS Basic Set of Applications‒ complying with non-safety critical Use Cases (e.g. loading zone

management)


IoT for “Last mile logistics” in Italy • Telecom Italia coordinates

a Smart City project funded by the Italian MIUR:– Pilots in Milan and Turin

• CNIT (with SSSA university membership) is in charge of the design, development, and implementation of all field components

December 10, 2015 Paolo Pagano ‐‐© CNIT

• Target KPI’s:‒ 20% decrease of commercial vehicles inside the metropolitan area ‒ 40% increase of the average truck load ‒ 40% decrease of CO2 emission thanks to efficiency in routing ‒ 5% cost saving deriving from dinamic routing ‒ ‐30%/‐50% reduction of fuel consumption and emissions thanks to hybrid vehicles

17

IoT compliant WSN in the C‐ITS roadside• Currently IoT are not considered as standalone

ITS‐S in the roadside segment:– Their inclusion is possible only by means of a gateway

as proprietary networks.

• Filling the gap from C‐ITS and M2M:– 6LoWPAN/CoAP based communication permits to

specialize the ITS‐Station down to low‐cost sensor nodes.

• Interfacing with Facilities layer services (e.g. CAM, DENM).

Conclusions and ongoing activities

• M2M capabilities in the ITS scenario can be included into reference C‐ITS architecture;

• In the C‐ITS roadside segment M2M capabilities can be added by using lightweight M2M library as provided by the CNIT prototype;

• The M2M Middleware supports dynamic distributed applications in resource‐constrained environments:– complying with ETSI M2M specifications.

• Preliminary results show the feasibility of the developed middleware solution.

• Ongoing activities:– implementing ITS services on constrained devices in the framework of a last mile logistics project.


Scholar references• M. Carignani, S. Ferrini, M. Petracca, M. Falcitelli, P. Pagano, "A Prototype Bridge Between

Automotive and the IoT", in Proceedings of the IEEE World Forum on Internet of Things, Italy, December 2015. To appear.

• M. Petracca, C. Salvadori, A. Azzarà, D. Alessandrelli, S. Bocchino, L. Maggiani, and P. Pagano, “Middleware solutions to support ITS services in IoT‐based Visual Sensor Networks”, in book “Intelligent Transportation Systems Technologies and Applications”, John Wiley & Sons Ltd, November 2015

• A. Azzarà, M. Petracca, and P. Pagano, “The ICSI M2M Middleware for IoT‐based Intelligent Transportation Systems”, in Proceedings of IEEE International Conference on Intelligent Transportation Systems, Spain, September 2015

• F. Pacini, Femi A. Aderohunmu, P. Pagano, A. Azzarà, M. Petracca, and S. Bocchino, "Performance Analysis of Data Serialization Formats in M2M Wireless Sensor Networks", in Proceedings of the 12th European Conference on Wireless Sensor Networks, Porto, Portugal, February 9‐11, 2015.

• A. Azzarà, D. Alessandrelli, S. Bocchino, M. Petracca, and P. Pagano, “PyoT: a Macroprogramming Framework for the Internet of Things”, in Proceedings of IEEE International Symposium on Industrial Embedded Systems, Pisa, June 2014.

• G. Pellerano, M. Falcitelli, M. Petracca, P. Pagano, “6LoWPAN conform ITS‐Station for non safety‐critical services and applications”, in Proceedings of the 13th International Conference on ITS Telecommunications (ITST 2013), Tampere, Finland, November 2013.

• D. Alessandrelli, M. Petracca, P. Pagano, “T‐Res: enabling reconfigurable in‐network processing in IoT‐based WSNs”, in Proceedings of the 9th IEEE International Conference on Distributed Computing in Sensor Systems (DCoSS) and Workshops, Cambridge, MA, May 2013


thank [email protected]

Documents

A middleware for M2M services in the IoT segment of ... · "Performance Analysis of Data Serialization Formats in M2M Wireless Sensor Networks", in Proceedings of the 12th European