WO2019005423A1 - Appareil, système et procédé d'authentification pour expérience d'utilisateur conversationnelle - Google Patents

Appareil, système et procédé d'authentification pour expérience d'utilisateur conversationnelle Download PDF

Info

Publication number
WO2019005423A1
WO2019005423A1 PCT/US2018/035645 US2018035645W WO2019005423A1 WO 2019005423 A1 WO2019005423 A1 WO 2019005423A1 US 2018035645 W US2018035645 W US 2018035645W WO 2019005423 A1 WO2019005423 A1 WO 2019005423A1
Authority
WO
WIPO (PCT)
Prior art keywords
trusted device
secret information
sending
use identifier
information
Prior art date
Application number
PCT/US2018/035645
Other languages
English (en)
Inventor
Brian ERIKSSON
Ajith PUDHIYAVEETIL
Shahab Hamidi-Rad
Charles Moreman
Original Assignee
Interdigital Ce Patent Holdings
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Interdigital Ce Patent Holdings filed Critical Interdigital Ce Patent Holdings
Publication of WO2019005423A1 publication Critical patent/WO2019005423A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6209—Protecting access to data via a platform, e.g. using keys or access control rules to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • H04L63/0838—Network architectures or network communication protocols for network security for authentication of entities using passwords using one-time-passwords
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2131—Lost password, e.g. recovery of lost or forgotten passwords

Definitions

  • the present principles relate generally to user interface (UI) and user experience (UX) technology and, more particularly, to user interface technology involving natural language from spoken or verbal commands.
  • Conversational user experience or user interfaces (e.g., Amazon Alexa, Apple Siri, Google Home) are becoming more prevalent in everyday life.
  • One area of interest is to use natural language to aid in authentication problems. For example, the user has forgotten their password. This can help prevent costly customer service calls.
  • conversational interfaces are not yet accurate enough to successfully authenticate a unique user by speech, and access to these interfaces is fairly open.
  • an Amazon Echo might be in the center of a living room with access by anyone in the house.
  • One response by a system such as an Amazon Echo to a verbal request for secret information such as a password could be an audio presentation of the secret information.
  • a user might state, "Alexa, what is the password for the home WiFi network?"
  • the Amazon Echo system could respond, "Your home WiFi network password is 'password' .”
  • providing an audio broadcast of secret information in the clear may undesirably make such information available to unintended or unauthorized parties.
  • an exemplary embodiment may comprise a method including receiving a voice command; detecting from the voice command a request for secret information; retrieving the secret information; identifying a trusted device associated with the secret information; determining contact information for the trusted device; and sending the secret information to the trusted device using the contact information.
  • an exemplary embodiment may comprise a method as described above wherein sending the secret information is preceded by determining whether the trusted device is authorized to receive the secret information; and responsive to the trusted device being authorized, enabling the transmission of the secret information to the trusted device.
  • an exemplary embodiment may comprise a method as described above wherein determining whether the trusted device is authorized includes determining at least one factor associated with the trusted device; processing the factor to determine an authentication score; and evaluating the authentication score to determine whether the trusted device is authorized to receive the secret information.
  • an exemplary embodiment may comprise a method as described above wherein the at least one factor comprises one or more of a location of the trusted device, a history of usage of the trusted device, an IoT behavior associated with the trusted device, and whether a device to which the secret information applies or provides access is on the same network as the trusted device.
  • an exemplary embodiment may comprise any of the above-described methods wherein sending the secret information is preceded by parsing the secret information into a non-secure portion and a secure portion; and wherein sending the secret information comprises providing the non-secure portion in the clear and sending the secure portion to only the trusted device.
  • an exemplary embodiment may comprise a method as described above wherein delivering the non-secure portion in the clear includes producing an audio output representing the non-secure portion.
  • an exemplary embodiment may comprise a method as described above wherein producing the audio output includes synthesizing a speech signal representing a verbal presentation of the non-secure information; and audibly reproducing the speech signal via an audio reproduction device.
  • an exemplary embodiment may comprise a method as described above wherein the request for secret information includes a request for a single-use identifier; retrieving the secret information includes generating the single-use identifier; and sending the secret information includes sending the single-use identifier to the trusted device.
  • an exemplary embodiment may comprise a method as described in the preceding paragraph wherein generating the single-use identifier includes one of selecting the single-use identifier from a list and random generation of the single-use identifier.
  • an exemplary embodiment may comprise a method as described above wherein sending the single-use identifier to the trusted device is followed by receiving a second voice command including the single-use identifier and requesting second secret information; recognizing the single-use identifier; providing the second secret information to the trusted device responsive to recognizing the single-use identifier; and disabling further recognition of the single-use identifier.
  • an exemplary embodiment may comprise a method as described above wherein receiving the voice command comprises receiving the voice command via a first device enabled to communicate on a communication network comprising one or more of a WiFi network, a Bluetooth network, an Ethernet network, and a mobile phone network.
  • an exemplary embodiment may comprise a method as described above wherein sending the secret information includes sending a text message including the secret information to the trusted device.
  • an exemplary embodiment may comprise a method as described above wherein sending the secret information to the trusted device is preceded by sending a lock signal to the trusted device to disable operation of the trusted device until an authorized user of the trusted device enters an unlock code.
  • an exemplary embodiment may comprise apparatus including a communication module configured to receive a voice command and to transmit a text message; and a processor configured to: process the voice command to identify a verbal request for secret information; access the secret information; identify a trusted device authorized to receive the secret information; and provide to the communication module the text message including the secret information for transmission to the trusted device.
  • an exemplary embodiment may comprise apparatus including a communication module configured to receive a voice command and to transmit a message; a memory; and a processor configured to: process the voice command to identify a request for secret information; access the secret information from the memory; identify a trusted device authorized to receive the secret information; determine contact information for the trusted device; and provide to the communication module the message including the secret information for transmission to the trusted device.
  • an exemplary embodiment may comprise apparatus as described above wherein the processor is further configured to, prior to transmission of the secret information: determine whether the trusted device is authorized to receive the secret information; and responsive to the trusted device being authorized, enable the communication module to transmit the secret information to the trusted device.
  • an exemplary embodiment may comprise apparatus as described above wherein the processor is further configured to determine whether the trusted device is authorized by: determining at least one factor associated with the trusted device; processing the factor to determine an authentication score; and evaluating the authentication score to determine whether the trusted device is authorized to receive the secret information.
  • an exemplary embodiment may comprise apparatus as described above wherein the at least one factor comprises one or more of a location of the trusted device, a history of usage of the trusted device, an IoT behavior associated with the trusted device, and whether a device to which the secret information applies or provides access is on the same network as the trusted device.
  • an exemplary embodiment may comprise apparatus as described above wherein transmission of the secret information is preceded by parsing the secret information into a non-secure portion and a secure portion; and wherein the non-secure portion is provided in the clear and the secure portion is transmitted to only the trusted device.
  • an exemplary embodiment may comprise apparatus as described above wherein providing the non-secure portion in the clear includes producing an audio output representing the non-secure portion.
  • an exemplary embodiment may comprise apparatus as described above wherein the processor is further configured to synthesize a speech signal representing a verbal presentation of the non-secure information; and the apparatus further includes an audio reproduction device to audibly reproduce the speech signal.
  • an exemplary embodiment may comprise apparatus as described above wherein: the request for secret information includes a request for a single-use identifier; accessing the secret information includes generating the single- use identifier; and sending the secret information includes sending the single-use identifier to the trusted device.
  • an exemplary embodiment may comprise apparatus as described above wherein generating the single-use identifier includes one of selecting the single-use identifier from a list and random generation of the single-use identifier.
  • an exemplary embodiment may comprise apparatus as described above wherein sending the single-use identifier to the trusted device is followed by: receiving a second voice command including the single-use identifier and requesting second secret information; recognizing the single-use identifier; providing the second secret information to the trusted device responsive to recognizing the single-use identifier; and disabling further recognition of the single-use identifier.
  • an exemplary embodiment may comprise apparatus as described above wherein receiving the voice command comprises receiving the voice command via a first device enabled to communicate on a communication network comprising one or more of a WiFi network, a Bluetooth network, an Ethernet network, and a mobile phone network.
  • an exemplary embodiment may comprise apparatus as described above wherein sending the secret information includes sending a text message including the secret information to the trusted device.
  • an exemplary embodiment may comprise apparatus as described above wherein sending the secret information to the trusted device is preceded by sending a lock signal to the trusted device to disable operation of the trusted device until an authorized user of the trusted device enters an unlock code.
  • an exemplary embodiment may comprise a non-transitory storage media having computer readable programming code stored thereon for performing any of the methods described above.
  • an exemplary embodiment may comprise a method including: receiving a first voice command; detecting a request for a single- use identifier included in the first voice command; generating the single-use identifier; identifying a trusted device authorized to receive the single-use identifier; determining contact information for the trusted device; sending the single-use identifier to the trusted device using the contact information; receiving a second voice command including the single-use identifier and requesting a secret information; disabling further use of the single-use identifier;
  • an exemplary embodiment may comprise a method as described in the preceding paragraph wherein sending the secret information is preceded by: determining whether the trusted device is authorized to receive the secret information; and responsive to the trusted device being authorized, enabling the sending to send the secret information to the trusted device.
  • an exemplary embodiment may comprise a method as described in the preceding paragraph wherein determining whether the trusted device is authorized comprises: determining at least one factor associated with the trusted device; processing the factor to determine an authentication score; and evaluating the authentication score to determine whether the trusted device is authorized to receive the secret information.
  • an exemplary embodiment may comprise a method as described in the preceding paragraph wherein the at least one factor comprises one or more of a location of the trusted device, a history of usage of the trusted device, an IoT behavior associated with the trusted device, and whether a device to which the secret information applies or provides access is on the same network as the trusted device.
  • FIG. 1 showing in block diagram form an apparatus and a system in accordance with one or more embodiments described herein;
  • FIG. 2 showing in flowchart form an aspect of one or more embodiments described herein;
  • FIG. 3 showing in flowchart form another aspect of one or more embodiments described herein;
  • FIG. 4 showing in flowchart form another aspect of one or more embodiments described herein;
  • FIG. 5 showing in flowchart form another aspect of one or more embodiments described herein;
  • FIG. 6 showing in flowchart form another aspect of one or more embodiments described herein;
  • FIG. 7 showing in flowchart form another aspect of one or more embodiments described herein;
  • FIG. 8 showing in flowchart form another aspect of one or more embodiments described herein.
  • FIG. 9 showing in flowchart form another aspect of one or more embodiments described herein.
  • the elements shown in the figures may be implemented in various forms of hardware, software or combinations thereof. Preferably, these elements are implemented in a combination of hardware and software on one or more appropriately programmed general-purpose devices, which may include a processor, memory and input/output interfaces.
  • general-purpose devices which may include a processor, memory and input/output interfaces.
  • the phrase "coupled" is defined to mean directly connected to or indirectly connected with or through one or more intermediate components. Such intermediate components may include both hardware and software based components.
  • processor or “controller” should not be construed to refer exclusively to hardware capable of executing software, and may implicitly include, without limitation, digital signal processor (DSP) hardware, read only memory (ROM) for storing software, random access memory (RAM), and nonvolatile storage.
  • DSP digital signal processor
  • ROM read only memory
  • RAM random access memory
  • any switches shown in the figures are conceptual only. Their function may be carried out through the operation of program logic, through dedicated logic, through the interaction of program control and dedicated logic, or even manually, the particular technique being selectable by the implementer as more specifically understood from the context.
  • any element expressed as a means for performing a specified function is intended to encompass any way of performing that function including, for example, a) a combination of circuit elements that performs that function or b) software in any form, including, therefore, firmware, microcode or the like, combined with appropriate circuitry for executing that software to perform the function.
  • the disclosure as defined by such claims resides in the fact that the functionalities provided by the various recited means are combined and brought together in the manner which the claims call for. It is thus regarded that any means that can provide those functionalities are equivalent to those shown herein.
  • FIG. 1 shows, in block diagram form, an exemplary embodiment of an apparatus and/or system in accordance with the present principles.
  • device 100 may receive, process and output various types of signals and communicate with other devices such as second device 190 and other resources (e.g., memory, processing capability, etc.), devices etc. in the cloud represented by 180.
  • device 190 may communicate directly with resources in the cloud 180.
  • Such communications between device 100, device 190 and the cloud 180 may be by wired and/or wireless means as will be apparent to one skilled in the art.
  • device 100 may be a device providing features similar to that of the Amazon Echo including receiving and processing voice commands.
  • device 100 may provide input/output such as via a wireless local network (e.g., WiFi, Bluetooth, etc.) and/or a wired network, e.g., Ethernet or cable, and/or via a communication system such as a cellular phone network.
  • a wireless local network e.g., WiFi, Bluetooth, etc.
  • a wired network e.g., Ethernet or cable
  • device 100 may output and/or receive SMS text signals via an RF communication path (e.g., WiFi, cellular, Internet, etc.).
  • Device 190 may be a device such as a mobile device, e.g., cell phone, tablet, laptop, etc.
  • Device 100 may include features such as a processor 120 coupled to data storage device 130 generally referred to herein as memory.
  • the processor and data storage may be implemented in various forms such as a system on a chip including memory (RAM and/or ROM and/or EEPROM and/or a hard drive, etc.), a microprocessor, and various other embodiments that will be apparent to one skilled in the art.
  • the processor may access software code stored in memory 130 and execute the code in accordance with aspects and embodiments described herein.
  • the capability of processor 120 may be supplemented or operate in conjunction with other processors, processing capability such as that which may be available in the cloud 180, e.g., remote servers, head end equipment, service providers, etc.
  • processing as described herein may occur solely within a device such as device 100 using processing capability included in device 100 such as illustrated by processor 120. Also, processing a described herein may occur in resources in cloud 180. Also, processing as described herein may occur using a combination of processing resources in device 100 and resources in the cloud 180. Various combinations and embodiments of processing in accordance with the present principles will be apparent to one skilled in the art.
  • Device 100 may further include various inputs and outputs. Input signals from the inputs may be received and processed by processor 120. Processor 120 may also produce output signals provided to the various outputs. For example, an input 110 may receive audio signals such as voice signals that are processed by processor 120 to identify an audio command such as "Alexa, what time is it?". Examples of input 110 include but are not limited to a microphone or other form of audio sensor or transducer. One or more inputs 115 may receive various other types of input signals such as from a touch screen, keyboard, etc.
  • Device 100 may also include one or more outputs such as output 140 for generating text signals, e.g., SMS text, suitable for output via a wireless signal such as a cellular signal and/or WiFi, Bluetooth or other wireless format, or via a hardwired connection, e.g., Ethernet, cable, optical, etc.
  • processor 120 may produce a text output signal at output 140 such as "The time is 8 AM" in response to the above-mentioned exemplary audio command and output the text output signal by a wireless network such as a cellular network to device 190.
  • Device 100 of Figure 1 may also produce outputs in other formats such as audio (e.g., an audio output of "The time is 8 AM") via audio output 150 or other output such as a visible image on a display device, email message, etc., represented by other output 160 in Figure 1.
  • audio e.g., an audio output of "The time is 8 AM”
  • audio output 150 or other output such as a visible image on a display device, email message, etc., represented by other output 160 in Figure 1.
  • device 100 may be connected to other resources that may be remote from 100 such as devices, servers, head-end services, etc. that may be considered to be in the cloud 180 and in communication with device 100 via wireless or wired communication. Utilizing such remote resources may involve device 100 forwarding or relaying input signals such as voice signals to the cloud for processing, e.g., by sending an audio file to resources in cloud 180 for processing where the audio file represents a voice command received and stored by device 100. Processing by a processor or resources in the cloud 180 may, for example, process the received audio file, determine how to respond in accordance with the present principles, generate an audio file representing a response (e.g., "The time is 8 AM"), and return the response audio file to device 100. Then, processor 120 of device 100 may process the audio response file and output the response, e.g., by sending a SMS text message to 190 or creating an audio signal that is then output as an audible response, e.g., via audio output 150.
  • processor 120 of device 100 may process the audio response file and output the
  • an exemplary embodiment may comprise a method such as that shown in Figure 2 that may, for example, be implemented in software and/or hardware such as the exemplary embodiment of a system or apparatus shown in Figure 1.
  • a processor such as processor 120 in Figure 1 may execute a software routine stored in memory 130 of Figure 1 to implement an exemplary embodiment such as the method illustrated in Figure 2.
  • An embodiment such as that shown in Figure 2 and other exemplary embodiments of methods in accordance with the present principles as described herein may encompass various steps or operations that, as will be apparent to one skilled in the art, may occur in an order or sequence other than that described.
  • the exemplary method begins when a voice command is received at 210, e.g., by voice input 110 in the system or apparatus of Figure 1.
  • the voice command is evaluated at 220, e.g., by processor 120 of Figure 1, to determine if the received voice command is a request for secure information such as a password or access code.
  • secure information may be referred to hereinafter as secure, secret or sensitive information and any such reference is intended as a general indication broadly encompassing various types of information for which access is, should be or may desirably be restricted or limited.
  • block 280 indicated in phantom in Figure 2 that may include various operations as indicated and as described below.
  • operation begins at 230 where a request for secure information results in retrieval of the secure information, e.g., by processor 120 retrieving the secure information from data storage such as memory 130 or other data storage accessible by processor 120, e.g., a database or secure data "vault" that may, for example, store secure information in a secure manner such as in an encrypted format.
  • a trusted device associated with the secure information is identified.
  • a database that stores secure information such as a password may include an identifier of a mobile device such as device 190 in Figure 1 that is a trusted device or authorized device in that the device is permitted to access or receive the requested secure information.
  • the identifier may be, for example, a mobile phone number to which secure information may be sent by SMS text message.
  • Other examples of suitable identifiers of a trusted device include but are not limited to a name of the device, e.g., "John's iPad", or an IP address or a local network identifier of the device.
  • Operation 240 is followed by 250 during which contact information associated with the trusted device is determined. For example, contact information such as a mobile phone number or email address associated with an identifier such as a name of a device may be determined, e.g., by accessing contact information that may be stored in the same or a different storage device or location as the identifier.
  • Operation 250 may be unnecessary, for example, if the identifier is itself contact information such as in the case of the identifier being a mobile phone number suitable for receiving communications such as an SMS text message. Operation 250 is followed by delivery of the secure information to the trusted device. Delivery of the secure information occurs in a manner that limits access to the secure information to only the trusted device. For example, the information may be delivered by sending a message such as SMS text message or email to the contact information determined for the trusted device.
  • the above-described exemplary embodiment of Figure 2 involves various processing operations such as processing voice commands, retrieving secure information, and delivery of secure information. In accordance with the present principles, such processing may be performed, for example, by features of device 100 of Figure 1 such as processor 120.
  • processing may occur using resources such as remote servers in the cloud 180 illustrated in Figure 1. Such processing may also occur using a combination of processing in device 100 and in the cloud. Processing may also occur in the trusted device.
  • an exemplary embodiment of the method of Figure 2 may comprise 210 occurring in a device such as an Amazon Echo device, 220 and 270 occurring in servers in the cloud that are associated with Amazon, and 230, 240, 250 and 260 occurring in a second server in the cloud processing customized operations not included as part of the original features of Echo. For example, processing of a command such as "Alexa, what time is it?" would occur in an Amazon server while a command such as "Alexa, what is my gateway password?” would be processed by the second server.
  • another exemplary embodiment may comprise a method such as that shown in Figure 3.
  • the method of Figure 3 begins when a voice command is received at 310, e.g., by voice input 110 as shown in Figure 1.
  • the voice command is processed, e.g., by processor 120 as shown in Figure 1, to determine if the voice command is a request for secure information. If not, 320 is followed by 360 where a response to the command is produced such as the above described audio output stating the time of day.
  • the operations occurring at 310, 320 and 360 may be similar to or the same as those described above in regard to 210, 220, and 270, respectively, of Figure 2.
  • the exemplary embodiment of Figure 3 illustrates increased or enhanced security features that may be implemented in accordance with the present principles. As shown in Figure 3, determining at 320 that the voice command is a request for secure information is followed at 330 by a determination as to whether or not enhanced security is to be applied.
  • Applying enhanced security may occur, e.g., as a result of enabling an enhanced security option by a system administrator or network administrator or other party having authorization to configure a system incorporating aspects of the present principles.
  • Such an option might be enabled for a particular time period, or for one command, or a plurality of commands, or until disabled by an authorized party, or for a particular command or category of commands such as a request for a particular type of secure information.
  • enhanced security might be enabled while there are visitors in the home to decrease the likelihood of unauthorized access to secure information by the visitors.
  • enhanced security might apply if a voice command requests a category of secure information that is highly sensitive information such as a bank account password or a social security number.
  • 330 determines that enhanced security is not applied, i.e., not enabled, then 330 is followed by 350 where the requested secure information is delivered, e.g., by a procedure such as described above in regard to 280 of Figure 2. If enhanced security is to be applied then 330 is followed by 340 where enhanced security is implemented in accordance with the present principles by one or more of various exemplary embodiments as described further below. Following implementation of enhanced security at 340, the requested secure information is delivered or provided such as by procedure 280 in Figure 2. That is, in some circumstances, providing secure information to a trusted device as in 280 of Figure 2 may provide adequate security. In other situations, enhanced security as described herein provides additional security measures beyond that of procedure 280 to further decrease the likelihood of unauthorized access to secure information such as the above-mentioned category of highly sensitive information.
  • an exemplary embodiment of enhanced security may comprise a method such as that shown in Figure 4.
  • enhanced security begins at 410 and is followed by process 480 indicated in phantom.
  • Process 480 begins at 420 where one or more authentication factors are accessed or determined such as by processor 120 of Figure 1.
  • Authentication factors relate to authenticating the identity of a user. Such factors may include information explicitly provided by a user, e.g., requiring the user to enter a password. Alternatively or in addition to explicit information, authentication factors may include information determined in an implicit manner. An example of an implicit factor is behavior or activity associated with a trusted device.
  • factors such as a current location of a device and/or a history of locations of the device and/or activity or interactions of the device with the Internet, with devices in the home (e.g., Internet of Things (IoT) devices), etc., may provide information sufficient to authenticate a user of a device.
  • IoT Internet of Things
  • Interaction with devices such as IoT devices and the history of such interactions e.g., history of time of interaction and/or the nature of the interaction
  • IoT behavior e.g., if the device has accessed a particular web site and has done so at the same time on multiple days then the activity may indicate with reasonable certainty that the user is authenticated.
  • a trusted device is associated with a user named John and the device is located in his home or in his room in his home then that may be interpreted as an indication that the trusted device is with John or in a location appropriate for John such that a request for secure information is from John and the secure information may be delivered to the trusted device.
  • Another example of an implicit factor is whether a device for which the requested secret information provides access and the device requesting the information are on the same network. If so, the common network indicates the trusted device may be authorized to receive the secret information. For example, if a device requests a password to login to another device on the same network such as a home WiFi network then the requesting device may be authenticated or authorized.
  • authorization or authentication is indicated if a trusted device currently connected to a home network requests secure information from another device on the same home network or requests secure information pertaining to another device on the same home network.
  • Such explicit and/or implicit factors may be processed to determine an authentication score or rating at 430 in Figure 4. For example, if multiple factors exist, each implicit and/or explicit factor may be weighted and the weighted factors combined to determine the authentication score or rating. As a specific example, if a user is required to enter a password such explicit information may indicate a high likelihood that the user is authorized and given a high weight such as .9 or .95 while implicit factors may be weighted to indicate less confidence, e.g., a weight of .5.
  • the authentication rating is evaluated at 440 where, if the resulting authentication rating is above a threshold or a particular value or meets certain criteria or is within established limits then authentication is confirmed and the requested secure information is provided.
  • the secure information is provided at 460 which may involve providing the requested secure information to a trusted device such as by process 280 of Figure 2. If the evaluation at 440 determines that the authentication rating is not adequate or not within limits then access to the secure information is denied at 450.
  • the authentication score and/or the authentication rating limit may vary depending on the sensitivity of the secure information. For example, if the request for secure information is a request for a home WiFi network password then a relatively low authentication rating or limit may be adequate. An authentication score or rating or limit indicating a greater level of confidence in the identification or authenticity of the requester may be set or required before providing secure information in response to a request for very sensitivity secure information such as a bank account password or ATM pin.
  • enhanced security may comprise a method such as that shown in Figure 5.
  • enhanced security begins at 510 and is followed by process 580 indicated in phantom.
  • process 580 provides a compromise by providing or communicating a portion of the secure information in the clear and, for example, keeping a portion or some characters of the secure information as a secure portion, e.g., by making the secure portion blank, hidden or obscured in the communication. Then, the secure portion may be delivered or provided via a trusted device.
  • process 580 begins at 520 where lookup of the requested sensitive or secure information occurs such as by processor 120 in Figure 1 accessing or looking up the secure information from data storage such as memory 130 or other data storage device.
  • Data lookup at 520 is followed by 530 where the secure information is parsed into two portions: a secure part and a non-secure part.
  • the request for secure information may be a request for a password such as a local network or WiFi password.
  • the password might be "ak2d_apple_5294”.
  • the parsing operation 530 might parse the password into a non-secure portion such as "ak2d_*****_5294" and a secure portion "apple”.
  • the secure portion may be provided in a secure manner at 540, e.g., provided to a trusted device in the same or similar manner as in operation 280 of Figure 2.
  • "apple” may be provided to only the trusted device by SMS text message or other means such as placing a call to the trusted device.
  • the secure portion could be static, i.e., have the same value each time the parsing operation is performed at 530, e.g., by storing the secure part. In such case, parsing as provided at 530 may involve reading both the secure and non-secure portions stored in memory.
  • the secure part could be determined or generated dynamically such as by varying the portion that is considered secure each time the parsing operation at 530 is performed.
  • Dynamic generation of the secure and non-secure parts could involve, for example, a stored list of a plurality of combinations of secure and non-secure portions and each operation of parsing at 530 then accesses a different one of the stored combinations.
  • various other approaches are possible for dynamic generation of secure and non-secure parts appropriate for use with the present principles.
  • the non-secure portion may be provided in the clear.
  • the content of the nonsecure portion could be converted to a voice signal by processor 120 of Figure 1 and broadcast via an audio output such as audio output 150 in Figure 1, e.g., a loudspeaker, enabling anyone in the vicinity of the audio output device to hear and understand the non-secure content described or presented in the audio output.
  • an audio output such as audio output 150 in Figure 1, e.g., a loudspeaker
  • Another example of providing the non-secure information in the clear would be to display the non-secure information on a television or other display device that is observable by anyone in the vicinity of the display device.
  • enhanced security may comprise a method such as that shown in Figure 6.
  • enhanced security begins at 610 and is followed by process 680 indicated in phantom.
  • Process 680 involves using voice interfaces and the concept of a skill to interact with a specific component.
  • a gateway device included in a home network for managing, receiving and delivering content could be named "Sophia”. Therefore, a voice command for a network including a device such as an Amazon Echo could be "Alexa, ask Sophia for my WiFi password" where "Sophia" may be considered to be the skill name.
  • a device name or skill name is known, anyone could ask for the password information and thus the information is not secure.
  • a form of enhanced security in accordance with the present principles and shown in an exemplary embodiment in process 680 of Figure 6 addresses and solves the described problem using a series of single-use skills.
  • a single-use skill as described herein represents a name or code that can be used once and only once to ask for secret or secure information. For example, in the preceding example involving the name Wu, if Sophia were a single-use skill name then the command "Alexa, ask Euro WiFi password" would work once to obtain the secure information, e.g., the network password, with the single-use skill name. The skill namedale would not be recognized or would be ignored after one successful communication of the namebericht and delivery of the associated secure information.
  • Such single-use skill names may be static, defined by the user, or generated randomly and communicated to a trusted device associated with the single use skill request via means such as SMS text message, a phone notification, email message, etc.
  • a user could request a single-use skill name, e.g., "Alexa, give me a single-use skill name”.
  • the system sends the name "Sophia" to a trusted device associated with single-use skill requests or authorized to request a single-use skill name.
  • the system sends the single-use skill name Sophia to a trusted smartphone by SMS text message or any of other various means of communicating with the trusted device such as phone call, voicemail or email.
  • the user asks "Alexa, ask Ontario to setup a guest network”.
  • the system recognizes the single-use skill name and performs the requested function. Afterwards, the skill namebericht would not be valid.
  • creating a custom skill that is operational with the system may require registration of the skill and the skill name with the service provider, e.g., Amazon.
  • a system such as Amazon's will recognize custom skills and redirect commands involving the custom skills to a particular server designated for handling such custom skills.
  • “Alexa, ask Sophia " will cause Amazon's system to detect and process the request to Alexa, determine a custom skill named "Sophia" is involved, and forward the command to the server handling the Sophia skill.
  • a system or service requiring registration of custom skills may make creating a single-use skill as described above problematic.
  • the registration process may make it problematic to create a single-use skill immediately in response to a request and to disable the skill after use. If so, another exemplary embodiment of enhanced security utilizing single-use skills in accordance with the present principles, the description above and the exemplary embodiment shown in Figure 6 may comprise the following:
  • the trusted person i.e. the owner of the trusted device
  • creates a single use identifier e.g., an alphanumeric text string such as "Temp”.
  • the single-use code "Temp” is sent to the person that needs secure information, e.g., a password to access a protected resource (e.g., Wifi Password).
  • a protected resource e.g., Wifi Password
  • process 680 begins at 620 following the beginning of enhanced security at 610.
  • a single- use identifier e.g., a single-use skill name
  • the generation of a single-use skill name or identifier may occur in response to a voice command requesting a single- use identifier.
  • Generation may involve, for example, accessing a single-use identifier from a list of available identifiers or by random generation of a name or by a user creating a single-use identifier such as a code or alphanumeric string.
  • the list of single-use identifiers may be created and maintained (e.g., updated, replaced, etc.) by an authorized user such as a system administrator periodically, when necessary, automatically, etc.
  • the single-use identifier is provided to a trusted device associated with, or authorized to use, single-use skill names.
  • the single-use identifier may be provided to the trusted device, for example, using operation 280 of Figure 2 where the single-use identifier may be considered to be the secure information.
  • the user of the trusted device may give a voice command using the single-use identifier such as in the example above: "Alexa, ask Sophia to setup a guest network".
  • the voice command is received at 640 and evaluated at 650, e.g., by a processor such as processor 120 in Figure 1, to determine whether the command includes a valid single-use identifier.
  • the secure information requested by the command including the single-use identifier is provided to the trusted device.
  • a guest network may be established by the system and the guest network access information is provided to the trusted device, e.g., using a procedure such as operation 280 in Figure 2. If the evaluation of the voice command at 650 determines that a valid single-use identifier is not included in the voice command then the voice command is processed further at 675.
  • another exemplary embodiment of enhanced security may comprise a method such as that shown in Figure 7.
  • enhanced security begins at 710 in response to a request for secure information and is followed by process 780 indicated in phantom.
  • a common security feature of many devices e.g., a mobile phone, tablet, laptop, etc.
  • the locked mode prevents or disables access or use of the device until an access code such as a PIN (personal identification number) is entered.
  • the present exemplary embodiment of enhanced security in accordance with the present principles incorporates use of a locked mode of a device.
  • process 780 begins at 720 where a trusted device is identified such as by look-up in memory of identification or contact information for a trusted device associated with the requested secure information.
  • the system sends a lock command to the trusted device using the identification or contact information determined in 720.
  • a lock command as described herein causes the trusted device to enter the above-described locked mode of the device.
  • the trusted device is locked and a user must enter a PIN or other access code generally referred to herein as a PIN.
  • the system processes the PFN entry by the user of the trusted device and the PFN entry is evaluated at 750.
  • the secure information is provided to the trusted device, e.g., using process 280 of Figure 2. If the PFN is incorrect or invalid then at 770 the request for secure information is ignored. That is, the system does not provide the requested secure information.
  • the particular PFN required for a successful or valid evaluation at 750 may vary.
  • a particular device may have one PFN to enable general or basic access to the device, e.g., to make phone calls.
  • a PFN having a different or more secure value (e.g., more characters) may be required to obtain access to secure information.
  • Various PFNs of various formats may be used for a single device. For example, a first PFN of four characters may be required for access to basic device operations such as making phone calls.
  • a second, different PFN such as a different combination of four characters or a PFN involving more characters may be required for access to secure information such as a local WiFi network password.
  • a third PFN different from the first and second PFNs (e.g., different four-character combination or including more characters) may be required for highly secure information such as bank account access information.
  • Another variation may involve selective locking in that the trusted device is locked only as to the secure information. For example, complete locking of a trusted device may be undesirable. A user may be performing an important operation or activity on the trusted device and the activity could undesirably be interrupted if the device received a lock command and proceeded to immediately enter a locked mode.
  • An exemplary embodiment in accordance with the present principles for overcoming the described problem may comprise the following operation: 1) The secure information is received and stored by the trusted device, e.g., stored by an application program, but the secure information is not displayed or otherwise immediately accessible.
  • the user is notified that secure information is available, e.g., notification by SMS text message, email, displaying a message on a screen of the trusted device, etc..
  • the access code or PIN may be generated and/or have characteristics as described above.
  • (1) above selectively locks the trusted device with respect to accessing the secure information while other functions of the device remain active or available to a user.
  • FIG. 8 shows an exemplary embodiment in accordance with the present principles wherein enhanced security includes a plurality of the above-described exemplary embodiments.
  • enhanced security begins at 810 and is followed by a first security procedure involving evaluation of authentication factors such as operation 480 of Figure 4 as described above. If the evaluation of authentication factors indicates the user of the trusted device is authorized then operation 480 in Figure 8 may be followed by an additional security procedure involving generation, delivery, use and evaluation of a single-use identifier by the trusted device such as operation 680 in Figure 6 as described above.
  • Receipt of a valid single-use identifier may be followed by a further security procedure involving parsing the secure information such as by using operation 580 in Figure 5 as described above.
  • a lock command procedure such as 780 of Figure 7 as described above may be used to lock the trusted device and require the user to enter a valid PIN, thereby confirming the user of the trusted device is the authorized user. If the results of all of these security procedures indicated the user is authorized then the secure information is provided via the trusted device at 820 in Figure 8.
  • Figure 9 illustrates another exemplary embodiment in accordance with the present principles that combines various features described above.
  • a voice command is received at 910.
  • the voice command is evaluated to determine whether the voice command includes a valid single-use identifier such as described previously in regard to Figure 6. If the voice command includes a valid single-use identifier then 920 is followed by 930 where any further use of the particular single-use identifier is blocked. Then, 930 is followed by 940 where the secure information associated with the single use identifier is delivered to a trusted device such as by operation 280 in Figure 2.
  • 920 is followed by 950 where further evaluation of the voice command occurs to determine whether the voice command includes a request for secure information. If not, then the voice command is processed at 980 to provide the appropriate response. If 950 determines that the voice command is a request for secure information then 950 is followed by 960 where the system checks to see if enhanced security is enabled or required. If not, 960 is followed by 940 where the requested secure information is delivered such as by operation 280 of Figure 2. If the system determines at 960 that enhanced security is enabled then enhanced security is applied at 970 prior to delivering the requested secure information at 940. Enhanced security as applied at 970 may be implemented in accordance with one or more of the exemplary embodiments described herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention concerne un appareil, un système et un procédé d'authentification pour l'expérience d'utilisateur conversationnelle qui traitent des instructions vocales et, en réponse à des demandes d'informations sécurisées, déterminent un dispositif de confiance associé aux informations sécurisées et délivrent les informations sécurisées au dispositif de confiance en utilisant des informations de contact pour le dispositif sécurisé. La délivrance des informations sécurisées peut uniquement avoir lieu après l'application d'une sécurité améliorée.
PCT/US2018/035645 2017-06-29 2018-06-01 Appareil, système et procédé d'authentification pour expérience d'utilisateur conversationnelle WO2019005423A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762526644P 2017-06-29 2017-06-29
US62/526,644 2017-06-29

Publications (1)

Publication Number Publication Date
WO2019005423A1 true WO2019005423A1 (fr) 2019-01-03

Family

ID=62713111

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2018/035645 WO2019005423A1 (fr) 2017-06-29 2018-06-01 Appareil, système et procédé d'authentification pour expérience d'utilisateur conversationnelle

Country Status (1)

Country Link
WO (1) WO2019005423A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170041296A1 (en) * 2015-08-05 2017-02-09 Intralinks, Inc. Systems and methods of secure data exchange

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170041296A1 (en) * 2015-08-05 2017-02-09 Intralinks, Inc. Systems and methods of secure data exchange

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ABILITYNET: "Adapting Technology Changing Lives Voice Recognition for Blind Computer Users", 31 January 2007 (2007-01-31), XP055501981, Retrieved from the Internet <URL:http://www.pathstoliteracy.org/sites/pathstoliteracy.perkinsdev1.org/files/uploaded-files/Voice-Recognition-for-Blind-Computer-Users_0.pdf> [retrieved on 20180824] *
PARASCHIV: "Forgot Your OneLogin Password? Don't Fret, Use SMS to Reset", 9 October 2014 (2014-10-09), XP055501976, Retrieved from the Internet <URL:https://web.archive.org/web/20141009151548/http://www.onelogin.com/blog/sms-password-reset/> [retrieved on 20180824] *

Similar Documents

Publication Publication Date Title
US11855981B2 (en) Authenticating a user device via a monitoring device
US10223520B2 (en) System and method for integrating two-factor authentication in a device
KR102511811B1 (ko) 봇 사용자를 안전하게 인증하는 기법
US10044761B2 (en) User authentication based on user characteristic authentication rules
US10523665B2 (en) Authentication on thin clients using independent devices
KR102188983B1 (ko) 애플리케이션의 인증
US10972458B1 (en) Methods and systems for authentication assistant
US20150088760A1 (en) Automatic injection of security confirmation
US20210119802A1 (en) Two-way authentication for voice-activated devices
KR102436509B1 (ko) 임시 계정 정보를 제공하는 방법, 장치 및 시스템
CN104025539A (zh) 促进单点登录服务的方法和装置
CN106470145B (zh) 即时通信的方法和装置
US11902275B2 (en) Context-based authentication of a user
US11777942B2 (en) Transfer of trust between authentication devices
US10511594B2 (en) Verification information processing method and device
US20170180986A1 (en) Multi-factor user authentication based on decoy security questions
KR20210074299A (ko) 사용자 크리덴셜을 관리하기 위한 시스템, 방법 및 매체
KR20220038704A (ko) 통화 인증을 위한 기술
AU2018101656A4 (en) A System and Method for Facilitating the Delivery of Secure Hyperlinked Content via Mobile Messaging
CN107231338B (zh) 网络连接方法、装置以及用于网络连接的装置
WO2017012212A1 (fr) Procédé, dispositif et système de traitement d&#39;informations, et support de stockage informatique
WO2018166142A1 (fr) Procédé et appareil de traitement d&#39;authentification
US20230224355A1 (en) Providing network access via communal device
WO2019005423A1 (fr) Appareil, système et procédé d&#39;authentification pour expérience d&#39;utilisateur conversationnelle
CN109450953B (zh) 一种授权方法及装置、电子设备和计算机可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18733758

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18733758

Country of ref document: EP

Kind code of ref document: A1