m2m stategy of the open mobile alliance - fraunhofer fuseco forum 2011

OMA’s Strategy for Machine-to-Machine Communications

Musa Unmehopa

Technical Plenary Chairman, OMA

Senior Manager, Alcatel-Lucent

www.openmobilealliance.org2011, Musa Unmehopa

1) M2M MANAGEMENT AND PROVISIONING

2) APIs FOR M2M APPLICATIONS

Today, I will be talking about …

www.openmobilealliance.org2011, Musa Unmehopa1) M2M MANAGEMENT AND PROVISIONING


Devices, devices everywhere…

According to industry analyst firm Ovum,

deployments of OMA enabled devices will reach

ONE BILLIONONE BILLION globally by the end of 2011 !4


M2M devices outnumber mobile devices by an

order of magnitude• Analysys Mason: Forecasts that the number of M2M device connections

will grow to 2.1 billion2.1 billion devices in 2020 [1]

• Machina Research: The installed base of M2M connected Consumer Electronics devices will exceed 4.2 billion4.2 billion by 2020 [2]

• GSMA: Estimates that there will be 20 billion20 billion devices connected to the web by 2020 [3]

Remote device management and provisioning

of all these M2M devices will be a critical aspect

to support this tremendous growth opportunity

• Another way of looking at this:

There will be more M2M devices shipped each year than PCs,There will be more M2M devices shipped each year than PCs,

cell phones, tablets, setcell phones, tablets, set--top boxes, and gaming platforms put togethertop boxes, and gaming platforms put together [4]

5


OMA DM Gateway Management Object

•DM Management Objects and the DM protocol:– Configure connectivity

– Update firmware

– Diagnose problems

– Monitor performance

– Install and update software

– Lock and wipe personal data

– Manage device capabilities

– Schedule and automate device management tasks

6


These challenges can be best addressed through an extension of

OMA DM remote management and provisioning capabilities using the

OMA Gateway Management Object and the new OMA work to develop

specifications for Lightweight Machine to Machine applications

OMA position and focus on M2M

OMA recognizes the importance of developing its Device OMA recognizes the importance of developing its Device Management (DM) technology to supportManagement (DM) technology to support

• new types of M2M devices which may have different characteristics and requirements from traditional mobile devices

• an evolution to heterogeneous networks that support both traditional mobile and M2M devices

• devices on heterogeneous networks managed through a gateway

• the use of M2M devices as a gateway for other devices

• provisioning and management protocol for constrained devices

• provisioning and management protocol for constrained connectivity

7


OMA DM Gateway Management Object

• Facilitates interaction between a management server and a management client when:

– Direct and unaided interaction between server and client is not possible

– Device does not have a publicly routable address

– Device may be sitting behind a firewall

– Device supports a management protocol other than OMA-DM

8

Approval scheduled for end of 2011


Lightweight M2M Protocol

• The need for a lightweight protocol for M2M– support capability constrained M2M devices

– data collection and remote controlling without complex computing and UI operations

– optimize network resources; very large numbers of devices may be connected to the communication network simultaneously

• Requirements– Compact protocol for combined service manipulation & management

– Binary based addressing scheme instead of URI

– Flat data model for efficient data access

– Simple protocol level authentication

– Simple Digest based authentication & authorization

– Support transport level security mechanism

– IP (TCP, UDP) & Non-IP Transport (SMS, USSD, CSD)

• Work just started, scheduled for completion end of next year– First step is Gap Analysis; ETSI, 3GPP, IETF CoAP, OMA DM

– Specific details being developed at this stage

9

www.openmobilealliance.org2011, Musa Unmehopa 2. APIs FOR M2M APPLICATIONS


Device API - DM Client side API Framework

• Defines APIs to enable local applications on a device to access the Management Objects supported by the OMA DM Client resident on the device:– Local application registration/unregistration with the DM Client, for notification on

updates of existing Management Objects

– Retrieval of Management Object and its parameters by the local application

– Management Object update by the local application

– Local application interaction with the DM Client Management Objects

• DM Management Objects and the DM protocol:– Configure connectivity

– Update firmware

– Diagnose problems

– Monitor performance

– Install and update software

– Lock and wipe personal data

– Manage device capabilities

– Schedule and automate device management tasks

• Interfaces defined using WebIDL

• Approved as Candidate by the OMA Board of Directors earlier this month

11


Device API - Open Connection Manager API

• Local applications on the device can use the Open Connection Manager API to manage connectivity and connections– Cellular network connection management

– Wi-Fi connection management

– Network selection

– Power management (hibernation, standby)

– etc

• Requirements are completed and approved as Candidate by the OMA Board of Directors in July 2011

• Scheduled for completion in the Spring of 2012

12

www.openmobilealliance.org2011, Musa Unmehopa CONCLUSION


OMA has a clear strategy for Machine2MachineMachine2Machine

– OMA Device Management is hugely successful in the market

– The Strategic focus of OMA on M2M is based on an extension of OMA DM, using Gateway Management Object and a Lightweight M2M protocol

– OMA APIs Standardize Access to Unique Resources within Operator Networks and on Devices

– Standardized APIs are necessary to help realize the tremendous growth potential for the M2M Applications Market

14

www.openmobilealliance.org2011, Musa UnmehopaREFERENCES AND BACKUP MATERIAL


OMA Converged Personal Network Service (CPNS)

• OMA CPNS enables interaction with in-home M2M services and applications, using CPNS connections between personal networks and the CPNS Server. This allows for remote control, monitoring and content delivery

16

Approved in May 2011

GwMOGwMO: Manage M2M Devices through a gateway

CPNSCPNS: Use device as a gateway to manage other devices


OMA API Program (Application Programming Interfaces)

• OMA APIs Standardize Access to Unique Resources within Operator Networks

• Standardized APIs are necessary to help realize the tremendous growth potential for the Applications Market

• OMA APIs expose the network assets that developers need - no matter what signaling protocols, platforms or other APIs they use

• Core network assets and device capabilities must be made available in order to deploy the wide variety of new applications and services that enter the market every day

• Includes both Device APIsDevice APIs as well as Network APIsNetwork APIs

http://www.openmobilealliance.org/API/

17


References

• [1] http://www.analysysmason.com/Research/Content/Reports/RRE02_M2M_devices_forecast/

• [2] http://www.machinaresearch.com/consumerelectronics2020.html

• [3] http://www.gsm.org/index.htm

• [4] http://blogs.windriver.com/m2m/

18


OMA – Overview

More than 150 members from across the mobile value chain

• Founded June 2002

• Operators, terminal and software vendors, content and entertainment providers

Interoperable service enablers across multiple domains

• Architecture, Security, Charging and Network APIs

• Person-to-Person Communications

• Device Capabilities

• Access to Content

• Services Access Interface

• Service Customization

Current and Ongoing Technical Deliverables – more detail in presentation

• 44 service enablers delivered in 2010 with 80 planned for 2011

• Ongoing refinement of interoperability testing program with Test on Demand in Q3 2011

• API Framework—building on success of GSMA OneAPI and Parlay affiliation

• M2M Communications—enabling terminals as gateways and converged personal networks

New and improved organizational structures and efficiencies

• Fast track process for omitting or combining steps and deliverables in OMA Process

• Min Max procedure for an alternative path to traditional testing of every OMA enabler

Collaboration with other bodies—including WAC, GSMA, W3C & ETSI

• Reduce duplication and fragmentation

• New strategic program of liaisons with appointed Board level champions to other bodies

• OMA maintains formal cooperation agreements or frameworks with nearly 50 industry bodies

19


OMA – Organizational Structure

20


Highlights of OMA Service Enablers

Over 50 Candidate and Approved Enablers Published in the Last 18 Months

Candidate Enabler Releases

• OMA Device Management Smart Card V1_0

• OMA Lock and Wipe Management Object V1_0

• OMA Converged Address Book V1_0

• OMA XML Document Management V2_1

• OMA Secure Content Identification Mechanism V1_0

• OMA SIP Push V1_0

• OMA Location in SIP/IP Core V1_0

• OMA Secure User Plane Location V2_0

• OMA Mobile Search Framework V1_0

• OMA Mobile Codes V1_0

• OMA Mobile Advertising V1_0

• OMA Mobile Spam Reporting V1_0

• OMA Customized Multimedia Ringing 1.0• OMA Presence Access Layer V 1.0• OMA Mobile Spam Reporting V1.0• OMA Application Layer Security Common Functions V1.1• OMA Next Generation Service Interfaces V1.0• OMA Digital Rights Management V2.2• OAM Key Performance Indicators in OMA V1.0• OMA Smart Card Web Server V1_2• OMA Mobile SMIL V 1.0 (Reference Release)

A Candidate Enabler Release (CER) delivers an approved set of open technical specifications that can be

implemented in products and solutions, and then tested for interoperability.

An Approved Enabler Release (AER) represents Candidate Enabler Releases that have gone through the

Interoperability Program (IOP) of OMA. The IOP tests interoperability between different member company’s

implementations—either within the OMA or through other means.

21


Highlights of OMA Service Enablers

Approved Enabler Releases

• OMA EFI V1.1

• OMA Browser Protocol Stack V1.2

• OMA Push V2.1

• OMA User Agent Profile V1.1

• OMA Rich-media Environment V 1.0

• OMA Games Services Client/Server Interface V1.0

• OMA DownLoad Over The Air V2.0

• OMA Browsing V2.4 (enhancements ph 2)

• OMA Look and Feel Customization

• OMA On Board key Generation / Wireless Public Key Infrastructure V1.0

• OMA Device Management V1_2

• OMA Smart Card Web Server V1_1

• OMA Presence SIMPLE V1_1

• OMA Global Service Architecture V1_0 (Reference Release)

• OMA IMPS Implementation Guidelines V1_3 (Reference Release)

A Candidate Enabler Release (CER) delivers an approved set of open technical specifications that can be

implemented in products and solutions, and then tested for interoperability.

An Approved Enabler Release (AER) represents Candidate Enabler Releases that have gone through the

Interoperability Program (IOP) of OMA. The IOP tests interoperability between different member company’s

implementations—either within the OMA or through other means.

22


More Information

• OMA Communications Contact

Bobby Fraher, External Communications Manager

[email protected]

• 2011 Q3 OMA Quarterly Newsletter

http://www.openmobilealliance.org/comms/pages/OMA_quarterly_2011_vol_3.htm

• Full list of OMA Mobile Service Enablers

http://www.openmobilealliance.org/Technical/releaseprogram.aspx

• Interested in joining the OMA

http://www.openmobilealliance.org/Membership/default.aspx

23

www.openmobilealliance.org2011, Musa Unmehopa ~ THE END ~

m2m stategy of the open mobile alliance - fraunhofer fuseco forum 2011

Technology

m2m management

m2m devices devices

management protocol

remote device management

remote management

device management tasks2011

management server

m2m oma