Geo-replicated IoT Hub Failover via Quorum-Based Ownership Transfer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing IoT systems face challenges in ensuring high availability and fault tolerance due to reliance on a single IoT hub, which can lead to operational failures and inefficiencies, especially in managing data consistency and connectivity across geographical regions.

Innovation Solution

Deploying multiple, independently-operated geo-replicated IoT hubs across various geographical regions allows IoT devices to seamlessly switch between hubs, ensuring that failure of one hub does not affect others, with data synchronization and ownership responsibilities managed to maintain high availability and low latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single IoT hub is used, then the system structure is simple, but the availability and fault tolerance are poor

Engineering Contradiction:
ImproveavailabilityVSAvoidsystem structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system is segmented into multiple independent geo-replicated IoT hubs distributed across different geographical regions. Each hub operates independently and can serve IoT devices in its region, eliminating the single point of failure. This segmentation directly improves availability while the modular nature keeps each individual hub relatively simple.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system changes the parameter of hub quantity from one to multiple, and introduces geographical distribution as a new parameter. This transformation fundamentally improves reliability and fault tolerance, as failures in one region do not affect other regions, while maintaining manageable complexity through standardized hub designs.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If multiple geo-replicated IoT hubs are deployed, then the availability and fault tolerance are improved, but the data consistency management becomes more complex

Engineering Contradiction:
Improvefault toleranceVSAvoiddata synchronization
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system creates copies of the IoT hub infrastructure across multiple geographical regions. Each hub maintains local data and can operate independently, while data synchronization mechanisms ensure consistency. This copying approach improves fault tolerance by providing redundant copies, while the standardized copy mechanism simplifies data consistency management compared to building custom synchronization solutions.

Inventive Principle:
Principle #26Copying

3Reliability

If data is synchronized synchronously across geo-replicated hubs, then data consistency is improved, but the latency increases

Engineering Contradiction:
Improvedata consistencyVSAvoidlatency
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The system dynamically adjusts the data synchronization mode between synchronous and asynchronous based on requirements. For critical data requiring high consistency, synchronous replication is used. For non-critical data or scenarios where latency is more important, asynchronous replication is employed. This dynamic approach allows the system to optimize the trade-off between data consistency and latency for different data types and operational contexts.

Inventive Principle:
Principle #15Dynamics

4Reliability

If IoT devices switch between geo-replicated hubs, then the service availability is improved, but the ownership management complexity increases

Engineering Contradiction:
Improveservice availabilityVSAvoidownership switching
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements feedback mechanisms where IoT hubs continuously monitor each other's status and availability. When a hub detects that another hub is available and appropriate for serving a particular IoT device (based on geographical location, load, or failure status), it triggers an ownership transfer. This feedback-driven approach automates the ownership switching process, improving service availability while reducing the complexity of manual management through intelligent, event-based transitions.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP3884648B1Geo-replicated IoT hub
Publication Date: 2023.07.12 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP3884648B1 patent drawingFigure 1
  • EP3884648B1 patent drawingFigure 2
  • EP3884648B1 patent drawingFigure 3

AI summary

Multiple geo-replicated and independent IoT (Internet of Things) hubs configured as servers with storage capacities are utilized and span across various regions in the world, to each of which IoT devices can connect and transmit telemetry data. The IoT devices, configured with sensors to generate telemetry data (e.g., temperature, pressure, etc.), can fail over to another geo-replicated IoT hub (the "target geo-replicated IoT hub") when one IoT hub experiences technical failures or the IoT device changes location to a region which is covered by the target IoT hub. Upon receiving a connection request from the IoT device, the target geo-replicated IoT hub submits a proposal to available geo-replicated IoT hubs for ownership over the IoT device, that is, receive data from and transmit messages to the IoT device. A quorum is sought so that all IoT hubs are in agreement as to a current owner of the IoT device.