Cross-Platform Component Invocation via Unified Identifier

Solution Overview

Problem

Existing applications face challenges in efficiently invoking components across different operating system platforms, leading to increased storage space occupation and development complexity due to the need for separate code generation for each platform.

Innovation Solution

A method and apparatus for component invocation that involves obtaining component invoking data with a component identifier, transferring it to a native layer using a communications channel, and invoking the corresponding native component, allowing cross-platform component invocation with a single set of development data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If separate code data is generated for each operating system platform, then platform-specific functionality is achieved, but storage space occupation increases and development difficulty increases

Engineering Contradiction:

Improveplatform compatibilityVSAvoidstorage space

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent merges multiple platform-specific code data into a single hybrid code data structure that contains both common code (executable on all platforms) and platform-specific code segments. This consolidation reduces the total quantity of code data stored while maintaining the ability to adapt to different operating system platforms through selective execution of appropriate code segments.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The hybrid code data is designed with universal functionality by incorporating a common code portion that can be executed on any platform, while including platform-specific portions that are conditionally executed. This multi-functional design allows a single code data structure to serve multiple platform requirements without requiring separate complete code sets for each platform.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If separate code data is generated for each operating system platform, then platform-specific functionality is achieved, but development difficulty increases

Engineering Contradiction:

Improveplatform compatibilityVSAvoiddevelopment complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple platform-specific code data into a single hybrid code data structure that contains both common code (executable on all platforms) and platform-specific code segments. This consolidation reduces the total quantity of code data stored while maintaining the ability to adapt to different operating system platforms through selective execution of appropriate code segments.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The hybrid code data is designed with universal functionality by incorporating a common code portion that can be executed on any platform, while including platform-specific portions that are conditionally executed. This multi-functional design allows a single code data structure to serve multiple platform requirements without requiring separate complete code sets for each platform.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Ease of manufacture

If a unified component invocation approach is used across platforms, then development is simplified and storage is reduced, but platform-specific native component compatibility must be maintained

Engineering Contradiction:

Improvedevelopment easeVSAvoidnative component compatibility

Core Design Contradiction:

Ease of manufactureVSReliability

Solution Approach 1:

The patent introduces a component invocation mechanism that acts as an intermediary between the unified hybrid code data and platform-specific native components. This intermediary parses the hybrid code data, identifies platform-specific component requirements, and dynamically invokes the appropriate native components on each platform. This mediator layer simplifies development by providing a unified interface while ensuring reliable platform-specific compatibility through targeted native component invocation.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10740114B2Component invoking method and apparatus, and component data processing method and apparatus

Publication Date: 2020.08.11 TENCENT TECHNOLOGY (SHENZHEN) CO LTD

AI summary

A component invoking method includes obtaining component invoking data corresponding to a child application. The component invoking data includes a component identifier identifying a first native component in a parent application and corresponding to a current system platform and a second native component running on another system platform and having a same function as the first native component. The method further includes transferring the component invoking data to a native layer corresponding to the parent application using a communications channel corresponding to the current system platform and invoking the first native component by the native layer based on the component invoking data.