Cloud communication for an edge device
Methods and systems of managing data transfers in a fixture. One system includes fixtures comprising: a communication interface; and a processor configured to optimize download efficiency by: receiving, from a remote device via the communication interface, a file comprising a plurality of data blocks, wherein each of the plurality of data blocks comprise a unique cyclical redundancy check (CRC) value and a payload; determining, for each of the plurality of data blocks, a check value based on a polynomial division of the respective payload; determining an error in at least one of the plurality of data blocks based on a comparison between each of the respective CRC values and the respective check values; and providing, to the remote device via the communication interface, a request for retransmission of each of the at least one of the plurality of data blocks with the determined error.
1. A fixture comprising:
a communication interface;
a non-volatile memory; and
a processor configured to recover from a disruption during an over the air (OTA) data transfer by:
initiating the OTA data transfer with a remote device via the communication interface;
receiving from the remote device a plurality of data packets;
persisting each of the plurality of data packets to the non-volatile memory as each of the plurality of data packets is received;
determining, after a reset of the processor, a progress of the OTA data transfer by reading the plurality of data packets from the non-volatile memory; and
providing, to the remote device, a request for resumption of the OTA data transfer based on the progress.
2. The fixture of claim 1 , wherein the progress of the OTA data transfer is determined during a boot sequence.
3. The fixture of claim 1 , wherein the reset of the processor is caused by a loss of power.
4. The fixture of claim 1 , wherein the processor is further configured to: provide, to the remote device, a request for cancelation of the OTA data transfer after a set number of failed attempts.
5. The fixture of claim 1 , wherein the processor is further configured to: clear the plurality of data packets from the non-volatile memory on completion of the OTA data transfer.
6. The fixture of claim 1 , wherein the plurality of data packets is received form the remote device through a Long Range (LoRa) messaging protocol via the OTA data transfer.
7. The fixture of claim 1 , wherein the plurality of data packets comprises an update to firmware.
8. The fixture of claim 1 , wherein the plurality of data packets comprises an update to at least one setting.
9. The fixture of claim 8 , wherein the update includes data for cloud purge scheduling.
10. The fixture of claim 1 , wherein the processor is further configured to: when a communication link between the remote device and the communication interface is inoperable, attempt to restore the communication link according to an exponentially increasing algorithm.
11. A computer implemented method for recovering from a disruption during an over the air (OTA) data transfer, the method executed by a processor and comprising:
initiating the OTA data transfer with a remote device via a communication interface; receiving from the remote device a plurality of data packets;
persisting each of the plurality of data packets to a non-volatile memory as each of the plurality of data packets is received;
determining, after a reset of the processor, a progress of the OTA data transfer by reading the plurality of data packets from the non-volatile memory; and
providing, to the remote device, a request for resumption of the OTA data transfer based on the progress.
12. The method of claim 11 , wherein the progress of the OTA data transfer is determined during a boot sequence.