IP Library › Granted Patent US 12,625,940
Granted Patent B2
US 12,625,940 · App. 18/458,520 · Granted May 12, 2026

Multi factor authentication using different devices

Inventors: François-Eric Michel Guyomarc'h (Clermont, FR); James William Holland (Braishfield, GB); Milan Khan (London, GB); Caleb Wattles (Paris, FR)
Assignee: ASSA ABLOY AB
G06F21/40G06F21/34G06F21/36G06F21/42G06F21/57G06Q20/3223G06Q20/3276H04L63/0838H04L63/0853H04L63/18H04W12/06G06K7/1417H04L63/0869H04W12/77
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 12,625,940
App. No.
18/458,520
Granted
May 12, 2026
Kind
B2
Abstract

Customizing an application on a mobile device includes storing at least a portion of customization data in a customization server that is independent of the mobile device, a user of the mobile device accessing the customization server independently of the mobile device, receiving authorization data from the customization server that enables the mobile device to securely receive customization data from the customization server, and the mobile device using the authorization data to cause the customization server to provide the customization data to the mobile device. The authorization data may be provided by postal message, email message, an SMS text message, and/or a visual code provided on a screen of a computer used to access the customization server. The user may use a computer to provide credential information to access the customization server. Customizing the application may allow the mobile device to access a user service on behalf of the user.

Claims (30)

1 . A method for customizing an application on a mobile device, the application being generic to at least one of a plurality of service providers or a plurality of users, the method comprising:

storing customization data in a customization server that is independent of the mobile device, wherein the customization data, when used to modify the application, changes the application to a customized application that is specific to at least one of a given service provider of the plurality of service providers or a user of the mobile device;

in response to the user of the mobile device initiating customization of the application by contacting the customization server through an access channel other than the application, providing authorization data to the user from the customization server, wherein the authorization data enables the mobile device to securely receive the customization data from the customization server; and

receiving the authorization data from the mobile device and causing the customization server to provide the customization data to the mobile device, wherein the customization data enables the mobile device to change the application to the customized application.

2 . The method, according to claim 1 , wherein the authorization data is provided by at least one of: postal message, email message, an SMS text message, or a visual code provided on a screen of a computer used to contact the customization server.

3 . The method, according to claim 2 , wherein the user uses a computer separate from the mobile device to contact the customization server to initiate customization of the application.

4 . The method, according to claim 2 , wherein the authorization data is provided by the visual code on the screen of the computer and the mobile device receives the visual code using a camera of the mobile device.

5 . The method, according to claim 1 , wherein customizing the application enables the mobile device to access a user service on behalf of the user.

6 . The method, according to claim 1 , wherein the user of the mobile device initiating customization of the application by contacting the customization server through an access channel other than the application comprises the user of the mobile device contacting the customization server without using the mobile device.

7 . The method, according to claim 5 , wherein the user service is banking.

8 . The method, according to claim 1 , wherein certificate pinning is used to require that the mobile device only communicate with predetermined customization servers.

9 . A non-transitory computer-readable medium containing executable code for customizing an application on a mobile device, the application being generic to at least one of a plurality of service providers or a plurality of users, the executable code, when executed by at least one processor, causing the processor to:

store customization data in a customization server that is independent of the mobile device, wherein the customization data, when used to modify the application, changes the application to a customized application that is specific to at least one of a given service provider of the plurality of service providers or a user of the mobile device;

in response to the user of the mobile device initiating customization of the application by contacting the customization server through an access channel other than the application, providing authorization data to the user from the customization server, wherein the authorization data enables the mobile device to securely receive customization data from the customization server; and

receive the authorization data from the mobile device and cause the customization server to provide the customization data to the mobile device, wherein the customization data enables the mobile device to change the application to the customized application.

10 . The non-transitory computer-readable medium, according to claim 9 , wherein the authorization data is provided by at least one of: postal message, email message, an SMS text message, or a visual code provided on a screen of a computer used to contact the customization server.

11 . The non-transitory computer-readable medium, according to claim 10 , wherein the access channel comprises a computer separate from the mobile device.

12 . The non-transitory computer-readable medium, according to claim 9 , wherein changing the application to the customized application enables the mobile device to access a user service on behalf of the user.

13 . The non-transitory computer-readable medium, according to claim 9 , wherein the user of the mobile device initiating customization of the application by contacting the customization server through an access channel other than the application comprises the user of the mobile device contacting the customization server without using the mobile device.

14 . The non-transitory computer-readable medium, according to claim 12 , wherein the customization data includes a secret key that enables the mobile device to access the user service.

15 . The non-transitory computer-readable medium, according to claim 12 , wherein the user service is banking.

16 . A method for customizing an application on a mobile device, the method comprising:

downloading the application to the mobile device, the application being generic to at least one of a plurality of service providers or a plurality of users;

initiating customization of the application by contacting a customization server through an access channel other than the application, the customization server being independent of the mobile device and storing customization data, wherein the customization data, when used to modify the application, changes the application to a customized application that is specific to at least one of a given service provider of the plurality of service providers or a user of the mobile device;

in response to contacting the customization server, receiving authorization data from the customization server, wherein the authorization data enables the mobile device to securely receive the customization data from the customization server; and

providing the authorization data from the mobile device to the customization server and, in response, receiving the customization data from the customization server, wherein the customization data enables the mobile device to change the application to the customized application.

17 . The method, according to claim 16 , wherein initiating customization of the application by contacting the customization server through an access channel other than the application comprises the user of the mobile device contacting the customization server without using the mobile device.

18 . The method, according to claim 16 , wherein receiving the authorization data from the customization server comprises receiving the authorization data by at least one of: postal message, email message, an SMS text message, or a visual code provided on a screen of a computer used to contact the customization server.

19 . The method, according to claim 16 , wherein the authorization data is received via a visual code on a screen of a computer used to contact the customization server and the method further comprises receiving the visual code using a camera of the mobile device.

20 . The method, according to claim 16 , wherein customizing the application enables the mobile device to access a user service on behalf of the user.

Assignments (2)
CORRECTIVE ASSIGNMENT TO CORRECT THE INVENTORSHIP BY ADDING FIRST INVENTOR THAT WAS INADVERTENTLY OMITTED WHEN PREVIOUSLY RECORDED ON REEL 064754 FRAME 0502. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Nov 29, 2023
From: GUYOMARC'H, FRANÇOIS-ERIC MICHEL; HOLLAND, JAMES WILLIAM; KHAN, MILAN; WATTLES, CALEB
To: ASSA ABLOY AB
Reel/Frame 065710/0799 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 30, 2023
From: HOLLAND, JAMES WILLIAM; KHAN, MILAN; WATTLES, CALEB
To: ASSA ABLOY AB
Reel/Frame 064754/0502 →
Continuity (4)
Continuation 16339309
Provisional Application 62411107 · Oct 21, 2016
Provisional Application 62404130 · Oct 4, 2016
Related Publication 20230409693A1 · Dec 21, 2023
References Cited (36)
US 6134659A · Sprong · 2000 [cited by examiner]
US 8732753B2 · Warrick · 2014 [cited by applicant]
US 9774590B1 · Bronshtein · 2017 [cited by examiner]
US 9819673B1 · Johansson · 2017 [cited by examiner]
US 10044695B1 · Cahill et al. · 2018 [cited by applicant]
US 20140250512A1 · Goldstone et al. · 2014 [cited by applicant]
US 20150089591A1 · Harris · 2015 [cited by applicant]
US 20150319252A1 · Momchilov · 2015 [cited by examiner]
US 20170295154A1 · Jackson et al. · 2017 [cited by applicant]
US 20170346851A1 · Drake · 2017 [cited by examiner]
US 20190228143A1 · Guyomarc'h et al. · 2019 [cited by applicant]
US 20200259825A1 · Van Prooijen et al. · 2020 [cited by applicant]
WO WO2013050738A2 · 2013 [cited by applicant]
“U.S. Appl. No. 16/339,309, Advisory Action mailed Apr. 10, 2023”, 4 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Advisory Action mailed Apr. 22, 2022”, 3 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Advisory Action mailed Aug. 9, 2021”, 3 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Corrected Notice of Allowability mailed Jun. 5, 2023”, 3 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Final Office Action mailed Jan. 13, 2023”, 16 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Final Office Action mailed Feb. 10, 2022”, 26 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Final Office Action mailed May 21, 2021”, 23 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Non Final Office Action mailed Jul. 8, 2022”, 14 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Non Final Office Action mailed Sep. 13, 2021”, 24 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Non Final Office Action mailed Dec. 22, 2020”, 18 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Notice of Allowance mailed May 26, 2023”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Response filed Mar. 13, 2023 to Final Office Action mailed Jan. 13, 2023”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Response filed Mar. 22, 2021 to Non Final Office Action mailed Dec. 22, 2020”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Response filed Apr. 8, 2022 to Final Office Action mailed Feb. 10, 2022”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Response filed Apr. 12, 2023 to Advisory Action mailed Apr. 10, 2023”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Response filed May 9, 2022 to Advisory Action mailed Apr. 22, 2022”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Response filed Jul. 15, 2021 to Final Office Action mailed May 21, 2021”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Response filed Aug. 23, 2021 to Advisory Action mailed Aug. 9, 2021”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Response filed Oct. 10, 2022 to Non Final Office Action mailed Jul. 8, 2022”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 16/339,309, Response filed Dec. 13, 2021 to Non Final Office Action mailed Sep. 13, 2021”, 12 pgs. [cited by applicant]
“International Application Serial No. PCT/IB2017/001362, International Preliminary Report on Patentability mailed Apr. 18, 2019”, 9 pgs. [cited by applicant]
“International Application Serial No. PCT/IB2017/001362, International Search Report mailed Feb. 21, 2018”, 3 pgs. [cited by applicant]
“International Application Serial No. PCT/IB2017/001362, Written Opinion mailed Feb. 21, 2018”, (7 pgs.). [cited by applicant]