What is SQC with an example


An instrument for testing and certification is the Eclipse IoT testware, which is part of the IoT-T project funded by the Federal Ministry for Economic Affairs and Energy (BMWi). The aim of this testware is to support companies in the creation of IoT-based solutions and products in the areas of quality assurance and certification.

Based on the test methodology practiced at ETSI, the test goods are characterized by a systematic approach. Automatically executable test suites are developed for IoT protocols and services. Proven and standardized technologies such as TTCN-3 are used. TTCN-3 is an established standard for testing protocols. Continuously developed since 1998, VoIP, 4G and IPv6 have already been tested with it. For the first time, test suites for conformity tests of the CoAP and MQTT protocols are being developed with the IoT testware TTCN-3. Protocols are the basis for communication between networked things, whereby in addition to HTTP, CoAP and MQTT in particular have established themselves for IoT solutions. The conformity tests mentioned are aimed at the robustness, reliability and dynamics of open environments. Accordingly, a holistic approach is to be pursued here, which, however, should remain completely in the open source area and cover or supplement the goals of other tools.

Test tool Eclipse Titan

'Eclipse Titan' functions as the test tool for the Eclipse IoT testware. The Titan tool was originally developed by Ericsson as an in-house tool and has been freely available to all TTCN-3 users as open source software for several years now. Eclipse Titan serves the IoT testware as a central integration and execution environment for test cases described in TTCN-3. Ericsson has already developed implementations for test access points (so-called test ports) - including for the MQTT and CoAP protocols. These are used in the respective test suites.

IoT test methods

One of the most important tasks in IoT testing is the definition of suitable test suites. B. can be derived from user scenarios or requirements or put together from existing test cases. The access points of the test system components must be determined on the basis of the architecture of the systems or objects to be tested and the selected test objectives. For each test, a suitable division of the process sequence as well as its assignment to parallel test components that execute the defined test steps or simulate environmental behavior is required.

How exactly the IoT test methods are used depends on the respective test objects and objectives. Such test objects can, for. B. be:

  • Microcontroller
  • Protocol implementations
  • IoT gateways
  • Server in the cloud
  • End devices of the users as well as
  • IoT infrastructures and solutions.

After the test has been carried out, developers can trace the individual test cases back to the conformance statements from the standard. This gives developers not only the success rate, but also a direct reference to the respective conformance statements in the standard.

Holistic solution through the IoT testware

In the case of test tools that have existed to date, often only limited partial aspects are considered, which under certain circumstances do not lead to an adequate quality statement. The young IoT industry lacks a cost-effective and comprehensive solution, especially for SMEs and startups with limited capacities. It is important that it can quickly and reliably check and prove quality, security, scalability and interoperability.

Overall, the Eclipse IoT testware is intended to close existing gaps in quality testing for IoT devices or IoT solutions in order to enable them to be adequately certified. The currently developed conformity tests for MQTT and CoAP are only a beginning part. Another special feature of the IoT testware is that it is completely in the open source area.