Automatic Mobile Device Configuration via XML Application Definition Files

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mobile device technologies face challenges in automatically configuring multiple wireless devices for server-side applications without human intervention, particularly for users without a technical background, due to incompatible operating systems and display characteristics, and the need for complex installation programs that require cable connections to PCs.

Innovation Solution

A method that involves generating and transmitting application definition files, formatted in XML, to mobile devices, which describe user interface formats, network message formats, and data storage formats, allowing for automatic configuration and installation of server-side applications across various devices via wireless connectivity, using virtual machine software that interprets these files to present interfaces and manage data exchange.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If complex installation programs are used to enable mobile devices to access server-side applications, then application functionality is achieved, but ease of operation deteriorates due to technical complexity and requirement for PC connections

Engineering Contradiction:
Improveease of installationVSAvoidinstallation program complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The mobile device automatically configures itself by receiving and processing a configuration document from the server. The device autonomously determines its capabilities, selects appropriate server-side applications, and configures itself without requiring manual intervention or PC connections, thereby eliminating the need for complex installation programs while maintaining full application functionality.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical cable connection system (cradle/PC connection) with a wireless communication system. The configuration document is transmitted via wireless network to the mobile device, eliminating the need for physical cable connections and PC-based installation programs, thus simplifying the installation process while maintaining application access.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Adaptability or versatility

If server-side applications are customized for each mobile device type, then adaptability is improved, but device complexity increases due to multiple modifications required

Engineering Contradiction:
Improvedevice compatibilityVSAvoidserver modification complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The configuration document is segmented into distinct sections: device capability descriptions, server-side application definitions, and mapping relationships. This segmentation allows the server to maintain a single standardized application while the mobile device interprets different portions of the document according to its specific capabilities, achieving device-specific customization without modifying the server-side application code.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of modifying server-side applications for different device types, the system changes the parameters of the configuration document to describe device-specific capabilities and interfaces. The server maintains a single application definition, while the mobile device receives customized configuration parameters that map the application to its specific hardware and operating system characteristics.

Inventive Principle:
Principle #35Parameter changes

3Loss of time

If manual configuration is performed for each mobile device, then configuration accuracy is improved, but loss of time increases due to manual intervention requirements

Engineering Contradiction:
Improveconfiguration timeVSAvoidautomatic configuration level
Core Design Contradiction:
Loss of timeVSExtent of automation

Solution Approach 1:

The server pre-generates the configuration document containing all necessary application definitions, interface descriptions, and mapping relationships before the mobile device needs to access the applications. This preliminary preparation allows the mobile device to automatically configure itself upon receiving the document, eliminating time-consuming manual configuration steps while ensuring accurate setup.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The mobile device performs self-configuration by automatically processing the configuration document, determining its own capabilities, selecting appropriate applications, and setting up all necessary parameters without human intervention. This self-service approach dramatically reduces configuration time compared to manual setup, while maintaining configuration accuracy through systematic automated processing.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP1881715B1Automatic mobile device configuration
Publication Date: 2012.08.22 BLACKBERRY LTD
  • EP1881715B1 patent drawingFigure 1
  • EP1881715B1 patent drawingFigure 2
  • EP1881715B1 patent drawingFigure 3

AI summary

A remote wireless device registers with a server. Responsively, the server determines the identity of a server-side application associated with a user of the remote wireless device. The server may then generate an application definition file specific to the server-side application and to the remote wireless device. The application definition file may contain definitions for: a user interface format; a format for network messages; and a format for storing data. Using these definitions, the wireless device may receive data generated by the server-side application and formatted in accordance with the definitions. The wireless device may then present a user interface for the server-side application. The application definition file may be an Extensible Markup Language (XML) file. Advantageously, configuration of devices is more efficiently accomplished.