Method and apparatus for dynamic extension of device management tree data model on a mobile

• US 20050282533A1
• Filed: 03/22/2005
• Published: 12/22/2005
• Est. Priority Date: 03/22/2004
• Status: Active Grant

• Current Assignee: Google Technology Holdings LLC (Alphabet Inc.)
• Original Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Inventors: Klots, Boris, Bruner, John D., Prabandham, Harish, Draluk, Vadim, Petushkov, Denis A.
• Granted Patent: US 7,242,929 B2
• Time in Patent Office: Days
• US Class Current: 455/418
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04M 2207/18 wireless networks
• CPC Class Codes: H04M 3/42178 by downloading data to substation equipment
• CPC Class Codes: H04W 8/22 Processing or transfer of terminal data, e.g. status or physical capabilities
• CPC Class Codes: H04W 8/245 from a network towards a terminal

Abstract

A mobile device having a framework (901) comprising a logical device management tree (903), a device management engine (905), and a plurality of application specific logical device management sub-trees (907, 909) logically connected to the logical device management tree.

Claims

1. A mobile device having a framework comprising:

a logical device management tree;

a device management engine; and

a plurality of application specific logical device management sub-trees logically connected to the logical device management tree.

2. The mobile station of claim 1, wherein the logical device management tree comprises a capability for upgrade wherein a new application specific logical device management sub-tree may be installed and logically connected to the logical device management tree.

3. The mobile station of claim 2, wherein each of the plurality of application specific logical device management sub-trees comprises metadata.

4. The mobile station of claim 2, wherein each of the plurality of application specific logical device management sub-trees comprises initialization scripts.

5. The mobile station of claim 2, wherein each of the plurality of application specific logical device management sub-trees comprises plug-ins.

6. The mobile station of claim 4, wherein the initialization scripts are XML scripts.

7. A method of updating a device management tree (DMT) on a mobile device application framework comprising:

receiving by a mobile station a bundle associated with an installable application;

determining whether the bundle contains DMT data;

determining whether the bundle is registered in an existing DMT;

determining whether a file type is contained by the bundle; and

generating unique filenames for the files of the file type contained in the bundle, associating the unique filenames with the files, and copying the files if the bundle is not registered in the existing DMT.

8. The method of claim 7, further comprising generating a log error message if the bundle is registered in the existing DMT.

9. The method of claim 7, wherein the step of determining whether a file type is contained by the bundle further comprises:

determining whether metadata files are contained by the bundle, generating unique filenames for the metadata files contained in the bundle, associating the unique filenames with the metadata files and copying the metadata files.

10. The method of claim 7, wherein the step of determining whether a file type is contained by the bundle further comprises:

determining whether plug-in files are contained by the bundle, generating unique filenames for the plug-in files contained in the bundle, associating the unique filenames with the plug-in files and copying the plug-in files.

11. The method of claim 7, wherein the step of determining whether a file type is contained by the bundle further comprises:

determining whether script files are contained by the bundle, and loading the script files.

12. The method of claim 7, further comprising invoking a native function and reloading metadata.

13. The method of claim 12, further comprising loading a plug-in file.

14. The method of claim 13, further comprising executing a script file.

15. The method of claim 14, wherein the script file is a SyncML script file.