etsi m2m workshop oct. 2010 conclusions

Summary of Session 1

Setting the M2M scene

Moderator: Marylin© ETSI 2010. All rights reserved

ETSI TC M2M WS 19-20 October 2010

Highlights from the presentations

� Session 1 : Setting the M2M Scene� Welcome Walter Weigel, ETSI Director-General� ETSI TC M2M presentation Marylin Arndt, ETSI TC M2M Chairman,

France Telecom� Future M2M Applications Holger Lenz, Cinterion � Expanding the role of mobile network operator in M2M Harish

2

� Expanding the role of mobile network operator in M2M Harish Viswanathan, Alcatel Lucent

� Key actions in M2M : � energy efficiency and managing sustainable developm ent� Security, Privacy, identification, addressing, inte rworking, become

essential aspects� variety of M2M applications (examples detailed by C interion: Electric

vehicles, and mobile health)� New business models emerging with M2M

Issues raised and Questions� On EV matters, what is lacking today in terms of st andards?

� Roaming between charging domains. Communication int erfaces between charging stations, and also authentication

� Here, only the cellular networks are mentioned, but also PLC networks from utilities to smart meters are to be taken into account…� Cellular networks allow more flexibility. The best communication technology

will be selected. Easier to make it in wireless (de ployment aspects are simpler) as wireless networks are already available . Wireless is the 1 st choice;

3

simpler) as wireless networks are already available . Wireless is the 1 st choice; maybe other possibilities in the future, but for no w wireless is the choice.

� question on the openness of the business models ?� Cellular network to the gateway : this model works best.

� Independence of M2M service providers from the net work providers� To develop APIs that will be widely adopted, as ETS I M2M does.

� Are MNOs able to managing devices?� Very high diversity of devices � Where to put the intelligence (device-gateway side / network side)

� more & more Gateways?� Scalability needed to use the device. Monitoring ev en when leaving the home.

More & more applications coming to the market deal with the mobility �� also mobile embedded devices/phones coming to the market

Possible next steps� Need of standards

� Develop an extension to M2M of the Roaming concept � Manage the complexity of deployment of a complete M 2M system (

TC M2M providing guidelines)� Manage high number of devices (firmware updating)

4

� Explore different business models� M2M, B2B, B2B2C, …

� And the Winner will be ?

The market will answer And the market needs open interoperable standards


M2M Vertical Applications

Harish Viswanathan, Alcatel-Lucent

© ETSI 2010. All rights reservedETSI TC M2M WS 19-20 October 2010


� Farming in Rural India� Provide GPRS based sensing of moisture levels and a utomate water

pump turning on/off

� Connected Home� Intrusion detection, home automation, temperature c ontrol, video

6

� Intrusion detection, home automation, temperature c ontrol, video monitoring, safety, healthcare

� Fleet Management for Professionals� taxi request dispatch, customer request allocated t o the best taxi, taxi

request follow-up, credit card payment, general mes sages (e.g. « speed camera at... »), personal messages (e.g. « cal l your wife back »), security alarm, with audio monitoring, taxi location

Issues

� A number of requirements need to be met spanning th e device, network and the application

� System Integrator needs Visibility

� Having to rewrite the application for different dev ices/platforms

� Agreement that standards are important to solve pro blems� Agreement that standards are important to solve pro blems

� There is room for innovation despite standards

� There is no single entity that will be offering the services in the connected home

� Network operator and 3rd party applications

7

Requirements - I– downlink messages– transmit messages to a group of addressees– groups are defined dynamically by the system– high priority acknowledged message– remote activation of audio– audio and data transmitted at the same time– group fonction, as seen in previous slides– ensure coverage all over taxi operating zone– ensure coverage all over taxi operating zone– standardized format(s) for (timestamped) location da ta– access to vehicle internal data (current OBD connec tor is not

enough)– visibility (communication logs, rejected communicat ions, user

subscription status, past and planned network outag es, etc.)

8

Requirements - II

� Multi-channels bi-directional communication

Traffic/bandwidth control (can be huge)

Responsiveness/latency of remote services

Openness to new services

� The GSM service that we can use for this needs to b e reliable response time. The message from the sensor must rea ch to central unit at least in x mins, always.

� The service has to be reliable. There should not be any data loss.

� The service needs to be cost effective.

� The M2M devices designed for this service, should b e low cost.

9

Next Steps

� ETSI M2M and other relevant standards to take into account the various requirements that were discussed

� Ensure that APIs/functions provide end-to-end visib ility� Standards like OMA-DM and network operator APIs pro vide visibility

10


Smart Energy

Joachim Koss© ETSI 2010. All rights reserved



� ESNA developed a protocol for communication between meters or other devices in the grid with data concentrators/s ubstations

� Smart City developments in 6 axes: Smart - Economy, - Mobility,- Governance, - Environment, - Living, and - People

� A new generation of services, more intelligent, per sonalized and ubiquitous will arise within cities & urban spaces

12

ubiquitous will arise within cities & urban spaces� Project Smart Santander aims at providing a Europea n

experimental test facility for the research and exp erimentation of architectures, key enabling technologies, services and applications for the Internet of Things (IoT) in th e context of the smart city.

� Deregulation in the EU energy market creates a new role: DSOwhich also needs clear definition of systems and in terfaces to provide interoperability �� desire for open standards

Issues raised � Smart Cities

� business models for Smart Cities are still unclear and requires shaping multiparty stakeholder-system and cooperati ve business approach

� Smart Metering� No communication technology provides 100% coverage

13

� No communication technology provides 100% coverage� Life cycle of (smart) meters and telecom are incomp atible

Possible next steps� Open Smart Grid Protocol

� Make public available, ESNA intention is to transfe r OSGP into an SDO standard

� Provide a certification process of protocol

� Proposals to TC M2M

14

� Proposals to TC M2M� To base architecture on IPv6� Considering specifications for overall Smart Meter Network

research is needed on functionality and performance� Considering gateway as central device in this SM/SG concept

determine functional specification for various comm unication technologies


M2M Architecture Aspects

Enrico Scarrone© ETSI 2010. All rights reserved



� Open API for M2M applications Karl Ostendorf, Deuts che Telekom: A common specified interface realised as OpenAPI pr ovides applications with a rich abstraction of core network capabilities and e ncapsulating the underlying communication protocols. This includes transactions , sessions, micro payment, asynchronous messaging and publish/subscribe metaph ors. The API offers an HTTP binding, designed using REST principles.

� Addressing unique M2M challenges with converged gat ewaysPaul Russel, InterDigital

16

Paul Russel, InterDigitalIntegration of standards based solutions for M2M in to a converged gateway will provide service capabilities to offload the network and robust security. It also brings advanced bandwidth management and self-organ izing capabilities and will fit the needs of the home and business market for s mart grids, consumer electronics and multimedia distribution..

� Current and future trends in hybrid cellular and se nsor networksYongjun Liu, HuaweiThe complementary cellular network technology and w ireless sensor networks technology have emerged as a key for Machine-to-Mac hine (M2M) applications. Hybrid Cellular and sensor networks enable reliable , long lifetime and cost effective ubiquitous services. In this paper, this network convergence design is o Smart Energy and Automotive Service applications.

Issues raised � Open Standard API are a key enabler for the develop ment of M2M

application� Abstraction from network implementations and techno logy is

needed� Exposure of network functionality to enrich the sup port of M2M is

desired

17

desired� Converged M2M gateways can provide support to M2M s ervices

and offload the network. These nodes shall support security and self configuration to make easier installation and configuration

� M2M services are supported by means of network that are provided by integration of mobile networks with wir eless sensor networks

� Hybrid network can provide long term telecommunicat ion support to M2M managing the technology evolution and replac ement

Possible next steps� Standardize of M2M API (ongoing in ETSI M2M)

� Standardize the M2M functionally of a converged gat eway

� Support as much as possible combination and integra tion of wireless sensor networks with mobile telecom networ ks

18

wireless sensor networks with mobile telecom networ ks (GPRS/UMTS/LTE)


M2M Future Challenges

Robin Duke-Woolley© ETSI 2010. All rights reserved



� Raising the question of the need for Quality of Ser vice for M2M applications using mobile networks

� Will there be a need for additional numbering for m obile networks to cater for additional connections required for M2 M?

20

� The opportunity to use Java as part of M2M architec ture

Issues raised � Regarding QoS, to what extent should mobile operato rs invest in this

when returns from individual applications may be lo w? There was a concern that the revenue generated may not justify the level of resource used to set up this infrastructure.Is this a short term versus longer term issue?

� Regarding numbering, many points were raised about the need for

21

� Regarding numbering, many points were raised about the need for this and whether there is a need for number portabi lity for M2M applications. Also, such numbering may only be requ ired when sending to such resources. To send out from them, e xtra numbers may not be required. It is also expected that IPv6 will cater for this in the longer term. Is there a need for a short to med ium term solution?

� Regarding use of Java, to what extent is this likel y to become a standard for M2M? What are the licensing issues?

Possible next steps� Regarding QoS, feedback from Mobile Operators of ho w they view

this issue would be useful.

� Regarding numbering, CEPT is looking now for feedba ck on this issue. ECC report on “Numbering and Addressing in M2 M Communications” has been issued.

22

� Regarding use of Java for M2M, further detail on cu rrent implementations of Java for M2M would be useful, al ong with licensing detail.


� OMA has a large number of enablers that map nicely to the ETSI M2M architecture, in particular OMA DM and CPNS. In add ition:� New M2M specific activities are taking place: e.g. lightweight DM� Parlay RESTful binding should also be of interest ( location, messaging, etc)

� The IETF and IPSO alliance have made a great progre ss in bringing IP to M2M devices. While initial work was around IPv6 and routing for 802.15.4,

24

ongoing work allows an HTTP like protocol (CoAP) to run on top of constrained devices… making end2end IP communication s a reality

� Device, Network and Applications are the main compo nents for M2M. All have to evolve in order to take into account fundam ental characteristics of M2M communications

� 3GPP fully recognised the need to evolve mobile acc ess and core network to allow for cost effective and massive dep loyments taking into account fundamental characteristics of M2M. While R 10 will mostly address overload control, several other optimisatio ns are in the pipe for R11 work

Issues raised � Too many standards organisations are dealing with M 2M, how

could we effectively coordinate? What is the best w ay to achieve a complementary set of standards� GSC15 tasked a special Task Force to serve as a pla tform to increase

collaboration around M2M, but this is an initial st ep. Further work is needed

� Security, what should be our approach

25

� Security, what should be our approach� There is no security mechanism fits all, security r equirements differ

on a case by case basis� Different security mechanisms are feasible but at d ifferent price

points

Possible next steps� Strengthen coordination

� OMA and ETSI M2M need to consider increased collabo ration: areas of interest include device management evolutions (l ightweight, gateway management), but also APIs.


26

� Fully engage in the GSC initiated Task Force about collaboration and coordination around M2M

� Consider endorsement of some of the OMA work incl. CPNS, APIs and DM

� Work with TIA TR50 to avoid overlap and seek comple mentarity

Highlights from the presentations (1)

� M2M is a step towards the Internet of Things

� Technology advancements & new business models are b ehind explosive growth of M2M

� Software defined modem (SDM) may be an enabler for the Internet of Things

28

of Things

� SDM may have a single HW platform, which provides f or flexibility

� It is worth considering enriching location informat ion with context data

� M2M enablers: M2M infrastructure + IT/business proc esses adapted to M2M

� Enable customers to identify, locate and use servic es

Highlights from the presentations (2)

� SIM cards are present in many M2M devices, and incl ude a number of applications including payment and securi ty services

� Possible to integrate SIM card into IPv4 & IPv6 net works

� Possible to remotely manage SIM/Smart cards via the network

� SIM card can act as a secure client/server using TC P/IP

29

� SIM card can act as a secure client/server using TC P/IP

� EC has a clear policy for the IoT including the fra mework for R&D

� EU is investing BILLIONS in the IoT

� RFID tags get smaller, number of connected objects increases

� Privacy and protection of personal data is essentia l

� Future architecture & governance of the IoT is a ma jor challenge

� IoT standards shall be developed in an open manner

Issues raised � Hardware of conventional modems is inflexible and f ollows a

difficult development process

� Barriers to SDM: computation load, standard complex ity, RF technology

� Type approval regime is a barrier, and must dot imp ede deployments.

30

deployments.

� Interoperability and Testing is key

� M2M difficulties: current host-centric Internet

� Privacy may be a handicap to deployments if the use rs have to sign a trust contract

� 20 – 35 thousand meters per day (IT managers headach e)

Possible next steps

� Be involved in UE IoT initiatives� Follow PPP and related FP7 projects� Check for standards opportunities in TC M2M


31

� Proposals to TC M2M� Investigate closer links with EU R&D projects� Possible synergies with CLOUD technologies – possibl e to have

common APIs� Considering TESTING and INTEROPERABILITY during the design

process� Consider the role of the SIM in the M2M architectur e

etsi m2m workshop oct. 2010 conclusions

Technology

m2m devices

steps etsi m2m

complete m2m system

etsi tc m2m chairman

m2m harish viswanathan

m2m scene moderator

different business models

rights reserved etsi