2009 Annual Report

The full Annual Report and its component pieces are available in PDF format. Please contact the OMA Communications Team for assistance with requests to reuse the content.

Table of Contents

I. Strategic Direction and Evolution of OMA
     Chairman's Review of 2009 and 2010 Outlook
     Fit for the Future OMA Board and Strategic Planning Committee Secure the Way Forward
     2007-2009 Member Participation and Contributions
II. Technical Program
     2009—A Year of Change and Productivity
     OMA Organizational Chart
Work Program Features
          • Architecture
          • Converged IP Messaging and Converged Address Book
          • Interoperability Program
          • Mobile Codes
          • Device Management
III. Speaking Program and Public Presentations
IV. Industry Collaboration with OMA
          • Rich Communication Suite (RCS)
V. 2009 OMA Technical Achievements
VI. 2010 Release Plan
VII. Current OMA Members
VIII. Contact OMA

Chairman's Review of 2009 and 2010 Outlook

by Fred Harrison
Chairman of the Board, Open Mobile Alliance
Head of Standards, Telefonica

The year 2009 has been one of significant change for OMA. We have experienced the impact of the financial crisis, and our Members told us that OMA needed to improve the market relevance of our work. Within OMA, the Board, our Members and the OMA staff have all responded to these challenges with responsible and appropriate actions, and I am grateful for the support and enthusiasm that has developed within our organisation. Thanks to this effort, I am proud to say that OMA remains fit for the future.

Regarding financial and operational efficiency, we have implemented major changes to the meeting, conferencing and support arrangements. Significant budget savings have been made, whilst the underlying quality of technical support has been maintained. In some cases the facilities and tools for members have even improved.

A major aspect of the Board of Directors’ focus has been the improvement of the OMA process in order to deliver better time to market. Several significant changes have been made to the process used for our technical work, including aspects such as fast tracking, improved decision making, and the concept of an annual OMA release. This annual milestone will improve the visibility, predictability and confidence in OMA deliverables for the whole industry.

The OMA Board, supported by the Strategic Planning Committee, has looked at specific market relevant topics. This has resulted in several new initiatives. There is a call for action to members to analyze the current and future work of OMA in order to support the next generation of Evolved Mobile All-IP systems, including LTE, WiMAX and WCDMA.

The Board has also endorsed the concept of profiling of OMA enablers to optimize delivery for specific market requirements. The successful interoperability program in OMA will be extended to include the idea of testing of deployment groups, focusing tests on a set of profiled enablers, which are determined using a market driven approach. The Board has also established a task force to address the development of OMA enabler APIs in order to facilitate the deployment and adoption of OMA’s technical work.

While some of these initiatives will take time to achieve maximum results, I believe that all of these changes will have a significant impact on the value of OMA to our members, as well as the wider industry. Even as we have been busy with ensuring OMA is fit for the future, the day-to-day technical work has continued to proceed at full flow. As established last year, our Annual Report gives an overview and also some detailed insights into the technical work of OMA.

In reviewing this Annual Report, I hope you will see that OMA continues to be a vigorous environment, delivering valuable results. As we look forward to 2010, I am highly optimistic that we can improve and extend our value to our members and to the ever-expanding mobile industry.

Request a PDF version of the Chairman's Letter.
Request a PDF version of the full OMA Annual Report.
Return to Table of Contents

Fit for the Future
OMA Board and Strategic Planning
Committee Secure the Way Forward

As part of its leadership of the OMA, the Board of Directors, and specifically the Strategic Planning Committee (SPC) are responsible for establishing the vision, strategies and objectives of OMA. This ensures that OMA meets market needs and supports OMA members in realizing the adoption of mobile data services.

Review of Strategic Direction Document—Version 2.2

Updated in March 2009, this document reflects the current vision, mission and scope of OMA by identifying specific goals. It is created as an internal document for all OMA members and is used by the OMA Board of Directors to define appropriate recommendations and actions for improvement or guidelines for the technical work of the organization. The document continues to be updated and released on a periodic basis. This vigilance ensures that OMA is aligned with overall member expectations and market direction.

Establishment of Communications Strategy and Guidelines

In 2009, the Board of Directors clearly defined the objectives, key messages and target audiences for OMA communication channels, as well as the communications tools used to reach these audiences. The publication of the OMA Annual Report is a direct result of this work.

The Communication Strategy and Guidelines offer a framework for OMA's Tactical Communications Plan, which is created annually by the OMA Communications Team. The Board of Directors approves the plan during the annual budgeting process.

In 2009, the communications efforts have primarily focused on disseminating information about the technical achievements of the OMA, using newsletters, technical briefings with press and analysts, as well as speaking engagements around the globe. OMA spokespeople introduce OMA Enabler Specifications to the mobile industry, and the features and benefits of OMA's technical work.

Throughout 2009, the OMA Board has reviewed the market requirements for its deliverables and considered the best way to ensure OMA is fit for the future. In 2010, the communications activities will offer increased public information about the future plans of the organization regarding its pipeline of technical work and specification release plans.

Board Mission Workshop

In May 2009, the Board of Directors took the decision to hold a Mission Workshop with the goal to review the OMA Mission, which had been originally created in 2002. This workshop addressed the strategic priorities of OMA, and provided recommendations for improving the market relevance of OMA enablers. Of primary consideration was how to adapt OMA Enablers to meet the dynamic requirements of the evolving mobile industry.

Held at OMA's Los Angeles meeting in October 2009 and conducted by the SPC Officers, the following key topics were considered:   

• Review of a Board of Directors Survey which measured Board company views on the level of interest, deployment and adoption of existing OMA enablers as well as future areas of interest for OMA's technical work

• Mobile ecosystem analysis focusing on the Mobile Internet in order to establish new areas of interest for OMA

• An analysis of the landscape of all mobile industry standards development organizations (SDO) in order to understand OMA's role in the wider standardization landscape

• Review of OMA Interoperability (IOP) program to respond to the changing demand for testing and to explore new possibilities to serve OMA members and the market

There was wide support and participation in the workshop by the OMA Board of Directors, with important results as follows:

• The OMA Board created a call to action for all OMA members to analyze the implications of supporting service deployment in Evolved Mobile All IP Systems. Considering both existing and future work of OMA, a follow up workshop on services support in evolved mobile ALL-IP networks will be held in February 2010.

• A Board API Task Force has been established to address the development of OMA enabler APIs by identifying and prioritizing highly relevant OMA enablers.

• The Board IOP Committee and Technical Plenary Officers will develop a concept for profiling of OMA specifications to explore opportunities with Deployment Groups for OMA enablers.

• The OMA Technical Plenary will introduce an OMA Enabler Release Plan beginning in 2010. The plan will outline the technical deliverables of the OMA on an annual basis.

• SPC will address membership retention in order to ensure OMA's relevance for existing members, motivate members to upgrade their level of participation, and attract new members to participate in OMA.

Request a PDF version of Fit for the Future.
Request a PDF version of the full OMA Annual Report.
Return to Table of Contents

2007-2009 Member Participation and Contributions

2009 – A Time to Focus on Member Value

2009 proved to be a year of challenges for many technical organizations. OMA's challenges mirrored many of the same issues faced by its members. As a result of the difficult global economic climate, 15% of OMA's sponsor and full members declined to renew their membership in the organization. OMA used the 2009 downturn as an opportunity to evaluate its operations and members support. Rising to this challenge, the Operations Team made adjustments designed to improve fiscal efficiency while maintaining value for OMA members.

In 2009, member companies continued to contribute at previous year’s levels but with scaled down delegations. OMA remains committed to providing strong tools and support services for its committees and working groups in 2010. In some cases, this support will be enhanced in an effort to balance the increasing demands placed on the working group chairs by their home companies.

Additionally, OMA has begun the rollout of new collaboration efforts that allow the working groups to be more effective in the work that takes place during face-to-face meetings. OMA's members believe in the work of the organization and have made it clear they intend to support financially, the effort required for continued success.

Consistency in the Technical Work

More than 100 companies have consistently contributed to OMA's specifications since the organization began in 2002. These companies represent the full spectrum of the mobile industry. They run the gamut from very large companies to small companies, and they are comprised of operators, telecom vendors and IT companies. At its core, 31 members of OMA account for 85% of the contributions over the period 2007—2009.

Fit for 2010 and Beyond

Despite the loss of some members in 2009, these highly active companies have maintained their membership, consistently contributing their ideas year after year. The results are a stable, competent backbone for the specification work of OMA. In fact, 2009 has shown the same level of technical contributions received in 2007 and 2008. The outlook for 2010 is bright, and OMA's finances are strong. The company has planned conservatively for 2010 and carries sufficient reserves to allow OMA to follow through on its strategic initiatives while ensuring its core work is executed.

Request a PDF version of 2007-2009 Member Participation and Contributions.
Request a PDF version of the full OMA Annual Report.
Return to Table of Contents

2009 — A Year of Change and Productivity

by Mark Cataldo
Chairman of the Technical Plenary, Open Mobile Alliance

What a year! 2009 has seen the OMA Technical Plenary undergo some of its most significant challenges and achievements since its first meeting in 2002.

The challenges we faced, a direct consequence of the world financial maelstrom, also significantly impacted many other fora. The OMA Technical Plenary was challenged to meet, address and overcome these obstacles, and I am proud to share our success in addressing them.

The global economic woes manifested themselves in many guises for OMA: reduction in membership numbers, reduction in delegation sizes, fewer meetings and pressure to deliver more, and deliver it faster. We have made significant improvements to meet these demands.

In the Technical Plenary, members have continued to be as technically active in 2009 as in 2008, with technical contributions running higher than 2008. New exciting work items continued to be submitted, with members promoting works to further expand our technological footprint.

Also, during 2009, we continued to maintain our technical rate of delivery and received Board ratification for

• 46 new/revised Requirements and Architecture Documents

• 64 new/revised Releases

• 37 new/revised test specifications

Over the last year, the Technical Plenary has improved the following aspects of our process, with specific initiatives that include:

• Major financial adjustments and efficiencies within the OMA budget

• Significant overhauls to our working practices

• Commenced drafting annual OMA Release Plans

• Tighter control of our Work Programme Management

• Enhanced and extended administrative support to our hard-working Officers and Convenors

Throughout 2010, we will hold a series of training sessions to communicate our enhanced processes and provide extensive training to our Officers, Convenors and wider membership.

Our goal for 2010 is to become even more focussed on fulfilling market needs and relevance in an increasingly challenging global landscape. In the presence of formidable new players in the mobile industry, rapidly advancing technology and the arrival of the service-enabled Internet, the OMA Technical Plenary is indeed fit for the future demands of the mobile industry.

We face 2010 and beyond with renewed vigour. Now more than ever, OMA's Technical Plenary is well-placed to meet the challenges ahead with the support of our strong and committed membership.

Request a PDF version of 2009—A Year of Change and Productivity.
Request a PDF version of the full OMA Annual Report.
Return to Table of Contents

OMA Organizational Chart

Request a PDF version of the OMA Organizational Chart.
Request a PDF version of the full OMA Annual Report.
Return to Table of Contents

Work Program Features

OMA Architecture

Service Oriented, Loosely Coupled, Broadly Interoperable Across Devices and Bearer Technologies

Creating Service Enablers in a Horizontal Environment

OMA's Architecture Working Group (ARC) was created at OMA's inception in 2002 to standardize reusable service components and to ensure architectural consistency across the OMA's body of technical work. In the development process, each Enabler passes through the Architecture Phase, resulting in the enabler's Architecture Document (AD). These individual architectures are all based upon a horizontal services architecture, defined as the OMA Service Environment (OSE).

For OMA's purposes, a horizontal services architecture is a reference system for creating and deploying loosely coupled interfaces among multiple OMA Enablers. Not limited to or defined by server side or terminal side deployments of OMA Enablers, the OSE is designed to allow operators to customize services or engage multiple vendors' enabler implementations across domain boundaries, while using standardized components. This allows differentiation of various products and services by using a Services Oriented Architecture (SOA).

OMA Service Environment

The OSE model allows each OMA enabler to define its own abstract interface which can be bound to a specific protocol to carry results back to the application. This way, nimble service building blocks based on network capabilities are made available to a large community of creative application developers to be composed with other building blocks into innovative new services. Since OMA's inception, the OSE has proved useful for the interoperability of applications and services across various bearers.

With the proliferation of third party service and application providers, the OSE allows service delivery to the end user in a controlled way. OMA ARC has designed the OSE to meet shifting market requirements, such as most recently the introduction of IP-based services across mobile networks. The OSE is prepared for the ever-widening demand for rich content and services, Web services or yet-to-be determined capabilities on any portable or network connected device. Various other Standards Development Organizations (SDOs) are socializing or adopting the OMA OSE concept for their own use in their own domain. These include the TM Forum's Service Delivery Framework, as well as the ITU-T Next Generation Network open service environment.

In summary:

• OMA specifies Mobile Service Enablers

• OSE defines interfaces to these Enablers' basic functions

• OSE interfaces are designed for re-use

• OSE supports various protocol bindings, including Web services

The Changing Landscape of Standardization

OMA now provides a consolidated location in the industry where Telecommunications Web Services and Application Programming Interfaces (APIs) can be specified. This further enhances the programmability of services.

OMA ARC continuously responds to market dynamics and adapts to industry demand for more services and the freedom to connect multiple services and applications to the mobile network, specifically in response to the convergence of Internet applications in the mobile domain. Most recently, in a drive to attract the larger community of Web developers, OMA ARC has successfully consolidated a group of Telecommunications based API specifications:

• OMA Parlay Service Access (PSA)

• RESTful Binding for Parlay X Web Services (ParlayREST)

• OneAPI Profile of the Parlay X SOAP Web Services (PXPROF)

• Ongoing OMA work in Next Generation Service Interfaces (NGSI)

More on OMA Parlay Service Access (PSA)

After the consolidation of the Parlay Group under the OMA umbrella without full affiliation in 2008, OMA ARC took up the maintenance and further evolution of Parlay's work in conjunction with 3GPP and ETSI. In particular, the resulting OMA PSA demonstrates significant cooperation between OMA and 3GPP. Further, the OMA OneAPI Profile of Parlay X SOAP as well as the OMA RESTful bindings for Parlay X Web Services demonstrate the ongoing collaboration between OMA and the GSM Association's OneAPI Project.

More on OMA RESTful Binding for Parlay X Web Services (ParlayREST)

The scope of the OMA REST enabler is to specify an HTTP protocol binding for a subset of Parlay X Web Services specifications in OMA, using the REST architectural style. These REST bindings are defined for abstract API definitions from existing OMA enablers. REST is the architectural style of the World Wide Web—the URI/HTTP/HTML-based transfer of resource representations between browsers and web sites. By defining a REST binding for these interfaces, the larger Web developer community can now integrate OMA Enablers in their own service compositions using the tools and methodologies they are already familiar with. This promises to open up many new markets where OMA Enablers can be deployed.

OMA Parlay REST 1.0 defines REST protocol bindings for the following APIs:

• Short Messaging Parlay X Web Services

• Multi Media Messaging Parlay X Web Services

• Payment Parlay X Web Services

• Terminal Location Parlay X Web Services

More on OneAPI Profile of the Parlay X SOAP Web Services (PXPROF)

Currently, OMA is the owner of the Parlay X SOAP specifications. After receiving a request from GSMA to provide a subset of these specifications as one standards package, OMA ARC began work on OMA PXPROF.

The OMA PXPROF 'OneAPI Profile of the Parlay X SOAP Web Services' provides a lightweight subset of already defined APIs. This will encourage developer communities to build applications using enablers that are consistently available across mobile carriers. The profile also helps to further reduce the complexity often inherent in telecommunications signaling protocols, bringing back the enablers to their basic operation (e.g. 'send SMS').

The current OMA PXPROF subset under consideration targets the very same APIs as OMA Parlay REST 1.0:

• Short Messaging Parlay X Web Services

• Multi Media Messaging Parlay X Web Services

• Payment Parlay X Web Services

• Terminal Location Parlay X Web Services
  

Parlay X and OMA PSA Provide Simple, Abstracted Web Services
Use of Network Functionality, Features and Enablers

Next Generation Services Interface (NGSI)

OMA REST and OMA PXPROF take existing interface definitions and increase their appeal to application developers either by defining an alternative binding technology or by profiling. Conversely, NGSI in OMA ARC focuses on new requirements and API extensions for server-to-server based third party services. Evolving from the integration of the Parlay work into OMA, NGSI will expand next generation networking and services for seamless integration of fixed and mobile networks. By creating a uniform and accepted standard of open APIs, third parties will use application interfaces to access network capabilities as well as further enhance existing capabilities.

The scope of NGSI includes the standardization of new functional APIs for:

• Data Configuration and Management

• Call Control and Configuration

• Multimedia List Handling Extensions

• Context Management

• Identity Control

• Registration and Discovery functions
  

Summary

OMA ARC has answered industry demand for increased programmability of services. Taking into account the ever-widening availability of these service across a wide variety of networks and bearers, OMA's service oriented environment will ensure interoperability of these services. As more companies enter the mobile domain, and technology continues its rapid advancement, OMA is fit for the future demands of this evolving mobile landscape.

Request a PDF version of Work Program Features: Architecture.
Request a PDF version of the full OMA Annual Report.
Return to Table of Contents

Work Program Features

Converged IP Messaging and
Converged Address Book

OMA Converged IP Messaging (CPM) and Converged Address Book (CAB) Make Way for the Evolution of Rich Services and Content Sharing by Integrating Existing Messaging Systems

Currently, voice mail, text (SMS), multi-media messaging (MMS), instant messaging and email services all live in individual silos. Different clients, on multiple devices, manage these services across various bearers and networks. This creates a confusing array of choices and decisions to be made when users want to contact each other, share content and communicate.

With the convergence of IP and mobile-based services and networks, as well as increased and increasing bandwidth capacity across networks, users now have the opportunity to use multiple access methods to all of these services. What's missing? The integration of all of these services into a single architecture.

OMA is near completion of two new specifications that create an integrated architecture for messaging and contact information using the SIP/IP core. This will require a richer communication experience on handsets, as well as interoperability between the new specification and legacy communications systems such as MMS and SMS.

Managing a Wide Variety of Devices, Capabilities and User Experiences

A converged messaging specification requires a broad set of functionalities that mirror the single messaging modes that exist today. In order to integrate these various messaging technologies and models, OMA CPM will allow messaging traffic to move in each of the following modes.

• Immediate/deferred delivery

• Push/pull delivery

• Pager/session mode

• Group communication

• Discrete/continuous media

Further, OMA CPM will support communication with multiple devices at various end-points. CPM will also offer enhanced communication scenarios among multiple users in a single session.

• Interworking with non-CPM users (e.g. SMS, MMS)

• From/to multiple addresses and devices

• Common network repository

• Presence

• User communication preferences / capabilities

Flexibility and evolution

• User preferences and user preference profiles offer the ability to pre-configure preferences. This affects how a user receives a CPM-based service. Preferences also offer the ability for group preferences in different contexts (e.g. Home, Office, etc.).

• Framework concept comprises a set of functional components and interfaces that have been designed to facilitate easy deployment of existing and future communication services.

Simplification and enrichment of user experience

• Communicate without the need to know what technology I am using

• Communicate without the need to know what technology my contacts are using

• Accessible from any (set of) device(s) concurrently over any IP network

Enables "global messaging community" instead of today's silo communities

• Global architecture that converges existing messaging user experiences

• Interworking with existing messaging services

• Common network repository for any type of message and media

CAB – Managing a Variety of Devices from a Single Environment

OMA CAB allows the use of a single network-based address book environment by a variety of services and devices. It provides advanced features aimed at enhancing the functionality and user experience of the address book.

CAB 1.0 Features

• Address Book (AB) synchronization with various devices registered by the same CAB User across IP networks

• Management of CAB User's Personal Contact Card (PCC) into different Contact Views (see figure next slide)

• Contact Subscription and publishing of PCCs to other CAB Users in order to automatically update their ABs with latest contact information

• Contact Share of AB and PCC information or subsets to other users (CAB Users or legacy)

• Search of contact information in AB and PCC data, subject to authorization rules set by CAB User owning the data

• Interworking with available non-CAB network based address book(s), performing format adaptation to/from Legacy Formats and support of search in External Directories.

• CAB exposes to other Enablers the capability to read data in AB and PCC

• CAB Enabler supports interoperation between service providers

Modularity and Reuse of OMA Enablers

CAB 1.0 works in conjunction with these OMA releases:

• XML Document Management 2.1

• Data Synchronization 1.2

• Device Management 1.2

CAB 1.0 External Dependencies

• IETF
  

Request a PDF version of Work Program Features: Converged IP Messaging and Converged Address Book.
Request a PDF version of the full OMA Annual Report.
Return to Table of Contents

Work Program Features

Interoperability Program

The Interoperability Program has been adjusting it's work to meet the economic challenges of the past 12 months. It has been recognised that travel budgets and resources of the Member companies have been reduced throughout the year.

To meet these challenges, OMA has introduced two new resources and improved an existing test mechanism to help members continue their testing efforts. These initiatives are:

• The launch of TestBank

• The improvement of OMA's Bi-Lateral Test Program, and

• The introduction of the Virtual Test Events

Virtual TestFest Logistics

TestBank allows member companies to register their interest in testing an implementation of an enabler. Details of the enabler they wish to test, their location, availability, and the type of testing they would like to perform are placed on the OMA member website for other OMA Members to view. If a suitable partner is found, then OMA staff can facilitate the organization of the testing and the creation, collection and analysis of the test reports for the testing performed.

OMA's Interoperability Program has recently introduced Virtual Test Events as a mechanism that will allow OMA members to test the majority of the OMA Enabler implementations remotely. This eliminates the need for any team to travel to a neutral or member test location. Such virtual testing is performed by using secure SMS messaging to support the enablers being tested, and is fully supported by OMA staff for logistics planning and reporting.

Testing can be performed using Bi-Lateral Testing, where one or more member companies will travel to the site of another company to perform a series of tests on the implementations of their enablers. In 2009, OMA staff have created new Bi-lateral test packs and test report procedures to help all the attending companies organize their test efforts more easily.

OMA's Interoperability Program has recently introduced Virtual Test Events as a mechanism that will allow OMA members to test the majority of the OMA Enabler implementations remotely. This eliminates the need for any team to travel to a neutral or member test location. Such virtual testing is performed by using secure SMS messaging to support the enablers being tested, and is fully supported by OMA staff for logistics planning and reporting.

Promotion of the new testing mechanisms was undertaken to members through an IOP Roadshow in the second half of the year. Presentations of how the mechanisms work and how to get the most out of the Interoperability Program helped attract more members to register for the new programs.

Also in 2009, the Interoperability program continued to develop its' TTCN-3 Source Code Development Program. After the successful Mobile Broadcast test case developments in early 2009, the group has expanded the program to include Secure User Plane for Location tests and is planning support for Simple Instant Messaging, Presence-SIMPLE, XML Document Management and Data Synchronization. These tests should be available to member companies in early 2010.

Finally, the Interoperability Program is looking forward to 2010 with a new initiative in Profiling and Deployment Groups where Operators will be able to initiate a market drive approach to testing the required features and capabilities of a group of OMA Enablers that they wish to have form the basis of a Service for their customers.

Request a PDF version of Work Program Features: Interoperability Program.
Request a PDF version of the full OMA Annual Report.
Return to Table of Contents

Work Program Features

Mobile Codes

OMA Mobile Codes Enabler aims to stimulate a global market in which Barcodes act as enablers for camera-equipped handsets to access content and services.

Existing Barcode Technologies

Mobile codes—2D and 1D Barcodes—have emerged as a promising enabler of the mobile Internet in some markets. Camera-equipped handsets offer improved optics, image resolution and processing capacity to read mobile codes on printed materials and electronic displays. These symbols encode information such as URLs, phone numbers, and in-line content such as business cards. Despite these successes, interoperability between different markets and players remains illusive. This hinders the wide adoption of mobile code readers as well as the deployment of mobile codes for use in advertising and promotion.

As with other technologies, the majority of consumers are unlikely to adopt the technology before it comes pre-installed on their devices. Therefore, marketing, publishing and other industries that are otherwise motivated to provide mobile codes will not adopt them without adequate potential for consumer uptake. The wide use of mobile codes by a variety of different industries will drive deployment of mobile code readers on a large variety of devices. This deployment will then drive interoperability between different service providers.

Currently, the fragmentation in the global market is due in large part to the variety of barcode symbologies (formats) available, which symbologies should be supported and what data they should contain. Further, for Direct and Indirect Codes, how client software should behave is not standardized. Likewise with Indirect Codes, how the backend resolution process supports the marketing goals of the Code Publishers remains unanswered.

OMA Mobile Codes

The OMA Mobile Codes Enabler seeks to halt fragmentation by providing guidelines on existing standards as well as creating specifications to support interoperability between devices and regions. Operators, marketers and retailers will be able to employ one standard for deployment from Singapore to San Francisco. The goal of any standards deployment is to reduce costs and improve convenience and reduce risk of deployment. OMA Mobile codes also seeks to help create user expectations and industry demand for 2D Barcodes. This would demand the reliability of code reading (‘decoding') by a wide variety of mobile devices. In particular for Indirect Codes, resolution of the barcode through different backend systems on the network in an interoperable way is critical to deliver the experience and reach intended for each code. Success in meeting these goals will enable new marketing opportunities and offer an exciting and reliable call-to-action channel for mobile advertisers.

The OMA Mobile Codes (MC) Enabler will meet the following requirements:

• Create a standard in which Mobile Codes act as conduits for camera-equipped handsets to access content and services, thus enabling the barcode to connect the physical world to virtual digital content and services.

• Standardise 2D barcode symbologies for mobile use, reusing existing open standard solutions. This will maximise modularity of the OMA MC Enabler with other OMA enablers, speeding development and facilitating wide scale adoption.

• Define the format of data stored in the 2D barcodes.

• Specify the behaviour of the code reader or the device when reading barcodes.

• Maximise backwards compatibility with existing and relevant 2D barcode systems.

• Define interoperable solutions for critical building blocks* (resident inside the network) in an Indirect Code ecosystem.

*Indirect Encoding allows for enhanced user analytics and code scan statistics reporting

Basic Use Cases for Mobile Codes — Direct and Indirect Modes

Direct Mode — Service information embedded in the 2D Barcode
        1. User scans a code
        2. Mobile Code Client processes the Code, which prompts access to data or a service
        3. An appropriate application is triggered, such as browsing to a specific URL, storing information on a business card, sending an SMS, etc.

Indirect Mode —2D Barcode data contains an ‘Identifier’ which needs to be resolved

Network Architectural Components for Indirect Mode

A Code Management Platform (CMP) performs routing and/or code resolution for Indirect Codes.

• The code registration function assigns and links a unique identifier to a specific user experience as directed by the Code Publisher.

• The code clearinghouse function is used to determine whether a code is hosted locally or remotely; the mobile codes registry may be queried to make this determination. It then redirects the code to the code resolution function (either locally or remotely).

• The code resolution function is used when hosting a code. It maps the code Identifier into content or an address for content (or service) as directed by the Code Publisher.

• In some markets, the clearinghouse or code resolution functions may reside in separate code management platforms.

• Each code management platform is assigned at least one Routing Prefix under which numerous Identifiers can be hosted.

A Mobile Code Registry (MCR) allocates unique routing prefixes to code management platforms.

• Obtains unique code management platform routing prefixes that are allocated by the root registry, which is maintained by the Open Mobile Naming Authority.

• Sub-allocates routing prefixes to code management platforms and ensures their orderly registration.

• Supports the discovery and routing information of the code management platform that is hosting (i.e. resolving) a particular Identifier.

A Mobile Code Client (MCC) is an application in the device that interacts with the device camera to capture the Barcode Symbology and decodes the glyph into a data string representing a Direct or Indirect Code.

• Symbologies present issues of code reading robustness and reliability.

• OMA MC will support a small set of barcode symbologies based on proven robustness and reliability for code reading.

• Mandate only open standards symbology(ies) to ensure a common entry point into the OMA Mobile Codes Enabler.

• Support updating the mobile code client with optional additional symbologies depending on market needs and device capabilities.

• Service Aspects Online and Offline modes support aspects of Indirect Code resolution with or without network interaction.

• OMA MC will ensure secure and efficient transfer of the data between the MC Client and network entities to safeguard a satisfactory user experience.

• Support optional collection and reporting of voluntary user profile information on an ‘Opt-In/Opt-out' and anonymised basis, including code scan statistics, etc.

• Support recognition, decoding and processing of a variety of content formats encoded directly in Direct Codes (including: business card information, email, phone numbers, http URIs, SMS URIs, IM URIs, etc.)

• Support OMA initiative of enabler APIs by exposing data read from a Direct Code to additional applications on the device.

System requirements

Deployment of the mobile code client in the factory is the ultimate goal for wide adoption of Mobile Codes. However, installation and configuration of the mobile code client can be supported over-the-air by OMA Device Management as well as other means, such as web services, local data cable connection, etc. Key requirements include:

• Invocation of appropriate applications upon Mobile Code processing.

• Service provider operational data transfer between network components is supported (Indirect Code scan statistics, data logging & reporting, charging events, error codes, etc.).

• Optional Indirect Code Security safeguards (prevent fraudulent use of Codes, etc.).

• Optional Mobile Code Service Policy control for each Indirect Code (expiration time, regional scanning constraints, etc.) as prescribed by the Code Publisher.

• Optional tracking & logging of user scanning behaviours (on ‘Opt-in' basis); communications with and in-between network components is secure.

• Optional support to online advertising charging models based on Indirect Code scans.

• Optional support to Transfer of Code Hosting responsibilities between CMPs.

1D Barcode requirements

• Mobile Code Client will read EAN/UPC Barcodes.

• Mobile Code Processing in the device should be common to the 2D Indirect Mobile Codes.

        ** Market-driven target (may be subject to phasing)

Availability of the Mobile Codes Enabler Release

OMA Mobile Codes 1.0 is progressing through the regular OMA development process, which will end with an approved mobile service enabler. This process includes requirements, architecture, technical specifications and interoperability testing. The requirements phase was completed in May 2009, and the architecture is expected to be completed in Q1 2010. The technical specifications should be complete by Q2 2010, with IOP validation soon to follow—subject to availability of vendor prototypes.

Request a PDF version of Work Program Features: Mobile Codes.
Request a PDF version of the full OMA Annual Report.
Return to Table of Contents

Work Program Features

OMA Device Management Working Group Maintains Industry Approval and Sets Stage for the Next Generation of Device Management in 2010

The OMA Device Management suite of mobile service enablers is well established in the mobile value chain, and widely respected for their reliability. Interoperability of services and devices is at the foundation of the OMA Device Management (DM) Working Group approach to standardization. Using the OMA DM Enabler and the various Management Objects provides seamless maintenance and integration of devices, services and applications—now and in the future. Before standardization, the only way to configure devices was in the factory or in the store.

OMA DM Enablers help operators and IT departments manage access capabilities, diagnose problems, fix and update devices over their networks. At home, in the office, on the road, consumer and enterprise applications must work with evermore-complex multi-use devices. These devices must work reliably in multiple environments across a variety of networks and regions. Interoperable and standardized OMA DM Enablers have the agility and complexity to meet the demands of this complex ecosystem.

The OMA DM Working Group has consistently produced device management specifications for over seven years. As a result, billions of handsets deploy OMA DM specifications on the full spectrum of platforms. In the coming year, OMA DM Working Group will continue the extension of OMA DM to standardize converged DM—the interoperability of all network connected devices and appliances. In order to create the most robust new standard, the OMA DM Working Group seeks cooperation with other standards bodies and industry fora.

**Basic OMA DM Architecture

First Generation OMA DM

Since the first publication of OMA DM 1.1.2, OMA DM has provided a platform neutral protocol to allow servers to remotely manage devices. The OMA DM Working Group has continued to enhance and improve the specification. In 1.2, native bootstrap was introduced, reducing the need for OMA Client Provisioning, as well as security enhancements. OMA DM 1.3 has continued this stepwise improvement with the following capabilities:

• Support for the DM Server to use HTTP and SIP Push to send notification messages to the DM Client to remotely start a DM session
  

• Mandatory support for the process of initial installation of parameters on a DM Client to establish a given service for the first time—no other enabler is required

• Support for rich information in notification messages including expiration or the reason for session initiation

• A DM Server is now able to easily discover which optional DM functionalities are supported by the DM Client

• SyncML Common files are merged into DM 1.3—no need for the developer to read other enablers to build a DM Server or Client

• Optional support for the DM Server to send out-of-session messages to the DM Client—reducing the overhead of simple maintenance

• Digital signing of Bootstrap and Sessionless messages is now required, providing authentication and security methods that were previously missing

Use of Management Objects to Ensure the Evolution of Devices and Services

Certain functions can be managed over the network to greatly improve the timeliness of repair and upgrades, as well as reduce the cost of repair and maintenance. Such functions include:

• Connectivity configuration

• Firmware update

• Diagnosis and monitoring

• Software installation and update

• Lock and wipe

• Device Capability Management

• Scheduling of all of these tasks

Why standardize these particular functions?
Standards provide uniform visibility into the resources and functionality of all devices. By using a standard, network operators can manage devices, conduct diagnosis and update devices remotely and without direct vendor support. The interoperability achieved through standardization directly impacts the consumer experience. Equally important, interoperability facilitates the wide adoption of mobile data services on a global scale. The direct cost and efficiency benefits include:

• Reduced support costs

• Fewer recalls/returns

• Operator cost saving and reduced churn

• Revenue enablement

• Service reliability

OMA DM Management Objects Released in 2009
OMA Browser Management Object (Reference Release)

• BMO facilitates management of Browser parameters

• The enabler's HomePage Node acts as a special bookmark, automatically going to the URL defined for the HomePage/URL

• The Favorites Node provides top-level bookmarks for the browser - similar to toolbars on many desk top browsers

• The Folders Node may contain more bookmarks and folders, but is not required to exist if folders are not supported

**OMA DM protocol compatibility for the BMO is version 1.2 or any later compatibility version.

OMA Device Capability Management Object (DCMO)
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.

OMA Diagnostic and Monitoring Management Object (DiagMon)
DiagMon determines the capabilities of any given device, performs fault detection and provides the ability to invoke diagnostic functions. This allows the Management Authority (network operators and corporate helpdesks) to detect and repair actual or potential troubles, This also enables fault reporting back to the network. DiagMon also allows terminals to measure and report key performance indicators. Management Authorities can use the diagnostic enabler to query the device for additional diagnostic data or to invoke specific repair procedures embedded in a given handset model. DiagMon functinalities include:

• Battery status

• Memory status

• Device/Application malfunctions logs

• SMS/MMS usage

• Device restart

• Browser usage reporting

• Application usage reporting

• RF metrics reporting
  

Other OMA DM Management Objects From Recent Years

• Connectivity Management Object (ConnMO)

• OMA Device Management Scheduling

• OMA Firmware Update Management Object (FUMO)

• Lock and Wipe Management Object (LAWMO)

• Software Component Management Object (SCOMO)

Fit for 2010 and Beyond—OMA DM 2.0 Will Meet the Requirements of the Next Generation
of Device Management Scenarios

There is clear market need for an expanded device management protocol - being able to deal with multiple DM Servers and multiple transport protocols. As more and more devices, appliances and technologies can be connected to a network, a wider perspective in how to manage and configure all of these various network-connected devices becomes necessary. The work begun for OMA DM 2.0 has two purposes:

1. Derive a management protocol suitable for converged/multi-mode devices—able to work over the air as well as locally.
2. Improve the First Generation OMA DM technology for inclusion into the new OMA DM 2.0 enabler.

Currently, the interface specification under consideration will 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. This will enable management of devices that lie outside the management domain of the service providers.

The specification will address HTTP, OBEX, UDP, SIP and Broadcast transport & notification, as well as the use of XML Schema. Support for virtualized platforms, such as myriad systems running on a single device, will also be included.

As always, OMA's DM Working Group will continue to liaise with other standards bodies such as the Broadband Forum, Cable Labs, Distributed Management Task Force and Universal Plug and Play, 3GPP and 3GPP2.

Request a PDF version of Work Program Features: Device Management.
Request a PDF version of the full OMA Annual Report.
Return to Table of Contents

2009 Speaking Program Highlights

Request a PDF version of Speaking Program and Public Presentations.
Request a PDF version of the full OMA Annual Report.
Return to Table of Contents

Industry Collaboration with OMA

OMA is not alone in its role of establishing standards, and recognizes the importance of working with other organizations that perform similar or complementary activities. To assist in this effort, the OMA External Liaison Program works to establish relationships with outside organizations and standards bodies to ensure broad industry participation.

Liaison agreements with OMA work in one of two ways:

• Cooperation Framework (CF) provides a set of guidelines agreed (but not formally signed) by OMA and the external organization.

• Cooperation Agreement (CA) where there is formal, signed agreement in place between the external organization and OMA.

OMA currently holds liaison agreements with the following organizations:

Request a PDF version of Industry Collaboration with OMA.
Request a PDF version of the full OMA Annual Report.
Return to Table of Contents

Industry Collaboration Feature

OMA Service Enablers Play Crucial Role in GSM Association's Rich Communication Suite Initiative (RCS)

RCS Market Analysis and Requirements

The RCS Initiative is the joint effort of leading industry players to speed and facilitate the adoption of applications and services that provide users with an interoperable, converged, rich communication experience. Based on IMS, the interoperability of RCS is achieved reusing existing standards, including 3GPP and OMA based enablers.

Over 90 companies are part of RCS, with a strong involvement of the different worldwide actors in the industry. Participating companies include operators, device manufacturers, network infrastructure vendors and software vendors. The primary goal of RCS is to offer interoperability across the four billion existing mobile customers.

The RCS Initiative delivered RCS Release 1 in December 2008 and RCS Release 2 in June 2009. Release 2 offers extension of RCS to the PC. In December 09, RCS Initiative successfully issued RCS Release 3 which provides some enhancements to RCS Release 1 and 2 service features.

End-User Benefits

With requirements provided by operators, device manufacturers, infrastructure vendors, RCS will offer an easy way for any end-user wishing to use enhanced communication services. This will ensure interoperability, economies of scale, and will further enable the wider IMS marketplace.

• RCS offers interoperable services across multiple platforms and customer interfaces.

• RCS leverages the existing Mobile number (MSISDN) without the need to create new accounts on multiple platforms.

• RCS operates just like voice, SMS and MMS today.

• RCS is tightly integrated with the native address book on the handset.

Features and the Use of OMA Standards

Profiling existing standards from 3GPP, OMA and GSMA, RCS integrates them into a single communication suite. In order to deliver instant messaging (IM), content sharing and enhanced address book services, RCS makes these features available on any device and enables interoperable communication accross different devices and networks.

The core feature set of RCS includes the following services:

• Enhanced phonebook, with service capabilities and presence enhanced contact information

• Enhanced messaging, which enables wider messaging options including chat, messaging history and conversational views
  

• Enriched call features such as sharing images, live video and video clips during a voice call

OMA Presence SIMPLE plays a key role in this work. Indeed presence information is used to communicate not only communication capabilities, but also personalized contact features including a photo, hyper availability, status icons, favorite links, free text and location information. Presence can be conveniently shown in the phonebook as well as any connection where services are launched.
**Source of standards for each component of the RCS services.

RCS relies on various OMA enablers including Presence, XDM and IM
Enhanced phonebook
          • OMA DS 1.2.1.
          • OMA Presence SIMPLE 1.1 and 2.0
          • OMA Presence Data Extension (PDE) 1.0
          • OMA XDM 1.1 and 2.0 (in using Permanent Presence State and Presence Content XDMS)
          • OMA XDM and Presence implementation guidelines (OMA XDM PRS IMPL 1.0)

Enhanced messaging features
          • OMA SIMPLE IM 1.0

Support for management objects and operations
          • OMA Device Management

Current Achievements and Future Plans

The RCS Initiative has defined a core feature set, developed reference implementations of the services and conducted interoperability testing in a multi-vendor environment. To date, core network standards are being developed in 3GPP while IMS based services are standardized in OMA.

The current focus of the RCS initiative is to overcome some of the existing obstacles to deployment and adoption of these future services. Using a common, well-defined set of features, based on profiling of the available standards coming from 3GPP and OMA, RCS ensures that interoperability can be achieved within that common feature set.

Latest OMA achievements in meeting RCS business needs

OMA has provided a standardized solution to handle label information associated with a favorite link. Favorite link is part of RCS Release 3 identified use cases. OMA PAG has recently defined OMA Presence Data Extension (PDE), which contains all the required presence attributes & elements to support such label information.

Request a PDF version of Rich Communication Suite (RCS).
Request a PDF version of the full OMA Annual Report.
Return to Table of Contents

2009 OMA Technical Achievements

Using a clear working process, the Enabler Release Program is designed to deliver three key milestones for each enabler:

OMA Candidate Enabler Releases (CER)
An OMA Candidate Enabler Release delivers an approved set of open technical specifications that can be implemented in products and solutions, and then tested for interoperability. Upon publication as a Candidate, specifications then enter the OMA Interoperability Testing Program where they will eventually reach Approved Enabler Release status.

OMA Candidate Reference Releases (CRR)
An OMA Candidate Reference Release delivers a set of specifications and/or white papers which form a formal deliverable of OMA. The release can be referenced or otherwise used to support implementable enabler releases, but it cannot by itself be implemented in products.

OMA Approved Enabler Release (AER)
An OMA Approved Enabler Release represents a Candidate Enabler Release that has gone through the Interoperability Program (IOP) of OMA. The IOP tests interoperability between different member companies' implementations-either within the OMA or through other means.

*Please note. Graphics of basic architecture for OMA Enablers are available by rolling your cursor over the title of the enabler.

Architecture, Security and Charging

OMA Global Permission Management V1_0 CER
OMA Global Permissions Management (GPM) enabler provides generic permissions checking and permissions management, which can be used by other resources. The role of the GPM enabler is to specify how authorized principals are managing the permission rules that determine if, when, how and to what extent information about end-users (i.e. Permissions Target) is released to Target Attribute Requesters and Consumers, (e.g. applications, enablers or other end-users), and to specify how permissions checking requests for release of information are defined and processed.
http://www.openmobilealliance.org/Technical/release_program/gpm_v1_0.aspx

OMA Charging V1_1 CER
OMA Charging Enabler enables charging for various types of Chargeable Events to a subscriber's account, possibly maintained by an underlying Charging Infrastructure. The Charging Enabler is not a Charging Infrastructure in its own right but a facilitator in the process of providing charging at the application and OMA enabler level. The value delivered by the OMA Charging Enabler with respect to other service providers relates to the enabling of new business models and entities that can benefit from open, standardized access to Charging Events generated in an OSE domain.
http://www.openmobilealliance.org/technical/release_program/charging_v1_1.aspx

OMA Charging Data V1_0 CRR
OMA Charging Data enables charging for various types of transactions. The value of OMA Charging Data rests in the ability to enable new business models and entities to benefit from open, standardized access to Charging Events generated in an OMA Service Environment (OSE) domain.
http://www.openmobilealliance.org/Technical/release_program/charging_data_v1_0.aspx

OMA Smart Card Web Server V1_1 AER
The OMA Smart Card Web Server allows local communication between the Smart Card Web Server and an HTTP application (e.g. Web browser) running in the handset.
http://www.openmobilealliance.org/Technical/release_program/SCWS_v1_1.aspx

OMA Parlay Service Access V1_0 CRR
The aim of OMA Parlay Service Access (PSA) is to address (per OMA processes) those 3GPP Release 8 requirements for which no technical work has been done in 3GPP and for which the responsibility of defining the resulting solution specification has been moved to OMA ARC WG.
http://www.openmobilealliance.org/Technical/release_program/psa_V1_0.aspx

Device Specifications

OMA Device Capability Management Object V1_0 CER
OMA Device Management Capabilities Management Object (DCMO) enabler 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 the DC. The device capability information will be exposed by DCMO to facilitate management of the device capability components.
http://www.openmobilealliance.org/Technical/release_program/dcmo_v1_0.aspx

OMA Software Component Management Object V1_0 CER
OMA Software Component Management Object (SCOMO) enables remote operations for software components within the device. SCOMO specifications allow operator and corporate IT departments to manage software inventory such as libraries and user interface elements. SCOMO ensures the compatibility of old and new software by removing/updating existing software and installing new software.
http://www.openmobilealliance.org/Technical/release_program/scomo_v1_0.aspx

OMA Device Profile Evolution V1_0 CER
OMA Device Profile Evolution enabler (DPE) provides a standardized solution to convey information on the device capabilities of a particular device. The DPE enabler conveys information on static device capabilities and dynamic device capabilities. This information originates in the device and is communicated to a Service Provider (SP), allowing enhanced quality of the services resulting in a better user experience.
http://www.openmobilealliance.org/Technical/release_program/dpe_V1_0.aspx

OMA Diagnostic Monitoring V1_0 CER
OMA Diagnostics and Monitoring (DiagMon) Enabler manages distributed, mobile wireless devices, in order to optimize a subscriber's experience and reduce network operating costs. With DiagMon, operators, vendors and enterprises can perform various diagnostics and monitoring operations on handsets across a network. These include Diagnostics Policies Management, Fault Detection and Reporting, Performance Monitoring, Device Interrogation and Remote Device Repair.
http://www.openmobilealliance.org/Technical/release_program/diagMon_V1_0.aspx

OMA SyncML Common V1_2_2 CER
OMA SyncML representation protocol is defined by a set of messages conveyed between entities participating in a SyncML operation. The messages are represented as an XML document. OMA SyncML defines the logical structure and format of various SyncML messages which are used by Data Services and Device Management. The SyncML representation protocol supports protocol models that are based on a request/response command structure, as well as those that are based on a 'blind push' command structure.
http://www.openmobilealliance.org/Technical/release_program/SyncML_v1_2_2.aspx

OMA Lock and Wipe Management Object V1_0 CER
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 Look and Feel Customization V1_0 CER (Figure 1)
(Figure 2)
OMA Look and Feel Customization (LFC) enabler allows different entities such as service providers, operators, manufacturers and enterprises to configure device look and feel according to their requirements and needs. Specific examples of customization include background wallpaper/screensavers, ring tones, audio cues and sounds, animations and splash screen, status indicators, fonts and menus.
http://www.openmobilealliance.org/Technical/release_program/LFC_V1_0.aspx

OMA Firmware Update Management Object V1_0_4 AER
OMA Firmware Update Management Object (FUMO) enables firmware updates by specifying the locations in the management tree where update packages could be downloaded. It also specifies commands that need to be invoked on specific nodes of the management tree to start an update activity.
http://www.openmobilealliance.org/Technical/release_program/fumo_v1_0.aspx

OMA Data Synchronization V2_0 CER
OMA Data Synchronization (DS) reduces traffic, improves security, introduces real-time synchronization, adjusts OMA DS based email synchronization and improves readability and interoperability.
http://www.openmobilealliance.org/Technical/release_program/ds_v2_0.aspx

OMA Browser Management Object V1_0 CRR
OMA Browser Management Object (BMO) facilitates management of Browser parameters. The enabler's HomePage node acts as a special bookmark, automatically going to the URL defined for the HomePage/URL. The Favorites node provides top-level bookmarks for the browser—similar to toolbars on many modern browsers. The Folders node may contain more bookmarks and folders, but is not required to exist if folders are not supported.
**OMA DM protocol compatibility for the BMO is version 1.2 or any later compatibility version.
http://www.openmobilealliance.org/Technical/release_program/bmo_v1_0.aspx

OMA Device Management Scheduling V1_0 CER
OMA DM Scheduling Enabler V1.0 specifies the Device Management Scheduling Framework and corresponding Management Objects that can be layered on top of the OMA DM v1.2 to add seamlessly the common scheduling functionality to existing management infrastructure.
http://www.openmobilealliance.org/Technical/release_program/dm_scheduling_v1_0.aspx

OMA Client Provisioning V1_1 AER
OMA Client Provisioning Enabler enables operators to send new settings over the air; after receiving the settings the customer simply saves them to the phone and is then able to use the service.
http://www.openmobilealliance.org/Technical/release_program/cp_v1_1.aspx

Service [Customization] Specifications

OMA XML Document Management V2_0 CER
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

OMA Location in SIP/IP Core V1_0 CER
OMA Location in SIP/IP core network (OMA LOCSIP) provides a SIP based interface to expose the location information of selected targets. The location information may be processed and utilized by other applications or services in the SIP/IP core network such as a Presence SIP Application server or a PoC Server to enrich the end user experience.
http://www.openmobilealliance.org/Technical/release_program/locsip_v1_0.aspx

OMA Presence SIMPLE V2_0 CER
OMA Presence SIMPLE enabler manages the collection and controlled dissemination of Presence Information. The Presence Enabler provides a variety of services that can be invoked from other enablers including OMA Push to Talk over Cellular and OMA XML Document Management.
http://www.openmobilealliance.org/Technical/release_program/Presence_simple_V2_0.aspx

OMA General Service Subscription Management V1_0 CER
OMA General Service Subscription Management (GSSM) enabler allows an authorized principal to setup, terminate, change, query subscriptions by actions [such as subscribing and unsubscribing to services], register authorized user(s) for using the service and setting subscription preferences and/or service usage constraints for associated user(s). The main objective of this enabler is to specify a set of common functions for all of the service subscriptions within the service provider's domain and thus avoids the unnecessary complexity of a silo approach to subscription management.
http://www.openmobilealliance.org/Technical/release_program/gssm_v1_0.aspx

OMA Secure User Plane Location V2_0 CER
OMA Secure User Plane Location (SUPL) utilizes existing standards where available, to transfer assistance data and positioning data over a User Plane bearer, such as IP, to aid network and SUPL Enabled Terminal (SET) based positioning technologies in the calculation of a SET's position. SUPL utilizes existing standards where available and possible, and SUPL should be extensible to enabling more positioning technologies as the need arises so that they utilize the same mechanism.
http://www.openmobilealliance.org/Technical/release_program/supl_V2_0.aspx

OMA Service Provider Environment V1_0 CRR
OMA Service Provider Environment (OSPE) enabler reduces deployment and lifecycle costs, improves service/component time-to-market challenges, allows component interchangeability (one vendor to another), allows the multi-vendor mixing-and-matching of components, provides run-time end-to-end diagnostics within and across domains/environments to improve services consistency and coherency.
http://www.openmobilealliance.org/Technical/release_program/ospe_v1_0.aspx

OMA Mobile Location Service V1_2 CER
OMA Mobile Location Service (MLS) consists of a set of location specifications complying with 3GPP Release 7 LCS Specification. OMA MLP describes the protocol between an MLS client and the LS. In the 3GPP context, MLP was chosen to be an instantiation of the stage 3 specification for the Le reference point
http://www.openmobilealliance.org/Technical/release_program/mls_v1_2.aspx

Person to Person Communication

OMA Push to Talk Over Cellular V2_0 CER (Figure 1)
(Figure 2)
OMA Push to talk over Cellular (PoC) is intended to provide rapid communications for business and consumer customers of mobile networks. OMA's PoC V2.0 will allow audio (e.g. speech, music), video (without audio component), still image, text (formatted and non-formatted) and file shared with a single recipient, (1-to-1) or between groups of recipients as in a group chat session. OMA-PoC seeks interoperability among the network entities to avoid market fragmentation, by realizing the PoC service in a widely acceptable and standardized manner.
http://www.openmobilealliance.org/Technical/release_program/poc_v2_0.aspx

OMA Push to Talk Over Cellular V1_0_4 AER (Figure 1)
(Figure 2)
OMA Push to talk over Cellular (PoC) is intended to provide rapid communications for business and consumer customers of mobile networks. OMA's PoC V2.0 will allow audio (e.g. speech, music), video (without audio component), still image, text (formatted and non-formatted) and file shared with a single recipient, (1-to-1) or between groups of recipients as in a group chat session. OMA-PoC seeks interoperability among the network entities to avoid market fragmentation, by realizing the PoC service in a widely acceptable and standardized manner.
http://www.openmobilealliance.org/Technical/release_program/poc_v1_0.aspx

OMA Mobile E-mail V1_0 CER
OMA Mobile Email (MEM) enabler provides an improved user experience over alternate means of access to email including browsing, email notification or message / voice based access. The goal of the MEM Enabler is to provide quasi-instantaneous and secure updates of the MEM Client with new emails and server changes, optimized online and off-line usage and capability to securely send email from the appropriate server.
http://www.openmobilealliance.org/Technical/release_program/mem_v1_0.aspx

OMA IMPS Implementation Guidelines V1.3 CRR
OMA IMPS Implementation Guidelines (IMPS) provide guidelines for the implementation of IMPS 1.3.
http://www.openmobilealliance.org/Technical/release_program/imps_impl_v1-0.aspx

Access to Content

OMA Push V2_2 CER
OMA Push (Push) allowing a Push Initiator (PI) to transmit push content and delivery instructions to a Push Proxy Gateway (PPG), according to the delivery instructions. Because 'push' transactions are server-initiated, the Push framework introduces a means to transmit information to a device without a user request.
http://www.openmobilealliance.org/Technical/release_program/push_v2_2.aspx

OMA Categorization Based Content Screening V1_0 CER
OMA Categorization Based Content Screening (CBCS) enabler screens content before delivering it to the user, based on content categories. CBCS can obtain the content category for a given piece of content from a categorization entity, categorization meta-data in the content itself or by analyzing the content. CBCS allows any unauthorized principal to create and manage screening rules according to the deployment scheme of the CBCS Service Provider.
http://www.openmobilealliance.org/Technical/release_program/cbcs_v1_0.aspx

OMA Secure Content Exchange V1_0 CER
OMA Secure Content Exchange (SCE) enables the planned sharing of purchased content between multiple devices, the unplanned and ad hoc sharing of content, enhances the interoperability between OMA and non-OMA DRM systems and extends OMA DRM using an MPEG-2 transport stream as a container of DRM Content.
http://www.openmobilealliance.org/Technical/release_program/sce_v1_0.aspx

OMA Dynamic Content Delivery V1_0 CER
OMA Dynamic Content Delivery (DCD) enhances a mobile user's experience through the periodic delivery of personalized or customized content. Either on a one-to-one (point-to-point) or one-to-many (broadcast) basis, DCD provides users with subscription-based or preference information maintained by the operator or service provider. As a complementary delivery mechanism to the existing mechanisms such as browsing or messaging, DCD will reuse as much existing technology as possible. With OMA DCD, operators can provide an enhanced user experience with the added benefit of delivery control management.
http://www.openmobilealliance.org/Technical/Release_program/dcd_v1-0.aspx

OMA Content Management Interface V1_0 CER
OMA Content Management Interface (CMI) enabler supports the content management needs of service providers including network operators, web portal service providers, and content providers as they deliver content-related services. The CMI enabler supports the deployment of services that depend upon such interactions via a standardized set of functions and interfaces, improving service deployment flexibility, interoperability, cost, and time-to-market. This will further enable consistent deployment of services using a variety of models for supplying content, including 'on-deck' and 'off-deck.'
http://www.openmobilealliance.org/Technical/release_program/CMI_V1_0.aspx

OMA Scalable Vector Graphics for the Mobile Domain V1_0 AER
OMA Scalable Vector Graphics (SVG) for the Mobile Domain V1_0 AER is delivered as a single functional release. It is a complete encapsulation of the W3C SVG Tiny 1.2 specification. It neither adds nor removes functionality. It is expected that as W3C releases subsequent versions of the ‘Tiny' profiled specification, that this enabler will require new versions.
http://www.openmobilealliance.org/Technical/release_program/svg_v1_0.aspx

OMA Mobile Broadcast V1_0 AER
OMA Broadcast (BCAST) is an open global standard for interactive mobile TV as well as on-demand video services, and is adaptable to any IP-based mobile content delivery technology. Currently, OMA's BCAST 1.0 can be adapted to broadcast systems like DVB-H as well as cellular systems like 3GPP MBMS, 3GPP2 BCMCS and mobile unicast streaming systems.
http://www.openmobilealliance.org/Technical/release_program/bcast_v1_0.aspx

OMA Secure Removable Media V1_0 AER (Figure 1)
(Figure 2)
(Figure 3)
OMA Secure Removable Media (SRM) offers a removable media service that protects against unauthorized access to internal content and data. Examples of SRM are secure memory cards and smartcards. OMA Digital Rights Management with SRM provides a secure mechanism to write, read, delete and update rights within SRM. This specification defines mechanisms and protocols of the SRM to extend the OM A Digital Rights Management version 2.0 or 2.1. This extension allows users to move rights among multiple devices and SRM. It also allows users to consume rights stored in SRM without generating and managing complex groups of devices in a domain.
http://www.openmobilealliance.org/Technical/release_program/srm_v1_0.aspx

Services Access Interfaces

OMA Policy Evaluation, Enforcement & Management V1_0 CER
OMA Policy Evaluation, Enforcement & Management (PEEM) enabler provides a standardized way to offer processing and management of policies for other enablers created within OMA. Policies are applied to requests to, or responses from resources or, when explicitly called by a resource. The PEEM enabler also supports service providers to expose service Enablers in a controlled and manageable manner that can be automated. Policy enforcement can be used to automatically satisfy the policies required to access a particular service enabler.
http://www.openmobilealliance.org/Technical/Release_program/peem_v1_0.aspx

Request a PDF version of 2009 Technical Achievements.
Request a PDF version of the full OMA Annual Report.
Return to Table of Contents

2010 OMA Release Plan

All releases planned for completion during 2010

Architecture, Security and Charging

Devices

Service Customisation

Person to Person Communications

Access to Content

Services Access Interfaces

Request a PDF version of 2010 Release Plan.
Request a PDF version of the full OMA Annual Report.
Return to Table of Contents

Current OMA Members

Sponsor Members (12)

Full Members (67)

Associate Members (64)

Supporter Members (70)

Request a PDF version of Current OMA Members.
Request a PDF version of the full OMA Annual Report.
Return to Table of Contents

Contact OMA

Technical Contacts

Staff

Request a PDF version of Contact OMA.
Request a PDF version of the full OMA Annual Report.
Return to Table of Contents

OMA Offices

NOTE: Please use the San Diego, California address for ALL written correspondence.

Return to Table of Contents