Method and system for updating firmware using a mobile device as a communications bridge
DC CAFCFirst Claim
1. A method of updating firmware, comprising:
- at a first mobile device of a first potential transactor, wherein the first mobile device includes one or more processors, memory, and two or more communication capabilities, wherein the two or more communication capabilities include a first communication capability and a second communication capability distinct from the first communication capability;
while executing an application compatible with a mobile device-to-machine payment system;
receiving, from a server of the mobile device-to-machine payment system, an update for the application and a firmware image for a payment module of the mobile device-to-machine payment system via the second communication capability;
after receiving the update for the application and the firmware image for the payment module;
updating the application based on the update; and
storing the firmware image for the payment module;
subsequent to and independent from the receiving, the updating, and the storing, obtaining an information packet broadcast by the payment module via the first communication capability, wherein the information packet at least includes a current firmware version of the payment module and an authorization code for initiating a transaction for a payment accepting unit coupled with the payment module;
comparing the current firmware version of the payment module with a version of the stored firmware image; and
in accordance with a first determination that the current firmware version of the payment module does not match the firmware version of the firmware image stored by the first mobile device, sending, to the payment module, firmware update information via the first communication capability, wherein the firmware update information includes one or more data packets for updating the current firmware version of the payment module to the version of the firmware image stored by the first mobile device.
1 Assignment
Litigations
0 Petitions
Accused Products
Abstract
A first device with one or more processors, processors, memory, and two or more communication capabilities obtains, from a payment module, advertised information via a first communication capability (e.g., BLE), where the advertised information at least includes a current firmware version of the payment module. In accordance with a determination that the current firmware version of the payment module satisfies one or more predefined firmware criteria (i.e., indicating that the payment module'"'"'s firmware needs updating), the first device includes sends, to the payment module, firmware update information via the first communication capability, where the firmware update information includes one or more data packets for updating the current firmware version of the payment module.
146 Citations
24 Claims
-
1. A method of updating firmware, comprising:
at a first mobile device of a first potential transactor, wherein the first mobile device includes one or more processors, memory, and two or more communication capabilities, wherein the two or more communication capabilities include a first communication capability and a second communication capability distinct from the first communication capability; while executing an application compatible with a mobile device-to-machine payment system; receiving, from a server of the mobile device-to-machine payment system, an update for the application and a firmware image for a payment module of the mobile device-to-machine payment system via the second communication capability; after receiving the update for the application and the firmware image for the payment module; updating the application based on the update; and storing the firmware image for the payment module; subsequent to and independent from the receiving, the updating, and the storing, obtaining an information packet broadcast by the payment module via the first communication capability, wherein the information packet at least includes a current firmware version of the payment module and an authorization code for initiating a transaction for a payment accepting unit coupled with the payment module; comparing the current firmware version of the payment module with a version of the stored firmware image; and in accordance with a first determination that the current firmware version of the payment module does not match the firmware version of the firmware image stored by the first mobile device, sending, to the payment module, firmware update information via the first communication capability, wherein the firmware update information includes one or more data packets for updating the current firmware version of the payment module to the version of the firmware image stored by the first mobile device. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
13. A mobile device of a potential transactor, comprising:
-
two or more communication capabilities, wherein the two or more communication capabilities include a first communication capability and a second communication capability distinct from the first communication capability; one or more processors; and memory storing one or more programs to be executed by the one or more processors, the one or more programs comprising instructions for; while executing an application compatible with a mobile device-to-machine payment system; receiving, from a server of the mobile device-to-machine payment system, an update for the application and a firmware image for a payment module of the mobile device-to-machine payment system via the second communication capability; after receiving the update for the application and the firmware image for the payment module; updating the application based on the update; and storing the firmware image for the payment module; subsequent to and independent from the receiving, the updating, and the storing, obtaining an information packet broadcast by the payment module via the first communication capability, wherein the information packet at least includes a current firmware version of the payment module and an authorization code for initiating a transaction for a payment accepting unit coupled with the payment module; comparing the current firmware version of the payment module with a version of the stored firmware image; and in accordance with a determination that the current firmware version of the payment module does not match the firmware version of the firmware image stored by the mobile device, sending, to the payment module, firmware update information via the first communication capability, wherein the firmware update information includes one or more data packets for updating the current firmware version of the payment module to the version of the firmware image stored by the mobile device. - View Dependent Claims (14, 15, 16, 17, 18)
-
-
19. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which, when executed by a mobile device of a potential transactor with one or more processors and two or more communication capabilities, wherein the two or more communication capabilities include a first communication capability and a second communication capability distinct from the first communication capability, cause the mobile device to perform operations comprising:
while executing an application compatible with a mobile device-to-machine payment system; receiving, from a server of the mobile device-to-machine payment system, an update for the application and a firmware image for a payment module of the mobile device-to-machine payment system via the second communication capability; after receiving the update for the application and the firmware image for the payment module; updating the application based on the update; and storing the firmware image for the payment module; subsequent to and independent from the receiving, the updating, and the storing, obtaining an information packet broadcast by the payment module via the first communication capability, wherein the information at least includes a current firmware version of the payment module and an authorization code for initiating a transaction for a payment accepting unit coupled with the payment module; comparing the current firmware version of the payment module with a version of the stored firmware image; and in accordance with a determination that the current firmware version of the payment module does not match the firmware version of the firmware image stored by the mobile device, sending, to the payment module, firmware update information via the first communication capability, wherein the firmware update information includes one or more data packets for updating the current firmware version of the payment module to the version of the firmware image stored by the mobile device. - View Dependent Claims (20, 21, 22, 23, 24)
Specification