How does your device get into the Internet of Things (IoT) easily?

 The Standard System Design for Mobile Connectivity

Modern devices are supposed to be connected to the IoT (Internet of Things), to the cloud. On the one hand to query sensor data and operating states centrally to allow for e.g. remote service, planning of maintenance and planned refilling of consumables. On the other hand, the devices should also be configured, controlled and maintained locally with a smartphone or tablet.

Many of these devices contain a controller which is deeply embedded, i.e. consists of printed circuit boards and not of off-the-shelf control components. The effort to implement all IoT-functions and especially the IoT-interfaces can be considerable. This is especially true since these control systems are usually very resource-limited (cost, energy consumption/cooling, space, processing power...).

Since the interfaces and the basic functions are the same for almost all applications and customers, we have developed a Standard System Design that greatly shortens the development of IoT functionality. It is not intended to be a "one size fits all" solution, but it is so flexible that it can be adapted with little effort for many "deeply embedded" IoT and M2M (Machine-To-Machine communication) tasks.

The specific part for your application we implement based on this Standard System Design. This custom part consists of software and hardware in the embedded system plus of the applications for the cloud, the PC and the mobile.

Since you get the sources and schematics of the whole project, there are no dependencies, no "vendor lock-in".

Realize your IoT system fast and efficiently, based on our standard building blocks for hardware and software.

Contact us for more information!

Fields of Application

  • Asset tracking
  • Sensors/ control
  • Preventive maintenance

Functionality

See also above drawing: dark part

  • Communication with the Internet/ the cloud:

    • on the road and outdoors via cellular mobile
    • in closed buildings via Wireless LAN

  • Communication with the local operator

    • for data: Bluetooth
    • for identification/security: NFC

  • Location by satellite navigation

The non-functional requirements that the design fulfills are also important. These are often the larger limitation than the functional aspects:

  • Data security (identification/encryption)

    • built-in hardware secure element (Root of Trust)
    • secure processor/ system on chip

  • Power supply

    • Lithium batteries (industrial temperature range -30..85°C)
    • wireless charging
    • low power for long service life and easy cooling (especially the communication modules can have a significant power consumption and corresponding cooling requirements)

  • Secure software updates via the Internet, secure boot of the controller
  • Protcols:

    • MQTT (Message Queuing Telemetry Transport)/ AMQP (Advanced Message Queuing Protocol)
    • CoAP (Constrained Application Protocol)

Technologies

This Standard System Design is based on the following technologies:

Contact us for more information!

Let us discuss your idea/ your project