Unified Application Platform for Service Versatility and Complexity Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network-based software application platforms face challenges such as labor-intensive provisioning and upgrading, difficulty in accessing log files and audit information, and multiple authentication requirements, which hinder productivity and integration.

Innovation Solution

A system that generates and configures appliances using metadata, allowing for standardized communication and management through an infrastructure management layer, decoupling operational and functional lifecycles, and enabling independent lifecycle management of each application instance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple network-based applications are deployed to provide diverse services, then service versatility is improved, but system complexity increases due to multiple seams and authentication requirements

Engineering Contradiction:
Improveservice versatilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple network-based applications into a single unified application that provides diverse services through different interfaces. This consolidation eliminates the complexity of managing multiple separate applications while maintaining service versatility. The unified application architecture allows multiple services to coexist without requiring separate authentication mechanisms or integration seams.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The invention implements a universal application platform that can deliver multiple services through a single application instance. The system uses a service registry and dynamic interface generation to enable one application to fulfill multiple functional roles, thereby reducing the need for multiple specialized applications and their associated complexity.

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

2Reliability

If traditional application provisioning methods are used, then application functionality is maintained, but provisioning and upgrading becomes labor intensive

Engineering Contradiction:
Improveapplication functionalityVSAvoidprovisioning efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements self-service provisioning through automated service discovery and instance generation. The system automatically registers services, generates appropriate interfaces, and provisions application instances based on service requests without requiring manual intervention. This automation maintains application functionality while dramatically improving provisioning efficiency.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The invention performs preliminary actions by pre-registering services and their interfaces in a service registry before actual deployment. This advance preparation allows the system to rapidly provision and upgrade applications by simply referencing the pre-defined service specifications, eliminating the need for labor-intensive manual configuration during deployment.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If separate application instances are used for different services, then service independence is improved, but access to log files and audit information becomes difficult

Engineering Contradiction:
Improveservice independenceVSAvoidaccessibility of log files
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent combines log files and audit information from multiple service instances into a unified logging mechanism. The unified application architecture captures logs and audit trails centrally, making them easily accessible while preserving the independence of individual service instances. This approach maintains service autonomy while simplifying access to operational information.

Inventive Principle:
Principle #5Merging (Combining)

4Adaptability or versatility

If multiple applications are deployed to handle different functions, then functional capability is improved, but integration and productivity are hindered by multiple seams

Engineering Contradiction:
Improvefunctional capabilityVSAvoidintegration efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The invention merges multiple functionally distinct applications into a single unified application that provides diverse services through different interfaces. This consolidation eliminates integration seams between separate applications while maintaining the functional capabilities of each service. The unified architecture enables seamless interaction between services without the overhead of inter-application communication protocols.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS10013291B1Enhanced software application platform
Publication Date: 2018.07.03 CA TECH INC
  • US10013291B1 patent drawing
  • US10013291B1 patent drawing
  • US10013291B1 patent drawing

AI summary

A system includes information for generating a first appliance based on first appliance information, information for generating a second appliance based on second appliance information, and information for configuring communication between the first appliance and the second appliance. The system further includes at least one processor configured to generate a first volume by copying the first appliance information using a first set of parameters associated with an environment in which the first volume is situated, and generate a second volume by copying the second appliance information using a second set of parameters associated with an environment in which the second volume is situated. The system also includes at least one processor configured to initiate a first appliance instance by executing code from the first volume using information in the third volume, and initiate a second appliance instance by executing code in the second volume using information in a fourth volume.