Platform Independent Registry Framework for Software Lifecycle Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing software applications across diverse systems with different hardware and software configurations poses a challenge, as administrators need to understand each system's specifics to perform lifecycle operations effectively, which can be cumbersome and error-prone, especially when managing multiple systems.

Innovation Solution

A platform-independent framework that receives abstract API commands, determines compatibility using a software application schema and platform-independent registry, maps these commands to OS-specific commands, executes them, and updates the registry, enabling standardized lifecycle operations across various systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If administrators manage multiple systems with different hardware and software configurations directly, then they can perform lifecycle operations on each system, but the administrative complexity and knowledge requirements increase significantly

Engineering Contradiction:
ImproveAbility to perform lifecycle operations across different systemsVSAvoidAdministrative complexity and knowledge requirements
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (the framework with schema and registry) between the administrator and the diverse target systems. This intermediary translates abstract lifecycle operation requests into system-specific commands, eliminating the need for administrators to directly understand each system's unique configuration while maintaining the ability to operate across different platforms

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If administrators understand each specific system configuration to perform lifecycle operations, then operations can be performed correctly, but the time and effort required increase

Engineering Contradiction:
ImproveCorrectness of lifecycle operationsVSAvoidTime required to understand and manage multiple systems
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by pre-defining software application schemas that capture essential system characteristics and pre-registering target systems with their specific configurations. This preparation work is done in advance, allowing administrators to perform lifecycle operations without needing to understand each system's details at the time of operation, thus reducing time while maintaining reliability

Inventive Principle:
Principle #10Preliminary action

3Productivity

If a platform-specific approach is used for managing software applications, then operations can be performed with detailed system knowledge, but the ease of operation decreases when managing multiple different systems

Engineering Contradiction:
ImproveEfficiency of lifecycle operationsVSAvoidConvenience of managing multiple systems
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent creates a universal framework that can handle multiple different target systems through a common interface. The software application schema and platform-independent registry work together to provide a unified approach that adapts to various systems, making it as easy to manage diverse systems as it is to manage a single system type

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

Data Source

PatentUS8151256B2Platform independent registry framework
Publication Date: 2012.04.03 ORACLE AMERICAN INC
  • US8151256B2 patent drawing
  • US8151256B2 patent drawing
  • US8151256B2 patent drawing

AI summary

A method for managing a software application. The method involves receiving an abstract API command to perform a life cycle operation (LCO) on a target system, where the LCO identifies the software application, where the software application is associated with a software application schema, and where the target system is associated with a platform independent registry, determining whether the LCO is compatible with the target system using the software application schema and the platform independent registry, where the LCO is compatible with the target system; mapping the abstract API command to an operating system (OS)-specific command for performing the LCO, where the OS-specific command is associated with an OS executing on the target system; executing the OS-specific API command to perform the LCO on the target system to obtain a result; and updating the platform independent registry based on the result.