GSM Operator Applications

     GSM Operator Applications Information
     3G Americas White Papers    
     Openwave, April 2009
GSM Operator Applications
 
Network Interfaces for Applications
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 (SMS). 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.
 
Prior to 2009, the interfaces for such functions were either 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 3rd Generation Partnership Project (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. 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.
 
 
Parlay X Specifications
 
 
Title
Functions
1
Common
Definitions common across Parlay X specifications
2
Third Party Call
Creates and manages calls
3
Call Notification
Management of calls initiated by a subscriber
4
Short Messaging
Send and receive of SMS including delivery receipts
5
Multimedia Messaging
Send and receive of multimedia messages
6
Payment
Pre-paid and post-paid payments and payment reservations
7
Account Management
Management of accounts of prepaid customers
8
Terminal Status
Obtain status such as reachable, unreachable or busy
9
Terminal Location
Obtain location of terminal
10
Call Handling
Control by application for call handling of specific numbers
11
Audio Call
Control for media to be added/dropped during call
12
Multimedia Conference
Create multimedia conferences including dynamic management of participants
13
Address List Management
Manage subscriber groups
14
Presence
Provide presence information
15
Message Broadcast
Send messages to all users in specified area
16
Geocoding
Obtain location address of subscriber
17
Application-driven QoS
Control quality of service of end-user connection
18
Devices Capabilities and Configuration
Obtain device capability information and be able to push device configuration to device
19
Multimedia Streaming Control
Control multimedia streaming to device
20
Multimedia Multicast Session Management
Control multicast sessions, members, multimedia stream and obtain channel presence information
 
 
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 Representational State Transfer (REST) interface for most functions as an alternative to using the Web service. REST-ful 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.
 
Mobile Application Architectures
Many applications used over wireless connections will be the same as those used over the Internet with desktop/laptop PCs. An increasing number of applications, however, will be developed specifically for mobile devices. This can be a challenge for developers, because there are a number of different mobile platforms now available including Android, Apple iPhone, LiMo, Palm Pre, RIM BlackBerry, Symbian and Windows Mobile. Unlike the desktop market, the mobile device market has become quite fragmented. Each of the device platforms comes with its own application development environment and developers must face a learning curve to become adept at programming for any specific platform. Some developers may be content targeting specific platforms. Others, however, may need their applications to operate across multiple platforms.
 
Fortunately, there are various developments that address the fragmentation challenge. These include:
  • Mobile Middleware. These are software infrastructures that consist of a client component that operates on the mobile device, and a server component that acts as a proxy for the client. Vendors provide tools with which developers can develop an application in a platform-neutral manner, and which then operates on multiple device types. Mobile middleware is mostly used for business applications.
  • Mobile Web 2.0. Mobile browsers are adopting many of the same sophisticated capabilities as desktop browsers. Combined with networks that have higher throughputs and lower latency, an increasing number of applications can be Web hosted, making the applications available from diverse platforms. Mobile Web 2.0 technologies include items such as Ajax, offline operation, video capabilities, fast JavaScript execution and mashups (combining data from multiple Web sources). Cloud computing, enabled by Mobile Web 2.0, will play as important a role for mobile systems as for desktops.
  • Java Developments. Though Java itself has presented a challenge through inconsistent implementation on devices, there are new capabilities that will result in more consistent, as well as more powerful, device execution environments. Examples include Mobile Service Architecture (MSA) for predictable capability and Mobile Information Device Profile 3 for multi-tasking.