US 12,323,273 B2
Data converter for emergency service network
Darell Stoick, Becker, MN (US); Karl Larsen, Waite Park, MN (US); John Lambaere, Sauk Rapids, MN (US); and John Katt, New York, NY (US)
Assigned to GEO-COMM, INC., St. Cloud, MN (US); and RAPIDS, INC., New York, NY (US)
Filed by GEO-COMM, INC., St. Cloud, MN (US); and RAPIDSOS, INC., New York, NY (US)
Filed on May 25, 2023, as Appl. No. 18/201,761.
Prior Publication US 2024/0396764 A1, Nov. 28, 2024
Int. Cl. H04L 67/12 (2022.01); H04L 12/12 (2006.01); H04L 12/46 (2006.01); H04L 12/54 (2022.01); H04L 12/66 (2006.01); H04L 41/0654 (2022.01); H04L 69/08 (2022.01); H04L 12/70 (2013.01)
CPC H04L 12/5601 (2013.01) [H04L 12/12 (2013.01); H04L 12/4612 (2013.01); H04L 12/66 (2013.01); H04L 41/0654 (2013.01); H04L 67/12 (2013.01); H04L 69/08 (2013.01); H04L 2012/5627 (2013.01)] 17 Claims
OG exemplary drawing
 
1. A method comprising:
establishing, by an apparatus, a secure authenticated network connection between an apparatus located at an emergency communication center (ECC) location and operatively coupled to an ECC functional entity, and an application programming interface (API) endpoint in a cloud-based infrastructure;
obtaining serial data from the functional entity by the apparatus;
creating an API message comprising a data payload containing the serial data, and an ECC identifier; and
sending the API message comprising the data payload to the API endpoint in a data packet;
detecting failure of a serial data port from which the serial data is being obtained;
re-initiating the serial port without caching data and without resetting the apparatus; and
resuming sending API messages to the API endpoint after re-initiation of the serial port.