The Protocol Testing Competence Centre 1 In Pursuit

The Protocol & Testing Competence Centre 1

In Pursuit of Interoperability q Ultimate aim of ICT standardisation is interoperability q Likelihood of interoperability is increased with Ø Well-defined, accurate and unambiguous standards Ø Systematic testing of products based on those standards q ETSI produces Base Standards and Test Specifications Test Specs Specification Development Testing 2

Unique Resources Available to ETSI Technical Bodies q TC MTS (Methods for Testing and Specification) Ø Develops specification methodologies and techniques • E. g. , this is where TTCN-3 was defined and is further evolving with significant contribution of PTCC • testing methodology (e. g. , IPv 6 Testing Framework) Ø http: //portal. etsi. org/mbs/ q ETSI PTCC (Protocol and Testing Competence Centre) Ø Supports ETSI Technical Bodies with the development of: • Protocol and service standards (Standards Engineering) • Test specifications Ø http: //www. etsi. org/ptcc q ETSI Plugtests Service Ø Organises interoperability events Ø http: //www. etsi. plugtests 3

How Does the PTCC Help? q Assist ETSI Technical Bodies on the use of state of the art techniques for Ø Specification, validation and testing Ø Good working practices (Standards Engineering) q Pragmatic and flexible approach Ø Based on experience q Help to develop usable methodologies Ø For ETSI’s current and emerging needs q Knowledge transfer Ø Quality through Continuity 5

Who PTCC Supports q Technical Bodies (TB) Ø Technical Committees Ø ETSI Projects Ø Partnership Projects etc. q Chairmen, Rapporteurs, Individuals q Working Groups (WG) q STFs (Specialist Task Forces) Ø PTCC budget for test specifications (15 -20 STFs per yr) q ETSI Secretariat 6

Typical PTCC Areas of Activity Ø GSM and 3 G (UMTS) terminals Ø Wireless: Hiper. ACCESS, Hiper. MAN/Wi. MAX (802. 16) Ø Cordless phones: DECT Ø Access terminals: FSK, SMS Ø ISDN, Broadband ISDN Ø OSA (API, IDL) – web services Ø NGN Ø Vo. IP: H. 225, H. 248, H. 245 (ITU), SIP (IETF) Ø SIGTRAN Ø Smartcards Ø DECT Ø Ø IPv 6: Core, IPSEC, Mobility, v 4 -> v 6 DSRC (ITS) DMR. . . future: More telematics/ITS, more security? 7

PTCC Expertise q Technical competence Ø GSM/3 G UMTS, OSA, Vo. IP, Wireless. Lan, IPv 6, DECT, INAP, BISDN etc. q Protocol Specification and Validation Ø Ø UML (Universal Modelling Language), MSC (Message Sequence Charts), SDL (Specification and Description Language), ASN. 1 (Abstract Syntax Notation One), q Production of Test Specifications Ø world recognised testing expertise Ø TTCN (Tree and Tabular Combined Notation) q Modern tool support 9

Design for Interoperability q Interoperability takes place on external interfaces Ø Normative (mandatory) features Ø Options • Consequences must be clear Ø Abnormal behaviour should be well-defined Ø Robustness q Never specify how product is to be implemented internally Ø Different levels of abstraction e. g. , 3 -stage approach q Methods like SDL, ASN. 1, XML, MSC and UML used to specify these interfaces Ø Data transferred on protocol interfaces • syntax and encodings (ASN. 1, XML) Ø Behaviour of modules as seen from these interfaces q TTCN and test methods used for black box testing Ø No need to know how product is implemented Ø External interface is tested according to specification 10

Profiling and Interworking q Many standards are ‘open’ Ø Include many options q Interoperability requires profiling Ø Ø e. g. ETSI TISPAN NGN Options are screwed down (dropped) Works with ‘similar’ technologies Implement and test the profile q Significantly different technologies Ø Interworking functions Ø e. g. , SIP – H. 323 q General reluctance to specify ‘profiles’ Ø Indications that situation is changing 12

Different Kinds of ETSI Test Specifications Conformance Interoperability Robustness Performance Network Integration RF/EMC 13

The PTCC Testing STFs Write Test Specifications q PTCC Ø 4 full-time experts + 1 assistant (employed by the ETSI Secretariat) Ø 60% test specification, 40% protocol specification q We use Specialist Task Forces (STFs) Ø Experts are seconded from the ETSI membership • PTCC STF Budget • Assignment of this budget is done by ETSI members (ETSI Board) Ø Produce test specifications Ø Short projects • e. g. , 2 man-months maintenance of Vo. IP tests Ø Long projects • e. g. , UMTS testing 58 man-months per year over 3 -4 years Ø 15 – 20 PTCC STFs per year Ø Typical total yearly resource = 10 -15 man-years (with UMTS) 14

What is an STF ? q An STF is a group of experts working together as a team, to produce one or more ETSI standards q STFs give ETSI a competitive advantage by accelerating the development of urgently needed standards q Funded by a dedicated budget line (FWP and PTCC) q STFs are proposed by the ETSI Technical Bodies q Experts are seconded from ETSI Members q Experts normally work at ETSI premises

The STF role in the standards production Normal work Urgent work Technical Body STF To. R Committee voluntary work Board approval Draft standard TB approval Draft ETSI standard ETSI Funding EC/EFTA Members Published ETSI standard STF (contracted experts)

STF funding ETSI Members ETSI budget EC/EFTA Voluntary funding OCG / Board Jan 1 st allocat. 2 nd allocat. Jun Contract … e. Europe Direct contracts Contract … STF 1, STF 2, . . . STF n 17

Information on STF process q General information http: //portal. etsi. org/Portal_Common/home. asp Ø List of STFs Ø Open Call for experts Ø etc. q STF Management principles and practice http: //portal. etsi. org/stfs/process/home. asp A guide through the STF process: Ø Ø How to create an STF How to join an STF ETSI contractual conditions etc … 19

Summary q Standards can be designed for interoperability q Standards should be engineered q Plan for testing (early) q Do the right kind of testing and test in parallel q We can help you achieve the above 20

PEX Help! q Open-door electronic access Ø Ø phone: +33 4 92 94 43 26 fax: +33 4 93 95 84 51 e-mail: ptcchelp@etsi. org Web pages: http: //www. etsi. org/ptcc