Method of receiving, storing, and providing device management parameters and firmware updates to application programs within a mobile device

• US 8,117,293 B1
• Filed: 01/05/2005
• Issued: 02/14/2012
• Est. Priority Date: 01/05/2005
• Status: Active Grant

• Current Assignee: Insignia Solutions Plc (America's Suppliers, Inc.)
• Original Assignee: Smith Micro Software Incorporated
• Inventors: Anderson, Ian P.
• Primary Examiner(s): Meky, Moustafa M
• Application Number:
  US11/030,373
• Time in Patent Office: 2,596 Days
• Field of Search: 709/217, 709/219, 709/223, 709200-203, 709/218, 709/227
• US Class Current: 709/223
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 12/35 Protecting application or service provisioning, e.g. securing SIM application provisioning
• CPC Class Codes: H04W 12/37 Managing security policies for mobile devices or for controlling mobile applications
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring

Abstract

A method for the efficient persistent storage of Device Management (DM) information on a mobile device is provided. More specifically, the present design provides methods for applications to access and update this information consistent with the Open Mobile Alliance (OMA) DM standard by extending the OMA SyncML DM standard and providing a physical implementation of a tree management data structure. This implementation enables device management parameters, originating from server applications to be received, stored and accessed by a client mobile device. The present design incorporates centralized access and security rights management for securing DM information such that only permitted applications may access and update this information. In addition, the present design provides a method for retrieving firmware update packages, saving the package as specified by the OMA Firmware Update Management Object standard, and triggering the update process to apply the package by an update agent.

Claims

1. A method for exchange of information between an Open Management Alliance (OMA) Synchronous Markup Language (SyncML) Device Management (DM) compliant server and a mobile device, said method comprising:

Receiving one or more over-the-air provisioning parameters from an OMA SyncML DM compliant server;

Storing said provisioning parameters received from the OMA SyncML DM compliant server in a management tree data structure within the mobile device;

Retrieving DM information stored in the mobile device;

Applying rights management via an Access Control List, wherein applying rights management comprises the mobile device evaluating the Access Control List against the DM information retrieved and selectively applying DM information retrieved in accordance with the Access Control List; and

Enabling application programs to access the provisioning parameters received from the OMA SyncML DM compliant server using a pseudo hostname, wherein access is granted based on rights management according to the management tree data structure and the Access Control Lists.

2. The method of claim 1, the mobile device further comprising an open management client, wherein said open management client further comprises a software component to handle the DM communication session allowing the mobile device to interoperate with an OMA DM compliant server application from one or more manufacturers through a communications channel using one or more access protocols.

3. The method of claim 1, the mobile device further comprising an open management client, wherein said open management client further comprises a software component to extend the OMA SyncML DM standard allowing for a plurality of software applications to communicate with a DM server.

4. The method of claim 1, the mobile device further comprising an open management client, wherein said open management client further comprises a software component to receive one or more synchronous alert messages from a DM server and to forward said alerts to a man machine interface.

5. The method of claim 1, the mobile device further comprising an open management client, wherein said open management client further comprises a software component to route the appropriate response back to the originating DM server, based on user input.

6. The method of claim 1, wherein said storing further comprises implementing a management tree data structure to persistently store named key/value pairs in accordance with the abstraction defined in the OMA DM standard consisting of named nodes each containing one or more sub-nodes or one or more leaves (i.e. name/value pairs).

7. The method of claim 6, wherein said management tree data structure further comprises implementing a data structure supporting both static and dynamic elements within the tree.

8. The method of claim 6, wherein said management tree data structure further comprises implementing a mechanism enabling external software components to manage branches of the DM tree.

9. The method of claim 6, wherein said management tree data structure further comprises implementing a routing adapter application mechanism to provide all the callback functions to the SyncML core.

10. The method of claim 1, wherein said storing further comprises a management tree data structure implementing how and where the nodes of the DM tree exist and where the associated data values and metadata are stored.

11. The method of claim 1, wherein said storing further comprises implementing an external storage mechanism to allow a data value for a node to be stored external to the management tree data structure.

12. The method of claim 1, the mobile device further comprising an open management client, wherein said open management client further comprises a software component providing access to a tree management data structure by implementing a plurality of callback functions required by a SyncML protocol supporting all received SyncML commands (e.g. add and delete nodes, get and replace values, Exec, etc,).

13. The method of claim 1, the mobile device further comprising an open management client, wherein said open management client further comprises writing the data structure to flash memory or a flash file system.

14. The method of claim 1, wherein said accessing further comprises implementing components to support locally stored applications to retrieve, store and provide DM information physically stored within the mobile device.

15. A method for exchanging information executing in a mobile device, comprising:

receiving provisioning parameters from an Open Management Alliance (OMA) Synchronous Markup Language (SyncML) Device Management (DM) compliant server;

storing said provisioning parameters received from the OMA SyncML DM compliant server in a management tree data structure within the mobile device;

applying rights management via an Access Control List, wherein applying rights management comprises the mobile device evaluating the Access Control List against the information retrieved and selectively applying information retrieved in accordance with the Access Control List; and

enabling application programs to access the provisioning parameters received from the OMA SyncML DM compliant server using a pseudo hostname, wherein access is granted based on rights management according to the management tree data structure and to the Access Control List.

16. The method of claim 15, the mobile device further comprising an open management client, wherein said open management client further comprises a software component to handle the communication session allowing the mobile device to interoperate with a server application from one or more manufacturers through a communications channel using one or more access protocols.

17. The method of claim 15, the mobile device further comprising an open management client, wherein said open management client further comprises a software component to extend standards allowing for a plurality of software applications to communicate with the server.

18. The method of claim 15, the mobile device further comprising an open management client, wherein said open management client further comprises a software component to receive one or more synchronous alert messages from the server and to forward said alerts to a man machine interface.

19. The method of claim 15, the mobile device further comprising an open management client, wherein said open management client further comprises a software component to route the appropriate response back to an originating server, based on user input.

20. A mobile device comprising:

means for receiving provisioning parameters from an Open Management Alliance (OMA) Synchronous Markup Language (SyncML) Device Management (DM) compliant server;

means for storing said provisioning parameters received from the OMA SyncML DM compliant server in a management tree data structure within the mobile device;

means for applying rights management via an Access Control List, wherein applying rights management comprises the mobile device evaluating the Access Control List against the information retrieved and selectively applying information retrieved in accordance with the Access Control List; and

means for enabling application programs to access the provisioning parameters received from the OMA SyncML DM compliant server using a pseudo hostname, wherein access is granted based on rights management according to the management tree data structure and the Access Control List.

21. The mobile device of claim 20, further comprising a software component to handle the communication session allowing the mobile device to interoperate with a server application from one or more manufacturers through a communications channel using one or more access protocols.

22. The mobile device of claim 20, further comprising a software component to extend standards allowing for a plurality of software applications to communicate with the OMA SyncML DM compliant server.

23. The mobile device of claim 20, further comprising a software component configured to receive one or more synchronous alert messages from the OMA SyncML DM compliant server and to forward said alerts to a man machine interface.

24. The mobile device of claim 20, wherein said client further comprises a software component to route the appropriate response back to an originating server, based on user input.