IP Library Granted Patent US 10,353,689
Granted Patent B2
US 10,353,689 · App. 14/838,428 · Granted Jul 16, 2019

Method for transferring a file via a mobile device and mobile device for performing same

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,353,689
App. No.
14/838,428
Granted
Jul 16, 2019
Kind
B2
Abstract

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.

Claims (92)

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 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.

21. 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 wire connection between the mobile device and terminal port of the terminal, the terminal port being identifiable by a unique identity;

requesting by the processor the unique identity from the terminal during the communication session;

matching, by the processor, the unique identity of the terminal port to an identity associated with the identity metadata from the at least one server during the communication session; and

uploading, by the processor, the encrypted file from the mobile device to the terminal during the communication session.

22. 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;

authenticating the terminal during the communication session by the the processor, including

requesting by the processor a unique identity from the terminal;

matching, by the processor, the unique identity from the terminal to an identity associated with the identity metadata from the at least one server; and

uploading, by the processor, the encrypted file from the mobile device to the terminal during the communication session.

23. A mobile device, comprising:

a communication device having a unique identity;

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;

authenticating the terminal during the communication session by the processor, including

requesting by the processor the unique identity of the communication device from the terminal;

matching, by the processor, the unique identity from the terminal to an identity associated with the identity metadata from the at least one server; and

uploading, by the processor, the encrypted file from the mobile device to the terminal during the communication session.

Assignments (10)
CORRECTIVE ASSIGNMENT TO CORRECT THE THE PROPERTIES SECTION BY INCLUDING IT WITH TEN PREVIOUSLY OMITTED PROPERTY NUMBERS PREVIOUSLY RECORDED ON REEL 65346 FRAME 367. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Recorded Aug 13, 2025
From: NCR ATLEOS CORPORATION; CARDTRONICS USA, LLC
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 072445/0072 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 30, 2024
From: NCR VOYIX CORPORATION
To: NCR ATLEOS CORPORATION
Reel/Frame 067590/0109 →
CHANGE OF NAME Recorded May 30, 2024
From: NCR CORPORATION
To: NCR VOYIX CORPORATION
Reel/Frame 067578/0417 →
CORRECTIVE ASSIGNMENT TO CORRECT THE DOCUMENT DATE AND REMOVE THE OATH/DECLARATION (37 CFR 1.63) PREVIOUSLY RECORDED AT REEL: 065331 FRAME: 0297. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Recorded Oct 31, 2023
From: NCR ATLEOS CORPORATION
To: CITIBANK, N.A.
Reel/Frame 065627/0332 →
SECURITY INTEREST Recorded Oct 25, 2023
From: NCR ATLEOS CORPORATION; CARDTRONICS USA, LLC
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 065346/0367 →
RELEASE OF PATENT SECURITY INTEREST Recorded Oct 25, 2023
From: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
To: NCR VOYIX CORPORATION
Reel/Frame 065346/0531 →
SECURITY INTEREST Recorded Oct 24, 2023
From: NCR ATLEOS CORPORATION
To: CITIBANK, N.A.
Reel/Frame 065331/0297 →
CORRECTIVE ASSIGNMENT TO CORRECT THE PROPERTY NUMBERS SECTION TO REMOVE PATENT APPLICATION: 15000000 PREVIOUSLY RECORDED AT REEL: 050874 FRAME: 0063. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Recorded Apr 12, 2021
From: NCR CORPORATION
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 057047/0161 →
SECURITY INTEREST Recorded Oct 29, 2019
From: NCR CORPORATION
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 050874/0063 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 28, 2015
From: MISHRA, RAVI PRAKASH; BHOWMICK, SUMAN KUMAR; BUDHARAJU, VIVEKANAND; KHAN, NAYYAR HUSAIN
To: NCR CORPORATION
Reel/Frame 036444/0899 →