April 2012 Technical Achievements

by OMA | Sunday, April 1, 2012

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

Service Access Interface

OMA RESTful Network API for Third Party Call V1.0 CER

OMA RESTful Network API for Third Party Call (REST_NetAPI_ThirdPartyCall) is a re-publication of the ParlayREST ThirdPartyCall API V 1.0 and is included in the suite of OMA RESTful Network APIs. Changes include “bug” fixes and structural changes to support this suite.

Version 1.0 of the RESTful Network API for Third Party Call continues to support the following operations:

  • Make a call session between calling participant and a number of called participants. (Compared to the Parlay X baseline, this specification adds a few optional parameters that include the option to specify announcements to be played to the participants when joining the call. Additionally, it provides an endpoint on which the Client can be notified of call events such as a participant joining or leaving the call. Also, the limitation of the maximum number of participants to two on call session creation is lifted.)
  • Obtain information about all call sessions
  • Obtain information about all participants of a call session
  • Obtain information about a participant in a call session
  • Obtain information about a call session
  • Add a participant into a call session
  • Transfer a participant from source call session to destination call session
  • Remove a participant from a call session
  • Terminate a call session

The following new functionalities have been introduced:

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

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

OMA RESTful Network API Audio Call V1.0 CER

OMA RESTful Network API for Audio Call (REST_NetAPI_AudioCall) is a re-publication of the ParlayREST AudioCall API V 1.0 and is included in the suite of OMA RESTful Network APIs. Changes include “bug” fixes and structural changes to support this suite.

Version 1.0 of the RESTful Network API for Audio Call continues to support the following operations:

  • Playing a text message (e.g. using text-to-speech) to one or more call participants
  • Playing an audio message to one or more call participants
  • Playing a VoiceXML message to one or more call participants
  • Playing a video message to one or more call participants
  • Playing a message and collecting user keypresses on the phone keypad
  • Playing a message and recording the user’s voice

The following new functionalities have been introduced:

  • Using a script to engage the user in a dialog, and automatically recognize the user’s spoken response
  • 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 that identifies an end user

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

OMA RESTful Network API One API Profile V3.0 AER

The OneAPI Profile of RESTful Network APIs (REST_NetAPI_OneAPI_Profile) is a re-publication of the OneAPI Profile of ParlayREST V2.0 [ParlayREST_OneAPI] and is included in the suite of OMA RESTful Network APIs. Changes include structural adjustments to support that suite. Some additional functional changes have been applied.

Version 3.0 of the OneAPI Profile of RESTful Network APIs defines subsets of the following APIs:

  • RESTful Network API for Short Messaging V 1.0
  • RESTful Network API for Messaging V 1.0
  • RESTful Network API for Terminal Location V 1.0
  • RESTful Network API for Payment V 1.0
  • RESTful Network API for Device Capabilities V 1.0
  • RESTful Network API for Terminal Status V 1.0
  • RESTful Network API for Third Party Call V 1.0, Call Notification V 1.0 and Audio Call V 1.0 (jointly referred to as Call Control APIs) as specified in the following chapter.

The RESTful Network APIs for Messaging and Payment have undergone changes which make them different in details from their ParlayREST V2.0 counterparts. Further details can be found in the actual specifications.

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

OMA Authorization for Network APIs V1.0 CER

OMA Authorization for Network APIs is based on IETF OAuth 2.0 specifications ([draft-ietf-oauth-v2], [draft-ietf-oauth-v2-bearer], [draft-lodderstedt-oauth-revocation] and [draft-recordon-oauth-v2-ux]) and in addition defines the following:

  • OMNA registry for Scope Values
  • Secondary channel, i.e. alternative to HTTP redirection for the delivery of response to Authorization Request
  • Deployment scenarios for environments where multiple Service Providers expose the same service
  • Resolution of resource server location from an issued Access Token
  • One-time Access Tokens

Considerations include:

  • Scope Value definitions
  • self-contained Access Token formats
  • service discovery
  • native Applications
  • HTTP redirect capture mechanisms

http://www.openmobilealliance.org/Technical/release_program/Autho4API_v1.0.aspx

OMA RESTful Network API Call Notification V1.0 CER

OMA RESTful Network API for Call Notification (RESTful_NetAPI_CallNotification) is a re-publication of the ParlayREST CallNotification API V1.0 and is included in the suite of OMA RESTful Network APIs. Changes include “bug” fixes and structural changes to support this suite.

Version 1.0 of the RESTful Network API for Call Notification continues to support the following operations:

  • Managing subscriptions for Call Notifications, Call Direction Notifications and Media Interaction Notifications
  • Notifications about Call Events, Call Direction Events and Media Interaction Events
  • Managing Call Event Monitors
  • Polling information about Call Events from Call Event Monitors

The following new functionalities have been introduced:

  • Notifications about Speech Recognition Events
  • 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 an ACR

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

OMA RESTful Network API for Video Share V1.0 CER

OMA RESTful Network API for Video Share (REST_NetAPI_VideoShare) contains HTTP protocol bindings based on the requirements for video share defined in [RC_API_RD], using the REST architectural style.

Version 1.0 of RESTful Network API for Video Share supports the following operations:

  • Manages subscriptions to video share related event notifications
  • Manages 1-1 video share sessions
  • Notifies the application about the 1-1 video share session invitation
  • Notifies the application about the 1-1 video share session acceptance
  • Notifies the application about the 1-1 video share events

In addition, Version 1.0 of RESTful Network API for Video Share 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/videoshareRESTv1_0.aspx

OMA RESTful Network API Image Share V1.0 CER

OMA RESTful Network API Image Share (REST_NetAPI_ImageShare) contains HTTP protocol bindings based on the requirements for Image Share defined in [RC_API_RD], using the REST architectural style. In this specification, the image share session refers to 1-1 image share session which incorporates exactly 2 participants: an Originator and a Receiver.

Version 1.0 of OMA RESTful Network API Image Share supports the following operations:

  • Manages subscriptions to image share related event notifications
  • Manages image share sessions
  • Notifies the application about the image share session invitation
  • Notifies the application about the image share session acceptance
  • Notifies the application about the image file link
  • Notifies the application about the image share events

In addition, OMA RESTful Network API Image Share 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/ImageShareREST.aspx

Service Customization

OMA Presence Access Layer V1.0 AER

OMA Presence Access Layer (PAL) enabler complements OMA Presence SIMPLE. OMA PAL specifies logically interoperable abstractions known as Presence Aspects. Presence Aspects consolidate Presence Information based on one or more Presence Information Elements. Presence Context associates applicable Presence Aspects required to fulfill service function points with a Presence Aware Service. This provides PAL Clients with a consolidated and determinate view of Presence Information.

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

OMA XML Document Management V2.1 AER

OMA XML Document Management (XDM) enables the storage of user-specific information in the network, which is managed by authorized principals and accessed by service enablers that require this information. XDM specifies how such information will be defined in XML documents, as well as the common protocol for access and manipulation of such XML documents.

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

OMA XML Document Management V2.0 AER

OMA XML Document Management (XDM) enables the storage of user-specific information in the network, which is managed by authorized principals and accessed by service enablers that require this information. XDM specifies how such information will be defined in XML documents, as well as the common protocol for access and manipulation of such XML documents.

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

Device Capabilities

OMA Device Capabilities Management Object V2.1 CER

OMA Device Capabilities Management Object (DCMO) allows control of device features such as Bluetooth, WiFi access and the camera; and specifies the mechanisms required for the remote management of device capabilities. In particular, DCMO will allow the Management Authority to remotely enable and/or disable certain features and capabilities. The basic features and capabilities of the device will be exposed by DCMO to facilitate management of the components.

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

Access to Content

OMA Mobile Advertising V1.0 AER

OMA Mobile Advertising (MobAd) enabler specifies mechanisms related to user profiles and context as well as mechanisms related to the associated content. Content providers, advertisers and operators will personalize and contextualize advertisements to be sent to a specific type of user. OMA’s MobAd supports interactivity, so users can interact with advertisements and other content. The standard specifies how to ‘use’ interactive advertisements to help users interact with advertisers and content. The specification enables metrics and data collection, including mechanisms to achieve accurate measurement of advertising campaigns based on user behavior.

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

OMA Customized Multimedia Ringing V1.0 AER

OMA Customized Multimedia Ringing (CMR) presents multimedia resources to an end user according to a specified event, e.g. the establishment of a call, the arrival of a message or mail. The CMR enabler provides these main functionalities: service management, resource management, and resource delivery and presentation controls. Additional basic functions of CMR Enabler include; charging, security, and privacy. Certain OMA/non-OMA enablers or third party applications can invoke the open APIs of OMACMR to implement the CMR services.

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

OMA Secure Content Identification Mechanism V1.0 AER

OMA Secure Content Identification Mechanism (SCIDM) enabler improves the management of intellectual property in a networked environment and allows the construction of automated services and transactions. The potential applications of secure content identification include charging, content search/management, automatic content monitoring for copyright verification and usage statistics, content filtering/blocking, content tracing, selective recording/playback, remote triggering of ads in broadcast chains, etc.

Secure identification and authentication of digital content would allow secure interactions between content and all other entities such as content providers, content distributor, service provider, operators and end users in the mobile service environment. This will result in a more trustworthy and efficient service and transaction environment.

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

OMA Rights Issuer Common Domain V1.0 AER

OMA Rights Issuer Common Domain (RICD) enabler allows domain management functions, domain rights issuer functions, and domain context to be separated and/or shared across multiple rights Issuers. OMA RICD adds support for offline delivery of Rights Issuer (RI) context and support for additional optional formats.

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