Firmware upgrade system and method in a device management architecture

• US 8,307,095 B2
• Filed: 06/21/2010
• Issued: 11/06/2012
• Est. Priority Date: 06/21/2010
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Research In Motion Limited (Blackberry Limited)
• Inventors: Clark, David Richard, Acharya, Vinaykumar, Carter, Jason Lee, Parry, Thomas
• Primary Examiner(s): VU, VIET DUY
• Application Number:
  US12/819,987
• Publication Number:
  US 20110314462A1
• Time in Patent Office: 869 Days
• Field of Search: 709/217, 709/219, 709/223, 709/225, 709/227, 709/228, 709/229, 709/250
• US Class Current: 709/227
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

In one embodiment, a device firmware upgrade scheme is disclosed for upgrading a device image of a mobile communications device. A device management session is established between the mobile communications device and a first server using a first protocol. Upon obtaining identity information of a second server operable to compute or otherwise determine a customized upgrade process, a device inventory is transmitted to the second server using a second protocol. Upon receiving the customized upgrade process, the mobile communications device downloads one or more upgrade files from one or more resources. Thereafter, the mobile communications device is operable to provide a status indication to the first server using the first protocol.

Claims

1. A device firmware upgrade method, comprising:

obtaining from a server, using a first protocol, identity information of an upgrade server adapted to operate with respect to a mobile communications device in a second protocol;

transmitting device image information relating to a device image associated with said mobile communications device to said upgrade server using said second protocol for computing a customized upgrade process with respect to said mobile communications device based on said device image information;

receiving a transaction from said upgrade server in said second protocol, said transaction including information defining said customized upgrade process computed at said upgrade server responsive to said device image information, and identity information of one or more content servers having upgrade resources;

issuing a download transaction to at least one of said one or more content servers based on said identity information received via said second protocol, said download transaction including said customized upgrade process computed at said upgrade server;

responsive to issuing said download transaction, receiving one or more upgrade files from said one or more content servers based on said customized upgrade process; and

upon completion of upgrading at least a portion of said mobile communications device'"'"'s device image based on said one or more upgrade files, providing a status indication to said server using said first protocol.

2. The method of claim 1, wherein said device image information comprises an inventory of application programs on said mobile communications device.

3. The method of claim 1, wherein said device image information comprises an inventory of non-application programs on said mobile communications device.

4. The method of claim 1, wherein said device image information comprises an inventory of user preferences and their status with respect to said mobile communications device.

5. The method of claim 1, wherein said server operating in said first protocol comprises an Open Mobile Alliance (OMA) Device Management (DM) server using OMA DM protocol.

6. The method of claim 1, wherein said upgrade server comprises an Original Equipment Manufacturer (OEM) server and said second protocol comprises HyperText Transfer Protocol (HTTP).

7. The method of claim 6, wherein said OEM server is hosted by at least one of an enterprise network and a carrier network and said HTTP is a secure HTTP.

8. The method of claim 1, wherein said identity information of said upgrade server is obtained via an Upgrade Details Document from said server operating in said first protocol.

9. The method of claim 8, wherein said Upgrade Details Document is obtained after receiving a Firmware Update Management Object (FUMO) Exec command from said server in a device management session with said server.

10. The method of claim 1, wherein said one or more upgrade files are co-located on a single content server.

11. The method of claim 1, wherein said one or more upgrade files are located on multiple content servers.

12. A mobile communications device, comprising:

a processor connected to a communication subsystem;

a persistent memory storage having a device management (DM) module, said DM module operating under control of said processor and configured to engage in a device management session with a server using a first protocol and to obtain from said server identity information of an upgrade server adapted to operate with respect to said mobile communications device in a second protocol; and

said processor and DM module further configured to;

effectuate transmission of device image information relating to a device image associated with said mobile communications device to said upgrade server using said second protocol for computing a customized upgrade process with respect to said mobile communications device based on said device image information;

process a transaction received from said upgrade server, said transaction including information defining said customized upgrade process computed at said upgrade server responsive to said device image information, and identity information of one or more content servers having upgrade resources;

issue a download transaction to at least one of said one or more content servers based on said identity information received via said second protocol, said download transaction including said customized upgrade process computed at said upgrade server;

responsive to issuing said download transaction, receive one or more upgrade files from one or more content servers based on said customized upgrade process; and

provide a status indication to said server using said first protocol upon completion of upgrading at least a portion of said mobile communications device'"'"'s device image based on said one or more upgrade files.

13. The mobile communications device of claim 12, wherein said device image information comprises an inventory of application programs on said mobile communications device.

14. The mobile communications device of claim 12, wherein said device image information comprises an inventory of non-application programs on said mobile communications device.

15. The mobile communications device of claim 12, wherein said device image information comprises an inventory of user preferences and their status with respect to said mobile communications device.

16. The mobile communications device of claim 12, wherein said first protocol comprises Open Mobile Alliance (OMA) Device Management (DM) (OMA DM) protocol.

17. The mobile communications device of claim 12, wherein said second protocol comprises a HyperText Transfer Protocol (HTTP) operable with an Original Equipment Manufacturer (OEM) server.

18. The mobile communications device of claim 12, wherein said second protocol comprises a secure HyperText Transfer Protocol (HTTP) operable with an Original Equipment Manufacturer (OEM) server.

19. The mobile communications device of claim 12, wherein said identity information of said upgrade server is obtained via an Upgrade Details Document received from said server via said first protocol.

20. The mobile communications device of claim 19, further comprising a component configured to process a Firmware Update Management Object (FUMO) Exec command from said server, wherein said Upgrade Details Document is obtained after receiving said FUMO Exec command.