Content Delivery

OMA Content Delivery Working Group



The OMA Content Delivery Working Group (CD) is responsible for service layer standardization of content delivery related technologies.

CD WG is chartered to define the basic delivery mechanisms, bi-directional exchange mechanisms, and the processing of key content formats, including the semantics and such user agents, behavior and programming interfaces.

The purpose of the CD WG is to write and maintain OMA specifications and serve as an OMA technical expert group in matters related to content delivery in an OMA environment.

Bringing Value to the Mobile Industry

CD WG provides a broad range of capabilities, which address requirements of content delivery via point-to-point and broadcast bearers in an OMA environment. Those requirements include:

  • the basic delivery mechanisms necessary to support various content delivery paradigms, including how aspects of the OMA environment such as location and presence are used to control content delivery,
  • the bi-directional exchange mechanisms necessary to support various content exchange paradigms, including how to upload content and/or information from the client device to the server, for example, media, social activity, location, device capability, etc,
  • the processing of key content formats, including the semantics and such user agents, behavior and programming interfaces, as is necessary to use such content formats, content rendering and the browser user agent, with the intention of enabling the creation and use of data services on mobile hand held devices, including mobile telephones, pagers and PDAs.


CD WG Highlighted Achievements 2002-2017

The following enablers represent some of the successful specifications delivered by CD WG over the last 10 years.

OMA Generic Open Terminal Framework (OMA GotAPI)

GotAPI provides a total secure framework for applications to access external devices and internal apps through device Web APIs using Web technologies.  This allows developers to create applications compatible with a variety of devices, which until now have required dedicated native code development efforts. With GotAPI, applications running in browsers can access external devices consistently across any OS, giving developers the opportunity to help create a new ecosystem of interoperable devices and applications. This open architecture allows developers to write less complex applications for smart devices while expanding market reach. Plug-Ins implement device Web APIs exposing services from external devices to applications through GotAPI. Read more>>

OMA Mobile Advertising 1.0 (OMA MobAd)

The MobAd Enabler defines a framework that facilitates the following advertising needs:

  • Personalization of Advertisements: One of the key performance indicators for the Mobile Advertising services is the degree of the advertisement’s personalization. The more targeted the advertisements are to a particular user, greater acceptance will be achieved. This work item will specify technologies to facilitate personalized targeting of Mobile Advertisements. Some already identified foundations to enable personalization of advertisements include:

Advertising metadata, its description and its usage,
Enhancement of user profiles with advertising preferences and its usage,
Advertising formats in order to obtain a good user experience and interoperability.

  • Interactivity of Advertisements: Since the first advertising services started using new technologies for delivery of advertisements (i.e. Internet), different pricing models have been defined. The first innovative one was the CPC (Cost per Click), in which the cost of the advertisement for a brand depends on the number of times the user clicks to an ad (e.g. goes to the brand site). While this model is still valid for Mobile Advertisement, new models have continued to emerge.
  • Technology to Facilitate Advertising Metrics: One of the most important parts of an advertising campaign is the metering of the advertisement’s impact and user behaviour. Using these metrics, the advertisers are able to verify the extent to which an advertisement has been delivered to the desired target audiences. Audience reach and frequency of exposure are among the commonly used metrics. Collecting data related to mobile advertisements reach and reaction to them, and correlating such data across large groups/audiences, can provide additional feedback to the Mobile Advertisement value chain. The service providers may offer a better service and additional revenue, or may consider charging for a certified statistics report, or use them as a tool to attract more advertisers. This work item will specify technologies to technically enable and facilitate:

Reporting of the needed advertising metrics,
Recording and collection of these metrics,
Group/audience statistics handling.

OMA Push

OMA Push allows Push Initiators and Application Servers to initiate service-related transactions and content delivery to user devices. OMA Push has evolved over several releases, beginning with WAP Push 1.x releases, which supported the WAP1 bearers, and releases from WAP Push 2.0 up to OMA Push 2.2, which extended support to WAP2 (HTTP) and SIP bearers. The service environment enabled by OMA Push is illustrated in the figure below, which shows the two main options for Push service deployment:

  • A service/content provider, acting as Push Initiator, requests the OMA Push-based delivery of content to a user through a Push Proxy Gateway (PPG)
  • An Application Server directly uses OMA Push to deliver content to a user.

OMA Mobile Broadcast Services

The Mobile Broadcast Services Enabler 1.X addresses functional areas generic enough to be common to many Broadcast Services and which can be defined and implemented in a bearer-independent way. These functional areas (or for short: ‘functions’) are: Service Guide, File Distribution, Stream Distribution, Service Protection, Content Protection, Service Interaction, Service Provisioning, Terminal Provisioning and Notification. Proposed technologies upon which this enabler is specified (e.g. for Service and Content Protection) are based on open standards, or will become part of an open standard; no proprietary parts or extensions are required. Thus, the functions described in this document fully comply with the ‘Open’ of the Open Mobile Alliance initiative.

OMA Digital Rights Management

OMA “Digital Rights Management” (DRM) enables the distribution and consumption of digital content in a controlled manner. The content is distributed and consumed on authenticated devices per the usage rights expressed by the content owners. OMA DRM work addresses the various technical aspects of this system by providing appropriate specifications for content formats, protocols, and a rights expression language.

OMA Mobile Search Framework

The Mobile Search Framework Enabler release defines an open framework providing different capabilities to support mobile search service. The capabilities of this enabler include (not limited to), search engine integration, selection, and results personalization. Search engines are not in the scope of this enabler; nevertheless, some requirements are identified for search engines to be integrated with the Mobile Search Framework Enabler in a standard way.

OMA Social Network Web (OMA SNeW 1.0)

The SNeW Enabler aims at allowing large-scale deployments and interoperability of SNEW Clients and SNEW Servers in a timely manner, further guaranteeing social network federation so that users can easily communicate with users on other SNs and migrate their data. In particular, this document identifies a coherent subset of functionalities specific to SNeW representing a core specification.

OMA Mobile Augmented Reality (OMA MobAR)

The OMA Mobile Augmented Reality (OMA MobAR) aims at providing an overall framework to enable mobile AR services that can assure cross-platform exchange of AR Content and universal access to AR Content by providing new mechanisms for transport, filtering and personalization of AR Contents. OMA MobAR is built over a client-server model, with the MobAR Client receiving the MobAR Server information, and content that can “augment” the scene the user is looking at through his/her mobile device.