Stateful Cache Synchronization for Mobile Device Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional mobile device management systems experience excessive traffic and delayed detection of configuration changes due to lack of awareness between mobile devices and management services, leading to inefficient bandwidth usage and increased total cost of ownership, especially for devices with limited connectivity.

Innovation Solution

Implementing a stateful cache layer on both mobile devices and management services to synchronize states periodically, allowing for immediate detection and handling of changes, and enabling unsolicited management sessions for configuration updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If same information is transmitted periodically between mobile device and management service, then the management service can maintain awareness of device state, but excessive traffic is generated due to duplicate information transmission

Engineering Contradiction:
Improvemanagement service awareness of device stateVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The client maintains a local cache of management information and proactively detects changes before periodic synchronization occurs. This preliminary detection mechanism allows the system to prepare change notifications in advance, eliminating the need for the management service to repeatedly query or transmit the same information during each periodic session.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The client implements a change detection mechanism that continuously monitors for modifications to cached management information. When changes are detected, the client immediately notifies the management service, creating a feedback loop that keeps the service aware of device state without requiring full periodic retransmission of all information.

Inventive Principle:
Principle #23Feedback

2Reliability

If periodic management sessions are used to synchronize information, then the management service can update device configuration, but lag time occurs between actual configuration changes on device and detection by management service

Engineering Contradiction:
Improveconfiguration change detection accuracyVSAvoiddetection delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The client proactively monitors for configuration changes and prepares change notifications immediately when modifications occur, rather than waiting for the next scheduled periodic session. This preliminary action eliminates the detection lag by ensuring changes are reported as soon as they happen.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system transitions from static periodic synchronization to dynamic event-driven notification. The client adapts its behavior based on actual configuration changes, immediately initiating communication with the management service when changes occur, rather than following a rigid periodic schedule.

Inventive Principle:
Principle #15Dynamics

3Reliability

If full management sessions are conducted periodically, then complete device state can be synchronized, but bandwidth usage increases due to repeated transmission of unchanged information

Engineering Contradiction:
Improvedevice state synchronization completenessVSAvoiddata transmission volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system extracts and transmits only the specific changed elements from the cached management information, rather than retransmitting the entire configuration set. The client identifies and isolates only those nodes or parameters that have changed, sending minimal necessary data to maintain synchronization completeness.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of performing complete periodic synchronization, the system applies partial action by transmitting only the necessary changed portions of configuration data. This selective transmission maintains synchronization reliability while significantly reducing data volume.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS7676573B2Node monitor client cache synchronization for mobile device management
Publication Date: 2010.03.09 MICROSOFT TECHNOLOGY LICENSING LLC
  • US7676573B2 patent drawing
  • US7676573B2 patent drawing
  • US7676573B2 patent drawing

AI summary

A stateful cache layer is created at a mobile device client that tracks the state on both the mobile device and management service. The states are synchronized between the mobile device and the management service on every management session. Through the statefulness of the cache layer, unauthorized changes on the mobile device are detected and accordingly handled such as internal correction or reporting to the management service for actionable instructions. A cache layer on the management server is configured to identify organizational policy changes that affect specific devices and initiate unsolicited immediate management sessions to update the configuration to the specific devices.