| Working Groups and Committees |
| Architecture | The OMA architecture Working Group is responsible for defining the overall OMA architecture, advising and assisting the architecture specification work in work groups and assuring, through review, adherence of specification work to OMA architecture... |
| Broadcasting | The Broadcasting Working Group(BCAST) will examine the needs of 'Mobile Broadcast Services' and the environments needed for their delivery... |
| Content Delivery | The Content Delivery Working Group (CD) refers to the delivery of information without the recipient having to request it. In the familiar web model, a client requests (pulls) content from a web server. With push, the server could deliver the content to the client without the client requesting it... |
Data Synchronization
| The Data Synchronization Working Group continues the work originated in the former SyncML Initiative. The group continues development of specifications for data synchronization, and the development of other similar specifications, including but not limited to SyncML technology... |
Developers Interest Group (closed)
| The Developers Interest Working Group collects and publishes data relevant to developers, provides a means for software developers to articulate and specify their needs to OMA and identifies missing or inconsistent developer interfaces.. |
Device Management
| The Device Management Working Group defines management protocols and mechanisms that enable robust management of the life cycle of the device and its applications over a variety of bearers. The Device Management Working Group continues the work previously conducted in the former WAP Forum and SyncML initiatives.... |
| Digital Rights Management | The goal of the Digital Rights Management (DRM) Working Group is to specify application level protocols and behaviors that provide transactional and life cycle management of content and applications on mobile devices... |
Games Services
| The Games Services Working Group continues the work of the Mobile Games Interoperability Forum (MGIF). The Games Services group is responsible for developing interoperability specifications, APIs and protocols for network enabled gaming, as well as, enabling game developers to develop and deploy mobile games to efficiently interoperate with OMA platforms and enable cost reduction for game developers, game platform owners and service providers... |
Interoperability
| The OMA Interoperability (IOP) Working Group acts as a center of excellence to identify, specify and maintain the required processes, policies and test programs for ensuring interoperability for OMA specified enablers and end-to-end services... |
Location
| The OMA Location Working Group continues the work originated in the Location Interoperability Forum (LIF). This group develops specifications to ensure interoperability of Mobile Location Services on an end-to-end basis... |
| Messaging | The OMA Messaging Working Group is responsible for the specification of messaging and related enabling technologies. The goal of Messaging Working Group is to specify a set of basic messaging features that may be used to enable specific messaging paradigms... |
Mobile Commerce & Charging
| The MCC is specifying a charging enabler to support the existing and emerging OMA enablers. This charging enabler defines the functions, and interfaces for the information flow from OMA enablers, applications and services into an underlying charging system. |
| Mobile Client Environment (MCE) | The Mobile Client Environment Working Group is responsible for the specification of application technologies used in the open mobile architecture... |
| Presence & Availability | The Presence and Availability Working Group has the goals of specifying the service enablers to permit the deployment of interoperable mobile presence and availability services. Presence and availability services enable applications to exchange dynamic information (e.g. status, location, and capabilities) about resources (e.g. users and devices) |
| Push to Talk Over Cellular | The Push to talk over Cellular (PoC) WG is positioned to develop application enabling specifications to permit the deployment of interoperable PoC services. The initial work of the Working Group will be |
| Release and Planning Management | The OMA Release Planning and Management Committee is a committee of the OMA Technical Plenary responsible for planning and managing OMA Releases, defining OMA Releases based on OMA specifications and Interoperability Testing programmes, and defines the Release planning process... |
| Requirements | The OMA Requirements Working Group specifies and identifies interoperability and usability requirements within OMA Working Groups... |
| Security | The OMA Security Working Group develops secure communication protocols between mobile clients and servers at transport and application layers, security and trust services provided by/to mobile clients and servers... |