M2M Prototype Demonstration ETSI M2M #12 –Philadelphia, …

M2M Prototype Demonstration

September 16, 2010

© 2010 InterDigital, Inc. All rights reserved.

M2M Prototype Demonstration

ETSI M2M #12 – Philadelphia, PA

Introduction

• We will be conducting two independent demonstrations:– M2M Gateway and M2M Core Network (referred to here as the M2M Server)

– M2M WPAN

• These demonstrations highlight the work that InterDigital is doing to prototype an M2M System based on the current ETSI M2M standard


ETSI M2M standard– Requirements and design were largely based on Version 0.5.1 of the Functional Architecture Document (TS102 690)

• They are building blocks for an end to end prototype that we are developing that will include devices that represent D’ devices connected to an ETSI compliant M2M Gateway and M2M Server

2

End-to-End M2M Prototype System

© 2010 InterDigital, Inc. All rights reserved.3

M2M Gateway and M2M Server


M2M Gateway and M2M Server

Demonstration

4

Demo High Level Description

• Demonstrate a variety of procedures between an ETSI compliant M2M Gateway and ETSI M2M Server

• Utilize a 3GPP connection between the Gateway and the Server

• Utilize two separate demo applications, one on the Gateway and one on the Server– Use demo application on the Gateway (also serving as the Gateway Application (GA)) to:• Provide control of the demo procedures from the gateway side and issue operations towards the Network Application (NA) such as read, write, and


operations towards the Network Application (NA) such as read, write, and execute

• Provide a dummy application that will respond to operations initiated from the NA such as read, write, and execute – An example could be a thermostat application that will provide temperature readings to the NA and allow the NA to set the temperature of the thermostat, etc

– Use the demo application on the Server (also serving as the NA) to:• Provide control of the demo procedures from the network side and issue operations towards the GA such as read, write, and execute

• Provide a dummy application that will respond to operations initiated from the GA such as read, write, and execute

5

Use Cases Currently Supported

• Device Registration (mId)

• Device Application Registration (mId & dIa)

• Network Application Registration (mIa)

• M2M DA Resource Creation (GW or Server)

• M2M DA Resource Deletion (GW or Server)

• M2M NA Resource Creation (GW or Server)

• M2M NA Resource Deletion (GW or Server)

• M2M NA to M2M Device Read (Online)

• M2M NA to M2M Device Write (Online)

• M2M NA to M2M Device Execute (Online)

• M2M NA to M2M Device Read (Offline)

• M2M NA to M2M Device Write (Offline)

• M2M NA to M2M Device Execute (Offline)

• M2M DA to M2M NA Read

• M2M DA to M2M NA Write

• M2M DA to M2M NA Execute


Notes: - In this demo the gateway is the only device therefore gateway and device are equivalent (as are GA and DA)

- Additional use case support is being added in the next phase of development

Platform Description

• M2M Gateway Laptop (Debian Linux)

– Sierra Wireless Compass 888 USB Modem data card for

backhaul connection

• M2M Server Laptop (Debian Linux)

• Picochip Femto Cell with Continuous Computing

Corporation (CCPU) Femto Access Point (FAP)


Corporation (CCPU) Femto Access Point (FAP)

Software

• Core Network Emulation (CNE) Laptop with CCPU

CNE SW (Redhat Linux)

• Ethernet Router/Switch

7

Demo Network Configuration


Note: For this demo the Gateway Application will run on the M2M Gateway laptop and the Network Application will run on the M2M Server laptop

M2M Gateway Software Overview

• Gateway Manager + Service Capabilities

• CoAP Support

• Gateway (Demo) Application

• 3G Connectivity:

– Driver for 3G Data Card is built into Debian Linux


– Utilize PPP protocol and connection scripts to establish the

packet data connection

M2M Gateway Processes


Note: Highlighted entities are currently supported as separate processes on the Linux platform

M2M Server Software Overview

• Server Service Capabilities

• Support for Gi MCN interface

• CoAP Support

• Network (Demo) Application


M2M Server Processes


Note: Highlighted entities are currently supported as separate processes on the Linux platform

M2M Server Integration into 3GPP CN (PS CN)

NodeB RNC

Femto Access Point (FAP)

Iub

MSC/

VLR

CS CN

SGSN GGSN

Operator Owned Network

PDN

HNB GWIuh

Iu

Iucs

Iups Gn Gi mIa

M2M Network App

Control Plane:Authentication, Authorization, & Registration • Device/GW � via GGSN• Network App � via GGSN


HLR

PS CN

NA

E

NGC

M2M Server

mId

CoApHTTPSIP

M2M Device/GW

SC

xGC

UMTS WiFi

Data Plane:• Device/GW initiated � PDP Context routed via GGSN to NGC• Network App initiated � Web Server application routed via Gi to NAE

IP R

outin

g

mIa

M2M Secure Session

In/Out Box

In/Out Box

M2M ServermIa

mId

M2M Network App

M2M

SC

xGC

UMTS WiFi Ka1

KNa1

Ka ??


Box

CoApHTTPSIP

M2M Device/GW Ka1 KNa1

Notes: 1. Application Keys for the M2M Device/GW are per session and are not common

with the M2M Network Application keys. This implies that per communication the M2M Server will cipher/decipher all messages.

2. Investigate how a shared key can be used for direct communication.


M2M WPAN Demonstration

15

Introduction

• This demonstration focuses on IP-based M2M Area

Networks based on IETF standards including CoAP

and 6LoWPAN

– M2M Area Networks is referred to as WPAN in this

presentation

– A WPAN consists of a WPAN Coordinator and WPAN


– A WPAN consists of a WPAN Coordinator and WPAN

Devices

– The latest CoAP protocol was implemented (draft-ietf-core-

coap-01)

– It serves as a building block for an end to end M2M

prototype

16

Demo High Level Description

• Purpose– Demonstrate full IP-based protocol stack running over low-power sensors devices, i.e. WPAN Devices

– Demonstrate two independent IP-based IEEE 802.15.4 WPAN networks on different IEEE 802.15.4 channels

• Use Case Currently Supported– Utilize two separate demo applications, one on WPAN Devices and one on the WPAN Coordinator• Demo application on the Laptop – CoAP Client

– Issue CoAP request message (GET) to read the temperature sensor value at a


– Issue CoAP request message (GET) to read the temperature sensor value at a WPAN Device

• Demo application on WPAN Devices – CoAP Server– Wait for CoAP request message from the Laptop, relayed via the WPAN Coordinator

– Read the temperature sensor which is integrated with each WPAN Device

– Pack the temperature value in a CoAP response message and send it back to the Laptop via the WPAN Coordinator

17

Notes: - Additional use cases (CoAP Methods) support are being added in the next phase of development

Platform Description

• The Laptop (Debian Linux)– Implement Demo application – CoAP Client

– Implement CoAP protocol

– Implement 6LoWPAN protocol stack (BLIP)

– Two USB ports

• WPAN Coordinator (TinyOS)– A Crossbow Micaz node connecting to the Laptop via USB port

– Run IPBaseStation application as a relaying point between WPAN


– Run IPBaseStation application as a relaying point between WPAN Devices and the Laptop

• WPAN Devices (TinyOS)– Crossbow Micaz nodes with a temperature sensor integrated

– Implement Demo application – CoAP Server

– Implement CoAP protocol

– Implement 6LoWPAN protocol stack (BLIP)

18

Demo Network Configuration


Protocol Stack


Software Overview

• Laptop– Demo application

– CoAP support

– 6LoWPAN (BLIP) support

– Serial communication (USB) support

• WPAN Devices

– Demo application

– CoAP support

– 6LoWPAN (BLIP)

support

– 802.15.4 communication


(USB) support

• WPAN Coordinator– IPBasestation

– Serial communication (USB) support



– Sensor reading support

21

Call Flow


Next Steps

• In the coming months, additional functionality will be added to the M2M Gateway, Server, and WPAN implementations including:– Gateway/Server:

• Additional features for existing Service Capability entities

• Implementation of the following Service Capability entities– xREM

– xCB

– xHDR

– xCS

• Additional security features

– WPAN


– WPAN• Additional use cases

– Home automation, home security, ETSI compliant device application registration

– Integrity validation, over-the-air (OTA) updates

• Additional CoAP features– POST, PUT, DELETE

– Caching/proxying

• Low-duty cycle sleeping nodes

• Integration of the Gateway and Server with the WPAN based sensor networks (representing D’ devices with CoAP support) to create an end-to-end ETSI Compliant M2M Prototype

23

Documents

M2M Prototype Demonstration ETSI M2M #12 –Philadelphia, …