scope:

Context for the present document

The oneM2M ETSI standard (oneM2M TS-0001 [1]) is now mature: 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".

• To measure KPIs defined in the present document. Different implementations exist that are compliant with the oneM2M standard, available either freely or commercially.

Use cases are evaluated in terms of chosen KPI: e.g. running time, memory space, numerosity of oneM2M entities (e.g. AE, MN-CSE and CSE), data transfer volume and real-time needs. Using a select set of available oneM2M CSE implementations, a simulation library or an ad hoc simulator is to be provided, offering the ability to evaluate and simulate the performance of the use cases and give crucial information/feedback to the general user of the oneM2M to choose and tune their IoT applications based on oneM2M framework. The results of this tool development and evaluations of the use cases will be the basis to generate other deliverables. The present document was developed in the context of ETSI 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 use case style and template from oneM2M have been adopted with a minor modification to address some performances issues. This phase of the work resulted in ETSI TR 103 839 [i.5].

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 the present document.

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 [i.5], present document 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, and expected performances that will gives crucial directives and information to designer and implementors. This phase of the work resulted in deliverable provisioning and expected performances. This phase resulted in ETSI TR 103 843 [i.4].

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

• ETSI TR 103 839[i.5]: Scenarios for evaluation of oneM2M deployments.

• ETSI TS 103 840 (the present document): Model for oneM2M Performances Evaluation.

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

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

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

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 a MM able to characterize application representation and deployment in the oneM2M standard. 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 a layered vision of one IoT application, designed using oneM2M and deployed over a distributed and connected platform of execution.

• Clause 5 highlights Key Configuration Parameters that could be manipulated by IoT architect and Key Performance Indicators that they could expect.

• Clause 6 focuses on the oneM2M Application Scenario Descriptor (OASD) able to describe the application in term of behavior, requirements and description as oneM2M resource.

• Clause 7 presents the subset model oneM2M CSE Performance Descriptor (OCPD) that expresses how a specific oneM2M service layer is decomposed and how is used hardware resource to create the oneM2M function.

• Clause 8 describes the oneM2M Solution Deployment Descriptor (OSDD). This subset model expresses processing, storage and network part of the execution platform on which common service entities are running.

• Clause 9 presents how a use case could be instantiated with the previous model templates.

• Clause 10 provides the conclusions of the present document.