Status of Machine to Machine Standards work in TC M2M
and oneM2M
Source : David Boswarthick (Technical Officer TC M2M).
Source :
David Boswarthick (Technical Officer TC M2M).
Many thanks to the various contributors from TC M2M
Setting the
Setting
the
Scene
2
Where do we stand in the maturity cycle of M2M?
in the maturity cycle of M2M?
Government stimulus programs boost M2M standards:
EC mandate to ETSI/CEN/CENELEC to develop EU standards for Smart
Metering (M/441), and later on for Smart Grid (M/490)
NIST mandated to pilot delivery of standards for Smart Grids
Principal focus of ETSI M2M:
prepare the deployment
“transition phase” to horizontal
platforms
3
Source: of graphic: The Yankee Group
Rationale
The M2M market is taking‐off:
g
• Government and industry initiatives
• Telecom actors business opportunity
• Ubiquitous networks and affordable hardware
Fragmented industry
• Industry verticals are solving their M2M needs on their own
I d t
ti l
l i th i M2M
d
th i
• Customised solutions abound
• but there is much commonality (authentication, security, access y(
,
y,
rights)
• Economies of scale necessary for M2M are difficult to achieve
¾Fast and global standardization is a key enabler to There is a need for a common efficient, easily and h
i
df
ffi i
il
d
widely available M2M Service Layer, which can be remove the technical barriers and ensure interoperable readily embedded within various hardware and
readily embedded within various hardware and software. M2M services and networks
4
OneM2M overview
Value chain evolution for Telcos
Application
pp
Layer Management M
t
Services
(SIM, Module, Connectivity)
Connectivity
Devices Application
Layer Service Enablement
Data
Management Management
Services
Connectivityy
Revenue distribution shift to:
— Support business decisions with M2M data intelligence.
data intelligence.
— Secure and manage M2M data.
— Identify and create new applications for M2M.
Devices Revenues are moving towards the service enablement layer and the support of data access, storage, management and security
5
Enabling information sharing
Tomorrow
SService i
Enablement
Today
Data
Management Services
Management Services
Connectivity
Connectivity
Connectivity
D i
Devices D i
Devices Devices
Devices Yesterday
Connectivity
Deployment
Integration
ETSI M2M is based on a “Store and Share” paradigm
The data may be made available in the platform to the other
The data may be made available in the platform to the other applications, interested application are notified by means of subscription
Privacy is ensured by a strict Access Rights Management
6
ETSI M2M
ETSI M2M
7
ETSI M2M Vision
Reduced complexity, R
d d
l it
Standard APIs and protocols,
Multi –
Reduced initial investment costs.
Application
Same service layer for many verticals
Same service layer for many verticals
Simplified applications development,
i lifi d
li i
d l
M2M Service Enabling vendor ecosystem, Reduces solution cost and improves Capabilities, interoperability.
R
Resource Based
B d
Business Application #1
Business Application #2
Business Application #N
Scalable horizontal solution,
Horizontal Shorter time to market
Re‐use of platform to test and roll out Common Application Allows to trail new services, Data
Multi‐Service new services,
Existing Standards
Infrastructure
Less expensive to roll out than p
BetterPlatform
Better network efficiency
network efficiency
R
d
dedicated solution. Re‐use and Network independent, Gateway
use best networks for deployment Technology
needs,
Local NW
Independent
Leverage on underlying networks
Leverage on underlying networks Device
Device
functionality
8
Integration
Transport Network 2
Transport Network 1
IP
Full package toolbox
End to End
Reducesd integrationtimeand cost
g
Device
Device
Simplified M2M Architecture
M2M Area Network
M2M Area Network
M2M Application
M2M A li ti
DIRECT CONNECT
Service Capabilities
M2M
Core
M2M
Gateway
Client
Application
DIRECT CONNECT
9
… based on existing Technologies
M2M Application
M2M A li ti
Smart Energy
gy
Core Networks
• 3GPP (GPRS, EPC)
• ETSI TISPAN
• ATTM
• NGN
Service Capabilities
M2M
Core
M2M Area Networks
M2M Area Network
M2M Area Network
• PLC
• SRD
• UWB
• ZigBee
DIRECT • M-BUS
M BUS
CONNECT
• Wireless M-BUS
• IEEE 802.15
•
Smart User
Smart
Health
Client
Application
Smart Transport
p
10
M2M
Access Networks
Gateway
• xDSL
• Hybrid
FiberCoax
y
• PLC
• Satellite
• GERAN, UTRAN, eUTRAN
• WLAN
DIRECT • SRDs
CONNECT
• UWB
• WiMAX
Overview of ETSI M2M
Defines a Defines
a “Service
Service Capability Capability
Layer” (SCL) on top of connectivity layers • SCL in network server, SCL in network server
gateways and devices.
• SCL does registration, access
rights, security&authentication,
data‐transfer (containers), subscribe / notify, groups …
API for applications is based on
REST principles allowing
• Scalability (stateless, idempotent)
• Unreliable connections
• Binding to e.g. HTTP, CoAP
Re‐uses TR‐069 (from BBF) and OMA DM (from OMA) for device management
11
M2M high level system overview
Application
pp
(e.g. Smart Metering application)
M2M Application Domain
mIa
User interface to application
e.g. Web portal interface
(usage monitoring,
user preferences, …)
ETSI M2M Service Capabilities
M2M Server
mId
Network
3GPP, Fixed, IP..
M2M Network Domain
Based on existing standards and
technologies, e.g.: 3GPP, TISPAN, IETF, …
Scope of
ETSI M2M
M2M Core
M2M Devices /
Gateways
M2M Service
Capabilities
M2M Gateway
M2M Gateway
dIa
M2M Area
Network
M2M Service
Capabilities
dIa
M2M Device Domain
Based on existing standards and
technologies, e.g.: DLMS, CEN, CENELEC,
PLT, Zigbee, M-BUS, KNX, etc.
12
M2M D’
Device
Application
Application
M2M Device
M2M Device(s)
ETSI M2M defines 3 interfaces
mIa ... application Ù Service Capabilities in the M2M Core
• Service capabilities are exposed (e.g. via an API) to applications in the form of service capability features
form of service capability features. dIa
... application Ù Service Capabilities in the M2M Device // GW
GW
• The service capability features at the dIa and at the mIa are assumed to be identical if no difference is explicitly defined.
mId … SC in the M2M Core Ù SC in the M2M Device / GW
• Reference point using IP connectivity, it includes interface between the Service Capability Client and the Service Capability server, and it the
Service Capability Client and the Service Capability server and it
makes parallel use of existing management protocols (including TR 069)
¾ Î ETSI M2M is modelling these interfaces following a RESTful approach. 13
13
TC M2M– Release 1
Release 1
Release 1
Core Release1 Finalized in November 2011. (http://docbox.etsi.org/M2M/Open/Latest_Drafts/ and www.etsi.org)
Including:
• Stage 1: Service and operational requirements for a multiservice M2M system
• Architecture: SCL, device, gateways and network platforms, RESTful resources A hi
SCL d i
d
k l f
RESTf l
•
•
•
information model and relates procedures, service bootstrap, reference points (dIa, mId, & mIa definition), legacy devices, etc
Device Management (with BBF and OMA DM)
Device Management (with BBF and OMA DM)
Security (Key management and Automated Bootstrapping)
Stage 3 (API primitives and parameter definitions, HTTP / CoAP Binding)
Release 1 core specs:
WI Ref
14
ETSI Ref
Specification Name
DTS/M2M‐00001
TS 102 689
TS 102 689
M2M service requirements
M2M service requirements
DTS/M2M‐00002
TS 102 690
M2M Architecture
DTS/M2M‐00010
TS 102 921
M2M Stage 3 Interfaces
ETSI TC M2M deliverables status
Use Cases [Stage 0]
TR 102 691
TR 102 732
TR 102 857
TR 102 898
TR 102 897
Smart Metering
eHealth
Connected Consumer
Automotive
City automation
TS 102 689
TR 101 584
TR 102 725
M2M S
Service
i
Requirements
Semantic
S
ti supportt
for M2M data
M2M Definitions
D fi i i
TS 102 690
TR 101 531
TR 102 167
M2M Functional
Architecture
Re-use of 3GPP
nodes by M2M SC
layer
Threat analysis &
counter measures to
M2M service layer
TS 102 921
TR 102 966
TS 101 603
M2M Comms;
mIa, dIa, mId interfaces
Interworking with
M2M Area
Networks
Service Layer
interworking with
3GPP networks
P
TR 102 935
Stage 1
Smart Grid
impacts on M2M
P (R1)
TS 103 092
OMA DM
compatible
Management
Objects
Stage 2
P
TS 103 093
Stage 3
BBF TR-069
compatible
Management
Objects
P (R1)
P
15
P (R1)
P
= Published
P
TC M2M future activities
TC M2M works on M2M Release 2,, and alreadyy set p
priorities;;
• charging, data models and semantics, security extensions, the
standardised use of operators’ network interfaces, multi‐operator
i platforms,
l tf
i discovery,
di
A
N t
k Management
M
t and
d
service
service
Area
Network
service interworking profiles.
j area of work are;;
The Two major
• Standardization of the Interworking with the 3GPP and 3GPP 2
•
networks
The study of solutions for the definition of common semantic rules
between applications belonging to different industrial segment, to
assure the understanding of the shared data
TC M2M is also looking at testing;
• DTS/M2M‐00019/DTS 103 104 Interoperability Test Specification for
CoAP Binding of ETSI M2M Primitives, Rapporteur: Zach Shelby.
16
oneM2M
17
From Technical Bodies to Partnerships
ETSI TC M2M
ETSI
TC M2M
established 2008. First set of M2M platform standards to market in 2011.
oneM2M Partnership p
project established July 2012
July 2012.
18
© ETSI 2012. All rights reserved
Evolution of ETSI TC M2M into a global partnership project
into a global partnership project
Leading regional SDOs have agreed to create a global Leading
regional SDOs have agreed to create a global
harmonisation partnership
• To prepare, approve and maintain globally applicable, access
To prepare approve and maintain globally applicable access‐
independent technical specifications and reports related to M2M solutions, with initial focus on the Service Layer
• same as ETSI M2M, some of whose work will be transferred to oneM2M and form the basis for further OneM2M work. ETSI M2M will refocus on EU issues
will refocus on EU issues.
• With the opportunity for broad and equitable participation by p
,
g
all stakeholders in the M2M marketplace, including manufacturers, service providers and end users from all industries
• avoiding any duplication of work between SDOs involved in the same domain of M2M Service Layer
19
OneM2M overview
Scope of oneM2M
Common set of Service Layer capabilities
Common
set of Service Layer capabilities
Access independent view of end‐to‐end services
Open /standard interfaces , APIs and protocols
Security, privacy, and charging aspects
Reachability and discovery of applications
Interoperability including test and conformance
Interoperability, including test and conformance specifications
Identification and naming of devices and applications
Identification and naming of devices and applications
Management aspects (including remote management of entities
20
OneM2M overview
Founding SDOs (Partner Type 1)
21
OneM2M overview
Supporters (Partner Type 2)
Industry organisations/associations y g
/
that have applied to join as pp
j
Partner Type 2, or have shown interest in applying:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
22
OMA
Open Mobile Alliance p
BBF
Broadband Forum
CDF
Connected Device Forum
CDG
C
G
CDMA Development Group
C
e e op e t G oup
Continua
Continua Health Alliance
IEEE SA
IEEE Standards Association
GSM Association
GSMA
GSM Association
HGI
Home Gateway Initiative
IPSO Alliance IP for Smart Objects
IPv6 Forum
IPv6 Forum IPv6 Forum
IPv6 Forum
ITU
International Telecommunication Union
KSGA
Korea Smart Grid Association
Mandat Intl represents FP7 IoT6
represents FP7 IoT6
Mandat Intl
Zigbee
Zigbee Alliance
OneM2M overview
((accepted 13 Sep 2012)
p
p
)
(applied 13 Sep 2012)
(applied 17 Sep 2012)
(applied 6 Aug 2012)
(applied 6 Aug 2012)
(applied Sep 2012)
(applied Sep 2012)
THANK YOU FOR YOUR ATTENTION
& ANY QUESTIONS?