IoT Connectivity Module for Legacy Device Retrofitting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing IoT devices without native IP connectivity require complex and costly modifications to add connectivity modules, involving hardware and software redesign, custom manufacturing processes, and intricate ID provisioning, which complicates manufacturing and assembly.
Innovation Solution
A method and system that provide IoT functionality by using a connectivity module with pre-loaded machine-to-machine credentials and a non-electronic label for wireless access, allowing devices to connect to the Internet without modifying the legacy electronics, using a data proxy module to transmit data between the connectivity module and the device's communication bus, and simplifying ID provisioning through cloud-based inventory databases.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If an add-on connectivity module is added to a legacy device, then Internet connectivity capability is improved, but device complexity and manufacturing complexity increase
Solution Approach 1:
The patent implements a universal connectivity module that can interface with multiple different legacy devices through a standardized communication bus (I2C, SPI, UART). The module contains a data proxy that can adapt to different device data models and protocols, eliminating the need for custom connectivity modules for each device type. This universal approach reduces device complexity while maintaining adaptability across different legacy devices.
Solution Approach 2:
The connectivity module acts as an intermediary between the legacy device and the Internet. It includes a data proxy that mediates communication by translating between the legacy device's native protocol and standard Internet protocols. This intermediary layer simplifies integration by handling all complexity within the connectivity module itself, preventing it from propagating to the legacy device.
2Adaptability or versatility
If custom hardware and software modifications are made to the legacy electronic module, then connectivity capability is improved, but ease of manufacture and assembly are worsened
Solution Approach 1:
The patent segments the connectivity functionality into a separate, standalone module that does not require integration into the legacy electronic module. The connectivity module is a discrete component that can be manufactured independently and then simply connected to the legacy device via a standard communication bus. This segmentation eliminates the need for complex hardware modifications to the legacy device, greatly simplifying manufacturing and assembly processes.
Solution Approach 2:
Instead of modifying the legacy device's hardware architecture, the patent uses a software-based data proxy that copies and translates communication protocols. The data proxy emulates standard communication interfaces while maintaining compatibility with the legacy device's native protocol, avoiding the need for physical hardware modifications and simplifying manufacturing.
3Adaptability or versatility
If device-specific data models and protocols are implemented in the connectivity module, then communication compatibility is improved, but manufacturing complexity and ID provisioning complexity increase
Solution Approach 1:
The data proxy in the connectivity module is designed to be dynamic and configurable rather than hard-coded for specific device protocols. It can adapt its behavior based on the connected legacy device's data model and protocol requirements. This dynamic approach allows a single connectivity module design to support multiple different device types without requiring manufacturing complexity to increase, as the adaptability is achieved through software configuration rather than hardware customization.
4Reliability
If complex ID provisioning and authentication procedures are implemented, then security and device identification are improved, but ease of operation and activation complexity increase
Solution Approach 1:
The connectivity module is designed to perform self-provisioning and self-authentication with backend servers. It automatically manages its own credentials, registers itself with the appropriate servers, and establishes secure connections without requiring manual configuration or complex activation procedures. This self-service capability maintains strong security while greatly simplifying the user activation process, as the system handles the complexity automatically in the background.
Data Source
AI summary
A method for providing an IoT functionality to a device, the method comprising manufacturing the device by: providing a connectivity module with a register comprising data related to machine-to-machine (M2M) credentials and comprising: a unique client identifier (Client ID), an authentication identifier (Authentication ID) related to a unique pair of public/private encryption keys, a wireless client access point identifier (miniAP SSID) and a wireless encryption key (miniAP WPA, WPA2); providing a non-electronic label associated with the connectivity module and comprising the wireless client access point Identifier (miniAP SSID) and the wireless encryption key (miniAP WPA, WPA2); providing an electronic module having a device serial number (Device ID S/N); providing a non-electronic label associated with the electronic module and comprising an activation code unique for the device; assembling the device by connecting the electronic module with the connectivity module; and providing a package comprising the device and the non-electronic labels.