Essential Requirements of the IoT
Meet essential requirements – the basis of reliable smart IoT services – with 7layers

Soda Model RequirementsTo ensure user acceptance of Smart Services and the Internet of Things (IoT) it will not be sufficient for users that the applications are just interesting and helpful. They must also be reliable, safe to use and reasonably priced.

To achieve this, it is necessary for Smart Services and connected devices not only to adhere to essential requirements such as Health, Quality of Products, Safety and Environmental aspect. New, additional requirements must also be fulfilled, namely

  • Connectivity
  • Data Security
  • Accountability and
  • Smart Services Quality.

Currently, the majority of Smart Services being developed and set-up are proprietary solutions comprising wireless-connected devices and sensors, Smart Services platforms, data collection, data analysis and pre-emptive actions. In general, such proprietary solutions adhere to specifically developed requirements and specifications.

Standardized requirements and specifications would make the development and set-up of Smart Services solutions faster and less expensive. Several organizations, such as the oneM2M initiative, are currently working on such standardizations.

In the meantime, however, it is in the interest of Smart Services Stakeholders to ensure that implemented devices, data platforms, applications, processes and services follow

  • applicable country-specific legislation
  • industry interest group-specific rules and regulations


  • specifically developed, proprietary specifications.

7layers has many years experience in the testing and certification of wireless connected devices in accordance with standardized regulations of countries and regions as well as certification requirements of wireless associations (PTCRB, GCF, Bluetooth SIG, CCC) and network operators.

This however does not cover all requirements relating to an individually developed Smart Service. The 7layers engineering capabilities, built up in conjunction with important players in the mobile communications industry, are ideally suited to supporting  the set-up and life cycle management of Smart Services.

Take a look at the 7layers portfolio for Smart Services lifecycle management which includes services such as consultancy, requirements capturing, development of specifications, test specifications. etc.


For successful Smart Services, not only reliable Connectivity but also Data Security aspects are especially important:

Read more

Many rules and regulations that touch Smart Services lifecycles already exist. They cover data security in general as well as the security of (wireless) networks, devices and communications technologies. Data protection rules (e.g. EU Data Protection Directive) exist in many countries. Interception of personal data transmitted via telecommunications networks is forbidden. IT processes should adhere to ISO security standards. Industry interest groups (e.g. GSMA, Bluetooth® SIG) have standards concerning technology implementation in devices in order to support seamless connectivity.

So-called “vertical markets” have their own additional rules (e.g. HIPAA Standards for Health Care in USA, EU Automotive EMC Directive, Smart Metering Protection Profile in Germany). Networks, devices and services that are part of an M2M process must already follow many existing specifications.

For example the oneM2M initiative, is therefore developing a universally acceptable, horizontal M2M Business Platform architecture comprising application and data transport security plus reliable registration processes that enable the handling of access rights, authentication, authorization, accounting and non-repudiation. Personal User IDs in combination with so-called trusted elements on the devices, data processors and service deliverers can help promote these developments.

Security guidelines based on standardization aim to give Users of M2M services a greater feeling of security without being too expensive or complicated. This would imply different security levels depending on how crucial a service is. The challenge is to develop such standards quickly enough for an impatient, fast-developing market and make them acceptable for all regions and all vertical market segments.