Field-Programmable Business Logic Wrapper for Mobile App Policy Enforcement

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Device administrators face challenges in efficiently managing and updating complex applications across multiple mobile devices, as existing solutions lack convenience and flexibility in enforcing policies and updating business logic without re-wrapping applications.

Innovation Solution

A method involving wrapping applications with field-programmable business logic, where a computing device loads application code, modifies it with an application wrapper to intercept functions, and creates a library file with implementation code linked to policy files, allowing for updates to be managed centrally and applied to user devices, enabling flexible policy enforcement and efficient updates without re-wrapping.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If applications are wrapped with business logic to enable policy enforcement and centralized management, then administrative control and flexibility are improved, but application complexity and deployment overhead increase

Engineering Contradiction:
Improvepolicy enforcement capabilityVSAvoidapplication structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the application into three distinct components: the original application code, an application wrapper that provides policy enforcement, and a separate library file containing field-programmable business logic. This segmentation allows each component to be developed, updated, and managed independently, reducing overall system complexity while maintaining adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The application wrapper acts as an intermediary layer between the original application and the policy management system. It intercepts function calls from the application and routes them to the appropriate business logic in the library file, enabling centralized policy enforcement without modifying the original application code.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If applications are updated across multiple devices, then functionality and security are improved, but deployment time and administrative effort increase

Engineering Contradiction:
Improveapplication securityVSAvoidupdate deployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

By separating business logic into a standalone library file, the patent enables selective updates of only the necessary components. Administrators can update the library file containing field-programmable business logic without requiring updates to the entire application package, significantly reducing deployment time across multiple devices.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The library file containing field-programmable business logic serves as a universal component that can be shared across multiple applications and devices. A single update to this library file can simultaneously update policy enforcement behavior across numerous deployed applications, improving efficiency and consistency.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Stability of the object's composition

If business logic is hardcoded in applications, then application functionality is maintained, but flexibility and ease of updates are reduced

Engineering Contradiction:
Improveapplication functionalityVSAvoidbusiness logic flexibility
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The application wrapper serves as an intermediary that decouples the original application code from the business logic. Instead of hardcoding business logic within the application, the wrapper intercepts function calls and dynamically resolves them to the field-programmable business logic in the external library file, enabling flexible updates without affecting application stability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent transforms the static, hardcoded business logic into a dynamic, field-programmable system. The library file contains business logic that can be programmatically modified and updated based on changing requirements, allowing the system to adapt to new policies and business rules without requiring application re-compilation or re-deployment.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP3274821B1Wrapping an application with field-programmable business logic
Publication Date: 2020.03.11 CITRIX SYSTEMS INC
  • EP3274821B1 patent drawingFigure 1
  • EP3274821B1 patent drawingFigure 2
  • EP3274821B1 patent drawingFigure 3

AI summary

Systems, methods, and computer-readable media for wrapping an application with field-programmable business logic are presented. In some embodiments, a computing device may load application code of a mobile application. Subsequently, the computing device may modify the application code to wrap the application with an application wrapper that is configured to manage execution of the application based on one or more policy files and configured to intercept one or more functions of the application code, where the one or more policy files each define one or more access controls that are enforced by a device management system on one or more user devices. Subsequently, the computing device may create a library file comprising field-programmable business logic defining implementation code linked to one or more of the functions intercepted by the wrapper. The computing device may then provide the wrapped application and the library file to at least one user device.