COST OPTIMIZATION FOR FIRMWARE UPDATES FOR GLOBALLY MOBILE MACHINE-TO-MACHINE DEVICES

• US 20140115574A1
• Filed: 10/24/2012
• Published: 04/24/2014
• Est. Priority Date: 10/24/2012
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Valentine, Eric Lee, Syed, Inayat
• Granted Patent: US 8,938,731 B2
• Time in Patent Office: Days
• US Class Current: 717/172
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

A firmware control management device and a method implemented by the firmware control management device are described herein which are configured to determine whether or not to push a firmware update to a machine-to-machine (M2M) device.

Claims

1. A firmware control management device for determining whether or not to push a firmware update to a machine-to-machine (M2M) device, the firmware control management device comprising:

a processor; and

a memory that stores processor-executable instructions where the processor interfaces with the memory and executes the processor-executable instructions to enable operations as follows;

receive a notification from the M2M device;

retrieve M2M configuration information associated with the M2M device;

obtain information related to firmware associated with the M2M device;

obtain information which indicates a network currently connected to the M2M device;

obtain information related to the network currently connected to the M2M device; and

determine whether or not to push the firmware update to the M2M device based at least on the M2M configuration information, the information related to firmware associated with the M2M device, and the information related to the network currently connected to the M2M device.

2. The firmware control management device of claim 1, wherein after retrieve the M2M configuration information associated with the M2M device and obtain the information related to firmware associated with the M2M device but before obtain the information indicative of the network connected to the M2M device the processor further executes the processor-executable instructions to enable operations as follows:

determine, based on the M2M configuration information and the information related to firmware associated with the M2M device, if firmware that is currently loaded in the M2M device is a latest version;

if the firmware currently loaded in the M2M device is the latest version, then end process since no further firmware updating is needed with respect to the M2M device; and

if the firmware currently loaded in the M2M device is not the latest version, then proceed to obtain information indicative of the network connected to the M2M device.

3. The firmware control management device of claim 1, wherein the processor further executes the processor-executable instructions to obtain the information which indicates the network currently connected to the M2M device by enabling operations as follows:

determine, based on the M2M configuration information, if the M2M device is capable of providing information which identifies the network currently servicing the M2M device;

if the M2M device is not capable of providing the information, then query a remote node to obtain the information indicative of the network connected to the M2M device; and

if the M2M device is capable of providing the information, then send a query to the M2M device to obtain information identifying the network connected to the M2M device.

4. The firmware control management device of claim 3, wherein the processor further executes the processor-executable instructions to query the remote node to obtain information which indicates the network currently connected to the M2M device by enabling operations as follows:

trigger a query to a mobile location center to receive information about a location of the M2M device; and

use a lookup table along with the location of the M2M device to determine the network which is likely connected to the M2M device.

5. The firmware control management device of claim 3, wherein the processor further executes the processor-executable instructions to query the remote node to obtain information which indicates the network currently connected to the M2M device by enabling operations as follows:

trigger a query to an external storage unit to obtain an address where the M2M device is registered; and

use the address to determine the network currently connected to the M2M device.

6. The firmware control management device of claim 3, wherein if the information indicative of the network connected to the M2M device is Global Positioning Satellite (GPS) coordinates of the M2M device then the processor further executes the processor-executable instructions to use a map function along with the GPS coordinates to determine the network currently connected to the M2M device.

7. The firmware control management device of claim 1, wherein the processor further executes the processor-executable instructions to determine whether or not to push the firmware update to the M2M device by enabling operations as follows:

determine if the firmware update is a critical firmware update or a non-critical firmware update;

if the firmware update is a critical firmware update, then push the critical firmware update to the M2M device;

if the firmware update is a non-critical firmware update, the determine if cost of using the network to push the non-critical firmware update to the M2M device exceeds a threshold;

if the cost exceeds the threshold, then do not push the non-critical firmware update to the M2M device;

or

if the cost does not exceed the threshold, then push the non-critical firmware update to the M2M device.

8. The firmware control management device of claim 1, wherein if there is a determination to push the firmware update to the M2M device then the processor further executes the processor-executable instructions to enable operations as follows:

push a single firmware update to the M2M device;

or

push one or more non-critical firmware updates to the M2M device and then push a critical firmware update to the M2M device.

9. The firmware control management device of claim 1, wherein if there is a determination not to push the firmware update to the M2M device then the processor further executes the processor-executable instructions to enable operations as follows:

instruct the M2M device to enter a quiet mode until the M2M device connects to another network.

10. The firmware control management device of claim 1, wherein the processor further executes the processor-executable instructions to enable operations as follows:

send a message to the M2M device instructing the M2M device to send the notification.

11. The firmware control management device of claim 1, wherein the processor further executes the processor-executable instructions to enable operations as follows:

send a message to the M2M device where the message has one or more conditions which when satisfied result in the M2M device sending the notification and once the notification is received then enable a lawful intercept of data which is transmitted from the M2M device.

12. The firmware control management device of claim 1, wherein the information related to firmware associated with the M2M device comprises:

information about current firmware upgrades;

past firmware upgrades;

a number of firmware images to be updated at the M2M device;

an installation order of the firmware images;

dependencies between the firmware images to be updated at the M2M device; and

firmware file size for each of the updates.

13. The firmware control management device of claim 1, wherein the information related to the network currently connected to the M2M device comprises:

data costs associated with using the network to push the firmware update to the M2M device.

14. A method for determining whether or not to push a firmware update to a machine-to-machine (M2M) device, the method implemented by a firmware control management device comprising the steps of:

receiving a notification from the M2M device;

retrieving M2M configuration information associated with the M2M device;

obtaining information related to firmware associated with the M2M device;

obtaining information which indicates a network currently connected to the M2M device;

obtaining information related to the network currently connected to the M2M device; and

determining whether or not to push the firmware update to the M2M device based at least on the M2M configuration information, the information related to firmware associated with the M2M device, and the information related to the network currently connected to the M2M device.

15. The method of claim 14, wherein after the steps of retrieving the M2M configuration information associated with the M2M device and obtaining the information related to firmware associated with the M2M device but before the step of obtaining the information which indicates the network currently connected to the M2M device further comprising the steps of:

determining, based on the M2M configuration information and the information related to firmware associated with the M2M device, if firmware that is currently loaded in the M2M device is a latest version;

if the firmware currently loaded in the M2M device is the latest version, then ending the process since no further firmware updating is needed with respect to the M2M device; and

if the firmware currently loaded in the M2M device is not the latest version, then proceeding to obtain information indicative of the network currently connected to the M2M device.

16. The method of claim 14, wherein the step of obtaining the information which indicates the network currently connected to the M2M device further comprises the steps of:

determining, based on the M2M configuration information, if the M2M device is capable of providing information which identifies the network currently servicing the M2M device;

if the M2M device is not capable of providing the information, then sending a query a remote node to obtain the information indicative of the network connected to the M2M device; and

if the M2M device is capable of providing the information, then sending a query to the M2M device to obtain information identifying the network connected to the M2M device.

17. The method of claim 16, wherein the step of sending the query to the remote node to obtain information which indicates the network currently connected to the M2M device further comprises the steps of:

triggering a query to a mobile location center to receive information about a location of the M2M device; and

using a lookup table along with the location of the M2M device to determine the network which is likely connected to the M2M device.

18. The method of claim 16, wherein the step of sending the query to the remote node to obtain information which indicates the network currently connected to the M2M device further comprises the steps of:

triggering a query to an external storage unit to obtain an address where the M2M device is registered; and

using the address to determine the network currently connected to the M2M device.

19. The method of claim 16, wherein if the information indicative of the network connected to the M2M device is Global Positioning Satellite (GPS) coordinates of the M2M device then further comprising a step of using a map function along with the GPS coordinates to determine the network currently connected to the M2M device.

20. The method of claim 14, wherein the step of determining whether or not to push the firmware update to the M2M device further comprises the steps of:

determining if the firmware update is a critical firmware update or a non-critical firmware update;

if the firmware update is a critical firmware update, then pushing the critical firmware update to the M2M device;

if the firmware update is a non-critical firmware update, the determining if a cost of using the network to push the non-critical firmware update to the M2M device exceeds a threshold;

if the cost exceeds the threshold, then do not push the non-critical firmware update to the M2M device;

or

if the cost does not exceed the threshold, then push the non-critical firmware update to the M2M device.

21. The method of claim 14, wherein if there is a determination to push the firmware update to the M2M device then performing the steps of:

pushing a single firmware update to the M2M device;

or

pushing one or more non-critical firmware updates to the M2M device and then pushing a critical firmware update to the M2M device.

22. The method of claim 14, wherein if there is a determination not to push the firmware update to the M2M device then performing the step of:

instructing the M2M device to enter a quite mode until the M2M device connects to another network.

23. The method of claim 14, further comprising a step of:

sending a message to the M2M device instructing the M2M device to send the notification.

24. The method of claim 14, further comprising steps of:

sending a message to the M2M device where the message has one or more conditions which when satisfied result in the M2M device sending the notification and once the notification is received then enabling a lawful intercept of data which is transmitted from the M2M device.

25. The method of claim 14, wherein the information related to firmware associated with the M2M device comprises:

information about current firmware upgrades;

past firmware upgrades;

a number of firmware images to be updated at the M2M device;

an installation order of the firmware images;

dependencies between the firmware images to be updated at the M2M device; and

firmware file size for each of the updates.

26. The method of claim 14, wherein the information related to the network currently connected to the M2M device comprises:

data costs associated with using the network to push the firmware update to the M2M device.