Software Provisioning System Architecture Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software provisioning systems require user input to determine appropriate software components for computer systems with different architectures, such as 32-bit and 64-bit systems, leading to inefficiencies in software distribution and compatibility.

Innovation Solution

A provisioning system that automatically determines the appropriate software components for installation by checking processor flags or operating system entries to ensure compatibility, allowing for the selection of either 32-bit or 64-bit software components based on the target computer's architecture, without requiring user input.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a provisioning system requires user input to determine appropriate software components for different architectures, then software compatibility can be ensured, but provisioning efficiency and automation are reduced

Engineering Contradiction:
Improvesoftware compatibilityVSAvoidprovisioning efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The computer system automatically determines its own architecture type (32-bit or 64-bit) by checking processor flags or operating system entries, and uses this information to select appropriate software components without requiring user input. This self-service approach resolves the contradiction by enabling both automated efficient provisioning and reliable compatibility through the system's own self-identification of its architectural capabilities.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The provisioning system retrieves architecture information from the computer system (through processor flags or OS entries) and uses this feedback to automatically determine which software components to provision. This feedback loop eliminates the need for manual user input while ensuring compatibility, as the system's actual architecture state directly guides the provisioning decisions.

Inventive Principle:
Principle #23Feedback

2Reliability

If manual intervention is used to determine software support, then architecture compatibility can be verified, but the complexity and time required for provisioning increases

Engineering Contradiction:
Improvearchitecture compatibilityVSAvoidprovisioning complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The computer system automatically provides its architecture information through processor flags or operating system entries, eliminating the need for manual verification. This self-service mechanism reduces provisioning complexity while maintaining reliable architecture compatibility, as the system itself supplies the necessary compatibility information without human intervention.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The architecture information is predetermined and stored in the computer system's processor flags or operating system entries before the provisioning process begins. This preliminary preparation of architecture data eliminates the need for complex manual verification during provisioning, reducing complexity while ensuring reliable compatibility determination.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If user input is required to select software components, then compatibility decisions can be made, but the provisioning process becomes less automated and more time-consuming

Engineering Contradiction:
Improvesoftware selection flexibilityVSAvoidprovisioning automation
Core Design Contradiction:
Adaptability or versatilityVSExtent of automation

Solution Approach 1:

The computer system automatically determines its architecture type and selects appropriate software components based on this self-identified information. This self-service approach achieves full automation of the provisioning process while maintaining adaptability, as the system's own architecture state guides the selection of compatible software without requiring user input or manual intervention.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The provisioning system uses feedback from the computer system's architecture information (processor flags or OS entries) to automatically select appropriate software components. This feedback-driven automation maintains versatility in software selection while eliminating the need for user input, achieving both high automation and adaptability simultaneously.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8832679B2Registration process for determining compatibility with 32-bit or 64-bit software
Publication Date: 2014.09.09 RED HAT INC
  • US8832679B2 patent drawing
  • US8832679B2 patent drawing
  • US8832679B2 patent drawing

AI summary

A registration process for computers as part of a provisioning system that automatically determines the appropriate components to install in each computer system. The registration process ensures that the configuration information necessary for provisioning of software components that are appropriate to each system are collected. The registration process can identify support for 64-bit components. The registration process checks a field in the processor to determine longword, that is 64-bit support, or checks an entry in a file maintained by an operating system to determine 64-bit support.