GSMA 3rd Party Access Project - OneAPI

Reference Site :
(https://gsma.securespsite.com/access/Access%20API%20Wiki/Home.aspx)

Welcome to the GSMA Access API wiki This Wiki describes the OneAPI (Open Network Enablers API). It is a set of API specifications that can be implemented by network operators to allow access to network capabilities such as SMS, MMS, location and payments.    Version 1 candidate release APIs The following APIs are OMA candidate releases. A minor change highlighted in the Payments API will be applied for the full 1.0 release, otherwise these are the v1 APIs:   RESTful APIs:  SMS RESTful API - send and receive SMS via your application MMS RESTful API - send and receive MMS via your application Location RESTful API - get the location of one or more mobile network users Payment RESTful API - charge mobile network users for your services The RESTful APIs are also available in this .zip PDF bundle (~235KB) Web Services APIs: (to be added soon) SMS Web Service API MMS Web Service API Location Web Service API Payment Web Service API Version 0.91 beta APIs Note that Version 0.91 OneAPI  is the current version deployed at the Canadian OneAPI Pilot.   Changelog: version 0.91 provides a bug fix to the formencoded-url POST methods, where the wrong syntax had been used. RESTful APIs:  SMS RESTful API v0.91 MMS RESTful API v0.91 Location RESTful API v0.91 Payment RESTful API v0.91 Web Services APIs: SMS Web Service API v0.91 MMS Web Service API v0.91 Location Web Service API v0.91 Payment Web Service API v0.91 Messaging RESTful Binding is also available for testing at Vodafone Betavine Prerequisites for using the APIs Please see the Dependencies page to learn how to authenticate your application to the APIs.   OneAPI 2.0 We are now looking at the additional APIs which will make up OneAPI 2.0. APIs to make delivery of video content to handsets easier: in other words, "Am I good to stream to this user?". This includes functions for: Data Connection profile to identify bearer and network Remaining Credits Look-Up to see if the user can afford the stream Determing the supported video codecs on the handset In-app billing Click-to-call to set up calls between two or more people. Call notification where a Web application can be informed of events in a phone call (caller busy, diverts etc.) These specifications should be available at the end of 2010. Please follow and comment upon the development of the new APIs at the OneAPI 2.0 page. OneAPI 3.0 For our 3rd phase (2011) we are looking at: SMS triggering via UDH and other triggering/provisioning technologies such as USSD QOS to ensure a good qualioty, jitter-free video stream between a Web server and handset Other suggestions very welcome! Please send to oneapi [at] gsm.org Datatypes: OneAPI also specify datatypes used to consume the APIs: Anonymous Customer Reference Unique Application ID (alpha)   NB for the Device Profile API, the Access group recommend utilising existing standards and implementations, as recommended by the W3C Device Description Working Group ( http://www.w3.org/2005/MWI/DDWG/ ).   The initial set of Use Cases led to an initial set of Functional Requirements, which may evolve according to developer and operator feedback.   We also believe that there are a number of Non-functional Requirements that will help developers deploy implementations quickly and securely across networks.   Using the APIs A Reference Implementation is now available for testing the APIs against operator networks - please visit http://oneapi.aepona.com for Europe and Canada; and http://locatrix.com/labs/oneapi/ for Asia-Pacific.   Regulatory considerations: We have researched the Regulatory Landscape around API usage from network operators and have our findings available at: https://gsma.securespsite.com/access/Access%20Library/Access_doc_11_004_Regulatory_Landscape.doc   Security & AAA: Please see (and comment on) our research on Best Practice for Security & AAA - is this workable for operators and developers? Meanwhile we will be working with other forums to see if it feasible to produce a AAA and operational framework that can be supported across OneAPI operators.   Glossary All the acronyms and terms we use are defined in our glossary.   Please provide your feedback on whether these are the correct APIs to help you write new applications and mash-ups? Please send you comments to us at oneapi@gsm.org or use the Feedback Forum on our Reference Implementation portal. Last modified at 08/06/2010 16:35  by Kevin Smith