Global Context Unit for Heterogeneous Application Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In heterogeneous application environments, direct communication between applications is challenging due to differing technologies and languages, leading to error-prone manual transfer of context information and requiring architectural changes for integration.

Innovation Solution

A global context unit is introduced to store and manage context information from source applications, allowing access to target applications without altering their architecture, using methods like 'Set_Value' and 'Get_Value' for seamless integration and access control.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If context information is transferred manually between heterogeneous applications, then integration can be achieved, but error rate increases and reliability decreases

Engineering Contradiction:
Improveintegration capabilityVSAvoiderror rate
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

A global context unit is introduced as an intermediary component that stores context information in a standardized format (context vectors). Applications access this unit through defined interfaces, eliminating direct manual transfers between heterogeneous applications and reducing errors caused by language differences and manual handling.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If context information is automatically transferred between applications, then productivity increases, but architectural changes are required

Engineering Contradiction:
Improveautomation levelVSAvoidarchitectural complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The global context unit serves as a universal interface that can be accessed by any application in the heterogeneous environment. It provides multi-functional capabilities including storing context information, managing context vectors, and providing standardized access methods, thereby enabling automatic transfer without requiring each application to be modified for specific integration scenarios.

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

Solution Approach 2:

The context information management is segmented into independent components: the global context unit, context vectors, and access interfaces. This segmentation allows applications to automatically access context information without requiring architectural changes to their core logic, as the segmentation isolates the integration mechanism from application internals.

Inventive Principle:
Principle #1Segmentation

3Measurement precision

If direct communication interfaces are programmed between applications, then access precision improves, but economic cost increases

Engineering Contradiction:
Improveaccess precisionVSAvoidprogramming cost
Core Design Contradiction:
Measurement precisionVSEase of manufacture

Solution Approach 1:

Applications access context information through self-service mechanisms by calling standardized methods on the global context unit. The context unit itself manages the precision of access through its internal structure (context vectors with named components), eliminating the need for custom programming interfaces between each application pair and reducing development costs.

Inventive Principle:
Principle #25Self-service

4Speed

If context information is stored in shared memory or buffer, then access speed improves, but design changes are required

Engineering Contradiction:
Improveaccess speedVSAvoiddesign complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The global context unit acts as an intermediary layer between applications and the underlying storage mechanism. It provides high-speed access similar to shared memory or buffers while encapsulating the design complexity within the context unit itself. Applications interact with the standardized interface rather than directly with the storage implementation, allowing speed optimization without requiring application design changes.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8910183B2Access to context information in a heterogeneous application environment
Publication Date: 2014.12.09 SAP SE
  • US8910183B2 patent drawing
  • US8910183B2 patent drawing
  • US8910183B2 patent drawing

AI summary

Various embodiments of systems and methods to provide access to context information in a heterogeneous application environment are described herein. The context information of a source application is received. The context information is based on the execution of the source application. Further, the context information is stored in one or more context vectors of a global context unit, the one or more context vectors corresponding to the source application and one or more target applications. Furthermore, access to the context information of the global context unit is provided for the one or more target applications upon receiving invoking access indication from the one or more target applications. Also, the source application and the one or more target applications are integrated with the global context unit.