Script Conversion for Offline Mobile Client Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional business applications written in backend-compatible languages are incompatible with mobile client-side applications in offline mode, requiring substantial additional development effort to implement modifications.

Innovation Solution

Automatically generating offline scripts in an offline scripting language and synchronizing them with mobile clients, allowing for efficient application development across heterogeneous online and offline architectures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If business applications are written in backend-compatible language, then modifications can be reflected on clients without client-side development, but the applications become incompatible with mobile client-side applications in offline mode

Engineering Contradiction:
Improveease of modificationVSAvoidcompatibility
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The system segments the application into backend-compatible components and mobile client-side components. The backend application remains in ABAP while mobile clients receive converted scripts in a mobile-compatible language, allowing each segment to operate in its optimal environment without requiring full rewriting.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The invention introduces an intermediary conversion mechanism that translates backend-compatible scripts into mobile client-side compatible scripts. This intermediary process enables compatibility between the backend application logic and mobile client requirements without modifying the original backend code.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of time

If modifications are made to backend-compatible business applications, then client-side updates are automatic, but substantial additional development effort is required for mobile client-side offline applications

Engineering Contradiction:
Improveupdate timeVSAvoiddevelopment efficiency
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

The system performs preliminary conversion of backend scripts into mobile client-side scripts in advance. By pre-converting the scripts before deployment to mobile clients, the system eliminates the need for additional development effort later, allowing modifications to be propagated automatically to both web and mobile platforms.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The invention creates a copied and adapted version of the backend-compatible scripts specifically for mobile client-side execution. This copying process generates mobile-optimized versions of the application logic that can run offline, preserving the original backend functionality while enabling mobile-specific operations.

Inventive Principle:
Principle #26Copying

3Ease of operation

If mobile client-side applications use offline mode, then local access to enterprise data is enabled, but modifications to backend applications do not reflect on mobile clients

Engineering Contradiction:
Improveoffline accessVSAvoidsynchronization
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The system implements a feedback mechanism where mobile clients periodically check for updates and retrieve converted scripts from the backend. This feedback loop ensures that modifications made to backend applications are automatically propagated to mobile clients in offline mode, maintaining synchronization without requiring continuous connectivity.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The invention changes the language parameter of the application scripts from backend-compatible language to mobile client-side compatible language through automatic conversion. This parameter transformation enables the same business logic to execute correctly in both backend and mobile offline environments, ensuring consistency across different deployment scenarios.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10817272B2Generation and usage of language-converted script
Publication Date: 2020.10.27 SAP SE
  • US10817272B2 patent drawing
  • US10817272B2 patent drawing
  • US10817272B2 patent drawing

AI summary

A system includes reception of a first script conforming to a first programming language, identification of a first declaration of a first variable in the first script, determination of a first datatype based on the first declaration, determination of a first initial value corresponding to the first datatype based on a second programming language, and generation of a first portion of a second script conforming to the second programming language, the first portion of the second script to initialize the first variable with the first initial value.