OneAPI 2.0

OneAPI 2.0

 

When is OneAPI 2.0 due?

We're aiming for December 2010

 

How do APIs get considered for OneAPI v2.0?

The criteria is a comnbination of the following:

 

Do application developers require this API?

We need to establish demand for new APIs, to avoid wasting everyone's time. So we source requests for new APIs at seminars, developer events and through our forum and feedback.

 

Do operators have the capability in their network to support the API?

This is important, as it lets us know which APIs can be delivered next and which require further groundwork.

 

Are there any existing standard we can profile?

If some work has been done already we can reuse the parts which application developers require, revisiting the definitions to be more 'Web friendly'.

 

What APIs are currently in OneAPI v2.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
  • Device Capabilities
• Click-to-call to set up calls between two or more people.

We are also looking to add use cases for 'Remaining Credits Look-Up', to see if the user can afford the stream/purchase; and 'in-app billing'.

• These specifications should be available at the end of 2010. As work evolves on these APIs, the Wiki pages for each will be updated.

See the below link >>>

http://gsma.securespsite.com/access/Access%20API%20Wiki/OneAPI%202.0.aspx