OMA 2011 Newsletter Volume 2by OMA | Friday, April 1, 2011
2011 Volume 2
OMA member companies have identified a market need for users belonging to one social network to interact and communicate with users on another social network. Currently, this is not possible in the global IP environment, because each social network is controlled by a single company or entity. When you consider the growing market demand for access to all applications and services—no matter what device is used to communicate and access content — OMA has nearly 10 years of experience to share with the growing number of social network communities that continue to launch around the world. OMA sees this market demand in the form of users who wish to move between devices and networks as they access their own social networks as well as their friends on other social networks.
In June, OMA published a white paper on mobile social networking that identifies many of the scenarios and requirements for interoperability among various social network communities. In a new work item from OMA, a dedicated Mobile Social Networking Working Group will address end-to-end, federated social network services in the mobile world. This will provide optimized solutions for end-users, operators and all related stakeholders in social network communities, through seamless notification mechanisms, air traffic saving and out-of-coverage compensation.
*Please find the OMA White Paper on Mobile Social Networking at http://www.openmobilealliance.org/documents/110601%20OMA%20MSN%20Whitepaper.pdf
*Please find the new OMA Work Item Definition for Mobile Social Networking at http://www.openmobilealliance.org/documents/OMA-WID_0244-MobSocNet-V1_0-20110405-D.pdf
OMA Technical Plenary Chair Sees Continued Relevance for OMA Device Management as Deployments Reach One Billion Globally
As many of you may know, the Industry Analyst Firm, Ovum has projected that the total number of handsets deploying OMA DM specifications will reach one billion in 2011. One billion! I am sure you join me in congratulating the OMA DM Working Group on this pending milestone. This achievement also got me thinking about the future relevance of OMA DM in particular and OMA more generally. One key area that comes to mind is Machine-to-Machine Communications (M2M).
Just recently, we have seen increased interest in OMA DM specs with regard to M2M. OMA DM easily extends to non-mobile and non-terminal devices, even those that don’t have a SIM card. The OMA DM Working Group continues its work to make sure that OMA DM functions in the All-IP environment. With OMA’s Gateway Management Object work item due to be completed in Q3, the DM Working Group has a great deal to be proud of and indeed to look forward to in the M2M space.
More generally, I can appreciate the modularity of OMA’s enablers as captured in the OMA Global Service Architecture. By mixing and matching multiple enablers, we begin to see scenarios where different building blocks from more than one OMA working group can be combined to create applications and services that are highly relevant in today’s established markets—as well as the new markets where all of our companies hope to find new revenue streams in the future. In the case of M2M, the pairing of OMA’s DM work with the new Converged Personal Network Services (CPNS) enabler, shows us myriad new use cases: from e-health sensors, to moving content across multiple devices in multiple locations, to managing home appliances on a customized personal network.
As I look at the OMA 2011 Release Plan, I am excited to learn more about the variety of combinations of OMA specifications that will help build and support our growing and evolving industry even as we continue to face global economic challenges.
* For more information about the full OMA DM Suite of Specifications, please find a recently created overview at http://member.openmobilealliance.org/ftp/COMMS/Documents/OMA Device Management Specification Suite.pdf.
* For more information about OMA CPNS, Gateway Management Object and M2M please find a recently created overview at http://member.openmobilealliance.org/ftp/COMMS/Documents/oma collateral m2m 5-11.pdf.
OMA and Near Field Communications Forum Agree to Cooperate with Diagnostics and Monitoring Management Object
On 16 May, the OMA Board of Directors approved a Cooperation Agreement with the Near Field Communication Forum, (NFC Forum). This agreement confirms the two groups’ common objectives to establish and promote global standards in the wireless telecommunications and Internet domain, and establishes a framework for joint work on NFC-enabled devices and related applications. The areas of cooperation will focus on OMA’s Device Management, Diagnostics and Monitoring specifications. These areas have been recognized as relevant and useful to the NFC Forum’s standardization efforts. The NFC Forum announced the Agreement on 12 July.
“With billions of devices already using OMA specifications in the market, it is good to see that our work is relevant in supporting new technologies and new markets”, says Fred Harrison, Chairman of the Board, OMA. “For OMA members as well as the wider mobile industry, the market for near field enabled devices offers vast new opportunities for processing transactions, distributing content and communication using new channels and devices.”
The NFC Forum is dedicated to advancing the use of Near Field Communication technology by developing specifications, ensuring interoperability among devices and services, and educating the market about NFC technology.
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 Enabler Releases (AER)
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.
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 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 Games Services Client Server Interface (GS CSI) enables the interaction between the client and the server of game services in a standard manner. OMA GS CSI allows the initial Game Server System to be extended into a more comprehensive Game Server System.
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 Rich Media Environment (RME) provides the language and transport mechanism that enables the distribution and display, on mobile devices, of rich media environment (RME) content. OMA RME defines flexible methods for accessing RME data. OMA RME will enable the creation of user friendly and compelling experiences, giving the user a richer experience when accessing services.
OMA Download Over the Air (DLOTA)V2.0 represents an evolution of OMA DLOTA 1.0, which provided a mechanism for user-initiated download of content, such as ring-tones, images and applications. OMA Download Over the Air V2.0 is backward compatible.
OMA Browsing (Browsing) provides OMA browsing capability for mobile and wireless handheld devices and any necessary or optional supporting network services which may be provided on a gateway or proxy. The suite of specifications defining OMA Browsing defines the application-level protocols, semantics, syntax, content formats, user agent behavior and the use of hypermedia transfer protocols required to achieve consistent function and interoperability of services.
OMA Browser Protocol Stack Enabler provides two protocol stacks for the integration of OMA services with underlying network bearers. At least one of these two stack architectures must be implemented in the client and server.
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 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.
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 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 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 screens, status indicators, fonts and menus.
OMA Device Management (DM) Scheduling Enabler specifies the Device Management Scheduling Framework and corresponding Management Objects that can be layered on top of OMA DM V1.2 to add seamless common scheduling functionality to existing management infrastructure. This functionality is fully interoperable with other Management Objects Enablers including OMA FUMO, OMA SCOMO, OMA DCMO and OMA DiagMon. This allows the management operations to be performed in a scheduled manner, avoiding costly management sessions.
OMA Converged Personal Network Services (CPNS) enables universal access to services across the convergence of a Personal Network and Wide Area Network/Cellular Network. OMA CPNS Enabler defines a collection of individual networks that can be interconnected by means of a Personal Network Gateway (PN GW) using a variety of mobile and fixed devices. This allows access to services from outside a single network and also allows one network or user to offer services to another user or external network.
OMA List Management Object (ListMO) lists the Management Objects supported by the OMA DM Client resident on the device and exposed by the device. OMA ListMO allows a device management server to easily retrieve the list of the supported MOs and any associated details.
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 SIMPLE Instant Messaging (SIMPLE IM) provides a framework for 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.
OMA Multimedia Messaging Service (OMA MMS) V1.3 provides a rich set of content to subscribers using mobile messaging. OMA MMS supports both sending and receiving messages via properly enabled client devices. OMA MMS V1.3 builds upon the existing OMA MMS V1.2 specifications. Key features of OMA MMS include the ability to support messaging activities with other available messaging systems.
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 External Functionality Interface (EFI) defines the way components or entities with embedded applications, which execute outside the Wireless Application Environment [WAE] user agent, conform to the external functionality requirements. These external functionalities can be utilized via user agents such as OMA Browsing or other user agents. The external functionality may be built-in to, or connected to, a mobile terminal supporting these user agents and the connection can be permanent or temporary.
This suite of OMA enablers provides access to service resources within networks and their exposed functionality.
OMA Secure User Plane Location (SUPL) V2.0 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 Presence Access Layer (PAL) Enabler complements OMA Presence SIMPLE. OMA PAL specifies logically interoperable abstractions known as Presence Aspects. Presence Aspects consolidate Presence Information based on one or more Presence Information Elements. Presence Context associates applicable Presence Aspects required to fulfill service function points with a Presence Aware Service. This provides PAL Clients with a consolidated and determinate view of Presence Information.
OMA User Profile (OMA UAProf) enables the end-to-end flow of a User Agent Profile (UAProf) between the device, the intermediate network points and the origin server ensuring that relevant device capability information is available for all necessary parties. Origin servers, gateways and proxies can then use the capability information to ensure that the user receives content that is particularly tailored for the intended environment.
OMA Presence SIMPLE Data Specification (PDE) 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.
The following work items have been approved by the Board of Directors and entered the OMA Work Program since March 2011:
WID – 217 Converged Address Book 1.1
WID – 218 Open Connection Manager AP
WID – 219 Delta Record Managed Object
WID – 221 Authorization Framework for Network APIs
WID – 224 RESTful Network API for FileTransfer
WID – 225 RESTful Network API for Presence
WID – 226 RESTful Network API for Notification Channel
WID – 227 RESTful Network API for Chat
WID – 228 RESTful Network API for Short Messaging
WID – 229 OneAPI Profile of RESTful Network APIs
WID – 230 Common for RESTful Network APIs
WID – 231 Guidelines for RESTful Network APIs
WID – 232 RESTful Network API for Third Party Call
WID – 233 RESTful Network API for Address List Management
WID – 234 RESTful Network API for Messaging
WID – 235 RESTful Network API for Payment
WID – 236 RESTful Network API to Device Capabilities
WID – 237 RESTful Network API for Audio Call
WID – 238 RESTful Network API for Call Notification
WID – 239 RESTful Network API for Terminal Status
WID – 240 RESTful Network API for Image Share
WID – 241 RESTful Network API for Terminal Location
WID – 242 RESTful Network API for Video Share
WID – 0244 Mobile Social Network 1.0
WID – 0245 Rights Issuer Common Domain 1.0
External Liaisons: Isabelle Valet-Harper, Microsoft
Strategic Planning Committee: Cecilia Corbi, Telecom Italia
External Liaisons: Thomas Picard, Alcatel-Lucent
Finance: Fran O'Brien, Alcatel-Lucent
Strategic Planning Committee: Ivan Ivanov, Samsung
Working Group Chair Elections
Communications: Kyung-Tak Lee, Samsung
Working Group Vice-Chair Elections
Release Planning and Management: Antonella Napolitano, Telecom Italia
Communications: Cristina Badulescu, Ericsson
Dr. Uwe Rauschenbach, Senior Specialist, Nokia Siemens Network, received OMA’s Outstanding Contribution Award for his contribution and commitment to OMA’s Architecture, BCAST and Content Delivery Work Programs. Uwe was nominated by Liliana Dinale, OMA Architecture Working Group Chair. The award was presented by OMA’s Technical Plenary Chair, Musa Unmehopa, during the Sorrento Technical Plenary in April.
15-16 June, 2011, Taichung, Taiwan
28-29 June 2011, Berlin, Germany
GSC M2M Task Force
18 May 2011, Dallas, USA
17-20 May 2011, Dallas, USA
27 April 2011, La Jolla, USA
GSMA Executive Management Committee
13 April 2011, Mexico City, Mexico
20-21 September, Berlin, Germany
4-7 October, Berlin, Germany
24-25 October, Basel, Switzerland
Event organizers can contact Bobby Fraher to invite an OMA contribution for an upcoming event.
7-11 November, Beijing, PRC
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|
|Oberthur Technologies S.A.||Full||www.oberthur.com/|
|Telecommunication Metrology Center of MIIT||Supporter||www.emcite.com>|