Firmware Upgrade System and Method in a Device Management Architecture

• US 20110314462A1
• Filed: 06/21/2010
• Published: 12/22/2011
• 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, Parry, Thomas, Carter, Jason Lee
• Granted Patent: US 8,307,095 B2
• Time in Patent Office: Days
• US Class Current: 717/169
• 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 first server, using a first protocol, identity information of a second server adapted to determine a customized upgrade process with respect to a mobile communications device;

transmitting device image information relating to a device image associated with said mobile communications device to said second server using a second protocol;

receiving information defining an upgrade process from said second server, said upgrade process being customized relative to said mobile communications device and said upgrade process including identity information of one or more resources;

downloading one or more upgrade files from said one or more resources based on said 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 first 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 first server comprises an Open Mobile Alliance (OMA) Device Management (DM) server and said first protocol comprises OMA DM protocol.

6. The method of claim 1, wherein said second 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 a carrier network and said HTTP is a secure HTTP.

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

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 first server upon commencing a device management session with said first 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 component configured to engage in a device management session with a first server using a first protocol and to obtain from said first server identity information of a second server adapted to determine a customized upgrade process with respect to said mobile communications device;

a component configured to transmit device image information relating to a device image associated with said mobile communications device to said second server using a second protocol;

a component configured to process information defining an upgrade process received from said second server, said upgrade process being customized relative to said mobile communications device and said upgrade process including identity information of one or more resources;

a component configured to download one or more upgrade files from one or more resources based on said upgrade process received from said second server; and

a component configured to provide a status indication to said first 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 second server is obtained via an Upgrade Details Document received from said first server.

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 first server, wherein said Upgrade Details Document is obtained after receiving said FUMO Exec command.

21. A device firmware upgrade server, comprising:

a component configured for processing device inventory information received from a mobile communications device;

a component for determining a customized upgrade process with respect to said mobile communications device based on said device inventory information; and

a component for transmitting said customized upgrade process to said mobile communications device, wherein said customized upgrade process includes identity information of one or more resources having one or more downloadable upgrade files for said mobile communications device.

22. The device firmware upgrade server of claim 21, wherein said device inventory information comprises an inventory of application programs on said mobile communications device.

23. The device firmware upgrade server of claim 21, wherein said device inventory information comprises an inventory of non-application programs on said mobile communications device.

24. The device firmware upgrade server of claim 21, wherein said device inventory information comprises an inventory of user preferences and their status with respect to said mobile communications device.

25. The device firmware upgrade server of claim 21, further comprising a component for effectuating a secure HyperText Transfer Protocol (HTTPS) communication path with said mobile communications device.