Third-Party Library Calling via Shared Function Registration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods for third-party program libraries in a Windows-based software platform require additional workload and synchronization changes when additional libraries are called, and explicit loading fails if the additional library is not present.

Innovation Solution

A software platform-specific mutual calling method that constructs, verifies, and mutually calls third-party program libraries using initialization, capability obtaining, and release submodules, allowing shared function access without explicit loading of additional libraries.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the current third-party program library is modified to implicitly or explicitly load the additional third-party program library, then the current library can call the additional library, but additional workload is required and synchronous changes are needed when the additional library changes

Engineering Contradiction:

Improvecapability to call additional third-party program libraryVSAvoidworkload and synchronization requirements

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary mechanism (the modification module and registration system) that mediates between the current third-party program library and the additional third-party program library. Instead of direct modification and loading, the system uses an intermediary layer that automatically manages the calling relationship, reducing the workload and synchronization requirements on the current library.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the library calling functionality into distinct modules: the initialization submodule, the modification module, and the registration module. This segmentation allows each module to handle specific aspects of the calling process independently, reducing the complexity and workload on any single component.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If the current third-party program library explicitly loads the additional third-party program library, then the calling relationship is established, but the current library cannot load the additional library if it does not exist

Engineering Contradiction:

Improveexplicit loading capabilityVSAvoidloading failure when library is missing

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies preliminary action by pre-registering the additional third-party program library with the system before the current library attempts to call it. The registration module stores information about the additional library in advance, allowing the system to verify its existence and prepare the calling relationship before actual execution, thus preventing loading failures.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements a feedback mechanism where the system checks whether the additional third-party program library exists and is properly registered before allowing the current library to call it. If the additional library is not found or not registered, the system provides feedback to prevent the calling operation, avoiding runtime errors and ensuring reliable operation.

Inventive Principle:

Principle #23Feedback

3Adaptability or versatility

If traditional modification methods are used to enable library calling, then functionality is achieved, but development effort and error likelihood increase

Engineering Contradiction:

Improvefunctionality to call additional librariesVSAvoiddevelopment effort and error rate

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent enables self-service by allowing the additional third-party program library to automatically register itself with the system during its initialization process. The library provides its own information (name, version, function list) to the registration module, eliminating the need for manual configuration or complex modification processes by the current library's developer.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent creates a universal calling mechanism that works with any third-party program library regardless of its specific implementation details. The standardized registration and calling interface allows different libraries to be integrated through a common process, reducing development effort and making the system adaptable to various library types without increasing error likelihood.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS12547396B2Software platform-specific mutual calling method for functions of third-party program libraries, and mutual calling system

Publication Date: 2026.02.10 SHANGHAI TOSUN TECH LTD

AI summary

A software platform-specific mutual calling method for functions of third-party program libraries includes: constructing a plurality of third-party program libraries; verifying validity of the third-party program library; and mutually calling the plurality of third-party program libraries. This implements a general calling framework by using a software platform, such that a function, registered with the software platform, of the third-party program library can be shared among all loaded third-party program libraries. When a current third-party program library needs to call an additional third-party program library, there is no need to load the additional third-party program library, and the additional third-party program library can be accessed only by using a function list that contains the additional third-party program library and that is shared by the software platform for the current third-party program library.