Mobile Device State Machine for Autonomous Compliance Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mobile device management (MDM) systems face scalability challenges and errors due to the need for servers to manage and configure large numbers of devices, leading to high processing demands and preventable configuration issues.

Innovation Solution

Implementing a state machine on mobile devices to autonomously configure compliance settings received from a server, allowing devices to manage their own configuration processes and reduce server workload by processing configuration information and dependencies as dictated by the state machine.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If servers manage and configure large numbers of mobile devices, then configuration control is centralized, but server processing demands increase and scalability deteriorates

Engineering Contradiction:
Improveconfiguration controlVSAvoidscalability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the configuration management system into server-side policy definition and device-side autonomous execution. The server defines compliance policies and configuration parameters, while mobile devices independently execute state machines to apply configurations. This segmentation distributes processing load from servers to devices, improving scalability while maintaining centralized policy control.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Mobile devices are empowered to autonomously manage their own configuration processes by executing state machines locally. Devices automatically process configuration information, manage dependencies, and apply compliance settings without requiring continuous server intervention. This self-service capability reduces server processing demands and enables scalable deployment across large device fleets.

Inventive Principle:
Principle #25Self-service

2Reliability

If servers manage configuration processes for mobile devices, then centralized control is maintained, but network activity and server latency increase

Engineering Contradiction:
Improvecentralized controlVSAvoidserver latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The server performs preliminary actions by defining complete configuration policies and parameters before device execution. Configuration information is prepared and transmitted to devices in advance, enabling devices to autonomously execute state machines without requiring real-time server processing. This preliminary action reduces server latency and network activity during configuration deployment.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If manual configuration processes are used for mobile devices, then flexibility is maintained, but configuration errors increase and productivity decreases

Engineering Contradiction:
Improveconfiguration flexibilityVSAvoidconfiguration accuracy
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent replaces manual mechanical configuration processes with automated state machine execution on mobile devices. State machines provide structured, repeatable configuration sequences that eliminate human error while maintaining flexibility through configurable parameters and policies. This automation ensures consistent, accurate configuration application across devices while preserving adaptability through policy definitions.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentEP3807754B1Implementation of compliance settings by a mobile device for compliance with a configuration scenario
Publication Date: 2025.03.26 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP3807754B1 patent drawingFigure 1
  • EP3807754B1 patent drawingFigure 2A
  • EP3807754B1 patent drawingFigure 2B

AI summary

Embodiments described herein are directed to implementing compliance settings by a computing device for bringing the computing device into compliance with a configuration scenario. For instance, a computing device may receive, from a server, configuration information describing compliance settings for implementing by the computing device to bring the computing device into compliance with a configuration scenario. Moreover, the computing device may identify a state machine indicated by the configuration information that describes a configuration process for implementing the compliance settings and execute the state machine to configure the computing device with the compliance settings.