OMA-TP-2003-0 630 - OMA Overview OMA Overview

1. OMA-TP-2003-0630-OMA OverviewOMA Overview Submitted To: OMA-3GPP2 Workshop Date: 20th November 2003 Availability: Public OMA Confidential Contact: Mark Cataldo mark.cataldo@openwave.com Source: Technical Plenary chair X USE OF THIS DOCUMENT BY NON-OMA MEMBERS IS SUBJECT TO ALL OF THE TERMS AND CONDITIONS OF THE USE AGREEMENT (located at http://www.openmobilealliance.org/UseAgreement.html) 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.

2. Contents OMA’s creation, mission and principles OMA structure OMA Membership, participation, Anti-trust, IPR

3. OMA’s creation, charter and principles

4. Open Mobile Alliance • In June 2002, the mobile industry set up a new, global organization called the Open Mobile Alliance (OMA) • The Open Mobile Architecture initiative supporters and the WAP Forum formed the foundation for the Open Mobile Alliance • The following organizations have integrated into OMA: • Location Interoperability Forum (LIF) • SyncML Initiative • MMS-IOP (Multimedia Messaging Interoperability Process) • Wireless Village • Mobile Gaming Interoperability (MGIF) • Mobile Wireless Internet Forum (MWIF) • Other industry forums focusing on interoperability and open standards are welcome to join  

5. What is OMA? • The OMA is designed to be a center for mobile service specification work, stimulating and contributing to the creation of interoperable services “No matter what device or operating system you have, no matter what service you have, no matter what carrier you use, you cancommunicate and exchange information.”

6. OMA Mission • Deliver responsive and high-quality open standards and specifications based upon market and customer requirements • Establish centers of excellence for best practices and conduct interoperability testing (IOT), including multi-standard interoperability to ensure seamless user experience • Create and promote common industry view on an architectural framework • Be the catalyst for the consolidation of standards fora; working in conjunction with other existing standards organizations and groups such as IETF, 3GPP, 3GPP2, W3C, JCP etc.

7. OMA Principles

8. OMA Principles • Products and services based on open, global standards, protocols and interfaces and not locked to proprietary technologies • The applications layer is bearer agnostic (examples: GSM, GPRS, EDGE, CDMA, UMTS) • The architecture framework and service enablers are independent of Operating Systems (OS) • Applications and platforms are interoperable, providing seamless geographic and inter-generational roaming

9. OMA – Making the difference • Why is this different? • Delivery of specifications based on mobile services use case scenarios and open standards • Creation and promotion of a common architectural framework • All key industry segments involved in specification work • Focus on improving the end-user experience by providing end-to-end & multi-standard interoperability • Companies committed to implementation of the open standards and IOP testing • Consolidate fragmented industries • Accelerates innovation and speeds time to market of new services and applications • Promote industry wide adoption of open standards over proprietary alternatives • Decreased operational costs for all involved by improving industry efficiencies

10. OMA structure

11. Technical Plenary structure Board Technical Plenary Mark Cataldo, Openwave Operations & Processes Dwight Smith, Motorola Release Planning & Management Peter Arnby, Ericsson Requirements Kevin Holley, mmo2 Browser & Content Alastair Angwin, IBM Games Services Lars Brenk, TTPCom Push to talk over cellular Gaby Lenhart, T-Mobile Architecture Christian Herzog Siemens Device Management James Jennings, IBM Location Hans Rohnert, Siemens Mobile Web Services Nilo Mitra, Ericsson Security Michel Mouly, Vodafone/Orange Data Synchronisation Leighton Ridgard, FusionOne Messaging Jerry Weingarten, Comverse Presence & Availability Frank Dawson, Nokia Interoperability Sanjay Gupta, Motorola Developers Interests Alan Kaplan, Panasonic Mobile Commerce & Charging Jouni Käiväräinen, Telia

12. Role of the Technical Plenary • Reports to the Board of Directors • Delegated by Board of Directors with responsibility for • technical specification drafting and planning activities • approval and maintenance of technical specifications and reports • resolution of technical issues • Produces technical specifications for application and service frameworks, with certifiable interoperability, in a timely manner enabling deployment of rich mobile applications and services • Uses the OMA Process to perform its duties • Charters a number of Working Groups and committees • Organises Plenary meetings, workshops and adhoc meetings

13. OMA membership, participation, anti-trust, IPR

14. OMA Membership • OMA member companies fall into 4 categories that define the various parts of the end-to-end value chain: • Wireless Vendors • Information Technology Companies • Mobile Operators • Application & Content Providers & Others • Companies can join OMA in any one of four membership categories: • Sponsor, Full, Associate, Supporter • As at 29th October 2003, OMA has: • 31 Sponsor members, 75 Full members, 133 Associate and 99 Supporter members • Total of 338 members, other applications pending • seehttp://www.openmobilealliance.org/currentmembers.html

15. Participation Policy • Member registration for OMA members • Guest registration • http://member.openmobilealliance.org/gen_info/TP/guest.asp • OMA-3GPP2 Cooperation Framework provides guidance on cross participation

16. Anti-trust • Anti-trust information provided on OMA website • http://www.openmobilealliance.org/ipr.html • contains information on anti-trust guidelines and anti-trust policy • OMA recognises the importance of anti-trust laws • OMA policy is to comply with anti-trust laws

17. Intellectual Property Rights • IPR information provided on OMA website • http://www.openmobilealliance.org/ipr.html • contains information on IPR guidelines, IPR declarations, Membership guidelines • Terms & Conditions: fair, reasonable and non-discriminatory to members • OMA and 3GPP2 Partners have similar principles in their respective membership policies regarding declaration of IPR and licence thereof • Members (and their associates) have an ongoing duty to use reasonable efforts to disclose their own and others’ Essential IPR in a timely manner • OMA-3GPP2 Cooperation Framework provides guidance on alerting each other of IPR in inputs received from each other

18. Summary • Created by leading mobile services companies to perform mobile services specification work, stimulating and contributing to the creation of interoperable services • Produces specifications enabling interoperable services and applications • does not standardised services and applications • Access, transport and device OS agnostic • Established to cooperate with other organisations • Any company may join: diverse membership across entire value chain • Structured to support detailed specification work using well defined working procedures and IPR/Anti-trust policies