OMA 2011 Newsletter Volume 3by OMA | Friday, July 1, 2011
2011 Volume 3
OMA officially launched its API program in late September and early October, with an invited presentation and a panel session at the Service Delivery Platform Global Summit, and the opening keynote at the ICIN Conference. These events were accompanied by a press release in which 30 OMA member companies publically endorsed OMA’s work in specifying APIs to enable operators and other service providers to expose existing network capabilities to as wide a variety of developers as possible. These endorsing member companies represent a wide spectrum of industry players, including operators, equipment manufacturers, and software vendors from all geographies across the globe. I am very pleased with this very strong signal of industry support!
The launch marked the availability of API specifications for more than 40 network and device resources, with various language and protocol bindings. It was an excellent opportunity to share OMA’s perspective on the fragmented landscape of available proprietary APIs, and to validate our strategic direction which promotes standardization to allow service providers to increase their developer base, reduce time-to-market for new applications and services, and simplify wider deployment of existing applications and services.
Our strategic messages, as well as our return to the public debate, were very well received by the industry participants at these events, which included media and analysts. The problem of fragmentation and lack of interoperability is widely recognized and OMA’s lead role in this space was acknowledged. There were also critical questions, about the timeliness and relevance of standards.
To address the particular point of relevance of standards, I will re-iterate the key problem that OMA aims to address. As the number of APIs that perform the same functionality proliferate, fragmentation occurs. This limits developer access to subscribers, and operator and service providers’ choices of development platforms and communities. This model does not scale and fails to fulfill the market potential as identified by various analyst firms. Through standardization, OMA offers a solution to the industry’s problem of fragmentation and lack of interoperability. Through its fast track processes, OMA has reduced the standards development cycle for APIs by more than 50%, with the typical API specification taking nine months from inception to publication.
Collecting critical feedback as well as industry validation for our work is vital in making sure we address the right market requirements. Not just in the area of APIs, but for standardization in the service and application layer in general. OMA must continue to participate in the industry debate, offering a leading voice for standardization. This is our chance to demonstrate we deliver technology that the market needs, and that our fast track process is bearing fruits.
I hope that you will enjoy reading this newsletter, and find the content both stimulating and engaging. Please share with your colleagues and business partners. Go out there any use our standards, and let us know what you think!
The following companies endorse OMA’s work in specifying APIs to enable operators and other service providers to expose their network capabilities to as wide a variety of developers as possible. As the Information and Communication Technology (ICT) industry deploys the next round of advanced services, many of these services require access to core network capabilities, common across all operators globally. These OMA member companies have publicly endorsed OMA’s standardized approach to offer access to core network capabilities. The OMA API program creates global API standards that expose these crucial capabilities in an open and programmable way.
|• Aepona• Alcatel-Lucent
• Bell Mobility
• Birdstep Technology
• Cambridge Silicon Radio, Ltd
• China Mobile
• China Unicom
• China Telecom
|• Deutsche Telekom AG• Ericsson
• GSM Association (GSMA)
• Hansol Inticube
• Huawei Technologies
• Interop Technologies
• NEC Corporation
• Nokia Siemens Networks
|• Oracle• Orange SA
• Red Bend Software
• Smith Micro Software,Inc.
• Songdo Telecom, Inc.
• Telecom Itália
• Telenor ASA
• U.S. Cellular
• ZTE Corporation
During the 2011 OMA Annual General Meeting in November in Beijing, OMA, and China Communications Standard Association (CCSA) will host a series of events for both the Chinese public and OMA members.
The event, Innovating New Services Across the Network of Everything – The Role of Standards in a Hyper Connected World will take place on 9 November throughout the course of the day.
Highlights of the day’s event include:
- Presentations from five Chinese company featuring relevant information about the Chinese Mobile Industry and the evolution of the Chinese market and its growing relevance around the globe
- Live technology demonstrations from Chinese start-up companies sponsored by Research Institute of Telecommunications Transmission (RITT)
- An Overview of OMA’s Machine to Machine Communication (M2M) and API work programs from Musa Unmehopa, Chair, OMA Technical Plenary
This event offers a unique opportunity for attendees to learn about specific technical work of the OMA and to see excellent examples of real world product deployments as well as future work of the OMA Technical Work Program. The OMA technical program currently has over 100 work items in development, and the OMA Board of Directors welcomes the participation of the wider Chinese mobile industry to this event.
*OMA members do not need to register to attend this meeting. You are automatically registered if you are attending the OMA Meeting.
Two dimensional (2D) and one dimensional (1D or linear) barcodes are an optical, machine-readable representation of encoded data containing digital content. Examples might include an URL, business card contact information, or a link to more elaborate information such as, coupons, product details and advertising promotions. Camera-equipped devices can now easily read a variety of barcodes using interpretive software (‘barcode scanner app’). This capability may be pre-loaded by the manufacturer or downloaded to devices after purchase. OMA Mobile Codes (MC) Enabler V1.0 currently covers 2D mobile barcodes using both Direct and Indirect methods; the MC Client performs functions including the barcode scanner app.
Mobile barcodes greatly simplify how users retrieve digital content while browsing casually – without entering URL information. Businesses will have a powerful new tool for mobile marketing that is ripe for creative use cases.
Example: Delivery Cost Calculation
The Code Publisher (generic company, online merchant) has set up an app with the postal service that automatically calculates the shipping cost for an item based on particulars of the item associated with the barcode. Step 1- The shopper scans the product barcode in an ad. Step 2- Total cost of the item is presented including shipping charges to his home zip code at different priority delivery levels. Step 3- Shopper selects the shipping method and completes the ordering and payment process.
*Please see OMA Mobile Codes Work Program: http://www.openmobilealliance.org/Technical/release_program/MobileCodes_v1_0.aspx
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 Content Management Interface V1_0 CER
OMA Content Management Interface (CMI) enabler supports the content management needs of service providers including network operators, web portal service providers, and content providers as they deliver content-related services. The CMI enabler supports the deployment of services that depend upon such interactions via a standardized set of functions and interfaces, improving service deployment flexibility, interoperability, cost, and time-to-market. This will further enable consistent deployment of services using a variety of models for supplying content, including ‘on-deck’ and ‘off-deck’.
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.
OMA LPP Extensions (LPPe) build on the 3GPP-defined LPP and extends the location, measurement and assistance data capabilities beyond 3GPP LPP without unnecessarily duplicating the work done in 3GPP. The OMA LPPe Release 1.0 enables the following services: support for high accuracy GNSS methods in the form of new positioning methods and assistance data types, emerging radio network–based positioning technologies including the radio network measurement reports for selected radio access types and terminal-to-terminal positioning and assistance data transfer.
*LTE Positioning Protocol
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.
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.
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.
OMA SIP Push Enabler defines the protocol used to implement a SIP Push based service. A SIP Push based service allows a client to receive content in a communication initiated by the server, or ‘pushed’ over the SIP/IP Core. The SIP Push Enabler provides analogous functionality such as Push Over the Air (OTA), using SIP as the underlying transport mechanism. For example, content is sent from the Push Initiator to the Push Proxy Gateway using the Push Access Protocol.
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.
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 Data Synchronization (DS) reduces traffic, improves security, introduces real-time synchronization, adjusts OMA DS based email synchronization and improves readability and interoperability.
OMA Device Capabilities Management Object (DCMO) allows control of device features such as Bluetooth, WiFi access and the camera; and 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 certain features and capabilities. The basic features and capabilities of the device will be exposed by DCMO to facilitate management of the components.
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.
OMA DM Scheduling (Sched) enabler specifies the Device Management Scheduling Framework and corresponding Management Objects that can be layered on top of the OMA DM v1.2 to add seamlessly the common scheduling functionality to existing management infrastructure.
OMA Software and Application Control Management Object (SACMO), enables remote operations for software and application control in the device. Software and application control management specifications will provide capabilities of processing management actions such as workflow, processing or on device management of software and applications utilizing existing management objects.
Person to Person
This suite of OMA enablers represents messaging and other communications means in various forms. Fundamentally, these enablers facilitate or encourage communication among users.
OMA Mobile Email (MEM) provides an improved user experience over alternate means of access to email including browsing, email notification or message / voice based access. OMA MEM provides 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.
OMA Push to Talk Over Cellular V2_0 CER (Figure 2)
OMA Push To Talk Over Cellular (PoC) is intended to provide rapid communications for business and consumer customers of mobile networks. OMA’s PoC V2.0 will allow audio (e.g. speech, music), video (without audio component), still image, text (formatted and non-formatted) and file shared with a single recipient, (one-to-one) or between groups of recipients as in a group chat session. OMA PoC seeks interoperability among the network entities to avoid market fragmentation, by realizing the PoC service in a widely acceptable and standardized manner.
OMA Push To Talk Over Cellular (PoC) is intended to provide rapid communications for business and consumer customers of mobile networks. OMA’s PoC V2.1 will allow audio (e.g. speech, music), video (without audio component), still image, text (formatted and non-formatted) and files shared with a single recipient, (one-to-one) or between groups of recipients as in a group chat session. OMA PoC seeks interoperability among the network entities to avoid market fragmentation, by realizing the PoC service in a widely acceptable and standardized manner.
PoC V2.1 defines new functionalities beyond Push To Talk Over Cellular (PoC) service extending the PoC V1.0 service including PoC Sessions with multiple PoC Groups, Browser based PoC Client Invocation, Dispatcher function and requests with other media types such as video, images, text and files.
Services Access Interface
This suite of OMA enablers includes enablers that facilitate the exposure of functionality in a secure and controlled way. Such exposure may occur towards other OMA enablers or to third party services, applications and specifications.
OMA PushREST V1_0 CRR
OMA RESTful Network API for OMA Push V1.0 (PushREST) enabler continues its support of the OMA Push v2.3 and defines an associated RESTful Network API that supports the Push Initiator (PI) ability to initiate the following operations to the Push Proxy Gateway (PPG): Push Submission, Push Submission with Replace, Push Cancellation, Status Query and Client Capabilities Query.
This suite of OMA enablers provides access to service resources within networks and their exposed functionality.
OMA Condition Based URIs Selection (CBUS) enabler is a common standard solution to fulfill the functionality requirements of OMA PoC service. OMA CBUS supports the retrieval of a list of addresses and makes them available for messaging, gaming, conferencing and advertisement services. The CBUS Enabler is a common standard solution to fulfill the functionality requirements of OMA PoC service.
The OMA Mobile Location Service (MLS) V1.0 consists of a set of location specifications complying with 3GPP Release 6 LCS Specification. OMA MLS V1.0 is primarily intended for use in a 3GPP environment. The set of specifications in MLS V1.0 consist of OMA Mobile Location Protocol (MLP) V3.2 and OMA Roaming Location Protocol (RLP) V1.0.
The OMA Mobile Location Service V1.1 (MLS V1.1) consists of a set of location specifications complying with 3GPP Release 6 LCS Specification. OMA MLS 1.1 is primarily intended for use in a 3GPP environment.
OMA Mobile Location Service V1.2 (MLS V1.2) consists of a set of location specifications complying with 3GPP Release 7 LCS Specification. OMA MLP describes the protocol between an MLS client and the LS. In the 3GPP context, MLP was chosen to be an instantiation of the stage 3 specification for the Le reference point.
The following work items have been approved by the Technical Plenary and entered the OMA Work Program since June 2011:
WID – 243 Rich Communication Centre
WID – 246 Lightweight Machine to Machine
WID – 249 BCAST Next Generation Handheld
WID – 251 Mobile Codes Enhancement and APIs
WID – 252 Converged Personal Network Service
Working Group Vice-Chair Elections
Content Delivery: Jin Peng, ZTE
20-21 September, Atlanta, USA
20-21 September, Berlin, Germany
4-7 October, Berlin, Germany
17 October, Geneva, Switzerland
24-25 October, Basel, Switzerland
26-27 October, Sophia Antipolis, France
30 October – 3 November, Halifax, Canada
17-18 November, Berlin, Germany
Event organizers can contact Bobby Fraher to invite an OMA contribution for an upcoming event.
The OMA is proud to welcome the following new members who have joined recently. We look forward to their participation!
|Company||Membership Level||Company URL|
|Birdstep Technology AB||Full||www.birdstep.com|
|Beijing Leadtone Wireless Ltd.||Associate||www.leadton.com|
|Flextronics (China) Electronics Technology Co., Ltd. ||Associate||www.flextronics.com|
|Mavenir Systems, Inc. ||Associate||www.mavenir.com|