5.1 Introduction

GSMA TS.34 [1] represents a guideline and giving requirements for whole IoT Device, as defined in Figure X to ensure an efficient connection.

Figure 5.1-1: Generalised IoT Device Architecture according to GSMA TS.34

Figure 5.1-1: Generalised IoT Device Architecture according to GSMA TS.34[1]

Requirements with regards to an efficient communication are grouped and categorized in TS.34 [1] . E.g. requirements are formulated for the following areas:

  • IoT Device Application Requirements
  • Communication Module Requirements
  • IoT Service Provider Requirements
  • Policy-based Connection Efficiency Requirements
  • Radio Policy Manager Requirements
  • 3GPP Connection Efficiency Features

oneM2M is most beneficially able to support an efficient communication in the area of the IoT Device Application, while other areas, like required support of "3GPP Connection Efficiency Features" can be considered out of scope of oneM2M, and hence out of scope of this WI. With regards to "IoT Device Application Requirements", GSMA TS.34 [1] differentiates further between:

  1. Monolithic IoT Device Application Requirements: Those requirements are applicable for devices without an embedded Service layer and hence are out of scope oneM2M anyway.

  2. Tiered IoT Device Applications Requirements: Those requirements are applicable for applications providing the required functionality according to GSMA TS.34 [1] , cooperatively together with the embedded Service layer.

  3. IoT Embedded Service Layer Requirements: Those requirements are applicable for the embedded Service layer, providing the required functionality according to GSMA TS.34 [i.1]

While the main focus of this work is primarily on 2) and 3) further requirements in GSMA TS.34 [1] have been screened, analysed and used to inspire functionality to be taken for oneM2M to ensure an efficient IoT communication.

The considered Requirements out of GSMA TS.34 [1] in the context of oneM2M are listed in the subsequent sections, with the respective numbering schema kept as used in TS.34 [1] , for your reference.