IP Library Granted Patent US 11,250,409
Granted Patent B2
US 11,250,409 · App. 14/431,204 · Granted Feb 15, 2022

Method and apparatus for providing secure services using a mobile device

Inventor: Mohammed Chakib Bouda (Rotterdam, NL)
Assignee: BELL IDENTIFICATION BV
G06Q20/322G06F21/44G06Q20/3223G06Q20/3226G06Q20/3829G06Q20/401H04L9/3226H04W12/033H04W12/08G06Q2220/00H04L2209/805
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 11,250,409
App. No.
14/431,204
Granted
Feb 15, 2022
Kind
B2
Abstract

This invention relates generally to methods and apparatus for providing secure services using a mobile device, and in particular for securely making transactions, such as payments, using mobile phones and smartphones.

Claims (46)

1. A method of providing secure services using a mobile device, the method comprising:

sending, by the mobile device, a token request comprising device identification data identifying the mobile device to a server;

receiving, by the mobile device, a public key of an asymmetric key pair comprising the public key and a private key, from the server;

requesting, by the mobile device, entry of a user identity verifier;

receiving, by the mobile device, the user identity verifier;

encrypting, by the mobile device, the entered user identity verifier using the public key and sending the encrypted user identity verifier to the server;

receiving, by the mobile device, a token from the server, the token indicating that the user identity verifier in the encrypted user identity verifier matches a stored user identity verifier and the device identification data matches stored eligible device identification data;

storing, by the mobile device, the token;

establishing, by the mobile device when the mobile device does not have network connectivity, communication with a service provider device;

sending, by the mobile device to the service provider device when the mobile device does not have network connectivity, a message requesting a service from the service provider device;

receiving, by the mobile device when the mobile device does not have network connectivity, service data regarding the requested service from the service provider device, the service data comprising a transaction amount associated with the requested service;

determining, by the mobile device when the mobile device does not have network connectivity, that the transaction amount associated with the requested service satisfies a transaction amount limit associated with the token; and

in response to determining that the transaction amount associated with the requested service satisfies the transaction amount limit associated with the token, sending, by the mobile device when the mobile device does not have network connectivity, the token to the service provider device to confirm that the token is valid.

2. The method according to claim 1 , wherein the mobile device requests entry of the user identity verifier each time the server receives a token request.

3. The method according to claim 1 , wherein the mobile device requests entry of the user identity verifier intermittently.

4. The method according to claim 3 , wherein the mobile device requests entry of the user identity verifier intermittently based on at least one of: time; number of tokens issued; or value of tokens issued.

5. The method according to claim 1 , wherein the mobile device requests entry of the user identity verifier the first time the server receives a token request.

6. The method according to claim 1 , wherein the mobile device requests and stores a plurality of tokens.

7. The method according to claim 1 , wherein the token request further comprises account identification data identifying a financial account and the token can be used to identify the financial account.

8. The method according to claim 7 , wherein to provide the requested service, the service provider device

contacts a bank system and bank system data identifying a financial account, service provider device data, and the service data to the bank system, the bank system verifying the data identifying the financial account and the service provider device data, verifying that the financial account can support the requested service, and sending authorization to complete the service to the service provider device; and

completes the requested service.

9. The method according to claim 8 , wherein the data identifying the financial account is derived from the token.

10. The method according to claim 8 , wherein the data identifying the financial account is the token.

11. The method of claim 1 , wherein the token is a cryptogram.

12. The method of claim 1 , wherein the token is an Authorized Request Cryptogram (ARQC).

13. The method of claim 1 , wherein the mobile device is a mobile phone.

14. The method of claim 1 , wherein the user identity verifier is a PIN of a user of the mobile device.

15. A mobile device comprising:

memory; and

a processing device coupled to the memory, the processing device to execute instructions from the memory to:

send a token request comprising device identification data identifying the mobile device to a server;

receive a public key of an asymmetric key pair comprising the public key and a private key, from the server;

request entry of a user identity verifier;

receive the user identity verifier;

encrypt the entered user identity verifier using the public key and send the encrypted user identity verifier to the server;

receive a token from the server, the token indicating that the user identity verifier in the encrypted user identity verifier matches a stored user identity verifier and the device identification data matches stored eligible device identification data;

store the token in the memory;

establish communication with a service provider device when the mobile device does not have network connectivity;

send, to the service provider device when the mobile device does not have network connectivity, a message requesting a service from the service provider device;

receive service data regarding the requested service from the service provider device when the mobile device does not have network connectivity, the service data comprising a transaction amount associated with the requested service;

determine that the transaction amount associated with the requested service satisfies a transaction amount limit associated with the token when the mobile device does not have network connectivity; and

in response to determining that the transaction amount associated with the requested service satisfies the transaction amount limit associated with the token, send the token to the service provider device when the mobile device does not have network connectivity, to confirm that the token is valid.

16. The mobile device of claim 15 , wherein the token is a cryptogram.

17. The mobile device of claim 15 , wherein the mobile device is a mobile phone.

18. The mobile device of claim 15 , wherein the token is an EMV token.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 13, 2015
From: BOUDA, MOHAMMED CHAKIB
To: BELL IDENTIFICATION BV
Reel/Frame 035395/0769 →
Priority Claims (1)
GB 1217448 · Sep 28, 2012 · national
Continuity (1)
Related Publication 20150262170A1 · Sep 17, 2015