# US 12,003,620 B2 · System and method for secure electronic data transfer > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,003,620 B2 - Document ID: US12003620B2 - Status: Granted - Kind: B2 - Application number: 17/516,889 - Filed: 2021-11-02 - Published: 2022-02-24 - Granted: 2024-06-04 - Earliest claimed: 2019-01-28 - Assignees: KnectIQ Inc. - Applicants: KnectIQ Inc. - Inventors: Shailendra Jain; Andrew Lunstad; Kenneth Morris - Web page: https://patentgrep.com/patent/US12003620B2 ## CPC - H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates} - H04L 9/088: {Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms (network architectures or network communication protocols for using time-dependent keys in a packet data network H04L63/068)} - H04L 9/0662: {with particular pseudorandom sequence generator} - H04L 9/0822: {using key encryption key} - H04L 9/0838: {Key agreement, i.e. key establishment technique in which a shared key is derived by parties as a function of information contributed by, or associated with, each of these (network architectures or network communication protocols for key exchange in a packet data network H04L63/061)} - H04L 63/0435: {wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for symmetric key encryption H04L9/06)} - H04L 63/0442: {wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30)} - H04L 63/062: {for key distribution, e.g. centrally by trusted party (cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819)} - H04L 63/068: {using time-dependent keys, e.g. periodically changing keys (cryptographic mechanisms or cryptographic arrangements for controlling usage of secret information H04L9/088)} - H04L 2463/061: applying further key derivation, e.g. deriving traffic keys from a pair-wise master key - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Systems and methods for secure electronic data transfer utilizing an ephemeral key for encryption and decryption of data. ## Claims ### Claim 1 A method of operating a broker device to enable a secure electronic data transfer between a sender client device and a receiver client device, wherein the sender and receiver client devices each comprise a computing device, the method comprising: generating a Key DNA and a Moniker for a sender client device, the Key DNA being formatted to facilitate generation of a Key for encrypting data; storing the Key DNA and the Moniker; sending the Key DNA and the Moniker to the sender client device; receiving a request from a receiver client device, the request including the Moniker; retrieving the Key DNA based upon the Moniker in response to the request; and sending the retrieved Key DNA to the receiver client device in response to the request; wherein the receiver client device is enabled by the received Key DNA to decrypt encrypted data received from the sender client device. ### Claim 2 (depends on 1) The method of claim 1, wherein prior to the step of generating a Key DNA and a Moniker, the method further comprising: receiving a request for a Key DNA from the sender client device; and operating the broker device to approve or decline the request for the Key DNA. ### Claim 3 (depends on 2) The method of claim 2, wherein following the step of operating the broker device to approve or decline the request, the method further comprising: delivering, from the broker device to an interceptor device, a request for verification of an intended transfer of data from the sender client device to the receiver client device; and receiving a decision from the interceptor device to approve or decline the request for verification. ### Claim 4 (depends on 1) The method of claim 1, further comprising: following the step of sending the retrieved Key DNA to the receiver client device, deleting the Key DNA and the Moniker from the broker device based upon pre-determined rules. ### Claim 5 (depends on 1) The method of claim 1, further comprising: logging information indicative of the broker device having received a request for the Key DNA from the sender client device or the receiver client device. ### Claim 6 (depends on 1) The method of claim 1, wherein a portion of the Key DNA is created by the sender client device. ### Claim 7 (depends on 1) The method of claim 1, wherein communications between the broker device and each of the sender client device and the receiver client device are secured. ### Claim 8 (depends on 7) The method of claim 7, further comprising: generating a first private/public key pair and a second private/public key pair using an asymmetric cryptographic algorithm; delivering the first public key to the sender client device; delivering the second public key to the receiver client device; operating the sender client device to generate a symmetric key; operating the sender client device to encrypt the symmetric key using the first public key; operating the sender client device to encrypt a communication to the broker device using the symmetric key; receiving an encrypted symmetric key and an encrypted communication from the sender client device, the encrypted symmetric key being generated based upon the first public key; decrypting the encrypted symmetric key using the public key; and decrypting the encrypted communication using the decrypted symmetric key. ### Claim 9 (depends on 1) The method of claim 1, wherein the broker device is a first broker device managing operations in a trust environment including the sender client device and the receiver client device, the trust environment further including a second broker device managing operations in the trust environment, the method further comprising: handing off management of the sender client device from the first broker device to the second broker device. ### Claim 10 (depends on 1) The method of claim 1, wherein the sender client device is provisioned to a first node and the receiver client device is provisioned to a second node, the first and second nodes being virtually established at the broker device, and further wherein the first and second nodes are linked by a pool established at the broker device. ### Claim 11 (depends on 1) The method of claim 1, wherein prior to the step of generating a Key DNA and a Moniker, the method further comprising: provisioning the sender client device. ### Claim 12 (depends on 11) The method of claim 11, wherein the step of provisioning includes: establishing a unique First Client ID for the sender client device; and storing the unique First Client ID. ### Claim 13 (depends on 12) The method of claim 12, further comprising provisioning the receiver client device, including establishing and storing a unique Second Client ID for the receiver client device. ### Claim 14 (depends on 13) The method of claim 13, wherein prior to the step of generating a Key DNA and a Moniker, the method further comprising: receiving a request for a Key DNA from the sender client device, the request including the First Client ID and an indication of intent to send encrypted data to the Second Client ID; approving or declining the request based upon the First Client ID and the Second Client ID. ### Claim 15 (depends on 14) The method of claim 14, wherein prior to the step of generating a Key DNA and a Moniker, the method further comprising: establishing a plurality of pools, each of the pools including two or more client devices; assigning a unique Pool Identifier to each pool of the plurality of pools; and storing each of the assigned Pool Identifiers. ### Claim 16 (depends on 15) The method of claim 15, wherein the request includes a Request Pool Identifier, and further wherein the step of approving or declining the request includes comparing the Request Pool Identifier with stored Pool Identifiers. ### Claim 17 (depends on 16) The method of claim 16, wherein the step of approving or declining the request includes: identifying a Matched Pool Identifier from the stored Pool Identifiers that matches the Request Pool Identifier; and reviewing rules associated with the Matched Pool Identifier. ### Claim 18 (depends on 1) The method of claim 1, wherein the broker device is operated as one of the sender client device and the receiver client device. ### Claim 19 (depends on 1) The method of claim 1, wherein the broker device is a first broker device, the method further comprising: sending the Key DNA to a second broker device for delivery to the receiver client device. ### Claim 20 (depends on 1) The method of claim 1, wherein the broker device is a first broker device, the method further comprising: transferring control over at least one of the sender client device and the receiver client device from the first broker device to a second broker device.