Remote Code Execution via Schema-Based Parameter Transformation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional approaches to remote code execution between computing environments require significant effort, especially for small or medium-scale deployments, due to the need for custom interfaces and strict data format compatibility, which is prohibitive for environments with different data formats, standards, or protocols.

Innovation Solution

The technology enables remote access to code by delegating calls from a source environment to a target environment, transforming sequences of fields or parameters using data schemas to ensure compatibility, allowing untyped or text data to be adapted for execution and return values to be compliant with the source environment, thereby facilitating generic communication and minimizing developer effort.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If custom interface modules are implemented for each individual call or service to be executed, then compatibility between different computing environments is improved, but the effort and complexity required for deployment increases significantly

Engineering Contradiction:
Improvecompatibility between different computing environmentsVSAvoideffort and complexity for deployment
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal interface module that can handle multiple different call types and data formats through a single standardized component. This module uses schema-based transformation to adapt between different computing environments (e.g., ABAP and Java) without requiring custom interfaces for each specific call, thereby reducing deployment complexity while maintaining compatibility.

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

Solution Approach 2:

The interface module dynamically changes parameters such as data formats, field names, and data types based on the target environment's schema. By automatically transforming parameters rather than requiring custom interfaces for each parameter set, the system achieves environment compatibility while minimizing the effort needed for deployment.

Inventive Principle:
Principle #35Parameter changes

2Manufacturing precision

If strict data format compatibility is enforced between source and target environments, then execution accuracy is improved, but the adaptability to different data formats and protocols deteriorates

Engineering Contradiction:
Improveexecution accuracyVSAvoidadaptability to different data formats and protocols
Core Design Contradiction:
Manufacturing precisionVSAdaptability or versatility

Solution Approach 1:

The patent introduces a schema-based transformation layer that acts as an intermediary between the source and target environments. This layer receives data in various formats, transforms it according to the target environment's schema requirements, and ensures execution accuracy without requiring the source environment to strictly adhere to the target's data format. The intermediary handles format adaptation while maintaining data integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If custom interfaces are implemented for every call, then reliability of execution is improved, but the productivity and scalability of the system deteriorates

Engineering Contradiction:
Improvereliability of executionVSAvoidproductivity and scalability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

A single universal interface module handles multiple different call types and data transformations, ensuring reliable execution through consistent schema-based validation and transformation. This approach enables the system to scale to hundreds or thousands of calls without requiring proportional increases in custom interface development, thereby maintaining both reliability and productivity.

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

Data Source

PatentUS11720534B2Remote code execution
Publication Date: 2023.08.08 SAP SE
  • US11720534B2 patent drawing
  • US11720534B2 patent drawing
  • US11720534B2 patent drawing

AI summary

Methods and systems are disclosed for remote code execution between computing environments having various dissimilarities. Client requests at a source environment lead to calls of various types lacking immediate support within the source environment. Calls are delegated to the target environment, where function schemas, data schemas, or copies of source-side schemas are variously used to reconcile called source-side entities with their target-side counterparts. Inconsistencies between name and data representations and datatypes are also addressed. Serially communicated (JSON) parameters are resolved into required target-side multi-level parameter structures, and vice versa. Expedited bulk data access to/from a database layer is supported. A use case is described for phased migration of a software application. Generic and extensible remote code execution allows rapid migration, adaptation, or deployment of software applications across diverse computing environments.