Software Update State Determination via Unique Code Matching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software updates on computing devices are often hindered by limited bandwidth and computing power, leading to time-consuming and costly transmission and processing, as well as potential incompatibility issues that can render devices non-functional.

Innovation Solution

A method and apparatus that determine the state of a computing device by generating unique codes for resident files and comparing them to reference codes for update files, allowing for efficient software updates by identifying compatible states and reducing unnecessary data transfer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the old software is completely deleted before installing the new version, then the new software can be installed cleanly, but the bandwidth required for transmitting the new software increases significantly

Engineering Contradiction:
Improvesoftware installation reliabilityVSAvoiddata transmission volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts only the necessary components for software update by using unique codes to identify specific files that need updating. Instead of transmitting entire software packages, the system transmits only the minimal required update data corresponding to files with mismatched unique codes, thereby reducing data transmission volume while maintaining installation reliability

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs preliminary determination of the computing device's state by comparing unique codes of resident files with reference codes before initiating software update transmission. This preliminary action identifies exactly which files need updating, allowing the system to prepare and transmit only the necessary update data, avoiding unnecessary bandwidth consumption

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the entire new software version is transmitted to the computing device, then complete software update is achieved, but the transmission time becomes excessively long

Engineering Contradiction:
Improvesoftware update completenessVSAvoidsoftware update time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system extracts and transmits only the specific file updates needed rather than the entire software version. By using unique codes to identify which files require updating, the patent reduces transmission time while ensuring that all necessary updates are applied for complete software update achievement

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by transmitting only the portion of software data that is actually needed for updating files with mismatched unique codes. This partial transmission approach achieves complete software update functionality while minimizing transmission time by avoiding unnecessary data transfer

Inventive Principle:
Principle #16Partial or excessive action

3Ease of operation

If software update is transmitted over wireless network, then mobility is maintained, but the cost per megabyte of data transmission increases

Engineering Contradiction:
Improvedevice mobilityVSAvoiddata transmission cost
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential update files identified by unique code mismatches and transmits minimal data over the wireless network. This approach maintains device mobility and wireless convenience while reducing data transmission volume, thereby lowering per-megabyte costs associated with wireless data plans

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary state determination by comparing unique codes before initiating wireless transmission. This preliminary identification of required updates allows the system to transmit only necessary data over the expensive wireless network, minimizing data transmission cost while maintaining the ease of wireless operation

Inventive Principle:
Principle #10Preliminary action

4Reliability

If the computing device processes complete uninstallation and installation of software, then software compatibility is ensured, but the computing power required increases

Engineering Contradiction:
Improvesoftware compatibilityVSAvoidcomputing device processing power
Core Design Contradiction:
ReliabilityVSPower

Solution Approach 1:

The patent extracts only the specific files that need updating by comparing unique codes, rather than requiring complete uninstallation and reinstallation. This selective update approach reduces the computing power burden on mobile devices while maintaining software compatibility through precise file-level updates

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary comparison of unique codes to determine the exact state of the computing device and identify which files need updating. This preliminary analysis reduces the processing burden by avoiding unnecessary uninstallation and reinstallation operations, thereby reducing power consumption while ensuring compatibility through targeted updates

Inventive Principle:
Principle #10Preliminary action

5Ease of manufacture

If software update is transmitted through a synchronization process via another computing device, then network infrastructure requirements are reduced, but the bandwidth of the intermediate device becomes a bottleneck

Engineering Contradiction:
Improvenetwork infrastructure simplicityVSAvoidsoftware update transmission speed
Core Design Contradiction:
Ease of manufactureVSSpeed

Solution Approach 1:

The patent extracts and transmits only the minimal required update data identified by unique code comparisons, rather than transmitting complete software versions. This reduces the bandwidth burden on intermediate computing devices used for synchronization, improving transmission speed while maintaining the simplicity of using existing devices as relays

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8271969B2Method and apparatus for determining the state of a computing device
Publication Date: 2012.09.18 MALIKIE INNOVATIONS LTD
  • US8271969B2 patent drawing
  • US8271969B2 patent drawing
  • US8271969B2 patent drawing

AI summary

According to embodiments described in the specification, a method and apparatus, for determining the state of a computing device is described, by first determining at least one unique code associated with at least one file resident on the computing device, the at least one unique code representative of a state of the at least one file. Then at least one unique reference code associated with at least one update file is determined, the at least one update file for updating said at least one file resident on the computing device, and the at least one unique reference code representative of an expected state of the at least one file resident on the computing device. Finally, the state of the computing device is determined to be in an expected state if the at least one unique code matches the at least one unique reference code, and in an unexpected state if the at least one unique code does not match the at least one unique reference code.