1 / 21

3GPP2 Evolution Workshop Enabling applications and services Mark Cataldo

3GPP2 Evolution Workshop Enabling applications and services Mark Cataldo Chairman, OMA Technical Plenary 27 th June, 2005. Open Mobile Alliance. 1. Vision and Mission of OMA The Need for Interoperable Standards OMA Market Position Industry Consolidation and Collaboration

bijan
Download Presentation

3GPP2 Evolution Workshop Enabling applications and services Mark Cataldo

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 3GPP2 Evolution Workshop Enabling applications and services Mark Cataldo Chairman, OMA Technical Plenary 27th June, 2005

  2. Open Mobile Alliance 1 Vision and Mission of OMA The Need for Interoperable Standards OMA Market Position Industry Consolidation and Collaboration OMA Deliverable and Enabler Releases 2 3 4 5

  3. OMA Vision “ No matter what device I have, no matter what service I want, no matter what carrier or network I’m using, I can communicate, access and exchange information. ”

  4. OMA Mission The mission of the Open Mobile Alliance is to facilitate global user adoption of mobile data services by specifying market driven mobile service enablers that ensure service interoperability across devices, geographies, service providers, operators, and networks while allowing businesses to compete through innovationand differentiation.

  5. OMA: A Unique Industry Forum • OMA is different because it brings together all of the links in the value chain • Wireless Vendors • Information Technology Companies • Mobile Operators • Application and Content Providers • Representation from companies of all sizes and across all geographic barriers • Deliver on end-to-end services and solutions and a truly open standard

  6. Today’s Standards Landscape X1 OITDA JEIDA S1 P1 INSTAC T1 FCC TR46 TR45 A1 MITF E1 CSA TIA TR41 FO2 M1 CIAJ PCC.III TR30 FO6 CITEL L3 CEPT EP T3 J22 PCC.I NCITS ARIB CAC CEN/ CENELEC B5 ETSI T4 GMM CG ISOC V1 TC GSM Assoc CDG Mobey Forum MPT/TTC Council ECMA ANSI IETF TC-32 OMG NNI PHS MoU Parlay IEEE ITU SDR TTC Comm. OASIS DIN AIC ITU-T JTC1 ITU-R ISO MPF AFNOR ITU-D NATIONAL OMA REGIONAL Paycircle IEC JISC GLOBAL 3GPP 3GPP2 IMTC BSI Liberty Alliance MPA POSIX Blue tooth GMCF JAIN IFPI UWCC INForum APT OIF W3C OIDA MMCF MIPI IMTC SIF ASTAP RIAA NIST CWTS NM IP UL ECTEL CTSI NS EMC TR & ACC PCIA IMT-2000 EIA TTA SIA SEMI NEMA CTIA MMTA ICSCA EMA

  7. The Need for Interoperable Standards A Simple Service Solution Client Server Service Enabler

  8. Multiple Clients Multiple Terminals Multiple Services Multiple Communications Protocols Multiple Application Servers Multiple Enablers The Need for Interoperable Standards

  9. The Need for Interoperable Standards

  10. OMA Market Position Foster the growth of mobile services End-2-end interoperability Consolidate overlapping standard fora and cooperate with others Cater for the whole mobile services value chain

  11. End-2-End Interoperability • High-quality open standards and specifications • Interoperability testing (IOT), including multi-standard interoperability • Wide adoption of open standards over proprietary alternatives

  12. Consolidation of Industry Organizations To date, six affiliates have consolidated into OMA In addition, work inherited from WAP Forum continues throughout the organization

  13. OMA Collaborates with Other Organizations • OMA has established cooperation agreements with many external organizations allowing for: • Closer cooperation and cross-participation between organizations • Document and information exchange • Other forms of cooperation as needed, including: • Joint MMS Workshop with 3GPP, 3GPP2, CDG, GSMA • OMA has established relationships with 17 industry organizations and SDO’s • Discussions underway with many more organizations

  14. External Liaisons with Outside Organizations

  15. Industry Collaboration • More Co-Operation with Certification Bodies • Formal Relationships, Information Sharing • Feedback on OMA Draft Specifications • Feedback on Priorities, Markets and Timelines • Reliance on OMA Achievements • Enabler Test Specifications • Use of TestFest Participation and Results to Augment Certification Process • Use of Common Tools • Certification Visibility, Web Links, Promotion of Results and Recognition of OMA

  16. Industry Collaboration • More Involvement of Test Tool Industry • Engage for Drafting Test Specifications • Contribute on Testability and Automation of testing • Additional Conformance Tools aligned with OMA Specifications • Involvement of Test Tool Industry in TestFests

  17. Scope of OMA Deliverables • OMA generated specifications • Based on market-driven requirements and use cases • OMA Release Programme • Delivers complete specifications packaged into “Enabler Releases” • Enabler Releases may consist of one or more specifications • OMA testing • Verifies Enabler Releases in interoperability test events for products built using OMA technical specifications • Enabler Releases used by different organizations to develop differentiating interoperable products and services • Enabler Test Specifications to be used in OMA interoperability test events or other interoperability testing • Others • Reports, analyses, white papers, industry studies etc.

  18. Market-Driven Activities • Members propose work items • If approved, items define a specification activity • Work items generated based on market needs • Use cases created to verify market needs • Requirements captured from use cases in Requirements Document • Architecture Document is defined to support the Requirements Document • Detailed technical specifications to enable requirements generated • Above documents are used to produce a set of functional specifications • Packaged document called an Enabler Release • Multiple reviews ensure consistency with market-driven requirements

  19. OMA Candidate Enabler Releases OMA Mobile Location Protocol 3.1 OMA Mobile Location Service 1.0 OMA On-Board Key Generator 1.0 OMA Online Certificate Status Protocol Mobile Profile 1.0 OMA Presence Simple 1.0 OMA Push to Talk Over Cellular 1.0 OMA Standard Transcoding Interface 1.0 OMA SyncML Common 1.2 OMA User Agent Profile 1.1 OMA User Agent Profile 2.0 OMA vObject Minimum Interoperability Profile 1.0 OMA Wireless Public Key Infrastructure 1.0 OMA XML Document Management 1.0 OMA Billing framework 1.0 OMA Browsing 2.1 OMA Browsing 2.2 OMA Browsing 2.3 OMA Browser Protocol Stack 2.1 OMA Client provisioning 1.1 OMA Data Synchronization 1.2 OMA Device Management 1.2 OMA Digital Rights Management 2.0 OMA Domain Name Server 1.0 OMA Email Notification 1.0 OMA External Functionality Interface 1.1 OMA Game Services 1.0 OMA IMS in OMA 1.0

  20. OMA Approved Enabler Releases OMA Data Synchronization 1.1.2 OMA Device Management 1.1.2 OMA Digital Rights Management 1.0 OMA Download 1.0 OMA Instant Messaging and Presence Service 1.1 OMA Instant Messaging and Presence Service 1.2 OMA Multimedia Messaging Service 1.1 OMA Multimedia Messaging Service 1.2 OMA SyncML Common Specification 1.1.2 OMA Web Services 1.0

  21. OMA Enablers Tested • Nine OMA TestFests conducted to date • 438 implementations tested IMPS59 clients / 50 servers Data Synchronization56 clients / 29 servers MMS52 clients / 33 servers DRM 1.0 32 clients / 18 servers DRM 2.0 12 clients / 8 servers Device Management22 clients / 24 servers Download 6 clients / 2 servers Client Provisioning8 clients / 5 servers Push-to-Talk 8clients / 6servers

More Related