The OMA architecture Working Group is responsible for defining the overall OMA architecture, advising and assisting the architecture specificat ion work in work groups and assuring, through review, adherence of specification work to OMA architecture… (including Mobile Commerce and Charging, Security).

The OMA Communications (COM) Working Group is responsible for the specification of messaging and related enabling technologies. The goal of COM Working Group is to specify a set of basic messaging features that may be used to enable specific messaging paradigms… (including Push to talk over Cellular (PoC).

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…
(including the Mobile Client Environment, Games Services).

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….

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…

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…

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…