1. Interoperability event Sept 2015 Group Name: WG TST Source: Sookhyun Jeon, TTA, shjeon@tta.or.kr Laurent Velez, ETSI, laurent.velez@etsi.org Meeting Date: 2015-03-25

2. Goals Purpose: – Now oneM2M Rel-1 has been published, it is essential to validate the produced standards, in order to eliminate any ambiguity and potential issues. – It is also important for industry that oneM2M provides them an opportunity to confirm their understanding of the oneM2M standards. It gives confidence to go to the market. – Interoperability events give a chance to companies to meet each other in a “neutral” environment, to debug their implementations. – For WG TST, it is a good way to validate the test specifications that have been produced or at least to find any potential issues.

3. Organization TTA and ETSI propose to co-organize the first oneM2M interoperability event, based on their experience from similar events and testing best practice. The participation will be free of charge and open to all (oneM2M members or not) The company test results will be confidential, participants will need to sign Non-Disclosure Agreement (NDA). The anonymous technical issues will be gathered in a report produced by TTA and ETSI, and provided to WG TST and the WGs for further standardization considerations.

4. Test Scope The scope of the event could be to test the oneM2M primitives communications, for managing the main oneM2M resources. It is the basis for validating the rel-1, before going to something more focused. Test Specifications: – TS-0013: Interoperability testing over HTTP – TS-00XX: Interoperability testing over CoAP

5. Proposed dates and location Things needed for the event: – Test specifications would need to be in stable draft status. – oneM2M devices and platforms would need to be available (even prototypes) – It needs many implementations in order to get relevant interop testing. – Need to find a good timeframe in order to get the maximum number of oneM2M implentations. In order to get a synergy with the oneM2M community and to avoid additional travels, the proposal is to co-locate the Interop test event at the TP#19 in Sophia-Antipolis. The week after TP#19 (7-11 Sept 2015) from Monday 14 to Wednesday 16 Sept 2015 in ETSI premises. The Interop test room is the room where the oneM2M showcase demos was located B2B3, with possible extension to B1AB

6. How to organise Interop event? 6 Event co-ordination – Registration – Event Promotion – Legal Aspects – Logistics Technical co-ordination Test plan Test Infrastructure Test tools Test Scheduling Test Session Reporting Final technical report

7. Registration 7 Attendance is free of charge but registration is mandatory Companies to register on the web event, indicating the number of participants ( importants for logistics) Companies to fill an oneline form indicating which products types they will test and which « features » are supported (CoAP, HTTP, …) – This is very important for preparing the event especially for scheduling the test sessions. Registration will be confirmed when NDA will be signed by the company

8. Example of Test Network 8

9. Example of a Test Session Scheduling 9

10. Event WIKI A WIKI could be put in place to enhance the exchange of communication and information in the preparation phase and during a Interop event The following information is available – Testing Information Test Specs / Base Specs Testing conventions Equipment parameters – Network Information Any info related to the test infrastructure – Minutes of Wrap Up Sessions Feedback to Standard 10

11. Test Reporting Tool The Test session Reporting (TRT) tool collects test data during testing events – Registration of individual users with distinct access rights, as well as companies and products – Creation of test session reports to capture test execution results and comments – Real-time result summaries of all recorded test sessions – Useful tool for wrap-up sessions – Facilitation for efficient test reporting – Provision of anonymised, statistical results for each test configuration Overall Result / Result per Test group / Result per specific test Technical background – Accessible via internet – Secure web-based access 11

12. Test tools When applicable, the organizers would provide needed test equipments and testing tools.