Modular Service Deployment for On-Premise and Cloud Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Business applications often have outdated features and user interface components, limiting user productivity due to legacy systems, and users may not have access to newer features or third-party services without a complete software upgrade, which is restrictive and inefficient.

Innovation Solution

A system that allows for the deployment of user productivity services independent of the underlying business application's deployment model, enabling on-demand or on-premise delivery of augmented features and services, including third-party integrations, to enhance user experience without requiring a full application upgrade.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a complete software upgrade is performed to update the business application with new features and UI components, then user productivity and access to new features are improved, but the complexity and cost of deployment increase significantly

Engineering Contradiction:
Improveuser productivityVSAvoiddeployment complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the business application into modular components: the core application framework and separate user productivity services. This allows individual services to be updated and deployed independently without requiring a complete application upgrade, thereby improving productivity while reducing deployment complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal service deployment architecture that can accommodate multiple types of user productivity services (third-party services, custom services, updates) through a common service registration and discovery mechanism. This multi-functional framework enables flexible service integration without increasing overall system complexity.

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

2Adaptability or versatility

If the business application is upgraded to access new features and third-party services, then functionality and user experience are improved, but compatibility with existing systems and user preferences may be compromised

Engineering Contradiction:
ImprovefunctionalityVSAvoidsystem compatibility
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent introduces a service registration and discovery mechanism as an intermediary layer between the core application and user productivity services. This mediator enables new services to be integrated while maintaining compatibility with existing systems through standardized interfaces and registration protocols, preserving system stability while enhancing functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a dynamic service configuration system where user productivity services can be registered, activated, and configured at runtime based on user roles and preferences. This dynamic approach allows the system to adapt functionality while maintaining stability through configurable service activation rather than hard-coded changes.

Inventive Principle:
Principle #15Dynamics

3Reliability

If on-premise deployment is used to maintain control and security, then security and control are improved, but flexibility and speed of service updates are reduced

Engineering Contradiction:
ImprovesecurityVSAvoidservice update speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements preliminary service registration and validation mechanisms that occur before service execution. Services are pre-registered, validated for security compliance, and cataloged in advance, enabling rapid deployment of verified services while maintaining security control through pre-established validation rules.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent incorporates feedback mechanisms where service performance and security metrics are monitored and fed back to the service registration system. This enables continuous improvement of service security while maintaining rapid update capabilities through automated security validation based on historical feedback data.

Inventive Principle:
Principle #23Feedback

4Adaptability or versatility

If third-party services are integrated to provide new functionality, then adaptability and features are improved, but system complexity and integration challenges increase

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

Solution Approach 1:

The patent introduces a service registration and discovery intermediary that standardizes the integration process for third-party services. This mediator provides unified interfaces for service registration, authentication, and configuration, reducing integration complexity while maintaining high adaptability for incorporating diverse third-party services.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent utilizes parameter-based service configuration where third-party services are integrated through configurable parameters and metadata rather than hard-coded integrations. This allows services to be adapted to different contexts through parameter changes without increasing structural complexity, enabling flexible third-party service integration.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9276825B2Single approach to on-premise and on-demand consumption of services
Publication Date: 2016.03.01 SAP SE
  • US9276825B2 patent drawing
  • US9276825B2 patent drawing
  • US9276825B2 patent drawing

AI summary

The present disclosure involves systems, software, and computer implemented methods for deployment of services independent of a particular deployment model. One process includes operations for receiving a selection for a user productivity service from a client device, the client device located in a corporate network. A request for a particular method of deployment of the user productivity service is received. At least a portion of the user productivity service is transmitted to the client device if the request is for on-demand deployment of the user productivity service. At least a portion of the user productivity service is transmitted to a server in the corporate network if the request is for on-premise deployment of the user productivity service.