Return to Table of Contents

Download Japanese translation

2011 OMA Technical Achievements

Using a clear working process, the Enabler Release Program is designed to deliver four 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.

OMA Approved Reference Releases (ARR)

An OMA Approved Reference Release represents Candidate Enabler Releases that have gone through the Interoperability Program (IOP) of OMA.

*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 Application Layer Security Common Functions V1_1 CER
OMA Application Layer Security Common Functions (SEC CF) provides a common set of security mechanisms with possible deployment options that can be re-used by OMA enablers. The OMA SEC CF specification will help prevent duplication of security efforts for each OMA Enabler that requires security functionality.  OMA SEC CF offers re-use of both the architectural entities (e.g. Security Gateways, etc) and security specifications (e.g. protocol profiles) when developing new OMA enablers.
http://www.openmobilealliance.org/Technical/release_program/sec_cf_v1_1.aspx

OMA Categorization Based Content Screening V1.0 CER
OMA Categorization Based Content Screening (CBCS) allows any Authorized Principal to create and manage Screening Rules, according to the deployment scheme of the CBCS Service Provider. OMA CBCS enabler facilitates the Content Category for a given piece of Content from a Categorization Entity [CBCS-RD], from categorization meta-data in the Content itself, or by analyzing the Content. OMA CBCS Enabler allows any Authorized 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 Charging Data V1_0 ARR
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 Global Permissions Management V1.0 AER
OMA Global Permissions Management (GPM) enabler re-uses the OMA Policy Evaluation, Enforcement and Management (OMA PEEM) enabler.  OMA GPM includes the Permission Checking and Management component, which provides the following main functions:  Permissions Checking function which processes Permissions Rules, Permissions Rules management function for creating, reading, deleting, modifying of Permissions Rules and a Consent interaction function.
http://www.openmobilealliance.org/Technical/release_program/gpm_v1_0.aspx

OMA Global Service Architecture V1_1 ARR (Figure 1)
OMA Global Service Architecture V1_1 ARR (Figure 2)

OMA Global Service Architecture V1.1 (OGSA), represents a comprehensive architectural view of OMA enablers leveraging the OSE (OMA Service Environment). OSE promotes common architectural principles for how OMA enablers are specified and how they interact with one another while ensuring architecture integrity, scalability and interoperability. OMA OGSA's primary focus is to support new (and/or revised) enabler specifications and to clarify how they fit into the current OMA landscape and how they may be used to support services.
http://www.openmobilealliance.org/Technical/release_program/ogsa_V1_1.aspx

OMA On-Board Key Generation V1_0 AER
OMA On-Board Key Generation V1.0 (OBKG) enables on-board key generation and remote key enrollment functionality by defining additional European Computer Manufacture Association (ECMA) scripts and functions in the Wireless Identity Module (WIM). OMA OBKG will enable a remote application of on-board key generation in the WIM and remote key enrollment for (new) user certificates. Both functions are implemented as ECMA scripts that are embedded in an xHTML page.
http://www.openmobilealliance.org/Technical/release_program/obkg-v1_0.aspx

OMA Smart Card Web Server V1.2 CER 
OMA Smart Card Web Server (SCWS) 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_2.aspx

Device Capabilities

OMA Client-Side Enabler API V1_0 ARR
The OMA Client-Side Enabler API (CSEA) enabler defines a set of requirements for API’s to be made available for Web applications running in browser or widget context web runtime environments; in its first phase, OMA CSEA is focused on OMA DCD, OMA Push and OMA DPE.
http://www.openmobilealliance.org/Technical/release_program/csea_v1_0.aspx

OMA Converged Personal Network Services V1.0 CER 
OMA Converged Personal Network Services (CPNS) enables universal access to services across the convergence of a Personal Network and Wide Area Network/Cellular Network. OMA CPNS Enabler defines a collection of individual networks that can be interconnected by means of a Personal Network Gateway (PN GW) using a variety of mobile and fixed devices. This allows access to services from outside a single network and also allows one network or user to offer services to another user or external network.
http://www.openmobilealliance.org/Technical/release_program/CPNS_v1_0.aspx

OMA Delta  Record Management Object 1.0 CER
OMA Delta Record Management Object (DeltaRecMO) allows the Device Management Server to track changes applied to the Client DM Management Objects (MO). OMA DeltaRecMO records any additions, deletions, and other changes applied to the Client DM MOs. OMA  DeltaRecMO allows a DM Server to retrieve, purge, and asynchronously send Delta Records using DeltaRecMO. 
http://www.openmobilealliance.org/Technical/release_program/DeltaRecMO_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 Device Capabilities Management Object V1_0 CER
OMA Device Capabilities Management Object (DCMO) allows control of device features such as Bluetooth, WiFi access and the camera; and specifies the mechanisms required for the remote management of device capabilities. In particular, DCMO will allow the Management Authority to remotely enable and/or disable certain features and capabilities. The basic features and capabilities of the device will be exposed by DCMO to facilitate management of the components.
http://www.openmobilealliance.org/Technical/release_program/dcmo_v1_0.aspx

OMA Device Management Scheduling V1_0 CER
OMA Device Management (DM) Scheduling Enabler specifies the Device Management Scheduling Framework and corresponding Management Objects that can be layered on top of OMA DM V1.2 to add seamless common scheduling functionality to existing management infrastructure. This functionality is fully interoperable with other Management Objects Enablers including OMA FUMO, OMA SCOMO, OMA DCMO and OMA DiagMon. This allows the management operations to be performed in a scheduled manner, avoiding costly management sessions.
http://www.openmobilealliance.org/Technical/release_program/dm_scheduling_v1_0.aspx

OMA Device Management Smart Card V1.0 CER
OMA Device Management Smart Card (DM SC) allows dynamic provisioning of management objects in the device and provisioning performed through local DM sessions between the smartcard and the DM Client in the device. It extends the provisioning capabilities of the smart card to cover more of the security of DM related operations. OMA DM SC is dependent OMA DM 1.2 and OMA SCWS1.1.
http://www.openmobilealliance.org/Technical/release_program/DM_SC_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 AER
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_1.aspx

OMA List Management Object V1.0 CER
OMA List Management Object (ListMO) lists the Management Objects supported by the OMA DM Client resident on the device and exposed by the device. OMA ListMO allows a device management server to easily retrieve the list of the supported MOs and any associated details.
http://www.openmobilealliance.org/Technical/release_program/ListMO_v1_0.aspx

OMA Look and Feel Customization V1_0 AER (Figure 1)
OMA Look and Feel Customization V1_0 AER (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 screens, status indicators, fonts and menus. 
http://www.openmobilealliance.org/Technical/release_program/LFC_V1_0.aspx

OMA Push V2.3 AER
OMA Push (Push) allows 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_3.aspx

OMA Software and Application Control Management Object V1_0 CER
OMA Software and Application Control Management Object (SACMO), enables remote operations for software and application control in the device. Software and application control management specifications will provide capabilities of processing management actions such as workflow, processing or on device management of software and applications utilizing existing management objects.
http://www.openmobilealliance.org/Technical/release_program/sacmo_v1_0.aspx

OMA Software Component Management Object V1.1 CER
The 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

Service Customization

OMA Condition Based URIs Selection V1_0 CER (Figure 1)
OMA Condition Based URIs Selection V1_0 CER (Figure 2)

OMA Condition Based URIs Selection (CBUS) enabler is a common standard solution to fulfill the functionality requirements of OMA PoC service. OMA CBUS supports the retrieval of a list of addresses and makes them available for messaging, gaming, conferencing and advertisement services. The CBUS Enabler is a common standard solution to fulfill the functionality requirements of OMA PoC service.

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

OMA Mobile Location Protocol V3.1 AER
OMA Mobile Location Protocol (MLP) determines the position of mobile stations (mobile phones, wireless personal digital assistants, etc.) independent of underlying network technology. OMA MLP serves as the interface between a Location Server and a Location Services (LCS) Client. This specification defines the core set of operations that a Location Server should be able to perform.
http://www.openmobilealliance.org/Technical/release_program/mlp_v31.aspx

OMA Mobile Location Service V1_0 CER
The OMA Mobile Location Service (MLS) V1.0 consists of a set of location specifications complying with 3GPP Release 6 LCS Specification. OMA MLS V1.0 is primarily intended for use in a 3GPP environment. The set of specifications in MLS V1.0 consist of OMA Mobile Location Protocol (MLP) V3.2 and OMA Roaming Location Protocol (RLP) V1.0.
http://www.openmobilealliance.org/Technical/release_program/mls_v1_0.aspx

OMA Open Connection Manager API 1.0
OMA Open Connection Manager API (OPENCMAPI) standardizes new functional APIs essential for applications to develop connection manager user interface and to extend applications and services with information related to the connection.
http://www.openmobilealliance.org/Technical/release_program/OpenCMAPI_v1_0.aspx

OMA Presence Access Layer V1_0 CER
OMA Presence Access Layer (PAL) Enabler complements OMA Presence SIMPLE. OMA PAL specifies logically interoperable abstractions known as Presence Aspects. Presence Aspects consolidate Presence Information based on one or more Presence Information Elements. Presence Context associates applicable Presence Aspects required to fulfill service function points with a Presence Aware Service. This provides PAL Clients with a consolidated and determinate view of Presence Information.
http://www.openmobilealliance.org/Technical/release_program/pal_v1_0.aspx

OMA Presence SIMPLE Data Extensions V1_3 CRR
OMA Presence SIMPLE Data Specification (PDE) reference release defines further Presence Information extensions and their mapping to the presence data model components and Presence Data Information Format extensions (PIDF) either defined in IETF or OMA.
http://www.openmobilealliance.org/Technical/release_program/pde_v1_3.aspx

OMA Secure User Plane Location V2_0 AER
OMA Secure User Plane Location (SUPL) V2.0 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 User Profile Management V1_0 CER
OMA Service User Profile Management (SUPM) enabler provides a standardized interface to access and manage the data related to Service User Profile, that allow applications and/or enablers to create, read, update and delete specific data in order to support contextualization and personalization of the user’s services.
http://www.openmobilealliance.org/Technical/release_program/ServUserProf_v1_0.aspx

OMA User Agent Profile V1_1 AER
OMA User Profile (OMA UAProf) enables the end-to-end flow of a User Agent Profile (UAProf) between the device, the intermediate network points and the origin server ensuring that relevant device capability information is available for all necessary parties. Origin servers, gateways and proxies can then use the capability information to ensure that the user receives content that is particularly tailored for the intended environment.
http://www.openmobilealliance.org/Technical/release_program/uap_v11.aspx

Person-to-Person Communication

OMA Mobile Spam Reporting V1_0 CER
OMA Mobile Spam Reporting (SpamRep) enabler provides a mechanism for a Reporter to designate received content as “spam” and provide a report to a network entity. The scope of OMA SpamRep enabler includes only the SpamRep message format and the message transfer between the mobile device and network entity.
http://www.openmobilealliance.org/Technical/release_program/SpamRep_V1_0.aspx

OMA Multimedia Messaging Service V1_3 AER
OMA Multimedia Messaging Service (OMA MMS) V1.3 provides a rich set of content to subscribers using mobile messaging. OMA MMS supports both sending and receiving messages via properly enabled client devices. OMA MMS V1.3 builds upon the existing OMA MMS V1.2 specifications. Key features of OMA MMS include the ability to support messaging activities with other available messaging systems. 
http://www.openmobilealliance.org/Technical/release_program/mms_v1_3.aspx

OMA Mobile Email V1_0 CER
OMA Mobile Email (MEM) provides an improved user experience over alternate means of access to email including browsing, email notification or message / voice based access. OMA MEM provides 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 Presence Data Elements V1_2 ARR
OMA Presence Data V1.2 (PRS) reference release defines further Presence Information extensions and their mapping to the presence data model components and Presence Data Information Format extensions (PIDF) either defined in IETF or OMA.
http://www.openmobilealliance.org/Technical/release_program/pde_v1_2.aspx

OMA Push to Talk Over Cellular V2_0 CER (Figure 1)
OMA Push to Talk Over Cellular V2_0 CER (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, (one-to-one) 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 V2_1 CER (Figure 1)
OMA Push To Talk Over Cellular V2_1 CER (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.1 will allow audio (e.g. speech, music), video (without audio component), still image, text (formatted and non-formatted) and files shared with a single recipient, (one-to-one) 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.

OMA SIMPLE Instant Messaging V1_0 CER
OMA SIMPLE Instant Messaging (SIMPLE IM) provides a framework for service development and an application allowing near real-time exchanges of instant messaging between users on mobile and fixed connections. SIMPLE IM architecture relies on common OMA enablers such as Presence, XDM and Device Management Services to provide the overall functionality and support for server hosted and client hosted IM conversations. It also supports conferences and one-to-one modes of the IM service.
http://www.openmobilealliance.org/Technical/release_program/simple_im_v1_0.aspx

Access to Content

OMA Browsing V2_4 AER
OMA Browsing (Browsing) provides OMA browsing capability for mobile and wireless handheld devices and any necessary or optional supporting network services which may be provided on a gateway or proxy. The suite of specifications defining OMA Browsing defines the application-level protocols, semantics, syntax, content formats, user agent behavior and the use of hypermedia transfer protocols required to achieve consistent function and interoperability of services.
http://www.openmobilealliance.org/Technical/release_program/browsing_v24.aspx

OMA Browser Protocol Stack V2_1 AER (Figure 1)
OMA Browser Protocol Stack V2_1 AER (Figure 2)
OMA Browser Protocol Stack Enabler provides two protocol stacks for the integration of OMA services with underlying network bearers. At least one of these two stack architectures must be implemented in the client and server.
http://www.openmobilealliance.org/Technical/release_program/browser_protocol_v21.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 Digital Rights Management V2_2 CER
OMA Digital Rights Management (DRM) V2.2 specification enables content providers to grant permissions for media objects that define how they should be consumed. A content provider can grant appropriate permissions to the user for each of these media objects. OMA DRM V2.2 represents significantly improved security and functionality. Improved security is achieved by providing bilateral authorization between Rights Issuer and Device, based on PKI certificates and confidentiality and integrity protecting Rights Objects. Improved functionality and usability is achieved by providing preview functions, mechanisms for sharing of content within a registered community of devices, and by enabling devices without a wide-area network connection (unconnected devices) to par.
http://www.openmobilealliance.org/Technical/release_program/drm_v2_2.aspx

OMA Download Over the Air V2_0 AER
OMA Download Over the Air (DLOTA)V2.0 represents an evolution of OMA DLOTA 1.0, which provided a mechanism for user-initiated download of content, such as ring-tones, images and applications. OMA Download Over the Air V2.0 is backward compatible.

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 Game Services Client Server Interface V1_0 AER
OMA Games Services Client Server Interface (GS CSI) enables the interaction between the client and the server of game services in a standard manner. OMA GS CSI allows the initial Game Server System to be extended into a more comprehensive Game Server System.
http://www.openmobilealliance.org/Technical/release_program/gs-csi_V1_0.aspx

OMA In-Game Advertising V1_0 ARR
OMA In Game Advertising (IGA) provides requirements and architectural principles for game developer advertisement-related consideration. Key objectives of OMA's IGA are identifying related functionalities that enable models and a focus on game-ad specific use cases and functionalities not addressed by other OMA enablers. OMA’s IGA enabler covers in-game advertising models, ads handling in-game, best-practice and case for in-game advertising.
http://www.openmobilealliance.org/Technical/release_program/iga_v1_0.aspx

OMA LPP* Extensions V1_0 CER
OMA LPP Extensions (LPPe) build on the 3GPP-defined LPP and extends the location, measurement and assistance data capabilities beyond 3GPP LPP without unnecessarily duplicating the work done in 3GPP. The OMA LPPe Release 1.0 enables the following services: support for high accuracy GNSS methods in the form of new positioning methods and assistance data types, emerging radio network–based positioning technologies including the radio network measurement reports for selected radio access types and terminal-to-terminal positioning and assistance data transfer.
*LTE Positioning Protocol
http://www.openmobilealliance.org/Technical/release_program/LPPe_v1_0.aspx

OMA Mobile Augmented Reality V1.0 CER
OMA Mobile Augmented Reality (MobAR) defines an overall framework to enable mobile Augmented Reality (AR) services. The core functionalities exposed by the MobAR enabler include: personalization and management of AR Content, user interactivity handling to AR Content, network and client APIs, security and privacy aspects.
http://www.openmobilealliance.org/Technical/release_program/MobAr_v1_0.aspx

OMA Mobile Search Framework V1_0 CER
OMA Mobile Search Framework (MSrch Framework) defines a mobile search enabler providing several capabilities (such as Search Engine integration, selection, results Personalization) to support mobile search service. Search Engines are not in the scope of this enabler, however some requirements are identified for search engines to be integrated with the OMA MSrch Framework enabler in a standard way.
http://www.openmobilealliance.org/Technical/release_program/MSrchFramework_v1_0.aspx

OMA PUSH V2_1 AER
OMA Push (Push) allows 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_1.aspx

OMA Rich Media Environment V1_0 AER
OMA Rich Media Environment (RME) provides the language and transport mechanism that enables the distribution and display, on mobile devices, of rich media environment (RME) content. OMA RME defines flexible methods for accessing RME data. OMA RME will enable the creation of user friendly and compelling experiences, giving the user a richer experience when accessing services.
http://www.openmobilealliance.org/Technical/release_program/rme_v1_0.aspx

OMA Secure Removable Media V1_1 CER
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_1.aspx

OMA Service 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 SIP Push V1_0 CER
OMA SIP Push Enabler defines the protocol used to implement a SIP Push based service. A SIP Push based service allows a client to receive content in a communication initiated by the server, or ‘pushed' over the SIP/IP Core. The SIP Push Enabler provides analogous functionality such as Push Over the Air (OTA), using SIP as the underlying transport mechanism. For example, content is sent from the Push Initiator to the Push Proxy Gateway using the Push Access Protocol.
http://www.openmobilealliance.org/Technical/release_program/SIP_Push_v1_0.aspx

Service Access Interfaces

OMA External Functionality Interface V1_1 AER
OMA External Functionality Interface (EFI) defines the way components or entities with embedded applications, which execute outside the Wireless Application Environment [WAE] user agent, conform to the external functionality requirements. These external functionalities can be utilized via user agents such as OMA Browsing or other user agents. The external functionality may be built-in to, or connected to, a mobile terminal supporting these user agents and the connection can be permanent or temporary.
http://www.openmobilealliance.org/Technical/release_program/efi_v11.aspx

OMA Next Generation Service Interfaces V1_0 CER
OMA Next Generation Service Interfaces (NGSI) 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 and Registration and Discovery functions.
http://www.openmobilealliance.org/Technical/release_program/NGSI_v1_0.aspx

OMA Next Generation Service Interfaces – SOAP V1_0 CER
OMA SOAP Bindings for NGSI (OMA NGSI_S) aims to specify a first protocol binding choice for selected abstract NGSI interfaces. SOAP binding will comprehend with the style/design as given for the existing PSA v1.0. OMA NGSI SOAP comprehend Parlay-X with extensions for call control, conferencing and multimedia list handling. 
http://www.openmobilealliance.org/Technical/release_program/NGSI_S_V1_0.aspx

OMA PushREST V1_0 CRR
OMA RESTful Network API for OMA Push V1.0 (PushREST) enabler continues its support of the OMA Push v2.3 and defines an associated RESTful Network API that supports the Push Initiator (PI) ability to initiate the following operations to the Push Proxy Gateway (PPG): Push Submission, Push Submission with Replace, Push Cancellation, Status Query and Client Capabilities Query.
http://www.openmobilealliance.org/Technical/release_program/PushREST_v1_0.aspx

OMA RESTful bindings for Parlay X Web Services (ParlayREST) V2_0 CER
OMA RESTful bindings for Parlay X Web Services (OMA REST) specifies an HTTP protocol binding for a subset of Parlay X Web Services interfaces, using the REST architectural style. 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. OMA Parlay REST 1.0 defines REST protocol bindings for the following APIs: Short Messaging Service API, Multi Media Messaging Service API, Payment Service API and Terminal Location Service API. ParlayREST V2_0 inherits the REST protocol bindings from ParlayREST 1.0 (listed previously). Additionally, ParlayREST V2_0 defines REST protocol bindings for the following APIs: Presence Parlay X Web Services APIs, Address List Management Parlay X Web Services APIs, Call Notification Parlay X Web Services APIs, 3rd Party Call Parlay X Web Services APIs, Audio Ca, Parlay X Web Services APIs, Terminal Status Parlay X Web Services APIs and Device Capabilities Parlay X Web Services APIs.
http://www.openmobilealliance.org/Technical/release_program/parlayREST_v2_0.aspx

Return to Table of Contents


Download Japanese translation