Cross-End Container Data Sharing via Shared Storage

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The existing mode of transmitting data between a cross-end runtime environment and a native runtime environment is typically time-consuming due to the need for data format conversion and repeated requests to external data sources.

Innovation Solution

A method and apparatus for sharing data between a cross-end container and a native runtime environment, where target data is saved in a shared storage region in both formats corresponding to each environment, allowing direct access and reading without format conversion, thereby reducing data transmission time and external data source requests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is transmitted through a bridge module between cross-end runtime environment and native runtime environment, then data transmission is enabled, but data transmission time increases

Engineering Contradiction:

Improvedata transmission capabilityVSAvoiddata transmission time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent creates a copy of the data in a shared storage region that both the cross-end container and native runtime environment can access directly. Instead of transmitting data through a bridge module, the data is duplicated in a location accessible by both environments, eliminating the need for time-consuming data transmission through the bridge.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent introduces a shared storage region as an intermediary between the cross-end container and native runtime environment. This intermediary storage area allows both environments to access the same data without direct communication through a bridge module, reducing transmission time while maintaining data consistency.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If data format conversion is performed for transmission between cross-end container and native runtime environment, then compatibility is achieved, but processing time increases

Engineering Contradiction:

Improveplatform compatibilityVSAvoiddata format conversion time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent performs data format conversion in advance when data is written to the shared storage region. The data is pre-converted into formats suitable for both cross-end container and native runtime environment before either needs to access it, eliminating the need for time-consuming format conversion at the moment of data access.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent changes the data format parameters proactively during the data writing process rather than during reading. By transforming the data into a universal or dual-compatible format when it's first introduced to the shared storage region, the system avoids repeated format conversions and enables direct access by both environments.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If multiple requests are made to external data sources by cross-end container and native runtime environment, then data availability is ensured, but request frequency increases

Engineering Contradiction:

Improvedata availabilityVSAvoiddata request efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent merges the data access operations of the cross-end container and native runtime environment into a single shared storage region. Instead of both environments independently requesting data from external sources, one environment's data acquisition result is stored in the shared region, allowing the other environment to access the same data without making a separate external request.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The patent eliminates redundant data requests by having one environment's data acquisition result serve both environments. The data is acquired once by either the cross-end container or native runtime environment, stored in the shared region, and then recovered and reused by the other environment, discarding the need for duplicate external requests.

Inventive Principle:

Principle #34Discarding and recovering

Data Source

PatentUS20250077318A1Method for sharing data between cross-end container and native runtime environment, device and medium

Publication Date: 2025.03.06 LEMON INC(GB)

AI summary

The embodiments of the present disclosure describe a method for sharing data between a cross-end container and a native runtime environment, a device and a medium. And the method includes: acquiring or updating, by the cross-end container or the native runtime environment, target data, and saving the target data to a shared storage region in the native runtime environment respectively in a first data format corresponding to the cross-end container and a second data format corresponding to the native runtime environment; and accessing, by the native runtime environment or the cross-end container, the shared storage region, and reading the target data in the second data format or the first data format respectively corresponding to the native runtime environment or the cross-end container.