Friday 18 September 2009

Network Interfaces for Applications using Parlay and OneAPI

Here is an old posting on Parlay/OSA that might be useful to put things in context.

An important development related to service evolution is operators making interfaces available to external applications for information and control. Two widely deployed capabilities today include location queries and short message service. With location, mobile devices or external applications (e.g., applications operating on computers outside of the network) can query the location of a user, subject to privacy restrictions. This can significantly enhance many applications including navigation, supplying location of nearby destinations (e.g., restaurants, stores), location of friends for social networking, and worker dispatch. With SMS, external applications can send user requested content such as flight updates.

Until now, the interfaces for such functions have either been proprietary, or specific to that function. However, there are now interfaces that span multiple functions using a consistent set of programming methods. One set is the Parlay X Web Services, a set of functions specified through a joint project of the Parlay Group, the European Telecommunications Standards Institute (ETSI) and 3GPP. The Open Mobile Alliance (OMA) now manages the Parlay X specifications. Parlay X Web Services include support for location and SMS, as well as many other functions with which developers will be able to build innovative applications.

Table 4 (above) summarizes the available Parlay X specifications. Operators are beginning to selectively deploy these functions. The advantage of this approach is that developers can build applications that are compatible with multiple operator networks.

A related project is GSMA OneAPI, a GSM Association project to also define network interfaces, but that prioritizes implementation based on expected market demand. OneAPI defines a simplified Web service for most functions that is essentially a subset of the related Parlay X Web service. It also defines a REST (Representational State Transfer) interface for most functions as an alternative to using the Web service. RESTful interfaces are simpler for developers to work with and experiment with than Web services.

Regardless of whether operators deploy with Parlay X or OneAPI, these are mainstream interfaces that will open wireless networks to thousands of Internet programmers who will be able to build applications that leverage the latent information and capabilities of wireless networks.

Source: 3G Americas Whitepaper '3GPP Broadband Evolution to IMT-Advanced (4G)'


Marcin said...

I have been working with Parlay and some legacy IN applicatoins for many years. From my experiene - operators are using vendor specific API not related with Parlay spec. Even Parlay gataways (Ericsson NRG/SAG, Aepona/Appium, etc) has own 'parlay APIs' wchich only base in general idea on original parlay specs.

In my opinion - parlay is a set of general schemas/procedures - 'how interfaces between core network delivered by particular vendors and internet should look like'.

Zahid Ghadialy said...

Thanks Marcin, always a pleasure to hear from people who are working in relevant areas.

api for sms said...

The call control, user interfacing which includes text messaging, SMS/MMS, audio, conferencing,and billing schemes are just few of the many features of the Parlay APIs. This recent development make the lives of developers easier.