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

OMA and Interoperability TestingOMA and Interoperability Testing

Gilbert Buty Gilbert Buty Chairman, Interoperability Working Group, OMAChairman, Interoperability Working Group, OMA

www.openmobilealliance.orgiMobicon, Seoul, Korea, August 22, 2007iMobicon, Seoul, Korea, August 22, 2007

2Copyright © August 2007Open Mobile Alliance Ltd. All Rights Reserved.

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


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


IOP Working Group ActivitiesThe 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


ArchitectureReview

ConsistencyReview

Candidate Package

PrototypeTesting

ETR

ApprovedEnabler

ETS

TestFests

Bilateral Testing

Testing Phase

OMA IOP Simplified Process

EnablerSpecifications

Test reports and

generation of IOP Report

Loop processLoop process

EVP

TP Agreed ?TP Agreed ?

Yes

No


ArchitectureReview

ConsistencyReview

Candidate Package

PrototypeTesting

ETR

ApprovedEnabler

ETS

TestFests

Bilateral Testing

Testing Phase



Test reports and



EVP


Yes

No

TWG prepares theTest requirementsTo be validated by IOP


ArchitectureReview

ConsistencyReview

Candidate Package

PrototypeTesting

ETR

ApprovedEnabler

ETS

TestFests

Bilateral Testing

Testing Phase



Test reports and



EVP


Yes

NoIOP starts to work on test specifications ASAPto foster the process


ArchitectureReview

ConsistencyReview

Candidate Package

PrototypeTesting

ETR

ApprovedEnabler

ETS

TestFests

Bilateral Testing

Testing Phase



Test reports and



EVP


Yes

No

When ETS/EVP sufficientlydeveloped, IOP maydecide to startprototype testing


ArchitectureReview

ConsistencyReview

Candidate Package

PrototypeTesting

ETR

ApprovedEnabler

ETS

TestFests

Bilateral Testing

Testing Phase



Test reports and



EVP


Yes

No

When ETS/EVP approvedby TP, enabler goes toTestFests or BilateralTesting events


ArchitectureReview

ConsistencyReview

Candidate Package

PrototypeTesting

ETR

ApprovedEnabler

ETS

TestFests

Bilateral Testing

Testing Phase



Test reports and



EVP


Yes

No

Results from testing are fed back to IOP to improve quality of specifications


ArchitectureReview

ConsistencyReview

Candidate Package

PrototypeTesting

ETR

ApprovedEnabler

ETS

TestFests

Bilateral Testing

Testing Phase



Test reports and



EVP


Yes

No

When enough test Results are collected, IOPrecommends “Approved” status


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


Status of Current Enablers in IOP

On the road towards the “Approved” Status

IMPS 1.1IMPS 1.1IMPS 1.2.1IMPS 1.2.1IMPS 1.3IMPS 1.3MMS 1.1MMS 1.1MMS 1.2MMS 1.2OCSP 1.0OCSP 1.0PoC 1.0PoC 1.0Presence 1.0Presence 1.0STI 1.0STI 1.0SUPL 1.0SUPL 1.0XDM 1.0XDM 1.0

““Approved”Approved”StatusStatusEnablersEnablers

Browsing 2.1Browsing 2.1Browsing 2.2Browsing 2.2Charging 1.0Charging 1.0CSCSF 1.0CSCSF 1.0DS 1.1.2DS 1.1.2DS 1.2DS 1.2DM 1.1.2DM 1.1.2DM 1.2DM 1.2DRM 1.0DRM 1.0DRM 2.0DRM 2.0DL 1.0DL 1.0FUMO 1.0FUMO 1.0

Browsing 2.3Browsing 2.3

BCAST 1.0BCAST 1.0

CP 1.1CP 1.1

DL 2.0DL 2.0

DRM 2.1DRM 2.1

EMN 1.0EMN 1.0

GS CSI 1.0GS CSI 1.0

MMS 1.3MMS 1.3

Push 2.1Push 2.1


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 availableTest 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


Available OMA Test Tools

DM v1.2SCTS for DM v1.2 – Open Source tool available from SourceForge (Project: OMA-SCTS)

DRM v2.0CTT from CoreMedia (Available to License)

BCAST v1.0TTCN-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



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



Provides confidential neutral environment

Allows inter-working between competitors

Provides complete mobile infrastructure2G and 3G networks (GSM, CDMA, W-CDMA)

WAP Gateway, PPG, SMS Centre, IMS System

Formal testing against Test Specifications

Results reported anonymously to IOP WGAllows assessment of enabler for approval

Problems and issues fed back into OMA process through neutral reporting system


OMA TestFest Achievements

21 Test Events held to so far

Over 1100 implementations tested144 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 OMAAll related to Specifications

Implementation errors dealt with by participants


Opportunities in 2007 & 2008

Continuing to Plan 5 TestFest per annum3 more events in 2007Over 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


TestFest Dates/Hosts in 2007/2008

7th - 14th September 2007Vodafone, Düsseldorf

All Enablers except BCAST

21st – 28th September 2007Vodafone, Düsseldorf

BCAST Only Event

9th - 16th November 2007Mobitel & Sintesio, Bled, Slovenia

2008 Dates available on OMA websiteLocations still being planned


OMA Permanent TestFest Sites

OMA’s ObjectiveTo 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 selectionCommercial Terms, Technical Ability, Organizational Capabilities

4 sites already selectedChina Mobile (Beijing), ITT (Montreal), TeliaSonera (Helsinki), Vodafone (Düsseldorf)

Opportunities for other companies to become a Permanent TestFest Site


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 2006http://product.openmobilealliance.org/

191 Products listed from 35 Companies already listed

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

Documents

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