© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-TP Slide #1 [OMA-Template-SlideDeck ] OMA-TP OMA Work Plan & Dependencies OMA Work Plan & Dependencies USE OF THIS DOCUMENT BY NON-OMA MEMBERS IS SUBJECT TO ALL OF THE TERMS AND CONDITIONS OF THE USE AGREEMENT (located at AND IF YOU HAVE NOT AGREED TO THE TERMS OF THE USE AGREEMENT, YOU DO NOT HAVE THE RIGHT TO USE, COPY OR DISTRIBUTE THIS DOCUMENT. THIS DOCUMENT IS PROVIDED ON AN "AS IS" "AS AVAILABLE" AND "WITH ALL FAULTS" BASIS. Submitted To:Technical Plenary Date:20 th November 2003 Availability: Public OMA Confidential Contact:Philippe Lucas Source:Technical Plenary vice-chair X

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-TP Slide #2 [OMA-Template-SlideDeck ] Contents of the presentation  Overview of process  Release & tracking process  Handling of work orginating from affilliate organisations  OMA Approved WIs and Work Programme

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-TP Slide #3 [OMA-Template-SlideDeck ] OMA has three processes The OMA organisation and process document Deals with general procedural matters for the Technical Plenary and in particular handling of Work Items and the subsequent specification/enabler development life cycle The OMA IOP process document Deals with interoperability processes, policies and principles The OMA Work Programme and Release Handling process document Deals with procedures for the OMA work programme and the release of enablers

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-TP Slide #4 [OMA-Template-SlideDeck ] OMA Work Programme and Release Handling process The process deals with the following topics: What kind of information the WP tracks When the information need to be made available to the WP How the information needed as input to the WP is to be collected and distributed How the information collected as part of the WP is intended to be used How OMA Releases are defined and named How OMA Releases are planned and managed How specifications and releases from incoming affiliates are handled

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-TP Slide #5 [OMA-Template-SlideDeck ] OMA Release Programme OMA working process is a market driven, continuous program designed to deliver three key milestones Ensures products and services work together seamlessly Requires thorough interoperability testing 3 Phases Phase 1: Candidate Enabler Release Phase 2: Approved Enabler Release Phase 3: Interoperability Release

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-TP Slide #6 [OMA-Template-SlideDeck ] OMA Release Programme OMA uses a Work Item List to scope an activity in OMA, including: a list of deliverables, a time schedule for the work to be undertaken any dependencies that the WI may have towards other ongoing work within or outside of OMA An Enabler Release is a collection of specifications that when combined form an enabler for a service area, e.g a download enabler, browsing enabler, etc. An Interoperability Release is a number of Enablers that have gone through the OMA Interoperability process and have proven interoperability

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-TP Slide #7 [OMA-Template-SlideDeck ] Tracking of work in progress All working groups that have ownership of Work Items are required to maintain time schedules for the work that is related to the Work Item Information of time schedules for the work is collected on a regular basis by the Release Planning and Management Committee The result is compiled and made available to the Technical Plenary and its working groups

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-TP Slide #8 [OMA-Template-SlideDeck ] Release process (1/4) The WG responsible for a WI identifies specifications to be included in an enabler and kicks off drafting the Enabler Release Definition (ERELD) When the specifications, ERELD and Enabler Test Requirements have been drafted and considered to be complete, they undergo a consistency review After the complete enabler package with the Requirements Document and Architecture Document, plus supporting information is submitted to the TP for review and approval The TP approval of the release results in a Candidate Enabler Release where all specifications belonging to it also get Candidate status Candidate Specification Draft Specification Enabler Release Definition + Candidate Enabler Release Review and approval by the TP Supporting documents + Phase1

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-TP Slide #9 [OMA-Template-SlideDeck ] Release process (2/4) The Candidate Enabler Release plus the IOT enabler test cases and IUT (Implementations Under Test) are used as input to OMA Test Fests for interoperability testing The Test Fests are likely to result in a number of Problem Reports (PRs) and Change Requests (CRs) that lead to updates of the specifications and test cases A successful Test Fest proves interoperability on enabler level and is documented in a Enabler Test Report Candidate Enabler Release + IOT Enabler Test cases IOT Test Fest IUT + Enabler Test Report Phase2 (1/2)

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-TP Slide #10 [OMA-Template-SlideDeck ] Release process (3/4) Approved CRs Approved CRs based on PRs + Candidate Enabler Release Incorporate CRs Updated Candidate Enabler Release Enabler Test Report Updated Candidate Enabler Release + Approved Enabler Release The documents in the Candidate Enabler Release are updated with the approved CRs to get a clean release The updated Candidate Enabler Release plus the final Enabler Test Report are brought to the Technical Plenary for approval The Technical Plenary approves the release becoming an Approved Enabler Release where all specifications belonging to it Phase2 (2/2) Review and approval by the TP

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-TP Slide #11 [OMA-Template-SlideDeck ] Release process (4/4) + Approved Enabler Release Progress of the work items that are intended to be included in an Interoperability Release is tracked Based on this input, the TP combines Approved Enabler Releases with an Interoperability Release definition and this combined forms an Interoperability Release The Approved Interoperability Release is made publicly available by OMA after TP approval Approved Enabler Release Interop release definition Approved Inter- operability Release Review and approval by the TP Phase3

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-TP Slide #12 [OMA-Template-SlideDeck ] Approved Work Item (1/3) Device Management Application Performance Issues Multimodal and Multi-device Services Digital Rights Management (DRM) Digital Rights Management (DRM) Release 2 Mobile Web Services M-Commerce Proxy-Based Redirection Privacy for Mobile Service Minimum IOP Requirement Document for MMS Web Services IF for Dev Man WCSS Minimum Profile Browsing Enhancements Standard Transcoding Interface

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-TP Slide #13 [OMA-Template-SlideDeck ] Approved Work Item (2/3) WAP-Push Security Maintenance & Enhancements of IMPS 1.X IMPS-Enablement Interface Technology OMA SIP/SIMPLE IMPS Service Definition Architecture Requirements on OMA Architecture and Architecture Framework WV-SIP/SIMPLE Interworking Maintenance of OMA Billing Framework Maintenance and enhancement of Games Services Specifications OMA Location Architecture Overview Roaming Location Protocol Maintenance of OMA legacy Location Specifications from LIF/WAPF Privacy Checking Protocol Push to Talk over Cellular (PoC)

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-TP Slide #14 [OMA-Template-SlideDeck ] Approved Work Item (3/3) Download OTA v2.0 On-board key generation and key enrolment Data Sync maintenance and Enhancement Identity Management Framework Default Style Sheet for XHTMLMP Session Initiation Protocol (SIP) Push OTA MPG Specification Maintenance Execution Policy Enforcement and Management Browsing Maintenance Mobile Application URI Schemes for Telephony and Service Linkage Interworking of Messaging Systems Interfaces for common functions

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-TP Slide #15 [OMA-Template-SlideDeck ] Work Programme Calendar view (1/2) Messaging Management Download/DRM Browser

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-TP Slide #16 [OMA-Template-SlideDeck ] Work Programme Calendar view (2/2) POC Location Games MWS SEC Protocols MCC

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-TP Slide #17 [OMA-Template-SlideDeck ] Summary Release planning process is well defined OMA maintains a work programme in which WI and enabler specifications are well referenced and tracked OMA work can be shared with partner organisations, in particular 3GPP2