Matrix-Based OMA DM Configuration for Preloaded Apps

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing Open Mobile Alliance (OMA) device management (DM) protocol is inflexible, limiting the ability to add or delete nodes, which restricts the number of supported applications and requires lengthy approval processes through a working group, making it difficult to manage and configure preloaded applications on mobile communication devices.

Innovation Solution

Implementing a matrix data structure within the OMA DM tree, where columns are indexed by brand identity and rows by service identity, allowing for configuration values that include function calls, enabling remote configuration and easier management of preloaded applications without altering the OMA DM tree definition.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the OMA DM protocol uses a fixed tree structure with predefined nodes, then the protocol maintains stability and standardization, but it becomes inflexible and difficult to add or delete applications

Engineering Contradiction:
Improveflexibility to add or delete applicationsVSAvoidcomplexity of managing preloaded applications
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the application management system into two parts: a fixed OMA DM tree structure (for stability) and a separate matrix data structure (for flexibility). The matrix is divided into rows representing applications and columns representing configuration parameters, allowing independent modification without affecting the core protocol structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a matrix data structure as an intermediary between the fixed OMA DM protocol and the variable application configurations. This matrix acts as a mediator that translates flexible application management requirements into the structured format required by the OMA DM protocol, enabling both flexibility and standardization to coexist.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If the OMA DM tree structure is modified to support new applications, then application versatility improves, but it requires lengthy working group approval processes

Engineering Contradiction:
Improvespeed of configuring preloaded applicationsVSAvoidtime for working group approval
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent performs preliminary configuration by pre-defining the matrix data structure with all possible application configurations before runtime. This allows the system to quickly select and apply appropriate configurations without requiring protocol modifications or working group approvals during deployment, significantly reducing configuration time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables dynamic configuration changes by modifying the matrix data structure parameters (application IDs, configuration values, row/column assignments) rather than changing the underlying OMA DM protocol structure. This allows rapid adaptation to new applications through parameter updates alone, bypassing lengthy approval processes.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If multiple preloaded applications are supported with custom configurations, then service coverage improves, but memory management becomes more difficult

Engineering Contradiction:
Improvenumber of supported applicationsVSAvoidmemory management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal matrix data structure that can accommodate multiple applications with different configurations using the same framework. Each application is represented as a row in the matrix with standardized columns for configuration parameters, allowing the system to manage diverse applications uniformly and simplifying memory allocation and management.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9681251B1Customization for preloaded applications
Publication Date: 2017.06.13 T MOBILE INNOVATIONS LLC
  • US9681251B1 patent drawing
  • US9681251B1 patent drawing
  • US9681251B1 patent drawing

AI summary

A mobile communication device. The mobile communication device comprises a processor, a memory, and an application stored in the memory that, when executed by the processor, parses an open mobile alliance (OMA) device management (DM) tree comprising a node that identifies a matrix, wherein the matrix comprises columns indexed by a brand identity, and rows indexed by a service identity, wherein the matrix cells store configuration values and wherein some configuration values are function calls, based on a brand identity of the mobile communication device, selects an entry of the matrix, and based on the selected entry, configures a preloaded application stored in the memory, whereby the mobile communication device may be configured remotely through a rule-based mechanism.