OMA Quarterly
2009 Volume 3Contents
Intended for distribution to OMA members, external organizations that hold formal relationships with OMA, as well as OMA's contacts in the media and analyst community, this is a public newsletter. Please pass it along to anyone you believe to be interested. In addition to a comprehensive list of all technical work published since the last newsletter, the content is meant to meet the needs of readers and feedback is welcome.
Please submit your feedback to OMA Director of Communications, Stephen Jones.
Please also indicate to Stephen Jones if you wish NOT to receive this newsletter in the future.
OMA Considers Support for Service Deployment in Evolved Mobile All IP System
Quarterly Technical AchievementsNew Work Items
Events Calendar
New Members
OMA Considers Support for Service
Deployment in Evolved Mobile All IP Systems
An OMA Board workshop in Los Angeles reviewed the mission and deliverables of the OMA. One outcome from the review is that the OMA Board of Directors has issued a call to action for all OMA members. This request will help OMA to develop a work program that can best support the deployment of services using various IP based platforms and technologies in its current and future activities.
In order to leverage spectral efficiency, increased data rates and low latency of LTE, SAE, WCDMA and WiMAX, OMA will consider the characteristics associated with these new high capacity networks. Some examples of these characteristics include non-SMS based platforms, All IP protocols and no circuit switches. With the convergence of IP, existing telecoms and mobile networks, the OMA Board has identified the industry's need to quickly and efficiently deploy higher bandwidth applications and services using OMA Enablers.
In a follow on workshop in February 2010, OMA members and the OMA Technical Plenary will prepare a series of presentations and discussions to identify how existing and new OMA Service Enablers can support the deployment of mobile data services using different Evolved Mobile All IP Systems. Intended for inclusion in new and innovative OMA Enablers, as well as relevant existing OMA Enablers such as OMA Push and OMA Converged IP Messaging, support for new service deployments using these evolved systems will begin in 2010.
Back to top
Quarterly Technical Achievements
OMA Work Program Structure and Hierarchy
Back to top
Working Group Chair and Vice Chairs Elections
Working Group Chair Elections
Release Planning & Management: Peter Arnby, Ericsson
Working Group Vice-Chair Elections
Messaging: Mike Parsel, Sprint
Architecture: Duan Xiang, China Mobile
Back to top
Current OMA Work Program
To date, OMA has published over 45 Enabler Releases. Using a clear working process, the Enabler Release Program is designed to deliver three key milestones for each enabler:
OMA Candidate Enabler Releases
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 Push V2_2
OMA Push (Push) allowing 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.
OMA Mobile E-mail V1_0
The OMA Mobile Email (MEM) enabler provides an improved user experience over alternate means of access to email including browsing, email notification or message / voice based access. The goal of the MEM Enabler is to provide 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 Device Capability Management Object V1_0
The OMA Device Management Capabilities Management Object (DCMO) enabler 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 the DC. The device capability information will be exposed by DCMO to facilitate management of the device capability components.
http://www.openmobilealliance.org/Technical/release_program/dcmo_v1_0.aspx
OMA Software Component Management Object V1_0
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
OMA Device Profile Evolution V1_0
The 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 XML Document Management V2_0
The OMA XML Document Management (XDM) enables the storage of user-specific information in the network, which is managed by authorized principals and accessed by service enablers that require this information. XDM specifies how such information will be defined in XML documents, as well as the common protocol for access and manipulation of such XML documents.
http://www.openmobilealliance.org/Technical/release_program/xdm_v2_0.aspx
OMA Location in SIP/IP Core V1_0
The OMA Location in SIP/IP core network (OMA LOCSIP) provides a SIP based interface to expose the location information of selected targets. The location information may be processed and utilized by other applications or services in the SIP/IP core network such as a Presence SIP Application server or a PoC Server to enrich the end user experience.
http://www.openmobilealliance.org/Technical/release_program/locsip_v1_0.aspx
OMA Charging V1_1
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_v1_1.aspx
OMA SyncML Common V1_2_2
The OMA SyncML representation protocol is defined by a set of messages conveyed between entities participating in a SyncML operation. The messages are represented as an XML document. OMA SyncML defines the logical structure and format of various SyncML messages which are used by Data Services and Device Management. The SyncML representation protocol supports protocol models that are based on a request/response command structure, as well as those that are based on a 'blind push' command structure.
http://www.openmobilealliance.org/Technical/release_program/SyncML_v1_2_2.aspx OMA Lock and Wipe Management Object V1_0
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 Policy Evaluation, Enforcement & Management V1_0
OMA Policy Evaluation, Enforcement & Management (PEEM), reduces management complexity while introducing consistent new subscriber services with the same or reduced time to market. PEEM enables the delegation of responsibility to other resources to help avoid the costly duplication of functionality across service enablers. PEEM also reduces the proliferation of ‘silos' in service provider domains.
http://www.openmobilealliance.org/Technical/Release_program/peem_v1_0.aspx
OMA Global Permissions Management V1_0
The Global Permissions Management (GPM) enabler provides generic permissions checking and permissions management, which can be used by other resources. The role of the GPM enabler is to specify how authorized principals are managing the permission rules that determine if, when, how and to what extent information about end-users (i.e. Permissions Target) is released to Target Attribute Requesters and Consumers, (e.g. applications, enablers or other end-users), and to specify how permissions checking requests for release of information are defined and processed.
http://www.openmobilealliance.org/Technical/release_program/gpm_v1_0.aspx
OMA Categorization Based Content Screening V1_0
OMA Categorization Based Content Screening (CBCS) enabler screens content before delivering it to the user, based on content categories. CBCS can obtain the content category for a given piece of content from a categorization entity, categorization meta-data in the content itself or by analyzing the content. CBCS allows any unauthorized 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 Secure Content Exchange V1_0
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 Look and Feel Customization V1_0 (Figure 1)
(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 screen, status indicators, fonts and menus.
http://www.openmobilealliance.org/Technical/release_program/CBUS_V1_0.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.
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 Back to topCandidate Reference Releases
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 Service Provider Environment V1_0
OMA Service Provider Environment (OSPE) enabler reduces deployment and lifecycle costs, improves service/component time-to-market challenges, allows component interchangeability (one vendor to another), allows the multi-vendor mixing-and-matching of components, provides run-time end-to-end diagnostics within and across domains/environments to improve services consistency and coherency.
Back to top
OMA Approved Enabler Releases
An Approved Enabler Release represents a Candidate Enabler Release 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 Firmware Update Management Object V1_0_4
OMA Firmware Update Management Object (FUMO) enables firmware updates by specifying the locations in the management tree where update packages could be downloaded. It also specifies commands that need to be invoked on specific nodes of the management tree to start an update activity.
http://www.openmobilealliance.org/Technical/release_program/fumo_v1_0.aspx
OMA Client Provisioning V1_1 AER
http://www.openmobilealliance.org/Technical/release_program/cp_v1_1.aspx
Back to top
New Work Items
The following work items have been approved by the Board of Directors and entered the OMA Work Program since June 2009:
WID187 - OMA Global Service Architecture V1_1
http://member.openmobilealliance.org/ftp/Public_documents/TP/Permanent_documents/OMA-WID_0187-OGSA-V1_1-20090526-A.zip
WID190 - OneAPI Profile of the Parlay X SOAP Web Services
http://member.openmobilealliance.org/ftp/Public_documents/TP/Permanent_documents/OMA-WID_0190-PXPROF-V1_0-20090818-A.zip
The following Work Items are under consideration by the OMA Technical Plenary:
WID188 - Presence Data Elements 1_1
http://member.openmobilealliance.org/ftp/Public_documents/TP/Permanent_documents/OMA-WID_0188-PDE_1_1-V1_0-20090424-D.zip
WID189 - Digital Rights Management V2.2
http://member.openmobilealliance.org/ftp/Public_documents/TP/Permanent_documents/OMA-WID_0189-DRMv2_2-V1_0-20090617-D.zip
WID192 - Key Performance Indicators (KPIs) for OMA Enablers
http://member.openmobilealliance.org/ftp/Public_documents/TP/Permanent_documents/OMA-WID_0192-KPIinOMA-V1_0-20090819-D.zip
WID193 - Software and Application Control Management Object
http://member.openmobilealliance.org/ftp/Public_documents/TP/Permanent_documents/OMA-WID_0193-SACMO-V1_0-20090824-D.zip
*For a full list of OMA Working Groups and links to current work items in the OMA Work Program, please visithttp://www.openmobilealliance.org/Technical/WorkingGroupsCommitees.aspx Back to top
Events Calendar
Recent 2009 Industry Events
Global Standards Collaborations, GSC-14
13-16 July Geneva, Switzerland
Fred Harrison, Chairman, OMA
OMA Work and Pipeline5th Annual Mobile Device Management and Security Forum
21-23 November, Berlin, Germany
Friedhelm Rodermund, Vice-Chair, Device Management Working Group, OMA
OMA Device Management and Platforms ICIN 2009
26-29 October, Bordeaux, France
2009 ICIN OMA Presentation
Upcoming 2009 Industry Events
5th International FOKUS IMS Workshop
11-12 November, Berlin, Germany
Event organizers can contact Bobby Fraher to invite an OMA contribution for an upcoming event.
OMA Member Company Benefits at industry events
OMA member companies often receive a substantial discount on the event registration fees when the OMA participates at an event. This discount applies to all employees of OMA member companies, not just to OMA delegates/participants. Registration discounts typically range from 10%-20% depending on the event. To take advantage of these opportunities, please contact Bobby Fraher.
2009 OMA Meetings
• 18-23 October, Los Angeles, USA
2010 OMA Meetings
• 31 January - 4 February, EUROPE
• 11 - 16 April, Bangkok, Thailand
• 27 June - 1 July, Las Vegas, USA
• 29 August - 3 September, EUROPE
• 14 - 18 November, ASIA
Back to top
New Members
The OMA is proud to welcome the following new members who have joined recently. We look forward to their participation!
Who Participates in OMA
OMA members facilitate global user adoption of mobile data services by specifying market driven mobile service enablers. There are more than 200 members of the OMA. These members represent the end-to-end value chain of mobile products and services around the world. Device manufacturers, mobile operators, IT companies and content providers are all participating members of the OMA. A full list of benefits of OMA membership along with information on how to join can be found at http://www.openmobilealliance.org/Membership/default.aspx.
Back to top
|
|