Efficient update mechanism in IoT event driven architectures

A system comprising:

• a memory storing instructions thereon;
• and
• at least one processor coupled to the memory and configured by the instructions to:
• receive, from a source application via a publish/subscribe broker service, a first block using a first IoT messaging session, the first block including a first portion of a file and a first plurality of communication parameters;
• transmit a first acknowledgement corresponding to the first block, the first acknowledgement approving a proposed parameter of the first plurality of communication parameters, including one or more of the first plurality of communication parameters, and indicating receipt of the first block;
• receive, based on the proposed parameter, from the source application via the publish/subscribe broker service, a second block using a second IoT messaging session, the second block including a second portion of the file and a second plurality of communication parameters;
• and
• transmit a second acknowledgement corresponding to the second block, the second acknowledgement including one or more of the second plurality of communication parameters, and indicating receipt of the second block.

A non-transitory computer-readable device having instructions thereon that, when executed by at least one computing device, causes the at least one computing device to perform operations comprising:

• transmitting, to an internet of things (IoT) device via a publish/subscribe broker service, a first block a first IoT messaging session, the first block including a first portion of a file and a first plurality of communication parameters including a proposed parameter;
• receiving a first acknowledgement corresponding to the first block, the first acknowledgement approving the proposed parameter, including one or more of the first plurality of communication parameters, and indicating receipt of the first block;
• transmitting, based on the proposed parameter, to the IoT device via the publish/subscribe broker service, a second block using a second IoT messaging session, the second block including a second portion of the file and a second plurality of communication parameters;
• and
• receiving a second acknowledgement corresponding to the second block, the second acknowledgement including one or more of the second plurality of communication parameters, and indicating receipt of the second block.