Management and Provisioning of M2M Devices for a Connected WorldETSI M2M Workshop26 October 2011Musa UnmehopaTechnical Ple...
What I’ll be Talking AboutETSI M2M 2011, Musa Unmehopa   2   www.openmobilealliance.org
EXECUTIVE SUMMARY         IN THE M2M DOMAIN, OMA HAS TWO STRENGTHS               1. PROVISIONING AND MANAGEMENT OF M2M DEV...
1. PROVISIONING AND MANAGEMENTETSI M2M 2011, Musa Unmehopa                      www.openmobilealliance.org
Devices, devices everywhere…                                     According to industry analyst firm Ovum,                 ...
M2M devices outnumber mobile devices by anorder of magnitude• Analysys Mason: Forecasts that the number of M2M device conn...
M2M devices outnumber mobile devices by anorder of magnitude• Analysys Mason: Forecasts that the number of M2M device conn...
M2M devices outnumber mobile devices by anorder of magnitude• Analysys Mason: Forecasts that the number of M2M device conn...
OMA position and focus OMA recognizes the need for current OMA Device Management technology   to evolve as follows •    Te...
OMA position and focus OMA recognizes the need for current OMA Device Management technology   to evolve as follows •    Te...
OMA DM Gateway Management Object    • Facilitates interaction between a management server and a      management client whe...
OMA Converged Personal Network Service (CPNS)    • OMA CPNS enables interaction with in-home M2M services and      applica...
Lightweight M2M Protocol • The need for a lightweight protocol for M2M       – support capability constrained M2M devices ...
2. APIs FOR M2M APPLICATIONSETSI M2M 2011, Musa Unmehopa                  www.openmobilealliance.org
OMA API Program (Application Programming Interfaces)• OMA APIs Standardize Access to Unique Resources within Operator  Net...
Device API - DM Client side API Framework • Defines APIs to enable local applications on a device to access the   Manageme...
Device API - Open Connection Manager API • Local applications on the device can use the Open Connection   Manager API to m...
Network APIs, a big list and growing                                                                                      ...
Bringing Everything Together                                Device API                                     Network APIDevi...
CONCLUSION         IN THE M2M DOMAIN, OMA HAS TWO STRENGTHS               1. PROVISIONING AND MANAGEMENT OF M2M DEVICES   ...
REFERENCES AND BACKUPETSI M2M 2011, Musa Unmehopa             www.openmobilealliance.org
References • [1]   http://www.analysysmason.com/Research/Content/Reports/RRE02_M2M   _devices_forecast/ • [2] http://www.m...
OMA – Overview           More than 150 members from across the mobile value chain           • Founded June 2002           ...
OMA – Organizational StructureETSI M2M 2011, Musa Unmehopa         20     www.openmobilealliance.org
Highlights of OMA Service Enablers    Over 50 Candidate and Approved Enablers Published in the Last 18 Months           Ca...
Highlights of OMA Service Enablers          Approved Enabler Releases                • OMA EFI V1.1                • OMA B...
More Information   • OMA Communications Contact   Bobby Fraher, External Communications Manager   bobby@agilis-communicati...
Upcoming SlideShare
Loading in …5
×

ETSI M2M Workshop - OMA Strategy for Internet of Things

1,124 views
1,026 views

Published on

ETSI M2M Workshop, 26 October 2011, Sophia Antipolis, France. "Management and Provisioning of M2M Devices for a Connected World". presentation by Musa Unmehopa, Technical Plenary Chairman of the Open Mobile Alliance (OMA) and Senior Manager at Alcatel-Lucent.

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,124
On SlideShare
0
From Embeds
0
Number of Embeds
13
Actions
Shares
0
Downloads
97
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

ETSI M2M Workshop - OMA Strategy for Internet of Things

  1. 1. Management and Provisioning of M2M Devices for a Connected WorldETSI M2M Workshop26 October 2011Musa UnmehopaTechnical Plenary Chairman, OMASenior Manager, Alcatel-LucentETSI M2M 2011, Musa Unmehopa www.openmobilealliance.org
  2. 2. What I’ll be Talking AboutETSI M2M 2011, Musa Unmehopa 2 www.openmobilealliance.org
  3. 3. EXECUTIVE SUMMARY IN THE M2M DOMAIN, OMA HAS TWO STRENGTHS 1. PROVISIONING AND MANAGEMENT OF M2M DEVICES 2. NETWORK AND DEVICE APIs FOR M2M APPLICATIONSETSI M2M 2011, Musa Unmehopa www.openmobilealliance.org
  4. 4. 1. PROVISIONING AND MANAGEMENTETSI M2M 2011, Musa Unmehopa www.openmobilealliance.org
  5. 5. Devices, devices everywhere… According to industry analyst firm Ovum, deployments of OMA enabled devices will reach ONE BILLION globally by the end of 2011 !ETSI M2M 2011, Musa Unmehopa 5 www.openmobilealliance.org
  6. 6. M2M devices outnumber mobile devices by anorder of magnitude• Analysys Mason: Forecasts that the number of M2M device connections will grow to 2.1 billion devices in 2020 [1]• Machina Research: The installed base of M2M connected Consumer Electronics devices will exceed 4.2 billion by 2020 [2]• GSMA: Estimates that there will be 20 billion devices connected to the web by 2020 [3]ETSI M2M 2011, Musa Unmehopa 6 www.openmobilealliance.org
  7. 7. M2M devices outnumber mobile devices by anorder of magnitude• Analysys Mason: Forecasts that the number of M2M device connections will grow to 2.1 billion devices in 2020 [1]• Machina Research: The installed base of M2M connected Consumer Electronics devices will exceed 4.2 billion by 2020 [2]• GSMA: Estimates that there will be 20 billion devices connected to the web by 2020 [3]• Another way of looking at this: There will be more M2M devices shipped each year than PCs, cell phones, tablets, set-top boxes, and gaming platforms put together [4] ETSI M2M 2011, Musa Unmehopa 6 www.openmobilealliance.org
  8. 8. M2M devices outnumber mobile devices by anorder of magnitude• Analysys Mason: Forecasts that the number of M2M device connections will grow to 2.1 billion devices in 2020 [1]• Machina Research: The installed base of M2M connected Consumer Electronics devices will exceed 4.2 billion by 2020 [2]• GSMA: Estimates that there will be 20 billion devices connected to the web by 2020 [3]• Another way of looking at this: There will be more M2M devices shipped each year than PCs, cell phones, tablets, set-top boxes, and gaming platforms put together [4] The industry needs to agree on a protocol to talk to these devices before it really can address the next level of issues. All these devices must be provisioned and managed ETSI M2M 2011, Musa Unmehopa 6 www.openmobilealliance.org
  9. 9. OMA position and focus OMA recognizes the need for current OMA Device Management technology to evolve as follows • Technology needs to evolve from traditional mobile devices networks to heterogeneous networks that support both mobile and M2M devices • Technology needs to support devices on heterogeneous networks through a Gateway • Technology needs to support M2M devices as a gateway for other devices • Technology needs to support provisioning and management protocol for constrained devices • Technology needs to support provisioning and management protocol for constrained connectivity • Provisioning and Management of M2M devices • Connecting the Internet to the Physical WorldETSI M2M 2011, Musa Unmehopa 7 www.openmobilealliance.org
  10. 10. OMA position and focus OMA recognizes the need for current OMA Device Management technology to evolve as follows • Technology needs to evolve from traditional mobile devices networks to heterogeneous networks that support both mobile and M2M devices • Technology needs to support devices on heterogeneous networks through a Gateway • Technology needs to support M2M devices as a gateway for other devices • Technology needs to support provisioning and management protocol for constrained devices • Technology needs to support provisioning and management protocol for constrained connectivity • Provisioning and Management of M2M devices • Connecting the Internet to the Physical World A natural extension of OMA DM through Gateway over lightweight M2M protocol can address these challengesETSI M2M 2011, Musa Unmehopa 7 www.openmobilealliance.org
  11. 11. 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-DMApproval scheduled for end of 2011 ETSI M2M 2011, Musa Unmehopa 8 www.openmobilealliance.org
  12. 12. 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 GwMO: Manage M2M Devices through a gateway GwMO CPNS: Use device as a gateway to manage other devices CPNSApproved in May 2011 ETSI M2M 2011, Musa Unmehopa 9 www.openmobilealliance.org
  13. 13. 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 stageETSI M2M 2011, Musa Unmehopa 10 www.openmobilealliance.org
  14. 14. 2. APIs FOR M2M APPLICATIONSETSI M2M 2011, Musa Unmehopa www.openmobilealliance.org
  15. 15. 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 APIs as well as Network APIs http://www.openmobilealliance.org/API/ETSI M2M 2011, Musa Unmehopa 12 www.openmobilealliance.org
  16. 16. 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 monthETSI M2M 2011, Musa Unmehopa 13 www.openmobilealliance.org
  17. 17. 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 2012ETSI M2M 2011, Musa Unmehopa 14 www.openmobilealliance.org
  18. 18. Network APIs, a big list and growing SOAP/WSDL APIs Abstract APIs • Account Management • Call Control • Audio Call • Call Notification • Application Driven QoS • Call Handling • Call Notification • Context Entity Discovery • Call Handling • Context Information • Content Management RESTful APIs • Generic Data Change Notification • Device Capabilities • Generic Data Management • Address List Management • Geocoding • Identity Management • Audio Call • Multimedia Conference • Identity Resolution • Call Control • Multimedia Messaging • Multimedia Conference • Call Notification • Multimedia Multicast Session mgt • Multimedia List Handling • Device Capabilities • Multimedia Streaming Control • Service Discovery • Multimedia Messaging • Payment • Service Registration • Payment • Policy • Presence • Presence • Service User Profile Management • Short Messaging • Short Messaging • Terminal Location • Terminal Location • Terminal Status • Terminal StatusPredominantly applicable in cellular environment • Third Party Call • Third Party CallAlso applicable in IP environment ETSI M2M 2011, Musa Unmehopa 15 www.openmobilealliance.org
  19. 19. Bringing Everything Together Device API Network APIDevice API CPNS CPNS GwMO DM ProtocolDevice API Network API Device API Lightweight M2MDevice API Core Network Provisioning and Management Remote Control and AccessDevice API M2M Device Access Network Mobile Device DM Client DM Server / CPNS Server ETSI M2M 2011, Musa Unmehopa 15 www.openmobilealliance.org
  20. 20. CONCLUSION IN THE M2M DOMAIN, OMA HAS TWO STRENGTHS 1. PROVISIONING AND MANAGEMENT OF M2M DEVICES 2. NETWORK AND DEVICE APIs FOR M2M APPLICATIONSETSI M2M 2011, Musa Unmehopa www.openmobilealliance.org
  21. 21. REFERENCES AND BACKUPETSI M2M 2011, Musa Unmehopa www.openmobilealliance.org
  22. 22. 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/ETSI M2M 2011, Musa Unmehopa 18 www.openmobilealliance.org
  23. 23. 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 bodiesETSI M2M 2011, Musa Unmehopa 19 www.openmobilealliance.org
  24. 24. OMA – Organizational StructureETSI M2M 2011, Musa Unmehopa 20 www.openmobilealliance.org
  25. 25. 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.ETSI M2M 2011, Musa Unmehopa 21 www.openmobilealliance.org
  26. 26. 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.ETSI M2M 2011, Musa Unmehopa 22 www.openmobilealliance.org
  27. 27. More Information • OMA Communications Contact Bobby Fraher, External Communications Manager bobby@agilis-communications.com • 2011 Q2 OMA Quarterly Newsletter http://www.openmobilealliance.org/comms/pages/OMA_quarterly_2011_vol_2.htm • Full list of OMA Mobile Service Enablers http://www.openmobilealliance.org/Technical/releaseprogram.aspx •OMA API Program http://www.openmobilealliance.org/API •Interested in joining the OMA http://www.openmobilealliance.org/Membership/default.aspxETSI M2M 2011, Musa Unmehopa 23 www.openmobilealliance.org

×