The oneM2M Partnership Project

Group Name: oneM2M ShowcaseSource: Peter Nurse, Qualcomm Inc., c_pnurse@qti.qualcomm.comMeeting Date: 2014-12-09Agenda Item: Setting the Scene

Overview

• goals

• motivation

• value proposition

• participation

• current state

Motivation

• Many industries are addressing machine-to-machine (M2M) solutions and applications that frequently require custom hardware and software, typically resulting in longer time-to-market, higher development costs, and higher operational expenses– Currently developed solutions are similar but unique to each industry

• M2M services often rely upon telecommunications providers for connectivity between the myriad of devices in the field and the M2M application servers

• Telecommunications companies are optimizing networks to more effectively meet industry needs for M2M communications and are in the process of developing standards for these optimizations

• Common cost-efficient, easily and widely available M2M Service Layer, readily embedded within various hardware and software

• Cooperative M2M community standards activity which leads to regularly enhanced releases of the M2M Service Layer specifications

Value Proposition

• Boost M2M economies of scale and shorten time-to-market– Lower capital and operating expenses

– Foster and optimize future investments of all involved parties

• Simplify development of applications – Intra- and inter-industry integration of services

– Allow same application to be used across different service platforms

• Leverage the worldwide network for enhanced potential of services and to expand business opportunities– Greater reach of services through broader network interoperability

• Reduce standardization overlap and confusion and provide ongoing standards support– Enhance interoperability

– Reduce market fragmentation

– Future proof services via collaboration

– Enhance security and reliability

Motivation

Transportation

Rail

SeaLand Air

Road

Car Truck

Motivation

Transportation

Application

Energy

Application SmartCity

Building Automation

Application

Common Service LayerCommon functions applicable to applications in different domains

Goals

• Develop one globally agreed M2M Service Layer specification• Consolidate current M2M Service Layer standards activities into the Global

Initiative• Identify a common Service Layer architecture and identify gaps where

existing standards do not fulfill the requirements and provide or initiate the creation of specifications to fill these gaps

• Develop and maintain Technical Specifications and Technical Reports in support of the M2M common Service Layer architecture framework

• Collaborate with wireless and wireline SDOs and fora responsible for developing standards for Core and Access Networks

• Collaborate with SDOs and fora in charge of developing the vertical markets (i.e., domain-specific) aspects of M2M applications

• Develop specifications that will help drive the industry towards a goal of lower operating expenses, lower capital expenses, faster time-to-market, and mass-market economies of scale

Participation

• Partner Type 1

• Partner Type 2

• Member

• Associate Member

Partners (Type 1)

– Legal entity and member-based organization

– IPR policy compatible with other Partners Type 1

– Contribute resources to the operation of oneM2M

– Provide strategic direction – no technical contributions

– Admit organizations as oneM2M Members

– Transfer work that overlaps with the work of oneM2M

– Transpose all relevant oneM2M Technical Specifications and Technical Reports into its own relevant deliverables through its normal process

Partners (Type 1)

China CCSA - China Communications Standards Association

Europe ETSI - European Telecommunications Standards Institute

JapanARIB - Association of Radio Industries and BusinessesTTC - Telecommunication Technology Committee of Japan

Korea TTA - Telecommunications Technology Association

North AmericaATIS - Alliance for Telecommunications Industry SolutionsTIA - Telecommunications Industry Association

Partners (Type 2)

– Legal entity and member-based organization

– IPR policy compatible with that of the Partners Type 1

– Contribute resources to the operation of oneM2M

– Provide strategic direction via Steering Committee

– Provide technical input via the Technical Plenary

Members

• Member– Legal entity– Provide technical input via the Technical Plenary

as a consequence of admission via Partner Type 1– under IPR policy of the admitting Partner Type 1

• Associate Member– Government or Regulatory agency– provide input via the Technical Plenary that is

limited to clarifications regarding regulatory matters and other informative contributions

Participation (Type 2 and Associate)

Type 2 BroadBand Forum

Home Gateway Initiative

Next Generation M2M Forum

Open Mobile Alliance

Personal Connected Health Alliance (Continua)

Associate Ministry of Science, ICT and Future Planning (MSIP) (Korea)

National Institute of Standards and Technology (NIST) (USA)

United States Department of Transportation (USA)

Brief History

2011-03-17 Industry Group teleconference to explore industry interest

2011-07-21 First F2F meeting of SDOs

2012-07-24 Launch of oneM2M

2012-07-24/26 First meeting of Steering Committee of oneM2M

2012-09-24/28 First meeting of Technical Plenary

2014-08-01 Candidate Release

2014-12-09 Showcase

Current State (workflow)

• Deliverables:– Technical Report (TR)

– Technical Specification (TS)

Stag

e 1

Use Cases,Requirements

Stag

e 2

Architecture,Security

Stag

e 3

Protocols,Security,Device Management

Current State (structure)

SC(Steering Committee)

FC(Finance Committee)

MARCOM(Marketing &

Communications)

LG(Legal Group)

MP(Methods & Procedures)

TP(Technical Plenary)

WG 1(Requirements)

WG 2(Architecture)

WG 3(Protocols)

WG 4 (Security)

WG 5(Management Abstraction &

Semantics)

WG 6(Testing)

AHG Work Programme

Management

AHG Methods of Work

Current State (timeline)

aubergine

TP #12

candidate

release

Jul

2014

Jan

2015

TP 15

full

release

TP #13

Sep

2014

TP #14

Nov

2014

oneM2M

Showcase

Dec 9

2014

Current State (aubergine)

Deliverable Version

TS 0001 - Functional Architecture 1.0.0

TS 0002 - Requirements 0.6.2

TS 0003 - Security Solutions 0.7.0

TS 0004 - Service Layer Protocol Core Specification 0.6.0

TS 0005 - Management Enablement (OMA) 0.3.0

TS 0006 - Management Enablement (BBF) 0.4.0

TS 0008 - CoAP Protocol Binding 0.5.0

TS 0009 - HTTP Protocol Binding 0.4.3

TS 0011 - Definitions and Acronyms 1.0.0

http://www.oneM2M.org/candidate_release

Current State (deliverables)

• «add current document set »

– it’ll be busy, but it’s a take-away

• if you like what you see, get involved

– you’ll learn more

– you can help develop and enhance

• if you don’t like what you see, get involved

– we’ll both learn more

– you can help develop and enhance

• get involved

© 2014 oneM2M Partners

Thank you

for your attention

22