Software Integration Connector for On-Premise Cloud Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Organizations face challenges in integrating on-premise and on-demand software solutions for business applications due to security, compliance, and cost concerns, requiring a seamless access and execution mechanism without modifying the business applications.

Innovation Solution

A method to integrate on-premise and on-demand software solutions by establishing a secure communication channel, allowing business applications to access and execute resources from either platform without modification, using a connector that enables bidirectional communication and resource sharing between on-premise and cloud environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If on-demand solution is used, then cost is reduced, but security and compliance issues arise

Engineering Contradiction:
Improvesecurity and complianceVSAvoidsoftware solution choice
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the software solution into multiple independent components that can be deployed across different platforms. Business applications are divided into modules that can execute on either on-premise or on-demand infrastructure, allowing organizations to select the appropriate deployment model for each component based on security requirements and cost considerations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer that enables communication and integration between on-premise and on-demand software solutions. This intermediary facilitates secure data exchange and coordination between the two environments, allowing organizations to leverage cloud-based on-demand solutions while maintaining security compliance through controlled integration points.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If on-premise solution is used, then security and compliance are maintained, but cost increases

Engineering Contradiction:
Improvesecurity and complianceVSAvoidcost
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies local quality by allowing different parts of the software system to have different deployment characteristics. Critical components requiring high security and compliance can be deployed on-premise, while non-critical components can be deployed on-demand to reduce costs. This enables organizations to optimize the cost-security tradeoff at the component level rather than making a blanket choice for the entire system.

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If different business applications are implemented in different software solutions, then specific requirements are met, but integration complexity increases

Engineering Contradiction:
Improveapplication-specific optimizationVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal integration framework that can handle multiple types of software solutions and communication protocols through a single standardized interface. This multi-functional approach allows different business applications deployed on different platforms to be integrated without requiring custom integration logic for each pair of applications, thereby reducing overall integration complexity while maintaining application-specific optimization.

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

Data Source

PatentUS9754228B2Integrating software solutions to execute business applications
Publication Date: 2017.09.05 SAP SE
  • US9754228B2 patent drawing
  • US9754228B2 patent drawing
  • US9754228B2 patent drawing

AI summary

Various embodiments of systems and methods to integrate software solutions to execute business applications are described herein. A request is received at a first software solution to execute a business application. In one aspect, the request is forwarded to a second software solution when a resource required to execute the business application is associated with the second software solution. A response is received from the second software solution corresponding to the execution of the business application. In another aspect, the business application is executed at the first software solution when the resource required to execute the business application is associated with the first software solution. The response corresponding to the execution of the business application is rendered on a computer generated UI associated with the first software solution.