Management and Provisioning of M2M Devices and Applications

Transcription

1 Management and Provisioning of M2M Devices and Applications Musa Unmehopa Technical Plenary Chairman, OMA Director of Standards, Alcatel-Lucent

2 M2M devices outnumber mobile devices by an order of magnitude Remote device management and provisioning of all these M2M devices will be a cri8cal aspect to support this tremendous growth opportunity

3 Commercially deployed on a global scale According to deployment informa8on from OMA members, OMA has now achieved commercial deployment of 1.4 Billion devices implemen8ng the Firmware Update Management Object enabler

4 OMA DM already being used for M2M applica;ons For example Press release, May 21 st 2012 Sprint, Metrum, Tollgrade Make Smart Grid Smarter Enabling smart meters with wireless connec;vity Both Metrum and Tollgrade have completed Open Mobile Alliance (OMA) Device Management (DM) cer;fica;on, allowing u;li;es to manage assets and infrastructure, ideally suited for large- scale deployments. This method of over the air management and ac;va;on enables a rapid configura;on processes and efficient use of the wireless network. Over the Air management and ac8va8on enables rapid configura8on of devices and efficient use of network resources. Ideally suited for large- scale deployments

5 OMA Device Management

6 OMA posi;on and focus how to manage billions of devices

7 OMA Firmware Update Management Object (FUMO) Defines the management tree objects, DM commands, messages and mechanisms necessary to download firmware update packages and to upgrade the firmware of already deployed devices Remote provisioning of new and used devices In- the- field feature deployment Over- The- Air firmware upgrades Approved in 2007

8 OMA Converged Personal Network Service (CPNS) OMA CPNS enables interac;on with in- home M2M services and applica;ons, using CPNS connec;ons between personal networks and the CPNS Server. This allows for remote control, monitoring and content delivery Bridge personal networks and cellular networks/wans Allows remote control, monitoring and content delivery to in- home devices, when you re not directly connected to personal network Allows any smart device to acts as Personal Network GW CPNS enables the extension of Internet- based services to M2M devices and home appliances V1 Approved in May 2011 V1.1 targeted for Fall 2012

9 OMA DM Gateway Management Object (GwMO) Facilitates interac;on between a management server and a management client when: Direct and unaided interac;on between server and client is not possible Device does not have a publicly routable address Device may be si^ng behind a firewall Device supports a management protocol other than OMA- DM V1.1 Approved in September 2012

10 OMA Lightweight M2M Service Enabler The need for a lightweight protocol for M2M support capability constrained M2M devices data collec;on and remote controlling without complex compu;ng and UI opera;ons op;mize network resources; very large numbers of devices may be connected to the communica;on network simultaneously Requirements Compact protocol for combined service manipula;on & management Binary based addressing scheme instead of URI Flat data model for efficient data access Simple protocol level authen;ca;on Simple Digest based authen;ca;on & authoriza;on Support transport level security mechanism IP (TCP, UDP) & Non- IP Transport (SMS, USSD, CSD) Work in process, scheduled for comple;on mid First step was Gap Analysis; ETSI, 3GPP, IETF CoAP, OMA DM Approval targeted for mid- 2013

11 OMA M2M Device Classifica;on The M2M Device Classifica;on Whitepaper enables the M2M industry to group a large and ever increasing number of M2M devices into a manageable number of classes M2M device classifica;on framework based on the horizontal aeributes wide area communica;on interface local area communica;on interface IP stack, human I/O capabili;es persistent configura;on storage Independent of ver;cal markets such as smart grid, connected cars, e- health, smart home, etc. A common classifica;on helps to avoid overlap and facilitate coordina;on related to M2M standardiza;on M2M device management and service protocols, methods, and procedures can be systema;cally analyzed for re- usability and incrementally developed for the gaps in handling the M2M device classes not fully addressed by exis;ng standards Approved June 2012

12 OMA Applica8on Programming Interfaces

13 Where does the revenue come from? M2M may represent a good growth opportunity overall for MNOs but not in terms of traffic revenue M2M generated 1.2% of mobile data revenue in 2010, falling to 0.8% in 2013, before rising to 1.4% in 2020 (Machina Research [2] ) Connec8ng, provisioning and managing all these billions of devices will unlock tremendous poten8al to provide innova8ve and exci8ng applica8ons

14 Device API - Open Connec;on Manager API OpenCMAPI v.1.1 started, scheduled for 2Q2013

15 Device API - DM Client- Side API Framework Defines APIs to enable local applica;ons on a device to access the Management Objects supported by the OMA DM Client resident on the device: Local applica;on registra;on/unregistra;on with the DM Client, for no;fica;on on updates of exis;ng Management Objects Retrieval of Management Object and its parameters by the local applica;on Management Object update by the local applica;on Local applica;on interac;on with the DM Client Management Objects DM Management Objects and the DM protocol - accessible func;onali;es (not exhaus;ve): Configure connec;vity Update firmware Diagnose problems Monitor performance Install and update sonware Lock and wipe personal data Manage device capabili;es Schedule and automate device management tasks Interfaces defined using WebIDL Approved in October 2011

16 OMA and their Industry Partners

17 OMA and the Industry Landscape Industry coordina8on and harmoniza8on

18 REFERENCES AND BACKUP

19 References [1] hep:// RRE02_M2M_devices_forecast/ [2] hep:// M2M Global Forecast and Analysis [3] hep:// [4] hep://blogs.windriver.com/m2m/ Image credits: Jerry Maguire 1996 TriStar Pictures, Inc. All Rights Reserved. hep:// 18

20 OMA DM Management Objects Architectural Diagrams 2012, Yankee Musa & Unmehopa SMI, Musa Unmehopa and Axel Ferrazzini

21 OMA Overview More than 120 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 >70 service enablers delivered in 2011 with 73 planned for 2012 Ongoing refinement of interoperability testing program with Test on Demand 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 onem2m, 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

22 OMA Organizational Structure