1. Test WG (WG6) 2015 Planning TST 15 Source: JaeSeung Song, TST WG Convenor (TTA), jssong@sejong.ac.krjssong@sejong.ac.kr Meeting Date: 2015-01-12 TST-2015-0007-WG6_2015_planning

2. Purpose of TST WG (2015) Develop a set of oneM2M test specifications Initiate oneM2M Interoperability Testing event Establish a proper certification model

3. Test Specifications A set of oneM2M test specifications: – TST-spec-1: Interoperability Test Descriptions of oneM2M Primitives over HTTP binding – TST-spec-2: Interoperability Test Descriptions of oneM2M Primitives over CoAP binding – TST-spec-3: Interoperability Test Descriptions of oneM2M Primitives over MQTT binding Schedule: -TST-spec-1 & 2: Aug. 2015 -TST-spec-3: Dec. 2015

4. Specification Development Plan Test spec.TP#15 (Jan) TP#16 (Mar) TP#17 (May) TP#18 (Jul) TP#19 (Sep) TP#20 (Nov) HTTP TST CoAP TST MQTT TST Skeleton & baseline Interop. configuration Develop each chapter Clean-up, consistency check, improve readability Distribute tasks Develop each chapter Clean-up, consistency check, improve readability Distribute tasks Develop each chapter Clean-up, consistency check, improve readability Distribute tasks

5. Interoperability Testing Events Twice in a year 1 st oneM2M Interoperability Testing Event: – Could consider July or August in 2015 once test specifications are ready oneM2M compliant devices and platforms are ready Items need to be discussed: – Where to host? Could co-locate with other events (e.g., oneM2M TP, IoT/M2M related conferences & workshops) – Who host? One of SDOs (ETSI and TTA show their interest) Action items: – A1: List up vendors and their product line together with developing status (Need to be updated in every TP meetings) – A2: Create a concrete plan for the 1 st oneM2M IOT event (Who takes lead and where to host)

6. Certification So far four models have been identified but maybe not limited to these four models: – Option 1: Having an independent certification entity outside of oneM2M (e.g., Global Certification Forum) – Option 2: oneM2M takes in charge of certification (e.g., HGI and Continua) – Option 3: Self certification (do not have any authorised certification entity) – Option 4: Hybrid certification Self-certification: for End Node devices developed by end users (D.I.Y) Common service layer certification: for devices & nodes produced for commercialization  need an independent certification entity Vertical certification: for specific devices & nodes in a vertical GCF will provide an introduction to their test&certification activities Several test&certification companies show their interest to oneM2M Will report available options to HoD after oneM2M TP #15