Summary of Session 1
Setting the M2M scene
Moderator: Marylin
ETSI TC M2M WS 19-20 October 2010
© ETSI 2010. All rights reserved
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
Viswanathan, Alcatel Lucent
Key actions in M2M :
energy efficiency and managing sustainable development
Security, Privacy, identification, addressing, interworking, become
essential aspects
variety of M2M applications (examples detailed by Cinterion: Electric
vehicles, and mobile health)
New business models emerging with M2M
2
Issues raised and Questions
On EV matters, what is lacking today in terms of standards?
Roaming between charging domains. Communication interfaces 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 (deployment aspects are
simpler) as wireless networks are already available. Wireless is the 1st choice;
maybe other possibilities in the future, but for now 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 network providers
To develop APIs that will be widely adopted, as ETSI 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 even when leaving the home.
More & more applications coming to the market deal with the mobility also
3
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 M2M system (
TC M2M providing guidelines)
Manage high number of devices (firmware updating)
Explore different business models
M2M, B2B, B2B2C, …
And the Winner will be ?
The market will answer
And the market needs open interoperable standards
4
Summary of Session 2
M2M Vertical Applications
ETSI TC M2M WS 19-20 October 2010
Harish Viswanathan,
Alcatel-Lucent
© ETSI 2010. All rights reserved
Highlights from the presentations
Farming in Rural India
Provide GPRS based sensing of moisture levels and automate water
pump turning on/off
Connected Home
Intrusion detection, home automation, temperature control, video
monitoring, safety, healthcare
Fleet Management for Professionals
taxi request dispatch, customer request allocated to the best taxi, taxi
request follow-up, credit card payment, general messages (e.g.
« speed camera at... »), personal messages (e.g. « call your wife
back »), security alarm, with audio monitoring, taxi location
6
Issues
A number of requirements need to be met spanning the device,
network and the application
System Integrator needs Visibility
Having to rewrite the application for different devices/platforms
Agreement that standards are important to solve problems
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
–
–
–
–
–
–
–
–
–
–
downlink messages
Requirements - I
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
standardized format(s) for (timestamped) location data
access to vehicle internal data (current OBD connector is not
enough)
– visibility (communication logs, rejected communications, user
subscription status, past and planned network outages, 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 be reliable
response time. The message from the sensor must reach 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 be 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 visibility
Standards like OMA-DM and network operator APIs provide visibility
10
Summary of Session 3
Smart Energy
Joachim Koss
ETSI TC M2M WS 19-20 October 2010
© ETSI 2010. All rights reserved
Highlights from the presentations
ESNA developed a protocol for communication between meters or
other devices in the grid with data concentrators/substations
Smart City developments in 6 axes: Smart - Economy, - Mobility,
- Governance, - Environment, - Living, and - People
A new generation of services, more intelligent, personalized and
ubiquitous will arise within cities & urban spaces
Project Smart Santander aims at providing a European
experimental test facility for the research and experimentation of
architectures, key enabling technologies, services and
applications for the Internet of Things (IoT) in the context of the
smart city.
Deregulation in the EU energy market creates a new role: DSO
which also needs clear definition of systems and interfaces to
provide interoperability desire for open standards
12
Issues raised
Smart Cities
business models for Smart Cities are still unclear and requires
shaping multiparty stakeholder-system and cooperative business
approach
Smart Metering
No communication technology provides 100% coverage
Life cycle of (smart) meters and telecom are incompatible
13
Possible next steps
Open Smart Grid Protocol
Make public available, ESNA intention is to transfer OSGP into an
SDO standard
Provide a certification process of protocol
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 communication
technologies
14
Summary of Session 4
M2M Architecture Aspects
Enrico Scarrone
ETSI TC M2M WS 19-20 October 2010
© ETSI 2010. All rights reserved
Highlights from the presentations
Open API for M2M applications Karl Ostendorf, Deutsche Telekom:
A common specified interface realised as OpenAPI provides applications with a
rich abstraction of core network capabilities and encapsulating the underlying
communication protocols. This includes transactions, sessions, micro payment,
asynchronous messaging and publish/subscribe metaphors. The API offers an
HTTP binding, designed using REST principles.
Addressing unique M2M challenges with converged gateways
Paul Russel, InterDigital
Integration of standards based solutions for M2M into a converged gateway will
provide service capabilities to offload the network and robust security. It also
brings advanced bandwidth management and self-organizing capabilities and will
fit the needs of the home and business market for smart grids, consumer
electronics and multimedia distribution..
Current and future trends in hybrid cellular and sensor networks
Yongjun Liu, Huawei
The complementary cellular network technology and wireless sensor networks
technology have emerged as a key for Machine-to-Machine (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.
16
Issues raised
Open Standard API are a key enabler for the development of M2M
application
Abstraction from network implementations and technology is
needed
Exposure of network functionality to enrich the support of M2M is
desired
Converged M2M gateways can provide support to M2M services
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 wireless sensor
networks
Hybrid network can provide long term telecommunication support
to M2M managing the technology evolution and replacement
17
Possible next steps
Standardize of M2M API (ongoing in ETSI M2M)
Standardize the M2M functionally of a converged gateway
Support as much as possible combination and integration of
wireless sensor networks with mobile telecom networks
(GPRS/UMTS/LTE)
18
Summary of Session 5
M2M Future Challenges
Robin Duke-Woolley
ETSI TC M2M WS 19-20 October 2010
© ETSI 2010. All rights reserved
Highlights from the presentations
Raising the question of the need for Quality of Service for M2M
applications using mobile networks
Will there be a need for additional numbering for mobile networks
to cater for additional connections required for M2M?
The opportunity to use Java as part of M2M architecture
20
Issues raised
Regarding QoS, to what extent should mobile operators invest in this
when returns from individual applications may be low? 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
this and whether there is a need for number portability for M2M
applications. Also, such numbering may only be required when
sending to such resources. To send out from them, extra 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 medium term solution?
Regarding use of Java, to what extent is this likely to become a
standard for M2M? What are the licensing issues?
21
Possible next steps
Regarding QoS, feedback from Mobile Operators of how they view
this issue would be useful.
Regarding numbering, CEPT is looking now for feedback on this
issue. ECC report on “Numbering and Addressing in M2M
Communications” has been issued.
Regarding use of Java for M2M, further detail on current
implementations of Java for M2M would be useful, along with
licensing detail.
22
Summary of Session 6
M2M International Collaboration
Omar Elloumi
ETSI TC M2M WS 19-20 October 2010
© ETSI 2010. All rights reserved
Highlights from the presentations
OMA has a large number of enablers that map nicely to the ETSI M2M
architecture, in particular OMA DM and CPNS. In addition:
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 progress in bringing IP to
M2M devices. While initial work was around IPv6 and routing for 802.15.4,
ongoing work allows an HTTP like protocol (CoAP) to run on top of
constrained devices… making end2end IP communications a reality
Device, Network and Applications are the main components for M2M. All
have to evolve in order to take into account fundamental characteristics
of M2M communications
3GPP fully recognised the need to evolve mobile access and core
network to allow for cost effective and massive deployments taking into
account fundamental characteristics of M2M. While R10 will mostly
address overload control, several other optimisations are in the pipe for
R11 work
24
Issues raised
Too many standards organisations are dealing with M2M, how
could we effectively coordinate? What is the best way to achieve
a complementary set of standards
GSC15 tasked a special Task Force to serve as a platform to increase
collaboration around M2M, but this is an initial step. Further work is
needed
Security, what should be our approach
There is no security mechanism fits all, security requirements differ
on a case by case basis
Different security mechanisms are feasible but at different price
points
25
Possible next steps
Strengthen coordination
OMA and ETSI M2M need to consider increased collaboration: areas
of interest include device management evolutions (lightweight,
gateway management), but also APIs.
Proposals to TC M2M
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 complementarity
26
Summary of Session 7
Path Towards the Internet of
Things
Patrick Wetterwald
ETSI TC M2M WS 19-20 October 2010
© ETSI 2010. All rights reserved
Highlights from the presentations (1)
M2M is a step towards the Internet of Things
Technology advancements & new business models are behind
explosive growth of M2M
Software defined modem (SDM) may be an enabler for the Internet
of Things
SDM may have a single HW platform, which provides for flexibility
It is worth considering enriching location information with context
data
M2M enablers: M2M infrastructure + IT/business processes
adapted to M2M
Enable customers to identify, locate and use services
28
Highlights from the presentations (2)
SIM cards are present in many M2M devices, and include a
number of applications including payment and security services
Possible to integrate SIM card into IPv4 & IPv6 networks
Possible to remotely manage SIM/Smart cards via the network
SIM card can act as a secure client/server using TCP/IP
EC has a clear policy for the IoT including the framework 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 essential
Future architecture & governance of the IoT is a major challenge
IoT standards shall be developed in an open manner
29
Issues raised
Hardware of conventional modems is inflexible and follows a
difficult development process
Barriers to SDM: computation load, standard complexity, RF
technology
Type approval regime is a barrier, and must dot impede
deployments.
Interoperability and Testing is key
M2M difficulties: current host-centric Internet
Privacy may be a handicap to deployments if the users have to
sign a trust contract
20 – 35 thousand meters per day (IT managers headache)
30
Possible next steps
Be involved in UE IoT initiatives
Follow PPP and related FP7 projects
Check for standards opportunities in TC M2M
Proposals to TC M2M
Investigate closer links with EU R&D projects
Possible synergies with CLOUD technologies – possible to have
common APIs
Considering TESTING and INTEROPERABILITY during the design
process
Consider the role of the SIM in the M2M architecture
31