IoT Controller Protocol Translation for Ad-Hoc Device Compatibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing IoT devices lack self-adaptability to technology advancements, leading to compatibility issues and waste due to the inability of controllers to support new generation devices with advanced functions.

Innovation Solution

A structured device control/communication protocol (SDP) is pre-created for IoT devices, including an SDPID and SDPDEF information, allowing controllers to acquire and decode necessary control information, enabling interoperability and forward compatibility through SDP data storage and user interface tools.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional industrial standards (BLE, Wi-Fi, Z-Wave, Zigbee) with predefined protocols are used, then data security and interoperability across products from different vendors are maintained, but the system lacks self-adaptability to technology advancements and new innovations, creating compatibility frustration and waste

Engineering Contradiction:
ImproveinteroperabilityVSAvoidself-adaptability to technology advancements
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent applies preliminary action by pre-creating and registering device control/communication protocol information (SDP) before device deployment. The SDP database stores standardized protocol definitions that controllers can retrieve and use to automatically configure communication with new devices, eliminating the need for manual protocol programming and enabling forward compatibility without requiring controller updates.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary mechanism through the SDP database and controller interface that mediates between devices with different protocols and the controller. The SDP acts as a translation layer, allowing controllers to communicate with devices using various predefined protocols without requiring direct protocol implementation in the controller, thus maintaining interoperability while enabling adaptability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If new generation controlee devices with advanced functions are developed, then more advance applications are enabled, but existing controllers cannot support these new devices due to outdated protocol libraries

Engineering Contradiction:
Improvesupport for new generation devicesVSAvoidcontroller protocol library complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-creating and storing device control/communication protocol information (SDP) in a database before devices are deployed. When a new device is introduced, the controller simply retrieves the corresponding SDP data rather than requiring updates to the controller's internal protocol library, thus supporting new devices without increasing controller complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating a copy of protocol information (SDP) that is stored externally in the database. Instead of modifying the controller's original protocol library, the controller copies the necessary protocol definitions from the SDP database for each new device, allowing unlimited device types without increasing controller complexity.

Inventive Principle:
Principle #26Copying

3Stability of the object's composition

If controllers are programmed to support certain communication protocols to perform necessary functions, then backward compatibility is maintained, but the controller cannot support new generation devices with updated protocols

Engineering Contradiction:
Improvebackward compatibilityVSAvoidforward compatibility
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent applies preliminary action by pre-creating and storing protocol information (SDP) before devices are deployed. This allows the controller to maintain backward compatibility with existing devices while simultaneously being able to support new devices with updated protocols, as the SDP database contains protocol definitions for both legacy and new device types.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces universality by designing a universal controller interface that can handle multiple protocol types through a single standardized mechanism. The controller uses a universal SDP retrieval and execution framework that works for both old and new devices, making the controller multi-functional across different protocol versions without requiring separate handling mechanisms.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12568128B2System configuration and communication method to enable post acquired ability to control and communicate with ad-hoc devices
Publication Date: 2026.03.03 WONG HO YIN
  • US12568128B2 patent drawing
  • US12568128B2 patent drawing
  • US12568128B2 patent drawing

AI summary

The present disclosure provides a communication method, apparatus, device, and system, relating to the technical field of communications. During the communication between the controlee device and the control terminal, translation can be performed by the controller. As the SDP of the controlee device and the SDPID of the SDP are pre-created, the controller can translate all functions corresponding to the SDP to controller's native execution coding. When any functions need to be altered or any function needs to be added, it only needs to follow the same process to re-create a new SDP and the SDPID of the SDP, that is, functions of all devices can be re-defined in ad-hoc manner and the controller counterpart will accommodate on demand base on the very same mechanism. All these processes can be automatically conducted without user intervention or even awareness, from the user perspective, they never need to worry about the FW compatibility with their controller, all they need is to add “another” new controlee device into their system.