Automated Scripting for Enterprise Mobility Management

Solution Overview

Problem

Enterprises face challenges in implementing custom feature sets in Enterprise Mobility Management (EMM) systems due to the lack of built-in support, leading to time-consuming and costly manual scripting, especially for devices with inconsistent connectivity.

Innovation Solution

A management server system that enables administrators to enroll user devices, install a management agent, and assign functional groups, allowing for automated scripting of custom feature sets that can monitor and respond to triggering events without further input, including actions like launching applications or manipulating files.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual scripting is used to add custom feature sets to EMM systems, then the feature can be implemented, but the process becomes time-consuming and expensive

Engineering Contradiction:

Improvecustom feature set implementationVSAvoidimplementation lead time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system enables self-service through automated scripting where the EMM system itself generates and deploys scripts without requiring external manual intervention. The scripting engine automatically creates deployment packages and pushes them to target devices, allowing the system to serve itself rather than relying on manual scripting operations.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by pre-configuring script templates and deployment parameters before actual feature implementation. Administrators can define script patterns and deployment rules in advance, which are then automatically instantiated when features need to be deployed, eliminating the need for ad-hoc manual scripting each time a feature is added.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If manual scripting is used to add custom feature sets to EMM systems, then the feature can be implemented, but specialized programming knowledge and labor are required

Engineering Contradiction:

Improvecustom feature set implementationVSAvoidimplementation complexity

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system enables self-service through automated scripting where the EMM system itself generates and deploys scripts without requiring external manual intervention. The scripting engine automatically creates deployment packages and pushes them to target devices, allowing the system to serve itself rather than relying on manual scripting operations.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system introduces an intermediary scripting engine that acts as a mediator between administrative intent and device implementation. This engine translates high-level feature definitions into executable deployment scripts, shielding administrators from complex programming details while maintaining implementation flexibility.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Reliability

If custom features are implemented for devices with inconsistent connectivity, then device autonomy is improved, but the complexity of managing disconnected devices increases

Engineering Contradiction:

Improvedevice autonomy in disconnected scenariosVSAvoidfeature set complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system applies segmentation by dividing the feature deployment process into discrete, modular script components that can be independently managed and deployed. Each script represents a self-contained unit of functionality that can operate autonomously on devices, allowing complex features to be broken down into manageable segments that don't require continuous server connectivity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system performs preliminary action by pre-configuring script templates and deployment parameters before actual feature implementation. Administrators can define script patterns and deployment rules in advance, which are then automatically instantiated when features need to be deployed, eliminating the need for ad-hoc manual scripting each time a feature is added.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11509523B2Automated scripting for managed devices

Publication Date: 2022.11.22 OMNISSA LLC

AI summary

Systems and methods are included for providing feature sets to groups of managed user devices within an enterprise mobility management (EMM) system. A feature set can enable a user device to detect one or more triggering events, and in response, automatically perform a specified action. An administrator can request a feature set using an interface provided by a management server. The management server can enroll the user device, install a management agent on the user device, and automatically build and deliver the requested feature set to the user device. After receiving the feature set, the management agent of the user device can monitor for recurring triggering events without further intervention from the management server.