Runtime Metadata Enrichment for Cross-Environment Application Execution

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing application programming models face challenges in seamlessly integrating and executing applications across different runtime environments, particularly in transitioning applications from one runtime environment to another while maintaining metadata consistency.

Innovation Solution

A system that registers and enriches application objects with metadata from a second runtime environment, allowing execution in a first runtime environment, by parsing annotation definitions, deriving entity and action definitions, and generating TypeScript interfaces for data and service entities, enabling smooth transition and execution across environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If an application is executed in a first runtime environment, then the application can run with its native runtime characteristics, but the application cannot seamlessly integrate with or transition to a second runtime environment while maintaining metadata consistency

Engineering Contradiction:

Improveability to execute in different runtime environmentsVSAvoidmetadata consistency

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent introduces a metadata enrichment mechanism that acts as an intermediary between the first runtime environment and the second runtime environment. The system enriches the application object definition with metadata from the second runtime environment, creating a bridge that allows the application to execute in the first runtime environment while maintaining consistency with the second runtime environment's metadata structure and semantics.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent performs preliminary enrichment of the application object definition with metadata from the second runtime environment before execution. By pre-loading and integrating the necessary metadata, type definitions, and service bindings in advance, the system ensures that when the application executes in the first runtime environment, it already possesses the information needed to maintain consistency with the second runtime environment, avoiding metadata loss during transition.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If metadata enrichment is performed to enable cross-runtime execution, then adaptability across runtime environments improves, but system complexity increases due to additional processing steps

Engineering Contradiction:

Improvecross-runtime environment execution capabilityVSAvoidmetadata processing complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal metadata enrichment mechanism that handles multiple runtime environments through a single, unified process. The enrichment system is designed to work with different runtime environments (such as SAP Business Application Studio and SAP Business Technology Platform) using a common approach, thereby reducing the need for environment-specific processing logic and simplifying the overall system architecture despite the added functionality.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent uses copying mechanisms to replicate metadata structures and type definitions from the second runtime environment into the first runtime environment. By creating copies of necessary metadata, type definitions, and service bindings, the system avoids complex real-time synchronization while maintaining consistency, thereby reducing processing complexity.

Inventive Principle:

Principle #26Copying

3Reliability

If application objects are enriched with metadata from a second runtime environment, then execution consistency across environments improves, but processing time increases due to additional enrichment steps

Engineering Contradiction:

Improveexecution consistencyVSAvoidmetadata enrichment time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent performs metadata enrichment as a preliminary action before application execution. By enriching the application object definition with necessary metadata, type definitions, and service bindings in advance, the system ensures execution consistency across runtime environments without incurring processing delays during actual application runtime. The enrichment occurs during the setup or deployment phase, separating the time-consuming metadata processing from the critical application execution path.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11194602B2Runtime execution of entities and services in an application object runtime environment

Publication Date: 2021.12.07 SAP SE

AI summary

Some embodiments provide a non-transitory machine-readable medium that stores a program. The program receives, from a client device, a request to execute an application object configured to execute in a first runtime environment. The program further registers the first runtime environment in a second runtime environment. The program also registers the application object in the first runtime environment. The program further enriches a definition of the application object with metadata associated with the second runtime environment. The program also executes the application object in the first runtime environment.