OMA DM Extension for Vendor-Specific Mobile Settings
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current device management systems face challenges in efficiently managing the increasing number of parameters and settings for mobile devices, as they are cumbersome and difficult to implement, especially when dealing with non-standardized settings not covered by existing OMA DM standards.
Innovation Solution
The introduction of an OMA DM extension that utilizes an XML schema to manage non-standardized settings and parameters by extending the OMA DM tree structure, allowing for remote or local creation, deletion, modification, and querying of these settings, thereby enhancing the functionality of OMA DM beyond standard access information management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing OMA DM structures are used to manage device settings, then standardization is maintained, but non-standardized parameters and settings cannot be managed
Solution Approach 1:
The patent segments the device management functionality by separating standardized OMA DM parameters from vendor-specific non-standardized parameters. This is achieved by creating distinct management objects: one for standard OMA DM settings and another for vendor-specific extensions, allowing each to be managed independently while maintaining overall system organization.
Solution Approach 2:
The patent implements nesting by embedding vendor-specific management objects within the existing OMA DM management structure. The vendor-specific parameters are nested as child nodes under the parent OMA DM management framework, allowing the standardized structure to contain and orchestrate non-standardized extensions without requiring a complete structural overhaul.
2Adaptability or versatility
If new management structures are created to handle non-standardized settings, then all settings can be managed, but implementation becomes cumbersome and difficult
Solution Approach 1:
The patent creates a universal management framework where a single OMA DM management structure can handle both standardized and vendor-specific parameters. The vendor-specific management objects are designed with the same interface and operational patterns as standard OMA DM objects, allowing the existing OMA DM infrastructure to manage diverse parameters uniformly without requiring separate implementation paths.
Solution Approach 2:
The patent introduces an intermediary layer in the form of vendor-specific management objects that act as mediators between the standardized OMA DM framework and proprietary device settings. These intermediary objects translate vendor-specific parameter requirements into the standardized OMA DM format, enabling seamless integration without direct modification of the core OMA DM structures.
3Adaptability or versatility
If the OMA DM functionality is extended to manage additional settings, then device provisioning becomes more comprehensive, but the workload on the DM server increases
Solution Approach 1:
The patent implements self-service mechanisms where the mobile device autonomously manages vendor-specific parameters using locally stored profiles and configurations. The device can perform self-provisioning and self-configuration for non-standardized settings without requiring constant server intervention, thereby reducing the DM server workload while maintaining comprehensive settings management.
Solution Approach 2:
The patent applies preliminary action by pre-configuring vendor-specific parameters and settings in profile files that are downloaded to the mobile device in advance. These pre-configured profiles contain default values and configuration templates that the device can automatically apply, reducing the need for real-time server processing and minimizing the ongoing workload on the DM server.
Data Source
AI summary
A method and system extends the functionality of the Open Mobile Alliance (OMA) Device Management (DM) standard to manage vendor specific configuration parameters and settings. An OMA DM structure is provided as an extension to the tree structure of the OMA DM standard. The OMA DM extension allows selected vendor specific parameters and settings to be managed under the OMA DM protocol.