Data Driven User Interface for Enterprise Device Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Configuring device and application settings across multiple devices in an enterprise setting is cumbersome and inefficient due to the need for multiple updates in EMM systems, often delaying the availability of new features.
Innovation Solution
A data-driven user interface (DDUI) system that allows administrators to configure device settings by generating a schema file from an application store, enabling quick distribution of settings across devices without updating the administrator console, device management server, or agent application.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional EMM systems are used to configure device settings, then device configuration can be managed across enterprise devices, but the process is cumbersome and requires multiple updates to the EMM server, administrator console, and agent application, significantly delaying the availability of new features
Solution Approach 1:
The patent extracts the configuration schema from the complex EMM system infrastructure and places it directly on the device via an agent application. This removes the need for updates to the EMM server, administrator console, and other central components when new device features are deployed. The schema file containing configuration options is downloaded directly to the device, bypassing the traditional multi-component update chain.
Solution Approach 2:
The device agent application autonomously downloads and processes configuration schemas directly from device manufacturer sources without requiring manual intervention or updates to central EMM components. The agent self-configures by retrieving schema files and applying them locally, enabling rapid deployment of new features without the administrative overhead of coordinating updates across multiple system components.
2Adaptability or versatility
If the EMM server and administrator console are updated to support new device features, then new features become available for configuration, but the update process is time-consuming and may never be completed for non-critical features
Solution Approach 1:
The configuration schema is prepared in advance by device manufacturers and made available for direct download by the device agent. This preliminary preparation eliminates the need for real-time updates to the EMM server and administrator console when new features are released. The schema file is ready ahead of time and can be immediately retrieved and applied by the device agent upon feature release.
Solution Approach 2:
Instead of pushing configuration capabilities from the EMM server down to devices, the patent inverts the flow by having devices pull configuration schemas directly from manufacturer sources. This reversal eliminates the bottleneck of updating central EMM components, as the configuration data flows directly to where it is needed without requiring intermediary system updates.
3Reliability
If multiple components (EMM server, administrator console, agent application) are updated simultaneously, then comprehensive feature support is achieved, but the complexity and time required for deployment increases significantly
Solution Approach 1:
The patent extracts the configuration schema from the complex multi-component EMM update process and delivers it directly to the device agent. This extraction simplifies the deployment process to a single action: the agent downloading and applying the schema file locally. The complex coordination of updating servers, consoles, and agents simultaneously is replaced by a straightforward direct-download approach that maintains complete feature support without the operational complexity.
Data Source
AI summary
Examples described here include systems and methods for configuring device settings for a number of user devices across an enterprise. A management server can provide a user interface at an administrator console for creating a profile and identifying an associated device type. The management server can then retrieve a schema file associated with the device type. Based on information in the schema file, the management server can populate the user interface at the administrator console with available configuration options pertaining to the device type. An administrator can configure the options and send instructions to the management server to deploy the profile across the number of user devices. The management server can instruct each user device to download a device configuration application from an application repository and transmit the settings information to an agent application of the user device that has permission to configure the device configuration application.