1 / 22

OMA and Interoperability Testing Gilbert Buty Chairman, Interoperability Working Group, OMA

OMA and Interoperability Testing Gilbert Buty Chairman, Interoperability Working Group, OMA www.openmobilealliance.org iMobicon, Seoul, Korea, August 22, 2007. Agenda. OMA and Interoperability (IOP) IOP Working Group Activities IOP Process OMA TestFest Benefits

teness
Download Presentation

OMA and Interoperability Testing Gilbert Buty Chairman, Interoperability Working Group, OMA

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. OMA and Interoperability Testing Gilbert Buty Chairman, Interoperability Working Group, OMA www.openmobilealliance.org iMobicon, Seoul, Korea, August 22, 2007

  2. Agenda • OMA and Interoperability (IOP) • IOP Working Group Activities • IOP Process • OMA TestFest Benefits • OMA Enablers (Current and Approved) • OMA Test Tools • OMA TestFests in Detail • TestFest Achievements

  3. OMA and Interoperability • Fast paced innovation and development have resulted in increased demand for interoperability and inter-working in a multi-party environment • OMA has a commitment to increase the number of Enabler specifications in which implementations are tested • OMA TestFests - Verification of specification interoperability, stability and quality • OMA is committed to reducing the time to market with open specifications which are tested for quality through its IOP program

  4. IOP Working Group Activities • The IOP Working Group objectives are to ensure the quality and interoperability of OMA specifications and the resulting implementations • Main activities: • Maintenance of the required processes, policies and test programs • Development and Approval of Test Specifications • Enabler Test Specification (ETS) • Enabler Validation Plan (EVP) • Enabler Implementation Conformance Statement (EICS) • Organization of OMA test events (TestFests) • Review and Analyze TestFest results reported

  5. Approved Enabler Testing Phase ETR TestFests Candidate Package Bilateral Testing TP Agreed ? Enabler Specifications Test reports and generation of IOP Report OMA IOP Simplified Process Consistency Review Architecture Review Yes EVP ETS No Prototype Testing Loop process

  6. Approved Enabler Testing Phase ETR TestFests Candidate Package Bilateral Testing TP Agreed ? Enabler Specifications Test reports and generation of IOP Report OMA IOP Simplified Process TWG prepares the Test requirements To be validated by IOP Consistency Review Architecture Review Yes EVP ETS No Prototype Testing Loop process

  7. Approved Enabler Testing Phase ETR TestFests Candidate Package Bilateral Testing TP Agreed ? Enabler Specifications Test reports and generation of IOP Report IOP starts to work on test specifications ASAP to foster the process OMA IOP Simplified Process Consistency Review Architecture Review Yes EVP ETS No Prototype Testing Loop process

  8. Approved Enabler Testing Phase ETR TestFests Candidate Package When ETS/EVP sufficiently developed, IOP may decide to start prototype testing Bilateral Testing TP Agreed ? Enabler Specifications Test reports and generation of IOP Report OMA IOP Simplified Process Consistency Review Architecture Review Yes EVP ETS No Prototype Testing Loop process

  9. Approved Enabler Testing Phase ETR TestFests When ETS/EVP approved by TP, enabler goes to TestFests or Bilateral Testing events Candidate Package Bilateral Testing TP Agreed ? Enabler Specifications Test reports and generation of IOP Report OMA IOP Simplified Process Consistency Review Architecture Review Yes EVP ETS No Prototype Testing Loop process

  10. Approved Enabler Testing Phase ETR TestFests Candidate Package Bilateral Testing TP Agreed ? Enabler Specifications Results from testing are fed back to IOP to improve quality of specifications Test reports and generation of IOP Report OMA IOP Simplified Process Consistency Review Architecture Review Yes EVP ETS No Prototype Testing Loop process

  11. Approved Enabler Testing Phase When enough test Results are collected, IOPrecommends “Approved” status ETR TestFests Candidate Package Bilateral Testing TP Agreed ? Enabler Specifications Test reports and generation of IOP Report OMA IOP Simplified Process Consistency Review Architecture Review Yes EVP ETS No Prototype Testing Loop process

  12. OMA TestFest Benefit to Members • By participating in an OMA TestFest, companies can: • Expand their market opportunities by ensuring that their products are interoperable with other industry implementations of OMA specifications • Avoid costs and delays in product deployments by resolving specification issues before deployment • Participate in the identification and resolution of technical issues to help bring new products and services to market much quicker

  13. Status of Current Enablers in IOP “Approved” StatusEnablers Browsing 2.1 Browsing 2.2 Charging 1.0 CSCSF 1.0 DS 1.1.2 DS 1.2 DM 1.1.2 DM 1.2 DRM 1.0 DRM 2.0 DL 1.0 FUMO 1.0 IMPS 1.1 IMPS 1.2.1 IMPS 1.3 MMS 1.1 MMS 1.2 OCSP 1.0 PoC 1.0 Presence 1.0 STI 1.0 SUPL 1.0 XDM 1.0 Browsing 2.3 BCAST 1.0 CP 1.1 DL 2.0 DRM 2.1 EMN 1.0 GS CSI 1.0 MMS 1.3 Push 2.1 On the road towards the “Approved” Status

  14. OMA Test Tools • IOP program also facilitates enabler test tools • No longer mandates test tools as entry criteria to OMA TestFests • Although continuing to work with test tool industry to develop TTCN-3-based Conformance Test Cases • Plan to make TTCN-3 Code available • Test Tool Industry will incorporate TTCN-3 code into their tools • Members can license tool from industry • Self test of implementations in own lab and • Results log file can be made available to customers

  15. Available OMA Test Tools • DM v1.2 • SCTS for DM v1.2 – Open Source tool available from SourceForge (Project: OMA-SCTS) • DRM v2.0 • CTT from CoreMedia (Available to License) • BCAST v1.0 • TTCN-3 Test Cases currently being developed in a pilot project to help make OMA tools available throughout the industry. Test Cases expected to be available in Oct 2007

  16. OMA TestFests in Detail • OMA interoperability events • Held 4 or 5 times per year • Between 80 and 140 engineers attending • Test about 6 to 8 different enablers • 40 to 60 test teams • 6 or 7 day event

  17. OMA TestFests in Detail • Provides confidential neutral environment • Allows inter-working between competitors • Provides complete mobile infrastructure • 2G and 3G networks (GSM, CDMA, W-CDMA) • WAP Gateway, PPG, SMS Centre, IMS System • Formal testing against Test Specifications • Results reported anonymously to IOP WG • Allows assessment of enabler for approval • Problems and issues fed back into OMA process through neutral reporting system

  18. OMA TestFest Achievements • 21 Test Events held to so far • Over 1100 implementations tested • 144 in 1st Year (11/02 – 10/03 – 5 events) • 178 in 2nd Year (11/03 – 10/04 – 4 events) • 263 in 3rd Year (11/04 – 10/05 – 4 events) • 429 in 4th Year (11/05 – 10/06 – 5 events) • 148 so far in Year 5. • Over 500 problems and issues raised to OMA • All related to Specifications • Implementation errors dealt with by participants

  19. Opportunities in 2007 & 2008 • Continuing to Plan 5 TestFest per annum • 3 more events in 2007 • Over 20 new Candidate Enablers will start Testing in 2008 • BCAST v1.0, DRM 2.1 already testing at September 2007 events • Other Opportunities to be explored

  20. TestFest Dates/Hosts in 2007/2008 • 7th - 14th September 2007 • Vodafone, Düsseldorf • All Enablers except BCAST • 21st – 28th September 2007 • Vodafone, Düsseldorf • BCAST Only Event • 9th - 16th November 2007 • Mobitel & Sintesio, Bled, Slovenia • 2008 Dates available on OMA website • Locations still being planned

  21. OMA Permanent TestFest Sites • OMA’s Objective • To appoint a number of sites ready to host TF • Help OMA to improve it’s ability to plan TestFests using both volunteer and permanent sites • Criteria for selection • Commercial Terms, Technical Ability, Organizational Capabilities • 4 sites already selected • China Mobile (Beijing), ITT (Montreal), TeliaSonera (Helsinki), Vodafone (Düsseldorf) • Opportunities for other companies to become a Permanent TestFest Site

  22. OMA Product Listing • Recognition for companies participating in TestFests • Ability to list products and the enablers they support • Must include general TestFest results • Can optionally list: • Functionality of Product (EICS) • Company’s Results achieved at TestFest (ITR) • Web-site open to public access in June 2006 http://product.openmobilealliance.org/ • 191 Products listed from 35 Companies already listed

More Related