OMA Quarterly
2010 Volume 2
Table of Contents
Quarterly Technology Feature — OMA’s AII-IP Activities
OMA Board Approves Reduced Fee for Sponsor Membership
Quarterly Feature on Industry Cooperation — OMA and GSMA’s OneAPI
2010 OMA Technical Plenary Elections
Current OMA Work Program
Quarterly Technical Achievements
New Work Items
Events Calendar
Upcoming 2010 Industry Events
2010 OMA Meetings
Membership
New Members
Quarterly Technical Feature
OMA Finds Early Relevance in Support of All-IP Network Environments
In October 2009, the OMA Board of Directors undertook an initiative to help ensure market readiness for a variety of Evolved Mobile All-IP systems and networks. OMA continues its ongoing commitment to delivering market relevant service enablers that best fit into a large variety of underlying networks. This now demonstrates significant promise for All-IP, including LTE deployment scenarios.
OMA’s All-IP architecture and concepts are designed for efficient support of mass-market usage of any IP-based service. All-IP technology offers increased speed and unlimited, always-on mobile data services, bringing wireless access with the same connectivity level as existing fixed network IP solutions. This will offer users seamless mobility between fixed and mobile environments. OMA has been committed to specifications that are relevant in fixed network environments since 2005.
Now, OMA’s “All-IP Ready” enablers will be available not only for mobile phones, but also notebooks, ultra-portables, cameras, camcorders and other network connected devices. OMA has extended its relevance to these different environments by supporting different transport bindings. Some of the service scenarios that would benefit from All-IP networks might include:
• Service customization
• Enhanced content and entertainment consumption
• Enhanced communication tools
• Multiplay
• On line advertising for new services
• Switching content between different devices including fixed terminals
OMA has already identified many of its enablers as the facilitators for optimizing delivery of service events. This enables device context awareness and contextually adaptive service delivery, as well as programmable content delivery services—a key value in “traffic shaping.”
Other OMA enablers that will provide users with a more engaging communication experience when used in an All-IP network include: Converged Address Book, Converged IP Messaging, Instant Messaging and Presence. These enablers are the primary components of the Rich Communications Suite (RCS), currently being specified by the GSMA. .
OMA has verified the following enablers as “All-IP Ready.”
• OMA Push:
http://www.openmobilealliance.org/Technical/release_program/push_v2_2.aspx
• OMA Device Profiles Evolution:
http://www.openmobilealliance.org/Technical/release_program/dpe_V1_0.aspx
• OMA Dynamic Content Delivery:
http://www.openmobilealliance.org/Technical/Release_program/dcd_v1_0.aspx
• OMA Device Management Enabler
http://www.openmobilealliance.org/Technical/release_program/dm_v1_3.aspx
• OMA Presence Simple:
http://www.openmobilealliance.org/Technical/release_program/Presence_simple_V2_0.aspx
• OMA XML Document Management:
http://www.openmobilealliance.org/Technical/release_program/xdm_v2_0.aspx
• OMA Simple IM:
http://www.openmobilealliance.org/Technical/release_program/simple_im_v1_0.aspx
• OMA Parlay Service Access
http://www.openmobilealliance.org/Technical/release_program/psa_V1_0.aspx
• OMA RESTful Bindings for Parlay X Web Services
http://www.openmobilealliance.org/Technical/release_program/parlayREST_v1_0.aspx
Return to Table of Contents
OMA Board Approves Reduced Fee for Sponsor Membership
The Board of Directors approved a reduction in the Sponsor fee to $85,000, effective January 15, 2011. This means that all Sponsor members will be able to renew their membership in 2011 at the reduced fee. This also means that Full members have the opportunity to upgrade their membership at the reduced fee. Since early 2009, the Board has been active in setting new technical priorities for OMA, including Developer API’s and M2M communications. The new pricing makes participation in the defining process more affordable to interested companies.
Return to Table of Contents
Quarterly Industry Cooperation Feature
Use of OMA in GSMA OneAPI Promises New Markets Where OMA Enablers Can Be Deployed
GSMA’s OneAPI offers a set of APIs that expose network capabilities over HTTP. The project has been developed publicly and is based upon existing Web standards and principles. GSMA OneAPI is a profile (i.e. subset) of OMA ParlayREST V1_0. OMA PXPROF (OneAPI Profile of the Parlay X SOAP Web Services) defines this profile/subset, which is supported by GSMA OneAPI.
The scope of the OMA ParlayREST 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.
The OMA PXPROF enabler uses a tabular convention to define the subset of OMA ParlayREST v1 that is supported by GSMA OneAPI v1.
• Short Message Service (SMS) API – The profile supports sending and receiving SMS messages, as well as notifications of SMS delivery. The profile does not support scheduled delivery of SMS, or other SMS types like SMS Logo and SMS Ringtone, which are a part of the full OMA Parlay REST Enabler.
• Multimedia Messing Service (MMS) API – Similarly, the profile supports sending and receiving of MMS messages, as well as notifications of MMS delivery. Again, the profile does not support scheduled delivery of messages as with OMA Parlay REST.
• Payment API – The profile supports direct charges as well as reservations for amount. The profile does not support volume charging as with OMA Parlay REST.
• Terminal Location API – The profile supports querying the location for one or more terminals. The profile does not support location notifications, or querying the distance between terminals or between a terminal and a fixed location as with OMA Parlay REST.
The OMA Reference Release Package for OneAPI Profile of the Parlay X SOAP Web Services (PXPROF) was approved by OMA in April 2010 and is now publicly available at the following URL: http://www.openmobilealliance.org/Technical/release_program/pxprof_v1_0.aspx
Return to Table of Contents
2010 OMA Technical Plenary Elections
Working Group Chair Elections
Interoperability: Martin Niekus, Alcatel-Lucent
Digital Rights Management: Sergey Seleznev, Samsung
Working Group Vice-Chair Elections
Location: Andreas Wachter, Qualcomm
Architecture: Liliana Dinale, Ericsson
Device Management: Axel Ferrazzini, RIM
Return to Table of Contents
Current OMA Work Program
Quarterly Technical Achievements
To date, OMA has published over 50 Enabler Releases. 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 Approved Enabler Releases (AER)
An OMA Approved Enabler Release represents Candidate Enabler Releases that have gone through the Interoperability Program (IOP) of OMA. The IOP tests interoperability between different member company's 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. The IOP tests interoperability between different member company's implementations—either within the OMA or through other means.
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.
*Please note. Graphics of basic architecture for OMA Enablers are available by rolling your cursor over the title of the enabler.
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 RESTful bindings for Parlay X Web Services V1_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 specifications in OMA, using the REST architectural style. These REST bindings are defined for abstract API definitions from existing OMA enablers. 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 Parlay X Web Services, Multi Media Messaging Parlay X Web Services, Payment Parlay X Web Services and Terminal Location Parlay X Web Services.
http://www.openmobilealliance.org/Technical/release_program/parlayREST_v_0.aspx
OMA Push V2_3 CER
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 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 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 Digital Rights Management V2_1_1 CER
The OMA DRM V2 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 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_1_1.aspx
OMA Mobile Advertising V1_0 CER
OMA Mobile Advertising enabler (MobAd) will specify mechanisms related to user profiles and context as well as mechanisms related to the associated content. Content providers, advertisers and operators will be able to personalise and contextualise advertisements to be sent to a specific type of user. OMA's MobAd will support interactivity, so users can interact with advertisements and other content. The standard will also specify how to ‘use' interactive advertisements to help users interact with advertisers and content. The specification will enable metrics and data collection, including mechanisms to achieve accurate measurement of advertising campaigns based on user behavior.
http://www.openmobilealliance.org/Technical/release_program/mobad_v1_0.aspx
OMA SIMPLE Instant Messaging V1_0 CER
OMA Simple Instant Messaging (SIMPLE IM) provides a framework for future 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
OMA SIP Push V1.0 CER
OMA SIP Push Enabler defines the protocol used to implement a SIP Pushbased service. A SIP Push based service allows a client to receivecontent in a communication initiated by the server, or ‘pushed' overthe SIP/IP Core. The SIP Push Enabler provides analogous functionalitysuch as Push Over the Air (OTA), using SIP as the underlying transportmechanism. For example, content is sent from the Push Initiator to thePush Proxy Gateway using the Push Access Protocol
http://www.openmobilealliance.org/Preview/Technical/release_program/SIP_Push_v1_0.aspx
OMA Global Service Architecture V1_0 CER
The OMA Global Service Architecture (OGSA) defines an overall service architectural view of OMA Enablers leveraging the OSE. OGSA positions the OMA enablers in OGSA Suite(s) to facilitate the justification for and representation for Enablers (not just individually but in a wider context), helps operators and external entities understand and leverage OMA Enablers and represents a re-usable set of enablers and exposed interfaces that illustrate modularity.
http://www.openmobilealliance.org/Technical/release_program/ogsa_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_0.aspx
OMA Diagnostic Monitoring V1_1 CER
OMA Diagnostics and Monitoring(DiagMon) Enabler manages distributed, mobile wireless devices, inorder 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.
OMA Device Management V1.3 CER
OMA Device Management 1.3 (OMA DM 1.3) represents an expansion of OMA DM 1.2. OMA DM 1.3 supports the following additional functionalities: support for SIP/UDP transport bindings, specify for mandatory support for bootstrap/TNDS, support for rich information in notification message including expiration, reason for session, etc. and support for the discovery of optional DM features supported by the DM Client.
OMA Parlay Service Access V1_0 ARR
The aim of OMA Parlay Service Access (PSA) is to address (per OMA processes) those GPP Release 8 requirements for which no technical work has been done in GPP 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
OMA Browser Management Object V1_0 ARR
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 Client-Side Enabler API V1_0 CRR
The OMA Client-Side Enabler API (CSEA) enabler will define a set of Javascript API’s to be made available for Web applications running in browser or widget context web runtime environments.
http://www.openmobilealliance.org/Technical/release_program/csea_v1_0.aspx
Return to Table of Contents
New Work Items
The following work items have been approved by the Board of Directors and entered the OMA Work Program since April 2010:
W0199 RESTful bindings for Parlay X Web Services
http://member.openmobilealliance.org/ftp/Public_documents/TP/Permanent_documents/OMA-WID_0199-ParlayREST2-V1_0-20100406-A.zip
W0200 DM Gateway Management Object 1.0
http://member.openmobilealliance.org/ftp/Public_documents/TP/Permanent_documents/OMA-WID_0200-GwMO-V1_0-20100407-A.zip
W0201 Software Component Management Object v 1.1
http://member.openmobilealliance.org/ftp/Public_documents/TP/Permanent_documents/OMA-WID_0201-SCOMO-V1_1-20100504-A.zip
W0204 Diagnostics & Monitoring
http://member.openmobilealliance.org/ftp/Public_documents/TP/Permanent_documents/OMA-WID_0204-DiagMon-V1_2-20100401-D.zip
Return to Table of Contents
Events Calendar
Upcoming 2010 Industry Events
Global Standards Collaboration, GSC-15
30 August – 2 September, Beijing, PRC
MDM and Telco Service Development Congress 2010
20-21 September, Berlin, Germany
Event organizers can contact Bobby Fraher to invite an OMA contribution for an upcoming event.
2010 OMA Meetings
29 August - 3 September, Budapest, Hungary
14 - 19 November, Seoul, ROK
Return to Table of Contents
Membership
New Members
The OMA is proud to welcome the following new members who have joined recently. We look forward to their participation!
Return to Table of Contents
| 
