Doc# OMA-TP-2003-0 353R1 -TP 6R1 New member orientation New Member Orientation

1. Doc# OMA-TP-2003-0353R1-TP6R1 New member orientationNew Member Orientation Submitted To: Technical Plenary Date: 29th August 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. Agenda • The Open Mobile Alliance • Organisational structure • Technical Plenary structure • Release Programme • IPR and anti-trust • Meetings • Useful URLs • Questions

3. The Open Mobile Alliance

4. 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 Village MGIF SyncML MWIF MMS IOP LiF

5. 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. 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 22nd August 2003, OMA has: • 31 Sponsor members, 71 Full members, 124 Associate and 94 Supporter members • Total of 320 members, other applications pending • seehttp://www.openmobilealliance.org/currentmembers.html

7. Organisational structure

8. Two parts • The OMA organisationally is split into two main components • Board of Directors • Technical Plenary

9. 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. 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. Technical Plenary Officers • Technical Plenary Officers • Chair: Mark Cataldo (Openwave) • Vice Chairs: Alastair Angwin (IBM) Philippe Lucas (Orange)

12. Technical Plenary structure

13. Technical Plenary structure

14. 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 • Definition of overall OMA architecture • Enable specification work in work groups • Assure, through review, adherence of specification work to OMA 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) Requirements Architecture Security OMA Work Groups

15. 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 • Identify, specify and maintain requirements, architecture, technical specifications and test events • Accelerate adoption of ubiquitous Instant Messaging and Presence Services • 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 Interoperability Mobile Web Services Instand Messaging & Presence Service OMA Work Groups

16. 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 • Specifications for data synchronization • Develop similar specifications, including but not limited to SyncML technology • Conformance specifications and a set of best practices • 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 Data Synchronisation Device Management Location OMA Work Groups

17. 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 • 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 • 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 Mobile Protocols Developers Interest Group OMA Work Groups

18. 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 • 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 Applications Mobile Commerce OMA Work Groups

19. 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 • 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 Operations & Processes OMA Committees

20. Release Programme

21. 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. IPR and anti-trust

23. 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. 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. Meetings

26. Future Technical Plenary meetings • TP#7 London, UK • 10th-14th November, 2003 • TP#8 Beverly Hills, California, USA • 1st-6th February, 2004 • WG Meetings Munich, Germany • 26th-30th April, 2004 • TP#9 Bangkok, Thailand • 20th-25th June, 2004 • TP#10 Location TBD • Planned for August, 2004 • WG Meetings Orlando, Florida, USA • 27th September-1st October, 2004 • TP#11 Barcelona, Spain • 14th-19th November, 2004 WGs, Committees and BoFs may hold additional meetings

27. 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. 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. Meeting logistics • Technical groups’ sessions • Mon-Wed 09:00 – 17:00 (nominal) WG, Committee and BoF sessions • Technical Plenary sessions • Thursday 08:30 – 18:00 Technical Plenary • Friday 08:30 – 15:00 Technical Plenary • Breaks • Mon-Fri 10:00 – 10:30 Morning break • Mon-Fri 12:00 – 13:00 Lunch • Mon-Thu 15:00 – 15:30 Afternoon break

30. 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. Questions Thank you for your attention, and now… over to you!