IoT Controller–Controlee Registration via C2C Proof of Possession

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing smart home devices face compatibility issues due to the lack of standardized communication protocols, leading to difficulties in seamless integration and operation across different IoT platforms, and current commissioning methods are cumbersome and prone to security threats.

Innovation Solution

A method for setting commissioning between an IoT controller and an IoT controlee using a cloud-to-cloud (C2C) connection, involving a proof-of-possession procedure to confirm the local presence of the IoT controlee and prevent unauthorized devices, utilizing a shorter numeric code for secure device registration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional commissioning methods are used for IoT devices, then device registration can be completed, but security vulnerabilities increase and user input errors occur

Engineering Contradiction:
Improvecommissioning securityVSAvoidcommissioning complexity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces a cloud server as an intermediary between the controller and controlee devices. The cloud server facilitates the commissioning process by receiving device information from the controller, generating QR codes, and enabling secure verification without requiring direct complex interactions between end devices, thus improving security while maintaining ease of operation

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements preliminary actions by having the controller discover and register the controlee device with the cloud server before actual commissioning. The cloud server pre-generates QR codes and verification information, so that when the user scans the QR code, the commissioning process is already prepared and streamlined, reducing both complexity and potential errors

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If cloud-to-cloud connection is implemented for device commissioning, then security is enhanced and compatibility is improved, but system complexity increases

Engineering Contradiction:
Improvedevice compatibilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The cloud server is designed as a universal platform that handles multiple functions: device registration, QR code generation, verification, and commissioning coordination. This multi-functional approach allows different IoT devices from various manufacturers to be commissioned through a single standardized interface, improving compatibility without requiring each device to implement complex individual solutions

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

Solution Approach 2:

The cloud server acts as a central intermediary that abstracts the complexity of device-to-device communication. Instead of implementing complex direct C2C connection logic in each IoT device, the cloud server mediates all commissioning interactions, simplifying the device architecture while enabling secure cloud-to-cloud verification

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12418424B2Method and apparatus for setting registration between IoT controller and IoT controlee on basis of C2C connection in wireless LAN system of smart home environment
Publication Date: 2025.09.16 LG ELECTRONICS INC
  • US12418424B2 patent drawing
  • US12418424B2 patent drawing
  • US12418424B2 patent drawing

AI summary

Proposed are a method and an apparatus for setting the registration between an IoT controller and IoT controlee on the basis of a C2C connection in a wireless LAN system of a smart home environment. Particularly, the controlee receives detection information about the controlee from the controller. The controlee transmits a challenge request message for requesting the first information from the controller. The controlee receives a challenge response message including the first information from the controller. The controlee transmits a challenge confirm message to the controller.