May 2012 Technical Achievements

by OMA | Tuesday, May 1, 2012

The following list of mobile service enablers was ratified by the OMA Board of Directors in May 2012.

Service Customization

OMA Secure User Plane Location V2.0 AER

OMA SUPL employs user plane data bearers for transferring location assistance information such as GPS assistance data, and for carrying positioning technology-related protocols between mobile terminal and the network. This version adds new functionality, and based on experience with SUPL 1.0, enhances the existing functionality while maintaining the SUPL 1.0 requirements. The new functionality includes triggered services (e.g., periodic and change of area), and network environments (e.g., I-WLAN). In addition, SUPL 2.0 addresses emergency services.

http://www.openmobilealliance.org/Technical/release_program/supl_v2_0.aspx

Device Capabilities

OMA Lock and Wipe Management Object V1.0 AER

OMA Lock and Wipe Management Object (LAWMO) allows deactivation of the device over the network giving operators an effective way to protect user and enterprise related data. Specific capabilities include locking and unlocking the device, wiping the device data and remote factory reset.

http://www.openmobilealliance.org/Technical/release_program/law_mo_v1_0.aspx

OMA Gateway Management Object V1.0 CER

OMA Gateway Management Object (GwMO) enables the management of devices that are not directly accessible from the OMA-DM server. These devices may be deployed behind a firewall or the device does not support OMA-DM. OMA GwMO supports the ability to fan-out commands from a DM server to multiple end devices and to aggregate responses from multiple end devices in order to facilitate a consolidated response back to the DM Server.

http://www.openmobilealliance.org/Technical/release_program/GwMO_V1_0.aspx

Service Access Interface

OMA Web Runtime API V1.0 CER

OMA Web Runtime API (WRAPI) defines an API exposing the event notification enabler services provided by OMA Push, GSM SMS, SIP MESSAGE, and other text messaging services to applications executing in Web Runtime environments. This API is referred to as the Push API.

http://www.openmobilealliance.org/Technical/release_program/WRAPI_v1_0.aspx

Version 1.0 of the Web Runtime API includes technical specifications for a Push API, and API Design Patterns for use in all OMA APIs exposed through Web Runtime environments.

Version 1.0 of the WRAPI Design Patterns specification addresses the following aspects:

  • Use of Web IDL for API specification
  • Asynchronous methods
  • Error handling
  • Arguments
  • Accessing APIs

Version 1.0 of the Push API specification addresses the following aspects:

  • Basis of the Push API design in the W3C API “Server-Sent Events” [W3C-EventSource]
  • Support for a subset of the features of the OMA “Push Client – Application Interface” specification [Push-CAI]
  • Push-OTA bearer binding, at minimum supporting SMS-based connectionless Push

To reduce the complexity of the Push API for this release, the ability to select specific OMA Push bearers to activate is deferred to a future release.

OMA Games Services API V1.0 CRR

OMA Game Services API (GSAPI) was created to become the standard to develop server-client network functions for mobile gaming. With OMA GSAPI, game developers can easily develop network functions like game score ranking, item purchasing and posting game scores. OMA GSAPI will stimulate the mobile game market by providing a streamlined way to develop network functions for game developers and will help developers make better mobile games with improved time to market.

http://www.openmobilealliance.org/Technical/release_program/GS_API_v1_0.aspx

OMA RESTful Network API Chat V1.0 CER

OMA RESTful Network API Chat (ORESTful_NetAPI_Chat) contains HTTP protocol bindings based on the requirements for Chat (also known as Instant Messaging), using the REST architectural style. The specification provides resource definitions, the HTTP verbs applicable for each of these resources, and the element data structures, as well as support material including flow diagrams and examples using the various supported message body formats (i.e. XML, JSON, and application/x-www-form-urlencoded).

Version 1.0 of this specification supports the following operations:

  • Manages subscriptions to chat-related event notifications
  • Sends and receiving 1-1 chat messages
  • Reports the status of 1-1 chat messages
  • Receives notifications about the status of 1-1 chat messages
  • Manages 1-1 chat sessions
  • Promotes a 1-1 chat session into a group chat session
  • Manages group chat sessions
  • Sends and receives group chat messages
  • Receives notifications about invitations to a 1-1 chat
  • Receives notifications about invitations to a group chat
  • Receives notifications about chat session events
  • Receives notifications about a change in the list of Participants in a group chat session

In addition, Version 1.0 of RESTful Network API Chat provides:

  • Support for scope values used with authorization framework defined in [Autho4API_10]
  • Support for Anonymous Customer Reference (ACR) as an end user identifier
  • Support for “acr:Authorization” as a reserved keyword in a resource URL variable that identifies an end user

http://www.openmobilealliance.org/Technical/release_program/RESTfulNetworkAPI_Chat_V1_0.aspx

OMA Rich Communication APIs V1.0 CER

OMA Rich Communication APIs V1.0 (REST_NetAPI_RCSProfile) specifies RESTful Network APIs for Rich Communications using an HTTP protocol binding. OMA REST_NetAPI_RCSProfile leverages on the GSMA RCS benefits and to support today’s demand for innovative service creation and lightweight UNI interfaces. The RESTful Network APIs for Rich Communications version 1.0 defines subsets of the following APIs:

  • RESTful Network API for Image Share V 1.0
  • RESTful Network API for Messaging V 1.0
  • RESTful Network API for Video Share V 1.0
  • RESTful Network API for File Transfer V 1.0
  • RESTful Network API for Address Book V 1.0
  • RESTful Network API for Chat V 1.0
  • RESTful Network API for Presence V 1.0
  • RESTful Network API for Notification Channel V 1.0
  • RESTful Network API for Third Party Call V 1.0
  • RESTful Network API for Call Notification V 1.0

http://www.openmobilealliance.org/Technical/release_program/RESTfulNetworkAPI_RichComms_v1_0.aspx

OMA RESTful Network API Common Definitions V1.0 CER

OMA RESTful Network API Common Definitions (RESTful_NetAPI_Common) is a republication of the ParlayREST Common V 1.1and OMA REST Common V 1.0 specifications from the ParlayREST 2.0 release, as part of the suite of OMA RESTful Network APIs. The content of these two specifications has been merged and restructured to fit that suite, and to separate general aspects from those aspects that are related to a Parlay X baseline [PSA]. Changes include “bug” fixes and structural changes to support this suite.

Version 1.0 of the Common Definitions and Specifications for RESTful Network APIs contains naming conventions, content type negotiation, resource creation, representation formats and serialization, fault definitions and common data types for RESTful Network APIs. It also includes an Annex that provides specifications which are shared by those RESTful Network APIs based on Parlay X baselines.

http://www.openmobilealliance.org/Technical/release_program/RESTNetAPICommon_v1_0.aspx

OMA RESTful Network API File Transfer V1.0 CER

OMA RESTful Network API File Transfer (REST_NetAPI_FileTransfer) contains HTTP protocol bindings based on the requirements for File Transfer, using the REST architectural style.

Version 1.0 of this specification supports the following operations:

  • Manages subscriptions to file transfer-related notifications
  • Manages file transfer sessions
  • Sends files
  • Receives notifications about file transfer session invitations
  • Receives notifications about file transfer session events
  • Receives notifications about file content link
  • Receives notifications about Receiver acceptance

In addition, Version 1.0 of RESTful Network API File Transfer provides:

  • Support for scope values used with authorization framework defined in [OMA Autho4API_10]
  • Support for Anonymous Customer Reference (ACR) as an end user identifier
  • Support for “acr:Authorization” as a reserved keyword in a resource URL variable that identifies an end user

http://www.openmobilealliance.org/Technical/release_program/RESTNetAPI_FileTransfer_v1_0.aspx