Distributed Device Association for Scalable IoT Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Maintaining device association data in IoT networks is costly and difficult to scale, and the data can become misaligned during transfer or storage, posing challenges in authorization and communication between devices.

Innovation Solution

A distributed database system utilizing blockchain-type data management techniques to manage device associations, ensuring secure and scalable peer-to-peer communication by using a decentralized database with blockchain technology to record and verify device associations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a centralized database is used to store device association data, then device associations can be managed, but the system becomes costly and difficult to scale

Engineering Contradiction:
Improvedevice association managementVSAvoidsystem scalability
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the centralized database into multiple distributed nodes across the network. Each node maintains a copy of the device association data, eliminating the single-point bottleneck and enabling horizontal scaling as devices are added to the network.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a distributed ledger as an intermediary mechanism that mediates device association verification. Instead of querying a centralized database, devices verify associations through the immutable ledger, reducing central coordination overhead and improving scalability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If device association data is stored centrally, then authorization can be performed, but data may become misaligned during transfer or storage

Engineering Contradiction:
Improveauthorization accuracyVSAvoiddata alignment
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent performs preliminary hashing of device association data before storage in the distributed ledger. This pre-processing ensures data integrity is established upfront, preventing misalignment during subsequent transfers or storage operations across the distributed network.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements cryptographic hashing and digital signatures that provide feedback mechanisms for verifying data integrity. Each device can verify the authenticity and alignment of association data through cryptographic validation, ensuring authorization accuracy across the distributed system.

Inventive Principle:
Principle #23Feedback

3Reliability

If a centralized authority manages device associations, then authorization decisions can be made, but the system incurs high costs

Engineering Contradiction:
Improveauthorization controlVSAvoidoperational cost
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent enables devices to autonomously verify associations through the distributed ledger without requiring centralized authority intervention. Each device independently validates cryptographic proofs and association data, eliminating the operational costs associated with centralized management while maintaining authorization control.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12531848B2Systems and methods for managing device association
Publication Date: 2026.01.20 COMCAST CABLE COMM LLC
  • US12531848B2 patent drawing
  • US12531848B2 patent drawing
  • US12531848B2 patent drawing

AI summary

A method and system for managing device association and access is disclosed. Some embodiments may include receiving, from a user device, a request to access a network device. The request may include a public key of the user device. The request may include a digital certificate, wherein the digital certificate may include the public key of the user device. A distributed database address of the user device may be determined by applying a deterministic function to the public key of the user device. A distributed database entry may include the address of the user device. A distributed database entry may be generated. The distributed database entry may include the address of the user device. Based on the address of the user device, access to the network device may be granted to the user device.