# US 2021/0344676 A1 · Method and system for securing communications between a lead device and a secondary device > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2021/0344676 A1 - Document ID: US20210344676A1 - Status: Published application - Kind: A1 - Application number: 17/356,234 - Filed: 2021-06-23 - Published: 2021-11-04 - Earliest claimed: 2017-12-28 - Assignees: Shoppertrak Rct Corporation - Applicants: ShopperTrak RCT Corporation - Inventors: Spencer NEILAN - Web page: https://patentgrep.com/patent/US20210344676A1 ## CPC - H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint} - H04L 9/0877: {using additional device, e.g. trusted platform module [TPM], smartcard, USB or hardware security module [HSM]} - H04L 9/30: Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy - H04L 9/3226: {using a predetermined code, e.g. password, passphrase or PIN (network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083)} - H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)} - H04L 63/168: {above the transport layer} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Techniques for establishing a secure connection between a lead device and a secondary device are disclosed herein. According to an embodiment, the lead device receives a request to establish a secure connection with the secondary device. The lead device determines whether the secure connection is an initial connection with the secondary device. In response to a determination that the secure connection is not an initial connection with the secondary device, the lead device authenticates the secondary device using one or more credentials associated with the secondary device and stored by the lead device. In response to a successful authentication using the one or more credentials, the lead device establishes the secure connection with the secondary device. ## Claims ### Claim at position 1 -20. (canceled) ### Claim 21 A computer-implemented method for establishing a secure connection between a lead device and a secondary device, the method comprising: receiving, by one or more processors of the lead device, a request to establish the secure connection with the secondary device, the request includes a network address of the secondary device; in response to receiving the request, authenticating the secondary device using the network address and one or more credentials associated with the secondary device and stored by the lead device; and in response to a successful authentication using the one or more credentials, establishing the secure connection with the secondary device. ### Claim 22 (depends on 21) The computer-implemented method of claim 21, further comprising: in response to an unsuccessful authentication using the one or more credentials, sending an error message from the lead device to the secondary device. ### Claim 23 (depends on 21) The computer-implemented method of claim 21, wherein the one or more credentials comprises password data associated with the secondary device. ### Claim 24 (depends on 21) The computer-implemented method of claim 21, wherein the network address is an Internet Protocol (IP) address or a Media Access Control (MAC) address. ### Claim 25 (depends on 21) The computer-implemented method of claim 21, wherein the secure connection is indicative of a secure shell (SSH) tunnel. ### Claim 26 (depends on 21) The computer-implemented method of claim 21, wherein the lead device and the secondary device forms at least a portion of a counting device. ### Claim 27 (depends on 21) The computer-implemented method of claim 21, wherein the secure connection is a subsequent connection between the lead device and the secondary device. ### Claim 28 A non-transitory computer-readable storage medium comprising a plurality of instructions, which, when executed on one or more processors, causes a lead device to: receive a request to establish a secure connection with a secondary device, the request includes a network address of the secondary device; in response to receiving the request, authenticate the secondary device using the network address and one or more credentials associated with the secondary device and stored by the lead device; and in response to a successful authentication using the one or more credentials, establish the secure connection with the secondary device. ### Claim 29 (depends on 28) The non-transitory computer-readable storage medium of claim 28, wherein the plurality of instructions further causes the lead device to further comprising: in response to an unsuccessful authentication using the one or more credentials, send an error message from the lead device to the secondary device. ### Claim 30 (depends on 28) The non-transitory computer-readable storage medium of claim 28, wherein the one or more credentials comprises password data associated with the secondary device. ### Claim 31 (depends on 28) The non-transitory computer-readable storage medium of claim 28, wherein the network address is an Internet Protocol (IP) address or a Media Access Control (MAC) address. ### Claim 32 (depends on 28) The non-transitory computer-readable storage medium of claim 28, wherein the secure connection is indicative of a secure shell (SSH) tunnel. ### Claim 33 (depends on 28) The non-transitory computer-readable storage medium of claim 28, wherein the lead device and the secondary device forms at least a portion of a counting device. ### Claim 34 (depends on 28) The non-transitory computer-readable storage medium of claim 28, wherein the secure connection is a subsequent connection between the lead device and the secondary device. ### Claim 35 A lead device, comprising: one or more processors; and a memory storing program code, which, when executed on the one or more processors, causes the lead device to: receive a request to establish a secure connection with a secondary device, the request includes a network address of the secondary device; in response to receiving the request, authenticate the secondary device using the network address and one or more credentials associated with the secondary device and stored by the lead device; and in response to a successful authentication using the one or more credentials, establish the secure connection with the secondary device. ### Claim 36 (depends on 35) The lead device of claim 35, wherein the program code further cause the lead device to: in response to an unsuccessful authentication using the one or more credentials, send an error message from the lead device to the secondary device. ### Claim 37 (depends on 35) The lead device of claim 35, wherein the one or more credentials comprises password data associated with the secondary device. ### Claim 38 (depends on 35) The lead device of claim 35, wherein the network address is an Internet Protocol (IP) address or a Media Access Control (MAC) address. ### Claim 39 (depends on 35) The lead device of claim 35, wherein the secure connection is indicative of a secure shell (SSH) tunnel. ### Claim 40 (depends on 35) The lead device of claim 35, wherein the lead device and the secondary device forms at least a portion of a counting device.