Data Deployment Service for Resource-Constrained IoT Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing solutions for delivering data objects to resource-constrained devices, such as microcontroller units (MCUs) and Internet of Things (IoT) devices, face challenges in efficiently managing data deployment due to limited resources and communication constraints, particularly in handling large data updates and ensuring data integrity.

Innovation Solution

A method and system that utilize a data deployment service to stream data objects in manageable blocks via a publish/subscribe messaging service, using services like data deployment manager, job scheduling, and delivery services, which configure and schedule data delivery, authenticate data, and utilize lightweight protocols like MQTT, ensuring data integrity and compatibility with device capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data objects are delivered to resource-constrained devices using traditional methods, then data delivery can be completed, but the devices experience resource exhaustion and communication buffer overflows due to limited memory and processing capabilities

Engineering Contradiction:
Improvedata delivery reliabilityVSAvoiddevice resource constraints
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments large data objects into smaller blocks that can be delivered incrementally to resource-constrained devices. Each block is independently manageable within the device's communication buffer limits, preventing resource exhaustion while maintaining reliable data delivery. The segmentation allows the device to process and store data in manageable chunks rather than requiring bulk memory allocation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary actions by pre-configuring delivery parameters, authentication credentials, and block delivery schedules before actual data transmission begins. This preliminary setup includes configuring the data deployment service with device capabilities, communication buffer sizes, and delivery group memberships, ensuring that the actual data delivery process can proceed without overwhelming device resources.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If large data objects are transmitted to devices with limited communication buffer size, then complete data delivery is achieved, but communication buffers overflow and data integrity is compromised

Engineering Contradiction:
Improvedata delivery volumeVSAvoiddata integrity
Core Design Contradiction:
Quantity of substanceVSManufacturing precision

Solution Approach 1:

The patent divides large data objects into smaller blocks that fit within the device's communication buffer constraints. Each block is delivered separately through the publish/subscribe messaging service, preventing buffer overflow while maintaining the ability to transmit large volumes of data cumulatively. The segmentation ensures that no single transmission exceeds buffer limits, preserving data integrity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements feedback mechanisms where the receiving device acknowledges successful block reception and the data deployment service tracks delivery status. This feedback loop ensures that data blocks are delivered in the correct sequence and allows for error detection and retransmission if data integrity is compromised, maintaining precision despite large data volumes.

Inventive Principle:
Principle #23Feedback

3Productivity

If data objects are delivered to large groups of devices simultaneously, then deployment efficiency is improved, but network overhead and service complexity increase

Engineering Contradiction:
Improvedeployment efficiencyVSAvoidservice complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent creates delivery groups that represent multiple devices with similar data delivery requirements. The data deployment service can simultaneously manage data delivery to entire delivery groups using unified configuration and authentication mechanisms. This universal approach allows efficient batch delivery to large device groups while abstracting the complexity of individual device management through group-level operations.

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

Solution Approach 2:

The patent introduces delivery groups as intermediary constructs between the data deployment service and individual devices. These groups act as mediators that simplify service complexity by allowing the service to target groups rather than managing each device individually. The publish/subscribe messaging service further mediates the actual data transmission, decoupling the deployment logic from individual device communication overhead.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If authentication is performed for each data object delivery, then data security is maintained, but processing time and device energy consumption increase

Engineering Contradiction:
Improvedata securityVSAvoidauthentication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs authentication preliminarily by establishing security credentials and authentication tokens before data delivery begins. Devices and the data deployment service authenticate each other in advance, and authentication context is cached for the duration of the data delivery session. This preliminary authentication maintains security while avoiding repeated authentication overhead during block-by-block data transmission.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3688588B1Receiving a data object at a device
Publication Date: 2022.06.22 AMAZON TECH INC
  • EP3688588B1 patent drawingFigure 1
  • EP3688588B1 patent drawingFigure 2
  • EP3688588B1 patent drawingFigure 3A

AI summary

A technology is provided for delivering a data object (114) to device (152). Data delivery instructions to distribute a data object (114) to a device (152) may be received at a delivery service (126) and include a storage location (112) of the data object (114), a messaging topic, and a size of data receivable by the device (152). The data object (114) is then divided into blocks corresponding to the size of data receivable by the device (152). A messaging topic is identified to which the device (152) is subscribed via a messaging service (130). The blocks are sent to the device (152) using the messaging topic and a network protocol installed on the device (152).