Multi-Entry Point Function for Application-Specific Behavior

Solution Overview

Problem

Static monitoring functions lack the ability to differentiate behavior based on calling applications, as they are unaware of the application's identity, making tailored behavior challenging, and dynamic code generation comes with increased resource demands and stability issues.

Innovation Solution

A static multi-entry point function is introduced, allowing multiple entry points with a common prologue that loads data into local variables, enabling the functional component to perform different actions based on the data, and including a default entry point for compatibility with scanners.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If dynamic code generation is used to enable application-specific behavior, then adaptability is improved, but device complexity and resource usage increase

Engineering Contradiction:

Improveapplication-specific behaviorVSAvoidcode generation engine

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The function is segmented into multiple entry points, each associated with different applications or callers. Each entry point has its own data associated with it, allowing the functional component to receive and process application-specific information without requiring dynamic code generation. This segmentation enables adaptability while maintaining static code structure.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

A single function serves multiple applications by accepting different entry points with associated data. The functional component is designed to handle various applications universally through the common prologue and epilogue structure, eliminating the need for separate functions for each application and avoiding dynamic code generation.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If dynamic code generation is used to enable application-specific behavior, then adaptability is improved, but reliability deteriorates

Engineering Contradiction:

Improveapplication-specific behaviorVSAvoidcode stability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The function is segmented into multiple entry points, each associated with different applications or callers. Each entry point has its own data associated with it, allowing the functional component to receive and process application-specific information without requiring dynamic code generation. This segmentation enables adaptability while maintaining static code structure.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The function appears static to scanners and compilers but dynamically adapts its behavior based on which entry point is called. The common prologue and epilogue provide stable, consistent structure while the functional component receives application-specific data through the entry point mechanism, achieving both stability and adaptability.

Inventive Principle:

Principle #15Dynamics

3Device complexity

If a static monitoring function is used, then device complexity is reduced, but adaptability deteriorates

Engineering Contradiction:

Improvefunction structureVSAvoidapplication-aware behavior

Core Design Contradiction:

Device complexityVSAdaptability or versatility

Solution Approach 1:

The function is segmented into multiple entry points, each associated with different applications or callers. Each entry point has its own data associated with it, allowing the functional component to receive and process application-specific information without requiring dynamic code generation. This segmentation enables adaptability while maintaining static code structure.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The entry point acts as an intermediary between the calling application and the functional component. Each entry point receives application-specific data and passes it to the functional component through the common prologue, enabling the static function to adapt to different applications without increasing overall complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10496378B2Generating and executing multi-entry point functions

Publication Date: 2019.12.03 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

A static multi-entry point function with more than one entry point is provided. The function allows callers to enter the function at different entry points using an offset. Each entry point of the function is associated with a different offset, and includes instructions that identify data that is associated with the entry point. Each entry point further includes an instruction that jumps to a common prologue of the function. The common prologue loads the identified data into local variables. The function also includes a functional component that performs different actions depending on the data in the local variables. The function includes a default entry point that is used when the function is called without any offset, so that the function appears to behave like a normal function to scanners.