Open Mobile Alliance Application Layer Interoperability in a Converged World IMOBICON

Open Mobile Alliance Open Mobile Alliance Application Layer Interoperability in a Converged WorldApplication Layer Interoperability in a Converged World

IMOBICONIMOBICON

Mark CataldoMark Cataldo

Chairman, Open Mobile Alliance Technical PlenaryChairman, Open Mobile Alliance Technical Plenary

August 22, 2007August 22, 2007

2Copyright 2007Open Mobile Alliance Ltd. All Rights Reserved.

Contents

Overview of Open Mobile Alliance

Impact of Fixed Mobile Convergence

OMA Working Groups and Industry Relevance

Summary


”

“OMA Vision

No matter what device I have,

No matter what service I want,

No matter what carrier or network I’m using,

I can communicate, access and exchange information.


The Open Mobile Alliance (OMA)

An international organization developing open, market driven interoperable specifications for global adoption of mobile data services

Created June 2002 by leading mobile operators, device and network suppliers, information technology companies, content and service providers – the entire mobile value chain

Created by combining many existing smaller industry organizations to work under the OMA umbrella

Approximately 350 OMA member companies represent a global organization with members from all regions

More companies from Korea than any other Asian market 45 current Korean member companies


OMA Deliverables and ValueOMA develops specifications and encourages interoperability at the application level

Broadcast Service, Digital Rights Management, Mobile Location Services, Games Services, Device Management

Scope of OMA specifications reaches beyond mobile marketApplicable to IP based networks both fixed and mobile

Consumer Electronics devices

Traditional PC and telephone environments

OMA avoids duplication, divergence and fragmentationOMA has an extensive network of liaison relationships

W3C as outlined in Browser presentation by Bennett Marks

TTA and many others - 37 total


OMA commitment to Interoperability OMA Interoperability

Verification of interoperability, stability and quality in multi-vendor, multi-operator and multi-content provider environments

OMA commitment to increase number of specification implementations tested

Over 1200 product implementations tested to date

OMA shortening time to market with open and tested quality specifications through its IOP programMore details in IOP presentation by Gilbert Buty


Contents




Summary


Convergence is here Multiple network access methods now a reality

Harmonization of user experience will happen in services and applications

Full integration of Internet and Mobile services New services should take advantage of existing functionality, capabilities

and services – not reinventing the wheel Emerging markets will see Internet access for first time users on mobile

devices, not PC’s

Consistent user experience becomes key in services and applications Agnostic of underlying networks Hidden complexity for access methods, such as multi-radio devices Ultimate goal of seamless service access and usability

Fast paced innovation and development increase demand for interoperability and interworking

Equal stake among various elements in end-to-end chain Demand for quality, open specifications enabling interoperable and

conformant implementations


Deployment and adoption demands global standards

OMA delivers open standard specifications, not products

Enabling differentiable services based upon market demand and quality of products and services

Innovation in mobile industry happening ever more rapidly

Consumers expect to access their data services in any market around the globe, regardless of devices or roaming agreements

Key factor in understanding of how mobile, content and IT industries must work together

Innovation in Internet boom drove the development of Web Services and open standards

the same will happen in broad adoption of broadcast services

Standards based solutions provide the framework for rapid deployment of new products and services

Kevin Holley’s Converged IP Messaging presentation will show need for interoperability across messaging platforms as well as development environments for innovation of new services and products


Contents




Summary


OMA OrganizationBoard

Technical Plenary

Release Planning& Management

Architecture

Interoperability

Security

Requirements

BrowserTechnologies

MobileBroadcast

ContentDelivery

DevelopersInterests

Mobile Comm.& Charging

Location

Messaging

Push to talkover cellular

Presence &Availability

Digital RightsManagement

DeviceManagement

DataSynchronization

GameServices


OMA Current Work Items

• 57

• 14

• 6

• 8

• 1

Work Items developing Enabler Releases Work Items developing Reference Releases/other deliverables Maintenance Work Items

Suspended Work Items Work Items under discussion

Total 86 Open Work ItemsSee http://www.openmobilealliance.org/tech/OMAWP/Current/Work_Item_by_status.pdf


Example of OMA Success - Device Management

Before DM was specified, the only way to configure devices was:In factory

In store

Remotely via Client Provisioning and one-way only configuration

Evolving devices and services created need for remote managementFirmware update

Diagnosis and monitoring

Individual installation of software

Device configuration

Scheduling of all of these tasks

Why standardize these functions?Uniform visibility into the resources and functionality of all devices

Network operators can manage devices, conduct diagnosis and update devices remotely and without direct vendor support

Interoperability directly impacts consumer experience


OMA Approved Enabler Releases for DM

DM 1.2 moved from Candidate to Approved in 6 months, and there are already many implementations in market

89% deployment rate of OMA DM according to major handset vendors around the globe90% deployment rate of OMA DM in operator implementations of DM services

Firmware Update Management Object (FUMO) 1.0 completed Interoperability Testing Program

is an Approved Enabler Release

Significant uptake in deployment and ever increasing industry demand for interoperability in device management

applicable to traditional mobile networks and relevant to corporate IT departments/help desks


Diagnostic Capabilities for Device ManagementDiagnostic Monitoring Object – In OMA Work Program

Detect and repair actual or potential problems

Report faults to network

Enable terminals to measure and report key performance indicators

Query device for additional diagnostic data

Operators or corporate helpdesks can also use the diagnostic enablerInvoke specific repair procedures embedded in a given handset model

Use caseSubscriber reports an error indicator or problem to operator or helpdesk

Customer care server or help desk agent queries device for more information

Cause of error or problem is identified

Action taken to repair or correct


Further Developments in DM

Connectivity Management Object -- In OMA Work ProgramSeamless operation of device over various protocols without manual administration of the device

UMTS, CDMA2000, WiFi3GPP Packet Switch, Proxy settings

Wireless data connectivity Specification of a set of data management object schemaExposure by an OMA DM clientTargeting by an OMA DM server from operator or corporate infrastructure

Software Component Management Object (SCOMO)Operator and corporate IT departments can manage software inventory such as libraries and user interface elements.Allows operators and corporate IT departments to ensure compatibility of old and new software.Remove and update existing software and install new software.


Additional Developments in Device Management

Additional DM Enablers in Early Stage DevelopmentLock and Wipe Management Object – remote deactivation of deviceDevice Capabilities Management Object – activation or deactivation of hardware on the device (e.g. WiFi access or other capabilities)

Smart CardStorage or management objects can be associated with SIM cardUsers can switch between devices and take security and other settings with them from device to device

Device Profiles Evolution -- Interoperability across OMA Work ProgramNot in the OMA DM group, but relatedApplications and services need to address variable network environmentsDifferent devices with wide range of capabilities and features DPE creates enhanced device profiles mechanismAllows devices to convey real time dynamic device properties to an ASPEnable any ASP to provide content best suited to device’s capabilities

such as memory size, cache size, CPU load, battery life


Contents


Impact of Fixed Mobile Convergence OMA Working Groups and Industry

Relevance Summary


Summary Multiple modes of connection are a reality

Connect and reconnect PC’s and handsets Access data or move content between users and devices Make users and networks more accessible to increasing number

of content, service and application providers Notion of mobile value chain is widening to include new

industries, such as mobile advertising, presented by David Puron No need to reinvent the wheel

Demands of innovation require incorporating what already exists to support interoperability with new devices and services

Mobility is for everyone, everywhere At home, in the office, on the road, consumer and enterprise

applications must work with ever more complex multi-use devices in multiple environments across a variety of networks and regions

Interoperability is the road to convergence and seamless services

Documents

Open Mobile Alliance Application Layer Interoperability in a Converged World IMOBICON