Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Droidcon: Benefits of Cross-Operator APIs

1,121 views

Published on

My talk at the Droidcon barcamp about benefits of Cross-Operator APIs.

Find more at http://manfredbo.tumblr.com

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Droidcon: Benefits of Cross-Operator APIs

  1. 1. Manfred Bortenschlager @ManfredBo @droidconUK, Oct 24, 2013 The benefits of cross-operator APIs
  2. 2. @ManfredBo What is this all about ? 2
  3. 3. @ManfredBo Mobile Network Operators have a lot of capabilities valuable for developers. These are underutilised. 3
  4. 4. @ManfredBo Why? 4
  5. 5. @ManfredBo Source: http://bulldogdrummond.com/blog/3745 5
  6. 6. @ManfredBo 6
  7. 7. @ManfredBo What can be done ? 7
  8. 8. @ManfredBo OneAPI Exchange 8
  9. 9. What is OneAPI Exchange ? @ManfredBo OneAPI Exchange is… … an infrastructure that allows developers access to mobile network operator assets via APIs. This infrastructure federates different operators into one unit providing a wider reach for developers. 9
  10. 10. Current Coverage @ManfredBo Current Partners: Total Reach: 215.7m Subscribers (C) http://www.traveltip.org 10
  11. 11. @ManfredBo How does that work operatively ? 11
  12. 12. Example Collaboration <<App Developers>> @ManfredBo <<App Users>> 12
  13. 13. Example Collaboration <<App Developers>> <<Developer Operator>> @ManfredBo <<App Users>> <<Serving Operator>> 13
  14. 14. Example Collaboration @ManfredBo Developer joins <<App Developers>> Operator’s developer program <<App Users>> User is subscriber of other Operator <<Developer Operator>> <<Serving Operator>> 14
  15. 15. Example @ManfredBo <<App Users>> <<App Developers>> All API calls of involved Operators are federated via the OneAPI Exchange. The Developer can reach far more users. <<Serving Operator>> <<Developer Operator>> Operator Registry Developer Registry Settlement … Developed by: 15
  16. 16. @ManfredBo A Payment API example flow 16
  17. 17. Example: Payment API Flow Example @ManfredBo 1. Uses developer operator’s APIs <<Developer Operator>> Operator Registry Developer Registry <<Serving Operator>> Settlement … OneAPI Exchange Developed by: 17
  18. 18. Example Example: Payment API Flow @ManfredBo 2. Downloads app (from anywhere) <<Developer Operator>> Operator Registry Developer Registry 3. Issues a payment <<Serving Operator>> Settlement … OneAPI Exchange Developed by: 18
  19. 19. Example: Payment API Flow Example @ManfredBo 4. Contact OneAPI Exchange to identify serving operator <<Developer Operator>> Operator Registry Developer Registry <<Serving Operator>> Settlement … OneAPI Exchange Developed by: 19
  20. 20. Example: Payment API Flow Example @ManfredBo 6. Charges to bill <<Developer Operator>> Operator Registry 5. Coordinates transaction with serving operator Developer Registry Settlement … <<Serving Operator>> OneAPI Exchange Developed by: 20
  21. 21. Example: Payment API Flow Example @ManfredBo 8. Developer operator pays out developer <<Developer Operator>> 7. Serving operator pays out developer operator Operator Registry Developer Registry Settlement … <<Serving Operator>> OneAPI Exchange Developed by: 21
  22. 22. @ManfredBo The benefits for developers 22
  23. 23. Benefits @ManfredBo 1. Simplicity  Relation with only one operator 2. Trust  User interacts only with serving operator’s brand 3. Speed  Platform independent REST APIs 4. Reach  Cover subscribers of all participating operators 5. Force  Operators compete for developers
  24. 24. @ManfredBo Current status 24
  25. 25. Current APIs @ManfredBo Lets users authenticate securely using the Operator Identity. Subscriber attributes can be leveraged. 25
  26. 26. Current APIs @ManfredBo Lets users conduct mobile payments which are conveniently settled via the Operator bill. 26
  27. 27. Current APIs @ManfredBo Lets users send/receive SMS/MMS out of an app and make use of rich communications. 27
  28. 28. Current APIs @ManfredBo Main OneAPI Exchange APIs • Payment API • Operator Identity API • Messaging API Supplementary OneAPI Exchange APIs • • • • Operator Discovery API Price Lookup API Transaction Logging API Logo API 28
  29. 29. OneAPI Exchange Status @ManfredBo API releases on rolling basis (based on demand) 29
  30. 30. @ManfredBo 30
  31. 31. @ManfredBo How can I start using the APIs ? 31
  32. 32. OneAPI Pilot Partner Program @ManfredBo Get involved in the OneAPI Pilot Partner Program !  Work closely with a Mobile Network Operator  Secure a long-term relationship  Contribute to shaping the APIs  Leverage promotion activities (eg, at Mobile World Congress) Register here: www.gsma.com/oneapi (Pilot partner program to be launched early November 2013) 32
  33. 33. Contact @ManfredBo 33

×