Application Metadata Hardware Constraint Evaluation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The lack of coordination between application versions and driver packages in remote application stores leads to issues such as non-functioning applications and operating system crashes, as hardware support applications are not easily migrated or updated, resulting in sloppy development practices and compatibility problems.

Innovation Solution

Incorporating additional application metadata in remote application stores that identifies hardware constraints, such as required operating systems, driver versions, and driver dates, to ensure that applications are only installed when compatible with the computer device's hardware, thereby mitigating non-functioning applications and operating system crashes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If applications are packaged and installed with drivers in remote application stores, then applications can be distributed and updated, but coordination between application versions and driver packages becomes difficult, leading to compatibility issues

Engineering Contradiction:
Improveapplication distribution and update efficiencyVSAvoidapplication-driver compatibility
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary evaluation of hardware constraints against available applications before installation occurs. The operating system checks whether the computer device meets the hardware requirements of applications before allowing installation, preventing compatibility issues from arising in the first place.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system establishes a feedback mechanism where the operating system continuously monitors hardware constraints and provides feedback to the application selection process. This ensures that only applications compatible with the device's hardware are selected for installation, maintaining reliability while enabling efficient distribution.

Inventive Principle:
Principle #23Feedback

2Productivity

If applications are updated without coordinated driver package updates, then application updates can be deployed quickly, but non-functioning applications and operating system crashes occur

Engineering Contradiction:
Improveapplication update deployment speedVSAvoidsystem stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

Before allowing an application update, the system performs preliminary evaluation to ensure the updated application's hardware constraints are satisfied by the current driver packages. This preliminary check prevents incompatible updates from being installed, maintaining system stability while enabling rapid deployment of compatible updates.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The operating system acts as an intermediary between application updates and driver packages. It mediates the update process by evaluating hardware constraints and determining whether an application update can be safely installed given the current driver state, preventing direct conflicts between applications and drivers.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If hardware constraint metadata is added to application information in remote application stores, then application-hardware compatibility is improved, but the complexity of application metadata increases

Engineering Contradiction:
Improveapplication-hardware compatibilityVSAvoidapplication metadata structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The hardware constraint metadata serves multiple functions: it describes application requirements, enables compatibility evaluation, and guides installation decisions. By making the metadata multi-functional, the system avoids adding unnecessary complexity while achieving improved compatibility through a single unified data structure.

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

Data Source

PatentUS10740079B2Maintaining tight coupling between driver and application versions
Publication Date: 2020.08.11 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10740079B2 patent drawing
  • US10740079B2 patent drawing
  • US10740079B2 patent drawing

AI summary

Methods and devices for selecting an application for download for use with hardware on a computer device may include receiving, from a remote application store, application metadata that includes at least one hardware constraint for an application in response to an application request for installation of the application. The methods and devices may include evaluating the application metadata to determine whether the at least one hardware constraint is satisfied on the computer device. The methods and devices may include installing the application when the at least one hardware constraint is satisfied on the computer device.