1. © 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-2003-0353R1Slide #1 [OMA-Template-SlideDeck-20030826] Doc# OMA-TP-2003-0353R1-TP6R1 New member orientation New Member Orientation 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.http://www.openmobilealliance.org/UseAgreement.html THIS DOCUMENT IS PROVIDED ON AN "AS IS" "AS AVAILABLE" AND "WITH ALL FAULTS" BASIS. Submitted To:Technical Plenary Date:29 th August 2003 Availability: Public OMA Confidential Contact:Mark Cataldo mark.cataldo@openwave.com Source:Technical Plenary chair X

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-2003-0353R1Slide #2 [OMA-Template-SlideDeck-20030826] Agenda The Open Mobile Alliance Organisational structure Technical Plenary structure Release Programme IPR and anti-trust Meetings Useful URLs Questions

3. © 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-2003-0353R1Slide #3 [OMA-Template-SlideDeck-20030826] The Open Mobile Alliance

4. © 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-2003-0353R1Slide #4 [OMA-Template-SlideDeck-20030826] What is the Open Mobile Alliance? companies and organisations committed to principles drive growth of the mobile industry enable interoperable mobile services and applications formed June 2002 by Open Mobile Architecture Initiative supporters WAP Forum microfora integrated into OMA Wireless VillageMGIF SyncMLMWIF MMS IOPLiF

5. © 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-2003-0353R1Slide #5 [OMA-Template-SlideDeck-20030826] Objectives enable consumer access to interoperable and easy to use mobile services across geographical locations, standards, operators and mobile terminals define an open standards based framework to permit services to be built, developed, and managed efficiently and reliably in a multi-vendor environment establish one mobile industry standards forum as the driving force responsible for creating service level interoperability drive implementation of open services and interface standards, through the user centric approach to ensure fast wide adoption of mobile services

6. © 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-2003-0353R1Slide #6 [OMA-Template-SlideDeck-20030826] 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 22 nd August 2003, OMA has: 31 Sponsor members, 71 Full members, 124 Associate and 94 Supporter members Total of 320 members, other applications pending see http://www.openmobilealliance.org/currentmembers.html http://www.openmobilealliance.org/currentmembers.html OMA Membership

7. © 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-2003-0353R1Slide #7 [OMA-Template-SlideDeck-20030826] Organisational structure

8. © 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-2003-0353R1Slide #8 [OMA-Template-SlideDeck-20030826] Two parts The OMA organisationally is split into two main components Board of Directors Technical Plenary

9. © 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-2003-0353R1Slide #9 [OMA-Template-SlideDeck-20030826] Board of Directors Legal and financial responsibility for running OMA 43 Board members Board Officers Chair: Jari Alvinen (Nokia) Vice Chairs: Clif Campbell (Cingular Wireless) Jacob Christfort (Oracle) Treasurer: Kevin Wagner (Openwave) Several committees to facilitate its work Technical work delegated to Technical Plenary

10. © 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-2003-0353R1Slide #10 [OMA-Template-SlideDeck-20030826] Technical Plenary Technical Plenary has the following types of groups reporting to it: Working Groups defining and performing technical work of OMA under auspices of Technical Plenary (e.g. creating specifications). Committees aid and support smooth running of Technical Plenary to deliver technical work (e.g. processes, planning/management) Birds of a Feather (BoFs) temporary groups making recommendations to Technical Plenary on a specific activity Technical Plenary and each group has its own webpages listing its officers, meeting plans, documents etc. Organisational structure http://www.openmobilealliance.org/organization.html

11. © 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-2003-0353R1Slide #11 [OMA-Template-SlideDeck-20030826] Technical Plenary Officers Chair: Mark Cataldo (Openwave) Vice Chairs: Alastair Angwin (IBM) Philippe Lucas (Orange)

12. © 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-2003-0353R1Slide #12 [OMA-Template-SlideDeck-20030826] Technical Plenary structure

13. © 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-2003-0353R1Slide #13 [OMA-Template-SlideDeck-20030826] Technical Plenary structure

14. © 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-2003-0353R1Slide #14 [OMA-Template-SlideDeck-20030826] OMA Work Groups Specify use-cases and identify interoperability and usability requirements From use cases provide requirements to work groups Coordinate requirements work in work groups Verify consistency of requirements in work groups Requirements Definition of overall OMA architecture Enable specification work in work groups Assure, through review, adherence of specification work to OMA architecture Architecture Secure communication protocols between mobile clients and servers at transport and application layers Security and trust services (e.g. authentication, confidentiality, integrity) provided by/to mobile clients and servers Secure interactions with entities (e.g. with secure hardware tokens) Security

15. © 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-2003-0353R1Slide #15 [OMA-Template-SlideDeck-20030826] OMA Work Groups Identify, specify and maintain processes policies and test programs to ensure interoperability for OMA enablers and end-to-end services Consolidate affiliate IOP groups into a common understanding of IOP activities Study and understand best practices Interoperability Identify, specify and maintain requirements, architecture, technical specifications and test events Accelerate adoption of ubiquitous Instant Messaging and Presence Services Instand Messaging & Presence Service Define application of web services within OMA architecture Provide application of web services converged with the work of external activities Generate recommendations, specifications and best practices to apply web services Leverage existing standards where applicable Mobile Web Services

16. © 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-2003-0353R1Slide #16 [OMA-Template-SlideDeck-20030826] OMA Work Groups Protocols and mechanisms for management of devices Setting of initial configuration data in devices Updates of persistent data in devices Retrieval of management data from devices Processing events and alarms generated by devices Device Management Specifications for data synchronization Develop similar specifications, including but not limited to SyncML technology Conformance specifications and a set of best practices Data Synchronisation Specifications to ensure interoperability of Mobile Location Services on an end-to-end basis Enable Mobile Location Services End-to-end Architectural Framework with relevant application and contents interfaces, privacy, security, charging and billing, and roaming Location

17. © 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-2003-0353R1Slide #17 [OMA-Template-SlideDeck-20030826] OMA Work Groups Collect and publish data relevant to developers Provide means for software developers to articulate needs to OMA Identify missing or inconsistent developer interfaces, make recommendations for additional / enhanced developer interfaces Developers Interest Group Consolidated and consistent approach to generic (horizontal) bearers and protocols Ensure consistent repeatable approach for leverage and usage across applications Identify and recommend bearers and Internet protocols, specify profiles of external specifications and define bearer/protocol adaptations or extensions Mobile Protocols Interoperability specifications, APIs and protocols for network enabled gaming Enable game developers to develop / deploy mobile games to efficiently interoperate with OMA platforms Enable cost reduction for game developers, game platform owners and service providers Games Services

18. © 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-2003-0353R1Slide #18 [OMA-Template-SlideDeck-20030826] OMA Work Groups Specify features (e.g. "user agents", content formats, programming interfaces etc.) that enable creation of data services on mobile hand held devices Create network-centric application models exploiting web architecture and leveraging its technology Develop content formats, browser user agent semantics, interfaces to other in-device applications, application-level services and facilities, application execution environments and application-level programming interfaces Mobile Applications Bring industry players (companies, forums, etc.) closer together to get a more coordinated effort on m-commerce Provide an overall m-commerce view Provide secure transactions, engage wireless network operators, meet financial industry requirements Mobile Commerce

19. © 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-2003-0353R1Slide #19 [OMA-Template-SlideDeck-20030826] OMA Committees Defines operational processes for Technical Plenary Provides support on operational and process activities makes operations/process recommendations to Technical Plenary Other support activities as Directed by the Technical Plenary Operations & Processes Responsible for planning and managing OMA Releases Defines (and proposes to Technical Plenary) the OMA Releases based on OMA specifications Co-operates with working groups and IOP group Supports Technical Plenary with OMA external communications Manage legacy specification approval process for affiliates Release Planning & Management

20. © 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-2003-0353R1Slide #20 [OMA-Template-SlideDeck-20030826] Release Programme

21. © 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-2003-0353R1Slide #21 [OMA-Template-SlideDeck-20030826] 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

22. © 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-2003-0353R1Slide #22 [OMA-Template-SlideDeck-20030826] IPR and anti-trust

23. © 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-2003-0353R1Slide #23 [OMA-Template-SlideDeck-20030826] Intellectual Property Rights IPR information provided on OMA website http://www.openmobilealliance.org/docs/OMA_IPR_Guidelines http://www.openmobilealliance.org/docs/OMA_IPR_Declarations Contains information on IPR guidelines, IPR declarations, Membership guidelines Members (and their associates) have an ongoing duty to use reasonable endeavours to disclose their own and others’ Essential IPR in a timely manner For your convenience, blank forms are available in the OMA Office Call to participants to disclose if their companies own, might own, or have knowledge of Essential IPR’s

24. © 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-2003-0353R1Slide #24 [OMA-Template-SlideDeck-20030826] Anti-trust Anti-trust information provided on OMA website http://www.openmobilealliance.org/docs/AntitrustPolicy.pdf http://www.openmobilealliance.org/docs/AntitrustGuidelines.pdf Contains information on anti-trust guidelines, anti-trust policy OMA recognises the importance of anti-trust laws OMA policy is to comply with anti-trust laws When in doubt, it is OMA policy to seek assistance of legal counsel experienced in anti-trust matters Ann Woodliff is the OMA Legal Counsel

25. © 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-2003-0353R1Slide #25 [OMA-Template-SlideDeck-20030826] Meetings

26. © 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-2003-0353R1Slide #26 [OMA-Template-SlideDeck-20030826] Future Technical Plenary meetings TP#7 London, UK 10 th -14 th November, 2003 TP#8 Beverly Hills, California, USA 1 st -6 th February, 2004 WG Meetings Munich, Germany 26 th -30 th April, 2004 TP#9 Bangkok, Thailand 20 th -25 th June, 2004 TP#10 Location TBD Planned for August, 2004 WG Meetings Orlando, Florida, USA 27 th September-1 st October, 2004 TP#11 Barcelona, Spain 14 th -19 th November, 2004 WGs, Committees and BoFs may hold additional meetings

27. © 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-2003-0353R1Slide #27 [OMA-Template-SlideDeck-20030826] Registration Pack Welcome letter Name badge Meeting receipt Lunch tickets Meeting schedule Meeting/hotel information, including hotel map, acronyms Hotel invitation and fax reservation form for next meeting

28. © 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-2003-0353R1Slide #28 [OMA-Template-SlideDeck-20030826] Meeting logistics 6 main meetings per year 4 TP meetings 2 Working Group/Committee meetings Additional meetings may be arranged by Working Groups/Committees online registration begins six weeks prior to meeting main meeting registration fee $500 for pre-registration $750 for on-site registration cancellations accepted until 5 days before main meeting meeting and hotel information notified at preceding main meeting sent to OMA-ALL posted on members only section of the web site registration desk open Sunday to Friday

29. © 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-2003-0353R1Slide #29 [OMA-Template-SlideDeck-20030826] Meeting logistics Technical groups’ sessions Mon-Wed09:00 – 17:00 (nominal) WG, Committee and BoF sessions Technical Plenary sessions Thursday08:30 – 18:00Technical Plenary Friday08:30 – 15:00Technical Plenary Breaks Mon-Fri10:00 – 10:30Morning break Mon-Fri12:00 – 13:00Lunch Mon-Thu15:00 – 15:30Afternoon break

30. © 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-2003-0353R1Slide #30 [OMA-Template-SlideDeck-20030826] Website: useful URLs Public page http://www.openmobilealliance.org/ General information about OMA, TP, WGs and Committees Press Centre, Events Membership How to join OMA Members’ page http://member.openmobilealliance.org/ WG pages Committee pages

31. © 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-2003-0353R1Slide #31 [OMA-Template-SlideDeck-20030826] Questions Thank you for your attention, and now… over to you!