Method for transferring a file via a mobile device and mobile device for performing same
US-2017063805-A1 · Mar 2, 2017 · US
US10353689B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10353689-B2 |
| Application number | US-201514838428-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 28, 2015 |
| Priority date | Aug 28, 2015 |
| Publication date | Jul 16, 2019 |
| Grant date | Jul 16, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A mobile device, such as a cellular phone, can transfer an encrypted file from a server to a terminal, such as an automated teller machine. The server can specify delivery to a specific terminal. The mobile device can download an encrypted file and identity metadata from at least one server. The mobile device can connect to a terminal, such as wirelessly or via a wired connection such as a universal serial bus (USB). The mobile device can match an identity of the terminal to an identity associated with the identity metadata. For a USB connection, the identity metadata can include a vendor identifier (VID), a product identifier (PID), and a unique terminal identifier. If the identities match, then the mobile device can upload the encrypted file to the terminal. If the identities do not match, then the mobile device can prevent the encrypted file from uploading to the terminal.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: downloading an encrypted file and identity metadata from at least one server to a mobile device by a processor of the mobile device; establishing, by the processor, a communication session with a terminal through a connection between the mobile device and the terminal; matching, by the processor, an identity of the terminal to an identity associated with the identity metadata during the communication session; and uploading, by the processor, the encrypted file from the mobile device to the terminal during the communication session. 2. The method of claim 1 , wherein the matching, on the mobile device, of the identity of the terminal to the identity associated with the identity metadata occurs before the uploading of the encrypted file from the mobile device to the terminal. 3. The method of claim 1 , wherein the matching, on the mobile device, the identity of the terminal to the identity associated with the identity metadata comprises: performing a hardware-level initialization to enable the communication session between the mobile device and the terminal; and receiving at the mobile device, from the terminal, data including the identity of the terminal. 4. The method of claim 1 , wherein the encrypted file includes instructions to the terminal to encrypt and transfer a second encrypted file from the terminal to the mobile device. 5. The method of claim 4 , further comprising: downloading, by the processor, the second encrypted file from the terminal to the mobile device; terminating, by the processor, the communication session with the terminal; and uploading, by the processor, the second encrypted file from the mobile device to the at least one server. 6. The method of claim 1 , wherein the mobile device connects to the terminal via a wired connection and uploads the encrypted file to the terminal via the wired connection. 7. The method of claim 6 , wherein the wired connection is a universal serial bus (USB) wired connection. 8. The method of claim 7 , wherein the matching, on the mobile device, the identity of the terminal to the identity associated with the identity metadata comprises: performing a hardware-level initialization to enable the communication session between the mobile device and the terminal; and receiving at the mobile device, from the terminal, a vendor identifier (VID), a product identifier (PID) of the terminal, and a terminal identifier of the terminal. 9. The method of claim 8 , wherein: the identity metadata includes a VID, a PID, and a terminal identifier; and the matching, on the mobile device, the identity of the terminal to the identity associated with the identity metadata comprises: matching the VID received from the terminal to the VID of the identity metadata; matching the PID received from the terminal to the PID of the identity metadata; and matching the terminal identifier received from the terminal to the terminal identifier of the identity metadata. 10. The method of claim 1 , wherein the mobile device connects to the terminal via a wireless connection and uploads the encrypted file to the terminal via the wireless connection. 11. The method of claim 1 , wherein the mobile device lacks an encryption key associated with the encrypted file. 12. A method, comprising: downloading, by a processor of a mobile device, an encrypted file and identity metadata via a wireless connection from at least one server; establishing, by the processor, a communication session with a terminal through a universal serial bus (USB) wired connection; and in the following order: matching, by the processor, an identity of the terminal to an identity associated with the identity metadata during the communication session; and uploading, by the processor, the encrypted file from the mobile device to the terminal via the USB wired connection during the communication session. 13. The method of claim 12 , wherein the matching the identity of the terminal to the identity associated with the identity metadata comprises: performing a hardware-level initialization to enable the communication session between the mobile device and the terminal; and receiving at the mobile device, from the terminal, data including a vendor identifier (VID), a product identifier (PID), and a terminal identifier of the terminal. 14. The method of claim 13 , wherein: the identity metadata includes a VID, a PID, and a terminal identifier; and the matching, on the mobile device, the identity of the terminal to the identity associated with the identity metadata comprises: matching the VID received from the terminal to the VID of the identity metadata; matching the PID received from the terminal to the PID of the identity metadata; and matching the terminal identifier received from the terminal to the terminal identifier of the identity metadata. 15. The method of claim 12 , wherein the encrypted file includes instructions to the terminal to encrypt and transfer a second encrypted file from the terminal to the mobile device via the USB wired connection; and further comprising: downloading, by the processor, the second encrypted file from the terminal to the mobile device via the USB wired connection; terminating, by the processor, the communication session with the terminal; and uploading, by the processor, the second encrypted file via the wireless connection from the mobile device to the at least one server. 16. The method of claim 12 , wherein the mobile device lacks an encryption key associated with the encrypted file. 17. A mobile device, comprising: a communication device; at least one processor; and at least one memory device storing instructions executable by the at least one processor, the instructions being executable by the at least one processor to perform data processing activities, the data processing activities comprising: downloading, by the processor, an encrypted file and identity metadata from at least one server to the memory device; establishing, by the processor, a communication session with a terminal through a connection between the mobile device and the terminal using the communication device; and matching, by the processor, an identity of the terminal to an identity associated with the identity metadata during the communication session; and uploading, by the processor, the encrypted file from the mobile device to the terminal during the communication session. 18. The mobile device of claim 17 , wherein the matching, on the mobile device, of the identity of the terminal to the identity associated with the identity metadata occurs before the uploading of the encrypted file from the mobile device to the terminal. 19. The mobile device of claim 17 , wherein: the connection comprises a universal serial bus (USB) wired connection; and the matching, on the mobile device, the identity of the terminal to the identity associated with the identity metadata comprises: performing a hardware-level initialization to enable the communication session between the mobile device and the terminal; and receiving at the mobile device, from the terminal, a vendor identifier (VID), a product identifier (PID), and a terminal identifier of the terminal. 20. The mobile device of claim 19 , wherein: the identity metadata includes a VID, a PID, and a terminal identifier; and the matching, on the mobile device, the identity of the terminal to the identity associated with the identity metadata comprises: matching the VID rece
using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories · CPC title
specially adapted for file transfer, e.g. file transfer protocol [FTP] · CPC title
wherein the data content is protected, e.g. by encrypting or encapsulating the payload · CPC title
by securing the transmission between two devices or processes · CPC title
File encryption · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.