ETSI M2M Workshop IPSO Alliance Standard Update · An Embedded Device: ... vending machine, smart grid ... The aim of this paper is to provide a technical overview of several of low

ETSI M2M Workshop

IPSO AllianceStandard Update

Copyright © 2009 Cisco Systems, Inc. All rights reserved.

Patrick Wetterwald

Cisco Smart Grid and IoT Product Marketing

President, IPSO Alliance

Standard Update

02/01/2009 IPSO Alliance @2009 2

Promoting the use of IP in networks of Smart Objects

http://www.ipso-alliance.org/Patrick Wetterwald, President

[email protected]

What is a Smart Object?

� An intelligent tag (RFID),

� A sensor: device that measures a physical quantity and converts it to a analog or digital signal: power consumption and quality, vibration of an engine, pollution, temperature, CO, motion detection, temperature, …

� An Actuator: device that controls a set of equipment (e.g. control and/or modulates the flow of a gas or liquid, control electricity distribution, perform a mechanical operation) perform a mechanical operation)

� An Embedded Device: a purpose built connected device that performs a specific function(e.g. a factory robotic arm, vending machine, smart grid analyzer)

� Any combination of the above features to form a more complex entity.

Sensor/Control Networks are everywhere …with a vast scope of applications

Improve Productivity

Energy Saving (I2E)

Predictive maintenance

Defense

Intelligent Building

IPSO Alliance @2008 4

Enable New Knowledge

Food & H20 Quality

Enhance Safety & Security

Health

Smart Home

Healthcare

High-Confidence Transport and assets tracking

Intelligent Building

02/01/2009Smart Grid

Objectives of IPSO

� Create awareness of available and developing technology with IP for Smart Objects

� Generate tutorials, white papers and highlight use cases� http://www.ipso-alliance.org/Pages/DocumentsAndWhitePapers.aspx

� Complement the IETF, IEEE, … which define standards, but

9/11/08 5

� Complement the IETF, IEEE, … which define standards, but does no marketing

� Link companies that support IP based sensing and control systems

� Coordinate and combine member marketing efforts

� Support and organize interoperability events

White papersWhy IP?

� The emerging application space for smart objects requires scalable and interoperable communication mechanisms that support future innovation as the application space grows. IP has proven itself a long-lived, stable, and highly scalable communication technology that supports both a wide range of applications, devices, and underlying communication technologies. The IP stack is lightweight and runs on tiny, battery operated embedded devices. IP therefore has all the qualities to make “The Internet of Things” a reality, connecting billions of communicating devices.

Lightweight OS

� Historically, smart objects have used a plethora of communication technologies, both at the physical and medium access control layers, and at upper layers. The upper layers of the communication stack remain either proprietary or specified by exclusive alliances. This plethora of solutions renders interoperability between different sensor networks difficult. It also makes the seamless integration of sensor networks with existing IP networks impossible. IP is an ideal solution to this end-to-end interoperability issue. However, the adoption of IP as the Layer-3 protocol to connect wireless or wired smart objects has been impaired by the common belief that IP is not well-suited for the memory and energy constraints of such devices. In this white paper we give insights on key implementation aspects, based on the experience of three interoperable IPv6 stacks.

6LoWPAN

� IP for Smart Objects seeks to extend the use of IP networking into resource-constrained devices over a wide range of low-power link technologies – IEEE 802.15.4 represents one such link. Extending IP to low-power, wireless personal area networks (LoWPANs) was once considered impractical because these networks are highly constrained and must operate unattended for multiyear lifetimes on modest batteries. Many vendors embraced proprietary protocols, assuming that IP was too resource-intensive to be scaled down to operate on the microcontrollers and low-power wireless links used in LoWPAN settings. However, 6LoWPAN radically alters the calculation by introducing an adaptation layer that enables efficient IPv6 communication over IEEE 802.15.4 LoWPAN links.

Security Introduction

� Security is as important in smart object networks as it is in traditional comput er networks, if not more so. By leveraging well-established security mechanisms and networking standards, and adapting them appropriately for resource-constrain ed environments, we can enhance the security of smart objects, their data and the networks in which they participate. In this white paper we discuss smart objec t applications and relevant threats, evaluate various approaches to securing aga inst specific threats, offer some practical guidelines for building security int o smart object networks, and finally tackle some common misconceptions about sec uring these devices.

Low Power Link Layer

� One of the fundamental properties of IP is to be based on a layered architecture, which means that each layer can evolve independently without compromising the architectural model. The aim of this paper is to provide a technical overview of several of low power wired and wireless technologies: IEEE 802.15.4, IEEE 802.15.4e, Low Power Wi-Fi, a low power Powerline Communication (PLC) technology known as WPC and the newly specified Homeplug green PHY. Several other low power link layer technologies will be covered in further revision of this paper. Note that some technical aspects described in this document are related to a specific implementation: still it was worth providing some details to show how low energy could be achievable on specific media. Furthermore, some technologies are still proprietary (this is explicitly indicated in this case) and on the path to standardization.

Members

Over 50 members

www.ipso-alliance.org

Alliance Actions

� IETF 6LoWPAN, ROLL, CORE Working Groups

� ISA100 Industrial Wireless� IEEE Working Groups

� Interoperability Testing� Architecture Design

� Technology Demonstrations

Support Activities On-going Activities

9/11/08 9

� IEEE Working Groups� ITU-T

� Technology Demonstrations� Use Cases / White Papers� Tutorials, Webinars and

Educational Materials� Joint activity with IPv6 forum

on IPv6 ready certification dedicated to smart objects

Formal liaisons

� IPv6 Forum� Zigbee alliance

� EC IoT expert group

A plethora of emerging new low power media for Smart Objects in SG networks

� Things are fast changing since the historical serial connection with RS485 …

� Then wide adoption of IEEE 802.15.4 as the low power RF technology (2.4 GHz and 900 MHz)

� As expected (and this is the good news) several other low

10Copyright © 2009 Cisco Systems, Inc. All rights reserved.

� As expected (and this is the good news) several other low power technologies have emerged:

Power Line Communication (PLC): key for the home and the Smart Grid: see new ITU initiative (G.hnem), IEE P1901.2 and HP Green PHY

Low power Wifi

New RF technologies: IEEE 802.15.4g, Wavenis, …

IP Smart objects networks are made of a variety of links !

IETF Update

• IETF formed in 1986,• Not considered as important for some time :-)• Not government approved :-)• Involving people not companies• Motto: “We reject kings, presidents and voting. We believe in rough consensus and running code ” Dave Clark (1992)• Organized in areas made of WGs,


Reuse whenever possible, Invent where needed

GEN OAM INT RTGAPS RAI TSVSEC

Reuse

LLNs6lowpan ROLLCORE

� 6LoWPAN is an adaption layer for IPv6 over IEEE 802.15.4 links, not a protocol stack, full solution for smart objects networks!

� Why do we need an adaptation layer ?

� IEEE 802.15.4 MTU is 127 bytes

� Performs 3 functions:

IETF 6LoWPAN Working Group (INT Area)


� Performs 3 functions:• Packet fragmentation and re-assembly

• Header compression

• 6LoWPAN ND

� Good Progress:• HC-09 deprecating RFC4944 for compression (Last Called)

• 6LoWPAN ND (Last Called)

RPL : new routing protocol for IP Smart object A reminder of the technical challenges

• Energy consumption is a major issue (for battery powered sensors/controllers),

• Limited processing power

• Very dynamic topologies:• Link failure (LP RF) 40

5060708090

100

PDR Variation


• Link failure (LP RF)

• Node failures (triggered or non triggered)

• Node mobility (in some environments),

• Data processing usually required on the node itself,

• Sometimes deployed in harsh environments (e.g. Industrial),

• Potentially deployed at very large scale,

• Must be self-managed (auto-discovery, self-organizing networks)

0102030

653

2034

3458

5047

6668

8273

9847

1151

313

237

1499

316

778

1850

320

318

2214

824

008

2591

327

803

2964

731

433

3403

6

Routing Over Low power and Lossy Link (ROLL) WG

� Working Group Formed in Jan 2008 and already re-charteredhttp://www.ietf.org/html.charters/roll-charter.html

Co-chairs: JP Vasseur (Cisco), David Culler (Arch Rock)

� Mission: define Routing Solutions for LLN (Low power and LossyNetworks)


Networks)

� Very active work with a good variety of participants with at first little IETF background

� Specification of a new protocol after detailed requirements and protocol survey

� Several proposals: one of then adopted as WG document, RPL

� RPL is now stable (passed all Last Call), with ~ 15 implementations, interop testing (Zigbee/IP and IPSO ), …

The IETF CoRE Working Group

� Working Group Formed in 2010http://www.ietf.org/html.charters/core-charter.html

Co-chairs: Cullen Jennings (Cisco), Carsten Bormann

� Mission: Provides a Framework for resource-oriented application intended to run on IP constrained network


� Applications to monitor/control IP smart objects (create, read, update and delete of resources)

� Definition of a simple protocol (CoAP) running over UDP to manipulate resources of a device => First plugfest at the last IETF!

� Definition of a proxy handling mapping between CoAP and REST APIs.

� CoAP supports caching (useful for sleepy devices)

CoAP


17

The IPSO Alliance will extend the reach of IP into “Internet of Things”