IoT Service Duplicate Device ID Management

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing IoT systems face issues with managing duplicate device identifiers for edge devices using radio communication protocols, leading to undesirable rejection of legitimate requests for device registration or network testing due to pre-registered IDs.

Innovation Solution

Implementing an IoT service that manages duplicate device identifiers by using a device manager to process join and provision requests, accepting requests based on a soft limit for the number of registered devices with duplicate IDs, and maintaining an exclusion list for popular testing IDs, allowing for flexible registration and testing without errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the service provider rejects join requests with duplicate device IDs to maintain unique identification, then device ID uniqueness is preserved, but legitimate testing requests and device registrations are incorrectly rejected

Engineering Contradiction:

Improvedevice ID uniquenessVSAvoidtesting environment flexibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the device ID validation process by introducing a duplicate detection mechanism that identifies and handles duplicate device IDs separately. This allows the system to maintain uniqueness for normal devices while creating a special pathway for testing devices, thus resolving the contradiction between maintaining uniqueness and allowing flexible testing.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism (duplicate device ID detection and handling logic) that mediates between the strict uniqueness requirement and the flexible testing requirement. This intermediary layer allows the system to accept duplicate IDs for testing purposes while maintaining the uniqueness guarantee for production devices.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the service provider accepts all join requests including duplicates to allow testing, then testing flexibility is improved, but processing overload from duplicate IDs occurs

Engineering Contradiction:

Improvetesting environment flexibilityVSAvoidrequest processing efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent applies preliminary action by detecting and handling duplicate device IDs before they enter the main processing queue. By identifying duplicates in advance and routing them through a specialized handling path, the system prevents processing overload while still allowing testing flexibility.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces dynamic handling of device ID validation by adjusting the strictness of duplicate checking based on the request type. For testing requests, the system dynamically allows duplicates, while for production requests, it maintains strict uniqueness, thus optimizing processing efficiency under different conditions.

Inventive Principle:

Principle #15Dynamics

3Reliability

If the service provider implements strict duplicate ID rejection to maintain data integrity, then data integrity is preserved, but the number of rejected legitimate requests increases

Engineering Contradiction:

Improvedata integrityVSAvoiddevice registration simplicity

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent segments the device registration process into two distinct pathways: one for production devices with strict duplicate checking to maintain data integrity, and another for testing devices that allows duplicates. This segmentation preserves data integrity for production while simplifying testing operations.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent changes the validation parameter (duplicate ID checking strictness) based on the device type. For testing devices, the parameter is relaxed to allow duplicates, while for production devices, it remains strict to preserve data integrity. This parameter adjustment resolves the contradiction between integrity and operational simplicity.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS11882517B1Managing duplicate device identifiers for edge devices of client networks that use a radio communication protocol

Publication Date: 2024.01.23 AMAZON TECH INC

AI summary

An IoT service of a provider network may be used to provision edge devices with duplicate device identifiers for edge devices that use a radio communication protocol (e.g., LoRaWAN). This may allow a service provider to accept legitimate registration requests from edge devices instead of automatically rejecting them. When the IoT service receives a registration request, the service determines whether there are other devices registered with the same device ID. If so, then the service determines whether to accept or reject the request. For example, the service may determine whether the number of duplicate device IDs being used for registered devices will remain within a predefined threshold if the device is registered. If so, then the service registers the device. Otherwise, the service rejects the request.