Your SlideShare is downloading. ×
0
Machine-to-Machine Communications and API StandardizationMusa UnmehopaTechnical Plenary Chairman, OMASenior Manager, Alcat...
Today, I____be Talking About … ____ will __ ______ ____OMA’s Strategy on Application Programming InterfacesOMA’s Strategy ...
2011, Musa Unmehopa   APPLICATION PROGRAMMING INTERFACES                                          www.openmobilealliance.org
Today’s Problem• Each operator can only reach a small set of application developers• Each application developer can only r...
OMA APIs Standardize Access to Unique Resourceswithin Operator Networks2011, Musa Unmehopa    5            www.openmobilea...
The Value of Standardized APIs           Available to                             Expose network assets    any developer c...
OMA APIs, a big list and growing                                              SOAP/WSDL APIs                              ...
31 OMA members endorsing the API Program•    Aepona                         •   Deutsche Telekom AG      •   Neustar•    A...
2011, Musa Unmehopa   MACHINE-2-MACHINE COMMUNICATION                                          www.openmobilealliance.org
Devices, devices everywhere…                            According to industry analyst firm Ovum,                      depl...
OMA DM Gateway Management Object • DM Management Objects and the DM protocol:       –   Configure connectivity       –   U...
OMA position and focus on M2M   OMA recognizes the importance of developing its Device     Management (DM) technology to s...
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 ...
2011, Musa Unmehopa      CONCLUSION                      www.openmobilealliance.org
Conclusion OMA has a clear strategy for APIs and M2MAPI• OMA APIs Standardize Access to Unique Resources within Operator  ...
2011, Musa Unmehopa   REFERENCES AND BACKUP                              www.openmobilealliance.org
OMA – Overview           More than 150 members from across the mobile value chain           • Founded June 2002           ...
OMA – Organizational Structure2011, Musa Unmehopa                         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...
2011, Musa Unmehopa   ~ THE END ~                      www.openmobilealliance.org
Upcoming SlideShare
Loading in...5
×

Open Mobile Alliance strategy on M2M and API - Keynote at OMA/CCSA Symposium in Beijing (PRC)

1,683

Published on

Keynote presentation at the international symposium hosted by the Open Mobile Alliance (OMA) and the China Communications Standards Association (CCSA), on Wednesday November 9, 2011, Beijing (China). The title of the symposium was "Innovating New Services Across the Network of Everything; The Role of Standards in a Hyper Connected World...". Presentation by Musa Unmehopa, Chairman of the Technical Plenary of the Open Mobile Alliance, and senior manager of standards at Alcatel-Lucent.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,683
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
146
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "Open Mobile Alliance strategy on M2M and API - Keynote at OMA/CCSA Symposium in Beijing (PRC)"

  1. 1. Machine-to-Machine Communications and API StandardizationMusa UnmehopaTechnical Plenary Chairman, OMASenior Manager, Alcatel-Lucent
  2. 2. Today, I____be Talking About … ____ will __ ______ ____OMA’s Strategy on Application Programming InterfacesOMA’s Strategy on Machine-to-Machine Communications2011, Musa Unmehopa www.openmobilealliance.org
  3. 3. 2011, Musa Unmehopa APPLICATION PROGRAMMING INTERFACES www.openmobilealliance.org
  4. 4. Today’s Problem• Each operator can only reach a small set of application developers• Each application developer can only reach the subscriber base of a few operators• Does not scale2011, Musa Unmehopa 4 www.openmobilealliance.org
  5. 5. OMA APIs Standardize Access to Unique Resourceswithin Operator Networks2011, Musa Unmehopa 5 www.openmobilealliance.org
  6. 6. The Value of Standardized APIs Available to Expose network assets any developer community independent of the independent of the signaling protocols, development platform network platforms, or access technology Operators benefit Developers benefit Users benefit Everybody benefits Reduces development cost Simplifies and fuels and time-to-market wider deployment of for new applications existing applications and services and services2011, Musa Unmehopa 6 www.openmobilealliance.org
  7. 7. OMA APIs, a big list and growing SOAP/WSDL APIs • Account Management Abstract APIs • Audio Call• Call Control • Application Driven QoS• Call Notification • Call Notification• Call Handling • Call Handling• Context Entity Discovery • Content Management• Context Information • Device Capabilities• Generic Data Change Notification • Geocoding• Generic Data Management RESTful APIs • Multimedia Conference• Identity Management • Address List Management • Multimedia Messaging• Identity Resolution • Audio Call • Multimedia Multicast Session mgt• Multimedia Conference • Call Control • Multimedia Streaming Control• Multimedia List Handling • Call Notification • Payment• Service Discovery • Device Capabilities • Policy• Service Registration • Multimedia Messaging • Presence • Payment • Short Messaging • Presence • Terminal Location • Service User Profile Management • Terminal Status • Short Messaging • Third Party Call • Terminal Location • Terminal Status • Third Party Call 2011, Musa Unmehopa 7 www.openmobilealliance.org
  8. 8. 31 OMA members endorsing the API Program• Aepona • Deutsche Telekom AG • Neustar• Alcatel-Lucent • Ericsson • Oracle• AT&T • ETRI • Orange SA• Bell Mobility • GSM Association (GSMA) • Red Bend Software• Birdstep Technology • Hansol Inticube • Smith Micro Software,Inc.• Cambridge Silicon Radio, Ltd • HTC • Songdo Telecom, Inc.• China Mobile • Huawei Technologies • Telecom Itália• China Unicom • Interop Technologies • Telenor ASA• China Telecom • NEC Corporation • TeliaSonera• Comverse • Nokia Siemens Networks • U.S. Cellular • ZTE Corporation These endorsing member companies represent a wide spectrum of industry players, including operators, equipment manufacturers, and software vendors from all geographies across the globe, signifying a very strong signal of industry support! 2011, Musa Unmehopa 8 www.openmobilealliance.org
  9. 9. 2011, Musa Unmehopa MACHINE-2-MACHINE COMMUNICATION www.openmobilealliance.org
  10. 10. Devices, devices everywhere… According to industry analyst firm Ovum, deployments of OMA enabled devices will reach ONE BILLION globally by the end of 2011 !2011, Musa Unmehopa 10 www.openmobilealliance.org
  11. 11. 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 tasks2011, Musa Unmehopa 11 www.openmobilealliance.org
  12. 12. OMA position and focus on M2M OMA recognizes the importance of developing its Device Management (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 These challenges can be best addressed through an extension ofOMA DM remote management and provisioning capabilities using theOMA Gateway Management Object and the new OMA work to develop specifications for Lightweight Machine to Machine applications 2011, Musa Unmehopa 12 www.openmobilealliance.org
  13. 13. 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 2011, Musa Unmehopa 13 www.openmobilealliance.org
  14. 14. 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 2011, Musa Unmehopa 14 www.openmobilealliance.org
  15. 15. 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 stage2011, Musa Unmehopa 15 www.openmobilealliance.org
  16. 16. 2011, Musa Unmehopa CONCLUSION www.openmobilealliance.org
  17. 17. Conclusion OMA has a clear strategy for APIs and M2MAPI• OMA APIs Standardize Access to Unique Resources within Operator Networks• Standardized APIs are necessary to help realize the tremendous growth potential for the Applications MarketM2M• 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 protocol2011, Musa Unmehopa 17 www.openmobilealliance.org
  18. 18. 2011, Musa Unmehopa REFERENCES AND BACKUP www.openmobilealliance.org
  19. 19. 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 bodies2011, Musa Unmehopa www.openmobilealliance.org
  20. 20. OMA – Organizational Structure2011, Musa Unmehopa www.openmobilealliance.org
  21. 21. 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.2011, Musa Unmehopa www.openmobilealliance.org
  22. 22. 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.2011, Musa Unmehopa www.openmobilealliance.org
  23. 23. More Information • OMA Communications Contact Bobby Fraher, External Communications Manager bobby@agilis-communications.com • 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.aspx2011, Musa Unmehopa www.openmobilealliance.org
  24. 24. 2011, Musa Unmehopa ~ THE END ~ www.openmobilealliance.org
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×