US 12,089,105 B2
Systems and methods of fail-safe packet transmission using long range wide area networks
Saurabh Arora, Gurugram (IN); and Sandeep Kumar Chauhan, Miyapur Hyderabad (IN)
Assigned to Bank of America Corporation, Charlotte, NC (US)
Filed by Bank of America Corporation, Charlotte, NC (US)
Filed on Apr. 4, 2022, as Appl. No. 17/712,248.
Prior Publication US 2023/0319664 A1, Oct. 5, 2023
Int. Cl. H04W 36/30 (2009.01); H04W 4/30 (2018.01); H04W 12/08 (2021.01); H04W 24/04 (2009.01); H04W 24/08 (2009.01); H04W 28/04 (2009.01); H04W 28/06 (2009.01); H04W 36/00 (2009.01); H04W 12/069 (2021.01)
CPC H04W 36/30 (2013.01) [H04W 24/04 (2013.01); H04W 24/08 (2013.01); H04W 28/04 (2013.01); H04W 28/06 (2013.01); H04W 36/0022 (2013.01); H04W 36/0069 (2018.08); H04W 12/069 (2021.01)] 20 Claims
OG exemplary drawing
 
1. A method for supporting a seamless transition of a transaction request from a first network to a second network in response to a detection of a first network connection failure, the method comprising:
using a mobile application running on a mobile device, transmitting the transaction request to the first network for being routed to an entity application server, the transaction request including a data packet comprising transaction request data;
failing to establish an electronic connection with the first network;
immediately in response to the failure to establish the electronic connection with the first network, using the mobile device to transmit the transaction request to the second network using a LoRa sensor embedded in the mobile device, the second network being a low-range wide area network (“LoRaWAN”);
receiving the transaction request at a first LoRaWAN gateway and at a second LoRaWAN gateway, the first LoRaWAN gateway and the second LoRaWAN gateway being associated with the second network, the first LoRaWAN gateway and the second LoRaWAN gateway each being within a pre-determined proximity to the mobile device;
receiving, at a network server, a first data packet including the transaction request from the first LoRaWAN gateway and a second data packet including the transaction request from the second LoRaWAN gateway, the network server bridging between the first LoRaWAN gateway and the second LoRaWAN gateway and an entity network;
upon receipt of the first data packet, storing in a gateway cache first transaction data associated with the first data packet;
in response to a determination, by the network server, that the first transaction data is not identical to transaction data already saved at the gateway cache, storing the transaction request in a queue;
upon receipt of the second data packet, storing in the gateway cache second transaction data associated with the second data packet;
in response to a determination, by the network server, that the second transaction data is identical to the first transaction data, deleting the second data packet;
upon a lapse of a pre-determined time period, validating all transaction requests included in data packets stored in the queue;
removing from the queue all data packets failing to validate and, in response to a failure to validate a transaction request, transmitting the transaction request back to a sender identified in a header of a data packet including the transaction request; and
after the removing, transmitting the transaction requests stored in the queue to the entity application server associated with the entity network.