IoT Device Registration via Pre-configured Network Credentials

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for registering customized devices in the Internet of Things (IoT) require users to manually input network access data, such as SSID and password, which is inconvenient and inefficient, leading to low registration efficiency.

Innovation Solution

A method that involves receiving a device type identifier, network access data, and a user identifier corresponding to an order identifier, obtaining an allocated device serial number, and writing this information into a customized device, allowing automatic network access and registration upon connection, with a server processing device registration requests based on these identifiers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual network access data entry is required for device registration, then users can establish device control, but the registration process becomes inconvenient and inefficient

Engineering Contradiction:
Improvedevice registration convenienceVSAvoidregistration time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system pre-configures network access data (SSID, password) and device identifiers (serial number, device type identifier) in the controlled device during manufacturing or initial setup. This preliminary configuration eliminates the need for users to manually enter network credentials during registration, directly resolving the contradiction by making registration convenient and fast

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The controlled device autonomously provides its own network access data and identification information to the terminal device during the registration process. The device self-services by automatically transmitting pre-configured credentials, eliminating manual user input and significantly reducing registration time while improving convenience

Inventive Principle:
Principle #25Self-service

2Productivity

If automatic network access is implemented through pre-configured data, then registration efficiency improves, but device complexity increases

Engineering Contradiction:
Improvedevice registration efficiencyVSAvoiddevice configuration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

All complex configuration data including network access credentials (SSID, password) and device identifiers (serial number, device type identifier) are pre-configured during manufacturing. This shifts the complexity from the registration phase to the manufacturing phase, enabling automatic fast registration without increasing end-user device complexity

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent extracts the complex configuration process from the device registration flow and places it in the manufacturing/setup phase. By separating configuration complexity from operational simplicity, the system achieves high registration efficiency without making the end-device complex for users

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11887176B2Method for registering customized device, server, and terminal
Publication Date: 2024.01.30 TENCENT TECHNOLOGY (SHENZHEN) CO LTD
  • US11887176B2 patent drawing
  • US11887176B2 patent drawing
  • US11887176B2 patent drawing

AI summary

A method is provided. The method includes receiving a device type identifier, network access data, and a user identifier that correspond to an order identifier from a terminal. An allocated device serial number corresponding to the order identifier is obtained, the device type identifier, the device serial number, the network access data being written into a customized controlled device. The customized controlled device that is identified by the allocated device serial number and the device type identifier is connected to. A device registration request is received from the terminal and, in response to receiving the device registration request, device registration is performed based on the device type identifier, the allocated device serial number, and the user identifier.