Deterministic Compliance Policy Enforcement for Mobile Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network traffic management systems face challenges in enforcing compliance policies deterministically and efficiently, particularly when immediate changes are needed to address security issues, as the scheduling of compliance policy execution is often based on variable parameters like system load and device enrollment, leading to ineffective and unpredictable enforcement.

Innovation Solution

A method and apparatus for deterministic enforcement of compliance policies, which involves receiving compliance policy changes, estimating the time required for enforcement, determining the acceptability of this time based on stored parameters, and enforcing the changes when acceptable, thereby ensuring quick and resource-efficient policy updates across enrolled devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If compliance policy execution is scheduled based on current and expected system load, then system resources are optimized, but the enforcement time becomes unpredictable and delayed

Engineering Contradiction:
Improvecompliance policy enforcement speedVSAvoidpolicy enforcement delay
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-calculating and storing the estimated enforcement time for compliance policies before actual enforcement is needed. When a policy change occurs, the pre-computed time estimate is immediately available, eliminating the delay of real-time calculation while still allowing resource optimization based on historical data and system capacity.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If compliance checks involve processing substantial information from all enrolled devices, then comprehensive compliance verification is achieved, but system computing resources are heavily consumed

Engineering Contradiction:
Improvecompliance verification completenessVSAvoidcomputing resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system applies local quality by tailoring the compliance check scope to the specific policy requirements. Different compliance policies are enforced with appropriate depth and breadth - some policies require full device inspection while others only need specific parameter verification. This selective approach ensures comprehensive verification where needed while conserving computing resources for less intensive checks.

Inventive Principle:
Principle #3Local quality

3Productivity

If compliance policy enforcement is scheduled based on variable parameters, then system capacity is optimized, but deterministic enforcement timing cannot be guaranteed

Engineering Contradiction:
Improvesystem capacity utilizationVSAvoidenforcement timing accuracy
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The system implements feedback by continuously monitoring actual enforcement times and comparing them against estimated times. This feedback loop allows the system to refine its time estimation algorithms and adjust scheduling parameters based on real-world performance data, progressively improving both timing accuracy and system capacity utilization without sacrificing deterministic enforcement capabilities.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10505990B1Methods for deterministic enforcement of compliance policies and devices thereof
Publication Date: 2019.12.10 F5 NETWORKS INC
  • US10505990B1 patent drawing
  • US10505990B1 patent drawing
  • US10505990B1 patent drawing

AI summary

Methods, non-transitory computer readable media, and mobile application manager apparatus that assists with deterministic enforcement of compliance policy includes receiving one or more compliance policy changes. An estimated time to enforce the received one or more compliance policy changes on one or more enrolled mobile devices is identified. It is determined whether the identified estimated time to enforce the received one or more compliance policy changes is acceptable based on one or more stored parameters. The received one or more compliance policy changes on the one or more enrolled mobile devices is enforced when the identified estimated time is determined to be acceptable and updating existing one or more compliancy policies with the received one or more compliance policy changes.