OMA 2011 Newsletter Volume 1by OMA | Saturday, January 1, 2011
2011 Volume 1
During the February meeting in Honolulu, the OMA held its first Home Environment Services (HES) Workshop. The event was well received by the OMA membership with more than 70 people attending. There were eight presentations by OMA member companies, including China Mobile, NEC, LG Electronics, Interop Technologies, Samsung Eectronics, Qualcomm, Orange and Huawei. Each presentation focused on how individual companies use OMA Enablers to offer services to end users in the home environment. There was also significant coverage of market trends and requirements for the new technologies and standards that will be necessary to enable services in the home environment.
The complete overview from OMA’s HES Workshop, including links to the eight presentations is available at http://www.openmobilealliance.org/AboutOMA/OMA_HES_Workshop.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 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.
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’s working process includes the maintenance of OMA service enablers, as well as the addition of new features and capabilities to existing enablers. OMA also creates entirely new versions of its enablers as needed to meet market demand. The combined architectures of OMA enablers present a modular group of logical technical entities, interfaces and interactions. The full OMA architecture is divided into six categories.
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 Mobile Search Framework (MSrch Framework) defines a mobile search enabler providing several capabilities (such as Search Engine integration, selection, results Personalization) to support mobile search service. Search Engines are not in the scope of this enabler, however some requirements are identified for search engines to be integrated with the OMA MSrch Framework enabler in a standard way.
OMA In Game Advertising (IGA) provides requirements and architectural principles for game developer advertisement-related consideration. Key objectives of OMA’s IGA are identifying related functionalities that enable models and a focus on game-ad specific use cases and functionalities not addressed by other OMA enablers. OMA’s IGA enabler covers in-game advertising models, ads handling in-game, best-practice and case for in-game advertising.
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 Application Layer Security Common Functions (SEC CF) provides a common set of security mechanisms with possible deployment options that can be re-used by OMA enablers. The OMA SEC CF specification will help prevent duplication of security efforts for each OMA Enabler that requires security functionality. OMA SEC CF offers re-use of both the architectural entities (e.g. Security Gateways, etc) and security specifications (e.g. protocol profiles) when developing new OMA enablers.
OMA On-Board Key Generation V1.0 (OBKG) enables on-board key generation and remote key enrollment functionality by defining additional European Computer Manufacture Association (ECMA) scripts and functions in the Wireless Identity Module (WIM). OMA OBKG will enable a remote application of on-board key generation in the WIM and remote key enrollment for (new) user certificates. Both functions are implemented as ECMA scripts that are embedded in an xHTML page.
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.
OMA Global Service Architecture V1.1 (OGSA), represents a comprehensive architectural view of OMA enablers leveraging the OSE (OMA Service Environment). OSE promotes common architectural principles for how OMA enablers are specified and how they interact with one another while ensuring architecture integrity, scalability and interoperability. OMA OGSA’s primary focus is to support new (and/or revised) enabler specifications and to clarify how they fit into the current OMA landscape and how they may be used to support services.
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.
The OMA Client-Side Enabler API (CSEA) enabler defines a set of requirements for API’s to be made available for Web applications running in browser or widget context web runtime environments; in its first phase, OMA CSEA is focused on OMA DCD, OMA Push and OMA DPE.
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 Spam Reporting (SpamRep) enabler provides a mechanism for a Reporter to designate received content as “spam” and provide a report to a network entity. The scope of OMA SpamRep enabler includes only the SpamRep message format and the message transfer between the mobile device and network entity.
OMA Presence Data V1.2 (PRS) reference release defines further Presence Information extensions and their mapping to the presence data model components and Presence Data Information Format extensions (PIDF) either defined in IETF or OMA.
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 SOAP Bindings for NGSI (OMA NGSI_S) aims to specify a first protocol binding choice for selected abstract NGSI interfaces. SOAP binding will comprehend with the style/design as given for the existing PSA v1.0. OMA NGSI SOAP comprehend Parlay-X with extensions for call control, conferencing and multimedia list handling.
OMA RESTful bindings for Parlay X Web Services (OMA REST) specifies an HTTP protocol binding for a subset of Parlay X Web Services interfaces, using the REST architectural style. 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 Service API, Multi Media Messaging Service API, Payment Service API and Terminal Location Service API. ParlayREST V2_0 inherits the REST protocol bindings from ParlayREST 1.0 (listed previously). Additionally, ParlayREST V2_0 defines REST protocol bindings for the following APIs: Presence Parlay X Web Services APIs, Address List Management Parlay X Web Services APIs, Call Notification Parlay X Web Services APIs, 3rd Party Call Parlay X Web Services APIs, Audio Ca, Parlay X Web Services APIs, Terminal Status Parlay X Web Services APIs and Device Capabilities Parlay X Web Services APIs.
OMA Next Generation Service Interfaces (NGSI) focuses on new requirements and API extensions for server-to-server based third party services. Evolving from the integration of the Parlay work into OMA, NGSI will expand next generation networking and services for seamless integration of fixed and mobile networks. By creating a uniform and accepted standard of open APIs, third parties will use application interfaces to access network capabilities as well as further enhance existing capabilities. The scope of NGSI includes the standardization of new functional APIs for: Data Configuration and Management, Call Control and Configuration, Multimedia List Handling extensions, Context Management, Identity Control and Registration and Discovery functions.
This suite of OMA enablers provides access to service resources within networks and their exposed functionality.
OMA Service User Profile Management (SUPM) enabler provides a standardized interface to access and manage the data related to Service User Profile, that allow applications and/or enablers to create, read, update and delete specific data in order to support contextualization and personalization of the user’s services.
The following work items have been approved by the Board of Directors and entered the OMA Work Program since December 2010:
WID – 211 List of supported Management Objects
WID – 213 APIs for Rich Communications
WID – 214 CAB architecture simplification with new market requirements
WID – 215 Converged Address Book APIs
WID – 218 Open Connection Manager API
Chairman: Fred Harrison, Telefonica
Vice-Chairs: Ileana Leuca, AT&T and Mark Cataldo, Orange
Treasurer: Gary Jones, T-Mobile
Working Group Chair Elections
Release, Planning and Management: Johan Zuidweg, Huawei Technologies
Device Management: Linyi Tian, Huawei Technologies
Requirements: Francesco Vadala, Telecom Italia
Working Group Vice-Chair Elections
Architecture: Vincenzo Amorino, Telecom Italia
Requirements: Jesus Martin, Telefonica
GSMA Executive Management Committee
13 April 2011, Mexico City, Mexico
27 April 2011, La Jolla, USA
19-21 September, Berlin, Germany
Event organizers can contact Bobby Fraher to invite an OMA contribution for an upcoming event.
27-30 June, Budapest, Hungary
29 August-2 September, Vancouver, Canada
7-10 November, Asia
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|
|Bluefish Technologies Holdings APS||Associate||www.bluefish.com|
|Logo Solvo Ltd.||Supporter||www.logossolvo.com|
|Smartontech Co. Ltd.||Supporter||www.smartontech.co.kr|