Home   
OMA Pipeline

This is a list of OMA Enablers that will be announced from July to December of 2009, as well as new work items that have begun recently. OMA updates this list and makes it public twice yearly in June and December. Roll over graphics are provided when available.


Pending Technical Achievements

OMA Mobile Advertising (MobAd) 1.0

OMA MobAd will specify mechanisms related to user profiles and context as well as mechanisms related to the associated content. Content providers, advertisers and operators will be able to personalise and contextualise advertisements to be sent to a specific type of user. OMA's MobAd will support interactivity, so users can interact with advertisements and other content. The standard will also specify how to 'use' interactive advertisements to help users interact with advertisers and content. The specification will enable metrics and data collection, including mechanisms to achieve accurate measurement of advertising campaigns based on user behaviour.

OMA Mobile Codes 1.0 (Figure 1)

(Figure 2)

(Figure 3)

2D and 1D barcodes—have emerged as a promising enabler that links users to rich and relevant information via scanning of symbols and the mobile Internet. Camera-equipped handsets now have good enough optics, image resolution and processing capacity to read mobile codes on printed materials and electronic displays. Two methods of encoding information are available. These bar code symbols can encode information Directly (e.g. URLs, phone numbers or business cards) for action by the handset.Indirectly, an index/identifier is encoded that is later resolved by a network server ‘CMP' into content or an address for content. Different code resolution systems have emerged. However, there is still a lack of interoperability among different markets and players. Without a standard service enabler, mass consumer adoption of this code reading experience remains questionable. Once the standard is implemented and compliant Code Readers are preloaded on devices, marketers, advertisers and service providers will be able to leverage mobile codes for enhanced customer response and interaction. OMA's Mobile Codes enabler will develop the requisite specifications to fill the interoperability gap. This will energise innovations and investments that realize a new user experience and create an emerging market for new advertising and marketing models.

OMA Push 2.3 Push-to-Multipoint

In the 'normal' client/server model, a client requests a service or information from a server, which then responds in transmitting information to the client. In contrast to this, there is also 'push' technology, which is based on the client/server model. In this model there is no explicit request from the client before the server transmits its content. The Push framework introduces a means to transmit information to a device without a user request. A push operation is accomplished by allowing a Push Initiator (PI) to transmit push content and delivery instructions to a Push Proxy Gateway (PPG). The PPG delivers the push content to the Push Client according to the delivery instructions. The Push Client subsequently delivers the push content to an OMA enabler user-agent or application in the device. The PPG and Push Client are the two architectural entities specified by the OMA Push enabler. In the case of Multipoint Push, client applications may be browsers, multimedia messaging clients, instant messaging clients or other device-based applications that are supported by the Push Client.

OMA Converged Address Book (CAB) 1.0

OMA CAB allows the use of a single network-based address book environment by a variety of services and devices. This provides advanced features aimed at enhancing the functionality and user experience of the address book, as well as interoperability among multiple clients and data bases.

OMA Converged IP Messaging (CPM) 1.0

OMA Converged IP Messaging (CPM) enables the creation of services for parallel conversations among different media types. As an example, concurrent use of several devices and the personalization of services is provided by setting preferences to indicate which messages are sent to which device(s). CPM also allows users to store any type of message or media in a common network repository. Seamlessly integrating legacy voice, video and messaging services (such as MMS, SMS), as well as new CPM services, the CPM Enabler can choose to use presence support to enhance communications experiences. It can also integrate all service communities within a single framework including a converged address book.

New Work Items

OMA Secure User Plane Location (SUPL) 3.0

The purpose of this work item is to enhance the existing OMA SUPL 2.0 enabler and OMA SUPL 3.0 will provide Location Support for Long Term Evolution (LTE). It introduces E-CID support for LTE by adding measurements already defined in 3GPP RAN. A-GPS, A-GNSS and other positioning methods will be supported by reusing existing 3GPP positioning protocols where possible. Explicit SUPL signalling will be used only where support from 3GPP and 3GPP2 positioning protocols is not available. 3.0 has Improved Location for IP Emergency Calls with additional emergency call scenarios such as location support after IP emergency call release is required in some regulatory environments (e.g. Japan). OMA SUPL will introduce improvements to SUPL INIT transport (reduction of latency and elimination of transport restrictions) and security.

SUPL 3.0's High Accuracy Location proposes to evaluate and if feasible support very high accuracy location data, adding new positioning methods, new assistance data and new measurements as needed. Triggered Location Enhancement will provide compressed data during slow/no movement, expanded data during rapid movement and/or change of direction, precise route tracking and new capabilities such as triggers based on location change and/or velocity data. SET to SET Location will enable the SET to continuously obtain absolute and/or relative location of other SETs and can be applied to both immediate and triggered use case scenarios. High accuracy relative SET to SET location will also be supported. Solutions to be evaluated include: direct SET to SET signalling, SET based positioning and SET to SET transfer of location and/or measurements.

NGSI

The main objective of the Next Generation Service Interface (NGSI) enabler is to define a set of new services for deployment across individual, corporate and general societal user communities. Building on extensions beyond today's Parlay X APIs (latest version: 3GPP Release 8Parlay/Parlay X APIs), NGSI will stimulate the usage of various service enablers into new services and applications. Considering the evolution of the network in the day-to-day life, including information sources, social communities and e-commerce, as well as network access and network infrastructure variety, NGSI is positioned to influence the future of the digital life.

OMA Converged Personal Network Service (CPNS) 1.0

Many new mobile services have been affected by the enhancement of Wireless Personal Area Network (WPAN) technologies and their increasing implementations on mobile devices. For instance, many mobile phones implement WPAN features such as Bluetooth, NFC, WiBree and UWB. As the personal devices implementing WPAN features increase, it can be expected that the various mobile data services using WPAN will also spread. To support and invigorate these various new services using WPAN features and to solve the relevant interoperability issues between diverse solutions and systems, standardization must occur. These services will use the converged network which includes both the cellular network and the WPAN together.

CPNS 1.0 considers these two interfaces together and will specify the proper protocol and command sets for a composed network. The composed network could be realized via servers in the network, and by server-less deployment which means peer-to-peer. The standardized protocol and interface have to cover various kinds of mobile data services. Compared to existing OMA enablers which mainly consider the mobile phone as the end point of the service, CPNS 1.0 will convey certain requested data services to devices connected to the personal network.

OMA Spam Reporting (SpamRep) 1.0

OMA SpamRep provides a standardised method for devices to report received spam to a network entity for processing. This Enabler will standardize the message content and interfaces and allows reporting many types of unwanted content—including SMS, MMS, email, video share, and more. The SpamRep client will interface with existing messaging clients in order to fully implement spam controls across the various delivery channels.

OMA DM 2.0

There is clear market need for a converged device management protocol as more and more devices, appliances and technologies can be connected to a network. The work begun for OMA Converged Device Management has two purposes—first to derive a remote management protocol suitable for converged/multi mode devices, and second, to improve the DM Version 1 technology for inclusion in the Converged DM specification. An interface specification is under consideration which can interact with the DM client's management objects. Plans include an improved mechanism for multiple management authorities dealing with a single client, as well as independent management of user accounts, clients and services on any device—not just handsets. The specification will address HTTP, OBEX, UDP, SIP and Broadcast transport & notification, as well as the use of XML Schema. Ideas under consideration for the Converged DM specification are support for virtualized platforms i.e. supporting DM functionality on devices with more than one access technologies/operating systems/environments, OMA's DM Working Group will liaise with other standards bodies such as the Broadband Forum, Cable Labs, Distributed Management Task Force and Universal Plug and Play.