OMA Requirements Working Group

Kennie Kwong


The OMA REQ WG, currently chaired by Kennie Kwong of AT&T, is one of the horizontal working groups in OMA and is responsible for identifying and specifying requirements for OMA service enablers in order to support end-to-end interoperability across different devices, network operators, and service providers. Those requirements are the basis of the technical specifications development in OMA.

OMA REQ WG also identifies use cases focused on deployment scenarios and the users’ point of view, with the aim to facilitate understanding of the requirements.

Requirements are usually accompanied by an end-to-end service description to provide indications on what is the business rational for creating a specific enabler release. This high level description of the features and functions defines enablers’ objectives, when considered as a service (e.g. Mobile Code, Mobile Advertising, Customized Multimedia Ringing, MMS, Mobile Spam Reporting) and/or a building block (e.g. Network APIs, Converged IP Messaging).

It is an OMA best practice that the development of requirements, which have significant horizontal implications across multiple OMA WGs, is done in the REQ WG. Nevertheless, the requirements might be developed in another OMA WG (e.g. LOC WG for location enablers) for specific activities. When this is the case, a process is followed in order to make the requirements development as transparent as possible to REQ WG. REQ WG requests regular reporting of progress on requirements development from other OMA WGs.

REQ WG is responsible for the management of the Formal Review for all requirements developed in OMA. The purpose of such reviews is to provide OMA members (in particular OMA REQ WG delegates) with well-defined procedures to capture, discuss and resolve their comments, and to provide transparency and traceability.

Bringing Value to the Mobile Industry

The OMA REQ WG has made significant contributions internally in OMA and externally.
In February 2010, the OMA Technical Plenary organized an internal Workshop on “Service deployment in evolved mobile all-IP systems”; in this event, OMA REQ elaborated and presented an input (see [1]) that, starting from trends analysis in the telco/IT world, aimed to identify a list of considerations that would allow operators to exploit the capability of All IP Systems to provide more appealing services to end-users. Among the items highlighted in the contribution were the evolution of messaging tools and social networking tools to enable an easy connectivity/connection management, Internet of Things, Cloud and personal data management.

In October 2011, the OMA Technical Plenary Chair was invited to speak at the ITU-T SDP Workshop on recent progress and achievements in standardization for service enablers, and requirements for future SDP (Service Delivery Platform) standardization activity. For this event, OMA REQ prepared an input (see [2]) that identified some insights for future SDP standardization from the point of view of OMA including:

  • support of composite services (mashed up of services executed on Operators SDP and 3rd part service providers);
  • support of dynamic offering, negotiation and subscription for accessing service components;
  • support of dynamic update of policies for protecting the exposed service components;
  • support of dynamic mechanisms for optimizing the allocation of resources according to the requests of the applications;
  • support of flexible payment model.



Active OMA REQ WG Members

The list of OMA members active in the REQ WG includes Telecom Italia, Deutsche Telekom, Telefonica, China Unicom, Huawei, ZTE, China Telecommunications, China Mobile, AT&T, ETRI and SK Telecom.

REQ WG Highlighted Achievements 2002-2012

The REQ WG has delivered many requirements specifications over the last 10 years. Below is a non-exhaustive list of these specifications:

  • The Always Online Infrastructure (AOI) enables applications to be online while reducing the number of connections needed, by providing a unified connection mechanism between different application clients and servers. Furthermore, the AOI could dynamically optimize the use of bandwidth based on connection priority and vacant bandwidth utilization.
  • The Converged Address Book (CAB) is an evolution of the address book and includes features that are not local to user devices, such as network storage and publication and subscription support.
  • The Converged IP Messaging (CPM) provides common building blocks to allow the creation of interpersonal interactive multimedia communication services, including features such as parallel conversations, personalization of services by setting preferences, store any type of message and Media in the network.
  • The Converged Personal Network Service (CPNS) provides functionality such as end-to-end management of service sessions, publication and discovery of services, and customization of service characteristics based upon device capabilities.
  • The Mobile Advertising (MobAd) specifies mechanisms related to the user profile and context as well as mechanisms related to the associated content that will be used to personalize and contextualize advertisements sent to a given user.
  • The Mobile Augmented Reality (MobAR) defines an overall framework that enables Mobile Augmented Reality services through personalization and management of AR Content and user interactivity handling to AR Content, network and client APIs.
  • The Open Connection Manager API (OpenCMAPI) enables local applications on the device to manage connectivity and connections, but also to provide information status on the connection or the device, notifications/call-backs and complementary services APIs such as SMS, USSD, and GNSS.
  • The Mobile Spam Reporting (SpamRep) defines a protocol/interface and message format for forwarding user-identified spam messages to a network collection point.
  • The Unified Virtual Experience (UVE) enables online-usage functionality, where users can try-out applications remotely on the server-side without first downloading them on his/her device.
  • The Social Network Web (SNeW) defines the architecture and the related entities and interfaces to allow interoperability between clients and servers and server-to-server federation, supporting features such as publication and sharing of content and activities and reactions between users across Social Networks.

Future Plans for 2013 and Beyond

Looking forward to 2013 and beyond, OMA REQ WG will continue creating new requirements specifications to support interoperable End-to-End mobile services.

In particular, the activity on Unified Cloud Disk (UCD) requirements will be finalized. The UCD aims to optimize the current cloud storage service by providing a unified cloud storage system for service providers and new Storage-as-a-service APIs for mobile users or applications.

In addition, the REQ WG will continue supporting other OMA WGs with formal and informal review of requirements, socialization of modifications to requirements previously approved, socialization of proposals for new Work Items, proactive monitoring of requirements specified in other OMA WGs, and will continue to be flexible in adapting to the new challenges coming from the evolution of the service layer world.