OTA Update Monitoring for Device Version and Risk Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manufacturers face challenges in updating Internet-connected devices post-manufacture, and there is a lack of efficient methods to track device attributes and settings changes, leading to inefficiencies and security vulnerabilities.

Innovation Solution

A network-based system and method for monitoring over-the-air software updates, utilizing an update monitoring computer device to track device versions and settings, determine risk profiles, and adjust insurance quotes based on these updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If over-the-air updates are implemented for Internet-connected devices, then device software can be remotely updated to fix bugs, add features, and update security, but it becomes difficult to track which device attributes and settings are being used

Engineering Contradiction:
Improvesoftware update capabilityVSAvoiddevice attribute tracking
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The system implements feedback by having devices periodically report their version and setting information to the monitoring server. This creates a closed-loop information flow where the server can track device attributes and settings changes after over-the-air updates are applied, resolving the contradiction between enabling remote updates and maintaining attribute visibility.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The update monitoring server acts as an intermediary between the device manufacturer and the end-user devices. It collects, stores, and analyzes version and setting information from devices, providing a centralized point for tracking device attributes without requiring direct manufacturer-device communication for each update check.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple device modes and options are allowed for user selection, then device functionality and adaptability are improved, but monitoring and tracking which options are being used becomes more complex

Engineering Contradiction:
Improvedevice mode selectionVSAvoidmonitoring system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The monitoring server implements a universal tracking mechanism that handles multiple device modes and options through a single standardized interface. By using consistent data structures and monitoring protocols that work across different device types and configurations, the system can track various user-selected options without proportionally increasing complexity.

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

3Ease of manufacture

If conventional techniques are used for device updates, then implementation is simpler, but inefficiencies and security vulnerabilities arise

Engineering Contradiction:
Improveupdate implementation simplicityVSAvoidsecurity and efficiency
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The system performs preliminary actions by having devices check for updates and report their current state before actual update installation. The monitoring server pre-evaluates update requirements and prepares version information in advance, allowing for more secure and efficient update deployment while maintaining relative simplicity in the implementation process.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12511111B1Systems and methods for advanced over-the-air software updates
Publication Date: 2025.12.30 STATE FARM MUTAL AUTOMOBILE INSURANCE COMPANY
  • US12511111B1 patent drawing
  • US12511111B1 patent drawing
  • US12511111B1 patent drawing

AI summary

A system for controlling over-the-air updates for a device (i) stores a plurality of version and setting information for plurality of devices; (ii) receives version and setting information for the first device of the plurality of devices; (iii) stores the version and setting information for the first device; (iv) determines a risk profile for the first device based upon the corresponding version and setting information; and (v) determines an insurance quote based upon the risk profile for the first device.