Mobile Configuration Difference Files for Low-Bandwidth Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Low bandwidth wireless connections, such as land mobile radio (LMR) connections, pose challenges in transmitting large configuration files due to high resource consumption and long transmission times, necessitating more efficient methods to update mobile device configurations.

Innovation Solution

A system that generates a difference file by comparing legacy and updated configuration files, identifying matching blocks and generating update data objects based on payload differences, which are then transmitted to mobile devices for efficient configuration updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a full configuration file is transmitted over a low bandwidth LMR connection, then the mobile device receives complete configuration data, but transmission time and bandwidth consumption increase significantly

Engineering Contradiction:
Improveconfiguration update completenessVSAvoidtransmission time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts only the changed portions (difference data) from the full configuration file and transmits only these extracted differences over the LMR connection. This is achieved by comparing the legacy configuration file with the updated configuration file, identifying modified blocks, and transmitting only these difference blocks to the mobile device, thereby significantly reducing transmission time while maintaining configuration update completeness.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The configuration file is segmented into multiple blocks, and only the changed blocks are identified and transmitted as difference data. The system divides the large configuration file into manageable segments (blocks), compares them between legacy and updated versions, and transmits only the segmented differences rather than the entire file, reducing overall transmission time.

Inventive Principle:
Principle #1Segmentation

2Reliability

If a full configuration file is transmitted over a low bandwidth LMR connection, then the mobile device receives complete configuration data, but bandwidth consumption increases significantly

Engineering Contradiction:
Improveconfiguration update completenessVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system extracts and transmits only the difference data representing changed configuration blocks rather than the complete configuration file. By extracting only the necessary update portions and transmitting these minimal differences over the LMR connection, bandwidth consumption is significantly reduced while ensuring the mobile device receives complete configuration updates.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The configuration file is divided into blocks, and only the segmented difference blocks that contain changes are transmitted. This segmentation approach allows the system to send only the necessary portions of configuration data, reducing the quantity of data transmitted over the limited bandwidth LMR connection.

Inventive Principle:
Principle #1Segmentation

3Reliability

If a full configuration file is transmitted over a low bandwidth LMR connection, then the mobile device receives complete configuration data, but energy consumption increases

Engineering Contradiction:
Improveconfiguration update completenessVSAvoidenergy consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system extracts and transmits only the difference data representing configuration changes rather than the complete configuration file. This extraction of minimal difference data reduces the transmission energy required by mobile devices communicating over LMR connections, as less data needs to be transmitted and processed while maintaining complete configuration update reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

By segmenting the configuration file into blocks and transmitting only the changed segments, the system reduces the total energy consumption associated with data transmission and processing on mobile devices.

Inventive Principle:
Principle #1Segmentation

4Reliability

If a full configuration file is transmitted over a low bandwidth LMR connection, then the mobile device receives complete configuration data, but coexistence with voice traffic deteriorates

Engineering Contradiction:
Improveconfiguration update completenessVSAvoidinterference with voice traffic
Core Design Contradiction:
ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The system extracts and transmits only the difference data representing configuration changes, significantly reducing the data volume transmitted over the LMR connection. This reduction in transmitted data minimizes interference with concurrent voice traffic, allowing configuration updates to coexist harmoniously with voice communications on the same low bandwidth channel.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

By segmenting the configuration file and transmitting only the changed blocks, the system reduces the overall transmission burden on the LMR connection, thereby reducing harmful interference with voice traffic and improving coexistence between data and voice communications.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12625700B2Differential configuration updates for mobile devices
Publication Date: 2026.05.12 MOTOROLA SOLUTIONS INC
  • US12625700B2 patent drawing
  • US12625700B2 patent drawing
  • US12625700B2 patent drawing

AI summary

A system includes memory hardware configured to store instructions and processing hardware configured to execute the instructions. The instructions include loading a legacy configuration file including a plurality of legacy blocks and loading an updated configuration file including a plurality of updated blocks. The instructions include, for each updated block, identifying one legacy block from the plurality of legacy blocks having a same type as the updated block and a payload representing a nearest match to a payload of the updated block and generating an update data object based on an identifier of the legacy block and an identifier of the updated block and adding the update data object to a difference file in response to the identified one legacy block and the updated block having matching payloads but different identifiers. The instructions include transmitting the difference file to a mobile device via a radio network to update the device.