Open Mobile Alliance Application Layer Interoperability in a Converged World IMOBICON

1. Open Mobile Alliance Application Layer Interoperability in a Converged World IMOBICON Mark Cataldo Chairman, Open Mobile Alliance Technical Plenary August 22, 2007

2. Contents • Overview of Open Mobile Alliance • Impact of Fixed Mobile Convergence • OMA Working Groups and Industry Relevance • Summary

3. OMA Vision “ No matter what device I have, No matter what serviceI want, No matter what carrieror networkI’m using, I can communicate, access and exchangeinformation. ”

4. 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

5. OMA Deliverables and Value • OMA 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 market • Applicable to IP based networks both fixed and mobile • Consumer Electronics devices • Traditional PC and telephone environments • OMA avoids duplication, divergence and fragmentation • OMA has an extensive network of liaison relationships • W3C as outlined in Browser presentation by Bennett Marks • TTA and many others - 37 total

6. 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 program • More details in IOP presentation by Gilbert Buty

7. Contents • Overview of Open Mobile Alliance • Impact of Fixed Mobile Convergence • OMA Working Groups and Industry Relevance • Summary

8. 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

9. 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

10. Contents • Overview of Open Mobile Alliance • Impact of Fixed Mobile Convergence • OMA Working Groups and Industry Relevance • Summary

11. OMA Organization Board Technical Plenary Release Planning & Management DeviceManagement Requirements MobileBroadcast Location Presence &Availability Digital RightsManagement Architecture BrowserTechnologies Mobile Comm.& Charging Push to talk over cellular DataSynchronization Security ContentDelivery Messaging GameServices Interoperability Developers Interests

12. Work Items developing Enabler Releases Work Items developing Reference Releases/other deliverables Maintenance Work Items Suspended Work Items Work Items under discussion • 6 • 1 • 8 • 57 • 14 OMA Current Work Items Total 86 Open Work Items See http://www.openmobilealliance.org/tech/OMAWP/Current/Work_Item_by_status.pdf

13. 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 management • Firmware 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

14. 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 globe • 90% 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

15. Diagnostic Capabilities for Device Management • Diagnostic 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 enabler • Invoke specific repair procedures embedded in a given handset model • Use case • Subscriber 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

16. Further Developments in DM • Connectivity Management Object -- In OMA Work Program • Seamless operation of device over various protocols without manual administration of the device • UMTS, CDMA2000, WiFi • 3GPP Packet Switch, Proxy settings • Wireless data connectivity • Specification of a set of data management object schema • Exposure by an OMA DM client • Targeting 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.

17. Additional Developments in Device Management • Additional DM Enablers in Early Stage Development • Lock and Wipe Management Object – remote deactivation of device • Device Capabilities Management Object – activation or deactivation of hardware on the device (e.g. WiFi access or other capabilities) • Smart Card • Storage or management objects can be associated with SIM card • Users can switch between devices and take security and other settings with them from device to device • Device Profiles Evolution -- Interoperability across OMA Work Program • Not in the OMA DM group, but related • Applications and services need to address variable network environments • Different devices with wide range of capabilities and features • DPE creates enhanced device profiles mechanism • Allows devices to convey real time dynamic device properties to an ASP • Enable any ASP to provide content best suited to device’s capabilities • such as memory size, cache size, CPU load, battery life

18. Contents • Overview of Open Mobile Alliance • Impact of Fixed Mobile Convergence • OMA Working Groups and Industry Relevance • Summary

19. 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