OMA 2011 Newsletter Volume 4by OMA | Saturday, October 1, 2011
2011 Volume 4
Quarterly Technical Feature
With the end-of-year festivities a few weeks behind us, there is only one major piece of official business from last year that we need to wrap up—the 2011 Annual Release. I am very pleased to announce that in 2011 the OMA Technical Plenary completed and published nearly 60 Enabler Packages, that include technologies such as Smart Card Web Server, Data Synchronization, Push, and Secure User Plane Location. Additionally, OMA added new emerging technologies to its growing suite of enabler packages, including Mobile Augmented Reality and Converged Personal Network Services. Furthermore, we have welcomed new additions to the inventory of Application Programming Interfaces (APIs), including a number of RESTful Network APIs as well as the Device Management Client-Side API Framework.
This diverse range of enabler technologies, across many functional domains, underlines the important role that OMA plays in the standards landscape for the communications industry. I hope you will join me as I congratulate our technical working groups and our contributing member delegates on the many technical achievements and accomplishments as part of the 2011 Annual Release.
OMA Smart Card Web Server (OMA SCWS) provides static and dynamic web pages, allowing local communication (i.e. transactions) between the Smart Card Web Server and an HTTP based application (e.g. Web browser) running in the handset. This enables the implementation of a mobile operator’s services making them portable across handsets. OMA SCWS Enabler also facilitates the remote administration of the SCWS content using HTTP(s) protocol.
OMA SCWS V1.1 was approved in May 2009. OMA SCWS V1.2 reached Candidate status in April of 2011 and is expected to reach final approval in mid of October 2012. OMA SCWS V1.2 offers several enhancements that will benefit operators and users.
Benefits of OMA Smart Card Web Server for Operators and Mobile Users
Use Case 1: Quick and Simple Access to Network Operator Services
Via a regular handset browser, OMA SCWS portal gives the end-user a set of pages constituting menus that enable service discovery based on local content reachable immediately any time. This teaser, free of charge, provides access to remote content by setting up a call to a voice server, sending a SMS or opening a Mobile Internet session at a dedicated address.
Use Case 2: The Content Store
The mix between local and remote content is optimized to favor the on-line purchasing of music or other multimedia content. The OMA SCWS Visual-Content Store provides a local catalog of contents with a rich display. The end-user can preview and pre-listen before purchasing content. This Content Store can be periodically updated remotely thanks to the OMA SCWS remote administration protocol to reflect new content or a specific promotion—such as the top-ten of the most downloaded content of the week.
Please see the OMA Smart Card Web Server Work Program: http://www.openmobilealliance.org/Technical/release_program/scws_v1_2.aspx
The Open Mobile Alliance will hold its second HES Workshop during its February Meeting in Barcelona on Thursday 23 February. This full-day Workshop is intended to address some of the challenges to support person-to-person and rich multimedia communication services. Workshop participants include OMA member companies and a number of industry organizations currently involved in HES activities.
Home Environment Services opens up the possibility to offer services that are meaningful to a group of people in close proximity, even if those people are not connected to the same physical network or using the same operator. Home environment services are related to the concept of Home Networking, e.g. the service can be offered to run between devices in the home environment, or between devices in the home environment and devices outside the home.
OMA has created over 200 specifications since its inception in June 2002. 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 Releases (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.
Access to Content
This suite of OMA enablers allows access to digital content through multiple terminals so that the terminals become entertainment devices. These architectures and functionalities enable users to subscribe to, and/or be able to, receive multimedia content.
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.
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.
Architecture, Security and Charging
This suite of OMA enablers provides functions and tools for the support of services enabled by other OGSA suites. These enablers have different natures and include provisioning of parameters and services, data synchronization, service platform common architecture, interconnections and some other horizontal activities such as security, privacy or charging, etc.
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.
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.
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.
This suite of OMA enablers provides functions and tools related directly to the user experience on a terminal. These enablers may be used in conjunction with other OMA enablers for the support of additional services and applications outside of the device management enablers.
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.
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.
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.
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.
This suite of OMA enablers provides access to service resources within networks and their exposed functionality.
OMA Secure User Plane Location (SUPL) 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.
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.
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.
The following work items have been approved by the Technical Plenary and entered the OMA Work Program since October 2011:
WID – 253 Secure User Plane Location
26-28 March, Munich, Germany
Musa Unmehopa, Chair, Open Mobile Alliance Technical Plenary, Distinguished Member of Technical Staff in the Software, Services and Solutions Group, Alcatel-Lucent
30 October – 3 November, Halifax, Canada
Seth Newberry, General Manager, Open Mobile Alliance, OMA Overview and Current Work
17-18 November, Berlin, Germany
Musa Unmehopa, Chair, Open Mobile Alliance Technical Plenary, Distinguished Member of Technical Staff in the Software, Services and Solutions Group, Alcatel-Lucent, Introduction to Upcoming OMA M2M APIs
19-22 December 2011, Delhi, India
OMA Overview and Current Work
16-19 April, Ho Chi Minh City, Vietnam
9-12 July, Brooklyn, USA
17-20 September, Bangkok, Thailand
12-16 November, Los Angeles, USA
The OMA is proud to welcome the following new member who has joined recently. We look forward to their participation!
|Company||Membership Level||Company URL|