Release Program | The Open Mobile Alliance

OMA Release Program

OMA Releases are made up of different types of Specifications which are publicly available from this portal. The sections below describe the Specifications that OMA publishes.

Requirements Definitions

OMA Requirement Documents (RDs) are normative documents that specify the (technical) requirements for an OMA Release, and describe the use cases that drive these requirements. RDs form an integral part of the Enabler or Reference Releases for which they specify requirements. The Release tables on this portal list the RDs included in each Enabler or Reference Release.

Architecture Definitions

OMA Architecture Documents (ADs) are normative documents that define the functional components and interfaces of an OMA Release, and may also describe high level security and charging aspects of the Release. ADs also form an integral part of the Enabler or Reference Releases for which they describe the architecture.

Enabler and Reference Releases

OMA publishes two types of Release:

An Enabler Release is a set of technical specifications that can be implemented in products and solutions and can be tested for interoperability. An Enabler Release consists of an RD, an AD and one or more Technical Specification (TS) documents. The Enabler Release Definition (ERELD) is a short document describing the specifications that make up the Enabler Release.
A Reference Release is a set of deliverables serving an alternative purpose, e.g. to provide design patterns, guidelines or best practices for developing other Releases. A Reference Release may contain an RD, AD and additional documents such as White Papers. The Reference Release Definition (RRELD) is a short document describing the specifications that make up the Reference Release.

OMA Releases are published in two subsequent phases:

Candidate Release – As soon as the documents making up the Release have been approved by OMA, they are published as a Candidate Release.
Approved Release – When a Candidate Release has undergone a period of public comment (minimum 30days) and, in the case of an Enabler Release has completed the applicable interoperability validation requirements, it is published as an Approved Release.

Test Specification and Validation Plan Documents

OMA facilitates interoperability testing of Enabler Release implementations so as to validate that an Enabler Release fulfils the industry’s requirements for interoperability. These interoperability tests require two types of document:

OMA Enabler Test Specification Documents (ETS)

Enabler Test Specifications (ETS) define the interoperability test cases for Enabler Releases, including the methodology to test, expected inputs and outputs, responses and behaviour for each specified test.

OMA Enabler Validation Plan Documents (EVP)

Enabler Validation Plans (EVP) describe the schedule by which OMA will validate an Enabler, including test events organized by OMA (referred to as “OMA Test Fests”) and other, alternative interoperability validation activities. The EVP also provides any information needed in addition to the ETS to describe the scope or quantity of testing necessary to complete the validation of implementations of an OMA Enabler.

Top Header Icon Menu

Footer Copyright content