US2020169552A1PendingUtilityA1

Using an audio interface device to authenticate another device

Assignee: AMAZON TECH INCPriority: Jul 31, 2017Filed: Jan 29, 2020Published: May 28, 2020
Est. expiryJul 31, 2037(~11 yrs left)· nominal 20-yr term from priority
H04L 63/105G10L 2015/223G10L 17/24H04L 63/083H04L 63/0861G10L 15/22G10L 17/005G10L 17/00H04L 67/306H04L 67/04H04L 9/3228H04L 63/18H04L 63/0807H04L 9/3231
53
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Disclosed are various embodiments for using an audio interface device to facilitate authentication for other devices. A client device presents an authentication code via an output device of the client device. The authentication code is received from a voice interface device. The voice interface device is in an authenticated state for access to an account, and the voice interface device received the authentication code from speech captured by a microphone of the voice interface device following a spoken wake word. The client device is authenticated for access to the account in response to determining that the authentication code received from the voice interface device matches the authentication code presented by the client device.

Claims

exact text as granted — not AI-modified
Therefore, the following is claimed: 
     
         1 . A method, comprising:
 causing, via at least one of one or more computing devices, a client device to present an authentication code via an output device of the client device;   receiving, via at least one of the one or more computing devices, the authentication code from a voice interface device, wherein the voice interface device is in an authenticated state for access to an account, and the voice interface device received the authentication code from speech captured by a microphone of the voice interface device following a spoken wake word; and   authenticating, via at least one of the one or more computing devices, the client device for access to the account in response to determining that the authentication code received from the voice interface device matches the authentication code presented by the client device.   
     
     
         2 . The method of  claim 1 , wherein the client device lacks both a touchscreen and a keyboard. 
     
     
         3 . The method of  claim 1 , wherein the voice interface device lacks both a touchscreen and a keyboard. 
     
     
         4 . The method of  claim 1 , wherein the voice interface device is associated with a fixed location. 
     
     
         5 . The method of  claim 1 , further comprising:
 determining, via at least one of the one or more computing devices, that a risk-based factor does not preclude authentication of the client device for access to the account; and   issuing, via at least one of the one or more computing devices, a registration token to the client device for access to the account.   
     
     
         6 . The method of  claim 1 , further comprising:
 randomly generating, via at least one of the one or more computing devices, the authentication code based at least in part on a required level of entropy and a time window for validity; and   sending, via at least one of the one or more computing devices, the authentication code to the client device via a network.   
     
     
         7 . The method of  claim 1 , wherein authenticating the client device for access to the account further comprises:
 performing, via at least one of the one or more computing devices, voice identification on the speech; and   determining, via at least one of the one or more computing devices, that an identified voice matches a voice profile of a user associated with the account.   
     
     
         8 . The method of  claim 1 , wherein authenticating the client device for access to the account further comprises determining, via at least one of the one or more computing devices, that the authentication code is valid for the account according to a time window for validity for the authentication code. 
     
     
         9 . The method of  claim 1 , wherein the output device of the client device is a local network interface, and the client device presents the authentication code by sending broadcast data via the local network interface. 
     
     
         10 . The method of  claim 1 , wherein the output device of the client device is a display, and the client device presents the authentication code by showing the authentication code on the display. 
     
     
         11 . The method of  claim 1 , wherein the output device of the client device is a speaker, and the client device presents the authentication code by emitting an audio signal via the speaker. 
     
     
         12 . The method of  claim 11 , wherein the audio signal encodes the authentication code in an ultrasonic frequency range. 
     
     
         13 . The method of  claim 11 , wherein the audio signal encodes the authentication code as a voice generated by a voice synthesizer. 
     
     
         14 . A system, comprising:
 at least one computing device; and   instructions executable in the at least one computing device, wherein when executed the instructions cause the at least one computing device to at least:
 cause a client device to present an authentication code via a display of the client device; 
 receive the authentication code from a voice interface device, wherein the voice interface device is in an authenticated state for access to an account, and the voice interface device received the authentication code as speech recorded via a microphone of the voice interface device in response to an entrance of the voice interface device into a listening mode following detection of an audio wake signal; and 
 authenticate the client device for access to the account in response to determining that the authentication code received from the voice interface device matches the authentication code presented by the client device. 
   
     
     
         15 . The system of  claim 14 , wherein the audio wake signal corresponds to a spoken wake word. 
     
     
         16 . The system of  claim 14 , wherein when executed the instructions further cause the at least one computing device to at least randomly generate the authentication code. 
     
     
         17 . The system of  claim 14 , wherein the account is unspecified by the client device. 
     
     
         18 . The system of  claim 14 , wherein when executed the instructions further cause the at least one computing device to at least authorize a transaction associated with the client device in response to determining that the authentication code received from the voice interface device matches the authentication code presented by the client device. 
     
     
         19 . A non-transitory computer-readable medium embodying a program executable in at least one computing device, wherein when executed the program causes the at least one computing device to at least:
 cause a client device to present an authentication code via a display of the client device;   receive the authentication code from a voice interface device, wherein the voice interface device is in an authenticated state for access to an account, and the voice interface device received the authentication code as speech recorded via a microphone of the voice interface device in response to an entrance of the voice interface device into a listening mode following detection of an audio wake signal; and   authenticate the client device for access to the account in response to determining that the authentication code received from the voice interface device matches the authentication code presented by the client device.   
     
     
         20 . The non-transitory computer-readable medium of  claim 19 , wherein when executed the program further causes the at least one computing device to at least authorize a transaction associated with the client device in response to determining that the authentication code received from the voice interface device matches the authentication code presented by the client device.

Join the waitlist — get patent alerts

Track US2020169552A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.