OMA Strategy on Open API Standardization

2,542 views

Published on

"OMA Strategy on Open API Standardization", presentation at the Next Generation Mobile Technology & Standardization Conference (KWISA), 17 November 2010, Seoul (Republic of Korea)

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

No Downloads
Views
Total views
2,542
On SlideShare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
86
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

OMA Strategy on Open API Standardization

  1. 1. Next Generation Mobile Technology & StandardizationConferenceOMA Strategy on Open API Standardization17 November 2010Seoul, Republic of KoreaMusa UnmehopaOMA Technical Plenary ChairmanDistinguished Member of Technical Staff at Alcatel-Lucent www.openmobilealliance.org
  2. 2. OMA is where Telecom APIs get standardized  The Telecom API landscape appears complex, but is harmonized  OMA plays a lead role in the harmonization and consolidation  OMA has the resources and the expertise OMA technical specifications provide the practical implementation of the commercial goals and go-to- market strategies of industry partnersOMA Strategies on Open API Standardization , 17 November 2010 2
  3. 3. OMA Strategies on Open API Standardization , 17 November 2010 3
  4. 4.  Use Application Programming Interfaces (APIs) to open up service capabilities and assets in the core network to application developers The APIs provide an abstracted view of these capabilities  Application developers do not require comprehensive knowledge of arcane telecommunication signaling protocols and call state models  Applications built towards the API can be ported across network types and access technologies Service Developer Content Systems Advertiser Provider Program Provider Integrator APIs Exposure layer Native network signaling protocols Network Location Identity Payment Presence Control Core network service capabilitiesOMA Strategies on Open API Standardization , 17 November 2010 4
  5. 5.  Abstract APIs  Focus on functional aspects  Protocol independent  API Binding Technologies  SOAP/WSDL web services  HTTP protocol binding using REST architectural style  Network APIs & Device APIs  Network API – exposed by a resource residing in the Network  Device API – exposed by a resource residing/running on a DeviceOMA Strategies on Open API Standardization , 17 November 2010 5
  6. 6.  OMA has released several APIs  Parlay Service Access (PSA) – completes 3GPP Release 8  Profile of Parlay X Web Services – GSMA OneAPI profile for SOAP  ParlayREST v1.0 – GSMA OneAPI profile for REST  Next Generation Service Interfaces (NGSI) – Parlay X extensions  Service User Profile – API bindings for SOAP, REST and LDAP  API work under development in OMA  ParlayREST v2.0 – GSMA OneAPI profile for REST  NGSI-S – SOAP/WSDL bindings for NGSI  RESTful binding for OMA Push Access Protocol (PushREST)   All targeted for completion in December 2010   Device Management Client Side API Framework   Targeted for completion in Summer of 2011OMA Strategies on Open API Standardization , 17 November 2010 6
  7. 7.  OMA is (considering) starting up new work on APIs  APIs for Mobile Augmented Reality  APIs for Mobile Advertizing  APIs for Mobile Social Networking  APIs for Games Services  APIs for Web Runtime environment  APIs for GSMA Rich Communications Suite (RCS)OMA Strategies on Open API Standardization , 17 November 2010 7
  8. 8.  Consistency in design and documentation  Improves marketing message  Facilitates developer uptake  Use of Best Practices  Industry Best Practices  OMA REST Guidelines  Promote re-use and avoid duplication  Common namespace, common data types, common design patterns  No competing APIs for the same function/use-case  Common authorization framework using OAuth for REST APIs  work area currently being considered as part of new RCS API work itemOMA Strategies on Open API Standardization , 17 November 2010 8
  9. 9.  Industry Best Practices  How industry best practices apply to REST API development in OMA  REST design patterns Guidelines developed by OMA  Content-type negotiation (XML, JSON, form-urlencoding)  API versioning  API documentation  Error handling  Serialization and internationalization  Backwards and forwards compatibility, extensibility  Encoding and Serialization Details for MIME format Looking to extend these to include Device API guidelines as well OMA Strategies on Open API Standardization , 17 November 2010 9
  10. 10. Parlay Service Access OMA: Has adopted the API work from 3GPP/ETSI Has affiliated the API activities from Parlay ParlayREST v1.0 ParlayREST v2.0 PXPROF v1.0GSMA: OMA:Developer outreach Technical SpecificationsGo-to-market Standards publication (draft) RCS APIBusiness models work item GSMA: OMA: Requirements Technical Specifications Standards publication OMA Strategies on Open API Standardization , 17 November 2010 10
  11. 11. Referencing OMA API specifications Referencing OMA Network APIsOMA Strategies on Open API Standardization , 17 November 2010 11
  12. 12. ParlayREST v1.0 Enabler Release Package• OMA ParlayREST Technical Specification• OMA ParlayREST WSDL SUP files GSMA OneAPI •  SMS • Developer guides •  MMS OMA TS ParlayREST OneAPI Profile • Reference implementation •  Payment • WiKi •  Location OMA TS OneAPI Profile • Commercial trial/pilot• OMA Test Requirements• OMA Conformance Requirements• OMA REST Best Practices Focus on •  commercial/regulatory aspectsFocus on •  developer outreach•  technical innovation •  payments reconciliation•  specification development •  commercial strategies•  correctness and validation •  business models•  standards publication Especially the latter three cannot be discussed in standards for a, for reasons of Antitrust and neutrality. OMA Strategies on Open API Standardization , 17 November 2010 12
  13. 13. OMA is where Telecom APIs get standardized  The Telecom API landscape appears complex, but is harmonized  OMA plays a lead role in the harmonization and consolidation  OMA has the resources and the expertise OMA technical specifications provide the practical implementation of the commercial goals and go-to- market strategies of industry partnersOMA Strategies on Open API Standardization , 17 November 2010 13
  14. 14. Musa Unmehopa OMA Technical Plenary Chairman musa.unmehopa@alcatel-lucent.comOMA Strategies on Open API Standardization , 17 November 2010 14

×