scope:

Context for the present document

The oneM2M standard is now mature and multiple deployments exist all over the world at both experimental and operational levels. The experimental deployments are conducted for multiple reasons: to evaluate the capabilities of the standard in terms of expressiveness, usability on specific equipment, connection with specific existing systems or performance evaluation. To provide a methodological study, based on performance evaluation (time, space) on a given set of "paradigmatic use cases". The present document will evaluate use cases in terms of running time, memory space, numerosity of oneM2M entities (like e.g. AE, MN-CSE, CSE, etc.), data transfer volume and real-time needs. The present document will use a selection of available oneM2M CSE implementations. The present document will provide a tool to evaluate and simulate the performance of the use cases. The results of this tool development and evaluations of the use cases will be the basis to generate three Technical Reports [i.2], [i.3] and [i.4] and one Technical Specification [i.1]. The present document was developed in the context of ETSI Testing Task Force (TTF) T019, set up to perform work on "Performance Evaluation and Analysis for oneM2M Planning and Deployment". Five elements were addressed sequentially:

1) A collection of use cases and derived requirements were formally identified and defined. This work includes identification of relevant deployment scenarios. The present document adopted the use case style and template from oneM2M with a minor modification to address some performances issues. This phase of the work resulted in ETSI TR 103 839 (the present document).

2) The definition of performance evaluation model, with specification of procedures to assess the performance of oneM2M-based IoT platforms. This includes the identification and definition of a set/list of KPIs necessary to assess the deployment. For those KPIs, provision of a formal description of the test campaign and the test results to be obtained. This phase of the work resulted in deliverable ETSI TS 103 840 [i.1].

3) The creation of a proof of concept of a performance evaluation tool. This work also relies on a formal description of the identified deployment scenarios (single vertical domain & multiple vertical domains). This phase of the work resulted in ETSI TR 103 841 [i.2].

4) A practical demonstration and analysis exercise putting the proposed tool to use, with a specific oneM2M implementation but aimed at being a blueprint for the adoption and re-use of the results of ETSI TR 103 839 (the present document), ETSI TS 103 840 [i.1] and ETSI TR 103 841 [i.2] with other oneM2M implementations and deployment scenarios. This phase of the work resulted in ETSI TR 103 842 [i.3].

5) The development of a set of guidelines and best practices documenting best practices and lessons learnt as well as providing instructions for IoT solution topology, capacity provisioning, expected performances. This phase of the work resulted in ETSI TR 103 843 [i.4].

The present document covers the first of the five items listed above and provides the basis for the related ETSI publications listed below:

• ETSI TR 103 839: Scenarios for evaluation of oneM2M deployments (the present document);

• ETSI TS 103 840: Model for oneM2M Performance Evaluation [i.1];

• ETSI TR 103 841: oneM2M Performances Evaluation Tool (Proof of Concept) [i.2];

• ETSI TR 103 842: Demonstration of Performance Evaluation and Analysis for oneM2M Planning and Deployment [i.3];

• ETSI TR 103 843: oneM2M deployment guidelines and best practices [i.4].

Scope of the present document

The present document identifies additional requirements to be potentially submitted to oneM2M in the areas of performance evaluation by means of relevant use cases. The oneM2M architecture ([i.5] and [i.6]) is targeted as the standard to be evaluated regarding these use cases and requirements. The present document is structured as follows:

• Clauses 1 to 3 set the scene and provide references as well as definition of terms, symbols and abbreviations, which are used in the present document.

• Clause 4 describes the method used for collecting Use Cases providing a proposal of a tiny extension of the use case "template" as provided in oneM2M-Template-Use-Case [i.7] and extensively used in oneM2M TR-0001 [i.8].

• Clause 5 presents Use Case, called "Smart Campus".

• Clause 6 presents a Use Case, called "Generalization of event trigger/periodic event IoT system" that focuses on classical event triggered and or time triggered behavioural aspects to be captured in IoT systems. The objective is to obtain, based on such an example, some generic constraints to be expressed and to determine the associated constraints and KPI to be evaluated.

• Clause 7 presents a Use Case, called "Traffic lights Control and monitoring", reflecting a deployment by C-DAC, India and several generic implementation variations.

• Clause 8 presents oneM2M feature coverage analysis of the use cases collected.