ETSI M2M WS 4.-5. June 2008

1

Architecture for the Internet of Things: focus on API,Inge Grønbæk, Telenor R&I, inge.gronbak@telenor.com.

ETSI Workshop on Machine to Machine Standardization, 4 - 5 June 2008 - ETSI,Sophia Antipolis, France.

ETSI M2M WS 4.-5. June 2008 2

Outline

• Vision

– Cooperation coordination and selective standards

– Secure API separating network technologies and services

– Fair and flexible compensation

• Architecture

– API

– Backbone

– Device networks

• Role of NGN and IMS

• Recommendations

ETSI M2M WS 4.-5. June 2008 3

Vision for the core Internet of Things

• Migrating the Internet to the true all-IP “Internet ofThings”, through:

– Cooperation and coordination, with standards development, toensure ubiquitous services in an enlarged competitive panEuropean market.

– Fair and flexible compensation.

– Architecture with secure API:

– decoupling applications and network infrastructure.

– Decoupling of API methods (i.e. primitives) and data type definitions

– supporting service relocation and replication.

– decoupling backbone and device networks.

– integrating fixed and mobile networks.

– integrating sessions and the connectionless class of services.

– Early piloting and deployment on European scale.

ETSI M2M WS 4.-5. June 2008 4

API, backbone and device networks

Service C

Service B

Service A

Businesslogic

Service provider B

PublicNetwork Service

Platform

DataRepos.

coBusiness

logicco

Telco / Newco position

Service provider A

DeviceNetwork

Telcohub

Mobileor

Fixed

co

co

co

co

co

co coAPI

co ServicePlatform

APILegend:

API

API

ETSI M2M WS 4.-5. June 2008 5

OSA Parlay architecture

Parlay Gateway

Parlay X Web Services

Parlay X APIs

Parlay APIs

Parlay XApplications

ParlayApplications

Network Protocols(e.g. SIP, INAP etc)

Network Elements

Increasingabstraction

May be used

ETSI M2M WS 4.-5. June 2008 6

API, flexibility and interconnect

StandardInternet

layer

Multicast / BroadcastMobility, locationQoS control of IP bearerIdentification and securityIP

”Freedom”

”Freedom”

InterconnectName resolutionRoutingManagement

Application layer

API:

ETSI M2M WS 4.-5. June 2008 7

Service aggregation from sub-layers

CO applications

-------------------------- Layer 6+ (API for basic applications)

CO application components (Naming, Presence, Events, Logging,storage and retrieval, Application level routing)

-------------------------- Layer 6 (CO vocabulary)

Presentation

-------------------------- Layer 5 (Diverse sessions)

Session

-------------------------- Layer 4 (Diverse transport capabilities)

Transport

-------------------------- Layer 3+ (Enhanced network service)

IP bearer

• Multicast / Broadcast

• Mobility, location

• QoS control of IP bearer

• Identification, security including AAA

-------------------------- Layer 3 (Basic network service)

Basic IP bearer

BackboneInterconnect(Name resolutionRoutingManagement)

Standard“Internet

layer”

In principle relayedtransparentlythrough theBackbone

ETSI M2M WS 4.-5. June 2008 8

CO higher layers

Transport-Selection(Destination-CO,Protocol)

Transport service. The abstract service for explicit transportprotocol selection (TCP, UDP, MQTT, NIL)

Invite(Destination,Profile)

Session service. In this context a session shall be understoodto represent the state of active communication betweenconnected objects; i.e. it is not required to be established bye.g. the Session Initiation Protocol (SIP).

Applicationdependent.(Pendingstandardization)

Presentation service. Defines the vocabulary for (controlof) CO service applications; i.e. the data structures andcommands required for COs to interoperate, e.g. for anadvanced control and surveillance application.

The actual monitoring or control protocol may be proprietary,related to actual sensors or controllers, or standards may beapplied.

Storage,retrievalEvent reportingPresenceApplicationroutingEtc.

Application component sub-layerThe application component sub-layer functionality may be

offered as either complete services or as additional buildingblocks for in-house or third party services. The followingrepresent example services.

ETSI M2M WS 4.-5. June 2008 9

“Internet layer”

ID (Naming)SecurityData transmissionMulticastMobilityQoS controlLocation & statusBasic IP bearer

Network service at the “Internet layer”The Internet layer is the IP network layer,

extended to include the inter-domainfunctionality required for end-to-endmaintenance of QoS control, Security, Mobility,Location, Multicast, Name resolution, Routingand Management.

This functionality is required to be maintainedacross interconnected domains of the Internetof Things, to support ubiquitous multifunctionalservices. This functionality is therefore criticalfor end-to-end service provisioning, sincenetwork elements in interconnected domainsneed to contribute to the functionality on a hop-by-hop basis.

ETSI M2M WS 4.-5. June 2008 10

Management

CompensationSoftware upgradesConfigurationProvisioning/fulfilmentAssurance/fault handling

ManagementThe management comprises functionality of genericnature that can not logically be confined to aspecific layer of the OSI stack.

ETSI M2M WS 4.-5. June 2008 11

Objects and network elements

RVS: Rendezvous ServerRH: Resolution HandlerONS: Object Naming ServerGW: Gateway

HITRadioGW

HITGW

RVSRH

ONSDNS

GPRS

BackboneIP network,e.g. Internet

IMSParlay-X

CO CO CO

GPRSHITGW

Devicenetwork

Devicenetwork

Bootstrap

Logging,Rating,Billing

Hosting

”Connected Objects”

”Connected Objects”

ETSI M2M WS 4.-5. June 2008 12

HIT gateway architecture

IPv4

HIP with security,mobility and multicast

TCP UDP

HTTP

Web services(XML, WSDL, UDDI)

E.g. ETHERNET

CO application

Device sideMappingBackbone side

(part) application

CO presentation

Transparent?

Transparent?

Transparent?

Transparent?

E.g. MAC

ETSI M2M WS 4.-5. June 2008 13

Device Network

• The interfaces towards the backbone must be obeyed.

• Benefits of standards (e.g. allowing high volume/low costVLSI implementation),

– Such standards are considered less urgent then the backbonestandard since the interconnect of diverse devices is possible aslong as the backbone interface definitions are obeyed.

– Flexibility is key. Rate of development is expected to exceedMore’s law.

– IETF WG roll active on device network routing

ETSI M2M WS 4.-5. June 2008 14

NGN and IMS backbone capabilities

• IMS may be used to support the functionality of the CO service-primitives.

• The major challenge is to handle small amounts of real-timedata efficient within the session oriented framework of IMS.

• The Use of the SIP MESSAGE method for such data exchange isa possible solution, but may result in functional redundancy.

• A better solution would be to offer a general QoS controlledconnectionless service at the network layer, i.e. the IP bearer.

• The session orientation of IMS makes it very suitable for highvolume streaming, but multicast is missing for low volumetransient real-time data.

• The bottom line is that IMS supports high volume streamingvery well, but IMS needs to be upgraded to effectively supportthe class of non session oriented applications.

ETSI M2M WS 4.-5. June 2008 15

Summary of core functionality

• Ubiquitous (cross domain) support of CO services.– Name and addressing flexibility, e.g. not limited by IP constraints.

– New services require only additional data definitions and builds onexisting service components accessed via standard API.

– CO service connectivity with UMTS/GPRS.

– Access to OSA Parlay functionality.

• Security.

• Privacy (in terms of location and identity).

• Mobility management (including network mobility andindirection).

• M:N multicast also for mobile objects.

• Presence, location and Notification.

• Efficient interfacing of proprietary and/or power constraineddevices.– Protocol-stack flexibility.

– Topological hierarchy and multi-homing

ETSI M2M WS 4.-5. June 2008 16

Recommendation

• Commence ETSI standards work on backbone issues

– ”The Internet of Things is the Internet enhanced to supportubiquitous services also for Connected Objects.”

Telenor contributions available at:http://portal.etsi.org/docbox/ERM/Open/RFIDWorkshop200712/ DOCUMENTS:

– RFID02_04, (API)

– RFID02_11, (Architecture)

Thank You for Your attention!