US20150172927A1 - Mobile Device Authentication - Google Patents
Mobile Device Authentication Download PDFInfo
- Publication number
- US20150172927A1 US20150172927A1 US14/629,879 US201514629879A US2015172927A1 US 20150172927 A1 US20150172927 A1 US 20150172927A1 US 201514629879 A US201514629879 A US 201514629879A US 2015172927 A1 US2015172927 A1 US 2015172927A1
- Authority
- US
- United States
- Prior art keywords
- mobile device
- proximity
- authentication
- component
- separate
- Prior art date
- Legal status (The legal status 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 status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H04W4/008—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/60—Context-dependent security
- H04W12/69—Identity-dependent
- H04W12/79—Radio fingerprint
Definitions
- Mobile devices are currently gaining wide popularity. Some mobile devices include cellular telephones, smart phones, and tablet or pad-based computers. Some mobile devices connect to a mobile communication network which could be a cellular network, a voice over IP (VOIP) network or a satellite communication network.
- a mobile communication network which could be a cellular network, a voice over IP (VOIP) network or a satellite communication network.
- VOIP voice over IP
- One common mechanism is to require the user to key in a password on a hardware keypad on the mobile device or on a software keypad displayed on a touch sensitive screen.
- Another mechanism is a fingerprint scan. This requires the user to place his or her finger on a fingerprint scan area of the mobile device to have the user's fingerprint scanned.
- Still other mechanisms include keys or other mechanical mechanisms which are mechanically inserted into a slot or port in the mobile device. When the key is properly inserted, it acts to authenticate the user to the mobile device and it unlocks the sensitive or secure information or actions on the mobile device.
- a mobile device has an authentication module that detects a proximity-based authentication component and unlocks sensitive areas of the mobile device when the proximity-based authentication component is within a desired proximity of the mobile device. If the proximity-based authentication component is not within the desired proximity of the mobile device, the mobile device automatically locks the secured areas of the mobile device.
- the proximity-based authentication component is separate from the mobile device in that it is not inserted or slid within the mobile device, or in any way attached to the mobile device, in order to be used.
- FIG. 1 is a block diagram of one illustrative authentication architecture.
- FIG. 2 is a flow diagram illustrating one embodiment for setting proximity-based authentication on a mobile device.
- FIG. 3 is a flow diagram illustrating one embodiment of the operation of the mobile device in use, once authentication has been set on the mobile device.
- FIGS. 3A-3I show one embodiment of user interface displays generated on a mobile device.
- FIG. 1 is a block diagram of one illustrative authentication architecture 100 .
- Architecture 100 illustratively includes mobile device 102 and a separate, proximity-based authentication component 104 .
- Architecture 100 shows that mobile device 102 is illustratively a communication device that can communicate using a mobile communication network 106 .
- network 106 is a cellular telephone network, a VOIP network, a satellite network, etc.
- FIG. 1 also shows that mobile device 102 illustratively includes storage 108 , mobile communication component 109 , authentication module 110 , display device 112 , user input mechanisms 114 and processor 116 .
- storage 108 mobile communication component 109
- authentication module 110 authentication module 110
- display device 112 user input mechanisms 114
- processor 116 processor 116
- Storage 108 is illustratively a hardware memory device that stores information used by the other components or modules of mobile device 102 .
- storage 108 includes authentication information 118 , one or more applications 120 , other data 122 , and other information 124 that can be stored.
- Storage 108 can be used to store computer readable instructions which, when executed by processor 116 , cause processor 116 to perform steps.
- Storage 108 is illustratively a hardware storage medium that stores the instructions for access by processor 116 .
- Authentication module 110 or parts of it, can comprise instructions stored in storage 108 as well.
- Mobile communication component 109 is illustratively a transceiver that can communicate over network 106 .
- component 109 there are a wide variety of components that can be used as component 109 .
- Processor 116 is illustratively a computer processor with associated memory and timing circuitry (not separately shown). In one embodiment, processor 116 is a functional component of mobile device 102 and is activated by, and facilitates the functionality of, other devices, mechanisms and modules or other components of mobile device 102 .
- Display device 112 is illustratively a user interface display screen that displays user interface displays to a user.
- Display device 112 can, for example, be a touch sensitive screen, or another display device for displaying information.
- User input mechanisms 114 can take a wide variety of different forms.
- the user input mechanisms can be keys on a keypad, sensors on a touch sensitive screen, speech recognition components for recognizing voice commands, displayed user actuable input mechanisms, such as buttons, menus, links, scroll actuators or other displayed items displayed on a touch sensitive screen or another type of user display device which can be actuated by the user either through touch, or through appropriate key inputs, point and click devices or in other ways, etc.
- Authentication module 110 illustratively generates user interface displays on display device 112 that allow a user to select a type of authentication that is to be used with mobile device 102 .
- Authentication module 110 also illustratively includes components for implementing security or authentication measures, once the user has selected a desired authentication mechanism and assigned it to secured areas of mobile device 102 .
- a secured area it is meant that the user can assign security to (or require authentication to access) one or more of a wide variety of different types of information on the mobile device 102 . It is also meant that the user can assign security to (or require authentication for) performing various actions using mobile device 102 .
- authentication module 110 implements the security associated with that authentication mechanisms as well.
- the authentication mechanisms the user can choose include a separate, proximity-based authentication component 104 .
- component 104 communicates with authentication module 110 or is readable by authentication module 110 , when component 104 is within a predetermined proximity of authentication module 110 .
- the separate proximity-based authentication component 104 is a radio frequency identification component (an RFID component)
- authentication module 110 can read information from component 104 when component 104 is within a range of an RFID reader that comprises part of authentication module 110 .
- authentication module 110 when separate, proximity-based authentication component 104 is a near field communication (NFC) component, authentication module 110 includes an NFC circuit that can exchange information with component 104 when component 104 is within a predetermined proximity of authentication module 110 (e.g., within several inches). In any case, once the user has assigned security to sensitive areas of mobile device 102 , then those areas can only be unlocked when component 104 is within the predetermined proximity of mobile device 102 .
- NFC near field communication
- component 104 is not insertable within, slidable within, or otherwise attached to, mobile device 102 in order to unlock the secured areas of mobile device 102 . Instead, component 104 is illustratively carried by the user 105 . In this way, if the user 105 leaves mobile device 102 , mobile device 102 will automatically lock the secured areas of mobile device 102 once the user 105 (and hence component 104 ) has left the predetermined proximity of mobile device 102 .
- component 104 can be incorporated into a badge, a piece of jewelry, a wrist watch, an item carried in the user's wallet or purse, an item of clothing, user's eyeglasses, or it can be any other item that is illustratively carried with user 105 .
- authentication module 110 can implement multi-factor security.
- multi-factor security is a type of security or authentication that requires multiple different security mechanisms input by the user.
- the user must bring authentication component 104 within the predetermined proximity of mobile device 102 in order to unlock the functionality of mobile device 102 .
- the user may be required to perform additional authentication steps (such as to key in a password, speak a password, provide a fingerprint scan, etc.).
- additional authentication steps such as to key in a password, speak a password, provide a fingerprint scan, etc.
- single factor authentication will be discussed, but this is for the sake of example only.
- FIG. 2 is a flow diagram illustrating one embodiment of the overall operation of architecture 100 shown in FIG. 1 in assigning a selected authentication mechanism to secured areas of mobile device 102 .
- mobile device 102 first generates displays that allow a user 105 to input setup information into device 102 .
- Receiving the setup information at mobile device 102 is indicated by block 128 in FIG. 2 .
- Setup information can, of course, include a wide variety of different types of information.
- the setup information can include an image (such as a photograph or picture of user 105 ) as indicated by block 130 .
- the setup information can also include contact information 132 (such as an email address, an alternate telephone number, various other communication information, address information, etc.)
- the setup information can include social network information 134 , such as a social network user name and password, or other social network information.
- the setup information can include a wide variety of different, or additional, information as well, and this is indicated by block 136 .
- authentication module 110 illustratively generates user interface displays on display device 112 that allow user 105 to select an authentication option for use on mobile device 102 .
- the user can illustratively repeat the process to set up the multiple security factors, as desired. Displaying the options for authentication is indicated by block 138 .
- the authentication options illustratively include a proximity-based option 140 , such as a near field communication component, an RFID component, or another proximity-based component 104 .
- the authentication options can also include a bar code option 142 in which the user would carry a barcode that is read by a barcode scanner on mobile device 102 .
- the authentication options can include a matrix barcode (or two-dimensional code), sometimes referred to as a QR code 144 . Like the barcode 142 , the QR code 144 can be carried by the user and read by a QR code reader on mobile device 102 .
- the authentication options can include a keyboard option 146 which allows the user to input a series of keystrokes as a password.
- a touch screen option 148 which allows the user to provide authentication information though a touch screen. This can include providing keystrokes on a virtual keyboard displayed on the touch screen, or putting in other patterns (such as tracing a pattern on the touch screen), touching various spots on the touch screen in a selected order, etc.
- a touch screen option 148 which allows the user to provide authentication information though a touch screen. This can include providing keystrokes on a virtual keyboard displayed on the touch screen, or putting in other patterns (such as tracing a pattern on the touch screen), touching various spots on the touch screen in a selected order, etc.
- authentication module 110 determines whether the user has selected the proximity-based option 140 . This is indicated by block 152 in FIG. 2 . If not, then authentication module 110 instructs the user to provide the other authentication input (such as the barcode, the QR code, the password, the touch screen input, etc.), whatever was selected by the user 105 . This is indicated by block 154 in FIG. 2 . Once the user has input that information, the password, touch screen input, QR code, barcode, etc. can then be assigned to secured areas of the cell phone (such as to secured information or actions on the cell phone). This is indicated by block 156 .
- the other authentication input such as the barcode, the QR code, the password, the touch screen input, etc.
- authentication module 110 determines that the user 105 has selected the proximity-based option 140 , then authentication module 110 generates user interface displays on display device 112 that instruct the user to bring the proximity-based component 104 within the predefined proximity of mobile device 102 , and authentication module 110 reads the proximity-based component 104 .
- the proximity-based component 104 is an RFID tag
- authentication module 110 reads the RFID tag.
- the component 104 is a NFC chip
- authentication module 110 communicates with the NFC chip. Reading the proximity-based authentication component is indicated by block 158 .
- the authentication information read from the authentication component 104 is assigned to the secured areas of the mobile device. Again, these areas can include various aspects of the mobile device operation, as indicated by block 160 .
- the authentication information can be assigned to applications 162 , folders 164 , individual files or other items of information 166 or to individual operations of mobile device 102 , such as operations that allow user 105 to share information from mobile device 102 , or others. This is indicated by block 168 .
- the authentication information can be assigned to other items as well (such as payment operations, accessing bank accounts, other information, etc.), and this is indicated by block 170 .
- FIG. 3 is a flow diagram illustrating one embodiment of the operation of architecture 100 .
- the user has assigned proximity-based authentication to one or more secured areas (data, software or operations) of mobile device 102 .
- authentication module 110 intermittently determines whether the authentication component 104 is within the desired proximity of mobile device 102 . This is indicated by block 180 .
- Authentication module 110 can do this on a periodic basis, such as after a predetermined amount of time has lapsed. Module 110 can also perform this operation based on certain actions input by the user. For instance, if the user attempts to access one of the secured areas of mobile device 102 , authentication module 110 can perform the operation at that time. Of course, authentication module 110 can make this determination at other times or in response to other actions as well.
- authentication module 110 determines that the separate proximity-based authentication component 104 is not within the desired proximity of mobile device 102 , then authentication module 110 generates a display on display device 112 displaying a message that the information or attempted action requires authentication. This is indicated by block 182 . This will prompt user 105 to bring the separate, proximity-based authentication component 104 within the predefined proximity of mobile device 102 for authentication so that mobile device 102 will unlock the secured areas of mobile device 102 .
- authentication module 110 determines that separate, proximity-based authentication component 104 is within the predefined proximity of mobile device 102 , then it unlocks the locked information or actions (or secured areas) of mobile device 102 so that the user can access them. This is indicated by block 184 .
- mobile device 102 By contrast, if the user sets mobile device 102 down and walks away, so that component 104 is outside the predetermined proximity of mobile device 102 , mobile device 102 automatically locks the secured areas of mobile device 102 which require component 104 for authentication. If the user 105 then re-approaches mobile device 102 , bringing component 104 within the predetermined proximity, mobile device 102 automatically again unlocks the secured areas of mobile device 102 . By automatically it is meant that the user need not physically interact with the mobile device 102 for authentication.
- FIGS. 3A-3I show a series of user interface displays on a mobile device (e.g., a smart phone) 200 .
- smart phone 200 has a touch sensitive screen 202 which can be used to display information.
- FIGS. 3A-3H illustrate exemplary user interface displays that can be displayed to walk user 105 through the operation of selecting proximity-based authentication for secured areas of phone 200 .
- the user interface display in FIG. 31 is one example of a message that can be displayed when the user has attempted to access secured areas of telephone 200 , without component 104 being in the predefined proximity of telephone 200 .
- FIG. 3A is a display that displays a welcome message such as “Hi. Welcome to your new phone. We will help you set it up.”
- FIGS. 3B-3D allow the user to input setup information. For instance, FIG. 3B instructs the user to take a picture or other image to be associated with user 105 .
- FIG. 3C instructs the user to enter information such as name, contact information, and social network account information.
- FIG. 3D displays the setup information, as it has been entered by user 105 .
- FIG. 3E shows a user interface display that can be used to instruct the user that he or she is about to enter the authentication process by which the user assigns security or authentication options to phone 200 .
- FIG. 3F displays three different authentication options which were briefly discussed above. The first option is the keyboard password option, the second is an RFID option, and the third is a QR code option.
- the user interface display 200 instructs the user to select one of the options. In the embodiment where the user interface display is a touch sensitive screen, the user simply needs to touch one of the options 204 , 206 , or 208 . Of course, where screen 202 is not a touch sensitive screen, the user can illustratively use arrow keys, a thumb pad, a scroll bar, or another input mechanism to select and actuate options 204 , 206 or 208 .
- FIG. 3G shows a user interface display that instructs the user to place his or her RFID tag near phone 200 so that the RFID information can be read from the user's RFID tag.
- the user 105 illustratively does this and presses or otherwise actuates OK button 210 shown in FIG. 3G .
- the user is then provided with user interface displays that allow the user to assign the authentication information to various secured areas of phone 200 (such as to actions that can be taken from phone 200 , or to information stored or accessible by phone 200 , or to applications that can be run on phone 200 , etc.).
- FIG. 3H shows a user interface display that can be generated explaining that the user has now finished the authentication process.
- phone 200 When the user subsequently attempts to access one of the secured areas of phone 200 , but does not have authentication component 104 within the predefined proximity of phone 200 , phone 200 illustratively generates an interface display such as that shown in FIG. 31 . This prompts the user that the secured area is in fact secured and that the authentication component 104 is needed to access that secured area.
- FIGS. 3A-3I are exemplary only. A wide variety of other user interface displays could be used.
- similar user interface displays can be used where the user selects a different type of authentication option. For instance, if the user selects the keyboard password option, then the user interface display will illustratively instruct the user to enter a password and repeat it. If the user selects a QR code option, the user interface display will illustratively instruct the user to scan the QR code that the user wishes to use for authentication. The same is true of a barcode option. Of course, where other options are selected, the user is instructed in an appropriate way.
Abstract
A mobile device has an authentication module that detects a proximity-based authentication component and unlocks sensitive areas of the mobile device when the proximity-based authentication component is within a desired proximity of the mobile device. If the proximity-based authentication component is not within the desired proximity of the mobile device, the mobile device automatically locks the secured areas of the mobile device. The proximity-based authentication component is separate from the mobile device in that it is not inserted or slid within the mobile device, or in any way attached to the mobile device, in order to be used.
Description
- The present application is a continuation of and claims priority of U.S. patent application Ser. No. 13/763,088, filed Feb. 8, 2013, the content of which is hereby incorporated by reference in its entirety.
- The present application is based on and claims the benefit of U.S. provisional patent application Ser. No. 61/597,564, filed Feb. 10, 2012, the content of which is hereby incorporated by reference in its entirety.
- Mobile devices are currently gaining wide popularity. Some mobile devices include cellular telephones, smart phones, and tablet or pad-based computers. Some mobile devices connect to a mobile communication network which could be a cellular network, a voice over IP (VOIP) network or a satellite communication network.
- Current mobile devices are not only used for communication, but are also used to run applications and process many different types of data. Some of the applications and data that can be used on a mobile device, or some of the actions that can be performed on a mobile device (such as making financial payments, etc.) are sensitive and confidential. Therefore, a user may desire these types of information, or these types of actions, to be secured.
- There have been a number of different mechanisms employed to secure information or actions on a mobile device. One common mechanism is to require the user to key in a password on a hardware keypad on the mobile device or on a software keypad displayed on a touch sensitive screen. Another mechanism is a fingerprint scan. This requires the user to place his or her finger on a fingerprint scan area of the mobile device to have the user's fingerprint scanned. Still other mechanisms include keys or other mechanical mechanisms which are mechanically inserted into a slot or port in the mobile device. When the key is properly inserted, it acts to authenticate the user to the mobile device and it unlocks the sensitive or secure information or actions on the mobile device.
- All of these different types of mechanisms have drawbacks. All of them require the user to physically interact with a mobile device in order to authenticate himself or herself to the device so that the secure areas of the mobile device (the secure information or secure actions) can be accessed. In addition, once the user has authenticated himself or herself to the mobile device, the user can walk away and accidently leave the mobile device behind, in an unsecured state. Anyone coming after the user can then simply pick up the mobile device and access all of the secured areas of the mobile device.
- The discussion above is merely provided for general background information and is not intended to be used as an aid in determining the scope of the claimed subject matter.
- A mobile device has an authentication module that detects a proximity-based authentication component and unlocks sensitive areas of the mobile device when the proximity-based authentication component is within a desired proximity of the mobile device. If the proximity-based authentication component is not within the desired proximity of the mobile device, the mobile device automatically locks the secured areas of the mobile device. The proximity-based authentication component is separate from the mobile device in that it is not inserted or slid within the mobile device, or in any way attached to the mobile device, in order to be used.
- This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. The claimed subject matter is not limited to implementations that solve any or all disadvantages noted in the background.
-
FIG. 1 is a block diagram of one illustrative authentication architecture. -
FIG. 2 is a flow diagram illustrating one embodiment for setting proximity-based authentication on a mobile device. -
FIG. 3 is a flow diagram illustrating one embodiment of the operation of the mobile device in use, once authentication has been set on the mobile device. -
FIGS. 3A-3I show one embodiment of user interface displays generated on a mobile device. -
FIG. 1 is a block diagram of oneillustrative authentication architecture 100.Architecture 100 illustratively includesmobile device 102 and a separate, proximity-basedauthentication component 104.Architecture 100 shows thatmobile device 102 is illustratively a communication device that can communicate using amobile communication network 106. In one embodiment,network 106 is a cellular telephone network, a VOIP network, a satellite network, etc. -
FIG. 1 also shows thatmobile device 102 illustratively includesstorage 108,mobile communication component 109,authentication module 110,display device 112,user input mechanisms 114 andprocessor 116. Of course, this is exemplary only and other or different components can be used inmobile device 102 as well. -
Storage 108 is illustratively a hardware memory device that stores information used by the other components or modules ofmobile device 102. In the embodiment shown,storage 108 includesauthentication information 118, one ormore applications 120,other data 122, andother information 124 that can be stored.Storage 108 can be used to store computer readable instructions which, when executed byprocessor 116, causeprocessor 116 to perform steps.Storage 108 is illustratively a hardware storage medium that stores the instructions for access byprocessor 116.Authentication module 110, or parts of it, can comprise instructions stored instorage 108 as well. -
Mobile communication component 109 is illustratively a transceiver that can communicate overnetwork 106. Of course, there are a wide variety of components that can be used ascomponent 109. -
Processor 116 is illustratively a computer processor with associated memory and timing circuitry (not separately shown). In one embodiment,processor 116 is a functional component ofmobile device 102 and is activated by, and facilitates the functionality of, other devices, mechanisms and modules or other components ofmobile device 102. -
Display device 112 is illustratively a user interface display screen that displays user interface displays to a user.Display device 112 can, for example, be a touch sensitive screen, or another display device for displaying information. -
User input mechanisms 114 can take a wide variety of different forms. For instance, the user input mechanisms can be keys on a keypad, sensors on a touch sensitive screen, speech recognition components for recognizing voice commands, displayed user actuable input mechanisms, such as buttons, menus, links, scroll actuators or other displayed items displayed on a touch sensitive screen or another type of user display device which can be actuated by the user either through touch, or through appropriate key inputs, point and click devices or in other ways, etc. -
Authentication module 110 illustratively generates user interface displays ondisplay device 112 that allow a user to select a type of authentication that is to be used withmobile device 102.Authentication module 110 also illustratively includes components for implementing security or authentication measures, once the user has selected a desired authentication mechanism and assigned it to secured areas ofmobile device 102. By a secured area it is meant that the user can assign security to (or require authentication to access) one or more of a wide variety of different types of information on themobile device 102. It is also meant that the user can assign security to (or require authentication for) performing various actions usingmobile device 102. In any case, onceauthentication module 110 has walked the user through a process by which the user selects a desired authentication mechanism,authentication module 110 implements the security associated with that authentication mechanisms as well. - In the embodiment shown in
FIG. 1 , the authentication mechanisms the user can choose include a separate, proximity-basedauthentication component 104. In one embodiment,component 104 communicates withauthentication module 110 or is readable byauthentication module 110, whencomponent 104 is within a predetermined proximity ofauthentication module 110. For instance, where the separate proximity-basedauthentication component 104 is a radio frequency identification component (an RFID component),authentication module 110 can read information fromcomponent 104 whencomponent 104 is within a range of an RFID reader that comprises part ofauthentication module 110. Similarly, when separate, proximity-basedauthentication component 104 is a near field communication (NFC) component,authentication module 110 includes an NFC circuit that can exchange information withcomponent 104 whencomponent 104 is within a predetermined proximity of authentication module 110 (e.g., within several inches). In any case, once the user has assigned security to sensitive areas ofmobile device 102, then those areas can only be unlocked whencomponent 104 is within the predetermined proximity ofmobile device 102. - It will be noted that, in accordance with one embodiment,
component 104 is not insertable within, slidable within, or otherwise attached to,mobile device 102 in order to unlock the secured areas ofmobile device 102. Instead,component 104 is illustratively carried by theuser 105. In this way, if theuser 105 leavesmobile device 102,mobile device 102 will automatically lock the secured areas ofmobile device 102 once the user 105 (and hence component 104) has left the predetermined proximity ofmobile device 102. Thus, for instance,component 104 can be incorporated into a badge, a piece of jewelry, a wrist watch, an item carried in the user's wallet or purse, an item of clothing, user's eyeglasses, or it can be any other item that is illustratively carried withuser 105. - It will also be noted that
authentication module 110 can implement multi-factor security. For instance, multi-factor security is a type of security or authentication that requires multiple different security mechanisms input by the user. By way of example, in one embodiment, the user must bringauthentication component 104 within the predetermined proximity ofmobile device 102 in order to unlock the functionality ofmobile device 102. Then, in order to access sensitive information onmobile device 102, the user may be required to perform additional authentication steps (such as to key in a password, speak a password, provide a fingerprint scan, etc.). However, for the sake of the present discussion, single factor authentication will be discussed, but this is for the sake of example only. -
FIG. 2 is a flow diagram illustrating one embodiment of the overall operation ofarchitecture 100 shown inFIG. 1 in assigning a selected authentication mechanism to secured areas ofmobile device 102. InFIG. 2 ,mobile device 102 first generates displays that allow auser 105 to input setup information intodevice 102. Receiving the setup information atmobile device 102 is indicated byblock 128 inFIG. 2 . - Setup information can, of course, include a wide variety of different types of information. For instance, the setup information can include an image (such as a photograph or picture of user 105) as indicated by
block 130. The setup information can also include contact information 132 (such as an email address, an alternate telephone number, various other communication information, address information, etc.) Similarly, the setup information can includesocial network information 134, such as a social network user name and password, or other social network information. Of course, the setup information can include a wide variety of different, or additional, information as well, and this is indicated byblock 136. - After the user has setup the phone,
authentication module 110 illustratively generates user interface displays ondisplay device 112 that allowuser 105 to select an authentication option for use onmobile device 102. As is briefly described above, if multi-factor authentication or security is used, the user can illustratively repeat the process to set up the multiple security factors, as desired. Displaying the options for authentication is indicated byblock 138. - The authentication options illustratively include a proximity-based
option 140, such as a near field communication component, an RFID component, or another proximity-basedcomponent 104. The authentication options can also include abar code option 142 in which the user would carry a barcode that is read by a barcode scanner onmobile device 102. The authentication options can include a matrix barcode (or two-dimensional code), sometimes referred to as aQR code 144. Like thebarcode 142, theQR code 144 can be carried by the user and read by a QR code reader onmobile device 102. The authentication options can include akeyboard option 146 which allows the user to input a series of keystrokes as a password. It can also include atouch screen option 148 which allows the user to provide authentication information though a touch screen. This can include providing keystrokes on a virtual keyboard displayed on the touch screen, or putting in other patterns (such as tracing a pattern on the touch screen), touching various spots on the touch screen in a selected order, etc. Of course, there can beother authentication options 150 as well. - The option that will be discussed at greatest length herein is the proximity-based option. Therefore,
authentication module 110 determines whether the user has selected the proximity-basedoption 140. This is indicated byblock 152 inFIG. 2 . If not, thenauthentication module 110 instructs the user to provide the other authentication input (such as the barcode, the QR code, the password, the touch screen input, etc.), whatever was selected by theuser 105. This is indicated byblock 154 inFIG. 2 . Once the user has input that information, the password, touch screen input, QR code, barcode, etc. can then be assigned to secured areas of the cell phone (such as to secured information or actions on the cell phone). This is indicated byblock 156. - However, if, at
block 152,authentication module 110 has determined that theuser 105 has selected the proximity-basedoption 140, thenauthentication module 110 generates user interface displays ondisplay device 112 that instruct the user to bring the proximity-basedcomponent 104 within the predefined proximity ofmobile device 102, andauthentication module 110 reads the proximity-basedcomponent 104. For instance, if the proximity-basedcomponent 104 is an RFID tag,authentication module 110 reads the RFID tag. If thecomponent 104 is a NFC chip, thenauthentication module 110 communicates with the NFC chip. Reading the proximity-based authentication component is indicated byblock 158. - Once the authentication component has been read, processing continues at
block 156 where the authentication information read from theauthentication component 104 is assigned to the secured areas of the mobile device. Again, these areas can include various aspects of the mobile device operation, as indicated byblock 160. The authentication information can be assigned toapplications 162,folders 164, individual files or other items ofinformation 166 or to individual operations ofmobile device 102, such as operations that allowuser 105 to share information frommobile device 102, or others. This is indicated byblock 168. Of course, the authentication information can be assigned to other items as well (such as payment operations, accessing bank accounts, other information, etc.), and this is indicated byblock 170. -
FIG. 3 is a flow diagram illustrating one embodiment of the operation ofarchitecture 100. The user has assigned proximity-based authentication to one or more secured areas (data, software or operations) ofmobile device 102. Whenmobile device 102 is started, or otherwise during its operation,authentication module 110 intermittently determines whether theauthentication component 104 is within the desired proximity ofmobile device 102. This is indicated byblock 180.Authentication module 110 can do this on a periodic basis, such as after a predetermined amount of time has lapsed.Module 110 can also perform this operation based on certain actions input by the user. For instance, if the user attempts to access one of the secured areas ofmobile device 102,authentication module 110 can perform the operation at that time. Of course,authentication module 110 can make this determination at other times or in response to other actions as well. - In any case, if
authentication module 110 determines that the separate proximity-basedauthentication component 104 is not within the desired proximity ofmobile device 102, thenauthentication module 110 generates a display ondisplay device 112 displaying a message that the information or attempted action requires authentication. This is indicated byblock 182. This will promptuser 105 to bring the separate, proximity-basedauthentication component 104 within the predefined proximity ofmobile device 102 for authentication so thatmobile device 102 will unlock the secured areas ofmobile device 102. - However, if, at
block 180,authentication module 110 determines that separate, proximity-basedauthentication component 104 is within the predefined proximity ofmobile device 102, then it unlocks the locked information or actions (or secured areas) ofmobile device 102 so that the user can access them. This is indicated byblock 184. - This provides a number of advantages. For instance, once
user 105 has gone through the authentication selection process and assigned authentication to various secured areas ofmobile device 102, theuser 105 need not interact physically withmobile device 102 at all, in order to access those secured areas. By way of example, ifcomponent 104 is an RFID card or an NFC transmitter, and the user is carrying that on his or her person in an area where it will be within the predetermined proximity ofmobile device 102,mobile device 102 will automatically unlock the secured areas ofmobile device 102 so that the user need not even provide any authenticating information or actions in order to access the secured areas. By contrast, if the user setsmobile device 102 down and walks away, so thatcomponent 104 is outside the predetermined proximity ofmobile device 102,mobile device 102 automatically locks the secured areas ofmobile device 102 which requirecomponent 104 for authentication. If theuser 105 then re-approachesmobile device 102, bringingcomponent 104 within the predetermined proximity,mobile device 102 automatically again unlocks the secured areas ofmobile device 102. By automatically it is meant that the user need not physically interact with themobile device 102 for authentication. -
FIGS. 3A-3I show a series of user interface displays on a mobile device (e.g., a smart phone) 200. In the embodiment shown,smart phone 200 has a touchsensitive screen 202 which can be used to display information. Before describing each display in more detail, it will be noted thatFIGS. 3A-3H illustrate exemplary user interface displays that can be displayed to walkuser 105 through the operation of selecting proximity-based authentication for secured areas ofphone 200. The user interface display inFIG. 31 is one example of a message that can be displayed when the user has attempted to access secured areas oftelephone 200, withoutcomponent 104 being in the predefined proximity oftelephone 200. -
FIG. 3A is a display that displays a welcome message such as “Hi. Welcome to your new phone. We will help you set it up.”FIGS. 3B-3D allow the user to input setup information. For instance,FIG. 3B instructs the user to take a picture or other image to be associated withuser 105.FIG. 3C instructs the user to enter information such as name, contact information, and social network account information.FIG. 3D displays the setup information, as it has been entered byuser 105. -
FIG. 3E shows a user interface display that can be used to instruct the user that he or she is about to enter the authentication process by which the user assigns security or authentication options tophone 200.FIG. 3F displays three different authentication options which were briefly discussed above. The first option is the keyboard password option, the second is an RFID option, and the third is a QR code option. Theuser interface display 200 instructs the user to select one of the options. In the embodiment where the user interface display is a touch sensitive screen, the user simply needs to touch one of the options 204, 206, or 208. Of course, wherescreen 202 is not a touch sensitive screen, the user can illustratively use arrow keys, a thumb pad, a scroll bar, or another input mechanism to select and actuate options 204, 206 or 208. - In the embodiment disclosed in
FIGS. 3A-3I , the user selects the RFID option 206.FIG. 3G shows a user interface display that instructs the user to place his or her RFID tag nearphone 200 so that the RFID information can be read from the user's RFID tag. Theuser 105 illustratively does this and presses or otherwise actuatesOK button 210 shown inFIG. 3G . In accordance with one embodiment, the user is then provided with user interface displays that allow the user to assign the authentication information to various secured areas of phone 200 (such as to actions that can be taken fromphone 200, or to information stored or accessible byphone 200, or to applications that can be run onphone 200, etc.). - Once the user has assigned the authentication to the secured areas of
phone 200,FIG. 3H shows a user interface display that can be generated explaining that the user has now finished the authentication process. - When the user subsequently attempts to access one of the secured areas of
phone 200, but does not haveauthentication component 104 within the predefined proximity ofphone 200,phone 200 illustratively generates an interface display such as that shown inFIG. 31 . This prompts the user that the secured area is in fact secured and that theauthentication component 104 is needed to access that secured area. - Of course, it will be noted that the user interface displays shown in
FIGS. 3A-3I are exemplary only. A wide variety of other user interface displays could be used. In addition, similar user interface displays can be used where the user selects a different type of authentication option. For instance, if the user selects the keyboard password option, then the user interface display will illustratively instruct the user to enter a password and repeat it. If the user selects a QR code option, the user interface display will illustratively instruct the user to scan the QR code that the user wishes to use for authentication. The same is true of a barcode option. Of course, where other options are selected, the user is instructed in an appropriate way. - Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims (20)
1. A mobile device, comprising:
a mobile communication component that communicates over a mobile communication network;
an authentication module that automatically detects whether a separate, proximity-based authentication component is within a predefined proximity of the authentication module and, in response to detecting that the separate, proximity-based authentication component is within the predefined proximity, the authentication module automatically unlocking a secured area of the mobile device, the authentication module, in response to detecting that the separate, proximity-based authentication component is outside of the predefined proximity, automatically locking the secured area of the mobile device; and
a processor, being a functional part of the mobile device and activated by the mobile communication component and the authentication module to facilitate communication, detection, locking and unlocking.
2. The mobile device of claim 1 wherein the separate, proximity-based authentication component comprises a radio frequency identification (RFID) tag, the authentication module further comprising:
an RFID reader that detects whether the RFID tag is within the predefined proximity by attempting to read the RFID tag.
3. The mobile device of claim 1 wherein the separate, proximity-based authentication component comprises a near field communication (NFC) device, the authentication module further comprising:
an NFC reader that detects whether the NFC device is within the predefined proximity by attempting to communicate with the NFC device.
4. The mobile device of claim 1 and further comprising:
a user interface display device displaying user interface displays that instruct a user to select an authentication mechanism used by the mobile device to detect whether the separate, proximity-based authentication component is within the predefined proximity of the authentication module.
5. The mobile device of claim 1 wherein the secured area comprises given functionality of the mobile device.
6. The mobile device of claim 1 wherein the secured area comprises given data accessible by the mobile device.
7. The mobile device of claim 6 wherein the secured area comprises one or more given folders accessible by the mobile device.
8. The mobile device of claim 6 wherein the secured area comprises one or more given files accessible by the mobile device.
9. The mobile device of claim 1 wherein the secured area comprises one or more given applications run on the mobile device.
10. The mobile device of claim 1 wherein the secured area comprises given tasks performed with the mobile device.
11. An authentication system, comprising:
a mobile device, comprising:
a mobile communication component that communicates over a mobile communication network;
an authentication module that automatically locks and unlocks a secured area of the mobile device based on an authentication mechanism; and
a processor, being a functional part of the mobile device and activated by the mobile communication component and the authentication module to facilitate communication, detection, locking and unlocking; and
a separate, proximity-based authentication component, selected by a user as the authentication mechanism used by the authentication module, the authentication module automatically detecting whether the separate, proximity-based authentication component is within a predefined proximity of the authentication module and, in response to detecting that the separate, proximity-based authentication component is within the predefined proximity, the authentication module automatically unlocking the secured area of the mobile device, and, in response to detecting that the separate, proximity-based authentication component is outside of the predefined proximity, the authentication module automatically locking the secured area of the mobile device.
12. The authentication system of claim 11 wherein the separate, proximity-based authentication component comprises a radio frequency identification (RFID) tag and wherein the authentication module further comprises:
an RFID reader that detects whether the RFID tag is within the predefined proximity by attempting to read the RFID tag.
13. The authentication system of claim 11 wherein the separate, proximity-based authentication component comprises a near field communication (NFC) device, and wherein the authentication component further comprises:
an NFC reader that detects whether the NFC device is within the predefined proximity by attempting to communicate with the NFC device.
14. The authentication system of claim 11 wherein the secured area comprises given functionality of the mobile device.
15. The authentication system of claim 11 wherein the secured area comprises given data accessible by the mobile device.
16. The authentication system of claim 1 wherein the secured area comprises one or more given applications run on the mobile device.
17. The authentication system of claim 1 wherein the secured area comprises given tasks performed with the mobile device.
18. A processor-implemented method of controlling a mobile device, comprising:
automatically detecting whether a separate, proximity-based authentication component is within a predefined proximity of the mobile device;
in response to detecting that the separate, proximity-based authentication component is within the predefined proximity, automatically unlocking a secured area of the mobile device; and
in response to detecting that the separate, proximity-based authentication component is outside of the predefined proximity, automatically locking the secured area of the mobile device.
19. The processor-implemented method of claim 18 wherein automatically detecting comprises:
automatically attempting to read a radio frequency identification (RFID) tag.
20. The processor-implemented method of claim 18 wherein automatically detecting comprises:
automatically attempting to read a near field communication (NFC) device.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/629,879 US20150172927A1 (en) | 2012-02-10 | 2015-02-24 | Mobile Device Authentication |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201261597564P | 2012-02-10 | 2012-02-10 | |
US13/763,088 US8995960B2 (en) | 2012-02-10 | 2013-02-08 | Mobile device authentication |
US14/629,879 US20150172927A1 (en) | 2012-02-10 | 2015-02-24 | Mobile Device Authentication |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/763,088 Continuation US8995960B2 (en) | 2012-02-10 | 2013-02-08 | Mobile device authentication |
Publications (1)
Publication Number | Publication Date |
---|---|
US20150172927A1 true US20150172927A1 (en) | 2015-06-18 |
Family
ID=49158083
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/763,088 Expired - Fee Related US8995960B2 (en) | 2012-02-10 | 2013-02-08 | Mobile device authentication |
US14/629,879 Abandoned US20150172927A1 (en) | 2012-02-10 | 2015-02-24 | Mobile Device Authentication |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/763,088 Expired - Fee Related US8995960B2 (en) | 2012-02-10 | 2013-02-08 | Mobile device authentication |
Country Status (1)
Country | Link |
---|---|
US (2) | US8995960B2 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160306955A1 (en) * | 2015-04-14 | 2016-10-20 | Intel Corporation | Performing user seamless authentications |
US10136326B2 (en) | 2017-04-24 | 2018-11-20 | International Business Machines Corporation | Mobile device locking |
US10172005B2 (en) | 2017-04-24 | 2019-01-01 | International Business Machines Corporation | Resonance frequency device locking |
Families Citing this family (225)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8645137B2 (en) | 2000-03-16 | 2014-02-04 | Apple Inc. | Fast, language-independent method for user authentication by voice |
US8677377B2 (en) | 2005-09-08 | 2014-03-18 | Apple Inc. | Method and apparatus for building an intelligent automated assistant |
US9318108B2 (en) | 2010-01-18 | 2016-04-19 | Apple Inc. | Intelligent automated assistant |
US8977255B2 (en) | 2007-04-03 | 2015-03-10 | Apple Inc. | Method and system for operating a multi-function portable electronic device using voice-activation |
US10002189B2 (en) | 2007-12-20 | 2018-06-19 | Apple Inc. | Method and apparatus for searching using an active ontology |
US9330720B2 (en) | 2008-01-03 | 2016-05-03 | Apple Inc. | Methods and apparatus for altering audio output signals |
US8996376B2 (en) | 2008-04-05 | 2015-03-31 | Apple Inc. | Intelligent text-to-speech conversion |
US20100030549A1 (en) | 2008-07-31 | 2010-02-04 | Lee Michael M | Mobile device having human language translation capability with positional feedback |
US8676904B2 (en) | 2008-10-02 | 2014-03-18 | Apple Inc. | Electronic devices with voice command and contextual data processing capabilities |
US20120311585A1 (en) | 2011-06-03 | 2012-12-06 | Apple Inc. | Organizing task items that represent tasks to perform |
US10241644B2 (en) | 2011-06-03 | 2019-03-26 | Apple Inc. | Actionable reminder entries |
US10241752B2 (en) | 2011-09-30 | 2019-03-26 | Apple Inc. | Interface for a virtual digital assistant |
US9431006B2 (en) | 2009-07-02 | 2016-08-30 | Apple Inc. | Methods and apparatuses for automatic speech recognition |
US10276170B2 (en) | 2010-01-18 | 2019-04-30 | Apple Inc. | Intelligent automated assistant |
US8682667B2 (en) | 2010-02-25 | 2014-03-25 | Apple Inc. | User profiling for selecting user specific voice input processing information |
US10082892B2 (en) | 2011-01-10 | 2018-09-25 | Apple Inc. | Button functionality |
US9262612B2 (en) | 2011-03-21 | 2016-02-16 | Apple Inc. | Device access using voice authentication |
US10057736B2 (en) | 2011-06-03 | 2018-08-21 | Apple Inc. | Active transport based notifications |
US8994660B2 (en) | 2011-08-29 | 2015-03-31 | Apple Inc. | Text correction processing |
US9002322B2 (en) | 2011-09-29 | 2015-04-07 | Apple Inc. | Authentication with secondary approver |
US8769624B2 (en) | 2011-09-29 | 2014-07-01 | Apple Inc. | Access control utilizing indirect authentication |
US10134385B2 (en) | 2012-03-02 | 2018-11-20 | Apple Inc. | Systems and methods for name pronunciation |
US10097496B2 (en) | 2012-05-09 | 2018-10-09 | Apple Inc. | Electronic mail user interface |
US10235014B2 (en) | 2012-05-09 | 2019-03-19 | Apple Inc. | Music user interface |
US10649622B2 (en) | 2012-05-09 | 2020-05-12 | Apple Inc. | Electronic message user interface |
US9280610B2 (en) | 2012-05-14 | 2016-03-08 | Apple Inc. | Crowd sourcing information to fulfill user requests |
US10417037B2 (en) | 2012-05-15 | 2019-09-17 | Apple Inc. | Systems and methods for integrating third party services with a digital assistant |
US9721563B2 (en) | 2012-06-08 | 2017-08-01 | Apple Inc. | Name recognition system |
US8855312B1 (en) * | 2012-06-29 | 2014-10-07 | Emc Corporation | Mobile trust broker |
US9569552B2 (en) * | 2012-07-31 | 2017-02-14 | D2L Corporation | Code based configuration of mobile devices |
US9547647B2 (en) | 2012-09-19 | 2017-01-17 | Apple Inc. | Voice-based media searching |
WO2014075734A1 (en) * | 2012-11-16 | 2014-05-22 | Telefonaktiebolaget L M Ericsson (Publ) | Vicinity-based multi-factor authentication |
US10199051B2 (en) | 2013-02-07 | 2019-02-05 | Apple Inc. | Voice trigger for a digital assistant |
US9432361B2 (en) * | 2013-03-13 | 2016-08-30 | Lookout, Inc. | System and method for changing security behavior of a device based on proximity to another device |
US10360364B2 (en) * | 2013-03-13 | 2019-07-23 | Lookout, Inc. | Method for changing mobile communication device functionality based upon receipt of a second code |
US9763097B2 (en) | 2013-03-13 | 2017-09-12 | Lookout, Inc. | Method for performing device security corrective actions based on loss of proximity to another device |
US11017069B2 (en) * | 2013-03-13 | 2021-05-25 | Lookout, Inc. | Method for changing mobile communications device functionality based upon receipt of a second code and the location of a key device |
US10652394B2 (en) | 2013-03-14 | 2020-05-12 | Apple Inc. | System and method for processing voicemail |
US10748529B1 (en) | 2013-03-15 | 2020-08-18 | Apple Inc. | Voice activated device for use with a voice-based digital assistant |
WO2014143776A2 (en) | 2013-03-15 | 2014-09-18 | Bodhi Technology Ventures Llc | Providing remote interactions with host device using a wireless device |
US9301139B2 (en) * | 2013-05-07 | 2016-03-29 | Prathamesh Anand Korgaonkar | System and method for multifactor authentication and login through smart wrist watch using near field communication |
WO2014197336A1 (en) | 2013-06-07 | 2014-12-11 | Apple Inc. | System and method for detecting errors in interactions with a voice-based digital assistant |
WO2014197334A2 (en) | 2013-06-07 | 2014-12-11 | Apple Inc. | System and method for user-specified pronunciation of words for speech synthesis and recognition |
US9582608B2 (en) | 2013-06-07 | 2017-02-28 | Apple Inc. | Unified ranking with entropy-weighted information for phrase-based semantic auto-completion |
WO2014197335A1 (en) | 2013-06-08 | 2014-12-11 | Apple Inc. | Interpreting and acting upon commands that involve sharing information with remote devices |
CN110442699A (en) | 2013-06-09 | 2019-11-12 | 苹果公司 | Operate method, computer-readable medium, electronic equipment and the system of digital assistants |
US10176167B2 (en) | 2013-06-09 | 2019-01-08 | Apple Inc. | System and method for inferring user intent from speech inputs |
US20150040198A1 (en) * | 2013-07-31 | 2015-02-05 | Wipro Limited | Systems and methods for accessing a device using a paired device in its proximity |
US9198041B2 (en) * | 2013-08-05 | 2015-11-24 | Nextek Power Systems, Inc. | Method of and system for authenticating a user to operate an electrical device |
US10001817B2 (en) | 2013-09-03 | 2018-06-19 | Apple Inc. | User interface for manipulating user interface objects with magnetic properties |
US9898642B2 (en) | 2013-09-09 | 2018-02-20 | Apple Inc. | Device, method, and graphical user interface for manipulating user interfaces based on fingerprint sensor inputs |
JP6349907B2 (en) * | 2013-11-18 | 2018-07-04 | 株式会社リコー | Information processing apparatus, information processing method, program, and image forming apparatus |
KR20150060275A (en) * | 2013-11-26 | 2015-06-03 | 삼성전자주식회사 | Electronic device and method for providing data service in electronic device |
US10296160B2 (en) | 2013-12-06 | 2019-05-21 | Apple Inc. | Method for extracting salient dialog usage from live data |
US9438587B2 (en) | 2013-12-13 | 2016-09-06 | Philip Hardy | System and method for user authentication |
US9483763B2 (en) | 2014-05-29 | 2016-11-01 | Apple Inc. | User interface for payments |
US9715875B2 (en) | 2014-05-30 | 2017-07-25 | Apple Inc. | Reducing the need for manual start/end-pointing and trigger phrases |
US10170123B2 (en) | 2014-05-30 | 2019-01-01 | Apple Inc. | Intelligent assistant for home automation |
EP3480811A1 (en) | 2014-05-30 | 2019-05-08 | Apple Inc. | Multi-command single utterance input method |
US9842101B2 (en) | 2014-05-30 | 2017-12-12 | Apple Inc. | Predictive conversion of language input |
US10313506B2 (en) | 2014-05-30 | 2019-06-04 | Apple Inc. | Wellness aggregator |
US9430463B2 (en) | 2014-05-30 | 2016-08-30 | Apple Inc. | Exemplar-based natural language processing |
WO2015183367A1 (en) | 2014-05-30 | 2015-12-03 | Apple Inc. | Continuity |
US9967401B2 (en) | 2014-05-30 | 2018-05-08 | Apple Inc. | User interface for phone call routing among devices |
US9633004B2 (en) | 2014-05-30 | 2017-04-25 | Apple Inc. | Better resolution when referencing to concepts |
CN104135753B (en) * | 2014-06-11 | 2016-01-20 | 腾讯科技(深圳)有限公司 | A kind of wireless network access method, device, terminal and server |
US9697385B2 (en) * | 2014-06-20 | 2017-07-04 | Google Inc. | Security adjustments in mobile devices |
US9264419B1 (en) * | 2014-06-26 | 2016-02-16 | Amazon Technologies, Inc. | Two factor authentication with authentication objects |
US9338493B2 (en) | 2014-06-30 | 2016-05-10 | Apple Inc. | Intelligent automated assistant for TV user interactions |
EP3862898A1 (en) * | 2014-08-15 | 2021-08-11 | Apple Inc. | Authenticated device used to unlock another device |
US10452253B2 (en) | 2014-08-15 | 2019-10-22 | Apple Inc. | Weather user interface |
US10339293B2 (en) | 2014-08-15 | 2019-07-02 | Apple Inc. | Authenticated device used to unlock another device |
WO2016030857A1 (en) * | 2014-08-28 | 2016-03-03 | Telezygology Inc | System for accessing a secure delivery |
WO2016036416A1 (en) | 2014-09-02 | 2016-03-10 | Apple Inc. | Button functionality |
US9547419B2 (en) | 2014-09-02 | 2017-01-17 | Apple Inc. | Reduced size configuration interface |
CN115623117A (en) | 2014-09-02 | 2023-01-17 | 苹果公司 | Telephone user interface |
WO2016036481A1 (en) | 2014-09-02 | 2016-03-10 | Apple Inc. | Reduced-size user interfaces for dynamically updated application overviews |
WO2016036413A1 (en) | 2014-09-02 | 2016-03-10 | Apple Inc. | Multi-dimensional object rearrangement |
EP3373122B1 (en) | 2014-09-02 | 2022-04-06 | Apple Inc. | Reduced-size interfaces for managing alerts |
US10066959B2 (en) | 2014-09-02 | 2018-09-04 | Apple Inc. | User interactions for a mapping application |
US9818400B2 (en) | 2014-09-11 | 2017-11-14 | Apple Inc. | Method and apparatus for discovering trending terms in speech requests |
US10789041B2 (en) | 2014-09-12 | 2020-09-29 | Apple Inc. | Dynamic thresholds for always listening speech trigger |
US9646609B2 (en) | 2014-09-30 | 2017-05-09 | Apple Inc. | Caching apparatus for serving phonetic pronunciations |
US10074360B2 (en) | 2014-09-30 | 2018-09-11 | Apple Inc. | Providing an indication of the suitability of speech recognition |
US9668121B2 (en) | 2014-09-30 | 2017-05-30 | Apple Inc. | Social reminders |
US10127911B2 (en) | 2014-09-30 | 2018-11-13 | Apple Inc. | Speaker identification and unsupervised speaker adaptation techniques |
US9886432B2 (en) | 2014-09-30 | 2018-02-06 | Apple Inc. | Parsimonious handling of word inflection via categorical stem + suffix N-gram language models |
EP3248384B1 (en) | 2015-01-19 | 2019-06-26 | Honeywell International Inc. | Automatic bump and calibration in gas detectors via short range wireless communication |
US9574896B2 (en) | 2015-02-13 | 2017-02-21 | Apple Inc. | Navigation user interface |
US10466883B2 (en) | 2015-03-02 | 2019-11-05 | Apple Inc. | Screenreader user interface |
US9865280B2 (en) | 2015-03-06 | 2018-01-09 | Apple Inc. | Structured dictation using intelligent automated assistants |
US10152299B2 (en) | 2015-03-06 | 2018-12-11 | Apple Inc. | Reducing response latency of intelligent automated assistants |
US10055121B2 (en) | 2015-03-07 | 2018-08-21 | Apple Inc. | Activity based thresholds and feedbacks |
US10567477B2 (en) | 2015-03-08 | 2020-02-18 | Apple Inc. | Virtual assistant continuity |
US9886953B2 (en) | 2015-03-08 | 2018-02-06 | Apple Inc. | Virtual assistant activation |
US10254911B2 (en) | 2015-03-08 | 2019-04-09 | Apple Inc. | Device configuration user interface |
US9721566B2 (en) | 2015-03-08 | 2017-08-01 | Apple Inc. | Competing devices responding to voice triggers |
US9899019B2 (en) | 2015-03-18 | 2018-02-20 | Apple Inc. | Systems and methods for structured stem and suffix language models |
US9842105B2 (en) | 2015-04-16 | 2017-12-12 | Apple Inc. | Parsimonious continuous-space phrase representations for natural language processing |
US10460227B2 (en) | 2015-05-15 | 2019-10-29 | Apple Inc. | Virtual assistant in a communication session |
US10083688B2 (en) | 2015-05-27 | 2018-09-25 | Apple Inc. | Device voice control for selecting a displayed affordance |
US10200824B2 (en) | 2015-05-27 | 2019-02-05 | Apple Inc. | Systems and methods for proactively identifying and surfacing relevant content on a touch-sensitive device |
US10127220B2 (en) | 2015-06-04 | 2018-11-13 | Apple Inc. | Language identification from short strings |
US9578173B2 (en) | 2015-06-05 | 2017-02-21 | Apple Inc. | Virtual assistant aided communication with 3rd party service in a communication session |
US20160358133A1 (en) | 2015-06-05 | 2016-12-08 | Apple Inc. | User interface for loyalty accounts and private label accounts for a wearable device |
US10101822B2 (en) | 2015-06-05 | 2018-10-16 | Apple Inc. | Language input correction |
US9916075B2 (en) | 2015-06-05 | 2018-03-13 | Apple Inc. | Formatting content for a reduced-size user interface |
US10186254B2 (en) | 2015-06-07 | 2019-01-22 | Apple Inc. | Context-based endpoint detection |
US10255907B2 (en) | 2015-06-07 | 2019-04-09 | Apple Inc. | Automatic accent detection using acoustic models |
US11025565B2 (en) | 2015-06-07 | 2021-06-01 | Apple Inc. | Personalized prediction of responses for instant messaging |
US20160378747A1 (en) | 2015-06-29 | 2016-12-29 | Apple Inc. | Virtual assistant for media playback |
US10033702B2 (en) * | 2015-08-05 | 2018-07-24 | Intralinks, Inc. | Systems and methods of secure data exchange |
US9743221B2 (en) | 2015-08-12 | 2017-08-22 | Honeywell International Inc. | User association with passive tags |
US9705570B2 (en) * | 2015-08-12 | 2017-07-11 | Honeywell International Inc. | Updating gas detector configuration using near field communication tags |
US10671428B2 (en) | 2015-09-08 | 2020-06-02 | Apple Inc. | Distributed personal assistant |
US10331312B2 (en) | 2015-09-08 | 2019-06-25 | Apple Inc. | Intelligent automated assistant in a media environment |
US10747498B2 (en) | 2015-09-08 | 2020-08-18 | Apple Inc. | Zero latency digital assistant |
US10740384B2 (en) | 2015-09-08 | 2020-08-11 | Apple Inc. | Intelligent automated assistant for media search and playback |
US9697820B2 (en) | 2015-09-24 | 2017-07-04 | Apple Inc. | Unit-selection text-to-speech synthesis using concatenation-sensitive neural networks |
US10366158B2 (en) | 2015-09-29 | 2019-07-30 | Apple Inc. | Efficient word encoding for recurrent neural network language models |
US11010550B2 (en) | 2015-09-29 | 2021-05-18 | Apple Inc. | Unified language modeling framework for word prediction, auto-completion and auto-correction |
US11587559B2 (en) | 2015-09-30 | 2023-02-21 | Apple Inc. | Intelligent device identification |
US10075845B2 (en) * | 2015-10-29 | 2018-09-11 | Ricoh Company, Ltd. | Authentication system, terminal apparatus, and authentication method |
US10691473B2 (en) | 2015-11-06 | 2020-06-23 | Apple Inc. | Intelligent automated assistant in a messaging environment |
US10956666B2 (en) | 2015-11-09 | 2021-03-23 | Apple Inc. | Unconventional virtual assistant interactions |
US10049668B2 (en) | 2015-12-02 | 2018-08-14 | Apple Inc. | Applying neural network language models to weighted finite state transducers for automatic speech recognition |
US10223066B2 (en) | 2015-12-23 | 2019-03-05 | Apple Inc. | Proactive assistance based on dialog communication between devices |
US10446143B2 (en) | 2016-03-14 | 2019-10-15 | Apple Inc. | Identification of voice inputs providing credentials |
DK179186B1 (en) | 2016-05-19 | 2018-01-15 | Apple Inc | REMOTE AUTHORIZATION TO CONTINUE WITH AN ACTION |
US9934775B2 (en) | 2016-05-26 | 2018-04-03 | Apple Inc. | Unit-selection text-to-speech synthesis based on predicted concatenation parameters |
US9972304B2 (en) | 2016-06-03 | 2018-05-15 | Apple Inc. | Privacy preserving distributed evaluation framework for embedded personalized systems |
US10249300B2 (en) | 2016-06-06 | 2019-04-02 | Apple Inc. | Intelligent list reading |
US11227589B2 (en) | 2016-06-06 | 2022-01-18 | Apple Inc. | Intelligent list reading |
US10049663B2 (en) | 2016-06-08 | 2018-08-14 | Apple, Inc. | Intelligent automated assistant for media exploration |
DK179309B1 (en) | 2016-06-09 | 2018-04-23 | Apple Inc | Intelligent automated assistant in a home environment |
US10192552B2 (en) | 2016-06-10 | 2019-01-29 | Apple Inc. | Digital assistant providing whispered speech |
US10509862B2 (en) | 2016-06-10 | 2019-12-17 | Apple Inc. | Dynamic phrase expansion of language input |
US10490187B2 (en) | 2016-06-10 | 2019-11-26 | Apple Inc. | Digital assistant providing automated status report |
US10586535B2 (en) | 2016-06-10 | 2020-03-10 | Apple Inc. | Intelligent digital assistant in a multi-tasking environment |
US10067938B2 (en) | 2016-06-10 | 2018-09-04 | Apple Inc. | Multilingual word prediction |
DK179049B1 (en) | 2016-06-11 | 2017-09-18 | Apple Inc | Data driven natural language event detection and classification |
DK201670540A1 (en) | 2016-06-11 | 2018-01-08 | Apple Inc | Application integration with a digital assistant |
DK179415B1 (en) | 2016-06-11 | 2018-06-14 | Apple Inc | Intelligent device arbitration and control |
DK179343B1 (en) | 2016-06-11 | 2018-05-14 | Apple Inc | Intelligent task discovery |
DK201670622A1 (en) | 2016-06-12 | 2018-02-12 | Apple Inc | User interfaces for transactions |
US10474753B2 (en) | 2016-09-07 | 2019-11-12 | Apple Inc. | Language identification using recurrent neural networks |
US10043516B2 (en) | 2016-09-23 | 2018-08-07 | Apple Inc. | Intelligent automated assistant |
US11281993B2 (en) | 2016-12-05 | 2022-03-22 | Apple Inc. | Model and ensemble compression for metric learning |
US10593346B2 (en) | 2016-12-22 | 2020-03-17 | Apple Inc. | Rank-reduced token representation for automatic speech recognition |
US11204787B2 (en) | 2017-01-09 | 2021-12-21 | Apple Inc. | Application integration with a digital assistant |
US11431836B2 (en) | 2017-05-02 | 2022-08-30 | Apple Inc. | Methods and interfaces for initiating media playback |
US10992795B2 (en) | 2017-05-16 | 2021-04-27 | Apple Inc. | Methods and interfaces for home media control |
DK201770383A1 (en) | 2017-05-09 | 2018-12-14 | Apple Inc. | User interface for correcting recognition errors |
US10417266B2 (en) | 2017-05-09 | 2019-09-17 | Apple Inc. | Context-aware ranking of intelligent response suggestions |
US10395654B2 (en) | 2017-05-11 | 2019-08-27 | Apple Inc. | Text normalization based on a data-driven learning network |
DK201770439A1 (en) | 2017-05-11 | 2018-12-13 | Apple Inc. | Offline personal assistant |
US10726832B2 (en) | 2017-05-11 | 2020-07-28 | Apple Inc. | Maintaining privacy of personal information |
DK180048B1 (en) | 2017-05-11 | 2020-02-04 | Apple Inc. | MAINTAINING THE DATA PROTECTION OF PERSONAL INFORMATION |
DK179496B1 (en) | 2017-05-12 | 2019-01-15 | Apple Inc. | USER-SPECIFIC Acoustic Models |
DK179745B1 (en) | 2017-05-12 | 2019-05-01 | Apple Inc. | SYNCHRONIZATION AND TASK DELEGATION OF A DIGITAL ASSISTANT |
DK201770428A1 (en) | 2017-05-12 | 2019-02-18 | Apple Inc. | Low-latency intelligent automated assistant |
US11301477B2 (en) | 2017-05-12 | 2022-04-12 | Apple Inc. | Feedback analysis of a digital assistant |
DK201770431A1 (en) | 2017-05-15 | 2018-12-20 | Apple Inc. | Optimizing dialogue policy decisions for digital assistants using implicit feedback |
DK201770432A1 (en) | 2017-05-15 | 2018-12-21 | Apple Inc. | Hierarchical belief states for digital assistants |
US20180336892A1 (en) | 2017-05-16 | 2018-11-22 | Apple Inc. | Detecting a trigger of a digital assistant |
US20180336275A1 (en) | 2017-05-16 | 2018-11-22 | Apple Inc. | Intelligent automated assistant for media exploration |
US10311144B2 (en) | 2017-05-16 | 2019-06-04 | Apple Inc. | Emoji word sense disambiguation |
CN111343060B (en) | 2017-05-16 | 2022-02-11 | 苹果公司 | Method and interface for home media control |
US10403278B2 (en) | 2017-05-16 | 2019-09-03 | Apple Inc. | Methods and systems for phonetic matching in digital assistant services |
DK179549B1 (en) | 2017-05-16 | 2019-02-12 | Apple Inc. | Far-field extension for digital assistant services |
US20220279063A1 (en) | 2017-05-16 | 2022-09-01 | Apple Inc. | Methods and interfaces for home media control |
US10657328B2 (en) | 2017-06-02 | 2020-05-19 | Apple Inc. | Multi-task recurrent neural network architecture for efficient morphology handling in neural language modeling |
US10244374B2 (en) * | 2017-07-17 | 2019-03-26 | Otis Elevator Company | Service tool proximity detection |
US10669122B2 (en) | 2017-07-17 | 2020-06-02 | Otis Elevator Company | Service tool location-based function availability |
US10445429B2 (en) | 2017-09-21 | 2019-10-15 | Apple Inc. | Natural language understanding using vocabularies with compressed serialized tries |
US10755051B2 (en) | 2017-09-29 | 2020-08-25 | Apple Inc. | Rule-based natural language processing |
US10636424B2 (en) | 2017-11-30 | 2020-04-28 | Apple Inc. | Multi-turn canned dialog |
US10733982B2 (en) | 2018-01-08 | 2020-08-04 | Apple Inc. | Multi-directional dialog |
EP4274286A3 (en) | 2018-01-22 | 2023-12-27 | Apple Inc. | Secure login with authentication based on a visual representation of data |
KR102530441B1 (en) * | 2018-01-29 | 2023-05-09 | 삼성전자주식회사 | Electronic device, external electronic device, system comprising the same and control method thereof |
US10733375B2 (en) | 2018-01-31 | 2020-08-04 | Apple Inc. | Knowledge-based framework for improving natural language understanding |
US10789959B2 (en) | 2018-03-02 | 2020-09-29 | Apple Inc. | Training speaker recognition models for digital assistants |
US10592604B2 (en) | 2018-03-12 | 2020-03-17 | Apple Inc. | Inverse text normalization for automatic speech recognition |
US10818288B2 (en) | 2018-03-26 | 2020-10-27 | Apple Inc. | Natural assistant interaction |
US10909331B2 (en) | 2018-03-30 | 2021-02-02 | Apple Inc. | Implicit identification of translation payload with neural machine translation |
US11145294B2 (en) | 2018-05-07 | 2021-10-12 | Apple Inc. | Intelligent automated assistant for delivering content from user experiences |
US10928918B2 (en) | 2018-05-07 | 2021-02-23 | Apple Inc. | Raise to speak |
US10984780B2 (en) | 2018-05-21 | 2021-04-20 | Apple Inc. | Global semantic word embeddings using bi-directional recurrent neural networks |
DK201870355A1 (en) | 2018-06-01 | 2019-12-16 | Apple Inc. | Virtual assistant operation in multi-device environments |
US10892996B2 (en) | 2018-06-01 | 2021-01-12 | Apple Inc. | Variable latency device coordination |
US11386266B2 (en) | 2018-06-01 | 2022-07-12 | Apple Inc. | Text correction |
DK179822B1 (en) | 2018-06-01 | 2019-07-12 | Apple Inc. | Voice interaction at a primary device to access call functionality of a companion device |
DK180639B1 (en) | 2018-06-01 | 2021-11-04 | Apple Inc | DISABILITY OF ATTENTION-ATTENTIVE VIRTUAL ASSISTANT |
US11076039B2 (en) | 2018-06-03 | 2021-07-27 | Apple Inc. | Accelerated task performance |
US11010561B2 (en) | 2018-09-27 | 2021-05-18 | Apple Inc. | Sentiment prediction from textual data |
US11462215B2 (en) | 2018-09-28 | 2022-10-04 | Apple Inc. | Multi-modal inputs for voice commands |
US11170166B2 (en) | 2018-09-28 | 2021-11-09 | Apple Inc. | Neural typographical error modeling via generative adversarial networks |
US10839159B2 (en) | 2018-09-28 | 2020-11-17 | Apple Inc. | Named entity normalization in a spoken dialog system |
US11475898B2 (en) | 2018-10-26 | 2022-10-18 | Apple Inc. | Low-latency multi-speaker speech recognition |
US11638059B2 (en) | 2019-01-04 | 2023-04-25 | Apple Inc. | Content playback on multiple devices |
US11348573B2 (en) | 2019-03-18 | 2022-05-31 | Apple Inc. | Multimodality in digital assistant systems |
DK201970509A1 (en) | 2019-05-06 | 2021-01-15 | Apple Inc | Spoken notifications |
US11307752B2 (en) | 2019-05-06 | 2022-04-19 | Apple Inc. | User configurable task triggers |
US11423908B2 (en) | 2019-05-06 | 2022-08-23 | Apple Inc. | Interpreting spoken requests |
US11475884B2 (en) | 2019-05-06 | 2022-10-18 | Apple Inc. | Reducing digital assistant latency when a language is incorrectly determined |
US11140099B2 (en) | 2019-05-21 | 2021-10-05 | Apple Inc. | Providing message response suggestions |
DK201970510A1 (en) | 2019-05-31 | 2021-02-11 | Apple Inc | Voice identification in digital assistant systems |
US11496600B2 (en) | 2019-05-31 | 2022-11-08 | Apple Inc. | Remote execution of machine-learned models |
US11289073B2 (en) | 2019-05-31 | 2022-03-29 | Apple Inc. | Device text to speech |
DK180129B1 (en) | 2019-05-31 | 2020-06-02 | Apple Inc. | User activity shortcut suggestions |
KR102436985B1 (en) | 2019-05-31 | 2022-08-29 | 애플 인크. | User interface for controlling audio media |
US11010121B2 (en) | 2019-05-31 | 2021-05-18 | Apple Inc. | User interfaces for audio media control |
US11468890B2 (en) | 2019-06-01 | 2022-10-11 | Apple Inc. | Methods and user interfaces for voice-based control of electronic devices |
US11360641B2 (en) | 2019-06-01 | 2022-06-14 | Apple Inc. | Increasing the relevance of new available information |
US11463449B2 (en) * | 2019-06-24 | 2022-10-04 | Motorola Mobility Llc | Authentication for key access |
WO2021056255A1 (en) | 2019-09-25 | 2021-04-01 | Apple Inc. | Text detection using global geometry estimators |
US11093944B1 (en) | 2020-04-30 | 2021-08-17 | Capital One Services, Llc | Systems and methods for peer-to-peer identity verification |
US11043220B1 (en) | 2020-05-11 | 2021-06-22 | Apple Inc. | Digital assistant hardware abstraction |
US11061543B1 (en) | 2020-05-11 | 2021-07-13 | Apple Inc. | Providing relevant data items based on context |
US11755276B2 (en) | 2020-05-12 | 2023-09-12 | Apple Inc. | Reducing description length based on confidence |
US11490204B2 (en) | 2020-07-20 | 2022-11-01 | Apple Inc. | Multi-device audio adjustment coordination |
US11438683B2 (en) | 2020-07-21 | 2022-09-06 | Apple Inc. | User identification using headphones |
US11392291B2 (en) | 2020-09-25 | 2022-07-19 | Apple Inc. | Methods and interfaces for media control with dynamic feedback |
US11942090B2 (en) | 2021-06-04 | 2024-03-26 | Apple Inc. | Accessory device based authentication for digital assistant requests |
US11847378B2 (en) | 2021-06-06 | 2023-12-19 | Apple Inc. | User interfaces for audio routing |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060105745A1 (en) * | 2004-10-22 | 2006-05-18 | Frank Edward H | System and method for protecting data provided by a cellular telephone |
US20080163345A1 (en) * | 2007-01-03 | 2008-07-03 | Bauman Amanda J | Rfid tag-based authentication for e-mail |
US20100323664A1 (en) * | 2009-06-18 | 2010-12-23 | Girish Sivaram | Dedicated memory partitions for users of a shared mobile device |
US20110111698A1 (en) * | 2009-11-10 | 2011-05-12 | Kabushiki Kaisha Toshiba | Electronic apparatus and access control method |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4655439B2 (en) * | 2001-09-13 | 2011-03-23 | ソニー株式会社 | Information processing apparatus and method, and program |
US7257374B1 (en) * | 2004-12-10 | 2007-08-14 | Cingular Wireless Ii, Llc | Automatic security locking method and system for wireless-enabled devices |
US7403743B2 (en) * | 2004-12-31 | 2008-07-22 | Sony Ericsson Mobile Communications Ab | System and method to unlock hidden multimedia content |
JP5450959B2 (en) * | 2006-02-08 | 2014-03-26 | 日本電気株式会社 | Portable terminal, portable terminal control method, portable terminal control program, and recording medium |
US8424079B2 (en) * | 2008-01-25 | 2013-04-16 | Research In Motion Limited | Method, system and mobile device employing enhanced user authentication |
US20100081414A1 (en) * | 2008-09-30 | 2010-04-01 | David Poisner | Backup pin entry using camera and ocr |
US8509808B2 (en) * | 2011-03-29 | 2013-08-13 | Research In Motion Limited | Mobile wireless communications device having a near field communication (NFC) device and providing memory disabling and related |
-
2013
- 2013-02-08 US US13/763,088 patent/US8995960B2/en not_active Expired - Fee Related
-
2015
- 2015-02-24 US US14/629,879 patent/US20150172927A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060105745A1 (en) * | 2004-10-22 | 2006-05-18 | Frank Edward H | System and method for protecting data provided by a cellular telephone |
US20080163345A1 (en) * | 2007-01-03 | 2008-07-03 | Bauman Amanda J | Rfid tag-based authentication for e-mail |
US20100323664A1 (en) * | 2009-06-18 | 2010-12-23 | Girish Sivaram | Dedicated memory partitions for users of a shared mobile device |
US20110111698A1 (en) * | 2009-11-10 | 2011-05-12 | Kabushiki Kaisha Toshiba | Electronic apparatus and access control method |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160306955A1 (en) * | 2015-04-14 | 2016-10-20 | Intel Corporation | Performing user seamless authentications |
US10136326B2 (en) | 2017-04-24 | 2018-11-20 | International Business Machines Corporation | Mobile device locking |
US10149167B2 (en) | 2017-04-24 | 2018-12-04 | International Business Machines Corporation | Mobile device locking |
US10172005B2 (en) | 2017-04-24 | 2019-01-01 | International Business Machines Corporation | Resonance frequency device locking |
US10368245B2 (en) | 2017-04-24 | 2019-07-30 | International Business Machines Corporation | Mobile device locking |
US10375575B2 (en) | 2017-04-24 | 2019-08-06 | International Business Machines Corporation | Mobile device locking |
US10588020B2 (en) | 2017-04-24 | 2020-03-10 | International Business Machines Corporation | Resonance frequency device locking |
US10701563B2 (en) | 2017-04-24 | 2020-06-30 | International Business Machines Corporation | Mobile device locking |
US10708784B2 (en) | 2017-04-24 | 2020-07-07 | International Business Machines Corporation | Mobile device locking |
Also Published As
Publication number | Publication date |
---|---|
US20130244615A1 (en) | 2013-09-19 |
US8995960B2 (en) | 2015-03-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8995960B2 (en) | Mobile device authentication | |
US11263303B1 (en) | Pattern-based mobile device unlocking | |
US10523670B2 (en) | Devices, systems, and methods for security using magnetic field based identification | |
TWI574197B (en) | Systems and methods for gesture lock obfuscation | |
US8955063B2 (en) | Terminal device authentication method, terminal device and program | |
US20130085941A1 (en) | Systems and methods for secure wireless financial transactions | |
US20100082490A1 (en) | Systems and methods for secure wireless transactions | |
CN106959841A (en) | The call method and device of function in a kind of application | |
US20100138914A1 (en) | System and method of providing biometric quick launch | |
US11171951B2 (en) | Device interface output based on biometric input orientation and captured proximate data | |
CN106355141B (en) | Portable electronic device and operation method thereof | |
CN111758095A (en) | Method and terminal for quickly opening application or application function | |
EP2192519B1 (en) | System and method of providing biometric quick launch | |
Agrawal et al. | Smart Authentication for smart phones | |
KR100562144B1 (en) | Method of displaying for finger image in wireless communication terminal | |
EP3786820A1 (en) | Authentication system, authentication device, authentication method, and program | |
JP2006191245A (en) | Dial lock function authentication unit and its method, and portable terminal employing it | |
EP3566163A1 (en) | Method for authenticating a first user and corresponding first device and system | |
US11928199B2 (en) | Authentication system, authentication device, authentication method and program | |
US10762182B2 (en) | Detection system, fingerprint sensor, and method of finger touch authentication thereof | |
KR100693592B1 (en) | Method of key setup/execution using fingerprint recognition and wireless communication terminal using it | |
KR20150063899A (en) | Method and Device for Unlocking Input using the Combination of Password Number and Pattern Image Input of Smartphone | |
CN102484590A (en) | Login system and login method | |
CN117043769A (en) | Access control for applications | |
JP2024510660A (en) | multi finger sensor |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |