IoT Hub Device Registration via Intermediary Mediator

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

IoT devices with limited computing power and memory face challenges in secure service registration and firmware updates, requiring efficient administrative processes to expand their functionality and reduce processing and signaling overhead.

Innovation Solution

A hub device acts as an intermediary, providing increased computing power and memory to assist IoT devices with secure service registration and firmware updates, using registration API functions to create IoT objects and manage device connections, thereby reducing the administrative burden on IoT devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If IoT devices perform secure service registration and firmware updates independently, then security and functionality are maintained, but processing overhead and signaling complexity increase significantly

Engineering Contradiction:
Improvesecure service registrationVSAvoidprocessing and signaling overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a hub device as an intermediary between IoT devices and the cloud service. The hub performs service registration, firmware update management, and other administrative functions on behalf of IoT devices. This reduces the processing and signaling overhead for resource-constrained IoT devices while maintaining security through cryptographic operations performed by the hub using credentials obtained during initial registration.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If IoT devices have limited computing power and memory, then device cost and power consumption are reduced, but administrative task performance deteriorates

Engineering Contradiction:
Improveadministrative task performanceVSAvoiddevice computing power
Core Design Contradiction:
ProductivityVSPower

Solution Approach 1:

The hub device serves as a powerful intermediary that performs computationally intensive administrative tasks such as service registration, firmware update validation, and security credential management. IoT devices with limited computing power can rely on the hub to handle these tasks, thereby achieving high administrative task performance without requiring significant local computing resources.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The hub device performs service registration and obtains security credentials in advance during initial device provisioning. This preliminary action allows the hub to cache authentication tokens and registration information, enabling subsequent firmware updates and administrative operations to proceed with minimal real-time processing requirements for both the hub and IoT devices.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If multiple IoT devices register individually with the IoT service, then device autonomy is maintained, but registration efficiency and scalability deteriorate

Engineering Contradiction:
Improveregistration efficiencyVSAvoiddevice autonomy
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent enables multiple IoT devices to be registered and managed collectively through a single hub device. The hub performs bulk service registration for multiple devices, obtaining security credentials that can be distributed to all connected IoT devices. This merging approach dramatically improves registration efficiency and scalability compared to individual device registration, while the hub maintains the ability to manage each device independently when needed.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS10979299B1Internet of things (IoT) device registration
Publication Date: 2021.04.13 AMAZON TECH INC
  • US10979299B1 patent drawing
  • US10979299B1 patent drawing
  • US10979299B1 patent drawing

AI summary

Technology is described for registering Internet of Things (IoT) devices. A hub device may receive a request for hub registration from an IoT device. The request for hub registration may include IoT device information. The hub device may validate the request for hub registration at the hub device based on the IoT device information. The hub device may retrieve registration information from an IoT service. The registration information may include a dedicated security certificate for the IoT device. The hub device may forward the registration information to the IoT device to enable the IoT device to communicate IoT device data to the IoT service.