Hierarchical IoT Device Management Architecture with Regional Autonomy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for managing IoT/M2M devices, especially those on moving machines like vehicles, face challenges in providing global management while allowing regional autonomy and adapting to diverse network environments, business rules, and hardware limitations.

Innovation Solution

A computer-implemented method and system for global device management architecture with regional autonomy, involving a master node, registration service module, and rules engine to assign and configure IoT devices to nodes based on device information, allowing for regional management and scalability across different clusters.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a centralized global management system is used for IoT devices, then global coordination and control are improved, but system complexity and latency increase

Engineering Contradiction:
Improveglobal coordinationVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the centralized management system into hierarchical segments: global master nodes, regional master nodes, and local domain nodes. Each level handles specific management functions, reducing the complexity burden on any single node while maintaining global coordination through the hierarchical structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a spatial dimension to device assignment by geographically distributing master nodes across different regions. Devices are assigned to regional master nodes based on their location, adding a geographic dimension to the management architecture that reduces latency and complexity for local operations.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Loss of time

If devices are assigned to regional nodes for local management, then latency is reduced and regional autonomy is improved, but global coordination becomes more difficult

Engineering Contradiction:
ImprovelatencyVSAvoidglobal coordination
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The hierarchical segmentation allows regional master nodes to independently manage local devices, reducing latency for regional operations. Simultaneously, global master nodes maintain oversight and coordination across all regions through the structured hierarchy, ensuring global reliability without sacrificing local responsiveness.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Regional master nodes act as intermediaries between local domain nodes and global master nodes. They handle local management tasks to reduce latency while maintaining communication channels with global nodes for coordination, effectively mediating between local autonomy and global control requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If a single global node manages all devices, then system simplicity is maintained, but scalability and adaptability to regional variations are limited

Engineering Contradiction:
Improvesystem simplicityVSAvoidregional adaptability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The system segments management functions across multiple hierarchical levels, allowing each segment to adapt to regional requirements while maintaining overall system simplicity through standardized interfaces and protocols. Regional nodes can be customized for local needs without complicating the global architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The hierarchical node structure provides universal functionality at each level that can adapt to different regional requirements. Master nodes and domain nodes can serve multiple purposes across different regions and device types, maintaining system simplicity while enhancing regional adaptability through configurable parameters and policies.

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

4Reliability

If devices are dynamically assigned to multiple nodes, then load balancing and reliability are improved, but assignment complexity and processing overhead increase

Engineering Contradiction:
Improveload distributionVSAvoidassignment complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The hierarchical segmentation naturally distributes device assignment complexity across multiple levels. Local domain nodes handle basic assignments, regional master nodes manage regional load balancing, and global master nodes coordinate overall distribution. This segmented approach improves reliability through load distribution while keeping assignment complexity manageable at each level.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a hierarchical dimension to device assignment, allowing devices to be assigned to multiple nodes across different levels (local, regional, global). This multi-dimensional assignment structure improves load distribution and reliability while the hierarchical organization keeps tracking and management complexity organized and manageable.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS11678181B2Global device management architecture for IoT devices with regional autonomy
Publication Date: 2023.06.13 AERIS COMM INC
  • US11678181B2 patent drawing
  • US11678181B2 patent drawing
  • US11678181B2 patent drawing

AI summary

A computer-implemented method and system for global device management architecture with regional autonomy for devices on a cellular network are disclosed. The computer implemented method for optimizing device management architecture for IoT devices includes providing device information to a server in a master node for registering a device with the master node; providing rules to assign the device to at least one node based on the device information; assigning the device to the at least one node in response to the rules; and automatically configuring the device to connect the device to the assigned node.